METHOD AND SYSTEM FOR MANAGING DISCOVERY OF EDGE APPLICATION SERVERS

Abstract

The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. Embodiments herein provide a method for method for managing discovery of an edge application servers (310). The method includes sending, by an edge enabler client (120) of a UE (100), an initial service provisioning request to an edge configuration server (400). Further, the method includes receiving, by the edge enabler client (120), an initial service provisioning response comprises an information element from the edge configuration server (400), where the information element indicates the supported discovery mode. Further, the method sending, by the edge enabler client (120), a request for discovering the edge application server (310) to at least one of the edge configuration server (400), a dedicated server for an edge application server information, and a Domain Name System (DNS) server based on the supported discovery mode.

Claims

1. A method for handling an Protocol Data Unit (PDU) session during an emergency service, the method comprises: detecting, by an AMF server, that one of a User Equipment (UE) has a PDU session for an emergency service and the UE is establishing a PDU session for the emergency service; detecting, by the AMF server, that a network slice authentication and authorization fails for all allowed Network Slice Selection Identifier (NSSAI); and performing, by the AMF server, a predetermined operation based on the detection.

2. The method of claim 1, wherein the predetermined operation is comprising: avoiding register with the UE.

3. The method of claim 2, wherein the predetermined operation is further comprising: sending a configuration update command including a rejected NS SAI and a predetermined rejection cause value to the UE.

4. The method of claim 3, wherein the predetermined rejection cause value includes # 62.

5. The method as claimed in claim 4, further comprises: determining, by the AMF server, that the PDU session for the emergency service is released; de-registering, by the AMF server, with the UE in response to determining that the PDU session for the emergency service is released; and sending, by the AMF server, a deregistration request message with the predetermined rejection cause value to the UE.

6. A method for handling a Protocol Data Unit (PDU) session during an emergency service, the method comprises: receiving, by the UE, a deregistration request message with a predetermined rejection cause value from an AMF server; selecting, by the UE, an Evolved Terrestrial Radio Access Network (E-UTRAN) cell of a network; initiating, by the UE, an attach procedure to the network based on the deregistration request message; and disabling, by the UE, an N1 mode capability for a 3GPP access based on the attach procedure.

7. The method of claim 6, wherein the predetermined rejection cause value includes # 62.

8. A system for handling a PDU session during an emergency service, comprising: a UE, and an AMF server, wherein the AMF server is configured to: detect one of a User Equipment (UE) has a PDU session for an emergency service and the UE is establishing a PDU session for the emergency service; detect a network slice authentication and authorization fails for all allowed Network Slice Selection Identifier (NSSAI); and perform a predetermined operation based on the detection.

9. The system of claim 8, wherein AMF server is further configured to not deregister the UE.

10. The system of claim 9, wherein AMF server is further configured to send a configuration update command including a rejected NSSAI and a predetermined rejection cause value to the UE deregister the UE.

11. The system as claimed in claim 8, wherein the AMF server is configured to: determine that the PDU session for the emergency service is released; de-register with the UE in response to determining that the PDU session for the emergency service is released; and send a deregistration request message with the rejection cause value to the UE.

12. The system as claimed in claim 11, wherein the UE is configured to: select a E-UTRAN cell of a network and initiating an attach procedure to the network based on the deregistration request message; and disable an N1 mode capability for a 3GPP access.

13. An AMF server for handling a Protocol Data Unit (PDU) session during an emergency service, comprises: a memory; and a processor, coupled with the memory, configured to: detect one of a User Equipment (UE) has a PDU session for an emergency service and the UE is establishing a PDU session for the emergency service; detect a network slice authentication and authorization fails for all allowed Network Slice Selection Identifier (NSSAI); and perform at least one of: avoid register with the UE, and send a configuration update command including a rejected NSSAI and a rejection cause value # 62 to the UE.

14. The AMF server as claimed in claim 13, wherein the processor is configured to: determine that the PDU session for the emergency service is released; de-register with the UE in response to determine that the PDU session for the emergency service is released; and send a deregistration request message with the rejection cause value # 62 to the UE.

