WO2020151803A1 - Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau - Google Patents

Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau Download PDF

Info

Publication number
WO2020151803A1
WO2020151803A1 PCT/EP2019/051380 EP2019051380W WO2020151803A1 WO 2020151803 A1 WO2020151803 A1 WO 2020151803A1 EP 2019051380 W EP2019051380 W EP 2019051380W WO 2020151803 A1 WO2020151803 A1 WO 2020151803A1
Authority
WO
WIPO (PCT)
Prior art keywords
renegotiation
sla
offers
service
slas
Prior art date
Application number
PCT/EP2019/051380
Other languages
English (en)
Inventor
Allan VIDAL
Pedro Henrique GOMES DA SILVA
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2019/051380 priority Critical patent/WO2020151803A1/fr
Publication of WO2020151803A1 publication Critical patent/WO2020151803A1/fr

Links

Classifications

    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5006—Creating or negotiating SLA contracts, guarantees or penalties
    • 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/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence

Definitions

  • the present disclosure generally relates to systems using network slicing.
  • a technique for performing a renegotiation of one or more service level agreements (SLAs) each being associated with a service being executed on one or more network slice instances (NSIs) in a network slicing based system is provided.
  • the renegotiation of the one or more SLAs is performed to implement a desired resource reallocation to NSIs in the system.
  • the technique may be embodied in methods, computer programs, apparatuses and systems.
  • a network slice is a logical network that can be dynamically created and which may serve a particular service with an agreed upon SLA.
  • network slicing is a key feature for the next generation network. It is about transforming the network/system from a static "one size fits all" paradigm, to a new paradigm where logical networks/partitions are created, with appropriate isolation, resources and optimized topology to serve a particular purpose or service category (e.g., use case/traffic category) or even individual customers (logical system created "on demand”). It can be enriched by use of network functions virtualization (NFV) and software defined networking (SDN).
  • NFV network functions virtualization
  • SDN software defined networking
  • an NSI corresponds to a set of network functions and resources therefor which are arranged and configured to form a complete logical network to meet certain network characteristics.
  • An NSI may thus include all functionalities and resources necessary to support a certain set of communication services.
  • communication services may be offered by communication service providers (CSPs) to communication service customers (CSCs) and may include B2C services, such as mobile web browsing, voice over long term evolution (VoLTE), etc., B2B services, such as Internet access, local area network (LAN) interconnection, etc., and services offered to other CSPs, such as international roaming, radio access network (RAN) sharing, etc., for example.
  • CSPs communication service providers
  • B2B services such as Internet access, local area network (LAN) interconnection, etc.
  • RAN radio access network
  • Network slicing management functions defined in 3GPP TR 28.801 comprise, inter alia, a communication service management function (CSMF) and a network slice management function (NSMF). While the CSMF is generally responsible for the interaction with CSCs, the NSMF is responsible for the management of the network infrastructure and, thus, for the actual deployment of network slices on the infrastructure.
  • the CSMF may receive communication service related requirements from the CSC, convert the communication service related requirements to network slice related requirements (such as network type, network capacity, quality of service (QoS) requirements, etc.) and delegate management of the network slices to the NSMF by providing the network slice related requirements to the NSMF.
  • the NSMF may then manage the NSIs based on the network slice related requirements received from the CSMF.
  • SLA Communication service related requirements are generally referred to herein using the term "SLA”.
  • An SLA may represent a set of service level related requirements associated with a service.
  • An SLA may be translated into network slice related requirements for the actual network infrastructure to ensure that the agreed upon service level is effectively achieved.
  • an SLA may define requirements, such as "end-to-end latency between two endpoints is less than 5 ms" or "bandwidth is at least 10 Gbps for 99.999% of the time”.
  • a resource reallocation may require a renegotiation of SLAs associated with the services to be able to free the required resources on the infrastructure. Renegotiating SLAs may be a time consuming process, however, and the implementation of the reallocation may be delayed until appropriate SLA adjustments required to free the needed resources are agreed upon. This generally limits the flexibility and increases the response times by which network operators may react to changing requirements.
  • a method for performing a renegotiation of one or more SLAs each being associated with a service being executed on one or more NSIs in a network slicing based system is provided, wherein the renegotiation of the one or more SLAs is performed to implement a desired resource reallocation to NSIs in the system.
  • the method is performed by a service management function and comprises generating, for each of the one or more SLAs, an SLA renegotiation offer reflecting an adjusted SLA required to achieve the desired resource reallocation to the NSIs in the system, ranking the SLA renegotiation offers using a classifier configured to rank SLA renegotiation offers according to their likelihood of acceptance, performing renegotiation of the one or more SLAs under prioritization of higher ranked SLA renegotiation offers among the SLA renegotiation offers, and triggering implementing the desired resource reallocation to the NSIs of the system in accordance with the adjusted SLAs of SLA renegotiation offers being accepted in the renegotiation.
  • the method may further comprise receiving, prior to generating the SLA
  • renegotiation offers a request necessitating implementing the desired resource reallocation to the NSIs in the system.
  • the request may be one of a service creation request and a network capacity reduction request.
  • the adjusted SLAs required to achieve the desired resource reallocation to the NSIs in the system may be reduced SLAs.
  • the classifier may be trained based on historical SLA renegotiation data using supervised learning.
  • the historical SLA renegotiation data may comprise a plurality of data sets obtained from responses to previous SLA renegotiation offers. Each of the plurality of data sets may comprise an SLA renegotiation offer for an SLA and a label indicating a response to the SLA renegotiation offer.
  • the SLA renegotiation offer may include a service identifier of a service associated with the SLA and at least one adjusted requirement for the SLA.
  • Each of the plurality of data sets may further comprise at least one of metadata regarding the service associated with the SLA and, optionally, regarding network slices on which the service is executed, metadata regarding a context in which the SLA renegotiation offer was made, and data regarding an owner of the service associated with the SLA.
  • Each of the SLA renegotiation offers to be ranked may be input as an unlabeled test data set to the classifier, wherein the classifier outputs a label for each test data set indicating an expected response to the respective SLA renegotiation offer along with a likelihood score for the expected response.
  • the SLA renegotiation offers may be ranked based on the likelihood scores.
  • Responses to the SLA renegotiation offers in the renegotiation may be stored as new data sets in the historical SLA renegotiation data.
  • the classifier may be updated based on the responses to the SLA renegotiation offers.
  • the method may further comprise splitting, prior to ranking the SLA renegotiation offers, a single SLA renegotiation offer among the SLA renegotiation offers into plural SLA renegotiation offers having a higher total likelihood of acceptance than the single SLA renegotiation offer based on simulations using the classifier.
  • the service may be a communication service
  • the system may be a network slicing based mobile communication system
  • the service management function may be a CSMF.
  • Triggering the desired resource reallocation to the NSIs of the system may include instructing an NSMF to implement the desired resource reallocation to the NSIs of the system.
  • the service management function may obtain the one or more SLAs from an NSI database storing information on NSIs of the system including their associated services and SLAs.
  • the historical SLA renegotiation data may be collected and/or stored by at least one of a MDAF and a NWDAF.
  • a computer program product comprises program code portions for performing the method of the first aspect when the computer program product is executed on one or more computing devices (e.g., a processor or a distributed set of processors).
  • the computer program product may be stored on a computer readable recording medium, such as a semiconductor memory, DVD, CD-ROM, and so on.
  • a computing unit configured to execute a service management function for performing a renegotiation of one or more SLAs each being associated with a service being executed on one or more NSIs in a network slicing based system, wherein the renegotiation of the one or more SLAs is performed to implement a desired resource reallocation to NSIs in the system.
  • the computing unit comprises at least one processor and at least one memory, wherein the at least one memory contains instructions executable by the at least one processor such that the service management function is operable to perform any of the method steps presented herein with respect to the first aspect.
  • a system comprising a computing unit according to the third aspect.
  • Fig. 1 illustrates an exemplary composition of a computing unit configured to
  • Fig. 2 illustrates a method which may be performed by the service management function according to the present disclosure
  • Fig. 3 illustrates an exemplary data structure of a data set stored in historical SLA renegotiation data according to the present disclosure
  • Fig. 4 illustrates an exemplary overview of a network slicing based system
  • Fig. 5 illustrates a signaling diagram of an exemplary interaction between the
  • Fig. 6 illustrates an exemplary flowchart of a method which may be performed by the CSMF according to the present disclosure.
  • Figure 1 schematically illustrates an exemplary composition of a computing unit 100 configured to execute a service management function for performing a renegotiation of one or more SLAs each being associated with a service being executed on one or more NSIs in a network slicing based system, wherein the renegotiation of the one or more SLAs is performed to implement a desired resource reallocation to NSIs in the system.
  • the computing unit 100 comprises at least one processor 102 and at least one memory 104, wherein the at least one memory 104 contains instructions executable by the at least one processor 102 such that the service management function is operable to carry out the method steps described herein below with reference to the service management function.
  • the computing unit 100 may be implemented on a physical computing unit or a virtualized computing unit, such as a virtual machine, for example. It will further be appreciated that the computing unit 100 may not necessarily be implemented on a standalone computing unit, but may be
  • Figure 2 illustrates a method which may be performed by the service management function executed on the computing unit 100 according to the present disclosure.
  • the method is dedicated to performing a renegotiation of one or more SLAs each being associated with a service being executed on one or more NSIs in a network slicing based system, wherein the renegotiation of the one or more SLAs is
  • step S202 the service management function receives a request necessitating implementing the desired resource reallocation to the NSIs in the system.
  • step S204 the service management function generates, for each of the one or more SLAs, an SLA renegotiation offer reflecting an adjusted SLA required to achieve the desired resource reallocation to the NSIs in the system.
  • step S206 the service
  • the management function ranks the SLA renegotiation offers using a classifier configured to rank SLA renegotiation offers according to their likelihood of acceptance.
  • the service management function performs renegotiation of the one or more SLAs under prioritization of higher ranked SLA renegotiation offers among the SLA renegotiation offers.
  • the service management function triggers implementing the desired resource reallocation to the NSIs of the system in accordance with the adjusted SLAs of SLA renegotiation offers being accepted in the renegotiation.
  • the desired resource reallocation to NSIs may be necessitated by a requirement to free resources in the system, such as to deploy a new service to be executed on one or more new NSIs in the system or to perform maintenance or upgrade procedures in the system.
  • the service management function may thus receive, prior to generating the SLA renegotiation offers, a request necessitating implementing the desired resource reallocation to the NSIs in the system in step S202.
  • the request may be one of a service creation request and a network capacity reduction request, for example, and the adjusted SLAs required to achieve the desired resource reallocation to the NSIs in the system may be reduced SLAs so that resources can effectively be freed in the system.
  • the service creation request may be received from a CSC when the CSC desires to create a new service to be deployed on the network infrastructure of the system, for example.
  • the network capacity reduction request may be received from a network operator when the network operator desires to accommodate new workloads in the system or to temporarily rearrange network resources in the system to be able to perform maintenance or upgrade procedures, for example.
  • the renegotiation of the one or more SLAs in accordance with steps S204 to S208 may then be performed to adjust at least one SLA currently in force to be able to free resources and implement the desired resource reallocation to NSIs in the system.
  • an SLA renegotiation offer may be generated for each of the one or more SLAs in step S204, wherein each SLA renegotiation offer may reflect an adjusted (e.g., reduced) SLA required to achieve the desired resource reallocation to the NSIs of the system.
  • the generation of the corresponding renegotiation offers may involve a determination of the necessary SLA adjustments and may be performed in accordance with known methods, such as the method disclosed in Paputungan, Irving Vitra, Ahmad Fadzil Mohamad Hani, Mohd Fadzil Hassan, Vijanth S. Asirvadam: "Real-Time and Proactive SLA Renegotiation for a Cloud-Based System", IEEE Systems Journal, IEEE, 2018.
  • the technique presented herein generally proposes to focus on those SLA renegotiation offers in the renegotiation for which it can be anticipated that they will more likely be accepted. In this way, the amount of time necessary to perform SLA renegotiation until the adjusted SLAs based on which the desired resource
  • reallocation can be implemented in a faster manner, thereby increasing the response times by which network operators may react to changing requirements in the network infrastructure.
  • the SLA renegotiation offers may be ranked using a classifier configured to rank SLA renegotiation offers according to their likelihood of acceptance in step
  • the classifier may be obtained using a supervised learning algorithm and may thus be trained based on historical SLA renegotiation data using supervised learning.
  • the historical SLA renegotiation data may comprise a plurality of data sets obtained from responses to previous SLA renegotiation offers. Renegotiation of the one or more SLAs may then be performed under prioritization of higher ranked SLA renegotiation offers among the SLA renegotiation offers in step S208.
  • renegotiation may be tried for one or more highest ranked SLA renegotiation offers first, followed by next ranked SLA renegotiation offers, if needed, until the adjusted one or more SLAs based on which the desired resource reallocation may be implemented are identified.
  • Renegotiating the one or more SLAs may include sending the SLA renegotiation offers to the respective owners of the services associated with the SLAs to be renegotiated and the service owners (e.g., CSCs) may respond to the SLA
  • renegotiation offers by accepting or rejecting the offers, e.g., through automated decision systems.
  • Communication between the service management function and the service owners may be carried out via an API or using a communication channel, for example.
  • automated SLA brokerage systems may be used, such as the one disclosed in Wu, Linlin, Saurabh Kumar Garg, Rajkumar Buyya, Chao Chen, Steve Versteeg: "Automated SLA Negotiation Framework for Cloud Computing", 13th
  • management function may trigger implementing the desired resource reallocation to the NSIs of the system in accordance with the adjusted SLAs of the SLA
  • renegotiation offers being accepted in the renegotiation in step S210, so that the desired resource reallocation is effectively implemented in the system.
  • each of the plurality of data sets may comprise an SLA renegotiation offer for an SLA and a label indicating a response to the SLA renegotiation offer.
  • renegotiation offer may include a service identifier of a service associated with the SLA and at least one adjusted requirement for the SLA.
  • the SLA may include a service identifier of a service associated with the SLA and at least one adjusted requirement for the SLA.
  • renegotiation offer may also comprise an indication of a compensation offered to the service owner.
  • the label included in the data set may indicate that the SLA
  • renegotiation offer of the data set has been accepted or rejected by the service owner, or whether no response has been received from the service owner at all.
  • each of the plurality of data sets may further comprise at least one of metadata regarding the service associated with the SLA and, optionally, regarding network slices on which the service is executed, metadata regarding a context in which the SLA renegotiation offer was made, and data regarding the owner of service associated with the SLA.
  • the service and/or network slices related metadata may include information on current utilization, historical utilization, the current SLA, priorities, and requirements (e.g., requirements regarding bandwidth, latency, QoS, etc.), the context related metadata may include
  • a data set 300 is represented by a vector including the SLA renegotiation offer, the service/network slices related metadata, the context related metadata, the service owner related metadata, and the label.
  • a data set may be represented by an n-dimensional vector usable for supervised learning algorithms, such as k-nearest neighbor (k-NN), support vector machines (SVMs), and the like.
  • the classifier may be trained based on historical SLA renegotiation data which may include data sets obtained from responses to previous SLA renegotiation offers.
  • each of SLA renegotiation offers to be ranked may be input as an unlabeled test data set to the classifier, wherein the classifier may output a label for each test data set indicating an expected response to the respective SLA renegotiation offer along with a likelihood score for the expected response.
  • a test data set may have the same structure as described above for the data sets of the historical SLA renegotiation data, the only difference being that the test data set may initially be unlabeled, e.g., the test data set may initially have an empty label or no label at all.
  • the classifier may determine a likelihood of acceptance for the SLA renegotiation offer included in the test data set and determine an expected response to the SLA renegotiation offer, optionally along with a likelihood score for the respective response (e.g., indicating 85% chance of "acceptance").
  • the SLA renegotiation offers may then be ranked based on the likelihood scores.
  • the classifier may be updated to adapt to recent renegotiation behavior of the service owners.
  • Responses to the SLA renegotiation offers in the renegotiation may thus be stored as new data sets in the historical SLA renegotiation data and the classifier may be updated based on the responses to the SLA renegotiation offers.
  • the SLA renegotiation offers may be adapted themselves to be more easily negotiable with service owners.
  • new SLA requirements of an SLA renegotiation offer may be split into smaller units. The service management function may thus split, prior to ranking the SLA
  • the service may be any service executed on one or more NSIs in the system.
  • the system and its components may comply with the definitions of 3GPP TR 28.801 V15.1.0 (2018-01), or successor versions thereof.
  • the service may thus be a communication service, the system may be a network slicing based mobile
  • the service management function may be a CSMF.
  • the CSMF may trigger the required rearrangement of the network via an NSMF. Triggering the desired resource reallocation to the NSIs of the system may thus include instructing an NSMF to implement the desired resource reallocation to the NSIs of the system.
  • the service management function may have access to an NSI database storing information on NSIs of the system including their associated services and SLAs and may obtain the one or more SLAs from the NSI database. Further, the historical SLA renegotiation data may be collected and/or stored by at least one of an MDAF and a NWDAF.
  • the MDAF and the NWDAF are components under discussion in 3GPP and represent components responsible for storing and providing analytics to other components. It will be understood, that the collection, aggregation and storage of historical data and classifiers may also be performed by other nodes or functions of the system.
  • FIG. 4 illustrates an exemplary overview of a network slicing based system in accordance with 3GPP TR 28.801 which is extended to support the technique presented herein.
  • the system comprises a CSMF 402 which may receive service related requests from other entities of the system, such as new service requests from a CSC 404 or network capacity reduction requests from a network operator 406, for example.
  • the CSMF 402 may delegate management of the network slices to an NSMF 408 which, in turn, may manage the actual deployment of network slices on the network infrastructure 410.
  • the CSMF 402 may have access to an NSI database 412 storing information on active NSIs deployed in the system including their associated services and SLAs, to a storage for historical renegotiation data 414 as well as to a classifier 416 configured to rank SLA renegotiation offers according to their likelihood of acceptance.
  • FIG. 5 illustrates a signaling diagram of an exemplary interaction between the CSMF 402, the NSMF 408 and the network infrastructure 410.
  • a new service request may be received from CSC 404.
  • the CSMF 402 may decompose the request into corresponding NSI creation or reconfiguration requests and may send these requests to the NSMF 408 in step 2.
  • the NSMF 408 may assess viability of the requested NSI changes and, if the changes are determined to be viable, the NSMF 408 may create or reconfigure NSIs on the network infrastructure 410 in step 3a.
  • the NSMF 408 may request the CSMF 402 to perform an SLA renegotiation to free resources required to implement the requested creation or reconfiguration of NSIs.
  • the CSMF 402 may perform SLA renegotiation in accordance with the technique presented herein.
  • the CSMF 402 may trigger, in step 5, NSI capacity reductions in accordance with the accepted new SLAs by instructing the NSMF 408 to implement these reductions.
  • the NSMF 408 may then reduce the NSI capacity as instructed in step 6.
  • the NSMF 408 may notify, in step 7, the CSMF 402 of the completion and, given that resources for the new service may now be free, the CSMF 402 may reattempt sending the NSI creation or reconfiguration request in step 1 to eventually create the new service.
  • the interaction shown in Figure 5 is merely exemplary and only elucidates a use case in which SLA renegotiation in accordance with the technique presented herein may be performed.
  • steps 4 to 7 may be performed, for example.
  • Figure 6 illustrates an exemplary flowchart of a method which may be performed by the CSMF 402 when performing an SLA renegotiation.
  • a need for resource reallocation e.g., a new service may need more resources or a network capacity reduction may be needed for maintenance, as described above
  • the CSMF 402 may start a renegotiation with owners of active services to reduce their SLAs, as described above, optionally in exchange for a compensation.
  • the classifier 416 as well as the historical SLA renegotiation data in the storage 414 may initially not be available and may need to be constructed first.
  • the CSMF 402 may create SLA renegotiation offers by calculating the necessary reduction in SLA for one or more active services being executed on one or more NSIs in the system.
  • the CSMF 402 may then determine in step S604 that a classifier 416 is not yet available and the CSMF 402 may thus obtain a list of all active services (or a subset of it) from the NSI database 412 in step S606. For all services in the list, the CSMF 402 may send SLA renegotiation offers to the respective service owners in step S608.
  • renegotiation offer may be stored together with the received response
  • the CSMF 402 may generate the classifier 416 using a supervised learning algorithm in step S612. At this point, historical data and the classifier 416 are available and, for subsequent renegotiations, the classifier 416 may be used to avoid performing SLA renegotiation with all service owners, thereby increasing the response time for implementing the new resource reallocation, as described above.
  • the CSMF 402 may now determine in step S604 that the classifier 416 is available.
  • the CSMF 402 may therefore generate, in step S614, a plurality of test data sets for each of the active services and run each test data set through the classifier 416, which may output a corresponding likelihood of acceptance for the SLA reductions given in the SLA renegotiation offers. Based on the likelihoods, a ranking of which SLA renegotiation offers will more likely be accepted by service owners may be generated.
  • renegotiation may be performed under prioritization of the higher ranked SLA renegotiation offers (e.g., respecting the list order) and responses may again be stored in accordance with step S610.
  • the CSMF 402 may update the classifier 416 based on the newly added data sets in the historical SLA renegotiation data in step S612. In this way, the CSMF 402 may adapt the classifier 416 to the recent renegotiation behavior of the service owners and thereby improve the classification results over time.
  • the present disclosure provides a technique for performing a renegotiation of one or more SLAs in a network slicing based system, wherein the renegotiation may be performed to implement a desired resource reallocation to NSIs in the system.
  • the presented technique may reduce the amount of time necessary to conduct SLA renegotiation involving multiple service owners, wherein historical SLA renegotiation data may be used to assess which of the service owners will most likely accept adjusted SLA terms with respect to their service and the network slices the service is executed on.
  • renegotiations may thus be conducted in an efficient manner and the resulting network reallocation may generally be performed faster.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne une technique permettant d'effectuer une renégociation d'un ou plusieurs contrats de niveau de service (SLA), chacun étant associé à un service étant exécuté sur une ou plusieurs instances de tranche de réseau (NSI) dans un système basé sur un découpage en réseau, la renégociation du ou des SLA étant effectuée pour mettre en œuvre une ré-attribution de ressources souhaitée sur des NSI dans le système. Un procédé de mise en œuvre de la technique est effectué par une fonction de gestion de service et comprend la génération (S204), pour chacun desdits SLA, d'une offre de renégociation de SLA reflétant un SLA modifié nécessaire pour obtenir la ré-attribution de ressource souhaitée sur les NSI dans le système, le classement (S206) des offres de renégociation de SLA à l'aide d'un classificateur configuré pour classer des offres de renégociation de SLA en fonction de leur probabilité d'acceptation, la réalisation (S208) d'une renégociation desdits SLA en donnant la priorité aux offres de renégociation de SLA de classement supérieur parmi les offres de renégociation de SLA, et le déclenchement (S210) d'une mise en œuvre de la ré-attribution de ressources souhaitée sur les NSI du système en fonction des SLA modifiés des offres de renégociation de SLA étant acceptés dans la renégociation.
PCT/EP2019/051380 2019-01-21 2019-01-21 Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau WO2020151803A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/051380 WO2020151803A1 (fr) 2019-01-21 2019-01-21 Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/051380 WO2020151803A1 (fr) 2019-01-21 2019-01-21 Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau

Publications (1)

Publication Number Publication Date
WO2020151803A1 true WO2020151803A1 (fr) 2020-07-30

Family

ID=65199418

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/051380 WO2020151803A1 (fr) 2019-01-21 2019-01-21 Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau

Country Status (1)

Country Link
WO (1) WO2020151803A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430380A (zh) * 2020-10-15 2022-05-03 中国移动通信集团浙江有限公司 切片容灾池分级方法、装置和设备
CN114979721A (zh) * 2022-05-18 2022-08-30 咪咕文化科技有限公司 视频切片方法、装置、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150030151A1 (en) * 2013-07-26 2015-01-29 Accenture S.P.A Next best action method and system
US20180317134A1 (en) * 2017-04-28 2018-11-01 Huawei Technologies Co., Ltd. Nssmf nsmf interaction connecting virtual 5g networks and subnets

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150030151A1 (en) * 2013-07-26 2015-01-29 Accenture S.P.A Next best action method and system
US20180317134A1 (en) * 2017-04-28 2018-11-01 Huawei Technologies Co., Ltd. Nssmf nsmf interaction connecting virtual 5g networks and subnets

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release 15)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.801, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. V15.1.0, 4 January 2018 (2018-01-04), pages 1 - 75, XP051392292 *
3GPP TR 28.801, January 2018 (2018-01-01)
LINLIN WU ET AL: "Automated SLA Negotiation Framework for Cloud Computing", CLUSTER, CLOUD AND GRID COMPUTING (CCGRID), 2013 13TH IEEE/ACM INTERNATIONAL SYMPOSIUM ON, IEEE, 13 May 2013 (2013-05-13), pages 235 - 244, XP032431206, ISBN: 978-1-4673-6465-2, DOI: 10.1109/CCGRID.2013.64 *
PAPUTUNGAN; IRVING VITRA; AHMAD FADZIL MOHAMAD HANI; MOHD FADZIL HASSAN; VIJANTH S. ASIRVADAM: "IEEE Systems Journal", 2018, IEEE, article "Real-Time and Proactive SLA Renegotiation for a Cloud-Based System"
PITTL BENEDIKT ET AL: "Simulating Negotiation-Based Cloud Markets", 12 June 2018, INTERNATIONAL CONFERENCE ON COMPUTER ANALYSIS OF IMAGES AND PATTERNS. CAIP 2017: COMPUTER ANALYSIS OF IMAGES AND PATTERNS; [LECTURE NOTES IN COMPUTER SCIENCE; LECT.NOTES COMPUTER], SPRINGER, BERLIN, HEIDELBERG, PAGE(S) 664 - 677, ISBN: 978-3-642-17318-9, XP047477873 *
SHARAF S ET AL: "Enabling service-level agreement renegotiation through extending WS-Agreement specification", SERVICE ORIENTED COMPUTING AND APPLICATIONS, SPRINGER LONDON, LONDON, vol. 9, no. 2, 19 June 2014 (2014-06-19), pages 177 - 191, XP035501169, ISSN: 1863-2386, [retrieved on 20140619], DOI: 10.1007/S11761-014-0159-5 *
WU, LINLIN; SAURABH KUMAR GARG; RAJKUMAR BUYYA; CHAO CHEN; STEVE VERSTEEG: "13th IEEE/ACM International Symposium on Cluster, Cloud, and Grid Computing (CCGrid", 2013, IEEE, article "Automated SLA Negotiation Framework for Cloud Computing", pages: 235 - 244

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114430380A (zh) * 2020-10-15 2022-05-03 中国移动通信集团浙江有限公司 切片容灾池分级方法、装置和设备
CN114430380B (zh) * 2020-10-15 2023-11-24 中国移动通信集团浙江有限公司 切片容灾池分级方法、装置和设备
CN114979721A (zh) * 2022-05-18 2022-08-30 咪咕文化科技有限公司 视频切片方法、装置、设备及存储介质
CN114979721B (zh) * 2022-05-18 2024-02-23 咪咕文化科技有限公司 视频切片方法、装置、设备及存储介质

