Registering pending status

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may send a registration request message. The UE may receive a registration pending message. The UE may enter a registration pending state. The UE may transmit a registration resume message based at least in part on one or more parameters associated with the registration pending message. The UE may receive a registration accept message or a registration reject message. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek patent application No. 20220100437, filed on May 25, 2022, entitled "REGISTRATION PENDING STATE" and assigned to the assignee of this application. The disclosure of the prior application is considered part of this patent application and is incorporated into this patent application by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for user equipment registration using a registration pending state in a non-terrestrial network. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include sending a registration request message. The method may include receiving a registration pending message. The method may include entering a registration pending state. The method may include sending a registration resume message based at least in part on one or more parameters associated with the registration pending message. The method may include receiving a registration accept message or a registration reject message.

[0008] Some aspects described herein relate to a method of wireless communication performed by a non-terrestrial network (NTN) entity. The method may include receiving a registration request message from a UE. The method may include sending a registration pending message. The method may include performing an authentication procedure of the UE to a terrestrial network entity. The method may include receiving a registration resume message from the UE. The method may include sending a registration accept message or a registration reject message based at least in part on whether the UE is authenticated.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a registration request message and receive a registration pending message. The one or more processors may be configured to enter a registration pending state. The one or more processors may be configured to send a registration recovery message based at least in part on one or more parameters associated with the registration pending message. The one or more processors may be configured to receive a registration acceptance message or a registration rejection message.

[0010] Some aspects described herein relate to an NTN entity for wireless communication. The NTN entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a registration request message from a UE. The one or more processors may be configured to send a registration pending message. The one or more processors may be configured to perform an authentication procedure of the UE to a ground network entity. The one or more processors may be configured to receive a registration recovery message from the UE. The one or more processors may be configured to send a registration acceptance message or a registration rejection message based at least in part on whether the UE is authenticated.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication performed by a UE. When the instruction set is executed by one or more processors of the UE, the UE may send a registration request message. When the instruction set is executed by one or more processors of the UE, the UE may receive a registration pending message. When the instruction set is executed by one or more processors of the UE, the UE may enter a registration pending state. When the instruction set is executed by one or more processors of the UE, the UE may send a registration recovery message based at least in part on one or more parameters associated with the registration pending message. When the instruction set is executed by one or more processors of the UE, the UE may receive a registration acceptance message or a registration rejection message.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by an NTN entity. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to receive a registration request message from a UE. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to send a registration pending message. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to perform an authentication procedure of the UE to a ground network entity. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to receive a registration recovery message from the UE. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to send a registration acceptance message or a registration rejection message based at least in part on whether the UE is authenticated.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a registration request message. The apparatus may include means for receiving a registration pending message. The apparatus may include means for entering a registration pending state. The apparatus may include means for sending a registration resume message based at least in part on one or more parameters associated with the registration pending message. The apparatus may include means for receiving a registration accept message or a registration reject message.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a registration request message from another apparatus. The apparatus may include means for sending a registration pending message. The apparatus may include means for performing an authentication procedure of the other apparatus to a ground network entity. The apparatus may include means for receiving a registration resume message from the other apparatus. The apparatus may include means for sending a registration accept message or a registration reject message based at least in part on whether the other apparatus is authenticated.

[0015] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of regenerative satellite deployment and an example of transparent satellite deployment in a non-terrestrial network (NTN) according to the present disclosure.

[0023] Figure 5A and Figure 5B is a diagram illustrating an example of an existing registration procedure according to the present disclosure.

[0024] Fig. 6A and Figure 6B is a diagram illustrating an example of using a registration pending state according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, by an NTN entity according to the present disclosure.

[0027] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] The various aspects of the disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure listed herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terminology often associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and beyond (e.g., 6G) RATs.

[0031] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0032] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0033] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0034] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with base station 110. In some aspects, the term "base station" or "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0036] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for the network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link.

[0038] In some aspects, as shown, the cell may be provided by a network entity (e.g., base station 110) of a non-terrestrial network (NTN). As used herein, a "non-terrestrial network" may refer to a network to which a non-terrestrial base station (such as a base station carried by a satellite, balloon, airship, aircraft, unmanned aerial vehicle, and / or a high-altitude platform station) provides access. A network entity in an NTN (NTN network entity) may use polarization. For example, a network entity in a satellite 135 (NTN network entity) may use circular polarization 136 or linear polarization 138 to send a communication to a UE 120. Circular polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space moves around a circle, and the electromagnetic wave may be formed by superimposing two orthogonal linearly polarized waves of equal amplitude and a phase difference of 90 degrees. Circular polarization may be right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). Linear polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space oscillates along a straight line over time.

