Time offset maintenance for non-terrestrial networks (NTNs)

Abstract

Embodiments of the present disclosure relate to time offset maintenance for non-terrestrial networks (NTNs). A user equipment (UE) associated with a non-terrestrial network (NTN) is disclosed. The UE includes a processor configured to determine a first time offset based on processing a timing offset indication signal received from a base station including the first time offset or associated parameters. In some embodiments, the first time offset indicates a time delay in a downlink (DL)-to-uplink (UL) interaction between the UE and the base station. The processor is further configured to determine a second time offset based on processing a subsequent timing offset indication signal comprising the second time offset or associated parameters received from the base station at a subsequent moment. In some embodiments, the processor is further configured to update the first time offset with the second time offset.

Description

[0001] This application is a divisional application of the invention patent application with application number 202080106548.8, application date October 23, 2020, and invention name “Time Offset Maintenance of Non-Terrestrial Network (NTN)”. Technical Field

[0002] The present disclosure relates to non-terrestrial networks (NTNs), and in particular to maintenance of time offsets in NTNs. Background Art

[0003] As the number of mobile devices connected to wireless networks and the demand for mobile data traffic continue to increase, changes are being made to system requirements and architectures to meet the current and expected rapid growth in demand. For example, wireless communication networks such as 5G New Radio (NR) systems may need to be deployed using satellites as part of non-terrestrial networks (NTNs). In one deployment scenario of NTN, satellites known as transparent satellites can act as relay stations to link user devices with land-based base stations and 5G core networks by implementing transparent payloads. In another deployment scenario, satellites known as regenerative satellites can have onboard processing capabilities to perform the functions of a base station by implementing regenerative payloads between user devices and the land-based 5G core network. Due to the wide coverage of satellites and the long distance between satellites and ground user devices, the propagation delay difference between two user devices within the beam footprint is greater than the propagation delay difference encountered in a strict terrestrial network. For example, for an NTN deploying satellites in geostationary orbit (GEO), the maximum differential delay between the lowest point and the point at the edge of the coverage area can be 10.3ms. For satellites deploying NTN in low earth orbit (LEO), the maximum differential delay may be 3.12 ms and 3.18 ms for altitudes of 600 km and 1200 km, respectively. Summary of the Invention

[0004] The purpose of the present disclosure is at least partially to address the technical problems existing in the prior art.

[0005] According to one embodiment of the present disclosure, a baseband (BB) processor of a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite serving as a base station or serving as a relay to a base station is provided, the BB processor being configured to perform operations including: determining a first time offset based on processing a timing offset indication signal including a first time offset or an associated parameter received from the base station, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, and wherein the first time offset is equal to or greater than twice a propagation delay between the UE and the base station; determining a second time offset based on processing a subsequent timing offset indication signal including a second time offset or an associated parameter received from the base station at a subsequent time, wherein the second time offset indicates a time delay in a DL to UL interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station; and updating the first time offset with the second time offset.

[0006] According to another embodiment of the present disclosure, a baseband (BB) processor of a base station (BS) operating in a non-terrestrial network (NTN) is provided, wherein the base station includes a satellite or a satellite having a relay to a user equipment (UE), and the BB processor is configured to perform operations including: sending a timing offset indication signal including a first time offset or an associated parameter to a user equipment (UE) so as to enable the UE to determine the first time offset, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than twice the propagation delay between the UE and the base station; and sending a subsequent timing offset indication signal including a second time offset or an associated parameter to the UE at a subsequent time so as to enable the UE to update the first time offset with the second time offset, wherein the second time offset indicates the time delay in the DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station.

[0007] According to another embodiment of the present disclosure, a baseband BB processor of a user equipment UE operating in a non-terrestrial network NTN having a satellite serving as a base station or serving as a relay to a base station is provided, the BB processor being configured to perform operations including: determining a time offset, wherein the time offset indicates a time delay in a downlink DL to uplink UL interaction between the UE and the base station, wherein the time offset is equal to or greater than twice a propagation delay between the UE and the base station; receiving a medium access control MAC control element CE from the base station; sending a hybrid automatic repeat request HARQ acknowledgment ACK feedback to the base station in response to receiving the MAC CE command; and determining a MAC CE activation time for activating the MAC CE command based on the determined time offset according to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command.

[0008] According to another embodiment of the present disclosure, a baseband BB processor of a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite as a base station or as a relay to a base station is provided, the BB processor being configured to perform operations including: determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than twice a propagation delay between the UE and the base station; receiving downlink control information (DCI) from the base station scheduling a DL transmission to the UE or an UL transmission from the UE, wherein the DCI indicates a mixed signal. a combined automatic repeat request HARQ process number, and wherein, when aggregation / blind retransmission is disabled, the DCI includes a single transmission of the DCI, and when aggregation / blind retransmission is enabled, the DCI includes multiple aggregation / blind retransmissions of the DCI; and based on the determined time offset, selectively processing subsequent DCI with the same HARQ process number received from the base station, wherein the subsequent DCI includes DCI received from the base station after receiving the single transmission of the DCI when aggregation / blind retransmission is disabled, or DCI received from the base station after receiving the multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled.

[0009] According to another embodiment of the present disclosure, a baseband BB processor of a user equipment UE operating in a non-terrestrial network NTN having a satellite serving as a base station or as a relay to a base station is provided, the BB processor being configured to perform operations including: determining a time offset, wherein the time offset indicates a time delay in a downlink DL to uplink UL interaction between the UE and the base station, wherein the time offset is equal to or greater than twice a propagation delay between the UE and the base station; sending a beam failure recovery request BFRQ to the base station, wherein the BFRQ indicates a beam failure; and in response to sending the BFRQ, monitoring reception of a beam failure recovery response BFRR from the base station, wherein the BFRR is monitored within a BFRR time window after sending the BFRQ, and wherein one or more parameters of the BFRR time window are determined based on the determined time offset.

[0010] According to the embodiments of the present disclosure, many technical advantages over the prior art can be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Some examples of circuits, devices and / or methods will be described below by way of example only.In this context, reference will be made to the accompanying drawings.

[0012] Figure 1 is an exemplary network according to one or more implementations described herein.

[0013] Figure 2 Non-terrestrial network (NTN) timing relationships are shown according to one embodiment of the present disclosure.

[0014] Figure 3 A simplified block diagram of a wireless communication system that facilitates updating time offsets according to one embodiment of the present disclosure is shown.

[0015] Figure 4a A simplified block diagram of a wireless communication system that facilitates determining Medium Access Control (MAC) Control Element (CE) activation timing based on a time offset is shown in accordance with one embodiment of the present disclosure.

[0016] Figure 4b Depicted is an exemplary diagram of DL MAC CE activation timing relationship in an NTN communication system according to one embodiment of the present disclosure.

[0017] Figure 4c Depicted is an exemplary diagram of UL MAC CE activation timing relationship in an NTN communication system according to one embodiment of the present disclosure.

[0018] Figure 5A simplified block diagram of a wireless communication system utilizing time offset in HARQ transmissions according to one embodiment of the present disclosure is shown.

[0019] Figure 6 A simplified block diagram of a wireless communication system utilizing a time offset to determine a time window for receiving a beam failure recovery response (BFRR) is shown according to one embodiment of the present disclosure.

[0020] Figure 7 A block diagram is shown of an apparatus that can be employed at a base station (BS), eNodeB, gNodeB, or other network device in accordance with various aspects described herein.

[0021] Figure 8 A block diagram is shown of an apparatus that can be employed at a user equipment (UE) or other network device (eg, an IoT device) in accordance with various aspects described herein.

[0022] Figure 9 A flowchart of a method for updating a time offset of a UE associated with a wireless communication system according to one embodiment of the present disclosure is shown.

[0023] Figure 10 A flow chart of a method for updating a time offset of a base station associated with a wireless communication system according to one embodiment of the present disclosure is shown.

[0024] Figure 11 A flowchart of a method for a UE associated with a wireless communication system to determine a Medium Access Control (MAC) Control Element (CE) activation timing based on a time offset according to one embodiment of the present disclosure is shown.

[0025] Figure 12 A flow chart of a method for a UE associated with a wireless communication system that utilizes a time offset in HARQ retransmissions according to one embodiment of the present disclosure is shown.

[0026] Figure 13 A flow chart of a method for a UE associated with a wireless communication system utilizing a time offset when determining a time window for receiving a beam failure recovery response (BFRR) according to one embodiment of the present disclosure is shown.

[0027] Figure 14 The architecture of a system including a core network (CN), such as a fifth generation (5G) CN (5GC), according to various embodiments is shown.

[0028] Figure 15 Exemplary components of an apparatus according to some embodiments are shown.

[0029] Figure 16An exemplary interface of a baseband circuit according to some embodiments is shown. DETAILED DESCRIPTION

[0030] In one embodiment of the present disclosure, a baseband (BB) processor for a user equipment (UE) is disclosed. The BB processor is configured to perform operations including determining a first time offset based on processing a timing offset indication signal including a first time offset or associated parameter received from a base station. In some embodiments, the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the first time offset is equal to or greater than twice the propagation delay between the UE and the base station. These operations also include: determining a second time offset based on processing a subsequent timing offset indication signal including a second time offset or associated parameter received from the base station at a subsequent moment. In some embodiments, the second time offset indicates a time delay in a DL to uplink UL interaction between the UE and the base station. In some embodiments, the second time offset is equal to or greater than twice the propagation delay between the UE and the base station. In addition, these operations include updating the first time offset with the second time offset.

[0031] In one embodiment of the present disclosure, a baseband (BB) processor for a base station (BS) operating in a non-terrestrial network (NTN) is disclosed, wherein the base station includes a satellite or a satellite having a relay to a user equipment. The BB processor is configured to perform operations including sending a timing offset indication signal including a first time offset or associated parameter to a user equipment (UE) so as to enable the UE to determine the first time offset. In some embodiments, the first time offset indicates the time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the first time offset is equal to or greater than twice the propagation delay between the UE and the base station. These operations also include: sending a subsequent timing offset indication signal including a second time offset or associated parameter to the UE at a subsequent time so as to enable the UE to update the first time offset using the second time offset. In some embodiments, the second time offset indicates the time delay in a DL to uplink UL interaction between the UE and the base station. In some embodiments, the second time offset is equal to or greater than twice the propagation delay between the UE and the base station.

[0032] In one embodiment of the present disclosure, a baseband (BB) processor for a user equipment (UE) is disclosed. The BB processor is configured to perform operations including determining a time offset. In some embodiments, the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. These operations also include: receiving a medium access control (MAC) control element (CE) command from the base station; and sending a hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback to the base station in response to receiving the MAC CE command. In addition, these operations include: determining a MAC CE activation time for activating the MAC CE command based on the determined time offset according to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command.

[0033] In one embodiment of the present disclosure, a baseband (BB) processor for a user equipment (UE) is disclosed. The BB processor is configured to perform operations including determining a time offset. In some embodiments, the time offset indicates the time delay in the downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. These operations also include: receiving downlink control information (DCI) from the base station, the DCI scheduling DL transmission to the UE or UL transmission from the UE. In some embodiments, the DCI identifies a hybrid automatic repeat request (HARQ) process number. In addition, these operations include selectively processing subsequent DCIs received from the base station with the same HARQ process number based on the determined time offset according to whether HARQ feedback, aggregate retransmission, or blind retransmission is enabled or disabled.

[0034] In one embodiment of the present disclosure, a baseband (BB) processor for a user equipment (UE) is disclosed. The BB processor is configured to perform operations including determining a time offset. In some embodiments, the time offset indicates the time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. These operations also include sending a beam failure recovery request (BFRQ) to the base station. In some embodiments, the BFRQ indicates a beam failure. In addition, these operations include monitoring to receive a beam failure recovery response (BFRR) from the base station in response to sending the BFRQ. In some embodiments, the BFRR is monitored within a BFRR time window after sending the BFRQ. In some embodiments, one or more parameters of the BFRR time window are determined based on the determined time offset.

[0035] The present disclosure will now be described with reference to the accompanying drawings, wherein similar figures are used to refer to similar elements throughout the text, and the structures and devices shown therein need not be drawn to scale. As used herein, the terms "component", "system", "interface", "circuit" and the like are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to a computer. For example, a component can be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer and / or a user equipment (e.g., a mobile phone, etc.) with a processing device. By way of example, an application and a server running on a server can also be a component. One or more components can reside in a process, and a component can be located on a computer and / or distributed between two or more computers. This article can describe a set of elements or other component sets, wherein the term "set" can be interpreted as "one or more".

[0036] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or across a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0037] As another example, a component may be a device that has a specific functionality provided by a mechanical component that operates through electrical or electronic circuitry, where the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific functionality through an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that provides the functionality of the electronic component.

[0038] The use of the word "exemplary" is intended to present concepts in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise or clear from the context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from the context to be directed to the singular form. Moreover, to the extent that the terms "comprising," "including," "having," "having," "with," or variations thereof are used in the detailed description and claims, such terms are intended to be inclusive in a manner similar to the term "comprising."

[0039] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different figures. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration and not limitation, so as to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that various aspects of the various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments due to unnecessary details.

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

[0041] A mobile communication network may include one or more types and / or generations of wireless communication networks, such as a 4th generation (4G) network, a 5th generation (5G) network, or a new radio (NR) network. Such a network may include user equipment (UE) and base stations that communicate wirelessly with each other. Such a network may also include or be connected to a non-terrestrial network (NTN), such that terrestrial network devices (e.g., user equipment (UE), base stations, etc.) may communicate with each other via non-terrestrial devices (e.g., low earth orbit (LEO) satellites, high earth orbit (GEO) satellites, etc.).

[0042] In this capacity, the satellite can operate transparently by relaying communications between the UE and the base station without the need for demodulation or remodulation. Alternatively, the satellite can operate regeneratively by using onboard processing capabilities to, for example, demodulate uplink (UL) signals and remodulate downlink (DL) signals between the UE and the base station. In some implementations, the satellite may be capable of operating as a base station or another type of network access point (AP) for a wireless terrestrial network. As such, references herein to functions performed by a base station may also or alternatively be performed by a satellite in a given scenario.

[0043] Enabling a UE to connect to a wireless terrestrial network via a satellite may enhance network connectivity and reliability by increasing the number of APs that the UE may use to communicate with the network. This may also increase the collective coverage area of ​​the network because the transmission capabilities (e.g., coverage area, coverage zone, etc.) of the satellite may be greater than the transmission capabilities of the terrestrial base stations. This increase in network coverage may result in scenarios where UEs directly connected to a terrestrial base station (e.g., UEs within the coverage area of ​​a base station) are geographically closer to the base station and therefore may have different transmission timing constraints (e.g., lower propagation delay) than UEs connected to the base station via a satellite or to a satellite operating as a base station. Additionally, UE transmission propagation delay may be at least partially affected by the type of satellite because, for example, the maximum differential delay of a GEO satellite may be 10.3 micrometers (μm), while the maximum differential delay of a LEO may be 3.12 μm and 3.18 μm, depending on the LEO altitude.

[0044] As used herein, propagation delay may be based on the UL transmission between the UE and a designated reference point (RP) (e.g., a base station, a satellite, etc.), which may include a network device that can observe the timing alignment of the UL and DL frames. In the case of a transparent satellite, the RP used to determine the propagation delay may be a base station. Conversely, in the case of a regenerative satellite, the RP used to determine the propagation delay may be a satellite. In 5G New Radio (NR), there are several different timing relationships defined for terrestrial networks (TNs). For example, K0 is the time gap between downlink control information (DCI) and the physical downlink shared channel (PDSCH). Additionally, K1 is the time gap between PDSCH reception and physical uplink control channel (PUCCH) transmission, and K2 is the time gap between DCI and the physical uplink shared channel (PUSCH). In NR Rel 16, for non-terrestrial networks (NTNs), these timing relationships may change due to the larger communication distances involved in NTNs, as their radio links go from terrestrial user equipment (UE) to satellite and back to the terrestrial network (or vice versa).

[0045] Figure 11 is an exemplary network 100 according to one or more implementations described herein. Exemplary network 100 may include UEs 110-1, 110-2, etc. (collectively, "UE 110" and individually, "UE 110"), a radio access network (RAN) 120, a core network (CN) 130, an application server 140, an external network 150, and satellites 160-1, 160-2, etc. (collectively, "satellite 160" and individually, "satellite 160"). As shown, network 100 may include a non-terrestrial network (NTN) including one or more satellites 160 (e.g., of a global navigation satellite system (GNSS)) in communication with UE 110 and RAN 120.

[0046] The systems and devices of the exemplary network 100 may operate in accordance with one or more communication standards, such as the 2nd Generation (2G), 3rd Generation (3G), 4th Generation (4G) (e.g., Long Term Evolution (LTE)), and / or 5th Generation (5G) (e.g., New Radio (NR)) communication standards of the 3rd Generation Partnership Project (3GPP). Additionally or alternatively, one or more of the systems and devices of the network 100 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., 6th Generation (6G) standards, 7th Generation (7G) standards, etc.), Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., Wireless Metropolitan Area Network (WMAN), Worldwide Interoperability for Microwave Access (WiMAX), etc.), and the like.

[0047] As shown, UE 110 may include a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more wireless communication networks). Additionally or alternatively, UE 110 may include other types of mobile or non-mobile computing devices capable of wireless communication, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld terminal, etc. In some implementations, UE 110 may include an Internet of Things (IoT) device (or IoT UE), which may include a network access layer designed for low-power IoT applications that utilize ephemeral UE connections. Additionally or alternatively, the IoT UE may utilize one or more types of technologies such as machine-to-machine (M2M) communication or machine-type communication (MTC) (e.g., to exchange data with an MTC server or other device via a public land mobile network (PLMN), proximity services (ProSe) or device-to-device (D2D) communication, sensor networks, IoT networks, and more. Depending on the scenario, the M2M or MTC exchange of data may be machine-initiated, and the IoT network may include IoT UEs (which may include uniquely identifiable embedded computing devices within the Internet infrastructure) interconnected via ephemeral connections. In some scenarios, the IoT UE may execute background applications (eg, keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0048] UE 110 may communicate and establish a connection (e.g., be communicatively coupled) with RAN 120, which may involve one or more radio channels 114-1 and 114-2, each of which may include a physical communication interface / layer. In some implementations, the UE may be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a UE capable of multiple reception and transmission (Rx / Tx) may use resources provided by different network nodes (e.g., 122-1 and 122-2), which may be connected via a non-ideal backhaul (e.g., one network node provides NR access and the other network node provides E-UTRA for LTE or NR access for 5G). In such a scenario, one network node may act as a master node (MN) and the other node may act as a secondary node (SN). The MN and SN may be connected via a network interface, and at least the MN may be connected to CN 130. In addition, at least one of the MN or the SN can operate with shared spectrum channel access, and the functions specified for the UE 110 can be used for an integrated access and backhaul mobile terminal (IAB-MT). Similar to the UE 101, the IAB-MT can access the network using one network node or using two different nodes with an enhanced dual connectivity (EN-DC) architecture, a new radio dual connectivity (NR-DC) architecture, etc.

[0049] As shown, UE 110 may also or alternatively be connected to access point (AP) 116 via interface 118, which may include an air interface that enables UE 110 to communicatively couple with AP 116. AP 116 may include a wireless local area network (WLAN), a WLAN node, a WLAN termination point, etc. Connection 1207 may include a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 116 may include a wireless fidelity protocol. Router or other AP. Figure 1 10. Although not explicitly depicted in the figure, AP 116 may be connected to another network (e.g., the Internet) without being connected to RAN 120 or CN 130. In some scenarios, UE 110, RAN 120, and AP 116 may be configured to utilize LTE-WLAN aggregation (LWA) technology or LTE WLAN radio level technology integrated with IPsec tunneling (LWIP). LWA may involve RAN 120 configuring UE 110 in the RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP may involve UE 110 using WLAN radio resources (e.g., connection interface 118) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) transmitted through connection interface 118. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0050] The RAN 120 may include one or more RAN nodes 122-1 and 122-2 (collectively, multiple RAN nodes 122, and individually, a RAN node 122) to enable connectivity between the UE 110 and the RAN 120. The RAN node 122 may include a network access point configured to provide radio baseband functionality for data and / or voice connectivity between a user and a network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, as an example, a RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next-generation base station (e.g., a 5G base station, a NR base station, a next-generation eNB (gNB), etc.). The RAN node 122 may include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., a terrestrial access point). In some scenarios, the RAN node 122 may be a dedicated physical device such as a macrocell base station and / or a low-power (LP) base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell. As described below, in some implementations, the satellite 160 may operate as a base station (e.g., the RAN node 122) relative to the UE 110. Therefore, references herein to a base station, RAN node 122, etc. may relate to implementations in which the base station, RAN node 122, etc. is a terrestrial network node, as well as implementations in which the base station, RAN node 122, etc. is a non-terrestrial network node (e.g., the satellite 160).

