Apparatus, methods, and computer programs related to terrestrial networks and non-terrestrial networks

Abstract

The subject of this disclosure is "Apparatus, Methods, and Computer Programs Related to Terrestrial and Non-Terrestrial Networks". An apparatus includes: means for receiving information indicating the unavailability of a terrestrial network (TN) for a user equipment based on a mobility pattern associated with the user equipment, and information indicating the unavailability of a non-terrestrial network (NTN) for the user equipment based on a mobility pattern associated with the user equipment; and means for operating according to the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN.

Description

Technical Field

[0001] Various embodiments of this disclosure relate to methods, apparatus, and computer programs, and specifically, but not exclusively, to apparatus, methods, and computer programs relating to terrestrial networks (TN) and non-terrestrial networks (NTN). Background Technology

[0002] A communication network can be viewed as a facility that allows communication between two or more communication devices or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards include the so-called 5G (fifth generation) and 6G (sixth generation) standards released by 3GPP. Summary of the Invention

[0004] Some embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure.

[0005] According to a first aspect, an apparatus is provided, comprising: means for receiving information indicating unavailability of a terrestrial network TN for a user equipment based on a mobility mode associated with the user equipment and information indicating unavailability of a non-terrestrial network NTN for the user equipment based on a mobility mode associated with the user equipment; and means for operating according to the information indicating unavailability of the TN and the information indicating unavailability of the NTN.

[0006] Information indicating the unavailability of TN and information indicating the unavailability of NTN can be received from the resource management server.

[0007] The resource management server may include a service enabler architecture layer for vertical (SEAL) servers.

[0008] At least one of the following: information indicating the unavailability of TN can provide information about the location or time of the unavailability of TN; or, information indicating the unavailability of NTN can provide information about the location or time of the unavailability of NTN.

[0009] At least one of the following: information indicating that the TN is unavailable can provide information about at least one of the location or time associated with higher congestion of the TN; or information indicating that the NTN is unavailable can provide information about at least one of the location or time associated with higher congestion of the TN.

[0010] The means for operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN can be used to prevent the transmission of uplink messages to the corresponding network of the NTN and the TN when one of the corresponding networks of the NTN and the TN is unavailable or has higher congestion.

[0011] The apparatus for operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN can be used to prevent cell search relative to the corresponding one of the NTN network and the TN when one of the corresponding ones of the NTN and TN is unavailable or has higher congestion.

[0012] The apparatus for operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN can be used to determine whether a switch from one of the NTN and TN to the other of the NTN and TN should occur based on the unavailability or higher congestion of the other of the NTN and TN.

[0013] The apparatus for operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN can be used to select the corresponding one of the NTN and TN with lower congestion using the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN.

[0014] The receiving device can be used to receive a request from a resource management server for satellite coverage availability information for the device.

[0015] The apparatus may include means for sending a response to a resource management server for a request for satellite coverage availability information for the apparatus, the response including information indicating that the apparatus supports satellite access.

[0016] The device can be configured to provide or include SEAL client functionality.

[0017] The device may include, be included in, or implement a user equipment.

[0018] According to a second aspect, a method is provided, comprising: receiving information indicating unavailability of a terrestrial network TN for a user equipment based on a mobility pattern associated with the user equipment, and information indicating unavailability of a non-terrestrial network NTN for the user equipment based on a mobility pattern associated with the user equipment; and operating according to the information indicating unavailability of the TN and the information indicating unavailability of the NTN.

[0019] Information indicating the unavailability of TN and information indicating the unavailability of NTN can be received from the resource management server.

[0020] The resource management server may include a service enabler architecture layer for vertical (SEAL) servers.

[0021] At least one of the following: information indicating the unavailability of TN can provide information about the location or time of the unavailability of TN; or, information indicating the unavailability of NTN can provide information about the location or time of the unavailability of NTN.

[0022] At least one of the following: information indicating that the TN is unavailable can provide information about at least one of the location or time associated with higher congestion of the TN; or information indicating that the NTN is unavailable can provide information about at least one of the location or time associated with higher congestion of the TN.

[0023] Operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN may include: not sending uplink messages to the corresponding network of the NTN and the corresponding network of the TN when one of the corresponding networks of the NTN and TN is unavailable or has higher congestion.

[0024] Operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN may include: not performing a cell search relative to the corresponding one of the NTN network and the TN when the corresponding one of the NTN and TN is unavailable or has higher congestion.

[0025] Operating based on information indicating the unavailability of the TN and information indicating the unavailability of the NTN may include determining whether a switchover from one of the NTN and TN to the other of the NTN and TN should occur based on the unavailability or higher congestion of the other of the NTN and TN.

[0026] Operating based on information indicating the unavailability of the TN and the NTN may include using the information indicating the unavailability of the TN and the NTN to select the one with lower congestion between the NTN and the TN.

[0027] The method may include receiving a request from a resource management server for satellite coverage availability information for user equipment.

[0028] The method may include sending a response to a resource management server for a request for satellite coverage availability information for a user equipment, the response including information indicating that the user equipment supports satellite access.

[0029] User equipment can be configured to provide SEAL client functionality.

[0030] This method can be performed by a device.

[0031] The device may include, be included in, or be implemented as a user equipment.

[0032] The apparatus may include means for performing the method.

[0033] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any of the methods of the second aspect.

[0034] According to a third aspect, an apparatus is provided, comprising: means for determining information indicating the unavailability of a terrestrial network TN of a user equipment based on a mobility pattern associated with the user equipment, and means for determining information indicating the unavailability of a non-terrestrial network NTN of the user equipment based on a mobility pattern associated with the user equipment; and means for transmitting the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN to the user equipment.