[0039] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0040] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network entity, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0041] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0043] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is expected that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may send a registration request message and receive a registration pending message. Communications manager 140 may enter a registration pending state. Communications manager 140 may send a registration resume message based at least in part on one or more parameters associated with the registration pending message, and receive a registration accept message or a registration reject message. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0047] In some aspects, the NTN network entity (e.g., base station 110, network entity, satellite 135) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a registration request message from the UE and send a registration pending message. The communication manager 150 may perform an authentication procedure of the UE to the ground network entity. The communication manager 150 may receive a registration resume message from the UE and send a registration accept message or a registration reject message based at least in part on whether the UE is authenticated. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0049] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0050] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t). Base station 110 may be an NTN network entity located in a terrestrial location or a non-terrestrial location (eg, satellite 135).

[0051] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0054] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 10 )Aspects of any of the methods described herein.

[0055] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 10 )Aspects of any of the methods described herein.

[0056] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of may perform one or more techniques associated with using a registration pending state in an NTN. In some aspects, the NTN entity is a network entity at the surface or at a satellite (e.g., 135). For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process of 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network entities and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of the network entity and / or UE 120, may cause one or more processors, UE 120, and / or the network entity to perform or direct, for example, Figure 7 The process of 700 Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0057] In some aspects, the UE 120 includes: a means for sending a registration request message; a means for receiving a registration pending message; a means for entering a registration pending state; a means for sending a registration resume message based at least in part on one or more parameters associated with the registration pending message; and / or a means for receiving a registration accept message or a registration reject message. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0058] In some aspects, the NTN entity (e.g., base station 110, network entity, satellite 135) includes: a component for receiving a registration request message from a UE; a component for sending a registration pending message; a component for performing an authentication procedure of the UE to the ground network entity; a component for receiving a registration recovery message from the UE; and / or a component for sending a registration acceptance message or a registration rejection message based at least in part on whether the UE is authenticated. In some aspects, the components for the NTN entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0059] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0061] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0062] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0063] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0065] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RTRIC 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may be generally referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. DU 330 and RU 340 may also be referred to as “O-RAN DU (O-DU)” and “O-RAN RU (O-RU)”, respectively. A network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may also include one or more of the following: a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0066] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, a unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

[0067] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0068] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0069] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0070] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0071] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0074] Figure 4 is a diagram illustrating an example 400 of a regenerative satellite deployment and an example 410 of a transparent satellite deployment in an NTN according to the present disclosure.

[0075] Example 400 illustrates a regenerative satellite deployment. In example 400, UE 120 is served by satellite 420 (e.g., satellite 135) via service link 430. For example, satellite 420 may include a network entity (e.g., base station 110, BS110a, gNB). In some aspects, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, an onboard processing repeater, and / or an NTN entity. In some aspects, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to produce downlink radio frequency transmissions. Satellite 420 may transmit downlink radio frequency signals on service link 430. Satellite 420 may provide a cell covering UE 120.

[0076] Example 410 shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In example 410, UE 120 is served by satellite 440 via service link 430. Satellite 440 may also be considered an NTN entity. Satellite 440 may be a transparent satellite. Satellite 440 may relay signals received from gateway 450 via feeder link 460. For example, a satellite may receive an uplink radio frequency transmission, and may transmit a downlink radio frequency transmission without demodulating the uplink radio frequency transmission. In some aspects, a satellite may convert the uplink radio frequency transmission frequency received on service link 430 to the frequency of the uplink radio frequency transmission on feeder link 460, and may amplify and / or filter the uplink radio frequency transmission. In some aspects, the UE 120 shown in examples 400 and 410 may be associated with a global navigation satellite system (GNSS) capability, a global positioning system (GPS) capability, etc., but not all UEs have such capabilities. Satellite 440 may provide a cell covering UE 120.

[0077] The service link 430 may include a link between the satellite 440 and the UE 120, and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 440 and the gateway 450, and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0078] Due to the movement of satellites 420 and 440 and the potential movement of UE 120, feeder link 460 and service link 430 may each experience Doppler effects. These Doppler effects may be significantly greater than the Doppler effects in the ground network. The Doppler effect on feeder link 460 can be compensated to a certain extent, but may still be associated with a certain amount of uncompensated frequency error. In addition, gateway 450 may be associated with residual frequency error, and / or satellite 420 / 440 may be associated with onboard frequency error. These frequency error sources may cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.

[0079] Satellites 420 and 440 may be satellites in a geostationary orbit (GSO) or a geosynchronous equatorial orbit (GEO), which may be located, for example, 36,000 kilometers (km) above the earth. The satellite has a negligible speed relative to the earth, but has a propagation delay of greater than 500 ms compared to a propagation delay of 25 milliseconds (ms) for a low earth orbit (LEO) satellite 600 km above the earth. In NTNs where the distance between the UE 120 and the satellite may be greater than 600 km, path loss changes may not be properly reflected in propagation delay variations. It is expected that the UE 120 can autonomously pre-compensate for propagation delays up to a reference point, and thus timing advance (TA) verification may be performed more directly, rather than relying on indirect parameters such as RSRP. Due to the propagation delay, the UE 120 may use the TA for timing alignment of the communication. The TA may inform the UE 120 to send the communication TA amount earlier than scheduled. In the case where the propagation distance between the UE 120 and the network entity changes, the TA may need to be verified. Furthermore, the satellite may not always be available to the UE 120 in the case where the satellite is in a non-geostationary orbit (NGSO).

