Coverage data transmission for communication with non-terrestrial network nodes

Abstract

The application relates to devices and components including apparatuses, systems and methods to support discontinuous network coverage. In an example, a UE and a network exchange information indicating capabilities for transmitting coverage data for a non-terrestrial network using a control plane, a user plane, a short message service, and / or an operation and maintenance server, the coverage data indicating when and / or where non-terrestrial network coverage is available to the UE. Based on the information, the coverage data is provided on the UE and in an access and mobility function (AMF) in the network. Thereafter, the UE may determine when the UE is in the coverage area of the non-terrestrial network, and may connect to a network node of the non-terrestrial network, such as a base station.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 63 / 442,404, filed January 31, 2023, the entire disclosure of which is hereby incorporated by reference for all purposes. Background Art

[0003] Cellular communications are defined in various standards to enable communication between user equipment and cellular networks. For example, the fifth-generation mobile network (5G) is a wireless standard designed to improve data transmission speed, reliability, availability, and other aspects. Cellular coverage is a relevant characteristic for data transmission. Specifically, when a user equipment (UE) is within cell coverage, the UE may be able to exchange data with the cellular network. Otherwise, the UE may be unable to do so. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 An example of a network environment according to some embodiments is illustrated.

[0005] Figure 2 A fifth generation (5G) network environment according to some embodiments is illustrated.

[0006] Figure 3 An example of network coverage according to some embodiments is illustrated.

[0007] Figure 4 An example of discontinuous coverage according to some embodiments is illustrated.

[0008] Figure 5 Examples of coverage maps according to some embodiments are illustrated.

[0009] Figure 6 An example of a sequence diagram in the context of transmitting overlay data using a control plane according to some embodiments is illustrated.

[0010] Figure 7 Another example of a sequence diagram in the context of transmitting overlay data using a control plane according to some embodiments is illustrated.

[0011] Figure 8 Another example of a sequence diagram in the context of transmitting overlay data using a control plane according to some embodiments is illustrated.

[0012] Figure 9 An example of a sequence diagram in the context of transmitting overlay data using a user plane according to some embodiments is illustrated.

[0013] Figure 10An example of a sequence diagram is illustrated in the context of transmitting coverage data using a short message service, according to some embodiments.

[0014] Figure 11 An example of a sequence diagram in the context of transmitting coverage data stored by an operations and maintenance server of a network is illustrated according to some embodiments.

[0015] Figure 12 Illustrated are examples of operational flows / algorithm structures implemented by a UE in the context of discontinuous network coverage according to some embodiments.

[0016] Figure 13 An example of an operational flow / algorithm structure implemented by a base station in the context of discontinuous network coverage according to some embodiments is illustrated.

[0017] Figure 14 An example of a receiving component according to some embodiments is illustrated.

[0018] Figure 15 An example of a UE according to some embodiments is illustrated.

[0019] Figure 16 An example of a base station according to some embodiments is illustrated. DETAILED DESCRIPTION

[0020] 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 the 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 instances, 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. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0021] Generally speaking, when a user equipment (UE) is in the network coverage of a network, the UE communicates with the network. Network coverage may be provided via a base station of the network. A base station may be referred to as a network node and may be a component of the radio access network (RAN) portion of the network. In some cases, the base station may be physically movable relative to the UE. For example, a base station may be implemented in a communication satellite orbiting the earth (in which case the base station may be referred to as an NTN node). In other cases, the UE may be physically movable relative to the base station (for example, when the UE is a mobile device traveling on the surface of the earth). Of course, there may be a situation where both the UE and the base station are movable relative to each other.

[0022] When the network coverage provided by the base station is no longer available to the UE (e.g., due to the orbital position of the communication satellite and / or the geographic location of the UE), the UE may no longer be able to communicate with the network until network coverage becomes available to the UE again (wherein this "re-coverage" may be provided by the same base station or a different base station). It is beneficial, at least for the UE, to determine when network coverage is available or unavailable (or will be available or unavailable) to it (e.g., in the future). For example, if the expected network coverage is unavailable during the next time interval, the UE may abandon attempts to connect to the network, thereby reducing its power consumption. To perform such a determination, the UE may receive coverage data from the network indicating the network coverage that may be provided to it (e.g., the expected network coverage to be provided by a base station, such as an NTN node). Based on this coverage data, the UE may determine time intervals during which the UE is in network coverage and time intervals during which the UE is out of network coverage. The former time interval may be referred to herein as an "access duration," while the latter time interval may be referred to herein as a "gap duration" (to allude to the fact that a network coverage gap exists).

[0023] Embodiments of the present disclosure implement various techniques for transmitting coverage data to a UE. In one example, a UE and a network (e.g., a control plane function of the network, such as an access and mobility management function (AMF)) may exchange capability information indicating supported data transmission types. This supported type may correspond to transmission using a control plane, a user plane, a short message service (SMS), a system information block (SIB) broadcast, or a transmission originating from an operation and maintenance (O&M) server of the network. Coverage data is transmitted to the UE using a supported data transmission type (e.g., a control plane, a user plane, an SMS, a SIB broadcast, or a transmission originating from an O&M server). The transmission may include specific information to enable the UE to receive and / or request the data from an endpoint storing the coverage data. Thereafter, the UE uses the coverage data to determine when network coverage is available and communicates with the relevant base station during the access duration.

[0024] The following is a glossary of terms that may be used in this disclosure.

[0025] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPG), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HC PLD), a structured ASIC, a programmable system on a chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0026] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes.

[0027] As used herein, the term "interface circuitry" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0028] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and that may describe a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, device, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. A UE may have a primary function of communicating with another UE or a network, and a UE may be integrated with other devices and / or systems (e.g., in a vehicle).

[0029] As used herein, the term "base station" refers to a device with radio communication capabilities, i.e., a device of a communication network (or more simply, a network), and can be configured as an access node in the communication network. A UE's access to the communication network can be at least partially managed by a base station, whereby the UE connects to the base station to access the communication network. Depending on the radio access technology (RAT), a base station can be referred to as a gNodeB (gNB), an eNodeB (eNB), an access point, etc.

[0030] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computing devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computing devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0031] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or network resources provided by a virtualization infrastructure to an application, device, system, etc. The terms "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resource" may refer to any type of shared entity that provides a service and may include computing resources or network resources. System resources can be considered a set of coherent functions, network data objects, or services that can be accessed through a server, where such system resources reside on a single host or multiple hosts and can be clearly identified.

[0032] As used herein, the term "channel" refers to any tangible or intangible transmission medium for conveying data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term representing a path or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection between two devices for sending and receiving information.

[0033] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0034] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0035] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0036] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0037] Figure 1 A network environment 100 according to some embodiments is illustrated. The network environment 100 may include a UE 104 and a network node 108. The network node 108 may be a base station that provides a wireless access cell; for example, a Third Generation Partnership Project (3GPP) New Radio (NR) cell, through which the UE 104 can communicate with the network node 108. The base station may be a component of a terrestrial network, a component of a non-terrestrial network, or a component distributed between a terrestrial network and a non-terrestrial network. The UE 104 and the network node 108 may communicate via an interface compatible with 3GPP technical specifications, such as those defining the fifth generation (5G) NR system standard.

[0038] The network node 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto delivery channels and then mapping the delivery channels onto physical channels. Logical channels can transmit data between the radio link control (RLC) layer and the medium access control (MAC) layer; delivery channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include a physical broadcast channel (PBCH); a physical downlink control channel (PDCCH); and a physical downlink shared channel (PDSCH).

[0039] The PBCH may be used to broadcast system information that a UE 104 may use to initially access a serving cell. The PBCH may be sent in a synchronization signal (SS) / PBCH block along with a physical synchronization signal (PSS) and a secondary synchronization signal (SSS). The SS / PBCH block (SSB) may be used by the UE 104 during the cell search process and for beam selection.

[0040] The PDSCH may be used to transmit end-user application data, Signaling Radio Bearer (SRB) messages, system information messages (except for example MIB), and paging messages.

[0041] The PDCCH may transmit downlink control information (DCI) that is used by the scheduler of the network node 108 to allocate both uplink and downlink resources. The DCI may also be used to provide uplink power control commands, configure the slot format, or indicate that preemption has occurred.

[0042] The network node 108 may also transmit various reference signals to the UE 104. The reference signals may include demodulation reference signals (DMRS) for the PBCH, PDCCH, and PDSCH. The UE 104 may compare the received version of the DMRS with the known transmitted DMRS sequence to estimate the impact of the propagation channel. The UE 104 may then apply the inverse of the propagation channel during the demodulation process of the corresponding physical channel transmission.

[0043] Reference signals may also include CSI-RS. CSI-RS may be a multi-purpose downlink transmission that may be used for CSI reporting, beam management, connected mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.

[0044] Reference signals and information from physical channels can be mapped to the resources of the resource grid. For a given antenna port, subcarrier spacing configuration and transmission direction (e.g., downlink or uplink), there is a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include one PRB in the frequency domain and one OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a resource group used to send PDCCH. One CCE can be mapped to multiple REGs; for example, six REGs.

[0045] Transmissions using different antenna ports may experience different radio channels. However, in some cases, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler shift, Doppler spread, average delay, delay spread, or spatial reception parameters (e.g., characteristics associated with the angle of arrival of the downlink received signal at the UE). Antenna ports that share one or more of these large-scale radio channel characteristics may be considered to be quasi-co-located (QCL) with each other. 3GPP has specified four types of QCL to indicate which specific channel characteristics are shared. In QCL Type A, antenna ports share Doppler shift, Doppler spread, average delay, and delay spread. In QCL Type B, antenna ports share Doppler shift and Doppler spread. In QCL Type C, antenna ports share Doppler shift and average delay. In QCL Type D, antenna ports share spatial receiver parameters.

