Method for managing a network segment whose functions are provided by several suppliers

Abstract

Method for managing a network slice whose functions are rendered by several providers. The invention relates to a method for managing a network slice (TR) by a management entity (CSP) responsible for providing communication services, the network slice (TR) comprising virtual network functions (VNF0, VNF, VNF', VNF'', VNF''') rendered by several providers and managed through management elements (EM), the functions being characterized by access points (SAPs) comprising information, characterized in that it comprises the following steps: Obtaining (OBT) access points (SAPs) characterizing the virtual network functions; Creating (CRT) a communication link (NNI) between the virtual network functions using information contained in the access points (SAPs);Transmit (SND) management instructions to virtual network functions through an interface (UNI) linking the management entity (CSP) to the management elements (EM), using information contained in the access points (SAP). Figure 1;

Description

Title of the invention: Method for managing a network slice whose functions are provided by several providers Technical field

[0001] The technical field is that of telecommunications.

[0002] More specifically, the invention relates to a method for managing a network slice whose virtual network functions are provided by several providers.

[0003] 5G networks (abbreviated for fifth generation mobile telecommunications networks) or 5GSA (acronym for 5G StandAlone) introduce the notion of network slice. This notion is based on the virtualization of network functions. A virtual network function (VNF or VNFs in the plural) is a computer application that implements a function expected of a computer or telecommunications network, such a function being for example a directory service, routing, or other.In a 5G network, unlike previous generations of telecommunications networks, all network functions are virtualized, meaning that the functions necessary for the operation of the network are rendered by computer programs running in virtual machines or similar technologies such as containers. This architectural principle for building new and future telecommunications networks is embodied in a framework standardized by ETSI (European Telecommunications Standard Institute), a framework called NFV (Network Function Virtualization), with ETSI defining its implementation in its ISG NFV (Industry Specification Group - Network Function Virtualization) working group.This is in contrast to previous generation telecommunications networks in which, in general, network functions were attached to dedicated hardware devices, such as PBXs, routers, base stations. In a 5G network, a set of hardware resources is available at several locations needed to perform network functions, but no function is a priori attached to a given piece of hardware.

[0004] In recent developments, network functions are increasingly contained in containers and are therefore no longer, in the true sense, 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 has not no matter, and we will only talk about virtual network functions, taking into account that these network functions can in fact also be containerized network functions.

[0005] A given physical 5G mobile network will therefore be able to partition its resources and deploy several instances of virtual network functions to build several separate network slices on the same infrastructure. These different slices will be able to have distinct quality of service parameters and correspond to different commercial offers. In this way, a given physical infrastructure is exploited to the best advantage.

[0006] The virtualization of network functions in a 5G network makes it possible to implement the notion of network slice by distributing network functions over hardware resources that have been previously selected and reserved. The set of operations that make it possible to deploy a network slice is referred to as orchestration.Orchestration is performed by an entity called the orchestrator that will implement the selection and reservation of hardware resources; the launch and shutdown of instances of virtual network functions (VNFs) 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 (SAP, acronym for Service Access Point) to manage the VNFs, for example to stop them, restart them, change their relationships, duplicate them or any other management operation, and also to connect the VNFs together and thus address them the data they must process during their operation and to recover the processed data. In the 5G standard, the orchestrator is attached to the mobile network operator whose resources are used to build several network slices.The management of the network slice itself is provided by an entity called BSS (acronym for Business Support System) which can create, modify, delete, activate or deactivate virtual network functions under the responsibility of the orchestrator.

[0007] In the 5G standard, a network slice is also defined in relation to an access network that allows a user terminal (in English, User Equipment, abbreviated as UE) physical access to communication with the network slice. This access network is generally a public land mobile network (in English, Public Land Mobile Network, abbreviated as PLMN) as is the case in mobile telecommunications networks of the fifth generation and beyond.

[0008] However, conceptually, the physical access network to the network slice may also be a fixed access network or any other means providing physical access to the virtualized network functions of the network slice. The concepts of virtualization network functions, and network slice, which originally appeared in the context of mobile telecommunications networks, can be applied in any type of network, including those with fixed access. Moreover, since a network slice is defined by a set of virtual network functions, there is no requirement that all virtual network functions be provided by a single mobile network operator and therefore nothing prevents different network functions from being provided by different providers.

[0009] The 3GPP TS 23.501 standard (Security architecture and procedures for 5G System) specifies these concepts and provides more details.

[0010] The invention relates to the management of a network slice in a telecommunications network, the network slice having to make several providers collaborate to make the different virtualized network functions of the slice. State of the art

[0011] The introduction of the notions of network slice and virtual network functions makes it possible to offer a given customer the possibility of having different providers for the different functions of a network, these different functions forming a single network slice used by the given customer. Two examples illustrate the interest of such a possibility.

[0012] A first example is a network slice dedicated to a road transport company. The company's trucks have a terminal that can send data in real time to the company's information system through a dedicated network slice. The standard access used by the slice may be a mobile telecommunications network. However, the trucks in question may cross white zones not covered by the provider of the mobile network used for access. It is then interesting to be able to switch to access via a satellite telecommunications network, which has universal coverage. But the road transport company does not want this access mode to be widespread, because the speed is lower via satellite than via the mobile network.It is therefore worth building a network slice dedicated to the road transport company, in which the terminals can switch between two modes of network access: access by mobile telephone in general, and access by satellite telecommunications in certain cases. The network slice in question therefore needs to involve two separate providers for the access functions, and perhaps other providers for the core network functions.

[0013] A second example is a network slice dedicated to the temporary organization of a film festival. A film festival organizer may wish to offer its participants, in addition to screenings in the festival halls, access to all the films presented through a mobile telecommunications network. available at the festival venue and more broadly in the city where festival-goers reside for the duration of the festival. A 5G mobile telecommunications network operator can provide such access, with increased throughput in the city in question to distribute the videos. But the organizer wants caching functions to ensure that the distribution of the films will be done without any latency, and wants special security for its caching functions to prevent film piracy. The mobile network operator does not have the resources to provide these functions and does not want to deploy them for the duration of the festival only.The film festival organizer may then wish to have a network slice where the mobile access functions are provided by a traditional 5G network operator, but where the cache management, film distribution, and access security functions are provided by a dedicated provider.

[0014] There is therefore an interest in being able to create network slices by combining functions offered by different providers. Such a network slice must also be able to be managed in a unified manner even if the different network functions are provided by different providers. There is also an interest in being able to create new slices on demand combining functions offered by different providers or in being able to change provider for one or more virtual network functions of an already existing slice. Indeed, this possibility allows the requester of a network slice to be able to play off competition between several providers in order to gain efficiency and price.

[0015] The management of a network slice will consist of sending management instructions to the different virtual network functions that form the slice. These instructions are addressed from the entity in charge of management, or more generally the entity that owns the network slice, to the virtual network functions through an interface called UNI (acronym for User-Network Interface). The virtual network functions receive the management instructions through application interfaces commonly called management elements, or EM (acronym for Element Manager). The EM management elements are therefore accessed through the UNI interface. All of the EM interfaces, as well as the management applications for one or more virtual network functions VNF, form a management system called EMS (acronym for Element Management System).

[0016] A distinction must be made between the data management instructions exchanged between network functions. This data is the data exchanged during the operation of a communications network, for example the messages sent by network users. Virtual network functions exchange data between themselves during their operation via interfaces called NNI (acronym for Network-Network Interface). The relationship between separate networks is done through exchange points, called peering points in English.

[0017] The GSMA NG 116 standard describes the attributes exchanged between different entities to characterize a network slice. Knowledge and exchange of these attributes is essential for creating a slice and then managing it. The GSMA NG 116 standard, in particular, describes a generic network slice model, called GST (acronym for Generic network Slice Template). The GST includes optional or mandatory attributes that allow the expected functionalities and performances of a network slice to be described, but without detailing the network functions that are instantiated in a given network slice.

