Monitoring method, service management method, network slice access management method and service access method, and devices configured to implement these methods

Abstract

The disclosed method for monitoring a network (NW) by a network controller (2) comprises: - a step of estimating at least one indicator representative of an environmental and / or energy impact due to a service provided via said network; and - a step of notifying, to an application server (4) associated with this service, that said indicator does not meet a given compliance criterion if said at least one indicator does not meet said compliance criterion.

Description

Background Technology

[0001] This invention belongs to the general telecommunications field.

[0002] More specifically, the present invention relates to a mechanism for managing environmental and energy commitments of communication networks.

[0003] General communication services, particularly those accessible via fixed or mobile network infrastructure, have a significant carbon footprint, which has been extensively documented for many years, especially for cloud-based communication networks. With global warming, most companies, including network operators and service providers, are now highly sensitive to corporate social responsibility (CSR) issues, and some have already set carbon neutrality and / or energy emission reduction targets.

[0004] With the emergence of new network infrastructure such as 5G mobile networks, and with the maturation of certain technologies, such as those facilitating the adoption of so-called "immersive" services (e.g., virtual or augmented reality), the sensitivity of such communications service deployments to their carbon footprint and / or energy consumption has recently increased. The deployment of cloud infrastructure in the context of a network transformation towards integrated virtualization and even automated software technologies is also partly responsible for the increased carbon footprint and energy costs associated with the overall changes in the telecommunications ecosystem and digital communications services.

[0005] Therefore, minimizing or even neutralizing carbon footprint and / or its energy costs has become a major challenge for most industrial sectors, especially network operators and service providers.

[0006] This invention proposes a mechanism to facilitate network operators and service providers in achieving this goal. Summary of the Invention

[0007] More specifically, this invention proposes a disruptive approach that advocates collaboration among all or some of the participants providing a service via a network—that is, collaboration between one or more communication devices, the service infrastructure, and the network accessing the service. In other words, instead of individual actions performed independently by each of these participants, this invention introduces collaboration among the network, service infrastructure, and communication devices to collectively work towards controlling or even reducing the environmental and / or energy impacts attributable to the service.

[0008] Therefore, according to a first aspect, the present invention proposes a monitoring method performed by a network controller of a network, the method comprising:

[0009] - The step of estimating at least one indicator of the environmental and / or energy impacts attributable to the services provided via the network;

[0010] - If at least one estimated metric does not meet a given compliance criterion, then notify the application server associated with the service that the at least one metric does not meet the compliance criterion.

[0011] Correspondingly, the present invention relates to a network controller for a network, the network controller comprising:

[0012] - An estimation module configured to estimate at least one indicator representing the environmental and / or energy impacts attributable to services provided via the network; and

[0013] - A notification module that is activated when at least one estimated metric fails to meet a given compliance criterion and is configured to notify the application server associated with the service that the at least one metric fails to meet the compliance criterion.

[0014] This invention is applicable to any type of metric when information about the environmental and / or energy impacts attributable to the service can be provided. For example, the metric could be a carbon footprint, flow metrics (such as a measure of contribution to the greenhouse effect), energy consumption, energy supply costs, etc.

[0015] According to a second aspect, the present invention provides a method for an application server to manage a service associated with a service provided via at least one network, the method comprising:

[0016] - The step of receiving, from the network controller of the network, a notification indicating that at least one indicator, estimated by the network controller, representing the environmental and / or energy impact attributable to the service, does not meet a given compliance criterion; and

[0017] - A step that triggers at least one management action to manage the environmental and / or energy impacts, the management action relating to all or part of the traffic related to the service.

[0018] Correspondingly, the present invention relates to an application server configured to manage services provided via at least one network, the application server comprising:

[0019] - A receiving module configured to receive from the network controller of the network a notification indicating that at least one indicator, estimated by the network controller, representing the environmental and / or energy impacts attributable to the service, does not meet a given compliance criterion; and

[0020] - A triggering module configured to trigger at least one management action for managing the environmental and / or energy impacts, the management action relating to all or part of the traffic related to the service.

[0021] According to a third aspect, the present invention relates to a method for accessing services provided via a network by a communication device, the method comprising:

[0022] - The step of sending an access request to the application server associated with the service; and

[0023] - The step of receiving a notification from the application server, which informs the communication device that: after the application server receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller representing the environmental and / or energy impact does not meet a given compliance criterion, at least one management measure for managing the environmental and / or energy impact attributable to the service will be applied to traffic related to the service from or to the communication device.

[0024] Correspondingly, the present invention relates to a communication device, the communication device comprising:

[0025] - A sending module configured to send an access request for accessing a service to an application server associated with a service provided via the network; and

[0026] - A receiving module configured to receive a notification from an application server informing the communication device that, after the application server receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller representing the environmental and / or energy impacts does not meet a given compliance criterion, at least one management measure for managing the environmental and / or energy impacts attributable to the service will be applied to traffic related to the service from or to the communication device.

[0027] According to a fourth aspect, the present invention relates to a method for an entity of a network to manage access to a network slice supported by the network, the method comprising:

[0028] - The step of receiving an access request from a communication device for accessing a given network slice supported by the network, wherein the network slice is shared among multiple communication devices accessing the service after an application server associated with a service provided via the network receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller, representing the environmental and / or energy impact attributable to the service, does not meet a given compliance criterion;

[0029] - The step of verifying with the application server associated with the service whether the communication device is authorized to access the shared given network slice; and

[0030] - Where applicable, the step of triggering the connection between the communication device and the shared given network slice.

[0031] Correspondingly, the present invention relates to a network entity configured to manage access to network slices supported by the network, the entity comprising:

[0032] - A receiving module configured to receive from a communication device an access request for accessing a given network slice supported by the network, wherein the network slice is shared among multiple communication devices accessing the service after an application server associated with a service provided via the network receives from the network controller of the network a notification indicating that at least one indicator estimated by the network controller, representing the environmental and / or energy impacts attributable to the service, does not meet a given compliance criterion.

[0033] - A verification module configured to verify with the application server associated with the service whether the communication device is authorized to access the shared given network slice; and

[0034] - A trigger module, which is activated where applicable and configured to trigger a connection between the communication device and the shared given network slice.

[0035] The present invention also relates to a system according to the invention, the system comprising at least one network controller and network entity, an application server associated with services provided via the network, and at least one communication device.

[0036] According to the collaborative mechanism proposed in this invention, a network controller, via which it provides services, monitors at least one indicator representing the environmental and / or energy impact attributable to the service, such as the carbon footprint attributable to the service. If one or more of the indicators in question do not meet a given compliance criterion (e.g., they do not meet reference values ​​defined for the service, typically expected, desired, or authorized values ​​for the service), the application server associated with the service is notified, triggering one or more adjustment actions. These adjustment actions constitute measures for managing the environmental and / or energy impact attributable to the service; they are designed, for example, to limit or even neutralize such environmental and / or energy impact attributable to the service. The notification from the application server may, for example, be generated by the application server subscribing to the network controller, causing the network controller to inform the application server of various events related to the environmental / energy impact of the service (e.g., the carbon footprint attributable to the service exceeds a given threshold). The one or more management measures may, for example, be triggered by the application server, or by the network controller itself in collaboration with the application server.

[0037] No assumptions are made regarding the frequency or method of estimating the one or more metrics. Such estimations can be performed ad hoc, continuously or quasi-continuously (e.g., on a sliding window), or at a regular frequency (e.g., daily, weekly, monthly). The estimations can be based on filters installed in the network and / or on feedback provided by probes deployed at various points in the network that allow the collection of information about various communications associated with one or more services. For this purpose, the network can specifically utilize protocols known per se such as NETCONF or IPFIX.

[0038] Therefore, for example, in one particular embodiment, the estimation step of the monitoring method includes receiving at least one piece of information from at least one detector deployed in the network, the at least one piece of information reflecting the environmental and / or energy impact of at least one communication related to the service, the at least one communication being established from or to a server involved in providing the service.

[0039] Furthermore, depending on the metrics considered and the desired outcome (prevention or remediation measures after service degradation), one or more compliance criteria compared to the estimated metrics can take different forms. For example, such compliance criteria could be exceeding a critical threshold (minimum or maximum value, depending on the metric considered), or exceeding an intermediate threshold (e.g., a percentage of that critical threshold) before reaching it, in order to trigger one or more preventative actions to anticipate service degradation. Another criterion could be the change of the metric over time.

