Location procedures in non-terrestrial networks

Abstract

A method may include receiving, by a wireless device, one or more non-terrestrial network (NTN) configuration parameters indicating a validity timer. The validity timer may indicate a maximum duration for which the one or more NTN configuration parameters are valid. The method may also include starting the validity timer in response to receiving the one or more NTN configuration parameters. The method may further include initiating a positioning procedure based on receiving a message requesting one or more measurements. The method may additionally include stopping the positioning procedure based on the validity timer.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 409,083, filed on September 22, 2022, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Examples of several of the various embodiments of the present disclosure are described herein with reference to the accompanying drawings.

[0004] Figure 1A and Figure 1B An example mobile communications network is shown in which embodiments of the present disclosure may be implemented.

[0005] Figure 2A and Figure 2B The New Radio (NR) user plane and control plane protocol stacks are shown separately.

[0006] Figure 3 Shown in Figure 2A Examples of services provided between the protocol layers of the NR user plane protocol stack.

[0007] Figure 4A Shows the flow Figure 2A Figure 2. Example downlink data flow of the NR user plane protocol stack.

[0008] Figure 4B An example format of a MAC subheader in a MAC PDU is shown.

[0009] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels for downlink and uplink are shown respectively.

[0010] Figure 6 is an example diagram showing RRC state transition of a UE.

[0011] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown.

[0012] Figure 8 An example configuration of slots in the time and frequency domain of an NR carrier is shown.

[0013] Fig. 9 An example of bandwidth adaptation using three configured BWPs for NR carriers is shown.

[0014] Fig. 10A Three carrier aggregation configurations with two component carriers are shown.

[0015] Fig. 10BAn example of how aggregated cells may be configured into one or more PUCCH groups is shown.

[0016] Fig.11A An example of SS / PBCH block structure and location is shown.

[0017] Fig. 11B An example of CSI-RS mapped in time and frequency domains is shown.

[0018] Fig. 12A and Fig. 12B Three examples of downlink and uplink beam management procedures are shown respectively.

[0019] Fig.13A , Fig. 13B and Fig. 13C A four-step contention-based random access procedure, a two-step contention-free random access procedure and another two-step random access procedure are shown respectively.

[0020] Fig.14A An example of a CORESET configuration for the bandwidth portion is shown.

[0021] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown.

[0022] Fig.15 An example of a wireless device communicating with a base station is shown.

[0023] Fig.16A , Fig. 16B , Fig. 16C and Fig.16D Example structures for uplink and downlink transmissions are shown.

[0024] Fig.17 Several DCI formats are shown.

[0025] Fig.18A An example of a non-terrestrial network is shown.

[0026] Fig.18B Figure 1 is an example diagram of different types of NTN platforms.

[0027] Fig.19A An example of an NTN with a transparent NTN platform is shown.

[0028] Fig.19B Examples of propagation delays corresponding to NTNs of different heights are shown.

[0029] Fig. 20 An example embodiment of a positioning procedure in a wireless communication system according to aspects of the present disclosure is shown.

[0030] Fig.21 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown.

[0031] Fig. 22 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown.

[0032] Fig.23 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0033] In the present disclosure, various embodiments are presented in the form of examples of how the disclosed technology can be implemented and / or how the disclosed technology can be practiced in environments and scenarios. It will be apparent to those skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope of the present invention. In fact, after reading the specification, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. The embodiments of the present invention should not be limited by any described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Restrictions, features and / or elements from the disclosed example embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figure highlighting functionality and advantages is provided for exemplary purposes only. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or only optionally used in certain embodiments.

[0034] Embodiments may be configured to operate as desired. For example, in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., when certain criteria are met, the disclosed mechanism may be executed. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various example embodiments may be applied. Therefore, example embodiments that selectively implement the disclosed protocol may be implemented.

[0035] A base station may communicate with a mixture of wireless devices. A wireless device and / or base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not comply with the disclosed method, for example, these wireless devices or base stations may perform based on older versions of LTE or 5G technology.

[0036] In the present disclosure, "a" and "an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase after the term "may" is an example of one of a variety of suitable possibilities that may or may not be used for one or more of the various embodiments. As used herein, the terms "comprising" and "consisting of..." list one or more components of the element being described. The terms "comprising" and "including" are interchangeable and do not exclude that unlisted components are included in the element being described. In contrast, "consisting of..." provides a complete listing of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on". As used herein, the term "and / or" represents any possible combination of the listed elements. For example, “A, B and / or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0037] If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopt / use" (or equivalently "at least adopt / use") indicates that the phrase after the phrase "adopt / use" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0038] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may refer to a specific setting in a device that affects the operating characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. Terms such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0039] In the present disclosure, a parameter (or equivalently referred to as a field or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE) N contains parameter (IE) M, and parameter (IE) M contains parameter (IE) K, and parameter (IE) K contains parameter (information element) J. Then, for example, N contains K, and N contains J. In an example embodiment, when one or more messages contain multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0040] Many of the features set forth are described as optional, either by the use of "may" or by the use of parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, i.e., having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0041] Many elements described in the disclosed embodiments can be implemented as modules. Modules are defined here as elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language, which is configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript). It is possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs and CPLDs are often programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between internal hardware blocks with fewer functions on the programmable devices. The mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0042] Figure 1A 1 shows an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) operated by a network operator. Figure 1A As shown, the mobile communication network 100 includes a core network (CN) 102 , a radio access network (RAN) 104 , and wireless devices 106 .

[0043] CN 102 may provide an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-carrier DNs, for wireless device 106. As part of the interface functionality, CN 102 may set up an end-to-end connection between wireless device 106 and one or more DNs, authenticate wireless device 106, and provide charging functionality.

[0044] The RAN 104 may connect the CN 102 to the wireless device 106 via radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The direction of communication from the RAN 104 to the wireless device 106 over the air interface is referred to as downlink, while the direction of communication from the wireless device 106 to the RAN 104 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0045] The term "wireless device" may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicle roadside unit (RSU), a relay node, a car, and / or any combination thereof. The term "wireless device" encompasses other terms including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0046] The RAN 104 may include one or more base stations (not shown). The term "base station" may be used throughout this disclosure to mean and encompass: a Node B (associated with UMTS and / or 3G standards); an evolved Node B (eNB, associated with E-UTRA and / or 4G standards); a remote radio head (RRH); a baseband processing unit coupled to one or more RRHs; a repeater node or relay node used to extend the coverage area of ​​a donor node; a next generation evolved Node B (ng-eNB); a generation Node B (gNB, associated with NR and / or 5G standards); an access point (AP, associated with, for example, WiFi or any other suitable wireless communication standard); and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0047] The base stations included in the RAN 104 may include one or more sets of antennas for communicating with the wireless devices 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to control three cells (or sectors) respectively. The size of a cell may be determined by the range at which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. The cells of the base stations may together provide radio coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0048] In addition to three-sector sites, other implementations of the base station are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectorized site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, a baseband processing unit coupled to several remote radio heads (RRHs), and / or a repeater or relay node for extending the coverage area of ​​a donor node. The baseband processing unit coupled to the RRH may be part of a centralized or cloud RAN architecture, in which the baseband processing unit may be concentrated in a baseband processing unit pool or virtualized. The repeater node may amplify and replay the radio signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the radio signal received from the donor node to eliminate noise before amplifying and replaying the radio signal.

[0049] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna types and similar high levels of transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, a small cell base station may be used to provide a small coverage area, such as a coverage area that overlaps with a relatively large coverage area provided by a macrocell base station. Small coverage areas may be provided in areas with high data traffic (or so-called "hot spots") or in areas where macrocell coverage is weak. Examples of small cell base stations include, in descending order of coverage area: microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0050] The Third Generation Partnership Project (3GPP) was established in 1998 to Figure 1A 3GPP provides global specification standardization for mobile communication networks similar to the mobile communication network 100 in the present invention. To date, 3GPP has developed specifications for three generations of mobile networks: the third generation (3G) network known as the Universal Mobile Telecommunications System (UMTS), the fourth generation (4G) network known as the Long Term Evolution (LTE), and the fifth generation (5G) network known as the 5G System (5GS). The embodiments of the present disclosure are described with reference to the RAN of the 3GPP 5G network known as the Next Generation RAN (NG-RAN). These embodiments may be applicable to the RAN of other mobile communication networks, such as Figure 1A The RAN 104 in 5G networks, the RANs of early 3G and 4G networks, and those of yet-to-be-specified future networks (e.g., 3GPP 6G networks). The NG-RAN implements the 5G radio access technology known as New Radio (NR) and may be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0051] Figure 1B Another example mobile communication network 150 is shown in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN operated by a network operator. Figure 1B As shown in FIG. 1 , the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively referred to as UE 156). Figure 1A The corresponding components described are implemented and operate in the same or similar manner.

[0052] 5G-CN 152 provides an interface to one or more DNs, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN, to UE 156. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and the one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CN of the 3GPP 4G network, the basis of 5G-CN152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as network functions that provide services to other network functions via interfaces. The network functions of 5G-CN 152 may be implemented in several ways, including as a network element on dedicated or shared hardware, as a software instance running on dedicated or shared hardware, or as a virtualized function instantiated on a platform (e.g., a cloud-based platform).

[0053] like Figure 1B As shown, 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B. For ease of explanation, Figure 1BThey are shown as one component AMF / UPF 158 in FIG. UPF 158B can act as a gateway between NG-RAN 154 and the one or more DNs. UPF 158B can perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, service usage reporting, uplink classification supporting routing of service flows to the one or more DNs, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement and uplink service verification), downlink packet buffering and downlink data notification triggering. UPF 158B can act as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected with the one or more DNs, and / or a fulcrum for supporting multi-host PDU sessions. UE 156 can be configured to receive services through a PDU session, which is a logical connection between the UE and the DN.

[0054] The AMF 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights verification, mobility management control (subscription and policy), network slicing support and / or session management function (SMF) selection. NAS may refer to functions operating between CN and UE, and AS may refer to functions operating between UE and RAN.

[0055] 5G-CN 152 may include Figure 1B , one or more additional network functions shown in . For example, 5G-CN 152 may include one or more of the following: session management function (SMF), NR repository function (NRF), policy control function (PCF), network exposure function (NEF), unified data management (UDM), application function (AF) and / or authentication server function (AUSF).

[0056] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via radio communications over an air interface. The NG-RAN 154 may include: one or more gNBs, shown as gNB 160A and gNB 160B (collectively referred to as gNB 160); and / or one or more ng-eNBs, shown as ng-eNB 162A and ng-eNB 162B (collectively referred to as ng-eNB 162). The gNB 160 and ng-eNB 162 may be more generally referred to as base stations. The gNB 160 and ng-eNB 162 may include one or more groups of antennas for communicating with the UE 156 over an air interface. For example, one or more gNBs in the gNB 160 and / or one or more ng-eNBs in the ng-eNB 162 may include three groups of antennas to control three cells (or sectors), respectively. The cells of gNB 160 and ng-eNB 162 may together provide radio coverage to UE 156 over a wide geographic area to support UE mobility.

[0057] like Figure 1B As shown in FIG, gNB 160 and / or ng-eNB 162 may be connected to 5G-CN 152 via an NG interface and to other base stations via an Xn interface. NG and Xn interfaces may be established using direct physical connections and / or indirect connections through underlying transport networks such as Internet Protocol (IP) transport networks. gNB 160 and / or ng-eNB 162 may be connected to UE 156 via a Uu interface. For example, Figure 1B As shown in FIG. 1 , gNB 160A may be connected to UE 156A via a Uu interface. NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stack associated with the interface may be composed of Figure 1B The network elements in a network are used to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data that the user is interested in. The control plane may process signaling messages that the network elements are interested in.

[0058] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of a NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane PDUs (e.g., non-guaranteed delivery) between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of a NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, delivery of NAS messages, paging, PDU session management, and configuration delivery and / or warning message transmission.

[0059] The gNB 160 may provide NR user plane and control plane protocol terminations to the UE 156 via a Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations to the UE 156A via a Uu interface associated with the first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 156 via a Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations to the UE 156B via a Uu interface associated with the second protocol stack.

[0060] 5G-CN 152 is described as being configured to handle both NR and 4G radio access. One of ordinary skill in the art will appreciate that it is possible for NR to be connected to a 4G core network in a mode known as "non-standalone operation". In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although Figure 1B Only one AMF / UPF 158 is shown in the figure, but a gNB or ng-eNB can be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0061] As discussed, Figure 1B The interfaces between network elements in a network (e.g., Uu, Xn, and NG interfaces) may be associated with a protocol stack used by the network elements to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. The user plane may process data of interest to the user, while the control plane may process signaling messages of interest to the network elements.

[0062] Figure 2A and Figure 2B Examples of NR user plane and NR control plane protocol stacks for the Uu interface between UE 210 and gNB 220 are shown, respectively. Figure 2A and Figure 2B The protocol stack shown in can be used with e.g. Figure 1B The protocol stacks of the Uu interface between UE156A and gNB 160A shown in are the same or similar.

[0063] Figure 2A An NR user plane protocol stack including five layers implemented in a UE 210 and a gNB 220 is shown. At the bottom of the protocol stack, the physical layer (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The next four protocols above the PHY 211 and 221 include a media access control layer (MAC) 212 and 222, a radio link control layer (RLC) 213 and 223, a packet data convergence protocol layer (PDCP) 214 and 224, and a service data application protocol layer (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0064] Figure 3 An example of services provided between protocol layers of the NR user plane protocol stack is shown. Figure 2A and Figure 3 Starting from the top of , SDAP 215 and 225 can perform QoS flow processing. UE 210 can receive services through a PDU session, which can be a logical connection between UE 210 and DN. A PDU session can have one or more QoS flows. The UPF of the CN (e.g., UPF 158B) can map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate and / or error rate). SDAP 215 and 225 can perform mapping / demapping between the one or more QoS flows and one or more data radio bearers. The mapping / demapping between the QoS flows and the data radio bearers can be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 can learn the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / demapping between QoS flows and data radio bearers.

[0065] The PDCP 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, may perform encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and may perform integrity protection to ensure that control messages originate from the intended source. The PDCP 214 and 224 may perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and removal of duplicate received packets due to, for example, intra-gNB handovers. The PDCP 214 and 224 may perform packet repetition to increase the likelihood that a packet is received, and remove any duplicate packets at the receiver. Packet repetition may be applicable to services that require high reliability.

[0066] although Figure 3 Not shown, but PDCP 214 and 224 can perform mapping / de-mapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technology that allows a UE to connect to two cells or more generally to two cell groups: a primary cell group (MCG) and a secondary cell group (SCG). A split bearer is a split bearer when a single radio bearer (such as one of the radio bearers provided by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. PDCP 214 and 224 can map / demapped split radio bearers between RLC channels belonging to a cell group.

[0067] RLC 213 and 223 can perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from MAC 212 and 222, respectively. RLC 213 and 223 can support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC can perform one or more of the functions described. RLC configuration can be based on each logical channel, independent of parameter sets and / or transmission time interval (TTI) duration. As shown in FIG. Figure 3 As shown in FIG. 1 , RLC 213 and 223 may provide RLC channels as services to PDCP 214 and 224, respectively.

[0068] The MAC 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units belonging to the one or more logical channels into / from a transport block (TB) delivered to / from the PHY 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs with the aid of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction by hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the UE 210 with the aid of logical channel prioritization, and / or padding. The MAC 212 and 222 may support one or more parameter sets and / or transmission timing. In an example, mapping restrictions in logical channel prioritization may control which parameter sets and / or transmission timings a logical channel may use. Figure 3 As shown, MAC 212 and 222 may provide logical channels as services to RLC 213 and 223 .

[0069] PHY 211 and 221 can perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. PHY 211 and 221 can perform multi-antenna mapping. Figure 3 As shown in , PHY 211 and 221 may provide one or more transport channels as a service to MAC 212 and 222 .

[0070] Figure 4A An example downlink data flow through the NR user plane protocol stack is shown. Figure 4A The downlink data flow of three IP packets (n, n+1, and m) flowing through the NR user plane protocol stack to generate two TBs at the gNB 220 is shown. The uplink data flow flowing through the NR user plane protocol stack can be the same as Figure 4A The downlink data flow is similar to that depicted in .

[0071] Figure 4A The downlink data flow of starts when SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to a radio bearer. Figure 4A In the SDAP header (in Figure 4AThe data unit from / to a higher protocol layer is called a service data unit (SDU) of the lower protocol layer, and the data unit to / from a lower protocol layer is called a protocol data unit (PDU) of the higher protocol layer. Figure 4A As shown in , the data unit from SDAP 225 is the SDU of the lower protocol layer PDCP 224 and is the PDU of SDAP 225 .

[0072] Figure 4A The remaining protocol layers in can perform their associated functions (e.g., Figure 3 ), add the corresponding headers, and forward their corresponding outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption, and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., Figure 4A 222) and forwards its output to MAC 222. MAC 222 may multiplex many RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, MAC subheaders may be distributed throughout the MAC PDU, as shown in FIG. Figure 4A In LTE, the MAC subheader can be located entirely at the beginning of the MAC PDU. The NR MAC PDU structure can reduce processing time and associated latency because the MAC PDU subheader can be calculated before assembling the complete MAC PDU.

[0073] Figure 4B An example format of a MAC subheader in a MAC PDU is shown. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originates to assist in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0074] Figure 4B Further shown is a MAC control element (CE) inserted into the MAC PDU by a MAC (such as MAC 223 or MAC 222). For example, Figure 4B Two MAC CEs are shown inserted into the MAC PDU. Figure 4B) and inserting a MAC CE at the end of a MAC PDU for uplink transmission. MAC CE may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reporting and power headroom reporting; activation / deactivation MAC CEs, such as those used for PDCP duplicate detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and activation / deactivation of previously configured components; discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC subheader having a format similar to that described for a MAC SDU may be present before the MAC CE, and the MAC CE may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0075] Before describing the NR control plane protocol stack, the mapping between logical channels, transport channels, and physical channels and channel types is first described. One or more of these channels can be used to perform functions associated with the NR control plane protocol stack described later below.

[0076] Figure 5A and Figure 5B The mapping between logical channels, transport channels and physical channels is shown for downlink and uplink respectively. Information is passed through channels between RLC, MAC and PHY of the NR protocol stack. Logical channels can be used between RLC and MAC and can be classified as control channels that carry control and configuration information in the NR control plane, or as traffic channels that carry data in the NR user plane. Logical channels can be classified as dedicated logical channels dedicated to a specific UE, or as common logical channels that can be used by more than one UE. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example:

[0077] - Paging Control Channel (PCCH), which is used to carry paging messages used to page UEs whose location is unknown to the network at cell level;

[0078] - Broadcast Control Channel (BCCH), which is used to carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which can be used by UEs to obtain information about how a cell is configured and how it operates within the cell;

[0079] - Common Control Channel (CCCH), which is used to carry control messages and random access;

[0080] - a dedicated control channel (DCCH) used to carry control messages to / from a specific UE to configure the UE; and

[0081] - Dedicated Traffic Channel (DTCH), which is used to carry user data to / from a specific UE.

[0082] Transport channels are used between the MAC layer and the PHY layer and can be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0083] - Paging Channel (PCH), which is used to carry paging messages originating from PCCH;

[0084] - Broadcast Channel (BCH), which is used to carry the MIB from the BCCH;

[0085] - Downlink Shared Channel (DL-SCH), which is used to carry downlink data and signaling messages, including SIBs from BCCH;

[0086] - Uplink Shared Channel (UL-SCH), which is used to carry uplink data and signaling messages; and

[0087] - Random Access Channel (RACH), which is used to allow a UE to contact the network without any previous scheduling.

[0088] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have a set of associated time-frequency resources for carrying information of one or more transport channels. The PHY may generate control information to support low-level operation of the PHY and provide control information to lower levels of the PHY via physical control channels (referred to as L1 / L2 control channels). The set of physical channels and physical control channels defined by NR includes, for example:

[0089] - Physical Broadcast Channel (PBCH), which is used to carry the MIB from the BCH;

[0090] - Physical Downlink Shared Channel (PDSCH), which is used to carry downlink data and signaling messages from DL-SCH and paging messages from PCH;

[0091] - Physical Downlink Control Channel (PDCCH), which is used to carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0092] - Physical Uplink Shared Channel (PUSCH), which is used to carry uplink data and signaling messages from the UL-SCH, and in some cases uplink control information (UCI) as described below;

[0093] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI) and scheduling request (SR); and

[0094] - Physical Random Access Channel (PRACH), which is used for random access.

[0095] Similar to the physical control channel, the physical layer generates physical signals to support the lower-level operations of the physical layer. Figure 5A and Figure 5B As shown in , the physical layer signals defined by NR include: primary synchronization signal (PSS), secondary synchronization signal (SSS), channel state information reference signal (CSI-RS), demodulation reference signal (DMRS), sounding reference signal (SRS) and phase tracking reference signal (PT-RS). These physical layer signals will be described in more detail below.

[0096] Figure 2B An example NR control plane protocol stack is shown. Figure 2B As shown in , the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane protocol stack instead has radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0097] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A) or more generally between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which NAS messages may be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0098] The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 or more generally between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functions between the UE 210 and the gNB 220 via signaling messages referred to as RRC messages. The RRC messages may be transported between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control plane and user plane data into the same transport block (TB). The RRC 216 and 226 may provide control plane functions such as: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance and release of RRC connection between UE 210 and RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; UE measurement reporting and control of the reporting; detection of radio link failure (RLF) and recovery from radio link failure; and / or NAS message delivery. As part of establishing an RRC connection, RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between UE 210 and RAN.

[0099] Figure 6 is an example diagram showing the RRC state transition of the UE. The UE can Figure 1A The wireless device 106 depicted in Figure 2A and Figure 2B The UE 210 depicted in FIG. 1 and any other wireless device described in the present disclosure may be the same or similar. Figure 6 As shown in , the UE may be in at least one of three RRC states: RRC connected 602 (eg, RRC_CONNECTED), RRC idle 604 (eg, RRC_IDLE), and RRC inactive 606 (eg, RRC_INACTIVE).

[0100] In RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the following: Figure 1A The one or more base stations included in the RAN 104 depicted in FIG. Figure 1B One of the gNB 160 or ng-eNB 162 depicted in FIG. Figure 2A and Figure 2B; or any other base station described in the present disclosure. A base station connected to a UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may contain parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., involving data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. When in RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from a serving cell and neighboring cells, and report these measurements to the base station currently serving the UE. The UE's serving base station may request handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 via a connection release procedure 608 , or to RRC inactive 606 via a connection deactivation procedure 610 .

[0101] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with a base station. When in RRC idle 604, the UE may be in a sleep state for most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once in each discontinuous reception cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0102] In RRC Inactive 606, the previously established RRC context is maintained in the UE and the base station. This allows a quick transition to RRC Connected 602 with reduced signaling overhead compared to the transition from RRC Idle 604 to RRC Connected 602. While in RRC Inactive 606, the UE may be in a sleep state, and the mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 through a Connection Resumption Procedure 614, or to RRC Idle 604 through a Connection Release Procedure 616, which may be the same or similar to the Connection Release Procedure 608.

[0103] The RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to notify the UE of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE at a cell group level, so that the paging message may be broadcast over a cell in the cell group in which the UE currently resides instead of over the entire mobile communication network. The mobility management mechanism used for RRC idle 604 and RRC inactive 606 tracks the UE at a cell group level. These mobility management mechanisms may do so using groups of different granularities. For example, there may be three levels of cell grouping granularity: a single cell; a cell within a RAN area identified by a RAN area identifier (RAI); and a cell within a group of RAN areas referred to as tracking areas and identified by a tracking area identifier (TAI).

[0104] Tracking areas may be used to track UEs at the CN level. A CN (e.g., CN 102 or 5G-CN 152) may provide a list of TAIs associated with UE registration areas to a UE. If a UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with a UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0105] The RAN area may be used to track the UE at the RAN level. For a UE in the RRC inactive 606 state, a RAN notification area may be assigned to the UE. The RAN notification area may contain one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves to a cell not included in the RAN notification area assigned to the UE through cell reselection, the UE may perform a notification area update on the RAN to update the RAN notification area of ​​the UE.