[0018] The entities that interact when creating a network slice are as follows: • A Communication Service Customer, or CSC. A CSC can be a user with a UE terminal, but also a company that needs a corporate network, or any other entity that needs communication services. • A communication service provider, or CSP (acronym for Communication Service Provider). A CSP is the entity that sells the CSC the communication services it needs. To do this, it will offer its CSC client an offer containing products that correspond to the services sold in a given offer. These products run in a network slice adapted to their needs. The CSP must therefore have access to the different virtual functions that make up the network slice. The CSP defines the characteristics of the network slice that it needs to provide the communication service to its customers. The CSP is therefore the owner of the network slice, and, as the owner of the network slice, it must be able to manage it. • A Network Slice Provider, or NSP. An NSP is the entity that provides the CSP with a network slice according to its requests. The NSP must therefore provide the CSP with SAP access points to the various virtualized network functions (VNFs) that make up the network slice it provides to the CSP. • A mobile network operator, or NOP (acronym for Network OPerator). The network slice is defined in relation to a public land mobile network (PLMN). It is the NOP mobile network operator who will define the access means that will allow user terminals UE to access the network slice.

[0019] These different roles can be fulfilled by separate actors or by a single entity. For example, a CSP communication service provider may also be a network slice provider NSP, and the CSP will then provide the CSC communication service customer with a network slice provided by it to meet the CSC customer's communication service needs. Similarly, a network slice provider NSP may also be a mobile network operator NOP, and the mobile network slice it will provide will simply be a network slice in relation to the PLMN mobile network which is operated by itself as a mobile network operator NOP.

[0020] The GSMA NG 116 standard describes precisely the interactions between the network slice provider NSP and the network operator NOP. As already explained, the information exchanged between the NSP and the NOP, described in the GSMA NG 116 standard, is limited to functional or quality of service parameters. The current version of the standard provides that a CSP requests an NSP to provide it with a network slice. The GSMA NG 116 standard then expresses in technical protocol elements, to be exchanged between the NSP and the NOP, the functional and quality of service elements defined during the exchange between the CSP and the NSP, this exchange not being defined in NG 116.

[0021] Furthermore, the GSMA NG 116 standard does not provide that a given network slice can be made up of virtual network functions belonging to separate providers. The different roles CSP, NSP and NOP can be confused but cannot be fulfilled by separate entities according to the GSMA NG116 standard.

[0022] To summarize, the exchanges provided by current solutions, for example those defined in the GSMA NG 116 standard, between different entities to result in the creation of a network slice are limited to functional or quality of service requests between the NSP and the NOP. In this context, the virtual network functions are predefined and are provided by a single provider.

[0023] The MEF (formerly the Metro Ethernet Forum) standardization forum also seeks to describe the concepts of network slice and network slice provisioning in the MEF 84 standard entitled Subscriber Network Slice Service and Attributes. It is stated in the MEF 84 standard that a service provider can provide several distinct network slices from a given network. It is also stated that a network slice can be composed of several network slices. In this case, the virtual network functions of the composite slice are rendered by several distinct providers. But the distribution of the different network functions of the composite slice between the different providers is then defined in advance and cannot be changed.The MEF 84 standard therefore allows for a network slice in which virtual network functions are provided by different providers, but in a predefined manner and which cannot evolve.

[0024] This situation has a clear disadvantage.

[0025] In the current situation of standards relating to 5G mobile telecommunications networks, the creation and management of network slices is understood as necessarily starting from a mobile network operator who will reserve resources in its network and make virtual functions available. The creation and management of network slices is done according to a vertical interaction between the NOP, the NSP and the CSP. The parameters exchanged do not allow specifying the virtual network functions that constitute a slice or their respective providers, but only global quality of service parameters. The MEF 84 standard allows having a slice composed of functions provided by several providers but in a predefined manner once and for all, without any possible evolution of the structure of the network slice in question.The distribution of functions provided by different providers is defined once and for all and cannot be negotiated between the different participating entities. This does not allow any dynamic creation of a new network slice whose functions are provided by different providers. The responsibilities between different entities for implementing the management of a network slice whose functions are provided by different providers are not clarified and there is no way to dynamically perform the creation and management of a network slice whose functions are provided by different providers.

[0026] The invention improves the situation. Statement of the invention

[0027] According to a first functional aspect, the invention relates to a method for managing a network slice by a management entity responsible for providing communication services, called the first management entity, the network slice comprising virtual network functions provided by several providers and managed through respective management elements, the functions being characterized by access points comprising information relating to the virtual network functions, characterized in that it comprises the following steps carried out by the first management entity: • Obtaining access points characterizing the virtual network functions provided by several providers; • Create a communication link between virtual network functions using information contained in the obtained access points; • Transmitting management instructions to the virtual network functions through an interface connecting the first management entity to the management elements of the virtual network functions, said interface using the information included in the obtained access points.

[0028] Thanks to the invention, in particular thanks to the communication link created between the virtual network functions, it is possible to dynamically create network slices formed from virtual functions provided by different providers. To do this, an entity responsible for providing communication services will first obtain access points characterizing the virtual network functions that will constitute the network slice. An access point comprises a set of information allowing communication with a virtual network function, for example a network address and data such as passwords, cryptographic keys or programming interface diagrams. The virtual network functions are provided by different providers, but are used by a communication service provider to offer a network slice to its customers.Obtaining access points characterizing the functions by the communication service provider then allows it to create a communication link between the virtual network functions. The access points make it possible to know the network addresses of the instances of the different virtual network functions and the password-type data that allows network links to be attached to the virtual network functions. In addition to the communication link between the virtual network functions, there is also an interface used for managing the slice. The communication link between the virtual network functions is used for the operation of the network slice itself and will carry the data exchanged between virtual network functions.Once the communication link and the management interface are deployed, the communication service provider can control the network slice formed by the virtual network functions by sending management instructions to the virtual network functions. Such management instructions include the instructions for launching the virtual network functions. The management method is therefore also a method for creating a network slice, this creation dynamically involving several providers of virtual network functions. Once the access points characterizing the functions are obtained by the communication service provider, it can connect the different functions together, then launch them, which is equivalent to creating the network slice.Sending other management instructions will allow the slice to be managed, for example by adding clients of the communication service as clients of the different functions. The clients of the communication service will then use the different virtual network functions and will be able to communicate thanks to the links deployed between them. The method also makes it possible to dynamically modify a slice, by obtaining new access points characterizing new virtual network functions which can replace old functions. Thanks to the invention, there is no need to define in advance the structure that the network slice will take. The creation and management of the network slice are therefore made . dynamic, and are carried out under the control of the communications service provider who owns the dynamically created network slice.

[0029] It may be noted that the operation of transmitting management instructions to management elements can be carried out while the communication link carrying the traffic between functions is not completely created, provided that the interface between the first management entity and the management elements is sufficiently defined, thanks to the access points obtained, to allow the sending of management instructions.

[0030] According to one embodiment, the first management entity having direct access to a first network, obtaining the access points comprises determining virtual network functions hosted in said first network directly accessible by the first management entity and obtaining the access points of these virtual network functions.

[0031] This mode allows a management entity responsible for providing a communication service, called the first management entity, to construct a network slice by combining virtual functions provided by several providers. But in particular, the first management entity may have certain virtual network functions. This embodiment allows the first management entity to identify the virtual functions present in the first network, which are directly accessible to it. These functions may be directly used by the first management entity without having to deploy a specific interface with another network.

[0032] According to another embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, obtaining the access points comprises a transmission by the first management entity to a management entity responsible for providing network slices, called the second management entity, having direct access to a second network, of a first request for access points characterizing virtual network functions and reception of a proposal for access points characterizing virtual network functions hosted in the network directly accessible by the second management entity, called the first proposal.