15. A UE for handling a Protocol Data Unit (PDU) session during an emergency service, comprises: a memory; and a processor, coupled with the memory, configured to: receive a deregistration request message with the rejection cause value # 62 from an AMF server; select an Evolved Terrestrial Radio Access Network (E-UTRAN) cell of a network; initiate an attach procedure to the network based on the deregistration request message; and disable a N1 mode capability for a 3GPP access based on the attach procedure.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0054] This method and apparatus 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:

[0055] FIG. 1 illustrates a general architecture of an edge computing system (1000) for enabling an edge application server (310) in a 3GPP network, according to a prior art;

[0056] FIG. 2 is a block diagram of a UE (100), according to an embodiment as disclosed herein;

[0057] FIG. 3a is a flow chart illustrating a method, implemented by the UE (100), for managing discovery of the edge application servers (310), according to an embodiment as disclosed herein;

[0058] FIG. 3b is a flow chart illustrating a method, implemented by the centralized edge enabler server (620), for managing discovery of the edge application servers (310), according to an embodiment as disclosed herein;

[0059] FIG. 3c is a flow chart illustrating a method for handling an PDU session during an emergency service, according to an embodiment as disclosed herein;

[0060] FIG. 3d is a flow chart illustrating a method for managing services provided to at least one of an edge application server (310) and an edge enabler client (120) of the UE (100), according to an embodiment as disclosed herein;

[0061] FIG. 3e is a flow chart illustrating a method for handling the PDU session during the emergency service, according to an embodiment as disclosed herein;

[0062] FIG. 4 illustrates signaling between the UE (100) and an edge configuration server (400) for provisioning the UE with configurations from the edge configuration server (400), according to an embodiment as disclosed herein;

[0063] FIG. 5 illustrates a proposed architecture of the edge computing system (1000) for enabling the edge application server (310) in the 3GPP network, according to an embodiment as disclosed herein;

[0064] FIG. 6 illustrates a proposed architecture of the edge computing system (1000) for publishing and discovering a service Application Programming Interface (API) of the edge application server (310) by using a Common API Framework (CAPIF) core function, according to an embodiment as disclosed herein;

[0065] FIG. 7 is a sequential diagram illustrating a method for managing an application context relocation, according to an embodiment as disclosed herein;

[0066] FIG. 8 illustrates an overview of a system (1000) for handling an PDU session during an emergency service, according to an embodiment as disclosed herein; and

[0067] FIG. 9 is a block diagram of an AMF server (800), according to an embodiment as disclosed herein.

DETAILED DESCRIPTION

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

[0069] 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 managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and 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 disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0070] Accordingly, the embodiments herein disclose a method for managing discovery of an edge application servers (310. The method includes sending, by an edge enabler client (120) of a UE (100), an initial service provisioning request to an edge configuration server (400). Further, the method includes receiving, by the edge enabler client (120) of the UE (100), an initial service provisioning response comprises an information element from the edge configuration server (400), where the information element indicates the supported discovery mode. Further, the method sending, by the edge enabler client (120) of the UE (100), a request for discovering the edge application server (310) to at least one of the edge enabler server (400), a dedicated server for an edge application server information, and a Domain Name System (DNS) server based on the supported discovery mode.

[0071] Unlike existing methods and systems, the proposed method allows an edge computing service provider to assist a UE for selecting a right discovery method. Further, the UE can adjust its behavior according to the selected discovery method and determine an availability of an edge application server in an edge data network using the discovery method. Thus, the proposed method reduces a complexity in an edge computing system in choosing the right discovery method for determining the availability of the edge application server in the edge data network.

[0072] Unlike existing methods and systems, a centralized edge enabler server contains information about service APIs of all edge application servers of all edge data networks. In response to receiving a request for relocation of an application context, the centralized edge enabler server identifies a second edge data network suitable for transferring the application context from a first edge data network. The centralized edge enabler server identifies the second edge data network based on the information about service APIs of an edge application server in the second edge data network. A latency in accessing a service at the UE will get reduced due to transferring the application context from the first edge data network to the second edge data network. Thus, the proposed method improves a user experience due to a reduced latency in accessing the service.

[0073] Referring now to the drawings, and more particularly to FIGS. 2 through 9, there are shown preferred embodiments.

[0074] FIG. 2 is a block diagram of a UE (100), according to an embodiment as disclosed herein. Examples for the UE (100) are, but not limited to a smart phone, a tablet computer, a personal digital assistance (PDA), an Internet of Things (IoT), an immersive device, a virtual reality device and the like. In an embodiment, the UE (100) includes an application client (110), an edge enabler client (120), a memory (130), a processor (140), a communicator (150), an edge application server discovery controller (160) and an emergency service based PDU session controller (170). The processor (140) is coupled with the application client (110), the edge enabler client (120), the memory (130), the communicator (150), the edge application server discovery controller (160), and the emergency service based PDU session controller (170).

[0075] The edge enabler client (120) provides supporting functions needed for the application client (110) through a reference point, i.e. an edge (5). The edge application server discovery controller (160) is operated with the edge enabler client (120). The edge application server discovery controller (160) is configured to send the initial service provisioning request to an edge configuration server (400) and receive an initial service provisioning response comprises an information element from the edge configuration server (400). The information element indicates the supported discovery mode. Further, the edge application server discovery controller (160) is configured to send a request for discovering the edge application server (310) to at least one of the edge configuration server (400), a dedicated server for an edge application server information, and a DNS server based on the supported discovery mode.

[0076] The emergency service based PDU session controller (170) receives a deregistration request message with the rejection cause value # 62 from an AMF server (800). Further, the emergency service based PDU session controller (170) selects an E-UTRAN cell of a network and initiates an attach procedure to the network based on the deregistration request message. Based on the attach procedure, the emergency service based PDU session controller (170) disables a N1 mode capability for a 3GPP access.

[0077] 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 an Electrically Programmable Memory (EPROM) or an Electrically Erasable and Programmable Memory (EEPROM).

[0078] 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 some examples, the memory (130) can be configured to store larger amounts of information than the memory (130) respectively. 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).

