[go: up one dir, main page]

WO2018149263A1 - Procédé et appareil d'instanciation d'un service de réseau - Google Patents

Procédé et appareil d'instanciation d'un service de réseau Download PDF

Info

Publication number
WO2018149263A1
WO2018149263A1 PCT/CN2018/072905 CN2018072905W WO2018149263A1 WO 2018149263 A1 WO2018149263 A1 WO 2018149263A1 CN 2018072905 W CN2018072905 W CN 2018072905W WO 2018149263 A1 WO2018149263 A1 WO 2018149263A1
Authority
WO
WIPO (PCT)
Prior art keywords
instance
priority
preemption
nfvo
oss
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2018/072905
Other languages
English (en)
Chinese (zh)
Inventor
方海鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2018149263A1 publication Critical patent/WO2018149263A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or 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/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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5022—Ensuring fulfilment of SLA by giving priorities, e.g. assigning classes of service
    • 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/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method and an apparatus for instantiating a network service.
  • FIG. 1 which is an architecture diagram of a network function virtualization (NFV) system
  • the NFV system includes: a network function virtualization orchestrator (NFVO), and a virtual network function management node (virtualized).
  • VNFM network function virtualization orchestrator
  • VNFM virtualized infrastructure manager
  • OSS operations support system
  • BSS business support system
  • element management node element management node
  • EM virtualized network function
  • VNFVI virtual function network infrastructure
  • the NFVO, VNFM, and VIM nodes constitute the NFV management and orchestration (NFV-MANO).
  • the NFVO can also be called the network function virtualization orchestrator.
  • VNFM is responsible for lifecycle management of VNF instances, such as instantiation, expansion/contraction, query, update, and termination
  • VIM is the management portal for infrastructure and resources, providing resource management for VNF instances, including providing a foundation for VNF instances.
  • NFVO can perform operations such as management and coordination of VIM, and NFVO is connected to all VIMs and VNFMs in the NFV system.
  • a network service (NS) instance usually consists of multiple VNF instances with a specific connection relationship.
  • the NFVO node needs to apply for the corresponding resources through VNFM.
  • VNF instances while VNFM allocates resources according to the principle of “first come, then come”, that is, allocate resources for different NS instances in the order of each NS instantiation request received by VNFM. Then, in case of insufficient resources, VNFM will feed back to NFVO.
  • the NS instance creation fails because the resource application fails. Then, for the NS instance creation process of the more important tenant or service, the NS instantiation method cannot effectively guarantee the quality of the network service.
  • the present invention provides a method and an apparatus for instantiating a network service, which can ensure the resource requirements of high-priority network services as much as possible in the case of insufficient resources, and improve the service quality of high-priority network services in the NFV system.
  • the first aspect provides a method for instantiating a network service, including: the OSS receives a creation request of a first NS instance to be created, where the creation request is used to indicate a preemption priority of the first NS instance; When the resources required by the NS instance are insufficient, the OSS may determine, according to the preemption priority of the first NS instance, the second NS instance that is allowed to be preempted, and the preemption priority of the second NS instance is lower than the preemption of the first NS instance.
  • Priority The OSS sends a condensing request of the second NS instance to the NFVO, where the condensing request is used to instruct the NFVO to perform a shrinking operation on the resource occupied by the second NS instance.
  • the OSS may send an instantiation request of the first NS instance to the NFVO, where the instantiation request is used to instruct the NFVO to perform the instantiation operation, Create the first NS instance above.
  • the second NS instance with the lower priority can be preempted by the shrinking to release the second NS.
  • a part of the resources occupied by the instance, so that the resources released by the part are used to create the first NS instance, which not only improves resource utilization, but also ensures resource requirements of high-priority network services as much as possible, thereby improving high priority in the NFV system.
  • the creation request includes the service type information and the tenant information of the first NS instance;
  • the resource preemption policy is included in the OSS, and the resource preemption policy includes the service type priority of the first NS instance, and the tenant a correspondence between the priority and the preemption priority;
  • the method further includes: the OSS according to the service type information, the tenant information, and the resource of the first NS instance.
  • the preemption policy determines the service type priority and the tenant priority of the first NS instance.
  • the OSS determines the service with the first NS instance according to the service type priority, the tenant priority, and the resource preemption policy of the first NS instance.
  • the preemption priority of the first NS instance is the preemption priority of the first NS instance.
  • the resource preemption policy further includes a correspondence between the preemption priority and the preemption authority.
  • the OSS determines, according to the preemption priority of the first NS instance, the second NS that allows the preempted resource.
  • the example includes: the OSS finds that the preemption priority is lower than the preemption priority of the first NS instance in the resource preemption policy, and the preemption authority is a target service type priority and a target tenant priority that are allowed to be preempted; the OSS An NS instance that meets the target service type priority and the target tenant priority is used as the second NS instance.
  • the resource preemption policy further includes a preemption condition, where the preemption condition is used to indicate a performance indicator that the NS instance that is allowed to be preempted needs to be satisfied; wherein the OSS meets the target service type priority and the An NS instance of the target tenant priority, as the second NS instance, includes: the OSS as the target NS instance, the at least one NS instance that meets the target service type priority and the target tenant priority; the OSS determines each target Whether the NS instance satisfies the preemption condition; the OSS determines an NS instance as the second NS instance from the target NS instance that satisfies the preemption condition.
  • the condition of the second NS instance of the preempted resource can be further restricted, and the problem that the service quality of the second NS instance cannot be guaranteed is avoided after the second NS instance is excessively reduced.
  • the request for the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the second NS instance performs the shrink operation: the second NS instance Resources are being seized.
  • the NFVO that receives the shrink request can be triggered to save the resource information occupied by the current second NS instance.
  • the NFVO may further recover the resources that the second NS instance is preempted according to the resource information.
  • the OSS further sends an expansion request of the second NS instance to the NFVO, where the expansion request is used to indicate that the NFVO recovers the The resource that the second NS instance is preempted.
  • a second aspect of the present invention provides a method for instantiating a network service, comprising: receiving, by the NFVO, a contention request of a second NS instance sent by the OSS of the operation support system, where the preemption priority of the second NS instance is lower than that of the first NS instance Preempting the priority; the NFVO performs a shrinking operation on the resource occupied by the second NS instance to create the first NS instance by using the resource released after the second NS instance is reduced.
  • the method further includes: the NFVO receiving the instantiation request of the first NS instance sent by the OSS; and the NFVO performing the instantiation operation, To create the first NS instance.
  • the method further includes: the NFVO receiving the preemption identifier of the first NS instance sent by the OSS, where the preemption identifier is used to indicate the first An NS instance allows preemption of resources occupied by other NS instances; NFVO determines that resources required to create the first NS instance are insufficient; NFVO reserves the session of the first NS instance for a preset period of time.
  • the NFVO performs an instantiation operation to create the first NS instance, including: the NFVO performs an instantiation operation according to the reserved session of the first NS instance to create the first NS instance.
  • the NFVO does not need to release the conference to create the first NS instance, but the session of the first NS instance can be reserved for a preset period of time. If the resources required to create the first NS instance are sufficient in the preset time period, the NFVO can directly perform the instantiation operation using the session of the first NS instance that has been reserved, so that the creation time of the first NS instance can be shortened.
  • the request for the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the second NS instance performs the shrink operation: the second NS instance The resource is preempted; wherein, before the NFVO performs the shrinking operation on the resource occupied by the second NS instance, the method further includes: NFVO recording resource information occupied by the second NS instance; wherein performing an instantiation operation on the NFVO to create After the first NS instance, the NFVO receives the expansion request of the second NS instance sent by the OSS, and the NFVO recovers the preempted resource of the second NS instance according to the recorded resource information of the second NS instance.
  • an OSS including: an obtaining unit, configured to receive a creation request of a first NS instance to be created, where the creation request is used to indicate a preemption priority of the first NS instance; When the resource required for the first NS instance is insufficient, the second NS instance that is allowed to be preempted is determined according to the preemption priority of the first NS instance, and the preemption priority of the second NS instance is lower than the first NS instance.
  • a sending unit configured to send a shrink request of the second NS instance to the network function virtualization scheduling node NFVO, where the shrink request is used to instruct the NFVO to perform a shrink operation on the resource occupied by the second NS instance And creating the first NS instance by using the resource released after the second NS instance is reduced.
  • the acquiring unit is further configured to receive a message that the shrinking operation of the second NS instance sent by the NFVO is completed, and the sending unit is further configured to send the first NS instance to the NFVO.
  • the creation request includes the service type information and the tenant information of the first NS instance; the resource preemption policy is included in the OSS, and the resource preemption policy includes the service type priority of the first NS instance, Determining the relationship between the tenant priority and the preemption priority; the determining unit is further configured to determine the service type priority of the first NS instance according to the service type information, the tenant information, and the resource preemption policy of the first NS instance.
  • the tenant priority level is determined according to the service type priority, the tenant priority, and the resource preemption policy of the first NS instance, and the preemption priority corresponding to the service type priority and the tenant priority of the first NS instance is the first NS instance. Preemption priority.
  • the resource preemption policy further includes a correspondence between the preemption priority and the preemption authority.
  • the determining unit is specifically configured to: find that the preemption priority is lower than the first in the resource preemption policy.
  • the preemption priority of the NS instance, and the preemption authority is the target service type priority and the target tenant priority that are allowed to be preempted; and an NS instance that meets the target service type priority and the target tenant priority is used as the second NS. Example.
  • the resource preemption policy further includes a preemption condition, where the preemption condition is used to indicate a performance indicator that the NS instance that is allowed to be preempted needs to be satisfied; the determining unit is specifically configured to: meet the target service type.
  • the at least one NS instance of the priority and the target tenant priority is used as the target NS instance; determining whether each target NS instance satisfies the preemption condition; and determining one of the target NS instances satisfying the preemption condition as the second NS instance.
  • the sending unit is further configured to send, to the NFVO, a content expansion request of the second NS instance, where the capacity expansion request is used to indicate that the NFVO recovers the resource that the second NS instance is preempted.
  • the fourth aspect provides an NFVO, including: an obtaining unit, configured to receive a shrink request of the second NS instance sent by the OSS, where the preemption priority of the second NS instance is lower than the preemption priority of the first NS instance; And a condensing unit, configured to perform a shrinking operation on the resource occupied by the second NS instance.
  • the NFVO further includes an instantiation unit, where the acquisition unit is further configured to receive an instantiation request of the first NS instance sent by the OSS, and the instantiation unit is configured to perform an instantiation operation. To create the first NS instance.
  • the NFVO further includes a determining unit and an executing unit, where the acquiring unit is further configured to receive a preemptive identifier of the first NS instance sent by the OSS, where the preemptive identifier is used to indicate that the first NS instance allows Preempting the resources occupied by the other NS instances; the determining unit is configured to determine that the resources required to create the first NS instance are insufficient; and the executing unit is configured to reserve the session of the first NS instance for a preset time period.
  • the instantiation unit is specifically configured to perform an instantiation operation according to the reserved session of the first NS instance to create the first NS instance.
  • the request for the second NS instance includes a resource change identifier, where the resource change identifier is used to indicate that the second NS instance performs the shrink operation: the second NS instance
  • the resource is preempted;
  • the NFVO further includes a recording unit and a capacity expansion unit, the recording unit is configured to record the resource information occupied by the second NS instance, and the acquiring unit is further configured to receive the expansion request of the second NS instance sent by the OSS.
  • the expansion unit is configured to restore the preempted resource of the second NS instance according to the recorded resource information occupied by the second NS instance.
  • an OSS comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the OSS is running, the processor The computer executing the memory store executes instructions to cause the OSS to perform the NS instantiation method of any of the first aspects.
  • an NFVO comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the NFVO is running, the processor The computer executing the memory store executes instructions to cause the NFVO to perform the NS instantiation method of any of the second aspects.
  • a computer readable storage medium storing instructions for causing the NFVO or OSS to perform NS instantiation of the above aspects when stored on the NFVO or OSS .
  • a computer program comprising instructions that, when executed by a computer, cause the computer to perform the NS instantiation method of the various aspects described above.
  • the names of the OSS and the NFVO are not limited to the device itself. In actual implementation, the devices may appear under other names. As long as the functions of the respective devices are similar to the embodiments of the present invention, they are within the scope of the claims and the equivalents thereof.
  • FIG. 1 is a schematic structural view of a NFV system in the prior art
  • FIG. 2 is a schematic diagram 1 of interaction of an NS instantiation method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram 2 of interaction of an NS instantiation method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram 3 of interaction of an NS instantiation method according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of an OSS according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an NFVO according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram 1 of a hardware structure of an OSS (or NFVO) according to an embodiment of the present disclosure
  • FIG. 8 is a second schematic structural diagram of a hardware structure of an OSS (or NFVO) according to an embodiment of the present invention.
  • first and second are used for descriptive purposes only, and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated.
  • features defining “first” and “second” may include one or more of the features either explicitly or implicitly.
  • the meaning of "a plurality" is two or more unless otherwise specified.
  • An embodiment of the present invention provides a method for instantiating an NS, which can be applied to an NFV system as shown in FIG. 1.
  • the OSS can be configured with different priorities for different services in advance, that is, the priority of the service type.
  • the service type priority of the service A can be configured as the higher priority (which can be expressed as H), and the service type priority of the service B.
  • the service type of service C has a lower priority (which can be expressed as L).
  • tenant priority when a tenant subscribes to an NS instance, the tenant can subscribe to its own priority, that is, the tenant priority.
  • tenant priority of tenant 1 is the higher priority (H)
  • tenant priority of tenant 2 is the medium priority.
  • M Tenant 3's tenant priority is lower priority (L).
  • Information such as tenant priority can be stored in a database (DB, data base).
  • the OSS can configure the preemption priority, the preemption permission, and the preemption condition (optional) of the NS instance based on the service type priority and/or the tenant priority to form a resource preemption policy.
  • the preemption condition is used to indicate that the preemption permission is a performance indicator that the NS instance that is allowed to be preempted needs to be satisfied.
  • Table 1 an example of a resource preemption policy provided by an embodiment of the present invention.
  • the preemption priority is the highest, that is, the preemption priority is 1.
  • the resources of the NS instance are not allowed to be preempted.
  • the priority of the service type is M
  • the priority of the service type is set to 2.
  • the priority of the NS instance is not allowed to be preempted. If the priority of the tenant is M and the priority of the service type is M, The preemption priority is set to 4.
  • the NS instance's own resources are preempted, but the preemption condition of the memory is greater than 1G.
  • the preemption priority can be configured.
  • the lowest level, that is, the preemption priority is 6.
  • the resources of the NS instance itself are allowed to be preempted, and there is no preemption condition.
  • the resource preemption policy indicates the preemption authority corresponding to the preemption priority.
  • the resource preemption policy shown in Table 1 includes the preemption priority, service priority, tenant priority, preemption condition, and preemption authority. Correspondence between them.
  • preemption authority may be configured together with the priority of the subscribers, and the embodiment of the present invention does not limit this.
  • the BSS sends a creation request to the OSS to create a first NS instance, where the creation request may be used to indicate the preemption priority of the first NS instance.
  • the creation request may carry the service type priority and the tenant priority of the first NS instance; further, the OSS may interact with the NFVO to determine whether the resources required to create the first NS instance are sufficient, when the OSS determines to create the first
  • the OSS may determine the second NS instance that is allowed to be preempted according to the preemption priority of the first NS instance indicated in the foregoing creation request.
  • the preemption priority of the first NS instance for example, the OSS may determine the preemption priority of the first NS instance according to the service type priority and the tenant priority, and determine the preemption priority according to the resource preemption policy shown in Table 1.
  • the NS instance of the first NS instance is the second NS instance.
  • the NS instance that is preempted and the preemption condition is the second NS instance.
  • the OSS may further send a shrink request of the second NS instance to the NFVO, that is, instruct the NFVO to perform a shrink operation on the resource occupied by the second NS instance, and release part of the resources occupied by the second NS instance, so that the part is released.
  • the resource can be used to create the first NS instance.
  • the OSS sends an instantiation request of the first NS instance to the NFVO, that is, instructs the NFVO to perform the instantiation operation, and finally creates the resource.
  • the second NS instance with the lower priority can be preempted by the shrinking to release the second NS.
  • the condition of the second NS instance of the preempted resource can be further restricted, and the problem that the service quality of the second NS instance cannot be guaranteed cannot be guaranteed after the second NS instance is excessively reduced.
  • any one of the functional nodes or network elements involved in the NFV system may be implemented by one physical device. It may be implemented by multiple physical devices. Multiple functional nodes in the NFV system may be implemented by different physical devices or by the same physical device. It can be understood that any functional node in the NFV system may be a logical functional module in the physical device, or may be a logical functional module composed of multiple physical devices.
  • the foregoing NFV system can be applied to a future fifth-generation mobile communication (5 rd-generation, 5G) system, a long term evolution (LTE) communication system, and can also be applied to LTE.
  • 5G fifth-generation mobile communication
  • LTE long term evolution
  • an evolved communication system such as a LTE-A (long term evolution) system
  • WCDMA third-generation mobile communication
  • FIG. 3 A method for instantiating an NS provided by an embodiment of the present invention is as shown in FIG. 3, where the method includes:
  • the OSS receives a creation request of the first NS instance to be created.
  • the OSS may receive a creation request of the first NS instance to be created sent by the BSS.
  • the creation request is used to indicate the preemption priority of the first NS instance.
  • the creation request may include service type information and tenant information of the first NS instance.
  • the OSS can determine the service type priority of the first NS instance according to the service type information. For example, the service type priority of the first NS instance is higher. Level (H).
  • the OSS may also check whether the tenant priority of the tenant is stored in the OSS according to the received tenant information, for example, the tenant ID. If not, the OSS may obtain the tenant priority corresponding to the tenant ID from the DB, for example, the tenant priority is medium priority (M).
  • M medium priority
  • the OSS determines the preemption priority and the preemption authority of the first NS instance, that is, the preemption priority of the first NS instance, in the resource preemption policy shown in Table 1 according to the service type priority and the tenant priority of the first NS instance. It is 3, and the preemption permission is not allowed to be preempted.
  • the OSS sends a first instantiation request of the first NS instance to the NFVO, where the first instantiation request includes a preemption identifier.
  • step 302 after receiving the creation request of the first NS instance, the OSS sends a first instantiation request of the first NS instance to the NFVO, that is, triggers the NFVO to apply for the resource for the first NS instance, and performs an instantiation operation to create the first NS instance.
  • the first instantiation request includes a preemption identifier, where the preemption identifier is used to indicate whether the first NS instance is allowed to preempt the resources occupied by other NS instances. For example, when the preemption flag is "on”, the first NS instance is allowed to preempt the resources occupied by other NS instances. When the preemption flag is "off", the first NS instance is not allowed to be preempted. The resources occupied by the NS instance.
  • the following takes the example of preempting the resources occupied by other NS instances when the first NS instance is created.
  • the NFVO determines whether the resources required to create the first NS instance are sufficient.
  • the NFVO may determine, according to the preemption identifier, that resources occupied by other NS instances may be preempted when the first NS instance is created.
  • NFVO can interact with the VNFM in accordance with the existing NS instance creation process to determine if the resources required to create the first NS instance are sufficient.
  • the NFVO may perform the NS instantiation operation according to the existing NS instance creation process, and finally create the first NS instance.
  • steps 304-312 described below are performed.
  • the NFVO reserves the session of the first NS instance for a preset time period.
  • step 304 if the resources required for creating the first NS instance are insufficient, the NFVO may be able to preempt the resources of other NS instances when the first NS instance is created by using the preemption identifier. Therefore, the NFVO does not need to directly create the first one.
  • the NS instance will be released, but the session of the first NS instance can be reserved for a preset period of time.
  • the NFVO may start a timer, so that if the resources required to create the first NS instance are sufficient in the preset time period set by the timer, the NFVO will re-receive the instantiation request of the first NS instance sent by the OSS. Then, the NFVO can directly perform the instantiation operation using the session of the first NS instance that has been reserved, and does not need to acquire the session of the first NS instance again, so that the creation time of the first NS instance can be shortened.
  • the session and the like of the first NS instance are automatically released after the timer expires.
  • the NFVO sends an acknowledgement response to the OSS, where the response response is used to indicate that the resources required to create the first NS instance are insufficient.
  • the response sent by the NFVO to the OSS carries the result of the foregoing first instantiation request, that is, the resources required to create the first NS instance are insufficient. It should be noted that the embodiment of the present invention does not limit the execution sequence between step 304 and step 305.
  • the identifier of the session of the first NS instance may be carried in the response response, so that the OSS does not release the session of the first NS instance after receiving the identifier of the session.
  • the size of the resource required to create the first NS instance may also be carried in the response response.
  • the total amount of resources required to create the first NS instance is 50G
  • the currently available resource size is 40G.
  • the resource size required to create the first NS that is, 10G, may be directly added in addition to the currently available resource size. Carry in the above response.
  • the OSS according to the preemption priority of the first NS instance, finds that the preemption priority is lower than the preemption priority of the first NS instance in the resource preemption policy, and the preemption permission is the target service type priority and the target tenant priority that are allowed to be preempted. level.
  • the OSS selects an NS instance that meets the target service type priority and the target tenant priority as the at least one target NS instance.
  • the OSS has determined the preemption priority and the preemption authority of the first NS instance according to the service type information and the tenant information carried in the creation request of the first NS instance. Then, in order to successfully create the first NS instance, the resources that the first NS instance preempts need to be further determined, so that the preempted resources are used to create the first NS instance.
  • the OSS may search for a preemption priority lower than the first NS instance in the resource preemption policy according to the preemption priority of the first NS instance, and the preemption permission is a target service type that is allowed to be preempted. Priority and target tenant priority. Further, the NS instance that satisfies the target service type priority and the target tenant priority may be regarded as at least one target NS instance.
  • the preemption priority of the first NS instance is still 3 as an example.
  • the OSS can determine that the preemption priorities lower than the preemption priority 3 are: 4, 5, and 6. Moreover, when the preemption priority is: 4, 5, or 6, the preemption authority is allowed to be preempted.
  • the tenant priority is M
  • any NS instance with the service type priority of M (excluding the first NS instance) can be used as the target NS instance
  • the tenant priority is M
  • the service type priority is L.
  • Any NS instance can be used as the target NS instance.
  • Any NS instance with the lease priority of L and the service type priority of L can be used as the target NS instance.
  • the OSS can determine the target NS instance according to the service type priority and the tenant priority of each NS instance that is recorded, because the service type priority and the tenant priority of each NS instance are recorded in the OSS.
  • the OSS determines a second NS instance from the at least one target NS instance.
  • the OSS further determines whether each target NS instance in the at least one target NS instance satisfies a corresponding preemption condition.
  • the tenant priority of the target NS instance 1 is M
  • the priority of the service type is M
  • the preemption condition of the target NS instance 1 is: when the memory of the target NS instance 1 is greater than 1 G, the preemption is allowed.
  • the OSS can further query the memory size of the target NS instance 1. If the memory of the target NS instance 1 is greater than 1G, it can be used as the second NS instance. If the memory of the target NS instance 1 is less than or equal to 1G, the OSS cannot It serves as a second NS instance.
  • the target NS instance that meets the preemption condition may be multiple.
  • the OSS may use the target NS instance with the lowest preemption priority as the second NS instance according to the preemption priority of the target NS instance.
  • the OSS may also randomly select one of the target NS instances as the second NS instance, and the embodiment of the present invention does not impose any limitation.
  • the OSS can further obtain the resource size of the target NS instance, and then calculate the size of the resource that can be released by each target NS instance. Finally, according to the size of the resource that can be released by each target NS instance, the size of the resource can be satisfied.
  • One or more target NS instances of the resource size required by an NS instance are used as the second NS instance. In this way, the OSS can directly determine the second NS instance that can meet its resource requirements for the first NS instance, and accurately calculate the size of the resource released when the second NS instance subsequently performs the shrink operation.
  • the OSS sends a shrink request of the second NS instance to the NFVO, where the shrink request is used to instruct the NFVO to perform a shrink operation on the resource occupied by the second NS instance.
  • the OSS may send a shrink request to the NFVO for each second NS instance.
  • the NFVO performs a shrinking operation on the resources occupied by the second NS instance.
  • the NSVO After the OSS determines the preempted second NS instance, the NSVO sends a shrink request of the second NS instance to indicate that the NFVO receiving the shrink request performs a shrink operation on the resource occupied by the second NS instance.
  • the NS instance is created by using a network service descriptor (NSD) file, and the resource capacity of the NS instance is recorded in the NSD file by a deploy flavour ID.
  • NSD network service descriptor
  • the Deploy Flavour ID of all created NS instances is recorded in the OSS. Therefore, the OSS can determine the minimum size of the resource capacity of the second NS instance by searching for the Deploy Flavour ID of the second NS instance.
  • the content reduction request of the second NS instance sent by the OSS to the NFVO may carry the minimum specification of the resource capacity of the second NS instance.
  • NFVO can shrink the second NS instance to the minimum specification of its resource capacity through a shrink operation. This ensures the normal operation of the second NS instance.
  • the OSS may carry the resource size into the above-mentioned shrink request. Sended to NFVO, NFVO can release the same resource size as the above resources through the shrink operation.
  • the content request identifier of the second NS instance may be further configured to: the resource change identifier is used to indicate that the second NS instance is subjected to the shrinking operation, and the resource of the second NS instance is preempted.
  • the NFVO that receives the contention request can save the resource information occupied by the current second NS instance.
  • the current second NS instance occupies 80G resources.
  • the NFVO may further recover the resource that the second NS instance is preempted according to the resource information.
  • the OSS sends a second instantiation request of the first NS instance to the NFVO to determine whether the resources required to create the first NS instance are sufficient.
  • the NFVO After performing the shrinking operation on the resources occupied by the second NS instance, the NFVO sends a message to the OSS to complete the shrinking operation. After the NFVO performs the shrinking operation on the resources occupied by the second NS instance, part of the NSVO is originally occupied by the second NS instance. The resource is released. Therefore, after receiving the message that the shrink operation is completed, the OSS may continue to try to send a second instantiation request of the first NS instance to the NFVO, and the NFVO determines whether the resources required for creating the first NS instance are sufficient at this time. And feedback the determined results to OSS.
  • the above steps 304-310 may be repeatedly performed until the resources required to create the first NS instance are sufficient.
  • step 312 is performed.
  • the NFVO performs an instantiation operation of the first NS instance to create a first NS instance.
  • the second NS instance with a lower priority can be preempted by the shrinking capacity.
  • the shrinking capacity To release a part of the resources occupied by the second NS instance, and use the partially released resources to create the first NS instance, which not only improves resource utilization, but also ensures resource requirements of high-priority network services as much as possible.
  • the normal operation of the second NS instance that is preempted by the resource is not interfered with.
  • the resources that the second NS instance is preempted can also be restored by the following steps 401-402.
  • the OSS sends a request for expansion of the second NS instance to the NFVO.
  • the NFVO performs the capacity expansion operation of the second NS instance according to the resource information occupied by the second NS instance.
  • the NFVO sends a message that the expansion operation is completed to the OSS.
  • step 401 there are two scenarios in which the OSS sends a request for expansion of the second NS instance to the NFVO.
  • the OSS can periodically send a request for the expansion of the second NS instance to the NFVO.
  • the NFVO determines whether the resources available in the current NFV system are sufficient to recover the resources that the second NS instance is preempted, and the capacity expansion request carries the identifier of the second NS instance.
  • the OSS can determine whether the available resource size in the current NFV system is greater than or equal to the second NS instance according to the real-time resource occupancy of each NS instance.
  • the size of the occupied resource if the size of the resource available in the current NFV system is greater than or equal to the size of the resource occupied by the second NS instance, the OSS may be triggered to send a request for the expansion of the second NS instance to the NFVO, and the expansion request is also Carry the identifier of the second NS instance.
  • the foregoing resource change identifier may also be carried in the content expansion request of the second NS instance, which is not limited in this embodiment of the present invention.
  • the NFVO Since in step 310, the NFVO has saved the resource information occupied by the second NS instance before performing the shrinking operation, in step 402, after the NFVO receives the expansion request of the second NS instance, if the current NFV If the size of the resource available in the system is greater than or equal to the size of the resource occupied by the second NS instance, the NFVO may find the resource information occupied by the saved second NS instance according to the identifier of the second NS instance. Then, the NFVO is based on the second NS. The resource information occupied by the instance is used to expand the capacity of the second NS instance, and the resources occupied by the second NS instance are expanded to the capacity specifications before the second NS instance is not reduced.
  • step 403 the message that the expansion operation is completed is sent to the OSS.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the network elements.
  • the foregoing OSS, NFVO, etc. in order to implement the above functions, include hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the embodiments of the invention.
  • the embodiments of the present invention may divide the functional modules of the OSS, the NFVO, and the like according to the foregoing method examples.
  • each functional module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 5 shows a possible structural diagram of the OSS involved in the foregoing embodiment, which includes an obtaining unit 51, a determining unit 52 and a transmitting unit 53 in the case of dividing the respective functional modules by corresponding functions.
  • the obtaining unit 51 is configured to support the OSS to perform the process 301 in FIG. 3 and the processes 501-503 in FIG. 5; the determining unit 52 is configured to support the NFVO to perform the processes 306-308 in FIG. 3; the transmitting unit 53 is configured to support the NFVO execution.
  • FIG. 6 shows a possible structural diagram of the NFVO involved in the foregoing embodiment, where the NFVO includes: an obtaining unit 61, a condensing unit 62, and an instantiating unit. 63, expansion unit 64, determination unit 65, execution unit 66 and recording unit 67.
  • the condensing unit 62 is configured to support the NFVO to perform the process 310 in FIG. 3; the instantiation unit 63 is configured to support the NFVO to perform the process 312 in FIG. 3; the expansion unit 64 is configured to support the NFVO to perform the process 402 in FIG. 4; the determining unit 65 The NFVO is used to support the process 303 in FIG. 3; the execution unit 66 is configured to support the NFVO to perform the process 304 in FIG.
  • the obtaining unit 61 is configured to support the NFVO to receive the volume reduction request of the second NS instance sent by the OSS, the second NS
  • the preemption priority of the instance is lower than the preemption priority of the first NS instance; if the resources required to create the first NS instance are sufficient, the instantiation request of the first NS instance sent by the OSS is received; and the first NS instance sent by the OSS is received.
  • a preemption identifier is used to indicate that the first NS instance is allowed to preempt the resources occupied by the other NS instance, and the second NS instance is used to support the NFVO to record the second NS instance.
  • Resource information All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.
  • FIG. 7 shows a possible structural diagram of the OSS (or NFVO) involved in the above embodiment.
  • the OSS (or NFVO) includes a processing module 72 and a communication module 73.
  • the processing module 72 is configured to control and manage the actions of the OSS (or NFVO).
  • the processing module 72 is configured to support the OSS (or NFVO) to perform the processes 301-312 in FIG. 3 and the processes 401-403 in FIG. 4, and / or other processes for the techniques described herein.
  • the communication module 73 is used to support communication of the OSS (or NFVO) with other network entities.
  • the OSS (or NFVO) may also include a storage module 71 for storing program code and data of the OSS (or NFVO).
  • the processing module 72 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out various exemplary logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the invention.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 73 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 61 can be a memory.
  • the processing module 72 is a processor
  • the communication module 73 is a transceiver
  • the storage module 71 is a memory
  • the OSS (or NFVO) involved in the embodiment of the present invention may be the OSS (or NFVO) shown in FIG. 8.
  • the OSS (or NFVO) includes a processor 82, a transceiver 81, a memory 83, and a bus 84.
  • the transceiver 81, the processor 82, and the memory 83 are connected to each other through a bus 84.
  • the bus 84 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • an embodiment of the present invention further provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, may cause the computer to perform the above steps 301-312, or the related NS instance in steps 401-403 Method.
  • an embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores instructions, when executed on a computer, causes the computer to execute the NS instantiation method in any of the above embodiments. .
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil d'instanciation d'un service de réseau qui se rapportent au domaine technique des communications, et qui permettent de garantir les exigences de ressources d'un service de réseau à haute priorité autant que possible dans le cas de ressources insuffisantes, et d'améliorer la qualité de service du service de réseau à haute priorité dans un système NFV. Le procédé comprend les étapes suivantes : un OSS reçoit une demande de création pour une première instance de NS à créer, la demande de création étant utilisée pour indiquer une priorité de préemption de la première instance de NS ; lorsque des ressources requises pour créer la première instance de NS sont insuffisantes, l'OSS détermine, en fonction de la priorité de préemption de la première instance de NS, une seconde instance de NS permettant une préemption de ressources ; et l'OSS envoie, à un NFVO, une demande de réduction de capacité destinée à la seconde instance de NS, la demande de réduction de capacité étant utilisée pour ordonner au NFVO d'effectuer une opération de réduction de capacité sur des ressources occupées par la seconde instance de NS, de façon à créer la première instance de NS à l'aide des ressources libérées après que la capacité de la seconde instance de NS a été réduite.
PCT/CN2018/072905 2017-02-15 2018-01-16 Procédé et appareil d'instanciation d'un service de réseau Ceased WO2018149263A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710081686.5 2017-02-15
CN201710081686.5A CN108429631B (zh) 2017-02-15 2017-02-15 一种网络业务实例化的方法及装置