[0106] The base station storing the RRC context for the UE or the last serving base station of the UE may be referred to as the anchor base station. The anchor base station may maintain the RRC context for the UE at least during the period of time that the UE remains in the RAN notification area of ​​the anchor base station and / or during the period of time that the UE remains in RRC inactivity 606.

[0107] gNB, such as Figure 1BThe gNB 160 in the example can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using the F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0108] In NR, physical signals and physical channels (about Figure 5A and Figure 5B Discussed) can be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal subcarriers (or tones). Before transmission, the data can be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols) and divided into F parallel symbol streams. The F parallel symbol streams can be treated as if they are in the frequency domain and used as input to the inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can take F source symbols at a time (one source symbol from each of the F parallel symbol streams), and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples can form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, the OFDM symbols provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be mixed using the FFT block before being processed by the IFFT block. The operation produces a discrete Fourier transform (DFT) precoded OFDM symbol and can be used by the UE in the uplink to reduce the peak to average power ratio (PAPR). The FFT block can be used to perform inverse processing on the OFDM symbol at the receiver to restore the data mapped to the source symbol.

[0109] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown. An NR frame may be identified by a system frame number (SFN). The SFN may repeat in a period of 1024 frames. As shown, a NR frame may have a duration of 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

[0110] The duration of a time slot may depend on the parameter set of the OFDM symbol used for the time slot. In NR, flexible parameter sets are supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz, up to cells with carrier frequencies in the mm-wave range). Parameter sets may be defined in terms of subcarrier spacing and cyclic prefix duration. For parameter sets in NR, the subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; and 240 kHz / 0.29 μs.

[0111] A slot may have a fixed number of OFDM symbols (eg, 14 OFDM symbols). Parameter sets with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 The transmission structure of the time slot duration and each subframe time slot associated with the parameter set is shown (for ease of explanation, Figure 7 Parameter sets with subcarrier spacing of 240kHz are not shown in Figure 1). Subframes in NR can be used as a time reference independent of the parameter set, while slots can be used as the unit for scheduling uplink and downlink transmissions. To support low latency, scheduling in NR can be decoupled from the slot duration and start at any OFDM symbol and continue to transmit as many symbols as needed. These partial slot transmissions can be called mini-slots or sub-slot transmissions.

[0112] Figure 8 An example configuration of time slots in the time and frequency domains of an NR carrier is shown. The time slots include resource elements (REs) and resource blocks (RBs). REs are the smallest physical resources in NR. REs span one OFDM symbol in the time domain through one subcarrier in the frequency domain, such as Figure 8 As shown in Figure 1. RB spans twelve consecutive REs in the frequency domain, as Figure 8 As shown. The NR carrier can be limited to a width of 275 RBs or 275×12=3300 subcarriers. If this restriction is used, the NR carrier can be limited to 50MHz, 100MHz, 200MHz and 400MHz for subcarrier spacings of 15kHz, 30kHz, 60kHz and 120kHz, respectively, where the 400MHz bandwidth can be set based on the 400MHz bandwidth limit per carrier.

[0113] Figure 8A single parameter set is shown used across the entire bandwidth of the NR carrier. In other example configurations, multiple parameter sets may be supported on the same carrier.

[0114] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Moreover, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, the UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0115] NR defines bandwidth parts (BWPs) to support UEs that cannot receive the full carrier bandwidth and supports bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. The UE may be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. The one or more BWPs may be referred to as active BWPs of a serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in an uplink carrier and one or more second active BWPs in a secondary uplink carrier.

[0116] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0117] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), the base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domain where a UE can look for control information. A search space may be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, a base station may configure a common search space for a UE on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

[0118] For an uplink BWP in the set of configured uplink BWPs, the BS may configure one or more resource sets for one or more PUCCH transmissions for the UE. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWP according to the configured parameter set (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP according to the configured parameter set (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0119] One or more BWP indicator fields may be provided in downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in a set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0120] The base station may semi-statically configure a default downlink BWP for the UE within the set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP to the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0121] The base station may configure the BWP inactivity timer value for the PCell for the UE. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer in the following circumstances: (a) when the UE detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) when the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or uplink BWP for unpaired spectrum operation. If the UE does not detect the DCI within a time interval (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., an increment from zero to the BWP inactivity timer value, or a decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0122] In an example, the base station may semi-statically configure the UE with one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., when the second BWP is the default BWP).

[0123] Downlink and uplink BWP switching can be performed independently in paired spectrum (where BWP switching refers to switching from a currently active BWP to a non-currently active BWP). In unpaired spectrum, downlink and uplink BWP switching can be performed simultaneously. Switching between configured BWPs can occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0124] Fig. 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. A UE configured with the three BWPs may switch from one BWP to another at a switching point. Fig. 9 In the example shown, the BWPs include: BWP 902, which has a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904, which has a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906, which has a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between BWPs at a switching point. Fig. 9 904. In the example of , the UE may switch from BWP 902 to BWP 904 at switch point 908. The switch at switch point 908 may occur for any suitable reason, such as in response to expiration of a BWP inactivity timer (indicating a switch to a default BWP) and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 906 at switch point 910 in response to receiving a DCI indicating that BWP 906 is an active BWP. The UE may switch from active BWP 906 to BWP 904 at switch point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating that BWP 904 is an active BWP. The UE may switch from active BWP 904 to BWP 902 at switch point 914 in response to receiving a DCI indicating that BWP 902 is an active BWP.

[0125] If the UE is configured for a secondary cell with a default downlink BWP and timer values ​​from the set of configured downlink BWPs, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell. For example, the UE may use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values ​​for the primary cell.

[0126] To provide higher data rates, two or more carriers may be aggregated and transmitted to / from the same UE simultaneously using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CC). When CA is used, there are many serving cells for the UE, one serving cell per CC. CCs may have three configurations in the frequency domain.

[0127] Fig. 10A Three CA configurations with two CCs are shown. In the intra-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (Band A) and are located directly adjacent to each other in the frequency band. In the intra-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (Band A) and are separated by a gap in the frequency band. In the inter-band configuration 1006, the two CCs are located in the frequency bands (Band A and Band B).

[0128] In an example, up to 32 CCs may be aggregated. Aggregated CCs may have the same or different bandwidths, subcarrier spacings, and / or duplex schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. For example, the ability to aggregate more downlink carriers than uplink carriers may be useful when the UE has more data traffic in the downlink than in the uplink.

[0129] When CA is used, one of the aggregated cells for the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects at RRC connection establishment, reestablishment and / or handover. The PCell may provide NAS mobility information and security input to the UE. The UE may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0130] The configured SCell for a UE can be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell can mean stopping PDCCH and PDSCH reception on the SCell, and stopping PUSCH, SRS, and CQI transmission on the SCell. Figure 4B The MAC CE may be used to activate and deactivate the configured SCells. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the UE. The configured SCells may be deactivated in response to the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0131] The downlink control information of a cell (such as scheduling assignments and scheduling grants) can be transmitted on the cell corresponding to the assignment and grant, which is called self-scheduling. The DCI of a cell can be transmitted on another cell, which is called cross-carrier scheduling. Uplink control information for aggregated cells (e.g., HARQ confirmation and channel state feedback, such as CQI, PMI and / or RI) can be transmitted on the PUCCH of the PCell. For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. The cell can be divided into multiple PUCCH groups.

[0132] Fig. 10B An example of how aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 may include one or more downlink CCs, respectively. Fig. 10B, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as primary Scell ​​(PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1010 (shown as UCI 1031, UCI 1032, and UCI 1033) may be transmitted in the uplink of PCell 1021. Uplink control information (UCI) related to the downlink CCs of PUCCH group 1050 (shown as UCI 1071, UCI 1072, and UCI 1073) may be transmitted in the uplink of PSCell 1061. In the example, if Fig. 10B If the aggregated cell depicted in FIG. 1 is not divided into PUCCH group 1010 and PUCCH group 1050 , a single uplink PCell transmits UCI associated with a downlink CC, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061 , overload can be prevented.

[0133] A physical cell ID and a cell index may be assigned to a cell comprising a downlink carrier and an optional uplink carrier. The physical cell ID or cell index may identify a downlink carrier and / or an uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In the present disclosure, the physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. For example, when the present disclosure relates to a first physical cell ID of a first downlink carrier, the present disclosure may mean that the first physical cell ID is used for a cell comprising the first downlink carrier. The same / similar concepts may apply, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the present specification may mean that a cell comprising the first carrier is activated.

[0134] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In an example, the HARQ entity can operate on the serving cell. A transport block can be generated based on the assignment / grant of each serving cell. A transport block and potential HARQ retransmissions of the transport block can be mapped to a serving cell.

[0135] In the downlink, the base station may transmit (e.g., unicast, multicast and / or broadcast) one or more reference signals (RS) to the UE (e.g., PSS, SSS, CSI-RS, DMRS and / or PT-RS, such as Figure 5A In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. Figure 5B ). The PSS and SSS may be transmitted by a base station and used by a UE to synchronize the UE with the base station. The PSS and SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station may periodically transmit bursts of SS / PBCH blocks.

[0136] Fig.11A An example of the structure and location of SS / PBCH blocks is shown. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, such as Fig.11A As shown). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). Bursts may be limited to half a frame (e.g., the first half frame with a duration of 5 ms). It should be understood that Fig.11A are examples, and these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, burst positioning within a frame) may be configured based on, for example: the carrier frequency of the cell in which the SS / PBCH blocks are transmitted; a parameter set or subcarrier spacing for the cell; configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume the subcarrier spacing of the SS / PBCH blocks based on the carrier frequency being monitored unless the radio network configures the UE to assume a different subcarrier spacing.

[0137] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Fig.11A ) and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., spanning the next 3 OFDM symbols) and may span 240 subcarriers.

[0138] The UE may not know the location of the SS / PBCH blocks in the time and frequency domains (for example, when the UE is searching for cells). In order to find and select a cell, the UE may monitor the carrier of the PSS. For example, the UE may monitor the frequency position within the carrier. If the PSS is not found after a certain duration (for example, 20ms), the UE may search for the PSS at different frequency positions within the carrier, as indicated by the synchronization raster. If the PSS is found at a certain position in the time and frequency domains, the UE may determine the location of the SSS and PBCH based on the known structure of the SS / PBCH block, respectively. The SS / PBCH block may be a cell definition SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, cell selection / search and / or reselection may be based on the CD-SSB.

[0139] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine the physical cell identifier (PCI) of the cell based on the sequence of the PSS and SSS, respectively. The UE may determine the location of the frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted according to a transmission pattern, wherein the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0140] The PBCH may use QPSK modulation and may use forward error correction (FEC). FEC may use polarity coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may contribute to the time synchronization of the UE with the base station. The PBCH may include a master information block (MIB) for providing one or more parameters to the UE. The MIB may be used by the UE to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may contain information required for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH that may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate that SIB1 does not exist. Based on the PBCH indicating that SIB1 does not exist, the UE may point to a frequency. The UE may search for SS / PBCH blocks at the frequency to which the UE is pointing.

[0141] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices.

[0142] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0143] In an example, within a frequency range of a carrier, a base station may transmit multiple SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block in the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block in the multiple SS / PBCH blocks. PCIs of SS / PBCH blocks transmitted in different frequency positions may be different or the same.

[0144] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more CSI-RSs of the same / similar CSI-RS. The UE may measure the one or more CSI-RSs. The UE may estimate the downlink channel state and / or generate a CSI report based on the measurement of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use the feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0145] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with positions and periodicity in the time and frequency domains. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that the CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

[0146] The base station can configure the UE to report CSI measurement values. The base station can configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE can be configured with the timing and / or period of multiple CSI reports. For aperiodic CSI reporting, the base station can request a CSI report. For example, the base station can command the UE to measure the configured CSI-RS resources and provide a CSI report related to the measurement value. For semi-persistent CSI reporting, the base station can configure the UE to transmit periodically and selectively activate or deactivate periodic reporting. The base station can configure the UE with a CSI-RS resource set and CSI reporting using RRC signaling.

[0147] The CSI-RS configuration may contain one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbol for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH blocks.

[0148] The downlink DMRS may be transmitted by the base station and used by the UE for channel estimation. For example, the downlink DMRS may be used for consistent demodulation of one or more downlink physical channels (e.g., PDSCH). The NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a frontload DMRS pattern. The frontload DMRS may be mapped on the one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontload DMRS symbols for PDSCH. The DMRS configuration may support one or more DMRS ports. For example, for single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multi-user MIMO, the DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. The radio network may (e.g., at least for CP-OFDM) support a common DMRS structure for downlink and uplink, in which the DMRS position, DMRS pattern, and / or scrambling sequence may be the same or different. The base station may use the same precoding matrix to transmit the downlink DMRS and the corresponding PDSCH. The UE may use the one or more downlink DMRS to perform consistent demodulation / channel estimation on the PDSCH.

[0149] In an example, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a transmission bandwidth. For example, a transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used throughout a set of PRBs. The set of PRBs may be represented as a precoding resource block group (PRG).

[0150] The PDSCH may contain one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer in the one or more layers of the PDSCH. Higher layers may configure up to 3 DMRS for the PDSCH.

[0151] The downlink PT-RS may be transmitted by a base station and used by a UE for phase noise compensation. Whether a downlink PT-RS exists may depend on an RRC configuration. The presence and / or type of a downlink PT-RS may be configured based on a UE-specific configuration using a combination of RRC signaling and / or an association with one or more parameters for other purposes (e.g., a modulation and coding scheme (MCS)) that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters containing at least an MCS. The NR network may support multiple PT-RS densities defined in time and / or frequency domains. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be limited to the scheduled time / frequency duration of the UE. The downlink PT-RS may be transmitted on a symbol to facilitate phase tracking at the receiver.

[0152] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS to consistently demodulate one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS mode. The front-loaded DMRS may be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the UE with the number (e.g., maximum number) of front-loaded DMRS symbols of the PUSCH and / or PUCCH, and the UE may use the front-loaded DMRS symbols to schedule single-symbol DMRS and / or dual-symbol DMRS. NR networks may support a common DMRS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS positions, DMRS patterns, and / or scrambling sequences of the DMRS may be the same or different.

[0153] The PUSCH may contain one or more layers, and the UE may transmit at least one symbol having a DMRS present on a layer in the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0154] Depending on the RRC configuration of the UE, an uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or type of the uplink PT-RS can be configured based on UE-specific configuration through a combination of RRC signaling and / or one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)) indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters containing at least the MCS. The radio network can support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can use the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS can be limited to the scheduled time / frequency duration of the UE.

[0155] The UE may transmit an SRS to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted by the UE may allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The applicability of the SRS resource set may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, the SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, being periodic, being non-periodic, etc.) may be transmitted at a certain time (e.g., at the same time). The UE may transmit one or more SRS resources in the SRS resource set. The NR network may support non-periodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be used for the UE to select at least one configured SRS resource set from one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after transmission of PUSCH and corresponding uplink DMRS.

[0156] The base station can semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or non-periodic SRS); time slot, mini-slot, and / or subframe level periodicity; time slots of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resources; the start OFDM symbol of the SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0157] The antenna ports are defined so that the channel through which one symbol on the antenna port is communicated can be inferred from the channel through which another symbol on the same antenna port is communicated. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver can infer the channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. If one or more large-scale properties of the channel through which the first symbol on the first antenna port is communicated can be inferred from the channel through which the second symbol on the second antenna port is communicated, the first antenna port and the second antenna port can be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial reception (Rx) parameters.

[0158] Channels using beamforming require beam management. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurements and generate beam measurement reports based on downlink reference signals (e.g., channel state information reference signals (CSI-RS)). After setting up an RRC connection with a base station, the UE may perform a downlink beam measurement procedure.

[0159] Fig. 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domain is shown. Fig. 11BThe squares shown in the figure may represent resource blocks (RBs) within the bandwidth of the cell. The base station may transmit one or more RRC messages containing CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more of the following parameters may be configured for the CSI-RS resource configuration through higher layer signaling (e.g., RRC and / or MAC signaling): CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions in a subframe), CSI-RS subframe configuration (e.g., subframe position, offset and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid) and / or other radio resource parameters.

[0160] Fig. 11B The three beams shown may be configured for a UE in a UE-specific configuration. Fig. 11B Three beams (beam #1, beam #2, and beam #3) are shown in the figure, and more or fewer beams can be configured. CSI-RS1101 can be allocated to beam #1, which can be transmitted in one or more subcarriers in the RB of the first symbol. CSI-RS1102 can be allocated to beam #2, which can be transmitted in one or more subcarriers in the RB of the second symbol. CSI-RS1103 can be allocated to beam #3, which can be transmitted in one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station can use other subcarriers in the same RB (for example, those subcarriers not used to transmit CSI-RS1101) to transmit another CSI-RS associated with the beam of another UE. By using time domain multiplexing (TDM), the beam for the UE can be configured so that the beam for the UE uses symbols from the beams of other UEs.

[0161] CSI-RS, such as Fig. 11BThose shown in (e.g., CSI-RS1101, 1102, 1103) can be transmitted by a base station and used by a UE for one or more measurements. For example, the UE can measure the reference signal received power (RSRP) of the configured CSI-RS resource. The base station can configure the UE with a reporting configuration, and the UE can report the RSRP measurement value to the network (e.g., via one or more base stations) based on the reporting configuration. In the example, the base station can determine one or more transmission configuration indication (TCI) states containing multiple reference signals based on the reported measurement results. In the example, the base station can indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE and / or DCI). The UE can receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In the example, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE can determine the spatial domain filter of the transmission (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam-corresponding capability, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate the uplink beam of the UE based on measurements of one or more SRS resources transmitted by the UE.

[0162] In the beam management procedure, the UE may assess (e.g., measure) the channel quality of one or more beam pair links, beam pair links comprising a transmission beam transmitted by a base station, and a reception beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, wherein the one or more beam pair quality parameters include, for example, one or more beam identifiers (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI) and / or rank indicator (RI).

[0163] Fig. 12AExamples of three downlink beam management procedures are shown: P1, P2, and P3. Procedure P1 can enable UE measurements of transmit (Tx) beams of a transmit reception point (TRP) (or multiple TRPs), for example to support selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top and bottom rows of P1, respectively). Beamforming at the TRP can include Tx beam sweeping for a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of Tx beams of TRPs (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller beam set than the beam set used in procedure P1, or using a narrower beam than the beam used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beam at the UE.

[0164] Fig. 12B Examples of three uplink beam management procedures are shown: U1, U2, and U3. Procedure U1 can be used to enable a base station to perform measurements on a UE's Tx beams, for example, to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top and bottom rows of U1, respectively). Beamforming at the UE can include, for example, Tx beam sweeping from a set of beams (shown as ovals rotating in a clockwise direction indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station can include, for example, Rx beam sweeping from a set of beams (shown as ovals rotating in a counterclockwise direction indicated by dashed arrows in the top rows of U1 and U2). Procedure U2 can be used to enable a base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station can perform procedure U2 using a smaller set of beams than the one used in procedure P1, or using a narrower beam than the one used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0165] The UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., preamble, UCI, SR, MAC CE, etc.) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having an error rate above an error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0166] The UE may measure the quality of a beam pair link using one or more reference signals (RS), the one or more reference signals comprising one or more SS / PBCH blocks, one or more CSI-RS resources and / or one or more demodulation reference signals (DMRS). The quality of a beam pair link may be based on one or more of the following: a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value and / or a CSI value measured on an RS resource. The base station may indicate that the RS resource is quasi-co-located (QCLed) with one or more DM-RS of a channel (e.g., a control channel, a shared data channel, etc.). When the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the UE via the RS resource are similar or identical to the channel characteristics from the transmission to the UE via the channel, the RS resource and the one or more DMRS of the channel may be QCLed.

[0167] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in RRC_IDLE state and / or RRC_INACTIVE state may initiate a random access procedure to request a connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or to obtain uplink timing (e.g., when the uplink synchronization state is not synchronized). The UE may initiate a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, etc.). The UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure for handover and / or for establishing time alignment for SCell addition.

[0168] Fig.13A A four-step contention-based random access procedure is shown.Before initiating the procedure, the base station may transmit a configuration message 1310 to the UE. Fig.13AThe procedure shown involves the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg 3 1313, and Msg 4 1314. Msg 1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0169] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in the RRC_CONNECTED state and / or the RRC_INACTIVE state). The UE may determine the time-frequency resources and / or uplink transmission power for transmitting Msg 1 1311 and / or Msg 3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the reception timing and downlink channel for receiving Msg 2 1312 and Msg 4 1314.

[0170] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that can be used to transmit Msg 11311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between: (a) one or more PRACH opportunities, and (b) one or more reference signals. The one or more RACH parameters may indicate an association between: (a) one or more preambles, and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunity and / or the number of preambles mapped to the SS / PBCH block.

[0171] The one or more RACH parameters provided in the configuration message 1310 can be used to determine the uplink transmission power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters can indicate a reference power for preamble transmission (e.g., the received target power and / or the initial power of preamble transmission). There can be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters can indicate: a power ramp step; a power offset between SSB and CSI-RS; a power offset between the transmissions of Msg 1 1311 and Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters can indicate one or more thresholds based on which the UE can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplementary uplink (SUL) carrier).

[0172] Msg 1 1311 can include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group can contain one or more preambles. The UE can determine the preamble group based on the path loss measurement value and / or the size of Msg 3 1313. The UE can measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP higher than the RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the UE can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0173] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station may use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the UE. If the association is configured, the UE may determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for selecting a preamble and for determining a PRACH opportunity. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

[0174] If no response is received after the preamble transmission, the UE may perform a preamble retransmission. The UE may increase the uplink transmission power for the preamble retransmission. The UE may select the initial preamble transmission power based on the path loss measurement and / or the target received preamble power configured by the network. The UE may determine to retransmit the preamble and may ramp up the uplink transmission power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp-up step size for the preamble retransmission. The ramp-up step size may be the amount of incremental increase in the uplink transmission power for retransmission. If the UE determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission, the UE may ramp up the uplink transmission power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds a threshold (eg, preambleTransMax) configured by the one or more RACH parameters, the UE may determine that the random access procedure is not successfully completed.

[0175] Msg 2 1312 received by the UE may include a RAR. In some scenarios, Msg 2 1312 may include multiple RARs corresponding to multiple UEs. Msg 2 1312 may be received after or in response to the transmission of Msg 1 1311. Msg 2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a random access RNTI (RA-RNTI). Msg 2 1312 may indicate that Msg 1 1311 is received by the base station. Msg 2 1312 may include a time alignment command that may be used by the UE to adjust the transmission timing of the UE, a scheduling grant for transmitting Msg 3 1313, and / or a temporary cell RNTI (TC-RNTI). After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of Msg 2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, the UE may start a time window of one or more symbols after the last symbol of the preamble (e.g., at the first PDCCH opportunity starting from the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a radio network temporary identifier (RNTI). The RNTI may be used depending on one or more events that initiate a random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. Examples of RA-RNTI may be as follows:

[0176] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0177] Wherein s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time slot of the PRACH opportunity in the system frame (e.g., 0≤t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≤f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for the NUL carrier and 1 for the SUL carrier).

[0178] The UE may transmit Msg 3 1313 in response to successfully receiving Msg 2 1312 (e.g., using the resources identified in Msg 2 1312). Msg 3 1313 may be used, for example, Fig.13A Contention resolution in a contention-based random access procedure as shown in . In some scenarios, multiple UEs may transmit the same preamble to a base station, and the base station may provide a RAR corresponding to the UE. If the multiple UEs interpret the RAR as corresponding to themselves, a conflict may occur. Contention resolution (e.g., using Msg 3 1313 and Msg 4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., if a C-RNTI is assigned, the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier).