[0079] The processor (140) is configured to execute instructions stored in the memory (130). The communicator (150) is configured to communicate internally between hardware components in UE (100) and the server.

[0080] Although the FIG. 2 shows the hardware components of the UE (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the UE (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 for managing discovery of the edge application servers (310).

[0081] FIG. 3a is a flow chart (S300a) illustrating a method, implemented by the UE (100), for managing discovery of the edge application server (310) of the edge data network (300), according to an embodiment as disclosed herein.

[0082] At S302a, the method includes sending, by the edge enabler client (120), the initial service provisioning request to the edge configuration server (400). At S304a, the method includes receiving, by the edge enabler client (120), the initial service provisioning response comprises an information element from the edge configuration server (400). The information element indicates the supported discovery mode. At S306a, the method sending, by the edge enabler client (120), the request for discovering the edge application server (310) to at least one of the edge configuration server (400), a dedicated server for an edge application server information, and a DNS server based on the supported discovery mode.

[0083] FIG. 3b is a flow chart (S300b) illustrating a method, implemented by the centralized edge enabler server (620), for managing discovery of the edge application servers (310, according to an embodiment as disclosed herein.

[0084] At S302b, the method includes receiving, by the centralized edge enabler server (620), the message comprising the service application programming interface (API) publish and discovery information from at least one edge application server (310). At S304b, the method includes providing at least one of an edge application access to a service API offered by the at least one edge application server (310) in the edge data network (300) by providing Common API Framework (CAPIF) function based on the received message. At S306b, the method includes providing at least one of a function for the edge application server service APIs publish and discovery response to the the at least one edge application server (310) based on the received message.

[0085] FIG. 3c is a flow chart (300c) illustrating a method for handling a PDU session during an emergency service, according to an embodiment as disclosed herein. At S302c, the method includes detecting, by an AMF server (800), one of a UE (100) has a PDU session for an emergency service and the UE (100) is establishing a PDU session for the emergency service. At S304c, the method includes detecting, by the AMF server (800), a network slice authentication and authorization fails for all allowed Network Slice Selection Identifier (NSSAI). At S306c, the method includes avoiding registering, by the AMF server, with the UE (100). At S308c, the method includes sending the configuration update command including a rejected NSSAI and a rejection cause value to the UE (100).

[0086] FIG. 3d is a flow chart (300d) illustrating a method for managing services provided to at least one of an edge application server (310) and an edge enabler client (120) of the UE (100), according to an embodiment as disclosed herein. At 302d, the method includes receiving a request message comprising a service support request from one or more edge application server (310a and 310b) and the UE (100). At 304d, the method includes configuring the response message comprising the service support information based on the request message. At 306d, the method includes sending the response message comprising the service supporting information to at least one of the edge application server (310) and the edge enabler client (120) of the UE (100).

[0087] FIG. 3e is a flow chart (300e) illustrating a method for handling the PDU session during the emergency service, according to an embodiment as disclosed herein. At 302e, the method includes receiving the deregistration request message with the rejection cause value # 62 from the AMF server (800). At 304e, the method includes selecting the E-UTRAN cell of the network. At 306e, the method includes initiating an attach procedure to the network based on the deregistration request message. At 308e, the method includes disabling a N1 mode capability for a 3GPP access based on the attach procedure.

[0088] The various actions, acts, blocks, steps, or the like in the flow diagram S300a, S300b, S300c, S300d and S300e 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.

[0089] FIG. 4 illustrates signaling between the UE (100) and the edge configuration server (400) for provisioning the UE (100) with configurations from the edge configuration server (400), according to an embodiment as disclosed herein. Various discovery methods available for the UE (100) to determine the availability of the edge enabler server (320) at the edge data network (300) are given below:

[0090] 1) Distributed discovery: The edge enabler client (120) can query to the edge enabler server (320) for obtaining information about the edge application server (310).

[0091] 2) Centralized discovery: The edge enabler client (120) can query to the edge configuration server (400) for obtaining the information about the edge application server (310).

[0092] 3) Hybrid discovery: The edge configuration server (400) can redirect the edge enabler client (120) to the edge enabler server (320). Further, the edge enabler server (320) can provide the information about the edge application server (310) to the edge enabler client (120).