[0051] Some or all of the RAN nodes 122 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP may implement a RAN functional split, such as a packet data convergence protocol (PDCP) split, where the radio resource control (RRC) and PDCP layers may be operated by the CRAN / vBBUP, and other layer 2 (L2) protocol entities may be operated by individual RAN nodes 122; a medium access control (MAC) / physical (PHY) layer split, where the RRC, PDCP, radio link control (RLC), and MAC layers may be operated by the CRAN / vBBUP, and the PHY layer may be operated by individual RAN nodes 122; or a "lower PHY" split, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer may be operated by the CRAN / vBBUP, and the lower portions of the PHY layer may be operated by individual RAN nodes 122. The virtualization framework may allow idle processor cores of the RAN node 122 to perform or execute other virtualized applications.

[0052] In some implementations, the individual RAN nodes 122 may represent respective gNB distributed units (DUs) connected to a gNB control unit (CU) via respective F1 interfaces. In such implementations, the gNB-DUs may include one or more remote radio heads or radio frequency (RF) front-end modules (RFEMs), and the gNB-CUs may be operated by a server (not shown) located in the RAN 120 or by a server pool (e.g., a group of servers configured to share resources) in a manner similar to a CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 122 may be a next-generation eNB (i.e., a gNB), which may provide Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the UE 110 and may be connected to the 5G core network (5GC) 130 via an NG interface.

[0053] Any of the RAN nodes 122 can serve as an endpoint for the air interface protocol and can be the first point of contact for the UE 110. In some implementations, any of the RAN nodes 122 can perform various logical functions of the RAN 120, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and mobility management. The UEs 110 can be configured to communicate with each other or with any of the RAN nodes 122 using orthogonal frequency division multiplexing (OFDM) communication signals over multi-carrier communication channels according to various communication technologies, such as, but not limited to, OFDMA communication technologies (e.g., for downlink communications) or single-carrier frequency division multiple access (SC-FDMA) communication technologies (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0054] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 122 to the UE 110, and similar techniques can be used for uplink transmissions. The grid can be a time-frequency grid (e.g., a resource grid or a time-frequency resource grid) that represents the physical resources for the downlink in each time slot. This type of time-frequency plane representation is common for OFDM systems and makes radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block can include a set of resource elements (REs); in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0055] In addition, the RAN nodes 122 may be configured to wirelessly communicate with the UE 110 and / or each other over a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band"), an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"), or a combination thereof. The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band. The licensed spectrum may correspond to channels or frequency bands that are selected, reserved, regulated, etc. for certain types of wireless activities (e.g., wireless telecommunications network activities), while the unlicensed spectrum may correspond to one or more frequency bands that are not restricted for certain types of wireless activities. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium may depend on one or more factors, such as frequency allocations determined by a public sector organization (e.g., a government agency, a regulatory agency, etc.) or by a private sector organization involved in developing wireless communication standards and protocols.

[0056] To operate in the unlicensed spectrum, the UE 110 and the RAN node 122 may operate using license-assisted access (LAA), eLAA, and / or feLAA mechanisms. In these implementations, the UE 110 and the RAN node 122 may perform one or more known medium sensing operations or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed in accordance with a listen-before-talk (LBT) protocol.

[0057] The LAA mechanism can be built on the carrier aggregation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier (CC). In some cases, each CC may have a different bandwidth from other CCs. In a time division duplex (TDD) system, the number of CCs and the bandwidth of each CC may be the same for DL ​​and UL. CA also includes individual serving cells to provide each CC. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell can provide a primary component carrier (PCC) for both UL and DL, and can handle radio resource control (RRC) and non-access layer (NAS) related activities. Other serving cells are called SCells, and each SCell can provide a single secondary component carrier (SCC) for both UL and DL. SCCs can be added and removed as needed, and changing the PCC may require UE110 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH start positions within the same subframe.

[0058] The PDSCH may carry user data and higher-layer signaling to UE 110. The physical downlink control channel (PDCCH) may carry information regarding, among other things, the transport format and resource allocation associated with the PDSCH channel. The PDCCH may also inform UE 110 of the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information associated with the uplink shared channel. Typically, downlink scheduling (e.g., allocating control and shared channel resource blocks to UE 110-2 within a cell) may be performed on any of RAN nodes 122 based on channel quality information fed back from any of UEs 110. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UEs 110.

[0059] PDCCH uses control channel elements (CCE) to convey control information, where many CCEs (e.g., 6, etc.) can be composed of resource element groups (REGs), where REGs are defined as physical resource blocks (PRBs) in OFDM symbols. Before being mapped to resource elements, PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged, for example, using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, 8, or 16) can be defined in LTE.

[0060] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to a set of nine four physical resource elements, called EREGs. In some cases, an ECCE may have other numbers of EREGs.

[0061] The RAN nodes 122 may be configured to communicate with each other via an interface 123. In an implementation where the network 100 is an LTE system, the interface 123 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes 122 (e.g., two or more eNBs / gNBs or a combination thereof) connected to an evolved packet core (EPC) or CN 130, and / or between two eNBs connected to an EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets transmitted over the X2 interface and may be used to convey information regarding the delivery of user data between eNBs or gNBs. For example, X2-U may provide specific sequence number information about user data transmitted from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in-sequence delivery of PDCP packet data units (PDUs) for user data from the SeNB to the UE 110; information about PDCP PDUs that were not delivered to the UE 110; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; etc. X2-C may provide intra-LTE access mobility functions (e.g., including context transfer from a source eNB to a target eNB, user plane transmission control, etc.), load management functions, and inter-cell interference coordination functions.

[0062] As shown, RAN 120 can be connected (e.g., communicatively coupled) to CN 130. CN 130 may include multiple network elements 132 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 110) connected to CN 130 via RAN 120. In some implementations, CN 130 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs. Components of CN 130 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) may be used to virtualize any or all of the aforementioned network node roles or functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 130 may be referred to as a network slice, and a logical instance of a portion of CN 130 may be referred to as a network subslice. Network Function Virtualization (NFV) architecture and infrastructure can be used to virtualize one or more network functions onto physical resources including a combination of industry-standard server hardware, storage hardware, or switches (instead of being performed by proprietary hardware). In other words, NFV systems can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0063] As shown, CN 130, application server (AS) 140, and external network 150 can be connected to each other via interfaces 134, 136, and 138, which may include IP network interfaces. Application server 140 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) that provide applications that use IP bearer resources through CN 130 (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). Application server 140 may also or alternatively be configured to support one or more communication services (e.g., IP voice (VoIP session, push-to-talk (PTT) session, group communication session, social network service, etc.)) for UE 110 via CN 130. Similarly, external network 150 may include one or more of various networks, including the Internet, thereby providing network access to various additional services, information, interconnectivity, and other network features to the mobile communication network and UE 110.

[0064] As shown, exemplary network 100 may include an NTN that may include one or more satellites 160-1 and 160-2 (collectively, "satellites 160"). Satellites 160 may communicate with UE 110 via a serving link or wireless interface 162 and / or communicate with RAN 120 via a feeder link or wireless interface 164 (depicted individually as 164-1 and 164). In some implementations, satellites 160 may operate as passive or transparent network relay nodes with respect to communications between UE 110 and a terrestrial network (e.g., RAN 120). In some implementations, satellites 160 may operate as active or regenerative network nodes, such that satellites 160 may operate as base stations to UE 110 (e.g., as gNBs for RAN 120) with respect to communications between UE 110 and RAN 120. In some implementations, the satellites 160 can communicate with each other via a direct wireless interface (e.g., 166) or an indirect wireless interface (e.g., via the RAN 120 using interfaces 164-1 and 164-2). Additionally or alternatively, the satellites 160 can include GEO satellites, LEO satellites, or another type of satellite. The satellites 160 can also or alternatively relate to one or more satellite systems or architectures, such as a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Global Navigation Satellite System (GLONASS), a BeiDou Navigation Satellite System (BDS), etc. In some implementations, the satellites 160 can operate as base stations (e.g., RAN nodes 122) relative to the UE 110. Thus, references herein to base stations, RAN nodes 122, etc. can relate to implementations where the base stations, RAN nodes 122, etc. are terrestrial network nodes, as well as implementations where the base stations, RAN nodes 122, etc. are non-terrestrial network nodes (e.g., satellites 160).

[0065] Figure 2Figure 2 is an illustration of an exemplary embodiment of NTN timing relationships 200. It can be seen that the downlink control information (DCI) for the uplink grant is in slot 0 of the gNB downlink (DL) frame 202, and K2 is set to 2 slots. If there were no significant propagation delay, as in a terrestrial network (TN), the scheduled PUSCH would be received in slot 2 of the gNB DL frame 202 (based on K2). However, due to the DL propagation delay of 4 slots in the NTN (which can vary in different implementations), the DCI is received 4 slots later at the UE DL frame 204. A timing advance (TA) of 8 slots is applied to the UE uplink (UL) frame 206. In some implementations, the TA is used to determine when to send the UL frame / slot. After applying the time offset Koffset of 8 slots, the scheduled PUSCH is provided at time slot 10 of the UE UL frame 206. Due to the UL propagation delay of 4 slots, the scheduled PUSCH arrives at the gNB UL frame 208 at time slot 10, which is K2 + time offset Koffset. For NTN networks, time offset is introduced in NR Rel-16. Koffset , to account for the large propagation delay in the NTN network. In some embodiments, the time offset K offset Indicates the time delay in the downlink (DL) to uplink (UL) interaction between the UE and the base station. In some embodiments, the time delay in the DL to UL interaction refers to the time delay of the wireless signal from the base station to the UE and then back to the base station, and / or the time delay of the wireless signal from the user equipment (UE) to the base station and then back to the UE. In some embodiments, the time offset K is defined in units of time slots. offset In some embodiments, the time offset K offset For enhancing existing timing of UE transmission types (e.g. Figure 2 DCI-scheduled PUSCH, RAR-scheduled PUSCH, PUCCH, MAC CE action timing, aperiodic SRS and CRI-RS reference resources are shown).

[0066] In this embodiment, the time offset K offset is shown as being equal to 8 time slots, which is equal to twice the propagation delay (i.e., the round-trip propagation delay). In some embodiments, the propagation delay is the delay in the propagation of the signal between the UE and the base station. In some embodiments, when there is a satellite acting as a relay between the UE and the base station, the propagation delay is the sum of the propagation delay between the UE and the satellite and the propagation delay between the satellite and the base station. However, in other embodiments, the time offset K is offset It can be different from the round trip propagation delay, for example, more than twice the propagation delay. In this embodiment, the time offset K offsetThis enables the base station to determine the correct time slot for scheduled PUSCH reception. Specifically, the time slot for DCI scheduled PUSCH is K2 + time offset K offset In addition, the UE uses the time offset K offset to determine the correct time slot for the scheduled PUSCH transmission. However, in other embodiments, the time offset K may be used differently offset In this particular embodiment, Koffset is shown to be equal to the timing advance (TA), which is typically twice the propagation delay. However, in other embodiments, Koffset can be greater than TA. In some embodiments, TA and Koffset are used jointly by the UE. For example, while Koffset can be used to determine which UL time slot to use for its uplink transmission, TA is used to determine when to send the UL frame / time slot.

[0067] In some embodiments, the time offset K is determined at the base station based on the round-trip propagation delay between the UE and the base station and one or more other factors. offset In some embodiments, the base station is further configured to provide the UE with a time offset K offset Currently, the base station is configured to determine a single value for the time offset (e.g., an initial time offset) and provide the initial time offset to the UE. However, moving satellites change the propagation delay between the satellite and the UE / base station. To account for the changing propagation delay, the time offset K needs to be updated. offset This article discloses a method for allowing a base station and a UE to update a time offset K offset In addition, this paper also discloses a system, circuit and technology for utilizing the time offset K in various scenarios. offset systems, circuits and techniques.

[0068] Figure 3 A simplified block diagram of a wireless communication system 300 according to one embodiment of the present disclosure is shown. In some embodiments, the wireless communication system 300 comprises a non-terrestrial network (NTN) communication system. In some embodiments, the wireless communication system 300 facilitates updating the time offset K offset , further details of which are provided below. The wireless communication system 300 includes a base station (BS) 302 and a user equipment (UE) 304. In some embodiments, the wireless communication system 300 also includes Figure 1The satellite shown in FIG30 or BS 302 may be part of a satellite and is not shown here for ease of illustration. In some embodiments, base station 302 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G New Radio (NR) system, etc. In some embodiments, UE 304 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, etc. Base station 302 and UE 304 are configured to communicate with each other via a communication medium (e.g., air).

[0069] In some embodiments, BS 302 is configured to send a timing offset indication signal 306 to UE 304. In some embodiments, timing offset indication signal 306 includes a first time offset Koffset1 or an associated parameter. In some embodiments, timing offset indication signal 306 enables UE 304 to determine the first time offset Koffset1. In some embodiments, the associated parameters included in timing offset indication signal 306 include a parameter indicating the first time offset Koffset1 or a parameter that helps UE 304 determine the first time offset Koffset1. In some embodiments, the first time offset Koffset1 indicates a time delay in a downlink (DL) to uplink (UL) interaction between UE 304 and base station 302. In some embodiments, the first time offset Koffset1 is equal to or greater than twice the propagation delay between UE 304 and base station 302. In some embodiments, the first time offset Koffset1 is similar to the above-mentioned time offset Koffset1. offset . UE 304 is configured to process the timing offset indication signal 306 and determine the first timing offset Koffset1 based thereon. In some embodiments, BS 302 is configured to determine the first time offset Koffset1 before sending the timing offset indication signal 306 to UE 304. Alternatively, in other embodiments, BS 302 may not be configured to determine the first time offset Koffset1 before sending the timing offset indication signal 306 to UE 304. In such an embodiment, UE 304 may be configured to determine the first time offset Koffset1 based on associated parameters within the timing offset indication signal 306, and indicate back the determined first time offset Koffset1 to BS 302.

[0070] In some embodiments, the first time offset Koffset1 comprises an initial time offset to be used by the UE 304 during an initial access procedure (e.g., a random access channel (RACH) procedure) (in order to gain access to the BS 302). In some embodiments, the initial time offset comprises the time offset K utilized by the UE 304. offsetIn some embodiments, the initial time offset may include a cell-specific time offset or a beam-specific time offset. In some embodiments, the initial time offset may be broadcast from BS 302 to UE 304 via a system information signal (e.g., a system information block (SIB)). Thus, in such an embodiment, timing offset indication signal 306 includes a system information signal similar to SIB1. However, in other embodiments, the initial time offset may be provided to UE 304 via other signals (e.g., a UE-specific signal). In some embodiments, the initial time offset is signaled together with the common timing advance (TA). In some embodiments, UE 304 utilizes the initial time offset in Msg 3 and / or the ACK for Msg 4 in the 4-step RACH process. In addition, in some embodiments, UE 304 uses the initial time offset in the ACK for MsgB (SuccessRAR) and / or Msg3 for MsgB (FallbackRAR).

[0071] In some embodiments, a moving satellite changes the propagation delay between the satellite and the UE 304 / BS 302. Therefore, in order to account for the changing propagation delay, in some embodiments, the first time offset Koffset1 needs to be updated. In some embodiments, BS 302 is triggered to update the first time offset Koffset1 based on the change in propagation delay. Alternatively, in some embodiments, BS 302 is triggered to update the first time offset Koffset1 when performing beam switching between satellites. In addition, in other embodiments, other factors may also trigger BS 302 to update the first time offset Koffset1. Once BS 302 is triggered to update the first time offset Koffset1, BS 302 is configured to determine a second time offset Koffset2 to update / replace the first time offset K1. In some embodiments, BS 302 is further configured to send a subsequent timing offset indication signal 308 including the second time offset or associated parameters to enable UE 304 to determine the second time offset Koffset2. In some embodiments, the second time offset indicates a time delay in a DL-to-UL exchange between UE 304 and base station 302. In some embodiments, the second time offset is equal to or greater than twice the propagation delay between UE 304 and base station 302. In some embodiments, the associated parameters included in subsequent timing offset indication signal 308 include parameters indicating the second time offset or parameters that assist UE 304 in determining the second time offset. Alternatively, in some embodiments, once BS 302 is triggered to update the first time offset Koffset1, BS 302 may provide UE 304 with subsequent timing offset indication signal 308 without determining the second time offset Koffset2. In such embodiments, subsequent timing offset indication signal 308 may include only the associated parameters. In such embodiments, second time offset Koffset2 is determined at UE 304 based on processing subsequent timing offset indication signal 308, and the second time offset Koffset2 may be indicated from UE 304 to BS 302 by sending a timing offset update notification signal 310 (e.g., higher layer signaling) including the second time offset.

[0072] In some embodiments, the UE 304 is configured to determine a second time offset Koffset2 based on processing the subsequent timing offset indication signal 308. After determining the second time offset Koffset2, the UE 304 is further configured to update / replace the first time offset Koffset1 with the second time offset Koffset2. In some embodiments, the second time offset Koffset2 is also similar to the time offset Koffset1 explained above. offset. In some embodiments, the second time offset Koffset2 can be beam-specific, UE group-specific, or UE-specific. In some embodiments, the second time offset Koffset2 will be utilized by BS 302 / UE 304 after an initial access procedure (e.g., a RACH procedure). In some embodiments, UE 304 is triggered to determine the second time offset Koffset2 upon receiving a subsequent timing offset indication signal 308 in order to update the first time offset Koffset1. Alternatively, in other embodiments, when one or more parameters indicated in the subsequent timing offset indication signal 308 at UE 304 exceed a predefined threshold, UE 304 is triggered to determine the second time offset Koffset2 in order to update the first time offset Koffset1, further details of which are given in the following embodiments.

[0073] In one embodiment, the subsequent timing offset signal 308 includes a random access response (RAR) message that includes the second time offset. In some embodiments, the second time offset Koffset2 is signaled in the RAR message along with the timing advance (TA) command. In another embodiment, the subsequent timing offset signal 308 includes a common radio resource control (RRC) message or a dedicated RRC message that includes the second time offset. In such an embodiment, the UE 304 is triggered to determine the second time offset Koffset2 upon receiving the common RRC message or the dedicated RRC message from the BS 302 in order to update the first time offset Koffset1. In some embodiments, the common RRC message is suitable for beam-specific K offset , and dedicated RRC messages are suitable for UE-specific K offset In yet another embodiment, the subsequent timing offset signal 308 includes group-common downlink control information (DCI), the DCI including the second time offset. Additionally, in some embodiments, the subsequent timing offset signal 308 includes dedicated DCI, the dedicated DCI including the second time offset or a parameter indicative of the second time offset.

[0074] In some embodiments, the dedicated DCI may include a time offset field (e.g., a Koffset field) that includes the second time offset Koffset2. Alternatively, in other embodiments, the Koffset field may include an entry index to a preconfigured table of Koffsets (i.e., a parameter indicating the second time offset Koffset2). Furthermore, in some embodiments, the Koffset field may include a relative Koffset (i.e., a parameter indicating the second time offset Koffset2). In such an embodiment, the UE 304 is configured to determine the second time offset Koffset2 by adding the relative Koffset to the first time offset, as given in equation (1) below.

[0075] Koffset_new=Koffset_old+relative Koffset (1)

[0076] Where Koffset_new is the second time offset and Koffset_old is the first time offset.

[0077] In an embodiment where the subsequent timing offset indication signal 308 includes a group common DCI or a dedicated DCI, the UE 304 is triggered upon receiving the group common DCI or the dedicated DCI to determine the second time offset Koffset2 in order to update the first time offset Koffset1. In some embodiments, the group common DCI is suitable for UE group specific K offset , and dedicated DCI is suitable for UE-specific K offset In addition, in another embodiment, the subsequent timing offset signal 308 includes a dedicated time offset medium access control (MAC) control element (CE), such as a Koffset MAC CE including a second time offset, a timing advance (TA) command MAC CE including a second time offset, or a timing drift rate MAC CE including a second time offset. In such an embodiment, the UE 304 is triggered to determine the second time offset Koffset2 upon receiving the dedicated time offset MAC CE including the second time offset, the TA command MAC CE including the second time offset, or the timing drift rate MAC CE including the second time offset, so as to update the first time offset Koffset1.

[0078] Furthermore, in another embodiment, the subsequent timing offset signal 308 includes a (TA) command MAC CE without the second time offset Koffset2. In such an embodiment, the second time offset Koffset2 is derived from the TA command included in the TA command MAC CE. Specifically, first, a new TA value TA_new is determined based on the TA command in the TA MAC CE, as given by:

[0079] TA_new=TA_old+TA_command (2)

[0080] Where TA_old is the old value of TA, and TA_command is the TA command included in the TA command MAC CE. A second time offset Koffset2 is then determined based on TA_new. In some embodiments, the second time offset Koffset2 is a function of TA_new. In some embodiments, the relationship between TA_new and the second time offset Koffset2 is predefined. In such embodiments, upon receiving a TA command MAC CE without the second time offset Koffset2, UE 304 is triggered to determine the second time offset Koffset2 in order to update the first time offset Koffset1.

