WO2021230723A1

WO2021230723A1 - Method and apparatus for deploying mission critical services over edge network in wireless communication system

Info

Publication number: WO2021230723A1
Application number: PCT/KR2021/006110
Authority: WO
Inventors: Nishant Gupta; Basavaraj Jayawant Pattan; Naveen Kumar NAIDU; Sapan Pramodkumar SHAH; Arunprasath Ramamoorthy
Original assignee: Samsung Electronics Co., Ltd.
Priority date: 2020-05-14
Filing date: 2021-05-14
Publication date: 2021-11-18

Abstract

A method performed by a server of an edge network between a user equipment (UE) and a core network is provided. The method may comprise: receiving, from the UE, traffics associated with mission critical (MC) services; identifying the received traffics as one among a user plane traffic and a control plane traffic; transmitting, to an application domain of the edge network via user plane functions deployed in the edge network, a first traffic identified as the user plane traffic; and transmitting, to an application domain of a cloud network via control plane functions deployed in the cloud network, a second traffic identified as the control plane traffic.

Description

METHOD AND APPARATUS FOR DEPLOYING MISSION CRITICAL SERVICES OVER EDGE NETWORK IN WIRELESS COMMUNICATION SYSTEM

The disclosure relates to a method and system for deploying Mission Critical (MC) services over an edge network.

To meet the demand for wireless data traffic having increased since deployment of 4th generation (4G) communication systems, efforts have been made to develop an improved 5th generation (5G) or pre-5G communication system. The 5G or pre-5G communication system is also called a 'beyond 4G network' or a 'post long term evolution (LTE) system'. The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large scale antenna techniques are discussed with respect to 5G communication systems. In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like. In the 5G system, hybrid frequency shift keying (FSK) and Feher's quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of everything (IoE), which is a combination of the IoT technology and the big data processing technology through connection with a cloud server, has emerged. As technology elements, such as "sensing technology", "wired/wireless communication and network infrastructure", "service interface technology", and "security technology" have been demanded for IoT implementation, a sensor network, a machine-to-machine (M2M) communication, machine type communication (MTC), and so forth have been recently researched. Such an IoT environment may provide intelligent Internet technology services that create a new value to human life by collecting and analyzing data generated among connected things. IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing information technology (IT) and various industrial applications.

In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, MTC, and M2M communication may be implemented by beamforming, MIMO, and array antennas. Application of a cloud RAN as the above-described big data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.

As described above, various services can be provided according to the development of a wireless communication system, and thus a method for easily providing such services is required.

The present disclosure provides a method and system for deploying Mission Critical (MC) services over an edge network.

The disclosure is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

FIG. 1A illustrates an architecture for enabling edge applications, according to the prior art;

FIG. 1B illustrates an MC service application plane and signalling control plane architecture, according to the prior art;

FIG. 2A illustrates a block diagram of a server of an edge network for deploying MC services, according to an embodiment as disclosed herein;

FIG. 2B is a flow diagram illustrating a method for deploying the MC services over the edge network, according to an embodiment as disclosed herein;

FIG. 3A illustrates an architecture for MC deployments on an edge using local breakout in an EPC or a 5GS, according to the embodiments as disclosed herein;

FIG. 3B illustrates an architecture for MC deployments on the edge using a CUPS mechanism in the EPC or a Non-Standalone network (NSA) network, according to the embodiments as disclosed herein;

FIG. 4A illustrates a high-level architecture for deployment of only an MC media plane on the edge while an MC signalling plane remains in a cloud network, using the local breakout in the EPC or the 5GS according to the embodiments as disclosed herein;

FIG. 4B illustrates a high-level architecture for deployment of only MC media plane on the edge while the MC signalling plane remains in cloud using the CUPS mechanism in the EPC or the NSA network, according to the embodiments as disclosed herein;

FIG. 5A illustrates a detailed Evolved Packet System (EPS) architecture for deployment of only the MC media plane on the Edge while the MC signalling plane remains in the cloud network using the local breakout, according to the embodiments as disclosed herein;

FIG. 5B illustrates an EPS or NSA architecture for deployment of only the MC media plane on the edge while the MC signalling plane remains in the cloud network using the CUPS mechanism, according to the embodiments as disclosed herein;

FIG. 6 illustrates a detailed 5GS architecture for deployment of only the MC media plane on the edge while the MC signalling plane remains in the cloud network using the local breakout, according to the embodiments as disclosed herein;

FIG. 7A illustrates a high-level architecture for deployment of some MC Features on the edge while other MC features are served by the cloud network using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein;

FIG. 7B illustrates a high-level architecture for deployment of some MC Features on the edge while other MC features are served by the cloud network using the CUPS mechanism in the EPC or the NSA network, according to the embodiments as disclosed herein;

FIG. 8A illustrates a detailed EPS architecture for deployment of some MC Features on the edge while other MC features are served by the cloud network using the local breakout, according to the embodiments as disclosed herein;

FIG. 8B illustrates a detailed EPS or NSA architecture for deployment of some MC Features on the edge while other MC features are served by the cloud network using the CUPS mechanism, according to the embodiments as disclosed herein;

FIG. 9 illustrates a detailed 5GS architecture for deployment of some MC Features on the edge while other MC features are served by the cloud network using the local breakout, according to the embodiments as disclosed herein;

FIG. 10A illustrates a high-level architecture for deployment of all MC features on the edge using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein;

FIG. 10B illustrates a high-level architecture for deployment of all MC features on the edge using the CUPS mechanism in the EPC or the NSA network, according to the embodiments as disclosed herein;

FIG. 11A illustrates a detailed EPS architecture for deployment of all MC features on the edge using the local breakout, according to the embodiments as disclosed herein;

FIG. 11B illustrates a detailed EPS or NSA architecture for deployment of all MC features on the edge using the CUPS mechanism, according to the embodiments as disclosed herein; and

FIG. 12 illustrates a detailed 5GS architecture for deployment of all MC features on the edge using the local breakout, according to the embodiments as disclosed herein.

FIG. 13 is a diagram illustrating a UE 1300 according to an embodiment of the present disclosure;

FIG. 14 is a diagram illustrating a base station 1400 according to an embodiment of the present disclosure; and

FIG. 15 schematically illustrates a network entity 1500 according to embodiments of the present disclosure.

Throughout the disclosure, the expression "at least one of a, b or c" indicates only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof. Throughout the specification, a layer (or a layer apparatus) may also be referred to as an entity. Hereinafter, operation principles of the disclosure will be described in detail with reference to accompanying drawings. In the following descriptions, well-known functions or configurations are not described in detail because they would obscure the disclosure with unnecessary details. The terms used in the specification are defined in consideration of functions used in the disclosure, and can be changed according to the intent or commonly used methods of users or operators. Accordingly, definitions of the terms are understood based on the entire descriptions of the present specification.

For the same reasons, in the drawings, some elements may be exaggerated, omitted, or roughly illustrated. Also, a size of each element does not exactly correspond to an actual size of each element. In each drawing, elements that are the same or are in correspondence are rendered the same reference numeral.

Advantages and features of the disclosure and methods of accomplishing the same may be understood more readily by reference to the following detailed descriptions of embodiments and accompanying drawings of the disclosure. The disclosure may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments of the disclosure are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the disclosure to one of ordinary skill in the art. Therefore, the scope of the disclosure is defined by the appended claims. Throughout the specification, like reference numerals refer to like elements. It will be understood that blocks in flowcharts or combinations of the flowcharts may be performed by computer program instructions. Because these computer program instructions may be loaded into a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing apparatus, the instructions, which are performed by a processor of a computer or another programmable data processing apparatus, create units for performing functions described in the flowchart block(s).