[0033] Thanks to this embodiment, the first management entity is not limited to using virtual functions located in the network which is directly accessible to it to construct a network slice. The first management entity requests a second management entity, in charge of providing network slices. Simply, the request transmitted by the first management entity to the second does not consist of a request for an already defined network slice, fixed once and for all, but in a request for access points characterizing virtual network functions, that is to say a request for the information, contained in the access points, which will make it possible to connect the virtual network functions together and to send them management instructions. The second management entity, in this embodiment, responds by proposing a set of access points characterizing virtual functions located in the network directly accessible to the second management entity. We recall that the access points include the information that will then allow the first management entity to manipulate the virtual network functions using the information included in the access points. Thanks to this mode, the first management entity will therefore be able to construct a network slice including virtual functions provided by a second management entity.

[0034] According to another embodiment, which may be implemented cumulatively with the preceding embodiments, the creation of a communication link between the virtual network functions, called first functions, hosted in the first network and the virtual network functions, called second functions, hosted in the second network, comprises the creation of an exchange point between the first network and the second network.

[0035] Thanks to this embodiment, the creation of the network slice takes into account the fact that the virtual network functions are provided by different providers and, in particular, may be hosted in at least two separate networks. However, significant telecom traffic may pass between the different virtual network functions and therefore may have to pass from one network to another. This situation makes it necessary to create an exchange point (peering point in English) to carry this significant traffic and ensure load balancing between the networks or appropriate compensation.

[0036] According to an embodiment, which may be implemented alternatively or cumulatively with the preceding modes, the first proposal of access points is completed by the second management entity with access points, called complementary access points, characterizing virtual network functions, called third functions, said complementary access points being proposed by a third management entity, having direct access to a third network, said third functions being hosted in said third network, and, in addition, the method comprises the creation of an exchange point between the second and the third network and a communication link with the third virtual network functions as well as an interface with the management elements of the third virtual network functions so as to avoid a direct link between the first network and the third network.

[0037] According to one embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, obtaining the access points comprises the following additional steps: • a sending, by the second management entity to a third management entity responsible for providing network slices, having direct access to a third network, of a request for access points characterizing virtual network functions, called the second request; • a reception by the second management entity of a proposal, called second proposal, of access points characterizing virtual network functions, called third functions, hosted in the third network directly accessible by the third management entity;

[0038] and, furthermore, : • the first proposal for access points includes access points from the second proposal; • creating a communication link with the third virtual network functions hosted in the third network includes deploying an exchange point between the third network and the second network in order to avoid a direct link between the first network and the third network; • the interface with the management elements of the third virtual network functions, hosted in the third network, comprises a part between the first management entity and an element hosted in the second network as well as another part between this element and elements of the third network in order to avoid a direct link between the first management entity and the third virtual network functions hosted in the third network.

[0039] Thanks to these embodiments, the invention makes it possible to provide a possibility of delegation from one supplier to another to provide the virtual network functions which will form the network slice. The second management entity, in charge of providing network slices, and therefore functions forming these slices, will request a third management entity, also in charge of providing network slices, to request access points characterizing virtual network functions. The first proposal, made by the second management entity to the first, will therefore comprise elements of the second proposal, made by the third management entity to the second entity. In these embodiments, the second management entity is placed "in cut" between the first management entity and the third management entity.The deployments of the communication link and the interface to the management elements of the third virtual network functions are carried out in such a way as to avoid visibility from the first management entity to the third network. In this way, in the situation given by these embodiments, the first management entity must only communicate with the second management entity but still has a network slice comprising virtual network functions offered by the third management entity.

[0040] According to an embodiment, which may be implemented cumulatively with the previous embodiment, the sending of a second request for access points to virtual network functions is done after the reception by the first management entity of a first proposal for access points to virtual network functions and the sending by the first management entity to the second management entity of information relating to the quality of the first proposal.

[0041] Thanks to this embodiment, the first management entity, responsible for providing communication services, can qualify the quality of a proposal made to it by a second management entity, responsible for providing a network slice and therefore access points on virtual network functions. The qualification made by the first management entity can include the refusal of certain functions (and therefore of their respective access points proposed in response to the first request), which will lead the second management entity to seek to improve its offer of virtual network functions. For this, the second management entity sends a second request for access points to a third management entity.The virtual network functions proposed by the third management entity will then be integrated into the proposal made by the second management entity to the first management entity, but according to a delegated mode already seen, in which the first management entity will not have direct visibility on the functions proposed by the third management entity, the second management entity being placed between the first and the third.

[0042] According to one embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, obtaining access points comprises, after receiving a first proposal, the following additional steps: • sending, by the first management entity to a fourth management entity, responsible for providing network slices, having direct access to a fourth network, a third request for access points to virtual network functions; • the receipt by the first management entity of a third proposal for access points to virtual network functions hosted in the fourth network directly accessible by the fourth management entity;

[0043] and, further, creating a communication link with the virtual network functions hosted in the fourth network comprises deploying an exchange point between the first network and the fourth network.

[0044] Thanks to this embodiment, the management entity in charge of providing communication services has another way of completing an unsatisfactory proposal of virtual network functions. After having received a proposal of access points from the second management entity, the first management entity will directly request a fourth management entity in charge of providing network slices, and therefore access points to virtual network functions. The creation of a communication link to these virtual network functions will then be done directly, and not in a delegated manner, by having another management entity in cut-off, but will have to include an exchange point in order to carry the traffic of data between the first and fourth networks. No specific constraints exist in this case on the interface to the management elements between the first management entity and the fourth network. This interface can in particular use direct visibility between the first and fourth networks.

[0045] According to one embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, the requests for access points to virtual network functions comprise information relating to the expected functionalities of the virtual network functions attached to the requested access points and quality of service parameters.

[0046] Thanks to this embodiment, the first management entity, in charge of providing communication services, specifies the requests that it makes to the different management entities in charge of providing network slices and virtual network functions. The requests are specified with information relating to the expected functionalities and quality of service parameters. This information makes it possible to define a service request precisely, by specifying the expected functions and qualities of service. Other elements can be added such as traffic forecasts, as well as proposed purchase prices.

[0047] According to one embodiment, which may be implemented cumulatively with the previous embodiment, the proposals for access points to virtual network functions include information relating to the guaranteed functionalities of the virtual network functions attached to the proposed access points and quality of service parameters.

[0048] Symmetrically to the previous mode, the proposals made by the management entities responsible for providing network slices in response to requests from the management entity responsible for providing communication services will include indications relating to the functionalities that the proposed virtual network functions will fulfill as well as the quality of service parameters that the entities responsible for providing network slices will guarantee. These elements present in the proposals made in response to requests for access points will allow the management entity responsible for providing communication systems to judge the quality of the proposals made to it in response to its requests. Other information elements may be present, for example relating to the expected traffic or the proposed price.

[0049] According to one embodiment, which may be implemented alternatively or cumulatively with the preceding embodiments, one or more of the virtual network functions are containerized network functions.

[0050] In the presentation made so far, only virtual network functions have been mentioned. The invention can equally well be applied to network functions containerized. The information contained in the access points will then be adapted to container manipulation to enable the creation and management of a network slice comprising containerized network functions.

[0051] According to a second functional aspect, the invention relates to a method for providing access points to virtual network functions included in a network slice comprising the following steps executed by a second management entity responsible for providing network slices, having direct access to a second network: • Receipt from a first management entity responsible for providing communications services of a first request for access points to virtual network functions; • Sending to the first management entity a first proposal for access points to virtual network functions hosted in the second network directly accessible by the second management entity.

[0052] Thanks to this aspect, operations symmetrical to those already presented are defined. A management entity in charge of providing network slices will be able to provide access points to virtual network functions. This provision is made in response to a request for access points to virtual network functions. This provision of access points will allow a management entity in charge of providing communication services to manage a network slice formed of virtual network functions provided by different providers by accessing the network functions thanks to the access points provided.

