Non-terrestrial user equipment measurements
Multiple SMTC configurations with different offsets and measurement gaps address the challenge of timing differences in NTN systems, enabling accurate UE measurements in NG and 6G networks.
Patent Information
- Application Number
- JP2023578887
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-21
- Filing Date
- 2022-10-21
- Publication Date
- 2024-11-06
AI Technical Summary
The increasing complexity of NG and 6G wireless networks, particularly in NTN systems, poses challenges due to the large timing differences between serving and neighboring cells caused by high relative motion, leading to inaccurate UE measurements.
Implementing multiple SMTC configurations with different offsets and measurement gaps to accommodate timing differences, allowing UEs to measure neighboring cells without disrupting service from the serving cell.
Enhances accurate UE measurements by ensuring that reference signals from neighboring cells can be measured within configured windows, addressing the issue of large propagation delays in NTN systems.
Smart Images

Figure 2024540791000001_ABST
Abstract
Description
[Technical field]
[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 270,420, filed October 21, 2021, which is incorporated by reference in its entirety herein.
[0002] Embodiments relate to Next Generation (NG) wireless networks, and in particular to measurements for non-terrestrial based network (NTN) systems. [Background technology]
[0003] The use and complexity of new NG or NR radio systems, including 5G networks and beginning to include sixth generation (6G) networks among others, is increasing due to both the increasing number of UE types using network resources and the amount of data and bandwidth used by various applications, such as video streaming, running on these UEs. With a significant increase in the number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, is becoming increasingly complex. As would be expected, with the advent of any new technology there are many issues, including the complexities associated with NTN networks. [Brief description of the drawings]
[0004] In the figures, the figures are not necessarily drawn to scale, but like numbers may depict like elements in different views of each other. Like numbers with different suffix letters may represent different instances of like components. The figures generally illustrate, by way of example, and not by way of limitation, various embodiments discussed in the present document.
[0005] [Figure 1A] 1 illustrates an architecture of a network, according to some aspects.
[0006] [Figure 1B]1 illustrates a non-roaming 5G system architecture, according to certain aspects.
[0007] [Figure 1C] 1 illustrates a non-roaming 5G system architecture, according to certain aspects.
[0008] [Diagram 2] 1 illustrates a block diagram of a communications device according to some embodiments.
[0009] [Diagram 3] 1 illustrates multiple Signaling System / Physical Broadcast Channel (SS / PBCH) Block Measurement Timing Configurations (SMTC) according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The following description and drawings sufficiently illustrate certain embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.
[0011] 1A illustrates an architecture of a network according to some aspects. Network 140A includes 3GPP LTE / 4G and NG network functions that may be extended to 6G and later generation functions. Thus, while reference is made to 5G, it should be understood that this should be extended to the extent possible to 6G (and later) structures, systems and functions. Network functions may be implemented as separate network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtualized functions instantiated on a suitable platform, e.g., dedicated hardware or cloud infrastructure.
[0012] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and UE 102 are illustrated as smartphones (e.g., handheld, touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and UE 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.
[0013] Any of the wireless links described herein (e.g., as used in network 140A or any other illustrated network) may operate according to any exemplary wireless communication technology and / or standard. Any spectrum management scheme may be used, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies, Spectrum Access System (SAS) in 3.55-3.7 GHz, and other frequencies, etc.). Different single carrier or orthogonal frequency domain multiplexing (OFDM) modes (such as CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), particularly 3GPP NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbol resources.
[0014] In some aspects, any of the UEs 101 and 102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, any of the UEs 101 and 102 may include a Narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a Further Enhanced NB-IoT (FeNB-IoT) UE). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device over a public land mobile network (PLMN), a Proximity-Based Service (ProSe), or a device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC exchange of data may be a machine-initiated data exchange. The IoT network includes interconnected IoT UEs, which may include embedded computing devices that are uniquely identifiable (within the Internet infrastructure) with short-lived connections. The IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network. In some aspects, either the UE 101 and the UE 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.
[0015] The UE 101 and the UE 102 may be configured to connect, e.g., communicatively couple, to a Radio Access Network (RAN) 110. The RAN 110 may be, e.g., a Universal Mobile Telecommunications System (UMTS), a Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The RAN 110 may include one or more gNBs, one or more of which may be implemented by multiple units. Although sometimes referred to herein as a gNB, the same aspects may apply to other generations of NodeBs, such as a sixth generation NodeB, and may be referred to as a next generation NodeB (NGNB).
[0016] Each gNB may implement protocol entities in the 3GPP protocol stack, where the layers are considered to be ordered from bottom to top in the following order: Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Control (PDCP), and Radio Resource Control (RRC) / Service Data Adaptation Protocol (SDAP) (for control plane / user plane). The protocol layers in each gNB may be distributed to different units, namely, a Central Unit (CU), at least one Distributed Unit (DU), and a Remote Radio Head (RRH). The CU may provide functions such as controlling the transfer of user data, performing mobility control, radio access network sharing, positioning, and session management, except for functions exclusively assigned to the DU.
[0017] The upper protocol layers (PDCP and RRC for the control plane / PDCP and SDAP for the user plane) may be implemented in the CU, and the RLC and MAC layers may be implemented in the DU. The PHY layer may be split, with the upper PHY layer also implemented in the DU and the lower PHY layer implemented in the RRH. The CU, DU, and RRH may be implemented by different manufacturers, but may nevertheless be connected by appropriate interfaces between them. The CU may be connected to multiple DUs.
[0018] Interfaces within the gNB include E1 and fronthaul (F)F1 interfaces. The E1 interface may be between the CU control plane (gNB-CU-CP) and the CU user plane (gNB-CU-UP) and thus may support the exchange of signaling information between the control plane and the user plane via E1AP services. The E1 interface may separate the radio network layer and the transport network layer and allow for the exchange of UE-related and non-UE-related information. The E1AP services may be non-UE related services related to the entire E1 interface instance between the gNB-CU-CP and the gNB-CU-UP using a non-UE related signaling connection, or may be UE related services related to a single UE and associated with a UE related signaling connection maintained for the UE.
[0019] The F1 interface may be disposed between the CU and the DU. The CU may control the operation of the DU via the F1 interface. Since signaling in the gNB is split into control plane and user plane signaling, the F1 interface may be split into an F1-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP and an F1-U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support separation of the control plane and the user plane. The F1 interface may separate the radio network layer and the transport network layer and enable the exchange of UE-related information and non-UE-related information. Additionally, the F2 interface may be between the lower and upper parts of the NR PHY layer. The F2 interface may also be separated into F2-C and F2-U interfaces based on the control plane and user plane functions.
[0020] UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed further below). In this example, connections 103 and 104 are illustrated as air interfaces enabling communication coupling and may be consistent with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GP Long Term Evolution (LTE) protocol, 5G protocol, 6G protocol, etc.
[0021] In one aspect, the UE 101 and the UE 102 may further directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a Sidelink (SL) interface that includes one or more logical channels, including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Broadcast Channel (PSFCH).
[0022] The UE 102 is shown configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, whereby the AP 106 may include a WiFi (wireless fidelity) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described further below).
[0023] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission / reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within a communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing a macrocell, e.g., a macro RAN node 111, and one or more RAN nodes for providing a femtocell or picocell (e.g., a cell with a smaller coverage area, lower user capacity, or larger bandwidth compared to a macrocell), e.g., a low power (LP) node 112.
[0024] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for the UE 101 and UE 102. In some aspects, either of the RAN nodes 111 and 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management, data packet scheduling, and radio network controller (RNC) functions such as mobility management. In one example, any of the nodes 111 and / or 112 may be a gNB, eNB, or another type of RAN node.
[0025] The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated with reference to FIGS. 1B-1C ). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a Service Gateway (S-GW) 122, and an S1-Mobility Management Entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and the MME 121.
[0026] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MME 121 may be functionally similar to the control plane of a legacy Serving General Packet Radio Service Support Node (GPRS) SGSN. The MME 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may include a database for network users, including subscriber-related information to support the network entity's processing of communication sessions. The CN 120 may include one or more HSSs 124 depending on the number of mobile subscribers, equipment capacity, organization of the network, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.
[0027] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.
[0028] The P-GW 123 may terminate the SGi interface to the PDN. The P-GW 123 may route data packets between the CN 120 and external networks (alternatively referred to as application functions (AFs)), such as a network including an application server 184, via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data with other external networks 131A, which may include the Internet, an IP multimedia subsystem (IPS) network, and other networks. In general, the application server 184 may be an element that provides applications that use IP bearer resources in conjunction with a core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
[0029] The P-GW 123 may further be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's IP-CAN (Internet Protocol Connectivity Access Network) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session, namely, a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
[0030] In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network, which includes 5G new radio networks that use communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is NB-IoT (narrowband-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and standalone LTE systems in the unlicensed spectrum, according to which LTE-based technologies operate only in the unlicensed spectrum without using an "anchor" in the licensed spectrum called MulteFire. Further enhanced operation of LTE systems in licensed spectrum as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.
[0031] The NG system architecture (or 6G system architecture) may include a RAN 110 and a core network (CN) 120. The NG-RAN 110 may include multiple nodes such as gNBs and NG-eNBs. The CN 120 (e.g., 5G core network (5GC)) may include an access and mobility function (AMF) and (or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNBs and NG-eNBs via an NG interface. More specifically, in some aspects, the gNBs and NG-eNBs may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNBs and NG-eNBs may be coupled to each other via an Xn interface.
[0032] In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some aspects, in a 5G architecture, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN).
[0033] FIG. 1B illustrates a non-roaming 5G system architecture according to some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in a reference point representation that may be extended to a 6G system architecture. More specifically, a UE 102 may communicate with a RAN 110, as well as one or more other CN network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146.
[0034] The UPF 134 may provide a connection to a data network (DN) 152, which may include, for example, operator services, Internet access, or third party services. The AMF 132 may be used to manage access control and mobility, and may also include a network slice selection function. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technology. The SMF 136 may be configured to set up and manage various sessions according to network policies. Thus, the SMF 136 may be responsible for session management and assignment of IP addresses to the UE. The SMF 136 may also select and control the UPF 134 for data forwarding. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. A different SMF may be assigned for each session. The use of different SMFs allows each session to be managed separately. As a result, the functions of each session may be independent of each other.
[0035] The UPF 134 may be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
[0036] The AF 150 may provide information about the packet flows to the PCF 148, which is responsible for policy control to support the desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine appropriate policies for appropriate operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.
[0037] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP multimedia subsystem 168B and a call session control function (CSCF). More specifically, the IMS 168B includes a CSCF that can act as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. 1B), or an interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 in the IM subsystem 168B. The S-CSCF 164B can be configured to handle session state in the network, and the E-CSCF can be configured to handle certain aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to act as a touch point within the network of the network operator for all IMS connections directed to its subscribers or roaming subscribers currently located within its service area. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170B, e.g., an IMS operated by another network operator.
[0038] In some aspects, the UDM / HSS 146 may be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or another application server. The AS 160B may be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.
[0039] The reference point representation indicates that there may be interactions between corresponding NF services. For example, FIG. 1B shows reference points N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), 1B are exemplified as follows: N8 (between UDM 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM 146, not shown), N14 (between two AMFs, not shown), N15 (between PCF 148 and AMF 132 in case of non-roaming scenario, between PCF 148 and visited network and AMF 132 in case of roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.
[0040] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated in FIG. 1B, the system architecture 140C may also include a network publication function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and the interactions between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
[0041] In some aspects, as illustrated in FIG. 1C, a service-based representation may be used to represent network functions in a control plane that allows other authorized network functions to access those services. In this regard, the 5G system architecture 140C may include service-based interfaces, namely Namf 158H (service-based interface exposed by AMF 132), Nsmf 158I (service-based interface presented by SMF 136), Nnef 158B (service-based interface presented by NEF 154), Npcf 158D (service-based interface presented by PCF 148), Nudm 158E (service-based interface presented by UDM 146), NaF 158f (service-based interface presented by AF 150), Nnrf 158C (service-based interface presented by NRF 156), Nnssf 158A (service-based interface presented by NSSF 142), Nausf 158G (service-based interface presented by AUSF 144). Other service-based interfaces not shown in FIG. 1C (e.g., Nudr, N5g-eir, and Nudsf) may also be used.
[0042] The NR-V2X architecture supports reliable, low-latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.
[0043] [Figure 2] illustrates a block diagram of a communication device, according to some embodiments. The communication device 200 may be a specialized computer, a UE such as a personal or laptop computer (PC), a tablet PC, or a smartphone, a dedicated network device such as an eNB, a server executing software that configures the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices shown in Figures 1A-1C. It is noted that the communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.
[0044] As described herein, examples may include or operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) that can perform certain operations and may be configured or arranged in a certain manner. In one example, a circuit may be arranged as a module in a certain way (e.g., internally or with respect to external entities such as other circuits). In one example, all or part of one or more computer systems (e.g., standalone, client or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application parts, or applications) as modules that operate to perform certain operations. In one example, the software may reside on a machine-readable medium. In one example, the software, when executed by the hardware underlying the module, causes the hardware to perform certain operations.
[0045] Thus, the terms "module" (and "component") are understood to encompass tangible entities, i.e., entities that are physically constructed or specifically configured (e.g., hardwired) or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a particular manner or to perform some or all of any operations described herein. Given examples in which the modules are temporarily configured, each of the modules need not be instantiated at any one time. For example, if the modules include a general-purpose hardware processor configured with software, the general-purpose hardware processor may be configured as different modules at different times. Thus, the software may configure the hardware processor, for example, to configure a particular module at one time and a different module at a different time.
[0046] The communication device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage, volatile memory, or non-volatile memory. The communication system 200 may further include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In one example, the display unit 210, the input device 212, and the UI navigation device 214 may be touch screen displays. The communication device 200 may further include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, other sensors, etc. The communication device 200 may include an output controller, such as a serial (e.g., Universal Serial Bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).
[0047] The storage device 216 may include a communication device-readable medium 222, which may include a non-transitory machine-readable medium 222 (hereinafter simply referred to as a machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodied or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within the static memory 206, and / or within the hardware processor 202 during execution by the communication device 200. Although the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 224.
[0048] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions for execution by communication device 200 and causing communication device 200 to perform any one or more of the techniques of this disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory, as well as optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices, magnetic disks, such as internal hard disks and removable disks, magneto-optical disks, Random Access Memory (RAM), and CD-ROM and DVD-ROM disks.
[0049] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via a network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Exemplary communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, the IEEE 802.16 family of standards known as WiMAX, the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, Next Generation (NG) / Fifth Generation (5G) standards, among others. In one example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the transmission medium 226.
[0050] It is noted that the term "circuitry" as used herein refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or groups) and / or memories (shared, dedicated, or groups), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc., configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuitry" may refer to a combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and that program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
[0051] The term "processor circuitry" or "processor" as used herein therefore refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term "processor circuitry" or "processor" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single or multi-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.
[0052] Any of the wireless links described herein may operate in accordance with any one or more of the wireless communication technologies and / or standards, including, but not limited to, the following: That is, GSM (Global System for Mobile Communications) wireless communication technology, GPRS (General Packet Radio Service) wireless communication technology, EDGE (Enhanced Data Rates for GSM Evolution) wireless communication technology, and / or 3GPP (Third Generation Partnership Project) wireless communication technology, such as UMTS (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3GPP LTE (Long Term Evolution), 3GPP LTE Advanced (Long Term Evolution Advanced), CDMA2000 (Code division multiple access 2000), CDPD (Cellular Digital Packet Data), Mobitex, 3G (Third Generation), CSD (Circuit Switched Data), HSCSD (High-Speed Circuit-Switched Data), UMTS (3G) (Universal Mobile Telecommunications System (Third Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA (High Speed Packet Access), HSDPA (High-Speed Downlink Packet Access), HSUPA (High-Speed Uplink Packet Access), HSPA+ (High Speed Packet Access Plus), UMTS-TDD (Universal Mobile TelecommunicationsSystem-Time-Division Duplex), TD-CDMA (Time Division-Code Division Multiple Access), TD-CDMA (Time Division-Synchronous Code Division Multiple Access), 3GPP Rel. 8 (Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4th Generation)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10), 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent releases (Rel. 18, Rel. 19, etc.), 3GPP 5G, 5G, 5G NR (5G New Radio), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LAA (LTE Licensed-Assisted Access), MuLTEfire, UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial RadioAccess), LTE Advanced (4G)(Long Term Evolution Advanced (4th Generation)), cdmaOne (2G), CDMA2000 (3G)(Code division multiple access 2000 (Third generation)), EV-DO(Evolution-Data Optimized or Evolution-Data Only), AMPS (1G)(Advanced Mobile Phone System (1st Generation)), TACS / ETACS(Total Access Communication System / Extended Total Access Communication System), D-AMPS (2G) (Digital AMPS (2nd Generation)), PTT (Push-to-talk), MTS (Mobile Telephone System), IMTS (Improved Mobile Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Mobiltelefonisystem D, or Mobile telephony system) Swedish abbreviation for D), Autotel / PALM (Public Automated Land Mobile), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), NTT's (Nippon Telegraph and Telephone) high capacity version (Hicap), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit SwitchedData), PHS (Personal Handy-phone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, 3GPP Generic Access Network, or UMA (Unlicensed Mobile Access), also known as GAN standard, Zigbee, Bluetooth(r), WiGig (Wireless Gigabit Alliance) standard, mmWave standard in general (wireless systems operating at 10-30 GHz and above, such as WiGig, IEEE 802.11ad, IEEE 802.11ay), technologies operating above 300 GHz and in the THz bands (3GPP / LTE-based, IEEE 802.11p, IEEE 802.11bd and others) Vehicle-to-Vehicle (V2V), Vehicle-to-X (V2X), Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, Dedicated Short Range Communications (DSRC) communication systems such as intelligent transportation systems and others (typically operating at 5850 MHz to 5925 MHz or higher (typically up to 5935 MHz according to the proposed changes in CEPT Report 71)), European ITS-G5 systems (i.e. European flavors of IEEE 802.11p-based DSRC, such as ITS-G5A). (i.e. ITS-G5 operation in the European ITS frequency bands dedicated to ITS for safety-related applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e. operation in the European ITS frequency bands dedicated to ITS non-safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e. operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700 MHz band (including 715 MHz to 725 MHz), IEEE 802.11bd-based systems, etc.
[0053] The aspects described herein may be used in the context of any spectrum management scheme, including dedicated licensed spectrum, license-free spectrum, license-exempt spectrum, (licensed) shared spectrum (such as LSA=Licensed Shared Access in the frequencies 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies, and SAS=Spectrum Access System / CBRS=Citizen Broadband Radio System in the frequencies 3.55-3.7 GHz and further frequencies).The applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum / bands, such as nationally allocated bands (450-470MHz, 902-928MHz (Note: allocated, for example, by the United States (FCC Part 15)), 863-868.6MHz (Note: allocated, for example, by the European Union (ETSI EN 300 220)), 915.9-929.7MHz (Note: allocated, for example, by Japan), 917-923.5MHz (Note: allocated, for example, by South Korea), 755-779MHz, etc. MHz, and 779-787MHz (Note: allocated, for example, in China), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: globally available ISM bands used by the Wi-Fi family of technologies (11b / g / n / ax) and Bluetooth), 2500-2690MHz, 698-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: allocated, for example, in Citizen Broadband Radio 5.15~5.25GHz, 5.25~5.35GHz, 5.47~5.725GHz, 5.725~5.85GHz (Note: Allocated in the US (FCC Part 15), consisting of four U-NII bands totaling 500MHz of spectrum), 5.725~5.875GHz (Note: Allocated in the EU (ETSI EN 893), for example), 5.47~5.65GHz (Note: Allocated in Korea, for example), 5925~7125MHz, 5925~6425MHz (Note: Under consideration in the US and EU, respectively. Note that next-generation Wi-Fi systems are expected to include the 6GHz band as an operating band, but as of December 2017, Wi-Fi systems are not yet permitted in this band.The restrictions are expected to expire in the 2019-2020 time frame), IMT Advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800-4200 MHz, 3.5 GHz bands, 700 MHz bands, and bands in the 24.25-86 GHz range, etc.), spectrum made available under the FCC's "Spectrum Frontier" 5G initiative (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHz, and 92-94 GHz, etc.), 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz Intelligent Transport Spectrum (ITS) spectrum. Bands currently allocated to WiGig, such as WiGig Band 1 (57.24~59.40 GHz), WiGig Band 2 (59.40~61.56 GHz), WiGig Band 3 (61.56~63.72 GHz), and WiGig Band 4 (63.72~65.88 GHz), 57~64 / 66 GHz (Note: this band has the near-global name for MGWS (Multi-Gigabit Wireless Systems) / WiGig, and the US (FCC part 15) has allocated a total of 14 GHz spectrum, and the EU (ETSI EN 302 567 and ETSI EN 301 for fixed P2P) 217-2) allocates a total of 9 GHz of spectrum), including the 70.2 GHz to 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76 to 81 GHz, and future bands including 94 to 300 GHz and above. Additionally, the scheme could be used on a secondary basis over bands such as the TV white space bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being promising candidates in particular.In addition to cellular applications, specific applications for vertical markets such as Program Making and Special Events (PMSE), medical, health, surgery, automotive, low latency, drones, etc. applications may be addressed.
[0054] The aspects described herein may also be implemented to allow for hierarchical application of the scheme by introducing a hierarchical prioritization of usage for different types of users (e.g., low / medium / high priority, etc.) based on prioritized access to spectrum, e.g., highest priority for Tier 1 users, then Tier 2, then Tier 3, etc.
[0055] The aspects described herein can also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), in particular 3GPP New Radio (NR), by allocating OFDM carrier data bit vectors to corresponding symbol resources.
[0056] Beyond traditional mobile broadband services, 5G networks will provide a variety of new services, such as the Internet of Things (IoT), industrial control, autonomous driving, and mission-critical communications, which have requirements for ultra-low latency, ultra-high reliability, and high data capacity due to safety and performance issues. Some of the features in this document are defined for the network side for AP, eNB, NR, gNB, etc. It is noted that the terminology is typically used in the context of 3GPP 5G and 6G communication systems, etc. Furthermore, a UE may also play this role and act as an AP, eNB, or gNB, i.e. some or all of the functions defined for network equipment may be implemented by the UE.
[0057] As mentioned above, in NTN systems where each cell is served by a different satellite in low earth orbit (LEO), due to the high relative velocity between the satellite and the UE (which can be tens of ms), the UE may experience a large timing difference between the serving neighbor cell and the target neighbor cell when measurements for mobility functions are made. This is typically the result of limited relative movement of the UE cell, so that the reference signal can be measured by the UE within the SMTC window. However, this is not the case in NTN systems where the relative movement between the UE and the satellite is large and delays may lead the UE to measure the reference signal from an incorrect cell in a particular SMTC. Multiple SMTCs for a set of multiple cells may be configured according to UE information and real-time estimation of the timing difference between the set of cells. Figure 3 illustrates multiple SMTCs according to some embodiments. As shown, multiple SMTC / measurement gap configurations may be used for a single frequency layer, allowing the UE to take advantage of more SMTC / gap opportunities to accurately measure signaling system blocks (SSBs) that may have drifted from one SMTC to another.
[0058] Measurement gaps are used by the UE to perform measurements when the UE cannot simultaneously transmit / receive on the serving cell and measure the target carrier frequency. The UE may use measurement gaps to perform inter-frequency / intra-frequency and inter-RAT measurements. The measurements may be gap-assisted (network configures the measurement gaps) or non-gap-assisted and may depend on the UE capabilities, the UE operating frequency (Frequency Range 1 (FR1) or FR2), and the active bandwidth portion (BWP). For example, measurement gap lengths of 1.5, 3, 3.5, 4, 5.5, and 6 ms and measurement gap repetition periods (periods at which the measurement gaps recur) of 20, 40, 80, and 160 ms may be used. The measurement gap pattern may have a gap offset indicating the starting subframe within the period (e.g., if the periodicity is 40 ms, the offset ranges from 0 to 39). The measurement gap timing advance (mgta), if set, indicates when the UE starts measurements before the occurrence of a gap subframe (i.e., the measurement gap starts mgta ms advanced to the end of the most recent subframe that occurs immediately before the measurement gap). TA may be 0.25 ms (FR2) or 0.5 ms (FR1). The UE may be provided with a subframe number and an indication of the serving cell whose subframe is used for gap calculation for the gap pattern.
[0059] During the measurement gaps, measurements (one or more of SS-RSRP / RSRQ / SINR) are performed on the neighbor cell's SSB. The network provides the timing of the neighbor cell SSB using SMTC. The measurement gap and SMTC duration are configured to allow the UE to identify and measure the SSB within the SMTC window. The measurement gap may be per UE or per FR. The network may provide the measurement gap pattern configuration to the UE via a Radio Resource Control (RRC) message, in particular the MeasGapConfig IE in the MeasConfig information element carried by the RRC reconfiguration message.
[0060] The network may configure the UE with multiple SMTC configurations, which may have different offsets and different periodicities. Different SMTC configurations may be associated with different sets of cells belonging to different satellite transmission / reception points (TRPs) / beams with different timing reference signals. According to the UE implementation, the UE reports the capability of supporting simultaneous SMTC configurations. That is, the UE indicates the maximum number of SMTC configurations it supports simultaneously, with different SMTC offsets (and may even have different periodicities). The network configures and reconfigures via specific signaling messages, including radio resource control (RRC), MAC control element (CE) and / or downlink control information (DCI), according to the UE capabilities and the estimated timing difference between the serving cell and the target cell. When the UE measures with multiple SMTC configurations, there may be scheduling restrictions on the SMTC opportunities according to different UE capabilities / implementations. This may avoid problems arising from large propagation delays between the serving cell and neighboring cells for NTN UE measurements.
[0061] 3GPP agreed to introduce multiple SMTCs and measurement gaps for a specific carrier frequency to address the issue of timing differences due to large propagation delays between serving and neighboring cells. The timing differences can be up to tens of milliseconds in various scenarios. Therefore, it is useful to introduce multiple SMTCs with different timing offsets. To take advantage of the configured multiple SMTCs, the UE may measure cell reference signals from the serving and neighboring cells using the same frequency but at different occasions within the same period (or the frequency may be different depending on the network configuration) and with different timing offsets. This means that the UE may measure the neighboring cell reference signals and receive / transmit on the serving cell at the same time.
[0062] In other cases, the specification of a scheduling restriction may be used to avoid such complications for the UE, and measurement gaps may be used to ensure measurements of neighboring cells even when the target neighboring cells are different frequency cells. This means that for a UE that does not have the capability to simultaneously measure in one of the configured SMTCs and receive / transmit on the serving cell, the network will not schedule data transmissions during said SMTC windows (i.e. no data from / to the UE may be scheduled). This restriction may be achieved by network implementation or by configured measurement gaps.
[0063] In the context of multiple SMTCs, SMTC configurations with different offsets may be associated with different cells in the same frequency layer. One problem with this multiple SMTC configuration is that the network may estimate in real time the timing difference between different cells using different satellite TRPs. One of the purposes of introducing different timing offsets to the SMTC is to accommodate the rather large timing difference caused by the long propagation delay difference between different satellite TRPs. The SMTC configuration may either be dynamically indicated to the UE or be semi-static. In the latter case, the SMTC configuration may be RRC-based such that there is no change in the SMTC offset without an RRC reconfiguration message.
[0064] The maximum number of SMTC configurations that a UE supports per frequency may depend on whether the UE dynamically monitors active SMTC configurations on a particular measurement object (MO): if the network has a relatively constant SMTC configuration on a target MO, the UE can accommodate a larger number of parallel SMTC offsets; conversely, if the network dynamically reconfigures the UE according to real-time estimation of timing differences between different cells, the UE cannot simultaneously support as many configurations as when the SMTC configurations are relatively constant.
[0065] Therefore, in general, the number of supported SMTC configurations with different offsets may be indicated via UE capability signaling. A maximum number of SMTC configurations may be supported on one ssbFrequency in parallel. According to different UE implementations and network configurations, the UE uses UE capability signaling to inform the network, so that the network configures an appropriate number of SMTC configurations according to different deployment scenarios.
[0066] We consider further here whether the network is supposed to configure the SMTC in a fairly dynamic way. The trade-off between having a more dynamic configuration scheme of the SMTC according to real-time timing difference estimation utilizing the UE reported location, and having a relatively constant set of SMTC configurations in general to reduce effort, should be considered for each deployment scenario. However, in most situations it is more useful to determine a middle ground in terms of designing the configuration between the above objectives, so that a fair trade-off between complexity and effectiveness can be reached.
[0067] One method is to configure and reconfigure the UE using dynamic signaling messages, e.g. DCI messages. Alternatively, instead of reconfiguring the UE with dynamic configuration, a fixed set of SMTC configurations may be used, but only a subset of the set of SMTC configurations is activated in the MAC CE or DCI.
[0068] Thus, the network may configure the UE with multiple SMTC configurations, which may have different offsets and even different periodicities. This allows different SMTC configurations to be associated with different sets of cells belonging to different satellite TRPs and / or beams with reference signals with different timings. Restrictions and / or measurement gaps may be used when the UE cannot perform simultaneous transmission / reception and SSB measurements. According to the UE implementation, the UE may report its SMTC configuration capability, indicating the maximum number of SMTC configurations that the UE can support simultaneously. Before the UE reports its capability signaling of the maximum number of supported SMTC configurations, the network may indicate whether dynamic or static configuration of multiple SMTCs is used by a flag in the system information. The maximum number of SMTC configurations indicated by the UE may depend on the value (e.g., dynamic or semi-static) indicated by the flag. The network configures and reconfigures the SMTC configurations through signaling messages including RRC, MAC CE and / or DCI according to the UE capabilities and the estimated timing difference between the serving cell and the target cell. When a UE measures with multiple SMTC configurations, scheduling restrictions may occur on SMTC opportunities according to different UE capabilities / implementations.
[0069] In order to guarantee the UE measurement performance, a set of preconditions for the UE to correctly perform measurements based on SSBs that may have drifted in the NTN system is considered. Multiple SMTC configurations provide more opportunities, and therefore the MTC window may cover the drifted target SSB with a higher probability. If the target SSB is not completely included in the SMTC window, the UE may not be able to correctly perform measurements on the SSBs because it is not supposed to measure outside the SMTC window. In FIG. 3, for example, when the UE is only capable of two multiple SMTCs and SMTC1, 2 are configured in the UE, the UE may not be able to correctly measure SSB2, SSB3 that are not completely included in the SMTC1, SMTC2 windows (in a single frequency layer). In some cases, the UE may select a subset of multiple configured SMTCs and / or scheduling restrictions even when the target neighbor cell is an intra-frequency cell, or the measurement gap may be used to avoid the problem. In some cases, the measurement gap may be used to measure the SMTC window for both intra-frequency and inter-frequency measurements, and the UE does not need to accurately measure the SSBs unless the SSBs are completely included in the measurement gap.
[0070] Although an embodiment has been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes may be made thereto without departing from the broader scope of the present disclosure. The specification and drawings should therefore be regarded in an illustrative and not restrictive sense. The accompanying drawings, which form a part of this specification, show, by way of example, and not by way of limitation, specific embodiments in which the subject matter may be practiced. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. This detailed description should therefore not be construed in a limiting sense, and the scope of the various embodiments is defined solely by the appended claims, along with the full scope of equivalents of those entitled thereto.
[0071] The subject matter may be referred to herein by the term "embodiments" individually and / or collectively for convenience only and without any intention to limit the scope of the present application to any single inventive concept when multiple inventive concepts are in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to one of ordinary skill in the art upon reviewing the above description.
[0072] In this document, the terms "a" or "an" are used to include one or more, independent of any other instance or use of "at least one" or "one or more," as is common in patent documents. In this document, the term "or" is used to refer to a non-exclusive OR, e.g., "A or B" includes "including A but not including B," "including B but not including A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain English equivalents of the terms "comprising" and "wherein," respectively. Also, in the claims that follow, the terms "including" and "comprising" are open-ended, i.e., a system, UE, article, composition, formation, or process that includes elements in addition to the elements recited after such terms in a claim will still be considered to be within the scope of that claim. Furthermore, in the claims that follow, the terms "first," "second," "third," etc. are used merely as labels and are not intended to impose numerical requirements on their objects.
[0073] The Abstract of the Disclosure is provided to comply with 37 CFR §1.72(b), requiring an abstract that will enable the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Additionally, in the foregoing Detailed Description, various features may be found grouped together in a single embodiment to streamline the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
Claims
1. 1. An apparatus for a fifth generation Node B (gNB), comprising: a memory and processing circuitry, the processing circuitry configured to: configuring a plurality of synchronization signal block (SSB) based measurement timing configurations (SMTC) for a set of cells in a non-terrestrial network (NTN) system based on user equipment (UE) capability information and a real-time estimation of a timing difference between the set of cells; and communicating data with the UE based on the plurality of SMTCs; The memory is configured to store the plurality of SMTCs.
2. the capability information indicating support for the UE for simultaneously measuring reference signals from the cells; The apparatus of claim 1 , wherein the processing circuitry is configured to cause the gNB to determine whether to schedule data during an SMTC window based on the capability information.
3. The apparatus of claim 1 , wherein the multiple SMTCs have different offsets.
4. The apparatus of claim 3 , wherein the multiple SMTCs have different periods.
5. The device according to any one of claims 1 to 4, wherein different SMTCs are associated with different sets of cells belonging to different satellite transmitting receiving points (TRPs) with different timing reference signals from said different sets of cells.
6. The apparatus of any one of claims 1 to 4, wherein the capability information indicates the UE's support for simultaneously measuring reference signals from the cells and a maximum number of simultaneously supported SMTCs.
7. The processing circuitry configures the gNB to use a control message to configure the UE with the multiple SMTCs; The apparatus of claim 1 , wherein the control message comprises at least one of a Radio Resource Control (RRC) message, a Medium Access Control (MAC) control element (CE), or a Downlink Control Information (DCI).
8. The processing circuitry is configured to: restricting scheduling of uplink and downlink data on SMTC opportunities of the plurality of SMTCs; and enabling the UE to measure reference signals for same-frequency cells using measurement gaps that overlap with the SMTC occasions.
9. The apparatus of any one of claims 1 to 4, wherein the multiple SMTCs have different offsets and are associated with different cells in a same frequency layer.
10. The processing circuitry is configured to: dynamically indicating the plurality of SMTCs to the UE using Downlink Control Information (DCI); and semi-statically indicating the plurality of SMTCs to the UE using Radio Resource Control (RRC) signaling.
11. The processing circuitry configures the gNB to reconfigure the multiple SMTCs in the UE; The apparatus of claim 10, wherein the maximum number of SMTCs that the UE supports simultaneously depends on a reconfiguration rate of the SMTCs.
12. The processing circuitry is configured to broadcast system information including a flag indicating whether the gNB uses dynamic configuration or semi-static configuration of the plurality of SMTCs; The apparatus of claim 10 , wherein the capability information indicates a maximum number of SMTCs that the UE supports simultaneously, the maximum number of SMTCs that the UE supports simultaneously being dependent on a value of the flag.
13. The processing circuitry is configured to: transmitting a set of multiple SMTCs to the UE via radio resource control (RRC) signaling, the multiple SMTCs having different offsets; and and activating a subset of the plurality of SMTCs via at least one of a Medium Access Control (MAC) control element (CE) and a Downlink Control Information (DCI) according to a real-time estimation of a timing difference between cells belonging to different satellites of the NTN system.
14. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a fifth generation (5G) nodeB (gNB), the one or more processors being configured to, when the instructions are executed, cause the gNB to: receiving capability information from a user equipment (UE) indicating support of the UE for simultaneously measuring reference signals from cells in a non-terrestrial based network (NTN) system; configuring a plurality of synchronization signal block (SSB) based measurement timing configurations (SMTC) for the cells based on the capability information and real-time estimation of timing differences between the cells; and configuring the UE to communicate data based on the plurality of SMTCs and the capability information.
15. The medium of claim 14 , wherein the multiple SMTCs have different offsets.
16. The medium of claim 15 , wherein the multiple SMTCs have different periods.
17. The one or more processors are configured to, when the instructions are executed, broadcast system information including a flag indicating whether the gNB uses a dynamic configuration or a semi-static configuration of the SMTC; The medium according to any one of claims 14 to 16, wherein the capability information indicates a maximum number of SMTCs that the UE supports simultaneously, the maximum number of SMTCs that the UE supports simultaneously being dependent on the value of the flag.
18. The one or more processors, when the instructions are executed, cause the gNB to: transmitting a set of multiple SMTCs to the UE via Radio Resource Control (RRC) signaling, the multiple SMTCs having different offsets; and and activating a subset of the plurality of SMTCs via at least one of a Medium Access Control (MAC) control element (CE) and a Downlink Control Information (DCI) according to a real-time estimation of a timing difference between cells belonging to different satellites of the NTN system.
19. An apparatus for a user equipment (UE), comprising: a memory and processing circuitry, the processing circuitry configured to cause the UE to: Transmitting capability information to a fifth generation NodeB (gNB) indicating a maximum number of synchronization signal block (SSB) based measurement timing configurations (SMTCs) that the UE supports simultaneously for measuring reference signals from cells in a non-terrestrial network (NTN) system; Receive, from the gNB, a plurality of SMTCs for the cells based on the capability information and a real-time estimation of a timing difference between the cells; and communicating data with the gNB based on the plurality of SMTCs; The memory is configured to store the plurality of SMTCs.
20. The processing circuitry is configured to: receiving, from the gNB, broadcast system information including a flag indicating whether the gNB uses dynamic or semi-static configuration of the plurality of SMTCs, wherein a maximum number of SMTCs supported simultaneously by the UE depends on the value of the flag; receiving, via radio resource control (RRC) signaling, a set of multiple SMTCs from the gNB, the multiple SMTCs having different offsets; and 20. The apparatus of claim 19, further comprising: determining a subset of the plurality of SMTCs based on at least one of a Medium Access Control (MAC) control element (CE) and a Downlink Control Information (DCI) from the gNB in accordance with a real-time estimation of a timing difference between cells belonging to different satellites of the NTN system.