[0081] In another embodiment, the subsequent timing offset signal 308 includes a random access response message. However, in this embodiment, the RAR message does not include the second time offset Koffset2 as described above. Instead, in such an embodiment, the second time offset Koffset2 is derived at the UE 304 based on the TA command included in the RAR message. Specifically, first, a new value of TA, TA_new, is derived based on the TA command in the RAR message and the common TA, as given by:

[0082] TA_new = TA command in RAR + public TA (2)

[0083] In some embodiments, a common TA may be provided to the UE 304 via higher layer signaling from the BS 302. After determining TA_new, a second time offset Koffset2 is determined based on TA_new. In some embodiments, the second time offset Koffset2 is a function of TA_new. For example, if a0 <= TA_new < a1, then Koffset_new = b0; if a1 <= TA_new < a2, then Koffset_new = b1; and so on, where Koffset_new is the second time offset Koffset2. In some embodiments, in addition to TA_new, the second time offset Koffset2 may also depend on the UL or DL parameter set (e.g., subcarrier spacing (SCS)). For example, if SCS = 15 kHz, a0 <= TA_new < a1, then Koffset_new = b0; if a1 <= TA_new < a2, then Koffset_new = b1, and so on. Similarly, if SCS = 30 kHz, a0 <= TA_new < a1′, then Koffset_new = b0; if a1′ <= TA_new < a2′, then Koffset_new = b1′, and so on.

[0084] Alternatively, in some embodiments, the subsequent timing offset signal 308 includes a timing drift rate indication signal, and the timing drift rate indication signal includes a timing drift rate R_drift. In some embodiments, the timing drift rate R_drift may include a dedicated R_drift or a common R_drift. In some embodiments, R_drift indicates the change / drift of the satellite position and also takes into account the moving satellite Doppler shift. In such an embodiment, the second time offset Koffset2 is derived at the UE 304 based on the R_drift indicated in the timing drift rate indication signal. Specifically, the second time offset Koffset2 is derived at the UE 304 based on the autonomously maintained TA that varies as a function of the timing drift rate R_drift. When the timing drift rate indication signal is received, first, a new value TA_new of the autonomously maintained TA is determined based on the earlier / older value TA_old of the autonomously maintained TA and R_drift, as given below:

[0085] TA_new = TA_old + R_drift * Delta_t (3)

[0086] Where Delta_t is the time interval between the UE receiving two timing drift rate or TA command MAC CEs. A second time offset, Koffset2, is then derived based on TA_new. In some embodiments, the second time offset, Koffset2, is a function of TA_new. In some embodiments, the relationship between TA_new and the second time offset, Koffset2, is predefined.

[0087] In such an embodiment, UE 304 is triggered to determine the second time offset Koffset2 in order to update the first time offset Koffset1 only when TA_new exceeds a predefined threshold. Thus, in embodiments where TA_new exceeds the predefined threshold, UE 304 determines the second time offset Koffset2 based on TA_new and autonomously updates the first time offset Koffset1 with the second time offset Koffset2. Alternatively, in embodiments where TA_new does not exceed the predefined threshold, UE 304 does not determine the second time offset Koffset2. In some embodiments, BS 302 is aware of the value of the second time offset derived at UE 304 based on knowledge of the UE's autonomously maintained TA. Alternatively, in other embodiments, UE 304 may trigger higher layer signaling (e.g., timing offset update notification signal 310) to notify BS 302 of the determined second time offset Koffset2.

[0088] Return Reference Figure 3In some embodiments, BS 302 may be further configured to determine a third time offset Koffset3 to update / replace the second time offset Koffset2 at a subsequent time. More specifically, BS 302 may be configured to update the time offset in subsequent iterations based on the changing propagation delay or other relevant factors. In such an embodiment, BS 302 may be configured to provide another timing offset indication signal (not shown) to UE 304 to update the second time offset Koffset2 with the third time offset Koffset3. To account for this possibility, even though the first time offset Koffset1 is explained above as the initial time offset used during the initial access procedure, in other embodiments, the first time offset Koffset1 may include a time offset obtained by updating / replacing the initial time offset in one or more subsequent iterations. In other words, the first time offset Koffset1 may be similar to the second time offset Koffset2 obtained based on updating the initial time offset in one or more iterations. Therefore, in such an embodiment, timing offset indication signal 306 may include any of the signals explained above with respect to subsequent timing offset indication signal 308. Thus, although not shown, in such an embodiment, BS 302 may be configured to provide one or more timing offset indication signals to UE 304 prior to providing timing offset indication signal 306 to enable UE 304 to determine the initial time offset and one / or more previous iterations of the time offset.

[0089] Figure 4a A simplified block diagram of a wireless communication system 400 according to one embodiment of the present disclosure is shown. In some embodiments, the wireless communication system 400 comprises a non-terrestrial network (NTN) communication system. In some embodiments, the wireless communication system 400 facilitates determining a medium access control (MAC) control element (CE) activation timing based on a time offset, further details of which are provided below. The wireless communication system 400 comprises a base station (BS) 402 and a user equipment (UE) 404. In some embodiments, the wireless communication system 400 further comprises a base station (BS) 402 and a user equipment (UE) 404. Figure 1 The satellite shown in FIG40 , or BS 402, may be part of a satellite and is not shown here for ease of illustration. In some embodiments, base station 402 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G New Radio (NR) system, or the like. In some embodiments, UE 404 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, or the like. Base station 402 and UE 404 are configured to communicate with each other via a communication medium (e.g., air).

[0090] In some embodiments, BS 402 is configured to send a timing offset indication signal 406 to UE 404. In some embodiments, timing offset indication signal 406 enables UE 404 to determine a time offset Koffset. In some embodiments, timing offset indication signal 406 includes the time offset Koffset or an associated parameter. In some embodiments, the associated parameter included in timing offset indication signal 406 includes a parameter indicating the time offset or a parameter that assists UE 404 in determining the time offset Koffset. In some embodiments, BS 402 is configured to determine the time offset Koffset before sending timing offset indication signal 406 to UE 404. Alternatively, in other embodiments, BS 402 may send timing offset indication signal 406 without determining the time offset Koffset. In such embodiments, timing offset indication signal 406 only includes the associated parameter. In some embodiments, time offset Koffset indicates a time delay in a downlink (DL) to uplink (UL) exchange between UE 404 and base station 402. In some embodiments, the time offset Koffset is equal to or greater than twice the propagation delay between the UE 404 and the base station 402. In some embodiments, the time offset Koffset is similar to the time offset Koffset described above with respect to Figure 2 and Figure 3 The time offset K offset The UE 404 is configured to process the timing offset indication signal 406 and determine a timing offset Koffset based thereon.

[0091] In some embodiments, BS 402 is further configured to send a medium access control (MAC) control element (CE) command 408 to UE 404. In some embodiments, MAC CE command 408 is included as part of a physical downlink shared channel (PDSCH). In some embodiments, MAC CE command 408 may include a downlink (DL) MAC CE. In some embodiments, the DL MAC CE is configured to configure UE 404 to receive a DL transmission 412 from BS 402. Alternatively, in other embodiments, MAC CE command 408 may include an uplink (UL) MAC CE. In some embodiments, the UL MAC CE is configured to configure UE 404 to send an UL transmission 414 to BS 402. UE 404 is configured to receive and process MAC CE command 408. UE 404 is further configured to generate and send hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback 410 in response to receiving MAC CE command 408.

[0092] In addition, the UE 404 is configured to determine a MAC CE activation time for activating the MAC CE command based on the determined time offset, depending on whether the MAC CE command 408 includes a DL MAC CE command or a UL MAC CE command. When the MAC CE command 408 includes a DL MAC CE command, the MAC CE activation time of the DL MAC CE command is referred to as the DL MAC CE activation time. In some embodiments, the DL MAC CE activation time determined at the UE 404 includes the time at which the DL transmission 412 (configured by the DL MAC CE command 408) is received from the BS 402. When the MAC CE command 408 includes a UL MAC CE command, the MAC CE activation time of the UL MAC CE command is referred to as the UL MAC CE activation time. In some embodiments, the UL MAC CE activation time determined at the UE 404 includes the time for sending the UL transmission 414 (configured by the UL MAC CE command 408) to the BS 402.

[0093] When the MAC CE command 408 includes a DL MAC CE command, the DL MAC CE activation time is determined to correspond to a time instant (X + time offset) after the HARQ-ACK feedback 410 is sent. In some embodiments, X is a predefined number and may be less than or equal to 3 ms. In some embodiments, X and the time offset are measured in time slots. Alternatively, in other embodiments, X and the time offset are measured in milliseconds (ms). In some embodiments, the time offset is used to compensate for the propagation delay between the UE 404 and the base station 402. In other embodiments, the time offset is used to compensate for the propagation delay between the UE 404 and the reference point. In some embodiments, the reference point may be defined as a point at which the timing alignment of the uplink and downlink frames can be observed. The reference point may be set at the satellite, at the base station, or anywhere in the serving link (i.e., the UE to satellite link) or anywhere in the feeder link (i.e., the satellite to base station link). After determining the DL MAC CE activation time, the UE 404 is further configured to activate the DL MAC CE command at the determined DL MAC CE activation time. In some embodiments, activating the DL MAC CE command includes receiving a DL transmission 412 as configured by the DL MAC CE command 408. Figure 4b An exemplary diagram of a DL MAC CE activation timing relationship 420 in an NTN communication system according to one embodiment of the present disclosure is depicted. DL MAC CE 422 (similar to Figure 4a MAC CE command 408 in the MAC CE command 408) from the BS (e.g., Figure 4a402 in the BS) to the UE (e.g., Figure 4a UE 404 in).

[0094] After a propagation delay of 4 slots, the DL MAC CE 422 is received at the UE DL frame 428. By considering the timing advance (TA) of 8 slots, the HARQ-ACK feedback 424 is sent to the BS at slot 10 of the UE UL frame 430 (similar to Figure 4a 4. After the HARQ-ACK feedback 424 is sent, the DL MAC CE activation time is determined at slot 20 of the UE UL frame 430, which is (X+Koffset) slots after the HARQ-ACK feedback 424 is sent. In some embodiments, the DL MAC CE activation time is determined to be (X+Koffset) slots after the HARQ-ACK feedback 424 is sent to account for the propagation delay in receiving the HARQ-ACK feedback 424 at the BS (i.e., at the gNB UL frame 432) and to account for the propagation delay in sending DL transmissions from the BS to the UE. After the DL MAC CE activation time is determined, the DL transmission is received at the UE at slot 20 (e.g., Figure 4a DL transmission 412 in).

[0095] Return Reference Figure 4a , when the MAC CE command 408 includes a UL MAC CE command, the UL MAC CE activation time is determined to correspond to a time K milliseconds (ms) after sending the HARQ-ACK feedback 410. In some embodiments, K is a predefined number. In some embodiments, K is equal to 3. In other words, in some embodiments, the UL MAC CE activation time is determined to correspond to a time 3 ms after sending the HARQ-ACK feedback 410. After determining the UL MAC CE activation time, the UE 404 is further configured to activate the UL MAC CE command at the determined UL MAC CE activation time. In some embodiments, activating the UL MAC CE command includes sending an UL transmission 414 as configured by the UL MAC CE command 408. Figure 4c Depicted is an exemplary diagram of UL MAC CE activation timing relationship 440 in an NTN communication system according to one embodiment of the present disclosure.

[0096] Use slot 0 of gNB DL frame 446 to send UL MAC CE 442 (similar to Figure 4a MAC CE command 408 in the MAC CE command 408) from the BS (e.g., Figure 4a 402 in the BS) to the UE (e.g., Figure 4a4 in the UE 404). After a propagation delay of 4 slots, the UL MAC CE 442 is received at the UE DL frame 448. By applying a timing advance (TA) of 8 slots, a HARQ-ACK feedback 444 is sent to the BS at slot 10 of the UE UL frame 450 (similar to Figure 4a After sending the HARQ-ACK feedback 444, a UL MAC CE activation time is determined at slot 13 of the UE UL frame 430, which is 3 ms after sending the HARQ-ACK feedback 444. After determining the UL MAC CE activation time, a UL transmission (e.g., Figure 4a UL transmission 414 in).

[0097] Figure 5 A simplified block diagram of a wireless communication system 500 according to one embodiment of the present disclosure is shown. In some embodiments, the wireless communication system 500 comprises a non-terrestrial network (NTN) communication system. In some embodiments, the wireless communication system 500 utilizes time offsets in HARQ retransmissions, further details of which are provided below. The wireless communication system 500 comprises a base station (BS) 502 and a user equipment (UE) 504. In some embodiments, the wireless communication system 500 further comprises a Figure 1 The satellite shown in FIG5 , or BS 502, may be part of a satellite and is not shown here for ease of illustration. In some embodiments, base station 502 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G New Radio (NR) system, or the like. In some embodiments, UE 504 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, or the like. Base station 502 and UE 504 are configured to communicate with each other via a communication medium (e.g., air).

[0098] In some embodiments, BS 502 is configured to send a timing offset indication signal 506 to UE 504. In some embodiments, timing offset indication signal 506 enables UE 504 to determine a time offset Koffset. In some embodiments, timing offset indication signal 506 includes the time offset Koffset or an associated parameter. In some embodiments, the associated parameter included in timing offset indication signal 506 includes a parameter indicating the time offset or a parameter that assists UE 504 in determining the time offset Koffset. In some embodiments, BS 502 is configured to determine the time offset Koffset before sending timing offset indication signal 506 to UE 504. Alternatively, in other embodiments, BS 502 may send timing offset indication signal 506 without determining the time offset Koffset. In such embodiments, timing offset indication signal 506 only includes the associated parameter. In some embodiments, time offset Koffset indicates a time delay in a downlink (DL) to uplink (UL) exchange between UE 504 and base station 502. In some embodiments, the time offset Koffset is equal to or greater than twice the propagation delay between the UE 504 and the base station 502. In some embodiments, the time offset Koffset is similar to the time offset Koffset described above with respect to Figure 2 and Figure 3 The time offset K offset The UE 504 is configured to process the timing offset indication signal 506 and determine a timing offset Koffset based thereon.

[0099] In some embodiments, BS 502 is further configured to send DL downlink control information (DCI) 508 to UE 504. In some embodiments, DL DCI 508 schedules a DL transmission (not shown) from BS 502 to UE 504. In some embodiments, DL DCI 508 identifies a first hybrid automatic repeat request (HARQ) process number. Although not shown, in some embodiments, a DL transmission may be sent as part of / along with DL DCI 508. Upon receiving DL DCI 508, UE 504 is further configured to send HARQ ACK feedback 510 in response to receiving DL DCI 508 or an associated DL transmission. In some embodiments, HARQ-ACK feedback 510 is sent by UE 504 to acknowledge (ACK) or negatively acknowledge (NACK) receipt of DL DCI 508 or an associated DL transmission.

[0100] In some embodiments, the UE 504 and the BS 502 are configured with hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback or HARQ retransmissions (e.g., via DL DCI 508). Thus, when the HARQ-ACK feedback 510 from the UE 504 includes a NACK, or when no HARQ-ACK feedback 510 from the UE is received at the BS 502 within a predefined time interval from the transmission of the DL DCI 512, the BS 502 is further configured to transmit a subsequent DL DCI 508 having the same first HARQ process number as the DL DCI 508 to the UE 504. In some embodiments, the UE 504 is further configured to receive the subsequent DL DCI 512. In some embodiments, aggregated retransmissions or blind retransmissions of the DL DCI 508 are disabled. To disable aggregated retransmissions of the DL DCI 508, an aggregation factor within the DL DCI 508 or the corresponding physical downlink shared channel (PDSCH) configuration is not configured or is configured to 1. Alternatively or additionally, the Time Domain Resource Allocation (TDRA) field within DL DCI 508 does not indicate aggregate retransmissions. To disable blind retransmissions of DL DCI, DL DCI 508 indicates no future blind transmissions. In embodiments where aggregate / blind transmissions are disabled, both DL DCI 508 and HARQ-ACK feedback 510 comprise a single transmission. Thus, in such embodiments, subsequent DL DCI 512 comprises DL DCI received at UE 504 after the single transmission of HARQ-ACK feedback 510 is sent to BS 502.

[0101] Alternatively, in other embodiments, aggregate retransmission or blind retransmission of DL DCI is enabled. To enable aggregate retransmission of DL DCI, the aggregation factor within the DL DCI 508 or the corresponding physical downlink shared channel (PDSCH) configuration is configured with a specific number of retransmissions. Alternatively or additionally, the time domain resource allocation (TDRA) field within the DL DCI 508 indicates aggregate retransmission. To enable blind retransmission of DL DCI, the DL DCI 508 indicates future blind transmission. In an embodiment in which aggregate / blind transmission is enabled, although not shown, the DL DCI 508 includes multiple aggregate / blind retransmissions of the DL DCI, and the HARQ-ACK feedback 510 includes corresponding multiple HARQ-ACK feedback. Specifically, in such an embodiment, multiple aggregate / blind retransmissions of the DL DCI are sent from the BS 502 to the UE 504 (e.g., at predefined time intervals) without waiting for corresponding HARQ-ACK feedback from the UE 504. In some embodiments, the number of transmissions within the multiple aggregated / blind transmissions is predefined (e.g., within the DL DCI 508). Thus, in such embodiments, the subsequent DL DCI 512 includes the DL DCI received at the UE 504 after the last of the multiple HARQ-ACK feedbacks is sent to the BS 502.

[0102] Upon receiving a subsequent DL DCI 512 indicating the same first HARQ process number as in the DL DCI 508, the UE 504 is configured to selectively process the subsequent DL DCI 512 based on a time offset derived from the timing offset indication signal 506. Specifically, when aggregation / blind retransmission is disabled and HARQ-ACK feedback is enabled, the UE 504 is configured to process the subsequent DL DCI 512 when the subsequent DL DCI 512 is received at a time period / time after a time equal to the time offset of the single transmission of the HARQ-ACK feedback 510. Furthermore, when the subsequent DL DCI 512 is received at a time period / time equal to the time offset of the single transmission of the HARQ-ACK feedback 510, the UE 504 is configured not to process (ignore processing) the subsequent DL DCI 512. In such an embodiment, the UE 504 may be further configured to send an error signal (not shown) indicating that the subsequent DL DCI 512 was not processed.

[0103] In an embodiment where aggregation / blind retransmission is enabled and HARQ-ACK feedback is enabled, the UE 504 is configured to process the subsequent DL DCI 512 when the subsequent DL DCI 512 is received at a time period / time after a time equal to the time offset from the transmission of the last HARQ-ACK feedback in the plurality of HARQ-ACK feedbacks 510. In addition, when the subsequent DL DCI 512 is received at a time period / time within a time equal to the time offset from the transmission of the last HARQ-ACK feedback in the plurality of HARQ-ACK feedbacks 510, the UE 504 is configured not to process (ignore processing) the subsequent DL DCI 512. In such an embodiment, the UE 504 may be further configured to send an error signal (not shown) indicating that the subsequent DL DCI 512 was not processed. In some embodiments, processing the subsequent DL DCI 512 based on the time offset is based on the fact that a time at least equal to the time offset is required between sending the HARQ-ACK feedback 510 (or the last HARQ-ACK feedback in the multiple HARQ-ACK feedbacks 510) from the UE 504 and receiving the subsequent DL DCI 512 at the UE 504.

[0104] Return Reference Figure 5 In some embodiments, BS 502 is further configured to send downlink control information (DCI) 514 to UE 504. In some embodiments, UL DCI 514 is configured to schedule an UL transmission 516 from UE 504 to BS 502. In some embodiments, UL DCI 514 identifies a second hybrid automatic repeat request (HARQ) process number. In this embodiment, UL DCI 514 is shown as being sent after sending DL DCI 508. However, in other embodiments, UL DCI 514 may be sent without sending DL DCI 508. In other words, in some embodiments, UL DCI 514 may be sent independently of sending DL DCI 508. UE 504 is configured to receive and process UL DCI 514. After processing UL DCI 514, UE 504 is further configured to send UL transmission 516 to BS 502. In some embodiments, the UE 504 and the BS 502 are configured with HARQ retransmissions (e.g., via the UL DCI 514). Accordingly, the BS 502 is further configured to send a subsequent UL DCI 518 having the same second HARQ process number as the UL DCI 514 to the UE 504 when no UL transmission 516 from the UE 504 is received at the BS 502 within a predetermined time interval from the sending of the UL DCI 514.

[0105] In some embodiments, UE 504 is further configured to receive subsequent UL DCI 518. In some embodiments, aggregated retransmissions or blind retransmissions of UL DCI 514 are disabled. To disable aggregated retransmissions of UL DCI 514, the aggregation factor within the UL DCI 514 or the corresponding physical uplink shared channel (PUSCH) configuration is not configured or is configured to 1. Alternatively or additionally, the time domain resource allocation (TDRA) field within the UL DCI 514 does not indicate aggregated retransmissions. To disable blind retransmissions of UL DCI 514, the UL DCI 514 indicates no future blind transmissions. In embodiments where aggregated / blind transmissions are disabled, both the UL DCI 514 and the UL transmission 516 comprise a single transmission. Thus, in such embodiments, the subsequent UL DCI 518 comprises the UL DCI received at UE 504 after the single transmission of UL transmission 516 is sent to BS 502.

[0106] Alternatively, in other embodiments, aggregated or blind retransmissions of UL DCI 514 are enabled. To enable aggregated retransmissions of UL DCI 514, an aggregation factor within the UL DCI 514 or a corresponding physical uplink shared channel (PUSCH) configuration is configured with a specific number of retransmissions. Alternatively or additionally, a time domain resource allocation (TDRA) field within the UL DCI 514 indicates aggregated retransmissions. To enable blind retransmissions of UL DCI 514, the UL DCI 514 indicates future blind transmissions. In embodiments where aggregated / blind transmissions are enabled, although not shown, the UL DCI 514 includes multiple aggregated / blind retransmissions of the UL DCI, and the UL transmission 516 includes corresponding multiple UL transmissions. Specifically, in such embodiments, multiple aggregated / blind retransmissions of the UL DCI are transmitted from the BS 502 to the UE 504 (e.g., at predefined time intervals) without waiting for corresponding UL transmissions from the UE 504. Thus, in such an embodiment, subsequent UL DCI 518 includes UL DCI received at UE 504 after sending the last UL transmission of the multiple UL transmissions to BS 502.

[0107] Upon receiving a subsequent UL DCI 518 indicating the same HARQ process number as in the UL DCI 514, the UE 504 is configured to selectively process the subsequent UL DCI 518 based on the time offset derived from the timing offset indication signal 506. Specifically, when aggregation / blind retransmission is disabled, the UE 504 is configured to process the subsequent UL DCI 518 when the subsequent UL DCI 518 is received at a time period / time equal to the time offset from the transmission of the single UL transmission 516. Furthermore, when the subsequent UL DCI 518 is received at a time period / time equal to the time offset from the transmission of the single UL transmission 516, the UE 504 is configured not to process (ignore processing) the subsequent UL DCI 518. In such an embodiment, the UE 504 may be further configured to send an error signal (not shown) indicating that the subsequent UL DCI 518 was not processed.

[0108] In embodiments where aggregation / blind retransmission is enabled, when a subsequent UL DCI 518 is received at a time period / time after a time equal to the time offset from the transmission of the last UL transmission in the plurality of UL transmissions 516, the UE 504 is configured to process the subsequent UL DCI 518. Furthermore, when a subsequent UL DCI 518 is received at a time period / time equal to the time offset from the transmission of the last UL transmission in the plurality of UL transmissions 516, the UE 504 is configured not to process (or ignore processing) the subsequent UL DCI 518. In such embodiments, the UE 504 may be further configured to send an error signal (not shown) indicating that the subsequent UL DCI 518 was not processed. In some embodiments, processing the subsequent UL DCI 512 based on the time offset is based on the fact that a time at least equal to the time offset is required between the transmission of the UL transmission 516 (or the last UL transmission in the plurality of UL transmissions 516) from the UE 504 and the receipt of the subsequent UL DCI 518 at the UE 504.

[0109] Figure 6 A simplified block diagram of a wireless communication system 600 according to one embodiment of the present disclosure is shown. In some embodiments, the wireless communication system 600 comprises a non-terrestrial network (NTN) communication system. In some embodiments, the wireless communication system 600 utilizes a time offset when determining a time window for receiving a beam failure recovery response (BFRR), further details of which are provided below. The wireless communication system 600 comprises a base station (BS) 602 and a user equipment (UE) 604. In some embodiments, the wireless communication system 600 further comprises a user equipment (UE) 604. Figure 1The satellite shown in FIG6 , or BS 602, may be part of a satellite and is not shown here for ease of illustration. In some embodiments, base station 602 is equivalent to an eNodeB in an LTE system, a gNodeB in a 5G New Radio (NR) system, or the like. In some embodiments, UE 604 may include a mobile phone, a tablet computer, an Internet of Things (IoT) device, a vehicle-to-everything (V2X) UE, or the like. Base station 602 and UE 604 are configured to communicate with each other via a communication medium (e.g., air).

[0110] In some embodiments, BS 602 is configured to send a timing offset indication signal 606 to UE 604. In some embodiments, timing offset indication signal 606 enables UE 604 to determine a time offset Koffset. In some embodiments, timing offset indication signal 606 includes the time offset Koffset or associated parameters. In some embodiments, the associated parameters included in timing offset indication signal 606 include parameters indicating the time offset or parameters that assist UE 604 in determining the time offset Koffset. In some embodiments, BS 602 is configured to determine the time offset Koffset before sending timing offset indication signal 606 to UE 504. Alternatively, in other embodiments, BS 602 may send timing offset indication signal 606 without determining the time offset Koffset. In such embodiments, timing offset indication signal 606 only includes associated parameters. In some embodiments, time offset Koffset indicates a time delay in a downlink (DL) to uplink (UL) exchange between UE 604 and base station 602. In some embodiments, the time offset Koffset is equal to or greater than twice the propagation delay between the UE 604 and the base station 602. In some embodiments, the time offset Koffset is similar to the time offset Koffset described above with respect to Figure 2 and Figure 3 The time offset K offset The UE 604 is configured to process the timing offset indication signal 606 and determine a timing offset Koffset based thereon.

[0111] In some embodiments, UE 604 is further configured to send a beam failure recovery request (BFRQ) 608 to BS 602. In some embodiments, BFRQ 608 indicates a beam failure. In some embodiments, BFRQ 608 includes a new beam index indicating a new beam. BS 602 is configured to receive and process BFRQ 608. When BFRQ 608 is successfully processed at base station 602, base station 602 is configured to send a beam failure recovery response (BFRR) 610 to UE 604. In some embodiments, BFRR 610 acknowledges receipt of BFRQ 608. UE 604 is further configured to receive and process BFRR 610. In some embodiments, UE 604 is configured to monitor for BFRR 610 prior to receiving and processing it. In some embodiments, the UE 604 is configured to monitor the BFRR 610 within a BFRR time window after sending the BFRQ 608. In some embodiments, the BFRR time window includes a time period during which the BFRR 610 is monitored. In some embodiments, one or more parameters of the BFRR time window are determined based on a time offset derived from the timing offset indication signal 606 to account for a large propagation delay between sending the BFRQ 608 and receiving the BFRR 610 in the NTN communication system.

[0112] In some embodiments, the BFRR time window includes a time period corresponding to (N + time offset) time slots from the time BFRQ 608 is sent to the BS 602. In some embodiments, N is a predefined number. In some embodiments, N is equal to 4. Alternatively, in other embodiments, the BFRR time window start time is offset by at least a time corresponding to the time offset from the time BFRQ 608 is sent. In other words, the BFRR time window begins after a time corresponding to the time offset from the time BFRQ 608 is sent. For example, in some embodiments, for primary cell (Pcell) beam failure recovery, the BFRR time window begins after a time corresponding to (Y + time offset) time slots after the contention-free physical random access channel (PRACH) including the BFRQ 608 is sent to the base station 602. In some embodiments, Y is a predefined number. In some embodiments, Y is equal to 4. In addition, in some embodiments, for secondary cell (Scell) beam failure recovery, the BFRR time window starts after a time corresponding to Koffset (or time offset) time slots after a scheduling request (SR) / medium access control (MAC) control element (CE) including a BFRQ 608 is sent to the base station 602.

[0113] In some embodiments, aggregate retransmissions or blind retransmissions (e.g., contention-free preamble transmissions) of the BFRQ 608 may be supported. In such embodiments, the BFRQ 608 includes multiple transmissions of the BFRQ (according to a predefined number of retransmissions). In such embodiments, the BFRR 610 is monitored within a BFRR time window after the first or last retransmission of the multiple retransmissions of the BFRQ. Return to Reference Figure 6 In some embodiments, when no BFRR 610 is received from the base station 602 within the BFRR time window, the UE 604 is further configured to send a subsequent BFRQ 612 to the base station 602. In some embodiments, sending the subsequent BFRQ 612 is equivalent to resending the BFRQ 608.

[0114] refer to Figure 7 , shows a block diagram of an apparatus 700 that can be employed at a base station (BS), eNodeB, gNodeB, or other network device according to various aspects described herein. In some embodiments, the apparatus 700 may be included in the base stations 302, 402, 502, and 602 of the above embodiments. However, in other embodiments, the apparatus 700 may be included in any base station associated with a wireless communication system. The apparatus 700 may include: one or more processors (e.g., one or more baseband processors, such as in conjunction with Figure 15 and / or Figure 16 One or more baseband processors discussed), including (one or more) processors 710 and associated interfaces (e.g., in conjunction with Figure 16 1506, which may include one or more transmitter circuits (e.g., associated with one or more transmit chains) or receiver circuits (e.g., associated with one or more receive chains), where the transmitter circuits and the receiver circuits may employ common circuit elements, different circuit elements, or a combination thereof); and memory 730 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processor 710 or the transceiver circuits 720).

[0115] Specifically, the term memory is intended to include installation media, such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media, such as hard drives or optical storage devices; registers, or other similar types of memory elements; etc. The memory medium may also include other types of memory or a combination thereof. In various aspects, the apparatus 700 may be included in an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (evolved Node B, eNodeB, or eNB), a next-generation Node B (gNodeB or gNB), or other base station or TRP (transmit / receive point) in a wireless communication network. In some aspects, the processor 710, transceiver circuitry 720, and memory 730 may be included in a single device, while in other aspects, they may be included in different devices, such as part of a distributed architecture. In some embodiments, one or more processors 710, transceiver circuitry 720, and memory circuitry 730 may be implemented as part of a modem system on a single integrated circuit (IC). Alternatively, in other embodiments, one or more of processor 710, transceiver circuitry 720, and memory circuitry 730 may be implemented on different ICs.

[0116] refer to Figure 8 , shows a block diagram of an apparatus 800 that can be employed at a user equipment (UE) or other network device (e.g., an IoT device) in accordance with various aspects described herein. In some embodiments, the apparatus 800 may be included within the UEs 304, 404, 504, and 605 of the above embodiments. However, in other embodiments, the apparatus 800 may be included within any UE associated with a wireless communication system. The apparatus 800 may include one or more processors 810 (e.g., one or more baseband processors, such as a processor in conjunction with a processor 810). Figure 15 and / or Figure 16 One or more baseband processors discussed), including processing circuitry and associated interfaces (e.g., in conjunction with Figure 16810 or one or more of the transceiver circuits 820). The apparatus 800 may further include a processor 810, a processor 820, ...

