Method for managing a communication service

Abstract

Method for managing a communication service. The invention relates to a method for managing a communication service comprising management functions (F) hosted in a network (NET), the method being implemented by a management entity (100) capable of executing a management function (F), referred to as the first management entity (100), characterized in that the method comprises storing, by a device (200) in the network (NET), associations between identifiers (ID) of said management functions (F) and data (DAT) relating to the functions (F), and characterized in that it comprises: Obtaining from the device (200) an identifier (ID) of a management function (F); Requesting from the device (200) the execution of a management function (F), the corresponding request (COM(ID)) including an identifier (ID) of said function (F). Figure 1

Description

Title of the invention: Method for managing a communication service. Technical field.

[0001] The technical field is that of telecommunications.

[0002] More specifically, the invention relates to a method for managing a communication service. The communication service includes management functions hosted in a network.

[0003] 5G networks (abbreviated for fifth-generation mobile telecommunications networks) or 5GSA (acronym for 5G StandAlone) introduce the concept of a network slice. This concept relies on the virtualization of network functions. A virtual network function (VNF, or VNFs in the plural) is a computer application that implements an expected function of a computer or telecommunications network, such a function being, for example, a directory service, a routing service, or another.

[0004] In a 5G network, unlike previous generations of telecommunications networks, all network functions are virtualized; that is, the functions necessary for the operation and management of the network are performed by computer programs running in virtual machines or similar technologies such as containers. This contrasts with previous generations of telecommunications networks in which, generally, network functions were attached to dedicated hardware equipment, such as PBXs, routers, and base stations. In a 5G network, a set of hardware resources is available at several locations necessary to perform network functions, but no function is a priori attached to a given piece of hardware.This concept of network function virtualization, which originally appeared in the context of mobile telecommunications networks, can be applied to any type of network, including those with fixed access.

[0005] The management operations of such a telecommunications network are also performed by virtual functions. Virtual functions may be dedicated to management operations, or virtual network functions may implement management operations in addition to their network operation functions. In this case, the management functions are often accessed through management elements of the virtual network functions.

[0006] The virtualization of network functions in a 5G network makes it possible to implement the concept of a network slice by distributing network functions across hardware resources that have been previously selected and reserved. The set of operations that allow the management of a network slice is referred to as orchestration. Orchestration is performed by an entity called the orchestrator, which implements the selection and reservation of hardware resources; the starting and stopping of virtual network function (VNF) instances using the reserved hardware resources; the creation of relationships between the VNFs to allow them to communicate with each other and the deletion of these relationships if necessary; and the provision of access points to manage the VNFs, for example, stopping them, restarting them, changing their relationships, duplicating them, or any other management operation.The creation of a network slice is therefore also a specific orchestration operation.

[0007] In recent developments, network functions are increasingly contained within containers and are therefore no longer, strictly speaking, virtual network functions. In this case, we will speak of containerized network functions and use the acronym CNF (Containerized Network Function). For our presentation, this recent development is not important, and we will only refer to virtual network functions, taking into account that these network functions can in fact also be containerized network functions.

[0008] A network slice is defined in relation to a public land mobile network (PLMN). Such a public land mobile network is a mobile telecommunications network, existing in a given country, that provides a user equipment (UE) with physical access to telecommunications through antennas, base stations, and any other necessary equipment. Once physical access to the telecommunications network is guaranteed by the PLMN, a user equipment can access one or more network slices and, more generally, a communication service using the access provided by the PLMN. Access to the service could be provided by a non-mobile access network, and the concepts would remain similar.

[0009] The 3GPP TS 23.501 standard (Security architecture and procedures for 5G System) defines and specifies the operation of the virtualized network functions that form a 5G slice. The GSMA NG 116 standard, for its part, describes the attributes exchanged between different entities to characterize a network slice, and in particular relies on a generic network slice template, called GST (Generic Network Slice Template). The GST includes optional attributes or These are mandatory attributes that describe the expected features and performance of a network slice, but without detailing the network functions instantiated within a given slice. By setting the values ​​of the GST attributes, it is possible to define a Network Slice Type (NEST). The values ​​set in a NEST express a set of requirements to fulfill a client use case.

[0010] Telecommunications service users, on the other hand, are not aware of the organization of networks into slices. They use a telecommunications service without knowing how it is delivered, which may involve the implementation and cooperation of several network slices.

[0011] For example, a telecommunications service for a company might consist of providing mobile devices and associated communication services to users who are employees of the company. Depending on the user's usage, the communication service offered will switch users between several network segments. For example, a first network segment might provide access to the Internet, and a second segment would correspond to the employee's corporate network. Different applications hosted on the device would then use different network segments; the web browser would use the Internet segment, while a business application would use the corporate network segment.Further additions are conceivable: for example, a user might want to purchase a dedicated network slice for gaming, with specific capabilities such as low latency, and would buy access to a third dedicated slice, separate from the general internet access slice; a user might hold a high-level position, and their company could provide them with access to a specific slice with additional security features. The whole system constitutes a single telecommunications service, provided to the end user by a communications service provider, which utilizes multiple network slices to deliver the final service. This switching between multiple network slices is not initially perceptible to the customer service user, except perhaps through the perception of an enhanced service for certain uses, such as online gaming in the example above.The final service thus provided is often called customer service, a translation of the English "Customer Facing Service," also known by the acronym CFS. More precisely, CFS is a technical definition that must be instantiated with specific values ​​to define a concrete service for users. Such customer service, the customer being an end user, a company, or any other organization, is provided by a communication service provider, a translation of the English "Communication Service Provider," also known by the acronym CSP. The CSP interacts with one or more network slice providers, called NSPs (acronym for Network Slice Provider). which themselves interact with network slice orchestrators, called NOPs (acronym for Network Operation).

[0012] More specifically, a customer service corresponds to a class of different products that can be provided by a CSP to distinct customers. The service sold to the customer is represented from a commercial point of view as a product. A product is built from a CFS definition, which provides attributes and possible values ​​for them. Defining a product consists of specifying the values ​​of the attributes in the CFS definition used with respect to the values ​​allowed by the CFS definition.