Publications (1)

Publication Number Publication Date
WO2018149263A1 true WO2018149263A1 (fr) 2018-08-23

Family

ID=63155472

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/072905 Ceased WO2018149263A1 (fr) 2017-02-15 2018-01-16 Procédé et appareil d'instanciation d'un service de réseau

Country Status (2)

Country Link
CN (1) CN108429631B (fr)
WO (1) WO2018149263A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110908808A (zh) * 2018-09-14 2020-03-24 网宿科技股份有限公司 一种控制api调用资源的方法和装置
WO2020057490A1 (fr) * 2018-09-17 2020-03-26 中兴通讯股份有限公司 Procédé et appareil de gestion de ressources de service, dispositif de réseau, et support de stockage lisible par machine
CN113032134A (zh) * 2019-12-24 2021-06-25 阿里巴巴集团控股有限公司 一种实现云计算资源分配的方法及装置和云管理服务器
GB2591521A (en) * 2020-02-03 2021-08-04 Samsung Electronics Co Ltd Improvements in and relating to a multi-access edge computing (MEC) network

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020037689A1 (fr) * 2018-08-24 2020-02-27 Nokia Shanghai Bell Co., Ltd. Appareil et procédé de gestion de priorités d'objets gérés dans un réseau 5g
CN113407317A (zh) 2018-09-11 2021-09-17 华为技术有限公司 一种资源调度方法及装置
CN111726237A (zh) * 2019-03-18 2020-09-29 中兴通讯股份有限公司 处理ns优先级的方法、nfvo、存储介质及系统
CN112114958B (zh) * 2019-06-21 2025-05-13 上海哔哩哔哩科技有限公司 资源隔离方法、分布式平台、计算机设备和存储介质
CN110716809B (zh) * 2019-10-21 2022-06-21 北京百度网讯科技有限公司 用于调度云资源的方法和装置
CN112887121B (zh) 2019-11-29 2022-08-19 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
CN113034166B (zh) * 2019-12-24 2024-09-06 阿里巴巴集团控股有限公司 一种获取云服务的方法、装置及云管理服务器
CN113055416B (zh) * 2019-12-26 2022-07-22 华为技术有限公司 容器集群节点资源池的管理方法和装置
CN113900766B (zh) * 2020-07-06 2025-08-05 华为云计算技术有限公司 一种计算实例规格变更方法、装置及设备
CN114513424B (zh) * 2020-10-26 2024-09-27 中国移动通信有限公司研究院 网络服务扩缩容处理方法、装置、设备及可读存储介质
CN112486642B (zh) * 2020-11-25 2024-01-19 广州虎牙科技有限公司 资源调度方法、装置、电子设备及计算机可读存储介质
CN115114636A (zh) * 2021-03-09 2022-09-27 华为技术有限公司 访问控制方法、相关装置及系统
CN114356558B (zh) * 2021-12-21 2022-11-18 北京穿杨科技有限公司 一种基于集群的缩容处理方法及装置
CN115087123B (zh) * 2022-06-14 2025-02-11 Oppo广东移动通信有限公司 物理层调度装置、方法、芯片、终端、系统和存储

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法
WO2016070729A1 (fr) * 2014-11-06 2016-05-12 华为技术有限公司 Procédé d'instanciation de vnf et dispositif de gestion d'élément de réseau
WO2016115844A1 (fr) * 2015-01-19 2016-07-28 华为技术有限公司 Procédé, appareil et système d'association d'un ns à une vnf

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100531453C (zh) * 2006-08-05 2009-08-19 华为技术有限公司 建立mbms业务信道及其辅公共控制物理信道的方法
CN104601492B (zh) * 2014-12-29 2018-11-09 上海华为技术有限公司 一种nfv架构下进行业务流控的方法及装置
CN105812171B (zh) * 2014-12-31 2019-06-11 华为技术有限公司 一种虚拟化的网络功能vnf控制方法和设备
CN106301829B (zh) * 2015-05-21 2019-08-09 华为技术有限公司 一种网络业务扩容的方法和装置
CN106341324B (zh) * 2016-09-30 2019-06-14 赛特斯信息科技股份有限公司 Sdn和nfv融合网络动态建立sdn控制器的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
WO2016070729A1 (fr) * 2014-11-06 2016-05-12 华为技术有限公司 Procédé d'instanciation de vnf et dispositif de gestion d'élément de réseau
WO2016115844A1 (fr) * 2015-01-19 2016-07-28 华为技术有限公司 Procédé, appareil et système d'association d'un ns à une vnf
CN105429780A (zh) * 2015-10-30 2016-03-23 南京优速网络科技有限公司 一种虚拟化网络服务业务自动生成和动态监控的方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110908808A (zh) * 2018-09-14 2020-03-24 网宿科技股份有限公司 一种控制api调用资源的方法和装置
CN110908808B (zh) * 2018-09-14 2023-06-23 深圳爱捷云科技有限公司 一种控制api调用资源的方法和装置
WO2020057490A1 (fr) * 2018-09-17 2020-03-26 中兴通讯股份有限公司 Procédé et appareil de gestion de ressources de service, dispositif de réseau, et support de stockage lisible par machine
CN113032134A (zh) * 2019-12-24 2021-06-25 阿里巴巴集团控股有限公司 一种实现云计算资源分配的方法及装置和云管理服务器
GB2591521A (en) * 2020-02-03 2021-08-04 Samsung Electronics Co Ltd Improvements in and relating to a multi-access edge computing (MEC) network
GB2591521B (en) * 2020-02-03 2023-03-29 Samsung Electronics Co Ltd Improvements in and relating to a multi-access edge computing (MEC) network