[0117] In various aspects discussed herein, signals and / or messages may be generated and output for transmission, and / or transmitted messages may be received and processed. Depending on the type of signal or message generated, outputting for transmission (e.g., by processor 810) may include one or more of: generating a set of associated bits indicating the content of the signal or message, encoding (e.g., which may include adding a cyclic redundancy check (CRC) and / or encoding with a turbo code, a low-density parity-check (LDPC) code, a tail-biting convolutional code (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulation (e.g., via one of binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.), and / or resource mapping (e.g., mapping to a scheduled set of resources, mapping to a set of time and frequency resources authorized for uplink transmission, etc.). Depending on the type of signal or message received, processing (e.g., by processor 810) may include one or more of the following operations: identifying physical resources associated with the signal / message, detecting the signal / message, resource element group deinterleaving, demodulation, descrambling, and / or decoding. In some embodiments, one or more processors 810, transceiver circuitry 820, and memory circuitry 830 may be implemented as part of a modem system on a single integrated circuit (IC). Alternatively, in other embodiments, one or more processors 810, transceiver circuitry 820, and memory circuitry 830 may be implemented on different ICs.

[0118] Figure 9A flow chart of a method 900 for updating a time offset of a UE associated with a wireless communication system (eg, a non-terrestrial network (NTN) communication system) according to one embodiment of the present disclosure is shown. Figure 8 In some embodiments, the apparatus 800 may include: Figure 3 Therefore, further reference is made to Figure 3 The method 900 is explained with reference to the wireless communication system 300 in FIG. At 902, a first time offset (e.g., Koffset1) is determined at one or more processors 810. In some embodiments, based on processing a first time offset (e.g., Koffset1) from a base station (e.g., Figure 3 The timing offset indication signal (eg, Figure 3 The first time offset is determined based on a time offset indication signal 306 in the UE. In some embodiments, the first time offset indicates a time delay in a downlink (DL) to uplink (UL) transaction between the UE and the base station. In some embodiments, the first time offset is equal to or greater than twice the propagation delay between the UE and the base station.

[0119] At 904, a second time offset (e.g., Koffset2) is determined using one or more processors 810. In some embodiments, the second time offset is determined based on processing a subsequent timing offset indication signal (e.g., a subsequent timing offset indication signal (e.g., Figure 3 In some embodiments, the subsequent timing offset indication signal may include the following: Figure 3 At 906, the first time offset is updated with the second time offset using one or more processors 810. At 908, a timing offset update notification signal (e.g., a timing offset update notification signal including the second time offset) is optionally sent to the base station using one or more processors 810. Figure 3 The timing offset update notification signal 310 in Figure 3 Explained.

[0120] Figure 10 A flow chart of a method 1000 for updating a time offset of a base station associated with a wireless communication system (eg, a non-terrestrial network (NTN) communication system) according to one embodiment of the present disclosure is shown. Figure 7 In some embodiments, the apparatus 700 may be included in the apparatus 700. Figure 3 BS 302. Therefore, further reference is made to Figure 3The method 1000 is explained with reference to the wireless communication system 300 in FIG. At 1002, one or more processors 710 are used to send a signal to a UE (e.g., Figure 3 UE 304 in the UE 304 sends a timing offset indication signal (eg, Figure 3 The UE may further include a time offset indication signal 306 in the base station to enable the UE to determine a first time offset. In some embodiments, the first time offset indicates a time delay in a downlink (DL) to uplink (UL) transaction between the UE and the base station. In some embodiments, the first time offset is equal to or greater than twice the propagation delay between the UE and the base station.

[0121] At 1004, a second time offset is determined using one or more processors 710. At 1006, at a subsequent time, a subsequent timing offset indication signal (e.g., Figure 3 At 1008, a timing offset update notification signal (e.g., a subsequent timing offset indication signal 308 in the UE) is received from the UE using one or more processors 710, including the second time offset. Figure 3 In some embodiments, the BS does not determine the second time offset at 1004 before sending the subsequent timing offset indication signal at 1006. In such embodiments, the BS is configured to determine the second time offset at 1008 after processing the timing offset update notification signal received from the UE.

[0122] Figure 11 A flow chart of a method 1100 for determining a medium access control (MAC) control element (CE) activation timing based on a time offset by a UE associated with a wireless communication system (e.g., a non-terrestrial network (NTN) communication system) according to one embodiment of the present disclosure is shown. Figure 8 In some embodiments, the apparatus 800 may include: Figure 4a Therefore, further reference is made to Figure 4a The method 1100 is explained with reference to the wireless communication system 400 in FIG. At 1102, one or more processors 810 are used to determine a time offset (e.g., Koffset). In some embodiments, the time offset indicates the time between the UE and the base station (e.g., Figure 4aIn some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. At 1104, a medium access control (MAC) control element (CE) command (e.g., Figure 4a 408 in the MAC CE command). In some embodiments, the MAC CE command may include a DL MAC CE. Alternatively, in other embodiments, the MAC CE command may include a UL MAC CE.

[0123] At 1106, in response to receiving the MAC CE command, one or more processors 810 are employed to send a hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback (e.g., Figure 4a At 1108, one or more processors 810 are used to determine a MAC CE activation time for activating the MAC CE command based on the determined time offset, depending on whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command. In some embodiments, when the MAC CE command includes a DL MAC CE, the DL MAC CE activation time (i.e., the time for receiving the MAC CE command) is Figure 4a The time of the DL transmission 412 in the HARQ-ACK feedback) is determined to correspond to the time (X + time offset) after the HARQ-ACK feedback is sent, where X is a predefined number. Alternatively, in other embodiments, when the MAC CE command includes a UL MAC CE, the UL MAC CE activation time (i.e., the time for sending the UL MAC CE) is determined to correspond to the time (X + time offset) after the HARQ-ACK feedback is sent, where X is a predefined number. Figure 4a The time of the UL transmission 414 in the HARQ-ACK feedback is determined to correspond to a time K milliseconds (ms) after the HARQ-ACK feedback is sent, where K is a predefined number. In some embodiments, K is equal to 3. At 1110, one or more processors 810 are used to activate the MAC CE command at the determined MAC CE activation time.

[0124] Figure 12 A flow chart of a method 1200 for a UE associated with a wireless communication system (eg, a non-terrestrial network (NTN) communication system) that utilizes a time offset in HARQ retransmissions according to one embodiment of the present disclosure is shown. Figure 8 In some embodiments, the apparatus 800 may include: Figure 5 Therefore, further reference is made to Figure 5The method 1200 is explained with reference to the wireless communication system 500 in FIG. At 1202, one or more processors 810 are used to determine a time offset (e.g., Koffset). In some embodiments, the time offset indicates the time between the UE and the base station (e.g., Figure 5 In some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. At 1204, downlink control information (DCI) (e.g., Figure 5 In some implementations, the DCI identifies a hybrid automatic repeat request (HARQ) process number.

[0125] At 1206, based on the determined time offset, one or more processors 810 are used to selectively process subsequent DCI (e.g., Figure 5 For example, when the DCI includes a DL DCI (e.g., Figure 5 508 in the DL DCI), the subsequent DCI includes the subsequent DL DCI (e.g., Figure 5 In such an embodiment, when aggregation / blind retransmission is disabled, when sending HARQ-ACK feedback (e.g., Figure 5When a subsequent DL DCI is received at a time period / time after a time equal to the time offset from the HARQ-ACK feedback 510 in the transmission, the subsequent DL DCI is processed. In addition, when aggregation / blind transmission is disabled and a subsequent DL DCI is received within a time period / time equal to the time offset from the transmission of the HARQ-ACK feedback, the subsequent DL DCI is not processed. When aggregation / blind retransmission is disabled, the DL DCI and the HARQ-ACK feedback comprise a single transmission. In an embodiment in which aggregation / blind transmission is enabled, the DL DCI comprises multiple aggregation / blind retransmissions of the DL DCI, and the HARQ-ACK feedback comprises corresponding multiple HARQ-ACK feedbacks. In such an embodiment, when a subsequent DL DCI is received at a time period / time equal to the time offset from the transmission of the last HARQ-ACK feedback among the multiple HARQ-ACK feedbacks, the subsequent DL DCI is processed. Furthermore, when aggregation / blind transmission is enabled and a subsequent DL DCI is received at a time period / time instant within a time period equal to a time offset from sending the last HARQ-ACK feedback among the multiple HARQ-ACK feedbacks, the subsequent DL DCI is not processed.

[0126] Similarly, when the DCI includes UL DCI (e.g., Figure 5 514 in the UL DCI), the subsequent DCI includes the subsequent UL DCI (e.g., Figure 5 In such an embodiment, when aggregation / blind retransmission is disabled, when sending a UL transmission sent in response to receiving a UL DCI (e.g., Figure 5 When a subsequent UL DCI is received at a time period / time after a time equal to the time offset from the UL transmission 516 in the transmission, the subsequent UL DCI is processed. In addition, when aggregation / blind transmission is disabled and a subsequent UL DCI is received at a time period / time equal to the time offset from the transmission of the UL transmission, the subsequent UL DCI is not processed. When aggregation / blind transmission is disabled, the UL DCI and the UL transmission comprise a single transmission. In an embodiment where aggregation retransmission or blind retransmission is enabled, the UL DCI comprises multiple aggregation / blind retransmissions of the UL DCI, and the UL transmission comprises corresponding multiple UL transmissions, as described above with respect to Figure 5In such an embodiment, when a subsequent UL DCI is received at a time period / time after a time equal to the time offset from the transmission of the last UL transmission among the multiple UL transmissions, the subsequent UL DCI is processed. In addition, when aggregation / blind transmission is enabled and a subsequent UL DCI is received at a time period / time within a time equal to the time offset from the transmission of the last UL transmission among the multiple UL transmissions, the subsequent UL DCI is not processed.

[0127] Figure 13 A flow chart of a method 1300 for a UE associated with a wireless communication system (e.g., a non-terrestrial network (NTN) communication system) utilizing a time offset when determining a time window for receiving a beam failure recovery response (BFRR) according to one embodiment of the present disclosure is shown. Figure 8 In some embodiments, the apparatus 800 may include: Figure 6 Therefore, further reference is made to Figure 6 The method 1300 is explained with reference to the wireless communication system 600 in FIG.

[0128] At 1302, a time offset (e.g., Koffset) is determined using one or more processors 810. In some embodiments, the time offset indicates the time between the UE and the base station (e.g., Figure 6 In some embodiments, the time offset is equal to or greater than twice the propagation delay between the UE and the base station. At 1304, using one or more processors 810, a beam failure recovery request (BFRQ) is sent to the base station (e.g., Figure 6 In some embodiments, the BFRQ indicates a beam failure. At 1306, in response to sending the BFRQ, one or more processors 810 are used to monitor for a beam failure recovery response (BFRR) from the base station (e.g., Figure 6 In some embodiments, the BFRR is monitored within the BFRR time window after the BFRQ is sent. In some embodiments, one or more parameters of the BFRR time window are determined based on the determined time offset, as described above with respect to Figure 6 At 1308, a BFRR is received and processed using one or more processors 810. At 1310, when no BFRR is received within the BFRR time window, a subsequent BFRQ (e.g., Figure 6 612 in the subsequent BFRQ).

[0129] Although method is shown and described as a series of actions or events above, it should be understood that the order of such actions or events shown should not be interpreted as having a limiting meaning. For example, some actions can occur in different orders and / or with other actions or events except those actions or events shown and / or described herein. In addition, all shown actions may not be needed to realize one or more aspects or embodiments disclosed herein. In addition, one or more actions in the action shown herein can be carried out in one or more separate actions and / or stages.

[0130] The embodiments described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 14 The architecture of a system 1400 including a core network (CN) 1420, such as a fifth generation (5G) CN (5GC), according to various embodiments is shown. The system 1400 is shown to include a UE 1401, which can be the same as or similar to one or more other UEs discussed herein; a third generation partnership project (3GPP) radio access network (wireless AN or RAN) or other (e.g., non-3GPP) AN, (R) AN 210, which can include one or more RAN nodes (e.g., evolved Node B (eNB)), next generation Node B (gNB and / or other nodes) or other nodes or access points; and a data network (DN) 203, which can be, for example, operator services, Internet access, or third-party services; and a fifth generation core network (5GC) 1420. 5GC 1420 may include one or more of the following functions and network components: authentication server function (AUSF) 1422; access and mobility management function (AMF) 1421; session management function (SMF) 1424; network exposure function (NEF) 1423; policy control function (PCF) 1426; network repository function (NRF) 1425; unified data management (UDM) 1427; application function (AF) 1428; user plane (UP) function (UPF) 1402; and network slice selection function (NSSF) 1429.

[0131] UPF 1402 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external protocol data unit (PDU) session point interconnected with DN 1403, and a branching point to support multi-homed PDU sessions. UPF 1402 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, perform lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), perform uplink traffic validation (e.g., service data flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1402 may include an uplink classifier to support routing of traffic to the data network. DN 1403 may represent various network operator services, internet access, or third-party services. DN 1403 may include or be similar to an application server. UPF 1402 may interact with SMF 1424 via an N4 reference point between SMF 1424 and UPF 1402.

[0132] The AUSF 1422 may store data used to authenticate the UE 1401 and handle authentication-related functions. The AUSF 1422 may facilitate a common authentication framework for various access types. The AUSF 1422 may communicate with the AMF 1421 via the N12 reference point between the AMF 1421 and the AUSF 1422; and may communicate with the UDM 1427 via the N13 reference point between the UDM 1427 and the AUSF 1422. In addition, the AUSF 1422 may present an interface based on the NAUSF service.

[0133] The AMF 1421 may be responsible for registration management (e.g., responsible for registering the UE 1401, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. The AMF 1421 may be the termination point of the N11 reference point between the AMF 1421 and the SMF 1424. The AMF 1421 may provide transport for SM messages between the UE 1401 and the SMF 1424 and act as a transparent proxy for routing SM messages. The AMF 1421 may also provide a communication channel between the UE 1401 and the Short Message Service (SMS) Function (SMSF) ( Figure 14401). The AMF 1421 may act as a security anchor function (SEAF), which may include interaction with the AUSF 1422 and the UE 1401 and / or receiving intermediate keys established as a result of the UE 1401 authentication process. In the case of using universal subscriber identity module (USIM)-based authentication, the AMF 1421 may retrieve security material from the AUSF 1422. The AMF 1421 may also include a single connection mode (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 1421 may be a termination point for the RAN control plane (CP) interface, which may include or may be an N2 reference point between the (R)AN 1410 and the AMF 1421; and the AMF 1421 may be a termination point for non-access stratum (NAS) (N1) signaling, and perform NAS encryption and integrity protection.

[0134] The AMF 1421 may also support NAS signaling with the UE 1401 over a non-3GPP (N3) interworking function (IWF) interface. The N3 IWF may be used to provide access to untrusted entities. The N3 IWF may be the termination point for the N2 interface between the (R)AN 1410 and the AMF 1421 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 1410 and the UPF 1402 for the user plane. Thus, the AMF 1421 may process N2 signaling for PDU sessions and QoS from the SMF 1424 and the AMF 1421, encapsulate / decapsulate packets for Internet Protocol (IP) Security (IPSec) and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, thereby taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 1401 and the AMF 1421 via the N1 reference point between the UE 1401 and the AMF 1421, and relay uplink and downlink user plane packets between the UE 1401 and the UPF 1402. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 1401. The AMF 1421 may present an interface based on Namf services and may be an N14 reference point between the two AMFs 1421 and an interface between the AMF 1421 and the 5G Equipment Identity Register (5G-EIR) ( Figure 14 The termination point of the N17 reference point between (not shown).

[0135] UE 1401 may register with AMF 1421 to receive network services. Registration Management (RM) is used to register or deregister UE 1401 with the network (e.g., AMF 1421) and establish a UE context in the network (e.g., AMF 1421). UE 1401 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 1401 is not registered with the network, and the UE context in AMF 1421 does not hold valid location or routing information for UE 1401, so UE 1401 is not accessible to AMF 1421. In the RM-REGISTERED state, UE 1401 is registered with the network, and the UE context in AMF 1421 may hold valid location or routing information for UE 1401, so UE 1401 is accessible to AMF 1421. In the RM-registered state, UE 1401 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (for example, to notify the network that UE 1401 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0136] The AMF 1421 may store one or more RM contexts for the UE 1401, where each RM context is associated with a specific access right of the network. The RM context may be a data structure, a database object, etc., which in particular indicates or stores the registration status and periodic update timer for each access type. The AMF 1421 may also store a 5GC Mobility Management (MM) context that is the same as or similar to the (Enhanced Packet System (EPS)) MM ((E)MM) context. In various embodiments, the AMF 1421 may store the Coverage Enhancement (CE) Mode B restriction parameters of the UE 1401 in the associated MM context or RM context. The AMF 1421 may also derive values ​​from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.

[0137] Connection Management (CM) can be used to establish and release a signaling connection between UE 1401 and AMF 1421 over the N1 interface. Signaling connections are used to enable NAS signaling exchanges between UE 1401 and CN 1420, and include both signaling connections between the UE and the AN (e.g., an RRC connection for non-3GPP access or a UE-N3IWF connection) and UE 1401's N2 connection between the AN (e.g., RAN 1410) and AMF 1421. UE 1401 can operate in one of two CM states: CM-Idle mode or CM-Connected mode. When UE 1401 is operating in the CM-Idle state / mode, UE 1401 may not have a NAS signaling connection established with AMF 1421 over the N1 interface, and a (R)AN 1410 signaling connection (e.g., an N2 and / or N3 connection) may exist for UE 1401. When the UE 1401 is operating in the CM-Connected state / mode, the UE 1401 may have a NAS signaling connection established with the AMF 1421 through the N1 interface, and there may be a (R)AN 1410 signaling connection (e.g., N2 and / or N3 connection) for the UE 1401. Establishment of the N2 connection between the (R)AN 1410 and the AMF 1421 may cause the UE 1401 to transition from the CM-Idle mode to the CM-Connected mode, and when the N2 signaling between the (R)AN 1410 and the AMF 1421 is released, the UE 1401 may transition from the CM-Connected mode to the CM-Idle mode.

[0138] The SMF 1424 may be responsible for session management (SM) (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring the UPF's traffic steering to route traffic to the correct destination; terminating the interface towards the policy control function; the control portion of policy enforcement and QoS; lawful interception (for SM events and the interface with the lawful interception (LI) system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the session and service continuity (SSC) mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 1401 and the data network (DN) 1403 identified by the data network name (DNN). A PDU session can be established at the request of UE 1401, modified at the request of UE 1401 and 5GC 1420, and released at the request of UE 1401 and 5GC 1420 using NAS SM signaling exchanged over the N1 reference point between UE 1401 and SMF 1424. Upon request from an application server, 5GC 1420 can trigger a specific application in UE 1401. In response to receiving the trigger message, UE 1401 can deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 1401. The identified applications in UE 1401 can establish a PDU session with a specific DNN. SMF 1424 can check whether the UE 1401 request complies with user subscription information associated with UE 1401. In this regard, SMF 1424 can retrieve and / or request notification of updates regarding SMF 1424-level subscription data from UDM 1427.

[0139] SMF 1424 may include the following roaming functions: handling local execution to apply QoS service level agreements (SLAs) (visited public land mobile network (VPLMN)); charging data collection and billing interfaces (VPLMN); lawful interception (for SM events and interfaces with LI systems, in VPLMN); and support for interaction with external DNs to transport signaling for PDU session authorization / authentication through external DNs. In roaming scenarios, an N16 reference point between two SMFs 1424 may be included in system 1400, which may be located between another SMF 1424 in the visited network and an SMF 1424 in the home network. In addition, SMF 1424 may present an interface based on Nsmf services.

[0140] NEF 1423 can provide components for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 1428), edge computing or fog computing systems, and the like. In such implementations, NEF 1423 can authenticate, authorize, and / or restrict the AF. NEF 1423 can also convert information exchanged with AF 1428 and information exchanged with internal network functions. For example, NEF 1423 can convert between AF service identifiers and internal 5GC information. NEF 1423 can also receive information from other network functions (NFs) based on their exposed capabilities. This information can be stored in NEF 1423 as structured data or in a data storage NF using standardized interfaces. The stored information can then be re-exposed by NEF 1423 to other NFs and AFs and / or used for other purposes such as analysis. In addition, NEF 1423 can present an interface based on NNEF services.

[0141] NRF 1425 can support service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to NF instances. NRF 1425 also maintains information about available NF instances and the services they support. As used herein, the term "instantiation" and the like can refer to the creation of an instance, and "instance" can refer to the specific occurrence of an object, which can occur, for example, during the execution of program code. In addition, NRF 1425 can present an interface based on Nnrf services.

[0142] PCF 1426 can provide control plane functions for enforcing their policy rules and can also support a unified policy framework for managing network behavior. PCF 1426 can also implement FEs to access subscription information related to policy decisions in the UDM 1427's UDR. PCF 1426 can communicate with AMF 1421 via the N15 reference point between PCF 1426 and AMF 1421, which can include the PCF 1426 in the visited network and the AMF 1421 in roaming scenarios. PCF 1426 can communicate with AF 1428 via the N5 reference point between PCF 1426 and AF 1428, and with SMF 1424 via the N7 reference point between PCF 1426 and SMF 1424. System 1400 and / or CN 1420 can also include an N24 reference point between PCF 1426 (in the home network) and PCF 1426 in the visited network. Additionally, PCF 1426 may present an interface based on Npcf services.

[0143] The UDM 1427 may process subscription-related information to support network entities in handling communication sessions and may store subscription data for the UE 1401. For example, subscription data may be transferred between the UDM 1427 and the AMF 1421 via the N8 reference point between the UDM 1427 and the AMF. The UDM 1427 may include two parts: an application function entity (FE) and a unified data repository (UDR). Figure 1 FE and UDR are not shown in the figure). The UDR can store subscription data and policy data of the UDM 1427 and PCF 1426, and / or structured data for exposure and application data of the NEF 1423 (including packet flow descriptions (PFDs) for application detection, application request information of multiple UEs 1401). An interface based on Nudr services can be presented by the UDR 221 to allow the UDM 1427, PCF 1426 and NEF 1423 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of changes to related data in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different FEs may serve the same user. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. The UDR may interact with the SMF 1424 via the N10 reference point between the UDM 1427 and the SMF 1424. The UDM 1427 may also support SMS management, where the SMS-FE implements similar application logic as discussed elsewhere herein. Additionally, the UDM 1427 may present an interface based on Nudm services.

[0144] AF 1428 can provide application influence on traffic routing, provide access to NEF 1423, and interact with the policy framework for policy control. 5GC 1420 and AF 1428 can provide information to each other via NEF 1423, which can be used for edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 1401 access point to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 1402 near the UE 1401 and perform traffic steering from the UPF 1402 to the DN 1403 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1428. In this way, AF 1428 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1428 is considered a trusted entity, the network operator may allow AF 1428 to interact directly with the relevant NF. Additionally, the AF 1428 may present an interface based on Naf services.

[0145] NSSF 1429 may select a set of network slice instances to serve UE 1401. NSSF 1429 may also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI), as appropriate. NSSF 1429 may also determine the set of AMFs to serve UE 1401, or a list of candidate AMFs 1421, based on appropriate configuration and possibly by querying NRF 1425. The selection of a set of network slice instances for UE 1401 may be triggered by AMF 1421, where UE 1401 registers by interacting with NSSF 1429, which may result in a change in AMF 1421. NSSF 1429 may interact with AMF 1421 via the N22 reference point between AMF 1421 and NSSF 1429; and may communicate via the N31 reference point ( Figure 14 (not shown) and communicate with another NSSF 1429 in the visited network. In addition, the NSSF 1429 may present an interface based on the Nnssf service.

[0146] As previously discussed, CN 1420 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from UE 1401 to / from other entities, such as an SMS-Gateway Mobile Services Switching Center (GMSC) / Interworking MSC (IWMSC) / SMS-Router. The SMSF may also interact with AMF 1421 and UDM 1427 for notification procedures, making UE 1401 available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 1427 when UE 1401 is available for SMS).

[0147] CN 1420 may also include Figure 14 Other elements not shown in the figure, such as data storage system / architecture, 5G-EIR, security edge protection agent (SEPP), etc. The data storage system may include structured data storage function (SDSF), unstructured data storage function (UDSF), etc. Any NF can communicate with any NF and UDSF ( Figure 1 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data into or from the UDSF (e.g., UE context). Each NF may share a UDSF for storing its respective unstructured data, or each NF may have its own UDSF located at or near each NF. In addition, the UDSF may present an interface based on the Nudsf service ( Figure 1 ). The 5G-EIR may be a NF that checks the status of the Permanent Equipment Identifier (PEI) to determine whether to blacklist a specific equipment / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0148] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 14 These interfaces and reference points are omitted. In one example, the CN 1420 may include an Nx interface, which is an inter-CN interface between an MME (e.g., a non-5G MME) and an AMF 1421, to enable interworking between the CN 1420 and a non-5G CN. Other exemplary interfaces / reference points may include an interface based on N5g-EIR services presented by the 5G-EIR, an N27 reference point between a network repository function (NRF) in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0149] Figure 15Exemplary components of a device 1500 according to some embodiments are shown. In some embodiments, the device 1500 may include application circuitry 1502, baseband circuitry 1504, radio frequency (RF) circuitry 1506, front-end module (FEM) circuitry 1508, one or more antennas 1510, and power management circuitry (PMC) 1512 (at least coupled together as shown). The components of the illustrated device 1500 may be included in a UE or a RAN node. In some embodiments, the device 1500 may include fewer elements (e.g., a RAN node may not utilize application circuitry 1502, but instead include a processor / controller to process IP data received from a CN such as a 5GC 1420 or an evolved packet core (EPC)). In some embodiments, the device 1500 may include additional elements such as memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, the following components may be included in more than one device (e.g., the circuitry may be separately included in more than one device for a cloud-RAN (C-RAN) implementation).

[0150] Application circuitry 1502 may include one or more application processors. For example, application circuitry 1502 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on device 1500. In some embodiments, the processors of application circuitry 1502 may process IP data packets received from the EPC.

[0151] The baseband circuitry 1504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1504 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuitry 1506 and generate baseband signals for the transmit signal path of the RF circuitry 1506. The baseband processing circuitry 1504 may interact with the application circuitry 1502 to generate and process baseband signals and control the operation of the RF circuitry 1506. For example, in some embodiments, the baseband circuitry 1504 may include a third generation (3G) baseband processor 1504A, a fourth generation (4G) baseband processor 1504B, a fifth generation (5G) baseband processor 1504C, or other baseband processors 1504D of other current generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). Baseband circuitry 1504 (e.g., one or more baseband processors 1504A-D) can handle various radio control functions, which can communicate with one or more radio networks via RF circuitry 1506. In other embodiments, some or all of the functions of baseband processors 1504A-D may be included in modules stored in memory 1504G and executed via central processing unit (CPU) 1504E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 1504 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 1504 may include convolution, tail-biting, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other embodiments.

[0152] In some embodiments, baseband circuitry 1504 may include one or more audio digital signal processors (DSPs) 1504F. Audio DSPs 1504F may include components for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of baseband circuitry 1504 and application circuitry 1502 may be implemented together, such as, for example, on a system on a chip (SOC).

[0153] In some embodiments, the baseband circuitry 1504 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1504 can support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN), or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN), etc. Embodiments in which the baseband circuitry 1504 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0154] RF circuitry 1506 can communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 1506 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 1506 can include a receive signal path, which can include circuitry for down-converting RF signals received from FEM circuitry 1508 and providing a baseband signal to baseband circuitry 1504. RF circuitry 1506 can also include a transmit signal path, which can include circuitry for up-converting baseband signals provided by baseband circuitry 1504 and providing an RF output signal to FEM circuitry 1508 for transmission.

[0155] In some embodiments, the receive signal path of RF circuitry 1506 may include mixer circuitry 1506a, amplifier circuitry 1506b, and filter circuitry 1506c. In some embodiments, the transmit signal path of RF circuitry 1506 may include filter circuitry 1506c and mixer circuitry 1506a. RF circuitry 1506 may also include synthesizer circuitry 1506d for synthesizing frequencies used by mixer circuitry 1506a in the receive and transmit signal paths. In some embodiments, mixer circuitry 1506a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 1508 based on the synthesized frequency provided by synthesizer circuitry 1506d. Amplifier circuitry 1506b may be configured to amplify the downconverted signal, and filter circuitry 1506c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1504 for further processing. In some embodiments, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 1506a of the receive signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0156] In some embodiments, mixer circuit 1506a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1506d to generate an RF output signal for FEM circuit 1508. The baseband signal can be provided by baseband circuit 1504 and can be filtered by filter circuit 1506c.

[0157] In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1506a of the receive signal path and the mixer circuit 1506a of the transmit signal path may be configured for superheterodyne operation.

[0158] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 1506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 1504 may include a digital baseband interface to communicate with RF circuitry 1506.

[0159] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0160] In some embodiments, synthesizer circuit 1506d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 1506d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0161] Synthesizer circuit 1506d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 1506a of RF circuit 1506. In some embodiments, synthesizer circuit 1506d may be a fractional-N / N+1 synthesizer.

[0162] In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input can be provided by baseband circuitry 1504 or application processor 1502 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by application processor 1502.

[0163] The synthesizer circuit 1506d of the RF circuit 1506 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-modulus frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable set of delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0164] In some embodiments, the synthesizer circuit 1506d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 1506 can include an IQ / polarity converter.

[0165] The FEM circuitry 1508 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 1510, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 1506 for further processing. The FEM circuitry 1508 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 1506 for transmission via one or more of the one or more antennas 1510. In various embodiments, amplification by either the transmit or receive signal path may be performed only in the RF circuitry 1506, only in the FEM 1508, or in both the RF circuitry 1506 and the FEM 1508.

[0166] In some embodiments, the FEM circuitry 1508 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 1506). The transmit signal path of the FEM circuitry 1508 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 1506), and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 1510).

[0167] In some embodiments, PMC 1512 can manage the power provided to baseband circuitry 1504. Specifically, PMC 1512 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. PMC 1512 is typically included when device 1500 is capable of being powered by a battery, such as when the device is included in a UE. PMC 1512 can improve power conversion efficiency while providing desired implementation size and heat dissipation characteristics.

[0168] Although Figure 15 PMC 1512 is shown coupled only to baseband circuitry 1504. However, in other embodiments, PMC 1512 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 1502, RF circuitry 1506, or FEM 1508) and perform similar power management operations.

[0169] In some embodiments, the PMC 1512 can control or otherwise be part of various power saving mechanisms of the device 1500. For example, if the device 1500 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device can enter a state known as discontinuous reception mode (DRX). During this state, the device 1500 can be powered down for short intervals, thereby saving power.

[0170] If there is no data traffic activity for an extended period of time, the device 1500 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The device 1500 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 1500 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state.

[0171] An additional power saving mode can disable the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0172] The processor of the application circuitry 1502 and the processor of the baseband circuitry 1504 can be used to execute elements of one or more instances of a protocol stack. For example, the processor of the baseband circuitry 1504 can be used alone or in combination to perform Layer 3, Layer 2, or Layer 1 functions, while the processor of the application circuitry 1504 can utilize data received from these layers (e.g., packet data) and further perform Layer 4 functions (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include a Radio Resource Control (RRC) layer, which is described in further detail below. As mentioned herein, Layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in further detail below. As mentioned herein, Layer 1 may include a Physical (PHY) layer of a UE / RAN node, which is described in further detail below.

[0173] Figure 16 1 shows an exemplary interface of a baseband circuit according to some embodiments. As discussed above, Figure 15 The baseband circuit 1504 may include processors 1504A-1504E and a memory 1504G utilized by the processors. Each of the processors 1504A-1504E may include a memory interface 1604A-1604E, respectively, for sending / receiving data to / from the memory 1504G.

[0174] The baseband circuit 1504 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1612 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1504); an application circuit interface 1614 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 1504); Figure 15 RF circuit interface 1616 (for example, for sending / receiving data to / from the application circuit 1502); Figure 15 an interface for sending / receiving data to / from a RF circuit 1506); a wireless hardware connection interface 1618 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 1620 (eg, an interface for sending / receiving power or control signals to / from the PMC 1512).

[0175] In various aspects, the embodiments discussed herein may facilitate inter-cell BM (beam management) techniques via L1 (Layer 1) through one or more variations of the first and / or second set of techniques. The first set of techniques discussed herein may facilitate L1 inter-cell BM via SSB (synchronization signal blocks). The second set of techniques discussed herein may facilitate L1 inter-cell BM via synchronization CSI (channel state information)-RS (reference signal).

[0176] Embodiments may include subject matter such as a method, an apparatus for performing the actions or blocks of the method, and at least one machine-readable medium comprising instructions that, when executed by a machine, cause the machine to perform the actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the embodiments and examples described herein.

[0177] Embodiment 1 is a baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite serving as a base station or serving as a relay to a base station, the BB processor being configured to perform operations including determining a first time offset based on processing a timing offset indication signal including a first time offset or an associated parameter received from the base station, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station; wherein the first time offset is equal to or greater than two times a propagation delay between the UE and the base station; determining a second time offset based on processing a subsequent timing offset indication signal including a second time offset or an associated parameter received from the base station at a subsequent time, wherein the second time offset indicates a time delay in a DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than two times the propagation delay between the UE and the base station; and updating the first time offset with the second time offset.

[0178] Embodiment 2 is a BB processor including the subject matter of embodiment 1, wherein the first time offset comprises an initial time offset to be used by the UE during an initial access procedure or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0179] Embodiment 3 is a BB processor including the subject matter described in embodiments 1 to 2, including or omitting elements, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0180] Embodiment 4 is a BB processor including the subject matter of embodiments 1 to 3, including or omitting elements, wherein the second time offset is utilized by the UE after the initial access procedure.

[0181] Embodiment 5 is a BB processor including the subject matter of embodiments 1 to 4, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and the RAR message includes the second time offset.

[0182] Embodiment 6 is a BB processor including the subject matter of embodiments 1 to 5, including or omitting elements, wherein the subsequent timing offset indication signal includes a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0183] Embodiment 7 is a BB processor including the subject matter described in embodiments 1 to 6, including or omitting elements, wherein when the common RRC message or the dedicated RRC message is received from the base station, determining the second time offset to update the first time offset is triggered.

[0184] Embodiment 8 is a BB processor including the subject matter described in embodiments 1 to 7, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI) including the second time offset; or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0185] Embodiment 9 is a BB processor including the subject matter of embodiments 1 to 8, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, the time offset field includes the second time offset or the parameter indicating the second time offset.