Similar Documents

Publication Publication Date Title
US11374831B2 (en) System and method to support network slicing in an MEC system providing automatic conflict resolution arising from multiple tenancy in the MEC environment
EP3461087B1 (fr) Procédé et appareil de gestion de ressources de tranches de réseau
US11258689B2 (en) Mobility network slice selection
WO2020258920A1 (fr) Procédé et appareil de gestion de ressources de tranches de réseau
Afolabi et al. Network slicing-based customization of 5G mobile services
US10313887B2 (en) System and method for provision and distribution of spectrum resources
Kang et al. An SDN-enhanced load-balancing technique in the cloud system
CN110463140B (zh) 计算机数据中心的网络服务水平协议
Brik et al. Service-oriented MEC applications placement in a federated edge cloud architecture
EP3800926A1 (fr) Procédé et dispositif d'alarme
WO2019174000A1 (fr) Procédé et appareil de gestion de service
WO2018201856A1 (fr) Système et procédé pour centre de données à auto-organisation
Attaoui et al. Vnf and cnf placement in 5g: Recent advances and future trends
Abreu et al. A rank scheduling mechanism for fog environments
Othman et al. Efficient admission control and resource allocation mechanisms for public safety communications over 5G network slice
Skulysh et al. Managing the process of servicing hybrid telecommunications services. Quality control and interaction procedure of service subsystems
WO2020151803A1 (fr) Technique de mise en œuvre d'une ré-attribution de ressources dans un système basé sur un découpage en réseau
Dimolitsas et al. A multi-criteria decision making method for network slice edge infrastructure selection
KR102389334B1 (ko) 클라우드 서비스를 위한 가상 머신 프로비저닝 시스템 및 방법
Ibn-Khedher et al. Cdnaas framework: Topsis as multi-criteria decision making for vcdn migration
WO2022198524A1 (fr) Procédé de déploiement d'instance de service, et procédé et système d'équilibrage de charge entre nœuds
Casetti et al. The vertical slicer: Verticals’ entry point to 5G networks
WO2024114630A1 (fr) Procédé et appareil de gestion d'intention
Zanzi et al. Latency-driven network slices orchestration
CN113098705B (zh) 网络业务的生命周期管理的授权方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19701335

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19701335

Country of ref document: EP

Kind code of ref document: A1