[0080] Some satellite operators may deploy satellite access with intentional coverage gaps or discontinuous coverage (DC). DC may involve LEO satellites, IoT networks, or satellite constellations that do not always cover a specific location on the earth. Some services may be delay tolerant and can use DC. Such services may include services for IoT devices and networks, services for utility meters, or services using sensors. DC can be used to address service availability and power consumption. In addition to DC, the feeder link 460 may have an intermittent connection to a ground station (such as gateway 450). Due to deployment design and / or cost, there may be some areas where it is not feasible to deploy ground stations.

[0081] Example 470 shows how the NTN network may experience unavailability of the feeder link 460 (FL) in addition to coverage gaps between successive overflights over ground stations. For example, cell sizes may range from 100 km to 1000 km, and the overflight time of a stationed UE may be 30 seconds to 5 minutes. Thus, a coverage gap may be 2 hours to 15 hours. However, when coverage is available, the feeder link 460 may be unavailable. Although the NTN may know the unavailability schedule of the feeder link 460, the UE 120 and the NTN may not know the coverage gap schedule.

[0082] In order to handle the unavailability of the feeder link 460, the satellite transmitter may include a network element at the satellite 420 / 440. Both the radio network and the core network aspects may be installed on the satellite 420 / 440. In one scenario, the entire control plane and user plane path may be installed on the satellite 420 / 440. For example, the control plane management entity (e.g., the mobile management entity (MME) in 4G or the access and mobility management function (AMF) and session management function (SMF) in NR) and the user plane path (e.g., the service gateway (GW) and the packet data network GW for 4G or the user plane function in NR) may be installed on the satellite 420 / 440. In this scenario, the ground station (e.g., the gateway 450) may include a home subscriber service (HSS), which includes subscription management, user authentication and authorization. In addition, in this scenario, some parts of the control plane path may be at the ground station (e.g., coordination between control plane management entities in different satellites, buffering of user data and control plane data when FL is unavailable). In this scenario, there may also be user data plane and control plane data buffering at the satellite due to DC. Finally, the Internet connection for the data plane may be at the ground station. Other functional splits between the satellite transmitter and the ground station may be employed.

[0083] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0084] Figure 5A is a diagram illustrating an example 500 of an existing registration procedure according to the present disclosure. Figure 5A As shown, NTN entity 510 (eg, base station 110, network entity, satellite 420, satellite 440) and UE 520 (eg, UE 120) may communicate with each other. UE 520 and ground network entity (eg, ground station 530) may communicate via NTN entity 510.

[0085] Figure 5AThe example 500 in FIG. 5 shows that a UE 520 may successfully or unsuccessfully register with an NTN network. The UE 520 may initiate a registration procedure with the NTN during a flyover. The registration procedure may include an attachment procedure to attach the UE 520 to the NTN network. In some signaling protocol implementations, registration may be referred to as "attachment".

[0086] As shown by reference numeral 535, UE 520 may send a registration request message. This may start a timer (e.g., T3410). In a successful scenario, NTN entity 510 may send a registration accept message, as shown by reference numeral 540. This may stop the timer. As shown by reference numeral 545, UE 520 may send a registration completion message.

[0087] Figure 5B The registration state and registration message of the existing registration procedure are shown. For example, the UE 520 may be in the deregistered state and send a registration message, such as a registration request. Registration is initiated. In the case of successful registration, the UE 520 may receive a registration acceptance message and enter the registered state. In the case of unsuccessful registration, the UE 520 may receive a registration rejection message and remain in the deregistered state.

[0088] Depending on the functional split between the NTN entity 510 and the ground station 530, the NTN entity 510 may need to contact the ground station 530 to complete the registration procedure or other procedures. The authentication procedure may include a handshake with the HSS at the ground station 530 to authenticate or authorize the user of the UE 520. However, the feeder link 460 may not be available at this time, and the registration request will be rejected because the NTN entity 510 cannot complete the authentication procedure to the ground station 530. Therefore, the NTN entity 510 may send a registration rejection message, as shown by reference numeral 550. When the feeder link 460 is available, the UE 520 will have to try to register again. In some scenarios, the NTN entity 510 may operate on the first registration request and prepare the necessary information (e.g., an authentication vector from the HSS) for the time when the feeder link 460 becomes available and the UE 520 retries the registration (during a subsequent overflight). As a result, in the case of retrying the authentication procedure, the authentication procedure can be completed even if the feeder link 460 is not available during the second overflight.