The computer program instructions may be stored in a computer-usable or computer-readable memory capable of directing a computer or another programmable data processing apparatus to implement a function in a particular manner, and thus the instructions stored in the computer-usable or computer-readable memory may also be capable of producing manufactured items containing instruction units for performing the functions described in the flowchart block(s). The computer program instructions may also be loaded into a computer or another programmable data processing apparatus, and thus, instructions for operating the computer or the other programmable data processing apparatus by generating a computer-executed process when a series of operations are performed in the computer or the other programmable data processing apparatus may provide operations for performing the functions described in the flowchart block(s).

In addition, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing specified logical function(s). It is also noted that, in some alternative implementations, functions mentioned in blocks may occur out of order. For example, two consecutive blocks may also be executed simultaneously or in reverse order depending on functions corresponding thereto.

As used herein, the term "unit" denotes a software element or a hardware element such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and performs a certain function. However, the term "unit" is not limited to software or hardware. The "unit" may be formed so as to be in an addressable storage medium, or may be formed so as to operate one or more processors. Thus, for example, the term "unit" may include elements (e.g., software elements, object-oriented software elements, class elements, and task elements), processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, micro-codes, circuits, data, a database, data structures, tables, arrays, or variables.

Functions provided by the elements and "units" may be combined into the smaller number of elements and "units", or may be divided into additional elements and "units". Furthermore, the elements and "units" may be embodied to reproduce one or more central processing units (CPUs) in a device or security multimedia card. Also, in an embodiment of the disclosure, the "unit" may include at least one processor. In the following descriptions of the disclosure, well-known functions or configurations are not described in detail because they would obscure the disclosure with unnecessary details.

Hereinafter, for convenience of explanation, the disclosure uses terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standards. However, the disclosure is not limited to the terms and names, and may also be applied to systems following other standards.

In the disclosure, an evolved node B (eNB) may be interchangeably used with a next-generation node B (gNB) for convenience of explanation. That is, a base station (BS) described by an eNB may represent a gNB. In the following descriptions, the term "base station" refers to an entity for allocating resources to a user equipment (UE) and may be used interchangeably with at least one of a gNode B, an eNode B, a node B, a base station (BS), a radio access unit, a base station controller (BSC), or a node over a network. The term "terminal" may be used interchangeably with a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. However, the disclosure is not limited to the aforementioned examples. In particular, the disclosure is applicable to 3GPP new radio (NR) (or 5th generation (5G)) mobile communication standards. In the following description, the term eNB may be interchangeably used with the term gNB for convenience of explanation. That is, a base station explained as an eNB may also indicate a gNB. The term UE may also indicate a mobile phone, NB-IoT devices, sensors, and other wireless communication devices.

3rd Generation Partnership Project (3GPP) TS 23.558 provides an application layer architecture and related procedures for enabling edge applications over 3GPP networks, as illustrates in FIG. 1A. Though 3GPP MC (mission critical) services are custom designed for public safety agencies, this does not prevent MC service providers from deploying the MC services in commercial networks for many other applicable industries and verticals. While some deployments could be smaller in scale and have a limited number of users but they may still require the same level of Key Performance Indicators (KPIs) defined by 3GPP for public safety usage. In such scenarios the Public Land Mobile Network (PLMN) and the MC service providers can host MC services closer to campus (i.e. on an edge network e.g., 3GPP edge) or in custom in-house data networks closer to a User Equipment (UE(s)). This reduces backhaul traffic over the commercial networks and at the same time provides lower latency, fulfilling the required KPIs.

Thus, it is desired to at least provide a useful alternative for deploying vertical services (e.g. MC services) closer to the UE(s) at the edge network, either completely or partially, by recommending different deployment architectures for the MC services to mitigate the backhaul traffic over the commercial networks and at the same time providing the lower latency, fulfilling the required KPIs.

The principal object of the embodiments herein is to provide a method and system for deploying MC services over an edge network by configuring user plane functions at the server of the edge network to redirect the received MC media plane traffic to an application domain of the edge network without passing through a core network to reduce latency between the UE and the application domain. Redirecting the received MC signalling plane traffic to an application domain of a cloud network.

Another object of the embodiment herein is to determine a requirement for individual features of MC functionality associated with the edge network and the core network, and split the MC functionality between entities over the core network and entities over the edge network based on the determined requirements. Redirecting the MC media plane traffic and the MC signalling plane traffic according to a split of the MC functionality.

Another object of the embodiment herein is to configure all MC functionality at the edge network to reduce latency and to improvise localization of services associated with the UE. Redirecting all the MC media plane traffic and the MC signalling plane traffic to the application domain of the edge network.

Another object of the embodiment herein is to deploy 3GPP MC services over 3GPP Edge and deliver MC services closer to the UE(s) at the edge network, for example, 3GPP Edge. The deployed MC services are either in a distributed or scalable manner, which implicitly increases the Quality of Service (QoS) of MC services and reduces overall latency.

Another object of the embodiment herein is to provide multiple alternates for deployment of the vertical applications (e.g. MC services, as illustrated) on the edge network wherein a media plane (i.e. MC media plane traffic) of the vertical application is moved to the edge network while a signalling plane (i.e. MC signalling plane traffic ) remains under the control of a cloud server; or wherein features of the vertical application including related signalling and media plane are split into two groups such that one set of the features are deployed on the edge network while the other set of the features remain under the control of the cloud server; or wherein all features of the vertical application including related signalling and media plane are deployed on the edge network to achieve a lower latency, reduced backhaul traffic and higher bandwidth.

Accordingly, the embodiment herein is to provide a method for deploying MC services over an edge network. The method includes receiving, by a server of the edge network, one of a MC media plane traffic and a MC signalling plane traffic from a UE. Further, the method includes deploying, by the server of the edge network, the MC services over the edge network by performing one of: configuring user plane functions at the server of the edge network to redirect the received MC media plane traffic to an application domain (i.e. application domain server) of the edge network without passing through a core network to reduce latency between the UE and the application domain and redirecting the received MC signalling plane traffic to an application domain of a cloud network; determining a requirement for individual features of MC functionality associated with the edge network and the core network and splitting the MC functionality between entities over the core network and entities over the edge network based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network to reduce latency and to improvise localization of services associated with the UE and redirecting all the MC media plane traffic and the MC signalling plane traffic to the application domain of the edge network.

In an embodiment, where the server of the edge network comprises the user plane functions, and where the application domain comprises of application plane functions and signalling control plane functions.

In an embodiment, where the user plane functions comprises a Serving Gateway (S-GW) and PDN Gateway (P-GW) for an Evolved Packet Core (EPC), GW-U and GW-C functions for an Control and User Plane Separation (CUPS) enabled EPC and User Plane Functions (UPFs) for 5G System (5GS).

In an embodiment, where the application plane function comprises Common Services Core, MC Service Server, MC user database and MC Gateway, and wherein the signalling control plane functions comprise IP Multimedia Subsystem (IPS), Session Initiation Protocol (SIP) core and Hypertext Transfer Protocol (HTTP) proxies.

In an embodiment, where the user plane functions of the edge network segregate and redirects the MC media plane traffic to the application plane functions of the application domain of the edge network and the MC signalling plane traffic to the signalling control plane functions of the application domain of the cloud network.

In an embodiment, where the MC functionality is split between the application domain entities deployed over the core network and application domain entities deployed over the edge network as per criticality requirements of individual features.

In an embodiment, where the application plane functions of the application domain of the edge network synchronize with the application plane functions of the application domain of the cloud network using a synchronization channel.

In an embodiment, where the user plane function deployed within the edge network is configured to split the MC signalling plane traffic and the MC media plane traffic between the edge network and the cloud network based on Fully Qualified Domain Names (FQDNs) or destination address.

In an embodiment, where all MC functionality associated with the MC media plane traffic and the MC signalling plane traffic is redirected towards the edge network instead of the core network.