[0046] The network node 108 may provide transmit configuration indicator (TCI) status information to the UE 104 to indicate the QCL relationship between antenna ports used for reference signals (e.g., synchronization signal / PBCH or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). The network node 108 may use a combination of RRC signaling, MAC control element signaling, and DCI to inform the UE 104 of these QCL relationships.

[0047] The UE 104 may use physical uplink channels to send data and control information to the network node 108. Different types of physical uplink channels are available, including a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH). The PUCCH carries control information from the UE 104 to the network node 108, such as uplink control information (UCI), while the PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0048] In an example, communications with the network node 108 and / or base station may use channels in the frequency range 1 (FR1) band (between 40 megahertz (MHz) and 7,125 MHz) and / or the frequency range 2 (FR2) band (between 24,250 MHz and 52,600 MHz), although other frequency ranges are possible (e.g., frequency ranges with frequencies greater than 52,600 MHz). The FR1 band includes licensed and unlicensed bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of radio access technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A listen-before-talk (LBT) process may be used to avoid or minimize conflicts between different RATs in NR-U, whereby a device applies a clear channel assessment (CCA) check before using a channel.

[0049] like Figure 1 As further illustrated, UE 104 may be located within coverage area 110. Specifically, network node 108 may provide signaling (e.g., the signaling may be carried by one or more beams) to coverage area 110. Coverage area 110 may represent a cell or a portion of a cell provided by network node 108. Coverage area 110 may include multiple UEs, similar to UE 104. When these UEs are within coverage area 110, these UEs may communicate with network node 108 on both the uplink and downlink based on channels available to them.

[0050] Figure 2 5G network environment 200 is illustrated according to some embodiments. Network environment 200 may include UE 204 as part of a 5G system (5GS) 208. UE 104 may be Figure 1 204. The 5GS 208 may also include a 5G access network (e.g., a next generation (NG) radio access network (RAN) 212) and a 5G core network (e.g., a 5G GC 216). The NG RAN 212 may include base stations, such as gNBs, that provide new radio (NR) user plane and control plane protocol terminations for the UE 204. The NG RAN 212 may be coupled with the AMF 220 of the 5GC 216. The AMF 226 is an example of a control plane function of the 5GS 208.

[0051] The components of the network environment 200 can be coupled to each other via various interfaces (or reference points) that define signaling protocols between the respective components. These interfaces can include an N1 interface between the UE 204 and the AMF 220 (e.g., between the NAS layer of the UE or, for simplicity, the NAS and the AMF 220); an N2 interface between the NG RAN 212 and the AMF 220; an NR-Uu interface between the UE 204 and the NG RAN 212; an LTE-Uu interface between the UE 204 and the Evolved Universal Terrestrial Access Network (E-UTRAN) 224; and an Xn interface between the E-UTRAN 224 and the NG RAN 212. The E-UTRAN 224 can be part of an evolved packet system (EPS) 232 that includes an evolved packet core (EPC) 228. The EPC 228 may include a Mobility Management Entity (MME) 229, which may be configured to provide a similar role to the AMF 220, except in the context of an E-UTRAN network. The MME 229 is an example of a control plane function of the EPS 232. The interface between the E-UTRAN 224 and the EPC 228 may be an S1 interface. It should be understood that these interfaces define the end-to-end signaling protocol between the respective components. The actual signals may pass through other components. For example, while signals between the AMF 220 and the UE 204 may be exchanged using the N1 protocol, these signals may be conveyed through one or more nodes of the NG RAN 212.

[0052] The AMF 220 may be a control plane function that provides registration management, connection management, reachability management, and mobility management services. Registration management may allow the UE 204 to register and deregister with the 5GS 208. Upon registration, a UE context may be created within the 5GC 216. The UE context may be a set of parameters that identify and characterize the UE 204. The UE context may include UE identification information, UE capability information, access and mobility information, or protocol data unit (PDU) session information.

[0053] Generally speaking, the AMF 220 and the 5GS 208 may perform a number of registration area management functions to allocate / reallocate a registration area to the UE 204. A registration area may include a set of tracking areas, where each tracking area includes one or more cells covering a geographic area. A tracking area is identified by a tracking area identifier, which may be broadcast in the cells of the tracking area.

[0054] Connection management may be used to establish and release a control plane signaling connection between the UE 204 (e.g., NAS) and the AMF 220. Establishing a control plane signaling connection moves the UE 204 from Connection Management (CM)-ID LE to CM-CONNECTED.

[0055] Mobility management may be used to maintain awareness of the location of the UE 204 within the network. Mobility management may be performed by the AMF 220 and the 5GS Mobility Management (5GMM) sublayer of the NAS within the UE 204 to support identification, security, and mobility of the UE 204 and to provide connection management services to other sublayers.

[0056] The 5GMM sublayer may be associated with different states that are managed independently based on the access type (e.g., 3GPP access or non-3GPP access). If the 5GMM context has not yet been established and the network does not know the UE location, the 5GMM sublayer may be in the 5GMM-DEREGISTERED state. In order to establish the 5GMM context, the sublayer may participate in the initial registration to enter the 5GMM-REGISTERED-INITIATED state, and once the initial registration is accepted, the sublayer may enter the 5GMM-REGISTERED state with the 5GMM context established. From the 5GMM-REGISTERED state, once deregistration is requested, the sublayer may enter the 5GMM-DEREGISTERED-INITIATED state. Once deregistration is accepted, the sublayer may enter the 5GMM-DEREGISTERED state. From the 5GMM-REGISTERED state, the sublayer may also enter the 5GMM-SERVICE-REQUEST-INITIATED state by initiating a service request, and once the service request is accepted, rejected, or fails, the sublayer may re-enter the 5GMM-REGISTERED state. As used herein, a service request may refer to both control plane and user plane service requests.

[0057] The 5GMM sublayer may have a 5GMM-CONNECTED mode and a 5GMM-IDLE mode that affect the manner in which various processes are performed.

[0058] The 5G MM-CONNECTED mode (or RRC Suspended state) with RRC Inactivity Indication is a NAS state introduced by 3GPP to improve the resumption and suspension operations of RRC connections by reducing the time it takes to reactivate suspended bearers compared to the Long Term Evolution (LTE) method of releasing the RRC connection and using a service request procedure to activate the RRC connection. Fast resumption or suspension of active data radio bearers (DRBs) can improve the user experience and reduce the use of radio resources.

[0059] The UE 204 may operate in a 5GMM-CONNECTED mode with an inactivity indication (this mode may be considered as a connectivity mode of the NAS layer with the AMF 220 via a signaling control plane) and in an RRC_INACTIVE state (this state may be considered as a connectivity state of the access stratum (AS) layer with the network via a data plane, whereby the UE 204 is not receiving and / or transmitting data). The UE 204 may also operate in a 5GMM-CONNECTED mode of the NAS layer and an RRC_CONNEC TED state of the AS layer (whereby the UE 204 is receiving and / or transmitting data).

[0060] UE 204 may be implemented as a baseband processor that supports a non-access stratum (NAS) and an access stratum (AS) (also referred to herein as the NAS layer and the AS layer, respectively). The NAS may include a 5G NAS and a legacy NAS. The legacy NAS may include a communication connection with a legacy AS. The 5G NAS may include a communication connection with a 5G AS, a non-3GPP AS, and a Wi-Fi AS. The 5G NAS may include functional entities associated with both access strata. Thus, the 5G NAS may include multiple 5G MM entities and a 5G session management (SM) entity. The legacy NAS may include functional entities such as a short message service (SMS) entity, an EPS session management (ESM) entity, a session management (SM) entity, an EPS mobility management (EM M) entity, and a mobility management (MM) / GPRS mobility management (GMM) entity. In addition, the legacy AS may include functional entities such as an LTE AS, a UMTS AS, and / or a GSM / GPRS AS.

[0061] The baseband processor architecture allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). 5G MM can maintain separate connection management and registration management state machines for each connection. Additionally, the UE 204 can register with a single public land mobile network (PLMN) using both 5G cellular access and non-cellular access. Furthermore, the UE can be in a connected state in one access and idle state in the other, or vice versa. Common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) can exist for both accesses.

[0062] In various embodiments, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform the method for saving power in discontinuous coverage as further described herein.

[0063] Figure 3 An example of network coverage 300 according to some embodiments is illustrated. A UE may be able to access a network 310 via a network node 320 that supports multiple coverage areas. Each coverage area represents a geographic area in which network coverage 300 is available. Support for coverage areas may not be simultaneous. Specifically, network coverage 300 may be discontinuous between coverage areas. For example, network coverage 300 may be available in a first coverage area during a time interval and unavailable in a second coverage area during the same time interval. During a different time interval, network coverage 300 may no longer be available in the first coverage area but available in the second coverage area.

[0064] In an example, the network 310 may implement a particular set of radio access technologies (RATs), such as, but not limited to, 5G and / or different generations of 3GPP networks (e.g., Figure 2 232). Network 310 may also be a terrestrial network, in which case network node 320 may be a terrestrial access node, such as a gNB or eNB (or more generally, a terrestrial base station). In another example, network 310 may be at least partially a non-terrestrial network, in which case network node 320 may be implemented on a communication satellite. In this case, network node 320 may be referred to as a non-terrestrial base station or non-terrestrial network node and may be coupled to the terrestrial network via gateway 332.

[0065] Generally, the network node 320 may cover a large geographic area, where the area may be divided into a large number of coverage areas (hundreds, if not thousands). A UE 304 may be located in a coverage area ( Figure 3350) and can be connected to network node 320 via feeder link 324. Feeder link 324 can use millimeter wave or sub-millimeter wave frequencies (e.g., in the S band or Ka band). In this way, UE 304 can access network 310 via network node 320.

[0066] Network coverage may be available in a coverage area based on a set of beams directed from network node 320 toward the area. This coverage may be temporary and therefore discontinuous. For example, the set of beams may be directed toward coverage area 350 during a first time interval and toward a different coverage area during a second time interval. Additionally or alternatively, network node 320 may be repositioned such that the direction of the set of beams changes from coverage area 350 to a different coverage area.

