Patent Description:
In recent years several broadband wireless technologies have been developed to meet the growing number of broadband subscribers for providing better applications and services. Second generation wireless communication system has been developed to provide voice services while ensuring the mobility of users. Third generation wireless communication system supports not only the voice service but also data service. In recent years, fourth wireless communication system has been developed to provide high-speed data service. However, currently, the fourth-generation wireless communication system suffers from a lack of resources to meet the growing demand for high-speed data services. This problem is solved by the deployment of fifth generation wireless communication system to meet the ever growing demand for high speed data services. Furthermore, the fifth-generation wireless communication system provides ultra-reliability and supports low latency applications.

<FIG> depicts an exemplary implementation details of fifth-generation (<NUM>) wireless communication system. <NUM> wireless system consists of <NUM> Access Network (AN) <NUM>, <NUM> Core Network <NUM> and UE <NUM> as per 3GPP TS <NUM> specification. With recent developments in <NUM> system, it is expected that <NUM> systems should be able to provide optimized support for a various communication services, different traffic loads, and different end user communities. For example, the communication services based on network slicing may include Vehicle-to-Everything (V2X) services. The <NUM> system aims to enhance its capability to meet KPI requirements of emerging technologies like V2X applications. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent. To make <NUM> system seamless Enhanced Mobile Broadband (eMBB) becomes one of the key technologies that enable network slicing, fixed mobile convergence (FMC) which includes wireless-to-the-everything (WTTx) and fibre-to-the-everything (FTTx). Along with the aforesaid, the <NUM> systems is expected to provide native support for network slicing as well. For optimization and resource efficiency, the <NUM> system will select the most appropriate 3GPP or non-3GPP access technology for a communication service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE. Further, massive IoT connections that support for massive Internet of Things (mIoT) brings many new requirements in addition to MBB enhancements. The communication services with massive IoT connections such as smart households, smart grid, smart agriculture and smart meter will require the support of a large number and high-density IoT devices to be efficient and cost effective. Operators can use one or more network slice instances to provide these communication services, which require similar network characteristics, to different vertical industries. 3GPP TS <NUM> and <NUM> defines the management of Network Slice in <NUM> networks. It further defines the concept of communication services, which are provided using one or multiple Network Slice. A Network Slice Instance (NSI) may support multiple Communication Service Instances (CSI). Similarly, a CSI may utilize multiple NSIs.

In the recent development in the <NUM> systems, 3GPP SA6 group is working on an architecture for enabling edge computing (3GPP TR <NUM>), which specifies an application framework or an enabling layer platform to support Edge Computing in 3GPP specified networks, (e.g. discovery of edge services, authentication of the clients). The work includes the interactions between the UE and the enabling layer platform, and the interactions between the applications deployed over edge and the enabling layer platform. Further, the work is to facilitate integration with the underlying 3GPP core network. The work defines Edge Application Server (EAS) or Edge Application as a piece of software running and deployed on virtual infrastructure at the edge of the 3GPP network.

<FIG> illustrates an exemplary implementation details of Application Architecture for Edge Apps (EDGEAPP) <NUM> for enabling edge computing, as per the state-of-the-art technique. The EDGEAPP <NUM> is a new activity, which groups across 3GPP starting to look at this. It aims to enable applications to be hosted on the Edge of the 3GPP network. One of the main areas focused on is to minimalize the impact to Edge based applications - so they do not need major App redevelopment for UE use at the Edge. As can be seen in the <FIG>, UE <NUM> is in communication with Edge data network configuration server <NUM> and Edge data network <NUM>. The Edge data network <NUM> communicates with 3GPP Core Network <NUM> and 3GPP Management system <NUM>. The 3GPP Management system <NUM> is in communication with the edge Application Provider <NUM>. The UE comprises Edge Enabler Client <NUM> that enables discovery of Edge Applications and provisioning of configuration data. The Edge data network comprises Edge Enabler Server <NUM> that provides information related to the Edge Application, such as availability/enablement and related configuration, to the Edge Enabler client <NUM> and discloses capabilities of 3GPP network to Edge Applications. The Edge Configuration Server <NUM> provides Edge Data Network Configuration information to the Edge Enabler Client <NUM>.

However, the lifecycle management of edge components is considered to be a crucial management aspect. SA6 has defined EES (Edge Enabler Server) and ECS (Edge Configuration Server). ECS can be a 3GPP network function deployed at a central location serving several EES. The lifecycle of ECS, as 3GPP network function are instantiation, termination, scaling, etc. which need to be managed efficiently. Currently, in TS <NUM> Generic Provisioning Management (createMOI operation) Service is being defined. Further, in 3GPP TS <NUM> procedures to deploy a VNF are defined. However, currently deployed systems fail to manage the lifecycle of ECS efficiently while providing a capability, but not limited to, instantiation, termination, scaling.

Thus, as may be seen, there exists a need to overcome at least one of the aforementioned shortcomings in the current wireless technologies.