Accordingly, the embodiment herein is to provide a system/ architecture for deploying the MC services on the edge network in a wireless network. The system includes the UE connected to an access node and configured to communicate with the access node through one of the MC media plane traffic and the MC signalling plane traffic. Further, the system includes the access node connected to one of the UE, a server of an edge network, a CUPS of the edge network and a server of a core network, and configured to communicate with the one of the UE, the server of the edge network, the CUPS of the edge network and the server of the core network through the one of the MC media plane traffic and the MC signalling plane traffic. Further, the system includes the server of the edge network connected to one of a server of the application domain (i.e. application domain server), the access node, the CUPS of the edge network and the server of the core network, and configured to communicate with the one of the server of the application domain, the access node, the CUPS of the edge network and the server of the core network through one of a synchronization channel, the MC media plane traffic , and the mission-critical signalling plane traffic channel. Further, the system includes the server of the core network connected to one of the server of the application domain, the server of the edge network, the CUPS of the edge network and the access node, and configured to communicate with one of the server of the application domain, the server of the edge network, the CUPS of the edge network and the access node through the MC signalling plane traffic. Further, the system includes the server of the application domain connected to one of the server of the core network and the server of the edge network through the one of the synchronization channel, the MC media plane traffic, and the MC signalling plane traffic.

Accordingly, the embodiments herein provide the server for deploying the MC services over the edge network. The server includes an MC services controller coupled with a processor and a memory. The MC services controller is configured to receive the MC media plane traffic and the MC signalling plane traffic from the UE. Further, the MC services controller is configured to deploy the MC services over the edge network by performing one of: configuring user plane functions at the server of the edge network to redirect the received MC media plane traffic to the application domain server of the cloud network without passing through the core network to reduce latency between the UE and the application domain server of the cloud network and redirecting the received MC signalling plane traffic to the application domain server of the cloud network; determining the requirement for individual features of MC functionality associated with the edge network and the core network and splitting the MC functionality between entities over the core network and entities over the edge network based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network to reduce latency and to improvise localization of services associated with the UE and redirecting all the MC media plane traffic and the MC signalling plane traffic to the server of the edge network.

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

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.

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.

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

The term MC Service Servers or MC Application Server being used in this document refers to MCPTT Server, MC Video Server and MC Data Server defined by 3GPP TS 23.379, 3GPP TS 23.281 and 3GPP TS 23.282 respectively. The term CSC (common services core) servers being used on this document refers to the Group Management Server (GMS), Configuration Management Server (CMS), Identity Management Server (IdMS), and Key Management Server (KMS) defined by 3GPP TS 23.280.

FIG. 1A illustrates an architecture (1000) for enabling edge applications, according to the prior art, as described in 3GPP TS 23.558.

FIG. 1B illustrates the MC Service application plane and signalling control plane architecture, according to the prior art, as described in 3GPP TS 23.280.

In an embodiment, MC services are taken as an example in the proposed method/system/architecture for illustration purposes. Similar principles can be applied to other vertical applications and their deployment in the edge networks.

Accordingly, embodiments herein achieve a method for deploying MC services over an edge network. The method includes receiving, by a server of the edge network, one of a MC media plane traffic and a MC signalling plane traffic from a UE. Further, the method includes deploying, by the server of the edge network, the MC services over the edge network by performing one of: configuring user plane functions at the server of the edge network to redirect the received MC media plane traffic to an application domain of the edge network without passing through a core network to reduce latency between the UE and the application domain and redirecting the received MC signalling plane traffic to an application domain of a cloud network; determining a requirement for individual features of MC functionality associated with the edge network and the core network and splitting the MC functionality between entities over the core network and entities over the edge network based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network to reduce latency and to improvise localization of services associated with the UE and redirecting all the MC media plane traffic and the MC signalling plane traffic to the application domain of the edge network.

Accordingly, the embodiment herein is to provide a system/ architecture for deploying the MC services on the edge network in a wireless network. The system includes the UE connected to an access node and configured to communicate with the access node through one of the MC media plane traffic and the MC signalling plane traffic. Further, the system includes the access node connected to one of the UE, a server of an edge network, a CUPS of the edge network and a server of a core network, and configured to communicate with the one of the UE, the server of the edge network, the CUPS of the edge network and the server of the core network through the one of the MC media plane traffic and the MC signalling plane traffic. Further, the system includes the server of the edge network connected to one of a server of the application domain, the access node, the CUPS of the edge network and the server of the core network, and configured to communicate with the one of the server of the application domain, the access node, the CUPS of the edge network and the server of the core network through one of a synchronization channel, the MC media plane traffic, and the mission-critical signalling plane traffic channel. Further, the system includes the server of the core network connected to one of the server of the application domain, the server of the edge network, the CUPS of the edge network and the access node, and configured to communicate with one of the server of the application domain, the server of the edge network, the CUPS of the edge network and the access node through the MC signalling plane traffic. Further, the system includes the server of the application domain connected to one of the server of the core network and the server of the edge network through one of the synchronization channel, the MC media plane traffic, and the MC signalling plane traffic.

Unlike existing methods and systems, the proposed method allows the server of the edge network to deploy the MC services over the edge network by configuring user plane functions at the server of the edge network to redirect the received MC media plane traffic to the application domain of the edge network without passing through the core network to reduce latency between the UE and the application domain. Redirecting the received MC signalling plane traffic to the application domain of the cloud network.

Unlike existing methods and systems, the proposed method allows the server of the edge network to determine a requirement for individual features of MC functionality associated with the edge network and the core network and splitting the MC functionality between entities over the core network and entities over the edge network based on the determined requirements. Redirecting the MC media plane traffic and the MC signalling plane traffic according to the split of the MC functionality.

Unlike existing methods and systems, the proposed method allows the server of the edge network to configure all MC functionality at the edge network to reduce latency and to improvise localization of services associated with the UE. Redirecting all the MC media plane traffic and the MC signalling plane traffic to the application domain of the edge network.

Unlike existing methods and systems, the proposed method allows the server of the edge network to deploy 3GPP MC services over 3GPP Edge and deliver MC services closer to the UE(s) at the edge network, for example, 3GPP Edge. The deployed MC services are either in a distributed and scalable manner, which implicitly increases the QoS of MC services and reduces overall latency.

Unlike existing methods and systems, the proposed method and system provides multiple alternates for deployment of the vertical applications (e.g. MC services, as illustrated) on the edge network wherein a media plane (i.e. MC media plane traffic ) of the vertical application is moved to the edge network while a signalling plane (i.e. MC signalling plane traffic ) remains under the control of a cloud server; or wherein features of the vertical application including related signalling and media plane are split into two groups such that one set of the features are deployed on the edge network while the other set of the features remain under the control of the cloud server; or wherein all features of the vertical application including related signalling and media plane are deployed on the edge network to achieve a lower latency, reduced backhaul traffic and higher bandwidth.

In an embodiment, multiple deployment choices are possible based on the requirements of the deployment, such as load capacity, latency requirements, localization needs etc. The proposed method provides multiple architectures and options for such deployment choices. For example, the MC services can be deployed with EPS or 5GS, and the invention covers both such options. Following models, for both EPS and 5GS are conceived by this invention:

Redirecting the MC user plane traffic (also called media plane) via the Edge data network e.g., 3GPP Edge while the MC control plane (also called signalling plane) traffic is handled at the central MC entities (deployed e.g. in the cloud network or 3rd party data centers such as AWS or Azure data centers or 3GPP core network).

Splitting the MC functionality between the central entity and the entities deployed over the edge as per the criticality requirements of the individual features.

Moving all of the MC functionality over to the edge.

In an embodiment, for model 1 and model 2 as mentioned above, detailed description and illustration given in FIG.3A to FIG.15,to redirect the user plane traffic (which includes control/signalling plane and user/media plane traffic of MC services) to the edge, it is suggested to deploy the user plane functions within the edge Network i.e. as distributed functions close to the end consumers, redirecting the user plane traffic either to the entities on the edge, or breaking it out to the central entities, skipping the core network. Edge Network here represents the entities between the UE and the 3GPP core network. For EPS and Non Standalone Architecture (NSA), it is suggested to utilize the CUPS (control and user plane separation) architecture, as provided in 3GPP TS 23.214 (Architecture enhancements for control and user plane separation of EPC nodes); while in 5GS, this separation of user plane functions and control plane is inherent. These core network functions are deployed close to the UE, e.g. along with the access network, or it can be virtualized between the access network and the edge.