Also Published As

Publication number Publication date
CN108429631A (zh) 2018-08-21
CN108429631B (zh) 2021-01-15

Similar Documents

Publication Publication Date Title
WO2018149263A1 (fr) Procédé et appareil d'instanciation d'un service de réseau
US12393436B2 (en) Method for deploying virtual machine and container, and related apparatus
US20240272930A1 (en) Method and Apparatus for Creating Virtual Machine
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
EP3313023B1 (fr) Procédé et appareil de gestion de cycle de vie
WO2015196931A1 (fr) Procédé et dispositif d'attribution de ressources virtuelles sur la base d'e/s de disque
CN107251486B (zh) 一种扩展联动的方法、装置及系统
WO2018006676A1 (fr) Procédé et appareil de traitement de ressources d'accélération et système de virtualisation de fonction de réseau
WO2018145615A1 (fr) Procédé et système de déploiement de vnf
CN107665143B (zh) 资源管理方法、装置及系统
WO2022007631A1 (fr) Procédé et appareil de gestion multi-occupants
WO2016183799A1 (fr) Procédé d'accélération de matériel et dispositif pertinent
CN114296891B (zh) 任务的调度方法、系统、计算设备、存储介质及程序产品
CN106161076A (zh) 虚拟网络功能扩展方法和装置
CN106664259B (zh) 虚拟网络功能扩容的方法和装置
WO2019062995A1 (fr) Procédé, dispositif et système de gestion de réseau
CN113849259A (zh) 一种虚拟机和容器混合调度系统、方法、调度器及装置
WO2017041650A1 (fr) Procédé et dispositif d'extension de service de cohérence distribué
CN109905258B (zh) PaaS的管理方法、装置及存储介质
CN115686843A (zh) 一种异构虚拟化多租户资源隔离调度方法及设备
CN115063282A (zh) 一种gpu资源调度方法、装置、设备及存储介质
CN107408058B (zh) 一种虚拟资源的部署方法、装置及系统
CN107534678B (zh) 建立vnfm与vim之间的连接的方法、装置及系统
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
WO2018014351A1 (fr) Procédé et appareil de configuration de ressources

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: 18754271

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: 18754271

Country of ref document: EP

Kind code of ref document: A1