Method and apparatus for obtaining edge enabler server (EES) information

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Accordingly, embodiments herein disclose a method for obtaining edge enabler server (EES) list. The method includes receiving, by an Edge Configuration Server (ECS) (200), a retrieve EES request from a source EES (100). Further, the method includes determining, by the ECS (200), at least one target EES list based on the retrieve EES request. The target EES list is used for application context synchronization between Edge Application Servers (EASs) or indicates the target EES(s) about a common EAS that has been selected. Further, the method includes sending, by the ECS (200), a retrieve EES response comprising the at least one target EES list.

Description

METHOD AND APPARATUS FOR OBTAINING EDGE ENABLER SERVER (EES) INFORMATION

[0001] The disclosure relates to a wireless communication, and more specifically related to a system and method for obtaining common Edge Application Server (EAS) information from an Application Server. Also, a system and method is used for obtaining edge enabler server list for announcement in the wireless communication.

[0002] 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 (THz) 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.

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

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

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

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

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

[0008] An edge computing system is a distributed computing paradigm that brings computations and data storages closer to a geographical location where the computations and the data storages are required, to improve response times and save bandwidth. In fifth generation (5G), data transmission speed is increased by multiple times compare to previous generation networks (e.g., 4G, 3G or the like). In order to reduce latency, edge computing is essential which brings computing resources near to end users. In release (Rel)-17, Third Generation partnership Project (3GPP) has defined an Edge Enabler Layer (EEL) in a technical specification (TS) 23.558. The EEL exposes Application Programming Interfaces (APIs) to support capabilities like service provisioning, registration, application server discovery, capability exposure to an Application Server (AS) and support for service continuity. Application Clients (ACs) in a User Equipment (UE) are able to locate and connect with a most suitable Edge Application Server (EAS) available in an Edge Data Network (EDN), using the capabilities provided by the EEL.

[0009] In current 3GPP specification TS 23.558, multiple Edge Enabler Servers (EESs) and multiple EASs offering a same service are deployed, possibly located at different locations (within same EDN or across multiple EDNs). The 3GPP specification enables a discovery of EAS by the EEC which is independent of the discovery of EAS by other UEs or the ACs which may belong to a same User or another User. In certain use cases, a real-time communication in a multi-user session is involved both between the AC and the EAS and between different ACs via the EAS, it is necessary or beneficial to use the services from a single common EAS to meet strict latency requirements, to avoid the requirement for inter-EAS synchronization or for any other reasons such as to provide same application experience for a group of users. The use cases may include, for example, a team of robots coordinating together on a manufacturing floor, a team of surgeons using virtual reality (VR) headsets and robotic surgery equipment to operate together on a patient, multiplayer gaming service, or a group of trucks using V2X for platooning.

[0010] In conventional method, if selection of EAS is not co-ordinated then the selection can result EAS selection across EDNs or contain race conditions can occur or procedure will be complex in nature. Further, as per the current 3GPP specification, the EEC of one user selects the EAS which is different from the EAS selected by another user - although both user are part of the same communication session. If different EASs are selected for the users then different EASs need to synchronize with each other in order to maintain the communication session. Dependent on the use case, the EEL applies different criteria to determine the list of EES according to the purpose.

[0011] Hence is desirable to address the above mentioned problem and disadvantages or at least provide a useful alternative.

[0012] The principal object of the embodiments herein is to provide system, an apparatus and method for obtaining common Edge Application Server (EAS) information from the Application Server (which is Edge Application Server or Edge Enabler Server or Edge Configuration Server).

[0013] Another object of the embodiments herein is to provide a system, an apparatus and a method for pre-configuring common Edge Application Server in an EAS profile.

[0014] Another object of the invention is to provide provisioning of common EAS information in initial and update requests from an EAS to EES via a EAS profile and then an EES to Edge Configuration Server (ECS) via the EES profile.

[0015] Another object of the invention is to provide that the EEC requesting to receive common EAS is associated to a group.

[0016] Yet another object of the embodiments herein is to provide a service provisioning procedure updating to the request and obtain the common EAS associated to the group.

[0017] Yet another object of the embodiments herein is to provide an EAS discovery procedure updating to request and obtain the common EAS associated to the group.