In an embodiment, for model 3, along with the user plane functions, certain control plane functions of the core network (such as MME and HSS in EPS, and AMF and SMF in 5GS) will also have to be moved to the Edge Network, to make the functionality completely independent of the core network. In a certain deployment, these core network functions when moved or deployed on the Edge Network may even share the platform or the edge hosting environment i.e. the physical compute and storage infrastructure on which edge network specific functions are deployed, e.g. as virtual network functions. In an alternate deployment, which can even be deployed as edge application servers as defined by 3GPP TS 23.558.

Referring now to the drawings and more particularly to FIGS. 2A through 15, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

FIG. 2A illustrates a block diagram of a server (301) of an edge network (300) (not shown in the FIG.) for deploying MC services, according to an embodiment as disclosed herein. The server (301) may communicate, directly or indirectly, with an endpoints/UEs (100), an access network (200) (e.g. eNodeB, NR), a CUPS (302), a core network (400), an application domain/cloud network (500).

In an embodiment, the server (301) may include a memory (301a), a processor (301b), a communicator (301c), and a MC services controller (301d).

In an embodiment, the memory (301a) is configured to store configured user plane function, application plane functions and signalling control plane functions. The memory (301a) may store instructions to be executed by the processor (301b). The memory (301a) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (301a) 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 (301a) is non-movable. In some examples, the memory (301a) can be configured to store larger amounts of information than the memory. 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). The memory (301a) can be an internal storage unit or it can be an external storage unit of the server (301), a cloud storage, or any other type of external storage.

The processor (301b) may communicate with the memory (301a), the communicator (301c), and the MC services controller (301d). The processor (301b) is configured to execute instructions stored in the memory (301a) and to perform various processes. The processor (301b) may include one or a plurality of processors, may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an Artificial intelligence (AI) dedicated processor such as a neural processing unit (NPU).

The communicator (301c) is configured for communicating internally between internal hardware components and with external devices (e.g. eNodeB, gNodeB, core network, cloud network) via one or more networks (e.g. Radio technology, internet, etc.). The communicator (301c) may include an electronic circuit specific to a standard that enables wired or wireless communication.

The MC services controller (301d) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

In an embodiment, the MC services controller (301d) is configured to receive a MC media plane traffic and a MC signalling plane traffic from the UE (100). Further, the MC services controller (301d) is configured to deploy the MC services by performing one of: configuring user plane functions at the server (301) of the edge network (300) to redirect the received MC media plane traffic to an application domain server (501) of the cloud network (500) without passing through the core network (400) to reduce latency between the at least one UE (100) and the application domain server (501) of the cloud network (500) and redirecting the received MC signalling plane traffic to the application domain server (501) of the cloud network (500); determining a requirement for individual features of MC functionality associated with the edge network (300) and the core network (400) and splitting the MC functionality between entities over the core network (400) and entities over the edge network (300) based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network (300) to reduce latency and to improvise localization of services associated with the at least one UE (100) and redirecting all the MC media plane traffic and the MC signalling plane traffic to the server (301) of the edge network (300).

In an embodiment, the server (301) of the edge network (300) comprise the user plane functions, and wherein the application domain server (501) and the server (301) comprises one of the application plane functions and the signalling control plane functions. The user plane functions comprise an S-GW and P-GW for an EPC, GW-U and GW-C functions for the CUPS (302) enabled EPC and UPFs for 5GS. The application plane function comprises Common Services Core, MC Service Server, MC user database and MC Gateway, and wherein the signalling control plane functions comprises IPS, SIP core and HTTP proxies.

In an embodiment, the user plane functions of the edge network (300) segregates and redirects the MC media plane traffic to the application plane functions of the server (301) of the edge network (300) and the MC signalling plane traffic to the signalling control plane functions of the application domain server (501) of the cloud network (500).

In an embodiment, the MC functionality is split between the application domain entities deployed over the core network (400) and application domain entities deployed over the edge network (300) as per criticality requirements of individual features.

In an embodiment, the application plane functions of the server (301) of the edge network (300) synchronize with the application plane functions of the application domain server (501) of the cloud network (500) using a synchronization channel.

In an embodiment, the user plane function deployed within the edge network (300) is configured to split the MC signalling plane traffic and the MC media plane traffic between the edge network (300) and the cloud network (500) based on FQDNs or destination address.

In an embodiment, all MC functionality associated with the MC media plane traffic and the MC signalling plane traffic is redirected towards the edge network (300) instead of the core network (400).

Although the FIG. 2A shows various hardware components of the server (301) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the server (301) 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 to deploy MC services over the edge network (300).

FIG. 2B is a flow diagram (S200) illustrating a method for deploying MC services over the edge network (300), according to an embodiment as disclosed herein. The operations (S202-S220) are performed by the server (301).

At S202, the method includes receiving the MC media plane traffic and the MC signalling plane traffic from the UE (100).

At S204, the method includes deploying the MC services over the edge network (300).

At S206, the method includes configuring user plane functions at the server (301) of the edge network (300) to redirect the received MC media plane traffic to an application domain server (501) of the cloud network (500).

At S208, the method includes redirecting the received MC media plane traffic to the application domain server (501) of the cloud network (500) without passing through the core network (400) to reduce latency between the UE (100) and the application domain server (501) of the cloud network (500).

At S210, the method includes redirecting the received MC signalling plane traffic to the application domain server (501) of the cloud network (500).

At S212, the method includes determining a requirement for individual features of MC functionality associated with the edge network (300) and the core network (400).

At S214, the method includes splitting the MC functionality between entities over the core network (400) and entities over the edge network (300) based on the determined requirements.

At S216, the method includes redirecting the MC media plane traffic and the MC signalling plane traffic according to the split of the MC functionality.

At S218, the method includes configuring all MC functionality at the edge network (300) to reduce latency and to improvise localization of services associated with the at least one UE (100).

At S220, the method includes redirecting all the MC media plane traffic and the MC signalling plane traffic to the server (301) of the edge network (300).

The various actions, acts, blocks, steps, or the like in the flow diagram (S200) 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.

FIG. 3A illustrates an architecture of the system (2000) for MC deployments on the edge (i.e. edge network (300)) using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein.

The architecture classifies the deployments into 5 sections: where endpoints (100) includes end terminals or UEs (100). Access network (200) includes Radio Access Technology (RAT), eNodeB for the EPS and New Radio (NR) for the 5GS (i.e. eNodeB/NR (201)).

Edge network (300) includes functional entities deployed distributed, close to the end terminals or UEs (100). The application servers are deployed on the edge platform as Edge Application Servers (EAS) (301). The FIG. 3A shows edge-specific Mission Critical service Application Servers (eMCX AS) along with the EAS (301) for IoT and Analytics. The EASs (301) for IoT and Analytics can be employed to provide additional services to the MC service provides as needed, e.g. MC group creation at the edge network (300) based on analytics information or connections to edge network (300), IoT surveillance cameras triggered incident handling at the edge network (300).

Although only one edge network (300) is shown in the FIG. 3A for illustration purposes, in real deployments there can be multiple edge data networks deployed with different service coverage areas and the inter-edge data networks communication can be used when there is a need for MC service coverage extends beyond the coverage area of one Edge data network. The edge network (300) also constitutes the user plane functions which, in the case of the EPC are the S-GW and P-GW and in case of the 5GS are the UPFs.