[0067] Thus, network coverage 300 varies geographically over time. With respect to a particular coverage area (e.g., coverage area 350), network coverage 300 provided by network 310 is discontinuous network coverage in one or more coverage areas. For example, during certain time intervals, network coverage 300 is available in coverage area 350 (e.g., available to UE 304 located in coverage area 350). During other time intervals, network coverage 300 is unavailable in coverage area 350 (e.g., unavailable to UE 304 located in coverage area 350).

[0068] For clarity of explanation, various embodiments are described below in conjunction with a communication satellite as an example of network node 320. However, the embodiments are not limited thereto and are similarly applicable to any other base station (terrestrial or non-terrestrial) belonging to a network that provides discontinuous network coverage and / or any other UE to which discontinuous network coverage can be provided. The discontinuity can be over time (for example, even when the UE does not change position, network coverage can be available to it during the access duration and then become unavailable during the gap duration). Additionally or alternatively, the discontinuity can be geographical. For example, network coverage is available from a first base station in a first area, available from a second base station (or even the same first base station) in a second area, and unavailable between the first area and the second area. In this example, network coverage (or lack of network coverage) can depend on the location of the UE within each area and when it moves between the two areas. Of course, the discontinuity can be both time-based and geographical. In addition, the cause of the discontinuous network coverage is described as being due to the repositioning of the communication satellite. However, there may be other reasons including, for example, a change in beam direction and / or a change in UE positioning (e.g., where the UE may be relocated from a covered area to a geographical area where network coverage is unavailable). These embodiments apply similarly to situations where such discontinuous network coverage reasons occur.

[0069] Figure 4 An example of discontinuous coverage 400 according to some embodiments is illustrated. Here, UE 410 may be located at a location on the Earth. The location may be stationary. A first communication satellite 420A may orbit the Earth and may be part of a network (e.g., by implementing a base station of the network or a component of the base station, such as its modem). The network may be a public land mobile network (PLMN). Radio frequency transmissions from the communication satellite 420A reach the Earth and cover a geographic area, thereby providing network coverage for the geographic area (in which case the network coverage may be referred to as satellite coverage). As the first communication satellite 420A orbits, the geographic area of ​​RF coverage changes, thereby changing the network coverage at least geographically. When the UE 410 is in network coverage (e.g., its location is contained within the geographic area of ​​RF coverage), the UE 410 has access to the network. This duration is Figure 4 4. When UE 410 is out of network coverage (e.g., its location is outside the geographical area of ​​RF coverage), UE 410 no longer has access to the network (e.g., at least via communication satellite 420A). Figure 4 In the example, the gap duration is 440.

[0070] Network coverage may become available again to UE 410 via communication satellite 420A within another access duration, depending on the orbit of communication satellite 420A, its RF transmissions (e.g., beam direction), and the location of UE 410. In other words, UE 410 may repeatedly move in and out of discontinuous network coverage 400 when considering only communication satellite 420A.

[0071] like Figure 4 As further illustrated in FIG, a plurality of communication satellites (illustrated as communication satellites 420A, 420B, ..., 420K) may orbit the Earth. Such communication satellites may belong to the same network (e.g., to the Home PLMN (HPLMN) of UE 410) or to different networks (e.g., to the HPLMN and / or one or more Visited PLMNs (VPLMNs)). Thus, depending on the orbital positioning, RF transmissions of such communication satellites, and the location of UE 410, UE 410 may repeatedly enter and exit discontinuous network coverage 400 provided by these communication satellites. Figure 4In the example of FIG4 , communication satellite 420A provides network coverage to UE 410 during access duration 430 and then does not provide network coverage to UE 410 during gap duration 440. Following gap duration 440, communication satellite 420B provides network coverage to UE 410 during the next access duration 431, after which no network coverage is available for UE 410 for the length of gap duration 441. Thereafter, communication satellite 420K also provides network coverage to UE 410 during a subsequent access duration 432, after which no network coverage is available for UE 410 for the length of gap duration 442. Depending on the orbiting (e.g., speed) and RF transmission (e.g., beamwidth) of communication satellites 420A through 420K, the lengths of access durations 430, 431, and 432 may be different and each may vary over time, and similarly, the lengths of gap durations 440, 441, and 442 may be different and each may vary over time.

[0072] In an example, the communication satellite may be a non-geostationary satellite, such as a low earth orbit (LEO) satellite or a medium earth orbit (MEO) satellite. LEO satellites and MEO satellites are non-geostationary satellites that orbit the Earth with a period varying between approximately 1.5 hours and 10 hours. LEO satellites orbit the Earth at an altitude between 300 km and 1500 km, and MEO satellites orbit the Earth at an altitude between 7000 km and 25000 km. Typically, a constellation of several non-geostationary satellites associated with a handover mechanism for a non-terrestrial network (NTN) may be used for service continuity.

[0073] In contrast, geostationary satellites have circular orbits 35,786 km above the Earth's equator and follow the Earth's rotation. Objects in such orbits have an orbital period equal to the Earth's rotation period and are therefore stationary to terrestrial UEs at a fixed location in the sky.

[0074] Without addressing coverage gaps, UE 410 may waste power searching for cells to monitor for scheduled paging occasions that coincide with coverage gaps, and searching for cells when UE 410 has data to transmit. A UE 410 that wishes to transmit or is scheduled to monitor for paging at a time of day (within a coverage gap) may find itself unable to receive transmissions from a cell and may attempt to find a new cell and reattach. In the worst case, since the scheduled occasion occurs within a coverage gap, UE 410 may be unreachable from the network's perspective. Furthermore, UE 410 may disconnect from the network and retry cell selection and registration (NAS attach). To mitigate discontinuous coverage, UE 410 and the network may need to be aware of gaps in coverage (e.g., be aware of discontinuous network coverage).

[0075] One method for discontinuous coverage mitigation involves providing coverage data to UE 410. The coverage data may indicate locations and / or times where network coverage is expected, and / or locations and / or times where network coverage is not expected. Based on the coverage data, UE 410 may determine whether network coverage is available to it. The behavior of UE 410 may be adopted based on the availability of network coverage. For example, when network coverage is available, the access stratum layer of UE 410 may be activated, and one or more non-access stratum processes may be performed to establish communication between the UE and the network via a base station (e.g., a communication satellite). UE 410 may then transmit data to the network, and vice versa. When network coverage is unavailable, the access stratum layer may be deactivated, and the non-access stratum layer of UE 410 may be notified of the deactivation. UE 410 may then forgo performing different processes including the non-access stratum process, thereby reducing its power consumption.

[0076] In the case of satellite coverage, the satellite orbit may be described by an initial condition and a set of orbital parameters. The satellite almanac contains a coarse orbit and is valid for scheduling purposes. Short-term ephemeris may be used for uplink synchronization and is provided in the form of two subsequent positioning broadcasts or broadcasts of the satellite's position and velocity. Almanac information and ephemeris information may be broadcast in SIBs for scheduling and synchronization purposes. SIB broadcasts may be issued by a communication satellite (e.g., configured as a base station). A UE at the edge of satellite coverage may be able to access the satellite during its access window (e.g., Figure 4 The almanac information may be received and decoded within the access duration 430 of the UE. The almanac information may be available to the UE at least once per access window. The information may also be provided through NAS signaling during the tracking area update procedure in EPS and / or the attach or registration procedure in 5GS. The UE may use the almanac-based prediction and the ephemeris information to determine when satellite coverage will be available and thus optimize its cell search, PLMN selection, and connectivity with the network to reduce power consumption. The network may periodically provide the UE with the next cell / satellite selection information or coverage gap information during the TAU procedure or the Mobility Registration Update (MRU) procedure (if applicable) to improve the cell reselection procedure / PLMN selection procedure and reduce power consumption.

[0077] In addition to or in lieu of using SIB broadcasts for almanac and ephemeris information, various embodiments of the present disclosure also implement other techniques for the network to provide coverage data to the UE, including using the control plane, user plane, SMS, or data transmission from the network's O&M server.

[0078] Different types of information may be included in the coverage data. For example, in the case of satellite coverage, the coverage data may include almanac information and / or ephemeris information. In this and / or other cases, the coverage data may additionally or alternatively include earth position data indicating an area and whether coverage is available in that area or node, and / or timing data indicating when coverage is available or unavailable in the area.

[0079] In an example, the coverage data represents a coverage map and may be referred to herein as coverage map data. The coverage data will indicate, for one or more locations and / or one or more times in the future, whether the UE can expect to receive or not receive coverage from at least one of the satellite RATs (or more generally, a network node of a RAN, including, for example, an NT N-node) at each of the locations and / or at each of the future times. The one or more locations may correspond to fixed locations (e.g., to grid points in a rectangular or hexagonal grid point array), or may correspond to locations along a known or predicted UE trajectory.

[0080] Figure 5 An example of a coverage map 500 according to some embodiments is illustrated. Here, the coverage map 500 is described as being based on coverage data indicating a location. As explained above, other types of information may be included in the coverage data, such as timing information, almanac information, and / or ephemeris information.