[0089] The current solution to solve the feeder link and coverage problems during UE registration is suboptimal, increases latency, and requires additional processing resources and signaling resources. For example, the rejection of UE 520 includes a complete reset of the registration procedure of UE 520, and UE 520 does not receive information about the rejection reason. In the next overflight period, UE 520 must start from scratch and provide all the same registration information in another registration request. The user of UE 520 is not provided with information about what is happening with the failed registration and about any new registration attempt. UE 520 does not have any additional information to help UE 520 determine when to retry registration. The rejection of UE 520 also involves the reset of the registration procedure of NTN entity 510. Although NTN entity 510 can perform some operations to help UE 520 succeed in the next attempt, UE 520 maintains its deregistered state. When UE 520 is in the deregistered state, incoming connection requests for UE 520 are rejected. This increases latency and wastes processing resources and signaling resources for other devices.

[0090] As indicated above, Figure 5A and Figure 5B are provided as examples. Other examples can be found in the Figure 5A and Figure 5B Different from what is described.

[0091] Fig. 6A is a diagram illustrating an example 600 of using a registration pending state according to the present disclosure.

[0092] According to various aspects described herein, in the presence of a coverage gap (between flights) and / or the feeder link 460 is unavailable, the UE 520 may enter a registration pending state that gives the NTN entity 510 an opportunity to wait for authentication by the NTN entity 510. In this way, a complete reset of the registration procedure is prevented, which reduces latency and saves processing and signaling resources of the UE 520 and other devices.

[0093] As shown by reference numeral 605, UE 520 may send a registration request message. This may be part of the first flyby of NTN entity 510. As shown by reference numeral 610, NTN entity 510 may send a registration pending message. In the case where feeder link 460 is unavailable, NTN entity 510 may send a registration pending message. As shown by reference numeral 615, UE 520 may enter a registration pending state in response to receiving the registration pending message. UE 520 may indicate the registration pending state to a user of UE 520 (e.g., via a display on a display screen of UE 520) and / or to other devices requesting a connection. When UE 520 is in the registration pending state, a connection request initiated by a user or application may be rejected locally in UE 520 without initiating a signaling procedure to NTN entity 510. The user or application that initiated the connection request may be notified of the reason for the rejection of the connection request (e.g., due to the registration pending state).

[0094] In some aspects, the registration pending message may include one or more parameters specified for the use of the registration pending state, or may be associated with it. For example, one parameter may be the duration of the registration pending state. The UE 520 may start a timer set to the duration. Before sending the registration recovery message, the UE 520 may wait until the timer expires. The duration may be associated with the timer until the next availability of the feeder link connection occurs. The UE 520 may also receive and store parameters from an earlier configuration. The NTN entity 510 may also enter a registration pending state and store parameters or information received in the registration request message and UE identification information, such as a first identifier (ID) and / or a second ID associated with the first ID and which may be a permanent ID (e.g., a subscriber ID).

[0095] In some aspects, the registration pending message may include a reason for the registration pending message, such as the feeder link 460 is unavailable or the NTN entity 510 is outside the coverage of an authenticated ground station, such as the ground station 530. The UE 520 may display the reason to a user of the UE 520 or indicate the reason to other devices or applications. The NTN entity 510 may also provide the reason to the requesting device. The NTN entity 510 may buffer incoming connection requests and process them after registration is complete.

[0096] As shown by reference numeral 620, the NTN entity 510 may send an authentication request message to a ground station 530, which may host or be connected to an HSS, AMF, SMF, or another authentication function. As shown by reference numeral 625, the ground station 530 may send an authentication response, regardless of whether the authentication is successful. This occurs when the feeder link 460 is available.

[0097] As shown by reference numeral 630, UE 520 may send a registration recovery message to resume the registration procedure. This may be during the second overflight. UE 520 may send a registration recovery message based at least in part on a cause, timer expiration, overflight schedule, feeder link schedule, and / or detected changes in traffic or channel conditions. In some aspects, for additional security, UE 520 may use the first ID as a temporary ID. The first ID and / or the second ID may be specific to the registration recovery message. For example, the first ID may be used only for the registration recovery message. The registration recovery message may also include only a subset of the parameters or only a subset of the information included in the registration request message. NTN entity 510 may identify UE 520 based at least in part on the first ID.

[0098] In some aspects, sending the registration pending message may include creating a record of UE 520 in a database and associating the record of UE 520 with a registration pending state. NTN entity 510 may create a first ID for UE 520 and associate the record of UE 520 with the first ID of UE 520. NTN entity 510 may identify UE 520 by retrieving the record of UE 520 from a database based at least in part on the first ID in the registration resume message.

[0099] In the case of successful registration (e.g., successful authentication), the NTN entity 510 may send a registration accept message, as shown by reference numeral 635. As shown by reference numeral 640, the UE 520 may send a registration complete message. By using the registration pending state, the UE 520 may save processing resources and signaling resources. Alternatively, in the case of an unsuccessful registration procedure (e.g., timeout, unsuccessful authentication), the NTN entity 510 may send a registration reject message.