Core network (400) includes the 3GPP core network like EPC or 5G Core (5GC), containing the core control/signalling plane functionalities like IPS (or the SIP core) and HTTP proxies. Cloud application domain (500) (i.e. application domain/cloud network (500)), where the central application servers are deployed. For application domain (500), there is no restriction on its deployment to cater for the practical needs of the service e.g. it can be deployed in the cloud network (500), along with the core network (400) or in dedicated infrastructure deployed by the application service provider. The access network (200) combined with the edge network (300) and functions in between such as User Plane Functions, constitute the edge network (300) necessary for the edge deployments.

FIG. 3B illustrates an architecture of the system (2000) for MC deployments on the edge using the CUPS (302) mechanism in the EPC or a Non-Standalone network (NSA) network, according to the embodiments as disclosed herein. Referring to the FIG. 3B, the proposed deployment strategy is an extension of the deployment architecture shown in the FIG. 3A with the EPC or the NSA network deployed with the CUPS (302) architecture/ mechanism.

The representation borrows the following concepts from deployment in the FIG. 3A such as the endpoints (100), the access network (200), the core network (400) and the cloud application domain/ cloud network (500).

The deployments differ in terms of the edge network (300), in addition to the application servers are deployed on the edge platform as the EAS (301), the edge network (300) also constitutes of the user plane functions which, in this case of CUPS (302) deployments constitutes of GW-U and GW-C functions. The GW-U function in this disclosure represents the PGW-U and SGW-U functions or a combination of both, while the GW-C function represents PGW-C and S-GW-C or a combination of both the functions of the CUPS (302) architecture defined by 3GPP TS 23.214.

FIG. 4A illustrates a high-level architecture of the system (2000) for deployment of only an MC media plane on the edge while an MC signalling plane remains in the cloud network (500) using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein.

Referring to the FIG. 4A, which is an extension of the architecture described in the FIG. 3A proposes the basic Architecture depicting segregation of the user/media plane traffic and control/signalling plane traffic of MC services. With that segregation, the control plane functions like call control are still handled by the IMS/SIP core and HTTP proxy functions in the core network (400) while the user/media plane traffic breaks out to the application domain (500) via the user plane functions deployed in the edge network (300). The solid lines in the FIG. 4A depicts the control/signalling plane traffic (i.e. MC signalling) while the dashed line depicts the user/media plane traffic (i.e. MC media).

FIG. 4B illustrates a high-level architecture of the system (2000) for deployment of only MC media plane on the edge while the MC signalling plane remains in the cloud network (500) using the CUPS (302) mechanism in the EPC or the NSA network, according to the embodiments as disclosed herein. Referring to the FIG. 4B, which is an extension of the architecture described in the FIG. 3B proposes a basic architecture for the EPC/ NSA network deployed in compliance with the CUPS (302) architecture.

FIG. 5A illustrates a detailed EPS architecture of the system (2000) for deployment of only the MC media plane on the edge while the MC signalling plane remains in the cloud network (500) using the local breakout, according to the embodiments as disclosed herein.

The architecture including the interfaces, for a segregated control/signalling plane and user/media plane deployment in the EPS. In this deployment, the edge network (300) hosts the P-GW and S-GW functions within the edge network (300) such that one instance of a SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while a S11 interface connects to the core network (400) (e.g. 3GPP core network). Further, the P-GW functions deployed within the edge network (300) are configured to segregate the signalling plane and media plane traffic of the MC application and deliver the signalling plane data to the application server (501) in the cloud network (500) while the deliver the media plane to the edge application server (301) (i.e. EAS) in the edge network (300).

FIG. 5B illustrates an EPS or NSA architecture of the system (2000) for deployment of only the MC media plane on the edge while the MC signalling plane remains in the cloud network (500) using the CUPS (302) mechanism, according to the embodiments as disclosed herein.

Referring to the FIG. 5B, which is a detailed architectural representation provides an alternate architecture represented in FIG.5A, with the use of the CUPS (302) architecture for the segregated control/signalling plane and user/media plane deployment in the EPC or NSA network. In this deployment, the edge network (300) hosts the GW-U and GW-C functions within the edge network (300) such that one instance of the SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while the S11 interface connects to the core network (400). Further, the GW-U functions deployed within the edge network (300) are configured to segregate the signalling plane and media plane traffic of the MC application and deliver the signalling plane data to the application server (501) in the cloud network (500) while the deliver the media plane to the EAS (301) in the edge network (300).

FIG. 6 illustrates a detailed 5GS architecture of the system (2000) for deployment of only the MC media plane on the edge while the MC signalling plane remains in the cloud network (500) using the local breakout, according to the embodiments as disclosed herein.

Referring to the FIG. 6, which is a detailed architectural representation that provides the interfaces, for the segregated control/signalling plane user/media plane deployment in the 5GS. In this deployment, the user plane functions deployed within the edge network (300) are configured to segregate the signalling plane and media plane traffic of the MC application and deliver the signalling plane data to the application server (501) in the cloud network (500) while the deliver the media plane to the EAS (301) in the edge network (300).

FIG. 7A illustrates a high-level architecture of the system (2000) for deployment of some MC Features on the edge while other MC features are served by the cloud network (500) using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein.

Referring to the FIG. 7A which is a high-level architectural representation is an extension of the architecture represented in FIG 3A. It provides an architecture depicting a deployment where the features of MC services, including both signalling plane and the media plane, are strategically split between the central entities and the entities on the edge network (300). This split will allow deploying the resource-intensive features requiring lower latency on the edge network (300) while keeping other functions available via the central application servers (i.e. cloud network (500)/ server (501) of the application domain/cloud network (500)).

To allow for such deployments, a flavor of the MC services application server with selective features is deployed at the edge network (300) as an Edge Application Server (eMCX AS) (301). Along with the eMCX AS (301), the underlying application layer functions to support the control/signalling plane of the application are also replicated at the edge - specifically the IMS or the SIP core (say, eIMS or eSIP Core where 'e' stands for Edge) and the HTTP proxy (say eHTTP proxy where 'e' stands for Edge). With that the UE/ endpoints (100) (or the application clients on the UE), will require enough intelligence, for example in form of configurations, to direct the requests for specific features to either edge or central entity based on where they are deployed. In an alternate embodiment, the network functions responsible for the handling of user plane are enhanced to do this separation of application data traffic, such that the application data traffic intended to be handled by the eMCX AS (301) is directed to the edge network (300), while other traffic is directed to the cloud network (500). The method like segregation based on the FQDNs/destination addresses can be done to redirect the received traffic to the right destination server on the cloud network (500) of the edge network. The solid lines in the FIG. 7A depict the control/signalling plane traffic while the dashed line depicts the user/media plane traffic.

With such a deployment, there may be a need for a new interface between the application servers (501) in the central entity (i.e. cloud network (500)) and the application servers (301) in the edge network (300) for synchronization purposes. The new interface (i.e. MC AS sync) is depicted in the FIG. 7A with a dotted line and will be dependent on the application and its requirements of synchronizations.

FIG. 7B illustrates a high-level architecture of the system (2000) for deployment of some MC Features on the edge while other MC features are served by the cloud network (500) using the CUPS (302) mechanism in the EPC or the NSA network according to the embodiments as disclosed herein. Referring to the FIG. 7B, the proposed architecture is an extension of FIG. 3B proposing a basic architecture for the EPC/ NSA deployed in compliance with the CUPS (302) architecture.

FIG. 8A illustrates a detailed EPS architecture of the system (2000) for deployment of some MC Features on the edge while other MC features are served by the cloud network (500) using the local breakout, according to the embodiments as disclosed herein.

Referring to the FIG. 8A which is a detailed architectural representation that provides the architecture including the interfaces, for partial deployment MCX features on the edge network (300) i.e. application features are split between the central application servers (501) and the edge application servers (301) deployed over the EPS network. In this deployment, the edge network (300) hosts the P-GW and S-GW functions within the edge network (300) such that one instance of the SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while the S11 interface connects to the core network (400). Along with the network functions, a flavor of application layer support functions such as IMS/SIP and HTTP are reduced and deployed on the edge network (300) to handle the signalling requests of the application intended to be processed at the edge network (300). Further, the P-GW functions deployed within the edge network (300) can be configured to segregate the application data traffic based on the FQDNs or destination address in incoming traffic. This allows delivery of the application data to Edge based on the split of application features and their deployment on the Edge.