[0093] 4) Dedicated server based discovery: The edge configuration server (400) can redirect the edge enabler client (120) to a dedicated server. Further, the dedicated server can provide the information about the edge application server (310) for a security of the information.

[0094] 5) DNS based discovery: The edge enabler client (120) can obtain the information about the edge application server (310) by communicating to a dedicated/shared DNS server.

[0095] The edge enabler client (120) performs provisioning with configuration information (i.e. information about the edge application server (310) obtained from the edge configuration server (400) to enable communication between the application client (110) and the edge application server (310) having the services.

[0096] In an embodiment, the UE (100) includes a dedicated edge data network configuration client for receiving the configuration information from the edge configuration server (400). In an embodiment, a DNS server can be used to provide discovery methods to the UE (100).

[0097] The proposed method for determining the availability of the edge enabler server (320) at the edge data network (300) in steps 401-402. At step 401, the edge enabler client (120) sends an initial service provisioning request to the edge configuration server (400). At step 402, the edge configuration server (400) sends an initial service provisioning response includes the configuration information to the UE (100). Information elements in the configuration information is given in table 1. ‘Discovery mode’ and ‘other provisioning related information’ are the information elements in the configuration information.

TABLE-US-00001 TABLE 1 Table 1: Initial service provisioning response Information elements Status Description Discovery mode M The supported mode of discovery. Other provisioning M Other provisioning related related information. information

[0098] The information element ‘discovery mode’ indicates the discovery method supported by the edge data network (300). In an embodiment, the discovery mode is specific to at least one of the UE (100), a location of the UE (100), an application, an application type, an application category.

[0099] In an embodiment, the UE (100) determines the discovery mode based on the configuration information received in the provisioning response. For example, when the initial service provisioning response includes a DNS resolver configuration, then the UE (100) determines that the discovery mode that is supported by the edge data network (300) is the DNS based discovery. In another example, when the initial service provisioning response includes an EAS configuration, then the UE (100) determines that the discovery mode that is supported by the edge data network (300) is the centralized discovery.

[0100] In an embodiment, the UE (100) continues to use one discovery mode unless the configuration information is either explicitly changed by the edge configuration server (400) or changed because of sending another provisioning request by the UE (100). When a service area of the UE (100) ever changes, then the UE (100) sends another provisioning request.

[0101] In an embodiment, if the multiple discovery methods are used in the deployment of the edge computing service, and when the edge configuration server (400) distributes the information about the edge application server (310) to different edge enabler servers (not shown), then the edge configuration server (400) includes information about an entity from which the UE (100) needs to query for the information about the edge application server (310) along with the discovery mode information element.

[0102] Such an implicit determination will fail in case the initial service provisioning response includes the information about the edge enabler server (320) that leads to two discovery modes. Consider, the two discovery modes are the distributed discovery and the hybrid discovery. In case of the distributed discovery, the UE (100) needs to direct all future discovery requests to the edge enabler server (320). In case of the hybrid discovery, the initial service provisioning request from the UE (100) should be first directed to the edge configuration server (400) for all discovery needs. Therefore, having an explicit indication of the supported mode as described in this invention is deterministic.

[0103] Having the indication of the discovery mode in the initial service provisioning response clarifies a course of action for the UE (100). Therefore, the UE (100) can adjust its behavior based on the discovery mode. For example, the UE (100) can decide whether to subscribe for notifications with the edge enabler server (320) or the edge configuration server (400) based on the initial service provisioning response. Names of the servers used here are only for illustrative purpose and does not limit the scope of the invention. In real time, various other names of the server based on a scenario can be used.

[0104] FIG. 5 illustrates a proposed architecture of the edge computing system (1000) for enabling the edge application server (310) in the 3GPP network (200), according to an embodiment as disclosed herein. The proposed architecture of the edge computing system (1000) includes the UE (100), the 3GPP network (200), the centralized edge enabler server (620), and a plurality of edge data networks (300A, 300B). An edge application server (310A) and an edge enabler server (320A) of the edge data network (300A) communicates through an edge (3) of the edge data network (300A), i.e. edge (3A). The edge data network (300A) communicates with the UE (100) through an application data traffic (500A). The edge data network (300A) communicates with the centralized edge enabler server (620) through a reference point called as an edge (8A). An edge application server (310B) and an edge enabler server (320B) of the edge data network (300B) communicate through an edge (3) of the edge data network (300A), i.e. edge (3B). The edge data network (300A) communicates with the UE (100) through an application data traffic (500B). The edge data network (300A) communicates with the centralized edge enabler server (620) through a reference point called as an edge (8B). The centralized edge enabler server (620) communicates with the edge enabler client (120) of the UE (100) and the 3GPP network (200) through an edge (1) and an edge (2) respectively, where the edge (1) and the edge (2) are reference points.

[0105] The centralized edge enabler server (620) provides supporting functions needed for the edge application servers (310A, 310B). The edge (8A) and the edge (8B) are reference points between the centralized edge enabler server (620) and the edge application servers (310A, 310B), where the edge (8A) and the edge (8B) supports interactions related to the edge enabler layers. The edge (8A) and the edge (8B) allows registration of the edge application servers (310A, 310B) with availability information such as time constraints, location constraints, etc. Further, the edge (8A) and the edge (8B) allows the UE (100) to access to network capability information such as a location information. The centralized edge enabler server (620) allows the edge application servers (310A, 310B) to publish the information about the edge application servers (310A, 310B) from multiple edge data networks (300A, 300B) to provide profile/availability information of the edge application servers (310A, 310B) such as, a geographical area of availability of the edge application servers (310A, 310B), a time of operation of the edge application servers (310A, 310B), etc.

[0106] The centralized edge enabler server (620) determines whether an application context for the UE (100) is to be relocated and to provide related instruction to a source edge application server (310C). The source edge application servers (310C) prepares the application context required for the UE (100) to be relocated and transfer the application context to a target edge application server (310D). The centralized edge enabler server (620) provides an IP address of the target edge application server (310D) to the UE (100) while relocating the application context.

[0107] The centralized edge enabler server (620) exposes a location reporting API to the edge application servers (310A, 310B) across multiple edge data networks (300A, 300B), in order to support tracking or checking the valid location of the UE (100). The location reporting API exposed by the edge application servers (310A, 310B) relies on a SCEFN/NEF northbound API for monitoring event of the location of the UE (100).

[0108] The centralized edge enabler server (620) exposes a UE identifier API to the edge application servers (310A, 310B) in order to provide a valid UE identifier for a capability exposure API over the edge (8A) and the edge (8B). The capability exposure API enables the edge application servers (310A, 310B) to point to a user anonymously over different service APIs exposed by the centralized edge enabler server (620).

[0109] The centralized edge enabler server (620) provides supporting functions needed for the edge enabler client (120) located within the UE (100). The interactions related to enabling edge computing between the centralized edge enabler server (620) and the edge enabler client (120) are supported by the edge (1). The edge (1) allows retrieval and provisioning of the configuration information for the UE (100). Further, the edge (1) allows discovery of the edge application servers (310A, 310B) available in the multiple edge data networks (300A, 300B).

[0110] The centralized edge enabler server (620) allows the edge enabler client (120) to discover the edge application servers (310A, 310B) across the multiple edge data networks (300A, 300B).

[0111] The centralized edge enabler server (620) allows a subscription from the edge enabler client (120) to the centralized edge enabler server (620) for a dynamic information such as a dynamic availability of the edge application servers (310A, 310B). In an embodiment, the subscription is very specific to one of the edge application servers (310A, 310B). In another embodiment, the subscription is generic to include all the edge application servers (310A, 310B).

[0112] The centralized edge enabler server (620) provides supporting functions needed for the 3GPP network (200). The edge (2) is the reference point that allow the interactions related to edge enabler layers between the edge enabler servers (320A, 320B) and the 3GPP network (200). The edge (2) allows an access to 3GPP network functions and APIs for retrieval of the network capability information.

[0113] In another embodiment, the centralized edge enabler server (620) can be deployed in a scenario when a distributed edge enabler server (320B) is not deployed within the edge data network (300A) and the centralized edge enabler server (620) supports the functionalities and the reference points. In another embodiment, the centralized edge enabler server (620) can be deployed within the 3GPP network (200) when the centralized edge enabler server (620) supports the functionalities and the reference points. In another embodiment, the centralized edge enabler server (620) can be deployed in another edge data network (300B) when the functionalities and the reference points are supported by the centralized edge enabler server (620).

[0114] FIG. 6 illustrates a proposed architecture of the edge computing system (1000) for publishing and discovering service APIs (314A, 314B) of the edge application server (310A, 310B) by using the CAPIF core function (621), according to an embodiment as disclosed herein. The centralized edge enabler server (620) includes a CAPIF core function (621). A PLMN trust domain (700) of the edge computing system (1000) includes edge application servers (310A, 310B), a centralized edge enabler server (620), and a PLMN edge application server (305B), where the edge application server (310B) and the PLMN edge application server (305B) is included in the edge data network (300B). A third-party edge application server (305A) and an edge application server (310A) are part of an edge data network (300A), whereas the third party edge application server (305A) is not included in the PLMN trust domain (700).

[0115] The centralized edge enabler server (620) allows the edge application server (305A, 305B) owned by a third party or a PLMN operator for accessing the service APIs (314A, 314B) offered by other edge application servers (310A, 310B) within and across the edge data network (300A, 300B) by providing the CAPIF core function (621). In an embodiment, the third-party edge application server (305A) provides service APIs and the third-party edge application server (305A) exists outside the PLMN trust domain (700). The third-party edge application server (305A) are allowed to utilize the CAPIF core function (621) of the PLMN trust domain (700).

[0116] The centralized edge enabler server (620) provides the following function for publish and discovery of the service APIs (314A, 314B) of the edge application servers (310A, 310B). The CAPIF core function (621) allows onboarding of the edge application servers (310A, 310B) (i.e. API invokers), publishing of the service APIs (314A, 314B), discovering the service APIs (314A, 314B) and charging for invocations of the service APIs (314A, 314B).

[0117] The edge application servers (310A, 310B) provide the following function for publishing and discovering the service APIs (314A, 314B). The API exposing function (311A) allows the invocation of the service APIs (314A) exposed from the edge application server (310A) via CAPIF (2e). The API exposing function (311B) allows the invocation of the service APIs (314B) exposed from the edge application server (310B) via CAPIF (2). Further, the API exposing function (311A, 311B) allows charging for invocations of the service APIs (314A, 314B) via CAPIF (3). The API publishing function (312A, 312B) allows the publishing of the service APIs (314A, 314B) to the CAPIF core function (621) of the centralized edge enabler server (620) via CAPIF (4). The API management function (313A, 313B) allows a management of the service APIs (314A, 314B) to the CAPIF core function (621) via CAPIF (5).

[0118] Further, following procedures are performed as specified in 3GPP TS 23.222. The edge application servers (310A, 310B) act as the API exposing functions (312A, 311B) and the edge application servers (310A, 310B) publishes the service APIs (314A, 314B) to the CAPIF core function (621) of the centralized edge enabler server (620). The service APIs (314A, 314B) of the edge data networks (300A, 300B) are made available to each other by the CAPIF core function (621). The edge application servers (310A, 310B) acts as the API invokers and is onboarded to the CAPIF core function (621). The edge application servers (310A, 310B) (i.e. API invokers) are authenticated with the CAPIF core function (621). The edge application servers (310A, 310B) discovers the service APIs (314A, 314B) published by the edge application servers (310A, 310B) via the CAPIF core function (621) by including end point address of the API exposing functions (311A, 311B). The service API invocation is performed based on the end point address. The edge application servers (310A, 310B) obtains authorization to invoke the service APIs (314A, 314B) from the CAPIF core function (621). The edge application servers (310A, 310B) invokes the service APIs (314A, 314B) after performing authentication with the CAPIF core function (621).

[0119] FIG. 7 is a sequential diagram illustrating a method for managing an application context relocation, according to an embodiment as disclosed herein. Consider an example scenario, the UE (100) is playing an online video by receiving data of the online video from a first edge data network (i.e. source edge data network) (300C). Later the UE (100) moves from the first geographical location and reaches a second geographical location while playing the online video, where a second edge data network (target edge data network) (300C) is more closer to the UE (100) than the first edge data network (300C). The centralized edge enabler server (620) supports the application context relocation from the source edge data network (300C) to the target edge data network (300D), where the application context as per the example scenario is a position in the online video from which the UE (100) needs to switch receiving the data of the online video from the second edge data network (300D).

[0120] At step 701, the source edge data network (300C) determines the application context relocation, in response to receiving a request from the UE (100). At step 702, the source edge data network (300C) sends a request for the application context relocation to the centralized edge enabler server (620). In an embodiment, the request for the application context relocation includes a UE information, a source application instance information, a Core Network-Network Function information, an application identifier, and an Edge Enabler Client registration context. At step 703, the centralized edge enabler server (620) acknowledges to the source edge data network (300C) in response to receiving the request for the application context relocation.

[0121] At step 704A, the source edge data network (300C) transfers the application context to the centralised edge enabler server (620). At step 704B, the centralised edge enabler server (620) forwards the application context to the centralised edge application server 610. At step 705A, the centralised edge application server (610) acknowledges to the centralised edge enabler server (620) in response to receiving the application context. At step 705B, the centralised edge enabler server (620) acknowledges to the source edge data network (300C) in response to receiving the acknowledgment from the centralised edge application server (610). The centralized edge enabler server (620) temporarily holds the application context until the target edge data network (300D) is determined. At step 706, the centralized edge enabler server (620) determines an information regarding the target edge data network (300D).

[0122] At step 707, the centralized edge enabler server (620) sends the request for the application context relocation to the target edge data network (300D). At step 708, the target edge data network (300D) acknowledges to the centralized edge enabler server (620) in response to receiving the request for the application context relocation. At step 709, the target edge data network (300D) sends an application context relocation response to the centralized edge enabler server (620). In an embodiment, the application context relocation response includes the UE information, an accepted Src application instance information, and a temporary edge application server information. At step 710, the centralized edge enabler server (620D) transfers the application context to the target edge data network (300D), in response to receiving the application context relocation response. At step 711, the centralized edge enabler server (620) sends the application context relocation response to the source edge data network (300C). At step 712, the source edge data network (300C) triggers an Application Function request to influence on traffic routing.

[0123] FIG. 8 illustrates an overview of a system (1000) for handling a PDU session during an emergency service, according to an embodiment as disclosed herein.

[0124] The proposed method for managing the UE (100) and a network (not shown) for a scenario when the UE (100) has a PDU session for emergency services is described as follows. The UE (100) sends a registration request message containing a NSSAI request to an AMF (800). The AMF server (800) process the registration request message. The AMF server (800) initiates a network slice-specific authentication and authorization procedure for an S-NSSAI present in the NSSAI request which are subject to a network slice-specific authentication and authorization.

[0125] When the network slice-specific authentication and authorization fails for all S-NSSAIs in an allowed NSSAI and the UE (100) is establishing/established the PDU session of the emergency services, then the AMF server (800) sends a NAS message (e.g. Configuration update command) with a list of rejected S-NS SAIs and the network for each of the list with an appropriate rejection cause value. Further, the AMF server (800) keeps an emergency PDU session active and proceeds with the emergency services. The network does not deregister the UE (100). Further, the network deregisters the UE (100) when the PDU session for the emergency service is released. For example, the AMF deactivates all non-emergency PDU session(s) using a NAS signaling or implicitly. Further, the AMF server (800) indicates an implicit deactivation of all active PDU session in the NAS message to the UE (100). Further, the AMF server (800) sends the list of rejected NSSAI to the UE (100) during a de-registration procedure (e.g. De-registration request message).

[0126] When the network slice-specific authentication and authorization fails for all the S-NSSAIs in the allowed NSSAI, and the UE (100) does have the PDU session for the emergency services, then the AMF executes a network-initiated deregistration procedure and includes the list of rejected S-NSSAIs and each of the list with the appropriate rejection cause value to an explicit de-registration request message. In response to receiving the de-registration request message with the rejection cause related to scenarios such as 5GMM cause value to # 62 “No network slices available”, the UE (100) selects an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) cell and initiates an attach procedure to an EPS network when the UE (100) finds a suitable cell on the E-UTRAN cell. For example, the UE (100) redirects the UE (100) to the EPS network by including an appropriate cause (e.g. # 31 “Redirection to Evolved Packet Core (EPC) required”) in the deregistration request message when the UE (100) can access an EPS service in the EPS network. In another example, the UE (100) redirects the UE (100) to the EPS network by including an indicator requesting the UE (100) to select the E-UTRAN cell. Upon receiving the deregistration request with the rejection cause or the indicator, the UE (100) performs at least one of the action as described below:

[0127] 1) The UE (100) sets a Fifth Generation System (5GS) update status to a value “5U3 roaming not allowed” and stores the 5GS update status.