[0035] The apparatus may include a module for requesting information about mobility patterns associated with a user equipment; and a means for receiving information about mobility patterns associated with a user equipment.

[0036] The apparatus may include means for requesting information about the unavailability of TN; and means for receiving information about the unavailability of TN.

[0037] The device may include means for determining satellite coverage information of the NTN using ephemeris data for one or more satellites.

[0038] The means for determining information indicating the unavailability of the TN and information indicating the unavailability of the NTN may use at least one of the following: TN unavailability information; satellite coverage information for the NTN; or information about mobility patterns associated with user equipment.

[0039] At least one of the following: information indicating the unavailability of the TN can provide information about the location or time of the TN's unavailability based on mobility patterns associated with the user equipment; information indicating the unavailability of the NTN can provide information about the location or time of the NTN's unavailability based on mobility patterns associated with the user equipment; information indicating the unavailability of the TN can provide information about the location or time associated with higher congestion of the TN based on mobility patterns associated with the user equipment; or, information indicating the unavailability of the NTN can provide information about the location or time associated with higher congestion of the TN based on mobility patterns associated with the user equipment.

[0040] The apparatus may include means for sending information indicating that the TN is unavailable and information indicating that the NTN is unavailable to the vertical application layer user equipment (VAL) UE.

[0041] The device may include or be configured to provide a resource management server.

[0042] The resource manager server can include or be configured to provide a SEAL server.

[0043] According to the fourth aspect, a method is provided, comprising: determining information indicating the unavailability of a terrestrial network TN for the user equipment based on a mobility pattern associated with the user equipment, and determining information indicating the unavailability of a non-terrestrial network NTN for the user equipment based on a mobility pattern associated with the user equipment; and sending the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN to the user equipment.

[0044] The method may include requesting information about mobility patterns associated with a user equipment; and means for receiving information about mobility patterns associated with a user equipment.

[0045] The method may include requesting information about the unavailability of TN; and means for receiving information about the unavailability of TN.

[0046] This method may include using ephemeris data for one or more satellites to determine satellite coverage information for the NTN.

[0047] The method may include using at least one of the following to determine information indicating the unavailability of the TN and information indicating the unavailability of the NTN: information about the unavailability of the TN; satellite coverage information for the NTN; or information about mobility patterns associated with user equipment.

[0048] At least one of the following: information indicating the unavailability of the TN can provide information about the location or time of the TN's unavailability based on mobility patterns associated with the user equipment; information indicating the unavailability of the NTN can provide information about the location or time of the NTN's unavailability based on mobility patterns associated with the user equipment; information indicating the unavailability of the TN can provide information about the location or time associated with higher congestion of the TN based on mobility patterns associated with the user equipment; or, information indicating the unavailability of the NTN can provide information about the location or time associated with higher congestion of the TN based on mobility patterns associated with the user equipment.

[0049] This method may include sending information indicating the unavailability of the TN and information indicating the unavailability of the NTN to the VAL UE.

[0050] This method can be performed by a device.

[0051] The device may include or be configured to provide a resource management server.

[0052] The resource manager server can include or be configured to provide a SEAL server.

[0053] The apparatus may include means for performing the method.

[0054] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any of the methods of the fourth aspect.

[0055] According to another aspect, a computer-readable medium is provided, including program instructions stored thereon for performing at least one of the methods described above.

[0056] According to one aspect, a non-transitory computer-readable medium is provided, including program instructions stored thereon for performing at least one of the methods described above.

[0057] According to one aspect, a non-volatile physical memory medium is provided, including program instructions stored thereon for performing at least one of the methods described above.

[0058] This article describes many different aspects. It should be understood that other aspects can be provided through any two or more of the aspects described herein.

[0059] Various other aspects are also described in this disclosure and claims. Attached Figure Description

[0060] Some embodiments will now be described by way of non-limiting and illustrative examples with reference to the accompanying drawings, in which:

[0061] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown;

[0062] Figure 2 This is a schematic diagram of a communication system, such as a 5G communication system (5GS).

[0063] Figure 3 A general network function model for the service enabler architecture layer of vertical (SEAL) is shown;

[0064] Figure 4 A first process according to some embodiments is shown;

[0065] Figure 5 A second process according to some embodiments is shown;

[0066] Figure 6 A first method according to some embodiments is shown;

[0067] Figure 7 A second method according to some embodiments is shown; and

[0068] Figure 8 Examples of apparatuses according to some embodiments are shown;

[0069] Figure 9 This illustrates a process for supporting discontinuous coverage for satellite access, according to some embodiments. Detailed Implementation

[0070] The following embodiments are provided by way of non-limiting and illustrative examples. While this disclosure may refer to "an," "one," or "some" embodiments in several places herein, this does not necessarily mean that every reference is to the same embodiment, or that a particular feature is applicable only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is intended that such feature, structure, or characteristic may be applied in combination with other embodiments (whether explicitly described or not).

[0071] It should be understood that although the terms "first," "second," etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0072] For the purposes of this invention, the phrases “at least one of A or B,” “at least one of A and B,” and “A and / or B” mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases “A, B, and / or C” mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0073] As used herein, the term “or” means non-exclusive “or” unless otherwise specified (e.g., “or other” or “or in alternatives”).

