WO2025244366A1

WO2025244366A1 - Managing connection procedures of a user equipment in a satellite communication system

Info

Publication number: WO2025244366A1
Application number: PCT/KR2025/006710
Authority: WO
Inventors: Basavaraj Jayawant Pattan; Sapan Pramodkumar SHAH
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2024-05-18
Filing date: 2025-05-16
Publication date: 2025-11-27
Anticipated expiration: 2026-11-18

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a User Equipment (UE) in a wireless communication system is provided. The method includes identifying a target Edge Enabler Server (EES). The method includes identifying a target Edge Application Server (EAS) associated with the target EES with EAS discovery. An Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS. In case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.

Description

MANAGING CONNECTION PROCEDURES OF A USER EQUIPMENT IN A SATELLITE COMMUNICATION SYSTEM

This application is based on and derives the benefit of Indian Provisional Application 202441039066 filed on 18^th May 2024, the contents of which are incorporated herein by reference. The disclosure relate to a wireless communication and satellite communication, more particularly, to managing connection procedures of a User Equipment (UE) in the satellite communication system.

5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

Moreover, there has been ongoing standardization in air interface architecture/protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture/service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

In an embodiment of the disclosure, a method performed by a User Equipment (UE) in a wireless communication system is provided. The method includes identifying a target Edge Enabler Server (EES). The method includes identifying a target Edge Application Server (EAS) associated with the target EES with EAS discovery. In an embodiment of the disclosure, an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS. In an embodiment of the disclosure, in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.

In an embodiment of the disclosure, the target EAS and the target EES are deployed on the satellite.

In an embodiment of the disclosure, an Edge Configuration Server (ECS) is deployed on ground, and the UE is located at least one of on ground, on sea, or in air.

In an embodiment of the disclosure, a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) is deployed on the satellite.

In an embodiment of the disclosure, the method includes storing information associated with at least one of the target EES or the target EAS along with a satellite Identifier (ID) of the satellite. In an embodiment of the disclosure, the method includes, in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, identifying, based on the satellite ID, that the UE stores the information associated with at least one of the target EES or the target EAS. In an embodiment of the disclosure, the EEC reconnects to the target EES and target EAS based on the stored information without repetition of EES discovery and the EAS discovery.

In an embodiment of the disclosure, a method performed by a satellite in a wireless communication system is provided. The method includes providing a service of a target Edge Enabler Server (EES) and a target Edge Application Server (EAS) to a User Equipment (UE). In an embodiment of the disclosure, the target EES is identified at the UE. In an embodiment of the disclosure, the target EAS is identified with EAS discovery at the UE. In an embodiment of the disclosure, an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS. In an embodiment of the disclosure, in case that the satellite comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.

In an embodiment of the disclosure, a User Equipment (UE) in a wireless communication system comprising at least one memory and at least one processor coupled to the at least one memory is provided. The at least one processor is configured to identify a target Edge Enabler Server (EES). The at least one processor is configured to identify a target Edge Application Server (EAS) associated with the target EES with EAS discovery. In an embodiment of the disclosure, an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS. In an embodiment of the disclosure, in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.

In an embodiment of the disclosure, a satellite in a wireless communication system comprising at least one memory and at least one processor coupled to the at least one memory is provided. The at least one processor is configured to provide a service of a target Edge Enabler Server (EES) and a target Edge Application Server (EAS) to a User Equipment (UE). In an embodiment of the disclosure, the target EES is identified at the UE. In an embodiment of the disclosure, the target EAS is identified with EAS discovery at the UE. In an embodiment of the disclosure, an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS. In an embodiment of the disclosure, in case that the satellite comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications.

These and other features, aspects, and advantages of the present disclosure are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

FIG. 1 is a schematic representation that illustrates a satellite-based edge computing deployment architecture with the EES and the EAS implemented onboard the satellite according to an embodiment of the disclosure;

FIG. 2 is a block diagram that illustrates the UE for managing connection procedures in the satellite communication system according to an embodiment of the disclosure;

FIG. 3 is a block diagram that illustrates the serving satellite for managing connection procedures of the UE in the satellite communication system according to an embodiment of the disclosure;

FIG. 4 is a flowchart that illustrates a method, performed by the UE, for managing connection procedures of the UE in the satellite communication system according to an embodiment of the disclosure;

FIG. 5 is a flowchart that illustrates a method, performed by the serving satellite, for managing connection procedures of the UE in the satellite communication system according to an embodiment of the disclosure;

FIG. 6 is a flowchart that illustrates a method for mitigating the wastage of ECS or EDN resources in the satellite communication system according to an embodiment of the disclosure;

FIG. 7 is a flowchart illustrating a method performed by a UE in a wireless communication system according to an embodiment of the disclosure; and

FIG. 8 is a flowchart illustrating a method performed by a satellite in a wireless communication system according to an embodiment of the disclosure.

The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments.

The term "or" as used herein, refers to a non-exclusive or, unless otherwise indicated.

Hereinafter, "A or B" as described in the present disclosure may be understood as "A and/or B," which may include A, or B, or both A and B. Furthermore, "A/B" as described in the present disclosure may be understood as "A and/or B," which may include A, or B, or both A and B. Furthermore, "A, B" as described in the present disclosure may be understood as "A and/or B," which may include A, or B, or both A and B. Furthermore, "A and B" as described in the present disclosure may be understood as "A and/or B," which may include A, or B, or both A and B.

In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C. In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples are not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions. These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method. Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

