Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F9/45533—Hypervisors; Virtual machine monitors
  • G06F9/45558—Hypervisor-specific management and integration aspects
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/12—Discovery or management of network topologies
  • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
  • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/52—Network services specially adapted for the location of the user terminal
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F9/45533—Hypervisors; Virtual machine monitors
  • G06F9/45558—Hypervisor-specific management and integration aspects
  • G06F2009/45562—Creating, deleting, cloning virtual machine instances
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
  • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
  • H04L41/5067—Customer-centric QoS measurements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
  • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
  • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
  • H04L43/0852—Delays
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L43/00—Arrangements for monitoring or testing data switching networks
  • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route

Definitions

• the invention is implemented in a communications network, such as a telecommunications network capable of routing communications data from and to fixed or mobile terminals.
• the invention aims more precisely to dynamically select one or more devices capable of hosting an application intended to be used by a client entity.
• the applications are installed in a durable and fixed manner on devices of a communication network and naming information of the DNS type (in English Domain Name System) or URI (in English Uniform Resource Identifier) makes it possible to identify and attach a device as well as an application installed on a device.
• the devices can be physical equipment or virtualized instances such as virtual machines.
• the development of network virtualization and the implementation of distributed architectures, particularly based on MEC (Mobile Edge Computing) type solutions, aimed at deploying storage and computing infrastructures as close as possible to users is essential. more and more common. These storage and computing infrastructures are also limited in resources and the users are themselves connected in different locations requiring applications to be deployed in a multitude of computing and storage infrastructures.
• On-demand instantiation services to avoid static configuration and installation of applications appear little by little, particularly among entities hosting content, but these offers, although more dynamic, are linked to content and do not make it possible to meet on-demand needs on a geo-distributed infrastructure and do not make it possible to respond in particular to new types of application, such as for example gaming applications while traveling, for example within a vehicle.
• Existing solutions therefore do not make it possible to manage in an economical manner, in particular the access resources of a communication network including the devices hosting the applications, these resources being limited since they are deployed on the periphery of a network infrastructure, while guaranteeing provides the user of an application with optimal quality of service independent of their location.
• solutions relating to the state of the art are quite expensive when an application must be deployed or updated, due to the multitude of PoPs to be updated, generally simultaneously to ensure satisfactory access to a plurality of users.
• the object of the present invention is to provide improvements compared to the state of the art.
• the invention improves the situation using a method for selecting a device suitable for hosting at least one process of an application among a plurality of devices of a communication infrastructure, the application being instantiated at from the at least one process, the method being implemented by an entity for managing the topology of the infrastructure, adapted to manage resources of the plurality of devices, and comprising:
• the selected device further comprising a resource making it possible to satisfy the parameter obtained.
• the selection method is new and inventive since it makes it possible to dynamically use an application, comprising at least one process or executed from at least one process, on one or more selected devices identified as a device. 'accommodation.
• This allows a customer to use the application, such as a data service (audio, video, text, etc.), guaranteeing compliance with the constraints associated with this application.
• the selection of an appropriate device makes it possible to guarantee a satisfactory customer experience for the customer who requested the use of the application and on the other hand a saving in the use of infrastructure resources.
• the method proves to be particularly relevant for applications or services requiring low latency where the position of the device, close to the client entity, and the characteristic or parameter of the service, for example QoS, make it possible to satisfy a latency requirement. specific to the required service.
• the method is particularly relevant because it makes it possible to deploy an application by selecting a device for each of the processes required to instantiate the application, each process being able to have distinct parameters and being able to be hosted more or less far from a client entity.
• certain processes of an application could be installed close to a client entity (for example in an MEC architecture (in English Mobile Edge Computing) while other processes of the application could be installed in the heart of the network of the infrastructure.
• An infrastructure device can correspond independently to a physical device (server, network equipment) or to a virtual machine.
• the client entity has a fairly broad meaning since it can be a client terminal ( PC, smartphone, box, etc.) but the usage request can also be obtained from an infrastructure administration entity, for example to instantiate a network application, also called a network service, in the infrastructure. For example, this may involve instantiating a new routing protocol in a network infrastructure or even a web access service optimization function.
• the method further comprises an instantiation of the at least one process on the selected device.
• the management entity can advantageously instantiate, directly or via another entity of the infrastructure, the process on a device in order to meet the requirements (parameters, location) required.
• the process also makes it possible to be able to best adjust the use of infrastructure resources by deploying applications on demand and thus limiting the use of resources of infrastructure devices.
• the selection method further comprises a transmission to the client entity of an instruction to put the client entity on hold corresponding to the instantiation delay of the at least a process on the selected device.
• At least one entity or device of the infrastructure thus includes a hardware or software component making it possible to put a client entity on hold before the actual instantiation of the application or process on a hosting device.
• the parameter associated with the at least one process belongs to the group comprising:
• the selection method can advantageously be implemented by taking into account one or more parameters.
• device capacity parameters in terms of CPU (in English Central Processing Unit) and/or GPU (in English Graphics Processing Unit) can be taken into account to quantify the resources required for the device or devices to be selected.
• Parameters relating to the process, particularly related to latency and quality of service can be taken into consideration for the selection of the device.
• the selection method further comprises a transmission to the client entity of identification data of the selected device.
• the management entity transmits to the client entity having issued the use request an identification data of the selected device, such as as DNS information (in English Domain Name System), information of the URI type (in English Uniform Resource Identifier), allowing the client entity for example to be able to directly contact this device and therefore the process or even the application.
• an identification data of the selected device such as as DNS information (in English Domain Name System), information of the URI type (in English Uniform Resource Identifier), allowing the client entity for example to be able to directly contact this device and therefore the process or even the application.
• the infrastructure topology management entity uses a weighted directed graph comprising the plurality of infrastructure devices to select the device from the plurality.
• the management entity can advantageously use a weighted directed graph to have improved knowledge of the distance of a device from the client entity and thus consider a distance, not only in relation to a geographical and/or topological distance. , but also in relation to link capacities between devices and/or processing capacities of devices.
• the selection of the device among the plurality comprises:
• the method may include a step of selecting a set of devices from the plurality, this set being at a maximum required distance from the client entity, this maximum distance being determined in relation to a reference value determined for example by the infrastructure operator and making it possible to guarantee a level of quality of service and/or a maximum number of hops for the device to be selected for the application process(es).
• This selection of a device in two stages allows firstly to consider only the eligible devices and then to analyze the hardware and software resources (memory, CPU, processing capacity, etc.) of these eligible devices only, knowing that ineligible devices, even if they had sufficient resources, could not be selected due to their distance from the client entity.
• the reference value corresponds to a number of hops between a device to be selected and the client entity, and/or to a geographical distance between the device to be selected and the client entity, and/or at a distance between the device to be selected and the client entity taking into account a weighting of at least one link and/or at least one function of the infrastructure positioned between the entity client and the device to select in the weighted graph.
• a reference value representing the distance between the client entity and the device to be selected can be represented by a variety of parameters used individually or in combination.
• a number of hops between the client entity and the device to be selected corresponding for example to a number of functions, illustrates the topology of the infrastructure.
• a geographic distance may be relevant if, for example, the infrastructure is centralized and the number of hops provides little information on the distance.
• Taking weighting into account provides improved information on the “distance” since a link or function of the infrastructure (possibly virtualized routing equipment, router, switch, etc.) having better capacities can be more suitable than a device that is closer from a topological point of view but whose lower capacities prove less advantageous in guaranteeing a level of quality of service for the process and therefore for the client entity for example.
• a link or function of the infrastructure possibly virtualized routing equipment, router, switch, etc.
• the method comprises at least one increment of the reference value up to a maximum reference value in the case where no device is selected and for each increment , a determination step and a selection step, according to the embodiment described above.
• the reference value can be increased incrementally up to a maximum value, no longer making it possible to guarantee a quality of experience sufficiently satisfactory for the process and the client entity or exceeding an authorized limit of deployment of the application in the infrastructure. If the maximum value is reached, the process cannot be used and/or instantiated on any device in the infrastructure.
• a single device is selected for a set of processes required for the instantiation of the application, the parameter obtained being relative to all the processes.
• a single device of the infrastructure can advantageously be selected. The selection can then be based on obtaining a parameter relating to the application or all of the processes concerned to determine the suitable device.
• the invention also relates to a device for selecting a device suitable for hosting at least one process of an application among a plurality of devices of a communication infrastructure, the application being instantiated from the at least one process , characterized in that the device is configured to implement:
• the selected device further comprising a resource making it possible to satisfy the parameter obtained.
• This selection device is capable of implementing in all its embodiments the selection process which has just been described.
• the invention also relates to a system for selecting at least one device adapted to host at least one process of an application among a plurality of devices of a communication infrastructure, the application being instantiated from the at least a process, characterized in that the system comprises a selection device, as described above, and a client entity adapted to send the request for use of the application to the selection device.
• the invention also relates to a computer program comprising instructions for implementing the steps of the selection method which has just been described, when this program is executed by a processor and a recording medium readable by a selection device on which the computer program is recorded.
• the above-mentioned program may use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in partially compiled form, or in n any other desirable shape.
• a medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or even a magnetic recording means.
• a storage means such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or even a magnetic recording means.
• Such a storage means can for example be a hard disk, flash memory, etc.
• an information carrier may be a transmissible medium such as an electrical or optical signal, which may be carried via an electrical or optical cable, by radio or by other means.
• a program according to the invention can in particular be downloaded onto an Internet-type network.
• an information carrier may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in executing the method in question.
• FIG 1 presents a network infrastructure in which the selection method is implemented according to one aspect of the invention
• FIG 2 describes an implementation of the selection method, according to one embodiment of the invention.
• FIG 3 describes an implementation of the selection method, according to another embodiment of the invention.
• FIG 4 describes a selection device, according to one embodiment of the invention.
• communications infrastructure or “communication network” can be used interchangeably in the embodiments of the invention.
• This communications infrastructure can be implemented to route communication data to fixed or mobile terminals and the infrastructure can be implemented from physical equipment and/or virtualized functions.
• This infrastructure can be used for the routing and/or processing of data from residential or business customers, fixed and mobile users, and can be operated by a telecommunications operator.
• FIG 1 presents a communication infrastructure in which the selection method is implemented according to one aspect of the invention.
• an entity 110 for managing the topology of the infrastructure 200 manages the different resources 102, 103, 104, VM1, VM2, VM3, VM4, VM5 of the infrastructure 200.
• This management entity 110 also called Topology Server, thus maintains a database including information on the different devices or resources 102, 103, 104, VM1, VM2, VM3, VM4, VM5 and on the applications and processes Procl, Proc2, Proc3 and Proc4 instantiated and instantiable on these devices.
• a device according to the invention can be physical equipment 102, 103, 104 or a virtual instance such as a virtual machine VM1, VM2, VM3, VM4 and VM5 or even a container, according to another example.
• the virtual machine VM1 thus corresponds to the virtual machine VM1 on the physical equipment 102.
• a process is considered instantiable on a device if its dependencies are installed, if the container images of the components comprising one or more processes are available on the device , if the device is authorized, for example by the infrastructure manager or the resource manager, to host this process.
• the management entity 110 comprises a selection device 100 (Sel) executing selection operations with a view to identifying a device of the infrastructure 200 already hosting a required process or to identifying a device on which will be instantiated a process required by a client entity (Clt).
• This selection can be carried out using a weighted directed graph comprising all of the devices 102, 103, 104, VM1, VM2, VM3, VM4, VM5 of the infrastructure 200 to select the device capable of hosting the process in accordance with the usage request received from the client entity 10.
• the client entity 10 may be a user terminal such as a smartphone, a PC, a residential gateway or any other device that a user can exploit to execute or use an app.
• the client entity Clt can also be an administration entity of the communication infrastructure, in charge for example of deploying network services on demand, therefore dynamically.
• the application can be a value-added application, such as a voice, video and/or data service for example with a server or a terminal not shown in [Fig 1].
• An application can be instantiated from one or more processes, a process being characterized by an ordered sequence of operations leading to a result.
• the application required by the client entity 10 from the management entity 110 comprises four processes Procl, Proc2, Proc3 and Proc4, these processes being able to be processes relating to network operations and /or application type operations. According to an example, this may involve an operation of discovering a server, connecting to a server, receiving an application flow, or processing an application flow.
• Each process Procl, Proc2, Proc3 and Proc4 of the application is characterized by a set of parameters. According to a non-exhaustive list of these parameters, a parameter can be
• this data can be represented for example by a number of milliseconds for a packet routed between the client entity and the device, this data can correspond to the Ping or Traceroute type network tool result,
• this data can be represented by a quality level of service (standard, silver, gold) or by guarantees of routing a data flow of a typical application.
• Each application therefore includes one or more processes, such as the Procl, Proc2, Proc3 and Proc4 processes, each process being characterized by a certain number of constraints or parameters, such as minimum amount of CPU/memory resources, use of a GPU ( in English Graphics Processing Unit), maximum latency allowed between the instantiated application and the user in particular to guarantee optimal quality of experience for the user of the client entity 10.
• the management entity 110 uses these parameters or constraints as well as the location of the client entity to determine the most suitable device for the use of the application by the client entity. So in the case where a process is already instantiated in the infrastructure 200, the management entity 110 must determine whether the location of this device is suitable for the execution of the application by the client entity having transmitted the request and whether on the other hand, the process is implemented in accordance with the identified parameters.
• the parameters can in fact be linked to the different processes Procl, Proc2, Proc3 and Proc4 of the application but also to the type of client entity 10, knowing for example that the parameters in terms of quality of service differ depending on example that the client entity is a terminal adapted to very high speed quality or not for example.
• the client entity 10 can be an administration station of the communication infrastructure 200 and the selection method is implemented to select and possibly instantiate a network service of the access, routing, address translation type. , conversion of protocols in the communication infrastructure 200.
• the client entity Clt sends to the entity managing the topology of a communication infrastructure comprising a selection device Sel a request Req for use of an application.
• the request can for example include an FQDN (Fully Qualified Domain Name) request to obtain the usage of an application.
• the client entity Clt will have previously been authenticated, in particular to verify that it can actually use the requested application and it will also have obtained the address of the management entity, for example when connecting to a communication infrastructure or by static configuration, for example in the case where the client entity is an infrastructure administration platform.
• the use request can be transmitted directly or indirectly, for example via an application management platform, to the management entity and therefore to the selection device included in the management entity.
• the selection device Sel having received this request, determines and selects the device(s) hosting or capable of hosting the application or a process of the application.
• the selection device Sel identifies the processes relating to the application. This step can be carried out from a database owned or not by the selection device Sel or it can be carried out by the service platform in the case where the request for use of the client entity is routed via this platform. In this case, the platform will forward the request and associated processes to the required application.
• the client entity transmits the usage request comprising process identifiers associated with the required application.
• the application includes a single process and this identification is not necessary. The process is represented by the application required by the client entity. It is considered in this example that the application whose use is required includes four processes Procl, Proc2, Proc3 and Proc4.
• the selection device Sel obtains one or more parameters associated with each process identified during the previous step or with the application, in the case for example where the application is single-process.
• This obtaining can be carried out through an internal database of the topology management entity making it possible to characterize a process by one or more parameters such as those described in [Fig 1], This obtaining can also be carried out via another entity capable of identifying the parameters associated with a process.
• the selection device will send a request including a process identifier to an entity managing the processes and will receive in return the parameters which are associated with the process.
• the service platform indicated in the description of step El above can also transmit the parameters associated with the processes.
• the parameters Pari and Par2 are obtained for the process Procl, the parameter Par3 for the process Proc2, the parameters Par3 and Par4 for the process Proc3 and the Pari and Par4 parameters for the Proc4 process.
• the selection device Sel selects one or more devices of the communication infrastructure, this or these devices having to be positioned according to a required distance between the selected device and the client entity Clt.
• the selected device(s) must also include resources making it possible to satisfy the parameters obtained previously and corresponding to each process.
• the selection device must select a device for each process Procl, Proc2, Proc3 and Proc4, the devices selected for each process may or may not be distinct.
• the device selected for the process Procl must include resources capable of satisfying the parameters Pari and Par2, the device selected for the process Proc2 must include resources capable of satisfying the parameter Par3, the device selected for the process Proc3 must include resources capable of to satisfy the parameters Par3 and Par4, the device selected for the Proc4 process must include resources capable of satisfying the Pari and Par4 parameters.
• the Sel selection device uses the location of the client entity, this location possibly being topological and/or geographical. Information on the location of the client entity, which may be an IP address and/or a GPS coordinate or any other data providing information on the location of the client entity, is for example transmitted when sending the request.
• This location data of the client entity is taken into account by the selection device to deploy, for example, applications in MEC type architectures (in English Mobile Edge Computing) and/or to ensure a balanced distribution of processes used by the client entities in the different infrastructure devices.
• the selection device for example using its database on the processes deployed in the different devices and/or on the resources available on the devices capable of hosting one or more processes, selects one or more devices VM1, VM2 and VM5 associated with each process and whose distance from the client entity Clt is for example less than a reference value, for example specific to a process and/or to the infrastructure, determined by the selection device.
• this selection step E3 comprises several sub-steps. The following steps are carried out for the selection of a device for the process Procl but these steps are identical for the selection of a device for the other processes Proc2, Proc3 and Proc4, knowing that the different selections for the different processes can be made iteratively or in parallel.
• the selection device Sel determines a set of devices among the plurality, this set comprising devices positioned at a distance less than a reference value based on location data from the client entity Clt .
• This reference value represents for example a number of hops in the infrastructure between a potentially selected infrastructure hosting device and the client entity, and/or a geographic distance between the potentially selected device and the client entity.
• a weighting of at least one link and/or at least one function (equipment, router, switch, etc.) positioned between the the client entity and the device to be selected, for example from a weighted directed graph as described above.
• the number of jumps corresponds for example to a number of functions ensuring the routing of a packet of a process between the client entity Clt and a potentially selected device.
• the set of devices determined as valid with respect to the reference value includes the devices VM1, VM2, VM3, VM4 as presented in [Fig 1]. Knowing that only the location data of the client entity Clt is taken into account for the definition of this set, these devices in the set are a priori selectable for the different processes Procl, Proc2, Proc3 and Proc4.
• the selection device Sel selects during a step E32 among these preselected devices VM1, VM2, VM3, VM4 alone, the device comprising resources capable of satisfying the parameters Pari and Par2 of the Process Procl.
• the Sel selection device determines whether one or more devices among the devices VM1, VM2, VM3, VM4 are already hosting the process in accordance with the Pari and Par2 parameters. If so, the Sel selection device selects it. If more than one device hosts the process, the selection device Sel chooses one among these devices either according to the distance of the device to be selected from the client entity Clt or for example according to the storage or calculation capacities of the device .
• the selection device Sel selects during step E32 the device or the virtual machine VM1.
• the selection device Sel informs the client entity Clt about the device VM1 selected for the process Procl. This step can be carried out immediately after step E32 or after the complete end of step E3.
• the selection device transmits a message comprising the different devices instantiating the different processes Procl, Proc2, Proc3 and Proc4 once a device has actually been selected for each process of the application, thus avoiding informing the client entity Clt by a message associated with each process, and only informing the client entity when the application, and therefore all of the processes required for the instantiation of the application, can be effectively instantiated in the communications infrastructure.
• This selection step E32 is repeated for the other processes Proc2, Proc3 and Proc4. If, during step E32, no device hosts a required process, then the selection device Sel instantiates the process on a device having the resources required to satisfy the parameters associated with the process. For example, the selection device Sel does not identify any device among the devices VM1, VM2, VM3, VM4 instantiating the process Proc2 and determines during step E'32 that the device VM2 has the resources for the instantiation of the process Proc2. During a step E5, the selection device instantiates the process Proc2 on the device or virtual machine VM2. This instantiation can be carried out directly by the selection device Sel or via another entity of the infrastructure, such as a device configuration entity.
• the selection device Sel transmits a waiting message to the client entity Clt, to indicate to it that the process is being instantiated.
• the waiting message relates to the requested application and the message is sent to the client entity Clt when one or more of the processes Procl, Proc2, Proc3, Proc4 of the application must be instantiated on a hosting device.
• the client entity Clt receives a waiting message directly linked to the use request initially transmitted.
• Waiting corresponds for example to the transmission of information on "a waiting room", corresponding to a component installed on a hosting device VM1, VM2, VM3, VM4 or on the management entity 110 or even on a specific device not shown, which redirects the client entity to the installed process once it has actually been installed.
• a waiting room corresponding to a component installed on a hosting device VM1, VM2, VM3, VM4 or on the management entity 110 or even on a specific device not shown, which redirects the client entity to the installed process once it has actually been installed.
• sending the wait instruction and using the waiting room on the device is not required unless the process is in standby or inoperative mode for a period.
• the waiting room is advantageously implemented in one of the devices hosting one of the processes, for example in a device comprising a process for managing application resources.
• This device whether it is a hosting device VM1, VM2, VM3, VM4, the management entity 110 or a specific device assigned to this role, must thus be informed of the instantiation effective of all the processes required for the instantiation of the application, in order to redirect the client entity Clt, for example by implementing an http redirection or by the use of an FQDN associated with the application.
• Steps E5 and E6 can be carried out directly after step E'32 or after the termination of step E3 for all of the processes Procl, Proc2, Proc3 and Proc4 as shown in [Fig 2].
• the reference value used to define a set of devices capable of hosting a process of the application is incremented during a step E”31.
• the increment may consist of adding one or more hops and/or expanding the geographic distance from the client entity Clt.
• the set of eligible hosting devices also includes the VM5 device now eligible to host one of the processes.
• the selection device Sel determines during a step E” '32 that the device VM5 is able to instantiate the process Proc3 in accordance with the parameters Par4 and Par5.
• the selection device Sel instantiates the process Proc3 on the virtual machine VM5 during a step E7 and, according to an alternative, transmits a waiting instruction to the client entity Clt during a step E8.
• step E”31 is repeated until the reference value reaches a maximum.
• the process could not be instantiated on a device in the infrastructure and the application, in the case where this process is absolutely necessary for the operation of the application, cannot be installed in the infrastructure in accordance with the required requirements. .
• the selection device informs the client entity Clt that the application cannot be used by the client and that its request cannot therefore be satisfied.
• the selection device determines among the eligible devices, before or after the increment of the reference value, that the device VM1 instantiates the process Proc4 and selects it.
• the selection device has the possibility of considering only the devices VM1, VM2, VM3 and VM4 to determine the device capable of hosting the process Proc4 or it can also consider the device VM5, depending on whether it performs step E” ”32 after step E”31 as in [Fig 2] or before this step E”31 according to an alternative not shown.
• the selection device can in fact select all possible processes in the set of devices defined by the reference value, or consider the largest possible set in relation to the reference value to select a device.
• step E3 only includes one iteration and the selection device selects the devices for the different processes in a set of devices defined in relation to the location of the client entity without the possibility of modifying this set.
• the selection device Sel can advantageously inform when of a step E9 the client entity Clt on the availability of the application in its completeness and possibly inform the client entity on the devices VM1, VM2 and VM5 used for the instantiation of the application processes.
• This information is particularly relevant in the case where the client entity Clt is an infrastructure administration entity where the information on the hosting of the processes of an application is very relevant, in particular to ensure the management and identification of incidents or degradation of quality of service.
• a device is selected to host an application, in accordance with a request for use of that application from a client entity.
• the application is single-component and the process or processes of the application are hosted on a single device of a communication infrastructure.
• FIG 3 presents the steps implemented by a device for selecting a communication infrastructure management entity.
• the device receives a request for use of an application from a client entity and obtains a set of parameters relating to this application, in accordance with steps El and E2 described in [Fig 2] .
• the selection device determines during a step E3 a set of devices whose distance from the entity client is less than a distance N.
• the selection device evaluates whether a device among the devices determined during step E31a has sufficient resources and has already instantiated the application required by the client entity, in accordance with the parameters obtained during step E2.
• the device informs the client entity during a step E9. If no device has instantiated it, the selection device evaluates during a step E32b whether a device selected during step E31a has the necessary resources for the process or processes of the required application, and consecutively the application itself. If a device is actually suitable for this hosting, it is selected, and an identifier (IP address, URI, FQDN identifier) is transmitted to the client entity during a step E9. In Furthermore, the application is actually instantiated on the device selected during a step E5.
• IP address, URI, FQDN identifier IP address, URI, FQDN identifier
• the device determines during a step E31b whether the value N is equal to or greater than a reference value NMax, representative of a maximum acceptable distance for a device to host the required application. If the value is equal to or greater than this value N, an error message is returned to the client entity during a step E10 indicating that the client entity cannot use the application or cannot install the application, depending on the client entity considered.
• NMax representative of a maximum acceptable distance for a device to host the required application.
• step E3 le In the case where the value N is less than the value NMax, the value N is incremented during a step E3 le, this increment may correspond to an increase in the number of jumps and/or to a larger radius of the domain in which a device is selected.
• step E3 is carried out again.
• Steps E31a, E31b and E31 c are sub-steps of step E31 described in [Fig 2] and steps E32a and E32b are sub-steps of step E32 described in [Fig 2].
• FIG 4 presents a selection device 100 according to one embodiment of the invention.
• Such a selection device can be implemented in a management entity, such as the administration entity of a telecommunications network, for example instantiated from virtualized functions.
• the selection device 100 comprises a processing unit 130, equipped for example with a microprocessor pP, and controlled by a computer program 110, stored in a memory 120 and implementing the selection method, in the different embodiments, according to the invention.
• a computer program 110 stored in a memory 120 and implementing the selection method, in the different embodiments, according to the invention.
• the code instructions of the computer program 190 are for example loaded into a RAM memory, before being executed by the processor of the processing unit 130.
• Such a selection device 100 comprises a module 101 reception, configured to receive from a client entity a Req request for use of the application, an obtaining module 102, configured to obtain a parameter associated with the at least one process and location data of the client entity, a module 103 for selecting the device from among the plurality, whose position in the infrastructure is at a required distance relative to the location data of the client entity obtained, the selected device further comprising a resource allowing the parameter obtained to be satisfied.
• the selection device 100 further comprises a transmitter, adapted to transmit to the client entity an instruction to put the client entity on hold corresponding to the instantiation delay of the at least one process on the device selected.
• the transmitter is configured to transmit identification data of the selected device to the client entity.
• the selection device 100 comprises a determination module, adapted to determine a set of devices among the plurality comprising devices whose distance relative to the client entity is less than a reference value calculated from the data of location, and a selection module, adapted to select the device from the determined set of devices, said device comprising resources capable of satisfying the parameter.
• module can correspond as well to a software component as to a hardware component or a set of hardware and software components, a software component itself corresponding to one or more computer programs or subprograms or in a manner more general to any element of a program capable of implementing a function or a set of functions.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• Medical Informatics (AREA)
• General Health & Medical Sciences (AREA)
• Computing Systems (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Health & Medical Sciences (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Stored Programmes (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=84053041

Family Applications (1)

Country Status (3)

Family Cites Families (2)

• 2022
  • 2022-09-28 FR FR2209826A patent/FR3140229A1/fr not_active Ceased
• 2023
  • 2023-09-19 WO PCT/EP2023/075726 patent/WO2024068350A1/fr not_active Ceased
  • 2023-09-19 EP EP23768917.9A patent/EP4595412A1/de active Pending

Also Published As

Similar Documents

Legal Events