[0074] As used herein, unless explicitly stated otherwise, “responding to A” to perform the corresponding feature, step, or function does not mean that the corresponding feature, step, or function is performed immediately after the occurrence of “A”, because one or more intervention features, steps, or functions may be performed (at least partially) between the occurrence of the corresponding feature, step, or function and “A”. Similarly, “based on A” to perform the corresponding feature, step, or function does not indicate that the corresponding feature, step, or function is performed solely based on “A”, because the corresponding feature, step, or function may be based on one or more other features, steps, or functions besides “A”. The described embodiments can be implemented in communication networks, such as any of the following radio access technologies (RATs): Global Microwave Access Interoperability (WiMAX), Global System for Mobile Communications (GSM, 2G), GSMEDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE and Enhanced LTE (eLTE), 5G (also known as NR), 6G or above. Furthermore, communications within the communication network may utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), and / or Discrete Fourier Transform Extended OFDM (DFT-s-OFDM). In the following text, references to the UE should be understood as references to any suitable terminal device.

[0075] The term "terminal device" refers to any terminal device capable of wireless communication. As a non-limiting and illustrative example, a terminal device may be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). Terminal devices can realize or include mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, USB adapters, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, targets, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc.

[0076] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown. The communication network, or cellular communication network, may include a network node 110 configured to provide one or more cells (e.g., cell 100), and a network node 112 configured to provide one or more other cells (e.g., cell 102). For example, each cell may be, for example, a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​a corresponding access node.

[0077] Network node 110 can be configured to provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from the network node to UE 120 and uplink (UL) communication from UE 120 to the network node. Examples of uplink channels include a Physical Uplink Control Channel (PUCCH) for transmitting control information and a Physical Uplink Shared Channel (PUSCH) for transmitting data to the network. Examples of downlink channels include a Physical Downlink Control Channel (PDCCH) for transmitting control information and a Physical Downlink Shared Channel (PDSCH) for transmitting data to the user equipment.

[0078] The system can have multiple UEs 120 and 122. Each of the multiple UEs 120 and 122 can be served by the same or different network nodes 110 and 112. UEs can be configured with dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 110 and 112. UEs 120 and 122 can communicate with each other by establishing a device-to-device (D2D) communication interface between UEs 120 and 122 via a so-called "side link" (SL). Such D2D communication can be referred to as, for example, machine-to-machine, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0079] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. For example, the LTE specification refers to this interface as the X2 interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be called the Xn interface.

[0080] Network nodes 110 and 112 can also be connected to the core network 202 of the communication network via another interface.

[0081] For example, the LTE specification designates the core network as the Evolved Packet Core (EPC), and the core network may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices within a tracking area comprising multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing within the core network as well as data routing to / from terminal devices.

[0082] For example, the 5G specification designates the core network as the 5G Core (5GC). The 5G Core can include, for example, Access and Mobility Management Functions (AMF) and User Plane Functions / Gateways (UPF), as well as other functions. AMF can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and / or security context management. For example, UPF nodes can support packet routing and forwarding, and / or packet inspection and Quality of Service (QoS) processing.

[0083] Figure 2A schematic diagram of a communication system, such as a 5G communication system (5GS), is shown. The 5GS may include a user equipment (UE), a 5G core network (5GC) 202, and one or more application functions 203. The UE may connect to the 5GC via a network node 110 (e.g., a radio access node) of the radio access network. Application functions 203 may be deployed in the 5GS as trusted application functions, or they may be deployed or hosted on one or more application servers of a data network (DN) 204. Such application functions may be untrusted application functions. The 5GS is configured to connect the UE to the data network, the access network, and the 5GC 202 (e.g., the 5GC's UPF).

[0084] 5GC may include the following network functions: Network Slice Selection Function (NSSF); Network Open Function (NEF) 205; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM) 206; Application Function (AF) 203; Authentication Server Function (AUSF) 207; Access and Mobility Management Function (AMF) 208; Session Management Function (SMF) 209; and / or User Plane Function (UPF) 210.

[0085] Figure 2 Various interfaces (N1, N2, etc.) that can be implemented between various components of the system are also shown. Figure 2 Not all of the above network functions are shown in the figure, and in some examples, 5GC may include other network functions in addition to those described above.

[0086] The AMF 208 can handle the termination of Non-Access Stratum (NAS) signaling, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and / or security context management. For example, the UPF210 can support packet routing and forwarding, and / or packet inspection and Quality of Service (QoS) processing.

[0087] Some implementations can be used with the Service Enabler Architecture Layer (SEAL) for vertical applications.

[0088] In this regard, refer to Figure 3 It illustrates a general network function model for SEAL. This comes from 3GPP TS23.434. Figure 6 .2-1.

[0089] Examples of SEAL services that can be supported by the vertical application layer VAL include: location management; group management; configuration management; identity management; key management; network resource management; data delivery; notification management; network slicing capability enablement; and / or application data analytics enablement.

[0090] A UE can be configured to support VAL clients. A VAL UE is a UE that can be used to participate in one or more VAL services. A VAL client is an entity that provides client-side functionality corresponding to a vertical application. A VAL user is an authorized user who can use a VAL UE to participate in one or more VAL services. A VAL user ID is a generic name for the user ID of a VAL user within a specific VAL service.

[0091] A UE can be configured to support a SEAL client. A SEAL client is an entity that provides client (UE)-side functionality corresponding to a specific SEAL service.

[0092] Provides a VAL server. A VAL server is a server application function for a specific VAL service.

[0093] Provide a SEAL server. A SEAL server is an entity that provides server-side functionality corresponding to a specific SEAL service. LMS (Location Management Server) is an example of a SEAL server.