The accompanying drawings facilitate understanding of various technical features. The embodiments are not limited by these drawings and extend to any alterations, equivalents, and substitutes. Terms like first, second, etc., are used for distinction and do not limit the elements.

The Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.558 defines an application layer architecture and corresponding procedures for enabling edge applications over 3GPP networks. This specification outlines the framework and methodologies that facilitate the deployment and operation of edge computing applications, which are used for reducing latency and improving the performance of services delivered to end users. Additionally, the 3GPP Technical Report (TR) 23.700-01 extends these concepts to the deployment of edge computing onboard satellites, thereby broadening the scope of edge computing to include scenarios where terrestrial connectivity might be limited or unavailable.

In the current architecture, during the initial service discovery phase, an Edge Enabler Client (EEC) within the User Equipment (UE) establishes communication with an Edge Configuration Server (ECS) via the EDGE-4 interface. This communication can occur through either a terrestrial or satellite link, and its purpose is to identify a suitable Edge Enabler Server (EES). Following this, during the Edge Application Server (EAS) discovery phase via the EDGE-1 interaction, an appropriate EAS instance is selected for the UE. Finally, the Application Client (AC) in the UE communicates with the chosen EAS to deliver the desired edge services.

However, several challenges arise in the context of satellite-based edge computing. One significant issue is the discontinuous coverage and the dynamic nature of satellite connectivity. Due to reasons such as the satellite being in motion or temporary obstructions, the UE may get disconnected from satellite access, leading to service disruptions. Even with the availability of Inter-Satellite Links (ISL), which can potentially provide service continuity from another satellite, there is still the problem of minimum disruption of service when switching between satellites.

Each time the UE disconnects and reconnects to satellite access, it is required to repeat the procedures of service provisioning and the EAS discovery to select an appropriate EAS. This repetitive process occurs regardless of whether the ISL is available or not, and it results in the same connection details being provided to the Edge Data Network (EDN) and the EAS. Consequently, the repeated execution of these procedures each time the UE reconnects to satellite access leads to unnecessary wastage of ECS/EDN resources.

The inefficiency of the current system is evident, as the process of repeating service provisioning and EAS discovery each time the UE reconnects to satellite access could be optimized.

Thus, it is desired to address the above-mentioned disadvantages, issues, or other shortcomings or at least provide a useful alternative.

The principal object of the disclosure is to manage connection procedures of the UE in the satellite communication system.

Yet another object of the disclosure is to provide a method for mapping the EES and the EAS connection information with a Satellite Identifier (Satellite ID). Further, the method reduces the wastage of the ECS and the EDN resources during the UE reconnection to the satellite access.

Yet another object of the disclosure is to optimize service continuity by reducing redundant service provisioning and the EAS discovery procedures each time the UE reconnects to a satellite. This is achieved by leveraging the previously stored mapping of the EES or EAS connection details with the corresponding satellite ID.

FIG. 1 is a schematic representation that illustrates a satellite-based edge computing deployment architecture with the EES and the EAS implemented onboard the satellite, according to an embodiment of the disclosure.

FIG. 1 may be described with reference to Clause 7.2.3.1.1.1 of 3GPP TR 23.700-01 V0.3.0. The FIG. 1 represents a satellite communication system that includes both space-based and ground-based components. In the space section, multiple satellites (102a and 102b) are depicted with inter-satellite communication capabilities. Edge computing functionalities, including the EES (108) and the EAS (107), are deployed on one or more satellites, while the ECS (110) is deployed on the ground. The UE may be located on the ground, at sea, or in the air (e.g., a drone).

In an embodiment of disclosure, a User Plane Function (UPF) (105a) may be deployed on the satellite to facilitate access to the EDN (106) in the satellite. In an embodiment of disclosure, a UPF (105b) may be deployed on the ground. The Radio Access Network (RAN), such as a gNodeB (104a, 104b), may be deployed on the ground (e.g., in a ship) and connected to the satellite UPF (105a) or on a regenerative satellite where the RAN components reside onboard on the serving satellite itself. The 5G System (5GS) control plane functions, including an Access and Mobility Management Function (AMF) and a Session Management Function (SMF), may be deployed on the ground. The EAS (107) instances and their registered EES instances may be distributed across multiple satellites, forming the EDN (106), with the coverage areas of these satellites corresponding to the EDN (106) service area.

To facilitate communication, the EEC in the UE (101) may contact the ECS (110) through an EDGE-4 (either through ground-based or satellite links) (112) to discover a suitable EES (108). Once the EES is identified, the EAS (107) discovery may be performed through an EDGE-1 (111), selecting appropriate EAS (107) instances. The Application Client (AC) in the UE (101) then may communicate with the selected EAS (107) for service execution. However, due to challenges such as satellite motion and discontinuous coverage, the UE (101) may experience frequent disconnections from satellite access, leading to service disruptions. Even with an Inter-Satellite Link (ISL) available, service continuity can be ensured with minimal disruption by switching to another satellite.

In the existing system, every time the UE (101) disconnects and reconnects to satellite access, UE repeats service provisioning and the EAS (107) discovery procedures. This results in redundant computations because the same satellite may eventually serve the UE (101) again, and the connection details for the EDN (106) and the EAS (107) remain unchanged. Therefore, the existing process leads to unnecessary consumption of the ECS (110) or the EDN (106) resources, highlighting inefficiencies in the current system.

FIG.2 is the block diagram that illustrates the UE for managing connection procedures in the satellite communication system, according to an embodiment of the disclosure.