FIG. 8B illustrates a detailed EPS or NSA architecture of the system (2000) for deployment of some MC Features on the edge while other MC features are served by the cloud network (500) using the CUPS (302) mechanism, according to the embodiments as disclosed herein.

Referring to the FIG. 8B, which is a detailed architectural representation provides an alternate architecture represented of FIG.8A with the use of the CUPS (302) architecture for a segregated control/signalling plane and user/media plane deployment in the EPC or NSA network. In this deployment, the edge network (300) hosts the GW-U and GW-C functions within the edge network (300) such that one instance of the SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while the S11 interface connects to the core network (400). Along with the network functions, a flavor of application layer support functions such as the IMS/SIP and HTTP are reduced and deployed on the Edge to handle the signalling requests of the application intended to be processed at the Edge. Further, the GW-U functions deployed within the edge network (300) can be configured to segregate the application data traffic based on the FQDNs or destination address in the incoming traffic. This allows delivery of the application data to Edge based on the split of application features and their deployment on the Edge.

FIG. 9 illustrates a detailed 5GS architecture of the system (2000) for deployment of some MC Features on the edge while other MC features are served by the cloud network (500) using the local breakout, according to the embodiments as disclosed herein.

Referring to the FIG. 9 which is a detailed architectural representation provides the interfaces, for partial deployment on the edge network (300) i.e. features split between the central application servers (501) and the edge application servers (301) over the 5GS. In this deployment, the user plane functions deployed within the edge network (300) are configured to segregate the application data traffic of the MC application based on the features deployed on the Edge and deliver the signalling plane and media plane data to the application server in the Edge. The segregation can be done based on the FQDNs or destination addresses in the application data traffic. Along with the eMCX AS (301), the underlying application layer functions to support the control/signalling plane of the application are also replicated at the edge - specifically the IMS or the SIP core (say, eIMS or eSIP Core where 'e' stands for Edge) and the HTTP proxy (say eHTTP proxy where 'e' stands for Edge). With that the UE/ endpoints (100) (or the application clients on the UE), will require enough intelligence, for example in form of configurations, to direct the requests for specific features to either edge or central entity based on where they are deployed.

In this model, for e.g., the MC Service providers and PLMN can deploy the MC service servers at the edge network (300) to serve a limited number of MC service users of an organization or industry and the CSC servers deployed at the cloud behind the core network (400) can be a centralized deployment which can serve multiple organizations. A limited number here could be deployment specific based on the hardware/software capabilities. The motive behind this architecture is that the data traffic generated by the MC UE/endpoints (100) to MC Service servers (501 and/or 301) and vice-versa will be more intense when compared to the traffic generated towards CSC functions. By this diversification data traffic at the backhaul will be reduced and QoS can be improved.

FIG. 10A illustrates a high-level architecture of the system (2000) for deployment of all MC features on the edge using the local breakout in the EPC or the 5GS, according to the embodiments as disclosed herein.

Referring to the FIG. 10A which is a high-level architectural representation is an extension of the architecture represented in FIG 3A. It provides an architecture depicting a deployment where all features of MC services, including signalling and media plane, are brought down and deployed at the edge network (300) as an Edge Application Server (eMCX AS) (301). This allows minimum latency and true localization of the services. To allow for such deployments, the MC services application server (eMCX AS) (301), with all its features will have to be deployed at the edge network (300). Along with the application server, the underlying functions to support the control/signalling plane of the application will also have to be replicated at the edge - specifically the IMS or the SIP core (say, eIMS or eSIP Core where 'e' stands for Edge) and the HTTP proxy (say, eHTTP proxy where 'e' stands for Edge). With that, even the access and mobility-related functions of the core network (400) will have to be deployed in a distributed manner within the edge network (300). The solid lines in the FIG. 10A depict the control/signalling plane traffic while the dashed line depicts the user/media plane traffic. Further, the network functions responsible for the handling of user plane are enhanced to do recognize and redirect all the application data traffic of the vertical application to the eMCX AS (301) deployed at the Edge.

Such deployment can work in complete isolation without support from the core network (400) or any central application layer entities; but will have localized coverage, limited to the coverage of the edge network (300). This challenge can be subdued with new interfaces allowing interaction amongst the Edge Networks/ edge network (300) and enforcing coordination between the individual servers deployed in different Edge Networks.

FIG. 10B illustrates a high-level architecture of the system (2000) for deployment of all MC features on the edge using the CUPS (302) mechanism in the EPC or the NSA network, according to the embodiments as disclosed herein. Referring to the FIG. 10B, the proposed architecture is an extension of FIG. 3B, proposes a basic architecture for the EPC/ NSA deployed in compliance with the CUPS (302) architecture.

FIG. 11A illustrates a detailed EPS architecture of the system (2000) for deployment of all MC features on the edge using the local breakout, according to the embodiments as disclosed herein.

Referring to the FIG. 11A which is a detailed architectural representation provides the architecture including the interfaces, for complete deployment of MC services on the edge in the EPS. In this deployment, the edge network (300) hosts the P-GW and S-GW functions within the edge network (300) such that one instance of the SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while the S11 interface connects to the core network (400). Along with the network functions, a flavor of application layer support functions such as IMS/SIP and HTTP are reduced and deployed on the Edge to handle the signalling requests of the application intended to be processed at the Edge. Further, the P-GW functions deployed within the edge network (300) can be configured to identify the application data traffic based on the FQDNs or destination address in the incoming traffic. This allows delivery of the application data to Edge.

FIG. 11B illustrates a detailed EPS or NSA architecture of the system (2000) for deployment of all MC features on the edge using the CUPS (302) mechanism, according to the embodiments as disclosed herein.

Referring to the FIG. 11B, which is a detailed architectural representation provides an alternate architecture representation of FIG.11A with the use of the CUPS (302) architecture for a segregated control/signalling plane and user/media plane deployment in the EPC or NSA network. In this deployment, the edge network (300) hosts the GW-U and GW-C functions within the edge network (300) such that one instance of the SGi interface connects to the cloud network (500) and the other to the entities in the edge network (300) while the S11 interface connects to the core network (400). Along with the network functions, a flavor of application layer support functions such as the IMS/SIP and HTTP are reduced and deployed on the Edge to handle the signalling requests of the application intended to be processed at the Edge. Further, the GW-U functions deployed within the edge network (300) can be configured to identify the application data traffic based on the FQDNs or destination address in the incoming traffic and redirect it to the Edge.

FIG. 12 illustrates a detailed 5GS architecture of the system (2000) for deployment of all MC features on the edge using the local breakout, according to the embodiments as disclosed herein.

Referring to the FIG. 12 which is a detailed architectural representation that provides the interfaces, for complete deployment of MC services on the edge in the 5GS. In this deployment, the user plane functions deployed within the edge network (300) are configured to identify the application data traffic of the MC application and deliver the signalling plane and media plane data to the application server in the edge network (300). The segregation can be done based on the FQDNs or destination addresses in the application data traffic. Along with the eMCX AS, the underlying application layer functions to support the control/signalling plane of the application are also replicated at the edge - specifically the IMS or the SIP core (say, eIMS or eSIP Core where 'e' stands for Edge) and the HTTP proxy (say eHTTP proxy where 'e' stands for Edge).

The proposed architecture will be ideal for, but not limited to, small scale MC Service deployment and also for the isolated mode of operation for public safety [MCIOPS].

FIG. 13 is a diagram illustrating a UE 1300 according to an embodiment of the present disclosure.

Referring to the FIG. 13, the UE 1300 may include a processor 1310, a transceiver 1320 and a memory 1330. However, all of the illustrated components are not essential. The UE 1300 may be implemented by more or less components than those illustrated in the FIG. 13. In addition, the processor 1310 and the transceiver 1320 and the memory 1330 may be implemented as a single chip according to another embodiment.