[0094] In the vertical application layer, VAL clients communicate with VAL servers through VAL-UU reference points. VAL-UU reference points support both unicast and multicast transmission modes. Communication between VAL clients and VAL servers can be via 3GPP network systems. This can be, for example, as follows: Figure 2 As shown.

[0095] The UE and the SEAL functional entities on the server are grouped into SEAL clients and SEAL servers, respectively. SEAL consists of a set of public services (e.g., group management, location management) and reference points. SEAL provides its services to the vertical application layer (VAL).

[0096] The vertical application layer can include vertical application enabler layer functions and application-specific functions. SEAL clients communicate with the SEAL server through the SEAL-UU reference point. SEAL-UU can support unicast and multicast transmission modes. Communication between the SEAL client and SEAL server can be via a 3GPP network system. This can be, for example, as follows: Figure 2 As shown.

[0097] The SEAL client provides service enabler layer support to the VAL client through the SEAL-C reference point. The VAL server communicates with the SEAL server through the SEAL-S reference point. The SEAL server can communicate with the underlying 3GPP network system using the appropriate 3GPP interface specified by the 3GPP network system.

[0098] The UE's satellite access can have discontinuous coverage.

[0099] Based on ephemeris and satellite coverage availability information, the SEAL server can retrieve unavailability periods (e.g., duration and start time) based on the UE's location. The SEAL server can then provide this information to the VAL UE. The SEAL server can then expose this information to the VAL UE to indicate that satellite unavailability periods may need to be considered when the VAL UE is using satellite access.

[0100] Based on satellite ephemeris and satellite coverage availability information, the SEAL server can retrieve unavailability periods (e.g., duration and start time of the unavailability period) to guide the UE on when it can trigger a UL service flow. In this example, the UE can obtain the unavailability period information.

[0101] The SEAL server can send unavailability period information to the VAL UE / SEAL client via an unavailability period information configuration request.

[0102] The SEAL client sends an acknowledgment to the SEAL server, indicating whether the SEAL client supports satellite access. The SEAL client will operate with unavailability period information in mind. For example, the SEAL client will not send UL messages during unavailability periods. This procedure can be followed when the UE is attached to a non-terrestrial network NTN (e.g., a network supported by one or more satellites).

[0103] However, the current proposal may have issues, for example, when both ground networks TN (e.g., 5G or 6G networks) and NTN may be available to the UE.

[0104] For example, current recommendations do not consider TN availability when the NTN is unavailable. For instance, when a UE is attached to an NTN and the NTN becomes unavailable, the UE may not have information about the TN's availability. This could cause the UE to attempt to send a UL message to the TN even when the NTN is unavailable, even if the TN is also unavailable.

[0105] Some embodiments take into account the unavailability of TN and NTN networks. Specifically, TN and NTN network unavailability information can be provided to the UE and can be specific to a particular UE. The TN and NTN network unavailability information for a particular UE can take into account the predicted mobility of that particular UE.

[0106] In some embodiments, unavailability information indicates areas or locations where individual networks are unavailable. Alternatively, in some embodiments, unavailability information indicates areas or locations where the corresponding network is available, from which areas or locations not covered by the corresponding network can be identified.

[0107] In some embodiments, the unavailability information indicates the time period and / or duration when the corresponding network is unavailable. Alternatively, in some embodiments, the unavailability information indicates the time period and / or duration when the corresponding network is available, from which the time period and / or duration can be determined when there is no coverage provided by the corresponding network.

[0108] In some embodiments, the UE is provided with unavailability information for both the NTN and TN. The UE can use this unavailability information to determine its behavior. For example, the UE can use this unavailability information to determine whether it should connect to the appropriate network. For example, the UE can use this unavailability information to determine whether it can send UL data to the appropriate network. For example, the UE can use this unavailability information to avoid searching for cells to latch in the appropriate network. This can result in power / energy savings.

[0109] In some embodiments, unavailability information of the UE's current location is provided to the UE. In some embodiments, unavailability information is provided to the UE not only based on the current UE location but also based on the UE's predicted location.

[0110] For example, the SEAL server can obtain the UE's predicted mobility pattern, and the unavailability information provided to the UE can take into account the UE's predicted mobility pattern. The SEAL server can obtain the predicted mobility pattern of at least one of TN or NTN from NWDAF and / or ADAES (Application Data Analytics Enablement Service) and / or any other suitable network function that provides data about the UE's predicted mobility pattern.

[0111] In some embodiments, NT and NTN unavailability information can be provided to the UE in different messages. The UE can respond to different messages with different responses or the same response.

[0112] In some embodiments, NT and NTN unavailability information can be provided to the UE in the same message, which can reduce signaling volume. The UE can respond to a message with different responses or the same response. This can reduce signaling volume when the UE provides a single response.

[0113] The SEAL server can determine the unavailability information of the NTN network and the NT network for the UE.

[0114] Based on UE mobility mode and NTN unavailability information, the SEAL server can request TN coverage information for areas and / or times where the NTN is unavailable and the UE is predicted to be located. The SEAL server can request TN coverage information from NEF or any other suitable network function.

[0115] The SEAL server can determine the UE's unavailability information. The SEAL server can provide the UE's unavailability information to both the VAL UE and the VAL server. The UE's unavailability information indicates when at least one of the NT or NTN is unavailable to the UE. The UE's unavailability information can also indicate to the UE when the corresponding network is unavailable to the UE.

[0116] In some embodiments, unavailability information may additionally or alternatively include information predicting network congestion at a specific location and / or time. This network congestion prediction information may be provided by NWDAF and / or ADAES and / or any other suitable network function. For example, higher network congestion may indicate to the UE that a network with that higher congestion is potentially unavailable to the UE or at least less available to the UE.