<CIT> relates to systems and methods for rapid application configuration and deployment. Various embodiments described therein provide systems, methods, and software to reduce the complexity of in purchasing, configuring, modifying, and deploying software applications, such as large-scale enterprise resource planning ("ERP") applications. Some embodiments reduce the complexity of configuring such application by providing tools that place configuration setting decisions in a context where the decision-making is easier. Further, some embodiments may provide tools to input application configuration preferences that, when received, are utilized by one or more processes to make configuration decisions that are consistent across the application under configuration.

Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.

Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises. a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

The present disclosure provides a method and system for ECS lifecycle management in wireless communication systemsfor deploying the Edge Configuration Server (ECS). In particular, an ECS Instance Object Class (IOC) is provided in an EDGE Network Resource Model (NRM) as an ECSFunction IOC. The NRM is maintained by 3GPP Management system containing IOCs of each object to be managed as Managed Functions. The <NUM> NRM is maintained in 3GPP TS <NUM> and TS <NUM>. This IOC represents the properties of an ECS. The ECSFunction IOC is to be included in TS <NUM>. This IOC includes attributes inherited from SubNetwork IOC (as defined in TS <NUM>[<NUM>]). The various attributes are defined in below Table <NUM>:.

<FIG> illustrates a signal flow for ECS creation and deployment procedure for ECS lifecycle management, according to an embodiment of the present disclosure. The mechanism <NUM> shown in the <FIG> may be implemented in the Edge Apps (EDGEAPP) <NUM> as shown in the <FIG>. The mechanism for creation and deployment of the ECS has following steps:.

At step <NUM>: Egde Computing Management Service Provider (ECMS_P) <NUM> receives a CreateECS request (this will use createMOI operation defined in 3GPP TS <NUM>) from Edge Computing Management Service Consumer (ECMS_C) <NUM> with ECS related requirements. The following are the list of requirements, which can be provided with the request as part of attributeListIn parameter of createMOI operation.

The above ECS requirements will be defined as attributes of ECSFunction Information Object Class (IOC) on which the createMOI operation would act. The IOC will be defined as part of <NUM> Network Resource Model (NRM) in 3GPP TS <NUM>. As an example, the one or more requirements includes, but not limited to, at least one of an EDNIInfo that includes information regarding EDN connection including DNN/ APN, EES endpoint and S-NSSAI. Further, the one or more attributes includes, but not limited to, pLMNIdList, a sNSSAIList, an endpoint information of the ECS, information about edge enabler server (EES) known to ECS including EES end point, and an edge data network (EDN) connection information as shown in the table <NUM>.

At step <NUM>: If ECS instance to be created contains virtualized part, ECMS_P derives the requirements for ECS VNF instance based on the ECS network function related requirements.

At step <NUM>: If corresponding ECS VNF Package needs to be on-boarded or changed, the NCMS_P invoke corresponding VNF Package management procedure as described in clause <NUM> in TS <NUM>.

At Step <NUM>: The NCMS_P invokes VNF lifecycle management with requirements for ECS VNF instance as descried in clause <NUM>. <NUM> in TS <NUM>.

At Step <NUM>: The ECMS_P creates the MOI (Managed Object Instance) for ECSFunction class. The MOI shall contain attributes as defined in ECSFunction IOC.

At Step <NUM>: The ECMS_P configures the new created MOI with corresponding configuration information as per the information model definition for Edge NRM 3GPP TS <NUM>.

At Step <NUM>: The ECMS_P sends the CreateECS response (this will use createMOI operation defined in 3GPP TS <NUM>) to ECMS_C with identifier of MOI and with identifier of ECMS_P which actually maintains the MOI for ECS instance.

<FIG> illustrates a flow diagram for the deployment of the ECS, according to an embodiment of the present disclosure. The deployment of the ECS <NUM> may be implemented in the EDGEAPP <NUM> for enabling edge computing as shown in <FIG> and <FIG> as disclosed above. Further, for the sake of simplicity some the explanation as applicable has been omitted herein. Further for the ease of explanation same reference numerals has been used in the forthcoming paragraphs. The method <NUM> includes the following steps.

At block <NUM>, the method <NUM> initially, receives, at a provider entity an operation request for deploying an ECS from a consumer entity. The operation request comprises one or more requirements associated with the ECS. In an implementation, the one or more requirements includes at least one of an EDNIInfo that includes information regarding EDN connection including DNN/APN, EES endpoint and S-NSSAI. As an example, alternatively, the provider entity or an ECMS_P <NUM> referred to an Edge Computing Management Service Provider (ECMSP) <NUM> and consumer entity or an ECMS_C <NUM> referred to ECMS consumer. The mechanism at the block <NUM> corresponds to the mechanism as explained in the step <NUM> of the <FIG>.

Thereafter, at block <NUM>, the method <NUM> further, identifies an ECSfunction Information Object Class (IOC) for creating an ECS instance, based on the one or more requirements included in the operation request and the IOC database. The IOC database comprises one or more IOCs.