[0100] Figure 6B The registration state and the registration message using the registration pending state are shown. For example, the UE 520 may be in the deregistered state and send a registration message, such as a registration request message. Once registration is initiated, the UE 520 may enter the registration pending state after receiving the registration pending message. When the UE 520 is in the registration pending state, authentication is performed. When the UE 520 sends a registration resume message, the registration procedure may resume.

[0101] If the registration is successful, the UE 520 may receive a registration acceptance message and enter a registered state. If the registration is unsuccessful, the UE 520 may receive a registration rejection message and remain in a deregistered state.

[0102] In some aspects, the UE 520 may indicate whether the use of the registration pending state is acceptable. That is, the UE 520 may be configured for the registration pending state and may determine to use the registration pending state or not to use the registration pending state. In the case where the UE 520 indicates that the registration pending state is unacceptable (e.g., not configured to use the registration pending state or determined not to use the registration pending state), the NTN entity 510 may reject the UE 520 and not use the registration pending state. This may be the case for real-time services, emergency calls, or other time-sensitive applications.

[0103] As indicated above, Fig. 6A and Figure 6B are provided as examples. Other examples can be found in the Fig. 6A and Figure 6B Different than described.

[0104] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a UE according to the present disclosure. Example process 700 is an example of a UE (eg, UE 120, UE 520) performing operations associated with using a registration pending state in an NTN.

[0105] like Figure 7 As shown, in some aspects, process 700 may include sending a registration request message (block 710). For example, a UE (e.g., using Fig. 9 The depicted communications manager 908 and / or sending component 904) can send a registration request message as described above.

[0106] like Figure 7 As further shown, in some aspects, process 700 may include receiving a registration pending message (block 720). For example, a UE (e.g., using Fig. 9 The depicted communications manager 908 and / or receiving component 902) can receive a registration pending message, as described above.

[0107] like Figure 7 As further shown, in some aspects, process 700 may include entering a registration pending state (block 730). For example, a UE (e.g., using Fig. 9 The depicted communications manager 908 and / or registration pending component 910) can enter a registration pending state, as described above.

[0108] like Figure 7 As further shown, in some aspects, process 700 may include sending a registration resume message based at least in part on one or more parameters associated with the registration pending message (block 740). Fig. 9The depicted communications manager 908 and / or sending component 904) can send a registration resume message based at least in part on one or more parameters associated with the registration pending message, as described above.

[0109] like Figure 7 As further shown, in some aspects, process 700 may include receiving a registration accept message or a registration reject message (block 750). Fig. 9 The depicted communications manager 908 and / or receiving component 902) can receive a registration accept message or a registration reject message, as described above.

[0110] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0111] In a first aspect, the one or more parameters indicate a duration to wait before sending a registration resume message, and sending the registration resume message includes sending the registration resume message after waiting for the duration.

[0112] In a second aspect, alone or in combination with the first aspect, process 700 includes starting a timer set to a duration, wherein sending the registration resume message includes sending the registration resume message based at least in part on expiration of the timer.

[0113] In a third aspect, alone or in combination with one or more of the first and second aspects, the registration request message indicates that the registration pending state can be accepted by the UE.

[0114] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the one or more parameters indicate a reason for registering the pending message.

[0115] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the registration resumption message includes the first identifier of the UE associated with the second identifier of the UE.

[0116] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the first identifier is a temporary identifier and the second identifier is a permanent identifier.

[0117] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the permanent identifier is a subscriber identifier.

[0118] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first identifier is specific to the registration resumption message.

[0119] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the second identifier is specific to the registration request message.

[0120] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 700 includes displaying an indication of a registration pending status during the registration pending status.

[0121] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the registration pending message includes an attach pending message, the registration pending state includes an attach pending state, and / or the registration recovery message includes an attach recovery message. In some aspects, the registration request message includes an attach request message, the registration accept message includes an attach accept message, the registration reject message includes an attach reject message, and / or the registration complete message includes an attach complete message.

[0122] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks in the process 700 may be performed in parallel.

[0123] Figure 8 is a diagram illustrating an example process 800 performed, for example, by an NTN entity according to the present disclosure. Example process 800 is an example of an NTN entity (eg, base station 110, network entity, satellite 420 / 440, NTN entity 510) performing operations associated with using a registration pending state.

[0124] like Figure 8 As shown, in some aspects, process 800 may include receiving a registration request message from a UE (block 810). For example, an NTN entity (e.g., using Fig.10 The depicted communications manager 1008 and / or receiving component 1002) can receive a registration request message from a UE, as described above.

[0125] like Figure 8 As further shown, in some aspects, process 800 may include sending a registration pending message (block 820). For example, an NTN entity (e.g., using Fig.10 The depicted communications manager 1008 and / or sending component 1004) can send a registration pending message as described above.

