EP3567803B1 - Procédé, dispositif et système de gestion de stratégie - Google Patents

Procédé, dispositif et système de gestion de stratégie Download PDF

Info

Publication number
EP3567803B1
EP3567803B1 EP18744251.2A EP18744251A EP3567803B1 EP 3567803 B1 EP3567803 B1 EP 3567803B1 EP 18744251 A EP18744251 A EP 18744251A EP 3567803 B1 EP3567803 B1 EP 3567803B1
Authority
EP
European Patent Office
Prior art keywords
policy
composite
management
nfvo
group
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.)
Active
Application number
EP18744251.2A
Other languages
German (de)
English (en)
Other versions
EP3567803A1 (fr
EP3567803A4 (fr
Inventor
Haitao Xia
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
Priority to EP20213360.9A priority Critical patent/EP3855680A1/fr
Publication of EP3567803A1 publication Critical patent/EP3567803A1/fr
Publication of EP3567803A4 publication Critical patent/EP3567803A4/fr
Application granted granted Critical
Publication of EP3567803B1 publication Critical patent/EP3567803B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/0893—Assignment of logical groups to network 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/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • 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/0894—Policy-based network configuration management
    • 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/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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45566—Nested virtual machines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution

Definitions

  • This application relates to the field of communications technologies, and in particular, to a policy management method and system, and an apparatus applicable to an NFV field.
  • NFV Network Function Virtualization
  • a telecommunications network operator uses a virtualization technology in the information technology (IT, Information Technology) field to decouple software and hardware for implementation of some telecommunications network functions in a general-purpose cloud server, switch, and memory, to implement rapid and efficient deployment of a network service (NS, Network Service), and achieve an operation target of reducing a capital expenditure (CAPEX, Capital expenditure) and an operating expense (OPEX, operating expense).
  • the telecommunications network function needs to be implemented in a software manner, can run on hardware of a general-purpose server, and can be migrated, instantiated, and deployed at different physical locations of a network as required, and no new device needs to be installed.
  • a scenario of providing an NS across management domains exists in deployment of a network service (Network Service, NS).
  • NS Network Service
  • This scenario may occur when a large service provider provides a global NS through cooperation of each branch, or a lease service of the NS is provided between different service providers by using a network sharing protocol.
  • the global NS is referred to as a composite NS
  • the composite NS includes a plurality of nested NSs
  • each nested NS is provided in a management domain different from that of the composite NS.
  • policies of different levels or different policies of a same level may conflict with each other due to diversity of functional entities that generate or create the policies.
  • an NFV MANO policy management technology is capable of performing only a management operation on a single policy.
  • a policy of a composite NS and a policy of a nested NS are separately performed, and this cannot meet a policy management requirement in the scenario of providing a composite NS across management domains. Therefore, a new policy management method needs to be proposed.
  • a possible NFV system includes an OSS/BSS (Operation Support System/Business Support System, operation support system/business support system) (101), an EMS (Element Management System, element management system) (102), a VNF (Virtualized Network Function, virtualized network function) (103), an NFVI (Network Function Virtualization Infrastructure, network function virtualization infrastructure) (104), and an NFV MANO (NFV Management and Orchestration, NFV management and orchestration) (105).
  • OSS/BSS Operaation Support System/Business Support System, operation support system/business support system
  • EMS Element Management System, element management system
  • VNF Virtualized Network Function, virtualized network function
  • NFVI Network Function Virtualization Infrastructure
  • 104 Network Function Virtualization Infrastructure
  • NFV MANO NFV Management and Orchestration, NFV management and orchestration
  • the NFV MANO includes a plurality of management function entities: an NFVO (NFV Orchestrator, network function virtualization orchestrator) (106), a VNFM (Virtualized Network Function Manager, virtualized network function manager) (107), and a VIM (Virtualized Infrastructure Manager, virtualized infrastructure manager) (108).
  • NFVO NFV Orchestrator, network function virtualization orchestrator
  • VNFM Virtualized Network Function Manager, virtualized network function manager
  • VIM Virtualized Infrastructure Manager, virtualized infrastructure manager
  • the OSS/BSS (101) mainly provides a telecommunications service operator with an integrated network management and service operation function, including network management (for example, fault monitoring and network information collection), accounting management, policy management, customer service management, and the like.
  • network management for example, fault monitoring and network information collection
  • accounting management for example, policy management
  • policy management for example, customer service management
  • customer service management for example, customer service management
  • the OSS/BSS undertakes a function of a policy decision entity.
  • the NFVO (106) implements network service life cycle management (NS LCM, Network Service Life cycle Management), and cooperates with the VNFM to implement functions such as life cycle management of the VNF.
  • NS LCM Network Service Life cycle Management
  • the VNFM (107) implements life cycle management of a virtualized network function VNF, including management and processing of a VNFD, initialization of a VNF instance, scaling out/in of the VNF, and termination of the VNF instance, and can receive a flexible scaling (scaling) policy delivered by the NFVO to implement flexible scaling of the VNF.
  • the VIM (108) is mainly responsible for management, monitoring, and fault reporting of a hardware resource and a virtualized resource at an infrastructure layer, and providing a virtualized resource pool for an upper-layer application.
  • FIG. 2 shows a possible architecture of a composite NS provided across management domains, including a plurality of management domains.
  • Each management domain includes a set of NFV MANO management function entities shown in FIG. 1 .
  • the NFVO is responsible for providing a network service and life cycle management of the network service in the management domain.
  • a management domain in which an NFVO-2 is located provides an NS-A
  • a management domain in which an NFVO-3 is located provides an NS-B
  • a management domain in which an NFVO-1 is located provides a composite NS in cooperation with the management domains in which the NFVO-2 and the NFVO-3 are located.
  • the NS-A and the NS-B are components of the composite NS, and the NS-A and the NS-B are referred to as nested NSs.
  • the NFVO-1, the NFVO-2, and the NFVO-3 form an umbrella-shaped management architecture.
  • the NFVO-1 is responsible for life cycle management of the composite NS
  • the NFVO-2 and the NFVO-3 are responsible for life cycle management of their respective nested NSs
  • the NFVO-1 communicates with the NFVO-2/the NFVO-3 through an Or-Or interface.
  • a network of a telecommunications operator with a relatively large scale has two layers of structures: one head office network and a plurality of subsidiary office networks.
  • Each subsidiary office network has a management domain configured with an NFVO.
  • An NFVO in the head office network is equivalent to the NFVO-1 in FIG. 2
  • an NFVO in each subsidiary office network is equivalent to the NFVO-2 or the NFVO-3 in FIG. 2 .
  • the head office network may be designated to provide a user management and policy control network service forming the VoLTE
  • a subsidiary office network A provides an EPC (Evolved Packet Core, evolved packet core) network service forming the VoLTE
  • a subsidiary office network B provides an IMS core network network service forming the VoLTE.
  • another network service in addition to the EPC network service and the IMS core network network service may further be required, or there may be another network service combination. Details are not described herein.
  • the policy decision entity in this application may be an OSS/BSS when being mapped to FIG. 2 , or may be an independent policy manager.
  • the OSS is used as an example to describe how the policy decision entity performs cooperative policy management across management domains.
  • the method is also applicable to a scenario in which the independent policy manager is used as the policy decision entity.
  • a composite NS architecture shown in FIG. 2 is used as an example.
  • Management domains in which the composite NS, a nested NS-A, and a nested NS-B are located are configured with life cycle management policies of respective NSs.
  • an NS cure policy is used as a management policy, and it is assumed that NS cure policies of the management domains are respectively as follows:
  • a cure policy 1 of the composite NS When receiving a virtual resource fault alarm of a severe fault level, the NFVO-1 migrates a member VNF instance (which does not include a member nested NS instance) of the composite NS instance to another available standby virtual machine.
  • a cure policy 2 of the nested NS-A When receiving a virtual resource fault alarm of a severe fault level, the NFVO-2 migrates a member VNF instance of the nested NS instance to another available container.
  • a cure policy 3 of the nested NS-B When detecting that a quantity of bytes sent/received by a virtual link per second is less than a preset threshold, the NFVO-3 migrates a member VNF instance of the nested NS instance to another available standby virtual machine.
  • an LCM policy of the composite NS and LCM policies of the nested NSs need to be managed in a unified manner.
  • a policy management method is proposed in this embodiment of the present invention. The LCM policy of the composite NS and the LCM policies of the nested NSs forming the composite NS are managed in a unified and cooperative manner as a policy group.
  • the NFVO-1 in the management domain of the composite NS needs to perform an operation on the LCM policy of the composite NS in the management domain, and in addition, needs to trigger the NFVO-2 in the management domain of the nested NS forming the composite NS to cooperate to perform an operation on the LCM policy of the nested NS, to ensure consistency between the LCM policy of the composite NS and the LCM policy of the nested NS forming the composite NS.
  • a policy conflict caused by separately setting and managing policies in the management domains is avoided, system maintenance efficiency is improved, and system running reliability and stability are ensured.
  • the following further describes the technical solutions of the present invention by using the composite NS architecture shown in FIG. 2 and the NS cure policies of the foregoing management domains as an example.
  • FIG. 3 is a schematic flowchart of creating a policy group based on the system architecture of the composite NS shown in FIG. 2 .
  • the OSS in the figure undertakes a function of a policy decision entity.
  • the NFVO-1 is located in a management domain of a composite NS, and undertakes a function of a policy execution entity in the management domain of the composite NS.
  • Group Descriptor basic description information
  • the identification information of the member policy includes an LCM policy identifier of one composite NS and LCM policy identifiers of one or more nested NSs forming the composite NS. It should be noted that identifiers of member policies need to be globally unique in the composite NS. In other words, the NFVO-1 can uniquely identify the policy. A numbering rule of the policy identifier is not within the scope of the technical solution of the present invention. Details are not described herein.
  • the NFVO-1 receives the request message, allocates an identifier to the policy group, and records a correspondence between the identifier of the policy group and an identifier of a member policy in the policy group.
  • the NFVO-1 sends a policy group creation response message to the OSS, where the message carries information about a newly allocated identifier of the policy group.
  • the OSS records the identifier, and subsequently instructs, by using the identifier of the policy group, the NFVO-1 to perform a cooperative operation on the member policy in the policy group.
  • the foregoing NS cure policies in the management domains are used as an example.
  • the created policy group is an NS cure policy group 1, and includes the following member policies: ⁇ a cure policy 1 of a composite NS, a cure policy 2 of a nested NS-A, and a cure policy 3 of a nested NS-B ⁇ .
  • the policy group may be created by using the method shown in FIG. 3 .
  • the policy decision entity requests the NFVO-1 to create the policy group, or the policy group may be created by separately performing configuration on the policy decision entity and the NFVO-1.
  • the policy group configuration data of the policy decision entity is consistent with policy group configuration data of the NFVO-1, for example, consistency between the identifiers of the policy groups and consistency between the identifiers of the member policies in the policy groups.
  • the OSS may request the NFVO-1 to perform, on a per-policy group basis, a corresponding management operation on the member policy in the policy group based on a requirement.
  • FIG. 4 is a schematic flowchart of performing, based on the system architecture of the composite NS shown in FIG. 2 , cooperative policy update on the NS cure policy group 1 created in FIG. 3 .
  • an OSS undertakes a function of a policy decision entity; when an NFVO-1 is located in a management domain of a composite NS; for the OSS, the NFVO-1 undertakes a function of a policy execution entity in the management domain of the composite NS; for an NFVO-2, the NFVO-1 implements a function of the OSS as a proxy and undertakes the function of the policy decision entity, to deliver a policy management operation request to the NFVO-2; when the NFVO-2 is located in a management domain of a nested NS-A, the NFVO-2 undertakes a function of a policy execution entity in the management domain of the nested NS-A; and when an NFVO-3 is located in a management domain of a nested NS-B, the NFVO-3 undertake
  • the cure policy 1 of the composite NS may be learned from the foregoing descriptions of the cure policy 1 of the composite NS, the cure policy 2 of the nested NS-A, and the cure policy 3 of the nested NS-B that the NS cure policy in the management domain of the composite NS is different from the NS cure policy in the management domain of each associated nested NS.
  • decision conditions for performing NS cure are different in different management domains, or specific manners of performing cure are different, and as a result, a device status in the management domain of the composite NS may be different from that in the management domain of each nested NS.
  • management domains have met a decision condition for an NS cure policy, and VNF instance migration has been started; but some management domains may not meet the decision condition for the NS cure policy. Consequently, that the composite NS provides a network service as a whole, or performs a life cycle maintenance operation of the network service as a whole may be probably affected. Therefore, it is necessary to update or modify all member policies in the policy group, to ensure consistency between the member policies.
  • Step S401 An OSS initiates a policy update request to an NFVO-1, where a request message includes an identifier of the cure policy 1 of the composite NS, an identifier of an NS cure policy group 1, and a policy update parameter.
  • the policy update parameter includes a condition or an action for policy execution.
  • the condition for NS cure is "a virtual resource fault alarm of a severe fault level is received”
  • the action for NS cure is "a member VNF instance of the NS instance is migrated to another available standby virtual machine or an available container”.
  • a policy management operation request message sent by the OSS to the NFVO-1 may not carry a policy identifier of the composite NS.
  • the NFVO-1 may learn of the identifier of the member policy in the policy group by using the identifier of the policy group, and the identifier of the member policy includes the policy identifier of the composite NS.
  • Step S402 The NFVO-1 updates the cure policy 1 of the composite NS in the local management domain, and returns a policy update response to a policy manager, where the response message carries a result obtained after the cure policy 1 of the composite NS is updated.
  • Step S403 The NFVO-1 obtains an identifier of an LCM policy of the nested NS in the policy group based on an identifier of the NS cure policy group 1 received in step S401, namely, an identifier of the cure policy 2 of the nested NS-A and an identifier of the cure policy 3 of the nested NS-B; and then sends a policy update request message to the NFVO-2, where the policy update request message includes the identifier of the cure policy 2 of the nested NS-A and the policy update parameter, where the policy update parameter is consistent with the policy update parameter received by the NFVO-1 in step S401.
  • the NFVO-1 may subscribe, to the NFVO-2 and the NFVO-3 by using an existing subscription notification mechanism, information about policy instances in the nested NS-A and the nested NS-B. In this way, NFVOs to which the cure policy 2 of the nested NS-A and the cure policy 3 of the nested NS-B belong may be learned of.
  • Step S404 The NFVO-2 updates the cure policy 2 of the nested NS-A based on the received policy update request message, and returns a policy update response message to the NFVO-1.
  • Step S405 Similar to step S403, the NFVO-1 initiates a policy update request message of the cure policy 3 of the nested NS-B to the NFVO-3, where the request message includes the identifier of the cure policy 3 of the nested NS-B and the policy update parameter.
  • the NFVO-1 cooperative policy management operations initiated by the NFVO-1 for management domains of a plurality of nested NSs forming the composite NS have no time sequence, namely, S403 and S405 have no time sequence. This processing principle is also applicable to messages in the following figure. Details are not described again.
  • Step S406 Similar to step S404, the NFVO-3 updates the cure policy 3 of the nested NS-B based on the received policy update request message, and returns a policy update response message to the NFVO-1.
  • NS cure policies in the management domain of the composite NS and management domains of two nested NSs are updated.
  • Member policies in the policy group are all updated, so that the LCM policy of the composite NS is consistent with the LCM policies of the nested NSs.
  • An updated policy is as follows:
  • the cure policy 1 of the composite NS When receiving a virtual resource fault alarm of a severe fault level, the NFVO-1 migrates a member VNF instance (which does not include a member nested NS instance) of the composite NS instance to another available standby virtual machine or an available container.
  • the cure policy 2 of the nested NS-A When receiving a virtual resource fault alarm of a severe fault level, the NFVO-2 migrates a member VNF instance of the nested NS instance to another available standby virtual machine or an available container.
  • the cure policy 3 of the nested NS-B When receiving a virtual resource fault alarm of a severe fault level, the NFVO-3 migrates a member VNF instance of the nested NS instance to another available standby virtual machine or an available container.
  • the policy execution entity NFVO-1 in the management domain of the composite NS shares a workload of the policy decision entity OSS.
  • the NFVO-1 performs an operation on the policy in the local management domain, and in addition, triggers policy operation in the management domain of the nested NS. This improves policy management execution efficiency in a scenario of providing a composite NS across management domains, and ensures consistency between the LCM policy of the composite NS and the LCM policy of the nested NS in the policy group.
  • a notification message may be sent to the OSS, to notify the OSS of a policy update result of the nested management domain.
  • the notification message may be sent by the NFVO-1 after step S406, or may be separately sent by the NFVO-2 and the NFVO-3 after the policy update of the nested management domain is completed.
  • the OSS may alternatively subscribe, to the NFVO in the management domain of the nested NS, status information of the policy by using an existing subscription notification mechanism.
  • the NFVO in the management domain of the nested NS sends a notification message to the OSS, to notify the OSS of a policy change status.
  • the identifier of the policy group may be used as an indication that the policy decision entity requires to perform a policy management operation on the member policy in the policy group, and directly initiates a policy management operation (for example, step S403 to step S406) on the LCM policy of the nested NS in the policy group.
  • a policy management operation for example, step S403 to step S406
  • it may be determined, based on a local policy, whether to perform the policy management operation on the LCM policy of the nested NS in the policy group.
  • FIG. 5 is a schematic flowchart of performing cooperative deletion on a member policy in the foregoing NS cure policy group 1 based on the system architecture of the composite NS shown in FIG. 2 .
  • a function of a functional entity in FIG. 5 is the same as a function of the functional entity in FIG. 4 . Details are not described again.
  • an OSS sends a policy deletion request message to an NFVO-1 in a management domain of a composite NS, where the policy deletion request message includes an identifier of the NS cure policy group 1, and optionally, may further include an identifier of a cure policy 1 of the composite NS.
  • the NFVO-1 deletes the cure policy 1 of the composite NS in the local management domain based on the request message, and separately sends a policy deletion request to an NFVO-2 and an NFVO-3, to request to delete a cure policy 2 of a nested NS-A and a cure policy 3 of a nested NS-B in the policy group.
  • An identifier of the cure policy 2 of the nested NS-A and an identifier of the cure policy 3 of the nested NS-B are respectively carried in the policy deletion request message in S503 and S505. There is no time sequence between the messages in S503 and S505.
  • FIG. 6 is a schematic flowchart of cooperatively activating a member policy in a policy group.
  • An OSS cooperatively activates the member policy in the policy group by using an NFVO-1 without needing to separately send a policy activation request message to an NFVO-2 and an NFVO-3.
  • FIG. 6 is a schematic flowchart of performing cooperative policy activation on an NS cure policy group 1 based on the system architecture of the composite NS shown in FIG. 2 .
  • Step S601 The OSS initiates a policy activation request to the NFVO-1 in a management domain of a composite NS, to request to activate a cure policy 1 of the composite NS and a cure policy of a nested NS included in the NS cure policy group 1.
  • the policy activation request command carries an identifier of the to-be-activated cure policy 1 of the composite NS and an identifier of the NS cure policy group 1.
  • Step S602 The NFVO-1 in the management domain of the composite NS returns a policy activation response to the OSS, where the response message carries a result of activating the cure policy 1 of the composite NS.
  • Step S603 The NFVO-1 in the management domain of the composite NS obtains, based on the received identifier of the NS cure policy group 1, an identifier of the cure policy of the nested NS that is in the policy group and that is associated with the cure policy 1 of the composite NS, and separately sends a policy activation command to the NFVO-2 and the NFVO-3 in step S603 and step S605, where the policy activation commands respectively carry an identifier of a cure policy 2 of a nested NS-A and an identifier of a cure policy 3 of a nested NS-B.
  • the NFVO-2 and the NFVO-3 in the management domains of the nested NSs return policy activation response messages to the NFVO-1 in the management domain of the composite NS in step S604 and step S606.
  • the OSS may perform a cooperative policy deactivation operation on the policy group by using the NFVO-1.
  • a procedure of the cooperative policy deactivation operation is the same as that in FIG. 6 .
  • a difference is that a request and a response message in FIG. 7 are a deactivation request and a deactivation response message.
  • a specific message procedure is not described again.
  • the policy decision entity may further send a policy group deletion request to the NFVO in the management domain of the composite NS to delete a created policy group, as shown in FIG. 8 .
  • the policy decision entity requests the NFVO in the management domain of the composite NS to delete the policy group, where a request message carries an identifier of the policy group.
  • the NFVO in the management domain of the composite NS deletes a record of the policy group that is locally recorded, and returns a policy group deletion response in step S802 to indicate a deleting result to the policy decision entity.
  • This procedure may be performed when the policy decision entity does not need to maintain the policy group, for example, when a life cycle of the composite NS ends.
  • the policy decision entity may first delete the policy group, and then create a policy group to update the member policy.
  • each function entity such as the OSS and the NFVO-1, includes a corresponding hardware structure and/or software module used to perform each function.
  • a person of ordinary skill in the art should easily be aware that, in combination with the examples described in the embodiments disclosed in this specification, units, algorithms steps may be implemented by hardware or a combination of hardware and computer software in the present invention. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the present invention.
  • FIG. 9 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • the computer device 900 includes at least one processor 901, a communications bus 902, a memory 903, and at least one communications interface 904.
  • the processor 901 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits used to control program execution of the solutions in the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communications bus 902 may include a path in which information is transmitted between the foregoing components.
  • the communications interface 904 by using any apparatus such as a transceiver, is configured to communicate with another device or communications network, such as an Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area network, WLAN).
  • a radio access network radio access network
  • WLAN wireless local area network
  • the memory 903 may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and instructions; and may also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM), or other compact disc storage, optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a blue-ray disc, or the like), and a disk storage medium or another disk storage device, or any other medium that can be used to carry or store expected program code that has an instruction or digital structure form and that can be accessed by a computer. This is not limited herein.
  • the memory may exist independently and is connected to the processor by using the bus. The memory may alternatively be integrated with the processor.
  • the memory 903 is configured to store application program code for performing the solution of the present invention, and execution of the application program code is controlled by the processor 901.
  • the processor 901 is configured to execute the application program code stored in the memory 903, to implement the function in the method in this patent.
  • the processor 901 may include one or more CPUs such as a CPU 0 and a CPU 1 in FIG. 9 .
  • the computer device 900 may include a plurality of processors such as a processor 901 and a processor 908 in FIG. 9 .
  • processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor herein may be one or more devices, circuits and/or processing cores used to process data (for example, a computer program instruction).
  • the computer device 900 may further include an output device 905 and an input device 906.
  • the output device 905 communicates with the processor 901 and may display information in various manners.
  • the output device 905 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, or a projector (projector).
  • the input device 906 communicates with the processor 901 and may receive input of a user in various manners.
  • the input device 906 may be a mouse, a keyboard, a touch panel device, or a sensing device.
  • the computer device 900 may be a general-purpose computer device or a special-purpose computer device.
  • the computer device 900 may be a desktop computer, a portable computer, a network server, a personal digital assistant (personal digital assistant, PDA), a mobile phone, a tablet computer, a wireless terminal device, a communications device, an embedded device, or a device having a structure similar to that shown in FIG. 8 .
  • a type of the computer device 900 is not limited in this embodiment of the present invention.
  • function module division may be performed on the policy decision entity or the NFVO in the management domain of the composite NS based on the method example in the method embodiment, for example, each function module may be divided based on each function, or two or more functions may be integrated in one function module.
  • unit division is an example, and is merely a logical function division. In actual implementation, another division manner may be used.
  • FIG. 10 is a possible schematic structural diagram of a policy decision entity in the foregoing embodiment, and the policy decision entity is configured to complete functions related to the policy decision entity in all the foregoing method embodiments.
  • the device 1000 includes a communication module 1001 and a processing module 1002.
  • the communication module 1001 is configured to send a request message to an NFVO in a management domain of a composite NS or receive a response message from the NFVO in the management domain of the composite NS.
  • the processing module 1002 is configured to: generate a policy management operation request message, and send the policy management operation request message by using the communication module, where the policy management operation request message includes an identifier of a policy group.
  • the processing module 1002 is further configured to generate a policy group creation or deletion request message, where the policy group creation request message includes an identifier of a member policy in the policy group, the member policy includes an LCM policy of one composite NS and LCM policies of one or more nested NSs forming the composite NS, and the policy group deletion request message includes the identifier of the policy group; and is further configured to: parse a policy group creation response message that is received by the communication module from the NFVO in the management domain of the composite NS, and record the identifier of the policy group included in the policy group creation response message.
  • FIG. 11 is a possible schematic structural diagram of an NFVO in a management domain of a composite NS in the foregoing embodiment, and the NFVO is configured to complete functions related to the NFVO in the management domain of the composite NS in all the foregoing method embodiments.
  • the device 1100 includes a communication module 1101 and a processing module 1102.
  • the communication module 1101 is configured to receive a policy group creation or deletion request message from a policy decision entity, is further configured to send a policy group creation or deletion response message to the policy decision entity, and is further configured to receive a policy management operation request message sent by the policy decision entity.
  • the processing module 1102 is configured to: parse the received policy management operation request message, determine, based on an identifier that is of a policy group and that is included in the policy management operation request message, an identifier of an LCM policy that is of a nested NS and that is included in the policy group, and generate a policy management operation request sent to an NFVO in a management domain of the nested NS, where the request message includes the identifier of the LCM policy of the nested NS.
  • the communication module 1101 of the NFVO in the management domain of the composite NS is further configured to receive the policy group creation or deletion request message from the policy decision entity, and is further configured to send the policy group creation or deletion response message to the policy decision entity.
  • the processing module 1102 of the NFVO in the management domain of the composite NS is further configured to: parse the received policy group creation request message, create the policy group locally, and allocate the identifier to the policy group, where the policy group creation request message includes an identifier of a member policy in the policy group, and the member policy includes an LCM policy of one composite NS and LCM policies of one or more nested NSs forming the composite NS; and generate the response message for the policy group creation request, and send the response message to the policy decision entity by using the communication module, where the response message for the policy group creation request includes the identifier of the policy group.
  • the processing module 1102 is further configured to parse the policy group deletion request message received by the communication module, and delete a corresponding policy group according to an identifier of the policy group in the request message.
  • the foregoing function module may be implemented in a form of hardware, or may be implemented in a form of a software function module.
  • a person skilled in the art may figure out that the policy decision entity 1000 or the NFVO 1100 in the management domain of the composite NS may be in a form shown in FIG 9 .
  • the processing module 1002 in FIG 10 may be implemented by invoking code in the memory 903 by the processor 901 in FIG 9 . This is not limited in this embodiment of the present invention.