[0081] In general, coverage maps 500 illustrate the expected coverage by one or more satellite RATs at one or more locations and for a specific time in the future. A set of coverage maps may then be provided for each time in a time series occurring at fixed periodic intervals, such as at one-minute intervals. The locations 510 supported by the coverage maps may correspond to grid points in a rectangular (or possibly hexagonal) array. Each grid point (in Figure 5 5 (shown as dots in the figure) represents a location 510. These locations 510 (e.g., grid points) can be spaced apart by a fixed distance 520 (e.g., 100 km to 400 km). The absolute location 510 of each grid point can then be known by specifying the absolute (global) location 510 of only one grid point in the array (e.g., the central grid point or a grid point at a corner). The expected satellite coverage at the location of each grid point can then be indicated by a value 530 (e.g., a binary value) indicating whether the coverage is expected to be available or not (e.g., a "zero" value indicates that satellite coverage is expected to be unavailable, as shown in FIG. 5 ). Figure 5 is shown as a blank dot in , while a value of “one” indicates that satellite coverage is expected to be available, as Figure 5Coverage data representing a coverage map 510 (or a set of such coverage maps) may be provided to the UE from a control plane function of the network or from an endpoint external to the network (where information about the endpoint may be provided to the UE by a control plane function of the network).

[0082] Different types of data transmission may be supported to provide coverage data to the UE. These types include control plane data transmission, user plane data transmission, SMS queries, SIB broadcasts, and data transmission associated with the O&M server. The appropriate type to be used may depend on various parameters, such as the coverage data content (e.g., location data, timing data, almanac data, ephemeris data, etc.), payload size, and / or update frequency. Based on the type and assuming that the UE and the network support this type, a target layer in the UE and the network may be used. Security protocols may be used to ensure that the coverage data transmission is secure. Additionally, the UE's subscription to the network may be checked to determine, for example, whether coverage data transmission to the UE is enabled (e.g., allowed via a subscription) and / or for billing an account for coverage data transmission.

[0083] In general, the data transmission type to be used can be negotiated or coordinated between the UE and the network. For example, capability information regarding the data transmission types supported by the UE and / or the network can be exchanged. Based on the capability information exchange, a selection can be made (e.g., by the network and / or the UE) to use a supported type.

[0084] In an example, the UE transmits UE capability information to the network (e.g., via RRC signaling or NAS signaling) indicating the data transmission types supported by the UE. If multiple types are indicated, the UE may also indicate its preferred data transmission type and / or a priority list of data transmission types. The network (e.g., a control plane function such as an AMF or MME) may select one of the data transmission types supported by the UE and indicate the selection to the UE. The indication may be explicit (e.g., via an RRC message or NAS message) or implicit (e.g., whereby the network begins using the selected data transmission type to transmit coverage data to the UE). In the case where the UE indicates a single UE-supported data transmission type, the network may, but need not, transmit an acknowledgment and may begin using that data transmission type.

[0085] The UE may indicate its UE capabilities for data transmission types in one or more mobility management capability information elements (IEs), such as the 5GMM capability IE. Such IEs may be of a specific type corresponding to coverage map data transmission capabilities.

[0086] In another example, the network transmits network capability information to the UE (e.g., via RRC signaling) indicating the data transmission types supported by the network. If multiple types are indicated, the network may also indicate its preferred data transmission type and / or a priority list of data transmission types. The UE may select one of the data transmission types supported by the network and indicate the selection to the network. The indication may be explicit (e.g., via an RRC message) or implicit (e.g., whereby the UE begins using the selected data transmission type to receive coverage data from the network). In the case where the network indicates a single data transmission type supported by the network, the UE may, but need not, transmit an acknowledgment and may begin using that data transmission type.

[0087] The network may indicate its network capabilities for data transmission types in one or more Network Feature Support IEs (such as 5GS Network Support IEs). Such IEs may have a specific type corresponding to coverage map data transmission capabilities.

[0088] Figure 6 An example of a sequence diagram 600 is illustrated in the context of transmitting coverage data using a control plane according to some embodiments. Sequence diagram 600 is illustrated in conjunction with EPS, where an MME of the EPS is used. However, embodiments of the present disclosure are not limited thereto, and other control plane functions of the EPS may additionally or alternatively be used.

[0089] Sequence diagram 600 may be applicable to a network that provides discontinuous network coverage (e.g., NTN) and utilizes E-UT RAN technology. The network includes an eNB 620 (e.g., having its components implemented on a communications satellite) and an MME 630 (e.g., implemented as a terrestrial component). Sequence diagram 600 includes a broadcast by eNB 620, which may indicate whether the network is a TN or an NTN. This broadcast may be received by UE 610. For example, this broadcast may be a SIB1 broadcast. This broadcast may also include almanac information and ephemeris information. Thus, UE 610 may determine whether the network is a TN or an NTN and, in the case of an NTN, may predict satellite coverage (or, more generally, network coverage). In the case of an NTN, the UE may have previously camped on an NTN cell of the network. The UE may determine whether it is still camped on the same NTN cell based on, for example, the cell ID, the camped tracking area identifier (TAI), and / or frequency characteristics. If it is the same NTN cell, the UE can skip reading the satellite coverage information (e.g., ephemeris information and almanac information) broadcast by the NTN cell, because the information will be the same. In this way, the UE can save power by not reading the same information again.

[0090] When UE 610 is in a coverage area (e.g., network coverage is provided to the UE by eNB 620 or another eNB implemented on a communication satellite), UE 610 may perform a number of procedures, including an attach procedure. As part of the attach procedure, UE 610 may transmit an attach request message to MME 630 via the applicable eNB. The attach request message may include UE capability information indicating the UE's ability to use the control plane for coverage data transmission. MME 630 may respond with an attach accept message. The attach accept message may include coverage map information. This information may include updated almanac information and ephemeris information. This information may also or alternatively include location information and / or timing information from the coverage map. Thus, the coverage map information includes one or more different types of information transmitted by the network (e.g., MME 630) to UE 610 as part of the coverage data. UE 610 may determine whether network coverage is as expected based on the coverage map information. This determination may include a prediction of where and / or when network coverage will be present (and associated access durations and / or gap durations).

[0091] Next, UE 610 is out of coverage. UE 610 may operate in a power saving mode. For example, the AS layer may be disabled to save power. The NAS layer may also abandon various network operations. The network may also abandon paging.

[0092] Thereafter, when the UE 610 is again in the coverage area, the UE 610 may exit the power saving mode. For example, the AS layer is activated and the NAS layer is notified. The UE 610 may perform multiple procedures including a TAU procedure. As part of the TAU procedure, the UE 610 transmits a TAU request message to the MME 630 via the relevant eNB, where the request may indicate the UE's capabilities for coverage data transmission types. The MME 630 may transmit a TAU accept message via the relevant eNB. The message may include coverage map information (e.g., updated coverage map information), which is then used by the UE 610 to further determine the expected network coverage.

[0093] Although TAU-related messages are described in sequence diagram 600 as being used to cover data transmission, other types of messages are possible. For example, downlink generic NAS transfer messages may be used.

[0094] Figure 7 Another example of a sequence diagram 700 is illustrated in the context of transmitting coverage data using a control plane according to some embodiments. Sequence diagram 600 is illustrated in conjunction with 5GS, where the 5GS AMF is used. However, embodiments of the present disclosure are not limited thereto, and other control plane functions of the 5GS may be used in addition or alternatively.

[0095] Sequence diagram 700 may be applicable to a network that provides discontinuous network coverage (e.g., NTN) and utilizes NG RAN technology. The network includes a gNB 720 (e.g., having its components implemented on a communications satellite) and an AMF 730 (e.g., implemented as a terrestrial component). Sequence diagram 700 includes a broadcast by gNB 720, which may indicate whether the network is a TN or an NTN. This broadcast may be received by UE 710. For example, this broadcast may be a SIB1 broadcast. This broadcast may also include almanac information and ephemeris information. Thus, UE 710 may determine whether the network is a TN or an NTN and, in the case of an NTN, may predict satellite coverage (or, more generally, network coverage).

[0096] When UE 710 is in a coverage area (e.g., network coverage is provided to the UE by gNB 720 or another gNB implemented on a communication satellite), UE 710 may perform various procedures, including a registration procedure. As part of the registration procedure, UE 710 may transmit a Registration Request message to AMF 730 via the applicable gNB. The Registration Request message may include UE capability information indicating the UE's ability to use the control plane for coverage data transmission. AMF 730 may respond with a Registration Accept message. The Registration Accept message may include coverage map information. This information may include updated almanac and ephemeris information. This information may also or alternatively include location information and / or timing information from the coverage map. Thus, the coverage map information includes one or more different types of information transmitted by the network (e.g., AMF 730) to UE 710 as part of the coverage data. Based on the coverage map information, UE 710 may determine whether network coverage is expected. This determination may include a prediction of where and / or when network coverage will be present (and associated access durations and / or gap durations).

[0097] Next, UE 710 is out of coverage. UE 710 may operate in a power saving mode. For example, the AS layer may be disabled to save power. The NAS layer may also abandon various network operations. The network may also abandon paging.

[0098] Thereafter, when UE 710 is again in coverage, it may exit power save mode. For example, the AS layer is activated and the NAS layer is notified. UE 710 performs various procedures, including a mobility and periodic update registration procedure. As part of this procedure, UE 710 transmits a mobility and periodic update registration request message to AMF 730 via the associated gNB, where the request may indicate UE capabilities. AMF 730 may transmit a registration accept message via the associated gNB. This message may include coverage map information, which UE 710 then uses to further determine expected network coverage.

[0099] In an example, in addition to or in lieu of using a registration procedure to provide coverage data to the UE 710, a configuration update procedure and / or NAS transfer messaging may be used. For example, the AMF 730 may transmit a Configuration Update Command message to the UE 710, wherein the message may include coverage map information. In response, the UE 710 may transmit a Configuration Update Complete message to the AMF 730. In another example, the UE may transmit an uplink NAS Transfer message to the AMF 730, wherein the message requests coverage data. In response, the AMF 730 may transmit a downlink NAS Transfer message including coverage map information.

[0100] In any of the above messages (e.g., a Registration Accept message, a Configuration Update message, or a Downlink NAS Transfer message), a container of the container type may be used, and one or more IEs may be added therein to include coverage map information. The container may be a transparent container (e.g., a container that may be encapsulated and / or not decoded by the gNB 720).

[0101] The container type may be specific to the coverage data described herein. For example, according to 3GPP TS24.501 Table 9.11.3.40.1, an IE with a payload container type value of one octet in length is used. This octet may be set to a value indicating "satellite coverage map data". The purpose of the payload container type IE indicates the type of payload included in the payload container IE, is encoded in Table 9.11.3.40.1, and is a type 1 information element. Therefore, an existing payload container (e.g., according to 3GPP TS24.501) may be used, but its payload container type IE may be updated to indicate "satellite coverage map data". Both IP-based data and non-IP-based data may be transmitted using control plane mechanisms.

[0102] Additionally or alternatively, new message exchanges may be defined between the UE 710 and the AMF 730. For example, new containers and / or new information elements may be defined similar to the UE Policy Delivery Service in Annex D of 3GPP TS 24.501, V18.1.0 (2022-12), which is incorporated herein by reference in its entirety. Figure 8 Examples of new messages are described in conjunction with satellite data commands as an example.

[0103] Re-reference Figures 6 and 7 , these figures illustrate the use of control plane data transmission. For power-efficient, relatively infrequent transmission of small amounts of coverage data, control plane data transmission can be a better choice than user plane data transmission. The target layers for using coverage data can be the MME / AMF on the network side and the EMM / 5GMM NAS layer on the UE side. When more than one message is transmitted, delivery features (such as packet numbering, sequential delivery and acknowledgment) do not need to be provided directly by the NAS transport. Such transmission features can be made available by higher layer protocols (such as control plane protocols other than NAS protocols). An example of such a protocol is the Reliable Data Service (RDS) described in 4GPP TS 24.250, V17.0.0 (2022-05), which is incorporated herein by reference in its entirety.

[0104] RDS supports peer-to-peer data transmission and provides reliable data delivery between the UE and the network. In EPS, data is transmitted via a packet data network (PDN) connection between the UE and a service capability exposure function (SCEF) or a PDN gateway (P-GW). In 5GS, data is transmitted between the UE and a network exposure function (NEF) or a user plane function (UPF) via a protocol data unit (PDU) session between the UE and a session management function (SMF). -RDS supports multiple applications on the UE to simultaneously perform data transmission with their peer entities on the network using a single PDN connection or PDU session between the UE and the network. In 5GS, the UE establishes a PDU session with the SMF through a UE-requested PDU session establishment procedure. The UE uses the PDU session identifier and the quality of service (QoS) flow identifier to select a flow to transmit the RDS PDU to the NEF or UPF. The PDU session identifier identifies the destination (at the UE or at the NEF or UPF) and is not carried in the frame because it is already included in the NAS 5GSM message header. The UE transmits an RDS request in an uplink NAS transfer message, and the network responds with a response in a downlink NAS transfer message. When using RDS, the UE may transmit a request for data in an uplink NAS transfer message, and RDS may respond with multiple downlink NAS transfer messages that may carry satellite coverage data. RDS can be used for both IP-based and non-IP-based data delivery.

[0105] Generally, the size of the data transferred can be limited to 65K octets. Data transfer can be accomplished using transparent containers or by using specific IEs. Existing NAS security mechanisms are applicable to ensure the security of data transfer. In addition, existing UE subscriptions can be taken into account and the UE can be billed accordingly.

[0106] Figure 8 Another example of a sequence diagram 800 is illustrated in the context of transmitting coverage data using a control plane, according to some embodiments. Here, the transmission of coverage data involves the use of a "Manage Satellite Data Command" message, which may be a new type of message defined for transmitting coverage map information. As illustrated, the network 820 (e.g., its control plane function) may transmit a Manage Satellite Data Command message to the UE 810. The message may include coverage map information, as described above and elsewhere in this disclosure. In response, the UE 810 may transmit a Manage Satellite Data Complete message based on the successful receipt of the coverage data payload. This message may indicate an acknowledgement of the response to the Manage Satellite Data Command message and / or the receipt of the coverage map information.

[0107] In an example, an application function (AF), a policy control function (PCF), or some other entity (or control plane function) of network 820 can provide coverage data to UE 810 in a manner similar to how UE policy is delivered to the UE as described in Annex D.2 of 3GPP TS 24.501. For example, the manage satellite data command message may include a payload container type indicating a procedure transaction identifier (PTI), a manage satellite data command message, an identifier, a container type, and a container type. The payload container type may be set to a value indicating "satellite coverage map data." The manage satellite data complete message may include a PTO and a manage satellite data complete message identifier.

[0108] Although the sequence diagram 800 is illustrated as Figure 6 Sequence diagram 600 and Figure 7 700, but the steps of sequence diagram 800 may be used in conjunction with or as part of sequence diagram 600 and / or sequence diagram 700. For example, after performing an attach procedure (as in sequence diagram 600) or after performing a registration procedure (as in sequence diagram 700), network 820 may transmit a manage satellite data command message to UE 810 (assuming UE 810 is in a coverage area).

[0109] Re-reference Figures 6 to 8, these figures illustrate the use of a control plane to transmit overlay data via a control plane function. Other possible methods for overlay data transmission are possible and are Figures 9 to 11 For the sake of clarity, the 5GS is further illustrated. Figures 9 to 11 However, similar sequence diagrams are also applicable to EPS. For example, Figure 6 As illustrated, the MME may be involved instead of the AMF. Figure 6 As illustrated, an attach request may be used instead of an initial registration request.

[0110] Figure 9 An example of a sequence diagram 900 is illustrated in the context of transmitting coverage data using a user plane, according to some embodiments. Sequence diagram 900 may be applicable to a network that provides discontinuous network coverage (e.g., NTN) and uses NG RAN technology. The network includes a gNB 920 (e.g., having its components implemented on a communication satellite) and an AMF 930 (e.g., implemented as a terrestrial component). Sequence diagram 900 includes a broadcast by gNB 920, which may indicate whether the network is a TN or an NTN. The broadcast may be received by UE 910. For example, the broadcast may be a SIB1 broadcast. The broadcast may also include almanac information and ephemeris information. Thus, UE 910 may determine whether the network is a TN or an NTN and, in the case of an NTN, may predict satellite coverage (or, more generally, network coverage).

[0111] When UE 910 is in a coverage area (e.g., network coverage is provided to the UE by gNB 920 or another gNB implemented on a communication satellite), UE 910 may perform various procedures, including a registration procedure. As part of the registration procedure, UE 910 may transmit a Registration Request message to AMF 930 via the applicable gNB. The Registration Request message may include UE capability information indicating the UE's ability to use the user plane for coverage data transmission. AMF 930 may respond with a Registration Accept message. The Registration Accept message may include coverage map information and endpoint information. The coverage map information may include updated almanac and ephemeris information. This information may also or alternatively include location information and / or timing information from the coverage map. Thus, the coverage map information includes one or more different types of information transmitted by the network (e.g., AMF 930) to UE 910 as part of the coverage data. Based on the coverage map information, UE 910 may determine whether network coverage is expected. This determination may include a prediction of where and / or when network coverage will be present (and associated access durations and / or gap durations). The endpoint information may include information about the endpoint 940 storing the coverage map information and / or information about accessing the coverage map information from the endpoint 940. Generally speaking, the endpoint 940 may belong to a network, and a connection to the endpoint may be established via a control plane function of the network (e.g., via an AF or SMF). The endpoint information may include an address of the endpoint (e.g., a network address such as a uniform resource identifier (URI) or a uniform resource locator (URL)) and a token. The token may be used to verify that the UE 910 is authorized to access the coverage map information and may be referred to herein as an authorization token.

[0112] Next, UE 910 is out of coverage. UE 910 may operate in a power saving mode. For example, the AS layer may be disabled to save power. The NAS layer may also abandon various network operations. The network may also abandon paging.

[0113] Thereafter, when UE 910 is in the coverage area again, UE 910 can exit power saving mode. For example, the AS layer is activated and the NAS layer is notified. Based on the activated AS layer, UE 910 can transmit a user plane request to endpoint 940. The user plane request may include a token so that endpoint 940 can determine that UE 910 is authorized to receive coverage map information. In an example, the user plane request may be a Hypertext Transfer Protocol Secure (HTTPS) GET request using the network address of endpoint 940. Then, endpoint 940 can transmit a user plane response to UE 910. The response may include coverage map information. In an example, the response may be an HTTPS 200 OK response. UE 910 then uses the received coverage map information to further determine the expected network coverage.

[0114] Generally speaking, user plane data transmission can be used for more frequent and / or larger amounts of coverage data transmission compared to control plane data transmission. In the case of user plane data transmission, the data transmission typically originates from an external server that can be considered an application function AF. Delivery features such as packet numbering, sequential delivery, and acknowledgment can be provided directly based on the user plane protocol (e.g., the HTTPS protocol). Data transmission can be accomplished using a transparent container or by using specific IEs. The size of the data can be greater than 65K octets. User plane security mechanisms are established, such as the security mechanisms provided by HTTPS. Existing UE subscriptions can be taken into account and the UE 910 can be charged accordingly. The UE 910 can transmit an HTTPS Get request {URI=authorization data}, and the endpoint 940 can return an HTTPS 200 OK message with the coverage data. The UE can use a registration procedure to obtain authorization data (e.g., an authorization token) and the network address of the endpoint 940. The authorization token included in the Get request can be used to authenticate the request. Alternatively or additionally, some or all of the endpoint information can be server configuration information pre-configured in the Universal Subscriber Identity Module (USIM) of the UE 910. For example, the USIM may store a network address and / or an authorization token. In this case, the network (e.g., AMF 930) may transmit updated endpoint information (e.g., an updated network address) or required endpoint information (e.g., an authorization token, when such a token is not stored in the USIM) to the UE 910.

[0115] Figure 10 An example of a sequence diagram 1000 is illustrated in the context of transmitting coverage data using a short message service (SMS) according to some embodiments. Sequence diagram 1000 may be applicable to a network that provides discontinuous network coverage (e.g., NTN) and uses NGRAN technology. The network includes a gNB 1020 (e.g., having its components implemented on a communications satellite) and an AMF 1030 (e.g., implemented as a terrestrial component). Sequence diagram 1000 includes a broadcast by gNB 1020, which may indicate whether the network is a TN or an NTN. The broadcast may be received by UE 1010. For example, the broadcast may be an SI B1 broadcast. The broadcast may also include almanac information and ephemeris information. Thus, UE 1010 may determine whether the network is a TN or an NTN and, in the case of an NTN, may predict satellite coverage (or, more generally, network coverage).

[0116] When UE 1010 is in a coverage area (e.g., network coverage is provided to the UE by gNB 1020 or another gNB implemented on a communication satellite), UE 1010 may perform various procedures, including a registration procedure. As part of the registration procedure, UE 1010 may transmit a Registration Request message to AMF 1030 via the applicable gNB. The Registration Request message may include UE capability information indicating the UE's ability to use SMS for coverage data transmission. AMF 1030 may respond with a Registration Accept message. The Registration Accept message may include coverage map information and endpoint information. The coverage map information may include updated almanac and ephemeris information. This information may also or alternatively include location information and / or timing information from the coverage map. Thus, the coverage map information includes one or more different types of information transmitted by the network (e.g., AMF 1030) to UE 1010 as part of the coverage data. Based on the coverage map information, UE 1010 may determine whether network coverage is as expected. The determination may include a prediction of where and / or when the network coverage will be (and associated access duration and / or gap duration). The endpoint information may include information about the endpoint 1040 storing the coverage map information and / or information about accessing the coverage map information from the endpoint 1040. In general, the endpoint 1040 may belong to a network and a connection to the endpoint may be established via a control plane function of the network (e.g., via an SMS function (SMSF) supporting SMS over NAS). The endpoint information may include an address of the endpoint (e.g., a network address such as a uniform resource identifier (URI) or uniform resource locator (URL)) and a token. The token may be used to verify that the UE 1010 is authorized to access the coverage map information and may be referred to herein as an authorization token.

[0117] Next, UE 1010 is out of coverage. UE 1010 may operate in a power saving mode. For example, the AS layer may be disabled to save power. The NAS layer may also abandon various network operations. The network may also abandon paging.

[0118] Thereafter, when UE 1010 is again in coverage, UE 1010 may exit power save mode. For example, the AS layer is activated and the NAS layer is notified. UE 1010 may transmit an SMS request to endpoint 1040 (e.g., via SMSF). The SMS request may be an SMS query and may include a token so that endpoint 1040 can determine that UE 1010 is authorized to receive coverage map information. Endpoint 1040 may then transmit an SMS response to UE 1010. The response may include coverage map information.

[0119] In general, SMS data transmission can be used for power-efficient, relatively infrequent transmission of small amounts of data. The target layers for using coverage data can be the AMF on the network side and the EMM / 5GMM NAS layer on the UE side. The size of the data can be limited to 160 octets, but the UE 1010 can use cascaded SMS to transmit larger amounts of data. Existing NAS security mechanisms are applicable to ensure the security of coverage data transmission. Existing UE subscriptions can be taken into account and the UE 1010 can be charged accordingly. The UE 1010 can transmit an SMS query request and the endpoint 1040 can return an SMS message with coverage map data. The UE 1010 can use a registration process to obtain authorization data (e.g., an authorization token), which can be included in the query. Alternatively or additionally, some or all of the endpoint information can be server configuration information pre-configured in the USIM of the UE 1010. For example, the USIM can store the network address and / or the authorization token. In this case, the network (e.g., AMF 1030) may transmit updated endpoint information (e.g., updated network address) or required endpoint information (e.g., authorization token, when such token is not stored in the USIM) to the UE 1010.

[0120] Figure 11 An example of a sequence diagram 1100 is illustrated in the context of transmitting coverage data stored by a network's operations and maintenance (O&M) server 1140, according to some embodiments. Sequence diagram 1100 may be applicable to networks that provide discontinuous network coverage (e.g., NTN) and utilize NG RAN technology. Generally speaking, the O&M server 1140 may receive and store coverage map information from endpoints external to the network. The stored coverage map information may then be provided to various entities of the network, such as the gNB 1120 and / or the AMF 1020.

[0121] gNB 1120 may transmit a broadcast indicating whether the network is a TN or NTN. This broadcast may be received by UE 1110. For example, this broadcast may be a SIB1 broadcast. The broadcast may also include almanac information and ephemeris information (and / or other types of information received from O&M server 1140). Thus, UE 1110 may determine whether the network is a TN or NTN and, in the case of an NTN, may predict satellite coverage (or, more generally, network coverage).

[0122] When UE 1110 is in a coverage area (e.g., network coverage is provided to the UE by gNB 1120 or another gNB implemented on a communication satellite), UE 1110 may perform various procedures, including a registration procedure. As part of the registration procedure, UE 1110 may transmit a Registration Request message to AMF 1130 via the applicable gNB. The Registration Request message may include UE capability information indicating the UE's ability to use the control plane, user plane, and / or SMS for coverage data transmission. AMF 1130 may respond with a Registration Accept message. The Registration Accept message may include coverage map information and, where applicable, endpoint information. The remaining steps of sequence diagram 1100 are similar to those of sequence diagrams 600 to 1000, depending on whether control plane data transmission, user plane data transmission, and / or SMS data transmission are used. Similar descriptions are not repeated here. Instead, these steps are equally or equivalently applicable to sequence diagram 1100.

[0123] In the context of the O&M server 1140, coverage map information is typically RAT and location-specific, not tied to a UE subscription, and is generally not UE-specific. This information can be provided directly from an external AF to the MME / AMF and may not be well-suited for all UEs, except for specific use cases where the UE knows ephemeris and / or almanac information and can retrieve the latest coverage map information. The AF can provide non-UE-specific information to the O&M server 1140 in the network. The UE can then retrieve coverage map information from both the EPS and 5GS based on UE-specific requirements.

[0124] Figure 12 An example of an operational flow / algorithm structure 1200 implemented by a UE (or its components) in the context of discontinuous network coverage according to some embodiments is illustrated. The UE is an example of any of the UEs described in this disclosure. The discontinuous network coverage may be from an NTN.

[0125] Operational flow / algorithm structure 1200 may include, at 1202, exchanging capability information indicating supported data transmission types for coverage data with a control plane function of a network, the coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network. For example, UE capability information may be communicated from the UE to the network (e.g., via its base station to its control plane function), and / or network capability information may be communicated from the network (e.g., from the control plane function via the base station) to the UE. If multiple data transmission types are supported, a selection may be made by the UE and / or the network to use the supported type. In an exemplary use case, a component of the UE includes processing circuitry configured to cause the capability information exchange with the control plane function of the network.

[0126] The operational flow / algorithm structure 1200 may include receiving coverage data using a supported data transmission type at 1204. For example, the supported type may be any of a control plane transmission, a user plane transmission, an SMS transmission, or a transmission originating from an O&M server of the network. In the case of a control plane or O&M server-originated transmission, the coverage data may correspond to coverage map information received from an MME or AMF (or another control plane function thereof) of the network, such as Figures 6 to 8 and Figure 11 In the case of user plane or SMS transmission, the coverage data may correspond to coverage map information received from an endpoint external to the network, such as Figures 9 and 10 In the exemplary use case, the processing circuit is further configured to process the overlay data by using the supported data transfer type.

[0127] The operational flow / algorithm structure 1200 may include, at 1206, communicating with an NTN node based on the coverage data. For example, the UE (e.g., processing circuitry) determines whether the UE is within the coverage area of ​​an NTN node (e.g., a non-terrestrial base station of the network) based on the received coverage data. When within the coverage area, the UE activates its AS layer. When outside the coverage area, the UE enters a power saving mode. In the exemplary use case, the processing circuitry is further configured to enable communication with the NTN node based on the coverage data.

[0128] Figure 13 An example of an operational flow / algorithm structure 1300 implemented by a base station in the context of discontinuous network coverage according to some embodiments is illustrated. The base station is an example of any base station described in this disclosure. The discontinuous network coverage may be from an NTN.

[0129] Operational flow / algorithm structure 1300 may include, at 1302, exchanging capability information, by a control plane function of a network, with a user equipment (UE), the capability information indicating supported data transmission types for coverage data, the coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network. For example, the UE capability information may be communicated from the UE to the network (e.g., via its base station to its control plane function), and / or the network capability information may be communicated from the network (e.g., via the base station from the control plane function to the UE). If multiple data transmission types are supported, the UE and / or the network may select to use the supported type.

[0130] The operational flow / algorithm structure 1300 may include, at 1304, causing coverage data to be transmitted to the UE based on the supported data transmission type, wherein communication between the UE and the NTN node is facilitated based on the coverage data. For example, the supported type may be any of control plane transmission, user plane transmission, SMS transmission, or transmission originating from an O&M server of the network. In the case of control plane or O&M server-originated transmission, the coverage data may correspond to coverage map information received from an MME or AMF (or another control plane function thereof) of the network, such as Figures 6 to 8 and Figure 11 In the case of user plane or SMS transmission, the coverage data may correspond to coverage map information received from an endpoint external to the network, such as Figures 9 and 10 Based on the received coverage data, the UE determines whether it is in the coverage area of ​​an NTN node (e.g., a non-terrestrial base station of the network). When in the coverage area, the UE activates its AS layer. When out of the coverage area, the UE enters a power saving mode.

[0131] Figure 14 14 illustrates a receiving component 1400 of a UE 104 according to some embodiments. A device, such as that described in any of the above figures, may include a similar receiving component. The receiving component 1400 may include an antenna panel 1404 that includes a plurality of antenna elements. The panel 1404 is shown as having four antenna elements, but other embodiments may include other numbers of antenna elements.

[0132] The antenna panel 1404 may be coupled to an analog beamforming (BF) assembly including a plurality of phase shifters 1408(1) to 1408(4). The phase shifters 1408(1) to 1408(4) may be coupled to a radio frequency (RF) chain 1412. The RF chain 1412 may amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal into a digital baseband signal that may be provided to a baseband processor for further processing.

[0133] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights (e.g., W1 to W4) to phase shifters 1408(1) to 1408(4) to provide receive beams at antenna panel 1404. These BF weights may represent phase shift values. These BF weights may be determined based on channel-based beamforming.

[0134] Figure 15 UE 1500 according to some embodiments is illustrated. UE 1500 may be similar to Figure 1UE 104 is, and is substantially interchangeable therewith. A device such as that described in any of the above figures may include similar components, including, for example, a processor, memory, and RF interface circuitry.

[0135] Similar to what is described above with respect to UE 104, UE 1500 may be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device, or a loose IoT device. In some embodiments, the UE may be a reduced-capacity UE or an NR-Light UE.

[0136] UE 1500 may include a processor 1504, an RF interface circuit 1508, a memory / storage 1512, a user interface 1516, a sensor 1520, a driver circuit 1522, a power management integrated circuit (PMIC) 1524, and a battery 1528. The components of UE 1500 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 15 The block diagram is intended to show a simplified view of some of the components of UE 1500. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0137] Components of UE 1500 may be coupled to various other components via one or more interconnects 1532, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0138] The processor 1504 may include processor circuits such as a baseband processor circuit (BB) 1504A, a central processor unit circuit (CPU) 1504B, and a graphics processor unit circuit (GPU) 1504C. The processor 1504 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from the memory / storage device 1512) to cause the UE 1500 to perform operations as described herein.