Examples of the UE (200) may include, but are not limited to, Consumer Electronics (such as Mobile Phones and Smartphones), Tablets, Wearable Devices, Television, Computing Devices (such as Laptops, Notebooks, Desktops, Workstations, etc.), IoT Devices, Automotive Systems (such as connected cars, Autonomous Vehicles, Vehicle-to-Everything (V2X) communication devices, etc.), Enterprise Devices such as robotics, Specialized Equipment (such as Medical Devices, Public Safety Devices, etc.), Media Devices (such as Gaming Consoles, Streaming Devices, etc.).

Examples of the wireless communication network system may include, but are not limited to, Cellular Networks (such as 2G, 3G, 4G, 5G, Beyond 5G (B5G)/6G, or advanced cellular networks), Local Area Networks (LANs) (such as Wi-Fi, Li-Fi, etc.), Personal Area Networks (PANs) (such as Bluetooth, Zigbee, Z-Wave, etc.), Wide Area Networks (WANs) (such as Satellite Communication Networks, Long Range Wide Area Network, Narrowband IoT, Low-bandwidth communication for IoT, etc.), Metropolitan Area Networks (MANs), Machine-to-Machine (M2M), Ad Hoc and Mesh Networks, Emerging and Advanced Networks.

The UE (200) may include the processor (210), the memory (220), an I/O interface (230) and a EES-EAS connection information controller (240). The processor (210) of the UE (200) may communicate with the memory (220), the I/O interface (230) and the EES-EAS connection information controller (240). The processor (210) is configured to execute instructions stored in the memory (220) and to perform various processes. The processor (210) may include one or a plurality of processors. The processor (210) may include a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

The memory (220) of the UE (200) may include storage locations to be addressable through the processor (210). The memory (220) is not limited to a volatile memory and/or a non-volatile memory. The memory (220) may include one or more computer-readable storage media. The memory (220) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. The memory (220) may include the EES-EAS connection information, satellite Identifier (ID), EES connection information, the EAS connection information, and reconnection parameters. The memory may include storage for the EEC software module, service endpoints, authentication credentials, and satellite metadata.

The I/O interface (230) may transmit the information between the memory (220) and external peripheral devices. The peripheral devices may be the input-output devices associated with the UE (200). The I/O interface (230) may receive several information from the UE (200).

The EES-EAS connection information controller (240) may be coupled to the memory (220) and the processor (210). This coupling allows for efficient data transfer and communication between the components, ensuring that the EES-EAS connection information controller (240) may access and process connection data in real-time. The EES-EAS connection information controller (240) may be an innovative integrated circuit that is implemented in the serving satellite (300). In an embodiment of the disclosure, the structure of such innovative integrated circuit may include a multi-core architecture that enables dynamic management of EES-EAS connection information in the satellite communication system. Each core may be optimized for specific tasks, such as connection state monitoring, service continuity management, and adjusting reconnection procedures, etc. The innovative integrated circuit for the management of EES-EAS connection information in the satellite communication system may be made of a combination of analog and digital components designed to optimize the power consumption and performance of the connection management mechanism. The analog components may include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components may include a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically manage the EES-EAS connection information based on satellite coverage conditions.

The EES-EAS connection information controller (240) may initiate the connection between the EEC of the UE (200) and the EAS (107) onboard satellite upon initial EAS discovery via satellite access. This initiation process may include scanning for available satellite signals and identifying the EAS (107) through a unique identifier broadcasted by the satellite. The EES-EAS connection information controller (240) then may establish a secure communication channel using encryption protocols to ensure data integrity and confidentiality. The EES-EAS connection information controller (240) may perform authentication procedures to verify the identity of the UE (200) before allowing access to the EAS (107).

The EES-EAS connection information controller (240) may store the EES (108) and the EAS (107) connection information at the memory (220) of the UE (200) along with the satellite Identifier (ID) of the serving satellite (300) that provides the EES (108) and EAS (107) services to the EEC. This storage process may include creating a data structure that maps the satellite ID to the corresponding EES and EAS connection parameters, such as IP addresses, port numbers, and encryption keys. The memory (220) may be organized to allow quick retrieval of this information, minimizing the time required for reconnection. The EES-EAS connection information controller (240) may periodically update this information to account for any changes in the satellite's configuration or service parameters.

The EES-EAS connection information controller (240) may detect the discontinuous coverage period during which the serving satellite (300) temporarily ceases to provide the EES (108) and EAS (107) services to the EEC. This detection may be achieved through continuous monitoring of the signal strength and quality metrics, such as signal-to-noise ratio (SNR) and bit error rate (BER). When these metrics fall below a predefined threshold, the EES-EAS connection information controller (240) may log the event and initiate a timer to track the duration of the coverage gap. The EES-EAS connection information controller (240) may send notifications to the UE (200) to inform the user about the temporary service interruption.

Upon re-establishment of coverage by the serving satellite (300) with the stored satellite Identifier, the EES-EAS connection information controller (240) may reconnect the EEC to the same EES (108) and EAS (107) to which the EEC was previously connected based on the stored EES (108) and EAS (107) connection information. The reconnection process may include validating the satellite ID against the stored information and re-establishing the secure communication channels using the previously stored encryption keys. The EES-EAS connection information controller (240) may perform a quick integrity check to ensure that the connection parameters have not been tampered with during the coverage gap. This seamless reconnection process may ensure minimal disruption to the user's experience.