Landscapes

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

Claims (12)

  1. Procédé de gestion de politique, dans lequel le procédé est appliqué à un scénario de fourniture d'un service de réseau, NS, composite à travers des domaines de gestion, le NS composite comprend un ou plusieurs NS imbriqué(s), le NS composite et le NS imbriqué formant le NS composite sont fournis dans différents domaines de gestion ; un orchestrateur de virtualisation des fonctions réseau, NFVO, dans un domaine de gestion du NS composite est chargé de la gestion du cycle de vie, LCM, du NS composite, et un NFVO dans un domaine de gestion du NS imbriqué est chargé de la gestion du cycle de vie du NS imbriqué, dans lequel le procédé comprend : l'envoi (301), par une entité de décision de politique, d'une première demande d'opération de gestion de politique au NFVO dans le domaine de gestion du NS composite, la première demande d'opération de gestion de politique comprenant un identifiant d'un groupe de politiques ; et
    la réception, par le NFVO dans le domaine de gestion du NS composite, de la première demande d'opération de gestion de politique, en déterminant, sur la base de l'identifiant du groupe de politiques, un identifiant d'une politique de LCM qui appartient au NS imbriqué et qui est compris dans le groupe de politiques, et l'envoi (302) d'une seconde demande d'opération de gestion de politique au NFVO dans le domaine de gestion du NS imbriqué, dans lequel la seconde demande d'opération de gestion de politique comprend l'identifiant de la politique de LCM du NS imbriqué, dans lequel avant l'envoi, par une entité de décision de politique, d'une première demande d'opération de gestion de politique adressée au NFVO dans le domaine de gestion du NS composite, le procédé comprend en outre : la demande, par l'entité de décision de politique, au NFVO dans le domaine de gestion du NS composite de créer un groupe de politiques, dans lequel la demande de création de groupe de politiques comprend un identifiant d'une politique membre du groupe de politiques, et la politique membre comprend une politique de LCM d'un NS composite et des politiques de LCM d'un ou de plusieurs NS imbriqué(s) formant le NS composite ;
    la création, par le NFVO dans le domaine de gestion du NS composite, du groupe de politiques sur la base de la demande de création de groupe de politiques, l'attribution d'un identifiant au groupe de politiques et l'envoi d'un message de réponse à l'entité de décision de politique, le message de réponse comprenant l'identifiant du groupe de politiques ; et
    l'obtention et l'enregistrement, par l'entité de décision de politique dans le message de réponse reçu qui est destiné à la demande de création de groupe de politiques et qui est envoyé par le NFVO dans le domaine de gestion du NS composite, de l'identifiant attribué au groupe de politiques par le NFVO dans le domaine de gestion du NS composite.
  2. Procédé selon la revendication 1, dans lequel l'entité de décision de politique demande au NFVO dans le domaine de gestion du NS composite de supprimer un groupe de politiques créé, et le message de demande de suppression de groupe de politiques comprend un identifiant d'un groupe de politiques à supprimer.
  3. Procédé selon la revendication 1, dans lequel un type d'opération de gestion de politique demandé dans la seconde demande d'opération de gestion de politique est le même qu'un type d'opération de gestion de politique demandé dans la première demande d'opération de gestion de politique, et comprend l'une quelconque des opérations de gestion de politique suivantes : la mise à jour de politique, la suppression de politique, l'activation de politique ou la désactivation de politique.
  4. Procédé selon la revendication 3, dans lequel lorsque la première demande d'opération de gestion de politique est utilisée en tant que demande de mise à jour de politique, la demande comprend en outre un paramètre de mise à jour de politique, et le paramètre de mise à jour de politique est appliqué à la politique membre dans le groupe de politiques.
  5. Entité de décision de politique, appliquée à un scénario de fourniture d'un service de réseau, NS, composite à travers des domaines de gestion, dans laquelle le NS composite comprend un ou plusieurs NS imbriqué(s), le NS composite et le NS imbriqué formant le NS composite sont fournis dans différents domaines de gestion, un orchestrateur de virtualisation des fonctions réseau, NFVO, dans un domaine de gestion du NS composite est chargé de la gestion du cycle de vie, LCM, du NS composite, et l'entité de décision de politique comprend : une interface de communication, configurée pour envoyer, au NFVO dans le domaine de gestion du NS composite, une première demande d'opération de gestion de politique générée par un processeur ;
    une mémoire, configurée pour stocker une instruction exécutable par ordinateur, un identifiant d'un groupe de politiques et un identifiant d'une politique membre comprise dans le groupe de politiques ; et
    le processeur, connecté à la mémoire et à l'interface de communication à l'aide d'un bus et configuré pour : exécuter l'instruction exécutable par ordinateur dans la mémoire pour générer la première demande d'opération de gestion de politique, et envoyer la première demande d'opération de gestion de politique au NFVO dans le domaine de gestion du NS composite par le biais de l'interface de communication, dans lequel la demande d'opération de gestion de politique comprend l'identifiant du groupe de politiques, dans lequel l'identifiant qui appartient au groupe de politiques et qui est stocké dans la mémoire est attribué par le NFVO dans le domaine de gestion du NS composite sur la base d'une demande de création de groupe de politiques envoyée par l'entité de décision de politique, et est renvoyé à l'entité de décision de politique à l'aide d'un message de réponse, qui est particulièrement mis en œuvre comme suit : l'interface de communication est en outre configurée pour : envoyer, au NFVO dans le domaine de gestion du NS composite, un message de demande de création de groupe de politiques généré par le processeur, et recevoir un message de réponse destiné à la demande de création de groupe de politiques et envoyé par le NFVO dans le domaine de gestion du NS composite ; et
    le processeur est en outre configuré pour exécuter l'instruction exécutable par ordinateur dans la mémoire afin de mettre en œuvre les fonctions suivantes : la génération du message de demande de création de groupe de politiques et l'envoi du message de demande de création de groupe de politiques au NFVO dans le domaine de gestion du NS composite par le biais de l'interface de communication, le message de demande de création de groupe de politiques comprenant l'identifiant de la politique membre dans le groupe de politiques, et la politique membre comprend une politique de LCM d'un NS composite et des politiques de LCM d'un ou de plusieurs NS imbriqué(s) formant le NS composite ; et
    l'analyse du message de réponse qui est destiné à la demande de création de groupe de politiques et qui est reçu par l'interface de communication et envoyé par le NFVO dans le domaine de gestion du NS composite, l'analyse et l'obtention de l'identifiant attribué par le NFVO dans le domaine de gestion du NS composite au groupe de politiques, et la transmission, à l'aide du bus, de l'identifiant du groupe de politiques à la mémoire pour stockage.
  6. Entité de décision de politique selon la revendication 5, dans laquelle le processeur est en outre configuré pour : générer un message de demande de suppression de groupe de politiques et envoyer le message de demande de suppression de groupe de politiques au NFVO dans le domaine de gestion du NS composite par le biais de l'interface de communication, pour demander au NFVO dans le domaine de gestion du NS composite de supprimer un groupe de politiques créé, le message de demande de suppression de groupe de politiques comprenant un identifiant d'un groupe de politiques à supprimer.
  7. Entité de décision de politique selon l'une quelconque des revendications 5 à 6, dans laquelle la première demande d'opération de gestion de politique qui est générée par le processeur et qui est envoyée au NFVO dans le domaine de gestion du NS composite par le biais de l'interface de communication comprend l'une quelconque parmi les opérations de gestion de politique suivantes : la mise à jour de politique, la suppression de politique, l'activation de politique ou la désactivation de politique.
  8. Entité d'orchestrateur de virtualisation des fonctions réseau, NFVO, dans un domaine de gestion d'un service de réseau, NS, composite appliqué à un scénario de fourniture d'un NS composite sur des domaines de gestion, dans laquelle le NS composite comprend un ou plusieurs NS imbriqué(s), le NS composite et les NS imbriqués formant le NS composite sont fournis dans différents domaines de gestion ;
    un NFVO dans un domaine de gestion du NS composite est chargé de la gestion du cycle de vie, LCM, du NS composite, un NFVO dans un domaine de gestion du NS imbriqué est chargé de la gestion du cycle de vie du NS imbriqué, et l'entité NFVO dans un domaine de gestion d'un NS composite comprend : une interface de communication, configurée pour : recevoir une première demande d'opération de gestion de politique envoyée par une entité de décision de politique, et envoyer, au NFVO dans le domaine de gestion du NS imbriqué, une seconde demande d'opération de gestion de politique générée par un processeur ;
    une mémoire, configurée pour stocker une instruction exécutable par ordinateur, un identifiant d'un groupe de politiques et un identifiant d'une politique membre comprise dans le groupe de politiques ; et
    le processeur, connecté à la mémoire et à l'interface de communication à l'aide d'un bus et configuré pour : exécuter l'instruction exécutable par ordinateur dans la mémoire pour analyser la première demande d'opération de gestion de politique, et déterminer, sur la base de l'identifiant qui appartient au groupe de politiques et qui est compris dans la première demande d'opération de gestion de politique, un identifiant d'une politique de LCM qui appartient à un NS imbriqué et qui est compris dans le groupe de politiques, pour générer la seconde demande d'opération de gestion de politique, et envoyer la seconde demande d'opération de gestion de politique au NFVO dans le domaine de gestion du NS imbriqué par le biais de l'interface de communication, dans lequel la seconde demande d'opération de gestion de politique comprend l'identifiant de la politique de LCM du NS imbriqué, le groupe de politiques étant créé par le NFVO dans le domaine de gestion du NS composite sur la base d'une demande de l'entité de décision de politique ;
    l'interface de communication est en outre configurée pour : recevoir un message de demande de création de groupe de politiques envoyé par l'entité de décision de politique, et renvoyer un message de réponse pour la demande de création de groupe de politiques à l'entité de décision de politique ; et
    le processeur est en outre configuré pour exécuter l'instruction exécutable par ordinateur dans la mémoire afin de mettre en œuvre les fonctions suivantes : l'analyse du message de demande de création de groupe de politiques reçu, la création du groupe de politiques et l'attribution d'un identifiant au groupe de politiques, le message de demande de création de groupe de politiques comprenant l'identifiant de la politique membre dans le groupe de politiques, et la politique membre comprenant une politique de LCM d'un NS composite et des politiques de LCM d'un ou de plusieurs NS imbriqué(s) formant le NS composite ; et
    la génération du message de réponse pour la demande de création de groupe de politiques, et l'envoi du message de réponse à l'entité de décision de politique par le biais de l'interface de communication, le message de réponse pour la demande de création de groupe de politiques comprenant l'identifiant du groupe de politiques.
  9. Entité NFVO dans un domaine de gestion d'un NS composite selon la revendication 8, dans laquelle l'interface de communication est en outre configurée pour recevoir un message de demande de suppression de groupe de politiques envoyé par l'entité de décision de politique, le message de demande de suppression de groupe de politiques comprend un identifiant d'un groupe de politiques à supprimer, et le processeur supprime le groupe de politiques correspondant en fonction de l'identifiant du groupe de politiques.
  10. Entité NFVO dans un domaine de gestion d'un NS composite selon la revendication 8 ou 9, dans laquelle un type d'opération de gestion de politique demandé dans la seconde demande d'opération de gestion de politique est le même qu'un type d'opération de gestion de politique demandé dans la première opération de gestion de politique, et comprend l'une des opérations de gestion de politique suivantes : la mise à jour de politique, la suppression de politique, l'activation de politique ou la désactivation de politique.
  11. Système de gestion de politique, comprenant l'entité de décision de politique selon l'une quelconque des revendications 5 à 7 et l'entité d'orchestrateur de virtualisation des fonctions réseau, NFVO, dans un domaine de gestion d'un service de réseau, NS, composite selon l'une quelconque des revendications 8 à 10.
  12. Support de stockage lisible par ordinateur, comprenant une instruction, dans lequel lorsque l'instruction s'exécute sur un ordinateur, l'ordinateur exécute le procédé lié à l'entité de décision de politique ou à l'entité d'orchestrateur de virtualisation des fonctions réseau, NFVO, dans un domaine de gestion d'un service de réseau, NS, composite selon les revendications 1 à 4.