[0139] In some embodiments, the baseband processor circuit 1504A can access the communication protocol stack 1536 in the memory / storage device 1512 to communicate over a 3GPP-compatible network. Generally speaking, the baseband processor circuit 1504A can access the communication protocol stack to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access stratum (NAS) layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuit 1508.

[0140] The baseband processor circuit 1504A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0141] The baseband processor circuit 1504A may also access group information from the memory / storage 1512 to determine search space groups in which multiple repetitions of the PDCCH may be sent.

[0142] The memory / storage 1512 may include any type of volatile memory or non-volatile memory that may be distributed throughout the UE 1500. In some embodiments, some of the memory / storage 1512 may be located on the processor 1504 itself (e.g., L1 cache and L2 cache), while other memory / storage 1512 may be external to the processor 1504 but accessible via a memory interface. The memory / storage 1512 may include any suitable volatile memory or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0143] The RF interface circuit 1508 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1500 to communicate with other devices via a radio access network. The RF interface circuit 1508 may include various components arranged in a transmit path or a receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, and the like.

[0144] In the receive path, the RFEM receives the radiated signal from the air interface via antenna 1550 and further filters and amplifies the signal (using a low-noise amplifier). The signal can be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of processor 1504.

[0145] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before radiating the signal across the air interface via the antenna 1550.