[0117] The UE can use information about predicted network congestion at a specific location and / or time to choose between NTN and TN. This selection can be based on the network predicted to have a lower congestion level. This can result in the UE having better Quality of Service (QoS) and / or better Quality of Experience (QoE). This helps with load balancing across networks.

[0118] refer to Figure 4 This illustrates a first example of a process according to some embodiments.

[0119] In this example, the UE can include or be configured to provide VAL clients and SEAL clients.

[0120] As mentioned at point 0, the SEAL server is configured to store ephemeris data for one or more satellites. The ephemeris data for one or more satellites indicates satellite access availability at location and / or time.

[0121] As mentioned in section 1, the SEAL server is configured to use ephemeris data from one or more satellites to determine satellite availability information and / or satellite unavailability information. Satellite availability information is configured to provide information about when each satellite is available and / or the locations or areas that each satellite will cover. Satellite unavailability information is configured to provide information about when each satellite is unavailable and / or the locations or areas that each satellite will not cover.

[0122] As mentioned in section 2, the SEAL server is configured to send a request for the predicted mobility mode of the VAL UE to the NWDAF and / or ADAES. The request to ADAES can be made via NEF.

[0123] As mentioned in section 3, the SEAL server is configured to receive responses from NWDAF and / or ADAES regarding requests for predicted mobility modes of the VAL UE. Responses from ADAES can be received via NEF. These responses provide information about the predicted mobility modes of the VAL UE.

[0124] As mentioned in section 4, the SEAL server is configured to send a satellite coverage availability information request to the UE. This is then sent to the SEAL client. The request determines whether the SEAL client is configured to have NTN coverage.

[0125] As mentioned in point 5, the SEAL client is configured to send a satellite coverage availability information response to the SEAL server. This response indicates whether the SEAL client is configured to have NTN coverage.

[0126] As mentioned in section 6, the SEAL server is configured to send a request for TN coverage information to the NEF. This request for TN coverage information is for the predicted path of the VALUE. The predicted path may include or may be based on the predicted mobility pattern. The predicted mobility pattern is obtained from the NWDAF, as discussed in the section on the process referenced in section 3.

[0127] As mentioned in point 7, NEF is configured to send a response to the SEAL server. This response includes TN coverage information for the predicted path of the requested VALUE.

[0128] As mentioned in point 8, the SEAL server is configured to determine the UE's unavailability information. This is based on satellite coverage availability information, TN coverage information, and the UE's predicted mobility pattern.

[0129] As mentioned in point 9, the SEAL server is configured to share the UE's unavailability information with the VAL UE. The UE's unavailability information can be provided in the unavailability period configuration request. The unavailability information can provide NTN coverage-related information and TN coverage-related information.

[0130] As mentioned at point 11, the SEAL server is configured to share UE unavailability information with the VAL server. UE unavailability information can be provided in the unavailability period information notification message. The unavailability information can provide NTN coverage-related information and TN coverage-related information.

[0131] It should be noted that the portions of the process referenced at points 9 and 11 may occur in any order or simultaneously. In some embodiments, the portion of the process referenced at point 11 may occur only after a response has been received from the UE in the portion of the process referenced at point 10.

[0132] As mentioned at point 10, the UE is configured to send an unavailability period configuration response in response to an unavailability period configuration request. This indicates that unavailability information has been configured at the UE. This information can be configured at the SEAL client at the UE. The response is then sent to the SEAL server.

[0133] Based on the unavailability period information received from the SEAL server, including NTN and TN related information, the UE can avoid cell search in areas and / or times when neither NTN nor TN coverage is available. This saves energy.

[0134] Based on TN unavailability information, the UE can continue to connect to the NTN without performing a cell search for a better connection, where the TN unavailability information indicates that the TN is unavailable at a specific time and / or location.

[0135] Based on NTN unavailability information, the UE can continue to connect to the TN without performing a cell search for a better connection, where the NTN unavailability information indicates that the NTN is unavailable at a specific time and / or location.

[0136] As previously mentioned, unavailability information can provide congestion-related information for at least one of the NTN and TN. Congestion-related information can be used to prevent the UE from seeking a better connection to a different network when another network is congested at a relevant time and / or location.

[0137] Congestion-related information can be used to enable the UE to find a better connection to a different network when the current network is congested at a relevant time and / or location.

[0138] refer to Figure 5 , Figure 5 A second example of a process according to some embodiments is shown.

[0139] In this example, the UE can include or be configured to provide VAL clients and SEAL clients.

[0140] The part of the process mentioned in 0 to 3 is usually related to Figure 4 The process described in the text is the same as the process mentioned in 0 to 3.

[0141] The parts of the process mentioned in 4 and 5 are usually related to Figure 4The process described in the text is the same as the process mentioned in 6 and 7.

[0142] The part of the process mentioned in 6 is usually related to Figure 4 The process described in the text is partly the same as the process mentioned in 8.

[0143] As mentioned in point 7, the SEAL server is configured to share the UE's unavailability information with the VAL UE and is configured to request satellite coverage availability information from the UE. This is sent to the SEAL client. The request determines whether the SEAL client is configured to have NTN coverage. The unavailability information can provide both NTN coverage-related information and TN coverage-related information. (See also: Regarding...) Figure 4 Compared to the described process, in Figure 4 The messages in the process mentioned at points 4 and 9 are combined in Figure 5 The example mentions the process in 7 places within a single message. The SEAL server provides coverage availability and NTN / TN unavailability for SEAL clients and / or VAL UEs.