[0018] Another object of the embodiments herein is to provide a method, an apparatus and system for obtaining EES list for announcement.

[0019] Another object of the embodiments herein is to retrieve a target EES from a source EES in order to transfer an application context during a service continuity scenario.

[0020] Another object of the embodiments herein is to send a request to an ECS to determine suitable target EES.

[0021] Another object of the embodiments herein is to determine and return the list of EES by the ECS. The list of EES to which the common EAS has to be announced, or enabling the EAS to find other EAS(s) with multi-user communication session to synchronize.

[0022] Accordingly, embodiments herein disclose a method for obtaining edge enabler server (EES) list. The method includes receiving, by an Edge Configuration Server (ECS), a retrieve EES request from a source EES. Further, the method includes determining, by the ECS, at least one target EES list based on the retrieve EES request. The target EES list is used for application context synchronization between Edge Application Servers (EASs) supporting the same application or indicates the target EES(s) about a common EAS that has been selected. Further, the method includes sending, by the ECS, a retrieve EES response comprising the at least one target EES list.

[0023] Accordingly, embodiments herein disclose a method for obtaining edge enabler server (EES) list. The method includes sending, by a source EES, a retrieve EES request to an Edge Configuration Server (ECS). Further, the method includes receiving, by the source EES, a retrieve EES response comprising at least one target EES list from the ECS based on the retrieve EES request, wherein the target EES list is used for application context synchronization between Edge Application Servers (EASs) or indicates the target EES(s) about a common EAS that has been selected.

[0024] Accordingly, embodiments herein disclose an ECS for obtaining EES list. The ECS includes an EES list obtaining controller communicatively coupled to a memory and a processor. The EES list obtaining controller is configured to receive a retrieve EES request from a source EES. Further, the EES list obtaining controller is configured to determine at least one target EES list based on the retrieve EES request. The target EES list is used for application context synchronization between EASs or indicates the target EES(s) about a common EAS that has been selected. Further, the EES list obtaining controller is configured to send a retrieve EES response comprising the at least one target EES list.

[0025] Accordingly, embodiments herein disclose a source EES for obtaining EES list. The source EES includes an EES list obtaining controller communicatively coupled to a memory and a processor. The EES list obtaining controller is configured to send a retrieve EES request to an Edge Configuration Server (ECS). Further, the EES list obtaining controller is configured to receive a retrieve EES response comprising at least one target EES list from the ECS based on the retrieve EES request, wherein the target EES list is used for application context synchronization between Edge Application Servers (EASs) or indicates the target EES(s) about a common EAS that has been selected.

[0026] In an embodiment, the at least one target EES list is used for redirecting EAS discovery to a common EAS that has been selected.

[0027] In an embodiment, the retrieve EES request comprises an obtain announcement EES list and an application group identifier (ID), wherein the obtain announcement EES list indicates to the ECS that the request is to obtain EES list for an announcement of common EAS, and the application group identifier (ID) identities a group of User Equipment’s (UEs) using an application.

[0028] In an embodiment, when the retrieve EES request comprises indication to the ECS that the request EES list retrieval is for the announcement of a common EAS, the ECS determines the list of EESs where the EAS is registered and serves a group ID included in the retrieve EES request.

[0029] In an embodiment, the retrieve EES response includes a list of EDN configuration information to the source EES, when the ECS has determined a EDN configuration information, wherein the list of EDN configuration information comprises a list of application groups information and an application group ID.

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

[0031] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

[0032] These and other features, aspects, and advantages of the 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:

[0033] FIG. 1 illustrates a scenario of retrieving T-EES procedure, accordingly to embodiments as disclosed herein;

[0034] FIG. 2 illustrates various hardware components of an ECS, according to the embodiments as disclosed herein.

[0035] FIG. 3 illustrates various hardware components of a source EES, according to the embodiments as disclosed herein.

[0036] FIG. 4 is a flow chart illustrating a method, implemented by the ECS, for obtaining an EES list, according to the embodiments as disclosed herein.

[0037] FIG. 5 is a flow chart illustrating a method, implemented by the source EES, for obtaining an EES list, according to the embodiments as disclosed herein.

[0038] FIG. 6 illustrates various hardware components of an entity, according to the embodiments as disclosed herein.