[0146] In various embodiments, the RF interface circuit 1508 may be configured to send / receive signals in a manner compatible with NR access technology.

[0147] Antenna 1550 may include multiple antenna elements, each of which converts electrical signals into radio waves to pass through the air and converts received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1550 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communications. Antenna 1550 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, and the like. Antenna 1550 may have one or more panels designed for specific frequency bands, including those in FR1 or FR2.

[0148] User interface circuitry 1516 includes various input / output (I / O) devices designed to enable a user to interact with UE 1500. User interface 1516 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a trackpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual components for displaying or otherwise conveying information, such as sensor readings, actuator positioning, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary status indicators (such as light-emitting diodes (LEDs)) and multi-character visual outputs) or more complex outputs (such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of UE 1500.

[0149] Sensors 1520 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and to communicate information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including three-axis accelerometers, three-axis gyroscopes, or magnetometers; fluid level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravity meters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and the like.

[0150] The driver circuitry 1522 may include software and hardware components that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1500. The driver circuitry 1522 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1500. For example, the driver circuitry 1522 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface, a sensor driver for obtaining sensor readings from the sensor circuitry 1520 and controlling and enabling access to the sensor circuitry 1520, a driver for obtaining actuator positioning of an electromechanical component or controlling and enabling access to an electromechanical component, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0151] The PMIC 1524 may manage the power provided to various components of the UE 1500. Specifically, with respect to the processor 1504, the PMIC 1524 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0152] In some embodiments, the PMIC 1524 may control or otherwise be part of various power-saving mechanisms for the UE 1500. For example, if a platform UE is in the RRC_Connected state, in which it remains connected to a RAN node because it expects to receive traffic soon, after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1500 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period, the UE 1500 may transition to the RRC_Idle state, in which the UE is disconnected from the network and does not perform operations such as channel quality feedback or handovers. The UE 1500 enters a very low-power state and wakes up to listen for paging from the network, and then powers down again. The UE 1500 may not receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. Additional power-saving modes may prevent the device from using the network for periods exceeding the paging interval (from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down or have its RF activity completely shut down. Any data transmitted during this time will incur significant latency, assuming that latency is acceptable.

[0153] Battery 1528 can power UE 1500, but in some examples, UE 1500 can be installed and deployed in a fixed location and can have a power source coupled to the power grid. Battery 1528 can be a lithium-ion battery, a metal-air battery (such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc.). In some specific implementations, such as in vehicle-based applications, battery 1528 can be a typical lead-acid automobile battery.

[0154] Figure 14 The gNB 1600 according to some embodiments is illustrated. The gNB 1600 may be similar to Figure 1 The gNB 108 is similar to and essentially interchangeable with it.

[0155] gNB 1600 may include a processor 1604, RAN interface circuitry 1608, core network (CN) interface circuitry 1612, and / or memory / storage device circuitry 1616.

[0156] The components of gNB 1600 may be coupled with various other components via one or more interconnects 1628.

[0157] The processor 1604, RAN interface circuit 1608, memory / storage circuit 1616 (including communication protocol stack 1610), antenna 1650 and interconnect 1628 may be used with respect to Figure 15Like-named elements are shown and described similarly.

[0158] The CN interface circuitry 1612 can provide connectivity to a core network (e.g., a 5GC using a fifth-generation core network (5GC)-compatible network interface protocol, such as a Carrier Ethernet protocol, or some other suitable protocol). Network connectivity can be provided to / from the gNB 1600 via optical fiber or wireless backhaul. The CN interface circuitry 1612 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1612 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

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

[0160] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below in the Examples section.

[0161] Example

[0162] In the following sections, additional exemplary embodiments are provided.

[0163] Embodiment 1 includes a method implemented by a user equipment (UE), the method comprising: exchanging capability information indicating supported data transmission types for coverage data with a control plane function of a network, the coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network; receiving the coverage data by using the supported data transmission types; and communicating with the NTN node based on the coverage data. In an exemplary use case, the method is implemented by a component of the UE, such as a processor of the UE (e.g., processor 1504), wherein the component includes processing circuitry and interface circuitry coupled to the processing circuitry, the interface circuitry being configured to communicatively couple the processing circuitry with another component of the apparatus. In this case, the processing circuitry is configured to cause an exchange of capability information indicating supported data transmission types for coverage data with a control plane function of the network, the coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network; processing the coverage data by using the supported data transmission types; and causing communication with the NTN node based on the coverage data. Accordingly, the method in the illustrative use case includes: causing an exchange of capability information with a control plane function of a network, the capability information indicating supported data transmission types for coverage data, the coverage data indicating at least one of location or timing of network coverage performed by a non-terrestrial network (NTN) node of the network; processing the coverage data by using the supported data transmission types; and causing communication with the NTN node based on the coverage data.

[0164] Embodiment 2 includes a method according to embodiment 1, wherein exchanging the capability information includes transmitting the capability information to the control plane function, wherein the capability information indicates one or more data transmission types supported by the UE, and wherein the method further includes: receiving selection information from the control plane function, wherein the selection information indicates a selection of a supported data transmission type from the one or more data transmission types.

[0165] Embodiment 3 includes a method according to embodiment 1, wherein exchanging the capability information includes receiving the capability information from the control plane function, wherein the capability information indicates one or more data transmission types supported by the network, and wherein the method further includes: selecting a supported data transmission type from the one or more data transmission types.

[0166] Embodiment 4 includes the method according to any preceding embodiment, wherein the capability information indicates that the UE supports at least one of a control plane or a user plane to receive the coverage data from the network.

[0167] Embodiment 5 includes the method according to any preceding embodiment, wherein the capability information indicates that the network supports at least one of a control plane or a user plane to transmit the coverage data to the UE.

[0168] Embodiment 6 includes the method of any preceding embodiment, wherein the supported data transmission type corresponds to a control plane, and wherein the coverage data is received from the control plane function using at least the control plane.

[0169] Embodiment 7 includes the method of embodiment 6, wherein the control plane function comprises a mobility management entity or an access and mobility management function.

[0170] Embodiment 8 includes the method of embodiment 6, wherein the coverage data is received via a non-access stratum (NAS) layer of the UE.

[0171] Embodiment 9 includes the method of embodiment 8, wherein the overlay data is received in multiple portions based on a control plane protocol other than a NAS protocol.

[0172] Embodiment 10 includes the method of embodiment 6, wherein the overlay data is transmitted using a non-IP based mechanism.

[0173] Embodiment 11 includes the method of embodiment 6, wherein the capability information is transmitted in a registration request message, and wherein the coverage data is received in a registration accept message.

[0174] Embodiment 12 includes the method of embodiment 6, wherein the coverage data is received in a configuration update command message.

[0175] Embodiment 13 includes the method of embodiment 6, wherein the coverage data is received in a message associated with a container type for transmitting NTN node network coverage.

[0176] Embodiment 14 includes the method of embodiment 13, wherein the message comprises a downlink NAS transfer message received based on an uplink NAS transfer message transmitted from the UE.

[0177] Embodiment 15 includes a method according to embodiment 13, wherein the message includes a command message indicating a process transaction identifier, a first message identifier, and a container type, and wherein the method further comprises: transmitting a completion message indicating the process transaction identifier and the second message identifier to the control plane function.

[0178] Embodiment 16 includes the method of embodiment 6, wherein the coverage data is received in an attach accept message or a tracking area update accept message.

[0179] Embodiment 17 includes the method of embodiment 1, wherein the supported data transmission type corresponds to a user plane, and wherein the coverage data is received from the endpoint using at least the user plane.

[0180] Embodiment 18 includes the method of embodiment 17, further comprising: receiving an address and a token of the endpoint from the control plane function; and transmitting a request for the overlay data and the token to the endpoint based on the address.

[0181] Embodiment 19 includes the method of embodiment 17, further comprising: determining configuration information of the endpoint from a universal subscriber identity module; and transmitting the request for the overlay data based on the configuration information.

[0182] Embodiment 20 includes the method of embodiment 1, wherein the supported data transmission type corresponds to Short Message Service (SMS), and wherein the coverage data is received from the endpoint in an SMS response or a cascaded SMS response.

[0183] Embodiment 21 includes the method of embodiment 20, further comprising: receiving an address and a token of the endpoint from the control plane function; and transmitting an SMS query for the coverage data and the token to the endpoint based on the address.

[0184] Embodiment 22 includes the method of embodiment 1, wherein the coverage data is received from the control plane function based on transmission of the coverage data from an operations and maintenance server of the network to the control plane function.

[0185] Embodiment 23 is a method implemented by a network, the method comprising: exchanging capability information, by a control plane function of the network, with a user equipment (UE), the capability information indicating a supported data transmission type for coverage data, the coverage data indicating at least one of a location or timing of network coverage performed by a non-terrestrial network (NTN) node of the network; and causing the coverage data to be transmitted to the UE based on the supported data transmission type, wherein communication between the UE and the NTN node is facilitated based on the coverage data.

[0186] Embodiment 24 includes the method of embodiment 23, wherein the supported data transmission type corresponds to a control plane, and wherein the overlay data is transmitted by the control plane function using at least the control plane or a non-IP based delivery mechanism.

[0187] Embodiment 25 includes the method of embodiment 23, wherein the supported data transmission type corresponds to a user plane, and wherein the method further comprises transmitting, by the control plane function, an address and a token of an endpoint to the UE, the endpoint storing the coverage data.

[0188] Embodiment 26 includes a method according to embodiment 23, wherein the supported data transmission type corresponds to short message service (SMS), and wherein the method further comprises: transmitting, by the control plane function, an address and a token of an endpoint to the UE, wherein the endpoint stores the coverage data.

[0189] Embodiment 27 includes the method of embodiment 23, wherein the transmission of the coverage data by the control plane function is based on transmission of the coverage data from an operation and maintenance server of the network to the control plane function.

[0190] Embodiment 28 includes the method of embodiment 23, wherein the coverage data is transmitted in a system information block (SIB) broadcast.

[0191] Embodiment 29 includes an apparatus comprising means for performing one or more elements of the method as described in or in connection with any one of embodiments 1 to 28.

[0192] Embodiment 30 includes one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of a device, cause the device to perform one or more elements of a method described in or related to any one of embodiments 1 to 28.

[0193] Embodiment 31 includes an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method as described or related to any one of embodiments 1-28.

[0194] Embodiment 32 includes a device comprising one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any one of embodiments 1 to 28.

[0195] Embodiment 33 includes a system comprising means for performing one or more elements of the method described in or related to any one of Embodiments 1 to 28.

[0196] Embodiment 34 includes a network comprising means for performing one or more elements of the method described in or related to any one of embodiments 1 to 28.

[0197] Embodiment 35 includes one or more non-transitory computer-readable media, wherein the one or more non-transitory computer-readable media include instructions that, when executed by one or more processors of a network, cause the network to perform one or more elements of a method described in or related to any one of embodiments 1 to 28.

[0198] Embodiment 36 includes a network comprising logic components, modules, or circuits for executing one or more elements of the method described in or related to any one of embodiments 1 to 28.

[0199] Embodiment 37 includes a network comprising one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of a method described in or related to any one of embodiments 1 to 28.

[0200] Embodiment 38 includes a component to be implemented in an apparatus (wherein the apparatus may be any of the apparatuses described above, such as a UE, a network, or a network node), the component comprising: a processing circuit configured to execute one or more elements of a method described or related to any one of embodiments 1 to 28; and an interface circuit coupled to the processing circuit, the interface circuit configured to communicatively couple the processing circuit with another component of the apparatus.

[0201] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0202] Unless expressly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0203] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method implemented by a user equipment (UE), the method comprising: causing an exchange of capabilities information with a control plane function of a network, the capabilities information indicating supported data transmission types for coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network; processing the overlay data using a supported data transfer type; and Communication with the NTN node is enabled based on the coverage data.