[0126] like Figure 8 As further shown, in some aspects, process 800 may include performing an authentication procedure of the UE to a ground network entity (block 830). For example, an NTN entity (e.g., using Fig.10The depicted communications manager 1008 and / or authentication component 1010) can perform authentication procedures of the UE with the ground network entity, as described above.

[0127] like Figure 8 As further shown, in some aspects, process 800 may include receiving a registration resume message from the UE (block 840). Fig.10 The depicted communications manager 1008 and / or receiving component 1002) can receive a registration resume message from a UE, as described above.

[0128] like Figure 8 As further shown, in some aspects, process 800 may include sending a registration accept message or a registration reject message based at least in part on whether the UE is authenticated (block 850). Fig.10 The depicted communications manager 1008 and / or sending component 1004) can send a registration accept message or a registration reject message based at least in part on whether the UE is authenticated, as described above.

[0129] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, the registration request message indicates that the registration pending state can be accepted by the UE.

[0131] In a second aspect, alone or in combination with the first aspect, the registration pending message includes one or more parameters indicating an expected duration before receiving a registration resume message.

[0132] In a third aspect, alone or in combination with one or more of the first and second aspects, the expected duration is associated with a duration of a time window between consecutive overflights of the NTN entity over the location of the ground station.

[0133] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes buffering messages for the UE between sending a registration pending message and sending a registration accept message or a registration reject message.

[0134] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 800 includes sending a registration pending indication in response to receiving a request to connect to the UE from another UE between sending a registration pending message and sending a registration accept message or a registration reject message.

[0135] In a sixth aspect, either alone or in combination with one or more of aspects one to five, sending a registration pending message comprises: creating a record of the UE in a database; associating the record of the UE with a registration pending status; creating a first identifier of the UE associated with a second identifier of the UE; and associating the record of the UE with the first identifier of the UE.

[0136] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, the registration resumption message includes a first identifier of the UE, which is associated with a second identifier of the UE and is specific to the registration resumption message, and process 800 includes identifying the UE based at least in part on the first identifier.

[0137] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, identifying the UE includes retrieving a record of the UE from a database based at least in part on the first identifier.

[0138] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The depicted blocks may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0139] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a UE (e.g., UE 120, UE 520), or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may use receiving component 902 and transmitting component 904 to communicate with another apparatus 906 (such as a UE, a base station, a network entity, an NTN entity, or another wireless communication device). As further shown, apparatus 900 may include a communication manager 908. The communication manager 908 may control and / or otherwise manage one or more operations of the receiving component 902 and / or the transmitting component 904. In some aspects, the communication manager 908 may include a communication manager 908 in conjunction with the receiving component 902 and / or the transmitting component 904. Figure 2 The communication manager 908 may be or be similar to one or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE. Figure 1 and Figure 2908 is depicted. For example, in some aspects, the communication manager 908 can be configured to perform one or more of the functions described as being performed by the communication manager 908. In some aspects, the communication manager 908 can include a receiving component 902 and / or a sending component 904. The communication manager 908 can include one or more of a registration pending component 910, etc.

[0140] In some aspects, the apparatus 900 may be configured to perform Figure 1 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or part of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0141] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0142] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0143] The sending component 904 can send a registration request message. The receiving component 902 can receive a registration pending message. The registration pending component 910 can enter a registration pending state. The sending component 904 can send a registration resume message based at least in part on one or more parameters associated with the registration pending message. The receiving component 902 can receive a registration accept message or a registration reject message.

[0144] Registration pending component 910 can start a timer set to a duration, and sending component 904 can send a registration resumption message based at least in part on expiration of the timer.Registration pending component 910 can display an indication of the registration pending state during the registration pending state.

[0145] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set (one or more) of components may be described as being executable by Fig. 9 Another group of components shown performs one or more functions.

[0146] Fig.10is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be an NTN entity (e.g., base station 110, satellite 420 / 440, NTN entity 510), or an NTN entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, a ground station, a network entity, an NTN entity, a relay station, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 1008. Communication manager 1008 may control and / or otherwise manage one or more operations of receiving component 1002 and / or transmitting component 1004. In some aspects, communication manager 1008 may include a communication manager 1008 in conjunction with receiving component 1002 and / or transmitting component 1004. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities. The communication manager 1008 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1008 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1008 can include a receiving component 1002 and / or a sending component 1004. The communication manager 1008 can include an authentication component 1010 and / or a buffering component 1012, among other things.

[0147] In some aspects, the apparatus 1000 may be configured to perform Figure 1 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 One or more components of the NTN entity. Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or part of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0148] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the NTN entity.

[0149] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the NTN entity. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0150] The receiving component 1002 can receive a registration request message from the UE. The sending component 1004 can send a registration pending message. The authentication component 1010 can perform an authentication procedure of the UE to the ground network entity. The receiving component 1002 can receive a registration resume message from the UE. The sending component 1004 can send a registration accept message or a registration reject message based at least in part on whether the UE is authenticated.