[0039] It may be noted that to the extent possible, like reference numerals have been used to represent like elements in the drawing. Further, those of ordinary skill in the art will appreciate that elements in the drawing are illustrated for simplicity and may not have been necessarily drawn to scale. For example, the dimension of some of the elements in the drawing may be exaggerated relative to other elements to help to improve the understanding of aspects of the invention. Furthermore, the one or more elements may have been represented in the drawing by conventional symbols, and the drawings may show only those specific details that are pertinent to the understanding the embodiments of the invention so as not to obscure the drawing with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

[0040] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal and a communication method thereof in a wireless communication system.

[0041] 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. 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 should not be construed as limiting the scope of the embodiments herein.

[0042] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as units or modules or the like, are physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, 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 may 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 may be physically separated into two or more interacting and discrete blocks without departing from the scope of the invention. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the invention

[0043] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.

[0044] Accordingly, embodiments herein disclose a system and method for pre-configuring common edge application server is disclosed. A current 3GPP specification TS 23.558, the EDN, multiple EESs and multiple EASs offering a same service are deployed, possibly located at different locations. The 3GPP specification enables an EAS discovery by the EEC which is independent of the EAS discovery by other UEs or the ACs which may belong to a same user or another user. In certain use cases, a real-time communication in a multi-user session is involved between both the AC and the EAS and between different ACs via the EAS to use the services from a single common EAS to satisfy strict latency requirements, to avoid the requirement for inter-EAS synchronization. Dependent on the use case, the EEL applies different additional criteria to determine the common EAS so that latency for all the ACs in the session is approximately the same or that the latency for a specific AC is minimized.

[0045] The method and system are used for obtaining EES list for announcement. In current 3GPP specification TS 23.558 V18.2.0 is used to retrieve a target EES from a source EES in order to transfer an application context during a service continuity scenario. Based on input parameters such as UE location, EASID and the source EES, a request is sent to the ECS to determine suitable target EES. The ECS determines and returns target EES information. The proposed method supports the service continuity and hence a response includes only one EES information.

[0046] In an embodiment, the ECS determines and returns the list of EES. For example, the list of EES to which the common EAS has to be announced, enabling the EAS to find other EAS(s) with multi-user communication session to synchronize.

[0047] In an embodiment, discovery procedures enable entities in an edge deployment to obtain information about the EAS and available services, based on specified criteria of interest. The EAS discovery enables the EEC to obtain information about available EASs of interest. The discovery of the EASs is based on matching EAS discovery filters provided in the request.

[0048] Enhancements to EAS Profiles:

[0049] Following enhancements to the EAS profile, an EES profile and an AC profile to include List of application group information containing Application Group ID is proposed in this disclosure.

[0050]

[0051]

[0052]

[0053]

[0054]

[0055]

[0056]

[0057] Enhancements to Registration procedures:

[0058] EAS Registration will include the EAS Profile-enhanced with application group information (as in TABLE.1). The EES Registration will include the EES Profile-enhanced with application group information (as in TABLE.2). Both the EES and the ECS are now aware of the common EAS associated to each of the Application Group ID.

[0059] Enhancements to Service Provisioning procedures:The service provisioning procedures (Request-response model and Subscribe-notify model), the EEC includes application group information i.e. application group ID for obtaining the common EAS information from the ECS (for example AC profile-enhanced as in TABLE.3). When the application group information (i.e. Application Group ID) is provided in the request, the ECS identifies the EAS associated to the same application group ID, as received in the EES profile. The ECS returns only one EES and hence EAS associated to each of the application group ID received in the request.

[0060] The EDN configuration information includes List of application group information containing Application Group ID as proposed in the disclosure.

[0061]

[0062]

[0063]

[0064] Enhancements to EAS discovery procedures:The EAS discovery procedures (Request-response model and Subscribe-notify model), the EEC includes application group information i.e. Application Group ID for discovering the common EAS information from the EES. When the application group information (i.e. Application Group ID) is provided in the request, then the EES identifies the EAS associated to the same application group ID, as received in the EAS registration. The EES returns only one EAS associated to each of the application group ID received in the request.

[0065] In an embodiment, the Application Group ID need not have the group members (e.g. UEs) pre-configured but can be added at later stage or dynamically added.