[0144] As mentioned in point 8, the SEAL client is configured to send satellite coverage availability information and unavailability period configuration responses to the SEAL server. This response indicates whether the SEAL client is configured with NTN coverage and whether unavailability information is configured at the UE. This information can be configured at the SEAL client on the UE. (See also: Regarding...) Figure 4 Compared to the described process, in Figure 4 The messages in the process mentioned at points 5 and 10 are combined in Figure 5 In the example, there are 8 instances of the process mentioned in a single message.

[0145] As mentioned at point 9, the SEAL server is configured to send satellite coverage availability information and UE unavailability information for the UE to the VAL server. If the VAL server periodically requests information about the VAL UE (e.g., location data) from the SEAL server, the SEAL server can notify the VAL server of VAL UE unavailability periods, which can instruct the VAL server on how to operate to minimize service impact (e.g., extending data buffers, pending downlink data transmission). The VAL server subscribes to VAL UE locations (e.g., this can be periodic), and while notifying the VAL server about VAL UE locations, the SEAL server can be configured to provide VAL unavailability information regarding NTN and / or TN unavailability, taking into account UE mobility modes. This unavailability-related information may include any unavailability-related information previously discussed.

[0146] Additionally, if congestion information is also shared with the UE location, it will also help the VAL server provide better service.

[0147] Satellite coverage availability and unavailability information for the UE can be provided in the notification message. Unavailability information can provide NTN coverage-related information and TN coverage-related information.

[0148] refer to Figure 6 and 7 It illustrates some methods of some embodiments.

[0149] Each method can be performed by a device.

[0150] The device may include suitable components, such as circuitry for providing the corresponding method.

[0151] Additionally or alternatively, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least provide a corresponding method.

[0152] Additionally or alternatively, the device may be as described above. Figure 8 The subject of discussion.

[0153] The corresponding methods can be provided by computer program code or computer executable instructions.

[0154] right Figure 6 For reference only. The device may include, may be included in, or may implement the user equipment.

[0155] As mentioned in A1, the method includes: receiving information indicating the unavailability of the terrestrial network TN for the user equipment based on a mobility pattern associated with the user equipment, and information indicating the unavailability of the non-terrestrial network NTN for the user equipment based on a mobility pattern associated with the user equipment.

[0156] As mentioned at A2, the method includes: operating based on information indicating the unavailability of TN and information indicating the unavailability of NTN.

[0157] right Figure 7 For reference only. This method can be performed by an apparatus. The apparatus may include a resource management server or be configured to provide a resource management server. The resource management server may include a SEAL server or be configured to provide a SEAL server.

[0158] As mentioned in section B1, the method includes: determining information indicating the unavailability of the terrestrial network TN for the user equipment based on mobility patterns associated with the user equipment, and determining information indicating the unavailability of the non-terrestrial network NTN for the user equipment based on mobility patterns associated with the user equipment.

[0159] As mentioned in section B2, the method includes sending information indicating the unavailability of the TN and information indicating the unavailability of the NTN to the user equipment.

[0160] It should be understood that, regarding Figure 6 or Figure 7 Any method described may be modified to include any feature (or portions thereof) discussed in the previous example.

[0161] It should be understood that the above references to various network functions may include means for performing at least some of the functions associated with these network functions. Furthermore, means including a network function may include a virtual network function instance of that network function.

[0162] Although the device has been described as a single entity, different modules and memories can be implemented in one or more physical or logical entities.

[0163] It should be noted that while some embodiments have been described with respect to 5G networks and other networks, similar principles can be applied with respect to other networks and communication systems. Some embodiments can be used with respect to 6G networks. Therefore, although various embodiments of this disclosure have been described herein by way of non-limiting and illustrative examples with reference to example architectures for wireless networks, technologies and standards, the various embodiments of this disclosure can be applied to any other suitable form of communication system besides the communication systems illustrated and described herein.

[0164] It should also be noted that although various embodiments have been described in this disclosure, several changes and modifications may be made to the various embodiments without departing from the scope of the invention.

[0165] Figure 8 A block diagram of apparatus 10 is shown by way of non-limiting and illustrative example. Apparatus 10 includes, for example, at least one processor 12 and at least one memory 14 storing instructions 15, which, when executed by the at least one processor, cause apparatus 10 to perform at least one or more methods (or portions thereof) disclosed herein, and any embodiments (or corresponding portions thereof) of the embodiments. In the example, the at least one memory and the instructions, together with the at least one processor, are configured to cause apparatus 10 to perform one or more methods (or portions thereof) disclosed herein, and any embodiments (or corresponding portions thereof) of the embodiments.

[0166] The processor 12 may include, or be configured as, one or more circuit systems configured to perform phases of the method according to the embodiments described herein.

[0167] As used herein, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation (e.g., an implementation in an analog, digital, and / or quantum circuit system) and (b) a combination of (multiple) hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuits with software / firmware; and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) with software and (multiple) memories, which work together to enable a device such as a mobile device (e.g., a user equipment), a computing device, or a server to perform various functions; and (c) any or all portions of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors, and / or (multiple) quantum processors, which require software (e.g., firmware) for operation, but may be absent when the software is not required for operation. This definition of circuit system applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations of only hardware circuitry or processors (or processors) or portions thereof and their accompanying software and / or firmware. The term "circuit system" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0168] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. For example, the memory 14 may be at least partially external to the device 10, but may be accessible from the device 10.

[0169] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on the persistence of data storage (e.g., random access memory RAM versus read-only memory ROM).

[0170] For example, device 10 may include, be included in, or implement a UE. The device may include a chipset. Device 10 may be caused or configured to at least perform... Figure 6 The method and / or any one or more embodiments (or portions thereof) of the embodiments described herein.