[0128] 2) The UE (100) deletes any 5G Globally Unique Temporary Identifier (5G-GUTI), last visited registered Tracking Area Identity (TAI), a TAI list and a key set identifier (ngKSI).

[0129] 3) The UE (100) resets a registration attempt counter and enters to a state “5GMM-deregistered”

[0130] 4) The UE (100) enables an E-UTRA capability if the E-UTRA capability was disabled.

[0131] 5) The UE (100) disables a N1 mode capability for a 3GPP access.

[0132] 6) If the UE (100) is operating in single-registration mode, the UE handles EPS Mobility Management (EMM) parameters, an EMM state, an EPS update status, a 4G Globally Unique Temporary Identifier (4G-GUTI), the TAI list, a key set identifier (eKSI) and an attach attempt counter as specified in 3GPP TS 24.301 for a case when an EPS attach procedure is rejected with the EMM cause with a value corresponding to the 5GMM cause value# 62 “No network slices available”.

[0133] FIG. 9 is a block diagram of the AMF server (800), according to an embodiment as disclosed herein. The AMF server (800) includes a processor (810), a memory (820), a communicator (830) and an emergency service based PDU session controller (840). The processor (810) is provided with the memory (820), the communicator (830) and the emergency service based PDU session controller (840). The general operations of the processor (810), the memory (820), and the communicator (830) are already explained in the FIG. 2.

[0134] The emergency service based PDU session controller (840) is configured to detect one of a UE (100) has a PDU session for an emergency service and the UE (100) is establishing a PDU session for the emergency service. Further, the emergency service based PDU session controller (840) is configured to detect a network slice authentication and authorization fails for all allowed Network Slice Selection Identifier (NSSAI). In response detect one of the UE (100) has the PDU session for the emergency service and the UE (100) is establishing the PDU session for the emergency service and detecting the network slice authentication and authorization fails for all allowed NSSAI, the emergency service based PDU session controller (840) does not deregister the UE (100), and send a configuration update command including a rejected NSSAI and a rejection cause value to the UE (100).

[0135] Further, the emergency service based PDU session controller (840) is configured to determine that the PDU session for the emergency service is completed. Further, the emergency service based PDU session controller (840) is configured to de-register with the UE (100) in response to determining that the PDU session for the emergency service is completed. Further, the emergency service based PDU session controller (840) is configured to send a deregistration request message with the rejection cause value to the UE (100).

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