[0186] Embodiment 10 is a BB processor including the subject matter of embodiments 1 to 9, including or omitting elements, wherein upon receiving the group common DCI message or the dedicated DCI message, determining the second time offset to update the first time offset is triggered.

[0187] Embodiment 11 is a BB processor including the subject matter described in embodiments 1 to 10, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0188] Embodiment 12 is a BB processor including the subject matter described in embodiments 1 to 11, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered when the dedicated time offset MAC CE or the TA command MAC CE or the timing drift rate MAC CE is received from the base station.

[0189] Embodiment 13 is a BB processor including the subject matter described in embodiments 1 to 12, including or omitting elements, wherein the subsequent timing offset indication signal includes a TA command medium access control (MAC) control element (CE), and wherein the second time offset is determined based on a timing advance (TA) value included in the TA command MAC CE.

[0190] Embodiment 14 is a BB processor including the subject matter of embodiments 1 to 13, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered upon receiving the TA MAC CE from the base station.

[0191] Embodiment 15 is a BB processor including the subject matter described in embodiments 1 to 14, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and wherein the second time offset is determined based on a timing advance (TA) command included in the RAR message.

[0192] Embodiment 16 is a BB processor including the subject matter of embodiments 1 to 15, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing drift rate indication signal, and wherein the second time offset is determined based on a timing drift rate included in the timing drift rate indication signal.