[0053] According to an embodiment of this second functional aspect, which may be implemented alternatively or cumulatively with the previous mode, the first management entity has direct access to a first network and the method comprises the deployment of an exchange point between the first network and the second network in order to allow the deployment of a communication link with the virtual network functions hosted in the second network.

[0054] Thanks to this embodiment, the connection between the different networks where the virtual network functions are hosted is taken into account. The connection between the first network, of the management entity responsible for providing communication services, and the second network, of the management entity responsible for providing network slices, is carried out with an exchange point. The use of an exchange point makes it possible to take into account the significant traffic due to network communications between the virtual network functions hosted in the two separate networks.

[0055] According to one embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, the first proposal of access points is completed by the second management entity with access points, called access points complementary, characterizing virtual network functions, called third functions, said complementary access points being proposed by a third management entity, having direct access to a third network, said third functions being hosted in said third network, and in that the method further comprises the creation of an exchange point between the second and the third network and a communication link with the third virtual network functions as well as an interface with the management elements of the third virtual network functions so as to avoid a direct link between the first network and the third network.

[0056] According to one embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, the method comprises, after receiving from the first management entity a first request for access points to virtual network functions, the following steps: • the sending by the second management entity to a third management entity responsible for providing network slices, having direct access to a third network, of a second request for access points to virtual network functions; • the receipt by the second management entity of a second proposal for access points to virtual network functions hosted in the third network directly accessible by the third management entity;

[0057] and, furthermore, : • the first proposal for access points includes access points from the second proposal; • the method comprises creating an exchange point between the third network and the second network and a communication link to the virtual network functions hosted in the third network using the exchange point in order to avoid a direct link between the first network and the third network; • the interface with the management elements of the virtual network functions hosted in the third network, comprises a part between the first management entity and an element hosted in the second network as well as another part between this element and elements of the third network in order to avoid a direct link between the first management entity and the third virtual network functions hosted in the third network.

[0058] Thanks to these embodiments, a management entity responsible for providing network slices, called the second management entity, can rely on another management entity, also responsible for providing network slices, called the third management entity, to provide a first management entity responsible for providing communication services with access points to virtual network functions. This provision by delegation requires that the management entity responsible for providing communication services does not have a direct link with the third management entity. The second management entity is indeed placed in a cut-off, which has an impact on the creation of a communication link between the virtual network functions as well as on the structure of the interface to the management elements of the virtual network functions hosted in the third network.

[0059] According to one embodiment, which may be implemented cumulatively with the previous embodiment, the sending of a second request for access points to virtual network functions is done after the sending to the first management entity of a first proposal for access points to virtual network functions and the reception by the second management entity of information relating to the quality of the first proposal.

[0060] In this embodiment, the provision of access points by delegation to virtual network functions is done after the first management entity, in charge of providing communication services, has qualified the first proposal of access points. In this way, if the first management entity qualifies the first proposal made by the second management entity as unsatisfactory, the latter will be able to improve its proposal thanks to access points requested from the third management entity.

[0061] According to one embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, the requests for access points to virtual network functions include information relating to the expected functionalities of the virtual network functions attached to the requested access points and quality of service parameters.

[0062] According to one embodiment, which may be implemented alternatively or cumulatively with the previous embodiment, the proposals for access points to virtual network functions include information relating to the guaranteed functionalities of the virtual network functions attached to the proposed access points and quality of service parameters.

[0063] In order to qualify the requests and proposals for access points, these embodiments integrate information relating to the requested and guaranteed functionalities as well as to the expected and proposed quality of service. This information makes it possible to construct rich exchanges between the management entity responsible for providing communication services, which requests access points to virtual network functions, and the management entity(ies) responsible for providing network slices and more particularly access points to virtual network functions. Other information may also be present such as requested or proposed prices, as well as forecasts of expected traffic or any other relevant information to describe a request or proposal for access points. to virtual network functions.

[0064] According to a first material aspect, the invention relates to a management entity responsible for providing communication services, called the first management entity, having direct access to a network, called the first network, said first entity implementing a method for managing a network slice comprising virtual network functions, the virtual network functions being managed through management elements, and comprising the following modules: a module for obtaining access points on virtual network functions; a module for creating a communication link between the virtual network functions, said link using information contained in the obtained access points; a module for transmitting management instructions to virtual network functions through an interface connecting the first management entity to the management elements of the virtual network functions, said interface using information contained in the access points obtained.

[0065] According to a second material aspect, the invention relates to a management entity responsible for providing network slices, called the second management entity, having direct access to a network, called the second network, the entity implementing a method for providing access points to virtual network functions included in a network slice, and comprising the following modules: a receiving module from a first management entity responsible for providing communications services for a request for access points to virtual network functions; a module for sending to the first management entity a proposal for access points to virtual network functions hosted in the second network directly accessible by the second management entity.

[0066] According to another material aspect, the invention relates to a computer program capable of being implemented by a management entity responsible for providing communication services, the program comprising code instructions which, when executed by a processor, performs the steps of the method for managing a network slice defined above.

[0067] According to another material aspect, the invention relates to a computer program capable of being implemented by a management entity responsible for providing network slices, the program comprising code instructions which, when executed by a processor, performs the steps of the method for providing access points to virtual network functions defined above.

[0068] Finally, according to another material aspect, the invention relates to data carriers on which are recorded computer programs comprising sequences of instructions for implementing the methods of managing a network slice and providing access points to virtual network functions defined above.

[0069] The data carriers may be any entity or device capable of storing the programs. For example, the carriers may comprise 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 disk. Furthermore, the carriers may be transmissible media such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The programs according to the invention may in particular be downloaded from a network such as the Internet. Alternatively, the information carrier may 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 method in question. Brief description of the figures

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

[0071] [Fig.l] represents a first management entity, in charge of providing communication services, as well as three other management entities, in charge of providing network slices, as well as a network slice, managed by the first management entity, comprising virtual network functions provided by the different management entities.

[0072] [Fig 2] illustrates an example of message exchange between different management entities within the framework of an embodiment of the invention.

[0073] [Fig 3] illustrates another example of message exchange between different management entities within the framework of another embodiment of the invention.

[0074] [Fig 4] illustrates a third example of message exchange between different management entities within the framework of another embodiment of the invention. Detailed description

[0075] [Fig.l] represents a computer system including a first management entity CSP in charge of providing communication services and a second management entity NSP1 in charge of providing network slices. Two other management entities NSP2 and NSP3 in charge of providing network slices are also represented.

[0076] The management entities CSP, NSP1, NSP2, NSP3 communicate with each other via a communication link using, for example, the Internet network, or any other suitable means. This link can use a public network such as the Internet or links private networks, including Virtual Private Networks (VPNs). The physical medium of this communication link can be a wired or wireless connection or a communication of different access technologies. This communication link is not shown in [Fig.l].

[0077] The first CSP management entity has the hardware architecture of a conventional computer. It includes in particular a processor, one or more RAM-type random access memories and one or more read-only memories such as a Flash or ROM memory (not shown in the figure) as well as input-output devices such as keyboards and / or screens (not shown in the figure). The CSP management entity can run in a hardware server accessible via a communication network such as the Internet, or any other network such as for example a dedicated communication network, or run in a cloud computing architecture. The CSP management entity can also have a distributed architecture and run thanks to the cooperation of several modules distributed over different hardware servers. This is particularly the case when the CSP management entity runs in a cloud computing architecture..

[0078] The second management entity NSP1 has a hardware architecture similar to the management entity CSP, as well as the other management entities NSP2 and NSP3.

[0079] The first CSP management entity, in charge of providing communication services, comprises a module 101 for obtaining OBT SAP access points on the virtual network functions VNF0, VNF, VNF', VNF”, VNF”'. The virtual network functions VNF0, VNF, VNF', VNF”, VNF”' may be virtual network functions themselves or containerized network functions, without loss of generality.

