Uplink control channel repetition in non-terrestrial networks

Abstract

A method may include transmitting, by a wireless device and for a random access procedure, a Message3, the Message3 including a field indicating whether to repeat a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for a Message4 of the random access procedure. The method may also include receiving the Message 4, and transmitting a repetition of the HARQ-ACK for the Message 4 via a physical uplink control channel (PUCCH).

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 411,263, filed on September 29, 2022, the entire disclosure of which is incorporated herein by reference. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0004] Figure 1A and Figure 1B illustrates an example mobile communication network in which embodiments of the present disclosure may be implemented.

[0005] Figure 2A and Figure 2B illustrate the New Radio (NR) user plane and control plane protocol stacks, respectively.

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

[0007] Figure 4A illustrates an example of a downlink data stream flowing through the Figure 2A NR user plane protocol stack.

[0008] Figure 4B illustrates an example format of a MAC sub - header in a MAC PDU.

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

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

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

[0012] Figure 8 illustrates an example configuration of time slots in the time and frequency domains of an NR carrier.

[0013] Figure 9 illustrates an example of bandwidth adaptation using three configured BWPs of an NR carrier.

[0014] Figure 10A illustrates three carrier aggregation configurations with two component carriers.

[0015] Figure 10B Shows an example of how aggregated cells can be configured into one or more PUCCH groups.

[0016] Figure 11A Shows an example of the SS / PBCH block structure and location.

[0017] Figure 11B Shows an example of CSI-RS mapped in the time and frequency domains.

[0018] Figure 12A and Figure 12B Shows examples of three downlink and uplink beam management procedures, respectively.

[0019] Figure 13A 、 Figure 13B and Figure 13C Shows a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure, respectively.

[0020] Figure 14A Shows an example of the CORESET configuration of the bandwidth part.

[0021] Figure 14B Shows an example of the CCE-to-REG mapping for DCI transmission in CORESET and PDCCH processing.

[0022] Figure 15 Shows an example of a wireless device communicating with a base station.

[0023] Figure 16A 、 Figure 16B 、 Figure 16C and Figure 16D Shows an example structure for uplink and downlink transmissions.

[0024] Figure 17A Shows an example NTN architecture corresponding to a transparent satellite model according to one aspect of an embodiment of the present disclosure.

[0025] Figure 17B Shows an example NTN architecture corresponding to a regenerative satellite model according to one aspect of an embodiment of the present disclosure.

[0026] Figure 18 Shows an example of the deployment of multiple satellites.

[0027] Figure 19 Shows an example of the propagation delay of NTN corresponding to different altitudes.

[0028] Figure 20A Shows an example of a serving link with the maximum propagation delay of a cell / beam.

[0029] Figure 20B Shows an example of a serving link with the maximum propagation delay of a cell / beam.

[0030] Figure 21 Shows an example of NTN.

[0031] Figure 22A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0032] Figure 22B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0033] Figure 23A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0034] Figure 23B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0035] Figure 24A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0036] Figure 24B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0037] Figure 25A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0038] Figure 25B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0039] Figure 26A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0040] Figure 26B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0041] Figure 27A Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0042] Figure 27B Shows an example timing diagram according to one aspect of an embodiment of the present disclosure.

[0043] Figure 28 Shows an example flowchart according to one aspect of an embodiment of the present disclosure. Detailed Description

[0044] 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 an environment and scenario. 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 of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of the present disclosure. Any figures that highlight functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough such that it can be utilized in a manner different from that shown. For example, the actions listed in any flowchart can be reordered or used only optionally in certain embodiments.

[0045] Embodiments can be configured to operate as needed. 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 mechanisms can be executed. Example criteria can be at least partially based 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 can be applied. Thus, example embodiments that selectively implement the disclosed protocol can be implemented.

[0046] A base station can communicate with a mixture of wireless devices. The wireless devices and / or the base station can 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 mean a subset of the total wireless devices in the coverage area. For example, the present disclosure may mean multiple wireless devices with a given capability and a given LTE or 5G version in a given sector of the base station. The multiple wireless devices in the present disclosure can refer to a selected multiple of wireless devices, and / or a subset of the total wireless devices in the coverage area that execute according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that may not conform to the disclosed method. For example, these wireless devices or base stations may execute based on an older version of LTE or 5G technology.

[0047] In this disclosure, "a", "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 this disclosure, the term "may" is interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of the various suitable possibilities that may or may not be used in one or more of the respective embodiments. As used herein, the terms "comprising" and "consisting of" enumerate one or more components of the element being described. The term "comprising" is interchangeable with "including" and does not exclude components not enumerated from being included in the element being described. In contrast, "consisting of" provides a complete enumeration of the one or more components of the element being described. As used herein, the term "based on" should be interpreted as "at least partially based on" rather than, for example, "only based on". As used herein, the term "and / or" represents any possible combination of the enumerated elements. For example, "A, B, and / or C" may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0048] 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 following the term "based on" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments. The phrase "responsive to" (or equivalently "at least responsive to") indicates that the phrase following the term "responsive to" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments. The phrase "depending on" (or equivalently "at least depending on") indicates that the phrase following the term "depending on" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments. The phrase "employing / using" (or equivalently "at least employing / using") indicates that the phrase following the term "employing / using" is an example of one of the various suitable possibilities that may or may not be used in one or more different embodiments.

[0049] The term "configured" can relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" can refer to specific settings within the device that affect the operational 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. can be "configured" within the device to provide the device with specific characteristics, whether the device is in an operational state or a non-operational state. The term such as "control message induced in the device" can 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.

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

[0051] Many of the features presented are described as optional by using "may" or by using 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 group of optional features. The present disclosure should be construed as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0052] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, all of which may be behaviorally equivalent. For example, a module may be implemented as a software routine written in a computer language 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 LabVIEW MathScript). 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++. 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 the less functional internal hardware modules on the programmable device. The technologies mentioned are often used in combination to achieve the results of functional modules.

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

[0054] The CN 102 may provide an interface to one or more data networks (DNs) (such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN) to the wireless device 106. As part of the interface function, the CN 102 may establish an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide a charging function.

[0055] The RAN 104 can connect the CN 102 to the wireless device 106 via radio communication through the air interface. As part of the radio communication, the RAN 104 can provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 via the air interface is referred to as the downlink, while the communication direction from the wireless device 106 to the RAN 104 via the air interface is referred to as the uplink. Frequency-division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing techniques can be used to separate downlink transmissions from uplink transmissions.

[0056] The term "wireless device" can be used throughout this disclosure to mean and encompass any mobile device or fixed (non-mobile) device that requires or can use wireless communication. For example, a wireless device can be a phone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, 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.

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

[0058] The base stations included in the RAN 104 can include one or more sets of antennas for communicating with the wireless device 106 via the air interface. For example, one or more of the base stations can include three sets of antennas to control three cells (or sectors) respectively. The size of a cell can be determined by the range within 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 a base station can together provide radio coverage over a wide geographic area to support the movement of wireless devices.

[0059] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in RAN 104 can be implemented as sectorized sites with more or fewer than three sectors. One or more of the base stations in RAN 104 can be implemented as access points, baseband processing units coupled to a number of remote radio heads (RRHs), and / or repeaters or relay nodes for extending the coverage area of a donor node. The baseband processing unit coupled to the RRH can be part of a centralized or cloud RAN architecture, where the baseband processing unit can be centralized in a pool of baseband processing units or virtualized. The repeater node can amplify and replay the radio signals received from the donor node. The relay node can perform the same / similar functions as the repeater node, but can decode the radio signals received from the donor node to eliminate noise before amplifying and replaying the radio signals.

[0060] RAN 104 can be deployed as a homogeneous network of macro cell base stations with similar antenna patterns and similar high-level transmission powers. RAN 104 can be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations can be used to provide small coverage areas, such as coverage areas that overlap with the relatively large coverage areas provided by macro cell base stations. Small coverage areas can be provided in areas with high data traffic (or so-called "hot spots") or in areas with weak macro cell coverage. Examples of small cell base stations, in decreasing order of coverage area, include: micro cell base stations, pico cell base stations, and femto cell base stations or home base stations.

[0061] The 3rd Generation Partnership Project (3GPP) was established in 1998 to provide global specification standardization for mobile communication networks similar to the mobile communication network 100 in Figure 1A . So far, 3GPP has developed specifications for three generations of mobile networks: the 3rd generation (3G) network, known as the Universal Mobile Telecommunications System (UMTS); the 4th generation (4G) network, known as Long Term Evolution (LTE); and the 5th generation (5G) network, known as the 5G System (5GS). 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 can be applicable to the RANs of other mobile communication networks, such as the RAN 104 in Figure 1A , the RANs of early 3G and 4G networks, and the RANs of future networks that have not been specified (e.g., the 3GPP 6G network). The NG-RAN implementation employs the 5G radio access technology known as New Radio (NR) and can be configured to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0062] Figure 1BFIG. 0 shows another example mobile communication network 150 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. As Figure 1B shown, 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 UEs 156). These components may be implemented and operated in the same or similar manner as the corresponding components described with respect to Figure 1A FIG.

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

[0064] As Figure 1B shown, the 5G-CN 152 includes an access and mobility management function (AMF) 158A and a user plane function (UPF) 158B, which are shown as a single component AMF / UPF 158 for ease of illustration in Figure 1B FIG.

[0065] The UPF 158B may act as a gateway between the NG-RAN 154 and the one or more DNs. The functions that the UPF 158B may perform include: packet routing and forwarding, packet inspection, and enforcement of user plane policy rules, service usage reporting, support for uplink classification for routing traffic flows to the one or more DNs, quality of service (QoS) handling of the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and triggering of downlink data notifications. The UPF 158B may act as an anchor for mobility within / across radio access technologies (RATs), an external protocol (or packet) data unit (PDU) session point for interconnecting with the one or more DNs, and / or a pivot for supporting multi-homed PDU sessions. The UEs 156 may be configured to receive services via PDU sessions, which are logical connections between the UEs and the DNs.The functions that AMF 158A can perform include, for example, non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN-inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, in-system and inter-system mobility support, access authentication, access authorization including roaming right verification, mobility management control (subscription and policy), network slice support, and / or session management function (SMF) selection. NAS can refer to the functions operating between the CN and the UE, and AS can refer to the functions operating between the UE and the RAN.

[0066] 5G-CN 152 may include one or more additional network functions not shown for clarity in Figure 1B 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).

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

[0068] As Figure 1BAs shown, gNB 160 and / or ng-eNB 162 can be connected to 5G-CN 152 via the NG interface and to other base stations via the Xn interface. The NG and Xn interfaces can be established using direct physical connections and / or indirect connections via an underlying transport network (such as an Internet Protocol (IP) transport network). gNB 160 and / or ng-eNB 162 can be connected to UE 156 via the Uu interface. For example, as Figure 1B shown, gNB 160A can be connected to UE156A via the Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces can be used by Figure 1B the network elements in to exchange data and signaling messages and can include two planes: a user plane and a control plane. The user plane can handle data of interest to the user. The control plane can handle signaling messages of interest to the network elements.

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

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

[0071] 5G-CN 152 is described as being configured to handle NR and 4G radio access. One of ordinary skill in the art will understand that NR may be connected to a 4G core network in a mode referred to 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, a gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across the multiple AMF / UPF nodes.

[0072] As discussed, Figure 1B interfaces between network elements in

[0073] Figure 2A and Figure 2B may be associated with protocol stacks used by network elements to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to users, while the control plane may handle signaling messages of interest to network elements. Figure 2A and Figure 2B show examples of the NR user plane and NR control plane protocol stacks for the Uu interface located between UE 210 and gNB 220, respectively. Figure 2A and Figure 2B The protocol stacks shown in Figure 1B may be the same as or similar to those for the Uu interface between UE156A and gNB 160A shown in Figure 1B for example.

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

[0075] Figure 3 shows an example of the services provided between protocol layers of the NR user plane protocol stack. From Figure 2A and Figure 3Starting from the top, 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 the DN. A PDU session can have one or more QoS flows. The UPF in 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 latency, 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 flow and the data radio bearer can be determined by SDAP 225 at gNB 220. SDAP 215 at UE 210 can learn the mapping between the QoS flow and the data radio bearer through reflective mapping or control signaling received from gNB 220. For reflective mapping, SDAP 225 at gNB 220 can mark downlink packets with a QoS flow indicator (QFI), which can be observed by SDAP 215 at UE 210 to determine the mapping / demapping between the QoS flow and the data radio bearer.

[0076] PDCP 214 and 224 can perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, can perform encryption / decryption to prevent unauthorized decoding of the data transmitted over the air interface, and can perform integrity protection to ensure that control messages originate from the expected source. PDCP 214 and 224 can perform retransmission of undelivered packets, in-order delivery and reordering of packets, and removal of packets that are repeatedly received due to, for example, handover within the gNB. PDCP 214 and 224 can perform packet duplication to increase the likelihood of a packet being received, and remove any duplicate packets at the receiver. Packet duplication can be applicable to services that require high reliability.

[0077] Although Figure 3 not shown in, PDCP 214 and 224 can perform mapping / demapping between split radio bearers and RLC channels in a dual-connectivity scenario. Dual-connectivity is a technology that allows a UE to be connected to two cells or more generally to two cell groups: a master 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 cell groups in a dual-connectivity. PDCP 214 and 224 can map / demap split radio bearers between RLC channels belonging to cell groups.

[0078] RLC 213 and 223 can perform segmentation, retransmission via 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 said functions. The RLC configuration can be per logical channel, independent of the parameter set and / or Transmission Time Interval (TTI) duration. As Figure 3 shown, RLC 213 and 223 can provide RLC channels as services to PDCP 214 and 224, respectively.

[0079] MAC 212 and 222 can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing can include: multiplexing data units belonging to the one or more logical channels into transport blocks (TBs) delivered to / from PHY 211 and 221 and demultiplexing the data units from the transport blocks. MAC 222 can be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling can be performed in gNB 220 (at MAC 222) for both downlink and uplink. MAC 212 and 222 can be configured to perform error correction via 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 UE 210 by means of logical channel prioritization, and / or padding. MAC 212 and 222 can support one or more parameter sets and / or transmission timings. In one example, mapping restrictions in logical channel prioritization can control which parameter set and / or transmission timing a logical channel can use. As Figure 3 shown, MAC 212 and 222 can provide logical channels as services to RLC 213 and 223.

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

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

[0082] Figure 4A The downlink data flow begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In Figure 4A , the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. An SDAP header (marked as "H" in Figure 4A ) is added to the IP packets. Data units from / to higher protocol layers are called service data units (SDUs) of the lower protocol layer, and data units to / from lower protocol layers are called protocol data units (PDUs) of the higher protocol layer. As shown in Figure 4A , the data unit from the SDAP 225 is the SDU of the lower protocol layer PDCP 224 and the PDU of the SDAP 225.

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

[0084] Figure 4BShows an example format of the MAC sub-header in the MAC PDU. The MAC sub-header includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU corresponding to the MAC sub-header; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to assist the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0085] Figure 4B Further shows the MAC control element (CE) inserted into the MAC PDU by the MAC (such as MAC 223 or MAC 222). For example, Figure 4B Shows two MAC CEs inserted into the MAC PDU. The MAC CE can be inserted at the beginning of the downlink transmission of the MAC PDU (as Figure 4B shown) and at the end of the uplink transmission of the MAC PDU. The MAC CE can be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those 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 sub-header with a format similar to that described for the MAC SDU can exist before the MAC CE, and the MAC CE can be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

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

[0087] Figure 5A and Figure 5BThe mapping between logical channels, transport channels, and physical channels is shown separately for the downlink and uplink. Information transfer occurs through the channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the 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:

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

[0089] - 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), where the system information messages can be used by the UE to obtain information on how the cell is configured and how to operate within the cell;

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

[0091] - Dedicated Control Channel (DCCH), which is used to carry control messages to / from a specific UE to configure the UE; and

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

[0093] 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:

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

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

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

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

[0098] - Random Access Channel (RACH), which is used to allow the UE to access the network without any prior scheduling.

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

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

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

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

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

[0104] - Physical Uplink Control Channel (PUCCH), which is used to carry UCI, and the UCI can include HARQ acknowledgments, Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR); and

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

[0106] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figure 5A and Figure 5B 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.

[0107] Figure 2B shows an example NR control plane protocol stack. AsFigure 2B As shown, 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 has radio resource control (RRC) 216 and 226 and NAS protocol 217 and 237 at the top of the NR control plane protocol stack.

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

[0109] RRC 216 and 226 may provide control plane functions between UE 210 and gNB 220 or more generally between UE 210 and the RAN. RRC 216 and 226 may provide control plane functions between UE 210 and gNB 220 via signaling messages called RRC messages. Signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers may be used to transmit RRC messages between UE 210 and the RAN. MAC may multiplex control plane and user plane data into the same transport block (TB). Control plane functions that RRC 216 and 226 may provide include: broadcasting of system information related to the AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of the RRC connection between UE 210 and the 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 passing. As part of establishing the RRC connection, RRC 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between UE 210 and the RAN.

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

[0111] In RRC connected 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 Figure 1B one of the gNB 160 or ng-eNB 162 depicted in Figure 2A and Figure 2B the gNB 220 depicted in

[0112] or any other base station described in the present disclosure. The base station connected to the UE may have an RRC context for the UE. The RRC context, referred to as the UE context, may include 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., related to 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 connected 602, the mobility of the UE may be managed by the RAN (e.g., RAN 104 or NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The serving base station of the UE may request a 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 through a connection release procedure 608 or to RRC inactive 606 through a connection deactivation procedure 610.In RRC idle state 604, an RRC context may not be established for the UE. In RRC idle state 604, the UE may not have an RRC connection to the base station. When in RRC idle state 604, the UE may be in a sleep state most of the time (e.g., to save battery power). The UE may wake up periodically (e.g., once per discontinuous reception cycle) to monitor paging messages from the RAN. The mobility of the UE may be managed by the UE through a procedure called cell reselection. The RRC state may be transitioned from RRC idle state 604 to RRC connected state 602 through a connection establishment procedure 612, which may involve a random access procedure, as discussed in more detail below.

[0113] In RRC inactive state 606, the previously established RRC context is maintained in the UE and the base station. This allows for a quick transition to RRC connected state 602 with reduced signaling overhead compared to the transition from RRC idle state 604 to RRC connected state 602. When in RRC inactive state 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 be transitioned from RRC inactive state 606 to RRC connected state 602 through a connection resume procedure 614, or to RRC idle state 604 through a connection release procedure 616, which may be the same as or similar to connection release procedure 608.

[0114] The RRC state may be associated with a mobility management mechanism. In RRC idle state 604 and RRC inactive state 606, the mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle state 604 and RRC inactive state 606 is to allow the network to be able to notify the UE of events via paging messages without having to broadcast the paging messages across the entire mobile communication network. The mobility management mechanism used in RRC idle state 604 and RRC inactive state 606 may allow the network to track the UE at the cell group level, such that the paging messages can be broadcast on the cells within the cell group in which the UE is currently resident rather than across the entire mobile communication network. The mobility management mechanisms for RRC idle state 604 and RRC inactive state 606 track the UE at the cell group level. These mobility management mechanisms may do so using different granularities of grouping. For example, there may be three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas called a tracking area and identified by a tracking area identifier (TAI).

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

[0116] RAN areas can be used to track UEs at the RAN level. For a UE in the RRC inactive 606 state, a RAN notification area can be assigned to the UE. The RAN notification area can include a list of one or more cell identities, RAI, or TAI. In one example, a base station can belong to one or more RAN notification areas. In one example, a cell can 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 can perform a notification area update to the RAN to update the UE's RAN notification area.

[0117] The base station that stores the RRC context for the UE or the last serving base station of the UE can be referred to as the anchor base station. The anchor base station can maintain the RRC context for the UE at least during the period when the UE remains in the RAN notification area of the anchor base station and / or during the period when the UE remains in the RRC inactive 606 state.

[0118] gNB, such as Figure 1B the gNB 160 in, 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.

[0119] In NR, physical signals and physical channels (regarding Figure 5A and Figure 5BThe (discussed) can be mapped onto an Orthogonal Frequency Division Multiplexing (OFDM) symbol. OFDM is a multi-carrier communication scheme that transmits data through F orthogonal sub-carriers (or tones). Before transmission, the data can be mapped onto 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 considered as if they are in the frequency domain and used as the input to an 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 sine basis functions corresponding to the F orthogonal sub-carriers. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal sub-carriers. 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 symbol provided by the IFFT block can be transmitted over the air interface at the carrier frequency. The F parallel symbol streams can be scrambled using an FFT block before being processed by the IFFT block. This 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 inverse processing can be performed on the OFDM symbol at the receiver using an FFT block to recover the data mapped onto the source symbols.

[0120] Figure 7 An example configuration of an NR frame into which OFDM symbols are grouped is shown. The NR frame can be identified by a System Frame Number (SFN). The SFN can repeat with a period of 1024 frames. As shown, the duration of one NR frame can be 10 milliseconds (ms) and can include 10 sub-frames with a duration of 1 ms each. The sub-frames can be divided into time slots, which include, for example, 14 OFDM symbols per time slot.

[0121] The duration of a time slot can depend on the parameter set of the OFDM symbols 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 mmWave range). The parameter sets can be defined in terms of subcarrier spacing and cyclic prefix duration. For the parameter sets in NR, the subcarrier spacing can be scaled by a power of two from a baseline subcarrier spacing of 15 kHz, and the cyclic prefix duration can be scaled by a power of two from a baseline cyclic prefix duration of 4.7 microseconds. For example, NR defines parameter sets with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 microseconds; 30 kHz / 2.3 microseconds; 60 kHz / 1.2 microseconds; 120 kHz / 0.59 microseconds; and 240 kHz / 0.29 microseconds.

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

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

[0124] Figure 8Shows a single parameter set used across the entire bandwidth of an NR carrier. In other example configurations, multiple parameter sets can be supported on the same carrier.

[0125] NR can 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). Also, in terms of UE power consumption, receiving the full carrier bandwidth may be prohibitive. In one example, to reduce power consumption and / or for other purposes, a UE can adapt the size of its receive bandwidth based on the traffic volume the UE is scheduled to receive. This is referred to as bandwidth adaptation.