EP18744251.2A 2017-01-25 2018-01-19 Procédé, dispositif et système de gestion de stratégie Active EP3567803B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20213360.9A EP3855680A1 (fr) 2017-01-25 2018-01-19 Procédé et système de gestion de politique et appareil

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710061358.9A CN108347343B (zh) 2017-01-25 2017-01-25 一种策略管理方法、装置和系统
PCT/CN2018/073449 WO2018137572A1 (fr) 2017-01-25 2018-01-19 Procédé, dispositif et système de gestion de stratégie

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP20213360.9A Division EP3855680A1 (fr) 2017-01-25 2018-01-19 Procédé et système de gestion de politique et appareil

Publications (3)

Publication Number Publication Date
EP3567803A1 EP3567803A1 (fr) 2019-11-13
EP3567803A4 EP3567803A4 (fr) 2019-11-13
EP3567803B1 true EP3567803B1 (fr) 2020-12-30

Family

ID=62963390

Family Applications (2)

Application Number Title Priority Date Filing Date
EP20213360.9A Withdrawn EP3855680A1 (fr) 2017-01-25 2018-01-19 Procédé et système de gestion de politique et appareil
EP18744251.2A Active EP3567803B1 (fr) 2017-01-25 2018-01-19 Procédé, dispositif et système de gestion de stratégie

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP20213360.9A Withdrawn EP3855680A1 (fr) 2017-01-25 2018-01-19 Procédé et système de gestion de politique et appareil