[0179] Msg 4 1314 may be received after or in response to the transmission of Msg 3 1313. If a C-RNTI is included in Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If a unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure is successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in an RRC_IDLE state or is not otherwise connected to the base station), Msg 4 1314 will be received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU contains a UE contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0180] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., a random access procedure) may be supported in an uplink carrier. For example, a base station may configure two separate RACH configurations for a UE: one for a SUL carrier and the other for a NUL carrier. For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. For example, if the measured quality of one or more reference signals is below a broadcast threshold, the UE may determine the SUL carrier. The uplink transmission (e.g., Msg 1 1311 and / or Msg 3 1313) of the random access procedure may remain on the selected carrier. In one or more cases, the UE may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE may determine and / or switch an uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on channel clarity assessment (eg, listen before talk).

[0181] Fig. 13B The two-step contention-free random access procedure is shown. Fig.13A Similar to the four-step contention-based random access procedure shown, the base station may transmit a configuration message 1320 to the UE before the procedure is initiated. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. Fig. 13B The procedure shown involves the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar in some respects to Fig.13A As shown in Msg 1 1311 and Msg 2 1312. Fig.13A and Fig. 13B It will be appreciated that the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314.

[0182] Can be initiated for beam failure recovery, other SI requests, SCell addition and / or handover Fig. 13B For example, the base station may indicate or assign a preamble to be used for Msg 1 1321 to the UE. The UE may receive an indication of the preamble (eg, ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0183] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. Fig. 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after or in response to the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322. For example, if the PDCCH transmission is addressed to the C-RNTI, the UE may determine that the random access procedure is successfully completed. For example, if the UE receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR contains a MAC sub-PDU with the preamble identifier, the UE may determine that the random access procedure is successfully completed. The UE may determine that the response is an indication of a confirmation of the SI request.

[0184] Fig. 13C Another two-step random access procedure is shown. Fig.13A and Fig. 13B Similar to the random access procedure shown, the base station may transmit a configuration message 1330 to the UE before the procedure is initiated. Configuration message 1330 may be similar to configuration message 1310 and / or configuration message 1320 in some aspects. Fig. 13C The procedure shown involves the transmission of two messages: Msg A 1331 and Msg B 1332.

[0185] Msg A 1331 may be transmitted by the UE in an uplink transmission. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. Transport block 1342 may include Fig.13A The transmission block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include the same content as the content of Msg 3 1313 shown in FIG. Fig.13A and Fig. 13B Msg 2 1312 (eg, RAR) and / or Fig.13A The content of Msg4 1314 shown is similar and / or identical.

[0186] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Fig. 13C The UE may determine whether to initiate a two-step random access procedure based on one or more factors. The one or more factors may be: the radio access technology being used (e.g., LTE, NR, etc.); whether the UE has a valid TA; the cell size; the RRC state of the UE; the type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0187] The UE may determine the radio resources and / or uplink transmission power of the preamble 1341 and / or the transport block 1342 included in the Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the modulation and coding scheme (MCS), time-frequency resources, and / or power control of the preamble 1341 and / or the transport block 1342. The time-frequency resources (e.g., PRACH) used for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) used for transmission of the transport block 1342 may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the reception timing and downlink channel for monitoring and / or receiving the Msg B 1332.

[0188] Transport block 1342 may include data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit Msg B 1332 as a response to Msg A 1331. Msg B 1332 may include at least one of the following: a preamble identifier; a timing high-level command; a power control command; an uplink grant (e.g., a radio resource assignment and / or MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the following conditions exist: the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 matches the identifier of the UE in Msg A 1331 (e.g., transport block 1342).

[0189] The UE and the base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0190] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transport format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) common to a group of UEs.

[0191] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include a Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of a radio network temporary identifier (RNTI).

[0192] DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a dynamically scheduled unicast transmission and / or the triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to Fig.13AThe other RNTIs configured by the base station to the UE may include: a configured scheduling RNTI (CS-RNTI), a transmission power control PUCCH RNTI (TPC-PUCCH-RNTI), a transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmission power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C-RNTI), etc.

[0193] Depending on the purpose and / or content of the DCI, the base station may transmit DCI with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling of PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a UE group. DCI format 2_1 may be used to notify a UE group of physical resource blocks and / or OFDM symbols, where the UE may assume that there is no transmission for the UE. DCI format 2_2 may be used to transmit a transmission power control (TPC) command for PUCCH or PUSCH. DCI formats 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0194] After scrambling the DCI with the RNTI, the base station may process the DCI with channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI on resource elements used for and / or configured for PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, the base station may transmit the DCI via a PDCCH occupying multiple consecutive control channel elements (CCEs). The number of consecutive CCEs (referred to as the aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. CCE may include the number of resource element groups (REGs) (e.g., 6). REG may include resource blocks in an OFDM symbol. The mapping of coded and modulated DCI on resource elements may be based on the mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0195] Fig.14A An example of a CORESET configuration for a bandwidth portion is shown. A base station may transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources in which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. Fig.14A In the example of FIG. 1401 , the first CORESET 1401 and the second CORESET 1402 appear at the first symbol in the time slot. The first CORESET 1401 overlaps the second CORESET 1402 in the frequency domain. The third CORESET 1403 appears at the third symbol in the time slot. The fourth CORESET 1404 appears at the seventh symbol in the time slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0196] Fig. 14B An example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing is shown. The CCE to REG mapping can be an interlaced mapping (e.g., for the purpose of providing frequency diversity) or a non-interlaced mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). The base station can perform different or the same CCE to REG mapping for different CORESETs. A CORESET can be associated with the CCE to REG mapping through RRC configuration. A CORESET can be configured with antenna port quasi-co-location (QCL) parameters. The antenna port QCL parameters can indicate the QCL information of the demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0197] The base station may transmit an RRC message containing configuration parameters of one or more CORESETs and one or more search space sets to the UE. The configuration parameters may indicate an association between a search space set and a CORESET. The search space set may contain a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: the number of PDCCH candidates to be monitored for each aggregation level; the PDCCH monitoring period and the PDCCH monitoring type; one or more DCI formats to be monitored by the UE; and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the identity of the UE (e.g., C-RNTI).

[0198] like Fig. 14B As shown, the UE may determine the time-frequency resources of the CORESET based on the RRC message. The UE may determine the CCE to REG mapping of the CORESET based on the configuration parameters of the CORESET (e.g., interlaced or non-interlaced and / or mapping parameters). The UE may determine the number of search space sets configured on the CORESET based on the RRC message (e.g., up to 10). The UE may monitor a set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates, which have possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the UE-specific search space) and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The UE may determine that the DCI is valid for the UE in response to a CRC check (e.g., scrambled bits of the CRC parity bits of the DCI matching the RNTI value). The UE may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, etc.).

[0199] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling transmission may include a hybrid automatic repeat request (HARQ) confirmation for the received DL-SCH transport block. The UE may transmit the HARQ confirmation after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating the channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. Based on the received CSI, the base station may determine the transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit UCI (e.g., HARQ confirmation (HARQ-ACK), CSI report, SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0200] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. If the transmission exceeds one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two, the UE may use PUCCH format 0 to transmit the UCI in the PUCCH resource. PUCCH format 1 may occupy between four and fourteen OFDM symbols and may include two or fewer bits. If four or more symbols are transmitted and the number of HARQ-ACK / SR bits is one or two, the UE may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. If the transmission exceeds one or two symbols and the number of UCI bits is two or more, the UE may use PUCCH format 2. PUCCH format 3 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources do not include orthogonal cover codes, the UE may use PUCCH format 3. PUCCH format 4 may occupy between four and fourteen OFDM symbols and may include more than two bits. If four or more symbols are transmitted, the number of UCI bits is two or more, and the PUCCH resources include orthogonal cover codes, the UE may use PUCCH format 4.

[0201] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE using, for example, an RRC message. The multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. The PUCCH resource set may be configured with: a PUCCH resource set index; multiple PUCCH resources having PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid); and / or multiple (e.g., maximum number) UCI ​​information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE may select one of the multiple PUCCH resource sets (e.g., HARQ-ACK, SR, and / or CSI) based on the total bit length of the UCI information bits. If the total bit length of the UCI information bits is two or less, the UE may select the first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than two and less than or equal to the first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0202] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine PUCCH resources for UCI (HARQ-ACK, CSI, and / or SR) transmission from the PUCCH resource set. The UE may determine the PUCCH resources based on a PUCCH resource indicator in a DCI (e.g., a DCI format 1_0 or a DCI for 1_1) received on the PDCCH. The three-bit PUCCH resource indicator in the DCI may indicate one PUCCH resource in eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may use the PUCCH resources indicated by the PUCCH resource indicator in the DCI to transmit UCI (HARQ-ACK, CSI, and / or SR).

[0203] Fig.15 An example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the present disclosure is shown. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as Figure 1A The mobile communication network 100 shown, Figure 1B The mobile communication network 150 shown or any other communication network. Fig.15 Only one wireless device 1502 and one base station 1504 are shown in FIG. 1 , but it should be understood that the mobile communication network may include more than one UE and / or more than one base station, which have the same Fig.15 Configurations the same or similar to those shown.

[0204] The base station 1504 may connect the wireless device 1502 to a core network (not shown) by radio communication via an air interface (or radio interface) 1506. The direction of communication from the base station 1504 to the wireless device 1502 over the air interface 1506 is referred to as downlink, while the direction of communication from the wireless device 1502 to the base station 1504 over the air interface is referred to as uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0205] In the downlink, data to be sent from base station 1504 to wireless device 1502 may be provided to processing system 1508 of base station 1504. The data may be provided to processing system 1508 via, for example, a core network. In the uplink, data to be sent from wireless device 1502 to base station 1504 may be provided to processing system 1518 of wireless device 1502. Processing system 1508 and processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A , Figure 2B , Figure 3 and Figure 4A Layer 3 may include the following: Figure 2B RRC layer.

[0206] After processing by processing system 1508, data to be transmitted to wireless device 1502 may be provided to transmission processing system 1510 of base station 1504. Similarly, after processing by processing system 1518, data to be transmitted to base station 1504 may be provided to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0207] At base station 1504, receive processing system 1512 may receive uplink transmissions from wireless device 1502. At wireless device 1502, receive processing system 1522 may receive downlink transmissions from base station 1504. Receive processing system 1512 and receive processing system 1522 may implement layer 1 OSI functions. Layer 1 may include information about Figure 2A , Figure 2B , Figure 3 and Figure 4A For reception processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, etc.

[0208] like Fig.15 As shown, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0209] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or codes that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed herein. Fig.15 Not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or codes that may be executed to perform one or more of their respective functions.

[0210] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0211] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functionality, such as a speaker, a microphone, a keyboard, a display, a touch pad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 may receive user input data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526 and / or provide user output data to the one or more peripheral devices. The processing system 1518 in the wireless device 1502 can receive power from the power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as batteries, solar cell units, fuel cell units, or any combination thereof. The processing system 1508 and / or the processing system 1518 can be connected to the GPS chipset 1517 and the GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 can be configured to provide geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0212] Fig.16AAn example structure for uplink transmission is shown. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols to one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. In the example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In the example, when transform precoding is not enabled, the uplink transmission may be performed by Fig.16A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0213] Fig. 16B An example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0214] Fig. 16C An example structure for downlink transmission is shown. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0215] Fig.16D Another example structure for modulation and up-conversion of a baseband signal to a carrier frequency is shown. The baseband signal may be a complex valued OFDM baseband signal at an antenna port. Filtering may be employed prior to transmission.

[0216] The wireless device may receive one or more messages (e.g., RRC messages) containing configuration parameters of multiple cells (e.g., primary cells, secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device at the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, and RRC layer. For example, the configuration parameters may include parameters for configuring physical layer and MAC layer channels, bearers, and the like. For example, the configuration parameters may include parameters indicating the values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0217] Once started, the timer can start running and continue running until it stops or until it expires. If the timer is not running, it can be started, or if it is running, it can be restarted. The timer can be associated with a value (for example, the timer can start or restart from a certain value, or can start from zero and expire once it reaches the value). The duration of the timer may not be updated until the timer stops or expires (for example, due to BWP switching). The timer can be used for the time period / window of the measurement process. When the specification refers to embodiments and procedures related to one or more timers, it should be understood that there are multiple ways to implement the one or more timers. For example, it should be understood that one or more of the multiple ways of implementing the timer can be used to measure the time period / window of the procedure. For example, the random access response window timer can be used to measure the time window for receiving a random access response. In the example, instead of the start and expiration of the random access response window timer, the time difference between two timestamps can be used. When the timer is restarted, the measurement process of the time window can be restarted. Other example embodiments can be provided to restart the measurement of the time window.

[0218] The base station may transmit one or more MAC PDUs to the wireless device. In an example, the MAC PDU may be a bit string that is length byte aligned (e.g., aligned to a multiple of eight bits). In an example, the bit string may be represented by a table, wherein the most significant bit is the leftmost bit of the first row of the table, and the least significant bit is the rightmost bit of the last row of the table. More generally, the bit string may be read from left to right and then in the order in which the lines are read. In an example, the bit order of the parameter fields within the MAC PDU is represented by the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0219] In an example, the MAC SDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). In an example, the MAC SDU may be included in the MAC PDU starting from the first bit. The MAC CE may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). The MAC subheader may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of eight bits). In an example, the MAC subheader may be placed directly in front of the corresponding MAC SDU, MAC CE, or padding. The MAC entity may ignore the value of the reserved bit in the DL MAC PDU.

[0220] In an example, a MAC PDU may include one or more MAC subPDUs. A MAC subPDU in the one or more MAC subPDUs may include: only a MAC subheader (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. A MAC SDU may have a variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0221] In an example, when the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may include: a reserved field (R field) having a one-bit length; a format field (F field) having a one-bit length; a logical channel identifier (LCID) field having a multi-bit length; a length field (L field) having a multi-bit length, indicating the length of the corresponding MAC SDU or variable-size MAC CE in bytes; or a combination thereof. In an example, the F field may indicate the size of the L field.

[0222] In an example, the MAC entity of the base station may transmit one or more MAC CEs (e.g., MAC CE commands) to the MAC entity of the wireless device. The one or more MAC CEs may include at least one of the following: SP ZP CSI-RS resource set activation / deactivation MAC CE; PUCCH spatial relation activation / deactivation MAC CE; SP SRS activation / deactivation MAC CE; SP CSI report on PUCCH activation / deactivation MAC CE; TCI status indication of UE-specific PDCCH MAC CE; TCI status indication of UE-specific PDSCH MAC CE; aperiodic CSI triggering state subselection MAC CE; SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE; UE contention resolution identity MAC CE; timing advance command MAC CE; DRX command MAC CE; long DRX command MAC CE; SCell activation / deactivation MAC CE (1 octet); SCell activation / deactivation MAC CE (4 octets); and / or duplicate activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in a MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in a MAC subheader, which may be different from a second LCID in a MAC subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0223] In an example, a MAC entity of a wireless device may transmit one or more MAC CEs to a MAC entity of a base station. The one or more MAC CEs may include at least one of the following: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured granted MAC CE; a single entry PHR MAC CE; a multi-entry PHR MAC CE; a short truncated BSR; and / or a long truncated BSR. In an example, a MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in a MAC subheader, which may be different from a second LCID in a MAC subheader of a second MAC CE. For example, the LCID given by 111011 in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE.

[0224] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may use CA techniques to simultaneously receive or transmit on one or more CCs depending on the capabilities of the wireless device. In an example, a wireless device may support CA for contiguous CCs and / or for non-contiguous CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells).

[0225] When configured with CA, the wireless device may have one RRC connection with the network. During RRC connection establishment / reestablishment / handover, the cell that provides NAS mobility information may be the serving cell. During RRC connection establishment / handover procedures, the cell that provides security input may be the serving cell. In an example, the serving cell may be the PCell.

[0226] In an example, the base station may transmit one or more messages (e.g., one or more downlink signals) to the wireless device. The one or more messages may include one or more RRC messages, such as one or more RRC configuration / reconfiguration messages. For example, the one or more RRC messages may include one or more configuration parameters (e.g., one or more RRC configuration parameters).

[0227] In an example, one or more configuration parameters may include configuration parameters of multiple one or more SCells depending on the capabilities of the wireless device. When configured with CA, the base station and / or the wireless device may adopt an activation / deactivation mechanism for the SCell to improve the battery or power consumption of the wireless device. When the wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. Depending on the configuration of the SCell, the Scell ​​may be immediately deactivated unless the SCell state associated with the SCell is set to "activated" or "dormant". The wireless device may activate / deactivate the SCell in response to receiving a SCell activation / deactivation MAC CE.

[0228] For example, the base station may configure the wireless device (e.g., via one or more RRC messages / parameters) with an uplink (UL) bandwidth part (BWP) and a downlink (DL) BWP to enable bandwidth adaptation (BA) on the PCell. If carrier aggregation (CA) is configured, the base station may further configure the wireless device with at least one DL BWP (e.g., there may be no ULBWP in the UL) to enable BA on the SCell. For the PCell, the initial active BWP may be the first BWP used for initial access. In a paired spectrum (e.g., FDD), the base station and / or the wireless device may switch the DL BWP and the UL BWP independently. In an unpaired spectrum (e.g., TDD), the base station and / or the wireless device may switch the DL BWP and the UL BWP simultaneously.

[0229] In an example, a base station and / or a wireless device may switch a BWP between configured BWPs by means of a DCI or a BWP invalidity timer. When the BWP invalidity timer is configured for a serving cell, the base station and / or the wireless device may switch the active BWP to a default BWP in response to the expiration of the BWP invalidity timer associated with the serving cell. The default BWP may be configured by the network. In an example, for an FDD system, when configured with a BA, one UL BWP and one DL BWP for each uplink carrier may be active at a time in an active serving cell. In an example, for a TDD system, a DL / UL BWP pair may be active at a time in an active serving cell. Operating on one UL BWP and one DL BWP (or one DL / UL pair) may improve wireless device battery consumption. One or more BWPs other than the active UL BWP and the active DL BWP on which the wireless device can operate may be deactivated. On one or more deactivated BWPs, the wireless device may: not monitor the PDCCH; and / or not transmit on the PUCCH, PRACH, and UL-SCH. In an example, the MAC entity of the wireless device may apply normal operations to the active BWP of the activated serving cell configured with the BWP, including: transmitting on UL-SCH; transmitting on RACH; monitoring PDCCH; transmitting PUCCH; receiving DL-SCH; and / or (re)initializing any suspended configured uplink grants of configured grant type 1 according to the stored configuration (if any). In an example, on the inactive / idle BWP of each activated serving cell configured with the BWP, the MAC entity of the wireless device may: not transmit on UL-SCH; not transmit on RACH; not monitor PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignments and configured uplink grants of configured grant type 2; and / or suspend any configured uplink grants of configured type 1.

[0230] In an example, a DCI addressed to the RNTI may include a CRC of the DCI scrambled with the RNTI. The wireless device may monitor a PDCCH addressed to (or for) the RNTI to detect the DCI. For example, the PDCCH may carry (or have) the DCI. In an example, the PDCCH may not carry the DCI.

[0231] In an example, a set of PDCCH candidates to be monitored by a wireless device is defined according to one or more search space sets. A search space set may include a common search space (CSS) set or a UE-specific search space (USS) set. The wireless device may monitor one or more PDCCH candidates in one or more of the following search space sets (e.g., one or more search space sets): a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB or by searchSpaceSIB1 in the PDCCH-ConfigCommon or by searchSpaceZero in the PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the SI-RNTI on the primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in the PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the SI-RNTI on the primary cell of the MCG; a Type1-PDCCH CSS set configured by ra-SearchSpace in the PDCCH-ConfigCommon for a DCI format with a CRC scrambled by the RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell CSS set; Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for DCI format with CRC scrambled by P-RNTI on primary cell of MCG; Type3-PDCCH configured by SearchSpace with searchSpaceType=common in PDCCH-Config for DCI format with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI or Power Saving RNTI (PS-RNTI) and only for primary cell, C-RNTI, MCS-C-RNTI or CS-RNTI CSS set; and the USS set configured by SearchSpace with searchSpaceType=ue-Specific in PDCCH-Config for a DCI format with a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI or SL-L-CS-RNTI.

[0232] In an example, a wireless device may monitor one or more PDCCH candidates according to one or more configuration parameters of a search space set. For example, the search space set may include multiple search spaces (SSs). The wireless device may monitor one or more PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring one or more PDCCH candidates may include decoding at least one PDCCH candidate among the one or more PDCCH candidates according to the monitored DCI format. For example, monitoring one or more PDCCH candidates may include decoding (e.g., blind decoding) the DCI content of at least one PDCCH candidate via possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a CSS set, and / or the number of PDCCH candidates in a USS), and / or possible (or configured) DCI formats.

[0233] In an example, the wireless device may receive a C-RNTI from a base station (e.g., via one or more previous transmissions). For example, the one or more previous transmissions may include Msg2 1312, Msg4 1314, or MsgB 1332. If a Type3-PDCCH CSS set or USS set is not provided to the wireless device and if a Type1-PDCCH CSS set is provided to the wireless device, the wireless device may monitor one or more PDCCH candidates having DCI format 0_0 and DCI format 1_0 scrambled with the C-RNTI in the Type1-PDCCH CSS set.

[0234] For example, one or more search space sets may correspond to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, and C-RNTI, MCS-C-RNTI, or CS-RNTI. The wireless device may monitor one or more PDCCH candidates having DCI format 0_0 and DCI format 1_0 with CRC scrambled with the C-RNTI, MCS-C-RNTI, or CS-RNTI in one or more search space sets in a time slot, where the wireless device monitors one or more PDCCH candidates having at least DCI format 0_0 or DCI format 1_0 with CRC scrambled with SI-RNTI, RA-RNTI, MSGB-RNTI, or P-RNTI.

[0235] Fig.17Several DCI formats are shown. For example, a base station may use a DCI format to transmit downlink control information to a wireless device. In an example, a wireless device may use a DCI format for PDCCH monitoring. Different DCI formats may contain different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. Fig.17 As shown, DCI format 0_0 can be used to schedule PUSCH in one cell. In the example, DCI format 0_1 ​​can be used to schedule one or more PUSCHs in one cell, or indicate CG-DFI (configured grant downlink feedback information) configured to grant PUSCH, etc.

[0236] In an example, the wireless device may support a baseline processing time / capability. For example, the wireless device may support an additional aggressive / faster processing time / capability. In an example, the wireless device may report the processing capability to the base station, for example, per subcarrier interval. In an example, the PDSCH processing time may be considered to be determined by the wireless device as the first uplink symbol of the PUCCH (e.g., determined based on at least the HARQ-ACK timing K1 and one or more PUCCH resources to be used, and including the effect of timing advance), which first uplink symbol contains HARQ-ACK information for the PDSCH scheduled by the DCI. In an example, the first uplink symbol of the PUCCH may not be earlier than a time gap (e.g., T 1 ) after the last symbol of the PDSCH received associated with the HARQ-ACK information. proc,1 ). In the example, the first uplink symbol of the PUCCH carrying HARQ-ACK information may start no earlier than symbol L1, where L1 is defined as the next uplink symbol whose cyclic prefix (CP) is at the time slot T after the end of the last symbol of the PDSCH. proc,1 Then start.

[0237] In an example, the transmission time of UL data may be determined taking into account the PUSCH preparation / processing time. For example, if the first uplink symbol (including DM-RS) in the PUSCH allocation for the transport block is not earlier than symbol L2, the wireless device may perform transmission of PUSCH. In an example, the wireless device may determine symbol L2 based at least on the time slot offset (e.g., K2) SLIV of the PUSCH allocation indicated by the time domain resource assignment of the scheduling DCI. In an example, symbol L2 may be designated as the next uplink symbol whose CP is after the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, within a time slot having a length T proc,2 starts after the time gap.