[0126] NR defines a bandwidth part (BWP) to support UEs that cannot receive the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP can be defined by a subset of consecutive RBs on a carrier. A UE can 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 can be active. The one or more BWPs can be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell can have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

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

[0129] For an uplink BWP in a 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 reception (e.g., PDCCH or PDSCH) in a downlink BWP according to a set of configured parameters for the downlink BWP (e.g., subcarrier spacing and cyclic prefix duration). The UE may transmit uplink transmission (e.g., PUCCH or PUSCH) in an uplink BWP according to a set of configured parameters (e.g., subcarrier spacing and cyclic prefix length of the uplink BWP).

[0130] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWP in the 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.

[0131] The base station may semi-statically configure a default downlink BWP for the UE within a set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP for 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.

[0132] The base station may configure a BWP inactivity timer value for the UE for the PCell. 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 when: (a) the UE detects DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; or (b) the UE detects DCI indicating an active downlink BWP or an active uplink BWP other than the default downlink BWP or the uplink BWP for unpaired spectrum operation. If the UE does not detect 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., incrementing from zero to the BWP inactivity timer value, or decrementing 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.

[0133] In one 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 DCI indicating that the second BWP is the active BWP and / or in response to the expiration of the BWP inactivity timer (e.g., in the case where the second BWP is the default BWP).

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

[0135] Figure 9 An example of bandwidth adaptation using three configured BWPs of an NR carrier is shown. The UE configured with the three BWPs may switch from one BWP to another at a handover point. In Figure 9 the example shown, the BWPs include: BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and BWP 906 with 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 the BWPs at the handover point. In Figure 9 the example, the UE may switch from BWP 902 to BWP 904 at the handover point 908. The handover at the handover point 908 may occur for any suitable reason, such as in response to the expiration of the BWP inactivity timer (indicating a handover to the default BWP) and / or in response to receiving DCI indicating that BWP 904 is the active BWP. The UE may switch from the active BWP 904 to BWP 906 at the handover point 910 in response to receiving DCI indicating that BWP 906 is the active BWP. The UE may switch from the active BWP 906 to BWP 904 at the handover point 912 in response to the expiration of the BWP inactivity timer and / or in response to receiving DCI indicating that BWP 904 is the active BWP. The UE may switch from the active BWP 904 to BWP 902 at the handover point 914 in response to receiving DCI indicating that BWP 902 is the active BWP.

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

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

[0138] Figure 10A Three CA configurations with two CCs are shown. In the in-band contiguous configuration 1002, the two CCs are aggregated in the same frequency band (band A) and are positioned directly adjacent to each other within the band. In the in-band non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (band A) and are separated by a certain gap within the band. In the inter-band configuration 1006, the two CCs are in different bands (band A and band B).

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

[0140] When using CA, one of the aggregated cells in the aggregated cells for a UE can be referred to as the primary cell (PCell). The PCell can be the serving cell to which the UE is initially connected at RRC connection establishment, re - establishment, and / or handover. The PCell can provide NAS mobility information and security inputs to the UE. The UE can have different PCells. In the downlink, the carrier corresponding to the PCell can be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell can be referred to as the uplink primary CC (UL PCC). Other aggregated cells for the UE can be referred to as secondary cells (SCells). In one example, an SCell can be configured after the PCell is configured for the UE. For example, an SCell can be configured through the RRC connection re - configuration procedure. In the downlink, the carrier corresponding to the SCell can be referred to as the downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell can be referred to as the uplink secondary CC (UL SCC).

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

[0142] The downlink control information of a cell (such as scheduling assignment and scheduling grant) 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. The uplink control information for the aggregated cells (e.g., HARQ acknowledgments 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 cells can be divided into multiple PUCCH groups.

[0143] Figure 10B An example of how the aggregated cells can be configured into one or more PUCCH groups is shown. PUCCH group 1010 and PUCCH group 1050 can each include one or more downlink CCs. In Figure 10BIn the example, PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. PUCCH group 1050 includes three downlink CCs in this example: PCell 1051, SCell 1052, and SCell 1053. One or more uplink CCs can be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs can be configured as the 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) can 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) can be transmitted in the uplink of PSCell 1061. In one example, if Figure 10B the aggregated cells depicted in

[0144] are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell transmits UCI related to the downlink CCs, and the PCell may become overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, overload can be prevented.

[0145] In CA, the multi-carrier nature of the PHY can be exposed to the MAC. In one example, the HARQ entity can operate on the serving cell. Transmission blocks can be generated according to the assignment / grant of each serving cell. The transmission block and potential HARQ retransmissions of the transmission block can be mapped to the serving cell.

[0146] In the downlink, the base station may transmit one or more reference signals (RSs) (e.g., unicast, multicast, and / or broadcast) to the UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as Figure 5A shown). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as Figure 5B shown). The PSS and SSS may be transmitted by the base station and used by the 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.

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

[0148] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as Figure 11A shown in the example), 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., after two symbols) 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.

[0149] The UE may not know the position of the SS / PBCH block in the time domain and the frequency domain (e.g., in the case where the UE is searching for a cell). 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 (e.g., 20 ms), 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 domain and the frequency domain, the UE may determine the positions of the SSS and the PBCH respectively based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one example, the primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. In one example, cell selection / search and / or reselection may be based on the CD-SSB.

[0150] 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 respectively based on the sequences of the PSS and the SSS. The UE may determine the position of the frame boundary of the cell based on the position of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted according to a transmission pattern, where the SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0151] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulating the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or the SS / PBCH block timing index. These parameters may assist the UE in time synchronization with the base station. The PBCH may include the 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 the system information block type 1 (SIB1). The SIB1 may contain the 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 the SIB1. The parameters provided in the MIB may be used to decode the SIB1. The PBCH may indicate the non-existence of the SIB1. Based on the PBCH indicating the non-existence of the SIB1, the UE may point to a frequency. The UE may search for the SS / PBCH block at the frequency pointed to by the UE.

[0152] The UE may assume that one or more SS / PBCH blocks transmitted using 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 having different SS / PBCH block indices.

[0153] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in a spatial direction (e.g., using different beams spanning the coverage area of the cell). In one 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.

[0154] In one example, within the frequency range of a carrier, the base station may transmit multiple SS / PBCH blocks. In one example, the first PCI of the first SS / PBCH block among the multiple SS / PBCH blocks may be different from the second PCI of the second SS / PBCH block among the multiple SS / PBCH blocks. The PCI of SS / PBCH blocks transmitted at different frequency positions may be different or the same.

[0155] CSI-RS may be transmitted by the base station and used by the UE to obtain channel state information (CSI). The base station may configure the UE using one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE using one or more of the same / similar CSI-RS. The UE may measure the one or more CSI-RS. 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-RS. The UE may provide the CSI report to the base station. The base station may perform link adaptation using the feedback provided by the UE (e.g., the estimated downlink channel state).

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

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

[0158] The CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and the control resource set (CORESET) when the downlink CSI-RS and the 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 use the same OFDM symbol for the downlink CSI-RS and the SS / PBCH block when the downlink CSI-RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI-RS are outside the PRBs configured for the SS / PBCH block.

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

[0160] In one example, a transmitter (e.g., a base station) can use a precoder matrix for a portion of the transmission bandwidth. For example, the transmitter can 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 can be different based on the first bandwidth being different from the second bandwidth. The UE can assume the same precoding matrix is used throughout the set of PRBs. The set of PRBs can be represented as a precoding resource block group (PRG).

[0161] The PDSCH can include one or more layers. The UE can assume that at least one symbol with DMRS exists on a layer among the one or more layers of the PDSCH. The higher layer can configure up to 3 DMRSs for the PDSCH.

[0162] Downlink PT-RS can be transmitted by the base station and used by the UE for phase noise compensation. The presence of downlink PT-RS can depend on the RRC configuration. The presence and / or pattern of downlink PT-RS can be configured on a UE-specific basis using a combination of RRC signaling and / or association with one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of downlink PT-RS can be associated with one or more DCI parameters including at least MCS. The NR network can support multiple PT-RS densities defined in the time and / or frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can employ 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. Downlink PT-RS can be restricted to the scheduled time / frequency duration of the UE. Downlink PT-RS can be transmitted on symbols to assist in phase tracking at the receiver.

[0163] The UE can transmit uplink DMRS to the base station for channel estimation. For example, the base station can use uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE can transmit uplink DMRS with PUSCH and / or PUCCH. Uplink DM-RS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration can support the pre-loaded DMRS mode. The pre-loaded DMRS can be mapped on one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS can be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure the UE with the number (e.g., maximum number) of pre-loaded DMRS symbols of PUSCH and / or PUCCH, and the UE can use the pre-loaded DMRS symbols to schedule single-symbol DMRS and / or double-symbol DMRS. The NR network can support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, where the DMRS position, DMRS pattern, and / or scrambling sequence of DMRS can be the same or different.

[0164] PUSCH can include one or more layers, and the UE can transmit at least one symbol with DMRS on the layer(s) present in one or more layers of PUSCH. In one example, the higher layer can configure up to three DMRS for PUSCH.

[0165] Depending on the RRC configuration of the UE, uplink PT-RS (which can be used by the base station for phase tracking and / or phase noise compensation) may or may not be present. The presence and / or pattern of the uplink PT-RS can be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters that can be indicated by DCI for other purposes (e.g., modulation and coding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS can be associated with one or more DCI parameters including at least MCS. The radio network may 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 may employ 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. For example, the uplink PT-RS may be restricted to the scheduled time / frequency duration of the UE.

[0166] The UE may transmit SRS to the 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 employ the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission from the UE. The base station may configure the UE semi-statically 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 SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, the SRS resources in one or more SRS resource sets (e.g., having the same / similar time-domain behavior, being periodic, being aperiodic, etc.) may be transmitted at a certain moment (e.g., simultaneously). The UE may transmit one or more SRS resources in an SRS resource set. The NR network may support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, where the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In one example, at least one DCI format may be employed 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 one example, when PUSCH and SRS are transmitted in the same time slot, the UE may be configured to transmit SRS after the transmission of PUSCH and the corresponding uplink DMRS.

[0167] The base station may semi-statically configure the UE using one or more SRS configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; time-domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and / or sub-frame level period; slot of the periodic and / or aperiodic SRS resource; number of OFDM symbols in the SRS resource; start OFDM symbol of the SRS resource; SRS bandwidth; hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0168] Antenna ports are defined such that a symbol on an antenna port through which it is conveyed can be inferred from a symbol on the same antenna port through which it is conveyed. If the first symbol and the second symbol are transmitted on the same antenna port, the receiver can infer the channel for conveying the second symbol on the antenna port from the channel for conveying the first symbol on the antenna port (e.g., fading gain, multipath delay, etc.). If one or more large-scale properties of the channel through which the first symbol on the first antenna port is conveyed can be inferred from the channel through which the second symbol on the second antenna port is conveyed, 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 receive (Rx) parameters.

[0169] 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 beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., channel state information reference signal (CSI-RS)) and generate a beam measurement report. After establishing an RRC connection with the base station, the UE may perform a downlink beam measurement procedure.

[0170] Figure 11B An example of a channel state information reference signal (CSI-RS) mapped in the time and frequency domains is shown. Figure 11BThe square shown in [description] can represent resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured for the CSI-RS resource configuration by 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 parameter, CSI-RS sequence parameter, code division multiplexing (CDM) type parameter, frequency density, transmission comb, quasi-co-location (QCL) parameter (e.g., QCL-scrambling identity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

[0173] In a beam management procedure, the UE may evaluate (e.g., measure) one or more beam pair links, including the beam pair link of the transmission beam transmitted by the base station and the channel quality of the receive beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters, the one or more beam pair quality parameters including, 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).

[0174] Figure 12AIllustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 can enable UE measurements of the transmission (Tx) beam of a transmission reception point (TRP) (or multiple TRPs), for example to support the selection of one or more base station Tx beams and / or UE Rx beams (shown as ellipses 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 ellipses rotating in the counterclockwise direction indicated by the dashed arrow in the top rows of P1 and P2). Beamforming at the UE can include Rx beam sweeping for a set of beams (shown as ellipses rotating in the clockwise direction indicated by the dashed arrow in the bottom rows of P1 and P3). Procedure P2 can be used to enable UE measurements of the Tx beam of the TRP (shown as an ellipse rotating in the counterclockwise direction indicated by the dashed arrow in the top row of P2). The UE and / or the base station can perform Procedure P2 using a smaller set of beams or beams that are narrower than the set of beams used in Procedure P1. This can be referred to as beam refinement. The UE can 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.

[0175] Figure 12B Illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 can be used to enable the base station to perform measurements on the Tx beam of the UE, for example to support the selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses 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 ellipses rotating in the clockwise direction indicated by the dashed arrow 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 ellipses rotating in the counterclockwise direction indicated by the dashed arrow in the top rows of U1 and U2). When the UE uses a fixed Tx beam, Procedure U2 can be used to enable the base station to adjust its Rx beam. The UE and / or the base station can perform Procedure U2 using a smaller set of beams or beams that are narrower than the set of beams used in Procedure P1. This can be referred to as beam refinement. The UE can perform Procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0176] The UE may initiate a Beam Failure Recovery (BFR) procedure based on detecting 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 beam failure based on the determination that the quality of the beam pair link of the associated control channel is not satisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, expiration of a timer, etc.).

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

[0178] 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 the RRC_IDLE state and / or RRC INACTIVE state may initiate a random access procedure to request 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., uplink transmission for SR when there are no available PUCCH resources) and / or 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.

[0179] Figure 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. Figure 13AThe program shown includes the transmission of four messages: Msg 1 1311, Msg 2 1312, Msg3 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).

[0180] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate to the UE one or more random access channel (RACH) parameters. 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.

[0181] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmitting Msg 1 1311. 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 the association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate the 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 a PRACH opportunity and / or the number of preambles mapped to an SS / PBCH block.

[0182] 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).

[0183] 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 include one or more preambles. The UE can determine a preamble group based on a 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 an 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.

[0184] The UE can determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE can determine the preamble based on path loss measurement, RSRP measurement, and / or the size of Msg 3 1313. As another example, the one or more RACH parameters can indicate: the preamble format; the 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 can use the one or more RACH parameters to configure the 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 can determine the preamble included in Msg 1 1311 based on the association. Msg 1 1311 can be transmitted to the base station via one or more PRACH opportunities. The UE can use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and for determining the PRACH opportunity. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) can indicate the association between the PRACH opportunity and the one or more reference signals.

[0185] If no response is received after the preamble transmission, the UE can perform preamble retransmission. The UE can increase the uplink transmission power for preamble retransmission. The UE can select the initial preamble transmission power based on the path loss measurement value and / or the target received preamble power configured by the network. The UE can determine the retransmission preamble and can ramp up the uplink transmission power. The UE can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp-up step for preamble retransmission. The ramp-up step can 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 can ramp up the uplink transmission power. The UE can count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). For example, if the number of preamble transmissions exceeds the threshold configured by the one or more RACH parameters (e.g., preambleTransMax), the UE can determine that the random access procedure has not been successfully completed.

[0186] 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 has been received by the base station. Msg 2 1312 may include a timing alignment command that can 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 occasion used by the UE 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 occasion starting from the end of the preamble transmission). The one or more symbols may be determined based on the parameter set. The PDCCH may be in a common search space configured by an RRC message (e.g., Type1-PDCCH common search space). 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 the random access procedure. The UE may use a random access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH occasion in which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on the following: OFDM symbol index; slot index; frequency domain index; and / or UL carrier indicator of the PRACH occasion. An example of the RA-RNTI may be as follows:

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

[0188] where s_id may be the index of the first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id may be the index of the first slot of the PRACH occasion in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH occasion 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).

[0189] 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 contention resolution in, for example Figure 13A the contention-based random access procedure shown in. In some scenarios, multiple UEs may transmit the same preamble to the 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 incorrectly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg 3 1313 (e.g., the TC-RNTI included in Msg 2 1312 and / or any other suitable identifier if a C-RNTI is assigned).

[0190] 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 the unique C-RNTI of the UE is detected on the PDCCH, it is determined that the random access procedure has been successfully completed. If a TC-RNTI is included in Msg 3 1313 (e.g., if the UE is in the 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 includes 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 has been successfully completed.

[0191] A UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, the base station may configure two separate RACH configurations for the UE: one for the SUL carrier and the other for the NUL carrier. For random access in a cell configured with an 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 of the random access procedure (e.g., Msg 1 1311 and / or Msg 3 1313) may be retained on the selected carrier. In one or more cases, the UE may switch the uplink carrier during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). For example, the UE may determine and / or switch the uplink carrier for Msg 1 1311 and / or Msg 3 1313 based on a clear channel assessment (e.g., listen-before-talk).

[0192] Figure 13B A two-step contention-free random access procedure is shown. Similar to Figure 13A 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. Figure 13B The procedure shown includes the transmission of two messages: Msg 1 1321 and Msg 2 1322. Msg 1 1321 and Msg 2 1322 may be similar to Figure 13A Msg 1 1311 and Msg 2 1312 shown, respectively, in some aspects. As can be understood from Figure 13A and Figure 13B the contention-free random access procedure may not include messages similar to Msg 3 1313 and / or Msg 4 1314.

[0193] The contention-free random access procedure shown may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. 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 (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC. Figure 13B

[0194] ​After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of 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 an RRC message (e.g., recoverySearchSpaceId). The UE may monitor PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In Figure 13B In the contention-free random access procedure shown, the UE may determine that the random access procedure is successfully completed after the transmission of Msg 1 1321 and the reception of the corresponding Msg 2 1322 or in response to the transmission and the reception. 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 an RAR that includes a preamble identifier corresponding to the preamble transmitted by the UE and / or the RAR includes a MAC sub-PDU with a 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 an acknowledgement of the SI request.

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

[0196] 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. The transport block 1342 may include content similar and / or equivalent to the content of Figure 13A the Msg3 1313 shown. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The UE may receive Msg B 1332 after transmitting Msg A 1331 or in response to the transmission. Msg B 1332 may include content similar and / or equivalent to Figure 13A and Figure 13B the Msg 2 1312 (e.g., RAR) shown and / or Figure 13A the content of the Msg 4 1314 shown.

[0197] The UE can initiate a call for licensed spectrum and / or unlicensed spectrum. Figure 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.

[0198] 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.

[0199] The transmission 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., transmission block 1342).

[0200] 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.

[0201] Downlink control signaling may include: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transmission format; slot format information; preemption indication; power control command; and / or any other suitable signaling. The UE may receive downlink control signaling in the payload transmitted by the base station on the 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.

[0202] The base station may append 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 the identifier of the UE (or the identifier of the group of UEs). Scrambling the CRC parity bits with the identifier may include modulo-2 addition (or 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).

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

[0204] 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 the scheduling of PUSCH in the 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 the scheduling of PUSCH in the cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for the scheduling of PDSCH in the 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 the scheduling of PDSCH in the cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide time 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 no transmission is expected for the UE. DCI format 2_2 may be used to transmit the transmission power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used to transmit a set of TPC commands for SRS transmission by one or more UEs. DCI formats with new functions may be defined in future releases. The DCI formats may have different DCI sizes or may share the same DCI size.