The UE (200) may directly reconnect to the EEC to the same EES (108) and EAS (107), bypassing the service provisioning and the EAS (107) discovery procedures. This direct reconnection may be facilitated by the pre-stored connection information, which eliminates the need for the UE (200) to undergo the time-consuming process of rediscovering the EAS (107) and re-establishing service provisioning. The EES-EAS connection information controller (240) may use a fast reconnection algorithm that prioritizes the restoration of communication links, ensuring that the UE (200) can resume normal operations as quickly as possible.

The EES-EAS connection information controller (240) may reconnect the EEC to the same EES (108) and EAS (107) to which the EEC was previously connected based on the stored EES (108) and EAS (107) connection information. This reconnection process may include verifying the integrity and validity of the stored connection information before re-establishing the communication links. The EES-EAS connection information controller (240) may perform a quick synchronization check to ensure that the EES (108) and EAS (107) are in a consistent state with the UE (200). This ensures that any data or service state changes that occurred during the coverage gap are properly accounted for.

The EES-EAS connection information controller (240) may determine whether the memory of the UE (200) includes the EES (108) and the EAS (107) connection information for the satellite ID of the serving satellite (300) that previously provided the EES and the EAS (107) services to the EEC upon re-establishment of the coverage by the serving satellite (300). This determination process may include querying the memory (220) for the presence of the relevant connection information and verifying its integrity using checksums or cryptographic hashes. If the information is found to be valid, the EES-EAS connection information controller (240) may proceed with the reconnection process; otherwise, it may initiate the service provisioning and discovery procedures.

The EES-EAS connection information controller (240) may reconnect the EEC directly to the EES (108) and the EAS (107) based on the stored EES (108) and EAS (107) connection information without requiring the EEC to rediscover the EES (108) and the EAS (107) connection information when the memory (220) of the UE (200) includes the EES (108) and the EAS connection information for the satellite ID. This direct reconnection may be achieved through the use of a fast reconnection protocol that leverages the pre-stored connection parameters to quickly re-establish the communication links. The EES-EAS connection information controller (240) may perform a quick validation check to ensure that the stored information is still valid and has not been compromised.

The EES-EAS connection information controller (240) may initiate the service provisioning and the EAS (107) discovery procedures when the memory (220) of the UE (200) does not include the EES (108) and the EAS (107) connection information for the satellite ID of the serving satellite (300). This initiation process may include scanning for available satellite signals, identifying the EAS (107) through its unique identifier, and establishing a secure communication channel. The EES-EAS connection information controller (240) then may perform the authentication and authorization procedures to provision the EES (108) and EAS (107) services for the UE (200).

The EES-EAS connection information controller (240) may store the EES (108) and the EAS (107) connection information, including building a mapping between the satellite ID and the EES (108) and the EAS connection information per application over time for an application. This mapping process may include creating a data structure that associates each satellite ID with the corresponding connection parameters for each application running on the UE (200). The EES-EAS connection information controller (240) may periodically update this mapping to account for any changes in the satellite's configuration or service parameters, ensuring that the UE (200) always has the most up-to-date connection information.

The EES-EAS Connection Information Controller (240) may manage the connection information between the EES (108), which is deployed on the ground, and the UE (200), which may be located on the ground, at sea, or in the air. This management process may include monitoring the connection quality and adjusting the communication parameters as needed. The EES-EAS connection information controller (240) may handle handovers between different satellites or ground stations to ensure seamless connectivity for the UE (200) regardless of its location.

The EES-EAS Connection Information Controller (240) may manage the connection information while the UPF is deployed on the serving satellite (300) to access the EDN (106). Both the EAS (107) and the EES (108) may be deployed on the serving satellite (300). This management process may include coordinating the communication between the UPF, EAS, and EES to ensure efficient data routing and service delivery. The EES-EAS connection information controller (240) may handle any protocol conversions or data encapsulations to facilitate seamless communication between the different network elements.

In an embodiment of the disclosure, the EES-EAS Connection Information Controller (240) may be included in the processor (210). In an embodiment of the disclosure, one or more operations of the EES-EAS Connection Information Controller (240) may be executed by the processor (210). In an embodiment of the disclosure, the processor (210) may be configured to execute one or more operations of the EES-EAS Connection Information Controller (240).

FIG.3 is the block diagram that illustrates the serving satellite for managing connection procedures of the UE in the satellite communication system, according to an embodiment of the disclosure.

Examples of the serving satellite (300) may include, but are not limited to, Low Earth Orbit (LEO) Satellites, Medium Earth Orbit (MEO) Satellites, Geostationary Earth Orbit (GEO) Satellites, Communication Satellites (such as broadband internet satellites, telecommunication relay satellites), Earth Observation Satellites (equipped with communication capabilities), Navigation Satellites (such as GPS, GLONASS, Galileo, BeiDou systems), Weather Satellites (with communication payloads), Research Satellites (with experimental communication systems), CubeSats and SmallSats (for specialized communication services), Constellation Network Nodes (such as those in Starlink, OneWeb, Kuiper systems), Military Communication Satellites, Intersatellite Communication Relay Nodes, Polar Orbit Communication Satellites, High-Throughput Satellites (HTS), and Software-Defined Satellite (SDS) platforms.

The serving satellite (300) may include a processor (310), a memory (320), an I/O interface (330) and a EES-EAS Connection Information Controller (340). The serving satellite (300) may communicate with the UE (200) via radio frequency signals to establish and maintain connectivity for providing EES and EAS services to the EEC. The processor (310) of the serving satellite (300) may communicate with the memory (320), the I/O interface (330) and the EES-EAS Connection Information Controller (340). The processor (310) may be configured to execute instructions stored in the memory (320) and to perform various processes. The processor (310) may include one or a plurality of processors. The processor (310) may include a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