[0238] In an example, the one or more configuration parameters may include one or more DRX configuration parameters (e.g., DRX-Config). The one or more DRX configuration parameters may configure the wireless device to have DRX operation. In an example, the one or more DRX configuration parameters may indicate monitoring of the PDCCH for the DRX operation. For example, when in the RRC_CONNECTED state, if the DRX operation is configured (e.g., DRX is configured or the DRX cycle is configured), then for all activated serving cells (e.g., serving cells), the MAC entity of the wireless device may monitor the PDCCH discontinuously using the DRX operation. Otherwise, the MAC entity may monitor the PDCCH continuously.

[0239] For example, the wireless device may use DRX operation when communicating with a base station in a serving cell based on the configured DRX operation. For example, the MAC entity (or MAC layer) of the wireless device may control the PDCCH monitoring activity of the MAC entity based on the configured DRX operation. When the DRX operation is configured, the wireless device may monitor the PDCCH for at least one RNTI. In the example, at least one RNTI may include one or more of the following: C-RNTI, cancellation indication RNTI (CI-RNTI), configured scheduling RNTI (CS-RNTI), interruption RNTI (INT-RNTI), time slot format indication RNTI (SFI-RNTI), semi-persistent channel state information RNTI (SP-CSI-RNTI), transmission power control physical uplink control channel RNTI (TPC-PUCCH-RNTI), transmission power control physical shared channel RNTI (TPC-PUSCH-RNTI), transmission power control channel sounding reference signal RNTI (TPC-SRS-RNTI) or availability indicator RNTI (AI-RNTI).

[0240] Fig.18A An example of a non-terrestrial network is shown. A non-terrestrial network (NTN) network (e.g., a satellite network) may be a network or network segment (e.g., an NG-RAN consisting of gNBs) for providing non-terrestrial NR access to wireless devices. The NTN may use a space vehicle to embody a transmission equipment relay node (e.g., a radio remote unit or a transparent payload) or a base station (or a regenerative payload). While a terrestrial network is a network located on the surface of the earth, an NTN may be a network that uses an NTN node (e.g., a satellite) as an access network, a backhaul interface network, or both. In an example, the NTN may include one or more NTN nodes (or payloads and / or space vehicles), each of which may provide a connection function between a service link and a feeder link.

[0241] NTN nodes may carry bent-pipe payloads (e.g., transparent payloads) or regenerative payloads. NTN nodes with transparent payloads may include transmitter / receiver circuitry without onboard digital signal processing (e.g., modulation and / or coding) capabilities and are connected to a base station (e.g., a base station of the NTN or an NTN base station or a non-terrestrial access point) via a feeder link. In some aspects, such as Fig.18A As shown, a base station (e.g., a gNB) may further include a transparent NTN node, a feeder link, and / or a gateway (e.g., an NTN gateway). A gateway may be a ground station located on the surface of the earth that provides a connection to an NTN payload using a feeder link. In some examples, an NTN node with a regenerative payload (e.g., a base station of an NTN or an NTN base station) may include the functionality of a base station, such as onboard processing for demodulating and decoding received signals and / or regenerating signals before sending / transmitting the signals back to the earth. In some aspects, as Fig.18A As shown, the base station (e.g., gNB) may further include a regenerated NTN node, a feeder link and / or a gateway (e.g., an NTN gateway).

[0242] In some examples, the NTN nodes may be satellites, balloons, airships, aircraft, unmanned aircraft systems (UAS), unmanned aerial vehicles (UAV), drones, etc. For example, the UAS may be a soft-aircraft, a high altitude platform station (HAPS), such as an aerial vehicle placed at an altitude between 8 km and 50 km carrying an NTN payload, or may be a pseudo-satellite station. Fig.18B is an example diagram of different types of NTN platforms. In an example, a satellite may be placed in a low earth orbit (LEO) at an altitude between 250km and 1500km, with an orbital period in the range of 90 minutes to 130 minutes. From the perspective of a given point on the earth's surface, the positioning of a LEO satellite may change. In an example, a satellite may be placed in a medium earth orbit (MEO) at an altitude between 5000km and 20000km, with an orbital period in the range of 2 hours to 14 hours. In an example, a satellite may be placed in a geosynchronous satellite orbit (GEO) at an altitude of 35,786km and directly above the equator. From the perspective of a given point on the earth's surface, the positioning of a GEO satellite may not change.

[0243] Fig.19A An example of an NTN with a transparent NTN platform is shown. Fig.19A As shown, an NTN node (e.g., a satellite) can forward received signals from an NTN gateway on the ground back to the earth via a feeder link. In an example, the gateway and the base station may not be collocated. The NTN node can forward received signals from another NTN node to a wireless device or base station, for example, via an inter-link satellite communication link.

[0244] An NTN node may generate one or more beams within a given area (e.g., a coverage area or cell). The coverage area of ​​a beam (or cell) may be referred to as a spot beam. For example, the coverage area of ​​a cell / beam may move over the surface of the Earth as the satellite moves (e.g., LEO with mobile cells or HAPS with mobile cells). The coverage area of ​​a cell / beam may be Earth-fixed, with the satellite using some beam-steering mechanism to compensate for its motion (e.g., LEO with Earth-fixed cells). Fig.18B As shown, the size of the spot beam can range from tens of kilometers to thousands of kilometers. For example, the size of the spot beam can depend on the system design.

[0245] The propagation delay may be the amount of time it takes for the header of a signal to travel from a sender (e.g., a base station or NTN node) to a receiver (e.g., a wireless device) (or vice versa). For an uplink, the sender may be a wireless device and the receiver may be a base station / access network. For a downlink, the sender may be a base station / access network and the receiver may be a wireless device. The propagation delay may vary depending on a change in the distance between the sender and the receiver, such as due to movement of an NTN node, movement of a wireless device, changes in an inter-satellite link, and / or a feeder link switch.

[0246] Fig.19B An example of propagation delay corresponding to NTNs of different heights is shown. The propagation delay in the figure can be a one-way delay / latency. In an example, the one-way delay / latency can be the amount of time required to propagate from a sender (e.g., a base station) to a receiver (e.g., a wireless device) through a telecommunications system. Fig.19B In the example shown, for transparent NTN, the round-trip propagation delay (RTD or UE-gNB RTT) can include the service link delay (e.g., between the NTN node and the wireless device), the feeder link delay (e.g., between the NTN gateway and the NTN node), and / or between the gateway and the base station (e.g., when the gateway and the NTN base station are not co-located). For example, the UE-gNB RTT (or RTD) can be twice the one-way delay between the wireless device and the base station. Fig.19B , in the case of a GEO satellite with a transparent payload, the RTD can be four times 138.9 milliseconds (approximately 556 milliseconds). In an example, the RTD of a terrestrial network (e.g., NR, E-UTRA, LTE) is negligible compared to the RTD of the NTN scenario (e.g., the RTD of the terrestrial network can be less than 1 millisecond). The maximum RTD of a LEO satellite with a transparent payload and 600km altitude is approximately 25.77 milliseconds, and the maximum RTD of a LEO satellite with a 1200km altitude is approximately 41.77 milliseconds.

[0247] The differential delay within a beam / cell of an NTN node may depend, for example, on the maximum diameter of the beam / cell coverage area at the lowest point. Fig.19A In an example, differential delay may mean that two wireless devices, such as Fig.19B The maximum difference between the communication delays that a first wireless device (UE1) near the center of a cell / beam and a second wireless device (UE2) near the edge of a cell / beam may experience when communicating with a base station via an NTN node. The first wireless device may experience a smaller RTD than the second wireless device. The link with the maximum propagation delay (e.g., the maximum delay link) may experience the highest propagation delay (or maximum RTD) in the cell / beam. In an example, the differential delay may mean the difference between the maximum delay of the cell / beam and the minimum delay of the cell / beam. In an example, the service link to the center of the cell / beam may experience the minimum propagation delay in the cell / beam. Depending on the implementation, for LEO satellites, the differential delay can be at least 3.12 milliseconds and can be increased to up to 8 milliseconds. In the example of a GEO satellite, the differential delay can be as high as 32 milliseconds depending on the implementation.