[0205] After scrambling the DCI with an RNTI, the base station may process the DCI with channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the encoded and modulated DCI on resource elements used for and / or configured for the PDCCH. Based on the payload size of the DCI and / or the coverage area of the base station, the base station may transmit the DCI via a PDCCH that occupies 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. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include resource blocks in an OFDM symbol. The mapping of the encoded and modulated DCI on resource elements may be based on the mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

[0206] Figure 14A An example of a CORESET configuration for a bandwidth part is shown. The base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources in which the UE attempts to decode DCI using one or more search spaces. The base station may configure the CORESET in the time-frequency domain. In Figure 14A the example, a first CORESET 1401 and a second CORESET 1402 appear at the first symbol in a time slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 appears at the third symbol in the time slot. A 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.

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

[0208] The base station may transmit an RRC message to the UE, including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate the association between the search space set and the CORESET. The search space set may include 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 at each aggregation level; the PDCCH monitoring period and PDCCH monitoring pattern; 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).

[0209] As Figure 14B 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 (e.g., interleaved or non-interleaved and / or mapping parameters) of the CORESET based on the configuration parameters of the CORESET. The UE may determine the number of search space sets configured on the CORESET (e.g., up to 10) based on the RRC message. The UE may monitor the set of PDCCH candidates according to the configuration parameters of the search space set. The UE may monitor the set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. The monitoring may include decoding one or more PDCCH candidates in the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding the DCI content of one or more PDCCH candidates, which has 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. The 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., the scrambling 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 assignment, uplink grant, power control, slot format indication, downlink preemption, etc.).

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

[0211] There can be five PUCCH formats, and the UE can 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 can have a length of one or two OFDM symbols and can include two or fewer bits. If the transmission is more than one or two symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bits) with a positive or negative SR is one or two, the UE can transmit the UCI in the PUCCH resource using PUCCH format 0. PUCCH format 1 can occupy a number between four and fourteen OFDM symbols and can include two or fewer bits. If the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two, the UE can use PUCCH format 1. PUCCH format 2 can occupy one or two OFDM symbols and can include more than two bits. If the transmission is more than one or two symbols and the number of UCI bits is two or more, the UE can use PUCCH format 2. PUCCH format 3 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. If the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code, the UE can use PUCCH format 3. PUCCH format 4 can occupy a number between four and fourteen OFDM symbols and can include more than two bits. If the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code, the UE can use PUCCH format 4.

[0212] The base station can transmit the configuration parameters of multiple PUCCH resource sets to the UE using, for example, RRC messages. The multiple PUCCH resource sets (e.g., up to four sets) can be configured on the uplink BWP of the cell. The PUCCH resource set can be configured with: a PUCCH resource set index; multiple PUCCH resources (e.g., pucch-Resourceid) having PUCCH resources identified by PUCCH resource identifiers; and / or multiple (e.g., maximum number) UCI information bits that the UE can transmit using one of the multiple PUCCH resources in the PUCCH resource set. When multiple PUCCH resource sets are configured, the UE can select one PUCCH resource set (e.g., HARQ-ACK, SR, and / or CSI) from the multiple PUCCH resource sets 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 can 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 can select the second PUCCH resource set with 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 can select the third PUCCH resource set with 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 the third value (e.g., 1406), the UE can select the fourth PUCCH resource set with a PUCCH resource set index equal to "3".

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

[0214] Figure 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 can be part of a mobile communication network, such as Figure 1A the mobile communication network 100 shownFigure 1B The mobile communication network 150 or any other communication network shown. Figure 15 Only one wireless device 1502 and one base station 1504 are shown, 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 or similar configurations as those shown. Figure 15 shown.

[0215] The base station 1504 can connect the wireless device 1502 to a core network (not shown) through radio communication via an air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 through the air interface 1506 is called the downlink, while the communication direction from the wireless device 1502 to the base station 1504 through the air interface is called the uplink. The downlink transmission and the uplink transmission can be separated using FDD, TDD, and / or some combination of the two duplexing techniques.

[0216] In the downlink, the data to be sent from the base station 1504 to the wireless device 1502 can be provided to the processing system 1508 of the base station 1504. The data can be provided to the processing system 1508 through, for example, the core network. In the uplink, the data to be sent from the wireless device 1502 to the base station 1504 can be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 can implement layer 3 and layer 2 OSI functions to process the data for transmission. Layer 2 can include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer regarding Figure 2A , Figure 2B , Figure 3 and Figure 4A . The layer 3 can include the RRC layer regarding Figure 2B .

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

[0218] At base station 1504, receive processing system 1512 can receive an uplink transmission from wireless device 1502. At wireless device 1502, receive processing system 1522 can receive a downlink transmission from base station 1504. Receive processing system 1512 and receive processing system 1522 can implement layer 1 OSI functions. Layer 1 can include regarding Figure 2A , Figure 2B , Figure 3 and Figure 4A of the PHY layer. For receive processing, the PHY layer can 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.

[0219] As Figure 15 shown, wireless device 1502 and base station 1504 can include multiple antennas. The multiple antennas can 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, wireless device 1502 and / or base station 1504 can have a single antenna.

[0220] Processing system 1508 and processing system 1518 can be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) can store computer program instructions or code that can be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions discussed in this application. Although Figure 15 not shown, transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 can be coupled to a memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code that can be executed to perform one or more of their respective functions.

[0221] Processing system 1508 and / or 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 devices, discrete gates and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of the following: signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and base station 1504 to operate in a wireless environment.

[0222] Processing system 1508 and / or processing system 1518 may be respectively connected to one or more peripheral devices 1516 and one or more peripheral devices 1526. 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 functions, such as speakers, microphones, keyboards, displays, touchpads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulation (FM) radio units, media players, Internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or 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 above-mentioned one or more peripheral devices. The processing system 1518 in the wireless device 1502 may receive power from a power supply and / or may be configured to distribute power to other components in the wireless device 1502. The power supply may include one or more power sources, such as batteries, solar cell units, fuel cell units, or any combination thereof. Processing system 1508 and / or processing system 1518 may be respectively connected to GPS chipset 1517 and GPS chipset 1527. GPS chipset 1517 and GPS chipset 1527 may be configured to provide the geographical location information of wireless device 1502 and base station 1504, respectively.

[0223] Figure 16AShows an example structure for uplink transmission. The baseband signal representing the 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 the scrambled bits to generate complex-valued symbols; mapping the complex-valued modulation symbols to one or more transport layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of the 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 so on. In one example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a Figure 16A CP-OFDM signal for uplink transmission may be generated. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0224] Figure 16B Shows an example structure for modulating and upconverting a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal of an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering may be employed before transmission.

[0225] Figure 16C Shows an example structure for downlink transmission. The baseband signal representing the physical downlink channel may perform one or more functions. The one or more functions may include: scrambling the coded bits in the codeword to be transmitted on the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols to one or more transport layers; precoding the complex-valued modulation symbols on the layer for transmission on an antenna port; mapping the complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and so on. These functions are shown as examples, and it is expected that other mechanisms may be implemented in various embodiments.

[0226] Figure 16D Shows another example structure for modulating and upconverting a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal of an antenna port. Filtering may be employed before transmission.

[0227] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for a plurality of cells (e.g., a primary cell, a secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the wireless device for 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, etc. For example, the configuration parameters may include parameters indicating values of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0228] Once started, a timer may begin to run and continue running until it is stopped or until it expires. If the timer is not running, it may be started, or if it is running, it may be restarted. A timer may be associated with a value (e.g., the timer may start or restart from a certain value, or may start from zero and expire once it reaches the value). The duration of the timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window of a 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 to implement a timer may be used to measure the time period / window of a procedure. For example, a random access response window timer may be used to measure the time window for receiving a random access response. In one example, instead of starting and expiring a random access response window timer, the time difference between two timestamps may be used. When the timer is restarted, the measurement process of the time window may be restarted. Other example embodiments may be provided to restart the measurement of the time window.

[0229] A satellite may include a spaceborne / aerial vehicle (e.g., a satellite, a balloon, a spacecraft, a high-altitude communication platform, an unmanned / piloted aerial vehicle system, a spaceborne platform, a drone, etc.). For example, a spaceborne vehicle may provide structure, power, command, telemetry, attitude control for a satellite, and may possibly provide an appropriate thermal environment, radiation shielding. A satellite may be referred to as, for example, an NTN base station. A satellite may be referred to as, for example, a (service) satellite. A satellite may be referred to as, for example, an NTN payload. A satellite may include, for example, an NTN payload. For example, an NTN payload may be a network node carried on a satellite. A satellite may, for example, orbit the Earth.

[0230] A satellite can be part of a bent pipe / transparent payload non-terrestrial network (NTN) communication link / system. For example, based on the satellite being part of a bent pipe / transparent payload NTN system, the satellite can forward signals with amplification between the service link and the feeder link. For example, based on the satellite being part of a bent pipe / transparent payload NTN system, the satellite can forward signals with frequency change / conversion / shifting between the service link and the feeder link. For example, based on the satellite being part of a bent pipe / transparent payload NTN system, the satellite can operate as a repeater. For example, based on the satellite being part of a bent pipe / transparent payload NTN system, the satellite can operate as a relay node. For example, based on the satellite being part of a bent pipe / transparent payload NTN system, the satellite can operate as a regenerator. The service link can connect the satellite and a wireless device on Earth. The feeder link can connect the satellite and an NTN gateway on Earth. The terrestrial base station can include the NTN gateway. The terrestrial base station can be connected to the core network.

[0231] A wireless device can transmit an uplink signal to the satellite (or NTN base station). The satellite can transmit the uplink signal to the terrestrial base station (or NTN gateway). The terrestrial base station can transmit the uplink signal to the core network. The satellite can transmit the uplink signal to a different satellite, for example, on an inter-satellite link / via an inter-satellite link.

[0232] A wireless device can receive a downlink signal from the satellite (or NTN base station). The satellite can receive the downlink signal from the terrestrial base station (or NTN gateway). The satellite can receive the downlink signal from a different satellite, for example, on an inter-satellite link / via an inter-satellite link. The terrestrial base station can receive the downlink signal from the core network.

[0233] The base station / gNB / eNB in NTN can include the NTN gateway. The base station / gNB / eNB in NTN can include a satellite / NTN base station / NTN payload. The base station / gNB / eNB in NTN can include a feeder link. The feeder link can connect the NTN gateway and the satellite. The base station / gNB / eNB in NTN can include non-NTN infrastructure that performs gNB / eNB functions. The non-NTN infrastructure can be referred to as, for example, a terrestrial base station / terrestrial gNB / terrestrial eNB. The base station / gNB / eNB in NTN (or a part of the base station / gNB / eNB) can be referred to as, for example, an NTN service link allocation system. In one example, the NTN gateway can be referred to as a terrestrial base station / terrestrial gNB / terrestrial eNB.

[0234] A satellite can be part of a regenerative payload NTN communication link / system. The satellite can be equipped with onboard processing. The onboard processing can include demodulating and decoding the received signals. For the service link and the feeder link, the demodulation and decoding procedures can be different. For example, the onboard processing can include at least two demodulation procedures and at least two decoding procedures. The at least two demodulation procedures can include a first demodulation procedure and a second demodulation procedure. The at least two decoding procedures can include a first decoding procedure and a second decoding procedure. For example, the satellite can apply the first demodulation procedure to the signals received by the satellite on the feeder link. The satellite can apply the second demodulation procedure to the signals received by the satellite on the service link. For example, the satellite can apply the first decoding procedure to the signals received by the satellite on the feeder link. The satellite can apply the second decoding procedure to the signals received by the satellite on the service link. The onboard processing can include regenerating signals. For the service link and the feeder link, the regeneration procedures can be different. For example, the onboard processing can include at least two regeneration procedures. The at least two regeneration procedures can include a first regeneration procedure and a second regeneration procedure. For example, the satellite can apply the first regeneration procedure to the signals received by the satellite on the feeder link. The satellite can apply the second regeneration procedure to the signals received by the satellite on the service link.

[0235] Figure 17A and Figure 17B is an example of an NTN architecture according to an embodiment of the present disclosure, where the satellite serves as part of the network.

[0236] Figure 17A FIG. shows an example NTN architecture corresponding to a transparent satellite model according to an aspect of an embodiment of the present disclosure. The NTN architecture can include a wireless device, a satellite, an NTN gateway, a base station or gNB / eNB, a core network, and / or a data network. The satellite can act as a remote radio unit (RRU) communicating with the NTN gateway. The satellite can perform frequency conversion and / or radio frequency (RF) amplification in the uplink direction. The satellite can perform frequency conversion and / or RF amplification in the downlink direction. The NTN gateway can be connected to the base station. In one example, the base station can be on the ground. The wireless device can transmit and receive via the satellite (e.g., as a relay party or repeater or regenerator). The satellite (e.g., RRU) can correspond to an analog RF repeater that relays signals from the service link (e.g., between the satellite and the wireless device) to the feeder link (e.g., between the NTN gateway and the satellite), and vice versa.

[0237] Figure 17BShows an example NTN architecture corresponding to a regenerative satellite model according to an aspect of an embodiment of the present disclosure. The NTN architecture may include a wireless device, a satellite, an NTN gateway, a core network, etc. The satellite may regenerate signals received from the Earth (e.g., from a wireless device or from an NTN gateway). The satellite may regenerate signals by decoding and re - encoding the signals. The satellite may regenerate signals by amplifying the signals. The satellite may regenerate signals by frequency - shifting the signals. The satellite may regenerate signals by changing the carrier frequency of the signals. In one example, the satellite may act as a base station.

[0238] In one example, NTN may be / include an NTN geostationary (cell) system / coverage. The NTN geostationary (cell) system / coverage may be referred to as, for example, an NTN geocentric (cell) system / coverage. One or more satellites in the NTN geostationary (cell) system / coverage may cover the same (geographical) area all / most / much of the time. The one or more satellites in the NTN geostationary system may be one or more geostationary / geosynchronous orbit (GEO / GSO) satellites. In one example, the NTN geostationary (cell) system / coverage may be rationed by beams that continuously cover the same geographical area at all times.

[0239] In one example, NTN may be / include an NTN quasi - geostationary (cell) system / coverage. The NTN quasi - geostationary (cell) system may be referred to as, for example, an NTN quasi - geocentric (cell) system / coverage. One or more satellites in the NTN quasi - geostationary (cell) system / coverage may cover a (geographical) area for a fixed duration and then cover a different (geographical) area in the next fixed duration. In one example, the NTN quasi - geostationary (cell) system / coverage may be rationed by beams that cover one geographical area for a limited time period and cover a different geographical area during another period. For example, the one or more satellites in the NTN quasi - geostationary (cell) system / coverage may cover a first (geographical) area at a first time. The one or more satellites in the NTN quasi - geostationary (cell) system / coverage may cover the first (geographical) area at a second time. The one or more satellites in the NTN quasi - geostationary (cell) system / coverage may cover a second (geographical) area at a third time. The one or more satellites in the NTN quasi - geostationary (cell) system / coverage may use steerable beams (and / or beam steering). The one or more satellites in the NTN quasi - geostationary (cell) system / coverage may be one or more non - GSO (NGSO) or non - GEO satellites (e.g., one or more low - Earth orbit (LEO) satellites, one or more medium - Earth orbit (MEO) satellites, etc.).

[0240] In one example, the NTN may be / include an NTN Earth moving (cell) system / coverage. The (geographical) area covered by one or more satellites in the NTN Earth moving (cell) system / coverage may move / slide on the Earth's surface. In one example, the NTN Earth moving (cell) system / coverage may be allocated by beams whose coverage areas slide on the Earth's surface. For example, the one or more satellites in the NTN Earth moving (cell) system / coverage may cover a first (geographical) area at a first time. The one or more satellites in the NTN Earth moving (cell) system / coverage may cover a second (geographical) area at a second time. The one or more satellites in the NTN Earth moving (cell) system / coverage may not use / generate steerable beams (or beam steering). The one or more satellites in the NTN Earth moving (cell) system / coverage may use / generate, for example, fixed beams. The one or more satellites in the NTN Earth moving (cell) system / coverage may use / generate, for example, non-steerable beams. The one or more satellites in the NTN Earth moving (cell) system / coverage may be one or more non-GSO (NGSO) or non-GEO satellites (e.g., one or more low Earth orbit (LEO) satellites, one or more medium Earth orbit (MEO) satellites, etc.).

[0241] In one example, one or more satellites in the NTN may be one or more NGSO / NGEO satellites. The NTN may be / include, for example, an NTN Earth fixed (cell) system / coverage. The NTN may be / include, for example, an NTN quasi-Earth fixed (cell) system / coverage. In another example, one or more satellites in the NTN may be one or more GSO / GEO satellites. The NTN may be / include, for example, an NTN Earth fixed (cell) system / coverage.

[0242] Figure 18 Examples of the deployment of multiple satellites are shown. In one example, satellites may be placed in a low Earth orbit (LEO) at an altitude between 250 km and 1500 km, with an orbital period in the range of 90 minutes to 130 minutes. The average orbital velocity required to maintain a stable LEO may be 7.8 km / s and may decrease as the orbital altitude increases. The average orbital velocity of a 200 km circular orbit may be 7.79 km / s. The average orbital velocity of a 1500 km circular orbit may be 7.12 km / s. From the perspective of a given point on the Earth's surface, the positioning of LEO satellites may change.

[0243] In one example, satellites may be placed in a medium Earth orbit (MEO) at an altitude between 5000 km and 20000 km, with an orbital period in the range of 2 hours to 14 hours.

[0244] In one example, a satellite can be placed in a geostationary earth orbit (GEO) at an altitude of 35,786 km and directly above the equator. This can correspond to an orbital velocity of 3.07 km / s and an orbital period of 1,436 minutes, which is equivalent to almost one sidereal day (23.934461223 hours). From the perspective of a given point on the earth's surface, the position of the GEO may not move.

[0245] In one example, NTN can be a network or network segment that uses a spaceborne vehicle to carry a transmission equipment relay node or base station. While a terrestrial network is a network located on the earth's surface, NTN can be a network that uses satellites as an access network, a backhaul interface network, or both. The satellite can generate several beams over a given area.

[0246] In one example, the coverage area of a satellite's beam can be elliptical (e.g., it can be considered a cell). The coverage area of the beam can be referred to as a point beam. The coverage area of the beam can be referred to as the beam coverage area. The coverage area of the beam can move above the earth's surface as the satellite moves. The coverage area of the beam can be earth-fixed, where the satellite uses one or more beam pointing mechanisms to compensate for its movement. The size of the beam coverage area can depend on the system design and can range from dozens of kilometers to thousands of kilometers.

[0247] The coverage area of one or more beams can be considered a cell. The coverage area of one or more beams can be referred to as a beam. The beam can be associated with one or more aspects of the cell. For example, the beam can be associated with a cell-specific reference signal (CRS), e.g., a beam-specific reference signal. In another example, the beam can be associated with a physical cell ID (PCI) or a physical beam ID. The terms cell and beam can be used interchangeably to refer to the one or more coverage areas of at least one beam.

[0248] A wireless device can be within the range (or coverage area) of a serving / primary cell / beam. One or more cells / beams (e.g., non-serving / adjacent / auxiliary / candidate cells / beams) can be installed within the range (or coverage area) of the serving cell / beam.

[0249] In one example, the propagation delay (e.g., between a satellite and the ground or between multiple satellites) can be the amount of time it takes for the head of a signal to travel from the sender to the receiver, and vice versa. For the uplink, the sender can be a wireless device and the receiver can be a base station / access network. For the downlink, the sender can be a base station / access network and the receiver can be a wireless device. The propagation delay can vary according to the distance between the sender and the receiver.

[0250] Figure 19Shows an example of the propagation delay of NTN corresponding to different heights. The propagation delay in the figure may be one-way delay. In one example, the one-way delay can be the amount of time required to propagate from a terminal to a receiver (e.g., a base station, eNB, gNB, RRU of a base station) via a telecommunications system.

[0251] In one example, for a transparent satellite model in the GEO case, the round-trip propagation time (RTT) can include a service link delay (e.g., between the satellite and the wireless device) and a feeder link delay (e.g., between the NTN gateway and the satellite). The RTT can be four times 138.9 milliseconds (approx. 556 milliseconds).

[0252] In one example, if processing time and congestion are considered, the RTT of a GEO satellite can exceed several seconds. In one example, the RTT of a terrestrial network (e.g., NR, E-UTRA, LTE) can be negligible. The RTT of a terrestrial network can be less than 1 millisecond. In one example, the RTT of a GEO satellite can be hundreds of times longer than the RTT of a terrestrial network.