[0066] In an embodiment, the new EAS registration and updates to common EAS are known to EES and shared to ECS and EEC.

[0067] In an embodiment, the updates to common EAS are known to EES, ECS and EEC through Service Provisioning or EAS discovery procedures.

[0068] In an embodiment, a retrieve T-EES procedure is utilized to determine the target EES to which the application context is pushed, in order to support the service continuity. The proposed method discloses to obtain the list of target EES, which is used for application context synchronization between the EASs or to let the target EES know about the common EAS that has been selected.

[0069] Enhancements to Retrieve EES request and response:Following enhancements to Retrieve EES request are proposed in this invention in TABLE.5. The enhancement includes Obtain announcement EES list IE and Application Group ID IE in the request message.

[0070]

[0071] TABLE.5 describes the information elements to retrieve T-EES information from the ECS.

[0072] The Retrieve EES response in the disclosure is enhanced to include the list of EESs supporting the EASID associated to the application group ID in TABLE.6. The EDN configuration information includes List of application group information containing Application Group ID.

[0073]

[0074] TABLE.6 defines the information elements for Service provisioning response.

[0075]

[0076]

[0077]

[0078] TABLE.7 defines the information elements in an EDN configuration information.

[0079] FIG. 1 is an example illustrating a scenario for retrieving T-EES procedure, accordingly to embodiments as disclosed herein. Alternatively, procedure for the S-EES (100) to retrieve the T-EES information from the ECS (200).

[0080] Enhancements to Retrieve EES procedures:

[0081] Below are the pre-condition:

[0082] 1. The S-EES (100) has been pre-configured with the address of the ECS (200); and

[0083] 2. The AC at the UE already has on-going application traffic with the S-EAS.

[0084] Retrieve T-EES procedure:At step 101, the S-EES (100) sends the Retrieve EES request (e.g., UE location information or UE identity, EASID of the S-EAS, target DNAI and UE connectivity information) to the ECS (200) in order to identify the T-EES which has an EAS available to serve a given AC in the UE.

[0085] For obtaining announcement EES list, the Retrieve EES request includes indication to the ECS that EES list retrieval is for the announcement of common EAS.

[0086] At step 102, if the request contains the UE identity (e.g. GPSI) but the UE location is not known to the ECS (200), then the ECS (200) interacts with a 3GPP core network to retrieve the UE location. The ECS (200) determines T-EES(s) as per the parameters (e.g. EASID, target DNAI) in the request and the UE location information.

[0087] When the Retrieve EES request includes indication to the ECS that the request EES list retrieval is for the announcement of common EAS, ECS determines the list of EESs where the EAS is registered and serves the Group ID included in the Retrieve EES request.

[0088] If the ECS does not identify any suitable EES(s) based on EDN configuration available at the ECS and UE's location, the ECS (200) determines a partner ECS that may satisfy the requirements. Based on ECSP policy, the ECS (200) may use preconfigured or OAM configured information about the partner ECSs or ECS discovery via ECS-ER. If required by the ECSP policies, the ECS (200) may use service provisioning information retrieval procedure to obtain service provisioning information from the partner ECS.

[0089] At step 103, the ECS (200) sends the Retrieve EES response. If the ECS has determined the EDN configuration information, the retrieve EES response includes the list of EDN configuration information to the S-EES. The list of EDN configuration information includes the EDN details with the endpoint information of T-EES(s). If the ECS has determined suitable partner ECS(s) instead, the retrieve EES response includes a list of ECS configuration information.

[0090] The list of EESs also includes the list of application groups to which the EAS is selected as a common EAS.

[0091] If the retrieve EES response contains a list of ECS configuration information, the S-EES may initiate retrieve T-EES procedure with one or more ECS(s) listed in the retrieve EES response.

[0092] The Retrieve EES request initiated by the S-EES is restricted only to its registered ECS.

[0093] In an embodiment, the presence of Application Group ID IE itself indicates that the request is for announcement.

[0094] In an embodiment, the presence of obtaining announcement EES list in the Retrieve EES request indicates to the ECS that EES list retrieval is for EAS synchronization.

[0095] In an embodiment, when obtaining announcement EES list is for EAS synchronization, ECS determines the list of EESs where the EAS is registered and serves the Group ID if included in the Retrieve EES request.