The memory (320) of the serving satellite (300) may include storage locations to be addressable through the processor (310). The memory (320) is not limited to a volatile memory and/or a non-volatile memory. The memory (320) may include one or more computer-readable storage media. The memory (320) may include non-volatile storage elements. For example, non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.

The I/O interface (330) may transmit the information between the memory (320) and external peripheral devices. The peripheral devices may be the input-output devices associated with the serving satellite (300). The I/O interface (330) may receive several information from the serving satellite (300).

The EES-EAS connection information controller (340) may be coupled to the memory (320) and the processor (310). This coupling allows for efficient data transfer and communication between the components, ensuring that the EES-EAS connection information controller (340) can access and process connection data in real-time. The EES-EAS connection information controller (340) may be an innovative integrated circuit that is implemented in the serving satellite (300). In an embodiment of the disclosure, the structure of such innovative integrated circuit may include a multi-core architecture that enables dynamic management of EES-EAS connection information in a satellite communication system. Each core may be optimized for specific tasks, such as signal processing, connection state monitoring, and service continuity management, etc. The innovative integrated circuit for the dynamic management of EES-EAS connection information in the satellite communication system may be made of a combination of analog and digital components designed to optimize the power consumption and performance of the connection management mechanism. The analog components may include a low-noise amplifier and a high-precision analog-to-digital converter to ensure accurate signal processing. The digital components may include a microcontroller unit (MCU) and a digital signal processor (DSP) that work in tandem to dynamically manage the EES-EAS connection information based on satellite coverage conditions.

The EES-EAS connection information controller (340) may provide the EES (108) and the EAS (107) to the EEC at the UE (200). The EES-EAS connection information controller (340) may detect a discontinuous coverage period during which the serving satellite (300) is temporarily ceases to provide the EES (108) and EAS service to the EEC. Upon re-establishment of coverage by the serving satellite (300) with the stored satellite Identifier, the EES-EAS connection information controller (340) may reconnect the EEC of the UE (200) to the same EES (108) and EAS (107) to which the EEC was previously connected, without requiring the EEC to rediscover the EES (108) and EAS (107) connection information.

The EES-EAS connection information controller (340) may deploy the EES (108) on the ground, and the UE (200) may be located on one of the ground, sea, or in the air. The controller (340) may be responsible for managing the communication links between the EES (108) and the UE (200), ensuring that data transmission is optimized based on the UE's location. This may include dynamically adjusting the communication parameters to account for varying signal strengths and latencies. The controller (340) may monitor the network conditions and may reconfigure the deployment of the EES (108) to maintain performance.

The EES-EAS connection information controller (340) in the serving satellite (300) may include the UPF. The UPF may be to access the satellite EDN (106) and may be deployed on the serving satellite (300), and the EAS (107) and the EES (108) may be deployed on the serving satellite (300). The UPF (User Plane Function) may handle the data forwarding between the satellite network and the terrestrial network. It ensures that data packets are routed efficiently, minimizing latency and maximizing throughput. The integration of the EAS (Edge Application Server) and the EES (Edge Execution Server) on the satellite allows for localized processing of data, reducing the need for data to travel back to a central data center, thus improving response times for the end-user.

The serving satellite (300) may include the EES-EAS Connection Information Controller (340), which manages the deployment of the EES (108) on the ground while the UE (200) may be located on the ground, at sea, or in the air. The controller (340) may ensure that the EES (108) is strategically positioned to provide the best possible service to the UE (200), regardless of its location. This may include using advanced algorithms to predict the movement of the UE (200) and adjusting the deployment of the EES (108) accordingly. The controller (340) may coordinate with other satellites in the network to provide seamless coverage and handover as the UE (200) moves.

The serving satellite (300) may include the EES-EAS Connection Information Controller (340), which integrates the UPF to facilitate access to the EDN (106). Both the EAS (107) and the EES (108) may be deployed on the serving satellite (300), ensuring seamless edge computing capabilities. The integration of these components allows for real-time processing of data at the edge of the network, reducing the load on the central data centers and improving the overall efficiency of the network. The EAS (107) may provide the computational resources for running applications, while the EES (108) handles the execution of these applications, ensuring that they run smoothly and efficiently. This setup is particularly beneficial for latency-sensitive applications, such as autonomous vehicles and remote surgery.

In an embodiment of the disclosure, the EES-EAS Connection Information Controller (340) may be included in the processor (310). In an embodiment of the disclosure, one or more operations of the EES-EAS Connection Information Controller (340) may be executed by the processor (310). In an embodiment of the disclosure, the processor (310) may be configured to execute one or more operations of the EES-EAS Connection Information Controller (340).

FIG.4 is the flowchart that illustrates a method, performed by the UE, for managing connection procedures of the UE in the satellite communication system according to an embodiment of the disclosure.

In operation 410, the method may include initiating the connection between the EEC of the UE (200) and the EAS (107) onboard the satellite upon initial EAS discovery via satellite access. The operation may include, by the UE (200), scanning for available satellites and establishing a communication link with the EAS (107) using predefined protocols. The initial connection setup may include authentication procedures and the exchange of credentials to ensure secure communication.