[0253] In one example, the maximum RTT of a LEO satellite with a transparent payload at an altitude of 600 km can be 25.77 milliseconds. The differential RTT can be 3.12 milliseconds. The differential RTT within the beam of the satellite can be calculated based on the maximum diameter of the beam coverage area at the lowest point. In one example, the differential RTT can imply the difference in communication delays that two wireless devices (e.g., one wireless device can be near the edge of a cell / beam while the other wireless device can be near the center of the cell / beam) may experience when communicating with an NTN node. In one example, for a LEO satellite with a transparent payload at an altitude of 1200 km, the maximum RTD can be 41.77 milliseconds. The differential RTT can be 3.18 milliseconds.

[0254] Figure 20A and Figure 20B Shows an example of a service link with the maximum propagation delay of a cell / beam. In one example, NTN can include at least one of the following: a transparent satellite, a feeder link, a terrestrial gNB / eNB, a cell / beam, and the service links of two wireless users.

[0255] In one example, as Figure 20A and / or Figure 20BAs shown, the first wireless device (e.g., UE1) may be located closer to the cell / beam center than the second wireless device (e.g., UE2). In one example, the first wireless device (e.g., UE1) may not be at / near the cell / beam center, but may otherwise be closer to the satellite than the second wireless device (UE2). Compared with the second wireless device (e.g., UE2), UE1 may have a smaller RTT. For example, for an NTN with a LEO satellite having a transparent payload and a height of 1200 km, the RTT experienced by UE1 may be 3.18 milliseconds lower than the RTT experienced by UE2.

[0256] In one example, the RTT may be the sum / addition / summation of a common delay and a wireless device-specific delay. The common delay may include, for example, the delay between the base station and the reference point. The wireless device-specific delay may include, for example, the delay between the wireless device and the reference point. In another example, the common delay may include the delay between the satellite and the reference point. The wireless device-specific delay may include the delay between the wireless device and the satellite.

[0257] In one example, the reference point of the NTN may be provided by the base station to the wireless device in a downlink message (e.g., via an SIB or RRC message). In one example, the reference point of the NTN may be predefined / preconfigured in / within the wireless device. The reference point may split the overall link between the wireless device and the base station into at least two links. The at least two links may include a common link and a wireless device-specific link. In one example, the common link may be a feeder link. In one example, the wireless device-specific link may be a service link. The propagation delay of the common link may be the common delay. In one example, the common delay may be the same for multiple wireless devices in a cell / beam. In another example, for multiple wireless devices in all cells / beams served by one satellite, the common delay may be the same. The propagation delay of the wireless device-specific link may be the wireless device-specific delay. The wireless device-specific delay may be different for different wireless devices in a cell / beam.

[0258] In one example, the reference point may be at a non-terrestrial location on the service link. In one example, the common delay may correspond to the propagation delay between the reference point and the terrestrial gNB / eNB. In one example, the common delay may correspond to the propagation delay between the reference point and the NTN gateway.

[0259] In one example, the reference point may be at a location in a cell / beam on the earth. The common delay may include the propagation delay between the reference point and the satellite and the feeder link delay. The wireless device-specific delay may include the propagation delay of the signal between the location of the wireless device and the reference point.

[0260] In one example, a wireless device may receive information from a base station in a downlink message (e.g., an SIB or an RRC message) to estimate the position of a satellite. The wireless device may use the position of the satellite to estimate / determine / deduce / calculate the propagation delay of the serving link. For example, the wireless device may receive satellite ephemeris via a downlink message (e.g., an SIB or an RRC message). For example, the wireless device may receive satellite ephemeris via one or more configuration parameters from the base station. The satellite ephemeris may indicate a state vector that indicates the coordinates of the satellite. The satellite ephemeris may indicate the orbital velocity of the satellite. In another example, the satellite ephemeris may include one or more Keplerian orbital elements or orbital elements or Keplerian elements, such as the semi-major axis, eccentricity, argument of perigee, longitude of the ascending node, inclination, and the true anomaly at the satellite epoch time. The wireless device may determine / deduce / calculate / estimate the position of the satellite based on the satellite ephemeris. For example, the wireless device may use the satellite ephemeris to determine / deduce / infer / calculate / estimate the Cartesian coordinates of the satellite at any given moment.

[0261] In one example, the satellite ephemeris may be broadcast periodically by the satellite as part of system information (e.g., an RRC message or an SIB). The system information message / signal / command (e.g., an SIB) may include an indication that indicates the rate at which the calculation of the RTT performed by the wireless device based on the satellite ephemeris should be updated. In one example, the wireless device may adjust the calculated RTT during a timer period based on the indicated rate. The timer period may indicate the duration between two consecutive receptions of the satellite ephemeris by the wireless device.

[0262] In one example, if the periodicity of broadcasting the satellite ephemeris is relatively long, the satellite ephemeris may not accurately provide the position of the satellite. For example, the position of the satellite determined by the wireless device may be inaccurate due to the expiration of the satellite ephemeris. The periodicity of broadcasting the satellite ephemeris may be set such that the satellite ephemeris can be updated before expiration. The periodicity of broadcasting the satellite ephemeris may depend, for example, on the altitude of the satellite. For example, the periodicity of broadcasting the satellite ephemeris of a GEO satellite may be greater than that of a LEO satellite. The periodicity of broadcasting the satellite ephemeris may further depend on the speed of the satellite. For example, a wireless device on the Earth may have visibility of at least two satellites. The at least two satellites may be a first satellite and a second satellite. The first satellite may move at a first speed. The second satellite may move at a second speed. The first speed may be greater / higher than the second speed. The periodicity of broadcasting the satellite ephemeris of the first satellite may be less than that of the second satellite. Broadcasting the satellite ephemeris may increase signaling overhead. Broadcasting the satellite ephemeris may increase the communication latency in NTN.

[0263] In one example, satellite ephemeris may not accurately provide the position of a satellite when needed. For example, the position of a satellite determined by a wireless device may be accurate when the wireless device receives the satellite ephemeris, but may be inaccurate when the wireless device uses the determined satellite position, for example, for random access preamble transmission (e.g., MSG1) or random access MSG3 transmission or MSG5 transmission.

[0264] In one example, if the movement of a satellite drifts gradually from the predicted orbit at a wireless device using satellite ephemeris, the satellite ephemeris may not accurately provide the position of the satellite.

[0265] In one example, satellite ephemeris data can provide a correction margin to a wireless device to help the wireless device compensate for the inaccuracy of the satellite ephemeris data. In one example, the wireless device can use the correction margin of the satellite ephemeris data to partially account for the drift of the satellite from the satellite orbit.

[0266] In one example, timing advance (e.g., in NTN 5G NR) can be based on orthogonal frequency division multiple access (OFDMA) as a multiple access scheme in the uplink. Transmissions from different wireless devices in a cell / beam may need to be time-aligned at the gNB / eNB and / or satellite to maintain uplink orthogonality. Time alignment can be achieved by using different timing advance (TA) values at different wireless devices to compensate for their different propagation delays or round-trip times (RTTs). In one example, transmissions from different wireless devices in a cell / beam may need to be time-aligned at the gNB / eNB. The TA value can include the serving link delay and the feeder link delay. In another example, transmissions from different wireless devices in a cell / beam may need to be time-aligned at the satellite. The TA value can include the serving link delay. In another example, transmissions from different wireless devices in a cell / beam may need to be time-aligned at a non-terrestrial point on the feeder link. The TA value can include a non-zero fraction of the serving link delay and the feeder link delay. In another example, transmissions from different wireless devices in a cell / beam may need to be time-aligned at a non-terrestrial point on the serving link. The TA value can include a non-zero fraction of the serving link delay.

[0267] In NTN, the size of a cell / beam can be larger than that of a cell in a terrestrial network. For example, the maximum coverage area of a GEO NTN cell / beam can be 3500 kilometers, and the maximum coverage area of a LEO NTN cell / beam can be 1000 kilometers. The size of a cell in a terrestrial network can be less than one kilometer to several kilometers. Due to the large coverage area of the beam / cell, different NTN wireless devices may experience different propagation delays between the satellite and the wireless device. Due to the large coverage area of the beam / cell, different NTN wireless devices may experience different propagation delays between the NTN gateway and the wireless device. Due to the large coverage area of the beam / cell, different NTN wireless devices may experience different propagation delays between the gNB / eNB and the wireless device.

[0268] The differential delay between two wireless devices can indicate the difference between the one-way propagation delays of the serving links for the two wireless devices. The maximum differential delay can indicate the difference between the maximum one-way delay in the serving link / the serving link (i.e., the one-way propagation delay experienced by the wireless device located at the point farthest from the satellite) and the minimum one-way delay (i.e., the one-way propagation delay experienced by the wireless device located at the point closest to the satellite). For example, a wireless device located / near the center of the cell / beam can be located at the point closest to the satellite. A wireless device located / near the edge / boundary of the cell / beam can be located at the point farthest from the satellite. The maximum differential delay of an NTN based on LEO satellites can be 3.18 milliseconds. The maximum differential delay of an NTN based on GEO satellites can be 10.3 milliseconds. The maximum differential delay in a terrestrial network can be less than 1 millisecond. The base station can receive random access preambles transmitted by different NTN wireless devices at the same RACH opportunity / within / on different times based on the differential delay between the wireless devices.

[0269] In one example, when operating in NTN, the base station can use an extended preamble reception window to receive random access preambles transmitted in / on / at the same RACH occasion. For example, the base station can use a preamble reception window that starts at [RACH occasion timing + 2 * minimum one-way propagation delay] and ends at [RACH occasion + 2 * maximum one-way propagation delay]. Using an extended preamble reception window can increase the time gap between two consecutive supported RACH occasions. For example, the time gap between two consecutive supported RACH occasions can be greater than 2 * (maximum differential delay). A finite number of PRACH configurations (e.g., 3 for GEO satellite-based NTN) can support or allow a time gap between two consecutive supported RACH occasions to be greater than 2 * (maximum differential delay). Based on the network traffic type, a finite number of PRACH configurations can support a small number of wireless devices in a given area, i.e., a finite number of PRACH configurations can support a small wireless device density. For example, when each wireless device accesses the RACH once every 10 minutes for an NTN served by a LEO satellite with a cell / beam coverage area of 26,000 square kilometers, the supported wireless device density can be 51 wireless devices per square kilometer. In one example, the wireless device can pre-compensate the random access preamble transmission based on the TA value to compensate for the long RTT, thereby allowing a smaller preamble reception window (e.g., 1 ms) at the base station. This can allow a larger number of wireless device density (e.g., 60,000 wireless devices per square kilometer). In one example, the random access procedure can be a four-step random access procedure. In one example, the random access procedure can be a two-step random access procedure.

[0270] Figure 21 An example of NTN is shown. Figure 21 The gNB depicted in can be subdivided into a non-NTN infrastructure gNB function and an NTN service link allocation system. Figure 21The NTN infrastructure shown can be (considered) subdivided into an NTN service link allocation system and NTN control functions. The NTN service link allocation system can include one or more NTN payloads and NTN gateways. The NTN payloads can be carried on spaceborne (or airborne) vehicles. The NTN payloads can provide structure, power, command, telemetry, and / or attitude control for the satellites. The NTN payloads can provide an appropriate thermal environment and / or radiation shielding. The NTN service link allocation system can map the NR-Uu radio protocol onto the radio resources (e.g., beams, channels, Tx power, etc.) of the NTN infrastructure. The NTN control functions can control the spaceborne (or airborne) vehicles. The NTN control functions can control one or more radio resources (e.g., NTN payloads and NTN gateways) of the NTN infrastructure. The NTN control functions can provide control data, such as satellite ephemeris, to the non-NTN infrastructure gNB functions of the gNB.

[0271] NTN can provide non-terrestrial access to wireless devices by means of NTN payloads and NTN gateways, depicting the service link between the NTN payload and the wireless device and the feeder link between the NTN gateway and the NTN payload. The NTN payloads can (also) be referred to as satellites.

[0272] The NTN payloads can transparently forward the radio protocol received from the wireless devices (e.g., via the service link) to the NTN gateways (e.g., via the feeder link), and vice versa. The NTN payloads can support the following connectivity:

[0273] - The gNB can serve multiple (e.g., more than one, multiple, etc.) NTN payloads;

[0274] - The NTN payloads can be served by multiple (e.g., more than one, multiple, etc.) gNBs.

[0275] The NTN payloads can change the carrier frequency before retransmitting it on the service link and vice versa (e.g., correspondingly on the feeder link).

[0276] For NTN, in addition to the network identity, the following can also be applied:

[0277] - The tracking area can correspond to a fixed geographical area. Any corresponding mapping can be configured in the radio access network (RAN).

[0278] - The mapped cell identity (ID).

[0279] A non-geostationary orbit (NGSO) may include a low Earth orbit at an altitude approximately between 300 km and 1500 km. The NGSO may include a medium Earth orbit at an altitude approximately between 7000 km and 25000 km.

[0280] At least three types of service links may be supported:

[0281] - Earth-fixed (system / service link / cell / cell system): Beam allocation that continuously covers the same geographical area at many (e.g., all) times (e.g., in the case of a GSO satellite);

[0282] - Quasi-Earth-fixed (system / service link / cell / cell system): Beam allocation that covers a geographical area within a limited period and covers a different geographical area during another period (e.g., in the case where an NGSO satellite generates steerable beams);

[0283] - Earth-mobile (system / service link / cell / cell system): Beam allocation where the coverage area slides above the Earth's surface (e.g., in the case where an NGSO satellite generates fixed or non-steerable beams).

[0284] Using an NGSO satellite, a gNB may provide quasi-Earth-fixed cell coverage or Earth-mobile cell coverage. A gNB operating with a GSO satellite may provide Earth-fixed cell coverage.

[0285] A wireless device supporting NTN may have GNSS capabilities.

[0286] In the case of NGSO NTN, service link handover may refer to a change of serving satellite.

[0287] In NTN, a wireless device may be configured to report the timing advance (TA) of the wireless device. The wireless device may be configured to report the TA, for example, during a random access procedure in the RRC_IDLE and / or RRC_INACTIVE states. The wireless device may be configured to report the TA, for example, during a random access procedure in the RRC_CONNECTED state (e.g., using event-triggered reporting; for an RRC reconstruction procedure, if indicated by the SI broadcast of the target cell; for a handover, if the target cell indicates TA reporting in the handover command, the wireless device may trigger the TA report).

[0288] To accommodate long propagation delays, the user plane procedures can be adjusted. For example, for the downlink, HARQ feedback can be enabled or disabled for each HARQ process. For example, for the uplink, the wireless device can be configured with HARQ mode A or HARQ mode B for each HARQ process. For example, the maximum number of HARQ processes can be extended to 32. For example, the value ranges of MAC layer timers (e.g., sr-ProhibitTimer and configuredGrantTimer), RLC layer timers (e.g., t-Reassembly), and PDCP layer timers (e.g., discardTimer and t-reordering) can be extended.

[0289] For example, the gNB can ensure the proper configuration of HARQ feedback (e.g., enable or disable) for the HARQ processes used by semi-persistent scheduling (SPS) configuration and the HARQ mode for the HARQ processes used by configured grant (CG) configuration.

[0290] If a logical channel is configured with allowedHARQ-mode, the logical channel can be (only) mapped to HARQ processes with the same HARQ mode.

[0291] To accommodate long propagation delays, several NR timings involving DL-UL timing interaction can be enhanced by supporting two scheduling offsets: K offset and k mac .

[0292] The timing relationship modified for NTN using Koffset can be the transmission timing of DCI-scheduled PUSCH (including CSI transmission on PUSCH), the transmission timing of PUSCH scheduled by random access response (RAR) grant or fallbackRAR grant, the timing of the first PUSCH transmission opportunity in type 2 configured grant, the transmission timing of HARQ-ACK (including HARQ-ACK on PUCCH) on physical uplink control channel (PUCCH) to message B (MsgB) in 2-step random access, the transmission timing of PDCCH-ordered physical random access channel (PRACH), the timing of adjustment of uplink transmission timing after receiving the corresponding timing advance command, the transmission timing of aperiodic sounding reference signal (SRS), and / or CSI reference resource timing.

[0293] k mac can be the scheduling offset supported in NTN for enhancing the MAC CE timing relationship. k macIt can be provided by the network (e.g., via SIB, RRC configuration, etc.) in response to misalignment of downlink and uplink frame timing at the gNB. For downlink-configured UE actions and assumptions indicated by MAC-CE commands in the PDSCH, k may be required mac K mac can be used for beam failure recovery, where after a PRACH transmission in uplink slot n, the UE starts monitoring the corresponding PDCCH from downlink slot "n + k mac + 4" within the corresponding RAR window.

[0294] In response to the UE being configured with k mac , when the UE transmits a PUCCH with HARQ-ACK information in the uplink slot n corresponding to the PDSCH carrying the MAC CE command in a downlink configuration, the UE actions and assumptions for the downlink configuration can be applied starting from the first slot after slot , where μ is the SCS configuration of the PUCCH.

[0295] To accommodate the long propagation delays experienced in NTN on both the serving link and the feeder link, the UE can (be able to) perform time pre-compensation for (all) uplink transmissions (e.g., PRACH preamble transmission, uplink transmissions during RRC_CONNECTED state, etc.). To perform pre-compensation, the UE can be assisted by GNSS (e.g., in / within the UE). To perform pre-compensation, the UE can be assisted by the network (e.g., gNB). The gNB can broadcast NTN assistance information periodically. The NTN assistance information can include serving satellite ephemeris. The NTN assistance information can include higher layer common TA related parameters. The higher layer common TA related parameters can be used to calculate the common round-trip delay (RTD), e.g., the delay on the feeder link.

[0296] The following formula for TA calculation can be applied by the UE to PRACH preamble transmission and in the RRC_CONNECTED state: where N TA can be the timing advance (or timing advance value) between downlink and uplink, and N TA,offset can be a fixed offset used to calculate the timing advance. For example, for msgA transmission on the PUSCH, the UE can use N TA = 0. can be a network-controlled common TA. can include any timing offset (e.g., feeder link delay / delay of the feeder link) that the network deems necessary. It can be derived from higher-layer parameters (e.g., TACommon, TACommonDrift, and TACommonDriftVariation) if configured, otherwise It can be a TA self-estimated by the wireless device for pre-compensating the delay of the serving link (e.g., serving link delay). It can be calculated by the wireless device based on the position of the wireless device and higher-layer parameters related to the serving satellite ephemeris if configured, otherwise T c It can be an NR basic time unit.

[0297] The wireless device can (be able to) use the obtained GNSS position and serving satellite ephemeris information (when provided by the network) of the wireless device to calculate frequency pre-compensation to reverse the instantaneous Doppler shift experienced on the serving link. The pre-compensation for the instantaneous Doppler shift experienced on the serving link can be performed by the UE. The management of the Doppler shift experienced on the feeder link and any transponder frequency errors (introduced either in the downlink or uplink) can be a network implementation.

[0298] The network (e.g., gNB) can broadcast multiple tracking area codes per PLMN in the NTN cell. The change of the tracking area code in the system information can be under network control. For example, it may not be precisely synchronized with the real-time illumination of the beam on the ground. The wireless device can implicitly determine the network type (e.g., terrestrial or non-terrestrial) through the presence of the scheduling information of SIB19 in SIB1. Wireless devices without NTN capabilities can be prevented from accessing NTN cells.

[0299] The satellite ephemeris (or NTN ephemeris) can be divided into the satellite ephemeris of the serving cell and the satellite ephemeris of the neighboring cells.

[0300] At least in the quasi-geostationary cell scenario, the wireless device can perform time-based and location-based cell selection / reselection. The timing information and location information associated with the (NTN) cell can be provided via system information (e.g., SIB, NTN-specific SIB, etc.). The timing information can refer to the time when the serving cell can stop serving a geographical area. The location information can refer to the reference location of the serving cell or neighboring cells. The location information can be used to conditionally assist cell reselection in NTN based on, for example, the distance between the wireless device and the reference locations of the serving cell and / or neighboring cells. The wireless device can support mobility between radio access technologies based on different orbits (GSO, NGSO at different altitudes, etc.).

[0301] A feeder link handover can be a procedure to change the feeder link from a source NTN gateway to a target NTN gateway for a specific NTN payload. The feeder link handover can be a transport network layer procedure. Both hard and soft feeder link handovers can be applied to NTN.