2. The method of claim 1 , wherein causing the exchange to occur comprises causing the capability information to be communicated to the control plane function, wherein the capability information indicates one or more data transmission types supported by the UE, and wherein the method further comprises: Selection information is processed, the selection information being received from the control plane function and indicating selection of a supported data transmission type from among the one or more data transmission types.

3. The method of claim 1 , wherein causing the exchange to occur comprises causing the capability information to be received from the control plane function, wherein the capability information indicates one or more data transmission types supported by the network, and wherein the method further comprises: A supported data transmission type is selected from the one or more data transmission types. 4 . The method according to claim 1 , wherein the capability information indicates that the UE supports at least one of a control plane or a user plane to receive the coverage data from the network. 5 . The method according to claim 1 , wherein the capability information indicates that the network supports at least one of a control plane or a user plane to transmit the coverage data to the UE.

6. The method of claim 1, wherein the supported data transmission type corresponds to a control plane, and wherein the coverage data is received from the control plane function using at least the control plane.

7. The method of claim 6, wherein the control plane function comprises a mobility management entity or an access and mobility management function.

8. The method of claim 6, wherein the coverage data is received via a non-access stratum (NAS) layer of the UE.

9. The method of claim 8, wherein the overlay data is received in multiple parts based on a control plane protocol other than a NAS protocol.