[0171] For example, apparatus 10 may include or be configured to provide a network entity, such as a SEAL server. The apparatus may include a chipset. Apparatus 10 may be caused or configured to at least perform... Figure 7 The method and / or any one or more embodiments (or portions thereof) of the embodiments described herein.

[0172] The device may include one or more entities of any of the protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity, or a PHY entity.

[0173] Device 10 optionally includes a radio interface 16. Radio interface 16 can provide communication capabilities to device 10. Radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. Radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. Receivers may include more than one receiver. Transmitters may include more than one transmitter. Radio interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. Transceivers may include more than one transceiver.

[0174] Device 10 may optionally include interface 18 (e.g., a user interface), which includes at least one of, for example, a keypad, microphone, touch display, display, speaker, etc. Interface 18 may be used (e.g., by a user) to control the device. Interface 18 may be external to device 10. For example, device 10 may be connected to another device, such as a computer, via a wireless or wired connection, and device 10 may be controlled by a user via the computer. In embodiments, at least some of the processes described herein may be performed by means including components for performing at least some of the described processes. Components for performing the method steps disclosed herein may include software and / or hardware components of device 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods (or portions thereof) disclosed herein and any embodiments (or corresponding portions thereof) in the embodiments. As used herein, the term “component” should be interpreted in the singular (i.e., referring to a single element) or in the plural (i.e., referring to a combination of single elements). Therefore, the term "components for [performing A, B, C]" should be interpreted as covering: either there exists only one component for performing A, B, and C, or there exists separate components for performing A, B, and C, or means for performing A, B, and C with partially or completely overlapping components. Furthermore, the term "means for performing A, means for performing B, means for performing C" should be interpreted as covering: either there exists only one component for performing A, B, and C, or there exists separate components for performing A, B, and C, or means for performing A, B, and C with partially or completely overlapping components.

[0175] In some embodiments, example 3GPP contributions are provided.

[0176] Title: Support for discontinuous coverage for satellite access

[0177] Work item code: 5GSAT_Ph3_App

[0178] Reason for change: In TR 23.700-01, it was concluded that solution #AE3 should be moved to the specification stage. The NRM server was selected as the SEAL server.

[0179] Overview of the changes: The following solutions based on AE #3 are proposed: UE mobility pattern prediction from NWDAF / ADAES; the NRM server requests NEF TN coverage information for areas where satellites are predicted to be unavailable in the UE's path, based on the UE mobility pattern and satellite coverage information; the actual UE unavailability time is calculated based on all the above information and provided to the VAL UE and the VAL server; and individual optimization requests for availability and unavailability are made to reduce the overall calculation from the UE's perspective.

[0180] First change (all new text below)

[0181] Version 8.X supports discontinuous coverage for satellite access.

[0182] 8.x.1 Overall

[0183] This process demonstrates how the NRM server obtains satellite-related information (e.g., ephemeris) from the satellite, retrieves unavailability periods for UEs with satellite access, and then exposes them to the VAL UE and the VAL server.

[0184] 8.x.2 Information Flow

[0185] TBD

[0186] 8.x.3 Procedure

[0187] Prerequisites:

[0188] 1. The SEAL server is an NRM server and the SEAL client is an NRM client.

[0189] 2. The SEAL server is provided with information for calling services from NWDAF and NEF.

[0190] 3. The VAL server has subscribed to the SEAL server to be notified of unavailability periods for VAL UEs.

[0191] Figure 9 The illustration depicts a process for supporting discontinuous coverage for satellite access, according to some embodiments.

[0192] 0. Assume that the SEAL server has already obtained the satellite ephemeris.

[0193] 1. The SEAL server may generate satellite coverage availability information based on the obtained satellite ephemeris and VAL UE location data, or, if the SEAL server receives satellite coverage availability information directly from different third parties (e.g., different satellite companies), shape it in a uniform format. An example of satellite coverage availability information can be found in Annex Q of 3GPP TS 23.501 [5].

[0194] 2. The SEAL server sends a request to the NWDAF for the UE mobility mode for the VAL UE.

[0195] 3. NWDAF provides the UE mobility mode for VAL UE in the response.

[0196] 4. Since satellite coverage availability information can indicate to the UE whether coverage is available for a specific location and time, the SEAL server configures satellite coverage availability information to the VAL UE / SEAL client via a satellite coverage availability information configuration request.

[0197] 5. If the SEAL client supports satellite access, then the SEAL client will confirm the SEAL server.

[0198] 6. The SEAL server sends a request to NEF for TN network coverage information.

[0199] 7. NEF provides TN network coverage information in its response.

[0200] 8. Based on satellite ephemeris and satellite coverage availability information, when the UE wants to directly obtain information on unavailability periods, the SEAL server can also retrieve unavailability periods (e.g., the duration of the unavailability period and the start time for that unavailability period) to guide the UE when it can trigger a UL service flow.

[0201] 9. The SEAL server sends unavailability period information to the VAL UE / SEAL client via an unavailability period information configuration request. This unavailability period information includes NTN coverage information and TN coverage information.

[0202] 10. If the SEAL client supports satellite access, the SEAL client will acknowledge the SEAL server. The SEAL client will also consider unavailability periods when operating (e.g., not sending UL messages during unavailability periods).

[0203] 11. If the VAL server periodically requests information about the VAL UE (e.g., location data), the SEAL server may notify the VAL server of the unavailability periods of the VAL UE. This unavailability period information can instruct the VAL server on how to operate to minimize service impact (e.g., extending data buffers, pending downlink data transmissions). This notification includes NTN coverage information and TN coverage information.