[0096] In an embodiment, when obtaining announcement EES list is for EAS synchronization, the list of EESs will also include the list of application groups which may be included in the received Retrieve EES request.

[0097] FIG. 2 shows various hardware components of the ECS (200), according to the embodiments as disclosed herein. In an embodiment, the ECS (200) includes a processor (210), a communicator (220), a memory (230) and a EES list obtaining controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the EES list obtaining controller (240).

[0098] The EES list obtaining controller (240) receives the retrieve EES request from the source EES (100). Further, the EES list obtaining controller (240) determines the at least one target EES list based on the retrieve EES request. The target EES list is used for application context synchronization between EASs or indicates the target EES(s) about a common EAS that has been selected. Further, the EES list obtaining controller (240) sends the retrieve EES response comprising the at least one target EES list.

[0099] The EES list obtaining controller (240) is 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 may optionally be driven by firmware.

[0100] The processor (210) may include one or a plurality of processors. The one or the plurality of processors may be 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (130).

[0101] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such 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. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0102] In an embodiment, the communicator (220) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (220) is configured to communicate internally between internal hardware components of the UE and with external devices via one or more networks.

[0103] Although the FIG. 2 shows various hardware components of the ECS (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the ECS (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the ECS (200).

[0104] FIG. 3 shows various hardware components of the source EES (100), according to the embodiments as disclosed herein. In an embodiment, the source EES (100) includes a processor (110), a communicator (120), a memory (130) and a EES list obtaining controller (140). The processor (110) is coupled with the communicator (120), the memory (130) and the EES list obtaining controller (140).

[0105] The EES list obtaining controller (140) sends the retrieve EES request to the ECS (200). Further, the EES list obtaining controller (140) receives the retrieve EES response comprising at least one target EES list from the ECS based on the retrieve EES request. The target EES list is used for application context synchronization between the EASs or indicates the target EES(s) about a common EAS that has been selected.

[0106] The EES list obtaining controller (140) is 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 may optionally be driven by firmware.

[0107] The processor (110) may include one or a plurality of processors. The one or the plurality of processors may be 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 AI-dedicated processor such as a neural processing unit (NPU). The processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).

[0108] Further, the processor (110) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (120) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such 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. In addition, the memory (130) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0109] In an embodiment, the communicator (120) includes an electronic circuit specific to a standard that enables wired or wireless communication. The communicator (120) is configured to communicate internally between internal hardware components of the UE and with external devices via one or more networks.

[0110] Although the FIG. 3 shows various hardware components of the source EES (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the source EES (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the source EES (100).

[0111] FIG. 4 is a flow chart (S400) illustrating a method, implemented by the ECS (200), for obtaining the EES list, according to the embodiments as disclosed herein. The operations (S402-S406) are handled by the EES list obtaining controller (240).

[0112] At S402, the method includes receiving the retrieve EES request from the source EES (100). At S404, the method includes determining the at least one target EES list based on the retrieve EES request. The target EES list is used for application context synchronization between the EASs or indicates the target EES(s) about a common EAS that has been selected. At S406, the method includes sending the retrieve EES response comprising the at least one target EES list.

[0113] FIG. 5 is a flow chart (S500) illustrating a method, implemented by the source EES (100), for obtaining an EES list, according to the embodiments as disclosed herein. The operations (S502-S504) are handled by the EES list obtaining controller (140).

[0114] At S502, the method includes sending the retrieve EES request to the ECS (200). At S504, the method includes receiving the retrieve EES response comprising the at least one target EES list from the ECS based on the retrieve EES request. The target EES list is used for application context synchronization between the EASs or indicates the target EES(s) about a common EAS that has been selected.

[0115] The various actions, acts, blocks, steps, or the like in the flow charts (S400 and S500) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0116] FIG. 6 illustrates various hardware components of a network entity, according to embodiments as disclosed herein.

[0117] Referring to FIG. 6, the network entity includes a transceiver (610), a memory (620), and a processor (630). The transceiver (610), the memory (620), and the processor (630) of the network entity may operate according to a communication method of the network entity described above. However, the components of the network entity are not limited thereto. For example, the network entity may include fewer or a greater number of components than those described above. In addition, the processor (630), the transceiver (610), and the memory (620) may be implemented as a single chip. Also, the processor (630) may include at least one processor.

[0118] The network entity includes at least one entity of a core network. For example, the network entity includes an Access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a network repository function (NRF), a user plane function (UPF), a network slicing selection function (NSSF), an authentication server function (AUSF), a unified data management (UDM) and a network exposure function (NEF), but the network entity is not limited thereto. For example, the network entity may correspond to an ECS or an EES.

[0119] The transceiver (610) collectively refers to a network entity receiver and a network entity transmitter, and may transmit / receive a signal to / from a base station or a UE. The signal transmitted or received to or from the base station or the UE may include control information and data. In this regard, the transceiver (610) may include an RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and an RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver (610) and components of the transceiver (610) are not limited to the RF transmitter and the RF receiver.

[0120] The transceiver (610) may receive and output, to the processor (630), a signal through a wireless channel, and transmit a signal output from the processor (630) through the wireless channel.

[0121] The memory (620) may store a program and data required for operations of the network entity. Also, the memory (620) may store control information or data included in a signal obtained by the network entity. The memory (620) may be a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0122] The processor (630) may control a series of processes such that the network entity operates as described above. For example, the transceiver (610) may receive a data signal including a control signal, and the processor (630) may determine a result of receiving the data signal.