[0080] The first CSP management entity, in charge of providing communication services, comprises a module 102 for creating CRT an NNI communication link between the virtual network functions VNF0, VNF, VNF', VNF”, VNF”', said NNI link using information contained in the SAP access points obtained OBT.

[0081] The first management entity CSP, in charge of providing communication services, comprises a module 103 for transmitting SND management instructions to virtual network functions VNF0, VNF, VNF', VNF”, VNF”' through a UNI interface connecting the first management entity CSP to the management elements EM of the virtual network functions VNF0, VNF, VNF', VNF”, VNF”', said UNI interface using information contained in the SAP access points obtained OBT.

[0082] The second management entity NSP1, in charge of providing network slices, comprises a module 201 for receiving from a first management entity CSP in charge of providing communications services of a DEMI request from SAP access points to virtual network functions.

[0083] The second management entity NSP1, responsible for providing network slices, comprises a module 202 for sending to the first management entity CSP a proposal PROP1 of SAP access points to virtual network functions hosted in the second network NNSP2 directly accessible by the second management entity NSP2.

[0084] The other management entities NSP2 and NSP3, responsible for providing network slices, also include modules for receiving a request and sending a proposal for SAP access points similar to modules 201 and 202 of the management entity NSP1, not shown in [Fig.l].

[0085] The first CSP management entity has direct access to an NCSP network. This network hosts its own communication links and its own computing resources. In particular, the NCSP network hosts two virtual network functions VNF0 and VNF.

[0086] The second management entity NSP1 has direct access to a network NNSPL This network hosts its own communication links and its own computing resources. In particular, the network NNSP1 hosts a virtual network function VNF'.

[0087] Similarly, the other management entities NSP2 and NSP3 each have direct access to a network, respectively NNSP2 and NNSP3. These networks host their own communication links and computing resources, and, in particular, the NNSP2 network hosts the virtual network function VNF' ' and the NNSP3 network hosts the VNF'”.

[0088] A network slice TR is represented in [Fig.l], consisting of the virtual network functions VNF0, VNF, VNF', VNF” and VNF'”. The network slice TR is therefore made up of virtual network functions hosted by separate networks, accessed directly by separate management entities. In this sense, the network slice TR is made up of virtual network functions VNF0, VNF, VNF', VNF” and VNF”' provided by different providers.

[0089] In addition to the virtual network functions VNF0, VNF, VNF', VNF” and VNF”', the network slice TR includes network links that enable the operation of the slice TR. These links are separated into two components: • on the one hand, an NNI communication link between the virtual network functions VNF0, VNF, VNF', VNF” and VNF”' which will carry the data flows between the network functions; • on the other hand, a UNI interface between the first CSP management entity and the EM management elements attached to the virtual network functions VNF0, VNF, VNF', VNF” and VNF'”.

[0090] This UNI interface allows the CSP management entity to transmit SND ins management instructions to virtual network functions VNFO, VNF, VNF', VNF” and VNF'”.

[0091] We will now detail how the invention makes it possible to manage a TR network slice whose functions are provided by several providers.

[0092] We recall that, in telecommunications, the notion of network slice appears from the definition of fifth generation telecommunications networks, known as 5G. In a network slice, the different functions are rendered by virtual network functions and are not attached to specific hardware elements. This makes it possible to envisage a very dynamic construction of network slices, involving several suppliers. But, in the current situation, network slices are predefined once and for all, with very few possibilities for dynamic evolution. This situation changes thanks to the invention. Virtual network functions can be virtualized functions themselves, or functions contained in containers.In our description, the term virtual network function should be understood as meaning both a virtual network function and a containerized network function.

[0093] The first CSP management entity is responsible for providing communication services. To do this, it wishes to have a TR network slice. According to the state of the art, the CSP management entity would request a management entity in charge of providing a network slice, for example the NSP1 management entity, to provide it with an already defined TR network slice.

[0094] A CSP management entity has a TR network slice with the ability to communicate with and manage the various virtual network functions that make up the TR network slice. This ability is first achieved by having SAP access points to the various virtual functions. A SAP access point can be, for example, a network address, or a URL (Uniform Resource Locator), or an API (Application Programming Interface) that allows communication with the network function. Additional elements such as passwords or cryptographic certificates can be used to secure communication with the virtual network function and are also part of the SAP access points.In particular, SAP access points provide access to the EM management elements which constitute the elements for addressing commands to the virtual network function by allowing a UNI interface to be defined to these EM management elements using the information contained in the SAP access points.

[0095] The information included in a SAP access point will also depend on the architecture of the network function itself. In the case of a containerized network function, the SAP access point may, for example, contain information relating to the container registry to which the containerized network function is registered. Whereas for a virtual network function itself, the SAP access point may contain information relating to the virtual machine on which the virtual network function is running.

[0096] To give a more detailed example, a virtual network function VNFO may be a database listing the clients of a communication service using the network slice TR. An access point SAP on the VNFO will for example include the network address and passwords to access the database. If the virtual network function VNFO is a virtual network function itself, the access point SAP may contain information about the running virtual machine. If it is a containerized network function, the access point SAP may contain information relating to access to the container.The SAP access point will also provide an API interface to add or remove customers from the database, or to query the database to see if a customer is present in the database, and the EM management element will allow commands to be sent to the database, such as a start or close command. These commands will be differentiated depending on the execution mode of the network function, namely a virtual or containerized function.

[0097] When the CSP management entity has the SAP access point on the VNFO virtual network function, which is a database listing customers of a communication service, and the associated EM management element, it can therefore start the customer database, then add or remove customers from it, and also connect it to other virtual network functions which can, for example, verify that a customer requesting to benefit from a service is indeed present in the database.

[0098] The CSP management entity will be able, thanks to the invention, to have a TR network slice whose virtual network functions VNFO, VNF, VNF', VNF” and VNF'” are provided by different providers. To do this, the CSP management entity performs a step of obtaining OBT of the SAP access points on the virtual network functions VNFO, VNF, VNF', VNF”, VNF'” provided by several providers.

[0099] A first way for the CSP management entity to have SAP access points on virtual network functions is to use those of the VNFO, VNF virtual network functions present in the NCSP network directly accessible to the CSP management entity. Indeed, the CSP management entity in charge of providing communication services has direct access to an NCSP network which allows it to directly manage the VNFO and VNF virtual network functions hosted in the NCSP network. The CSP management entity can therefore obtain the SAP access points of these two VNFO and VNF virtual network functions.

[0100] However, these two functions VNFO and VNF are not sufficient to constitute the slice TR network.

[0101] In our example, the first CSP management entity will therefore send a DEMI request for SAP access points to the second NSP1 management entity. The NSP1 management entity is responsible for providing network slices. It is natural to request such a management entity not to obtain a network slice in its entirety, already defined, but a part of it in the form of a certain number of virtual network functions.

[0102] The DEMI request is therefore a request for SAP access points to virtual network functions. The management entity NSP1 responds to this DEMI request with a proposal PROP1 for SAP access points to virtual network functions. In particular, in the example shown in [Fig.l], the management entity NSP1 may propose in the proposal PROP1 an SAP access point to the virtual network function VNF' hosted in the network NNSP1 directly accessible to the management entity NSP1. The management entity NSP1 in fact has an SAP access point to the virtual network functions hosted in its network, said SAP access point comprising all the information necessary to communicate and manipulate the virtual network function VNF'.

[0103] If the proposal PROP1 made by the management entity NSP1 to the access point entity SAP is not sufficient for the management entity CSP to be able to constitute the network slice TR, the method according to the invention makes it possible to proceed according to two options.