After, identifying the ECSfunction Information Object Class (IOC), the method <NUM> performs obtaining a plurality of attributes associated with the identified ECSfunction IOC from the IOC database. The plurality of attributes including at least one of a pLMNIdList, a sNSSAIList, an endpoint information of the ECS, information about edge enabler server (EES) known to ECS including EES end point, and an edge data network (EDN) connection information.

As a further implementation, the method <NUM> performs determining if the ECS instance to be created contains a virtualized part. This determination is performed by deriving the requirements for ECS VNF instance. This step corresponds to step <NUM> of the <FIG>. Thereafter, determining if a VNF instance, of the corresponding virtualized part, is required to be one of to be on-boarded or updated. Based on the determination a VNF Package management for the corresponding VNF instance is being invoked. This step corresponds to step <NUM> of the <FIG>. Thereafter, the method <NUM> performs invoking a VNF lifecycle management with the determined requirement for the VNF instance for the ECS instance. This step corresponds to step <NUM> of the <FIG>.

In yet further implementation, the method <NUM>, creates a Managed Object Instance (MOI) for the identified ECSfunction IOC based on the obtained plurality of attributes. In an embodiment the MOI corresponds to the ECS instance. This step corresponds to step <NUM> of the <FIG>. In particular, the method <NUM>, performs replacing a value of the one or more attributes associated with the ECSfunction IOC based on the one or more requirements included in the operation request, during creation of the MOI. Thereby, configuring the new created MOI with corresponding configuration information as per the information model definition for Edge NRM 3GPP TS <NUM> as explained in the step <NUM> of the <FIG>.

Thereafter, at block <NUM>, the method <NUM>, deploys the ECS based on the identified ECSfunction IOC and the one or more requirements. This step is based on the steps <NUM>-<NUM> of the <FIG>.

After creating and configuring the MOI of the ECS instance, the method <NUM>, performs transmitting an operation request response, to the consumer entity, along with an identifier associated with the MOI and another identifier associated with the ECSMP that maintains the MOI for the ECS instance in response to the deployment of the ECS. As an example, the operation request is a create MOI request and the operation request response is a createECS. This step corresponds to step <NUM> of the <FIG>.

In view of the aforesaid, there are provided various advantageous features relating to the present disclosure:.

<FIG> illustrates another exemplary diagram of a network node. The network node <NUM> may include a communication unit <NUM> (e.g., communicator or communication interface), a memory unit <NUM> (e.g., storage), and at least one processor <NUM>. Further, the network node <NUM> may also include the Cloud -RAN (C-RAN), a Central Unit (CU), a core Network (NW), a Distributed unit (DU) or the any other possible network (NW) entity. The various examples of the network node is explained above therefore omitted here for the sake of brevity. The communication unit <NUM> may perform functions for transmitting and receiving signals via a wireless channel.

In an example, the processor <NUM> may be a single processing unit or a number of units, all of which could include multiple computing units. The processor <NUM> may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/ or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor <NUM> is configured to fetch and execute computer-readable instructions and data stored in the memory.

The processor may include one or a plurality of processors. At this time, 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 Al-dedicated processor such as a neural processing unit (NPU). The one or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or artificial intelligence (AI) model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning.

The memory may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.

<FIG> is a diagram illustrating the configuration of a terminal <NUM> in a wireless communication system according to an embodiment of the present disclosure. The configuration of <FIG> may be understood as a part of the configuration of the terminal <NUM>. Hereinafter, it is understood that terms including "unit" or "module" at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

Referring to <FIG>, the terminal <NUM> may include a communication unit <NUM> (e.g., communicator or communication interface), a storage unit <NUM> (e.g., storage), and at least one processor <NUM>. By way of example, the terminal <NUM> may be a User Equipment, such as a cellular phone or other device that communicates over a plurality of cellular networks (such as a <NUM>, <NUM>, a <NUM> or pre-<NUM> network or any future wireless communication network).

The communication unit <NUM> may perform functions for transmitting and receiving signals via a wireless channel.

However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

Claim 1:
A method for deploying an edge configuration server, ECS, by a provider entity in an edge computing communication system, the method comprising:
receiving (<NUM>) an operation request related to deployment of an ECS instance from a consumer entity, wherein the operation request comprises one or more requirements associated with the ECS;
identifying (<NUM>) at least one ECSfunction information object class, IOC, for the ECS based on the one or more requirements associated with the ECS; and
creating (<NUM>) the ECS instance based on the identified at least one ECSfunction IOC and the operation request,
wherein the ECSfunction IOC is defined with at least one attribute comprising endpoint information of the ECS, information about an edge enabler server, EES, known to the ECS including EES endpoint, and edge data network, EDN, connection information,
wherein creating the ECS instance comprises creating a managed object instance, MOI, for the identified at least one ECSfunction IOC based on the at least one attribute, the MOI corresponding to the ECS instance.