[0123] 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

1.A method performed by an edge enabler server, EES, in a wireless communication system, the method comprising:transmitting, to an edge configuration server, ECS, a retrieve EES request message including an indicator for obtaining a list of EESs for an announcement of common edge application server, EAS; andreceiving, from the ECS, a retrieve EES response message including edge data network, EDN, configuration information, the EDN configuration information includes the list of EESs based on the retrieve EES request message.2.The method of claim 1,wherein the indicator includes an application group identifier, ID, that identifies a group of user equipment, UE, using a same application.3.The method of claim 2,wherein the list of EESs indicates EESs associated with the application group ID included in the retrieve EES request message.4.The method of claim 1,wherein the list of EESs includes information on a list of application groups associated with an EAS.5.A method performed by an edge configuration server, ECS, in a wireless communication system, the method comprising:receiving, from an edge enabler server, EES, a retrieve EES request message including an indicator for obtaining a list of EESs for an announcement of common edge application server, EAS; andtransmitting, to the EES, a retrieve EES response message including edge data network, EDN, configuration information, the EDN configuration information includes the list of EESs based on the retrieve EES request message.6.The method of claim 5,wherein the indicator includes an application group identifier, ID, that identifies a group of user equipment, UE, using a same application.7.The method of claim 6,wherein the list of EESs indicates EESs associated with the application group ID included in the retrieve EES request message.8.The method of claim 5,wherein the list of EESs includes information on a list of application groups associated with an EAS.9.An edge enabler server, EES, in a wireless communication system, the EES comprising:a transceiver; anda controller coupled with the transceiver and configured to:transmit, to an edge configuration server, ECS, a retrieve EES request message including an indicator for obtaining a list of EESs for an announcement of common edge application server, EAS; andreceive, from the ECS, a retrieve EES response message including edge data network, EDN, configuration information, the EDN configuration information includes the list of EESs based on the retrieve EES request message.10.The EES of claim 9,wherein the indicator includes an application group identifier, ID, that identifies a group of user equipment, UE, using a same application.11.The EES of claim 10,wherein the list of EESs indicates EESs associated with the application group ID included in the retrieve EES request message.12.The EES of claim 9,wherein the list of EESs includes information on a list of application groups associated with an EAS.13.An edge configuration server, ECS, in a wireless communication system, the ECS comprising:a transceiver; anda controller coupled with the transceiver and configured to:receive, from an edge enabler server, EES, a retrieve EES request message including an indicator for obtaining a list of EESs for an announcement of common edge application server, EAS; andtransmit, to the EES, a retrieve EES response message including edge data network, EDN, configuration information, the EDN configuration information includes the list of EESs based on the retrieve EES request message.14.The ECS of claim 13,wherein the indicator includes an application group identifier, ID, that identifies a group of user equipment, UE, using a same application.15.The ECS of claim 14,wherein the list of EESs indicates EESs associated with the application group ID included in the retrieve EES request message, andwherein the list of EESs includes information on a list of application groups associated with an EAS.

Images