The aforementioned components will now be described in detail.

The processor 1310 may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the UE 1300 may be implemented by the processor 1310.

The transceiver 1320 may be connected to the processor 1310 and transmit and/or receive a signal. In addition, the transceiver 1320 may receive the signal through a wireless channel and output the signal to the processor 1310. The transceiver 1320 may transmit the signal output from the processor 1310 through the wireless channel.

The memory 1330 may store the control information or the data included in a signal obtained by the UE 1300. The memory 1330 may be connected to the processor 1310 and store at least one instruction or a protocol or a parameter for the proposed function, process, and/or method. The memory 1330 may include read-only memory (ROM) and/or random access memory (RAM) and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

FIG. 14 is a diagram illustrating a base station 1400 according to an embodiment of the present disclosure.

Referring to the FIG. 14, the base station 1400 may include a processor 1410, a transceiver 1420 and a memory 1430. However, all of the illustrated components are not essential. The base station 1400 may be implemented by more or less components than those illustrated in FIG. 14. In addition, the processor 1410 and the transceiver 1420 and the memory 1430 may be implemented as a single chip according to another embodiment.

The aforementioned components will now be described in detail.

The processor 1410 may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the base station 1400 may be implemented by the processor 1410.

The transceiver 1420 may be connected to the processor 1410 and transmit and/or receive a signal. The signal may include control information and data. In addition, the transceiver 1420 may receive the signal through a wireless channel and output the signal to the processor 1410. The transceiver 1320 may transmit a signal output from the processor 1410 through the wireless channel.

The memory 1430 may store the control information or the data included in a signal obtained by the base station 1400. The memory 1430 may be connected to the processor 1410 and store at least one instruction or a protocol or a parameter for the proposed function, process, and/or method. The memory 1430 may include read-only memory (ROM) and/or random access memory (RAM) and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

FIG. 15 schematically illustrates a network entity according to embodiments of the present disclosure.

Each of the entities of the core network or the edge network or cloud network described above may correspond to the network entity 1500.

Referring to the FIG. 15, the network entity 1500 may include a processor 1510, a transceiver 1520 and a memory 1530. However, all of the illustrated components are not essential. The network entity 1500 may be implemented by more or less components than those illustrated in FIG. 15. In addition, the processor 1510 and the transceiver 1520 and the memory 1530 may be implemented as a single chip according to another embodiment.

The aforementioned components will now be described in detail.

The transceiver 1520 may provide an interface for performing communication with other devices in a network. That is, the transceiver 1520 may convert a bitstream transmitted from the network entity 1500 to other devices to a physical signal and covert a physical signal received from other devices to a bitstream. That is, the transceiver 1520 may transmit and receive a signal. The transceiver 1520 may be referred to as modem, transmitter, receiver, communication unit and communication module. The transceiver 1520 may enable the network entity 1500 to communicate with other devices or system through backhaul connection or other connection method.

The memory 1530 may store a basic program, an application program, configuration information for an operation of the network entity 1500. The memory 1530 may include volatile memory, non-volatile memory and a combination of the volatile memory and the non-volatile memory. The memory 1530 may provide data according to a request from the processor 1510.

The processor 1510 may control overall operations of the network entity 1500. For example, the processor 1510 may transmit and receive a signal through the transceiver 1520. The processor 1510 may include at least one processor. The processor 1510 may control the network entity 1500 to perform operations according to embodiments of the present disclosure.

In accordance with an embodiment of the disclosure, a method for deploying Mission Critical (MC) services over an edge network (300) is provided. The method may comprise: receiving, by a server (301) of the edge network (300), at least one of a MC media plane traffic and a MC signalling plane traffic from at least one user equipment (UE) (100); deploying, by the server (301) of the edge network (300), the MC services over the edge network (300) by performing at least one of: configuring user plane functions at the server (301) of the edge network (300) to redirect the received MC media plane traffic to an application domain server (501) of the cloud network (500) without passing through a core network (400) to reduce latency between the at least one UE (100) and the application domain server (501) of the cloud network (500) and redirecting the received MC signalling plane traffic to the application domain server (501) of the cloud network (500); determining a requirement for individual features of MC functionality associated with the edge network (300) and the core network (400) and splitting the MC functionality between entities over the core network (400) and entities over the edge network (300) based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network (300) to reduce latency and to improvise localization of services associated with the at least one UE (100) and redirecting all the MC media plane traffic and the MC signalling plane traffic to the server (301) of the edge network (300).

In an embodiment, wherein the server (301) of the edge network (300) comprises the user plane functions, and wherein the application domain server (501) and the server (301) comprises of application plane functions and signalling control plane functions.

In an embodiment, wherein the user plane functions comprises a Serving Gateway (S-GW) and PDN Gateway (P-GW) for an Evolved Packet Core (EPC), GW-U and GW-C functions for an Control and User Plane Separation (CUPS) (302) enabled Evolved Packet Core (EPC), and User Plane Functions (UPFs) for 5G System (5GS).

In an embodiment, wherein the application plane function comprises Common Services Core, MC Service Server, MC user database and MC Gateway, and wherein the signalling control plane functions comprises IP Multimedia Subsystem (IPS), Session Initiation Protocol (SIP) core and Hypertext Transfer Protocol (HTTP) proxies.

In an embodiment, wherein the user plane functions of the edge network (300) segregates and redirects the MC media plane traffic to the application plane functions of the server (301) of the edge network (300) and the MC signalling plane traffic to the signalling control plane functions of the application domain server (501) of the cloud network (500).

In an embodiment, wherein the MC functionality is split between the application domain entities deployed over the core network (400) and application domain entities deployed over the edge network (300) as per criticality requirements of individual features.

In an embodiment, wherein the application plane functions of the server (301) of the edge network (300) synchronize with the application plane functions of the application domain server (501) of the cloud network (500) using a synchronization channel.

In an embodiment, wherein the user plane function deployed within the edge network (300) is configured to split the MC signalling plane traffic and the MC media plane traffic between the edge network (300) and the cloud network (500) based on Fully Qualified Domain Names (FQDNs) or destination address.

In an embodiment, wherein the all MC functionality associated with the MC media plane traffic and the MC signalling plane traffic is redirected towards the edge network (300) instead of the core network (400).

In accordance with an embodiment of the disclosure, a system (2000) for deploying Mission Critical (MC) services on an edge network (300) in a wireless network is provided. The system may comprise: at least one user equipment (UE) (100) connected to at least one access node (200) and configured to communicate with the at least one access node (200) through at least one of a MC media plane traffic and a MC signalling plane traffic; the at least one access node (200) connected to at least one of the at least one UE (100), a server (301) of an edge network (300), a Control and User Plane Separation (CUPS) (302) of the edge network (300) and a server (401) of a core network (400), and configured to communicate with the at least one of the at least one UE (100), the server (301) of the edge network (300), the CUPS (302) of the edge network (300) and the server (401) of the core network (400) through the at least one of the MC media plane traffic and the MC signalling plane traffic; the server (301) of the edge network (300) connected to at least one of an application domain server (501), the at least one access node (200), the CUPS (302) of the edge network (300) and the server (401) of the core network (400), and configured to communicate with the at least one of the application domain server (501), the at least one access node (200), the CUPS (302) of the edge network (300) and the server (401) of the core network (400) through at least one of a synchronization channel, the MC media plane traffic , and the mission-critical signalling plane traffic channel; the server of the core network (400) connected to at least one of the application domain server (501), the server of the edge network (300), the CUPS (302) of the edge network (300) and the at least one access node (200), and configured to communicate with the at least one of the application domain server (501), the server of the edge network (300), the CUPS (302) of the edge network (300) and the at least one access node (200) through the MC signalling plane traffic; and the application domain server (501) connected to at least one of the server (401) of the core network (400) and the server (301) of the edge network (300) through the at least one of the synchronization channel, the MC media plane traffic, and the MC signalling plane traffic.