[0193] Embodiment 17 is a BB processor including the subject matter described in embodiments 1 to 16, including or omitting elements, wherein when the autonomously maintained timing advance (TA) of the UE that varies as a function of the timing drift rate exceeds a predefined TA threshold, determining the second time offset to update the first time offset is triggered.

[0194] Embodiment 18 is a BB processor including the subject matter of embodiments 1 to 17, including or omitting elements, wherein the operation further includes: after determining the second time offset, sending a timing offset update notification signal including the second time offset to the base station.

[0195] Embodiment 19 is a baseband (BB) processor for a base station (BS) operating in a non-terrestrial network (NTN), wherein the base station includes a satellite or a satellite having a relay to a user equipment (UE), the BB processor being configured to perform operations including sending a timing offset indication signal including a first time offset or an associated parameter to a user equipment (UE) so as to enable the UE to determine the first time offset, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than twice the propagation delay between the UE and the base station; and sending a subsequent timing offset indication signal including a second time offset or an associated parameter to the UE at a subsequent time so as to enable the UE to update the first time offset with the second time offset, wherein the second time offset indicates the time delay in the DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station.

[0196] Embodiment 20 is a BB processor including the subject matter of embodiment 19, wherein the operations further comprise determining the second time offset before sending the subsequent timing offset indication signal to the UE.

[0197] Embodiment 21 is a BB processor including the subject matter described in embodiments 19 to 20, including or omitting elements, wherein the operation further includes: in response to sending the subsequent timing offset indication signal to the UE, determining the second time offset based on processing the timing offset update notification signal received from the UE.

[0198] Embodiment 22 is a BB processor including the subject matter described in embodiments 19 to 21, including or omitting elements, wherein the first time offset includes an initial time offset to be used by the UE during an initial access process or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0199] Embodiment 23 is a BB processor including the subject matter of embodiments 19 to 22, including or omitting elements, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0200] Embodiment 24 is a BB processor including the subject matter of embodiments 19 to 23, including or omitting elements, wherein the second time offset is to be utilized by the UE after the initial access procedure.

[0201] Embodiment 25 is a BB processor including the subject matter of embodiments 19 to 24, including or omitting elements, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, the RAR message including the second time offset.

[0202] Embodiment 26 is a BB processor including the subject matter of embodiments 19 to 25, including or omitting elements, wherein the subsequent timing offset indication signal includes a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0203] Embodiment 27 is a BB processor including the subject matter described in embodiments 19 to 26, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI); or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0204] Embodiment 28 is a BB processor including the subject matter of embodiments 19 to 27, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, the time offset field includes the second time offset or the parameter indicating the second time offset.

[0205] Embodiment 29 is a BB processor including the subject matter described in embodiments 19 to 28, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset received from the base station; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0206] Embodiment 30 is a BB processor including the subject matter of embodiments 19 to 29, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing advance (TA) command medium access control (MAC) control element (CE), and the TA command MAC CE includes a TA value.

[0207] Embodiment 31 is a BB processor including the subject matter of embodiments 19 to 30, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message including a timing advance (TA) command.

[0208] Embodiment 32 is a BB processor including the subject matter of embodiments 19 to 31, including or omitting elements, wherein the subsequent timing offset indication signal comprises a timing drift rate indication signal, the timing drift rate indication signal comprising a timing drift rate.

[0209] Embodiment 33 is a BB processor including the subject matter of embodiments 19 to 32, including or omitting elements, and determining the second time offset when beam switching between satellites.

[0210] Embodiment 34 is a baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the BB processor being configured to perform operations including determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than twice a propagation delay between the UE and the base station; receiving a medium access control (MAC) control element (CE) from the base station; sending a hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback to the base station in response to receiving the MAC CE command; and determining a MAC CE activation time for activating the MAC CE command based on the determined time offset according to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command.

[0211] Embodiment 35 is a BB processor including the subject matter described in embodiment 34, wherein, when the MAC CE command includes the DL MAC CE command, the MAC CE activation time of the DL MAC CE command constituting the DL MAC CE activation time is determined to correspond to a moment (X+time offset) after sending the HARQ-ACK feedback, where X is a predefined number.

[0212] Embodiment 36 is a BB processor comprising the subject matter of embodiments 34-35, including or omitting elements, wherein X and the time offset are measured in milliseconds (ms).

[0213] Embodiment 37 is a BB processor comprising the subject matter of embodiments 34 to 36, including or omitting elements, wherein X is less than or equal to 3 ms.

[0214] Embodiment 38 is a BB processor including the subject matter of embodiments 34 to 37, including or omitting elements, wherein the operations further comprise activating the DL MAC CE command at the determined DL MAC CE activation time.

[0215] Embodiment 39 is a BB processor including the subject matter described in embodiments 34 to 38, including or omitting elements, wherein, when the MAC CE command includes the UL MAC CE command, the MAC CE activation time of the UL MAC CE command constituting the UL MAC CE activation time is determined to correspond to a moment K milliseconds (ms) after sending the HARQ-ACK feedback, where K is a predefined number.

[0216] Embodiment 40 is a BB processor comprising the subject matter of embodiments 34 to 39, including or omitting elements, wherein K is equal to 3 milliseconds (ms).

[0217] Embodiment 41 is a BB processor including the subject matter of embodiments 34 to 40, including or omitting elements, wherein the operations further comprise activating the UL MAC CE command at the determined UL MAC CE activation time.

[0218] Embodiment 42 is a BB processor including the subject matter of embodiments 34 to 41, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station including the time offset or an associated parameter.

[0219] Embodiment 43 is a baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the BB processor being configured to perform operations comprising determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; receiving downlink control information (DCI) from the base station scheduling a DL transmission to the UE or a UL transmission from the UE, wherein the DCI identifies a hybrid self- The method comprises: receiving a HARQ process number of the DCI, wherein the DCI comprises a single transmission of the DCI when aggregation / blind retransmission is disabled, and the DCI comprises multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled; and selectively processing subsequent DCI with the same HARQ process number received from the base station based on the determined time offset, wherein the subsequent DCI comprises DCI received from the base station after receiving the single transmission of the DCI when aggregation / blind retransmission is disabled, or DCI received from the base station after receiving the multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled.

[0220] Embodiment 44 is a BB processor including the subject matter of embodiment 43, wherein the DCI comprises a DL DCI scheduling the DL transmission to the UE, and the subsequent DCI comprises a subsequent DL DCI scheduling a retransmission of the DL transmission.

[0221] Embodiment 45 is a BB processor including the subject matter described in embodiments 43 to 44, including or omitting elements, wherein the operation further includes: before receiving the subsequent DL DCI, in response to receiving the DL DCI or the associated DL transmission, sending a hybrid automatic repeat request (HARQ) confirmation (ACK) feedback to the base station.

[0222] Embodiment 46 is a BB processor including the subject matter of embodiments 43 to 45, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the DL DCI and the HARQ-ACK feedback comprise a single transmission.

[0223] Embodiment 47 is a BB processor including the subject matter described in embodiments 43 to 46, including or omitting elements, wherein the subsequent DL DCI is processed when the subsequent DL DCI is received at a time period / time equal to the time offset from the single transmission of the HARQ-ACK feedback.

[0224] Embodiment 48 is a BB processor including the subject matter described in embodiments 43 to 47, including or omitting elements, wherein the operation further includes: when the subsequent DL DCI is received within the time equal to the time offset from the single transmission of sending the HARQ-ACK feedback, ignoring the processing of the subsequent DL DCI.

[0225] Embodiment 49 is a BB processor including the subject matter described in embodiments 43 to 48, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the DL DCI includes multiple aggregate / blind retransmissions of the DL DCI, and the HARQ-ACK feedback includes corresponding multiple HARQ-ACK feedback.

[0226] Embodiment 50 is a BB processor including the subject matter described in embodiments 43 to 49, including or omitting elements, wherein when a subsequent DL DCI is received at a time period / time after a time equal to the time offset from sending the last HARQ-ACK feedback in the multiple HARQ-ACK feedbacks, the subsequent DL DCI is processed.

[0227] Embodiment 51 is a BB processor including the subject matter described in embodiments 43 to 50, including or omitting elements, wherein the operation further includes: when the subsequent DL DCI is received within the time equal to the time offset from sending the last HARQ-ACK feedback in the multiple HARQ-ACK feedbacks, ignoring the processing of the subsequent DL DCI.

[0228] Embodiment 52 is a BB processor including the subject matter of embodiments 43 to 51, including or omitting elements, wherein the DCI comprises a UL DCI scheduling the UL transmission to the UE, and the subsequent DCI comprises a subsequent UL DCI scheduling a retransmission of the UL transmission.

[0229] Embodiment 53 is a BB processor including the subject matter of embodiments 43 to 52, including or omitting elements, the operation further comprising: before receiving the subsequent UL DCI, in response to receiving the UL DCI, sending a UL transmission to the base station.

[0230] Embodiment 54 is a BB processor including the subject matter of embodiments 43 to 53, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the UL DCI and the UL transmission comprise a single transmission.

[0231] Embodiment 55 is a BB processor including the subject matter of embodiments 43 to 54, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time after a time equal to the time offset from sending the single UL transmission.

[0232] Embodiment 56 is a BB processor including the subject matter described in embodiments 43 to 55, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the single UL transmission, ignoring the processing of the subsequent UL DCI.

[0233] Embodiment 57 is a BB processor including the subject matter described in embodiments 43 to 56, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the UL DCI includes multiple aggregate / blind retransmissions of the UL DCI, and the UL transmission includes corresponding multiple UL transmissions / retransmissions.

[0234] Embodiment 58 is a BB processor including the subject matter described in embodiments 43 to 57, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time equal to the time offset from sending the last UL transmission of the multiple UL transmissions.

[0235] Embodiment 59 is a BB processor including the subject matter described in embodiments 43 to 58, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the last UL transmission of the multiple UL transmissions, ignoring the processing of the subsequent UL DCI.

[0236] Embodiment 60 is a BB processor including the subject matter of embodiments 43 to 59, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station including the time offset or an associated parameter.

[0237] Embodiment 61 is a baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the BB processor being configured to perform operations including determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; sending a beam failure recovery request (BFRQ) to the base station, wherein the BFRQ indicates a beam failure; and in response to sending the BFRQ, monitoring for receipt of a beam failure recovery response (BFRR) from the base station, wherein the BFRR is monitored within a BFRR time window after sending the BFRQ, and wherein one or more parameters of the BFRR time window are determined based on the determined time offset.

[0238] Embodiment 62 is a BB processor including the subject matter of embodiment 61, wherein the operations further comprise sending a subsequent BFRQ to the base station when the BFRR is not received within the BFRR time window.

[0239] Embodiment 63 is a BB processor including the subject matter of embodiments 61 to 62, including or omitting elements, wherein the BFRR time window includes a time period corresponding to (N+time offset) time slots from sending the BFRQ, where N is a predefined number.

[0240] Embodiment 64 is a BB processor comprising the subject matter of embodiments 61 to 63, including or omitting elements, wherein N is equal to 4.

[0241] Embodiment 65 is a BB processor including the subject matter of embodiments 61 to 64, including or omitting elements, wherein the BFRR time window start time is offset by at least a time corresponding to the time offset from sending the BFRQ.

[0242] Embodiment 66 is a BB processor including the subject matter described in embodiments 61 to 65, including or omitting elements, wherein for primary cell (Pcell) beam failure recovery, the BFRR time window starts after a time corresponding to (Y+time offset) time slots after sending a contention-free physical random access channel (PRACH) including the BFRQ, where Y is a predefined number.

[0243] Embodiment 67 is a BB processor comprising the subject matter of embodiments 61 to 66, including or omitting elements, wherein Y is equal to 4 time slots.

[0244] Embodiment 68 is a BB processor including the subject matter described in embodiments 61 to 67, including or omitting elements, wherein for secondary cell (Scell) beam failure recovery, the BFRR time window starts after a time corresponding to a time offset of time slots after sending a scheduling request (SR) / medium access control (MAC) control element (CE) including the BFRQ.

[0245] Embodiment 69 is a BB processor including the subject matter described in embodiments 61 to 68, including or omitting elements, wherein when aggregate retransmission or blind retransmission of the BFRQ is supported, the BFRQ includes multiple transmissions of the BFRQ, and wherein the BFRR is monitored within the BFRR time window after the first or last retransmission of the multiple retransmissions of the BFRQ.

[0246] Embodiment 70 is a BB processor including the subject matter of embodiments 61 to 69, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station including the time offset or an associated parameter.

[0247] Embodiment 71 is a user equipment (UE), which includes a processor configured to perform operations including determining the first time offset based on processing a timing offset indication signal including a first time offset or associated parameter received from a base station, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, and wherein the first time offset is equal to or greater than twice the propagation delay between the UE and the base station; determining the second time offset based on processing a subsequent timing offset indication signal including a second time offset or associated parameter received from the base station at a subsequent moment, wherein the second time offset indicates a time delay in a DL to uplink UL interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station; and updating the first time offset with the second time offset.

[0248] Embodiment 72 is a UE including the subject matter of embodiment 71, wherein the first time offset comprises an initial time offset to be used by the UE during an initial access procedure or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0249] Embodiment 73 is a UE including the subject matter described in embodiments 71 to 72, including or omitting elements, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0250] Embodiment 74 is a UE comprising the subject matter described in embodiments 71 to 73, including or omitting elements, wherein the second time offset is utilized by the UE after the initial access procedure.

[0251] Embodiment 75 is a UE including the subject matter described in embodiments 71 to 74, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and the RAR message includes the second time offset.

[0252] Embodiment 76 is a UE comprising the subject matter described in embodiments 71 to 75, including or omitting elements, wherein the subsequent timing offset indication signal comprises a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0253] Embodiment 77 is a UE including the subject matter described in embodiments 71 to 76, including or omitting elements, wherein when the common RRC message or the dedicated RRC message is received from the base station, determining the second time offset to update the first time offset is triggered.

[0254] Embodiment 78 is a UE including the subject matter described in embodiments 71 to 77, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI) including the second time offset; or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0255] Embodiment 79 is a UE including the subject matter described in embodiments 71 to 78, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, and the time offset field includes the second time offset or the parameter indicating the second time offset.

[0256] Embodiment 80 is a UE including the subject matter described in embodiments 71 to 79, including or omitting elements, wherein upon receiving the group common DCI message or the dedicated DCI message, determining the second time offset to update the first time offset is triggered.

[0257] Embodiment 81 is a UE including the subject matter described in embodiments 71 to 80, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0258] Embodiment 82 is a UE including the subject matter described in Embodiments 71 to 81, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered when the dedicated time offset MAC CE or the TA command MAC CE or the timing drift rate MAC CE is received from the base station.

[0259] Embodiment 83 is a UE including the subject matter described in embodiments 71 to 82, including or omitting elements, wherein the subsequent timing offset indication signal includes a TA command medium access control (MAC) control element (CE), and wherein the second time offset is determined based on a timing advance (TA) value included in the TA command MAC CE.

[0260] Embodiment 84 is a UE including the subject matter of embodiments 71 to 83, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered upon receiving the TA MAC CE from the base station.

[0261] Embodiment 85 is a UE including the subject matter described in embodiments 71 to 84, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and wherein the second time offset is determined based on a timing advance (TA) command included in the RAR message.

[0262] Embodiment 86 is a UE including the subject matter described in embodiments 71 to 85, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing drift rate indication signal, and wherein the second time offset is determined based on the timing drift rate included in the timing drift rate indication signal.

[0263] Embodiment 87 is a UE comprising the subject matter described in embodiments 71 to 86, including or omitting elements, wherein when the autonomously maintained timing advance (TA) of the UE, which varies as a function of the timing drift rate, exceeds a predefined TA threshold, determining the second time offset to update the first time offset is triggered.

[0264] Embodiment 88 is a UE including the subject matter described in Embodiments 71 to 87, including or omitting elements, wherein the operation further includes: after determining the second time offset, sending a timing offset update notification signal including the second time offset to the base station.