[0151] The buffering component 1012 can buffer messages for the UE between sending of the registration pending message and sending of the registration accept message or the registration reject message. The sending component 1004 can send a registration pending indication in response to receiving a request to connect to the UE from another UE between sending of the registration pending message and sending of the registration accept message or the registration reject message.

[0152] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The illustrated set (one or more) of components may be described as being executable by Fig.10 Another group of components shown performs one or more functions.

[0153] The following provides an overview of some aspects of the disclosure:

[0154] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: sending a registration request message; receiving a registration pending message; entering a registration pending state; sending a registration resume message based at least in part on one or more parameters associated with the registration pending message; and receiving a registration accept message or a registration reject message.

[0155] Aspect 2: The method according to aspect 1, wherein the one or more parameters indicate a duration to wait before sending the registration resumption message, and wherein sending the registration resumption message includes sending the registration resumption message after waiting for the duration.

[0156] Aspect 3: The method according to aspect 2 further comprises starting a timer set to the duration, wherein sending the registration restoration message comprises sending the registration restoration message based at least in part on expiration of the timer.

[0157] Aspect 4: The method according to any one of aspects 1 to 3, wherein the registration request message indicates that the registration pending state can be accepted by the UE.

[0158] Aspect 5: The method according to any one of aspects 1 to 4, wherein the one or more parameters indicate a cause of the registration pending message.

[0159] Aspect 6: The method according to any one of aspects 1 to 5, wherein the registration resumption message includes the first identifier of the UE associated with the second identifier of the UE.

[0160] Aspect 7: The method according to aspect 6, wherein the first identifier is a temporary identifier and the second identifier is a permanent identifier.

[0161] Aspect 8: The method according to aspect 7, wherein the permanent identifier is a subscriber identifier.

[0162] Aspect 9: The method according to aspect 6, wherein the first identifier is specific to the registration resumption message.

[0163] Aspect 10: The method according to aspect 6, wherein the second identifier is specific to the registration request message.

[0164] Aspect 11: The method according to any one of aspects 1 to 10, further comprising displaying an indication of the registration pending state during the registration pending state.

[0165] Aspect 12: The method according to any one of aspects 1 to 11, wherein the registration pending message includes an attach pending message, the registration pending state includes an attach pending state, and the registration resume message includes an attach resume message.

[0166] Aspect 13: A method of wireless communication performed by a non-terrestrial network entity, the method comprising: receiving a registration request message from a user equipment (UE); sending a registration pending message; performing an authentication procedure of the UE to the terrestrial network entity; receiving a registration recovery message from the UE; and sending a registration acceptance message or a registration rejection message based at least in part on whether the UE is authenticated.

[0167] Aspect 14: The method according to aspect 13, wherein the registration request message indicates that the registration pending state can be accepted by the UE.

[0168] Aspect 15: The method according to aspect 13 or 14, wherein the registration pending message includes one or more parameters indicating an expected duration before receiving the registration resume message.

[0169] Aspect 16: The method according to aspect 15, wherein the expected duration is associated with the duration of a time window between consecutive overflights of the non-ground network entity over the location of a ground station.

[0170] Aspect 17: According to any one of aspects 13 to 16, the method further includes buffering messages for the UE between sending the registration pending message and sending the registration accept message or the registration reject message.

[0171] Aspect 18: According to the method of any one of Aspects 13 to 17, the method also includes sending a registration pending indication in response to receiving a request to connect to the UE from another UE between sending the registration pending message and sending the registration accept message or the registration reject message.

[0172] Aspect 19: A method according to any one of Aspects 13 to 18, wherein sending the registration pending message includes: creating a record of the UE in a database; associating the record of the UE with a registration pending status; creating a first identifier of the UE associated with a second identifier of the UE; and associating the record of the UE with the first identifier of the UE.

[0173] Aspect 20: A method according to any one of Aspects 13 to 19, wherein the registration resumption message includes a first identifier of the UE, the first identifier is associated with the second identifier of the UE and is specific to the registration resumption message, and wherein the method also includes identifying the UE at least in part based on the first identifier.

[0174] Aspect 21: The method according to aspect 20, wherein identifying the UE includes retrieving a record of the UE from a database based at least in part on the first identifier.

[0175] Aspect 22: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 21.

[0176] Aspect 23: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 21.

[0177] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 21.

[0178] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 21.

[0179] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 21.

[0180] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0181] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the system or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code for implementing these systems and / or methods does not limit various aspects. Therefore, there is no reference to specific software code herein to describe the operation and behavior of the system and / or method, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

[0182] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0183] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0184] Any element, action or instruction used herein should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "said one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: Send a registration request message; Receive a registration pending message; Enter the registration pending state; sending a registration resume message based at least in part on one or more parameters associated with the registration pending message; as well as Receive a registration acceptance message or a registration rejection message.