[0104] In a first option, the second management entity NSP1 will make a request DEM2 for SAP access points to a third management entity NSP2. This management entity NSP2 is also responsible for providing network slices and is therefore likely to provide SAP access points to virtual network functions making it possible to constitute a network slice TR. The proposal PROP2 for SAP access points will then allow the management entity NSP1 to include additional SAP access points in its own proposal PROP1. In this option, the management entity NSP2 plays a subcontractor role with respect to the management entity NSP1 and will not be known a priori to the management entity CSP.

[0105] A second option is for the CSP management entity to directly make a DEM3 request for access points to a fourth NSP3 management entity responsible for providing network slices. Here again, the NSP3 management entity will be able to respond in a PROP3 proposal for SAP access points on virtual network functions hosted in the NNSP3 network directly accessible to the NSP3 management entity.

[0106] These two options can of course be combined and the CSP management entity will ultimately be able to have proposals for SAP access points from the management entity NSP1 management, supplemented by access points from the NSP2 management entity, the NSP1 management entity being placed between the CSP management entity and the NSP2 management entity, and on the other hand access points from the NSP3 management entity obtained directly by a DEM3 request from the CSP management entity.

[0107] The DEMI, DEM2, DEM3 requests for SAP access points may contain any type of useful information to better describe the request. The first category of information will be a description of the expected functionalities of the virtual network functions accessible by the requested SAP access points. For example, the CSP management entity may have virtual network functions allowing its customers to have terrestrial mobile access to its communication services, but not satellite access. To complete the TR network slice managed by the CSP management entity, the latter may include in its DEMI request for SAP access points to the NSP1 management entity that the expected functionality is satellite access.

[0108] Other information may supplement the DEMI, DEM2, DEM3 requests. This is, for example, information relating to the expected quality of service. To take the example of the request for a satellite access function, this request would be supplemented with information relating to the quantity of parallel accesses that can be processed, the throughput of communications, the latency of response times during an access and any other relevant information.

[0109] Another relevant information that can qualify the DEMI, DEM2, DEM3 requests is the price offered by the CSP management entity to have the virtual network functions accessible by the requested SAP access points. The price can also be negotiated elsewhere and the methods according to the invention can only be used for the technical implementation of the TR network slice.

[0110] The information described here in requests DEMI, DEM2, DEM3 will also be found in proposals PROP1, PROP2, PROP3 for SAP access points made in response to requests DEMI, DEM2, DEM3. The proposed functionalities will be present in proposals PROP1, PROP2, PROP3, qualified by quality of service parameters and possibly by proposed prices.

[0111] In addition, the access point proposals PROP1, PROP2, PROP3 can be qualified by the CSP management entity which will decide whether these SAP access point proposals satisfactorily respond to the requests DEMI, DEM2, DEM3. The exchanges between the CSP, NSP1, NSP2 and NSP3 management entities can therefore take place repeatedly, in a negotiation process, until a proposal for SAP access points approved by the CSP management entity is reached.

[0112] We have seen that the NSP1 management entity can make a DEM2 request for points SAP access points to the NSP2 management entity in order to complete the PR0P1 proposal for SAP access points that the NSP1 management entity will make in response to the DEMI request from the CSP management entity. This DEM2 request can be made using two options: • In a first option, the NSP1 management entity sends a DEM2 request directly to the NSP2 management entity, before making a PR0P1 proposal to the CSP management entity. In this option, the NSP1 management entity decides that it cannot respond to the DEMI request alone and wishes to supplement it from the outset with SAP access points from the PR0P2 proposal of the NSP2 management entity. • In a second option, the NSP1 management entity sends to the CSP management entity a PR0P1 proposal for SAP access points in response to the DEMI request. The CSP management entity provides in response a qualification of the PR0P1 proposal which encourages the NSP1 management entity to improve its PROPI proposal. It is following this qualification that the NSP1 management entity makes a DEM2 request for SAP access points to the NSP2 entity and receives a PR0P2 proposal which will allow it to improve its PR0P1 proposal in a subsequent sending to the CSP management entity.

[0113] These two options can be combined, namely that several exchanges of requests and proposals will take place, either spontaneously on the part of the NSP1 management entity, or following qualifications of the PROP1 proposal on the part of the CSP management entity, until the PROP1 proposal is suitable for the CSP management entity.

[0114] In the situation represented by [Fig.l], the NSP1 management entity only makes a DEM2 request to a single NSP2 management entity, but it can of course make several requests to several management entities responsible for providing network slices in order to have proposals for SAP access points on virtual network functions.

[0115] Similarly, the management entity NSP3 is represented in [Fig.l] as responding to the request DEM3 with a proposal PROP3 of SAP access points established only with SAP access points of virtual network functions hosted in the NNSP3 network directly accessible to the management entity NSP3. But the latter can of course, in a similar manner to the management entity NSP1, request other management entities capable of providing network slices to complete its proposal PROP3 of SAP access points.

[0116] Finally, the CSP management entity can itself request other management entities in addition to the NSP1, NSP2, NSP3 entities represented in [Fig.l]. This request can be made either at the time when the CSP management entity seeks to obtain SAP access points in addition to those directly accessible in the NCSP network, or in response to proposals PR0P1, PR0P3 deemed insufficient by the CSP management entity.

[0117] Finally, the CSP management entity will have SAP access points on virtual network functions VNFO, VNF, VNF', VNF”, VNF”'. These SAP access points are located either in the NCSP network directly accessible by the CSP management entity, or in other networks NNSP1, NNSP2, NNSP3 directly accessible by management entities NSP1, NSP2, NSP3 in charge of providing network slices which, here, will provide only virtual network functions and not complete network slices. Obtaining SAP access points is done either directly, by proposals made to requests for SAP access points or following exchanges between the management entities, in which the CSP management entity qualifies the proposals for SAP access points which are made to it and judged insufficient. The CSP management entity can involve entities other than those represented in [Fig.l], but these will be classified into two categories: either they will be in direct relation with the CSP management entity, as is the case for the NSP1 and NSP3 management entities; or they will be in a delegation situation, because they will not have responded to a direct request for SAP access points from the CSP management entity and will therefore not be in direct relation with the CSP management entity. This is the case for the NSP2 management entity whose relation with the CSP management entity is made via the NSP1 management entity which is placed in between the two CSP and NSP2 management entities.

[0118] When the CSP management entity has obtained the SAP access points on virtual network functions, the management method according to the invention continues by the creation CRT of an NNI communication link between the virtual network functions using information contained in the obtained SAP access points. The NNI communication link will carry the data flows between the virtual network functions and is distinct from the UNI interface between the first CSP management entity and the EM management elements of the virtual network functions.

[0119] The CRT creation of the NNI communication link uses the information contained in the SAP access points of the virtual network functions. These SAP access points make it possible to obtain information such as network addresses or passwords. Thanks to this information, the CSP management entity can construct the NNI communication link between the virtual network functions which will carry the network traffic which takes place due to the operation of the TR network slice. This network traffic will be for example that between the virtual network functions which are used for access by users of the TR network slice and those which have rather core network functions. This network traffic will therefore be massive, and will include a significant quantity of data. Such traffic cannot therefore be seen as negligible in the economy of the networks it will use. Therefore, when this traffic has to pass from one network to another, the creation of CRT includes the creation of PP exchange points between the NCSP, NNSP1, NNSP2 and NNSP3 networks. Such PP exchange points ensure a fair distribution of any remuneration from network operators according to the traffic of users of the communication service offered by the CSP management entity using the TR tranche.

[0120] In addition to the NNI communication link between the virtual network functions, there is a UNI interface connecting the first CSP management entity to the EM management elements of the different virtual network functions that form the TR network slice. This UNI interface allows the CSP management entity to transmit SND management instructions to the EM management elements of the virtual network functions. Here again, it is the OBT obtaining of the SAP access points that allows the CSP management entity to have the information describing the UNI interface, information such as network addresses, passwords, cryptographic certificates, application interface models or any other useful information. Since the traffic that will pass through the UNI interface will be limited to management instructions, its size will therefore be negligible compared to the actual network traffic that uses the NNI links.The UNI interface therefore does not require deploying PP exchange points between the different networks in which the virtual network functions are hosted.