[0204] Change completed

[0205] Although various embodiments of this disclosure have been described with reference to non-limiting and illustrative examples based on the accompanying drawings, it is apparent that the scope of this disclosure is not limited thereto and that it can be modified in many different ways. As the technology advances, those skilled in the art will understand how this disclosure can be further implemented and / or modified in various ways. Furthermore, those skilled in the art will appreciate that the embodiments described herein can, but are not required to, be combined in various ways with other embodiments described herein.

Claims

1. An apparatus for communication, the apparatus comprising: At least one processor, and At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Receive information indicating the unavailability of the terrestrial network TN for the user equipment based on the mobility mode associated with the user equipment, and information indicating the unavailability of the non-terrestrial network NTN for the user equipment based on the mobility mode associated with the user equipment; as well as The operation is performed based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN.

2. The apparatus of claim 1, wherein the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN are received from a resource management server.

3. The apparatus according to any one of the preceding claims, wherein the resource management server includes a service enabler architecture layer for a vertical SEAL server.

4. The apparatus according to any one of the preceding claims, wherein at least one of the following: The information indicating the unavailability of the TN provides information about at least one of the location or time of the unavailability of the TN; or The information indicating the unavailability of the NTN provides information about at least one of the location or time of the unavailability of the NTN.

5. The apparatus according to any one of claims 1 to 4, wherein at least one of the following: The information indicating the unavailability of the TN provides information about at least one of the location or time associated with higher congestion of the TN; or The information indicating the unavailability of the NTN provides information about at least one of the location or time associated with higher congestion of the TN.

6. The apparatus according to any one of the preceding claims, wherein it operates based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN, for not sending an uplink message to the corresponding one of the NTN network and the TN when the corresponding one of the NTN and the TN is unavailable or has higher congestion.

7. The apparatus according to any one of the preceding claims, wherein it operates based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN, for not performing a cell search with respect to the NTN network and the corresponding one of the TN when the corresponding one of the NTN and the TN is unavailable or has higher congestion.

8. The apparatus according to any one of the preceding claims, wherein it operates based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN, for determining whether a switch from one of the NTN and TN to the other of the NTN and TN will occur based on the unavailability or higher congestion of the other of the NTN and TN.

9. The apparatus according to claim 5 or any claim dependent to claim 5, wherein it operates based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN, for selecting a corresponding one of the NTN and the TN with lower congestion using the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN.

10. The apparatus according to claim 2 or any claim dependent to claim 2, wherein the receiving is configured to receive a request from the resource management server for satellite coverage availability information for the apparatus.

11. The apparatus of claim 9, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least: send a response to the resource management server to the request for satellite coverage availability information for the apparatus, the response including information indicating that the apparatus supports satellite access.

12. The apparatus according to claim 3 or any one of claims 4 to 11 when dependent on claim 3, wherein the apparatus provides SEAL client functionality.

13. An apparatus for communication, the apparatus comprising: At least one processor, and At least one memory stores instructions that, when executed by the at least one processor, cause the device to perform at least the following: Based on the mobility pattern associated with the user equipment, information indicating the unavailability of the terrestrial network TN for the user equipment is determined, and based on the mobility pattern associated with the user equipment, information indicating the unavailability of the non-terrestrial network NTN for the user equipment is determined. as well as The information indicating the unavailability of the TN and the information indicating the unavailability of the NTN are sent to the user equipment.

14. The apparatus of claim 13, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform at least: Request information about the mobility pattern associated with the user equipment; and Receive the information regarding the mobility mode associated with the user equipment.

15. The apparatus of claim 13 or 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus to perform at least: Request information regarding the unavailability of the TN; and Receive the information regarding the unavailability of the TN.

16. The apparatus according to any one of claims 13 to 15, wherein determining the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN uses at least one of the following: The information regarding the unavailability of the TN; The satellite coverage information for the NTN; or The information regarding the mobility pattern associated with the user equipment.

17. The apparatus according to any one of claims 13 to 16, wherein at least one of the following: The information indicating the unavailability of the TN, based on the mobility pattern associated with the user equipment, provides information about at least one of the location or time of the unavailability of the TN; The information indicating the unavailability of the NTN, based on the mobility pattern associated with the user equipment, provides information about at least one of the location or time of the unavailability of the NTN; The information indicating the unavailability of the TN, based on the mobility pattern associated with the user equipment, provides information about at least one of the location or time associated with higher congestion of the TN; or The information indicating the unavailability of the NTN provides information about at least one of the location or time associated with higher congestion of the TN, based on the mobility patterns associated with the user equipment.

18. A method for communication, the method comprising: Receive information indicating the unavailability of the terrestrial network TN for the user equipment based on the mobility mode associated with the user equipment, and information indicating the unavailability of the non-terrestrial network NTN for the user equipment based on the mobility mode associated with the user equipment; as well as The operation is performed based on the information indicating the unavailability of the TN and the information indicating the unavailability of the NTN.

19. A method for communication, the method comprising: Based on the mobility pattern associated with the user equipment, information indicating the unavailability of the terrestrial network TN for the user equipment is determined, and based on the mobility pattern associated with the user equipment, information indicating the unavailability of the non-terrestrial network NTN for the user equipment is determined. as well as The information indicating the unavailability of the TN and the information indicating the unavailability of the NTN are sent to the user equipment.

20. A computer program product comprising computer-executable instructions, which, when executed, cause the method of claim 18 or the method of claim 19 to be performed.

Images