[0265] Embodiment 89 is a base station (BS) operating in a non-terrestrial network (NTN), wherein the base station includes a satellite or a satellite having a relay to a user equipment, the base station including a processor configured to perform operations including sending a timing offset indication signal including a first time offset or an associated parameter to a user equipment (UE) so as to enable the UE to determine the first time offset, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than two times the propagation delay between the UE and the base station; and sending a subsequent timing offset indication signal including a second time offset or an associated parameter to the UE at a subsequent time so as to enable the UE to update the first time offset with the second time offset, wherein the second time offset indicates the time delay in the DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than two times the propagation delay between the UE and the base station.

[0266] Embodiment 90 is a BS including the subject matter of embodiment 89, wherein the operations further comprise determining the second time offset before sending the subsequent timing offset indication signal to the UE.

[0267] Embodiment 91 is a BS including the subject matter described in embodiments 89 to 90, including or omitting elements, wherein the operation further includes: in response to sending the subsequent timing offset indication signal to the UE, determining the second time offset based on processing the timing offset update notification signal received from the UE.

[0268] Embodiment 92 is a BS including the subject matter described in embodiments 89 to 91, including or omitting elements, wherein the first time offset includes an initial time offset to be used by the UE during the initial access process or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0269] Embodiment 93 is a BS including the subject matter described in embodiments 89 to 92, including or omitting elements, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0270] Embodiment 94 is a BS comprising the subject matter of embodiments 89 to 93, including or omitting elements, wherein the second time offset is to be utilized by the UE after the initial access procedure.

[0271] Embodiment 95 is a BS including the subject matter of embodiments 89 to 94, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and the RAR message includes the second time offset.

[0272] Embodiment 96 is a BS including the subject matter described in embodiments 89 to 95, including or omitting elements, wherein the subsequent timing offset indication signal includes a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0273] Embodiment 97 is a BS including the subject matter described in embodiments 89 to 96, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI); or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0274] Embodiment 98 is a BS including the subject matter described in embodiments 89 to 97, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, and the time offset field includes the second time offset or the parameter indicating the second time offset.

[0275] Embodiment 99 is a BS including the subject matter described in embodiments 89 to 98, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset received from the base station; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0276] Embodiment 100 is a BS including the subject matter of embodiments 89 to 99, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing advance (TA) command medium access control (MAC) control element (CE), and the TA command MAC CE includes a TA value.

[0277] Embodiment 101 is a BS including the subject matter of embodiments 89 to 100, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and the RAR message includes a timing advance (TA) command.

[0278] Embodiment 102 is a BS including the subject matter of embodiments 89 to 101, including or omitting elements, wherein the subsequent timing offset indication signal comprises a timing drift rate indication signal, the timing drift rate indication signal comprising a timing drift rate.

[0279] Embodiment 103 is a BS including the subject matter described in embodiments 89 to 102, including or omitting elements, and determining the second time offset when switching beams between satellites.

[0280] Embodiment 104 is a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite serving as a base station or serving as a relay to a base station, the UE being configured to include a processor configured to perform operations including determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; receiving a medium access control (MAC) control element (CE) from the base station; sending a hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback to the base station in response to receiving the MAC CE command; and determining a MAC CE activation time for activating the MAC CE command based on the determined time offset according to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command.

[0281] Embodiment 105 is a UE including the subject matter described in embodiment 104, wherein, when the MAC CE command includes the DL MAC CE command, the MAC CE activation time of the DL MAC CE command constituting the DL MAC CE activation time is determined to correspond to a moment (X+time offset) after sending the HARQ-ACK feedback, where X is a predefined number.

[0282] Embodiment 106 is a UE comprising the subject matter of embodiments 104 to 105, including or omitting elements, wherein X and the time offset are measured in milliseconds (ms).

[0283] Embodiment 107 is a UE comprising the subject matter of embodiments 104 to 106, including or omitting elements, wherein X is less than or equal to 3 ms.

[0284] Embodiment 108 is a UE including the subject matter of embodiments 104 to 107, including or omitting elements, wherein the operations further include activating the DL MAC CE command at the determined DL MAC CE activation time.

[0285] Embodiment 109 is a UE including the subject matter described in embodiments 104 to 108, including or omitting elements, wherein, when the MAC CE command includes the UL MAC CE command, the MAC CE activation time of the UL MAC CE command constituting the UL MAC CE activation time is determined to correspond to a moment K milliseconds (ms) after sending the HARQ-ACK feedback, where K is a predefined number.

[0286] Embodiment 110 is a UE including the subject matter of embodiments 104 to 109, including or omitting elements, wherein K is equal to 3 milliseconds (ms).

[0287] Embodiment 111 is a UE including the subject matter of embodiments 104 to 110, including or omitting elements, wherein the operation further includes activating the UL MAC CE command at the determined UL MAC CE activation time.

[0288] Embodiment 112 is a UE including the subject matter of embodiments 104 to 111, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal including the time offset or associated parameters received from the base station.

[0289] Embodiment 113 is a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the UE comprising a processor configured to perform operations including determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station; receiving downlink control information (DCI) from the base station scheduling a DL transmission to the UE or a UL transmission from the UE, wherein the DCI identifies a hybrid automatic repeat request (HARQ) process number, and wherein wherein, when aggregation / blind retransmission is disabled, the DCI includes a single transmission of the DCI, and when aggregation / blind retransmission is enabled, the DCI includes multiple aggregation / blind retransmissions of the DCI; and based on the determined time offset, selectively processing subsequent DCI with the same HARQ process number received from the base station, wherein the subsequent DCI includes DCI received from the base station after receiving the single transmission of the DCI when aggregation / blind retransmission is disabled, or DCI received from the base station after receiving the multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled.

[0290] Embodiment 114 is a UE including the subject matter of embodiment 113, wherein the DCI comprises a DL DCI scheduling the DL transmission to the UE, and the subsequent DCI comprises a subsequent DL DCI scheduling a retransmission of the DL transmission.

[0291] Embodiment 115 is a UE including the subject matter described in embodiments 113 to 114, including or omitting elements, wherein the operation further includes: before receiving the subsequent DL DCI, in response to receiving the DL DCI or the associated DL transmission, sending a hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback to the base station.

[0292] Embodiment 116 is a UE comprising the subject matter of embodiments 113 to 115, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the DL DCI and the HARQ-ACK feedback comprise a single transmission.

[0293] Embodiment 117 is a UE including the subject matter described in embodiments 113 to 116, including or omitting elements, wherein the subsequent DL DCI is processed when the subsequent DL DCI is received in a time period / time equal to the time offset from the single transmission of the HARQ-ACK feedback.

[0294] Embodiment 118 is a UE including the subject matter described in embodiments 113 to 117, including or omitting elements, wherein the operation further includes: ignoring the processing of the subsequent DL DCI when the subsequent DL DCI is received within the time equal to the time offset from the single transmission of the HARQ-ACK feedback.

[0295] Embodiment 119 is a UE including the subject matter described in embodiments 113 to 118, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the DL DCI includes multiple aggregate / blind retransmissions of the DL DCI, and the HARQ-ACK feedback includes corresponding multiple HARQ-ACK feedback.

[0296] Embodiment 120 is a UE including the subject matter described in embodiments 113 to 119, including or omitting elements, wherein when a subsequent DL DCI is received at a time period / time after a time equal to the time offset from sending the last HARQ-ACK feedback among the multiple HARQ-ACK feedbacks, the subsequent DL DCI is processed.

[0297] Embodiment 121 is a UE including the subject matter described in embodiments 113 to 120, including or omitting elements, wherein the operation further includes: when the subsequent DL DCI is received within the time equal to the time offset from sending the last HARQ-ACK feedback among the multiple HARQ-ACK feedbacks, ignoring the processing of the subsequent DL DCI.

[0298] Embodiment 122 is a UE including the subject matter described in embodiments 113 to 121, including or omitting elements, wherein the DCI includes a UL DCI that schedules the UL transmission to the UE, and the subsequent DCI includes a subsequent UL DCI that schedules a retransmission of the UL transmission.

[0299] Embodiment 123 is a UE including the subject matter described in embodiments 113 to 122, including or omitting elements, and the operation further includes: before receiving the subsequent UL DCI, in response to receiving the UL DCI, sending a UL transmission to the base station.

[0300] Embodiment 124 is a UE comprising the subject matter of embodiments 113 to 123, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the UL DCI and the UL transmission comprise a single transmission.

[0301] Embodiment 125 is a UE including the subject matter described in embodiments 113 to 124, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time after a time equal to the time offset from sending the single UL transmission.

[0302] Embodiment 126 is a UE including the subject matter described in embodiments 113 to 125, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the single UL transmission, ignoring the processing of the subsequent UL DCI.

[0303] Embodiment 127 is a UE including the subject matter described in embodiments 113 to 126, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the UL DCI includes multiple aggregates / blind retransmissions of the UL DCI, and the UL transmission includes corresponding multiple UL transmissions / retransmissions.

[0304] Embodiment 128 is a UE including the subject matter described in embodiments 113 to 127, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time equal to the time offset from sending the last UL transmission of the multiple UL transmissions.

[0305] Embodiment 129 is a UE including the subject matter described in embodiments 113 to 128, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the last UL transmission of the multiple UL transmissions, ignoring the processing of the subsequent UL DCI.

[0306] Embodiment 130 is a UE comprising the subject matter of embodiments 113 to 129, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

[0307] Embodiment 131 is a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the UE comprising a processor configured to perform operations including determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; sending a beam failure recovery request (BFRQ) to the base station, wherein the BFRQ indicates a beam failure; and in response to sending the BFRQ, monitoring for receipt of a beam failure recovery response (BFRR) from the base station, wherein the BFRR is monitored within a BFRR time window after sending the BFRQ, and wherein one or more parameters of the BFRR time window are determined based on the determined time offset.

[0308] Embodiment 132 is a UE including the subject matter of embodiment 131, wherein the operations further comprise sending a subsequent BFRQ to the base station when the BFRR is not received within the BFRR time window.

[0309] Embodiment 133 is a UE comprising the subject matter described in embodiments 131 to 132, including or omitting elements, wherein the BFRR time window includes a time period corresponding to (N+time offset) time slots from sending the BFRQ, where N is a predefined number.

[0310] Embodiment 134 is a UE including the subject matter described in embodiments 131 to 133, including or omitting elements, wherein N is equal to 4.

[0311] Embodiment 135 is a UE including the subject matter of embodiments 131 to 134, including or omitting elements, wherein the BFRR time window start time is offset by at least a time corresponding to the time offset from sending the BFRQ.

[0312] Embodiment 136 is a UE comprising the subject matter described in embodiments 131 to 135, including or omitting elements, wherein for primary cell (Pcell) beam failure recovery, the BFRR time window starts after a time corresponding to (Y+time offset) time slots after sending a contention-free physical random access channel (PRACH) including the BFRQ, where Y is a predefined number.

[0313] Embodiment 137 is a UE comprising the subject matter described in embodiments 131 to 136, including or omitting elements, wherein Y is equal to 4 time slots.

[0314] Embodiment 138 is a UE including the subject matter described in embodiments 131 to 137, including or omitting elements, wherein for secondary cell (Scell) beam failure recovery, the BFRR time window starts after a time corresponding to a time offset of time slots after sending a scheduling request (SR) / medium access control (MAC) control element (CE) including the BFRQ.

[0315] Embodiment 139 is a UE including the subject matter described in embodiments 131 to 138, including or omitting elements, wherein when aggregate retransmission or blind retransmission of the BFRQ is supported, the BFRQ includes multiple transmissions of the BFRQ, and wherein BFRR is monitored within the BFRR time window after the first or last retransmission of the multiple retransmissions of the BFRQ.

[0316] Embodiment 140 is a UE comprising the subject matter of embodiments 131 to 139, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

[0317] Embodiment 141 is a method for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite serving as a base station or serving as a relay to a base station, the method comprising: determining a first time offset based on processing a timing offset indication signal including a first time offset or associated parameter received from the base station, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than two times a propagation delay between the UE and the base station; determining a second time offset based on processing a subsequent timing offset indication signal including a second time offset or associated parameter received from the base station at a subsequent time, wherein the second time offset indicates a time delay in a DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than two times the propagation delay between the UE and the base station; and updating the first time offset with the second time offset.

[0318] Embodiment 142 is a method including the subject matter of embodiment 141, wherein the first time offset comprises an initial time offset to be used by the UE during an initial access procedure or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0319] Embodiment 143 is a method including the subject matter described in embodiments 141 to 142, including or omitting elements, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0320] Embodiment 144 is a method comprising the subject matter of embodiments 141 to 143, including or omitting elements, wherein the second time offset is utilized by the UE after the initial access procedure.

[0321] Embodiment 145 is a method including the subject matter of embodiments 141 to 144, including or omitting elements, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and the RAR message includes the second time offset.

[0322] Embodiment 146 is a method including the subject matter described in embodiments 141 to 145, including or omitting elements, wherein the subsequent timing offset indication signal includes a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0323] Embodiment 147 is a method including the subject matter described in embodiments 141 to 146, including or omitting elements, wherein when the common RRC message or the dedicated RRC message is received from the base station, determining the second time offset to update the first time offset is triggered.

[0324] Embodiment 148 is a method including the subject matter described in embodiments 141 to 147, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI) including the second time offset; or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0325] Embodiment 149 is a method including the subject matter described in embodiments 141 to 148, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, and the time offset field includes the second time offset or the parameter indicating the second time offset.

[0326] Embodiment 150 is a method including the subject matter of embodiments 141 to 149, including or omitting elements, wherein upon receipt of the group common DCI message or the dedicated DCI message, determining the second time offset to update the first time offset is triggered.

[0327] Embodiment 151 is a method including the subject matter described in embodiments 141 to 150, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0328] Embodiment 152 is a method including the subject matter described in embodiments 141 to 151, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered when the dedicated time offset MAC CE or the TA command MAC CE or the timing drift rate MAC CE is received from the base station.

[0329] Embodiment 153 is a method including the subject matter of embodiments 141 to 152, including or omitting elements, wherein the subsequent timing offset indication signal includes a TA command medium access control (MAC) control element (CE), and wherein the second time offset is determined based on a timing advance (TA) value included in the TA command MAC CE.

[0330] Embodiment 154 is a method including the subject matter of embodiments 141 to 153, including or omitting elements, wherein determining the second time offset to update the first time offset is triggered upon receiving the TA MAC CE from the base station.

[0331] Embodiment 155 is a method including the subject matter described in embodiments 141 to 154, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and wherein the second time offset is determined based on a timing advance (TA) command included in the RAR message.

[0332] Embodiment 156 is a method including the subject matter described in embodiments 141 to 155, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing drift rate indication signal, and wherein the second time offset is determined based on the timing drift rate included in the timing drift rate indication signal.

[0333] Embodiment 157 is a method including the subject matter described in embodiments 141 to 156, including or omitting elements, wherein when the autonomously maintained timing advance (TA) of the UE, which varies as a function of the timing drift rate, exceeds a predefined TA threshold, determining the second time offset to update the first time offset is triggered.

[0334] Embodiment 158 ​​is a method including the subject matter described in embodiments 141 to 157, including or omitting elements, wherein the operation further includes: after determining the second time offset, sending a timing offset update notification signal including the second time offset to the base station.

[0335] Embodiment 159 is a method for a base station (BS) operating in a non-terrestrial network (NTN), wherein the base station includes a satellite or a satellite having a relay to a user equipment, the method including sending a timing offset indication signal including a first time offset or an associated parameter to a user equipment (UE) so as to enable the UE to determine the first time offset, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than two times the propagation delay between the UE and the base station; and sending a subsequent timing offset indication signal including a second time offset or an associated parameter to the UE at a subsequent time so as to enable the UE to update the first time offset with the second time offset, wherein the second time offset indicates the time delay in the DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than two times the propagation delay between the UE and the base station.

[0336] Embodiment 160 is a method including the subject matter of embodiment 159, wherein the operations further comprise determining the second time offset before sending the subsequent timing offset indication signal to the UE.

[0337] Embodiment 161 is a method including the subject matter described in embodiments 159 to 160, including or omitting elements, wherein the operation further includes: in response to sending the subsequent timing offset indication signal to the UE, determining the second time offset based on processing the timing offset update notification signal received from the UE.

[0338] Embodiment 162 is a method including the subject matter described in embodiments 159 to 161, including or omitting elements, wherein the first time offset includes an initial time offset to be used by the UE during an initial access process or an updated time offset that updates the initial time offset in one or more subsequent iterations.

[0339] Embodiment 163 includes the subject matter of embodiments 159 to 162, including or omitting elements of the method, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal, and the system information signal includes the initial time offset.

[0340] Embodiment 164 is a method including the subject matter of embodiments 159 to 163, including or omitting elements, wherein the second time offset is to be utilized by the UE after the initial access procedure.

[0341] Embodiment 165 is a method including the subject matter of embodiments 159 to 162, including or omitting elements, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and the RAR message includes the second time offset.

[0342] Embodiment 166 is a method including the subject matter described in embodiments 159 to 165, including or omitting elements, wherein the subsequent timing offset indication signal includes a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

[0343] Embodiment 167 is a method including the subject matter described in embodiments 159 to 166, including or omitting elements, wherein the subsequent timing offset indication signal includes: group common downlink control information (DCI); or a dedicated DCI including the second time offset or a parameter indicating the second time offset.

[0344] Embodiment 168 is a method including the subject matter described in embodiments 159 to 167, including or omitting elements, wherein the group common DCI and / or the dedicated DCI includes a time offset field, and the time offset field includes the second time offset or the parameter indicating the second time offset.

[0345] Embodiment 169 is a method including the subject matter described in embodiments 159 to 168, including or omitting elements, wherein the subsequent timing offset indication signal includes: a dedicated time offset medium access control (MAC) control element (CE) including the second time offset received from the base station; or a timing advance (TA) command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

[0346] Embodiment 170 is a method including the subject matter of embodiments 159 to 169, including or omitting elements, wherein the subsequent timing offset indication signal includes a timing advance (TA) command medium access control (MAC) control element (CE), and the TA command MAC CE includes a TA value.

[0347] Embodiment 171 is a method including the subject matter of embodiments 159 to 170, including or omitting elements, wherein the subsequent timing offset indication signal includes a random access response (RAR) message, and the RAR message includes a timing advance (TA) command.

[0348] Embodiment 172 is a method including the subject matter of embodiments 159 to 171, including or omitting elements, wherein the subsequent timing offset indication signal comprises a timing drift rate indication signal, and the timing drift rate indication signal comprises a timing drift rate.

[0349] Embodiment 173 is a method including the subject matter of embodiments 159 to 172, including or omitting elements, and determining the second time offset when beam switching between satellites.

[0350] Embodiment 174 is a method for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the method comprising determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; receiving a medium access control (MAC) control element (CE) from the base station; sending a hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback to the base station in response to receiving the MAC CE command; and determining a MAC CE activation time for activating the MAC CE command based on the determined time offset according to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command.

[0351] Embodiment 175 is a method including the subject matter of embodiment 104, wherein, when the MAC CE command includes the DL MAC CE command, the MAC CE activation time of the DL MAC CE command constituting the DL MAC CE activation time is determined to correspond to a moment (X+time offset) after sending the HARQ-ACK feedback, where X is a predefined number.

[0352] Embodiment 176 is a method comprising the subject matter of embodiments 104 to 175, including or omitting elements, wherein X and the time offset are measured in milliseconds (ms).

[0353] Embodiment 177 is a method comprising the subject matter of embodiments 174 to 176, including or omitting elements, wherein X is less than or equal to 3 ms.

[0354] Embodiment 178 is a method including the subject matter of embodiments 174 to 177, including or omitting elements, wherein the operations further include activating the DL MAC CE command at the determined DL MAC CE activation time.

[0355] Embodiment 179 is a UE including the subject matter described in embodiments 174 to 178, including or omitting elements, wherein, when the MAC CE command includes the UL MAC CE command, the MAC CE activation time of the UL MAC CE command constituting the UL MAC CE activation time is determined to correspond to a moment K milliseconds (ms) after sending the HARQ-ACK feedback, where K is a predefined number.

[0356] Embodiment 180 is a method comprising the subject matter of embodiments 174 to 179, including or omitting elements, wherein K is equal to 3 milliseconds (ms).

[0357] Embodiment 181 is a method including the subject matter of embodiments 174 to 180, including or omitting elements, wherein the operation further comprises activating the UL MAC CE command at the determined UL MAC CE activation time.

[0358] Embodiment 182 is a method including the subject matter of embodiments 174 to 181, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or associated parameters.

[0359] Embodiment 183 is a method for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the method comprising determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station; receiving downlink control information (DCI) from the base station scheduling a DL transmission to the UE or an UL transmission from the UE, wherein the DCI identifies a hybrid automatic repeat request (HARQ) process number, and wherein, when aggregation / When aggregation / blind retransmission is disabled, the DCI includes a single transmission of the DCI, and when aggregation / blind retransmission is enabled, the DCI includes multiple aggregation / blind retransmissions of the DCI; and based on the determined time offset, selectively processing subsequent DCI with the same HARQ process number received from the base station, wherein the subsequent DCI includes DCI received from the base station after receiving the single transmission of the DCI when aggregation / blind retransmission is disabled, or DCI received from the base station after receiving the multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled.