[0013] To give another example, a communications service provider may want to offer companies a service in which user terminals (its employees' terminals) have access to a higher-performing network in specific geographic areas. These geographic areas could be, for example, the company's production sites. At these sites, employee terminals have access to higher bandwidth, allowing them to easily transmit video, and lower latency. Such a preferred geographic area is often called a tracking area. Outside of these preferred areas, terminals have access to a standard service.

[0014] Such a service can be offered by a service provider to several companies, which will of course require that the tracking areas be adapted to their own sites. The communication service provider will therefore have to provide different products for the different companies concerned to whom it provides the service.

[0015] The concepts of service, which corresponds to a possible class of products, and product, which corresponds to the implementation of a given service in a given context, can often be confused. In the following, we will refer to communication services for elements that can be services in the sense of a CFS definition or products, that is, instantiated communication services. In particular, we will speak of service management for operations that consist of managing a given product, instantiated according to a given CFS definition.

[0016] The invention relates to the management of a communication service. State of the art

[0017] A communication service provider (designated by the acronym CSP) has management needs for the service(s) it offers to its customers, who may be the end users of the service or organizations such as companies that group the end users.

[0018] A primary management requirement of the CSP is the ability to create a communication service. This communication service is provided by virtual network functions hosted within a 5G network, organized into different segments. Numerous operations must be performed to create the service, such as launching virtual network functions and linking these functions together to create slices. Furthermore, parameter values ​​must be set, for example, different throughput values ​​for different slices in the service examples presented.

[0019] These operations are performed by a network orchestrator, designated by the acronym NOP (Network Operator), which executes management functions, with fixed parameters, to carry out management operations and, in particular, the creation of the service. These operations are performed at the request of the CSP, but generally in a non-automated manner. When a contract is established between the CSP and the operator in charge of the orchestrator, an agreement is reached on a network slice architecture that will constitute the service, and the orchestrator then performs these management operations, including the creation of the service. The interaction between the CSP and the NOP orchestrator often takes place through a network slice provider, called an NSP (Network Slice Provider).A Communication Service Provider (CSP) orders network slices from one or more Network Service Providers (NSPs) to operate its communication service. The NSP(s) then request one or more Network Operations Platforms (NOPs) to orchestrate the ordered network slices. All of these operational requests are made manually, and the CSP does not have access to the service management functions associated with creating network slices. Currently, the exchanges between these entities, as defined by the GSMA NG 116 standard, are limited to functional or quality of service requests and do not allow for the precise specification of the virtualized network functions that will be instantiated to provide a communication service, nor the links that will be created between them.The various operating parameters of virtual network functions, such as function throughput, latency, authentication data, etc., are also not specified in this standard.

[0020] Another service management operation that the CSP must be able to perform is provisioning. This involves transmitting end-user information to the virtual functions that need it, for example, all those that manage identity. Provisioning operations are generally carried out by registering the information in the 5G network's Universal Data Repository (UDR) virtual network function. The network operator will therefore allow the communication service provider to call its UDR function to register the necessary data during provisioning operations.

[0021] Other management operations, in addition to provisioning, are performed by calling the network's UDR function to register data corresponding to the instantiation of the communication service. These calls to the UDR function must comply with the specific characteristics of the UDR function as provided by the equipment manufacturer (often referred to as OEM, an acronym for Original Equipment Manufacturer) that supplies this function to the network operator. The OEM may be a hardware supplier in which the software implementing the UDR function runs, or a pure software supplier.

[0022] Other management functions are called via management elements attached to virtual network functions. These management elements are entry points for virtual network functions that allow operating parameters to be specified, while other entry points correspond to the function's operation. Here too, calls to the management elements must comply with the specific characteristics of the management functions provided by the equipment manufacturers.

[0023] Other management functions are described according to the FCAPS model (Fault, Configuration, Accounting, Performance, Security). In the current state of 5G standardization, there is no standardized management function that allows a communication service provider to access these management functions. Many management functions exist for these aspects and are deployed in networks but are generally not accessible to communication service providers. They remain for the exclusive use of network operators who host the virtualized network functions that form the slices included in the communication services.

[0024] To summarize, the management operations of a communication service, including the creation of network slices forming the service, the setting of parameter values, the provisioning of service users, and the various operations corresponding to the FCAPS model, are performed by executing management functions (or management elements, which are calls dedicated to network function management). The ability to call these functions or management elements is generally not available to the communication service provider. When it is possible for the CSP to directly call a network management function, it is the function as defined by the OEM that is made accessible, for example, to perform provisioning operations by calling the UDR function.

[0025] The current situation presents several disadvantages.

[0026] The main drawback is that management operations are poorly accessible or not accessible at all to communication service providers. Consequently, developments Service updates are difficult to perform, requiring manual execution of instructions by the network orchestrator(s) in response to requests from service providers. Communication service architectures are generally fixed in advance and cannot be changed by communication service providers through link updates between virtual network functions. Even simple parameter changes, such as the previously discussed changes to the data rates provided by premium and standard network segments, are not necessarily within the control of the communication service provider and may require significant human intervention, thus lengthening communication service update times.

[0027] In some cases, access to management functions is granted to the communication service provider. This is often the case for certain accesses to the UDR function to allow the communication service provider to provision its service with end-user information. The drawback here is that the operation of the communication service becomes tied to the specifics of the management functions as provided by the OEMs. If the NSP network slice provider, or the NOP orchestrator of the network slice included in the communication service, decides to change the OEM for a management function to which the CSP has access, the CSP will have to change all its interactions with the management function.These updates can be complicated and will hinder OEM equipment changes, especially since they must be made for all communication service providers that interact with the changed management function that is hosted by the NSP network slice provider or NOP orchestrator.

[0028] The invention improves the situation. Description of the invention

[0029] According to a first functional aspect, the invention relates to a method for managing a communication service comprising management functions hosted in a network, the method being implemented by a management entity capable of performing a management function, referred to as the first management entity, characterized in that the method comprises storing, on a network device, associations between management function identifiers and data relating to the functions, respectively, and characterized in that it comprises: - Obtain from the device an identifier for a management function; - Request the device to execute a management function, the corresponding request including an identifier of said function.

[0030] In exemplary embodiments, the first management entity implementing the process is responsible for providing communication services. The execution of one or more management functions corresponds to the implementation of a communication service management operation. A complex management operation can be decomposed into several requests for the execution of management functions.

[0031] Thanks to the invention, a management entity responsible for providing communication services gains the ability to have management operations performed by management functions hosted on the network. To do this, the management entity requests the execution of a management function from the device. One possible way to do this is to transmit one or more requests to the network device to execute management functions. The management entity has previously obtained identifiers that will be used for the various requests to execute the different management functions via the network device. The network device has an association between function identifiers and data relating to the functions that will allow it to fulfill the request to execute the management function.This data includes, for example, network addresses for reaching the function, specifics of function calls, parameters to use, etc.

[0032] The first drawback of the prior art, namely the difficulty for communication service providers to access the management functions of the communication service they offer, is therefore corrected by the network device which accepts requests to execute management functions.

[0033] However, the second drawback of the prior art is also remedied by the fact that the network device transmits only management function identifiers to the management entity and maintains an association between these identifiers and function data. This function data will include, for example, all the specific features introduced by the various equipment manufacturers that provide the management functions. If the equipment manufacturer providing a management function were to change, it is not necessary to notify the various communication service providers that call upon this management function. The identifier of the management function they use does not change; only the function data needs to be updated.

[0034] More generally, the invention makes it possible to avoid fixing the architecture of network slices and communication services according to the architecture defined by the OEM that provides the infrastructure on which the communication service runs. A given OEM can change its architecture, and this can be done without impact on the communication service provider since the latter only interacts with the network slices through a module under the responsibility of the operator in charge of slice orchestration. Or even, it It will be possible to completely change providers for one or more functions of the network segments used by the service. With the method according to the invention, an infrastructure change can be carried out without the entity responsible for providing the communication service having to change the values ​​of all the operating parameters associated with the various pieces of equipment it currently manages. Furthermore, thanks to the invention, the OEM no longer has to adapt its offerings to the different possible uses of its equipment; it is the responsibility of the communication service providers and orchestrators to adapt the architecture proposed by the OEMs to their specific needs.

[0035] The disadvantages of the prior art are therefore corrected by the invention.

[0036] According to one embodiment of the invention, the method further comprises a step of creating a communication link between the management entity and the network device.

[0037] In this embodiment, if the link does not pre-exist the implementation of the process, it is created to enable communication between the management entity responsible for providing a communication service and the network device hosting the communication service management functions. This step of creating the communication link can take place at any time before requests to execute management functions are sent to the network device.

[0038] According to a first embodiment of the invention, the request to execute a management function includes an update of a parameter value and the data associated with the identifier included in the request includes a constraint on the parameter value.

[0039] Thanks to this embodiment, the network device can perform checks on a management operation that consists of updating a parameter value. To take a given example, a parameter that the communication service might want to update is the bandwidth allocated by different network segments forming the communication service to end users. The communication service provider might want to update the different bandwidths through a management operation that includes requesting the execution of a management function. The updated bandwidth values ​​must comply with constraints on their maximum values. The data associated with the identifiers of the called functions includes, in this embodiment, constraints on the possible values ​​of the updated parameters, which will allow the network device to execute the update operation or not.

[0040] According to another embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, the process includes a preliminary step of request by the management entity to the management function initiation device. According to some embodiments, the request to initiate management functions is included in a request to create one or more network segments included in the communication service.

[0041] In this embodiment, a communication service is created by a service-providing management entity, avoiding the rigidities of the current model and, in particular, the excessive reliance on information provided by the equipment manufacturer(s) supplying the hardware components in which the virtual network functions forming the slice(s) used by the service run. The management entity requests the launch of management functions and receives in return identifiers for the various management functions. This request to launch management functions is generally included in a broader request to launch virtual network functions or network slices that constitute the communication service.

[0042] In response to this request, the management entity receives management function identifiers that will allow it to manage the service without being tied to the specific characteristics of the equipment manufacturers. Information specific to the equipment manufacturers, relating to the virtual network functions present in the slices that will actually perform the management operations, is hidden from the management entity providing the service. When the management entity in charge of the service sends a request to execute a management function, it does so to a network device, which will translate the request into an instruction acceptable to the virtual network function present in the slice that will actually perform the management operation. This translation uses the data relating to the management functions associated with the identifier used.Therefore, information from equipment manufacturers does not need to be known to the management entity responsible for providing the communication service.

[0043] According to another embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, the device is a network slice orchestrator and the management entity transmits execution requests to a dedicated module of the device.

[0044] Thanks to this embodiment, the invention makes it possible to create network slices (this is the role of the orchestrator) which will form a communication service, while allowing the communication provider to directly manage the communication service formed by the slices created by the orchestrator. To avoid excessive dependence on equipment manufacturers, the orchestrator's ability to directly manage the service does not consist of leaving open access to the equipment manufacturers' management functions, but rather of offering a dedicated module that acts as a gateway to the management functions. This dedicated module manages an association between identifiers of the management functions and data relating to these functions. When the provider of The communication service needs to perform a management operation; it uses the identifier that has been provided to it, transmits the execution request with this identifier to the access gateway, and the access gateway can retrieve the data necessary to actually call the management function using the data associated with the identifier.

[0045] According to another embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, the step of obtaining an identifier of a management function is done through a management entity in charge of providing network slices, called the second management entity.

[0046] According to one embodiment, which can be implemented cumulatively with the previous embodiment, the second management entity acts as an intermediary for the request to launch management functions, by the first management entity, to the network device.

[0047] According to one embodiment, which may be implemented cumulatively with the preceding embodiments, the second management entity acts as an intermediary for the request to create one or more network segments included in the communication service, by the first management entity, to the network device, said request to create segments including a request to launch management functions.

[0048] This embodiment introduces an additional role to enable greater dynamism in the provision of communication services. Specifically, the entity responsible for providing network slices, referred to as the second management entity, can be separate from the device responsible for orchestrating the network slices, which is a telecommunications operator closely linked to the physical implementation of the network slices. Following a request to create network slices, which includes a request to launch management functions, from the entity responsible for providing a communication service, the entity responsible for providing network slices can choose from several possibilities to present the best options to the entity responsible for providing the communication service. In some embodiments, the request to launch management functions includes information on requested characteristics.In this way, the choice of created slices and the launched management functions take these characteristics into account. In some embodiments, the network slices pre-exist the implementation of the communication service management process, and the management entity responsible for providing network slices acts as an intermediary for the provision of data by the network device to the management entity.

[0049] According to another embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, the step of obtaining a management function identifier includes the provision of additional information by the second management entity to the first management entity. According to another method, which may be implemented alternatively or cumulatively with the previous method, the step of obtaining an identifier of a management function includes the provision of additional information by the second management entity to the device, said additional information being associated by the device with identifiers of management functions in addition to the data relating to the functions.

[0050] Through these embodiments, the management entity that acts as an intermediary between the communication service provider and the network slice orchestrator will provide additional information useful to both entities for the implementation of the communication service. For example, the requested quality of service information, which involves specific network slice configurations, can be transmitted to the management entity responsible for orchestrating the network slices. This information, combined with the identifiers of the management functions, can then serve as constraints when the relevant management functions are called.

[0051] According to another embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, the identifiers obtained by the first management entity are supplemented by the first management entity with additional information, said supplemented information associating functionalities of the communication service and functions hosted in the network.

[0052] Thanks to this embodiment, the management of the communication service by the first management entity is facilitated. For example, enriching the received identifiers makes it possible to link a specific communication service management operation, known to the first management entity, to an identifier, known to the network device, which can be used to transmit a request to execute a management function.

[0053] According to another embodiment, which can be implemented cumulatively with the previous embodiment, the information completed is also used by the first management entity to display a catalogue of services provided by the first management entity.

[0054] Thanks to this embodiment, the complete set of information allows the first management entity to display a catalog of offered services to its potential customers. Such a catalog will include, for example, information on the quality of service offered. It may also include information useful to the customer for registering for the service, which will require the use of service functionalities corresponding to network slice management operations, and therefore to requests for the execution of management functions.

[0055] According to a second functional aspect, the invention relates to a method for making available management functions of a communication service, said management functions being hosted in a network and being capable of being executed by a management entity, the method being implemented by a network device, characterized in that the device stores associations between management function identifiers and data relating to the functions, respectively, and characterized in that it comprises the following steps: - Providing the management entity with an identifier for a management function; - Receiving a request from the management entity to execute a management function including an identifier for said function; - Execution of the received request by calling the management function using the data associated with the identifier included in the request.

[0056] Thanks to this aspect of the invention, the management functions are readily accessible to the management entity responsible for providing the communication service, without the latter being tied to the specific characteristics of the equipment manufacturers providing the management functions. A network device first provides management function identifiers to the communication service provider. Requests to execute management functions are then sent to the network device. Through the link maintained by the network device between these identifiers and any information useful for executing the corresponding management functions, the network device can execute the request by calling the identified management function. The associated data includes, for example, the network addresses of the function in question.

[0057] According to a first embodiment of this second aspect, the request to execute a management function includes an update of a parameter value; the data relating to the identified management function includes a constraint on the value of the parameter; and the device only calls the management function if the constraint on the value of the parameter is met.

[0058] Thanks to this embodiment, constraints on possible management operations are implemented and respected by the network device that carries out the actual transmission of execution requests to the management functions. If an update of a parameter falls outside the accepted limits, the execution request is not carried out by calling the function.

[0059] According to a first material aspect, the invention relates to a management entity implementing a method for managing a communication service comprising management functions hosted in a network, the management entity being capable of performing a management function, characterized in that a device of the network stores associations between management function identifiers and function-related data, respectively, and characterized in that it comprises the following modules: - Module for obtaining an identifier for a management function from the device; - Query module to the device of an execution of a management function, the corresponding query including an identifier of said function.

[0060] According to a second material aspect, the invention relates to a device belonging to a network, implementing a method for making available management functions of a communication service, said management functions being hosted in the network and being capable of being executed by a management entity, characterized in that the device stores associations between management function identifiers and data relating to the functions and characterized in that it comprises the following modules: - Module for providing the management entity with an identifier for a management function; - Reception module from the management entity of a request to execute a management function including an identifier of said function; - Module for executing the received request by calling the management function using the data associated with the identifier included in the request.

[0061] According to one embodiment of this material aspect, the device belonging to a network is an orchestrator of slices included in said network.

[0062] According to another material aspect, the invention relates to a computer program capable of being implemented by a management entity capable of performing a management function of a communication service, said program comprising code instructions which, when executed by a processor, carries out the steps of the management process defined above.

[0063] According to another material aspect, the invention relates to a computer program capable of being implemented by a device belonging to a network, said program comprising code instructions which, when executed by a processor, carries out the steps of the provisioning process defined above.

[0064] According to another material aspect, the invention relates to a data carrier on which is recorded a computer program suitable for implementation by a management entity capable of performing a management function of a communication service, said program comprising code instructions which, when executed by a processor, carries out the steps of the management process defined above.

[0065] According to another material aspect, the invention relates to a data carrier on which is recorded a computer program capable of being implemented by a device belonging to a network, said program comprising instructions for code which, when executed by a processor, carries out the steps of the provisioning process defined above.

[0066] In another embodiment, the invention relates to a method for managing a communication service comprising management functions hosted in a network, said method being implemented by a telecommunications system comprising a management entity capable of performing a management function, referred to as the first management entity, and a network device, characterized in that the method comprises storing, on the device, associations between management function identifiers and data relating to the functions, and characterized in that it comprises the following steps: - Obtaining by the management entity from the device an identifier of a management function; - Request by the management entity to the device for the execution of a management function, said request including an identifier of said function; - Execution by the device of the received request by calling the management function using the data associated with the identifier included in the request.

[0067] According to a material aspect of this other embodiment, the invention relates to a telecommunications system implementing a method for managing a communication service comprising management functions hosted in a network, said system comprising a management entity capable of performing a management function, referred to as the first management entity, and a network device, characterized in that the device stores associations between management function identifiers and data relating to the functions, and characterized in that the first management entity comprises the following modules: - Module for obtaining an identifier for a management function from the device; - Query module for the execution of a management function, the corresponding query including an identifier of said function;

[0068] And characterized in that the device comprises the following modules: - Module for providing the management entity with an identifier for a management function; - Reception module from the management entity of a request to execute a management function including an identifier of said function; - Module for executing the received request by calling the management function using the data associated with the identifier included in the request.

[0069] According to another embodiment of this material aspect, the telecommunications system includes a second management entity which serves as an intermediary for the first management entity to obtain, from the network device, an identifier of a management function.

[0070] Data carriers can be any entity or device capable of storing programs. For example, the carriers can include a storage means, such as a ROM, for example a CD-ROM or a microelectronic circuit ROM, or a magnetic recording means such as a hard drive. Alternatively, the carriers can be transmissible media such as an electrical or optical signal, which can be transmitted via an electrical or optical cable, by radio, or by other means. The programs according to the invention can, in particular, be downloaded from a network such as the Internet. Alternatively, the information carrier can be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the process in question.The program according to the invention can use any type of computer technology in terms of compiled programming languages, interpreted languages, or a combination of both, as well as in terms of operating systems. Brief description of the figures.

[0071] The invention will be better understood upon reading the following description, given by way of example, and made with reference to the accompanying drawings in which:

[0072] [Fig-1] represents a management entity and a network device according to the invention.

[0073] [Fig.2] represents an example of a system in which the methods according to the invention are executed.

[0074] [Fig.3] illustrates an example of a sequence of message exchanges between elements of a system within the framework of an embodiment of the invention. Detailed description

[0075] Fig. 1 represents a management entity 100 and a network device 200 according to an example of an embodiment of the invention.

[0076] The management entity 100 and the device 200 have the hardware architecture of a conventional computer. They include in particular one or more processors, one or more RAM type random access memories and one or more read-only memories such as Flash memory, ROM, (not shown in the figure) as well as input-output devices such as keyboards and / or screens (not shown in the figure) and devices dedicated to network communication, such as network ports, antennas, or others depending on the communication technology used.

[0077] The management entity 100 and the device 200 can be embedded in a server or run in a cloud computing architecture.

[0078] Management entity 100 comprises, in the example presented here, the following modules: - A module 101 for obtaining from device 200 an ID identifier of a management function F; - A module 102 requesting device 200 from an execution of a management function F, the corresponding COM(ID) request including an ID identifier of said function F.

[0079] Device 200 includes, in the example presented here, the following modules: - A module 201 for providing the management entity 100 with an ID identifier of a management function F; - A module 202 receiving from management entity 100 a COM(ID) request to execute a management function F including an ID identifier of said function F; - A module 203 for executing the received request by calling the management function F using the DAT(F) data associated with the ID included in the request.

[0080] Furthermore, the device 200 stores associations between ID identifiers of management functions F and DAT(F) data relating to the functions F. Such an association is managed, for example, by using a database, a key-value file, or any other computer component to save the associated data and the association between this data and identifiers. The association is managed using computer means to save the associated DAT(F) data and retrieve it from an ID identifier, such as calls to dedicated functions, file writes, relational or non-relational database operations, or any other appropriate means.

[0081] Management entity 100 implements a process for managing a communication service. In some embodiments, management entity 100 fulfills the role of a communication service provider, designated by the acronym CSP (Communication Service Provider). In this case, management entity 100 is responsible for providing a communication service to customers not shown in [Fig. 1], who may be end users of the service or organizations that order the service for their users. As a service provider, management entity 100 wishes to be able to manage communication service 100 to conform to its needs. To manage the communication service, management entity 100 must be able to perform management operations that include executing management functions.

[0082] The communication service in question is built according to the architectural principles of network function virtualization. In accordance with this principle, the operation of the communication service is rendered by the execution of virtualized network functions and, in particular, the service management operations of Communication is achieved by executing management functions (F). The virtualized functions forming the communication service, and in particular the management functions (F), are hosted on a network (NET). The communication service can comprise several network slices, which are appropriate groupings of virtual network functions.

[0083] Only one management function F is shown in [Fig. 1], but a typical communication service will comprise several thousand virtualized functions, which can be managed by management elements, organized into several network slices, connected by dedicated communication links. The set of management operations for a communication service is therefore very complex. The FC APS model describes the main categories of management operations that can be performed. These consist either of calling dedicated functions, which primarily perform management operations for the communication service, or of calling management elements, which allow the management of a network function whose main function is an operation of the service itself.In what follows, no distinction is made between the execution of a management function and the execution of a management element of a function that performs operations other than management operations. Performing a management operation such as provisioning users for the communication service will often involve calling several management functions or management elements, with dedicated parameters, according to a specific sequence.

[0084] Among the functions that primarily perform management operations, we can mention the UDR (Universal Data Repository) function, which acts as a repository for all the data necessary for the operation of the communication service. Management operations related to the UDR function include setting parameter values ​​(for example, data rates) which are stored in the UDR; provisioning service users by storing their connection and subscription data, among other things, in the UDR; defining and changing the communication service architecture by storing, again in the UDR, data relating to the links between virtualized functions, etc.

[0085] Device 200 implements a method for making available management functions for a communication service comprising management functions F hosted on the NET network. This provision is made for the benefit of the management entity 100, which wishes to execute management functions in order to perform management operations for the communication service provided by functions hosted on the NET network. In some embodiments, Device 200 is an orchestrator of network slices and virtual network functions hosted on the NET network. Device 200 can then be designated by the acronym NOP (of (English: Network Operator). The implementation of this process allows device 200, which belongs to the NET network, in addition to orchestrating virtual functions and network slices to build a communication service, to make communication service management functions available to entity 100, which is responsible for providing the communication service. Thanks to this provision, management entity 100 can autonomously perform the management operations of the communication service it provides to its customers by calling the management functions through device 200.

[0086] The processes for managing the service, on the one hand, and for making management functions available, on the other, begin with the management entity 100 obtaining (or the device 200 providing) management function IDs. These IDs will then be used to execute COM requests for the management functions F. To this end, the device 200 stores associations between the IDs and DAT data relating to the management functions F identified by the IDs.

[0087] IDs can also be business operation identifiers in cases where several business operations are performed by differentiated calls to a single business function, or where the execution of a business operation involves the successive calling of several business functions. For the sake of simplicity, we will present only business function identifiers hereafter. In the exposition of [Fig. 2], we provide more details on the data categories that can be used within the scope of the invention.

[0088] For example, the device 200 will manage an association between an identifier corresponding to the UDR function and data relating to the actual operation of that UDR function. The NET network can host several UDR functions that fulfill the functionalities of a universal data repository for different communication services. In this case, the device 200 will provide each management entity 100 with different identifiers for the UDR function assigned to it. Each management entity that wishes to manage the communication service it provides by recording data using its own UDR function will have its own identifier for this purpose. The DAT data associated with each identifier could be, for example, the network addresses of the UDR functions deployed in the NET network, the address associated with an identifier for a communication service being that of the UDR function of that communication service.Other data can be associated with a single identifier, for example, function call forms specific to each UDR function of each communication service. For example, the UDR functions hosted in the NET network can be provided by different equipment manufacturers (designated by the acronym OEM for Original Equipment Manufacturer). The DAT data associated with the different IDs of the F functions, in this case, can correspond to the different function call syntaxes as defined by the various OEMs. Depending on the OEM providing the UDR function for a given communication service, it will therefore be possible to find the specific syntax imposed by the OEM within the DAT data corresponding to the UDR function ID for that communication service. In other examples, a single UDR function, provided by a given OEM, will be used in parallel by several communication services. Each management entity will be assigned a different ID to call its UDR function. The DAT management data associated with the different IDs may then relate to different access paths to the same UDR function, which offers parallel calling capabilities for the different communication services.

[0089] When the management entity 100 needs to perform a management operation on the communication service, it will execute a management function F hosted on the NET network. However, the management entity 100 only has one ID identifier corresponding to the function F. The processes for managing the service, on the one hand, and for making the management functions available, on the other hand, therefore proceed by a transmission by the management entity 100 (respectively a reception by the device 200) of a COM(ID) request to execute a management function F including an ID identifier of said function F.

[0090] We saw above how the association managed by device 200 between ID identifiers and DAT(F) data allows device 200 to retrieve data that enables the specific call to function F. The provisioning process then continues with device 200 transmitting the completed execution request to management function F, using DAT(F) data associated with the ID identifier. This transmission could, for example, correspond to a call to function F, by retrieving its network address and the exact syntax required to call it from among the DAT(F) data associated with the ID identifier. The call to the management function is thus carried out in accordance with the initial request of management entity 100.

[0091] The implementation of management processes on the one hand and the provision of management functions on the other resolves two drawbacks of the state of the art. First, the management functions hosted in the NET network are indeed made available to the management entity 100 responsible for providing the communication service, which therefore wishes to be able to perform management operations. Second, and most importantly, this openness is achieved without being tied to the specificities of the OEM equipment manufacturers that provide the concrete management function. To this end, a device 200 in the NET network manages an association between abstract ID identifiers, The system provides management entity 100 with concrete DAT data to perform management operations, enabling calls to the management functions. Device 200 then executes or requests the execution of the concrete functions F following a request from management entity 100. This request is identified by an ID, which allows the DAT data for execution to be retrieved. The management operations are therefore performed at the request of management entity 100, without being tied to the specific requirements of OEMs. Indeed, the OEM supplier of function F can change, and it is not necessary for management entities 100 requesting the management operations performed by this function F to be informed or to change their requests for executing management functions.Only the DAT(F) data associated with the ID identifiers, managed by device 200, need to be modified in the event of a change of OEM equipment supplier.

[0092] In executable examples, the COM(ID) request corresponds to updating a parameter value. A typical example is setting a throughput value for a communication service element. In this case, the network device 200 can manage, within the data associated with the COM(ID) request (DAT(F)), a constraint on the possible values ​​that the parameter can take, typically a maximum value for a throughput. When the COM(ID) request is received, the device 200 can then check that the value transmitted by the management entity 100 complies with the associated constraint present in the DAT(F) data. If it does not, the request will not be executed by the device 200; it will not call the function F to update the parameter. In executable examples, the device 200 will inform the management entity 100 of the failure to execute the COM(ID) request, possibly justifying the non-execution by the violated constraint. 。

[0093] In examples of embodiments, the methods of the invention include a prior step of request by the management entity 100 to the device 200 to launch management functions F. This request to launch management functions F may be included in a request to create network slices.

[0094] The methods of the invention can be implemented in the context of creating a communication service. The management entity 100, responsible for providing a communication service, can request the device 200, which can be a network slice orchestrator, to create network slices that will constitute the communication service to be created. In addition to executing the request to create network slices, the device 200 will provide management function identifiers to the management entity 100 in response. These identifiers can then be used by the management entity 100 to request the execution of COM(ID) requests to execute management functions.

[0095] Device 200, as a network slice orchestrator, is particularly well-suited to implement the process of making management functions available. When it creates network slices at the request of the management entity 100, this creation includes launching management functions to enable the future management of the communication service. Device 200 can then create identifiers for all the management functions (or management operations comprising the successive calling of several management functions) that it wishes to make available to the management entity 100. Device 200 will manage the association between these abstract IDs and the concrete DAT(F) data that enables the management operation to be performed by calling the management function F. Device 200, as a network slice orchestrator, knows the concrete DAT(F) data since it has launched the management functions F.A dedicated module of device 200 is then used to manage the association between function ID identifiers and DAT(F) data relating to the functions, receiving COM(ID) requests and executing the received COM(ID) requests by calling the management functions F using the associated DAT(F) data.

[0096] In exemplary embodiments, obtaining a management function identifier is done through a second management entity (not shown in [Fig. 1]) responsible for providing network slices. [Fig. 2] shows an example of such an embodiment, in which three management entities and devices interact: - Management entity 100 is in charge of providing communication services and is referred to as CSP in [Fig.2]. - A second management entity, responsible for providing network slices, is named NSP in [Fig.2] and serves as an intermediary between management entity 100 and device 200. - Device 200 is responsible for orchestrating network slices and is referred to as NOP in [Fig.2].

[0097] Figure 2 represents an example of a telecommunications system in which the methods according to the invention are carried out.

[0098] The system in question comprises entities and devices that implement the methods according to the invention, enabling the management of a telecommunications service. In this embodiment, it comprises three management entities: CSP, NSP, and NOP. The CSP management entity corresponds to management entity 100 in [Fig. 1]. The NOP management entity corresponds to device 200 in [Fig. 1]. The NSP management entity corresponds to a management entity acting as an intermediary between entity 100 and device 200 for certain operations. [Fig. 2] represents another example of an implementation of the methods of the invention.

[0099] The CSP, NSP, and NOP management entities have the hardware architecture of a conventional computer. They include, in particular, one or more processors, one or more RAM memory units, and one or more read-only memory units such as Flash memory or ROM (not shown in the figure), as well as input / output devices such as keyboards and / or screens (not shown in the figure).

[0100] The CSP, NSP, and NOP management entities are distinguished in the figure because they are separate functional entities that perform separate steps of the processes according to the invention in the embodiment described herein. However, in the principal embodiment, the invention is implemented only by a first CSP management entity, responsible for providing a communication service, referred to as management entity 100 in [Fig. 1], and a second NOP management entity, responsible for orchestrating a network slice, referred to as device 200 in [Fig. 1]. In this case, communications between the first CSP management entity and the second NOP management entity occur directly, without passing through an NSP entity responsible for providing network slices.It can also be considered that, in this case, the NOP and NSP management entities are merged into a single entity, which performs network slice orchestration and then provides them to entities responsible for providing communication services.

[0101] It can also be considered that the three entities CSP, NSP, NOP form a telecommunications system which implements a process for managing a communication service.

[0102] The hardware resources required to perform the processes according to the invention may be, for example, three separate servers corresponding to the three management entities CSP, NSP, and NOP. In the case of a grouping of the management entities, the grouped management entities may run on the same server. In other embodiments, the hardware resources required to perform the process are obtained from a cloud computing infrastructure.

[0103] The network in which the management functions are hosted is not shown in [Fig.2]. In the example in [Fig.2], the communication service comprises three network slices TRI, TR2, TR3 which are orchestrated by the NOP orchestrator.

[0104] The CSP management entity performs the functions of a Communication Service Provider. In the embodiment shown here, it comprises the following modules: - A DEM module performing, in the example presented here, a request operation to the NOP management entity, here via the entity of NSP management, creation of one or more TRI, TR2, TR3 network segments which will be included in the communication service; - The DEM module also obtains the management function identifiers and corresponds to module 101 represented in [Fig.1]; - A FAB1 module performing, in the example presented here, information completion, the completed information being used to link service functionalities, including management operations, and virtual network functions; - A CAT module which, in the example presented here, displays a catalogue of services provided by the first CSP management entity; - A SOM module which, in the example presented here, performs the transmission to the NOP orchestrator of requests to execute management functions.

[0105] The SOM module actually manages the communication service by requesting the execution of management functions from the NOP orchestrator. The acronym SOM stands for Service Order Management.

[0106] The communication service is described in the catalog displayed by the CAT module. This catalog specifies on which network slice (TR1, TR2, TR3) the service should be executed, as well as the execution properties. The service is activated when a customer who subscribes to the service is provisioned.

[0107] The CSP management entity requests the creation of network slices to create a communication service which it will be able to provision, among other management operations, by executing functions of the TRI, TR2, TR3 network slices. The service can then be sold to an end user (not shown in the figure), with an identity embodied in a SIM (for Subscriber Information Module) or eSIM card provided by the first CSP management entity.

[0108] In some embodiments, the SOM module performs service order management by sending requests to execute management functions to functions included in the TRI, TR2, TR3 slices. This sending of requests to the TRI, TR2, TR3 slices is done via the NOP orchestrator.

[0109] In some embodiments, the request to the NOP orchestrator, here via the NSP management entity, to create one or more TRI, TR2, TR3 network slices, is a request negotiated with the NSP management entity, which will be adjusted according to the needs of the CSP management entity and relayed to the NOP orchestrator after agreement on a network slice proposal made by the NSP management entity in response to the request made by the CSP management entity.

[0110] The NSP management entity performs the functions of a Network Slice Provider. In the embodiment shown here, it comprises the following modules: - A TRS module performing, in the example presented here, the transmission of the request to create network slices between the first CSP management entity and the NOP orchestrator and the transmission of management function identifiers provided by the NOP orchestrator to the first CSP management entity; - A FAB2 module which, in the example presented here, provides information intended for the first management entity CSP and the second management entity NOP.

[0111] In some embodiments of the invention, the relationship between the communication service provider (CSP) and the NOP orchestrator is direct, without an intermediary. In other examples, the network slice provider (NSP) is the same as the NOP orchestrator.

[0112] The NOP management entity performs the functions of network slice orchestration and network operator. In the embodiment shown here, it comprises the following modules: - A PRV module for providing the first CSP management entity with management function identifiers; - The PRV module corresponds to module 201 shown in [Fig.2]; - A FAB3 module, in the example implementation presented here, which provides additional information to the management function identifiers provided by the NOP orchestrator to the first CSP management entity; - An AGW module serving as an intermediary allowing access by the first CSP management entity to the TRI, TR2, TR3 network segments included in the service; - The AGW module corresponds to modules 202 and 203 of [Fig.1], and also includes the storage of associations between management function identifiers and data relating to management functions.

[0113] The AGW module serves as an access gateway to the management functions present in the network slices TRI, TR2, and TR3 created by the NOP orchestrator to constitute the communication service whose creation is the subject of the process. In exemplary embodiments, the AGW module receives requests from the SOM module of the first CSP management entity, the requests designating a management function from among the slices TRI, TR2, and TR3. However, it must be possible to precisely identify where the targeted network function (provided by an OEM) is deployed. This technical information must not be known to the first CSP management entity in order to conceal the actual topology. of the network. The NOP orchestrator can therefore migrate its solutions without the CSP management entity being aware. If the CSP management entity had this information, it could access the NOP directly, creating a security vulnerability, and it would be impacted with every function change. The AGW module can retrieve this information, for example, by understanding or interacting with a slice inventory maintained by the NOP orchestrator of the targeted slice. In implementation examples, the AGW module can perform additional checks on the received request related to properties held in the NOP slice inventory. This slice inventory includes the associations between identifiers and data.

[0114] The three modules FAB1, FAB2, and FAB3, belonging respectively to the communication service provider CSP, the network slice provider NSP, and the orchestrator NOP, the third and second management entities, all have a similar role in enriching, transforming, and aggregating the information provided by the orchestrator NOP to the communication service provider CSP. This information includes, at a minimum, management function identifiers and, more generally, information relating to the network slices TRI, TR2, and TR3 created by the orchestrator NOP. This enrichment consists of data specific to the respective entities CSP, NSP, and NOP, independently of the information specific to the network slices created TRI, TR2, and TR3. In exemplary embodiments, these three modules FAB1, FAB2, and FAB3, with their similar functions, are grouped into a separate management entity FAB, referred to as a factory.In these implementations, the FAB management entity, distributed across the three entities CSP, NSP, and NOP, handles the various data enrichment operations for the network slices created for the communication service, incorporating information specific to each level of service creation. The FAB management entity acts as a data repository for this data, distributed across the different levels of the system. The resulting data from the processing performed by the FAB management entity can also be stored in the pre-existing inventories of the CSP, NSP, and NOP entities for reasons of solution portability and maintenance.In some implementation examples, the FAB management entity can be developed independently of the other CSP, NSP, and NOP entities and can be provided to these entities in order to complement them and standardize the processing of information useful for managing network slices between these different entities.

[0115] The information relating to the TRI, TR2, TR3 slices which is provided by the FAB3 module of the NOP orchestrator in addition to the management function identifiers can be grouped into four categories: Connectivity information. This refers to the definitions that enable users to connect to the service. For example, this includes information that users' SIM cards need to know, and therefore is provided by the CSP management entity to the end users of the created service, so that the SIM cards can interact with the virtual network functions of the slices, such as the UDR (Unified Data Repository). Information related to communication services. This information enables the correct routing of the end user between the different functions of the service components. It describes the subscribed services and the components that support their execution. This information, combined with other network information, allows for the routing of application traffic originating from the terminals. When an end user wishes to access a service (for example, sending an SMS message), the information present on the user's terminal is functional information. The technical information corresponding to the network address of the function must be retrieved by the NOP management entity to allow the end user access to the correct function.This technical information will not necessarily be passed all the way to the end customer; a correspondence between a service identity and the technical information can be created at an intermediate level to allow end customers to avoid having to manipulate the technical information produced by the NOP orchestrator. This information consists of virtual function parameters. Creating a communication service involves setting operating parameters for virtual network functions. These parameters include, for example, throughput, latency, expected packet sizes, or any other parameter useful for defining the network functions. Network slices created or orchestrated by the NOP management entity are composed of functions whose parameters fall within a specific operating range. Information relating to these operating ranges is provided by the FAB3 module. One way to describe this information is through a shared data mechanism. An identifier corresponding to a whole set of parameter values ​​is defined in advance. Rather than retrieving all the parameter value ranges for several thousand functions, the FAB3 module retrieves an identifier that allows the corresponding values ​​to be found, which is very economical in terms of data exchanged. Such a mechanism, known as shared data, implies a standardization (at the 3GPP level) of identifiers and... corresponding values. Such parameter values ​​can then be set by the CSP management entity by performing a management operation which includes calling management functions using the method of the invention. - Roaming information. Information regarding customer routing to communication services is specific to the case of roaming customers. The FAB3 module of the NOP orchestrator retrieves the necessary information for this aspect, enabling roaming customers to access virtual network functions.

[0116] All of this data can be arranged in the form of API calls, allowing entities that need it to retrieve it. The shared data mechanism corresponds to this operation. Calling an API using a shared data parameter defined by the standard allows retrieval of a whole set of data. For roaming information, this standardization does not currently exist, and the FAB3 module adds a proprietary field to carry this identifier value, which allows information to be retrieved.

[0117] This information will be enriched, transformed and / or aggregated by the other FAB2 and FAB1 modules in the following way, in addition to the transmission of management function identifiers.

[0118] The FAB2 module belongs to the NSP management entity responsible for providing network slices and receives information relating to network slices TRI, TR2, TR3 from the FAB3 module of the NOP orchestrator, in addition to the management function identifiers to be transmitted to the CSP communication service provider. This information is transformed by the FAB2 module as follows: The connectivity and communication service information returned by the NOP orchestrator consists of technical data, such as network or function addresses, which allows the end user of the communication service, via their user terminal, to access the various virtual network functions. This technical information is not relevant in this form for a user terminal, which manipulates functional concepts, such as service names, for example, "send SMS". The FAB2 module will perform a join between the technical information returned by the FAB3 module and the functional concepts known to the client terminals. This joined information is sent back to the NOP management entity and will be used by the AGW module, which can then direct requests identified by a functional concept to the correct virtual network function. using the technical information associated with the functional concept. This attached information is also sent to the first CSP management entity, which will use it to call the virtual network functions of the slices forming the created service. Furthermore, the connectivity and communication service information provided by the NOP orchestrator is relevant in a 5G context. However, end users will sometimes find themselves in radio environments that may only allow the use of older networks, such as 2G, 3G, or 4G. In this case, common functions must be used across the different network technologies to enable interoperability. The UDR function is one such example. The FAB2 module will send information back to the NOP orchestrator that links functionalities, outside of 5G, to technical data. The FAB2 module will also send the NOP orchestrator constraints on the functions to be shared between different network technologies within the 5G bands.This information will be used by the AGW module to direct future requests from clients of the created communication service to the appropriate network function, in response to a functional request. - In some implementation examples, information relating to the parameters of the slice functions, as well as roaming information, is transmitted without modification by the NSP management entity to the first CSP management entity. This parameter information, in the case of shared data, is being standardized by 3GPP and therefore does not need to be modified. Roaming information, however, is proprietary and depends on the equipment manufacturers. It cannot be modified, and the CSP management entity must be able to process it, taking into account the variety of possible equipment manufacturers.

[0119] The FAB1 module belongs to the first management entity, CSP. It receives network slice information from the NOP orchestrator, possibly enriched by the intermediate management entity, NSP. The FAB1 module will perform transformations or enrichments specific to the service aspect, under the responsibility of the CSP entity. These transformations are as follows: - The CSP management entity received information from the NOP management entity regarding the operating parameters of the virtual network functions included in the TRI, TR2, and TR3 slices. The information returned by the NOP orchestrator represents possible operating ranges for these parameters. The CSP management entity The service provider (CSP) must define parameter values ​​within these possible operating ranges for the given service it will create and then offer to its customers. For example, a throughput parameter reported by the NOP orchestrator is a maximum value, and the CSP sets a precise value consistent with this maximum. These defined values ​​are used to implement the created service. In some implementation examples, they are displayed in the service catalog produced by the CSP management entity's CAT module. They can also be used in management instructions addressed to network virtual functions via the AGW access module to define the operating values ​​of the network virtual functions included in the created communication service. - The connectivity information received is supplemented by the FAB1 module with elements specific to the actual provision of the service to end customers. These elements concern, for example, SIM card management: is it a physical or virtual card (eSIM)? Does it need to be delivered to the end customer? And any other questions that need to be defined in this regard.

[0120] It should be noted that, for these processes to function, certain values ​​must be fixed in advance to ensure common knowledge between the CSP, NSP, and NOP entities. For example, identifiers corresponding to sets of values, in the case of shared data, must be known in advance, which is made possible by standardization. Other identifiers, such as those related to roaming, still need to be standardized.

[0121] In the embodiment shown here, the CSP management entity responsible for providing a communication service interacts with an NSP management entity responsible for providing one or more network slices and a NOP management entity responsible for creating and orchestrating network slices. In other examples, the CSP management entity interacts only with the NOP orchestrator. In these examples, the CSP communication service provider directly requests the NOP network slice orchestrator to create the TRI, TR2, and TR3 network slices that will constitute the communication service and can then perform management operations using the management function credentials provided by the NOP orchestrator and the ability to access these management functions through the AGW access gateway included in the NOP orchestrator.

[0122] In other embodiments, there will still be only one CSP management entity but several NOP and / or NSP management entities. Indeed, since the purpose of the process is the management of a communication service, this service will only be provided to end users under the responsibility of a single service provider. communication. However, obtaining the TRI, TR2, and TR3 network slices that form the communication service can be done by using separate network slice providers (NSPs) and network slice orchestrators (NOPs). The CSP management entity can solicit several NSPs, which can themselves solicit several NOPs, who can separately provide the network slices that form the communication service and perform management operations through the respective network slice orchestrators.

[0123] In other embodiments, a single NOP orchestrator responds to requests from several CSP communication service providers, possibly via several NSP network slice providers. By providing management function identifiers, the NOP orchestrator enables each CSP communication service provider to perform management operations related to the communication service(s) it provides, through the NOP orchestrator's AGW gateway, even if the specific management function, for example a UDR function, is shared between several slices or services orchestrated by the NOP orchestrator.

[0124] Figure 2 also represents three network slices, TRI, TR2, and TR3. These three network slices are included in the communication service that is created or managed by the execution of the method according to the invention. They are created at the request of the first CSP management entity by the NOP orchestrator in certain embodiments, but they may also pre-exist such a request. The creation of the network slices corresponds to a specific orchestration operation, and the NOP management entity is responsible for orchestrating the network slices in the system represented in Figure 2.Once the management function identifiers are provided to the CSP management entity, management instructions can be sent to them. These instructions will, for example, allow users to populate their respective directories and then enable these users to implement the virtual network functions present in the TRI, TR2, and TR3 slices, and thus use the communication service formed by the slices. The orchestration of the network slices is performed by the NOP management entity, either in response to the network slice creation request made by the first CSP management entity, or it may have been performed beforehand, independently of a specific request. The activation and sending of management instructions to the network slices is then done solely through the AGW module of the NOP management entity.

[0125] The advantage of the process described here is that it can be carried out without relying on proprietary definitions from equipment manufacturers. The technical information retrieved by the NOP orchestrator is enriched and transformed by the various FAB2 and FAB1 modules in order to link it with the specific functional information. to the created service. This information allows the CSP service provider to access the various virtual network functions that make up the service without having to consider these different technical details, via the AGW access module. This then allows the NOP orchestrator, if necessary, to change the equipment manufacturers that provide the different virtual functions. The AGW access module will bridge the gap between the requests, which use functional information, and the new technical information required by the equipment change.

[0126] Fig. 3, meanwhile, presents an example of a sequence of message exchanges between management entities within the framework of an embodiment of the invention.

[0127] In the example presented here, the communication service managed by the implementation of the method according to the invention by the communication service provider (CSP) consists of two network segments, TRI and TR2. This could be, for example, the service described previously, in which a communication service customer can switch from a standard TRI segment to a higher-performance TR2 segment (lower latency, higher bandwidth, etc.) depending on their geographical location (standard segment in general; premium segment when the customer is located at production sites, which allows the use of high-bandwidth video services for real-time communication of production incidents). This switchover is automatic based on the customer's location.

[0128] In this example, the communication service provider (CSP) defines a service class where this distinction between geographic areas is offered. When the CSP offers a communication service to an enterprise customer, it must define the premium geographic area for the sites of interest to its customer. A link must be established between technical data (antenna addresses corresponding to locations of interest to the end customer) and functional data (labels of geographic areas significant to the end customer). Once this link is established, the technical data can change transparently for the communication service customer and end users.Geographic areas must be able to change throughout the life of the communication service, both functionally (the CSP client wishes to add a new geographic area to their premium tier) and technically (the orchestrator wishes to change the antennas covering the premium area).

[0129] Furthermore, certain communication service functions will be shared between the network segments. For example, everything related to client authentication can be performed by the corresponding functions present in the TRI segment and will be used by both virtual network functions of the TRI segment and those of the TR2 segment.

[0130] In the embodiment of the method according to the invention presented here, the method is implemented by a CSP management entity responsible for providing the communication service that will be managed by the implementation of the method, an NSP management entity responsible for providing the TRI, TR2 network slices that will constitute the communication service, and a NOP management entity responsible for orchestrating the TRI, TR2 network slices, including their creation, which is viewed as an initial orchestration operation. In other examples, there is no NSP management entity, and in this case, the relationships between the CSP management entity and the NOP management entity are direct. In still other examples, several NSP management entities and several NOP management entities may submit competing proposals to the CSP management entity for the TRI, TR2 network slices that will form the communication service.

[0131] To return to the example presented here, we consider a CSP management entity, an NSP management entity, and a NOP management entity. The CSP management entity, responsible for providing the communication service, sends a request to the NSP management entity, responsible for providing network slices, to create two network slices, TRI and TR2. This creation request may be accompanied by information relating to the quality of service constraints requested by the CSP management entity. These constraints are what will differentiate between the TRI slice, which provides a standard service, and the TR2 slice, which provides a premium service. These constraints are also provided with geographic information such as GPS coordinates and area labels for the areas that must be covered by the premium slice and those covered by the standard slice.

[0132] The NSP management entity transmits these requests to the NOP management entity for the creation of network slices TRI and TR2. The NOP management entity performs a specific orchestration operation that creates the network slices TRI and TR2. Such an orchestration operation is actually a series of operations that include reserving hardware, computing, memory, or network resources; launching virtual network functions; and creating communication links between virtual functions. The orchestration operations in question depend on the equipment manufacturers that provide the hardware resources and virtual network functions that make up the network slices.

[0133] Once the orchestration operations corresponding to the creation of the network slices have been carried out, information useful for accessing the TRI, TR2 network slices will be provided by the NOP management entity and in particular identifiers of the management functions which will then allow management operations to be carried out.

[0134] In the embodiment shown here, this information is enriched by information specific to the NOP management entity. For example, certain parameters The quality of service information guaranteed by the NOP management entity can only be provided by the NOP management entity, which has a complete view of the architecture of the network slices created (TRI, TR2). The NOP management entity can also retrieve information related to access to virtual network functions, but this information is independent of the various equipment manufacturers that provide them. This data processing and enrichment is performed by the FAB module within the NOP management entity before the enriched and completed information is sent to the NSP management entity.

[0135] In this embodiment, the NSP management entity will also enrich the received information using its own FAB module. Some of this enriched information will be transmitted to the CSP management entity. This will include, for example, access information for the various virtual network functions, but using access points defined by the NSP management entity. In this way, the NSP entity is indeed the provider of the TRI and TR2 network slices. The enriched information can also include quality of service parameters refined by the NSP management entity.

[0136] Another part of the enriched information is returned to the NOP management entity. This is information for which information known at the NSP management entity level is necessary for the NOP management entity to control the TRI, TR2 network segments.

[0137] In this embodiment, the information returned to the CSP management entity is also enriched by the FAB module present in the CSP management entity. This enrichment can relate to the link between management operations and identifiers corresponding to management functions present in the TRI and TR2 tiers. The enrichment can also correspond to quality of service parameters that the CSP management entity can determine from the information returned by the NOP and NSP management entities, supplemented by its own information. For example, the NOP orchestrator may have provided a maximum throughput value when an end customer is connected to the premium tier, and the CSP service provider will precisely set this throughput, respecting the maximum value returned by the NOP orchestrator.The value set by the CSP service provider will be displayed in the service catalogue produced by the CAT module and will also be transmitted to the management functions to be set in concrete terms.

[0138] The enriched information will be used by the CSP entity, in the embodiment presented here, to display a CAT catalog of offered services. Indeed, this information, such as quality of service parameters and access points to service functionalities, is useful to present in a catalog.

[0139] The enriched information is also provided to the SOM module of the CSP management entity. The SOM module enables the management of the service created by interacting with the network management functions of the TRI and TR2 slices via the AGW module of the NOP management entity.

[0140] To return to the example of a service with differentiated quality of service depending on the geographic area, the CSP management entity will provide the NSP with a service creation request specifying the characteristics of the differentiated geographic areas, expressed, for example, as GPS coordinates. The CSP will then provide identifiers corresponding to these areas, which will be used in future interactions. The NSP then requests the NOP orchestrator to create the two service segments TRI and TR2 with differentiated quality of service based on geographic criteria. The NOP orchestrator will perform this creation, and the NOP orchestrator's FAB3 factory will perform the matching operations between the geographic identifiers transmitted by the CSP and the corresponding technical data.The FAB3 factory will specifically build management function identifiers that will then allow for the management of geographic zones, using the identifiers provided by the CSP, without needing to know the technical data differentiating the two geographic zones. The management function identifiers are sent by the NOP to the NSP, which can then supplement them with its own information, such as throughput constraints specific to the two distinct slices. The NSP is the one that knows these constraints since it is the one conducting commercial negotiations with the CSP. This information, correlated by the NSP's FAB2 factory with the previously created information, will be sent to the NOP orchestrator. In the AGW module, these constraints can be used to control requests for the execution of management functions sent by the CSP to the NOP orchestrator.

[0141] Finally, it should be noted here that, in this text, the term "module" can refer to a software component, a hardware component, or a set of hardware and software components. A software component itself corresponds to one or more computer programs or subprograms, or more generally to any element of a program capable of implementing a function or set of functions as described for the modules concerned. Similarly, a hardware component corresponds to any element of a hardware assembly capable of implementing a function or set of functions for the module concerned (integrated circuit, smart card, memory card, etc.).

Claims

Demands

1. Device (200) belonging to a network (NET), implementing a method for making available management functions of a communication service, said management functions (F) being hosted in the network (NET) and being capable of being executed by a management entity (100), characterized in that the device (200) stores associations between identifiers (ID) of management functions (F) and data (DAT(F)), respectively, relating to the functions (F) and characterized in that it comprises the following modules: - Module (201) for providing the management entity (100) with an identifier (ID) of a management function (F); - Module (202) for receiving from the management entity (100) an execution request (COM(ID)) of a management function (F) including an identifier (ID) of said function (F); - Module (203) for executing the received query by calling the management function (F) using the data (DAT(F)) associated with the identifier (ID) included in the query.

Images