In an embodiment, wherein the user plane functions of the edge network (300) segregates and redirects the MC media plane traffic to the application plane functions of the application domain of the edge network (300) and the MC signalling plane traffic to the signalling control plane functions of the application domain of the cloud network (500).

In an embodiment, wherein application plane functions of the application domain of the edge network (300) synchronize with the application plane functions of the application domain of the cloud network (500) using a synchronization channel.

In an embodiment, wherein all MC functionality associated with the MC media plane traffic and the MC signalling plane traffic is redirected towards the edge network (300) instead of the core network (400).

In accordance with an embodiment of the disclosure, a server (301) for deploying Mission Critical (MC) services over an edge network (300) is provided. The server (301) may comprise: a memory (301a); a processor (301b); and a MC services controller (301d), operably connected to the memory (301a) and the processor (301b), configured to: receive at least one of a MC media plane traffic and a MC signalling plane traffic from at least one user equipment (UE) (100); deploy the MC services over the edge network (300) by performing at least one of: configuring user plane functions at the server (301) of the edge network (300) to redirect the received MC media plane traffic to an application domain server (501) of the cloud network (500) without passing through a core network (400) to reduce latency between the at least one UE (100) and the application domain server (501) of the cloud network (500) and redirecting the received MC signalling plane traffic to the application domain server (501) of the cloud network (500); determining a requirement for individual features of MC functionality associated with the edge network (300) and the core network (400) and splitting the MC functionality between entities over the core network (400) and entities over the edge network (300) based on the determined requirements and redirecting the MC media plane traffic and the MC signalling plane traffic according to split of the MC functionality; and configuring all MC functionality at the edge network (300) to reduce latency and to improvise localization of services associated with the at least one UE (100) and redirecting all the MC media plane traffic and the MC signalling plane traffic to the server (301) of the edge network (300).

Embodiments herein provide multiple alternates for deployment of the vertical applications (e.g. MC services) on an edge network (300) wherein a media plane (i.e. MC media plane traffic ) of the vertical application is moved to the edge network (300) while a signalling plane (i.e. MC signalling plane traffic ) remains under the control of a server (501) of a cloud network (500); or where features of the vertical application including related signalling and media plane are split into two groups such that one set of the features are deployed on the edge network (300) while the other set of the features remain under the control of the server (501) of the cloud network (500); or where all features of the vertical application including related signalling and media plane are deployed on the edge network (300) to achieve a lower latency, reduced backhaul traffic and higher bandwidth. In accordance with an embodiment of the disclosure, a method performed by a server of an edge network between a user equipment (UE) and a core network is provided. The method may comprise: receiving, from the UE, traffics associated with mission critical (MC) services; identifying the received traffics as one among a user plane traffic and a control plane traffic; transmitting, to an application domain of the edge network via user plane functions deployed in the edge network, a first traffic identified as the user plane traffic; and transmitting, to an application domain of a cloud network via control plane functions deployed in the cloud network, a second traffic identified as the control plane traffic.

In an embodiment, wherein CSC servers are deployed in the cloud network.

In an embodiment, wherein the CSC servers comprise at least one among group management server (GMS), configuration management server (CMS), identity management server (IdMS), and key management server (KMS).

In an embodiment, wherein the first traffic is directly transmitted from the UE to the edge network without passing through the core network.

In an embodiment, wherein traffics associated with the CSC servers are transmitted from the UE to the cloud network via the core network.

In accordance with an embodiment of the disclosure, a method performed by a server of an edge network between a user equipment (UE) and a core network is provided. The method may comprise: receiving, from the UE, a first traffic associated with mission critical (MC) service server and a second traffic associated with a CSC server, wherein user plane functions of the MC service server and control plane functions of the MC service are deployed in the edge network and the CSC server is deployed in a cloud network; transmitting the first traffic to an application domain of the edge network via at least one among the user plane functions and the control plane functions; and transmitting the second traffic to the CSC server in the cloud network.

In an embodiment, wherein the CSC server comprises at least one among group management server (GMS), configuration management server (CMS), identity management server (IdMS), and key management server (KMS).

In an embodiment, wherein the second traffic is transmitted from the UE to the cloud network via the core network.

In an embodiment, wherein the first traffic comprises a user plane traffic and a control plain traffic.

In accordance with an embodiment of the disclosure, a method performed by a server of an edge network between a user equipment (UE) and a core network is provided. The method may comprise: receiving, from the UE, a traffic associated with a mission critical (MC) service, wherein user plane functions, control plane functions and CSC functions of the MC service are deployed in the edge network; transmitting the traffic to an application domain of the edge network via at least one among the user plane functions, control plane functions and CSC functions.

In an embodiment, wherein the traffic is directly transmitted from the UE to the edge network without passing through the core network.

In an embodiment, wherein the traffic comprises a user plane traffic and a control plain traffic.

In an embodiment, wherein a session initiation protocol (SIP) core and hypertext transfer protocol (HTTP) proxies are deployed in the edge network.

The embodiments disclosed herein can be implemented using at least one hardware device and performing network management functions to control the elements.

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 spirit and scope of the embodiments as described herein.

Claims

A method performed by a server of an edge network between a user equipment (UE) and a core network, the method comprising:

receiving, from the UE, traffics associated with mission critical (MC) services;

identifying the received traffics as one among a user plane traffic and a control plane traffic;

transmitting, to an application domain of the edge network via user plane functions deployed in the edge network, a first traffic identified as the user plane traffic; and

transmitting, to an application domain of a cloud network via control plane functions deployed in the cloud network, a second traffic identified as the control plane traffic.
The method of claim 1, wherein common services core (CSC) servers are deployed in the cloud network.
The method of claim 1, wherein the CSC servers comprise at least one among a group management server (GMS), a configuration management server (CMS), an identity management server (IdMS), and a key management server (KMS).
The method of claim 1, wherein the first traffic is directly transmitted from the UE to the edge network without passing through the core network.
The method of claim 1, wherein traffics associated with the CSC servers are transmitted from the UE to the cloud network via the core network.
A method performed by a server of an edge network between a user equipment (UE) and a core network, the method comprising:

receiving, from the UE, a first traffic associated with mission critical (MC) service server and a second traffic associated with a common services core (CSC) server,

wherein user plane functions of the MC service server and control plane functions of the MC service are deployed in the edge network and the CSC server is deployed in a cloud network;

transmitting the first traffic to an application domain of the edge network via at least one among the user plane functions and the control plane functions; and

transmitting the second traffic to the CSC server in the cloud network.
The method of claim 6, wherein the CSC server comprises at least one among a group management server (GMS), a configuration management server (CMS), an identity management server (IdMS), and a key management server (KMS).
The method of claim 6, wherein the first traffic is directly transmitted from the UE to the edge network without passing through the core network.
The method of claim 6, wherein the second traffic is transmitted from the UE to the cloud network via the core network.
The method of claim 6, wherein the first traffic comprises a user plane traffic and a control plain traffic.
A method performed by a server of an edge network between a user equipment (UE) and a core network, the method comprising:

receiving, from the UE, a traffic associated with a mission critical (MC) service,

wherein user plane functions, control plane functions and common services core (CSC) functions of the MC service are deployed in the edge network;

transmitting the traffic to an application domain of the edge network via at least one among the user plane functions, control plane functions and CSC functions.
The method of claim 11, wherein the CSC server comprises at least one among a group management server (GMS), a configuration management server (CMS), an identity management server (IdMS), and a key management server (KMS).
The method of claim 11, wherein the traffic is directly transmitted from the UE to the edge network without passing through the core network.
The method of claim 11, wherein the traffic comprises a user plane traffic and a control plain traffic.
The method of claim 11, wherein a session initiation protocol (SIP) core and hypertext transfer protocol (HTTP) proxies are deployed in the edge network.