Country Status (5)

Country Link
US (2) US10855543B2 (fr)
EP (2) EP3855680A1 (fr)
CN (2) CN108347343B (fr)
ES (1) ES2854286T3 (fr)
WO (1) WO2018137572A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9379998B2 (en) * 2014-02-07 2016-06-28 International Business Machines Corporation Symmetric coherent request/response policy enforcement
ES2929061T3 (es) * 2017-12-29 2022-11-24 Huawei Tech Co Ltd Método de gestión de servicios de red, dispositivo y sistema relacionados
CN114880078A (zh) * 2018-06-05 2022-08-09 华为技术有限公司 管理容器服务的方法和装置
FR3094812A1 (fr) * 2019-04-08 2020-10-09 Orange Procédé et dispositif de migration d’une fonction virtualisée en cas de défaillance de l’environnement technique de serveurs
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
CN114944979A (zh) 2019-09-02 2022-08-26 华为技术有限公司 一种多管理域的通信方法和装置
CN115412439A (zh) * 2019-11-29 2022-11-29 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
CN112994917B (zh) * 2019-12-17 2022-12-13 华为技术有限公司 网络管理方法和网络管理装置
CN113098705B (zh) * 2019-12-23 2022-08-26 华为技术有限公司 网络业务的生命周期管理的授权方法及装置
CN115361291A (zh) * 2019-12-27 2022-11-18 华为技术有限公司 网络服务实例化的方法及网络功能虚拟化编排器

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5841870A (en) * 1996-11-12 1998-11-24 Cheyenne Property Trust Dynamic classes of service for an international cryptography framework
WO2011016011A2 (fr) 2009-08-07 2011-02-10 Ecolab Usa Inc. Pompe de produit de nettoyage et d’étanchéité
US9037711B2 (en) * 2009-12-02 2015-05-19 Metasecure Corporation Policy directed security-centric model driven architecture to secure client and cloud hosted web service enabled processes
US20150052095A1 (en) * 2013-08-15 2015-02-19 Cisco Technology, Inc. Model-based approach to intelligent automation in a computing domain
US9760428B1 (en) * 2013-12-19 2017-09-12 Amdocs Software Systems Limited System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network
US9806979B1 (en) * 2013-12-19 2017-10-31 Amdocs Software Systems Limited System, method, and computer program for optimizing a chain of virtual network functions in a network based on network function virtualization (NFV)
US9667509B1 (en) * 2015-01-26 2017-05-30 Amdocs Software Systems Limited System, method, and computer program for secluding a service in a network based on network function virtualization (NFV)
CN104811328B (zh) 2014-01-27 2018-08-10 新华三技术有限公司 虚拟网络资源管理方法及装置
WO2015197025A1 (fr) * 2014-06-26 2015-12-30 Huawei Technologies Co., Ltd. Système et procédé de gestion de politiques de fonctions virtuelles de réseau
CN105656646B (zh) * 2014-11-10 2019-02-05 中国移动通信集团公司 一种虚拟网元的部署方法及装置
US9912558B2 (en) * 2015-01-13 2018-03-06 Intel IP Corporation Techniques for monitoring virtualized network functions or network functions virtualization infrastructure
CN104618396B (zh) * 2015-03-04 2018-01-02 浪潮集团有限公司 一种可信网络接入与访问控制方法
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
CN106302068A (zh) * 2015-05-11 2017-01-04 中兴通讯股份有限公司 虚拟网络功能vnf的虚拟资源的管理方法及装置
CN106325979B (zh) * 2015-06-26 2020-02-28 中兴通讯股份有限公司 虚拟机部署方法、装置及网络功能虚拟化编排nvfo
CN105847237B (zh) * 2016-03-15 2019-01-15 中国联合网络通信集团有限公司 一种基于nfv的安全管理方法和装置