[0360] Embodiment 184 is a method including the subject matter of embodiment 183, wherein the DCI comprises a DL DCI scheduling the DL transmission to the UE, and the subsequent DCI comprises a subsequent DL DCI scheduling a retransmission of the DL transmission.

[0361] Embodiment 185 is a method including the subject matter described in embodiments 183 to 184, including or omitting elements, wherein the operation further includes: before receiving the subsequent DL DCI, in response to receiving the DL DCI or the associated DL transmission, sending a hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback to the base station.

[0362] Embodiment 186 is a method including the subject matter of embodiments 183 to 185, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the DL DCI and the HARQ-ACK feedback comprise a single transmission.

[0363] Embodiment 187 is a method including the subject matter described in embodiments 183 to 186, including or omitting elements, wherein the subsequent DL DCI is processed when the subsequent DL DCI is received at a time period / time equal to the time offset from the single transmission of the HARQ-ACK feedback.

[0364] Embodiment 188 is a method including the subject matter described in embodiments 183 to 187, including or omitting elements, wherein the operation further includes: ignoring the processing of the subsequent DL DCI when the subsequent DL DCI is received within the time equal to the time offset from the single transmission of the HARQ-ACK feedback.

[0365] Embodiment 189 is a method including the subject matter described in embodiment 188, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the DL DCI includes multiple aggregate / blind retransmissions of the DL DCI, and the HARQ-ACK feedback includes corresponding multiple HARQ-ACK feedback.

[0366] Embodiment 190 is a method including the subject matter described in embodiments 183 to 189, including or omitting elements, wherein when a subsequent DL DCI is received at a time period / time after a time equal to the time offset from sending the last HARQ-ACK feedback in the multiple HARQ-ACK feedbacks, the subsequent DL DCI is processed.

[0367] Embodiment 191 is a method including the subject matter described in embodiments 183 to 190, including or omitting elements, wherein the operation further includes: when the subsequent DL DCI is received within the time equal to the time offset from sending the last HARQ-ACK feedback in the multiple HARQ-ACK feedbacks, ignoring the processing of the subsequent DL DCI.

[0368] Embodiment 192 is a method including the subject matter described in embodiments 183 to 191, including or omitting elements, wherein the DCI includes a UL DCI that schedules the UL transmission to the UE, and the subsequent DCI includes a subsequent UL DCI that schedules a retransmission of the UL transmission.

[0369] Embodiment 193 is a method including the subject matter of embodiments 183 to 192, including or omitting elements, the operation further comprising: before receiving the subsequent UL DCI, in response to receiving the UL DCI, sending a UL transmission to the base station.

[0370] Embodiment 194 is a method including the subject matter of embodiments 183 to 193, including or omitting elements, wherein aggregate retransmission or blind retransmission is disabled, and wherein the UL DCI and the UL transmission comprise a single transmission.

[0371] Embodiment 195 is a method including the subject matter of embodiments 183 to 194, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time equal to the time offset from sending the single UL transmission.

[0372] Embodiment 196 is a method including the subject matter described in embodiments 183 to 195, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the single UL transmission, ignoring the processing of the subsequent UL DCI.

[0373] Embodiment 197 is a method including the subject matter described in embodiments 183 to 196, including or omitting elements, wherein aggregate retransmission or blind retransmission is enabled, and wherein the UL DCI includes multiple aggregates / blind retransmissions of the UL DCI, and the UL transmission includes corresponding multiple UL transmissions / retransmissions.

[0374] Embodiment 198 is a method including the subject matter described in embodiments 183 to 197, including or omitting elements, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time equal to the time offset from sending the last UL transmission of the multiple UL transmissions.

[0375] Embodiment 199 is a method including the subject matter described in embodiments 183 to 198, including or omitting elements, and the operation further includes: when the subsequent UL DCI is received within the time equal to the time offset from sending the last UL transmission of the multiple UL transmissions, ignoring the processing of the subsequent UL DCI.

[0376] Embodiment 200 is a method including the subject matter of embodiments 183 to 199, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

[0377] Embodiment 201 is a method for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite acting as a base station or as a relay to a base station, the method comprising determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times the propagation delay between the UE and the base station, wherein the time offset is equal to or greater than two times the propagation delay between the UE and the base station; sending a beam failure recovery request (BFRQ) to the base station, wherein the BFRQ indicates a beam failure; and in response to sending the BFRQ, monitoring for receipt of a beam failure recovery response (BFRR) from the base station, wherein the BFRR is monitored within a BFRR time window after sending the BFRQ, and wherein one or more parameters of the BFRR time window are determined based on the determined time offset.

[0378] Embodiment 202 is a UE including the subject matter of embodiment 201, wherein the operations further include: sending a subsequent BFRQ to the base station when the BFRR is not received within the BFRR time window.

[0379] Embodiment 203 is a UE comprising the subject matter of embodiments 201 to 202, including or omitting elements, wherein the BFRR time window comprises a time period corresponding to (N+time offset) time slots from sending the BFRQ, where N is a predefined number.

[0380] Embodiment 204 is a UE including the subject matter described in embodiments 201 to 203, including or omitting elements, wherein N is equal to 4.

[0381] Embodiment 205 is a UE including the subject matter of embodiments 201 to 204, including or omitting elements, wherein the BFRR time window start time is offset by at least a time corresponding to the time offset from sending the BFRQ.

[0382] Embodiment 206 is a UE including the subject matter described in embodiments 201 to 205, including or omitting elements, wherein for primary cell (Pcell) beam failure recovery, the BFRR time window starts after a time corresponding to (Y+time offset) time slots after sending a contention-free physical random access channel (PRACH) including the BFRQ, where Y is a predefined number.

[0383] Embodiment 207 is a UE comprising the subject matter described in embodiments 201 to 206, including or omitting elements, wherein Y is equal to 4 time slots.

[0384] Embodiment 208 is a UE including the subject matter described in embodiments 201 to 207, including or omitting elements, wherein for secondary cell (Scell) beam failure recovery, the BFRR time window starts after a time corresponding to a time offset of time slots after sending a scheduling request (SR) / medium access control (MAC) control element (CE) including the BFRQ.

[0385] Embodiment 209 is a UE including the subject matter described in embodiments 201 to 208, including or omitting elements, wherein when aggregate retransmission or blind retransmission of the BFRQ is supported, the BFRQ includes multiple transmissions of the BFRQ, and wherein BFRR is monitored within the BFRR time window after the first or last retransmission of the multiple retransmissions of the BFRQ.

[0386] Embodiment 210 is a UE comprising the subject matter of embodiments 201 to 209, including or omitting elements, wherein the time offset is determined based on processing a timing offset indication signal received from the base station including the time offset or associated parameters.

[0387] While the invention has been shown and described with respect to one or more specific embodiments, changes and / or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In particular, with respect to the various functions performed by the aforementioned components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise indicated, terms used to describe such components (including references to "means") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the function in the exemplary implementations of the invention illustrated herein.

[0388] The above description of the exemplary embodiments of the disclosed subject matter, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. Although specific embodiments and examples are described herein for illustrative purposes, various modifications are contemplated within the scope of such embodiments and examples, as those skilled in the relevant art will recognize.

Claims

1. A baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite as a base station or as a relay to a base station, the BB processor being configured to perform operations comprising: determining the first time offset based on processing a timing offset indication signal received from the base station and including a first time offset or an associated parameter, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than two times a propagation delay between the UE and the base station; determining the second time offset based on processing a subsequent timing offset indication signal received from the base station at a subsequent time instant and including a second time offset or an associated parameter, wherein the second time offset indicates a time delay in a DL-to-UL interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station; as well as The first time offset is updated with the second time offset.

2. The BB processor of claim 1, wherein the first time offset comprises an initial time offset to be used by the UE during an initial access procedure or an updated time offset that updates the initial time offset in one or more subsequent iterations. 3 . The BB processor according to claim 2 , wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal including the initial time offset. 4 . The BB processor of claim 2 , wherein the second time offset is utilized by the UE after the initial access procedure. 5 . The BB processor according to claim 1 , wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and the RAR message comprises the second time offset. 6 . The BB processor of claim 1 , wherein the subsequent timing offset indication signal comprises a common radio resource control (RRC) message or a dedicated RRC message including the second time offset. 7 . The BB processor according to claim 6 , wherein determining the second time offset to update the first time offset is triggered when the common RRC message or the dedicated RRC message is received from the base station.

8. The BB processor of claim 1 , wherein the subsequent timing offset indication signal comprises: Group common downlink control information DCI including the second time offset; or dedicated DCI including the second time offset or a parameter indicating the second time offset. 9 . The BB processor according to claim 8 , wherein the group common DCI and / or the dedicated DCI comprises a time offset field, the time offset field comprising the second time offset or the parameter indicating the second time offset. 10 . The BB processor according to claim 8 , wherein determining the second time offset to update the first time offset is triggered upon reception of the group common DCI or the dedicated DCI.

11. The BB processor of claim 1 , wherein the subsequent timing offset indication signal comprises: A dedicated time offset medium access control MAC control element CE including the second time offset; or a timing advance TA command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

12. The BB processor according to claim 11, wherein determining the second time offset to update the first time offset is triggered upon receiving the dedicated time offset MAC CE, the TA command MAC CE, or the timing drift rate MAC CE from the base station.

13. The BB processor of claim 1, wherein the subsequent timing offset indication signal comprises a TA command medium access control (MAC) control element (CE), and wherein the second time offset is determined based on a timing advance (TA) value included in the TA command MAC CE. 14 . The BB processor according to claim 13 , wherein determining the second time offset to update the first time offset is triggered when the TA command MAC CE is received from the base station.

15. The BB processor of claim 1, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and wherein the second time offset is determined based on a timing advance (TA) command included in the RAR message.

16. The BB processor of claim 1, wherein the subsequent timing offset indication signal comprises a timing drift rate indication signal, and wherein the second time offset is determined based on a timing drift rate included in the timing drift rate indication signal.

17. The BB processor of claim 16, wherein determining the second time offset to update the first time offset is triggered when the autonomously maintained timing advance (TA) of the UE that varies as a function of the timing drift rate exceeds a predefined TA threshold.

18. The BB processor of claim 1 , wherein the operations further comprise: After determining the second time offset, a timing offset update notification signal including the second time offset is sent to the base station.

19. A baseband (BB) processor for a base station (BS) operating in a non-terrestrial network (NTN), wherein the base station comprises a satellite or has a satellite acting as a relay to user equipment, the BB processor being configured to perform operations comprising: sending a timing offset indication signal comprising a first time offset or an associated parameter to a user equipment (UE) to enable the UE to determine the first time offset, wherein the first time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the first time offset is equal to or greater than two times a propagation delay between the UE and the base station; and Sending a subsequent timing offset indication signal including a second time offset or an associated parameter to the UE at a subsequent time, so as to enable the UE to update the first time offset with the second time offset, wherein the second time offset indicates the time delay in the DL to uplink (UL) interaction between the UE and the base station, and wherein the second time offset is equal to or greater than twice the propagation delay between the UE and the base station.

20. The BB processor of claim 19, wherein the operations further comprise: Before sending the subsequent timing offset indication signal to the UE, the second time offset is determined.

21. The BB processor of claim 19, wherein the operations further comprise: In response to sending the subsequent timing offset indication signal to the UE, the second time offset is determined based on processing a timing offset update notification signal received from the UE.

22. The BB processor of claim 19, wherein the first time offset comprises an initial time offset to be used by the UE during an initial access procedure or an updated time offset that updates the initial time offset in one or more subsequent iterations.

23. The BB processor of claim 22, wherein when the first time offset includes the initial time offset, the timing offset indication signal includes a system information signal including the initial time offset.

24. The BB processor of claim 19, wherein the second time offset is to be utilized by the UE after the initial access procedure.

25. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and the RAR message comprises the second time offset.

26. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises a common radio resource control (RRC) message or a dedicated RRC message including the second time offset.

27. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises: Group common downlink control information DCI including the second time offset or a parameter indicating the second time offset; or dedicated DCI including the second time offset or a parameter indicating the second time offset.

28. The BB processor according to claim 27, wherein the group common DCI and / or the dedicated DCI comprises a time offset field, the time offset field comprising the second time offset or the parameter indicating the second time offset.

29. The BB processor of claim 19, wherein the subsequent timing offset indication signal received from the base station comprises: a dedicated time offset medium access control MAC control element CE including the second time offset; or a timing advance TA command MAC CE including the second time offset; or a timing drift rate MAC CE including the second time offset.

30. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises a Timing Advance (TA) Command Medium Access Control (MAC) Control Element (CE), the TA Command MAC CE comprising a TA value.

31. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises a random access response (RAR) message, and the RAR message comprises a timing advance (TA) command.

32. The BB processor of claim 19, wherein the subsequent timing offset indication signal comprises a timing drift rate indication signal, the timing drift rate indication signal comprising a timing drift rate.

33. The BB processor of claim 19, wherein the second time offset is determined when beam switching is performed between satellites.

34. A baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite as a base station or as a relay to a base station, the BB processor being configured to perform operations comprising: determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; receiving a medium access control MAC control element CE from the base station; In response to receiving the MAC CE command, sending a hybrid automatic repeat request HARQ acknowledgment ACK feedback to the base station; as well as According to whether the MAC CE command includes a DL MAC CE command or a UL MAC CE command, a MAC CE activation time for activating the MAC CE command is determined based on the determined time offset.

35. The BB processor according to claim 34, wherein: When the MAC CE command includes the DL MAC CE command, the MAC CE activation time of the DL MAC CE command constituting a DL MAC CE activation time is determined to correspond to a time of X+time offset after sending the HARQ-ACK feedback, where X is a predefined number.

36. The BB processor of claim 35, wherein X and the time offset are measured in milliseconds (ms).

37. The BB processor of claim 35, wherein X is less than or equal to 3 ms.

38. The BB processor of claim 34, wherein the operations further comprise activating the DL MAC CE command at the determined DL MAC CE activation time.

39. The BB processor according to claim 34, wherein: When the MAC CE command includes the UL MAC CE command, the MAC CE activation time of the UL MAC CE command constituting the UL MAC CE activation time is determined to correspond to a time K milliseconds ms after sending the HARQ-ACK feedback, where K is a predefined number.

40. The BB processor of claim 39, wherein K is equal to 3 milliseconds (ms).

41. The BB processor of claim 39, wherein the operations further comprise activating the UL MAC CE command at the determined UL MAC CE activation time.

42. The BB processor of claim 34, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

43. A baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite as a base station or as a relay to a base station, the BB processor being configured to perform operations comprising: determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; receiving downlink control information (DCI) from the base station for scheduling DL transmission to the UE or UL transmission from the UE, wherein the DCI identifies a hybrid automatic repeat request (HARQ) process number, and wherein, When aggregation / blind retransmission is disabled, the DCI includes a single transmission of the DCI, and when aggregation / blind retransmission is enabled, the DCI includes multiple aggregation / blind retransmissions of the DCI; as well as Based on the determined time offset, selectively process subsequent DCI received from the base station with the same HARQ process number, wherein the subsequent DCI includes DCI received from the base station after receiving the single transmission of the DCI when aggregation / blind retransmission is disabled, or DCI received from the base station after receiving the multiple aggregation / blind retransmissions of the DCI when aggregation / blind retransmission is enabled.

44. The BB processor of claim 43, wherein the DCI comprises a DL DCI scheduling the DL transmission to the UE, and the subsequent DCI comprises a subsequent DL DCI scheduling a retransmission of the DL transmission.

45. The BB processor of claim 44, wherein the operations further comprise: Before receiving the subsequent DL DCI, a hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback is sent to the base station in response to receiving the DL DCI or the associated DL transmission.

46. ​​The BB processor of claim 45, wherein aggregate retransmission or blind retransmission is disabled, and wherein the DLDCI and the HARQ-ACK feedback comprise a single transmission.

47. The BB processor of claim 46, wherein the subsequent DL DCI is processed when the subsequent DL DCI is received at a time period / time instant after a time equal to the time offset from sending the single transmission of the HARQ-ACK feedback.

48. The BB processor of claim 47, wherein the operations further comprise: When the subsequent DL DCI is received within the time equal to the time offset from sending the single transmission of the HARQ-ACK feedback, the processing of the subsequent DL DCI is omitted.

49. The BB processor of claim 45, wherein aggregate retransmission or blind retransmission is enabled, and wherein the DL DCI comprises multiple aggregate / blind retransmissions of the DL DCI, and the HARQ-ACK feedback comprises corresponding multiple HARQ-ACK feedbacks.

50. The BB processor of claim 49, wherein the subsequent DL DCI is processed when the subsequent DL DCI is received at a time period / time after a time equal to the time offset from sending a last HARQ-ACK feedback among the plurality of HARQ-ACK feedbacks.

51. The BB processor of claim 50, wherein the operations further comprise: When the subsequent DL DCI is received within the time equal to the time offset from sending a last HARQ-ACK feedback among the multiple HARQ-ACK feedbacks, omitting the processing of the subsequent DL DCI.

52. The BB processor of claim 43, wherein the DCI comprises a UL DCI scheduling the UL transmission to the UE, and the subsequent DCI comprises a subsequent UL DCI scheduling a retransmission of the UL transmission.

53. The BB processor of claim 52, said operations further comprising: Prior to receiving the subsequent UL DCI, sending a UL transmission to the base station in response to receiving the UL DCI.

54. The BB processor of claim 53, wherein aggregate retransmission or blind retransmission is disabled, and wherein the UL DCI and the UL transmission comprise a single transmission.

55. The BB processor of claim 54, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time after a time equal to the time offset from sending the single UL transmission.

56. The BB processor of claim 55, said operations further comprising: When the subsequent UL DCI is received within the time equal to the time offset from sending the single UL transmission, the processing of the subsequent UL DCI is omitted.

57. The BB processor of claim 53, wherein aggregate retransmission or blind retransmission is enabled, and wherein the UL DCI comprises a plurality of aggregated / blind retransmissions of the UL DCI, and the UL transmission comprises a corresponding plurality of UL transmissions / retransmissions.

58. The BB processor of claim 57, wherein the subsequent UL DCI is processed when the subsequent UL DCI is received at a time period / time after a time equal to the time offset from sending a last UL transmission of the plurality of UL transmissions.

59. The BB processor of claim 58, said operations further comprising: When the subsequent UL DCI is received within the time equal to the time offset from sending a last UL transmission of the plurality of UL transmissions, the processing of the subsequent UL DCI is omitted.

60. The BB processor of claim 43, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

61. A baseband (BB) processor for a user equipment (UE) operating in a non-terrestrial network (NTN) having a satellite as a base station or as a relay to a base station, the BB processor being configured to perform operations comprising: determining a time offset, wherein the time offset indicates a time delay in a downlink (DL) to uplink (UL) interaction between the UE and the base station, wherein the time offset is equal to or greater than two times a propagation delay between the UE and the base station; sending a beam failure recovery request (BFRQ) to the base station, where the BFRQ indicates a beam failure; as well as In response to sending the BFRQ, monitoring for receipt of a beam failure recovery response (BFRR) from the base station, wherein the BFRR is monitored within a BFRR time window after sending the BFRQ, and wherein one or more parameters of the BFRR time window are determined based on the determined time offset.

62. The BB processor of claim 61 , wherein the operations further comprise: When the BFRR is not received within the BFRR time window, a subsequent BFRQ is sent to the base station.

63. The BB processor of claim 61, wherein the BFRR time window comprises a time period corresponding to N + time offset time slots from sending the BFRQ, where N is a predefined number.

64. The BB processor of claim 63, wherein N is equal to 4.

65. The BB processor of claim 61, wherein the BFRR time window start time is offset by at least a time corresponding to the time offset from sending the BFRQ.

66. The BB processor according to claim 65, wherein for primary cell (Pcell) beam failure recovery, the BFRR time window starts after a time corresponding to Y+time offset time slots after sending a contention-free physical random access channel (PRACH) including the BFRQ, where Y is a predefined number.

67. The BB processor of claim 66, wherein Y is equal to 4 time slots.

68. The BB processor according to claim 65, wherein for secondary cell (Scell) beam failure recovery, the BFRR time window starts after a time corresponding to a time offset of time slots after a scheduling request SR / medium access control MAC control element CE including the BFRQ is sent.

69. The BB processor of claim 61 , wherein when aggregate retransmission or blind retransmission of the BFRQ is supported, the BFRQ comprises multiple transmissions of the BFRQ, and wherein BFRR is monitored within the BFRR time window after a first or last retransmission of the multiple retransmissions of the BFRQ.

70. The BB processor of claim 61, wherein the time offset is determined based on processing a timing offset indication signal received from the base station that includes the time offset or an associated parameter.

Images