2. The UE of claim 1 , wherein the one or more parameters indicate a duration to wait before sending the registration resume message, and wherein the one or more processors for sending the registration resume message are configured to send the registration resume message after waiting for the duration.

3. The UE of claim 2, wherein the one or more processors are configured to start a timer set to the duration, wherein the one or more processors for sending the registration resumption message are configured to send the registration resumption message based at least in part on expiration of the timer. 4 . The UE according to claim 1 , wherein the registration request message indicates that the registration pending state can be accepted by the UE. 5 . The UE of claim 1 , wherein the one or more parameters indicate a cause of the registration pending message.

6. The UE of claim 1, wherein the registration resumption message comprises a first identifier of the UE associated with a second identifier of the UE. The UE according to claim 6 , wherein the first identifier is a temporary identifier and the second identifier is a permanent identifier. The UE according to claim 7 , wherein the permanent identifier is a subscriber identifier.

9. The UE of claim 6, wherein the first identifier is specific to the registration resumption message.

10. The UE of claim 6, wherein the second identifier is specific to the registration request message.

11. The UE of claim 1, wherein the one or more processors are configured to display an indication of the registration pending state during the registration pending state.

12. The UE of claim 1, wherein the registration pending message comprises an attach pending message, the registration pending state comprises an attach pending state, and the registration resume message comprises an attach resume message.

13. A non-terrestrial network (NTN) entity for wireless communication, the non-terrestrial network (NTN) entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a registration request message from a user equipment (UE); Send a registration pending message; executing an authentication procedure of the UE to a ground network entity; receiving a registration resume message from the UE; as well as A registration accept message or a registration reject message is sent based at least in part on whether the UE is authenticated.

14. The NTN entity according to claim 13, wherein the registration request message indicates that the registration pending state can be accepted by the UE.

15. The NTN entity of claim 13, wherein the registration pending message comprises one or more parameters indicating an expected duration before receipt of the registration resume message.

16. The NTN entity of claim 15, wherein the expected duration is associated with the duration of a time window between consecutive overflights of the non-terrestrial network entity over the location of a ground station.

17. The NTN entity of claim 13, wherein the one or more processors are configured to buffer messages for the UE between sending of the registration pending message and sending of the registration accept message or the registration reject message.

18. The NTN entity of claim 13, wherein the one or more processors are configured to send a registration pending indication in response to receiving a request to connect to the UE from another UE between sending of the registration pending message and sending of the registration accept message or the registration reject message.

19. The NTN entity of claim 13, wherein the one or more processors for sending the registration pending message are configured to: Creating a record of the UE in a database; associating the record of the UE with a registration pending state; creating a first identifier of the UE associated with a second identifier of the UE; as well as The record of the UE is associated with the first identifier of the UE.

20. The NTN entity of claim 13, wherein the registration resumption message includes a first identifier of the UE, the first identifier being associated with a second identifier of the UE and specific to the registration resumption message, and wherein the one or more processors are configured to identify the UE based at least in part on the first identifier.

21. The NTN entity of claim 20, wherein the one or more processors for identifying the UE are configured to retrieve a record of the UE from a database based at least in part on the first identifier.

22. A method of wireless communication performed by a user equipment (UE), the method comprising: Send a registration request message; Receive a registration pending message; Enter the registration pending state; sending a registration resume message based at least in part on one or more parameters associated with the registration pending message; as well as Receive a registration acceptance message or a registration rejection message.

23. The method of claim 22, wherein the one or more parameters indicate a duration to wait before sending the registration resume message, and wherein sending the registration resume message comprises sending the registration resume message after waiting for the duration.

24. The method of claim 22, wherein the registration request message indicates that the registration pending state can be accepted by the UE.

25. The method of claim 22, wherein the registration resumption message comprises a first identifier of the UE associated with a second identifier of the UE, wherein the first identifier is a temporary identifier and the second identifier is a permanent identifier.

26. The method of claim 22, further comprising displaying an indication of the registration pending status during the registration pending status.

27. A method of wireless communication performed by a non-terrestrial network entity, the method comprising: receiving a registration request message from a user equipment (UE); Send a registration pending message; executing an authentication procedure of the UE to a ground network entity; receiving a registration resume message from the UE; as well as A registration accept message or a registration reject message is sent based at least in part on whether the UE is authenticated.

28. A method according to claim 27, wherein the registration pending message includes one or more parameters indicating an expected duration before receiving the registration resumption message, and wherein the expected duration is associated with the duration of a time window between consecutive overflights of the non-ground network entity over the location of the ground station.

29. The method of claim 27, wherein sending the registration pending message comprises: Creating a record of the UE in a database; associating the record of the UE with a registration pending state; creating a first identifier of the UE associated with a second identifier of the UE; as well as The record of the UE is associated with the first identifier of the UE.

30. The method of claim 29, wherein the method further comprises identifying the UE by retrieving the record of the UE from the database based at least in part on the first identifier.

Images