[0248] Wireless devices (e.g. Fig.19BIn some aspects, the wireless device may indicate a capability of NR NTN access (e.g., nonTerrestrialNetwork-r17), for example, a capability of receiving one or more NTN configuration parameters (e.g., via one or more NTN-specific SIBs). For example, the wireless device may receive one or more NTN configuration parameters from broadcast system information (e.g., SIB1 and / or one or more NTN-specific SIBs). The one or more NTN configuration parameters may facilitate / manage the calculation / determination / measurement of propagation delay (e.g., UE-gNBRTT) and / or timing advance (TA) at one or more wireless devices (e.g., wireless devices) residing in a cell / beam. In an example, the one or more NTN configuration parameters may include at least one ephemeris parameter (e.g., satellite ephemeris parameter or NTN ephemeris parameter), one or more common delay / TA parameters, validity duration (or timer or window) of UL synchronization, epoch time, and / or one or more timing offset parameters. The validity duration may be used for uplink synchronization assistance information (e.g., one or more NTN configuration parameters). In an example, the validity duration may indicate a maximum time that the wireless device may apply the assistance information (e.g., one or more NTN configuration parameters) without (re)acquiring new assistance information (e.g., without reacquiring NTN specific SIB or SIB1). For example, one or more NTN configuration parameters may enable TA reporting.

[0249] In an example, the wireless device may maintain / calculate a cell-specific timing offset, one or more beam-specific timing offsets, and / or a UE-specific timing offset (e.g., a UE-specific K_Offset) based on one or more timing offset parameters and / or one or more MAC CE commands and / or one or more RRC signaling. For example, the one or more timing offset parameters may include a first timing offset (e.g., Koffset in ServingCellConfigCommon). In some aspects, the first timing offset may be the reason why the cell / beam has the largest RTD. For example, the wireless device may track / update / maintain the cell / beam-specific timing offset based on an update of the first timing offset received from the base station. For example, the wireless device may receive a second timing offset (e.g., a differential UE-specific K_Offset MAC CE). The wireless device may update / track / maintain the UE-specific timing offset based on the second timing offset and / or the cell-specific timing offset.

[0250] In an example, one or more timing offset parameters may configure / indicate a third timing offset. The wireless device (or base station) may set a MAC-specific timing offset (or MAC layer timing offset) represented by K-Mac based on the third timing offset. For example, when the third timing offset is not indicated / configured, K-Mac may be 0. For example, in an NTN scenario with transparent NTN nodes, when UL frames and DL frames are aligned at the base station, the third timing offset may not be present in one or more NTN configuration parameters or may be 0. In an example, as Fig.19B As shown, the MAC-specific timing offset may indicate a portion of the propagation delay (e.g., UE-gNB RTT) that the base station may pre-compensate for (e.g., when the UL frame and the DL frame are not aligned at the base station), for example, the third timing offset may indicate the difference between the UL frame / configuration timing and the DL frame / configuration timing at the base station. Fig.19B As shown, the UL frame and the DL frame may be aligned at a reference point on the feeder link. For example, the reference point may be an NTN node, for example, the third timing offset is equal to the feeder link delay.

[0251] To maintain uplink orthogonality, the signals from different wireless devices in a cell / beam (e.g. Fig.19B The transmissions of the first wireless device and the second wireless device in the wireless communication may need to be aligned in time at the base station and / or NTN node (e.g., satellite). In an example, time alignment / synchronization may be achieved by using different timing advance (TA) values ​​at different wireless devices to compensate for their different propagation delays (or RTDs). Fig.19B As shown, the first wireless device may use a first TA value (eg, TA_1), and the second wireless device may use a second TA value (TA_2).

[0252] For example, the wireless device may calculate / measure / maintain the current TA (value) of the wireless device (e.g., N) based at least on a combination of a closed-loop TA program / control and / or an open-loop TA program / control. TA ). The current TA value of the first wireless device may be TA_1, and the current TA value of the second wireless device may be TA_2.

[0253] The closed-loop TA procedure / control may be based on receiving at least one TA command (TAC) MAC CE from the base station. For example, the at least one TAC CE may include the TA (or absolute TA) command field of Msg2 1312 (or MsgB 1332).

[0254] The open-loop TA procedure / control may require the wireless device's GNSS acquisition of a position fix (or location information) and / or require receiving one or more NTN configuration parameters, such as one or more ephemeris parameters (e.g., satellite ephemeris data) and / or one or more common delay / TA parameters (e.g., common TA value). Based on the implemented orbit predictor / propagator model, the wireless device may use one or more ephemeris parameters (and / or GNSS acquisition of a position fix) to measure / calculate / maintain the satellite's movement pattern, estimate / measure the service link delay, and / or adjust the current TA value (e.g., the wireless device's TA) via the open-loop TA procedure / control. In an example, a combination of closed-loop TA control and open-loop TA control may be based on adding / summing an open-loop TA value (e.g., derived / calculated based on the open-loop TA procedure / control) and a closed-loop TA value (or a portion of the closed-loop TA procedure / control).

[0255] In an example, the wireless device may calculate / measure / estimate the UE-gNB RTT (or RTD) based on the current TA value and a third timing offset (e.g., K-Mac). For example, the UE-gNB RTT may be the sum of the current TA value and K-Mac. In an example, if the third timing offset is not indicated or when K-Mac is 0, the wireless device may determine / measure the UE-gNB RTT based on the current TA value, e.g., the UE-gNB RTT is equal to the current TA value. In an example, the wireless device may maintain / calculate / update the open-loop TA value (or UE-gNB RTT) for a validity duration. For example, the validity duration may indicate a validity period for (satellite) ephemeris data / information and / or one or more common TA parameters. In an example, the validity duration may specify / indicate a maximum time period / window (e.g., corresponding to an orbit predictor / propagator model that the wireless device is using to estimate / calculate propagation delay and / or a maximum allowable error when estimating / measuring / calculating an open-loop TA value), during which the wireless device may not need to read / update / acquire satellite ephemeris data and / or acquire one or more NTN-specific SIBs. For example, based on or in response to acquiring new (satellite) ephemeris data (or parameters) and / or one or more NTN-specific SIBs, the wireless device may start / restart the validity duration based on an epoch time indicated by one or more NTN configuration parameters. In an example, in response to determining that the validity duration has expired, the wireless device may acquire one or more NTN-specific SIBs to receive updated (satellite) ephemeris data / information and / or an update of one or more common TA parameters. In an example, after the validity duration has expired and when the wireless device is unable to acquire one or more NTN-specific SIBs, the wireless device may become unsynchronized with the base station, e.g., for UL communication with the base station.

[0256] In some aspects, in response to receiving one or more NTN configuration parameters (e.g., via obtaining one or more NTN-specific SIBs) and / or obtaining an updated GNSS acquisition position, the wireless device may calculate / measure / update a current TA value via an open-loop TA procedure / control. In another example, the wireless device may update the current TA value based on a closed-loop TA procedure / control, for example, based on receiving one or more TAC MAC CEs. In the example, based on the current TA value being updated, the wireless device may adjust (recalculate) the UE-gNB RTT. In the example, based on receiving a new third timing offset, the wireless device may set K-Mac and adjust (recalculate) the UE-gNB RTT. In another example, the wireless device may periodically calculate / measure / update the current TA value. For example, before performing an uplink transmission, the wireless device may calculate / measure / update the current TA value.

[0257] In an example, the wireless device may set the common TA / delay to zero in response to determining that one or more common TA / delay parameters are not present in one or more NTN configuration messages. For example, when the reference point is located at the NTN node (e.g., the third timing offset is equal to the feeder link delay), the common TA / delay may be zero. In another example, for NTN with transparent payload, when UL timing synchronization is maintained at the NTN node (e.g., UL and DL frames are aligned at the base station), the wireless device may not pre-compensate for the common TA.

[0258] In an example, a wireless device with GNSS capabilities may need to estimate the propagation delay (or service link delay) based on one or more measurements. For example, the one or more measurements may indicate the location information (positioning) acquired by the GNSS of the wireless device. In an example, the one or more measurements may allow the wireless device to calculate / estimate the propagation delay (or open-loop TA value) using the GNSS-acquired positioning and (satellite) ephemeris data / information. In another example, the one or more measurements may allow the wireless device to estimate / calculate the propagation delay via one or more timestamps (e.g., timestamps of configured broadcast signals) and / or epoch times. In an example, the one or more measurements may allow the wireless device to estimate / measure the rate of change of the common TA and / or service link delay over a period of time.

[0259] In the prior art, a base station may configure a wireless device using one or more measurement configuration parameters (e.g., MeasConfig). In some examples, one or more configuration parameters (e.g., RRCReconfiguration or RRCResume) may include one or more measurement configuration parameters. One or more measurement configuration parameters may configure the wireless device to, for example, perform positioning measurements (e.g., one or more location-related measurements and / or perform positioning measurement procedures) on at least one serving cell (e.g., serving cell) and / or on at least one non-serving cell. In some examples, one or more measurement configuration parameters (e.g., MeasConfig) may indicate (e.g., specify, configure) one or more measurements (e.g., at least one measurement and / or one or more location-related measurements and / or one or more positioning measurements) for performing positioning measurements during one or more positioning measurement gaps (or one or more positioning measurement gap opportunities / occurrences). In some examples, one or more measurement configuration parameters may indicate / configure one or more positioning measurement gaps (e.g., via PosGapConfig).

[0260] In the prior art, with respect to performing positioning measurements, the wireless device may request a base station (e.g., a network) to activate or deactivate a positioning measurement gap in one or more positioning measurement gaps, for example, by transmitting a positioning measurement gap request MAC CE. In some examples, the positioning measurement gap request MAC CE may be a positioning measurement gap activation request MAC CE, for requesting activation of a positioning measurement gap, for example, to perform a positioning measurement procedure during the positioning measurement gap. In some other examples, the positioning measurement gap request MAC CE may be a positioning measurement gap deactivation request MAC CE, for requesting deactivation (activated) of the positioning measurement gap (e.g., stopping performing the positioning measurement procedure during the positioning measurement gap). In the prior art, in order to transmit the positioning measurement gap request MAC CE, the wireless device may determine whether the positioning measurement gap request is triggered and not canceled. In some examples, in response to determining that the positioning measurement gap request is not canceled and UL-SCH resources are available for new UL transmission (e.g., the UL-SCH resources accommodate the positioning measurement gap request MAC CE and its subheader due to logical channel prioritization (LCP), the wireless device may transmit the positioning measurement gap request MAC CE. In some other examples, in response to determining that the positioning measurement gap request is not canceled and UL-SCH resources are not available for new transmission (e.g., the UL-SCH resources accommodate the positioning measurement gap request MAC CE and its subheader due to LCP), the wireless device may trigger a scheduling request (SR) for the positioning measurement gap request. The wireless device may cancel the triggered positioning measurement gap request based on transmitting the positioning measurement gap request MAC CE or the SR.

[0261] In the prior art, in an NTN scenario, there may be continuous (and / or substantial) changes / fluctuations in the round-trip transmission delay (e.g., UE-gNB RTT) between the wireless device and the base station by moving / shifting the NTN payload / node. Based on the prior art, the wireless device may lose UL synchronization (of a serving cell in one or more serving cells) based on, for example, invalidity of one or more NTN configuration parameters and / or expiration of a validity timer (e.g., a validity timer corresponding to / for the validity of the NTN configuration parameters). In some examples, the wireless device may lose UL synchronization of the serving cell before transmitting a positioning measurement gap request MAC CE or after receiving a response (e.g., a positioning measurement gap activation command MAC CE) from the base station.

[0262] In the prior art, in an NTN scenario, despite the loss of UL synchronization (of a serving cell in one or more serving cells), the wireless device may continue to trigger a positioning measurement gap request and / or attempt to transmit (unsuccessfully) a positioning measurement gap request MAC CE. In some cases, when the wireless device is not synchronized with the base station (e.g., the UL synchronization of a serving cell in one or more serving cells is lost), any uplink transmission (e.g., transmission of a positioning measurement gap request MAC CE) may not be allowed. In some examples, the wireless device may clear the HARQ buffer (e.g., the HARQ buffer of the positioning measurement gap request MAC CE) based on the loss of UL synchronization of a serving cell in one or more serving cells when the positioning measurement gap request is triggered and not cancelled. In some cases, in response to (re)acquiring an NTN-specific SIB or SIB1 (e.g., verifying one or more NTN configuration parameters) and a triggered positioning measurement gap request pending (not cancelled), the wireless device may attempt to transmit a positioning measurement gap request MAC CE when the HARQ buffer of the positioning measurement gap request MAC CE is cleared. This may result in undefined behavior / conditions at the wireless device.

[0263] In another example, before transmitting the positioning measurement gap deactivation request MAC CE after receiving the positioning measurement gap activation command MAC CE from the base station, the wireless device may lose UL synchronization of the serving cell in one or more serving cells. Despite the loss of UL synchronization of the serving cell in one or more serving cells, the wireless device may maintain / keep the positioning measurement gap activated. Based on the implementation of the prior art, in the NTN scenario, the efficiency of the wireless device activating / deactivating the positioning measurement gap may be reduced. In some examples, the wireless device may unnecessarily keep the positioning measurement gap activated. This may increase the power consumption or complexity of the wireless device, for example, by performing one or more measurements during the positioning measurement gap.

[0264] According to an example embodiment of the present disclosure, a wireless device may determine whether to request a base station (e.g., a network) to activate / deactivate a positioning measurement gap in one or more positioning measurement gaps (e.g., whether to trigger a positioning measurement gap request) based on a validity timer corresponding to a serving cell in one or more serving cells. Some example embodiments may improve the efficiency of positioning procedures in NTN scenarios, and / or reduce the power consumption or complexity of wireless devices.

[0265] In an example embodiment of the present disclosure, based on whether UL synchronization of a serving cell in one or more serving cells is lost (e.g., whether a validity timer corresponding to the serving cell is running), the wireless device may determine whether to request a base station (e.g., a network) to activate / deactivate a positioning measurement gap in one or more positioning measurement gaps (e.g., whether to trigger a positioning measurement gap request). In an example, based on obtaining / maintaining UL synchronization of a serving cell in one or more serving cells, for example, the validity timer corresponding to the serving cell is running, the wireless device may trigger a positioning measurement gap request (e.g., requesting the base station to activate / deactivate the positioning measurement gap). For example, based on one or more NTN configuration parameters being invalid (e.g., the validity timer is running), the wireless device may not trigger a positioning measurement gap request (e.g., requesting the base station to activate / deactivate the positioning measurement gap).

[0266] In an example embodiment, the wireless device may determine that a triggered measurement gap deactivation request (e.g., positioning measurement gap deactivation request MAC CE) is triggered and not canceled. In an example embodiment, in response to a UL synchronization loss of a serving cell (e.g., expiration of a validity timer of the serving cell and / or invalidation of one or more NTN configuration parameters), a higher layer (e.g., RRC sublayer) of the wireless device may send / notify a lower layer (e.g., MAC layer) of the wireless device to cancel the triggered measurement gap deactivation request. Some example embodiments may reduce the likelihood of undefined behavior at the wireless device.

[0267] In an example embodiment, the base station may configure the wireless device with a first configuration parameter (e.g., via one or more configuration parameters). For example, in response to determining that the first configuration parameter is indicated / configured (or enabled or not disabled, or present in one or more configuration parameters), the wireless device may determine whether to trigger a positioning measurement gap activation / deactivation request based on whether UL synchronization of a serving cell in one or more serving cells is lost (e.g., based on whether one or more NTN configuration parameters are valid). For example, based on the first configuration parameter being indicated / configured (or enabled or not disabled, or present in one or more configuration parameters) and one or more NTN configuration parameters being invalid (e.g., UL synchronization of a serving cell in one or more serving cells is lost), the wireless device may not trigger a positioning measurement gap activation / deactivation request.

[0268] In an example embodiment, based on one or more NTN configuration parameters being invalid (e.g., the validity timer of the serving cell is not running or expired), the lower layer (e.g., MAC layer) of the wireless device may cancel the triggered positioning measurement gap activation / deactivation request. For example, the wireless device may not request the base station to activate / deactivate the positioning measurement gap.

[0269] Some example embodiments may reduce the complexity of a wireless device, for example, by determining whether to trigger a positioning measurement gap activation / deactivation request based on whether one or more NTN configuration parameters are valid.

[0270] In an example embodiment, in response to determining that UL synchronization of a serving cell is lost (e.g., one or more NTN configuration parameters are invalid and / or a validity timer of the serving cell expires), the wireless device may (automatically) deactivate an activated positioning measurement gap on the serving cell. For example, the wireless device may determine (e.g., using the activated positioning measurement gap) that a positioning measurement procedure is ongoing. For example, the wireless device may stop / interrupt / pause / deactivate performing the positioning measurement procedure on the serving cell. A benefit of deactivating the positioning measurement gap may be a reduction in processing complexity / consumption power of the wireless device. A disadvantage of deactivating the positioning measurement gap may be a reduction in the accuracy of location information at the wireless device and / or base station.

[0271] In an example embodiment, the wireless device may deactivate the positioning measurement gap within / during the waiting (or deactivation) window / duration / time period. For example, the waiting window may be used for the wireless device to (re)acquire the NTN-specific SIB and / or SIB1 (e.g., verify one or more NTN configuration parameters). For example, the wireless device may stop / interrupt / pause performing the positioning measurement procedure on the serving cell during the waiting window. In response to (re)acquiring the NTN-specific SIB and / or SIB1 (e.g., starting the validity timer and / or verifying one or more NTN configuration parameters), the wireless device may (automatically) start (or resume) the positioning measurement procedure on the serving cell.

[0272] In an example embodiment, in response to determining that UL synchronization of a serving cell is lost (e.g., one or more NTN configuration parameters are invalid and / or validity timers expire), the wireless device may not deactivate the positioning measurement gap on the serving cell (e.g., the wireless device may keep the positioning measurement gap activated). For example, the wireless device may determine that a positioning measurement procedure is ongoing. Some example embodiments may allow the wireless device (and / or base station) to keep performing the positioning measurement procedure despite the loss of UL synchronization of the serving cell (e.g., to improve the performance / accuracy of the positioning procedure). A disadvantage may be increased processing complexity / consumption power of the wireless device.

[0273] In an example embodiment, the base station may configure the wireless device with a second configuration parameter (e.g., via one or more configuration parameters). The second configuration parameter may, for example, indicate whether to (automatically) deactivate (activate) the positioning measurement gap in response to a UL synchronization loss of a serving cell in one or more serving cells. For example, in response to determining that the second configuration parameter is indicated / configured (or enabled or not deactivated, or present in one or more configuration parameters), the wireless device may determine whether to deactivate the positioning measurement gap based on the UL synchronization loss of the serving cell in one or more serving cells (e.g., based on whether one or more NTN configuration parameters are valid). For example, based on the second configuration parameter not being indicated / configured (or being deactivated or not enabled, or not present in one or more configuration parameters) and the UL synchronization loss of the serving cell in one or more serving cells, the wireless device may not deactivate the positioning measurement gap on the serving cell (e.g., the wireless device may keep the positioning measurement gap activated).

[0274] In an example embodiment, the wireless device may transmit a UE capability message to the base station. For example, the UE capability of the wireless device may indicate the ability of the wireless device to perform one or more measurements when UL synchronization of a serving cell is lost (e.g., due to expiration of a validity timer of the serving cell and / or invalidity of one or more configuration parameters). In some other cases, the UE capability message may indicate the ability of the wireless device to automatically deactivate (activate) positioning measurement gaps or not deactivate (activate) positioning measurement gaps in response to UL synchronization loss of a serving cell in one or more serving cells.

[0275] Fig. 20 An example embodiment of a positioning procedure in a wireless communication system according to aspects of the present disclosure is shown. For example, a wireless device may be in an RRC connected state / mode (e.g., RRC_CONNECTED state) and / or in an RRC non-connected state / mxttode (e.g., RRC_INACTIVE / IDLE state or RRC_IDLE state). In some embodiments, Fig. 20 An embodiment of a method (or process) for locating a procedure may be shown.

[0276] The wireless device may communicate with the base station, for example, via a non-terrestrial network (NTN), for example, the wireless device and the base station may operate in the NTN and / or the base station may be an NTN base station and / or the cell (e.g., a serving cell in one or more serving cells) may be part of the NTN. For example, the cell may be a serving cell or a non-serving cell.

[0277] like Fig. 20 As shown, the wireless device may receive one or more configuration parameters (e.g., one or more RRC configuration parameters) from the base station at time T0. The one or more configuration parameters may, for example, include one or more serving cell (e.g., one or more serving cells or one or more cells) configuration parameters (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB and / or ServingCell Config) for configuring one or more cells (e.g., one or more serving cells).

[0278] For example, one or more cells may include a master / primary cell group (MSG) and / or a secondary cell group (SCG). In some cases, a cell in one or more cells may be a primary / secondary cell (PSCell), or a primary cell (PCell) or a secondary cell (SCell), or a special cell (SpCell). In some other cases, a cell in one or more cells may belong to a first cell group corresponding to a primary TAG (pTAG) or a second cell group corresponding to a secondary TAG (sTAG). For example, one or more configuration parameters may configure the wireless device for multi-cell communication and / or carrier aggregation.

[0279] One or more configuration parameters (e.g., using RRCReconfiguration or RRCResume) may include one or more measurement configuration parameters (e.g., MeasConfig). In an example, one or more measurement configuration parameters may configure the wireless device to, for example, perform measurements (e.g., one or more measurements or one or more location-related measurements and / or perform a positioning measurement procedure) on at least one serving cell (e.g., a serving cell) or on at least one non-serving cell. One or more measurement configuration parameters (e.g., MeasConfig) may indicate / specify / configure one or more measurements (e.g., at least one measurement and / or one or more location-related measurements). In some cases, one or more measurement configuration parameters (e.g., MeasConfig) may cover / include intra-frequency, inter-frequency, and inter-RAT mobility and measurement gap configuration. The wireless device may perform one or more measurements (e.g., one or more location-related measurements and / or a positioning measurement procedure) using / based on one or more measurement configuration parameters (e.g., MeasConfig). For example, in order to perform a positioning procedure, the wireless device may perform one or more measurements (e.g., at least one measurement and / or one or more location-related measurements).

[0280] For example, the one or more measurement configuration parameters may include at least one of the following: a measurement object indicating a list of (measurement) objects on which the wireless device may perform measurements (e.g., one or more location-related measurements); and / or a reporting configuration; and / or a measurement identity indicating a list of measurement identities, wherein each measurement entity (in the list of measurement identities) links one measurement object (in the measurement objects) with one reporting configuration (in the reporting configuration); and / or a quantity configuration (e.g., QuantityConfig) indicating / defining a measurement filter configuration for all event evaluations and related reports and for periodically reporting measurements (e.g., location-related measurements in one or more location-related measurements); and / or a measurement gap (e.g., MeasGapConfig) indicating one or more time periods / windows / durations for performing measurements (e.g., one or more location-related measurements); and / or a measurement threshold for NR SpCell RSRP measurement (e.g., s-MeasureConfig) that controls when the wireless device performs measurements on non-serving cells (e.g., RSRP based on SS / PBCH blocks or CSI-RS).

[0281] like Fig. 20 As shown, the one or more configuration parameters may include one or more NTN configuration parameters. For example, the wireless device may receive the one or more NTN configuration parameters by acquiring SIB1 and / or NTN-specific SIBs (eg, SIB19).

[0282] In some cases, such as Fig. 20 As shown, one of the one or more NTN configuration parameters may include multiple NTN-specific configuration parameters (e.g., ntn-Config), such as one or more NTN-specific configuration parameters. For example, one of the one or more NTN configuration parameters may include one or more ephemeris parameters (e.g., satellite ephemeris data and / or at least one satellite ephemeris data / information) of at least one NTN node / payload, and / or one or more common delay / TA parameters (e.g., at least one common TA / delay parameter) and / or a reference location (e.g., referenceLocation) and / or an antenna polarization mode (e.g., vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization). The base station may communicate with the wireless device via at least one NTN node / payload (e.g., via at least one service link).

[0283] like Fig. 20As shown, a first NTN-specific configuration parameter among the multiple NTN-specific configuration parameters (or one or more NTN configuration parameters) may correspond to a first serving cell among the one or more serving cells (e.g., NTN-Config-r17 IE of the NTN-specific SIB). For example, the one or more NTN configuration parameters may include one or more second NTN-specific configuration parameters corresponding to one or more NTN neighboring cells (e.g., NTN-Config-r17 IE in the ntn-NeighCellConfigList IE of the NTN-specific SIB). For example, the NTN neighboring cell among the one or more NTN neighboring cells may be one of the one or more serving cells. In another example, the NTN neighboring cell among the one or more NTN neighboring cells may not be one of the one or more serving cells (e.g., may be a non-serving cell). In some examples, such as Fig. 20 As shown, an NTN neighbor cell in the one or more NTN neighbor cells may correspond to a physical cell ID (eg, PhysCellId) and / or a carrier frequency.

[0284] In some examples, a cell in the one or more cells may be a (first) serving cell or a cell in one or more NTN neighboring cells. For example, a cell may include one or more NTN nodes and / or one or more service links (e.g., for communicating with a wireless device). For example, a cell (e.g., a serving cell) may include one or more second cells (e.g., each of the one or more second cells may correspond to each of the one or more service links or one or more NTN nodes).

[0285] In some examples, the NTN node may be (only) a transmission point (TP) for transmitting a DL positioning reference (DL-PRS) signal. For example, the NTN node may not be associated with a cell in one or more cells or a serving link in at least one serving link. For example, the NTN node may be (only) used to receive a UL SRS signal (e.g., from a wireless device).

[0286] In some examples, the NTN node may be a reception point (RP) for performing a positioning procedure. The NTN node may include a set of geographically collocated antennas (e.g., antennas including only UL-SRS RPs or only SRS RPs). For example, the NTN node may correspond to a cell in one or more cells.

[0287] For example, an NTN-specific configuration parameter among multiple NTN-specific configuration parameters (e.g., a first NTN-specific configuration parameter or a second NTN-specific configuration parameter among one or more second NTN-specific configuration parameters) may include one or more corresponding ephemeris parameters (e.g., corresponding satellite ephemeris data, e.g., ephemerisInfo) and / or one or more corresponding common delay / TA parameters (e.g., ta-Info) and / or one or more corresponding antenna polarization modes (e.g., vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization) for UL / DL communication on a corresponding service link (or corresponding service cell).

[0288] In some cases, a serving cell corresponding to an NTN-specific configuration parameter in the plurality of NTN-specific configuration parameters may include a single NTN node / payload. One or more corresponding ephemeris parameters (e.g., corresponding satellite ephemeris data, e.g., ephemerisInfo) and / or one or more corresponding common delay / TA parameters (e.g., ta-Info) and / or one or more corresponding antenna polarization modes (e.g., vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization) may correspond to a serving link corresponding to a single NTN node.

[0289] In some other cases, a service cell corresponding to an NTN-specific configuration parameter in the plurality of NTN-specific configuration parameters may include one or more NTN nodes / payloads. One or more corresponding ephemeris parameters (e.g., corresponding satellite ephemeris data, e.g., ephemerisInfo) and / or one or more corresponding common delay / TA parameters (e.g., ta-Info) and / or one or more corresponding antenna polarization modes (e.g., vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization) may, for example, correspond to one or more service links corresponding to the one or more NTN nodes / payloads.

[0290] For example, the wireless device may determine at least one common TA / delay using / based on one or more common TA parameters in a plurality of NTN-specific configuration parameters. Each common TA / delay in at least one common TA / delay may correspond to a TAG and / or a serving cell in one or more serving cells, and / or an NTN node in one or more NTN nodes. At least one common TA / delay may correspond to one or more TAGs (e.g., a primary TAG or a secondary TAG). The common TA / delay in at least one common TA / delay may correspond to a serving cell (e.g., one or more serving cells) and / or a non-serving cell (e.g., one or more non-serving cells). In some examples, the common TA / delay in at least one common TA / delay may correspond to a feeder link of a serving cell or a feeder link of a non-serving cell. The wireless device may determine the common TA / delay in at least one common TA / delay based on one or more common TA parameters in corresponding NTN-specific configuration parameters in a plurality of NTN-specific configuration parameters.

[0291] For example, the wireless device may use / determine at least one service link delay based on one or more ephemeris parameters in a plurality of NTN-specific configuration parameters. Each service link delay in at least one service link delay may correspond to a TAG and / or a service cell in one or more service cells, and / or an NTN node in one or more NTN nodes. At least one service link delay may correspond to one or more TAGs (e.g., a primary TAG or a secondary TAG). The common TA / delay in at least one service link delay may correspond to a service cell (e.g., one or more service cells) and / or a non-service cell (e.g., one or more non-service cells). In some examples, the service link delay in at least one service link delay may correspond to a service link of a service cell or a service link of a non-service cell. The wireless device may determine the service link delay in at least one service link delay based on one or more ephemeris parameters in a corresponding NTN-specific configuration parameter in a plurality of NTN-specific configuration parameters.

[0292] For example, the wireless device may determine at least one open-loop TA using / based on multiple NTN-specific configuration parameters (e.g., each open-loop TA in the at least one open-loop TA may correspond to a TAG in one or more serving cells or a serving cell and / or an NTN node in one or more NTN nodes). At least one open-loop TA may correspond to one or more TAGs (e.g., a primary TAG or a secondary TAG). The open-loop TAs in the at least one open-loop TA may correspond to a serving cell (e.g., one or more serving cells) and / or a non-serving cell (e.g., one or more non-serving cells). In some examples, the open-loop TAs in the at least one open-loop TA may correspond to an NTN node in the at least one NTN node. The wireless device may determine the open-loop TA in the at least one open-loop TA based on the corresponding common TA / delay and / or the corresponding serving link delay. For example, the wireless device may determine the corresponding UE-gNB RTT corresponding to the open-loop TA in the at least one open-loop TA.

[0293] For example, the wireless device may determine / maintain / calculate at least one TA value using / based on at least one open-loop TA and / or one or more TAC MAC CEs (e.g., each TA value in the at least one TA value may correspond to a TAG or a service cell in one or more service cells). One or more TAC MAC CEs may be received by the wireless device from one or more service cells or the service cell or at least one service cell. For example, the first (or each) TAC MAC CE in the one or more TAC MAC CEs may contain a first TA repair / correction / update (or a first TA value) and at least one first index / ID. The at least one first index / ID may be one of the following: a first TAG ID, and / or a first cell ID, and / or a first beam ID, and / or a first NTN node ID / index, etc. Based on receiving the first TAC MAC CE in the one or more TAC MAC CEs, the wireless device may calculate / maintain / update / determine a TA value in the at least one TA value corresponding to the indicated at least one first TAG ID. At least one TA value may correspond to one or more TAGs (e.g., a primary TAG or a secondary TAG). The TA value in the at least one TA value may correspond to a serving cell (e.g., one or more serving cells) and / or a non-serving cell (e.g., one or more non-serving cells). In some examples, the TA value in the at least one TA value may correspond to an NTN node in the at least one NTN node.

[0294] For example, the wireless device may determine at least one UE-gNB RTT using / based on multiple NTN-specific configuration parameters (e.g., each UE-gNB RTT in the at least one UE-gNB RTT may correspond to a TAG or a serving cell in one or more serving cells). At least one UE-gNB RTT may correspond to one or more TAGs (e.g., a primary TAG or a secondary TAG). The UE-gNB RTTs in the at least one UE-gNB RTT may correspond to a serving cell (e.g., one or more serving cells) and / or a non-serving cell (e.g., one or more non-serving cells). In some examples, the UE-gNB RTT of the at least one UE-gNB RTT may correspond to an NTN node in the at least one NTN node. The wireless device may determine the UE-gNB RTT in the at least one UE-gNB RTT based on a corresponding open-loop TA (a corresponding TA value) and / or a corresponding MAC layer timing offset (e.g., K-Mac). In some examples, the wireless device may determine a UE-gNB RTT in at least one UE-gNB RTT based on (e.g., by summing) a corresponding open-loop TA value (or corresponding TA value) in at least one open-loop TA value (e.g., in ms / time slot / symbol / subframe) and a corresponding MAC layer timing offset (e.g., K-Mac) (e.g., in ms / time slot / symbol / subframe).

[0295] In the example, Fig. 20 As shown, each of the multiple NTN-specific configuration parameters may include a MAC layer timing offset (e.g., K-Mac or Kmac), for example, corresponding to a feeder link and / or an NTN node and / or a serving cell and / or a non-serving cell, etc. For example, one or more NTN configuration parameters may indicate one or more MAC layer timing offsets corresponding to one or more feeder links and / or one or more serving cells. For example, one or more NTN configuration parameters may indicate a first MAC layer timing offset in one or more MAC layer timing offsets corresponding to a primary TAG. In some examples, one or more NTN configuration parameters may indicate a second MAC layer timing offset in one or more MAC layer timing offsets corresponding to a secondary TAG.

[0296] For example, one or more NTN configuration parameters may indicate a first MAC layer timing offset in one or more MAC layer timing offsets corresponding to a primary TAG or a first cell group (e.g., MSG). In some examples, one or more NTN configuration parameters may indicate a second MAC layer timing offset in one or more MAC layer timing offsets corresponding to a secondary TAG and / or a second cell group (e.g., SCG).

[0297] In an example, each of the plurality of NTN specific configuration parameters may include a cell-specific timing offset (e.g., CellSpecific_K_offset), e.g., corresponding to a serving cell or a TAG of a serving cell or a serving link or an NTN node of a serving cell, etc. For example, one or more NTN configuration parameters may indicate one or more (or at least one) cell-specific timing offsets corresponding to one or more serving links and / or one or more NTN nodes / payloads and / or one or more cells (e.g., one or more serving cells).

[0298] For example, one or more NTN configuration parameters may indicate a first cell-specific timing offset among one or more cell-specific timing offsets corresponding to a primary TAG or a first cell group (e.g., MSG). In some examples, one or more NTN configuration parameters may indicate a second cell-specific timing offset among one or more cell-specific timing offsets corresponding to a secondary TAG and / or a second cell group (e.g., SCG).

[0299] For example, the wireless device may use one or more NTN configuration parameters to determine / measure / calculate / maintain / update / estimate at least one open-loop TA value and / or at least one common TA / delay and / or at least one serving link delay and / or at least one UE-gNB RTT and / or at least one TA value of the wireless device. In some cases, each TA value of the at least one TA value (and / or each open-loop TA value of the at least one open-loop TA value, and / or each cell-specific timing offset of the at least one cell-specific timing offset, and / or each MAC layer timing offset of the at least one MAC layer timing offset) may correspond to a serving cell and / or a serving link and / or a TAG and / or an NTN node and / or a feeder link, etc.

[0300] In some other cases, the wireless device may determine / measure / maintain one or more NTN specific parameters / values ​​based on one or more NTN configuration parameters. In some embodiments, one or more NTN specific parameters / values ​​(and / or one or more NTN configuration parameters) may include the type of NTN payload corresponding to at least one serving cell (e.g., GEO satellite, MEO satellite, LEO satellite and / or HAPS). In some embodiments, one or more NTN specific parameters / values ​​(and / or one or more NTN configuration parameters) may include the type of cell / beam corresponding to at least one serving cell or one or more non-serving cells (e.g., earth-fixed cell / beam or earth-mobile cell / beam). In some cases, the wireless device may determine at least one location information (or positioning) of at least one NTN node / payload based on one or more NTN configuration parameters and / or one or more NTN specific parameters / values. For example, the wireless device may use one or more NTN configuration parameters (e.g., one or more ephemeris parameters and / or one or more common delay / TA parameters and / or referenceLocation) to calculate / determine / maintain / update at least one location information of at least one NTN node / payload (e.g., satellite).

[0301] The wireless device may maintain / acquire UL synchronization of one or more cells in response to acquiring / reacquiring NTN-specific SIBs and / or SIB1 (e.g., receiving one or more NTN configuration parameters). For example, the wireless device may determine whether UL synchronization of a first cell in the one or more cells and / or a second cell in the one or more cells is lost.

[0302] In some cases, in response to obtaining UL synchronization of a first cell in one or more cells (e.g., based on receiving one or more NTN configuration parameters or receiving one or more NTN configuration parameters corresponding to the first cell), the wireless device may determine that UL synchronization of a second cell in the one or more cells has been obtained / maintained. For example, in response to losing UL synchronization of a first cell in one or more cells, the wireless device may determine that UL synchronization of a second cell in the one or more cells has been lost. For example, the first cell may correspond to a primary TAG. In some cases, the first cell may be a cell in which the wireless device is receiving NTN-specific SIBs and / or SIB1. In some cases, the first cell may be a PCell, and / or a cell of an MSG. For example, the wireless device may determine that UL synchronization of the second cell has been lost based on expiration of a validity timer of the first cell. For example, the wireless device may determine that UL synchronization of the second cell has been obtained based on the validity timer of the first cell being running.

[0303] In some examples, the wireless device may acquire / maintain UL synchronization of the second cell independently of UL synchronization of the first cell. For example, the wireless device may determine that UL synchronization of the second cell is lost without responding to UL synchronization loss of the first cell. In another example, the wireless device may determine that UL synchronization of the second cell is acquired without responding to UL synchronization of the first cell being acquired. For example, the wireless device may determine that UL synchronization of the second cell is lost based on expiration of a validity timer of the second cell. For example, the wireless device may determine that UL synchronization of the second cell is acquired based on the validity timer of the second cell being running.

[0304] In an example, an NTN-specific configuration parameter in a plurality of NTN-specific configuration parameters may include a duration ntn-UlSyncValidityDuration and / or epochTime. In some cases, the wireless device may start / restart at least one validity timer / window / time period / duration (e.g., with a duration UlSyncValidityDuration) based on acquiring / reacquiring an NTN-specific SIB and / or SIB1 (e.g., receiving one or more NTN configuration parameters). A validity timer in at least one validity timer (e.g., a T430 timer) may correspond to a cell (e.g., a serving cell or an NTN neighboring cell) and / or a TAG (e.g., a primary TAG or a secondary TAG) in one or more cells and / or a serving link in at least one serving link and / or an NTN node or at least one NTN node and / or a cell group (e.g., a PCG or an SCG).

[0305] In an embodiment, for example, when in an RRC inactive / idle state, the wireless device may start / restart (each) validity timer (e.g., corresponding to a cell in one or more cells, such as a serving cell in one or more serving cells, and / or a TAG and / or a serving link in at least one serving link and / or a cell group and / or an NTN node in at least one NTN node) in response to receiving one or more NTN configuration parameters, such as NTN-specific configuration parameters corresponding to a cell (e.g., a serving cell) and / or a TAG and / or a serving link in at least one serving link and / or a cell group and / or an NTN node in at least one NTN node. For example, the wireless device may start / restart (e.g., the validity timer of the serving cell) with a duration ntn-UlSyncValidityDuration in the corresponding NTN-specific configuration parameter starting from the subframe indicated by the epochTime in the corresponding NTN-specific configuration parameter. In some scenarios, the wireless device may determine the epochTime based on the subframe and / or system information (SI) modification window and / or SFN in which the corresponding NTN-specific configuration parameter (and / or NTN-specific SIB or SIB1) is received / obtained. The wireless device may request (or attempt to reacquire) an NTN-specific SIB (e.g., SIB19) and / or SIB1 before expiration of a validity timer in at least one validity timer (e.g., before the end of a duration indicated by ntn-UlSyncValidityDuration of the NTN-specific configuration parameter of the corresponding serving cell).

[0306] In an example, in response to expiration of a validity timer in at least one validity timer (e.g., corresponding to a serving cell and / or a non-serving cell and / or a TAG and / or a serving link in at least one serving link and / or a cell group and / or an NTN node in at least one NTN node in one or more serving cells), the wireless device may determine a UL synchronization loss for each of the one or more serving cells (e.g., the wireless device may stop at least one validity timer if the at least one validity timer is running). For example, the wireless device (re)acquires the NTN-specific SIB and / or SIB1. For example, based on expiration of a validity timer corresponding to a cell in the one or more cells (e.g., a PCell, or a cell in a pTAG, or a cell in an MCG, or a PsCell), the wireless device may determine a UL synchronization loss for each of the one or more serving cells (e.g., the wireless device may stop at least one validity timer if the at least one validity timer is running).

[0307] In an example, in response to expiration of at least one validity timer (e.g., corresponding to a serving cell in the one or more serving cells), the wireless device may determine that UL synchronization of a serving cell in the one or more serving cells is lost. For example, the wireless device (re)acquires the NTN-specific SIB and / or SIB1.

[0308] In some other cases, corresponding to each open-loop TA value of the at least one TA value (or a TAG or a serving cell of the one or more serving cells), the wireless device may run / maintain / start / restart a validity timer / window / duration. In response to the expiration of the validity timer corresponding to the TAG or the serving cell, the wireless device may determine that UL synchronization of the corresponding serving cell (or each serving cell of the one or more serving cells or a corresponding non-serving cell) is lost. For example, the wireless device (re)acquires the NTN-specific SIB and / or SIB1, and / or the corresponding NTN-specific configuration parameters.

[0309] In some embodiments, the wireless device may transmit a UE capability message to the base station. The UE capability message may indicate the wireless device's ability to (simultaneously) maintain / estimate / update / measure / calculate at least one open-loop TA value (and / or at least one UE-gNB RTT) of the wireless device. In other embodiments, the UE capability message may indicate the wireless device's ability to maintain (e.g., run, start, restart) at least one validity timer corresponding to one or more serving cells (e.g., including a serving cell and one or more NTN neighbor cells). In other embodiments, the UE capability message may indicate the wireless device's ability to maintain (e.g., run, start, restart) a single validity timer corresponding to all serving cells (e.g., including a serving cell and one or more NTN neighbor cells).

[0310] For example, the UE capability message may indicate the ability of the wireless device to communicate with the base station simultaneously via at least one NTN node / payload and / or at least one service link (and / or at least one feeder link). For example, an NTN node in the at least one NTN node may correspond to a serving cell. In some other cases, an NTN node in the at least one NTN node may correspond to a non-serving cell. In some examples, at least one NTN node may correspond to a different serving cell.

[0311] like Fig. 20As shown, one (or each) of the multiple NTN-specific configuration parameters may include at least one (antenna) polarization mode / information. For example, at least one antenna polarization mode of the NTN-specific configuration parameter may include at least one DL antenna polarization mode (e.g., ntn-PolarizationDL), which indicates one or more polarization information / modes of DL transmission (e.g., PDCCH / PDSCH / SSB transmission) on the corresponding service link (e.g., the service link of the service cell corresponding to the NTN-specific configuration parameter). In another example, at least one antenna polarization mode may include at least UL antenna polarization mode / information (e.g., ntn-PolarizationUL), which indicates one or more polarization information / modes of UL transmission (e.g., PUSCH / PUCCH / PRACH / SRS transmission) on the service link (e.g., the service link of the service cell corresponding to the NTN-specific configuration parameter).

[0312] In an example, the antenna polarization pattern of the NTN node / payload of the serving cell (or non-serving cell) can be based on at least one antenna polarization pattern of the NTN specific configuration parameter. For example, the antenna polarization pattern of the NTN node / payload can correspond to the DL antenna polarization pattern on the corresponding serving link (e.g., for DL ​​transmission) or the UL antenna polarization pattern on the corresponding serving link (e.g., for UL transmission). In some cases, at least the UL antenna polarization pattern of the NTN node / payload of the serving cell (or non-serving cell) can be the same as at least the DL antenna polarization pattern of the NTN node / payload of the serving cell (or non-serving cell).

[0313] For example, the positioning procedure (or operation) may include a positioning measurement procedure, and / or a positioning measurement gap activation / deactivation procedure, and / or a position measurement indication, and / or a positioning measurement gap activation / deactivation request. The wireless device may perform a positioning procedure (or operation) for at least one serving cell and / or at least one non-serving cell among one or more serving cells. For example, the wireless device may perform a positioning procedure for / corresponding to a serving link corresponding to a serving cell or a non-serving cell. In some cases, the wireless device may perform a positioning procedure for / corresponding to an NTN node (of at least one NTN node) corresponding to a serving cell or a non-serving cell. In some other cases, the wireless device may perform a positioning procedure for / corresponding to a serving link (of at least one serving link) corresponding to a serving cell or a non-serving cell.

[0314] For example, one or more configuration parameters may include one or more positioning RS (PRS) configuration parameters. One or more PRS configuration parameters may configure the wireless device with one or more DL PRS resource sets (e.g., via NR-DL-PRS-ResourceSet and NR-DL-PRS-Resource). Each DL PRS resource set in one or more DL PRS resource sets may include a number (K>1) of DL PRS resources. One or more PRS configuration parameters (e.g., via NR-DL-PRS-Positioning FrequencyLayer, NR-DL-PRS-ResourceSet, and NR-DL-PRS-Resource) may configure each DL PRS resource set in one or more DL PRS resource sets. In some examples, one or more PRS configuration parameters may configure the wireless device with one or more DL PRS positioning frequency layer configurations (e.g., via NR-DL-PRS-PositioningFrequencyLayer).

[0315] A DL PRS resource set in one or more DL PRS resource sets (eg, configured by NR-DL-PRS-ResourceSet) may include one or more DL PRS resources. In an example, the one or more DL PRS resources may include at least one of the following: nr-DL-PRS-ResourceSetID (e.g., indicating the identity of the DL PRS resource set); dl-PRS-Periodicity-and-ResourceSetSlotOffset (e.g., indicating the number of times a DL-PRS resource is repeated for a single instance of a DL-PRS resource set); dl-PRS-ResourceRepetitionFactor; dl-PRS-ResourceTimeGap (e.g., indicating an offset in the number of time slots between two repeated instances of a DL PRS resource with the same nr-DL-PRS-ResourceID within a single instance of a DL PRS resource set); dl-PRS-MutingOption1 and dl-PRS-MutingOption2; NR-DL-PRS-SFN0-Offset; dl-PRS-ResourceList (e.g., indicating one or more DL PRS resources included in a DL PRS resource set); dl-PRS-ResourceSlotOffset; dl-PRS-ResourceSybolOffset; and / or dl-PRS-QCL-Info. For example, the wireless device may (uniquely) identify / determine one DL PRS resource in one or more DL PRS resource sets based on at least one of the following: dl-PRS-ID; nr-DL-PRS-ResourceSetID; and / or nr-DL-PRS-ResourceID-r16. In some cases, the wireless device may determine a DL PRS to transmit from a serving cell or a non-serving cell, for example based on one or more configuration parameters (e.g., at least one of dl-PRS-ID, nr-PhysCellID, nr-CellGlobalID, and / or nr-ARFCN).For example, to perform a positioning measurement procedure (e.g., a positioning procedure), one or more configuration parameters (e.g., nr-DL-PRS-ReferenceInfo) may indicate that the wireless device may use one or more DL PRS resources as a reference for DL ​​RSTD, DL PRS-RSRP, and / or UE Rx-Tx time difference measurement. The reference (e.g., provided by nr-DL-PRS-ReferenceInfo) may include a dl-PRS-ID, a DL PRS resource set ID, and optionally a single DL PRS resource ID or a list of DL PRS resource IDs.

[0316] In some cases, one or more DL PRS resource sets (e.g., configured by NR-DL-PRS-ResourceSet) may be referred to as pre-configured assistance data or DL-PRS assistance data during an (ongoing) LPP positioning session. For example, a base station may send / transmit DL-PRS assistance data (e.g., one or more PRS configuration parameters) before or during an ongoing LPP positioning session.

[0317] In some embodiments, one or more DL PRS resource sets (e.g., of a cell, such as a serving cell or a non-serving cell) may correspond to at least one antenna polarization mode (e.g., at least one DL antenna polarization mode), such as vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization. For example, at least one polarization mode may include an antenna polarization mode of a wireless device, and / or an antenna polarization mode of an NTN node / payload. In some examples, a DL PRS resource set may include an indication of at least one antenna polarization mode (e.g., vertical horizontal polarization, right-hand circular polarization, or left-hand circular polarization). For example, as Fig. 20 As shown, the positioning procedure may be based on at least one polarization pattern (eg, corresponding to a DLPRS resource set).

[0318] In some embodiments, the positioning procedure may be based on multiple NTN nodes / payloads (e.g., multiple satellites and / or corresponding to at least one serving link), for example, including NTN payloads / nodes corresponding to one or more serving cells and / or one or more non-serving cells.

[0319] In some other embodiments, the positioning procedure may be based on multiple time point measurements of a single NTN node / payload (e.g., satellite) corresponding to a serving cell or a non-serving cell in one or more serving cells. For example, each time point measurement in the multiple time point measurements (e.g., during a (positioning) measurement gap opportunity) is associated with a position / positioning (and / or attributes / characteristics / features of a serving link) of / corresponding to a single NTN node.

[0320] In some embodiments, the attribute of the serving link (e.g., a serving link in at least one serving link and / or a serving link corresponding to a serving cell or NTN node) may be at least one of the one or more attributes of the serving link. For example, one of the one or more attributes of the serving link may include (or may be) at least one of the following: a UE-gNB RTT corresponding to the serving link (e.g., a UE-gNB RTT of a serving cell in one or more serving cells); a propagation delay of the serving link; and / or a length of the serving link (e.g., a distance between the wireless device and the NTN payload, or a relative position / positioning of the NTN node / payload with respect to the position / positioning of the wireless device, and / or a distance between the wireless device and a reference position); and / or an elevation angle of the serving link; and the like. For example, the one or more attributes of the serving link may be based on (or dependent on) a GNSS acquisition position (or position information) of the wireless device.

[0321] In some examples, the service link may include one or more intermediate nodes (e.g., an aircraft and / or an unmanned aerial vehicle (UAV) and / or a HAPS node / payload and / or a low-orbit satellite). For example, using one or more NTN configuration parameters corresponding to a serving cell, the wireless device may determine one or more attributes of a service link of / corresponding to a serving cell or NTN node.

[0322] In some other embodiments, one or more attributes of the service link may be based on one or more timestamps (e.g., timestamps of one or more NTN configuration parameters and / or timestamps of NTN-specific SIBs) and / or epoch times (e.g., epoch times of NTN-specific SIBs or epoch times of SIBx, where x=1, 2, ...). For example, determining at least one location information / positioning of the NTN node in at least one NTN node may be based on one or more timestamps.

[0323] In an embodiment, based on performing a positioning procedure, the wireless device may measure and report a first number of DL RSTD measurements (e.g., 4 DL RSTD measurements), for example, based on a dl-PRS-ID (e.g., a UE-specific TRP ID corresponding to one or more PRS configuration parameters) and / or based on a DL antenna polarization mode. In some cases, each measurement in the first number of DL RSTD measurements may be between different DL PRS resource pairs (or DL ​​PRS resource sets), for example, each DL PRS resource may be associated with (or identified by) a dl-PRS-ID and / or a DL antenna polarization mode. In an example embodiment, the first number of DL RSTD measurements (e.g., based on the same pair of dl-PRS-IDs) may use one or more reference timings (e.g., corresponding to measurements at multiple time points). The wireless device may transmit the report to the base station. In some examples, each measurement in the first number of DL RSTD measurements may correspond to an antenna polarization mode of the wireless device and / or NTN node (e.g., for DL ​​or UL communication of a service link in at least one service link).

[0324] In an example, the one or more measurement configuration parameters may include one or more positioning measurement gaps (e.g., configured via PosGapConfig and / or GapConfig). For example, the wireless device may perform one or more location-related measurements based on (or using or during) the one or more positioning measurement gaps. In some cases, the positioning measurement gaps in the one or more positioning measurement gaps may be per-UE measurement gaps (e.g., gapType is perUE). In some other cases, the positioning measurement gaps in the one or more positioning measurement gaps may be per-RF (e.g., per-RF1 or per-RF2) measurement gaps (e.g., gapType is perRF1 / perRF2).

[0325] In an example embodiment, a positioning measurement gap in the one or more positioning measurement gaps may correspond to a DL antenna polarization pattern in at least one DL antenna polarization pattern (eg, on a serving link corresponding to a cell, eg, the cell is a serving cell or a non-serving cell).

[0326] In some scenarios, to perform a positioning procedure, the wireless device may set / configure a positioning measurement gap in a measurement gap (e.g., one or more positioning measurement gaps), for example, based on: a measurement gap length (in ms) of the positioning measurement gap; and / or a measurement gap repetition period (in ms) of the positioning measurement gap; and / or a gap offset (e.g., gapOffset) of the positioning measurement gap; and / or one or more NTN configuration parameters corresponding to a cell such as a serving cell or a non-serving cell, for example. For example, the wireless device may set / configure a positioning measurement gap in a measurement gap (e.g., one or more positioning measurement gaps) based on NTN configuration parameters corresponding to the cell (e.g., physical cell ID, epoch time, SFN, polarization mode / information, etc.). In an example, to set / configure a positioning measurement gap in a measurement gap (e.g., one or more positioning measurement gaps), the wireless device may determine that at least one of the following items is satisfied: gapFR1 is set to setup, and / or gapFR2 is set to setup, and / or gapUE is set to setup. Based on (or using) the measurement gap (e.g., gapOffset of the positioning measurement gap), the wireless device may identify / determine a timing (e.g., DL timing / symbol / time slot / frame / subframe and / or timer instance) at which the positioning measurement gap may start / occur, for example, based on determining, for example, the SFN and the (DL frame / configured) subframe corresponding to the cell (e.g., the first / starting / earliest / initial subframe of the measurement gap). For example, the wireless device may apply the measurement gap TA (e.g., mgta) of the positioning measurement gap, for example, based on the open-loop TA (and / or UE-gNB RTT) corresponding to the serving cell (or non-serving cell) or TAG. In some scenarios, the wireless device may start performing one or more location-related measurements, the measurement gap TA (e.g., mgta), before the first / starting / earliest / initial subframe of the positioning measurement gap (e.g., before the occurrence of the positioning measurement gap or the subframe where the positioning measurement gap starts / occurs, for example, based on at least one DL antenna polarization pattern and / or the antenna polarization pattern corresponding to the positioning measurement gap.

[0327] In some embodiments, the wireless device may configure / determine reference signal (RS) measurement timing (e.g., positioning RS (PRS)). In an example, the wireless device may set / identify the first / starting / initial / earliest SS / PBCH block measurement timing configuration (SMTC) based on a periodicityAndOffset parameter (providing Periodicity and Offset values) in one or more measurement configuration parameters (e.g., in an smtc1 configuration and / or an smtc2 configuration and / or an smtc3 configuration and / or an smtc4 configuration, etc.). In some cases, the wireless device may set / determine / configure the measurement gap based on a periodicity parameter in an smtc (i.e., not smtc1, such as smtc2 and / or smtc3 and / or smtc4) configuration. For example, the wireless device may set / determine / configure the measurement gap based on an Offset (derived / determined based on a parameter periodicityAndOffset of a corresponding smtc configuration) and / or a duration parameter from an smtc1 configuration. In some other cases, the wireless device may set / determine the RSSI measurement timing configuration (RMTC) based on one or more measurement configuration parameters (e.g., rmtc-Periodicity and / or rmtc-SubframeOffset).

[0328] The wireless device (e.g., in RRC_CONNECTED state) may maintain a measurement object list of measurement objects, a reporting configuration list of reporting configurations, and a measurement identity list of measurement identities. The measurement object list may, for example, include at least one of the following: an NR measurement object, a CLI measurement object, an inter-RAT object, and / or an L2 U2N relay object. The reporting configuration list may, for example, include at least one of the following: an NR, an inter-RAT, and / or an L2 U2N relay reporting configuration. In some embodiments, for NR measurement objects, the wireless device may measure and report on serving cells (of one or more serving cells) and / or detected cells (e.g., cells that are not listed in the measurement object but detected by the wireless device based on the SSB frequency and subcarrier spacing indicated by the measurement object) and / or listed cells (e.g., indicated by the measurement object and / or one or more NTN configuration parameters).

[0329] For example, to perform a positioning procedure, the wireless device may perform (positioning) measurements, such as one or more measurements (e.g., one or more location-related measurements) corresponding to at least one cell (e.g., a serving cell and / or a non-serving cell). In some cases, the wireless device may perform the measurements by measuring one or more beams of a cell in at least one cell (e.g., a serving cell). In some examples, the wireless device may apply layer 3 filtering to perform the measurements, such as when measurements are not performed for RSSI and / or CLI measurements. In some cases, the measurements may be based on an antenna polarization pattern of a wireless device and / or an NTN node corresponding to a cell in at least one cell (e.g., on a DL / UL serving link of the cell).

[0330] In an example, corresponding to at least one serving cell and / or non-serving cell (e.g., serving cell and / or one or more NTN neighboring cells), the positioning procedure can be used to verify the location information / positioning of the wireless device (e.g., network-verified UE location) and / or the location information / positioning of the NTN node / payload (e.g., satellite) and / or the location information / positioning of the base station. In some aspects, the positioning procedure can be based on at least one of the following: enhanced cell identification (E-CID) method / procedure, downlink arrival time difference (DL-TDOA) method / procedure, downlink departure angle (DL-AoD) method / procedure, multi-round trip time (Multi-RTT) method / procedure, uplink arrival time difference (UL-TDOA) method / procedure and / or uplink arrival angle (UL-AoA) method / procedure, and / or AI / ML-based positioning procedure. The positioning procedure can be based on the UE positioning function of NG-RAN, which provides a mechanism to support or assist in calculating the geographical location of the wireless device. For example, the positioning knowledge of the wireless device can be used to support radio resource management functions, location-based services for operators, subscribers and third-party service providers, for example.

[0331] In some aspects, the wireless device may perform a positioning procedure by executing / performing / conducting, for example, one or more location-related measurements corresponding to at least one cell and / or at least one NTN node. For example, the one or more location-related measurements may be for / for one or more radio access technologies (RATs), such as E-UTRA (eutra-RSTD) and / or NR (nr-RSTD, nr-UE-RxTxTimeDiff, nr-PRS-RSRP) and / or NTN segments, etc. (e.g., 6G).

[0332] The positioning procedure may include one or more location-related measurements, for example, corresponding to at least one NTN node and / or at least one serving cell and / or at least one serving link (e.g., corresponding to the same serving cell). For example, the wireless device may perform one or more location-related measurements based on (or by using or via) one or more positioning measurement gaps and performing the positioning procedure. In some embodiments, one or more configuration parameters (e.g., via LPP) may configure the wireless device to measure any RTD, PRS-RSRP, and PRS of UE Rx-Tx time difference measurements, for example, to perform one or more location-related measurements. For example, one or more location-related measurements may include NR positioning measurements (e.g., RSTD, PRS-RSRP, UE Rx-Tx time difference, NR E-CID, and PRS-RSRPP measurements). One or more location-related measurements may correspond to one or more RATs. In some cases, one or more location-related measurements may be based on gap-based (e.g., using one or more positioning measurement gaps) measurements and / or gapless measurements.

[0333] The wireless device may measure at least one PRS resource in a DL PRS resource set (of one or more DL PRS resource sets) during a positioning measurement gap. In some examples, at least one PRS resource in a DL PRS resource set may correspond to, for example, at least one antenna polarization pattern of a wireless device and / or an NTN node / payload corresponding to a cell (e.g., a serving cell or a non-serving cell). For example, the wireless device may measure at least one PRS resource in a DL PRS resource set (of one or more DL PRS resource sets) that completely or partially overlaps with a positioning measurement gap (opportunity). Based on all (or some) instances of a PRS resource overlapping with a positioning measurement gap, at least one (DL) PRS resource may completely (or partially) overlap with a positioning measurement gap. The wireless device may (uniquely) identify / determine a (DL) PRS based on at least one of the following: dl-PRS-ID, nr-DL-PRS-ResourceSetID, and / or nr-DL-PRS-ResourceID-r16, and / or a physical cell ID of a cell corresponding to a serving NTN node or a serving link. For example, the wireless device may determine (by the base station) to transmit at least one DL PRS (resource) from / via a serving cell (of one or more serving cells) and / or via an NTN node corresponding to a serving link. In some cases, the serving cell may be the same as the serving cell defined / identified / determined by the SS / PBCH block (e.g., the DL PRS and the SS / PBCH block are transmitted from the same serving cell). In some other cases, the DL PRS may be transmitted (by the base station) from a non-serving cell. In some cases, the DL PRS may be transmitted (by the base station) from a serving cell (or non-serving cell) via at least one NTN node and / or via at least one serving link.

[0334] Fig.21 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown. In some scenarios, Fig.21 An example embodiment of a procedure for requesting activation / deactivation of positioning measurement gaps (eg, at a base station and / or a wireless device) is described. Fig.21 An example of a location measurement indication procedure (e.g., for requesting activation / deactivation of a positioning measurement gap) in an RRC connected state / mode (e.g., RRC_CONNECTED state) and / or in an RRC non-connected state / mode (e.g., RRC_INACTIVE / IDLE state or RRC_IDLE state) may be shown. In some embodiments, Fig.21An embodiment of a method (or process) for a positioning procedure may be shown. Through / via / based on a location measurement indication procedure, a wireless device may indicate (or inform / notify) a base station (or network), for example, via a cell (e.g., a serving cell or a non-serving cell) that the wireless device is starting (e.g., by requesting a positioning measurement gap activation) one or more location-related measurements or stopping (e.g., by requesting a positioning measurement gap deactivation) one or more location-related measurements. For example, a positioning procedure may include one or more location-related measurements corresponding to at least one NTN node and / or at least one serving cell and / or at least one serving link (e.g., corresponding to the same serving cell).

[0335] The base station may communicate with the wireless device via / using one or more cells (e.g., one or more serving cells / serving cells). For example, the wireless device may be in an RRC_IDLE (or RRC idle) state / mode, and / or an RRC_INACTIVE / IDLE (or RRC inactive / idle) state / mode, or an RRC_CONNECTED (or RRC connected) state / mode. For example, the wireless device may be in an RRC non-connected state / mode (e.g., an RRC inactive / idle state / mode, or an RRC idle state / mode). The wireless device may communicate with the base station, for example, via a non-terrestrial network (NTN), for example, the wireless device and the base station may operate in the NTN and / or the base station may be an NTN base station and / or the cell (e.g., a serving cell in one or more serving cells) may be part of the NTN. For example, the cell may be a serving cell or a non-serving cell.

[0336] like Fig.21As shown, the wireless device may receive one or more configuration parameters (e.g., one or more RRC configuration parameters) from a base station. The one or more configuration parameters may, for example, include one or more serving cell (e.g., one or more serving cells or one or more cells) configuration parameters (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB and / or ServingCell Config) for configuring one or more cells (e.g., one or more serving cells). In some examples, the one or more configuration parameters may include one or more NTN configuration parameters. For example, one or more cells may include a master / primary cell group (MSG) and / or a secondary cell group (SCG). In some cases, a cell in one or more cells may be a primary / secondary cell (PSCell), or a primary cell (PCell) or a secondary cell (SCell), or a special cell (SpCell). In some other cases, a cell in one or more cells may belong to a first cell group corresponding to a primary TAG (pTAG) or a second cell group corresponding to a secondary TAG (sTAG). For example, one or more configuration parameters may configure the wireless device for multi-cell communication and / or carrier aggregation.

[0337] like Fig.21 As shown, the one or more configuration parameters may include one or more NTN configuration parameters. For example, the wireless device may receive one or more NTN configuration parameters by acquiring SIB1 and / or NTN-specific SIBs (e.g., SIB19). The one or more configuration parameters may, for example, include one or more positioning RS (PRS) configuration parameters. One or more configuration parameters (e.g., using / via RRCReconfiguration or RRCResume) may include one or more measurement configuration parameters (e.g., MeasConfig). In an example, one or more measurement configuration parameters may configure the wireless device to, for example, perform measurements (e.g., one or more location-related measurements and / or perform positioning measurement procedures) on at least one serving cell (e.g., a serving cell) or on at least one non-serving cell.

[0338] In an example, the wireless device may receive a message (e.g., NR-DL-TDOA-RequestLocationInformation message and / or NR-DL-AoD-ProvideAssistanceData message and / or nr-Multi-RTT-Request LocationInformation message and / or nr-ECID-RequestLocationInformation message) from a location management function (LMF) (e.g., via the LTE positioning protocol (LPP)). The base station may transmit the message to the wireless device, for example, via a DL signal (e.g., PDSCH or PDCCH). In some cases, the message may be an RRC message. In some other cases, the message may be a MAC CE. The message may request the wireless device to measure and / or report (one or more) measurements (e.g., PRS-RSRP, DL reference signal time difference (RSTD), PRS-RSRPP, and / or one or more UE Rx-Tx time differences), for example, for at least one cell. In some cases, for enhanced cell identification (E-CID) (e.g., NR E-CID) positioning, the wireless device may report at least one of the following: SS-RSRP, SS-RSRQ, CSI-RSRP, and CSI-RSRQ. For example, the (requested) report (e.g., based on receiving a message) may be based on an antenna polarization pattern of the wireless device and / or NTN node corresponding to a cell in at least one cell (e.g., on a DL / UL serving link of the cell).

[0339] The wireless device may initiate / start performing measurements (e.g., location measurements, such as location-related measurements in one or more location-related measurements) based on an indication for initiating measurements. For example, the RRC or MAC layer of the wireless device may receive an indication for initiating measurements from a higher layer of the wireless device (e.g., a layer above the RRC layer). For example, the indication for initiating measurements may be in response to, for example, receiving a message from the LMF at the RRC layer (or MAC layer) or a higher layer (e.g., a layer above the RRC layer) of the wireless device (e.g., via LPP). In some cases, the indication for initiating measurements may be in response to starting an LPP positioning session (e.g., at the wireless device and / or base station). In some examples, the wireless device may receive an indication for initiating measurements during an ongoing LPP positioning procedure.

[0340] In some other examples, the wireless device may initiate / start / trigger a location measurement indication procedure (e.g., after successful AS security activation and in response to (or based on) an indication to initiate measurement). In an example embodiment, the wireless device may determine that UL synchronization of a cell (e.g., a serving cell or a non-serving cell) is maintained / acquired (e.g., a validity timer corresponding to the cell is running).

[0341] In response to a UL synchronization loss of a cell (e.g., a serving cell or a non-serving cell) (e.g., a validity timer corresponding to the cell is lost), the wireless device may not initiate / start / trigger (or avoid / bypass initiation / bypass starting / bypass triggering) a location measurement indication procedure. For example, before initiating / starting / triggering the location measurement indication procedure, the wireless device may (re)acquire, for example, NTN configuration parameters (e.g., NTN-specific SIB or SIB1) corresponding to the cell.

[0342] By / via / based on the location measurement indication procedure, the wireless device may indicate (or inform / notify) to the base station (or network), for example, via a cell (e.g., a serving cell or a non-serving cell), that the wireless device is starting (e.g., by requesting a positioning measurement gap activation or a positioning measurement gap activation request) one or more location-related measurements or stopping (e.g., by requesting a positioning measurement gap deactivation or a positioning measurement gap deactivation request) one or more location-related measurements. The wireless device may notify / inform the base station by transmitting a UL signal / message (e.g., MAC CE or RRC signaling) to the base station (e.g., via the cell). For example, the UL signal / message (e.g., for requesting the positioning measurement gap activation / deactivation) may include / indicate at least one of the one or more positioning measurement gaps. In some examples, the wireless device may determine to activate / deactivate at least one of the one or more positioning measurement gaps (e.g., determine to request the positioning measurement gap activation / deactivation), for example, within or during the initiated / started / triggered location measurement indication procedure.

[0343] The wireless device may trigger / initiate a procedure for positioning measurement gap request, for example, in response to (or based on receiving) an indication for initiating measurement (or after receiving an indication for initiating measurement) or in response to starting / initiating / triggering a location measurement indication procedure (or after starting / initiating / triggering a location measurement indication procedure). In some cases, the procedure for positioning measurement gap request may be used to (indicate / trigger / request) activate / deactivate at least one positioning measurement gap of one or more positioning measurement gaps. For example, the wireless device may indicate / trigger / request to activate / deactivate at least one positioning measurement gap of one or more positioning measurement gaps, for example, in response to (or based on) an indication for initiating measurement (or after receiving an indication for initiating measurement).

[0344] In some cases, the wireless device may determine that the (or at least one) measurement gap (e.g., for positioning) is sufficient for one or more location-related measurements. For example, a higher layer (e.g., RRC layer) of the wireless device may trigger a lower layer (e.g., MAC layer) of the wireless device to initiate a measurement gap activation request using UL MAC CE (e.g., transmitting a UL signal / message indicating a request for positioning measurement gap activation to a base station), e.g., corresponding to a positioning measurement gap activation request. In some other cases, the wireless device may trigger a lower layer (e.g., MAC layer) of the wireless device to initiate a measurement gap deactivation request using UL MAC CE (e.g., transmitting a UL signal / message indicating a request for positioning measurement gap deactivation to a base station), e.g., corresponding to a positioning measurement gap deactivation request.

[0345] In some cases, the wireless device may perform location-related measurements in one or more location-related measurements for / targeting one or more radio access technologies (RATs), such as for / targeting E-UTRA or NR. In some other scenarios, the wireless device may perform location-related measurements in one or more location-related measurements for starting subframe and slot timing detection for E-UTRA. In some examples, the wireless device may perform location measurements during a measurement gap or one (or at least one) of one or more positioning measurement gaps.

[0346] In some cases, in response to an indication for initiating measurements, the wireless device may determine that a positioning procedure is initiated / triggered as an indicate start (e.g., an indication start of one or more location-related measurements, or an indication start of a start of subframe and slot timing detection for E-UTRA). In some examples, the indication start may correspond to a RAT of one or more RATs. For example, the wireless device may determine that a positioning procedure is initiated / triggered for performing RSTD measurements for E-UTRA. In another example, the wireless device may determine that a positioning procedure is initiated / triggered for performing positioning measurements for NR. For example, the wireless device may determine that at least one measurement gap for performing a positioning procedure is insufficient.

[0347] In some cases, the base station may configure the wireless device to perform a positioning procedure / operation without maintaining UL synchronization with a cell (e.g., a serving cell or a non-serving cell). Regardless of whether the UL synchronization of the cell is lost and in response to an indication for initiating measurement, the wireless device may initiate / trigger the positioning procedure as an indicate start. In an example, the wireless device may initiate / trigger the positioning procedure as an indicate start when the UL synchronization of the cell is lost (e.g., the validity timer of the cell expires). In another example, the wireless device may initiate / trigger the positioning procedure as an indicate start when the UL synchronization of the cell is maintained (e.g., the validity timer of the cell is running).

[0348] In some other cases, the base station may configure the wireless device to perform a positioning procedure / operation when it is necessary to maintain UL synchronization with a cell (e.g., a serving cell or a non-serving cell). Based on the UL synchronization of the cell being obtained and in response to an indication for initiating measurement, the wireless device may initiate / trigger a positioning procedure as indicate start.

[0349] In order to perform a positioning procedure (e.g., according to or based on a positioning measurement procedure being initiated / triggered as an indicate start of one or more location-related measurements), the wireless device may perform at least one measurement (e.g., one or more measurements and / or one or more location-related measurements) in one (or activated) positioning measurement gap (e.g., a measurement gap or at least one measurement gap or one or more positioning measurement gaps). In some cases, the wireless device may set one or more contents / fields of the LocationMeasurementIndication message. Based on the (ongoing) positioning measurement procedure being initiated as an indicate start of one or more location-related measurements and / or one or more RATs, the wireless device may set the measurementIndication content / field of one or more contents in the LocationMeasurementIndication message. In some examples, the wireless device may set the measurementIndication content / field of one or more contents in the LocationMeasurementIndication message to eutra-RSTD (e.g., when the (ongoing) measurement procedure is initiated for positioning measurement for E-UTRA, and / or when the (ongoing) measurement procedure is initiated for RSTD measurement for E-UTRA) or nr-PRS-Measurement (e.g., when the ongoing measurement procedure is initiated for positioning measurement towards NR). In another example, the wireless device may set the measurementIndication content / field of one or more contents in the LocationMeasurementIndication message to the value eutra-FineTimingDetection (e.g., when the positioning measurement procedure is initiated as an indicate start for subframe and slot timing detection for E-UTRA). In some cases, the wireless device may submit the LocationMeasurementIndication message to a lower layer (e.g., MAC layer) of the wireless device for transmission. For example, the wireless device may transmit the LocationMeasurementIndication message.

[0350] In an example embodiment, for example, in response to an indication for initiating measurement, based on whether UL synchronization of a serving cell (or one or more serving cells) is lost (e.g., validity timers corresponding to the serving cell and / or TAG and / or a serving link in at least one serving link are running or not running), the wireless device may determine whether to request a base station (e.g., a network) to activate / deactivate a positioning measurement gap in one or more positioning measurement gaps (e.g., whether to trigger a positioning measurement gap request). In an example, based on the UL synchronization of the serving cell (or one or more serving cells) being obtained / maintained or not lost, for example, validity timers corresponding to the serving cell or TAG and / or the serving link are running, the wireless device may trigger a positioning measurement gap request (e.g., requesting a base station on, for example, a serving cell to activate / deactivate the positioning measurement gap). For example, based on one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG or the serving link) being invalid (e.g., validity timers corresponding to the serving cell or TAG or the serving link are running), the wireless device may not trigger a positioning measurement gap request (e.g., requesting a base station on, for example, a serving cell to activate / deactivate the positioning measurement gap). In some cases, the wireless device may determine that the time alignment timer (e.g., timeAlignmentTimer) of the TAG (or serving cell) is running. For example, requesting, for example, a base station on the serving cell to activate / deactivate the positioning measurement gap may be based on the identity / ID / index of the positioning measurement gap (e.g., the positioning MG ID of the positioning measurement gap activation / deactivation request MAC CE). For example, the positioning measurement gap may correspond to at least one DL antenna polarization pattern (e.g., on the serving link of the serving cell or the NTN node of the serving cell).

[0351] In an example embodiment, in response to determining that the time alignment timer (e.g., timeAlignmentTimer) of the TAG (or serving cell) stops / expired, the wireless device may not trigger a positioning measurement gap request (e.g., requesting a base station on the serving cell to activate / deactivate the positioning measurement gap, for example). For example, the wireless device may determine that UL synchronization of the serving cell or TAG is not lost, for example, the validity timer corresponding to the serving cell or TAG is running.

[0352] In an example embodiment, in response to determining that the time alignment timer (e.g., timeAlignmentTimer) of the TAG (or serving cell) is running and the UL synchronization of the serving cell or TAG is not lost (e.g., the validity timer corresponding to the serving cell or TAG is running), the wireless device may trigger a positioning measurement gap request (e.g., requesting, for example, a base station on the serving cell to activate / deactivate the positioning measurement gap). In response to determining that the time alignment timer (e.g., timeAlignmentTimer) of the TAG (or serving cell) is running and the UL synchronization of the serving cell or TAG is lost (e.g., the validity timer corresponding to the serving cell or TAG expires), the wireless device may not trigger a positioning measurement gap request (e.g., not requesting, for example, a base station on the serving cell to activate / deactivate the positioning measurement gap).

[0353] In an example embodiment, if Fig.21 As shown, based on one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) being valid (e.g., the validity timer corresponding to the serving cell or TAG is running), the wireless device may request the base station (e.g., the network) to activate / deactivate the positioning measurement gap in at least one measurement gap (e.g., whether to trigger a positioning measurement gap request). For example, based on one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) being invalid (e.g., the validity timer corresponding to the serving cell or TAG is running), the wireless device may not trigger a positioning measurement gap request (e.g., requesting a base station on the serving cell to activate / deactivate the positioning measurement gap).

[0354] like Fig.21 As shown, based on the triggered positioning measurement gap request, the wireless device may transmit a positioning measurement gap request MAC CE to the base station, for example, on / via the serving cell or via the serving link of at least one serving link. The positioning measurement gap request MAC CE may be a measurement gap activation request MAC CE (e.g., positioning measurement gap activation request MAC CE) for requesting activation of the positioning measurement gap. In some other examples, the positioning measurement gap request MAC CE may be a measurement gap deactivation request MAC CE (e.g., positioning measurement gap deactivation request MAC CE) for requesting deactivation (activated) of the positioning measurement gap. For example, the wireless device may determine that UL synchronization of the serving cell (or one or more serving cells) has been acquired (e.g., the validity timer corresponding to the serving cell or TAG is running).

[0355] The positioning measurement gap activation / deactivation request MAC CE may be identified by a MAC subheader with a corresponding eLCID (e.g., code point 238 and / or index 302). The positioning measurement gap activation / deactivation request MAC CE may include one or more fields. The one or more fields may include at least one of the following: a positioning MG ID field (e.g., 4 bits in length) indicating an identifier of the positioning measurement gap; and / or an A / D field (e.g., 1 bit in length) indicating activation or deactivation of the positioning measurement gap; and / or at least one physical cell ID (e.g., a cell ID of at least one serving cell and / or at least one non-serving cell); and / or a polarization mode (e.g., corresponding to an NTN node on a serving link of a cell); and / or an NTN node ID corresponding to a serving link corresponding to a serving cell or a non-serving cell. For example, based on the A / D field of the positioning measurement gap activation / deactivation request MAC CE being set to '1', the wireless device may request activation of the positioning measurement gap. For example, based on the A / D field of the positioning measurement gap activation / deactivation request MAC CE being set to '0', the wireless device may request deactivation of the positioning measurement gap.

[0356] In some cases, to request a base station (e.g., a network) to activate or deactivate a positioning measurement gap, the wireless device may determine that a remaining duration of a validity timer corresponding to a serving cell or a TAG (e.g., a time until the validity timer expires) is greater than a threshold. In some cases, one or more configuration parameters may indicate / configure the threshold. In other examples, the wireless device may determine the threshold (e.g., based on, for example, one or more NTN configuration parameters corresponding to the serving cell and / or the TAG). For example, the threshold may be a UE-gNB RTT corresponding to the serving cell or the TAG. The threshold may, for example, be greater than the UE-gNB RTT corresponding to the serving cell or the TAG. For example, the threshold may be less than the UE-gNB RTT corresponding to the serving cell or the TAG.

[0357] In an example embodiment, based on one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) being valid (e.g., a validity timer corresponding to a serving cell or TAG is running), in order to request a base station (e.g., a network) to activate a positioning measurement gap, the wireless device may trigger a measurement gap activation request (e.g., a positioning measurement gap activation request MAC CE). In an example, a higher layer (e.g., an RRC sublayer) of the wireless device may notify / trigger a lower layer (e.g., a MAC layer) of the wireless device to initiate / trigger a measurement gap activation request (e.g., trigger positioning measurement gap activation request). In some embodiments, a higher layer (e.g., an RRC sublayer) of the wireless device may send an indication to a lower layer (e.g., a MAC layer) of the wireless device. The indication may instruct / notify / trigger a lower layer (e.g., a MAC layer) of the wireless device to transmit a measurement gap activation request MAC CE (e.g., a positioning measurement gap activation request MAC CE). Transmitting a measurement gap activation request MAC CE (e.g., a positioning measurement gap activation request MAC CE). For example, based on the triggered measurement gap activation request (eg, triggered positioning measurement gap activation request MAC CE), the wireless device may transmit a positioning measurement gap activation request MAC CE (eg, positioning measurement gap activation request MAC CE) to, for example, a base station on a serving cell.