[0302] The feeder link handover can enable the transfer of the connection established for the affected radio device between two gNBs. For soft feeder link handover, the NTN payload can be able to connect to more than one NTN gateway during a given period, e.g., a temporary overlap can be ensured during the transition between feeder links. For hard feeder link handover, the NTN payload can be connected to only one NTN gateway at any given time, e.g., a radio link interruption may occur during the transition between feeder links.

[0303] The NTN control function can determine the time point to perform the feeder link handover between two gNBs. The transfer of the context of the affected radio device during the feeder link handover can be performed by means of NG-based or Xn-based handover. The transfer can depend on the implementation and configuration information of the gNB provided by the NTN control function to the gNB.

[0304] During the mobility between NTN and the terrestrial network, it may not be necessary for the radio device to be connected to both NTN and the terrestrial network simultaneously. The mobility between NTN and the terrestrial network can be referred to as NTN-terrestrial network handover. The NTN-terrestrial network handover can refer to the mobility in both directions, e.g., from NTN to the terrestrial network (handover in) and from the terrestrial network to NTN (handover out).

[0305] NTN may not support DAPS handover. The radio device can support the mobility between radio access technologies (GSO, NGSO at different altitudes) based on different orbits.

[0306] NTN can support additional trigger conditions based on which the UE can perform a conditional handover (CHO) to a candidate cell:

[0307] - Event A4;

[0308] - Time-based trigger condition; and / or

[0309] - Location-based trigger condition.

[0310] The time-based or location-based trigger condition can be configured together with a measurement-based trigger condition (e.g., Event A4). The location can be defined based on the distance between the radio device and a reference location. The time can be defined based on the time between T1 and T2, where T1 is an absolute time value and T2 is a duration starting at T1.

[0311] (NTN) Base stations / networks may:

[0312] - Use propagation delay differences, feeder link delays, and / or serving / neighboring satellite cell ephemerides, depending on the wireless device capabilities, to configure multiple SMTCs in parallel for each carrier and / or for a given cell set; and / or

[0313] - Configure measurement gaps using the same propagation delay differences calculated for SMTCs.

[0314] Adjustment of SMTCs may be possible under network control for the connected mode and under wireless device control based on wireless device location information and ephemerides for the idle / inactive modes.

[0315] After a network request and after establishing AS security in the connected mode, the wireless device may report rough wireless device location information (e.g., the X most significant bits of the GNSS coordinates of the wireless device with an accuracy of about 2 km level) to the NG-RAN without receiving any prior explicit user consent. If user consent is available at the wireless device, the wireless device may report the rough wireless device location information. Otherwise, the wireless device may respond with "no rough GNSS location available". Periodic location reports may be configured by the gNB to obtain wireless device location updates for mobile wireless devices in the RRC_CONNECTED mode / status.

[0316] Base stations (e.g., gNBs) may transmit / broadcast NTN-specific SIBs. The NTN-specific SIB may be, for example, SIB19. The NTN-specific SIB may include satellite assistance information. For example, the NTN-specific SIB may include ephemeris data. For example, the NTN-specific SIB may include common TA parameters. For example, the NTN-specific SIB may include common TA parameters. For example, the NTN-specific SIB may include a k offset. For example, the NTN-specific SIB may include the validity duration of UL synchronization information. For example, the NTN-specific SIB may include the epoch time. For example, the NTN-specific SIB may include the reference location of the (NTN) cell provided via the NTN quasi-geostationary system.

[0317] The NTN-specific SIB may include t_service. The t_service may indicate time information about when the (NTN) cell provided via the NTN quasi-geostationary system will stop serving the area currently covered by the (NTN) cell. The t_service may count the number of UTC seconds in units of 10 ms starting from January 1, 1900, 00:00:00 UTC (midnight between Sunday, December 31, 1899, and Monday, January 1, 1900).

[0318] After receiving the NTN-specific SIB, the wireless device may instruct the lower layer to start or restart ntn-UlSyncValidityDuration from the subframe / slot indicated by the epoch time. The wireless device may attempt to re-acquire the NTN-specific SIB before the end of the duration indicated by ntn-UlSyncValidityDuration and the epoch time.

[0319] Support for bandwidth-constrained low-complexity (BL) wireless devices, wireless devices in enhanced coverage, and / or narrowband Internet of Things (NB-IoT) wireless devices on NTN may be applicable. Wireless devices that do not support NTN may be prohibited from entering NTN cells.

[0320] In NTN, support for BL wireless devices, wireless devices in enhanced coverage, and NB-IoT wireless devices with GNSS capabilities may be provided.

[0321] To accommodate the long propagation delay in NTN, increased timer values, window sizes, or delayed start times may be supported for the physical layer and / or higher layers.

[0322] For UL transmissions with repetitions in NTN, UL segmented transmissions may be supported. The wireless device may apply wireless device pre-compensation to each segment of the UL transmissions of PUSCH / PUCCH / PRACH for eMTC and NPUSCH / NPRACH for NB-IoT from one segment to the next.

[0323] To accommodate the long propagation delay, several IoT timings involving DL-UL timing interaction may be enhanced by supporting two scheduling offsets: K offset and K mac . K offset may be the round-trip time between the wireless device and the uplink time synchronization reference point (RP). K offset may correspond to the sum of the serving link RTT and the common TA (if indicated). K mac may be the round-trip time between the RP and the eNB / gNB.

[0324] DL and UL may be frame-aligned at the uplink time synchronization RP with an offset given by N TA,offset .

[0325] The timing relationships modified for NB-IoT using K offset are summarized as follows:

[0326] - Transmission timing of NPUSCH format 1 scheduled by NPDCCH.

[0327] - Transmission timing of NPUSCH format 1 granted by random access response (RAR).

[0328] - Transmission timing of HARQ-ACK on NPUSCH format 2.

[0329] - Transmission timing of NPDCCH sorted NB-IoT physical random access channel (NPRACH).

[0330] - Timing of adjustment of uplink transmission timing after receiving the corresponding timing advance command.

[0331] K can be used offset The timing relationships modified for eMTC are summarized as follows:

[0332] - Transmission timing of PUSCH scheduled by MPDCCH.

[0333] - Transmission timing of PUSCH granted by random access response (RAR).

[0334] - Timing of the first PUSCH transmission opportunity in UL SPS.

[0335] - Transmission timing of HARQ-ACK on physical uplink control channel (PUCCH).

[0336] - Transmission timing of MPDCCH sorted physical random access channel (PRACH).

[0337] - Timing of adjustment of uplink transmission timing after receiving the corresponding timing advance command.

[0338] - Transmission timing of aperiodic sounding reference signal (SRS).

[0339] - CSI reference resource timing.

[0340] - Transmission timing of preamble retransmission.

[0341] For initial access, the information of K can be carried in the system information offset The information of K can be supported to be updated after initial access offset The network / gNB / eNB / base station can use MAC CE to provide and update UE-specific K offset .

[0342] K mac is a scheduling offset for enhancing the MAC CE timing relationship that can be supported in NTN. If the downlink and uplink frame timings are not aligned at the eNB, K can be provided by the network macFor UE actions and assumptions for the downlink configuration indicated by the MAC-CE command in (N)PDSCH, K may be required mac K mac It can also be used in preconfigured uplink resources. In response to the wireless device starting an (N)PUSCH transmission using a preconfigured uplink resource that ends in subframe n, the wireless device will start or resume monitoring N / MPDCCH from DL subframe n+4+K mac Monitor N / MPDCCH.

[0343] For the serving cell, the network / eNB / gNB may broadcast ephemeris information and common TA parameters for the wireless device to perform TA pre-compensation autonomously. For the serving cell, the network / gNB / eNB may broadcast ephemeris information and common TA parameters for the wireless device to perform frequency shift pre-compensation autonomously.

[0344] The wireless device may acquire the GNSS position of the wireless device before connecting to the NTN cell to ensure the synchronization of the wireless device. The wireless device may acquire satellite ephemeris and common TA before connecting to the NTN cell to ensure the synchronization of the wireless device. Before performing random access, the wireless device may autonomously pre-compensate the TA for long propagation delays and frequency Doppler shifts by considering the common TA, the position of the wireless device, and the satellite positions through the satellite ephemeris.

[0345] In the RRC_CONNECTED mode, the wireless device may continuously update the TA and frequency pre-compensation. It may not be expected that the wireless device performs GNSS acquisition. One or more timers may ensure that the UE does not perform any transmissions due to outdated satellite ephemeris, common TA, or GNSS position. In the connected mode, after outdated satellite ephemeris and common TA, the wireless device may re-acquire one or more broadcast parameters. After an outdated GNSS positioning, the wireless device may move to the RRC_IDLE mode.

[0346] The wireless device may be configured to report the TA at initial access or in the RRC_CONNECTED mode. In the RRC_CONEECTED mode, triggered TA reporting may be supported.

[0347] The wireless device may be able to use the acquired GNSS position of the wireless device and satellite ephemeris information (when provided by the network / gNB / eNB) to calculate the frequency pre-compensation to reverse the instantaneous Doppler shift experienced on the serving link.

[0348] The management of the Doppler shift experienced on the feed link and any transponder frequency errors (introduced either in the DL or UL) may be left to the network implementation.

[0349] When a satellite moves in a specified orbit, e.g., in the case of an NGSO satellite, due to the orbital movement of the satellite, the satellite beam coverage area can move and cover different parts of a geographical area. Thus, wireless devices located in the geographical area of interest may experience a situation of discontinuous coverage due to, for example, sparse satellite constellation deployment.

[0350] To enable wireless devices to save power during uncovered periods, the network / gNB / eNB can provide satellite assistance information (e.g., satellite ephemeris parameters, start time of upcoming satellite coverage, end time of satellite coverage, etc.) ephemeris parameters so that the wireless devices can predict when coverage will be provided by an upcoming satellite. The prediction outside and inside the coverage area can depend on the wireless device implementation. When outside the coverage area, it may not be required for the wireless device to perform access stratum functions.

[0351] Feeding link switching can be a procedure for changing the feeding link from a source NTN gateway to a target NTN gateway for a specific NTN payload. Feeding link switching can be a transport network layer procedure. Both hard and soft feeding link switching can be applied to NTN.

[0352] Feeding link switching can implement the transfer of a connection established for an affected wireless device between two eNB / gNB / base stations.

[0353] For soft feeding link switching, the NTN payload can be able to connect to more than one NTN gateway during a given period, e.g., a temporary overlap can be ensured during the transition between feeding links. For hard feeding link switching, the NTN payload can be connected to only one NTN gateway at any given time, e.g., a radio link interruption may occur during the transition between feeding links.

[0354] The NTN control function can determine the time point for performing feeding link switching between two eNB / gNB / base stations. For BL wireless devices and wireless devices in enhanced coverage, the transfer of the context of the affected wireless device between two eNB / gNB / base stations during feeding link switching can be performed by means of an S1-based or X2-based handover. The transfer can depend on the implementation of the two eNB / gNB / base stations and the configuration information provided by the NTN control function to the two eNB / gNB / base stations.

[0355] In the prior art, a wireless device can transmit a random access message 1 (Msg1) (e.g., Figure 13A Msg 1 1311 in Figure 13AMsg 2 in (1312). The wireless device may receive Msg2 in response to transmitting Msg1. The wireless device may transmit a random access message 3 (Msg3) in response to receiving Msg2 (e.g., Figure 13A Msg 3 in (1313). The base station may receive Msg3. The base station may transmit a random access message 4 (Msg4) in response to receiving Msg3 (e.g., Figure 13A Msg 4 in (1314). The wireless device may receive Msg4. In response to receiving Msg4, the wireless device may transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) message (e.g., HARQ-ACK, HARQ-ACK message, HARQ-ACK feedback, HARQ-ACK information, HARQ-ACK information for PDSCH including UE / wireless device contention resolution identity, Msg4 HARQ-ACK, PUCCH HARQ-ACK, etc.).

[0356] In an additional example describing the prior art, the wireless device may be in an NTN. The path loss (e.g., attenuation of the signal) experienced by the uplink / downlink signal in the NTN may be higher / greater / more than the path loss experienced by the uplink / downlink signal in a terrestrial network (e.g., 3 dB, 5 dB, 10 dB, etc.). Due to the increased path loss, the coverage of the NTN may be limited. The wireless device may repeat the transmission of the uplink / downlink signal (e.g., PRACH, PUSCH, PUCCH, SRS, HARQ-ACK, etc.) (e.g., perform repetition, including repetition, perform multiple transmissions, etc.), for example to enhance coverage. For example, the wireless device may use / perform / transmit repetition of Msg4 / for the HARQ-ACK of Msg4 (e.g., PUCCH repetition) to enhance coverage. Using the prior art, multiple (e.g., all) wireless devices in a cell (e.g., cell sector, area, coverage area, beam coverage area, etc.) may transmit uplink repetition of HARQ-ACK (e.g., PUCCH repetition). Transmitting uplink repetition of HARQ-ACK may be unnecessary (e.g., when the wireless device is not in an area where coverage enhancement is needed (e.g., line-of-sight path from the NTN payload / base station)), and may result in unnecessary and undesirable consequences. Specifically, unnecessarily transmitting uplink repetition of HARQ-ACK may increase signaling overhead, increase power consumption at the wireless device, and / or shorten the battery life of the wireless device.

[0357] In view of the prior art, there is a need to improve the uplink repetition procedure in an NTN (e.g., PUCCH repetition of HARQ-ACK). The example embodiments described in the present disclosure may improve the battery life of the wireless device and / or reduce the signaling overhead associated with uplink repetition.

[0358] According to an example embodiment of the present disclosure, a wireless device may determine a repeated HARQ-ACK (e.g., determine to perform (uplink) repetition of HARQ-ACK) in response to a propagation time being greater than (or equal to) a threshold (e.g., a time threshold). The propagation time may indicate, for example, the round-trip time between the wireless device and a base station (e.g., an NTN satellite, a terrestrial base station, an NTN gateway, etc.). Based on the propagation time being greater than the threshold, the wireless device may indicate to the base station that the wireless device may perform / transmit an uplink repetition of HARQ-ACK, for example, via a random access message (e.g., implicitly via selection of a random access resource for Msg1 transmission, implicitly via selection of a random access resource for Msg1 transmission associated with PUCCH / Msg1 / Msg3 repetition, explicitly indicate via Msg3, implicitly indicate via Msg3, etc.). In another example embodiment, the wireless device may determine a repeated HARQ-ACK (e.g., determine to perform an uplink repetition of HARQ-ACK) in response to a reference signal received power (RSRP) of a reference signal being less than (or equal to) a threshold (e.g., a power threshold).

[0359] Based on performing / transmitting an uplink repetition of HARQ-ACK in response to a propagation time being greater than a (time) threshold and / or an RSRP being less than a (power) threshold, the wireless device may reduce unnecessary repetitions of HARQ-ACK. For example, when the wireless device is in a line-of-sight path with a satellite / NTN payload, the wireless device may not perform / transmit an uplink repetition of HARQ-ACK. For example, when the path loss experienced by an uplink signal transmitted by the wireless device is not severe (e.g., a path loss of 100 dB, 120 dB, etc.), the wireless device may not perform / transmit an uplink repetition of HARQ-ACK. Examples of reducing unnecessary repetitions of HARQ-ACK may reduce signaling overhead, reduce power consumption in the wireless device, and / or improve / extend / enhance the battery life of the wireless device.

[0360] In an example embodiment, the wireless device may receive one or more configuration parameters from a base station. The base station may be an NTN base station (e.g., an NTN payload, a satellite, an NTN gateway, a gNB, an eNB, etc.). The one or more parameters may be broadcast configuration parameters. The one or more configuration parameters may be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB 31, etc.).

[0361] Figure 22A An example timing diagram is shown according to an aspect of an embodiment of the present disclosure. According to Figure 22A the example, the wireless device ( Figure 22AThe UE in ) can receive one or more configuration parameters from a base station / satellite. The one or more configuration parameters can be one or more broadcast configuration parameters. The one or more configuration parameters can be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-Config, NTN-specific system information blocks, NTN-specific / related system information parameters, SIB19, SIB 31, etc.).

[0362] The one or more configuration parameters can include / indicate, for example, a common timing advance (TA), such as common TA-related parameters, ta-Common, common TA drift (ta-CommonDrift), common TA drift variant (ta-CommonDriftVariant), etc.

[0363] In one example, the common TA can be the same / common for multiple wireless devices in a cell. In another example, the common TA can be the same / common for multiple wireless devices in a beam. In another example, the common TA can be the same / common for multiple wireless devices in a beam coverage area. The wireless device can, for example, use the common TA to determine the one or more propagation time values.

[0364] In an example embodiment, the common TA can, for example, correspond to the round-trip time (or round-trip delay) of the feeder link. The common TA can, for example, correspond to the round-trip time (or round-trip delay) of a part of the feeder link. The common TA can, for example, correspond to the round-trip time (or round-trip delay) of a part of the feeder link and the service link.

[0365] In an example embodiment, the common TA can be at least one common delay value. The at least one common delay value can, for example, correspond to the one-way propagation time in / of the feeder link. The at least one common delay value can, for example, be referred to as the feeder link propagation time value. The at least one common delay value can, for example, correspond to the one-way propagation time in / of a part of the feeder link. The at least one common delay value can, for example, correspond to the one-way propagation time in / of the feeder link and in / of a part of the service link. In one example, the at least one common delay value can be approximately half of the at least one common timing advance value.

[0366] In an example embodiment, the common TA may be at least one common slot offset value. The at least one common slot offset value may be referred to as K_mac, for example. For example, the at least one common slot offset value may correspond to the number of slots spanned in a duration corresponding to the propagation time (or round-trip delay) of the feeder link. For example, the at least one common slot offset value may correspond to the number of slots spanned in a duration corresponding to the propagation time (or round-trip delay) of a part of the feeder link. For example, the part of the feeder link may correspond to a part of the feeder link between the reference point and the NTN gateway. In another example, the part of the feeder link may correspond to a part of the feeder link between the reference point and the base station / gNB / eNB.

[0367] The number of slots spanned in the duration can be calculated based on the slot length and the duration. The number of slots spanned in the duration may be, for example, equal to the duration divided by the slot length. The slot length may depend on the subcarrier spacing and / or the parameter set used. For example, for the first parameter set (e.g., mu = 0), the slot length may be 1 millisecond. In another example, for the second parameter set (e.g., mu = 1), the slot length may be 0.5 millisecond. In another example, for the third parameter set (e.g., mu = 2), the slot length may be 0.25 millisecond. In another example, for the fourth parameter set (e.g., mu = 3), the slot length may be 0.125 millisecond. In another example, for the fifth parameter set (e.g., mu = 4), the slot length may be 0.0625 millisecond. The first parameter set may be associated with a first subcarrier spacing. The first subcarrier spacing may be 15 kilohertz. The second parameter set may be associated with a second subcarrier spacing. The second subcarrier spacing may be 30 kilohertz. The third parameter set may be associated with a third subcarrier spacing. The third subcarrier spacing may be 60 kilohertz. The fourth parameter set may be associated with a fourth subcarrier spacing. The fourth subcarrier spacing may be 120 kilohertz. The fifth parameter set may be associated with a fifth subcarrier spacing. The fifth subcarrier spacing may be 240 kilohertz.

[0368] In an example embodiment, the common TA may be at least one common subframe offset value. The at least one common subframe offset value may be referred to as K_mac, for example. For example, the at least one common subframe offset value may correspond to the number of subframes spanned in a duration corresponding to the propagation time (or round-trip delay) of the feeder link. For example, the at least one common subframe offset value may correspond to the number of subframes spanned in a duration corresponding to the propagation time (or round-trip delay) of a part of the feeder link. For example, the part of the feeder link may correspond to a part of the feeder link between a reference point and an NTN gateway. In another example, the part of the feeder link may correspond to a part of the feeder link between a reference point and a base station / gNB / eNB.

[0369] The number of subframes spanned in the duration may be calculated based on the subframe length and the duration. The number of subframes spanned in the duration may be equal to the duration divided by the subframe length, for example. The subframe length may be 1 millisecond.

[0370] In an example embodiment, the common TA may be a feeder link propagation distance value. In one example, the feeder link propagation distance value may correspond to the at least one common delay value multiplied by the propagation speed of the NTN signal. In one example, the feeder link propagation distance value may correspond to half of the common TA multiplied by the propagation speed of the NTN signal. The feeder link propagation distance value may correspond to the distance between a satellite and an NTN gateway, for example.