[0121] In the situation of [Fig.l], the management entity NSP2 is a subcontractor of the management entity NSP1 with regard to the provision of SAP access points on the virtual network function VNF” to the management entity CSP. This implies that the management entity NSP1 is located in a cut-off between the management entity CSP and the management entity NSP2. In particular, the communication link NNI and the interface UNI are constructed in such a way as to avoid direct visibility from the management entity CSP to elements managed by the management entity NSP2, namely the virtual network function VNF” hosted in the network NNSP2, as well as its SAP access point and its management element EM.

[0122] The presentation of [Fig.l] that we have just made can be seen as presenting the creation of the management slice TR. The management entity CSP obtains OBT from the SAP access points on virtual network functions VNFO, VNF, VNF', VNF”, VNF'” and then creates the communication link NNI, which creates a network slice TR, formed by the virtual network functions VNFO, VNF, VNF', VNF”, VNF'” connected to each other by the link NNI which carries the data traffic between these functions, the interface UNI allowing to send management instructions to the virtual network functions VNFO, VNF, VNF', VNF”, VNF”'.

[0123] However, these different operations can also be seen as allowing the management of the TR network slice by the CSP management entity. Indeed, if the CSP management entity manages the TR network slice in order to provide communication services, it may be required to change the virtual network functions that form the TR network slice. Such a modification of the architecture of the TR network slice is carried out by following the steps of the management method according to the invention.

[0124] It is this creation or modification of the TR network slice which allows the CSP management entity to have the resources to manage the TR network slice.

[0125] The actual management of the TR network slice by the CSP management entity then involves sending management instructions to the virtual network functions that form the TR slice. These management instructions pass through the dedicated UNI interface to the EM management elements of the virtual network functions VNFO, VNF, VNF', VNF”, VNF”'. These instructions can be of any type. For example, they are instructions for starting or stopping the virtual network functions. These can also be instructions that make it possible to change the operating parameters of the network functions, such as response times or throughputs or any other parameter. These can also be instructions that make it possible to modify security elements, such as passwords or cryptographic certificates.

[0126] The invention therefore makes it possible to manage a TR network slice provided by different suppliers, in this case, in the example of [Fig.l], the management entities CSP, NSP1, NSP2 and NSP3.

[0127] [Fig 2], for its part, illustrates an example of exchange of messages between different management entities within the framework of an embodiment of the invention.

[0128] In the example of [Fig 2], the first management entity CSP sends a DEMI request for SAP access points to the second management entity NSP2. The second management entity considers that it cannot respond directly to the DEMI request for SAP access points. For example, the management entity NSP1 does not host in the NNSP1 network which is directly accessible to it a virtual network function which fulfills a functionality explicitly requested by the management entity CSP in the DEMI request. The second management entity NSP1 will then send a DEM2 request for SAP access points to the third management entity NSP2. For example, the DEM2 request will relate to the functionality requested by the management entity CSP which is not provided by the virtual network functions hosted in the NNSP1 network. The management entity NSP2 responds to the DEM2 request with a PROP2 proposal for SAP access points.The NSP1 management entity can then integrate SAP access points present in the PROP2 proposal into the PROP1 proposal of SAP access points which it sends to the first CSP management entity. In this way, a functionality requested in the DEMI request, but which could not be fulfilled by a virtual network function hosted in the NNSP1 network, could be provided by a virtual network function hosted in the NNSP2 network, and the SAP access point for this function will be proposed in the PR0P2 proposal and then integrated into the PROPI proposal.

[0129] [Fig 3], for its part, illustrates another example of exchange of messages between different management entities within the framework of another embodiment of the invention.

[0130] In the example of [Fig 2], the first management entity CSP sends a DEMI request for SAP access points to the second management entity NSP2, in a manner identical to the example of [Fig 2]. However, in the example of [Fig 3], the management entity NSP2 considers that it can respond directly to the DEMI request and sends a PROP1 proposal for SAP access points to the management entity CSP. The management entity CSP then transmits to the management entity NSP1 information representative of the quality of the PROP1 proposal.

[0131] In the example represented by [Fig 3], this information is contained in an ANS message. For example, the information contained in the ANS message may be that a quality of service parameter present in the proposal PROP1 is considered insufficient by the CSP management entity for the operation of the network slice TR that this management entity seeks to constitute to provide a communication service. The NSP1 management entity will then send a request DEM2 for SAP access points to the third NSP2 management entity, taking into account the information transmitted in the ANS message. The NSP2 management entity will then make to the NSP1 management entity a proposal PROP2 for SAP access points which can be used to improve the proposal PROP1 for SAP access points which is transmitted again, improved, to the CSP management entity.For example, for a given functionality that can be rendered by a virtual network function hosted in the NNSP1 network or in the NNSP2 network, the function of the NNSP1 network may have been initially proposed in the PROP1 proposal but had an unsatisfactory quality of service parameter. The PROP2 proposal may give a SAP access point on a function hosted in NNSP2 rendering the same functionality, with a better quality of service parameter, and the PROP1 proposal may be modified by using this other SAP access point, associated with a better quality of service parameter, which therefore has a better chance of being accepted by the CSP management entity.

[0132] [Fig 4], for its part, illustrates a third example of exchange of messages between different management entities within the framework of another embodiment of the invention.

[0133] In the example of [Fig 4], as in the two previous examples, the first CSP management entity sends a DEMI request for SAP access points to the second management entity NSP1. In response, the management entity NSP1 sends a proposal PROP1 for SAP access points. In the example in [Fig 4], the management entity CSP will seek to complete the proposal PROP1 for SAP access points by sending a request DEM3 to a fourth management entity NSP3, which will respond with a proposal PROP3.

[0134] These different examples can be implemented separately or combined. The proposal PROP1 received by the CSP management entity in the example of [Fig 4] may have been supplemented by SAP access points received in a proposal PROP2 made by the NSP2 management entity to the NSP1 management entity. In general, the requests for SAP access points and the proposals made in response can form a tree whose top is the CSP management entity. The CSP management entity will then be able to build and manage a network slice TR whose virtual network functions are provided by several providers. The first provider is the CSP management entity itself but other virtual network functions are provided by management entities in charge of providing network slices, which host these virtual network functions in the networks directly accessible to them.Among the management entities responsible for providing network slices, a distinction is made between those that are directly visible from the CSP management entity and those that are in a subcontracting position to other management entities responsible for providing network slices, and will therefore not be directly visible to the CSP management entity. The creation of the NNI communication link as well as the UNI management interface take this distinction into account and respect this non-visibility by the CSP management entity of certain virtual network function providers.

[0135] Finally, let us point out here that, in the present text, the term “module” can correspond to a software component as well as to a hardware component or a set of hardware and software components, a software component itself corresponding to one or more computer programs or sub-programs or, more generally, to any element of a program capable of implementing a function or a set of functions as described for the modules concerned. In the same way, a hardware component corresponds to any element of a hardware assembly capable of implementing a function or a set of functions for the module concerned (integrated circuit, smart card, memory card, etc.).

Claims

Claims

1. Method for managing a network slice (TR) by a management entity (CSP) in charge of providing communication services, called the first management entity, the network slice (TR) comprising virtual network functions (VNFO, VNF, VNF', VNF”, VNF”') provided by several providers and managed through respective management elements (EM), the functions being characterized by access points (SAP) comprising information relating to the virtual network functions (VNFO, VNF, VNF', VNF”, VNF”'), characterized in that it comprises the following steps carried out by the first management entity (CSP): • Obtaining (OBT) access points (SAP) characterizing the virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”) provided by several providers;• Create (CRT) a communication link (NNI) between the virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”) using information contained in the access points (SAP) obtained (OBT); • Transmit (SND) management instructions to the virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”) through an interface (UNI) connecting the first management entity (CSP) to the management elements (EM) of the virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”), said interface (UNI) using information included in the access points (SAP) obtained (OBT).;