In operation 420, the method may include storing the EES (108) and the EAS (107) connection information in the memory of UE (200) along with a satellite ID of the serving satellite (300) that provides the EES (108) and EAS (107) services to the EEC. The connection information may include information such as EES ID, EES Endpoint, EAS information, EAS information and list of EAS bundle information. This information may be stored in a non-volatile memory to ensure it is retained even if the UE (200) is powered off. The satellite ID may be used to uniquely identify the serving satellite and facilitate quick reconnection.

In operation 430, the method may include detecting the discontinuous coverage period during which the serving satellite (300) temporarily ceases to provide the EES (108) and the EAS (107) services to the EEC. This detection may be achieved through monitoring signal strength, quality metrics, and timing information. The UE (200) may use algorithms to predict coverage gaps based on the satellite's orbital parameters and historical data. During this period, the UE (200) may enter a low-power state to conserve battery life.

In operation 440, the method may include re-establishing coverage with the serving satellite (300) matching the stored satellite ID and reconnecting the EEC to the previously connected EES (108) and EAS (107) using the stored connection data. The method may include bypassing the service provisioning and the EAS discovery procedures by leveraging the stored EES (108) and EAS (107) connection information, ensuring seamless reconnection while optimizing ECS/EDN resource utilization. The UE (200) may use the stored parameters to quickly re-establish the communication link, reducing latency and improving user experience. The operation may include re-authentication using previously exchanged credentials.

FIG.5 is the flowchart that illustrates a method, performed by the serving satellite, for managing connection procedures of the UE in the satellite communication system according to an embodiment of the disclosure.

In operation 510, the method may include providing the EES (108) and the EAS (107) to the EEC at the UE (200) through the serving satellite (300). The satellite (300) may broadcast its availability and service capabilities, allowing the UE (200) to initiate and maintain a connection. The satellite's onboard systems may manage multiple connections simultaneously, ensuring efficient resource allocation.

In operation 520, the method may include detecting the discontinuous coverage period experienced during which the serving satellite (300) temporarily ceases to provide the EES and the EAS (107) services to the EEC. The satellite (300) may monitor its coverage area and inform connected UEs (200) of impending coverage gaps. This detection may include real-time analysis of orbital dynamics and environmental factors affecting signal propagation.

In operation 530, the method may include re-establishing coverage and reconnecting the EEC to the previously connected EES (108) and EAS (107) through the serving satellite (300) without requiring the EEC to rediscover the EES (108) and the EAS (107) connection information. The satellite (300) may use the stored connection data to facilitate a quick reconnection process. This operation may minimize the time the UE (200) spends without service, enhancing overall system reliability and user satisfaction.

FIG.6 is the flowchart that illustrates the method for mitigating the wastage of ECS or EDN resources in the satellite communication system according to an embodiment of the disclosure.

In operation 610, the method may include initiating communication between the Application Client (AC) in the UE (200) and the selected EAS (107) onboard the serving satellite (300) after the initial EAS discovery through the satellite access. The AC in the UE (200) may send a request to the EAS (107) to establish a session, which includes application-specific parameters and requirements.

In operation 620, the method may include storing the EES (108) and the EAS (107) connection information along with the Satellite ID of the serving satellite (300) in the UE's (200) memory (220) for an application. The stored mapping information between the satellite ID and the EES or EAS connection details may be accumulated over time for several applications. This information may be organized in a structured format, allowing quick access and updates. The memory (220) may use indexing techniques to efficiently manage multiple entries.

In operation 630, the method may include detecting the discontinuous coverage period during which the UE (200) experiences the temporary disconnection from satellite access due to factors such as satellite motion or disruptions in coverage. The UE (200) may monitor signal quality and other metrics to detect coverage loss. Advanced algorithms may predict coverage gaps based on the satellite's trajectory and environmental conditions.

In operation 640, the method may include reconnecting the UE (200) to satellite access once coverage is restored and the application is initiated. The UE (200) first may verify if the stored memory (220) contains the EES or EAS (107) connection information for the connected satellite ID. This verification process may include checking the integrity and validity of the stored data. If the data is valid, the UE (200) may proceed with the reconnection process.

In operation 650, the method may include performing the standard service provisioning and the EAS discovery as per prior art when the UE (200) memory lacks the connection information in order to establish the connection with the selected EAS (107). The operation may include a full discovery and provisioning process, including authentication, capability exchange, and session setup. The UE (200) may use fallback mechanisms to ensure connectivity even if the stored data is unavailable.

In operation 660, the method may include directly reconnecting the UE (200) to the previously connected EES (108) and EAS (107) when the UE (200) memory (220) contains the EES/EAS connection information, thereby bypassing service provisioning and EAS discovery, optimizing resource utilization, and mitigating the wastage of the ECS or EDN resources. The operation may ensure a quick and efficient reconnection process, reducing the load on the satellite's resources and improving overall system performance.

FIG. 7 is a flowchart illustrating a method performed by a UE in a wireless communication system according to an embodiment of the disclosure.

In operation 710, the UE may identify a target Edge Enabler Server (EES).

In operation 720, the UE may identify a target Edge Application Server (EAS) associated with the target EES with EAS discovery.

In an embodiment of the disclosure, an Edge Enabler Client (EEC) of the UE may connect to at least one of the target EES or the target EAS.

In an embodiment of the disclosure, in case that a satellite providing a service of at least one of the target EES or the target EAS comes back for serving based on a discontinuous coverage, the EEC may reconnect to at least one of the target EES or the target EAS without repetition of at least one of EES discovery or the EAS discovery.

In an embodiment of the disclosure, at least one of the target EAS or the target EES may be deployed on the satellite.