[0358] In an example embodiment, based on one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) being valid (e.g., a validity timer corresponding to a serving cell or TAG is running) and in order to request a base station (e.g., a network) to deactivate the positioning measurement gap, the wireless device may trigger a measurement gap deactivation request (e.g., a positioning measurement gap deactivation request MAC CE). In an example, a higher layer (e.g., an RRC sublayer) of the wireless device may notify / trigger a lower layer (e.g., a MAC layer) of the wireless device to initiate / trigger the measurement gap deactivation request. In some embodiments, a higher layer (e.g., an RRC sublayer) of the wireless device may send an indication to a lower layer (e.g., a MAC layer) of the wireless device. The indication may indicate / notify / trigger a lower layer (e.g., a MAC layer) of the wireless device to transmit a measurement gap deactivation request MAC CE (e.g., a positioning measurement gap deactivation request MAC CE). For example, based on the triggered measurement gap deactivation request (e.g., a triggered positioning measurement gap deactivation request MAC CE), the wireless device may transmit a positioning measurement gap deactivation request MAC CE (e.g., a positioning measurement gap deactivation request MAC CE) to, for example, a base station on a serving cell. For example, the wireless device may deactivate (all) activated measurement gaps for positioning (eg, corresponding to a serving cell).

[0359] In order to transmit a positioning measurement gap activation / deactivation request MAC CE (e.g., positioning measurement gap activation / deactivation request MAC CE) to a base station on a serving cell, for example, the wireless device may determine whether the positioning measurement gap request (e.g., positioning measurement gap activation / deactivation request) is triggered and not canceled. For example, in response to determining that the positioning measurement gap request is canceled, the wireless device may not transmit the positioning measurement gap activation / deactivation request MAC CE. For example, the wireless device may determine that UL synchronization of the serving cell (or one or more serving cells) has been obtained / maintained (e.g., the validity timer of the serving cell and / or TAG is running) and / or the time alignment timer (corresponding to the TAG) is running.

