Discovery of multi-user session common edge application servers in edge data networks
Through the edge enabler client detecting and determining the public edge application server, the problem of synchronous delay between edge application servers in multi-user sessions is solved, and the waiting time equalization and communication efficiency are achieved.
Patent Information
- Application Number
- CN202380032132.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-20
- Filing Date
- 2023-03-29
- Publication Date
- 2024-11-15
AI Technical Summary
In multi-user sessions or multi-application client sessions, synchronization between edge application servers increases latency and difficulty, resulting in increased communication waiting time.
The edge enabler client detects the discovery trigger on the public edge application server, and sends an EAS discovery request message to the edge enabler server, receiving a response message to determine the public edge application server, avoiding the Synchronize requirements.
It is realized that the waiting time is kept approximately the same for multi-user sessions or multi-application client sessions in the wireless communication network, reducing the waiting time in communication and improving the efficiency of real-time communication.
Smart Images

Figure CN118975217A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to edge computing, and more particularly to an edge enabler client (EEC) and a method of discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session. Background Art
[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave including 28 GHz and 39 GHz. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.
[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), standardization is underway on beamforming and massive MIMO for mitigating radio wave path loss in mmWave and increasing mmWave transmission distance, parameter sets supporting dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods for large-volume data transmission (such as LDPC (low-density parity check) codes and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.
[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation intended to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable), and positioning.
[0005] In addition, there has been standardization of technologies in air interface architecture / protocols, such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also underway on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / service for mobile edge computing (MEC) for receiving services based on UE location.
[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., 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] In addition, such development of 5G mobile communication systems will not only serve as the basis for developing new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum) and RIS (reconfigurable smart surface), and full-duplex technology for improving frequency efficiency and improving system networks for 6G mobile communication technology, AI-based communication technology for achieving 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 achieving services with a level of complexity that exceeds the limitations of UE operating capabilities by utilizing ultra-high performance communication and computing resources.
[0008] Generally, edge computing systems are distributed computing paradigms that bring computing and data storage closer to geographic locations. Edge enabler clients (EECs) connect to edge application servers (EASs) through edge enabler servers (EESs) to obtain services. In some scenarios, multiple EESs and multiple EASs that provide the same service are deployed within edge data networks (EDNs) located in different locations.
[0009] During real-time communication in a multi-user session, multiple EECs in the multi-user session select at least one EAS from multiple EASs for the multi-user session, wherein the EAS selected by one EEC may be different from the EAS selected by other EECs. Therefore, the selected multiple EASs need to be synchronized with each other in order to maintain the multi-user session. However, due to the synchronization between EASs, maintaining a multi-user session connected through multiple EASs increases delay and difficulty.
[0010] It would therefore be desirable to address the above-mentioned disadvantages or others, or at least provide a useful alternative to avoid inter-EAS synchronization and reduce latency in communications. Summary of the invention
[0011] Solution to the problem
[0012] The main aspect of the embodiments herein is to provide an edge enabler client (EEC) and a method of discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session to keep the latency of all ACs in the session approximately the same.
[0013] Another aspect of embodiments herein is to determine a common EAS for establishing a multi-user session or a multi-AC session between a first EEC (100) and at least one second EEC, which avoids the need for inter-EAS synchronization.
[0014] Another aspect of embodiments herein is to determine at least one second EES to inform a selected common EAS for a multi-user session or a multi-AC session.
[0015] Another aspect of the embodiments herein is to determine whether a common EAS has been selected for a multi-user session or a multi-AC session based on the grouping information.
[0016] Therefore, an embodiment of the present invention provides a method for discovering a public edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network. The method also includes detecting a trigger for EAS discovery by a first edge enabler client (EEC). The method also includes sending an EAS discovery request message to an edge enabler server (EES) by a first EEC, wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session. The method also includes receiving an EAS discovery response message from the EES by the first EEC, wherein the EAS discovery response message includes at least one of a plurality of EAS or a selected public EAS based on the grouping information. The method also includes determining, by the first EEC, a public EAS for establishing a multi-user session or a multi-AC session between a first EEC and at least one second EEC based on the EAS discovery response message and at least one of the grouping information.
[0017] In one embodiment, the method includes sending a selected EAS announce request message by a first EEC to an EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES. The method also includes receiving a selected EAS announce response message by the first EEC from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0018] In one embodiment, the grouping information includes: a grouping requirement information element (IE), indicating that the application requires grouping; a multi-user session IE, indicating that the application requires a multi-user session; a multi-AC session IE, indicating that multiple ACs are part of the session; a group ID IE, indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE, indicating one or more ACIDs that need to be served by a common EAS as part of a multi-user session.
[0019] In an embodiment, the selected EAS advertisement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
[0020] In an embodiment, the method includes receiving, by a first EES, an EAS discovery request message from a first EEC, wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session. The method also includes sending, by the first EES, an EAS discovery response message to the first EEC, wherein the EAS discovery response message includes a plurality of EASs based on the grouping information. The method also includes receiving, by the first EES, a selected EAS notification request message from the first EEC, wherein the selected EAS notification request message includes a selected public EAS, wherein the first EEC selects a public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC and at least one second EEC. The method also includes determining, by the first EES, at least one second EES to notify the selected public EAS for the multi-user session or the multi-AC session.
[0021] In an embodiment, the method includes sending, by a first EES, an ID of a selected public EAS to an ECS, wherein the ECS (301) determines at least one second EES that serves the same ID of the selected public EAS. The method also includes receiving, by the first EES, an identifier of at least one second EES having the same ID of the selected public EAS from the ECS. The method also includes sending, by the first EES, a declare public EAS request message to at least one second EES; wherein the declare public EAS request message includes the selected public EAS and grouping information. The method also includes receiving, by the first EES, a declare public EAS response message from at least one second EES; wherein the declare public EAS response message includes an acknowledgment.
[0022] In an embodiment, the method includes receiving an EAS discovery request message from a first EEC by a first EES. The method also includes determining by the first EES whether a public EAS has been selected for a multi-user session or a multi-AC session based on grouping information. The method also includes sending the selected public EAS to the first EEC to initiate the multi-user session or the multi-AC session when the public EAS has been selected for the multi-user session or the multi-AC session based on the grouping information. The method also includes selecting multiple EASs based on the grouping information by the EES when the public EAS has not been selected for the multi-user session or the multi-AC session based on the grouping information. The method also includes transmitting multiple EASs to the first EEC.
[0023] Therefore, embodiments of the present invention provide a first EEC for discovering a public edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network. The first EEC includes a memory; a processor; and an EAS discoverer coupled to the memory and the processor. The EAS discoverer is configured to detect a trigger for EAS discovery. The EAS discoverer is also configured to send an EAS discovery request message to an edge enabler server (EES), wherein the EAS discovery request message includes grouping information of the multi-user session or the multi-AC session. The EAS discoverer is also configured to receive an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a selected public EAS based on the grouping information. The EAS discoverer is also configured to determine a public EAS for establishing a multi-user session or a multi-AC session between the first EEC and at least one second EEC based on at least one of the EAS discovery response message and the grouping information.
[0024] Therefore, an embodiment of the present invention is to provide a first EES for discovering a public edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network. The first EES includes a memory; a processor; and an EAS announcer, coupled to the memory and the processor. The EAS announcer is configured to receive an EAS discovery request message from a first edge enabler client (EEC), wherein the EAS discovery request message includes grouping information of the multi-user session or the multi-AC session. The EAS announcer is also configured to send an EAS discovery response message to the first EEC, wherein the EAS discovery response message includes a plurality of EASs based on the grouping information. The EAS announcer is also configured to receive a selected EAS announcement request message from the first EEC, wherein the selected EAS announcement request message includes a selected public EAS, wherein the first EEC selects a public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC and at least one second EEC. The EAS announcer is also configured to determine at least one second EES to notify the selected public EAS for the multi-user session or the multi-AC session.
[0025] When considered in conjunction with the following description and the accompanying drawings, these and other aspects of the embodiments herein will be better appreciated and understood. However, it should be understood that the following description, although indicating preferred embodiments and many specific details thereof, is given by way of illustration and not limitation. Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] The present disclosure is illustrated in the accompanying drawings, and the same reference numerals indicate corresponding parts in the various drawings throughout the drawings. The embodiments of the present invention will be better understood from the following description with reference to the accompanying drawings, in which:
[0027] Figure 1 is a sequence diagram illustrating an edge application server (EAS) discovery process according to the prior art;
[0028] Figure 2 is a block diagram of a system for discovering a public EAS according to an embodiment disclosed herein;
[0029] Figure 3a is a flow chart illustrating a method of discovering a public EAS by an edge enabler client (EEC) according to an embodiment disclosed herein;
[0030] Figure 3b is a flow chart illustrating a method of discovering a public EAS by an edge enabler server (EES) according to an embodiment disclosed herein;
[0031] Figure 4is a sequence diagram illustrating an EEC-based EAS discovery process for public EAS selection according to an embodiment disclosed herein;
[0032] Figure 5 is a sequence diagram illustrating an EAS discovery process based on an EEC and participation of an EAS according to an embodiment disclosed herein;
[0033] Figure 6 is a sequence diagram illustrating discovery of a common EAS when multiple EECs are connected to the same EES according to an embodiment disclosed herein; and
[0034] Figure 7 is a sequence diagram illustrating discovery of a common EAS when multiple EECs are connected to different EESs according to an embodiment disclosed herein. DETAILED DESCRIPTION
[0035] The embodiments of this article and its various features and advantageous details are explained more fully with reference to the non-limiting embodiments shown in the drawings and described in detail in the following description. The description of known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of this article. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" as used herein refers to a non-exclusive or. The examples used herein are intended only to facilitate understanding of the manner in which the embodiments of this article can be practiced, and further enable those skilled in the art to practice the embodiments of this article. Therefore, the examples should not be interpreted as limiting the scope of the embodiments of this article.
[0036] As is conventional in the art, embodiments may be described and illustrated in terms of blocks that perform one or more functions described. These blocks (which may be referred to herein as managers, units, modules, hardware components, etc.) 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, hard-wired circuits, etc.), and may be optionally driven by firmware and software. The circuit may be, for example, embodied in one or more semiconductor chips, or embodied on a substrate support such as a printed circuit board. The circuits that constitute the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware that performs some functions of the blocks and a processor that performs other functions of the blocks. Without departing from the scope of the present disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of the embodiment may be physically combined into more complex blocks.
[0037] 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. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and substitutes other than those specifically set forth in the accompanying drawings. Although the terms first, second, etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.
[0038] Edge computing systems are a distributed computing paradigm that brings computation and data storage closer to the geographic locations where computation and data storage are needed to improve response time and save bandwidth. In the case of the fifth generation (5G), the expected data transmission speed has increased multiple times compared to the previous generation of networks. To reduce latency, edge computing is necessary, which brings computing resources close to the end user. In Rel-17, 3GPP has defined the Edge Enabler Layer (EEL) in TS23.558. The EEL exposes APIs to support capabilities such as service provisioning, registration, application server discovery, access stratum (AS) capability exposure, and support for service continuity. The application client (AC) in the user equipment (UE) is able to use the capabilities provided by the EEL to locate and connect to the most suitable edge application server (EAS) available in the edge data network (EDN).
[0039] According to the traditional approach, within an EDN, several EESs and several EASs providing the same service may be deployed, possibly at different locations. And the specification enables the discovery of the EAS by one EEC, independent of the discovery of the EAS by other UEs or ACs, which may belong to the same user or another user. However, for certain use cases involving real-time communications between ACs and EASs and in multi-user sessions between different ACs via EASs, it may be necessary or beneficial to use services from a single common EAS to meet strict latency requirements, to avoid the need for inter-EAS synchronization or for any other reason. Use cases may include, for example, a team of robots coordinating together on a manufacturing floor, a team of surgeons operating together on a patient using VR headsets and robotic surgical equipment, a multi-player gaming service, or a group of trucks platooning using V2X.
[0040] According to the traditional method, the EEC of one user may select an EAS different from the EAS selected by another user - even though both users are part of the same communication session. If different EASs are selected for the users, the different EASs need to be synchronized with each other in order to maintain the communication session.
[0041] Depending on the use case, the EEL may apply different additional criteria to determine the common EAS. For example, it may be desirable to determine the EAS so that the waiting time for all ACs in a session is approximately the same, or to minimize the waiting time for a particular AC.
[0042] For certain use cases involving real-time communications between ACs and EASs and in multi-user sessions between different ACs via EASs, it may be necessary or beneficial to use services from a single common EAS to meet strict latency requirements, to avoid the need for inter-EAS synchronization, or for any other reason. Use cases may include, for example, a team of robots coordinating together on a manufacturing floor, a team of surgeons operating together on a patient using VR headsets and robotic surgical equipment, or a group of trucks platooning using V2X.
[0043] According to conventional methods, the EEC of one user may select an EAS that is different from the EAS selected by another user - even though both users are part of the same communication session. If different EASs are selected for the users, the different EASs need to be synchronized with each other in order to maintain the communication session. Depending on the use case, the EEL may apply different additional criteria to determine the common EAS. For example, it may be desirable to determine the EAS so that the latency of all ACs in the session is approximately the same, or to minimize the latency of a particular AC.
[0044] Figure 1 is a sequence diagram illustrating an edge application server (EAS) discovery process according to the prior art.
[0045] In step 102, the EEC performs a startup process for initial service provisioning with the help of the ECS.
[0046] In step 103, the EEC performs EAS discovery and returns one or more EASs.
[0047] At step 104, when multiple EASs are discovered for a specific AC, the EEC may select one or more EASs to enable AC communication with one of the selected EASs, ie, the EEC (or the AC and the EEC) selects an initial EAS from the discovered EAS candidates.
[0048] In step 105, the EEC (100) transmits the selected EAS announcement to the EES (150).
[0049] At step 106, the EES transmits the selected EAS advertisement response to the EEC (100).
[0050] Referring now to the drawings and more particularly to Figures 2 to 7, wherein like reference numerals indicate corresponding features throughout the drawings, there is shown a preferred embodiment.
[0051] Figure 2 is a block diagram of a system (200) for discovering a public EAS according to embodiments disclosed herein.
[0052] Figure 2 A block diagram of a system (200) for discovering a public EAS is shown. The system includes a first edge enabler client (EEC) (100), a first edge enabler service (EES) (150), and an edge configuration server (301).
[0053] The EEC (100) includes a memory (211), a communicator (212), a processor (213), and an EAS discoverer (216). The EAS discoverer (216) includes a trigger detector (214) and an EAS selector (215).
[0054] An EEC (100) for discovering a public EAS according to an embodiment disclosed herein. Examples of the EEC (100) include, but are not limited to, smartphones, tablet computers, personal digital assistants (PDAs), Internet of Things (IoT) devices, AR devices, VR devices, wearable devices, etc.
[0055] In an embodiment, the memory (211) stores normal vectors associated with the point cloud, spatial features associated with the point cloud, similarity scores for each vertex associated with the point cloud, attention scores, global feature vectors, model view and projection matrices (MVP), multiple image frames, and information associated with the point cloud. The memory (211) stores instructions to be executed by the processor (213). The memory (211) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (211) may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (211) being non-removable. In some examples, the memory (211) may be configured to store a larger amount of information than the memory. In some examples, non-transitory storage media may store data that may change over time (e.g., in random access memory (RAM) or cache memory). Memory 211 may be an internal storage unit, or it may be an external storage unit of the EEC (100), a cloud storage device, or any other type of external storage device.
[0056] The processor (213) communicates with the memory (211), and the processor (213) is configured to execute instructions stored in the memory (211) and perform various processes. The processor (213) may include one or more processors, which may be a general-purpose processor (such as a central processing unit (CPU), an application processor (AP), etc.), a graphics 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)).
[0057] The communicator (212) is configured to communicate internally between internal hardware components and with external devices (e.g., eNodeB, gNodeB, servers, etc.) via one or more networks (e.g., radio technologies). The communicator (212) includes electronic circuitry specific to a standard that implements wired or wireless communications.
[0058] The EAS finder (216) is implemented by processing circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board.
[0059] The trigger detector (214) detects a trigger for EAS discovery. The EAS selector (215) sends an EAS discovery request message to an edge enabler server (EES), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session, and receives an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a public EAS that has been selected based on the grouping information. The trigger detector (214) determines a public EAS for establishing a multi-user session or a multi-AC session between a first EEC (100) and at least one second EEC based on at least one of the EAS discovery response message and the grouping information.
[0060] The EAS discoverer (216) is configured to send a selected EAS announce request message to the EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES. The EAS discoverer (216) is also configured to receive a selected EAS announce response message from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0061] In one embodiment, the grouping information includes: a grouping requirement information element (IE), indicating that the application requires grouping; a multi-user session IE, indicating that the application requires a multi-user session; a multi-AC session IE, indicating that multiple ACs are part of the session; a group ID IE, indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE, indicating one or more ACIDs that need to be served by a common EAS as part of a multi-user session.
[0062] In an embodiment, the selected EAS advertisement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
[0063] The EES (150) includes a memory (221), a communicator (222), a processor (223), and an EAS notifier (226). The EAS notifier (226) includes a related EES determiner (224) and an edge application server determiner (225).
[0064] In an embodiment, the memory (221) stores normal vectors associated with the point cloud, spatial features associated with the point cloud, similarity scores for each vertex associated with the point cloud, attention scores, global feature vectors, model view and projection matrices (MVP), multiple image frames, and information associated with the point cloud. The memory (221) stores instructions to be executed by the processor (223). The memory (221) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or an electrically programmable memory (EPROM) or an electrically erasable programmable (EEPROM) memory. In addition, in some examples, the memory (221) may be considered to be a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (221) being non-removable. In some examples, the memory (221) may be configured to store a larger amount of information than the memory. In some examples, non-transitory storage media may store data that may change over time (e.g., in random access memory (RAM) or cache memory). The memory (221) may be an internal storage unit, or it may be an external storage unit of the EES (150), a cloud storage device, or any other type of external storage device.
[0065] The processor (223) communicates with the memory (221), and the processor (223) is configured to execute instructions stored in the memory (221) and perform various processes. The processor (223) may include one or more processors, which may be a general-purpose processor (such as a central processing unit (CPU), an application processor (AP), etc.), a graphics 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)).
[0066] The communicator (222) is configured to communicate internally between internal hardware components and with external devices (e.g., eNodeB, gNodeB, servers, etc.) via one or more networks (e.g., radio technologies). The communicator (222) includes electronic circuitry specific to standards that implement wired or wireless communications.
[0067] The EAS annunciator (226) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, etc., and may optionally be driven by firmware. The circuitry may, for example, be embodied in one or more semiconductor chips, or on a substrate support such as a printed circuit board.
[0068] The edge application server determiner (225) receives an EAS discovery request message from a first edge enabler client (EEC), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session, and sends an EAS discovery response message to the first EEC (100), wherein the EAS discovery response message includes a plurality of EASs based on the grouping information.
[0069] The related EES determiner (224) receives a selected EAS notification request message from a first EEC (100), wherein the selected EAS notification request message includes a selected public EAS, wherein the first EEC (100) selects the public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC. The related EES determiner (224) determines at least one second EES to notify the selected public EAS for the multi-user session or the multi-AC session.
[0070] The EAS announcer (226) is configured to send an identifier (ID) of the selected public EAS to an edge configuration server (ECS), wherein the ECS (301) determines at least one second EES serving the same ID of the selected public EAS. The EAS announcer (226) is also configured to receive an identifier of at least one second EES having the same ID of the selected public EAS from the ECS (301). The EAS announcer (226) is also configured to send a declare public EAS request message to the at least one second EES; wherein the declare public EAS request message includes the selected public EAS and grouping information. The EAS announcer (226) is also configured to receive a declare public EAS response message from the at least one second EES; wherein the declare public EAS response message includes an acknowledgment.
[0071] The ECS (301) is connected to the first EEC (100) and the EES (150).
[0072] The EAS announcer (226) is configured to determine whether a public EAS has been selected for a multi-user session or a multi-AC session based on the grouping information. The EAS announcer (226) is further configured to send the selected public EAS to the first EEC (100) to initiate the multi-user session or the multi-AC session when the public EAS has been selected for the multi-user session or the multi-AC session based on the grouping information. The EAS announcer (226) is further configured to select a plurality of EASs based on the grouping information when the public EAS has not been selected for the multi-user session or the multi-AC session based on the grouping information; and transmit the plurality of EASs to the first EEC (100).
[0073] Figure 3a is a flow chart (300A) illustrating a method of discovering a public EAS by a first EEC (100) according to embodiments disclosed herein.
[0074] At step 301, a first EEC (100) detects a trigger for EAS discovery.
[0075] In step 302, the first EEC (100) sends an EAS discovery request message to the EES, wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session.
[0076] In step 303, the first EEC (100) receives an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a public EAS that has been selected based on the grouping information.
[0077] In step 304, the first EEC (100) determines a common EAS for establishing a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC based on at least one of the EAS discovery response message and the grouping information.
[0078] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0079] Figure 3b is a flow chart (300B) illustrating a method of discovering a public EAS by an EES according to embodiments disclosed herein.
[0080] In step 305, the EES receives an EAS discovery request message from a first edge enabler client (EEC) (100), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session.
[0081] In step 306, the EES sends an EAS discovery response message to the first EEC (100), wherein the EAS discovery response message includes a plurality of EASs based on the grouping information.
[0082] In step 307, the EES receives a selected EAS announce request message from the first EEC (100), wherein the selected EAS announce request message includes the selected public EAS, wherein the first EEC (100) selects the public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC.
[0083] In step 308, the EES determines at least one second EES to notify the selected common EAS for the multi-user session or the multi-AC session.
[0084] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0085] Figure 4 is a sequence diagram illustrating an EEC-based EAS discovery process for public EAS selection according to embodiments disclosed herein.
[0086] In addition to the AC profile defined in the prior art, the following enhancements to the AC profile including grouping information are proposed in the proposed invention.
[0087] <Table-1 (AC Profile-Enhanced)>
[0088]
[0089] The process for supporting the selection of a common EAS is provided below and is the same for all figures of the proposed invention.
[0090] Same ACID on UEs of different users (known or unknown to each other) within the same EDN
[0091] A set of ACIDs on the UE of the same user in the same EDN
[0092] Each group in the same EDN and the same ACID
[0093] For new UEs requesting to join after a public EAS has been selected
[0094] • Reselect a common EAS to maintain a similar service experience between users (known or unknown to each other) requesting the same ACID, e.g., whenever a new UE is added to or removed from a session due to mobility, unavailability of EAS.
[0095] • Handling race conditions, such as EAS discovery before public EAS announcements to the EES.
[0096] Users can connect to multiple EDNs simultaneously, and multiple EDNs can be available at one location
[0097] The prerequisites are provided below and are the same for all figures of the proposed invention:
[0098] l The AC profile is enhanced with the grouping required information, which tells the AC whether multi-user sessions or multi-AC sessions are required, etc.
[0099] l EAS registers with EES according to clause 8.4.3 EAS registration in TS23.558.
[0100] l EEC-1 is registered to EES-1, and EEC-2 is registered to EES-n.
[0101] l EEC-1 can receive the list of EESs from the ECS associated with the group ID.
[0102] At step 404, the EEC detects a trigger for EAS discovery.
[0103] In step 405, the EEC sends an EAS discovery request message to the EES, wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session.
[0104] In step 406, EEC receives the EAS discovery response message from EES, and EES-1 considers the grouping information as one of the discovery filters to determine the EAS list returned in response to EEC-1's EAS discovery request. The grouping information can be a multi-user session or a multi-AC session or a combination of both. EES-1 checks whether the selected EAS corresponding to the received grouping requirement information from EEC-1 already exists. If it exists, EES returns the selected EAS. Otherwise, EES determines the EAS list.
[0105] In step 407, the EEC determines a public EAS for establishing a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC based on at least one of the EAS discovery response message and the grouping information. In addition, in an embodiment, the public EAS is selected from an EAS list.
[0106] At step 408, the EEC sends the selected EAS announce request message to the EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES; and
[0107] At step 409, the EEC receives the selected EAS announce response message from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0108] In step 410, the first EES (150) determines at least one second EES to notify a selected common EAS for a multi-user session or a multi-AC session.
[0109] Step 410 also includes the selected EES-1 contacting the ECS (301) with the EASID information of the selected EAS to determine which other EESs serve the same EASID. Otherwise, the EES-1 (150) uses the list of other EESs received in the previous step. The ECS (301) provides the endpoint information of the other EESs corresponding to the requested EASID information.
[0110] In step 411, the first EES (150) sends a declare public EAS request message to at least one second EES; wherein the declare public EAS request message includes the selected public EAS and grouping information.
[0111] At step 412, the first EES (150) receives a declare public EAS response message from at least one second EES; wherein the declare public EAS response message includes an acknowledgement.
[0112] In step 413, when EEC-2 accesses EES-n, step 405 will be performed between EEC-2 and EES-n.
[0113] In step 414, the EES-n checks whether the selected EAS is already available for matching the packet information.
[0114] At step 415, the first EES-n will utilize EEC-2 to perform step 406. The EDN configuration information received from the ECS (301) may then be used by EEC-1 and EEC-2 to establish a connection to the common EAS.
[0115] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0116] Figure 5 is a sequence diagram illustrating an EEC-based EAS discovery process and EAS participation according to an embodiment disclosed herein.
[0117] In step 502, the EAS transmits an EAS registration request to EES-1. The request should include an enhanced EAS profile, including the grouping information described in Table 1.
[0118] At step 503, upon successful authorization, EES-1 stores the EAS profile for later use (eg, for servicing EAS discovery requests received from the EEC, etc.), and replies to the EAS with an EAS Registration Response.
[0119] In step 504, EES-1 considers the grouping information from the registered EAS as one of the discovery filters to decide the EAS list returned in response to EEC-1's EAS discovery request. The grouping information can be a multi-user session or a multi-AC session or a combination of both. EES-1 checks whether the selected EAS corresponding to the grouping required information and the AC profile information from EEC-1 already exists based on the grouping information from the registered EAS and the AC profile information of the discovery request from EEC-1. If it exists, EES returns the selected EAS. Otherwise, EES determines the EAS list.
[0120] At step 505, the EES responds to EEC-1 with the selected public EAS information in an EAS discovery response message.
[0121] At step 506, EES-1 determines which other EESs to notify of the selected EAS, eg, serving the same AC within the EDN.
[0122] At step 507, the selected EES-1 then announces the common EAS selection to all determined EESs (EES-n).
[0123] In step 508, EES-n stores the received common EAS information and the information required for grouping, and transmits an acknowledgement back to EES-1.
[0124] In step 509, similar to step 503, EES-n receives the EAS discovery request from EEC-2.
[0125] In step 510, EES-n checks whether the selected EAS corresponding to the AC profile information in the EAS discovery request message from EEC-2 already exists.
[0126] In step 511, when the public EAS is available, EES-n then notifies EEC-2 of the public EAS information.
[0127] In an embodiment, from Figure 5 Steps 508 to 510 may be performed by EEC-1 instead of EES-1. The EDN configuration information received from the ECS (301) may then be used by EEC-1 and EEC-2 to establish a connection to a common EAS.
[0128] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0129] In an embodiment, EEC-1 and EEC-2 of a multi-user session may belong to the same ECSP or different ECSPs, and are used to discover the common EAS of the EEC (100) located in the same service provider domain or different service provider domains. When ECS-2 belongs to a different ECSP, EEC-2 may receive configuration information of the EDN of the other ECSP based on a service level agreement (i.e., via federation) between the two service providers.
[0130] In an embodiment, EES-1 and EEN-n may be in the same EDN or different EDNs for discovering the common EAS of EEC (100) located in the same EDN or different EDNs. When ECS-2 belongs to another EDN, EEC-2 may receive configuration information of another EDN from the common ECS.
[0131] In an embodiment, the ACs of a multi-AC session may be in the same UE or in different UEs, for discovering a common EAS of an EEC (100) located in the same EDN or in different EDNs. When the ACs are located on the same UE, the EEC notifies the other ACs involved in the multi-AC session (UE internal communication, i.e., via EDGE-5) of the selected common EAS. When the ACs are located on different UEs, the EEC notifies another AC located on another UE of the selected common EAS, such as Figure 5 described.
[0132] In one embodiment, when it is desired to use services from a public EAS with service continuity support, steps 504 to 508 are repeated to select a new public EAS.
[0133] In an embodiment, the attributes multi-user session and multi-AC session are part of the AC type attribute of the AC profile or are independent attributes.
[0134] The embodiments disclosed herein may be implemented using at least one hardware device and performing a network management function to control elements.
[0135] In an embodiment, the process supports selection of a common EAS for the same ACID on UEs of different users (known or unknown to each other). Within the same EDN, or for a group of ACIDs on UEs of the same user within the same EDN, or for each group within the same EDN, and for the same ACID or for a new UE requesting to join after a common EAS has been selected, or for reselection of a common EAS, to maintain a similar service experience between users (known or unknown to each other) requesting the same ACID, for example, whenever a new UE is added to or removed from a session due to mobility, unavailability of EAS. Handling of race conditions, such as EAS discovery prior to public EAS announcement to EES or users can be connected to multiple EDNs simultaneously, and there can be multiple available EDNs at one location.
[0136] In an embodiment, EES-1 determines which other EESs are notified of the selected EAS, e.g., serving the same AC within the EDN, according to the procedure in clause 8.8.3.3 of TS23.558, so that EES-1 retrieves EES-n information from the ECS. The selected EES-1 contacts the ECS (301) along with the EASID information of the selected EAS to determine which other EESs serve the same EASID. The ECS (301) provides the endpoint information of the other EESs as described in the table, corresponding to the requested EASID information.
[0137] In an embodiment, the EDN configuration information received from ECS-1 can then be used by EEC-1 and EEC-2 to establish a connection to the common EAS. If the EECs (100) connected to the common EAS do not meet the KPIs (e.g., whenever a new UE is added to or removed from the session due to mobility, unavailability of the EAS), the ACR process should be used to reselect a new common EAS to ensure equivalent KPIs for these EECs. In order to handle any race conditions, the ACR process should be used to reselect a new common EAS to ensure equivalent KPIs for these EECs.
[0138] In an embodiment, from Figure 4 Steps 413 to 415 may be performed by EEC-1 instead of EES-1.
[0139] In an embodiment, EEC-1 and EEC-2 of a multi-user session may belong to the same ECSP or different ECSPs, and are used to discover the common EAS of the EEC (100) located in the same service provider domain or different service provider domains. When ECS-2 belongs to a different ECSP, EEC-2 may receive configuration information of the EDN of the other ECSP based on a service level agreement (i.e., via federation) between the two service providers.
[0140] In an embodiment, EES-1 and EEN-n may be in the same EDN or different EDNs for discovering the common EAS of EEC (100) located in the same EDN or different EDNs. When ECS-2 belongs to another EDN, EEC-2 may receive configuration information of another EDN from the common ECS.
[0141] In an embodiment, the ACs of a multi-AC session can be in the same UE or different UEs, and can be used to discover the public EAS of the EEC (100) located in the same EDN or different EDNs. When the ACs are located on the same UE, the EEC notifies the other ACs involved in the multi-AC session of the selected public EAS (UE internal communication, i.e., through EDGE-5). When the ACs are located on different UEs, the EEC notifies the selected public EAS to the other ACs located in the same EDN or different EDNs via the EEC (100) and the EES. Figure 2 Another AC on the other UE.
[0142] In an embodiment, when it is desired to use services from a public EAS with service continuity support, steps 2 to 6 are repeated to select a new public EAS.
[0143] In an embodiment, the attributes multi-user session and multi-AC session are part of the AC type attribute of the AC profile or are independent attributes.
[0144] Figure 6is a sequence diagram illustrating discovery of a common EAS when multiple EECs are connected to the same EES according to an embodiment disclosed herein.
[0145] At step 601, the EEC detects a trigger for EAS discovery.
[0146] In step 602, the EEC sends an EAS discovery request message to EES-1, wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session.
[0147] In step 603, the EEC receives an EAS discovery response message from EES-1, and EES-1 considers the grouping information as one of the discovery filters to determine the EAS list returned in response to the EAS discovery request of EEC-1. The grouping information can be a multi-user session or a multi-AC session or a combination of both. EES-1 checks whether the selected EAS corresponding to the received grouping requirement information from EEC-1 already exists. If it exists, EES returns the selected EAS. Otherwise, EES determines the EAS list.
[0148] In step 604, the EEC determines a public EAS for establishing a multi-user session or a multi-AC session between the first EEC (100) and the EEC-3 based on at least one of the EAS discovery response message and the grouping information. In addition, in an embodiment, the public EAS is selected from an EAS list.
[0149] In step 605, the EEC sends the selected EAS announce request message to EES-1, wherein the selected EAS announce request message includes the selected public EAS and grouping information to EES-1.
[0150] At step 606, the EEC receives the selected EAS announce response message from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0151] In step 607, similar to step 602, EES-n receives an EAS discovery request from EEC-3.
[0152] In step 608, EES-1 checks whether the selected EAS corresponding to the AC profile information in the EAS discovery request message from EEC-3 already exists.
[0153] When the public EAS is available, EES-1 then informs EEC-3 of the public EAS information at step 609. The EDN configuration information received from the ECS can then be used by EEC-1 and EEC-3 to establish a connection to the public EAS.
[0154] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0155] Figure 7 is a sequence diagram illustrating discovery of a common EAS when multiple EECs are connected to different EESs according to an embodiment disclosed herein.
[0156] In steps 701 and 702, the EEC and EEC-2 perform a common EAS discovery process.
[0157] In step 703, EES-1 determines which other EES are informed of the selected public EAS, for example, serving the same EASID within the EDN, so that the EES retrieves other EES information from the ECS. The EES contacts the ECS (301) with the EASID information of the selected public EAS to determine which other EES serve the same EASID. The ECS (301) provides endpoint information of other EES as described in Table 8.3.3.3.3-2 of 3GPP TS23.558, corresponding to the requested EASID information.
[0158] In step 704, EES-1 then announces the selected common EAS to all determined EESs along with the grouping required information and group ID (if any).
[0159] In step 705, the receiving EES stores the received selected public EAS information along with the grouping required information and group ID (if any), and an acknowledgement is transmitted back to the transmitting EES by EEC-2. The EES, EAS receiving the selected public EAS information is notified of other public EASs via EDGE-3 notification, where the selected public EAS information is different from the information of the public EAS it has already selected. The EAS may initiate EAS-EAS synchronization which is determined and supported by the application, and the details of which are implementation specific.
[0160] The various actions, actions, blocks, steps, etc. in the flowchart (200) may be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some of the actions, actions, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present invention.
[0161] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can easily modify and / or adapt these specific embodiments for various applications by applying current knowledge without departing from the general concepts, and therefore, these adaptations and modifications should and are intended to be understood to be within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced by modification within the scope of the embodiments as described herein.
[0162] According to an embodiment, a method for discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network is provided. The method includes: a first edge enabler client (EEC) (100) detects a trigger for EAS discovery; the first EEC (100) sends an EAS discovery request message to an edge enabler server (EES) (150), wherein the EAS discovery request message includes grouping information of the multi-user session or the multi-AC session; the first EEC (100) receives an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a public EAS that has been selected based on the grouping information; and the first EEC (100) determines, based on at least one of the EAS discovery response message and the grouping information, a public EAS for establishing a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC.
[0163] According to an embodiment, the method includes: sending a selected EAS announce request message by a first EEC (100) to an EES, wherein the selected EAS announce request message includes a selected public EAS and grouping information to the EES; and receiving a selected EAS announce response message by the first EEC (100) from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0164] According to an embodiment, the grouping information includes: a grouping requirement IE, indicating that the application requires grouping; a multi-user session IE, indicating that the application requires a multi-user session; a multi-AC session IE, indicating that multiple ACs are part of the session; a group ID IE, indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE, indicating one or more ACIDs that need to be served by a public EAS as part of a multi-user session.
[0165] According to an embodiment, the selected EAS advertisement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
[0166] According to an embodiment, a method of discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network is provided. The method comprises: receiving, by a first edge enabler server (EES) (150), an EAS discovery request message from a first edge enabler client (EEC) (100), wherein the EAS discovery request message comprises grouping information of a multi-user session or a multi-AC session; sending, by the first EES (150), an EAS discovery response message to the first EEC (100), wherein the EAS discovery response message comprises a plurality of EASs based on the grouping information; receiving, by the first EES (150), a selected EAS announcement request message from the first EEC (100), wherein the selected EAS announcement request message comprises a selected public EAS, wherein the first EEC (100) selects a public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC; and determining, by the first EES (150), at least one second EES to notify the selected public EAS for the multi-user session or the multi-AC session.
[0167] According to an embodiment, determining at least one second EES by a first EES (150) to notify a selected public EAS for a multi-user session or a multi-AC session includes: sending an identifier (ID) of the selected public EAS to an edge configuration server (ECS) by the first EES (150), wherein the ECS (301) determines at least one second EES serving the same ID of the selected public EAS; receiving an identifier of at least one second EES having the same ID of the selected public EAS from the ECS by the first EES (150); sending a declare public EAS request message by the first EES (150) to the at least one second EES; wherein the declare public EAS request message includes the selected public EAS and grouping information; and receiving a declare public EAS response message by the first EES (150) from the at least one second EES; wherein the declare public EAS response message includes a confirmation.
[0168] According to an embodiment, receiving an EAS discovery request message from a first EEC (100) by a first EES (150) includes: determining by the first EES (150) whether a public EAS has been selected for a multi-user session or a multi-AC session based on grouping information; performing by the first EES (150) one of the following: when a public EAS has been selected for a multi-user session or a multi-AC session based on grouping information, sending the selected public EAS to the first EEC (100) to initiate the multi-user session or the multi-AC session; or when a public EAS has not been selected for a multi-user session or a multi-AC session based on grouping information, selecting by the EES a plurality of EASs based on grouping information; and transmitting the plurality of EASs to the first EEC (100).
[0169] According to an embodiment, the grouping information includes: a grouping requirement IE, indicating that the application requires grouping; a multi-user session IE, indicating that the application requires a multi-user session; a multi-AC session IE, indicating that multiple ACs are part of the session; a group ID IE, indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE, indicating one or more ACIDs that need to be served by a public EAS as part of a multi-user session.
[0170] According to an embodiment, the selected EAS advertisement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
[0171] According to an embodiment, a first edge enabler client (EEC) (100) for discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session in a wireless communication network is provided. The first EEC includes: a memory (211); a processor (213); an EAS discoverer (216), coupled to the memory (211) and the processor (213), configured to: detect a trigger for EAS discovery; send an EAS discovery request message to an edge enabler server (EES) (150), wherein the EAS discovery request message includes grouping information of the multi-user session or the multi-AC session; receive an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a selected public EAS based on the grouping information; and determine a public EAS for establishing a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC based on the EAS discovery response message and at least one of the grouping information.
[0172] According to an embodiment, the EAS discoverer (216) is configured to: send a selected EAS announce request message to the EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES; and receive a selected EAS announce response message from the EES, wherein the selected EAS announce response message includes an acknowledgment.
[0173] According to an embodiment, the grouping information includes: a grouping requirement IE, indicating that the application requires grouping; a multi-user session IE, indicating that the application requires a multi-user session; a multi-AC session IE, indicating that multiple ACs are part of the session; a group ID IE, indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE, indicating one or more ACIDs that need to be served by a public EAS as part of a multi-user session.
[0174] According to an embodiment, the selected EAS advertisement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
[0175] According to one embodiment, a first edge enabler server (EES) (150) in a wireless communication network for discovering a common edge application server (EAS) for a multi-user session or a multi-application client (AC) session is provided. The first EES includes: a memory (221); a processor (223); an EAS notifier (226), coupled to the memory (221) and the processor (223), and configured to: receive an EAS discovery request message from a first edge enabler client (EEC) (100), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-AC session; send an EAS discovery response message to the first EEC (100), wherein the EAS discovery response message includes a plurality of EASs based on the grouping information; receive a selected EAS announcement request message from the first EEC (100), wherein the selected EAS announcement request message includes a selected public EAS, wherein the first EEC (100) selects a public EAS from a plurality of EASs for a multi-user session or a multi-AC session between the first EEC (100) and at least one second EEC; and determine at least one second EES to notify the selected public EAS for the multi-user session or the multi-AC session.
[0176] According to an embodiment, determining at least one second EES to notify the selected public EAS for a multi-user session or a multi-AC session includes: sending an identifier (ID) of the selected public EAS to an edge configuration server (ECS), wherein the ECS (301) determines at least one second EES serving the same ID of the selected public EAS; receiving an identifier of at least one second EES having the same ID of the selected public EAS from the ECS; sending a declare public EAS request message to the at least one second EES; wherein the declare public EAS request message includes the selected public EAS and grouping information; and receiving a declare public EAS response message from the at least one second EES; wherein the declare public EAS response message includes a confirmation.
[0177] According to an embodiment, receiving an EAS discovery request message from a first EEC (100) includes: determining whether a public EAS has been selected for a multi-user session or a multi-AC session based on grouping information; performing one of the following: when a public EAS has been selected for a multi-user session or a multi-AC session based on the grouping information, sending the selected public EAS to the first EEC (100) to initiate the multi-user session or the multi-AC session; or when a public EAS has not been selected for the multi-user session or the multi-AC session based on the grouping information, selecting a plurality of EASs based on the grouping information; and transmitting the plurality of EASs to the first EEC (100).
[0178] According to an embodiment, the grouping information includes: a grouping requirement IE indicating that the application requires grouping; a multi-user session IE indicating that the application requires a multi-user session; a multi-AC session IE indicating that multiple ACs are part of the session; a group ID IE indicating the ID of the grouping of users of the same AC or the grouping of ACs; and an ACID list IE indicating one or more ACIDs that need to be served by a public EAS as part of a multi-user session.
[0179] According to an embodiment, the selected EAS announcement request message includes an AC ID, an EAS ID, an EAS endpoint, and a user equipment ID.
Claims
1. A method performed by a first edge enabler client (EEC) in a wireless communication network, the method include: Detection of triggers for edge application server (EAS) discovery; Sending an EAS discovery request message to an edge enabler server (EES), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-application client (AC) session; receiving an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a selected public EAS based on the grouping information; as well as Based on at least one of the EAS discovery response message and grouping information, a common EAS for establishing the multi-user session or the multi-AC session between the first EEC and at least one second EEC is determined.
2. The method according to claim 1, include: sending the selected EAS announce request message to the EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES; and A selected EAS announce response message is received from the EES, wherein the selected EAS announce response message includes the acknowledgment.
3. The method according to claim 1, in, The grouping information includes at least one of the following: Grouping Required Information Element (IE), indicating that the application requires grouping; Multi-user session IE, indicating that the application requires multi-user sessions; A multi-AC session IE indicates that multiple ACs are part of the session; Group ID IE, indicating the ID of a group of users or a group of ACs for the same AC; as well as The ACID List IE indicates one or more ACIDs that need to be served by the public EAS as part of the multi-user session.
4. The method according to claim 1, in, The selected EAS announcement request message includes at least one of the AC ID, EASID, EAS endpoint, and user equipment ID.
5. A method performed by a first edge enabler server (EES) in a wireless communication network, the method include: receiving an edge application server (EAS) discovery request message from a first edge enabler client (EEC), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-application client (AC) session; sending an EAS discovery response message to the first EEC, wherein the EAS discovery response message includes a plurality of EASs based on the grouping information; receiving a selected EAS announce request message from the first EEC, wherein the selected EAS announce request message includes a selected public EAS, wherein the first EEC selects the public EAS from the plurality of EASs for the multi-user session or the multi-AC session between the first EEC and at least one second EEC; as well as At least one second EES is determined to inform the selected common EAS for the multi-user session or the multi-AC session.
6. The method according to claim 5, in, Determining at least one second EES to notify the selected common EAS for the multi-user session or the multi-AC session includes: sending an identifier (ID) of the selected public EAS to an edge configuration server (ECS), wherein the ECS determines the at least one second EES serving the same ID of the selected public EAS; receiving from the ECS an ID of the at least one second EES having the same ID of the selected public EAS; sending a declare public EAS request message to the at least one second EES, wherein the declare public EAS request message includes the selected public EAS and the grouping information; and A declare public EAS response message is received from the at least one second EES, wherein the declare public EAS response message includes the acknowledgment.
7. The method according to claim 5, in, Receiving the EAS discovery request message from the first EEC includes: determining whether the common EAS has been selected for the multi-user session or the multi-AC session based on the grouping information; Do one of the following: When the public EAS has been selected for the multi-user session or the multi-AC session based on the grouping information, sending the selected public EAS to the first EEC to initiate the multi-user session or the multi-AC session; or When the common EAS is not selected for the multi-user session or the multi-AC session based on the grouping information, selecting the plurality of EASs based on the grouping information; and The plurality of EASs are transmitted to the first EEC.
8. The method according to claim 5, in, The grouping information includes at least one of the following: Grouping Required Information Element (IE), indicating that the application requires grouping; Multi-user session IE, indicating that the application requires multi-user sessions; A multi-AC session IE indicates that multiple ACs are part of the session; Group ID IE, indicating the ID of a group of users or a group of ACs for the same AC; as well as The ACID List IE indicates one or more ACIDs that need to be served by the public EAS as part of the multi-user session.
9. The method according to claim 5, in, The selected EAS announcement request message includes at least one of the AC ID, EASID, EAS endpoint, and user equipment ID.
10. A first edge enabler client (EEC) in a wireless communication network, the EEC include: Memory; processor; an edge application server (EAS) discoverer, coupled to the memory and the processor, and configured to: Detecting triggers for EAS discovery; Sending an EAS discovery request message to an edge enabler server (EES), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-application client (AC) session; receiving an EAS discovery response message from the EES, wherein the EAS discovery response message includes at least one of a plurality of EASs or a selected public EAS based on the grouping information; as well as Based on at least one of the EAS discovery response message and grouping information, a common EAS for establishing the multi-user session or the multi-AC session between the first EEC and at least one second EEC is determined.
11. The first EEC according to claim 10, in, The EAS discoverer is configured to: sending the selected EAS announce request message to the EES, wherein the selected EAS announce request message includes the selected public EAS and grouping information to the EES; and A selected EAS announce response message is received from the EES, wherein the selected EAS announce response message includes the acknowledgment.
12. The first EEC according to claim 10, in, The grouping information includes at least one of the following: Grouping Required Information Element (IE), indicating that the application requires grouping; Multi-user session IE, indicating that the application requires multi-user sessions; A multi-AC session IE indicates that multiple ACs are part of the session; Group ID IE, indicating the ID of a group of users or a group of ACs for the same AC; as well as The ACID List IE indicates one or more ACIDs that need to be served by the public EAS as part of the multi-user session.
13. The first EEC according to claim 10, in, The selected EAS announcement request message includes at least one of the AC ID, the EAS ID, the EAS endpoint, and the user equipment ID.
14. A first edge enabler server (EES) in a wireless communication network, wherein the first EES include: Memory; processor; an edge application server (EAS) notifier, coupled to the memory and the processor, and configured to: receiving an EAS discovery request message from a first edge enabler client (EEC), wherein the EAS discovery request message includes grouping information of a multi-user session or a multi-application client (AC) session; sending an EAS discovery response message to the first EEC, wherein the EAS discovery response message includes a plurality of EASs based on the grouping information; receiving a selected EAS announce request message from the first EEC, wherein the selected EAS announce request message includes a selected public EAS, wherein the first EEC selects the public EAS from the plurality of EASs for the multi-user session or the multi-AC session between the first EEC and at least one second EEC; as well as At least one second EES is determined to inform the selected common EAS for the multi-user session or the multi-AC session.
15. The first EES according to claim 14, in, The EAS Advertiser is configured to: sending an identifier (ID) of the selected public EAS to an edge configuration server (ECS), wherein the ECS determines the at least one second EES serving the same ID of the selected public EAS; receiving from the ECS an identifier of the at least one second EES having the same ID of the selected public EAS; sending a declare public EAS request message to the at least one second EES, wherein the declare public EAS request message includes the selected public EAS and the grouping information; as well as A declare public EAS response message is received from the at least one second EES, wherein the declare public EAS response message includes the acknowledgment.