[0371] The propagation speed of the NTN signal may depend on the satellite altitude. For example, the propagation speed of the NTN signal may be a first speed for communication between a wireless device and a GEO satellite. The propagation speed of the NTN signal may be a second speed for communication between a wireless device and a LEO satellite. In one example, the first speed and the second speed may be approximately the same. The wireless device may use the first speed or the second speed to determine (e.g., deduce, calculate) the one or more propagation time values. In another example, the first speed and the second speed may be different. When communicating with a GEO satellite, the wireless device may use the first speed to determine (e.g., deduce, calculate) the one or more propagation time values. When communicating with a LEO satellite, the wireless device may use the second speed to determine (e.g., deduce, calculate) the one or more propagation time values. In one example, the propagation speed of the NTN signal may be the average propagation speed of the NTN signal between the wireless device and the satellite.

[0372] In an example embodiment, a common TA is implicitly indicated to the wireless device. For example, the one or more configuration parameters may indicate the location of the NTN gateway. The common TA may be a feeder link propagation distance value. In one example, the wireless device may calculate / deduce / estimate / determine the feeder link propagation distance value based on the location of the NTN gateway. The wireless device may calculate / deduce / estimate / determine the feeder link propagation distance value based on the satellite position. The wireless device may determine (e.g., obtain, estimate, calculate) the satellite position based on the satellite ephemeris. In one example, the wireless device may calculate the feeder link propagation distance value based on an equation. The equation may include the location of the NTN gateway. The equation may include the satellite position. In one example, the Cartesian coordinates of the location of the NTN gateway may be (X1, Y1, Z1). The Cartesian coordinates of the satellite position may be (X2, Y2, Z2). In one example, the wireless device may determine / deduce / calculate / estimate the square of the feeder link propagation distance value as (X1 - X2)*(X1 - X2)+(Y1 - Y2)*(Y1 - Y2)+(Z1 - Z2)(Z1 - Z2).

[0373] In an example embodiment, a common TA may be implicitly indicated to the wireless device. For example, the one or more configuration parameters may indicate the location of the base station / gNB / eNB. The common TA may be a feeder link propagation distance value. In one example, the wireless device may calculate / deduce / estimate / determine the feeder link propagation distance value based on the location of the base station / gNB / eNB. The wireless device may calculate / deduce / estimate / determine the feeder link propagation distance value based on the satellite position. The wireless device may determine (e.g., obtain, estimate, calculate) the satellite position based on the satellite ephemeris. In one example, the wireless device may calculate the feeder link propagation distance value based on an equation. The equation may include the location of the base station / gNB / eNB. The equation may include the satellite position. In one example, the Cartesian coordinates of the location of the base station / gNB / eNB may be (X1, Y1, Z1). The Cartesian coordinates of the satellite position may be (X2, Y2, Z2). In one example, the wireless device may determine / deduce / calculate / estimate the square of the feeder link propagation distance value as (X1 - X2)*(X1 - X2)+(Y1 - Y2)*(Y1 - Y2)+(Z1 - Z2)(Z1 - Z2).

[0374] The one or more configuration parameters may include / indicate, for example, a threshold (e.g., a time threshold). The threshold may indicate (e.g., may be for) the uplink repetition of the HARQ-ACK of the random access message. The random access message may be, for example, Msg4. Msg4 may also be referred to as a physical downlink shared channel (PDSCH transmission / reception). Msg4 may also be referred to as a PDSCH including the contention resolution identity of the wireless device (e.g., UE contention resolution identity).

[0375] The one or more configuration parameters may indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets may include a first RACH resource set. Figure 22A R1 in [reference] indicates the first RACH resource set. The at least two RACH resource sets may include a second RACH resource set. Figure 22A R2 in [reference] indicates the second RACH resource set.

[0376] The first RACH resource set may be associated with, for example, one or more repetitions of an uplink signal (e.g., PUCCH repetitions of HARQ-ACK for Msg4, PUCCH repetitions of Msg4 HARQ-ACK, PUCCH repetitions of HARQ-ACK for PDSCH including the contention resolution identity of the wireless device, PRACH repetitions, Msg3 repetitions, etc.). For example, a wireless device may use / transmit Msg1 (e.g., a preamble) via one or more first RACH resources from the first RACH resource set. The wireless device may, for example, transmit one or more repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 / Msg4 based on transmitting Msg1 using / via the one or more first RACH resources from the first RACH resource set.

[0377] The second RACH resource set may be associated with, for example, no repetition of an uplink signal (e.g., PUCCH repetitions of HARQ-ACK for Msg4, PUCCH repetitions of Msg4 HARQ-ACK, PUCCH repetitions of HARQ-ACK for PDSCH including the contention resolution identity of the wireless device, etc.) (or may not be associated with any / one or more repetitions). For example, a wireless device may use / transmit Msg1 (e.g., a preamble) via one or more second RACH resources from the second RACH resource set. The wireless device may, for example, transmit no repetition (e.g., a single transmission without any repetition) of HARQ-ACK for Msg4 / Msg4 based on transmitting Msg1 using / via the one or more second RACH resources from the second RACH resource set.

[0378] In Figure 22A the example of [reference], a wireless device may, for example, determine whether HARQ-ACK for Msg4 / for Msg4 requires uplink repetition based on receiving the one or more configuration parameters. For example, the wireless device may determine the propagation time.

[0379] In one example, a wireless device may determine (e.g., calculate, infer, estimate) the propagation time based on a common TA. In one example, the propagation time may be the round-trip time (RTT) between the wireless device and the (terrestrial) NTN gateway. The propagation time may be referred to as UE-gNB RTT (or UE-eNB RTT). The sum of the propagation time and the scheduling offset (e.g., kmac) may indicate the TA value that the wireless device may use for uplink transmission.

[0380] In another example, the propagation time may be the TA value that the wireless device may use for uplink transmission. The TA value may be expressed as or referred to as T_TA (or T TA )

[0381] In one example, the propagation time may be greater than (or equal to) a threshold. The wireless device may determine to perform / use / transmit an uplink repetition of the HARQ-ACK for Msg4 based on the propagation time being greater than (or equal to) the threshold.

[0382] In another example, the one or more configuration parameters may indicate one or more reference signals (e.g., path loss reference signal, synchronization signal / physical broadcast channel (SS / PBCH) block (SSB), cell-specific reference signal, CSI-RS, SRS, etc.). The wireless device may determine (e.g., infer, calculate, estimate, measure, etc.) the RSRP value based on measuring the one or more reference signals. In one example, the one or more configuration parameters may indicate a power threshold for the uplink repetition of the HARQ-ACK for Msg4. In one example, the RSRP value may be greater than / higher than / exceed / be more than (or equal to) the power threshold. The wireless device may determine to perform / use / transmit an uplink repetition of the HARQ-ACK for Msg4 based on the RSRP value being greater than / higher than / exceed / be more than (or equal to) the power threshold.

[0383] In one example, the wireless device may use a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., preamble) based on the propagation time being greater than (or equal to) a threshold. In one example, the wireless device may use a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., preamble) based on the RSRP value being greater than / higher than / exceeding / more than (or equal to) a power threshold. In one example, the wireless device may use a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., preamble) based on determining to perform / use / transmit an uplink repetition of the HARQ-ACK for Msg4.

[0384] In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) of the HARQ-ACK for Msg4 / Msg4 based on transmitting Msg1 using a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources). In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) of the HARQ-ACK for Msg4 / Msg4 based on the propagation time being greater than (or equal to) a threshold. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) of the HARQ-ACK for Msg4 / Msg4 based on the RSRP value being greater than / higher than / exceeding / more than (or equal to) a power threshold.

[0385] A wireless device may receive, for example, Msg4 from a base station. In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 in response to the wireless device transmitting Msg1 (e.g., a preamble) using a first RACH resource from a first RACH resource set (e.g., selected / determined / picked from the first RACH resource set). In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 in response to the wireless device indicating to the base station that the wireless device may use / transmit / executing one or more repetitions (e.g., uplink repetitions, PUCCH repetitions) of HARQ-ACK for Msg4.

[0386] Based on receiving one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4, the wireless device may transmit one or more uplink repetitions of HARQ-ACK for Msg4.

[0387] Figure 22B An example timing diagram is shown according to an aspect of an embodiment of the present disclosure. According to Figure 22B the example, a wireless device ( Figure 22B the UE in

[0388] In Figure 22B the example, the wireless device may determine the propagation time, for example, based on a common TA (e.g., indicated / included in the one or more configuration parameters). In one example, the one or more configuration parameters may include / indicate, for example, a threshold (e.g., a time threshold). The threshold may indicate (e.g., may be for) the uplink repetition of HARQ-ACK for a random access message.

[0389] In one example, the propagation time may be less than (or equal to) the threshold. The wireless device may determine to perform / use / transmit HARQ-ACK for Msg4 without uplink repetition based on the propagation time being less than (or equal to) the threshold.

[0390] The non-repetition of HARQ-ACK (or uplink repetition, or PUCCH repetition) includes a single transmission of HARQ-ACK without subsequent repetitions of the same HARQ-ACK. In some cases, non-repetition may also be referred to as single repetition.

[0391] In another example, the one or more configuration parameters may indicate one or more reference signals (e.g., path loss reference signal, synchronization signal / physical broadcast channel (SS / PBCH) block (SSB), cell-specific reference signal, CSI-RS, SRS, etc.). The wireless device may determine (e.g., deduce, calculate, estimate, measure, etc.) the RSRP value based on measuring the one or more reference signals. In one example, the one or more configuration parameters may indicate a power threshold for uplink repetition of HARQ-ACK for / to Msg4. In one example, the RSRP value may be less than (or equal to) the power threshold. The wireless device may determine to perform / use / transmit uplink repetition of HARQ-ACK for / to Msg4 based on the RSRP value being less than (or equal to) the power threshold.

[0392] The one or more configuration parameters may indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets may include a first RACH resource set. Figure 22B R1 in indicates the first RACH resource set. The at least two RACH resource sets may include a second RACH resource set. Figure 22B R2 in indicates the second RACH resource set.

[0393] The first RACH resource set may be associated with, for example, one or more repetitions of an uplink signal (e.g., PUCCH repetition of HARQ-ACK for Msg4, PUCCH repetition of Msg4 HARQ-ACK, PUCCH repetition of HARQ-ACK for PDSCH including the contention resolution identity of the wireless device, etc.). For example, the wireless device may use / via one or more first RACH resources from the first RACH resource set to transmit Msg1 (e.g., preamble). The wireless device may transmit one or more repetitions (e.g., PUCCH repetition) of HARQ-ACK for / to Msg4 based on transmitting Msg1 using / via the one or more first RACH resources from the first RACH resource set.

[0394] The second RACH resource set may be associated with, for example, no repetition of uplink signals (e.g., PUCCH repetition of HARQ-ACK of Msg4, PUCCH repetition of Msg4 HARQ-ACK, PUCCH repetition of HARQ-ACK of PDSCH including the contention resolution identity of the wireless device, etc.). For example, a wireless device may use / transmit Msg1 (e.g., a preamble) using one or more second RACH resources from the second RACH resource set. The wireless device may transmit a non-repeated (e.g., a single transmission without any repetition) HARQ-ACK for / to Msg4 based on transmitting Msg1 using / through the one or more second RACH resources from the second RACH resource set.

[0395] In one example, the wireless device may use a second RACH resource from the second RACH resource set (e.g., select / determine / pick from the second RACH resource set) to transmit Msg1 (e.g., a preamble) based on the propagation time being less than (or equal to) a threshold. In one example, the wireless device may use a second RACH resource from the second RACH resource set (e.g., select / determine / pick from the second RACH resource set) to transmit Msg1 (e.g., a preamble) based on the RSRP value being less than (or equal to) a power threshold.

[0396] In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform a non-repeated (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for / to Msg4 based on transmitting Msg1 using a second RACH resource from the second RACH resource set (e.g., select / determine / pick from the second RACH resource set). In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform a non-repeated (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for / to Msg4 based on the propagation time being below (or equal to) a threshold. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform a non-repeated (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for / to Msg4 based on the RSRP value being less than (or equal to) a power threshold.

[0397] The wireless device may receive, for example, Msg4 from the base station. In an example, Msg4 may include / indicate one or more uplink resources, and the one or more uplink resources are used to transmit / perform / use no uplink repetition (e.g., PUCCH repetition) of HARQ-ACK / for Msg4 in response to the wireless device transmitting Msg1 (e.g., preamble) using a second RACH resource from a second RACH resource set (e.g., selected / determined / selected from the second RACH resource set). In an example, Msg4 may include / indicate one or more uplink resources, and the one or more uplink resources are used to transmit / perform / use no uplink repetition (e.g., PUCCH repetition) of HARQ-ACK / for Msg4 in response to the wireless device indicating to the base station that the wireless device may use / transmit / perform / no uplink repetition (e.g., uplink repetition, PUCCH repetition) of HARQ-ACK / for Msg4.

[0398] Based on receiving one or more uplink resources for transmitting / performing / using HARQ-ACK for Msg4 / Msg4 without uplink repetition (e.g., PUCCH repetition), the wireless device may transmit, for example, a single transmission (e.g., without repetition) of HARQ-ACK for Msg4 / Msg4.

[0399] Figure 23A An example timing diagram according to one aspect of an embodiment of the present disclosure is shown. Figure 23A For example, a wireless device ( Figure 23A The UE in the wireless communication network may receive one or more configuration parameters from the base station / satellite. The one or more parameters may be broadcast configuration parameters. The one or more configuration parameters may be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB31, etc.).

[0400] The one or more configuration parameters may include / indicate, for example, a common timing advance (TA), such as a common TA related parameter, ta-Common, a common TA drift (ta-CommonDrift), a common TA drift variant (ta-CommonDriftVariant), etc.

[0401] The one or more configuration parameters may include / indicate, for example, a threshold (such as a time threshold). The threshold may indicate (e.g., may be for) an uplink repetition of a HARQ-ACK for a random access message. The random access message may be, for example, Msg4. Msg4 may also be referred to as a physical downlink shared channel (PDSCH transmission / reception). Msg4 may also be referred to as a PDSCH including a contention resolution identity of a wireless device.

[0402] In Figure 23A the example of, the wireless device may, for example, determine whether uplink repetition of the HARQ-ACK for Msg4 is needed based on receiving the one or more configuration parameters. For example, the wireless device may determine a propagation time.

[0403] In one example, the wireless device may determine (e.g., calculate, deduce, estimate) the propagation time based on a common TA. In one example, the propagation time may be a round-trip time (RTT) between the wireless device and a (terrestrial) NTN gateway. The propagation time may be referred to as UE-gNB RTT (or UE-eNB RTT). The sum of the propagation time and a scheduling offset (e.g., kmac) may indicate a TA value that the wireless device may use for uplink transmission.

[0404] In another example, the propagation time may be a TA value that the wireless device may use for uplink transmission. The TA value may be expressed as or referred to as T_TA (or T TA )).

[0405] In one example, the propagation time may be greater than (or equal to) the threshold. The wireless device may determine to perform / use / transmit an uplink repetition of the HARQ-ACK for Msg4 based on the propagation time being greater than (or equal to) the threshold.

[0406] In another example, the one or more configuration parameters may indicate one or more reference signals (e.g., a path loss reference signal, a synchronization signal / physical broadcast channel (SS / PBCH) block (SSB), a cell-specific reference signal, a CSI-RS, an SRS, etc.). The wireless device may determine (e.g., deduce, calculate, estimate, measure, etc.) an RSRP value based on measuring the one or more reference signals. In one example, the one or more configuration parameters may indicate a power threshold for uplink repetition of the HARQ-ACK for Msg4. In one example, the RSRP value may be greater than / higher than / exceed / more than (or equal to) the power threshold. The wireless device may determine to perform / use / transmit an uplink repetition of the HARQ-ACK for Msg4 based on the RSRP value being greater than / higher than / exceed / more than (or equal to) the power threshold.

[0407] In one example, the wireless device may transmit a first control command in Msg3 based on the propagation time being greater than (or equal to) a threshold. In one example, the wireless device may transmit a first control command in Msg3 based on the RSRP value being greater than / higher than / exceeding / more than (or equal to) a power threshold. The first control command may be / include a Media Access Control (MAC) Control Element (CE). Msg3 may include a MAC CE indicating / including the first control command. The first control command may be a UCI field. The first control command may be a field indicating whether to use uplink repetition (e.g., uplink repetition or PUCCH repetition, PUCCH repetition for HARQ-ACK of Msg4 / towards Msg4, PUCCH repetition for HARQ-ACK of PDSCH including the contention resolution identity of the wireless device).

[0408] The first control command (in Msg3) may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) for HARQ-ACK of Msg4 / towards Msg4.

[0409] In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) for HARQ-ACK of Msg4 / towards Msg4 based on transmitting the first control command in Msg3. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) for HARQ-ACK of Msg4 / towards Msg4 based on the propagation time being greater than (or equal to) a threshold. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) for HARQ-ACK of Msg4 / towards Msg4 based on the RSRP value being greater than / higher than / exceeding / more than (or equal to) a power threshold.

[0410] A wireless device may receive, for example, Msg4 from a base station. In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 in response to the wireless device transmitting a first control command in Msg3. In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., uplink repetitions, PUCCH repetitions) of HARQ-ACK for Msg4 in response to the wireless device indicating to the base station that the wireless device may use / transmit / executing one or more repetitions of HARQ-ACK for Msg4 to transmit / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4.

[0411] Based on receiving one or more uplink resources for transmitting / executing / using one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4, the wireless device may transmit, for example, one or more uplink repetitions of HARQ-ACK for Msg4.

[0412] Figure 23B An example timing diagram is shown for one aspect of an embodiment in accordance with the present disclosure. According to Figure 23B the example, a wireless device ( Figure 23B the UE in) may receive one or more configuration parameters from a base station / satellite. The one or more parameters may be broadcast configuration parameters. The one or more configuration parameters may be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB 31, etc.).

[0413] In Figure 23B the example, the wireless device may determine the propagation time, for example, based on a common TA (e.g., indicated / included in the one or more configuration parameters). In one example, the one or more configuration parameters may include / indicate, for example, a threshold (e.g., a time threshold). The threshold may indicate (e.g., may be for) uplink repetitions of HARQ-ACK for random access messages.

[0414] In one example, the propagation time may be less than (or equal to) the threshold. The wireless device may determine to perform / use / transmit HARQ-ACK for Msg4 without uplink repetitions based on the propagation time being less than (or equal to) the threshold.

[0415] The non - repetition of HARQ - ACK (or uplink repetition, or PUCCH repetition) includes a single transmission of HARQ - ACK without subsequent repetition of the same HARQ - ACK. In some cases, non - repetition can also be referred to as single repetition.

[0416] In another example, the one or more configuration parameters may indicate one or more reference signals (e.g., path loss reference signal, synchronization signal / physical broadcast channel (SS / PBCH) block (SSB), cell - specific reference signal, CSI - RS, SRS, etc.). The wireless device may determine (e.g., deduce, calculate, estimate, measure, etc.) the RSRP value based on measuring the one or more reference signals. In one example, the one or more configuration parameters may indicate a power threshold for uplink repetition of HARQ - ACK for / to Msg4. In one example, the RSRP value may be less than (or equal to) the power threshold. The wireless device may determine to perform / use / transmit uplink repetition of HARQ - ACK for / to Msg4 based on the RSRP value being less than (or equal to) the power threshold.

[0417] In one example, the wireless device may transmit a second control command in Msg3 indicating no uplink repetition of HARQ - ACK for / to Msg4 based on the propagation time being less than (or equal to) a threshold. In one example, the wireless device may transmit a second control command in Msg3 indicating no uplink repetition of HARQ - ACK for / to Msg4 based on the RSRP value being less than (or equal to) the power threshold. The control command may be a MAC CE. The second control command may be a UCI field. The second control command may be a field indicating whether to use uplink repetition (e.g., uplink repetition or PUCCH repetition, PUCCH repetition of HARQ - ACK for / to Msg4, PUCCH repetition of HARQ - ACK of PDSCH including the contention resolution identity of the wireless device).