[0040] There are no restrictions on the nature of management measures that can be triggered in response to detected non-compliance. These management measures are designed, for example, to establish collaboration among networks, service infrastructure, and / or communication equipment to limit or neutralize the environmental and / or energy impacts attributable to the service, and thus ensure that traffic from and / or to communication equipment can be carried under optimal digital restraint conditions. A management measure can also be envisioned that results in the aggregation of multiple service platforms (particularly a reduction in their number) and leads to modifications to the compliance criteria considered for the service (e.g., increasing or carrying over the authorized allowance for the service's carbon footprint).

[0041] Therefore, in a particular embodiment, the at least one management measure may be selected from at least the following:

[0042] - Use encoding of data related to the service, where the encoding contributes less to the environmental and / or energy impacts attributable to the service than the current encoding;

[0043] -Restrict access to the service via the network;

[0044] - (Time-based) Scheduling access to the service from multiple communication devices;

[0045] - During the access to the service by multiple communication devices, at least one given resource of the network is shared by the communication devices; and

[0046] - Tag traffic associated with the service to store it in at least one queue.

[0047] Of course, other management measures can be envisioned as variations.

[0048] Advantageously, these management measures can be selected and / or parameterized based on estimates of the metrics under consideration, enabling action to be taken in a dynamic, targeted, and appropriate manner. These management measures can be applied to all or part of the traffic associated with the service.

[0049] Therefore, in one specific embodiment, the management method implemented by the application server includes:

[0050] - The steps of receiving an access request from a communication device to access the service;

[0051] - If the communication device is affected by the management measures, then the management measures are applied to the service-related traffic from or to the communication device.

[0052] One conceivable management approach is programmable scheduling, which allows for the organization of access to services by multiple communication devices over time.

[0053] Therefore, in a particular embodiment, when the at least one management measure includes scheduling access to the service by multiple communication devices, the management method implemented by the application server includes the step of selecting a time slot to be allocated to the multiple communication devices for accessing the service after the at least one communication device requests access to the service.

[0054] In other words, the application server determines when each communication device requesting access to the service actually accesses the service, and thus is able to send or receive data associated with that service. Multiple communication devices requesting access to the service within a given time interval can be allocated the same time slot for accessing the service. Therefore, a communication device's access to the service can be delayed based on programming already made for the use of the resources used to provide the service, that is, the time slots already allocated for the service. It should be noted that the focus here is on the organization of user access to the service by communication devices (e.g., access to streaming video content), rather than strictly speaking the scheduling of data packets associated with users on network resources.

[0055] When communication devices share the same resources used to access services—that is, in a context where services are not provided to communication devices via dedicated resources but rather shared to provide services to multiple communication devices—programmable scheduling for accessing that service is preferred. The combination of shared resource use by multiple communication devices with programmable scheduling not only helps to better manage the environmental and / or energy impact of the network but also helps to improve the efficiency of network resource utilization and traffic routing policies implemented within the network. This approach makes it possible to consider the energy and environmental budgets of each service and each user. This promising approach can also be applied to different contexts: communication between data centers, dynamic management of corporate processes (or workflows), resource tuning that allows access to event services and content at appropriate quality levels, etc.

[0056] Resource sharing can be easily established based on the network controller. In one particular embodiment, the monitoring method further includes:

[0057] - The step of receiving from the application server a notification regarding the shared use of at least one given resource of the network by multiple communication devices during access to the service; and

[0058] - The steps to configure at least one entity in the network to allow such shared use.

[0059] Such entities in a network are, for example, edge nodes that are configured with new classification rules to consider the shared use of resources.

[0060] In the context of this invention, different resources of a network can be shared. For example, in the context of streaming video services, it is conceivable to use a multicast tree deployed in the network (or even deployed in a network-supported slice) to send the same video content to multiple communication devices via the network. According to another example, it is conceivable that multiple communication devices use the same network slice supported by the network (typically a network slice dedicated to such shared use) to access the service.

[0061] Therefore, in one particular embodiment, the at least one shared resource includes a given network slice supported by the network, and the notification received from the application server includes information indicating a scheduling of communication devices accessing the service via the network slice.

[0062] Therefore, in order to limit the environmental and / or energy impact of the service, this embodiment proposes that multiple communication devices share one or more network slices supported by the network to access the service, and access to the network slices in question is organized according to a specific schedule appropriately selected by the application server.

[0063] Therefore, this invention has a preferred but non-limiting application in the context of networks that support network slicing, such as 5G networks. In a manner known per se, a network slice can be defined as a Virtual Private Network (VPN) deployed on fixed or mobile network infrastructure or both, and designed to provide a specific set of performance capabilities. This network slice can be considered a logical network that provides connectivity to its users and has its own characteristics in terms of capacity (bandwidth), quality of service (latency, rate, one-way transmission time, jitter (or inter-packet delay variation, etc.)), and security (e.g., maintaining the confidentiality of information transmitted within the VPN through the use of encryption).

[0064] This embodiment can be easily implemented by working with a network controller and / or communication equipment.

[0065] Therefore, in one particular embodiment, the management method implemented by the application server may include at least one step selected from the following:

[0066] - The step of informing the network controller of the communication device's shared use of the given network slice according to the determined schedule; and

[0067] - The steps of notifying the communication device of the given network slice to be shared by the communication device during access to the service and notifying the determined schedule to be applied.

[0068] Accordingly, for communication devices, in embodiments where the at least one management measure includes shared use of a given network slice supported by the network by multiple communication devices, including the communication device in question, according to a determined schedule during access to the service, the method may include:

[0069] - The step of sending an access request to an entity in the network for accessing a given network slice of the shared network; and

[0070] - The step of accessing the service via the shared given network slice after the communication device has been connected to the shared given network slice.

[0071] Furthermore, before a communication device uses a shared network slice, control can be implemented on the application server by the entity of the network responsible for managing access to that network slice. Therefore, in one particular embodiment, the management method implemented by the application server may include the step of receiving a request from the entity of the network to verify whether the communication device is authorized to access the given network slice.

[0072] In a particular embodiment of the invention, if, after notifying the application server, the network controller detects that the application server has not implemented management measures for managing environmental and / or energy impacts attributable to the service, the network controller itself may trigger such management measures.

[0073] For example, in one embodiment, the monitoring method includes the step of activating at least one processing step in the network for all or part of the traffic related to the service, in response to an indicator indicating that the environmental and / or energy impact attributable to the service does not meet compliance criteria at the end of a defined period after the application server is notified.

[0074] Such processing may include, for example, switching all or part of the traffic flowing through the network in relation to the service to a network slice that provides a degraded level of service compared to the expected level of service for the service, such as a quality level best suited to the conditions for accessing the service, also known as best-effort.

[0075] In one particular embodiment, the monitoring, management, and access methods are implemented by a computer.

[0076] The present invention also relates to a computer program on a storage medium, wherein the program is executable in a computer or more generally in a network controller according to the invention, and includes instructions suitable for implementing the monitoring method as described above.

[0077] The present invention also relates to a computer program on a storage medium, wherein the program is executable in a computer or more generally in an application server according to the invention, and includes instructions suitable for implementing the methods for managing services as described above.

[0078] The present invention also relates to a computer program on a storage medium, wherein the program is executable in a computer or more generally in an entity of a network according to the invention, and includes instructions adapted to implement the methods described above for managing access to network slices.

[0079] The present invention also relates to a computer program on a storage medium, wherein the program is executable in a computer or more generally in a communication device according to the invention, and includes instructions suitable for implementing the method for accessing services as described above.

[0080] Each of these programs can be written in any programming language and can be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other desired form.

[0081] The present invention also relates to a computer-readable information medium or storage medium comprising instructions of a computer program as mentioned above.

[0082] The information or storage medium can be any entity or device capable of storing programs. For example, the medium can include storage devices such as ROM (e.g., CD-ROM or microelectronic circuit ROM), or even magnetic storage devices (e.g., hard disk or flash memory).

[0083] Furthermore, the information or storage medium can be a transmittable medium such as an electrical signal or an optical signal, which can be routed via a cable or optical fiber, a radio link, a wireless optical link, or other means.

[0084] The program according to the invention can be downloaded specifically via the Internet.

[0085] Alternatively, the information or storage medium may be an integrated circuit incorporating a program, the circuit being adapted to execute or be used to execute the access management method, service management method, access method, and monitoring method according to the present invention.

[0086] In other embodiments, combinations of the monitoring method, service management method, network slice access management method and service access method, network controller, application server, network entities and communication devices, and system according to the present invention having all or some of the above features are also conceivable. Attached Figure Description

[0087] Other features and advantages of the invention will become apparent from the following description, which is illustrated with reference to the accompanying drawings, which show exemplary embodiments of the invention in a manner that is by no means limiting. In the drawings:

[0088] [ Figure 1 ] Figure 1 The system according to the invention is shown in its environment in a particular embodiment;

[0089] [ Figure 2 ] Figure 2 The illustration schematically shows the genus according to the invention. Figure 1 The hardware architecture of the system is capable of hosting network controllers, application servers, management entities, or communication devices.

[0090] [ Figure 3 ] Figure 3 The flowchart illustrates, in a particular embodiment, the process of... Figure 1 The main steps of the monitoring method according to the present invention implemented by the network controller of the system;

[0091] [ Figure 4 ] Figure 4The flowchart illustrates, in a particular embodiment, the process of... Figure 1 The main steps of the method for managing service access according to the present invention implemented by the application server of the system;

[0092] [ Figure 5 ] Figure 5 The flowchart illustrates, in a particular embodiment, the process of... Figure 1 The main steps of the method for managing network slices according to the present invention implemented by the system's management entity;

[0093] [ Figure 6 ] Figure 6 The flowchart illustrates, in a particular embodiment, the process of... Figure 1 The main steps of the method for accessing services according to the present invention implemented by the communication equipment of the system; and

[0094] [ Figure 7 ] Figure 7 An example of the format of the COSINUS_OP option that can be used in the context of this invention is shown. Detailed Implementation

[0095] Figure 1 The system 1 according to the invention is shown in a particular embodiment in its environment. The system 1 is configured to implement a cooperative mechanism designed to control (manage) and potentially reduce (or even neutralize) the environmental and / or energy impacts of the service S provided via the communication network NW.

[0096] In the embodiments envisioned here, the communication network NW supports multiple network slices SL1, SL2, ..., SLK, where K represents an integer greater than 1. These network slices can be used to aggregate traffic associated with one or more services (i.e., traffic sent to or received from one or more services). Each network slice may involve one or more service functions, also known as network functions. Such service / network functions are, for example, base station or gNB (gNodeB) functions, user plane functions (UPF), traffic labeling, classification, and scheduling functions, etc. The same service / network function can be provided by one or more service function instances or network function instances. Service function chains (SFCs) can be established to facilitate routing of different types of traffic with different profiles for the purpose of generating (i.e., designing and deploying) network slices or routing within network slices.

[0097] A network NW is, for example, a 5G mobile network defined by 3GPP standards. It can be divided into multiple distinct (sub)networks (also called "segments"), thus forming many different domains. For example, a network NW can consist of a radio access network (RAN), a core network (CN), and a transport network (TN), providing connectivity within and between the core network and the radio access network. Each domain supports network slicing, the engineering and operation of which are characteristics of that domain. For example, slices deployed on a 5G mobile core network utilize the traffic processing and operational features specific to the 5G mobile core network.

[0098] No assumptions are made here regarding the nature or number of network slices supported by Network NW. These network slices may extend across one or more domains (and thus consist of multiple “local” network slices deployed in different domains; these network slices are then referred to as “multi-domain” network slices, “stitched slices”, or “hierarchical slices”). The ways of designing and deploying network slices to provide services are known in themselves and will not be described in detail herein.

[0099] It should be noted that these assumptions are not limiting in themselves, and the invention is applicable to other contexts, and particularly to other networks (which may or may not support network slicing), such as those based on SD-WAN (Software-Defined Wide Area Network) or SDN (Software-Defined Networking) architectures or those based on the use of Network Functions Virtualization (NFV) technology.

[0100] As previously described, system 1 is configured to control the environmental and / or energy impacts of service S provided via network NW. Therefore, in the embodiments described herein, the system includes at least:

[0101] -The network controller 2 and the network slice management entity 3 of the network NW according to the present invention;

[0102] - The application server (AS) associated with service S according to the present invention; and

[0103] - According to at least one communication device 5 of the present invention, the at least one communication device is connected to network NW and is able to access service S via network NW.

[0104] This invention is applicable to any type of service S (streaming video, virtual or augmented reality, video conferencing, etc.). Figure 1In the example, service S is a streaming video service provided by a service provider separate from the network NW operator, and application server 4 is a remote server located outside the network NW. However, this assumption is not limiting in itself, and the invention applies regardless of the location of the service. It should also be noted that application server 4 associated with service S is not necessarily, strictly speaking, the server providing service S; the application server can be any application server or service instance belonging to the service infrastructure providing service S. In the example contemplated here, the provider of service S is a network slice-based service provider or SSP (slice service provider). It is assumed that when communication device 5 subscribes to service S from the SSP, it has negotiated one or more network slices that it can use to send or receive traffic associated with service S via the network NW. Furthermore, the type of each network slice has been negotiated between communication device 5 and the network NW in a manner known per se.

[0105] In the example envisioned here, communication device 5 is a user equipment (UE), such as a smartphone, laptop computer, digital tablet computer, etc. However, the present invention can be readily applied to other fixed or mobile, software or hardware communication devices 5, such as service instances, home gateways, or CPEs (customer premises equipment).

[0106] In the embodiments described herein, the network controller 2, management entity 3, application server 4, and communication device 5 each have, as follows: Figure 2 The hardware architecture of computer 6 is shown. This hardware architecture specifically includes a processor (PROC), random access memory (MEM), read-only memory (ROM), non-volatile memory (NVM), and a communication device (COM). The non-volatile memory (NVM) constitutes a storage medium according to the invention, which can be read by the processor (PROC) and stores programs according to the invention.

[0107] When the hardware architecture of computer 6 is the same as that of the network controller (e.g., network controller 2) according to the present invention, the program, denoted as PROG-2, is stored in non-volatile memory (NVM) and includes instructions defining the main steps of the monitoring method according to the present invention. More specifically, the program defines the functional modules of network controller 2 (in... Figure 1 (As shown in the diagram), these functional modules are based on and / or control all or part of the components PROC, MEM, ROM, NVM, and COM of the aforementioned computer 6. In an example of service S, these functional modules include:

[0108] - Estimation module 2A, configured to estimate at least one indicator IND representing the environmental and / or energy impacts attributable to the service S provided via the network NW; and

[0109] - Notification module 2B, which is activated when at least one estimated metric IND does not meet a given compliance criterion CRIT (different criteria may be conceived depending on the metric under consideration), and is configured to notify the application server 4 associated with service S of this non-compliance.

[0110] In the embodiments described herein, network controller 2 further includes the following functional modules defined by computer program PROG-2:

[0111] - Triggering module 2C, configured here, is to trigger itself management actions (also known as "adjustment actions") for managing environmental and / or energy impacts attributable to the service, and more specifically, to trigger the default adjustment action ACT-DEF if application server 4 does not trigger such management actions after receiving a notification from notification module 2B indicating that the indicator IND does not meet the standard CRIT. This default adjustment action ACT-DEF is triggered in response to the non-compliance of the standard CRIT and is intended, for example, to reduce or neutralize environmental and / or energy impacts attributable to the service. An example of the default adjustment action ACT-DEF is given later for illustrative purposes; and

[0112] - Configuration module 2D, used to configure entities of network NW to allow the execution of management measures (default or triggered by application server 4) for managing the environmental and / or energy impacts of services S in the network.

[0113] Refer to later Figure 3 The functions of modules 2A to 2D of the network controller 2 are described in more detail. This figure illustrates the main steps of the monitoring method according to the present invention.

[0114] When the hardware architecture of computer 6 is that of an application server (e.g., application server 4) according to the present invention, the program according to the present invention stored in the non-volatile memory (NVM) of computer 6 is program PROG-4, which includes instructions defining the main steps of the method for managing services according to the present invention. Program PROG-4 defines the functional modules of application server 4 (in... Figure 1 (As shown in the diagram), these functional modules are based on and / or control all or part of the components PROC, MEM, ROM, NVM, and COM of the aforementioned computer 6. In an example of service S, these functional modules include:

[0115] - Receiving module 4A, configured to receive, where applicable, notification from network controller 2 that at least one indicator IND does not meet compliance standard CRIT; and

[0116] - Trigger module 4B, configured to trigger at least one management action ACT for managing environmental and / or energy impacts attributable to service S, the management action ACT involving all or part of the traffic related to service S. Examples of management action ACTs that can be triggered include:

[0117] ○ Use encoding of data related to service S, which contributes less to the environmental and / or energy impact attributable to service S than the encoding currently used by the communication devices accessing service S and / or the application servers providing service S;

[0118] ○Restrict access to service S via network NW;

[0119] ○Schedule access to service S from multiple communication devices;

[0120] ○ During the access to service S by multiple communication devices, at least one given resource of network NW is shared by these communication devices.

[0121] ○ Tag traffic associated with the service to store it in at least one queue;

[0122] ○ etc.

[0123] The phrase "shared use of resources" here refers to a mode in which the resource is not exclusively dedicated to providing a service to a single communication device, but rather used simultaneously to provide the service to multiple communication devices that wish to access the service within a given interval. This contrasts with the mode in which, after a communication device requests access to a service, the resource in question is used only for the flow of traffic from the service to that communication device (the resource is dedicated to that communication device), regardless of other communication devices wishing to access the same service. For example, multicast transmission mode demonstrates the shared use of resources to transmit data streams, as opposed to unicast transmission mode dedicated to a single user.

[0124] Of course, other management measures (or adjustment actions) can be conceived as variations, typically measures to limit or neutralize environmental and / or energy impacts attributable to service S. For example, management measures may include modifying the considered compliance standard CRIT (which, if the standard is a quota to be complied with, may, for example, be increased or carried forward). Furthermore, triggering module 4B can trigger combinations of the aforementioned management measures, as described in more detail later. Typically, in the embodiments described herein, shared use combining network slicing supported by network NW with a (so-called programmable) scheduling mechanism that organizes such shared use among relevant communication devices is considered.

[0125] In the embodiment described herein, application server 4 further includes the following functional modules defined by computer program PROG-4:

[0126] - Notification module 4C, which is configured to notify (i.e. inform) the network controller 2 and / or the communication devices accessing the service of one or more management measures triggered by its triggering module 4B;

[0127] - Verification module 4D, which is configured to perform various verifications on requests from entities of network NW (e.g., management entity 3); and

[0128] - Provide module 4E, which is configured to provide service S to communication devices (including communication device 5) connected to the network NW via the network NW.

[0129] No assumptions are made regarding the organization of modules 4A to 4E, which have just been described. These modules may be integrated in separate service instances or in a single service instance. Thus, for example, in the embodiment described herein, it is assumed that application server 4 exposes a PCP (Port Control Protocol) server to interact with communication devices (including communication device 5), network controller 2, and entities of network NW, particularly management entity 3, that wish to access service S. The PCP protocol, as described in RFC 6887 entitled "Port Control Protocol (PCP)" by D. Wing et al., published by the IETF in April 2013, is particularly advantageous because it helps conserve energy by allowing devices using the PCP protocol to avoid sending "keep-alive" messages (e.g., battery consumption from such devices where applicable) and avoids unnecessary stress on network resources. Typically, modules 4A, 4C, and 4D of application server 4 are based on or can be integrated into this PCP server.

[0130] Refer to later Figure 4 The functions of modules 4A to 4E of application server 4 are described in more detail. This figure illustrates the main steps of the method for managing services according to the present invention.

[0131] In the embodiments described herein, application server 4 performs certain management measures for managing environmental and / or energy impacts attributable to service S, such as, in particular, the use of shared resources (e.g., network slices) of network NW by multiple communication devices and scheduling access to the service by these communication devices, based on network NW management entity 3. When the hardware architecture of computer 6 is that of the management entity (e.g., management entity 3) according to the invention, the program according to the invention stored in the non-volatile memory NVM of computer 6 is program PROG-3, which includes instructions defining the main steps of a method according to the invention for managing access to network slices. Program PROG-3 defines the functional modules of management entity 3 (in... Figure 1 (As shown in the diagram), these functional modules are based on and / or control all or part of the components PROC, MEM, ROM, NVM, and COM of the aforementioned computer 6. In an example of service S, these functional modules include:

[0132] - Receiving module 3A, which is configured to receive from a communication device such as communication device 5, for accessing a given network slice SL1, ..., SLK supported by network NW, the network slice SLopt being shared among multiple communication devices accessing service S provided via network NW, so that after application server 4 receives a notification from network controller 2 indicating that at least one indicator IND attributable to the environmental and / or energy impact of service S does not meet the compliance standard CRIT, the environmental and / or energy impact attributable to service S is adjusted.

[0133] - Verification module 3B, configured to verify with application server 4 associated with service S whether the communication device in question is authorized to access the shared network slice SLopt; and

[0134] - Trigger module 3C, which is activated where applicable and configured to trigger the connection between the communication device and the shared network slice SLopt.

[0135] Refer to later Figure 5 The functions of modules 3A to 3C of management entity 3 are described in more detail. The figure illustrates the main steps of a method for managing access to network slices according to the present invention.

[0136] Finally, when the hardware architecture of computer 6 is that of a communication device (e.g., communication device 5) according to the present invention, the program according to the present invention stored in the non-volatile memory (NVM) of computer 6 is program PROG-5, which includes instructions defining the main steps of the method for accessing the service according to the present invention. Program PROG-5 defines the functional modules of communication device 5 (in... Figure 1(As shown in the diagram), these functional modules are based on and / or control all or part of the components PROC, MEM, ROM, NVM, and COM of the aforementioned computer 6. In an example of service S, these functional modules include:

[0137] - Sending module 5A, configured to send an access request for accessing service S to application server 4; and

[0138] - Receiving module 5B, which is configured to receive a notification from application server 4, which informs communication device 5 that at least one management measure for managing the environmental and / or energy impacts attributable to service S will be applied to traffic applications related to service S from or to communication device 5, the management measure being taken after application server 4 receives a notification from network controller 2 indicating that the at least one indicator IND does not meet compliance standard CRIT.

[0139] Refer to later Figure 6 The functions of modules 5A and 5B of the communication device 5 are described in more detail. The figure illustrates the main steps of the method for accessing services according to the present invention.

[0140] Now refer to Figures 3 to 6 This describes the main steps performed by the components of System 1 (network controller 2, application server 4, management entity 3, and communication device 5) when they function within the collaborative mechanism proposed in this invention to control / manage the environmental and / or energy impacts attributable to service S. More specifically, Figure 3 The main steps of the monitoring method according to the present invention, implemented by the network controller 2, are shown. Figure 4 The main steps of the method for managing services according to the present invention, implemented by application server 4, are shown. Figure 5 The main steps of a method according to the invention for managing access to network slices, implemented by management entity 3, are shown, and Figure 6 The main steps of a method for accessing a service according to the present invention, implemented by communication device 5 in a particular embodiment, are shown.

[0141] In the specific embodiments described herein, when a service S is provided via a network NW supporting multiple network slices, particular attention is paid to the environmental impact attributable to service S, and especially to its carbon footprint (a metric representing the environmental impact attributable to service S in the context of this invention). In this context, the collaborative mechanism proposed in this invention is hereinafter referred to as the COSINUS (Carbon Optimized Slice Network with Scheduled Service Continuity) process or service.

[0142] This invention can, of course, be conceived in other contexts, as previously described, and can be applied to the energy impact of a control service S, or its environmental impact and its energy impact. There are no limitations on the nature or number of indicators that can be used to measure such impact. Therefore, in addition to carbon footprint, energy consumption, energy supply costs, traffic volume indicators, environmental indicators (e.g., temperature of network equipment), descriptions of one or more energy sources used (e.g., batteries, nuclear power plants, UPS), deployment sustainability factors (DSF), etc., can also be considered as indicators.

[0143] In the embodiments described herein, it is assumed that in the initial stage (corresponding to...) Figure 3 Step E10 and Figure 4 In step F10), network controller 2 and application server 4 dynamically negotiate and implement the COSINUS process for service S and network NW, for example, via a dedicated application programming interface (API) (here referred to as COSINUSAPI). To expose and use the COSINUS API, network controller 2 and application server 4 use, for example, the dynamic negotiation protocol CPNP (Connectivity Provisioning Negotiation Protocol), which is described in RFC 8921, entitled "Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)," published by the IETF in October 2020 by M. Boucadair et al. As a variant, protocols other than CPNP can be used, such as the RESTCONF protocol described in IETF document RFC 8040, entitled "RESTCONF Protocol," published by A. Bierman et al. in January 2017.

[0144] During this negotiation phase, application server 4 specifically sends a subscription message to network controller 2 via the COSINUS API in order to benefit from the COSINUS process of service S. This subscription message contains at least one IP address (and possibly a port number, domain name, etc.) used to contact (and thus notify) application server 4. In the example of a PCP server exposed by application server 4, this IP address (and, where applicable, the port number) may be encoded in the "Contact_Locator" field of the PCP subscription message.

[0145] Network controller 2 accepts subscriptions from application server 4 and sends it an identifier (e.g., AS4_id) using the COSINUS API. This identifier is assigned by the network NW (e.g., by network controller 2) to unambiguously (i.e., explicitly) identify application server 4 on the network NW during the COSINUS process. Here, network controller 2 also provides application server 4 with a range of IP addresses (IPv4 and / or IPv6) or prefixes of the network NW intended for use by communication devices when accessing service S.

[0146] In a variant embodiment, the identifier AS4_id is generated by the application server 4 itself and provided to the network controller 2 in its subscription message. In this variant, the application server 4 appropriately executes a program to ensure that the identifier AS4_id is globally unique across the multiple networks (including network NW) through which services S can be provided.

[0147] In yet another variant, the identifier AS4_id may be generated by a third-party entity (such as IANA or the Internet Number Assignment Authority) and provided by that third-party entity to network controller 2 and / or application server 4.

[0148] During the negotiation / subscription phase, the information exchanged between the network controller 2 and the application server 4 is stored by these units, for example, in a table named AS_COSINUS_SUBERS stored in the network NW for the network controller 2 (so that it can be accessed by network entities that play a part in the COSINUS process, such as, in particular, management entity 3), and in a table named NTW_COSINUS_SUBSCRIPTIONS for the application server 4, which is stored locally in its memory NVM.

[0149] It should be noted that this negotiation / subscription phase between network controller 2 and application server 4 can be repeated between network controller 2 and other application servers associated with services other than service S, and / or between application server 4 and other network controllers of networks (other than network NW) through which service S can be provided. Therefore, the AS_COSINUS_SUBSCRIBERS table maintained by network controller 2 summarizes all information exchanged with application servers (including application server 4) that have subscribed to the COSINUS procedure from network controller 2 for services associated with them and provided via network NW, and the NTW_COSINUS_SUBSCRIPTIONS table maintained by application server 4 summarizes all information exchanged with network controllers of networks (including network controller 2 of network NW) that have subscribed to the COSINUS procedure for service S.

[0150] For each application server 4 referenced in the AS_COSINUS_SUBSCRIBERS table, the network NW operator (through network controller 2 or another entity in the network) establishes or configures filters (used to identify traffic associated with service S) and probes deployed in the network NW to collect information reflecting the environmental and / or energy impact of service S. For example, the filters involve the IP addresses of different service instances of application server 4 involved in providing service S; these IP addresses are, for example, transmitted by application server 4 to network controller 2 during the negotiation / subscription phase.

[0151] In the embodiments described herein, the information collected by detectors deployed in the network NW reflects the carbon consumption of all communications established to or to service instances of one or more application servers involved in providing service S. It should be noted that application server 4, although associated with service S, is not necessarily directly involved in providing the service. However, for simplicity, it is assumed here that application server 4 not only manages access to service S but also provides said service, and is the only application service involved in that provision.

[0152] In variant embodiments, it is conceivable to collect information reflecting the environmental and / or energy impacts of service S that are associated only with certain communications (e.g., with certain types of traffic, with a specific set of users, etc.).

[0153] Information reflecting the environmental and / or energy impact of service S, specifically collected by the detectors and through filters provided by the application, is transmitted to network controller 2 (step E20), which then aggregates it to estimate at least one indicator IND representing the environmental and / or energy impact of service S (step E30). Network controller 2 may obtain this information from the detectors, for example, using protocols known as NETCONF or IPFIX. The information reflecting the environmental and / or energy impact of service S collected by the detectors may be obtained and aggregated by network controller 2 (via its estimation module 2A) continuously, quasi-continuously, or periodically.

[0154] In the hypothetical example described here, as previously stated, network controller 2 estimates the carbon footprint attributable to service S as an indicator IND. For this purpose, network controller 2 uses, for example, the known so-called LCA (Life Cycle Assessment) method or a simplified LCA method, such as those described in the paper entitled “Assessing the carbon footprint of the data transmission on a backbone network” presented by M. Ficher et al. at the 24th Cloud, Internet and Network Innovation Conference (ICIN 2021) in 2021.

[0155] Of course, other metrics for estimating the environmental and / or energy impacts of service S and other methods for estimating these metrics can be envisioned, such as energy consumption attributable to service S in network NW, battery state, etc. Examples of such metrics (or measures) are specifically described in the paper entitled "Green Networking Metrics" by A. Clemm et al., published by the IETF on June 16, 2023. Various methods for estimating such indicators are described in particular in the following literature: IETF document RFC 7577 entitled "Definition of ManagedObjects for Battery Monitoring" by J. Quittek et al., published in July 2015; IETF document RFC 7460 entitled "Monitoring and Control MIB for Power and Energy" by M. Chandramouli et al., published in October 2015; or OPSA working group document entitled "Power and Energy Efficiency" by J. Lindblad et al., published on October 20, 2023.

[0156] In addition, in variant embodiments, network controller 2 may estimate multiple indicators IND that collectively reflect the environmental and / or energy impact of service S (e.g., indicator IND(1) representing the carbon footprint of service S and indicator IND(2) representing its energy consumption).

[0157] Then, network controller 2 (e.g., here via its estimation module 2A) determines whether the estimated metric IND meets a given compliance criterion (here, criterion CRIT), that is, a predetermined or predefined compliance criterion (test step E40). For example, network controller 2 compares the metric IND with a threshold defined for the metric IND and for service S, and checks whether the metric IND has exceeded the threshold. Typically, in the carbon footprint example, network controller 2 checks whether the carbon footprint has exceeded a threshold corresponding to a certain maximum value that the network NW (i.e., the network operator) accepts (or desires or authorizes) for such a carbon footprint for service S. This maximum value may specifically correspond to a carbon footprint quota that the network has allocated to service S and that service S must not exceed. Thus, in this illustrative example, compliance criterion CRIT is a carbon footprint exceeding the threshold / quota in question. Of course, this is only an illustrative example, and other compliance criteria can be envisioned depending on the metric under consideration (e.g., exceeding a minimum threshold, specific changes in the metric, etc.).

[0158] If the indicator IND meets the compliance standard CRIT (the "Yes" response in test step E40), then the network controller 2 repeats the steps of obtaining E20, estimating E30, and comparing E40 with the compliance standard CRIT.

[0159] If indicator IND (or one of indicator INDs) does not meet compliance criterion CRIT (the "No" response in test step E40), network controller 2 notifies application server 4 (and more specifically its PCP server) via its notification module 2B that indicator IND does not meet compliance criteria; in other words, in the carbon footprint example, the carbon footprint exceeds the quota allocated to service S by network NW (step E50). Network controller 2 obtains the information needed to reach application server 4 (and more specifically its PCP server) by consulting the AS_COSINUS_SUBSCRIBERS table. Here, the notification sent by network controller 2 to application server 4 further instructs application server 4 on the management measures required for managing the environmental and / or energy impact (i.e., its carbon footprint) of service S.

[0160] In a variant embodiment, it is conceivable that network controller 2 also sends intermediate notifications to application server 4 each time the metric IND crosses various intermediate thresholds (e.g., 50% of the quota allocated to service S, and then 75% of that quota).

[0161] refer to Figure 4After the receiving module 4A of application server 4 has received a notification from network controller 2 (step F20), application server 4 triggers at least one management measure ACT (step F30) via its triggering module 4B to manage the environmental and / or energy impacts attributed to service S (i.e., its carbon footprint). This one or more management measures may involve all or part of the traffic related to service S exchanged via network NW. The management measure may specifically be a measure to limit or neutralize the environmental and / or energy impacts attributed to service S, or any other management measure designed to control the environmental and / or energy impacts attributed to service S.

[0162] In the embodiment described herein, the management measure ACT triggered by application server 4 is a programmable scheduling mechanism. This mechanism is based on the shared use of one or more given resources of network NW by these communication devices during access to service S by these communication devices, and on time-based scheduling of access to the shared one or more resources by the communication devices in question. Other examples of conceivable management measures have been previously described.

[0163] More specifically, in the example of the streaming video service S considered here by way of illustration, the shared resource is a dedicated network slice SLopt supported by the network NW, where the video stream is distributed in a multicast transmission mode (referred to as programmed multicast distribution or time-slot-based multicast) by means of defined time slots. This transmission mode is advantageous for simultaneously sending the same video content to multiple communication devices during defined time slots (e.g., fixed time slots of 1 minute, 5 minutes, 15 minutes, etc.). This mode of programmed multicast distribution of data is more efficient in terms of environmental and / or energy impact than the mode of immediate unicast transmission of data, in which the same content is copied to each communication device.

[0164] To establish this programmatic distribution pattern, application server 4, through its triggering module 4B, selects one or more time slots (each time slot identified here by an identifier called `content_id`) for each video content to be distributed, provided by service S. The application server allocates these one or more time slots for transmitting data related to the video content via a shared network slice SLopt. This or the time slots associated with the video content `content_id` are then assigned (distributed among these communication devices) to communication devices wishing to access the video content in question via service S. Multiple communication devices requesting access to the video content during a given time interval may be assigned the same time slot `slot_id` for accessing the content, and thus access the content simultaneously. Therefore, the sharing of the network slice SLopt takes the form of multiple communication devices using the network slice simultaneously. This is equivalent to determining a time-based schedule, according to which the communication device in question will use the network slice SLopt to access service S, and more specifically, access the video content `content_id`.

[0165] Then, application server 4 notifies network controller 2 via its notification module 4C (and possibly via an API provided for this purpose) that it has triggered one or more management measures ACT (step F40) to control (e.g., reduce) the environmental and / or energy impacts attributable to service S. In the example envisioned here, application server 4 thus informs network controller 2 of the shared use of network slice SLopt by multiple communication devices accessing service S and the schedule selected for such shared use by sending an ACTIVATE(SLopt, SCHEDULE) message to the network controller, whereby SCHEDULE specifies information representing the schedule and, more specifically, the association between content_id and slot_id. The validity period can be associated with the management measure and transmitted in the ACTIVATE message, for example, the time when the indicator IND attributable to service S meets compliance criteria or is reset for application server 4 and / or service S.

[0166] In the embodiments described herein, after receiving an ACTIVATE notification (the "Yes" response in test step E60) informing its application server 4 to trigger one or more management measures, network controller 2 configures at least one entity of the network to support the management measure (step E70). More specifically, in the example contemplated herein, in step E70, configuration module 2D of network controller 2 configures the edge nodes (or BRs (border routers)) of the network NW with updated traffic classification rules, such that data packets related to service S received from or intended for application server 4 are associated with network slice SLopt. The identifier content_id associated with each data stream (video content stream in the example contemplated herein) transmitting data packets related to service S is shared with network controller 2 and the edge nodes BR configured by the network controller, enabling them to identify the associated streams, which are received from application server 4 and transmitted via network slice SLopt in multicast transmission mode.

[0167] Network controller 2 confirms that the management measures transmitted by application server 4 have been considered, and that the edge node BR of network NW has been configured to allow the implementation of such management measures (step E80). Therefore, upon receiving this confirmation (step F50), application server 4 can provide service S via its providing module 4E, and more specifically, in the example envisioned here, can perform programmed distribution of one or more streams of video content_id to network slice SLopt in multicast mode according to the scheduling SCHEDULE selected by application server 4 in step F30 (step F60). Then, in network NW, data is routed to communication devices connected to network NW that have subscribed to the corresponding one or more multicast groups using a multicast distribution tree deployed in network slice SLopt for each association between the identifier content_id in the scheduling SCHEDULE and one or more identifiers slot_id.

[0168] As a variant, one could envision a distribution tree with multiple different contents (that is, multiple identifiers content_id).

[0169] In the embodiments described herein, if the network controller 2 is not notified (i.e., informed) by the application server 4 to trigger management measures for managing environmental and / or energy impacts attributable to service S (the "No" response in test step E60) at the end of the defined time period denoted as Tmax, it activates processing in the network NW in response to the indicator IND failing to meet the compliance criterion CRIT on all or part of the traffic related to service S (step E90). This processing is intended, for example, to reduce or neutralize the environmental and / or energy impacts attributable to service S. For this purpose, in the embodiments described herein, the triggering module 2D embedded in the network controller 2 triggers a default management measure ACT-DEF, which includes switching all or part of the traffic related to service S flowing through the network NW to a network slice denoted as SL-LBE determined from the network slices SL1, ..., SLK supported by the network NW, which provides a degraded service level compared to the expected service level for service S. This degraded service level is, for example, the service quality level best suited to the conditions for accessing the service, and is more commonly specified as best-effort, or a service level below that "best-effort" service level, also specified as LBE (below best-effort). Of course, other alternatives are conceivable. Activation step E90 accompanies the network controller 2 configuring the edge node BR of the network NW (and more specifically, the access network) via its configuration module 2D, whereby the traffic classification rules are updated so that traffic related to service S is associated with that network slice SL-LBE (step E100). This configuration of the edge node BR can be performed directly or indirectly via the controller. The updated classification rules are also transmitted to the communication devices accessing service S.

[0170] In addition, the network controller 2 can inform the application server 4 via its notification module 2C that traffic related to service S will subsequently be reclassified at the entry point of the network NW so that it can be directed (routed) to the network slice SL-LBE (step E110).

[0171] Furthermore, in the embodiments described herein, once network controller 2 detects that the indicator IND representing environmental and / or energy impact meets compliance criterion CRIT (e.g., after the administrative action ACT-DEF has been triggered, the environmental and / or energy impact attributable to service S has decreased, or the indicator IND has been reset), network controller 2 cancels the processing that was default activated by its module 2D in step E90 (in other words, the default administrative action ACT-DEF). In the example envisioned here, this takes the form of reinstalling the network slice typically used to access service S (and configuring the edge nodes BR accordingly).

[0172] As a variant, in the absence of management measures for managing the environmental and / or energy impacts of service S triggered by application server 4, network controller 2 may activate other processes. For example, the network controller may activate the relabeling of traffic related to service S to store it in another queue, activate rate limiting or rejection of all or some data packets related to service S, activate the redirection of data packets related to service S to a forced portal, etc.

[0173] Now refer to Figure 4 , Figure 5 and Figure 6 Demonstrate the triggering of one or more management actions (ACTs) for managing the environmental and / or energy impacts attributable to Service S, and more specifically, the form that takes place on communication devices accessing Service S, and more specifically on communication device 5.

[0174] In the embodiments described herein, reference is made to Figure 6 Initially, it is assumed that communication device 5 discovers (step G10) at least one management entity 3 for managing network slices supported by network NW. This management entity may be involved in the COSINUS process and, in particular, in certain management measures taken to reduce (or even neutralize) the environmental and / or energy impacts (here, typically its carbon footprint) attributable to service S. One or more management entities 3 may exist in network NW for implementing the COSINUS process (also referred to herein as "COSINUS repeaters"). However, for simplicity, a single network slice management entity 3 according to the invention, i.e., a single COSINUS repeater, is considered here in network NW.

[0175] It was discovered that step G10 can be implemented in different ways.

[0176] Therefore, in the first variant embodiment, the management entity 3 can be configured on the communication device 5 by the network NW (that is, by its operator). For example, the network NW supplies the communication device 5 with at least one IP address and port number associated with the network slice management entity 3 and allows access to the network slice management entity. As a variant, the network can also supply the communication device 5 with an authentication identifier (or ADN (Authentication Domain Name)) associated with the management entity 3 to allow the communication device to authenticate itself to the management entity. This configuration by the network NW can be performed using a dedicated protocol (such as DHCP (Dynamic Host Configuration Protocol)) or via Router Advertisement (RA) messages.

[0177] In the second variant, communication device 5 can use anycast or multicast addresses to send discovery messages related to network slice management entity 3 operating in network NW. Management entity 3 then responds to the discovery messages by sending, for example, an IP address and port number (and, where applicable, an authentication identifier), as described in the first variant.

[0178] In the third variant, communication device 5 may use a Special Purpose Domain Name (SUDN), as described in RFC 6761, entitled "Special-Use Domain Names," published by the IETF in February 2013 by S. Cheshire et al., and request domain name resolution associated with that reserved domain name to obtain a Resource Record (RR) of type SVCB from management entity 3, as described in IETF RFC 9460, entitled "Service binding and parameter specification via the DNS (DNS SVCB and HTTPSSVC)," published by B. Schwartz et al. in November 2023. For example, suppose the SVCB record RR from management entity 3 according to the invention includes the parameter "SvcParam," which is defined for the purposes of the invention and named COSINUS herein, indicating the management entity 3's support for the COSINUS procedure. The SVCB RR may also include a list of network slice types and / or identifiers managed by management entity 3.

[0179] After the application server 4 has triggered the management action ACT in step F30 described above, the application server 4 continues as follows for communication devices connected to the network NW via the network NW access service S.

[0180] Therefore, assume that communication device 5 sends an access request REQ-S for accessing service S to application server 4 via its sending module 5A (step G20), and more specifically, in the illustrative example of the streaming video service S contemplated here, an access request for streaming access to video content CONT is sent. The request REQ-S is sent by communication device 5 via the network slice to which it is connected (e.g., network slice SL1 here). The access request REQ-S includes a source IP address provided to communication device 5 by network NW and within the IP address range provided by network controller 2 when application server 4 subscribes to the COSINUS process (steps E10 / F10 described previously).

[0181] Upon receiving the access request REQ-S (step F61), Figure 4 Following this, application server 4 extracts the source IP address from the access request REQ-S and verifies whether the IP address corresponds to the IP address range recorded in the NTW_COSINUS_SUBSCRIPTIONS table maintained by application server 4. The application server also verifies whether it has received a non-compliance notification from network controller 2 of network NW indicating an environmental and / or energy impact attributed to service S (test step F62).

[0182] If application server 4 does not find an entry in the NTW_COSINUS_SUBSCRIPTIONS table, or does not receive a notification for service S from controller 2 of network NW (the "No" response in test step F62), then network NW and application server 4 process the access request REQ-S for accessing service S in the usual manner, and then process the data packets exchanged as part of the access to service S (to or from communication device 5), that is, by using network slices in network slices SL1, ..., SLK supported by network NW, which are connected to communication device 5 and adapted to service S in a manner known per se, such as network slice SL1 (step F63).

[0183] In the example envisioned here, a notification has been received from the network controller 2 of the network NW in step F20, and in response to the notification, the application server 4 has triggered the management action ACT in step F30 to manage the environmental and / or energy impacts attributed to service S.

[0184] If application server 4 finds an entry in the NTW_COSINUS_SUBSCRIPTIONS table and has received notification of non-compliance with environmental and / or energy impacts (the "Yes" response in test step F62), as in the example envisioned here, then the management action ACT triggered by application server 4 is applied to the traffic related to service S exchanged with communication device 5 (that is, the traffic transmitted by communication device 5 and the traffic intended for communication device 5 as part of its access to service S). More specifically, in the illustrative example envisioned here, the traffic related to service S (specifically video content CONT) associated with communication device 5 is transmitted via a shared network slice SLopt, and the supply of this traffic to communication devices sharing the network slice SLopt is organized according to a scheduling SCHEDULE determined by application server 4, that is, during a time slot identified by a slot_id associated with the identifier content_id corresponding to video content CONT (step F64). Therefore, application server 4 selects a time slot identified by slot_id for communication device 5 to allow the communication device to access content CONT.

[0185] In the embodiment described herein, application server 4 then notifies (i.e., informs) communication device 5 via its notification module 4C of the management measures ACT triggered and applied to traffic related to its associated service S, i.e., traffic transmitted to or from communication device 5. In the example envisioned here, notification module 4C sends a notification message to communication device 5 informing it of the use of the shared network slice SLopt when communication device 5 accesses service S and the allocation of a slot_id for transmitting content_id via network slice SLopt (step F65). Here, in addition to the identifier of the shared network slice SLopt, the notification message also includes an indication, according to which communication device 5 desires to receive streaming video content CONT, for example, not immediately in response to the access request REQ-S for accessing service S, but distributed to the shared network slice SLopt at a specified time (e.g., 30 seconds, 1 minute, 3 minutes) corresponding to the identifier slot_id.

[0186] It should be noted that in the embodiments described herein, a static scheduling scheme is envisioned, determined by application server 4 and transmitted upstream to controller 2 in step F40 for accessing (strictly speaking) service S. However, this does not preclude such scheduling from changing over time (and therefore application server 4 from sending multiple messages to controller 2 reflecting such changes), particularly based on access requests received by application server 4 from communication devices. Furthermore, as a variation, it is envisioned that application server 4 dynamically determines its envisioned scheduling scheme for accessing service S via network slice SLopt from the communication device in question, based on requests for accessing service S received from the communication device during, for example, a defined time interval.

[0187] Communication device 5 confirms that it has received the notification message (step G30) and takes it into account (step G40).

[0188] Upon receiving the confirmation, application server 4 adds communication device 5 to the list of communication devices receiving video content CONT distributed on the shared network slice SLopt, located in its local cache, for example, in its non-volatile memory NVM, and obtains an identifier for communication device 5, denoted as ID5. For example, this identifier ID5 is randomly generated by application server 4 for communication device 5, such as by a module (or service instance) responsible for managing all connections between communication devices and application server 4. As a variant, an identifier for communication device 5 generated per connection or per service session can be envisioned; this variant can be adopted depending on the nature of the service, for example, in the case where the service is transactional.

[0189] Application server 4 sends its own identifier AS4_id, an identifier ID5 generated for communication device 5, an identifier slot_id indicating the time slot allocated to communication device 5 for transmitting traffic related to service S associated with the communication device according to the multicast transmission mode, and an identifier content_id associated with the video content CONT (step F66). Furthermore, application server 4 creates a context associated with communication device 5 in its local cache, where it stores the identifier ID5, slot_id, and content_id.

[0190] Application server 4 operates in the same manner as other communication devices that wish to access the same content as communication device 5 and are subject to management measures ACT.

[0191] After communication device 5 has received these identifiers (step G50), it sends an access request REQ-SLopt to management entity 3 (COSINUS repeater) for accessing the shared network slice SLopt to manage the network slice (and specifically the network slice SLopt) supported by network NW discovered in discovery step G10 (step G60). Alternatively, discovery step G10 can be performed by communication device 5 at any time, after receiving the identifiers provided by application server 4 in step G50 or before that receiving step.

[0192] In the embodiments described herein, the access request REQ-SLopt for accessing the shared network slice SLopt takes the form of a subscription request for subscribing to a multicast group whose multicast distribution tree is associated with identifiers slot_id and content_id and is deployed within the network slice. It is assumed that the multicast group address corresponding to the deployment of the distribution tree has previously been distributed by management entity 3. In the described embodiments, the access request sent by communication device 5 includes various identifiers (ID5, AS4_id, slot_id, and content_id) provided to communication device 5 by application server 4.

[0193] In one embodiment, when the network NW uses the IPv6 protocol, the subscription request sent is an "MLD Report" message of the MLD (Multicast Listener Group) protocol, which has been modified for the purposes of this invention to specifically include the aforementioned identifiers. When the network NW uses the IPv4 protocol, this message may be an IGMP (Internet Group Management Protocol) message. In another embodiment, the access request for accessing the shared network slice SLopt takes the form of a regular MLD report subscription request for subscribing to the multicast distribution tree, accompanied by a message according to the ICMPv6 (Internet Control Message Protocol version 6) protocol, thereby transmitting various identifiers (ID5, AS4_id, slot_id, and content_id) that will be provided to the communication device 5 by the application server 4. The purpose of the ICMPv6 message is to trigger the management entity 3 to send an "MLD Query" message. This MLD message is typically sent by the router to which the device is connected, under the control of the management entity 3.

[0194] refer to Figure 5 The management entity 3 receives the request REQ-SLopt from the communication device 5 via its receiving module 3A (step H10). The management entity 3 extracts the identifiers ID5, AS4_id, slot_id, and content_id contained in the request REQ-SLopt, and performs various verifications based on these identifiers (step H20).

[0195] More specifically, in the embodiment described herein, management entity 3 queries the AS_COSINUS_SUBSCRIBERS table stored in the network NW and determines whether an entry in the table is associated with the identifier AS4_id. Where applicable, management entity 3 retrieves from the AS_COSINUS_SUBSCRIBERS table information for reaching application server 4 (IP address, and, where applicable, particularly the port number of the PCP server used by application server 4, provided by the application server in the "Contact_Locator" field during the initial negotiation / subscription phase with network controller 2).

[0196] Then, management entity 3, via its verification module 3B, uses the obtained information to verify with the PCP server of application server 4 whether communication device 5 is indeed authorized (has the right) to access network slice SLopt. In the embodiment described herein, for this purpose, the verification module 3B of management entity 3 sends a PCP request to the PCP server of application server 4, which includes an option referred to herein as COSINUS_OP, defined for the purposes of this invention, which includes identifiers ID5, AS4_id, slot_id, and content_id. Figure 7 This demonstrates an example of the format for this option, with the option code TBA (to be assigned) provided by IANA in a standardization context.

[0197] refer to Figure 4 Upon receiving a PCP request from management entity 3, the PCP server of application server 4 (and more specifically, the verification module 4D integrated within the PCP server) verifies whether the context corresponding to the identifier ID5, slot_id, and content_id received in the PCP request is maintained in the local cache of application server 4 (step F67). If application server 4 does not maintain the context corresponding to identifier ID5, slot_id, and content_id, the verification module 4D of application server 4 sends an error message to management entity 3, indicating that communication device 5 is not authorized to use the shared network slice SLopt. Management entity 3 rejects the request REQ-SLopt from communication device 5 through its verification module 3B. The management entity may also inform the dedicated platform.

[0198] Conversely, if application server 4 maintains a context corresponding to identifier ID5, slot_id, and content_id, then verification module 4D sends an affirmative response to management entity 3 confirming that communication device 5 is authorized to access shared network slice SLopt.

[0199] Upon receiving the affirmative response, the management entity 3 accepts the request REQ-SLopt (and thus accepts the subscription request for subscribing to the multicast distribution tree associated with the shared network slice SLopt) (step H30), and triggers the connection between the communication device 5 and the shared network slice SLopt via its triggering module 3C (step H40).

[0200] In this embodiment, the connection between communication device 5 and the shared network slice SLopt is triggered by management entity 3, that is, triggered at the initiative of network NW. As a variant, it is conceivable that communication device 5 initiates its connection with the shared network slice SLopt, and before or simultaneously with sending its subscription request for subscribing to the multicast distribution tree associated with the shared network slice SLopt, the connection request of communication device 5 may be sent to the appropriate entity of the network NW that manages the network slice SLopt (e.g., management entity 3 or another management entity for managing the network slice SLopt).

[0201] After communication device 5 has connected to the shared network slice SLopt (step G70), communication device 5 accesses service S via the shared network slice SLopt (step G90). More specifically, in the example of the video streaming service envisioned here, the video content identified by the identifier content_id is transmitted by the providing module 4E of application server 4 to communication device 5 via the shared network slice SLopt in the time slot identified by the identifier slot_id. Figure 5 (Step F68 in the text). Therefore, the time slot identified by slot_id is used to simultaneously transmit the video content CONT to multiple communication devices (including communication device 5) via network slice SLopt.

[0202] Once controller 2 has detected that the indicator IND, which represents the environmental and / or energy impact attributable to service S, has met the standard CRIT, management measures ACT can be permanently implemented or deactivated.

Claims

1. A monitoring method performed by a network controller (2) of a network, the method comprising: - Step (E30) to estimate at least one indicator (IND) attributable to the environmental and / or energy impacts of services provided via the network. as well as - If at least one metric does not meet a given compliance criterion (CRIT), then notify the application server associated with the service that the metric does not meet the compliance criterion (E50).

2. The monitoring method of claim 1 further includes, in response to the failure of the compliance standard to be met, activating at least one processing (ACT-DEF) in the network for all or part of the traffic related to the service if the application server has not triggered at least one management measure for managing the environmental and / or energy impacts at the end of a defined period after the application server is notified (E90).

3. The monitoring method as described in claim 2, wherein, The at least one process (ACT-DEF) includes switching all or part of the traffic flowing through the network related to the service to a network slice (SL-LBE) that provides a degraded service level compared to the expected service level for the service.

4. The monitoring method according to any one of claims 1 to 3, wherein, The estimation step (E30) includes receiving (E20) at least one piece of information from at least one detector deployed in the network, the at least one piece of information reflecting the environmental and / or energy impact of at least one communication related to the service, the at least one communication being established from or to a server involved in providing the service.

5. The monitoring method according to any one of claims 1 to 4, further comprising: - The step of receiving from the application server a notification indicating that at least one given resource (SLopt) of the network is shared by the communication devices during access to the service by multiple communication devices; as well as - The step of configuring at least one entity of the network to allow the shared use (E70).

6. The monitoring method as described in claim 5, wherein, The at least one given resource includes a given network slice (SLopt) supported by the network, and the notification received from the application server includes information indicating that the communication device is scheduled to access the service via the network slice (SCHEDULE).

7. A method for an application server (4) to manage services provided via at least one network, the method comprising: - The step of receiving, from the network controller (2) of the network, a notification indicating that at least one indicator estimated by the network controller, representing the environmental and / or energy impact attributable to the service, does not meet a given compliance criterion (F20); and - Step (F30) to trigger at least one management action (ACT) for managing the environmental and / or energy impacts, the management action relating to all or part of the traffic related to the service.

8. The management method as described in claim 7, wherein, The at least one management measure is selected from at least the following: - Use encoding of data related to the service, where the encoding contributes less to the environmental and / or energy impacts attributable to the service than the current encoding; -Restrict access to the service via the network; -Schedule access to the service from multiple communication devices; - During the access to the service by multiple communication devices, at least one given resource of the network is shared by the communication devices; - Tag traffic associated with the service to store it in at least one queue.

9. The management method of claim 7 or 8, further comprising, when the at least one management action (ACT) includes scheduling access to the service by multiple communication devices, the step of selecting a slot (slot_id) to be allocated to the at least one communication device for accessing the service after the at least one communication device requests access to the service.

10. The management method according to any one of claims 7 to 9, wherein, The at least one management measure includes the shared use of a given network slice (SLopt) supported by the network by multiple communication devices during access to the service, according to a determined schedule.

11. The management method of claim 10, comprising at least one step selected from the following: - The step (F40) of informing the network controller, according to the determined schedule, of the communication device's shared use of the given network slice; and - The step of informing the communication device of the given network slice to be shared by the communication device during access to the service and informing the determined schedule to be applied (F65).

12. The management method of claim 10 or 11 further includes the step of receiving a request from the entity (3) of the network for verifying whether the communication device (5) is authorized to access the given network slice (SLopt) (F67).

13. The management method as described in any one of claims 7 to 12, comprising: - Step (F61) to receive an access request for accessing the service from the communication device (5); - If the communication device is affected by the management measures, then apply the management measures to the service-related traffic from or to the communication device (F64).

14. A method for an entity (3) of a network to manage access to a network slice supported by said network, the method comprising: - The step (H10) of receiving an access request from a communication device (5) for accessing a given network slice (SLopt) supported by the network, wherein the network slice is shared among multiple communication devices accessing the service after the application server associated with the service provided via the network receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller, representing the environmental and / or energy impact attributable to the service, does not meet a given compliance criterion; - The step of verifying with the application server associated with the service whether the communication device is authorized to access the shared given network slice (H20). as well as - Where applicable, the step of triggering the connection between the communication device and the shared given network slice (H40).

15. A method for accessing a service (S) provided via a network by a communication device (5), the method comprising: - The step of sending an access request for accessing the service to the application server (4) associated with the service (G20); - Step G30: Receive a notification from the application server, the notification informing the communication device that: after the application server receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller representing the environmental and / or energy impact does not meet a given compliance criterion, at least one management measure for managing the environmental and / or energy impact attributable to the service will be applied to traffic related to the service from or to the communication device.

16. The access method as described in claim 15, wherein, The at least one management measure includes shared use of a given network slice supported by the network by multiple communication devices, including the communication device, according to a determined schedule during access to the service, and the method includes: - The step (G60) of sending an access request to an entity in the network for accessing a given network slice (SLopt) of the shared network; and - The step of accessing the service via the shared given network slice after the communication device has been connected (G80) to the shared given network slice (G90).

17. A network controller (2) for a network, comprising: - An estimation module (2A) is configured to estimate at least one indicator representing the environmental and / or energy impacts attributable to services provided via the network; as well as - Notification module (2B), which is activated when at least one estimated metric fails to meet a given compliance criterion, and is configured to notify the application server associated with the service that the at least one metric fails to meet the compliance criterion.

18. An application server (4) configured to manage services provided via at least one network, the application server comprising: - A receiving module (4A) is configured to receive from the network controller of the network a notification indicating that at least one indicator estimated by the network controller, representing the environmental and / or energy impacts attributable to the service, does not meet a given compliance criterion. as well as - Triggering module (4B), the triggering module being configured to trigger at least one management measure for managing the environmental and / or energy impacts, the management measure involving all or part of the traffic related to the service.

19. A network entity (3) configured to manage access to network slices supported by the network, the entity comprising: - A receiving module (3A) is configured to receive from a communication device an access request for accessing a given network slice supported by the network, wherein the network slice is shared among multiple communication devices accessing the service after an application server associated with a service provided via the network receives from the network controller of the network a notification indicating that at least one metric estimated by the network controller, representing the environmental and / or energy impacts attributable to the service, does not meet a given compliance criterion. - Verification module (3B), the verification module is configured to verify with the application server associated with the service whether the communication device is authorized to access the shared given network slice; as well as - Trigger module (3C), which is activated where applicable and configured to trigger a connection between the communication device and the shared given network slice.

20. A communication device (5), comprising: - Sending module (5A), the sending module being configured to send an access request for accessing the service to an application server associated with a service provided via the network; as well as - A receiving module (5B) is configured to receive a notification from the application server, the notification informing the communication device that: after the application server receives a notification from the network controller of the network indicating that at least one indicator estimated by the network controller representing the environmental and / or energy impact does not meet a given compliance criterion, at least one management measure for managing the environmental and / or energy impact attributable to the service will be applied to traffic related to the service from or to the communication device.

Images