[0360] For example, in response to determining that the positioning measurement gap request is not canceled and at least one UL-SCH resource is available for a new UL transmission (e.g., on a serving cell), the wireless device may transmit a positioning measurement gap activation / deactivation request MAC CE to the base station by instructing a multiplexing and assembling procedure to generate a positioning measurement gap activation / deactivation request MAC CE (e.g., based on a triggered positioning measurement gap request). For example, the wireless device may determine that at least one UL-SCH resource accommodates the positioning measurement gap request MAC CE and its subheader (e.g., based on or due to logical channel prioritization (LCP)). For example, the wireless device may transmit a MAC PDU containing the positioning measurement gap activation / deactivation request MAC CE. The wireless device may cancel the triggered positioning measurement gap request based on transmitting the positioning measurement gap activation / deactivation request MAC CE.

[0361] In some other examples, in response to determining that the positioning measurement gap request is not canceled and at least one UL-SCH resource is not available for new transmission (e.g., the UL-SCH resource accommodates the positioning measurement gap request MAC CE and its subheader due to LCP), the wireless device may trigger (or send to the base station) a scheduling request (SR) for the positioning measurement gap activation / deactivation request. In an example embodiment, the wireless device may determine that a fourth configuration parameter for the SR for the positioning measurement gap activation / deactivation request is enabled (or indicated / configured, or not disabled). The one or more configuration parameters may indicate / configure the fourth configuration parameter. For example, the one or more configuration questions may include one or more SR configuration parameters corresponding to / for the positioning measurement gap activation / deactivation request. The wireless device may cancel the triggered positioning measurement gap request based on transmitting the SR for the positioning measurement gap activation / deactivation request.

[0362] For example, in response to transmitting a positioning measurement gap activation request MAC CE or an SR for a positioning measurement gap activation request, the base station may transmit a confirmation of activating the positioning measurement gap. For example, the base station may transmit a DL MAC CE for a positioning measurement gap activation command (e.g., a positioning measurement gap activation command MAC CE).

[0363] In some examples, in response to transmitting a positioning measurement gap deactivation request MAC CE or an SR for a positioning measurement gap deactivation request, the base station may transmit a confirmation of deactivating the positioning measurement gap. For example, the base station may transmit a DL MAC CE for a positioning measurement gap deactivation command (e.g., a positioning measurement gap deactivation command MAC CE) to the wireless device.

[0364] The positioning measurement gap activation / deactivation command MAC CE may be identified by a MAC subheader with a corresponding eLCID (e.g., code point 237 and / or index 301). The positioning measurement gap activation / deactivation command MAC CE may include one or more fields. The one or more fields may include at least one of the following: a positioning MG ID field (e.g., 4 bits in length), which indicates an identifier of the positioning measurement gap; and / or an A / D field (e.g., 1 bit in length), which indicates activation or deactivation of the positioning measurement gap; and / or at least one physical cell ID (e.g., a cell ID of at least one serving cell and / or at least one non-serving cell); and / or a polarization mode (e.g., corresponding to an NTN node on a serving link of a cell); and / or an NTN node corresponding to a serving link corresponding to a serving cell or a non-serving cell. For example, based on the A / D field of the positioning measurement gap activation / deactivation command MAC CE being set to '1', the wireless device may activate the positioning measurement gap (e.g., corresponding to the serving cell and / or the polarization mode and / or the NTN node of the serving link). Based on the A / D field of the positioning measurement gap activation / deactivation command MAC CE being set to '0', the wireless device may deactivate the positioning measurement gap (eg, corresponding to the serving cell and / or polarization mode and / or NTN node of the serving link).

[0365] In some examples, based on receiving the positioning measurement gap deactivation command MAC CE, the wireless device may deactivate the positioning measurement gap (e.g., corresponding to the NTN node of the serving cell and / or polarization mode and / or serving link). In some other examples, based on receiving the positioning measurement gap activation command MAC CE, the wireless device may activate the positioning measurement gap (e.g., corresponding to the NTN node of the serving cell and / or polarization mode and / or serving link).

[0366] In / during the (activated) positioning measurement gap, the wireless device may perform one or more location-related measurements on at least one of the one or more serving cells and in a corresponding frequency range and / or corresponding polarization mode of the positioning measurement gap (e.g., configured / indicated by one or more measurement configuration parameters, such as measGapConfig). In some cases, the wireless device may perform at least one of the following: not performing transmission of HARQ feedback, SR, and CSI; and / or not reporting SRS; and / or not transmitting messages other than Msg3 or MSGA payload of a random access procedure on UL-SCH. In some other cases, based on the random access response (RAR) window (e.g., ra-ResponseWindow or msgB-ResponseWindow) and / or the contention resolution timer (e.g., ra-ContentionResolutionTimer) being running, the wireless device may monitor PDCCH during the activated positioning measurement gap. For example, during the activated positioning measurement gap, the wireless device may not monitor PDCCH (e.g., when the RAR window is not running or when the contention resolution timer is not running) and / or not receive on DL-SCH.

[0367] In some embodiments, the wireless device may determine that the triggered measurement gap deactivation request (e.g., positioning measurement gap deactivation request MAC CE) is not canceled. In an example, for the triggered measurement gap deactivation request, the wireless device may determine from a higher layer (e.g., RRC sublayer) of the wireless device that an indication for initiating the measurement gap deactivation request is (previously) sent to a lower layer (e.g., MAC layer) of the wireless device. In an example embodiment, in response to determining that one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) are invalid (e.g., a validity timer corresponding to a serving cell or TAG expires), the higher layer (e.g., RRC sublayer) of the wireless device may send / notify a lower layer (e.g., MAC layer) of the wireless device to cancel the triggered measurement gap deactivation request. For example, the higher layer (e.g., RRC sublayer) of the wireless device may send an indication to the lower layer (e.g., MAC layer) of the wireless device. The indication may indicate / notify the lower layer (e.g., MAC layer) of the wireless device to cancel the triggered positioning measurement gap activation / deactivation request (e.g., triggered positioning measurement gap activation / deactivation request MAC CE). A lower layer (e.g., MAC layer) of the wireless device may cancel the triggered measurement gap deactivation request based on receiving the indication. In some scenarios, based on canceling the triggered positioning measurement gap request, the wireless device may stop (e.g., if running) an SR prohibit timer (e.g., sr-ProhibitTimer) corresponding to the triggered SR for positioning measurement gap activation / deactivation request.