Also Published As

Publication number Publication date
CN111917571B (zh) 2022-09-23
CN108347343A (zh) 2018-07-31
US20190349258A1 (en) 2019-11-14
CN108347343B (zh) 2020-07-14
ES2854286T3 (es) 2021-09-21
US11611481B2 (en) 2023-03-21
EP3855680A1 (fr) 2021-07-28
EP3567803A1 (fr) 2019-11-13
US20210075683A1 (en) 2021-03-11
US10855543B2 (en) 2020-12-01
WO2018137572A1 (fr) 2018-08-02
CN111917571A (zh) 2020-11-10
EP3567803A4 (fr) 2019-11-13

Similar Documents

Publication Publication Date Title
EP3567803B1 (fr) Procédé, dispositif et système de gestion de stratégie
US10700928B2 (en) Method and apparatus for deploying service in virtualized network
EP3609161B1 (fr) Procédé et appareil de création de tranche de réseau, et système de communication
US11481249B2 (en) Service migration method, apparatus, and server that are used in software upgrade in NFV architecture
US10241835B2 (en) Scheduling storage and computing resources based on task types and service levels
US10979859B2 (en) Allocation of resources in a networked computing environment based on physical location mapping
CN112532675B (zh) 一种网络边缘计算系统的创建方法、装置及介质
US20200403970A1 (en) Providing Network Address Translation in a Software Defined Networking Environment
WO2017041508A1 (fr) Procédé et dispositif permettant d'instancier à nouveau une fonction de réseau virtuel
CN106817432B (zh) 云计算环境下虚拟资源弹性伸展的方法，系统和设备
EP3358790B1 (fr) Procédé de traitement de ressource de virtualisation de fonction de réseau et gestionnaire de fonction de réseau virtualisée
KR20220103796A (ko) 노드 관리 방법, 장치, 디바이스, 저장 매체 및 시스템
EP3457668B1 (fr) Mise en grappe dans des services de communication et de collaboration unifiés
US20130054768A1 (en) Migrating device management between object managers
Rocha et al. CNS-AOM: design, implementation and integration of an architecture for orchestration and management of cloud-network slices
CN112889247B (zh) Vnf服务实例化方法及装置
WO2018120222A1 (fr) Procédé, dispositif et système de gestion de vnffg
CN111404980A (zh) 一种数据存储方法及一种对象存储系统

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190807

A4 Supplementary search report drawn up and despatched

Effective date: 20191016

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200811

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018011393

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1351022

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210330

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210331

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1351022

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210330

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20201230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210430

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2854286

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20210921

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210119

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210430

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018011393

Country of ref document: DE

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602018011393

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210131

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210131

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

26N No opposition filed

Effective date: 20211001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210119

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210131

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201230

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20180119

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231130

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231212

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20240205

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201230

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20231205

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20231212

Year of fee payment: 7