2. Management method according to claim 1 characterized in that the first management entity (CSP) has direct access to a first network (NCSP) and in that obtaining (OBT) the access points (SAP) comprises determining virtual network functions (VNFO, VNF) hosted in said first network (NCSP) directly accessible by the first management entity (CSP) and obtaining (OBT) the access points (SAP) of these virtual network functions (VNFO, VNF).

3. Management method according to one of claims 1 or 2 characterized in that obtaining (OBT) the access points (SAP) comprises a transmission (SND) by the first management entity (CSP) to a management entity (NSP1) responsible for providing network slices, called the second management entity (NSP1), having direct access to a second network (NNSP1), of a first request (DEMI) for access points (SAP) characterizing virtual network functions and reception of a proposal (PR0P1) for access points (SAP) characterizing virtual network functions (VNF') hosted in the network (NNSP1) directly accessible by the second management entity (NSP1), called the first proposal (PR0P1).

4. Management method according to claim 3 characterized in that the creation (CRT) of a communication link (NNI) between the virtual network functions (VNO, VNF), called first functions, hosted in the first network (NCSP) and the virtual network functions (VNF'), called second functions, hosted in the second network (NNSP1), comprises the creation of an exchange point (PP) between the first network (NCSP) and the second network (NNSP1).

5. Management method according to one of claims 3 or 4 characterized in that the first proposal (PROP1) of access points (SAP) is completed by the second management entity (NSP1) with access points (SAP), called complementary access points, characterizing virtual network functions (VNFs), called third functions, said complementary access points (SAPs) being proposed by a third management entity (NSP2), having direct access to a third network (NNSP2), said third functions (VNFs) being hosted in said third network (NNSP2), and, moreover,the method comprises creating an exchange point (PP) between the second network (NNSP1) and the third network (NNSP2) and a communication link (NNI) with the third virtual network functions (VNFs) as well as an interface (UNI) with the management elements (EM) of the third virtual network functions (VNFs) so as to avoid a direct link between the first network (NCSP) and the third network (NNSP2).,

6. Management method according to one of claims 3 to 5 characterized in that obtaining (OBT) the access points (SAP) comprises, after receiving a first proposal (PROP1), the following additional steps: • sending, by the first management entity (NCSP) to a fourth management entity (NSP3), in charge of providing network slices, having direct access to a fourth network (NNSP3), of another request (DEM3) for access points (SAP) to virtual network functions; • the reception by the first management entity (NCSP) of another proposal (PROP 3) for access points (SAP) to virtual network functions (VNF'”) hosted in the fourth network (NNSP3) directly accessible by the fourth management entity (NSP3); and, in addition, the creation (CRT) of a communication link (NNI) with the virtual network functions (VNF”') hosted in the fourth network (NNSP3) includes the deployment of an exchange point (PP) between the first network (NCSP) and the fourth network (NNSP3).

7. Management method according to one of claims 3 to 6 characterized in that the requests (DEMI, DEM2, DEM3) for access points (SAP) to virtual network functions include information relating to the expected functionalities of the virtual network functions attached to the requested access points (SAP) and quality of service parameters.

8. Management method according to one of claims 3 to 7 characterized in that the proposals (PROP1, PROP2, PROP3) of access points (SAP) to virtual network functions include information relating to the guaranteed functionalities of the virtual network functions attached to the proposed access points (SAP) and quality of service parameters.

9. Method for providing access points (SAP) to virtual network functions included in a network slice (TR) comprising the following steps executed by a second management entity (NSP1) in charge of providing network slices, having direct access to a second network (NNSP1): • Receiving from a first management entity (CSP) in charge of providing communications services a first request (DEMI) for access points (SAP) to virtual network functions; • Sending to the first management entity (CSP) a first proposal (PROP1) for access points (SAP) to virtual network functions (VNF') hosted in the second network (NNSP1) directly accessible by the second management entity (NSP1).

10. A method of providing according to claim 9 characterized in that the first management entity (CSP) has direct access to a first network (NCSP) and the method comprises the deployment of an exchange point (PP) between the first network (NCSP) and the second network (NNSP1) in order to allow the deployment of a communication link (NNI) with the virtual network functions (VNF') hosted in the second network (NNSP1).

11. A method of providing according to one of claims 9 or 10, characterized in that the first proposal (PROP1) of access points (SAP) is supplemented by the second management entity (NSP1) with access points (SAP), called complementary access points, characterizing virtual network functions (VNFs), called third functions, said complementary access points (SAPs) being proposed by a third management entity (NSP2), having direct access to a third network (NNSP2), said third functions (VNFs) being hosted in said third network (NNSP2),and in that the method further comprises creating an exchange point (PP) between the second network (NNSP1) and the third network (NNSP2) and a communication link (NNI) with the third virtual network functions (VNFs) as well as an interface (UNI) with the management elements (EM) of the third virtual network functions (VNFs) so as to avoid a direct link between the first network (NCSP) and the third network (NNSP2).,

12. Method of providing according to one of claims 9 to 11 characterized in that the requests for access points (SAP) to virtual network functions include information relating to the expected functionalities of the virtual network functions attached to the requested access points (SAP) and quality of service parameters.

13. Method of providing according to one of claims 9 to 12 characterized in that the proposals for access points (SAP) to virtual network functions comprise information relating to the guaranteed functionalities of the virtual network functions attached to the proposed access points (SAP) and quality of service parameters.

14. Management entity (CSP) responsible for providing communication services- nication, called first management entity, having direct access to a network (NCSP), called first network, said first management entity (CSP) implementing a method for managing a network slice (TR) comprising virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”), the virtual network functions being managed through management elements (EM), and comprising the following modules: • a module (101) for obtaining (OBT) access points (SAP) on the virtual network functions (VNFO, VNF, VNF', VNF”, VNF'”); • a module (102) for creating (CRT) a communication link (NNI) between the virtual network functions, said link (NNI) using information contained in the access points (SAP) obtained (OBT); • a module (103) for transmitting (SND) management instructions to virtual network functions through an interface (UNI) connecting the first management entity (CSP) to the management elements (EM) of the virtual network functions, said interface (UNI) using information contained in the access points (SAP) obtained (OBT).

15. Management entity (NSP1) responsible for providing network slices, called second management entity, having direct access to a network (NNSP1), called second network, said second management entity (NSP1) implementing a method for providing access points (SAP) to virtual network functions included in a network slice (TR), and comprising the following modules: • a module (201) for receiving from a first management entity (CSP) responsible for providing communications services of a request for access points (SAP) to virtual network functions; • a module (202) for sending to the first management entity (CSP) a proposal for access points (SAP) to virtual network functions hosted in the second network (NNSP1) directly accessible by the second management entity (NSP1).

16. Computer program capable of being implemented by a management entity (CSP) responsible for providing communication services according to claim 14, the program comprising code instructions which, when executed by a processor, performs the steps of the method for managing a network slice (TR) according to claim 1.

17. A computer program capable of being implemented by a management entity (NSP1) responsible for providing network slices according to claim 15, the program comprising code instructions which, when executed by a processor, performs the steps of the method for providing access points (SAP) to virtual network functions included in a network slice (TR) according to claim 9.

18. Data medium on which is recorded a computer program comprising a sequence of instructions for implementing the method for managing a network slice according to claim 1 when it is loaded into and executed by a processor.

19. A data carrier on which is recorded a computer program comprising a sequence of instructions for implementing the method of providing access points according to claim 9 when loaded into and executed by a processor.

Images