In an embodiment of the disclosure, an Edge Configuration Server (ECS) may be deployed on ground. In an embodiment of the disclosure, the UE may be located at least one of on ground, on sea, or in air.

In an embodiment of the disclosure, a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) may be deployed on the satellite.

In an embodiment of the disclosure, the UE may store information associated with at least one of the target EES or the target EAS. In an embodiment of the disclosure, the UE may store information associated with at least one of the target EES or the target EAS along with a satellite Identifier (ID) of the satellite.

In an embodiment of the disclosure, in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the UE may identify, based on the satellite ID, that the UE stores the information associated with at least one of the target EES or the target EAS. In an embodiment of the disclosure, the EEC may reconnect to at least one of the target EES or target EAS based on the stored information without repetition of at least one of EES discovery or the EAS discovery.

In operation 810, the satellite may provide a service of a target Edge Enabler Server (EES) and a target Edge Application Server (EAS) to a User Equipment (UE).

In an embodiment of the disclosure, the satellite may provide a service of at least one of a target Edge Enabler Server (EES) or a target Edge Application Server (EAS) to a User Equipment (UE). In an embodiment of the disclosure, the target EES may be identified at the UE. In an embodiment of the disclosure, the target EAS may be identified with EAS discovery at the UE. In an embodiment of the disclosure, the EEC of the UE may connect to at least one of the target EES or the target EAS.

In an embodiment of the disclosure, in case that the satellite comes back for serving based on a discontinuous coverage, the EEC may reconnect to at least one of the target EES or the target EAS without repetition of at least one of EES discovery or the EAS discovery.

In an embodiment of the disclosure, the proposed method applies to both stationary and mobile UEs, ensuring efficient resource utilization regardless of movement conditions. The system dynamically adapts to the UE's mobility, optimizing connection procedures based on real-time location and movement patterns.

In an embodiment of the disclosure, the stored mapping information is updated when the EES or EAS (107) connection information changes. This ensures that the UE (201) has the latest connection parameters, enhancing reliability and reducing the likelihood of connection failures.

In an embodiment of the disclosure, the resource wastage mitigation may apply only to the EAS (107) discovery while service provisioning might still be required. This selective optimization allows for flexibility in managing different types of connections and services.

In an embodiment of the disclosure, the mapping information between the satellite ID and the EES or EAS (107) connection details may be stored per application outside the UE (201), such as in the ECS (110). This centralized storage approach allows for better management and synchronization of connection data across multiple UEs.

In an embodiment of the disclosure, the UE (201) is capable of determining when to perform service provisioning and the EAS (107) discovery and when to bypass these procedures. The UE (201) uses intelligent algorithms to make these decisions based on current conditions and historical data.

In an embodiment of the disclosure, when the ISL is available, the same EES/EAS connection information may be used to minimize service disruption and avoid repeating service provisioning and the EAS (107) discovery procedure. The ISL provides an additional layer of connectivity, enhancing the robustness and reliability of the communication system.

In an aspect, the objectives are achieved by providing a method for managing connection procedures of the UE in the satellite communication system. Further, the method includes initiating by the UE a connection between the EEC of the UE and the EAS onboard on satellite upon initial EAS discovery via satellite access. Further, the method includes storing by the UE the EES and EAS connection information in a memory of the UE along with a satellite Identifier (ID) of a serving satellite that provides EES and EAS services to the EEC. Further, the method includes detecting by the UE the discontinuous coverage period during which the serving satellite temporarily ceases to provide the EES and EAS services to the EEC. Further, the method includes upon re-establishment of coverage by the serving satellite, reconnecting by the UE the EEC to the same EES and EAS to which the EEC was previously connected based on the stored EES and EAS connection information. The UE directly reconnects the EEC to the same EES and EAS, bypassing the service provisioning and EAS discovery procedures.

In an embodiment of the disclosure, the method includes reconnecting by the UE the EEC to the same EES and EAS to which the EEC was previously connected based on the stored EES and EAS connection information. Further, the method includes determining by the UE whether the memory of the UE includes the EES and EAS connection information for the satellite ID of the serving satellite that previously provided the EES and EAS services to the EEC upon re-establishment of the coverage by the serving satellite. Further, the method includes reconnecting by the UE the EEC directly to the EES and the EAS based on the stored EES and EAS connection information without requiring the EEC to rediscover the EES and EAS connection information when the memory of the UE includes the EES and EAS connection information for the satellite ID.

In an embodiment of the disclosure, the method includes initiating by the UE the service provisioning and EAS discovery procedures when the memory of the UE does not include the EES and EAS connection information for the satellite ID of the serving satellite.

In an embodiment of the disclosure, the method includes storing the EES and the EAS connection information, including building a mapping between the satellite ID and the EES and the EAS connection information per application over time for an application.

In an embodiment of the disclosure, the method includes the EES is deployed on the ground and the UE is located on one of the ground, sea, or in the air.

In an embodiment of the disclosure, the method includes a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) is deployed on the serving satellite and the EAS and EES are deployed on the serving satellite.

In an embodiment of the disclosure, the method includes providing by the serving satellite the EES and the EAS to the EEC at the UE. Further, the method includes detecting by the serving satellite the discontinuous coverage period experienced by the serving satellite during which the serving satellite temporarily ceases to provide the EES and EAS services to the EEC. Further, the method includes upon re-establishment of coverage by the serving satellite, reconnecting by the serving satellite the EEC to the same EES and EAS to which the EEC was previously connected without requiring the EEC to rediscover the EES and EAS connection information.