[0418] In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform non-repetitive (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for Msg4 / Msg4 based on a second control command transmitted in Msg3 indicating non-uplink repetition of the HARQ-ACK for Msg4 / Msg4. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform non-repetitive (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for Msg4 / Msg4 based on the propagation time being below (or equal to) a threshold. In one example, the wireless device may indicate to the base station that the wireless device may use / transmit / perform non-repetitive (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for Msg4 / Msg4 based on the RSRP value being less than (or equal to) a power threshold.

[0419] The wireless device may receive, for example, Msg4 from the base station. In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using non-uplink repetition (e.g., PUCCH repetition) of Msg4's / HARQ-ACK for Msg4 in response to the wireless device transmitting a second control command in Msg3 indicating non-uplink repetition of the HARQ-ACK for Msg4 / Msg4. In one example, Msg4 may include / indicate one or more uplink resources for transmitting / executing / using non-uplink repetition (e.g., PUCCH repetition) of Msg4's / HARQ-ACK for Msg4 in response to the wireless device indicating to the base station that the wireless device may use / transmit / perform / non-repetitive (e.g., uplink repetition, PUCCH repetition) HARQ-ACK for Msg4 / Msg4.

[0420] Based on receiving one or more uplink resources for transmitting / executing / using non-uplink repetition (e.g., PUCCH repetition) of Msg4's / HARQ-ACK for Msg4, the wireless device may transmit, for example, a single transmission (e.g., non-repetitive) of HARQ-ACK for Msg4 / Msg4.

[0421] Figure 24A An example timing diagram is shown according to one aspect of an embodiment of the present disclosure. According to Figure 24A the example, the wireless device ( Figure 24AThe UE in ) can receive one or more configuration parameters from a base station / satellite. The one or more parameters can be broadcast configuration parameters. The one or more configuration parameters can be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB 31, etc.).

[0422] The one or more configuration parameters can include / indicate, for example, a common timing advance (TA), such as common TA-related parameters, ta-Common, common TA drift (ta-CommonDrift), common TA drift variant (ta-CommonDriftVariant), etc.

[0423] The one or more configuration parameters can include a first threshold and a second threshold. The first threshold can be for (e.g., can be used for, can indicate, etc.) the uplink repetition of HARQ-ACK for Msg4 / for Msg4 (e.g., PUCCH repetition). The second threshold can be for the repetition of Msg3.

[0424] The one or more configuration parameters can indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets can include a first RACH resource set. Figure 24A R1 in indicates the first RACH resource set. The at least two RACH resource sets can include a second RACH resource set. Figure 24A R2 in indicates the second RACH resource set.

[0425] The first RACH resource set can be associated with, for example, one or more repetitions of Msg3. For example, a wireless device can transmit Msg1 (e.g., preamble) using / via one or more first RACH resources from the first RACH resource set. The wireless device can transmit one or more repetitions of Msg3 based on transmitting Msg1 using / via the one or more first RACH resources from the first RACH resource set.

[0426] The second RACH resource set can be associated with, for example, no repetition of Msg3. For example, a wireless device can transmit Msg1 (e.g., preamble) using / via one or more second RACH resources from the second RACH resource set. The wireless device can transmit no repetition of Msg3 (e.g., a single transmission without any repetition) based on transmitting Msg1 using / via the one or more second RACH resources from the second RACH resource set.

[0427] In one example, a wireless device may use a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble). In response to transmitting Msg1 (e.g., a preamble) using the first RACH resource from the first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources), the wireless device may transmit one or more repetitions of Msg3. In response to transmitting Msg1 (e.g., a preamble) using the first RACH resource from the first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) and / or in response to transmitting one or more repetitions of Msg3, the wireless device may receive one or more uplink resources from the base station (e.g., in Msg4, included in Msg4, indicated in Msg4, via Msg4). The one or more uplink resources may indicate (or may be used to perform / use / transmit) one or more repetitions of HARQ-ACK for Msg4 / towards Msg4 (e.g., uplink repetitions, PUCCH repetitions, etc.).

[0428] Based on receiving the one or more uplink resources for transmitting / executing / using one or more uplink repetitions of HARQ-ACK for Msg4 / towards Msg4 (e.g., PUCCH repetitions), the wireless device may transmit, for example, one or more uplink repetitions of HARQ-ACK for Msg4 / towards Msg4.

[0429] In Figure 24A the example, the wireless device may use a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble) based on, for example, the propagation time being greater than a time threshold. The wireless device may use a RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble) based on, for example, the RSRP value being less than a power threshold. By using the first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble), the wireless device may implicitly indicate to the base station that the wireless device may transmit / use / perform uplink repetitions of HARQ-ACK for Msg4 / towards Msg4.

[0430] Figure 24B FIG. shows an example timing diagram according to one aspect of an embodiment of the present disclosure. According to Figure 24B the example, a wireless device ( Figure 24BThe UE) can receive one or more configuration parameters from a base station / satellite. The one or more parameters can be broadcast configuration parameters. The one or more configuration parameters can be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB 31, etc.).

[0431] In Figure 24B the example of, a wireless device can determine the propagation time, for example, based on a common TA (e.g., indicated / included in the one or more configuration parameters). In one example, the one or more configuration parameters can include / indicate, for example, a threshold (e.g., a time threshold). The threshold can indicate (e.g., can be for) the uplink repetition of HARQ-ACK for a random access message.

[0432] The one or more configuration parameters can indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets can include a first RACH resource set. Figure 24B R1 in indicates the first RACH resource set. The at least two RACH resource sets can include a second RACH resource set. Figure 24B R2 in indicates the second RACH resource set.

[0433] The first RACH resource set can be associated with, for example, one or more repetitions of Msg3. For example, a wireless device can use / via one or more first RACH resources from the first RACH resource set to transmit Msg1 (e.g., a preamble). The wireless device can transmit one or more repetitions of Msg3 based on transmitting Msg1 using / via the one or more first RACH resources from the first RACH resource set.

[0434] The second RACH resource set can be associated with, for example, no repetition of Msg3. For example, a wireless device can use / via one or more second RACH resources from the second RACH resource set to transmit Msg1 (e.g., a preamble). The wireless device can transmit no repetition of Msg3 (e.g., a single transmission without any repetition) based on transmitting Msg1 using / via the one or more second RACH resources from the second RACH resource set.

[0435] In one example, a wireless device may use a second RACH resource from a second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) to transmit Msg1 (e.g., a preamble). In response to transmitting Msg1 (e.g., a preamble) using the second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set), the wireless device may transmit a non-duplicate of Msg3. In response to transmitting Msg1 (e.g., a preamble) using the second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) and / or in response to transmitting a non-duplicate of Msg3, the wireless device may receive one or more uplink resources from the base station (e.g., in Msg4, included in Msg4, indicated in Msg4, via Msg4). The one or more uplink resources may indicate (or may be used to perform / use / transmit) a non-duplicate of HARQ-ACK for Msg4 (e.g., may not indicate any duplication, such as uplink duplication, PUCCH duplication, etc.).

[0436] Based on receiving the one or more uplink resources for transmitting / performing / using a non-uplink duplication of HARQ-ACK for Msg4 (e.g., PUCCH duplication), the wireless device may transmit, for example, a non-uplink duplication of HARQ-ACK for Msg4.

[0437] In Figure 24B the example, the wireless device may transmit Msg1 (e.g., a preamble) using the second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) based on, for example, the propagation time being greater / higher / more than (or equal to) a time threshold. The wireless device may transmit Msg1 (e.g., a preamble) using the second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) based on, for example, the RSRP value being lower / less than (or equal to) a power threshold. By transmitting Msg1 (e.g., a preamble) using the second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set), the wireless device may implicitly indicate to the base station that the wireless device may not transmit / use / perform one or more / any duplications of HARQ-ACK for Msg4.

[0438] Figure 24A and Figure 24B The example embodiments of Figure 22A and Figure 22B may be used together with or independently of the example embodiments ofFigure 22A and Figure 22B For example, a wireless device may determine to use non-redundant / for Msg3 based on, for example, the propagation time being less than a first threshold (or the RSRP value being greater than a first power threshold). The wireless device may determine to use one or more repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 / for Msg4 based on, for example, the propagation time being greater than / higher than / exceeding / more than (or equal to) a second threshold (or the RSRP value being less than a second power threshold).

[0439] The wireless device may transmit Msg3 on / via / using the Physical Uplink Shared Channel (PUSCH). The wireless device may transmit HARQ-ACK for Msg4 / Msg4 on / via / using the Physical Uplink Control Channel (PUCCH). The characteristics of PUSCH transmission (e.g., path loss, attenuation, phase shift, spatial domain characteristics, beam, TCI state, etc.) may be different from the characteristics of PUCCH transmission (e.g., path loss, attenuation, phase shift, spatial domain characteristics, beam, TCI state, etc.). Performing / using / transmitting one or more repetitions of PUCCH (e.g., HARQ-ACK for Msg4 / for Msg4) may not require performing / using / transmitting one or more repetitions of PUSCH (e.g., Msg3), and / or vice versa.

[0440] Figure 25A An example timing diagram showing one aspect of an embodiment according to the present disclosure is presented. According to Figure 25A the example, a wireless device ( Figure 25A the UE in

[0441] The one or more configuration parameters may include / indicate, for example, a common Timing Advance (TA), such as common TA related parameters, ta-Common, common TA drift (ta-CommonDrift), common TA drift variant (ta-CommonDriftVariant), etc.

[0442] The one or more configuration parameters may include a first threshold and a second threshold. The first threshold may be for (e.g., may be used for, may indicate, etc.) uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 / for Msg4. The second threshold may be for repetitions of Msg1.

[0443] The one or more configuration parameters may indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets may include a first RACH resource set. The at least two RACH resource sets may include a second RACH resource set.

[0444] The first RACH resource set may be associated with, for example, one or more repetitions of Msg1. For example, a wireless device may use / transmit Msg1 (e.g., a preamble) using one or more first RACH resources from the first RACH resource set. The wireless device may transmit one or more repetitions of Msg1 based on transmitting Msg1 using / via the one or more first RACH resources from the first RACH resource set.

[0445] The second RACH resource set may be associated with, for example, no repetition of Msg1. For example, a wireless device may use / transmit Msg1 (e.g., a preamble) using one or more second RACH resources from the second RACH resource set. The wireless device may transmit no repetition of Msg1 (e.g., a single transmission without any repetition) based on transmitting Msg1 using / via the one or more second RACH resources from the second RACH resource set.

[0446] In one example, a wireless device may use a first RACH resource from the first RACH resource set (e.g., selected / determined / picked from the first RACH resource set) to transmit Msg1 (e.g., a preamble). In response to transmitting Msg1 (e.g., a preamble) using the first RACH resource from the first RACH resource set (e.g., selected / determined / picked from the first RACH resource set), the wireless device may transmit one or more repetitions of Msg1. In response to transmitting Msg1 (e.g., a preamble) using the first RACH resource from the first RACH resource set (e.g., selected / determined / picked from the first RACH resource set) and / or in response to transmitting one or more repetitions of Msg1, the wireless device may receive one or more uplink resources from a base station (e.g., in Msg4, included in Msg4, indicated in Msg4, via Msg4). The one or more uplink resources may indicate (or may be used to perform / use / transmit) one or more repetitions of HARQ-ACK for Msg4 / for Msg4 (e.g., uplink repetitions, PUCCH repetitions, etc.).

[0447] Based on receiving one or more uplink resources for transmitting / executing / using HARQ-ACK for Msg4 / towards Msg4, the wireless device may transmit one or more uplink repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 / towards Msg4.

[0448] In Figure 25A the example of, the wireless device may transmit Msg1 (e.g., preamble) using a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources), for example, based on the propagation time being greater than a time threshold. The wireless device may transmit Msg1 (e.g., preamble) using a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources), for example, based on the RSRP value being less than a power threshold. By transmitting Msg1 (e.g., preamble) using a first RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources), the wireless device may implicitly indicate to the base station that the wireless device may transmit one or more repetitions of HARQ-ACK for Msg4 / towards Msg4.

[0449] Figure 25B shows an example timing diagram according to an aspect of an embodiment of the present disclosure. According to Figure 25B the example of, a wireless device ( Figure 25B the UE in) may receive one or more configuration parameters from a base station / satellite. The one or more parameters may be broadcast configuration parameters. The one or more configuration parameters may be / include one or more NTN-related configuration parameters (e.g., NTN-specific configuration parameters, NTN-specific system information blocks, SIB19, SIB 31, etc.).

[0450] In Figure 25B the example of, the wireless device may determine the propagation time, for example, based on a common TA (e.g., indicated / included in the one or more configuration parameters). In one example, the one or more configuration parameters may include / indicate, for example, a threshold (e.g., a time threshold). The threshold may indicate (e.g., may be for) uplink repetitions of HARQ-ACK for random access messages.

[0451] The one or more configuration parameters may indicate, for example, at least two random access channel (RACH) resource sets (e.g., random access resources, RACH resources, PRACH resources, preamble resources, time and frequency resources for RACH transmission, etc.). The at least two RACH resource sets may include a first RACH resource set. The at least two RACH resource sets may include a second RACH resource set.

[0452] The first RACH resource set may be associated with, for example, one or more repetitions of Msg1. For example, a wireless device may use / transmit Msg1 (e.g., a preamble) using one or more first RACH resources from the first RACH resource set. The wireless device may transmit one or more repetitions of Msg1 based on transmitting Msg1 using / transmitting Msg1 via the one or more first RACH resources from the first RACH resource set.

[0453] The second RACH resource set may be associated with, for example, no repetition of Msg1. For example, a wireless device may use / transmit Msg1 (e.g., a preamble) using one or more second RACH resources from the second RACH resource set. The wireless device may transmit no repetition of Msg1 (e.g., a single transmission without any repetition) based on transmitting Msg1 using / transmitting Msg1 via the one or more second RACH resources from the second RACH resource set.

[0454] In one example, a wireless device may use a second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) to transmit Msg1 (e.g., a preamble). In response to transmitting Msg1 (e.g., a preamble) using a second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set), the wireless device may transmit no repetition of Msg1. In response to transmitting Msg1 (e.g., a preamble) using a second RACH resource from the second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) and / or in response to transmitting no repetition of Msg1, the wireless device may receive one or more uplink resources (e.g., in Msg4, included in Msg4, indicated in Msg4, via Msg4) from the base station. The one or more uplink resources may indicate (or may be used to perform / use / transmit) no repetition of HARQ-ACK for Msg4 / towards Msg4 (e.g., may not indicate any repetition, such as uplink repetition, PUCCH repetition, etc.).

[0455] Based on receiving the one or more uplink resources for transmitting / performing / using no uplink repetition of HARQ-ACK for Msg4 / towards Msg4 (e.g., PUCCH repetition), the wireless device may transmit, for example, no uplink repetition of HARQ-ACK for Msg4 / towards Msg4.

[0456] In Figure 25BIn an example, the wireless device may use a second RACH resource from a second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) to transmit Msg1 (e.g., a preamble) based on, for example, the propagation time being greater than / higher than / exceeding (or equal to) a time threshold. The wireless device may use a second RACH resource from a second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) to transmit Msg1 (e.g., a preamble) based on, for example, the RSRP value being less than (or equal to) a power threshold. By using a second RACH resource from a second RACH resource set (e.g., selected / determined / picked from the second RACH resource set) to transmit Msg1 (e.g., a preamble), the wireless device may (implicitly) indicate to the base station that the wireless device can transmit / perform / use non-redundant HARQ-ACK for / to Msg4.

[0457] Figure 25A and Figure 25B The example embodiments of Figure 22A and Figure 22B may be used together with the example embodiments of Figure 22A and Figure 22B or used independently of the example embodiments of

[0458] The wireless device may transmit Msg1 on / via / using the physical random access channel (PRACH). The wireless device may transmit the HARQ-ACK for / to Msg4 on / via / using the PUCCH. The characteristics of the PRACH transmission (e.g., path loss, attenuation, phase shift, spatial domain characteristics, beam, TCI state, etc.) may be different from the characteristics of the PUCCH transmission (e.g., path loss, attenuation, phase shift, spatial domain characteristics, beam, TCI state, etc.). Performing / using / transmitting one or more repetitions of the PUCCH (e.g., the HARQ-ACK for / to Msg4) may not require performing / using / transmitting one or more repetitions of the PRACH (e.g., Msg3), and / or vice versa.

[0459] For example, it may be based on the wireless device not transmitting / sending a TA report in Msg3 to use Figure 22A 、Figure 22B , Figure 23A , Figure 23B , Figure 24A , Figure 24B , Figure 25A and Figure 25B the example embodiments (or one or more features in the example embodiments).