[0368] In some embodiments, the base station may configure the wireless device with a second configuration parameter (e.g., via one or more configuration parameters). According to an example embodiment, the one or more configuration parameters may include a second configuration parameter. The second configuration parameter may, for example, indicate whether the wireless device uses / adopts one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) to determine whether to trigger a positioning measurement gap activation / deactivation request. For example, in response to determining that the second configuration parameter is indicated / configured (or enabled or not disabled, or present in one or more configuration parameters), the wireless device may determine whether to trigger a positioning measurement gap activation / deactivation request based on whether UL synchronization of a serving cell in one or more serving cells is lost (e.g., based on whether one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) are valid). For example, based on the second configuration parameter being indicated / configured (or enabled or not disabled, or present in one or more configuration parameters) and one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) being invalid (e.g., UL synchronization of a serving cell in one or more serving cells is lost), the wireless device may not trigger a positioning measurement gap activation / deactivation request.

[0369] In some embodiments, the wireless device may transmit a UE capability message to the base station. In an example embodiment, the UE capability message may indicate the ability of the wireless device to activate / deactivate positioning measurement gaps when UL synchronization of the serving cell is maintained / acquired (e.g., a validity timer corresponding to the serving cell or TAG is running). In an example embodiment, the UE capability message may indicate the ability of the wireless device to activate / deactivate positioning measurement gaps when UL synchronization of the serving cell is lost (e.g., a validity timer corresponding to the serving cell or TAG expires).

[0370] Example embodiments may reduce complexity of a wireless device (eg, by determining whether to trigger a positioning measurement gap activation / deactivation request based on whether one or more NTN configuration parameters (eg, corresponding to a serving cell or TAG) are valid).

[0371] Fig. 22 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown. In some scenarios, Fig. 22 An example embodiment of a procedure for requesting activation / deactivation of positioning measurement gaps (eg, at a base station and / or a wireless device) may be shown. Fig. 22 An example of a location measurement indication procedure (e.g., for requesting activation / deactivation of a positioning measurement gap) in an RRC connected state / mode (e.g., RRC_CONNECTED state) and / or in an RRC non-connected state / mode (e.g., RRC_INACTIVE / IDLE state or RRC_IDLE state) may be shown. In some embodiments, Fig. 22 An embodiment of a method (or process) for locating a procedure may be shown.

[0372] The base station may communicate with the wireless device via / using one or more cells (e.g., one or more serving cells). The wireless device may communicate with the base station, for example, via a non-terrestrial network (NTN), for example, the wireless device and the base station may operate in the NTN and / or the base station may be an NTN base station and / or the cell (e.g., a serving cell in one or more serving cells) may be part of the NTN. For example, the cell may be a serving cell or a non-serving cell. Fig.21As shown, the wireless device may receive one or more configuration parameters (e.g., one or more RRC configuration parameters) from a base station. The one or more configuration parameters may, for example, include one or more serving cell (e.g., one or more serving cells or one or more cells) configuration parameters (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB, and / or ServingCellConfig) for configuring one or more cells (e.g., one or more serving cells).

[0373] In some examples, the one or more configuration parameters may include one or more NTN configuration parameters. For example, the one or more configuration parameters may include one or more positioning RS (PRS) configuration parameters. For example, the one or more PRS configuration parameters may configure the wireless device with one or more DL PRS resource sets (e.g., via NR-DL-PRS-ResourceSet and NR-DL-PRS-Resource). One or more configuration parameters (e.g., using RRCReconfiguration or RRCResume) may include one or more measurement configuration parameters (e.g., MeasConfig). In an example, the one or more measurement configuration parameters may configure the wireless device to perform measurements (e.g., one or more location-related measurements), for example, on a serving cell or on a non-serving cell.

[0374] In an example, the wireless device may receive a message (e.g., NR-DL-TDOA-RequestLocationInformation message and / or NR-DL-AoD-ProvideAssistanceData message and / or nr-Multi-RTT-Request LocationInformation message and / or nr-ECID-RequestLocationInformation message) from the LMF via LPP requesting the wireless device to measure and / or report (e.g., PRS-RSRP, DL RSTD, PRS-RSRPP, and / or one or more UE Rx-Tx time differences) measurements. The wireless device may initiate the performance of measurements (e.g., location measurements, such as location-related measurements in one or more location-related measurements), for example, based on receiving an indication for initiating measurements from a higher layer (e.g., a layer above the RRC sublayer, such as an IP layer, a PDU layer, an application layer) and / or based on receiving a message from the LMF via LPP. In some cases, the wireless device may determine that the positioning procedure is initiated as an indicate start of one or more location-related measurements.

[0375] like Fig. 22As shown, the wireless device may trigger a positioning measurement gap request to request a base station (e.g., a network) to activate / deactivate a positioning measurement gap in at least one measurement gap. In an example, a higher layer (e.g., an RRC sublayer) of the wireless device may notify / trigger a lower layer (e.g., a MAC layer) of the wireless device to initiate / trigger a measurement gap activation / deactivation request. In some examples, a higher layer (e.g., an RRC sublayer) of the wireless device may send an indication to a lower layer (e.g., a MAC layer) of the wireless device. The indication may trigger the lower layer (e.g., a MAC layer) of the wireless device to trigger a measurement gap activation / deactivation request (e.g., a positioning measurement gap activation / deactivation request MAC CE).

[0376] In an example embodiment, if Fig. 22 As shown, the lower layer (e.g., MAC layer) of the wireless device may determine whether to cancel the triggered measurement gap activation / deactivation request based on the triggered measurement gap activation / deactivation request and whether one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) are invalid (e.g., whether the validity timer corresponding to the serving cell or TAG expires and / or whether the UL synchronization of the serving cell is lost). For example, the lower layer (e.g., MAC layer) of the wireless device may determine whether to transmit a positioning measurement gap activation / deactivation request MAC CE and / or whether to trigger a scheduling request (SR) for the triggered measurement gap activation / deactivation request.

[0377] In an example embodiment, if Fig. 22 As shown, based on one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) being invalid (e.g., the validity timer corresponding to the serving cell or TAG is not running or expired), such as whether the UL synchronization of the serving cell is lost, the lower layer (e.g., MAC layer) of the wireless device may cancel the triggering of the positioning measurement gap activation / deactivation request. For example, the wireless device may not request the base station to activate / deactivate the positioning measurement gap.

[0378] In some examples, a higher layer (e.g., an RRC sublayer) of a wireless device may inform / notify a lower layer (e.g., a MAC sublayer) of UL synchronization loss (e.g., for UL transmission with a base station and / or UL transmission on a serving cell in one or more serving cells). For example, a higher layer (e.g., an RRC sublayer) of a wireless device may send / transmit a first indication indicating UL synchronization loss (e.g., of a serving cell) to a lower layer (e.g., a MAC layer) of the wireless device. For example, the first indication may indicate UL synchronization loss for each serving cell (e.g., each serving cell and / or serving cell in one or more serving cells). In an example, the wireless device may clear all HARQ buffers (e.g., HARQ buffers of a MAC PDU containing a positioning measurement gap activation / deactivation request MAC CE) and / or may not perform (e.g., any) uplink transmission on a serving cell (or each) of the one or more serving cells. In an example, the wireless device may stop location-related measurements (e.g., corresponding to a cell, such as a serving cell). For example, the wireless device may set measurementIndication of a LocationMeasurementIndication message to a value of release.

[0379] In some embodiments, the base station may configure the wireless device with a second configuration parameter (e.g., via one or more configuration parameters). According to an example embodiment, the one or more configuration parameters may include a second configuration parameter. The second configuration parameter may, for example, indicate whether the wireless device uses / adopts one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) to determine whether to cancel the triggered positioning measurement gap activation / deactivation request. For example, in response to determining that the second configuration parameter is indicated / configured (or enabled or not disabled, or present in one or more configuration parameters), the wireless device may determine whether to cancel the triggered positioning measurement gap activation / deactivation request based on whether UL synchronization of a serving cell in one or more serving cells is lost (e.g., based on whether one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) are valid). For example, based on the second configuration parameter being indicated / configured (or enabled or not disabled, or present in one or more configuration parameters) and one or more NTN configuration parameters (e.g., corresponding to a serving cell or TAG) being invalid (e.g., UL synchronization of a serving cell in one or more serving cells is lost), the wireless device may cancel the triggered positioning measurement gap activation / deactivation request.

[0380] Some example embodiments may reduce complexity of a wireless device (eg, by determining whether to cancel a triggered positioning measurement gap activation / deactivation request based on one or more NTN configuration parameters (eg, corresponding to a serving cell or TAG) being invalid).

[0381] Fig.23 An example embodiment of a procedure for positioning measurement gap activation / deactivation in a wireless communication system according to aspects of the present disclosure is shown. In some scenarios, Fig.23 An example embodiment of a procedure for requesting activation / deactivation of positioning measurement gaps (eg, at a base station and / or a wireless device) may be shown. Fig.23 An example of a location measurement indication procedure (e.g., for requesting activation / deactivation of a positioning measurement gap) in an RRC connected state / mode (e.g., RRC_CONNECTED state) and / or in an RRC non-connected state / mode (e.g., RRC_INACTIVE / IDLE state or RRC_IDLE state) may be shown. In some embodiments, Fig.23 An embodiment of a method (or process) for locating a procedure may be shown.

[0382] The base station may communicate with the wireless device via / using one or more cells (e.g., one or more serving cells). For example, the wireless device may be in an RRC_CONNECTED (or RRC connected) state / mode. The wireless device may communicate with the base station, for example, via a non-terrestrial network (NTN), for example, the wireless device and the base station may operate in the NTN and / or the base station may be an NTN base station and / or the cell (e.g., a serving cell in one or more serving cells) may be part of the NTN. For example, the cell may be a serving cell in one or more serving cells. Fig.23 As shown, the wireless device may receive one or more configuration parameters (e.g., one or more RRC configuration parameters) from a base station. The one or more configuration parameters may, for example, include one or more serving cell (e.g., one or more serving cells or one or more cells) configuration parameters (e.g., ServingCellConfigCommon, ServingCellConfig CommonSIB, and / or ServingCellConfig) for configuring one or more cells (e.g., one or more serving cells).

[0383] In some examples, the one or more configuration parameters may include one or more NTN configuration parameters. For example, the one or more configuration parameters may include one or more positioning RS (PRS) configuration parameters. For example, the one or more PRS configuration parameters may configure the wireless device with one or more DL PRS resource sets (e.g., via NR-DL-PRS-ResourceSet and NR-DL-PRS-Resource). One or more configuration parameters (e.g., using RRCReconfiguration or RRCResume) may include one or more measurement configuration parameters (e.g., MeasConfig). In an example, the one or more measurement configuration parameters may configure the wireless device to perform measurements (e.g., one or more location-related measurements), for example, on at least one serving cell of one or more serving cells or on at least one non-serving cell.

[0384] In an example, the wireless device may receive a message (e.g., NR-DL-TDOA-RequestLocationInformation message and / or NR-DL-AoD-ProvideAssistanceData message and / or nr-Multi-RTT-Request LocationInformation message and / or nr-ECID-RequestLocationInformation message) from the LMF via the LPP requesting the wireless device to measure and / or report (e.g., PRS-RSRP, DL RSTD, PRS-RSRPP and / or one or more UE Rx-Tx time differences) measurements. The wireless device may initiate (or perform) a positioning measurement procedure, such as performing one (or at least one) measurement (e.g., a location measurement, such as a location-related measurement in one or more location-related measurements), for example, based on receiving an indication for initiating / performing a positioning measurement procedure from a higher layer (e.g., a layer above the RRC sublayer, such as the LMF via the LPP, and / or based on receiving a message from the LMF via the LPP). In some cases, the wireless device may determine that the initiated / triggered positioning measurement procedure is an indicate start of one or more location-related measurements. In some cases, the positioning procedure is initiated / triggered for RSTD measurements for E-UTRA. In some other cases, the positioning procedure is initiated / triggered for positioning measurements for NR.

[0385] like Fig.23As shown, the wireless device may perform measurements (e.g., one or more location-related measurements) during the positioning measurement gap in one or more positioning measurement gaps by / in connection with performing a positioning procedure. For example, the wireless device may activate the positioning measurement gap by / in connection with performing a positioning measurement procedure (e.g., based on the above description). Fig. 20 and / or Fig.21 of the embodiment of the invention).

[0386] In an example embodiment, if Fig.23 As shown, in response to determining that UL synchronization of the serving cell is lost (e.g., one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) are invalid and / or the validity timer corresponding to the serving cell expires), the wireless device can (automatically) deactivate the positioning measurement gap on the serving cell. For example, the wireless device can use / via the positioning measurement gap to determine that the positioning measurement procedure is in progress. For example, the wireless device can stop / interrupt / suspend the execution of the positioning measurement procedure on the serving cell. For example, in order to stop / interrupt / suspend the execution of the positioning measurement procedure, the wireless device can initiate the positioning measurement procedure as an indicate stop (e.g., an indicate stop of one or more location-related measurements or an indication stop for subframe and slot timing detection for E-UTRA).

[0387] Some example embodiments may allow a wireless device (and / or a base station) to stop performing a positioning measurement procedure (e.g., by deactivating a positioning measurement gap) in response to a UL synchronization loss of a serving cell. For example, based on the positioning procedure being a TDOA and / or AOD method, the wireless device may stop performing a positioning measurement procedure (e.g., by deactivating a positioning measurement gap) in response to a UL synchronization loss of a serving cell.

[0388] The benefit of deactivating the positioning measurement gaps may be reduced processing complexity / consumption power of the wireless device. The disadvantage of deactivating the positioning measurement gaps may be inaccurate location information at the wireless device and / or the base station.

[0389] In some examples, the wireless device may deactivate the positioning measurement gap within / during the waiting (or deactivation) window / duration / time period. For example, the waiting window may be used for the wireless device to (re)acquire the NTN-specific SIB and / or SIB1 (e.g., verify one or more NTN configuration parameters). For example, the wireless device may stop / interrupt / pause performing a positioning procedure on the serving cell during the waiting window.

[0390] In response to (re)acquiring the NTN-specific SIB and / or SIB1 (e.g., starting, for example, a validity timer corresponding to the serving cell, and / or verifying, for example, one or more NTN configuration parameters corresponding to the serving cell), the wireless device may start (or resume) a positioning procedure on the serving cell. For example, in order to stop / interrupt / suspend the execution of the positioning measurement procedure, the wireless device may initiate the positioning procedure as indicate start. For example, the wireless device may obtain UL synchronization of the serving cell. In some examples, the wireless device may (automatically) activate (deactivate) the positioning measurement gap, for example, based on (re)acquiring the NTN-specific SIB and / or SIB1. For example, the wireless device may start the positioning measurement procedure according to the EpochTime of one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) and / or the timing when one or more NTN configuration parameters (e.g., corresponding to the serving cell or TAG) become available and / or the time (e.g., time slot, subframe, frame or symbol) when the validity timer is started.

[0391] In order to stop performing the positioning procedure (e.g., in order to initiate the positioning measurement procedure as an indicate stop), the wireless device may set one or more contents of the LocationMeasurementIndication message. Based on the (ongoing) positioning procedure being initiated as an indicate stop of one or more location-related measurements (e.g., being stopped / interrupted / paused), the wireless device may set the measurementIndication content in one or more contents of the LocationMeasurementIndication message to the value release. The wireless device may, for example, submit the LocationMeasurementIndication message to a lower layer (e.g., MAC layer or PHY layer) for transmission after (successfully) (re)acq...

Claims

1. A method comprising: receiving, by the wireless device, one or more non-terrestrial network (NTN) configuration parameters indicating a validity timer, wherein the validity timer indicates a maximum duration for which the one or more NTN configuration parameters are valid; starting the validity timer in response to receiving the one or more NTN configuration parameters; initiating a positioning procedure based on receiving a message requesting one or more measurements; and Based on the validity timer, the positioning procedure is stopped.

2. A method comprising: One or more non-terrestrial network (NTN) configuration parameters indicating a validity timer are transmitted by a base station to a wireless device, wherein the validity timer indicates a maximum duration for which the one or more NTN configuration parameters are valid, wherein the validity timer is started in response to receiving the one or more NTN configuration parameters, wherein a positioning procedure is initiated based on receiving a message requesting one or more measurements, and wherein the positioning procedure is stopped based on the validity timer.

3. The method of claim 1 or claim 2, wherein the positioning procedure is stopped based on the validity timer not running. The method of claim 3 , wherein the validity timer not being in operation comprises the validity timer expiring or stopping. 5 . The method according to claim 1 , wherein the stopping the positioning procedure comprises suspending the execution of the one or more measurements until one or more first NTN configuration parameters are received via a system information block (SIB).

6. The method according to any one of claims 1 to 5, wherein the one or more measurements of the positioning procedure are based on at least one antenna polarization mode, wherein the one or more NTN configuration parameters indicate the at least one antenna polarization mode.

7. The method according to any one of claims 1 or 3 to 6 further comprises receiving one or more DL PRS configuration parameters indicating multiple downlink positioning reference signal DL PRS resources, wherein the one or more measurements of the positioning procedure are based on measuring one or more first DL PRS resources among the multiple DL PRS resources. 8 . The method of claim 7 , wherein a DL PRS resource in the one or more first DL PRS resources is associated with an antenna polarization mode, wherein the one or more NTN configuration parameters indicate the antenna polarization mode.

9. The method according to any one of claims 1 to 8, wherein the one or more measurements correspond to at least one NTN node of a cell. 10 . The method according to claim 1 , wherein the initiating the positioning procedure is performed during a radio resource control (RRC) inactive state of the wireless device.

11. The method according to any one of claims 1 or 3 to 10, further comprising receiving one or more configuration parameters, in: The one or more configuration parameters include one or more measurement gap configuration parameters indicating one or more positioning measurement gaps; and The initiated positioning procedure uses at least one positioning measurement gap in the one or more positioning procedures to perform the one or more measurements of the positioning procedure.

12. The method according to any one of claims 1 or 3 to 11, further comprising setting a positioning measurement gap in the at least one positioning measurement gap based on at least one of the following: the one or more NTN configuration parameters; or The one or more configuration parameters, wherein the one or more configuration parameters indicate one or more offsets, wherein each of the one or more offsets is associated with each of the one or more positioning measurement gaps.

13. The method according to claim 12, wherein the start timing of the positioning measurement gap is based on at least one of the following: an offset corresponding to the positioning measurement gap; or A serving link propagation delay between the wireless device and an NTN node of a cell, wherein the serving link delay is determined based on the one or more NTN configuration parameters.

14. The method according to any one of claims 11 to 13, wherein the one or more configuration parameters indicate whether triggering a positioning measurement gap request for activation or deactivation of a positioning measurement gap is enabled.

15. The method according to any one of claims 11 to 14, further comprising transmitting an uplink medium access control (MAC) control element for a triggered positioning measurement gap activation request based on the one or more configuration parameters indicating the one or more positioning measurement gaps, triggering the positioning measurement gap request for activating a first positioning measurement gap among the one or more positioning measurement gaps.

16. The method according to any one of claims 11 to 15, further comprising transmitting an uplink medium access control (MAC) control element for a triggered positioning measurement gap deactivation request based on the one or more configuration parameters, triggering the positioning measurement gap request for deactivating a first positioning measurement gap among the one or more positioning measurement gaps.

17. The method according to any one of claims 11 to 16, further comprising: triggering a positioning measurement gap request to activate or deactivate a first positioning measurement gap of the one or more positioning measurement gaps; An SR associated with a Scheduling Request (SR) configuration for a triggered Positioning Measurement Gap Request is transmitted based on: the triggered positioning measurement gap request; the one or more configuration parameters indicating the SR configuration, wherein the SR configuration is associated with a triggered positioning measurement gap; and The triggered positioning measurement gap request is cancelled in response to the transmitting the SR.

18. The method according to any one of claims 11 to 17, further comprising determining whether to trigger a positioning measurement gap request for activating or deactivating a first positioning measurement gap among the one or more positioning measurement gaps based on the validity timer.

19. The method of claim 18, further comprising triggering the positioning measurement gap request based on the validity timer being running.

20. The method of claim 19, further comprising canceling the triggered positioning measurement gap request in response to the stopping the positioning procedure.

21. The method of claim 18 or claim 19, further comprising: transmitting an uplink signal for the triggered positioning measurement gap request while the validity timer is running and during the positioning procedure; and The triggered positioning measurement gap request is cancelled based on the uplink signal transmitting the triggered positioning measurement gap request.

22. The method according to any one of claims 18 to 21, further comprising avoiding triggering the positioning measurement gap request based on the validity timer not being running.

23. The method of claim 22, wherein the avoiding triggering the positioning measurement gap request continues until one or more first NTN configuration parameters are received.

24. The method according to any one of claims 11 to 23, further comprising: receiving a positioning measurement gap activation command for activating a third positioning measurement gap among the one or more positioning measurement gaps; activating the third positioning measurement gap for performing at least one of the one or more measurements in response to receiving the positioning measurement gap activation command; and In response to the validity timer not being running, the third positioning measurement gap is deactivated.

25. The method of claim 24, wherein the deactivating the third positioning measurement gap lasts until one or more first NTN configuration parameters are received via a SIB.

26. The method of any one of claims 1 or 2 to 25, further comprising determining that a time alignment timer is running.

27. The method according to any one of claims 11 to 26, wherein the one or more measurement gap configuration parameters indicate a second measurement gap for performing a Global Navigation Satellite System (GNSS) measurement among the one or more measurements in a Radio Resource Control (RRC) connected state of the wireless device, wherein the second measurement gap is not one of the at least one positioning measurement gap.

28. The method according to claim 27, further comprising Receiving a media access control MAC control element CE triggering the GNSS measurement in the RRC connected state; and The GNSS measurement is performed during the second measurement gap and in the RRC connected state based on the MAC CE.

29. The method of claim 28, further comprising: refraining from transmitting an uplink signal while the validity timer is running and during the second measurement gap in which the GNSS measurement is performed; and Receiving downlink signals is avoided during the second measurement gap in which the GNSS measurement is performed.

30. The method of claim 29, further comprising avoiding re-acquisition of one or more first NTN configuration parameters via a SIB based on expiration of the validity timer and when performing the GNSS measurement during the first measurement gap.

31. A method according to any one of claims 1 to 30, wherein the message comes from a location server.

32. The method according to any one of claims 2 to 6, 9 or 10 further comprises transmitting one or more DL PRS configuration parameters indicating multiple downlink positioning reference signal DL PRS resources to the wireless device, wherein the one or more measurements of the positioning procedure are based on measuring one or more first DL PRS resources among the multiple DL PRS resources.

33. The method of claim 32, wherein a DL PRS resource of the one or more first DL PRS resources is associated with an antenna polarization pattern, wherein the one or more NTN configuration parameters indicate the antenna polarization pattern.

34. The method of any one of claims 2 to 6, 9, 10, 32 or 33, further comprising: and transmitting a positioning measurement gap activation command to the wireless device to activate a third positioning measurement gap among the one or more positioning measurement gaps, wherein the wireless device will activate the third positioning measurement gap for performing at least one measurement among the one or more measurements in response to receiving the positioning measurement gap activation command, and will deactivate the third positioning measurement gap in response to the validity timer not running.

35. The method of any one of claims 2 to 6, 9, 10 or 32 to 34, further comprising A medium access control MAC control element CE triggering GNSS measurement is transmitted to the wireless device in the RRC connected state, wherein the wireless device is to perform the GNSS measurement during the second measurement gap and in the RRC connected state based on the MAC CE.

36. A device comprising one or more processors and a memory storing instructions which, when executed by the one or more processors, cause the device to at least perform the method according to any one of claims 1 to 35.

37. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors of a device, cause the device to perform the method of any one of claims 1 to 35.

38. An apparatus comprising means for performing the method according to any one of claims 1 to 35.

39. An apparatus comprising circuitry for performing the method of any one of claims 1 to 35.

40. A computer program product encoding instructions for performing the method according to any one of claims 1 to 35.

Images