In another aspect, the objectives are achieved by providing the UE for managing connection procedures in the satellite communication system, including a memory, the EEC, a processor, and an EES-EAS connection information controller. Further, the EES-EAS connection information controller is coupled to the memory and the processor. Further, the EES-EAS connection information controller initiates the connection between the EEC of the UE and EAS upon initial EAS discovery with satellite access. Further, the EES-EAS connection information controller stores the EES and EAS connection information in the memory of the UE along with the satellite ID of the serving satellite that provides EES and EAS services to the EEC. Further, the EES-EAS connection information controller detects the discontinuous coverage period during which the serving satellite temporarily ceases to provide the EES and EAS services to the EEC. Further, the EES-EAS connection information controller determines whether the memory of the UE includes the EES and EAS connection information for the satellite ID of the satellite that previously provided the EES and EAS to the EEC upon re-establishment of the coverage by the serving satellite. Further, the EES-EAS connection information controller reconnects the EEC of the UE directly to the EES and the EAS based on the stored EES and EAS connection information without requiring the EEC to rediscover the EES and EAS when the memory of the UE includes the EES and EAS connection information for the satellite ID.

In another aspect, the objectives are achieved by providing the serving satellite for managing connection procedures of the UE in the satellite communication system, including the memory, the processor, and the EES-EAS connection information controller coupled to the memory and the processor. Further, the EES-EAS connection information controller provides the EES and the EAS to the EEC at the UE. Further, the EES-EAS connection information controller detects the discontinuous coverage period during which the serving satellite temporarily ceases to provide the EES and EAS service to the EEC. Further, the EES-EAS connection information controller, upon re-establishment of coverage by the serving satellite with the stored satellite Identifier, reconnects the EEC of the UE to the same EES and EAS to which the EEC was previously connected without requiring the EEC to rediscover the EES and EAS connection information.

Embodiments of the present invention provide a method for managing connection procedures of a User Equipment (UE) in a satellite communication system. The method includes initiating a connection between the UE and an Earth Exploration Satellite (EES) and an Earth Access Satellite (EAS) onboard a satellite. Connection information for the EES and EAS, along with the satellite identifier, is stored in the memory of the UE. The method further includes detecting a discontinuous coverage period during which the serving satellite temporarily ceases to provide EES and EAS services to the UE. Upon re-establishment of coverage by the serving satellite, the UE reconnects to the same EES and EAS using the stored satellite identifier. This reconnection bypasses the service provisioning and EAS discovery procedures, allowing the UE to directly reconnect to the previously connected EES and EAS, thereby improving the efficiency and reliability of the satellite communication system.

The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

A method performed by a User Equipment (UE) in a wireless communication system, comprising:

identifying a target Edge Enabler Server (EES); and

identifying a target Edge Application Server (EAS) associated with the target EES with EAS discovery, wherein an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS, and

wherein in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.
The method of claim 1, wherein the target EAS and the target EES are deployed on the satellite.
The method of claim 1, wherein an Edge Configuration Server (ECS) is deployed on ground, and the UE is located at least one of on ground, on sea, or in air.
The method of claim 1, wherein a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) is deployed on the satellite.
The method of claim 1, further comprising:

storing information associated with at least one of the target EES or the target EAS along with a satellite Identifier (ID) of the satellite; and

in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, identifying, based on the satellite ID, that the UE stores the information associated with at least one of the target EES or the target EAS, wherein the EEC reconnects to the target EES and target EAS based on the stored information without repetition of the EES discovery and the EAS discovery.
A method performed by a satellite in a wireless communication system, comprising:

providing a service of a target Edge Enabler Server (EES) and a target Edge Application Server (EAS) to a User Equipment (UE), wherein the target EES is identified at the UE, the target EAS is identified with EAS discovery at the UE, and an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS, and

wherein in case that the satellite comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.
The method of claim 6, wherein the target EAS and the target EES are deployed on the satellite.
The method of claim 6, wherein an Edge Configuration Server (ECS) is deployed on ground, and the UE is located at least one of on ground, on sea, or in air.
The method of claim 6, wherein a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) is deployed on the satellite.
A User Equipment (UE) in a wireless communication system, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, wherein the at least one processor is configured to:

identify a target Edge Enabler Server (EES); and

identify a target Edge Application Server (EAS) associated with the target EES with EAS discovery, wherein an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS, and

wherein in case that a satellite providing a service of the target EES and the target EAS comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.
The UE of claim 10, wherein the target EAS and the target EES are deployed on the satellite.
The UE of claim 10, wherein an Edge Configuration Server (ECS) is deployed on ground, and the UE is located at least one of on ground, on sea, or in air.
The UE of claim 10, wherein a User Plane Function (UPF) to access a satellite Edge Data Network (EDN) is deployed on the satellite.
A satellite in a wireless communication system, comprising:

at least one memory; and

at least one processor coupled to the at least one memory, wherein the at least one processor is configured to:

provide a service of a target Edge Enabler Server (EES) and a target Edge Application Server (EAS) to a User Equipment (UE), wherein the target EES is identified at the UE, the target EAS is identified with EAS discovery at the UE, and an Edge Enabler Client (EEC) of the UE connects to the target EES and the target EAS, and

wherein in case that the satellite comes back for serving based on a discontinuous coverage, the EEC reconnects to the target EES and the target EAS without repetition of EES discovery and the EAS discovery.
The satellite of claim 14, wherein the target EAS and the target EES are deployed on the satellite.