[0460] Figure 26A shows an example timing diagram according to an aspect of an embodiment of the present disclosure. In Figure 26A the example, a wireless device ( Figure 26A[[END the UE in) may transmit a UE capability message to a base station. The UE capability message may indicate that reporting information related to TA pre-compensation is not supported (e.g., does not indicate support). Based on the UE capability message indicating that reporting information related to TA pre-compensation is not supported (e.g., does not indicate support), the wireless device may not transmit a TA report (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.) in / via / with Msg3.

[0461] ​ shows an example timing diagram according to an aspect of an embodiment of the present disclosure. In ​ the example, a wireless device ( ​ the UE in) may receive one or more configuration parameters from a base station. The one or more configuration parameters may include / indicate NTN-specific system information parameters (e.g., NTN-config, SIB19). In one example, the NTN-specific system information parameter may not include a field indicating a TA report (e.g., the field indicating a TA report may not exist). Based on the NTN-specific system information parameter not including a field indicating a TA report (e.g., the field indicating a TA report does not exist), the wireless device may not transmit a TA report (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.) in / via / with Msg3.

[0462] In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may use a RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble) based on the propagation time being greater than (or equal to) a threshold. In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may use a RACH resource from a first set of RACH resources (e.g., selected / determined / picked from the first set of RACH resources) to transmit Msg1 (e.g., a preamble) based on the RSRP value being greater than / higher than / exceeding / more than (or equal to) a power threshold. In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may indicate to the base station that the wireless device may use / transmit / perform one or more repetitions (e.g., uplink repetition, PUCCH repetition) of the HARQ-ACK for Msg4 / of Msg4.

[0463] In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may use a RACH resource from a second set of RACH resources (e.g., selected / determined / picked from the second set of RACH resources) to transmit Msg1 (e.g., a preamble) based on the propagation time being less than (or equal to) a threshold. In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may use a RACH resource from a second set of RACH resources (e.g., selected / determined / picked from the second set of RACH resources) to transmit Msg1 (e.g., a preamble) based on the RSRP value being less than (or equal to) a power threshold. In response to the wireless device not transmitting a TA report in / via / with Msg3 (e.g., TA report MAC CE, TA report MAC CE, TAR MAC CE, etc.), the wireless device may indicate to the base station that the wireless device may use / transmit / perform no repetitions (e.g., uplink repetition, PUCCH repetition) of the HARQ-ACK for Msg4 / of Msg4.

[0464] In one example, the one or more configuration parameters may indicate a threshold (e.g., a time threshold). In one example, the one or more configuration parameters may indicate a power threshold. In one example, Msg2 (e.g., RAR, RAR UL grant, etc.) may indicate a threshold (e.g., a time threshold). In one example, Msg2 may indicate a power threshold. In one example, Msg4 may indicate a threshold (e.g., a time threshold). In one example, Msg4 may indicate a power threshold.

[0465] In one example, a RACH resource may be referred to as a random access resource. For example, a first set of RACH resources may be referred to as a first set of random access resources. For example, a second set of RACH resources may be referred to as a second set of random access resources.

[0466] In one example, a wireless device may consider an uplink repetition (e.g., PUCCH repetition) to be applicable to a random access procedure (e.g., PUCCH repetition for Msg4 / for HARQ-ACK of Msg4) based on, for example, determining to perform / use / transmit an uplink repetition for HARQ-ACK for Msg4.

[0467] In one example, a wireless device may transmit Msg3. The wireless device may transmit Msg3 including / indicating a contention resolution identity of the wireless device (e.g., UE contention resolution identity). The wireless device may receive Msg4 in response to transmitting Msg3. In one example, Msg4 may include a PDSCH transmission / reception / transport block / message. The wireless device may decode the PDSCH transmission / reception / transport block / message. In response to receiving a PDSCH with a UE contention resolution identity, the wireless device may transmit HARQ-ACK information (e.g., for Msg4) via / on / in a PUCCH. The wireless device may perform / use / transmit PUCCH repetition of HARQ-ACK information according to one or more embodiments of the present disclosure (e.g., ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ , ​ example embodiments in

[0468] In an example embodiment, a wireless device may be enabled using a Global Navigation Satellite System (GNSS) transceiver. The wireless device may determine the location of the wireless device based on transmitting and receiving signals using the GNSS transceiver. The wireless device may use the GNSS transceiver to transmit signals to and receive signals from one or more GNSS satellites. In one example, the one or more GNSS satellites may be one or more Global Positioning System (GPS) satellites. In another example, the one or more GNSS satellites may be one or more Galileo satellites. In another example, the one or more GNSS satellites may be one or more Global Navigation Satellite System (GLONASS) satellites. In another example, the one or more GNSS satellites may be one or more BeiDou Navigation Satellite System (BDS) satellites. In another example, the one or more GNSS satellites may be one or more Quasi-Zenith Satellite System (QZSS) satellites. In another example, the one or more GNSS satellites may be one or more Indian Regional Navigation Satellite System (IRNSS) satellites. The wireless device may determine the location of the wireless based on transmitting signals to and receiving signals from one or more GNSS satellites.

[0469] In an example embodiment, a wireless device may be enabled without using a GNSS transceiver. The wireless device may determine the location of the wireless device without using a GNSS transceiver. For example, the wireless device may transmit one or more signals to and / or receive one or more signals from one or more satellites to determine the distance between the wireless device and the one or more satellites. In one example, the one or more satellites may not be GNSS satellites. The wireless device may use range-based location determination techniques (e.g., trilateration, multilateration) to determine the location of the wireless device.

[0470] In another example, the wireless device may transmit signals to and / or receive signals from one or more neighboring wireless devices (e.g., sidelink communication signals, NR sidelink communication signals, LTE device-to-device (D2D) communication signals, Bluetooth communication signals, ZigBee communication signals, Near Field Communication (NFC) signals). The wireless device may determine the location of the wireless device based on the transmission and reception of signals to / from one or more neighboring wireless devices. For example, the one or more neighboring wireless devices may know the location of the one or more neighboring wireless devices. The one or more neighboring wireless devices may determine the location of the wireless device based on, for example, the time of flight of one or more signals transmitted to and / or received from the wireless device.

[0471] In one example, the one or more neighboring wireless devices may indicate the location of the wireless device to the wireless device. The one or more neighboring wireless devices may, for example, indicate the location of the one or more neighboring wireless devices to the wireless device. In one example, the one or more neighboring wireless devices may indicate to the wireless device one or more distances between the wireless device and the one or more neighboring wireless devices. In one example, the one or more neighboring wireless devices may indicate to the wireless device one or more time-of-flight values. In one example, the one or more neighboring wireless devices may indicate to the wireless device one or more angle-of-arrival (or angle-of-departure) values.

[0472] ​ FIG. shows an example timing diagram according to one aspect of an embodiment of the present disclosure. According to Figure 27A the example, the base station transmits one or more configuration parameters to the wireless device ( Figure 27A UE in). The one or more configuration parameters include / indicate a field indicating TA reporting. The field indicating TA reporting may be enabled, for example. In response to the field indicating TA reporting to be enabled, the wireless device may transmit a TA report (e.g., TAR MAC CE) in Msg3 / with Msg3 / via Msg3. Based on the received TA report included in Msg3, the base station may determine whether an uplink repetition (e.g., PUCCH repetition) of HARQ-ACK for Msg4 (e.g., HARQ-ACK feedback, HARQ-ACK information, etc.) of Msg4 is required.

[0473] In one example, the TA reported in Msg3 / via Msg3 / with Msg3 may be greater than a time threshold. The base station may, for example, indicate to the wireless device via Msg4 to perform / use / transmit one or more repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4. In response to receiving Msg4 indicating one or more repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4, the wireless device may, for example, transmit one or more repetitions (e.g., PUCCH repetitions) of HARQ-ACK for Msg4 in / indicated / included in Msg4, or by means of / via one or more uplink resources of Msg4, or using the one or more uplink resources, or in the one or more uplink resources.

[0474] Figure 27B FIG. shows an example timing diagram according to one aspect of an embodiment of the present disclosure. According to Figure 27B the example, the base station transmits to the wireless device ( Figure 27BThe UE) in it transmits one or more configuration parameters. The one or more configuration parameters include / indicate a field indicating TA report. The field indicating TA report can be enabled, for example. In response to the field indicating TA report to be enabled, the wireless device can transmit a TA report (e.g., TAR MAC CE) in Msg3 / with Msg3 / via Msg3. Based on the received TA report included in Msg3, the base station can determine whether an uplink repetition (e.g., PUCCH repetition) of the HARQ-ACK for Msg4 (e.g., HARQ-ACK feedback, HARQ-ACK information, etc.) of Msg4 is needed.

[0475] In one example, the TA reported in Msg3 / via Msg3 / with Msg3 can be less than (or equal to) a time threshold. The base station can, for example, indicate to the wireless device via Msg4 to perform / use / transmit a non-repetition (e.g., PUCCH repetition) of the HARQ-ACK for Msg4. In response to receiving Msg4 indicating a non-repetition (e.g., PUCCH repetition) of the HARQ-ACK for Msg4, the wireless device can, for example, transmit a single transmission (e.g., without any repetition, with or without repetition, without any PUCCH repetition, with or without PUCCH repetition, etc.) of the HARQ-ACK for Msg4 in / indicated by / included in Msg4, or by means of / via one or more uplink resources of Msg4, or using the one or more uplink resources, or in the one or more uplink resources.

[0476] Figure 28 Shows an example flowchart according to one aspect of an embodiment of the present disclosure. According to Figure 28 the embodiment, the wireless device can receive one or more configuration parameters from the base station. The one or more configuration parameters can include / indicate a common TA. The one or more configuration parameters can include / indicate a threshold (e.g., time threshold, power threshold, etc.) for uplink repetition (e.g., PUCCH repetition, PUSCH repetition, PRACH repetition, etc.) of the HARQ-ACK for a random access message (e.g., Msg4, Msg2, etc.). The wireless device can not include a TA report for the random access procedure in Msg3. In response to the TA report not being included in Msg3, the wireless device can, for example, determine to perform / use / transmit one or more repetitions of the HARQ-ACK for Msg4 based on whether the propagation time (e.g., UE-gNB RTT) is greater than the threshold.

[0477] In one example, the propagation time can be greater than / higher than / exceed (or equal to) a threshold. In response to the TA report not being included in Msg3 and the propagation time can be greater than / higher than / exceed (or equal to) the threshold, the wireless device can indicate to the base station that the HARQ-ACK for Msg4 / for Msg4 requires uplink repetition (e.g., via Msg3, via the MAC CE included in Msg3, by selecting a RACH resource from a first RACH resource set, by transmitting one or more repetitions of Msg1, by transmitting one or more repetitions of Msg3, etc.). In response to indicating to the base station that the HARQ-ACK for Msg4 / for Msg4 requires uplink repetition (e.g., PUCCH repetition), the wireless device can receive one or more uplink resources for transmitting one or more repetitions of the HARQ-ACK for Msg4 / for Msg4. The wireless device can transmit the one or more repetitions of the HARQ-ACK for Msg4 / Msg4.

[0478] In one example, the propagation time can be less than (or equal to) a threshold. In response to the TA report not being included in Msg3 and the propagation time can be less than (or equal to) the threshold, the wireless device can indicate to the base station that the HARQ-ACK for Msg4 / for Msg4 does not require uplink repetition (or requires no uplink repetition) (e.g., via Msg3, via the MAC CE included in Msg3, by selecting a RACH resource from a second RACH resource set, by transmitting no repetition of Msg1, by transmitting no repetition of Msg3, etc.). In response to indicating to the base station that the HARQ-ACK for Msg4 / for Msg4 does not require uplink repetition (or requires no uplink repetition), the wireless device can receive one or more uplink resources for transmitting a single transmission of the HARQ-ACK for Msg4 / for Msg4 (e.g., with or without repetition, without any repetition, with or without PUCCH repetition, without any PUCCH repetition). The wireless device can transmit a single transmission of the HARQ-ACK for Msg4 / Msg4 (e.g., with or without repetition, without any repetition, with or without PUCCH repetition, without any PUCCH repetition).

[0479] In Figure 22A 、 Figure 22B 、 Figure 23A 、 Figure 23B 、 Figure 24A 、 Figure 24B 、 Figure 25A 、 Figure 25B 、 Figure 26A 、 Figure 26B 、 Figure 27A 、 Figure 27B and / or Figure 28In each / any embodiment, any or all of Msg1, Msg2, Msg3, and / or Msg4 can be transmitted for a random access procedure. In one example, the random access procedure can be a two-step random access procedure. In one example, the random access procedure can be a four-step random access procedure. In one example, the random access procedure can be initiated by a wireless device. In one example, the random access procedure can be initiated by a base station / gNB / eNB / NTN gateway / satellite.

[0480] In one example, a random access procedure can be initiated for initial access of a wireless device from the RRC_IDLE / RRC_INACTIVE state / mode. In one example, the random access procedure can be triggered by / for an RRC connection reestablishment procedure. In one example, when UL synchronization is out of sync, during RRC_CONNECTED or during RRC_INACTIVE, when a small data transfer (SDT) procedure is in progress, the random access procedure can be triggered by / for downlink (DL) or uplink (UL) data arrival. In one example, when there is no PUCCH resource available for SR, during RRC_CONNECTED or during RRC_INACTIVE, when the SDT procedure is in progress, the random access procedure can be triggered by / for UL data arrival. In one example, the random access procedure can be triggered by / for an SR failure. In one example, the random access procedure can be triggered by / for a request for RRC after a synchronization reconfiguration (e.g., handover). In one example, the random access procedure can be triggered by / for an RRC connection resume procedure from the RRC_INACTIVE mode / state. In one example, the random access procedure can be triggered to establish time alignment for an auxiliary timing advance group. In one example, the random access procedure can be triggered by / for a request for other system information. In one example, the random access procedure can be triggered by / for beam failure recovery. In one example, the random access procedure can be triggered by / for a consistent UL listen-before-talk failure on a special cell. In one example, the random access procedure can be triggered by / for SDT in the RRC_INACTIVE state / mode. In one example, the random access procedure can be triggered by / for positioning purposes during RRC_CONNECTED when a random access procedure is needed, e.g., when UE positioning requires timing advance.

[0481] An example method includes: receiving, by a wireless device, one or more configuration parameters, the one or more configuration parameters including / indicating: a common TA; and a threshold for uplink repetition of HARQ-ACK for Msg4 / towards Msg4; determining a propagation time based on the common TA; and transmitting a random access message indicating repetition of HARQ-ACK for Msg4 when the propagation time meets the threshold.

[0482] According to the above example method, one or more of the configuration parameters are broadcast configuration parameters;

[0483] According to one or more of the above example methods, the timing advance value is a common timing advance value.

[0484] According to one or more of the above example methods, one or more of the configuration parameters further indicate satellite ephemeris.

[0485] According to one or more of the above example methods, the determination is further based on the satellite ephemeris.

[0486] According to one or more of the above example methods, the common timing advance value is at least one of the following:

[0487] Common delay value;

[0488] Common time offset value;

[0489] Feeder link propagation time value;

[0490] Feeder link propagation distance value;

[0491] Location of the NTN gateway; and / or

[0492] Location of the ground base station / gNB / eNB.

[0493] According to one or more of the above example methods, the propagation time is at least one of the following:

[0494] Timing advance;

[0495] Round-trip time between the wireless device and the base station / gNB / eNB;

[0496] Round-trip time between the wireless device and the NTN payload;

[0497] Round-trip distance between the wireless device and the base station;

[0498] Round-trip distance between the wireless device and the NTN payload;

[0499] Time offset; and / or

[0500] Distance between the wireless device and the reference point.

[0501] According to one or more of the above example methods, one or more of the configuration parameters include / indicate the reference point.

[0502] According to one or more of the above example methods, wherein there is no field indicating a timing advance report among the one or more configuration parameters.

[0503] According to one or more of the above example methods, wherein the determination is further based on the non - existence of the field among the one or more configuration parameters.

[0504] According to one or more of the above example methods, wherein the transmission of the random access message indicating the repetition of the HARQ - ACK of Msg4 is based on the propagation time being greater than (or equal to) a threshold.

[0505] According to one or more of the above example methods, it further includes receiving Msg4 in response to the transmission.

[0506] According to one or more of the above example methods, wherein Msg4 indicates one or more uplink resources for transmitting the HARQ - ACK of Msg4.

[0507] According to one or more of the above example methods, wherein Msg4 indicates one or more repetitions of the HARQ - ACK of Msg4.

[0508] According to one or more of the above example methods, wherein the Msg4 is based on the transmission indicating one or more repetitions of the HARQ - ACK of Msg4.

[0509] According to one or more of the above example methods, it further includes transmitting the one or more repetitions of the HARQ - ACK of Msg4.

[0510] According to one or more of the above example methods, it further includes transmitting one or more repetitions of the HARQ - ACK of Msg4 via the one or more uplink resources.

[0511] According to one or more of the above example methods, it further includes transmitting a random access message 3 (Msg3).

[0512] According to one or more of the above example methods, wherein Msg3 does not include a timing advance report.

[0513] According to one or more of the above example methods, wherein the transmission of the random access message indicating the repetition of the HARQ - ACK of Msg4 based on the propagation time satisfying the threshold is in response to Msg3 not including the timing advance report.

Claims

1. A method, comprising: Transmitting, by a wireless device and for a random access procedure, a Message3, the Message3 including a field for a hybrid automatic repeat request acknowledgement (HARQ-ACK) of a Message4 indicating whether repetition is used for the random access procedure; Receiving the Message4; Transmitting, via a physical uplink control channel (PUCCH), a repetition of the HARQ-ACK for the Message4.

2. A method, comprising: Transmitting, by a wireless device and for a random access procedure, a Message3, the Message3 including a field for a hybrid automatic repeat request acknowledgement (HARQ-ACK) of a Message4 indicating whether repetition is used for the random access procedure.

3. The method according to claim 2, further comprising receiving the Message4.

4. The method according to claim 3, further comprising transmitting, via the PUCCH, a repetition of the HARQ-ACK for the Message4.

5. The method according to any one of claims 1 to 4, wherein the Message4 is a physical downlink shared channel reception including a contention resolution identity of the wireless device.

6. The method according to any one of claims 1 to 5, further comprising receiving a random access response.

7. The method according to claim 6, wherein the random access response includes a scheduling grant for the Message3.

8. The method according to any one of claims 2 to 7, wherein the Message3 is transmitted via a physical uplink shared channel (PUSCH).

9. The method according to any one of claims 1 to 8, wherein the Message3 includes a contention resolution identity of the wireless device.

10. The method according to any one of claims 1 to 9, further comprising transmitting the Message3 to a non-terrestrial network payload.

11. The method according to claim 10, wherein the non-terrestrial network payload is at least one of the following: A low Earth orbit satellite; A medium Earth orbit satellite; A geostationary orbit satellite; A non-geostationary orbit satellite; An unmanned aerial vehicle; or A drone.

12. The method according to any one of claims 1 to 11, further comprising receiving configuration parameters from a base station.

13. The method according to claim 12, wherein the configuration parameters indicate: One or more reference signals; and One or more reference signal received power (RSRP) thresholds for determining the repetition of the HARQ-ACK for the Message4.

14. The method according to claim 12 or claim 13, wherein the configuration parameters are for a cell.

15. The method according to claim 13 or claim 14, wherein the one or more reference signals are for a cell.

16. The method according to any one of claims 13 to 15, further comprising determining the repetition of the HARQ-ACK of the Message4 based on the radio link quality of the one or more reference signals.

17. The method according to claim 16, further comprising determining the repetition of the HARQ-ACK of the Message4 based on comparing the radio link quality of the one or more reference signals with one or more RSRP thresholds.

18. The method according to claim 17, wherein the Message4 indicates one or more uplink resources for a plurality of repetitions of the HARQ-ACK of the Message4.

19. The method according to claim 18, further comprising transmitting the plurality of repetitions of the HARQ-ACK of the Message4 via the one or more uplink resources and a physical uplink control channel.

20. The method according to claim 17 or claim 18, wherein the Message4 indicates one or more uplink resources for a single repetition of the HARQ-ACK of the Message4.

21. The method according to claim 20, further comprising transmitting the single repetition of the HARQ-ACK of the Message4 via the one or more uplink resources and a physical uplink control channel.

22. The method according to any one of claims 1 to 21, wherein the field is one of the following: A control command; Uplink control information; or A media access control (MAC) control element (CE).

23. A method, comprising: Receiving, by a wireless device, configuration parameters indicating: A first reference signal received power (RSRP) threshold for determining a repetition of a Message3 (Msg3) of a random access procedure; and A second RSRP threshold for determining a repetition of a hybrid automatic repeat request acknowledgement (HARQ-ACK) of a Message4 (Msg4) of the random access procedure; Transmitting the Msg3 with or without repetition based on a comparison of the RSRP of a reference signal with the first RSRP threshold; and Transmitting the Msg3 indicating whether repetition is used for the HARQ-ACK of the Msg4 based on a comparison of the RSRP of the reference signal with the second RSRP threshold.

24. A method, comprising: Receiving, by a wireless device, configuration parameters indicating a reference signal received power (RSRP) threshold for determining whether repetition is indicated for a hybrid automatic repeat request acknowledgement (HARQ-ACK) of a Message4 (Msg4) in a Message3 (Msg3) of a random access procedure; and Transmitting the Msg3 based on the RSRP threshold.

25. The method according to claim 23 or claim 24, further comprising transmitting the Msg3 to a non-terrestrial network payload.

26. The method according to claim 25, wherein the non-terrestrial network payload is at least one of the following: Low Earth Orbit satellite; Medium Earth Orbit satellite; Geostationary Orbit satellite; Non-Geostationary Orbit satellite; Unmanned Aerial Vehicle; or Drone.

27. The method according to any one of claims 24 to 26, further comprising receiving the Msg4.

28. The method according to claim 27, further comprising transmitting a repetition of the HARQ-ACK for the Msg4 via PUCCH.

29. The method according to any one of claims 24 to 28, wherein the Msg4 is a Physical Downlink Shared Channel reception including a contention resolution identity of the wireless device.

30. The method according to any one of claims 24 to 29, further comprising receiving a random access response.

31. The method according to claim 30, wherein the random access response includes a scheduling grant for the Msg3.

32. The method according to any one of claims 23 to 31, wherein the Msg3 is transmitted via a Physical Uplink Shared Channel (PUSCH).

33. The method according to any one of claims 23 to 32, wherein the Msg3 includes a contention resolution identity of the wireless device.

34. The method according to any one of claims 23 to 33, wherein the configuration parameter is for a cell.

35. The method according to claim 34, wherein the cell is a non-terrestrial network cell.

36. The method according to any one of claims 23 to 35, wherein the transmission of the Msg3 is further based on the Reference Signal Received Power (RSRP) of a reference signal.

37. The method according to claim 36, wherein the transmission of the Msg3 is further based on comparing the RSRP of the reference signal with an RSRP threshold.

38. The method according to any one of claims 23 to 37, wherein the configuration parameter further indicates a second RSRP threshold for determining the repetition of Msg3 of the random access procedure.

39. The method according to claim 38, further comprising transmitting the Msg3 with or without repetition based on a comparison of the RSRP of the reference signal with the second RSRP threshold.

40. The method according to any one of claims 23 to 39, wherein the Msg3 includes a field indicating whether repetition is used for the HARQ-ACK of the Msg4.

41. The method according to claim 40, wherein the field is at least one of the following: Control command; Uplink control information; or Medium Access Control (MAC) Control Element (CE).

42. A method, comprising: The base station receives Message3 from a wireless device and for a random access procedure, the Message3 including a field of a hybrid automatic repeat request acknowledgement (HARQ-ACK) of Message4 indicating whether repetition is used for the random access procedure; Transmit the Message4; Receive a repetition of the HARQ-ACK for the Message4 via a physical uplink control channel (PUCCH).

43. A method, comprising: The base station receives Message3 from a wireless device and for a random access procedure, the Message3 including a field of a hybrid automatic repeat request acknowledgement (HARQ-ACK) of Message4 indicating whether repetition is used for the random access procedure.

44. A method, comprising: The base station transmits configuration parameters to a wireless device, the configuration parameters indicating: A first reference signal received power (RSRP) threshold for determining repetition of Message3 (Msg3) of a random access procedure; and A second RSRP threshold for determining repetition of a hybrid automatic repeat request acknowledgement (HARQ-ACK) of Message4 (Msg4) of the random access procedure; Receive the Msg3 with or without repetition based on a comparison of the RSRP of a reference signal made by the wireless device with the first RSRP threshold; And Receive the Msg3 indicating whether repetition is used for the HARQ-ACK of the Msg4 based on a comparison of the RSRP of the reference signal made by the wireless device with the second RSRP threshold.

45. A method, comprising: The base station transmits configuration parameters indicating a reference signal received power (RSRP) threshold to a wireless device, the RSRP threshold being used to determine whether repetition is indicated in Message3 (Msg3) of a random access procedure for a hybrid automatic repeat request acknowledgement (HARQ-ACK) of Message4 (Msg4) of the random access procedure; and Receive the Msg3 based on the RSRP threshold.

46. An apparatus, comprising one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least the method according to any one of claims 1-45.

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

48. An apparatus, comprising means for performing the method according to any one of claims 1-45.

49. An apparatus, comprising circuitry configured to perform the method according to any one of claims 1-45.

50. A computer program product, encoding instructions for performing the method according to any one of claims 1-45.

Images