10. The method of claim 6, wherein the overlay data is transmitted using a non-IP based mechanism.

11. The method of claim 6, wherein the capability information is transmitted in a registration request message, and wherein the coverage data is received in a registration accept message.

12. The method of claim 6, wherein the coverage data is received in a configuration update command message.

13. The method of claim 6, wherein the coverage data is received in a message associated with a container type for transmitting NTN node network coverage.

14. The method of claim 13, wherein the message comprises a downlink NAS transfer message received based on an uplink NAS transfer message transmitted from the UE.

15. The method of claim 13, wherein the message comprises a command message indicating a process transaction identifier, a first message identifier, and the container type, and wherein the method further comprises: A completion message is caused to be transmitted to the control plane function, the completion message indicating the process transaction identifier and the second message identifier.

16. The method of claim 6, wherein the coverage data is received in an Attach Accept message or a Tracking Area Update Accept message.

17. A component to be implemented in a device, the component comprising: a processing circuit, the processing circuit being configured to: causing an exchange of capabilities information with a control plane function of a network, the capabilities information indicating supported data transmission types for coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network; processing the overlay data by using a supported data transfer type; as well as enabling communication with the NTN node based on the coverage data; as well as An interface circuit is coupled to the processing circuit, the interface circuit being configured to communicatively couple the processing circuit with another component of the apparatus.

18. The component of claim 17, wherein the supported data transmission type corresponds to a user plane, and wherein the coverage data is received from the endpoint using at least the user plane.

19. The assembly of claim 18, wherein the processing circuit is further configured to: processing the endpoint's address and token received from the control plane function; and Based on the address, a request for the overlay data and the token is caused to be transmitted to the endpoint.

20. The assembly of claim 18, wherein the processing circuit is further configured to: determining configuration information for the endpoint from a universal subscriber identity module; and Based on the configuration information, a request for the overlay data is caused to be transmitted.

21. The component of claim 17, wherein the supported data transmission type corresponds to Short Message Service (SMS), and wherein the coverage data is received from the endpoint in an SMS response or a cascaded SMS response.

22. The assembly of claim 21 , wherein the processing circuit is further configured to: processing the endpoint's address and token received from the control plane function; and Based on the address, an SMS query for the coverage data and the token is caused to be transmitted to the endpoint.

23. The assembly of claim 17, wherein the coverage data is received from the control plane function based on transmission of the coverage data from an operations and maintenance server of the network to the control plane function.

24. A network, comprising: one or more processors; as well as one or more memories storing instructions that, when executed by the one or more processors, configure the network to: exchanging, by a control plane function of the network with a user equipment (UE), capability information indicating supported data transmission types for coverage data, the coverage data indicating at least one of location or timing of network coverage by a non-terrestrial network (NTN) node of the network; as well as The coverage data is caused to be transmitted to the UE based on the supported data transmission type, wherein communication between the UE and the NTN node is facilitated based on the coverage data.

25. The network of claim 24, wherein the supported data transmission type corresponds to a control plane, and wherein the overlay data is transmitted by the control plane function using at least the control plane or a non-IP based delivery mechanism.

26. The network of claim 24, wherein the supported data transmission type corresponds to a user plane, and wherein the one or more memories store further instructions that, when executed by the one or more processors, configure the network to: The control plane function transmits an endpoint address and a token to the UE, and the endpoint stores the coverage data.

27. The network of claim 24, wherein the supported data transmission type corresponds to Short Message Service (SMS), and wherein the one or more memories store further instructions that, when executed by the one or more processors, configure the network to: The control plane function transmits an endpoint address and a token to the UE, and the endpoint stores the coverage data.

28. The network of claim 24, wherein the coverage data is communicated by the control plane function based on transmission of the coverage data from an operations and maintenance server of the network to the control plane function.

29. The network of claim 24, wherein the coverage data is transmitted in a system information block (SIB) broadcast.

Images