WO2019109948A1

WO2019109948A1 - Paas management method and device, and storage medium

Info

Publication number: WO2019109948A1
Application number: PCT/CN2018/119367
Authority: WO
Inventors: 夏海涛
Original assignee: 华为技术有限公司
Priority date: 2017-12-07
Filing date: 2018-12-05
Publication date: 2019-06-13
Also published as: CN109905258B; CN109905258A

Abstract

The present application relates to the technical field of cloud computing and discloses a PaaS management method and device, and a storage medium. The method comprises: a MANO entity sending a service configuration request for a target service to a PaaS upon determining that a target service subscriber no longer needs to call a target service; the PaaS ending a binding contract between the target service subscriber and the target service on the basis of the service configuration request; and the PaaS ending all instances of the target service upon determining that there is no binding contract between other service subscribers and the target service. Therefore, services provided by the present application are different from exclusive services which terminate along with the end of instances of a service subscriber, thereby improving the reuse of instances of a service between a plurality of service subscribers, and greatly improving the efficiency of PaaS platform service resource management.

Description

PaaS management method, device and storage medium

This application claims the priority of the Chinese patent application submitted by the State Intellectual Property Office of China, application number 201711288701.X, and the invention name "PaaS management method, device and storage medium" on December 7, 2017. The citations are incorporated herein by reference.

Technical field

The present application relates to the field of cloud computing technologies, and in particular, to a method, an apparatus, and a storage medium for managing Platform as a Service (PaaS).

Background technique

PaaS refers to providing the server as a service to users so that users can develop, test, and deploy applications such as applications online. At present, the implementation of PaaS is mainly through Network Function Virtualization (NFV) technology, that is, the PaaS is deployed in the NFV architecture, and the virtualized network function (VNF) in the NFV architecture is in the instance. When the service deployed on the PaaS needs to be invoked, the service is instantiated to implement the network function corresponding to the service. Among them, instantiation refers to the process of configuring virtual resources for services or VNFs through the Network Function Virtualization Infrastructure (NFVI) in the NFV architecture. Among them, the VNF that invokes a service can be called the service tenant of the service.

In the related art, there are two types of services deployed on PaaS, one is a public service and the other is a proprietary service. The life cycle of the public service is independent of the life cycle of the VNF that invokes the public service, that is, the public service remains online after the instantiation, and a VNF in the NFV architecture needs to be invoked during the instantiation process. The public service only needs to invoke the instance corresponding to the public service, and the instance of the public service does not end with the termination of the instance of the VNF. The life cycle of a proprietary service is closely related to the life cycle of the VNF that invokes the proprietary service, that is, the proprietary service is instantiated with the instantiation of the VNF that invoked the proprietary service, with the call of the proprietary service The end of the VNF instance ends.

In the above PaaS management method, for a public service, whether or not a VNF needs to be invoked, the public service instance is kept online, which increases the resource occupation burden on the PaaS; and for the proprietary service, the proprietary service The instance of the service will be terminated with the termination of the instance of the VNF that invoked the proprietary service, so each time the proprietary service is invoked, the proprietary service needs to be instantiated, reducing the flexibility of the application of the proprietary service. Sex.

Summary of the invention

In order to solve the problem of low flexibility of the proprietary service application of the related art, the present application provides a method, an apparatus, and a storage medium for managing a PaaS. The technical solution is as follows:

In a first aspect, a method for managing a PaaS is provided, which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the method includes:

Receiving a service configuration request for a target service sent by a Management and Orchestration (MANO) entity in the NFV architecture, the service configuration request being a target service tenant in the determining the NFV architecture by the MANO entity And when the target service is no longer invoked, the target service is any one of the multiple services;

Determining, by the service configuration request, a contract binding relationship between the target service tenant and the target service, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;

When it is determined that there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated.

In the embodiment of the present application, when the target service tenant no longer invokes the target service, the contract binding relationship between the target service tenant and the target service is first released, and other service tenants and target services in the NFV architecture are determined to be absent. When the contract binding relationship is terminated, all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.

Optionally, the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.

Because in some scenarios, the contract binding relationship between the target service tenant and the target service needs to be dismissed, and in some scenarios, the use binding relationship between the target service tenant instance and the target service instance needs to be released. In this application, the type of configuration carried in the service configuration request can be used to determine which relationship needs to be terminated.

Optionally, after the releasing the contract binding relationship between the target service tenant and the target service based on the service configuration request, the method further includes:

Sending a first type of service configuration response message to the MANO entity, where the first type of service configuration response message is used to indicate that a contract binding relationship between the target service and the target service tenant has been released.

After the PaaS releases the contract binding relationship between the target service tenant and the target service, it is necessary to notify the MANO entity that the contract binding relationship has been released.

Optionally, the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, where the configuration type is decommissioning;

Correspondingly, the canceling a contract binding relationship between the target service tenant and the target service based on the service configuration request includes:

Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;

When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.

Specifically, when the configuration type is decommissioning, it indicates that the MANO entity wants to release the use binding relationship between the target service tenant instance and the target service instance, and the PaaS is between the target service tenant instance and the target service instance. After the binding relationship is used, the contract binding relationship between the target service tenant and the target service can also be cancelled in the above manner.

Optionally, after the releasing the use binding relationship between the instance of the target service and the instance of the target service tenant, the method further includes:

Sending a second type of service configuration response message to the MANO entity, the second type of service configuration response message indicating that a usage binding relationship between the instance of the target service and an instance of the target service tenant has been released.

Similarly, after the PaaS releases the binding relationship between the instance of the target service tenant and the instance of the target service, the MANO entity needs to be notified in time that the binding relationship has been released.

Optionally, before receiving the service configuration request for the target service sent by the MANO entity in the NFV architecture, the method further includes:

Receiving a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;

Establishing a usage binding relationship between an instance of the target service tenant and an instance of the target service based on an identifier of an instance of the target service tenant and an identifier of an instance of the target service, and determining the target service Establishing a contract binding relationship between the target service tenant and the target service when the target service tenant does not exist in the tenant list.

Specifically, in the present application, the PaaS may establish a binding relationship between the target service tenant instance and the target service instance when the MANO entity sends the configuration request, and establish the target service tenant and the target service according to actual conditions. Contract binding relationship between.

Optionally, before receiving the configuration request sent by the MANO entity, the method further includes:

Receiving an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;

Sending a first response message to the MANO entity when the instance of the target service is determined to be present based on the identifier of the target service, the first response message is used to indicate that the target service has been instantiated, and the A response message carries an identifier of an instance of the target service;

Sending a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, the second response message is used to indicate that the target service is not instantiated, and receiving the a service instantiation request sent by the MANO entity, where the service instantiation request carries an identifier of the target service, and the target service is instantiated based on the identifier of the target service, and an instance of the target service is obtained. The MANO entity sends an instantiation response message, the instantiated response message carrying an identity of an instance of the target service.

Specifically, the MANO entity can obtain the identity of the instance of the target service by sending an instance acquisition request to the PaaS. Wherein, when the PaaS determines that there is currently no instance of the target service, it also needs to feed back to the MANO entity an instance of the target service that does not currently exist, so that the MANO entity sends an instantiation request for the target service.

Optionally, the instantiating the target service based on the identifier of the target service, and obtaining an instance of the target service, including:

Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;

And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.

Specifically, the PaaS can instantiate the target service through the above process to obtain an instance of the target service.

Optionally, the MANO entity is a virtual network function manager (VNFM) in the NFV architecture.

Among them, in the present application, the MANO entity may be a VNFM in the NFV architecture.

In a second aspect, another method for managing a PaaS is provided, which is applied to a MANO entity in a network function virtualization NFV architecture, where the NFV architecture is deployed with PaaS, wherein a plurality of services are deployed on the PaaS. The method includes:

When it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS;

The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.

In the embodiment of the present application, when the target service tenant no longer invokes the target service, the MANO entity may send a service configuration request to the PaaS, so that the PaaS first removes the contract binding relationship between the target service tenant and the target service, and determines When there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.

Optionally, when it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS, including:

When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;

When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.

Specifically, when the descriptor file of the target service tenant is updated, the MANO entity may be triggered to send a service configuration request to the PaaS.

Optionally, after the sending the service configuration request to the PaaS, the method further includes:

Receiving a first type of service configuration response message sent by the PaaS, where the first type of service configuration response message is used to indicate that a contract binding relationship between the target service and the target service tenant has been released.

When the MANO entity receives the first type of service configuration response message, it indicates that the PaaS has released the contract binding relationship between the target service and the target service tenant.

Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;

Determining a lag time according to the descriptor file of the target service tenant;

And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.

Specifically, when the identifier of the instance of the target service tenant is deleted, the MANO entity may be triggered to send a service configuration request to the PaaS.

Receiving a second type of service configuration response message sent by the PaaS, where the second type of service configuration response message is used to indicate that a usage binding relationship between the instance of the target service and an instance of the target service tenant has been released.

When the MANO entity receives the second type of service configuration response message, it indicates that the PaaS has deactivated the use binding relationship between the instance of the target service and the instance of the target service tenant.

Optionally, before the sending the service configuration request for the target service to the PaaS, the method further includes:

Sending a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to instruct the PaaS to establish an instance of the target service tenant A binding relationship with the instance of the target service.

In the present application, in order to facilitate an instance of the target service tenant to invoke an instance of the target service, the MANO entity may send a configuration request to the PaaS to enable the PaaS to establish a binding relationship between the instance of the target service tenant and the instance of the target service. .

Optionally, before the sending the configuration request to the PaaS, the method further includes:

When it is determined that the instance of the target service tenant needs to invoke the target service, sending an instance obtaining request to the PaaS, where the instance obtaining request carries an identifier of the target service;

Receiving a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;

Receiving a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target service And an identifier that is sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.

Specifically, the MANO entity may obtain the identifier of the instance of the target service by using the foregoing two methods before sending the configuration request. The MANO entity may also obtain the identifier of the instance of the target service by sending an instantiation request when the instance of the target service does not exist in the PaaS.

Optionally, the MANO entity is a virtual network function manager VNFM in the NFV architecture.

According to a third aspect, there is provided a management apparatus for a PaaS, the management apparatus of the PaaS having a function of implementing a behavior of a management method of PaaS in the above first aspect. The management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the above first aspect.

According to a fourth aspect, there is provided another management apparatus for a PaaS, the management apparatus of the PaaS having a function of implementing the behavior of the management method of the PaaS in the second aspect. The management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the second aspect.

According to a fifth aspect, there is provided another management apparatus for a PaaS, wherein the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-enabled management device to perform the PaaS provided by the first aspect. A program for managing the method, and data related to the management method for implementing the PaaS provided by the first aspect described above. The processor is configured to execute a program stored in the memory. The operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.

According to a sixth aspect, there is provided another management apparatus for a PaaS, wherein the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-supporting management device to perform the PaaS provided by the second aspect. A program for managing the method, and data related to the management method for implementing the PaaS provided by the second aspect described above. The processor is configured to execute a program stored in the memory. The operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.

According to a seventh aspect, there is provided a computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the first aspect described above when it is run on a computer.

According to an eighth aspect, there is provided another computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the second aspect described above when it is run on a computer.

According to a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the PaaS management method of the first aspect described above.

According to a tenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of managing the PaaS described in the second aspect above.

The technical effects obtained by the third aspect, the fifth aspect, the seventh aspect, and the ninth aspect are similar to those obtained by the corresponding technical means in the first aspect, and are not described herein again.

The technical effects obtained by the fourth aspect, the sixth aspect, the eighth aspect, and the tenth aspect are similar to those obtained by the corresponding technical means in the second aspect, and are not described herein again.

The beneficial effects brought by the technical solutions provided by the present application are:

In the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, it sends a service configuration request for the target service to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance between multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management.

DRAWINGS

1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application;

2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application;

2B is a schematic structural diagram of a PaaS according to an embodiment of the present application;

3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application;

4A is a block diagram of a management device for a PaaS according to an embodiment of the present application;

4B is a block diagram of another PaaS management apparatus according to an embodiment of the present application;

FIG. 5A is a block diagram of another PaaS management apparatus according to an embodiment of the present application; FIG.

FIG. 5B is a block diagram of another PaaS management apparatus according to an embodiment of the present application.

Detailed ways

In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

Before the embodiments of the present application are further described in detail, the application scenarios of the embodiments of the present application are introduced.

Since the PaaS of the embodiment of the present application is deployed in the NFV architecture, the NFV architecture is first introduced herein. FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application. The NFV system architecture can be applied to various types of networks, for example, to an operator communication network or a local area network.

As shown in FIG. 1 , the NFV architecture mainly includes a MANO entity 110, an NFVI 120, multiple VNFs 130, multiple Element Management (EM) 140, and an Operation Support System/Business Support System (Operation Support System/Business Support System). OSS/BSS) 150 and so on. The MANO entity 110 further includes a network function virtualization orchestrator (NFVO) 110a, one or more VNFMs 110b, and a virtualized infrastructure manager (VIM) 110c.

For the convenience of the description, the functions of each module in the NFV architecture in FIG. 1 are introduced.

NFVO 110a is used to implement Network Service Descriptors (NSD), and management and processing of VNF Forwarding Graph (VNFFG), management of network service life cycle, and VNFM to achieve VNF life cycle. Management and global view capabilities of virtual resources.

VNFM 110b is used to implement VNF lifecycle management, including management of virtualized network function descriptors (VNFD) files, instantiation of VNFs, and elastic scaling of VNF instances (including expansion of Scaling out/up and shrinking Scaling in). /down), healing of the VNF instance and the end of the VNF instance. VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.

The VIM 110b is responsible for managing the infrastructure layer hardware resources, virtualized resources (including reservation and allocation), monitoring and fault reporting of virtual resource status, and providing virtualized resource pools for upper-layer applications.

OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.

The EM 140 is used to perform traditional fault, configuration, user, performance, and security management (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, FCAPS) functions for the VNF 130.

The VNF 130 corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as a virtualized 4G core network (Evolved Packet Core, EPC) EPC node, such as a Mobility Management Entity (MME). , Serving Gate Way (SGW), Packet Data Network Gateway (PGW), etc. Among them, the functional behavior and state of network functions are not related to virtualization. The requirement of NFV technology is that VNF and PNF have the same functional behavior and external interfaces.

In addition, the VNF 130 can be composed of multiple VNF components (VNFCs). Therefore, in practical applications, one VNF 130 can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component. The function. Of course, a VNF 130 can also be deployed on a VM.

NFVI 120 is composed of hardware resources and virtual resources and a virtualization layer. From the perspective of VNF 130, the virtualization layer and hardware resources appear to be a complete entity capable of providing the required virtual resources.

In addition, the embodiment of the present application mainly implements a method for managing services on the PaaS. Therefore, the PaaS platform is also briefly introduced herein.

PaaS is a business model that uses the server platform as a service. For example, providing a corresponding cloud computing platform or development environment in the cloud computing era as a service is a type of PaaS. In addition, in the typical level of cloud computing, the PaaS layer is between Software as a Service (SaaS) and Infrastructure as a Service (IaaS).

Among them, the PaaS platform should have the following characteristics:

Application running environment: including distributed computing operating environment, multiple types of data storage, dynamic resource scaling.

Application lifecycle support: including software development kit (SDK), integrated development environment (IDE), etc. to accelerate the development, testing and deployment of applications.

Public service: Provides public services such as queue services, storage services, and cache services in the form of an Application Programming Interface (API).

Monitoring, management and metering: Provide resource pool, application system management and monitoring functions, and accurately measure.

Integrated, composite application building capabilities: including connectivity services, integration services, messaging services, and process services.

Moreover, with the continuous development of NFV technology, the original VNF representation based on the NFVI layer VM incorporates new features, supporting cloud-native VNF and cloud architecture that integrates PaaS platform services. Will become a new trend in the development of telecommunications clouds. The PaaS management method provided by the embodiment of the present application is applied to an NFV architecture deployed with PaaS.

2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application. As shown in FIG. 2A, the NVF architecture shown in FIG. 2A further includes a PaaS 160, which is included in the NFV architecture shown in FIG. 160 includes a plurality of services and PaaS management for managing the plurality of services.

The VNF 130 in the NFV architecture can implement the instantiation of the VNF by calling a service in the PaaS 160.

It should be noted that, in addition to the VNF, the NFV architecture can call the service in the PaaS, and other modules can also invoke the service in the PaaS. For the convenience of description, the modules that call the service in the PaaS are collectively referred to as the service tenant. That is, in the embodiment of the present application, the service tenant may be a VNF in the NFV architecture.

In addition, the MANO entity in the PaaS and NFV architecture deployed in the NFV architecture is used to perform the PaaS management method provided by the embodiment of the present application. Specifically, the application is implemented by the PaaS management in the PaaS and the MANO entity in the NFV architecture. The management method of PaaS provided by the embodiment.

The PaaS management may also be referred to as a PaaS management entity or a PaaS management plane, and the MANO entity may specifically be a VNFM in the NFV architecture.

FIG. 2B is a schematic structural diagram of a PaaS according to an embodiment of the present application. The function of PaaS in Fig. 2A can be realized by the computer device shown in Fig. 2B. Referring to FIG. 2B, the computer device includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.

The processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.

Communication bus 202 can include a path for communicating information between the components described above.

The memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed, but is not limited to this. Memory 203 may be present independently and coupled to processor 201 via communication bus 202. The memory 203 can also be integrated with the processor 201.

The communication interface 204 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), or Wireless Local Area Networks (WLAN). .

In a particular implementation, as an embodiment, processor 201 may include one or more CPUs, such as CPU0 and CPU1 shown in Figure 2B.

In a particular implementation, as an embodiment, a computer device can include multiple processors, such as processor 201 and processor 205 shown in FIG. 2B. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a specific implementation, as an embodiment, the computer device may further include an output device 206 and an input device 207. Output device 206 is in communication with processor 201 and can display information in a variety of ways. For example, the output device 206 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 207 is in communication with processor 201 and can receive user input in a variety of ways. For example, input device 207 can be a mouse, keyboard, touch screen device, or sensing device, and the like.

The computer device described above may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device. The embodiments of the present application do not limit the type of computer equipment.

The memory 203 is used to store program code for executing the solution of the present application, and is controlled by the processor 201 for execution. The processor 201 is configured to execute the program code 208 stored in the memory 203. One or more software modules may be included in program code 208.

The embodiment of the present application also provides a structure of a MANO entity including at least one processor, a communication bus, a memory, and at least one communication interface. The functions of the processor, the communication bus, the memory, and the communication interface included in the MANO entity and the processor, the communication bus, the memory, and the communication interface in FIG. 2B are substantially the same, and will not be described in detail herein.

Next, the management method of the PaaS provided by the embodiment of the present application is explained in detail.

FIG. 3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application. The flowchart is applied to the NFV architecture deployed in the PaaS shown in FIG. 2A. As shown in FIG. 2A, multiple services are deployed on the PaaS. Specifically, as shown in FIG. 3, the method includes the following steps:

Step 301: The MANO entity sends a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service.

In the embodiment of the present application, the management of the PaaS deployed in the NFV architecture mainly includes two aspects, the first aspect is the instantiation of the service deployed in the PaaS, and the second aspect is the deployment in the PaaS. The end of the service.

Steps

301 and 302 are used to expand the content of the first aspect, and steps 303 to 305 are used to expand the content of the second aspect.

It should be noted that, for the target service tenant in the NFV architecture, in order to ensure that the instance of the target service tenant can invoke the instance of the target service deployed on the PaaS, the MANO entity needs to go to the PaaS after obtaining the identity of the instance of the target service. And sending a configuration request, so that the PaaS carries the identifier of the instance of the target service tenant and the identifier of the instance of the target service according to the configuration request, and establishes a use binding relationship between the instance of the target service tenant and the instance of the target service.

The identifier of the instance of the target service is used to uniquely identify an instance of the target service, and the identifier of the instance of the target service tenant is used to uniquely identify an instance of the target service tenant.

Further, after the MANO entity sends the configuration request to the PaaS, in order to ensure that the instance of the target service tenant can smoothly invoke the instance of the target service, the MANO entity also needs to establish an instance between the target service tenant and the target service instance. Use binding relationships.

In addition, the identity of the instance of the target service that the MANO entity obtains can be implemented by the following two possible implementations:

The first possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance obtaining request to the PaaS, the instance obtaining request carries the identifier of the target service; and the PaaS receiving the instance obtaining sent by the MANO entity Requesting, when the instance of the target service is currently present, sending a first response message to the MANO entity, the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of the instance of the target service .

It should be noted that for any service deployed on the PaaS, the service may have multiple instances, which may be occupied by instances of the service tenant, or some instances may not be occupied by instances of the service tenant. Therefore, when the MANO entity determines that the instance of the tenant of the target service needs to invoke the target service, the instance acquisition request for the target service may be first sent to the PaaS to determine whether there is an instance of the target service that is not occupied in the PaaS.

That is, in the embodiment of the present application, when the MANO entity determines that the instance of the target service tenant needs to invoke the target service, the MANO entity sends an instance acquisition request for the target service to the PaaS, where the instance obtains the identifier of the target service. . When the PaaS receives the instance acquisition request, it determines whether an instance of the target service exists currently according to the identifier of the target service, so as to send the identifier of the instance of the target service to the MANO entity according to the first possible implementation manner.

In addition, when the MANO entity receives the first response message, since the MANO entity determines that the target service tenant instance needs to invoke the target service, the instance acquisition request is sent to the PaaS, so the MANO entity can be based on the first The identifier of the target service carried by the response message establishes a usage binding relationship between the instance of the target service tenant and the instance of the target service, so that the instance of the target service tenant can invoke the instance of the target service.

Specifically, the instance obtaining request may be a lifecycle state query request. At this time, the first response message carries a lifecycle state of the target service, and the lifecycle state is instantiated, and is used to indicate that the target service has an instance. And there is currently an instance of the target service.

Optionally, the MANO entity may further determine, in other manners, whether an instance of the target service exists in the PaaS, for example, determining whether an instance of the target service exists in the PaaS by using a subscription manner.

The second possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance acquisition request to the PaaS, where the instance obtains the identifier of the target service. The PaaS receives the instance acquisition request sent by the MANO entity, and when the instance of the target service does not exist, sends a second response message to the MANO entity, where the second response message is used to indicate that the target service is not instantiated. The MANO entity receives the second response message and sends a service instantiation request for the target service to the PaaS, the service instantiation request carrying the identity of the target service. When the PaaS receives the service instantiation request sent by the MANO entity, the target service is instantiated based on the identifier of the target service, an instance of the target service is obtained, and an instantiation response message is sent to the MANO entity, and the instantiation is performed. The reply message carries the identity of the instance of the target service.

In a second possible implementation manner, the PaaS sends a second response message to the MANO entity, and the MANO entity determines that the current PaaS does not exist because the instance of the target service does not currently exist. An instance of the target service. At this time, in order for the instance of the target service tenant to invoke the target service, the MANO entity may send a service instantiation request for the target service to the PaaS to obtain an instance of the target service.

For example, when the instance obtains a request for a lifecycle state query request, the second response message carries a lifecycle state of the target service, and the lifecycle state is uninstantiated, indicating that the target service is not instantiated, That is, there is currently no instance of the target service that is not occupied.

Specifically, the implementation of the target service by the PaaS may be: the PaaS obtains the descriptor file of the target service from the descriptor file of the stored service, and the descriptor file of the target service is used to describe the target. The information needed during the service instantiation process. The PaaS instantiates the target service according to the information required in the target service instantiation process in the descriptor file of the target service, and obtains an instance of the target service.

The identifier of the target service carried in the instance obtaining request and the instantiation request is used to uniquely identify the target service. Specifically, the identifier of the target service may be the name of the target service.

In addition, the information required in the target service instantiation process is pre-set information, and the information required in the target service instantiation process mainly includes instance parameters, the number of instances, or the scale when the target service is initially deployed. The PaaS instantiates the target service, that is, the PaaS completes the configuration of the target service and the allocation of resources according to the instance parameters, the number of instances, or the scale when the target service is initially deployed.

That is, in the embodiment of the present application, for any service deployed on the PaaS, a descriptor file corresponding to the service is stored in the PaaS, and when the service needs to be instantiated, the The service corresponding descriptor file instantiates the service.

According to the first possible implementation manner and the second possible implementation manner, after the MANO entity sends an instance acquisition request for the target service to the PaaS, the PaaS is determined whether or not the instance of the target service is currently present. After the instance of the target service, the identity of the instance of the target service is sent to the MANO entity to ensure that the instance of the target service tenant can invoke the instance of the target service.

It should be noted that the identifier of the instance that the PaaS sends the target service to the MANO entity may be an identifier of an instance of the target service, or may be an identifier of multiple instances of the target service, that is, the PaaS may be assigned to the target according to the actual situation. The target service tenant is one or more instances of the target service, and the embodiment of the present application is not specifically limited herein.

In addition, it can be seen from the foregoing first possible implementation manner and the second possible implementation manner that the MANO entity sends an instance acquisition request for the target service to the PaaS when determining that the target service tenant instance needs to invoke the target service.

The MANO entity can determine that the target service tenant needs to invoke the target service. The following two scenarios may exist: that is, in the embodiment of the present application, the service in the PaaS may be instantiated in the following two scenarios:

Scenario 1: The MANO entity creates an identifier of the instance of the target service tenant, and determines that the target service is included in the service list used by the target service tenant, and determines that the target service tenant instance needs to invoke the target service.

It should be noted that, for any service tenant, there is a descriptor file corresponding to the service tenant, and the descriptor file defines a user that the corresponding service tenant can invoke. In addition, after the MANO entity creates the identity of an instance of the service tenant, the instance of the service tenant will invoke an instance of the service defined in the descriptor file during the subsequent instantiation.

Therefore, when the MANO entity creates an identity of the instance of the target service tenant, it can indicate that the target service tenant needs to invoke an instance of the target service.

That is, when the MANO entity creates an identifier of the instance of the target service tenant, the service that can be invoked by the target service tenant defined in the descriptor file is determined as the target service according to the descriptor file of the target service tenant, and An instance get request for the target service is sent to the PaaS.

When the PaaS receives the instance acquisition request, the identifier of the instance of the target service is sent to the MANO entity according to the two possible implementation manners, so that the identifier of the instance of the target service is received by the MANO entity according to step 301 to the PaaS. Send a configuration request.

In scenario 1, after the MANO entity completes the creation of the identifier of the target service tenant instance, when the instance of the target service tenant needs to be instantiated, the target service tenant may be directly invoked according to the established use binding relationship. An instance of the target service corresponding to the instance to complete the instantiation process of the instance of the target service tenant.

Specifically, the MANO entity is a VNFM. When the VNFM receives the instance identifier creation request of the target service tenant sent by the NFVO or the EM, the VNFM locally creates an instance identifier of the target service tenant, and describes from the target service tenant. The service file obtains an identifier of the target service that the target service tenant can invoke, and sends the foregoing instance acquisition request according to the identifier of the target service.

It should be noted that, in scenario 1, the precondition for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the descriptor file is explicitly defined in the target service tenant's descriptor file. The service that the target service tenant can call.

Scenario 2: When the MANO entity instantiates an instance of the target service tenant and determines that the target service is included in the service list used by the target service tenant, it is determined that the target service tenant instance needs to invoke the target service.

In scenario 2, when the MANO entity creates the identity of the instance of the target service tenant, it does not send an instance acquisition request to the PaaS to obtain an instance of the target service as in scenario one, but creates an identifier of the instance of the target service tenant. Then, in the process of instantiating the instance of the target service tenant, an instance acquisition request for the target service that the target service tenant can invoke is sent to the PaaS.

That is, after the MANO entity creates the identity of the instance of the target service tenant, when the instance of the target service tenant currently needs to be instantiated, the descriptor file of the target service tenant is determined, and the target defined in the descriptor file is determined. The service that the service tenant can call is determined to be the target service, and an instance acquisition request for the target service is sent to the PaaS.

When the PaaS receives the instance acquisition request, the identifier of the instance of the target service may be sent to the MANO entity according to the two possible implementation manners, so that the MANO entity receives the identifier of the instance of the target service according to step 301. Send a configuration request to the PaaS.

Obviously, in scenario 2, the prerequisite for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the MANO entity has created the identity of the instance of the target service tenant, and the target is The service tenant's descriptor file clearly defines the services that the target service tenant can invoke.

Step 302: The PaaS receives the configuration request, and establishes a binding relationship between the instance of the target service and the instance of the target service tenant based on the identifier of the instance of the target service tenant and the identifier of the instance of the target service carried by the configuration request. And when the target service tenant does not exist in the tenant list of the target service, the contract binding relationship between the target service tenant and the target service is established.

When the PaaS receives the configuration request, in order to ensure that the instance of the target service tenant can invoke the instance of the target service, the PaaS needs to establish a usage binding relationship between the instance of the target service and the instance of the target service tenant.

That is, after the PaaS sends the identifier of the instance of the target service to the MANO entity, in order to ensure that the instance of the target service tenant can invoke the instance of the target service, an instance of the target service tenant is stored in both the PaaS and the MANO entity. A binding relationship between instances of the target service.

It is worth noting that, since different service tenants can invoke the same service, in the example of the present invention, when the target service tenant first instantiates the target service, that is, PaaS creates the first one according to the target service tenant. When an instance of the target service is used, PaaS needs to establish a contract binding relationship between the target service tenant and the target service. Then, when the target service tenant instantiates the target service for the second time, there is no need to establish a contract binding relationship between the target service tenant and the target service. That is, when there is a contract binding relationship between the service and the service tenant, it indicates that the service tenant can invoke the service.

Therefore, when the PaaS receives the service configuration request and establishes a usage binding relationship between the instance of the target service and the instance of the target service tenant, it may be determined whether the instance of the target service is the target service tenant for the first time to the target service instance. The instance of the time, if it is, then the contract binding relationship between the target service tenant and the target service needs to be established at this time.

It should be noted that for any service deployed on the PaaS, the PaaS maintains a tenant list for the service, and the tenant list records the identifier of the service tenant that has called the service.

Therefore, when establishing a binding relationship between the instance of the target service and the instance of the target service tenant, the PaaS may determine whether the target service tenant exists in the tenant list of the target service according to the identifier of the target service tenant, if not Existence indicates that the target service tenant is the first to create an instance of the target service, and the contract binding relationship between the target service tenant and the target service is established.

It should be noted that, as shown in step 302, there are two different binding relationships in the embodiment of the present application, and the binding relationship and the contract binding relationship are used. To avoid confusion, the usage relationship and the contract binding relationship are performed here. explain:

For PaaS, in order to ensure that the service tenant can invoke the service, a correspondence between the service tenant and the service needs to be established; and in order to ensure that the instance of the service tenant can invoke the instance of the service, an instance between the service tenant and the instance of the service needs to be established. Correspondence. Therefore, for convenience of explanation, the correspondence between the service tenant and the service is called the contract binding relationship between the service tenant and the service, and the correspondence between the instance of the service tenant and the instance of the service is called an instance of the service tenant. A binding relationship with an instance of a service. That is, a contract binding relationship is established between the service tenant and the service, and a binding relationship is established between the instance of the service tenant and the instance of the service.

Since a service tenant usually has multiple instances, and a service usually has multiple instances, the contract binding relationship can only indicate that there is an instance of the service tenant instance calling the service, but it cannot indicate which instance of the service tenant is called. An instance of the service, and the use of a binding relationship can clearly indicate which instance of the service tenant invoked the instance of the service.

For example, for the target service tenant and the target service, if the target service tenant has three instances, namely A1, A2, and A3, the target service also has three instances, namely B1, B2, and B3, and the instance of the target service invoked by the current A1. The instance of the target service called for B1, A2 is B2, and the instance of the target service called by A3 is B3. At this time, in PaaS, there is only one contract binding relationship for the target service tenant and the target service, that is, the contract binding relationship between the target service tenant and the target service. However, there are three binding relationships, which are the binding relationship between A1 and B1, the usage relationship between A2 and B2, and the binding relationship between A3 and B3.

The foregoing steps 301 and 302 are used to describe the instantiation process of the service provided by the embodiment of the present application. The process of terminating the service provided by the embodiment of the present application is introduced in the following steps 303 to 305.

Step 303: When the MANO entity determines that the target service tenant in the NFV architecture no longer invokes the target service, sends a service configuration request for the target service to the PaaS.

In the embodiment of the present application, in order to avoid the termination of the service due to the termination of the service tenant calling the service, when the MANO entity determines that the target service tenant no longer needs to invoke the target service, in order to terminate the target service, the MANO entity needs to The service configuration request for the target service is first sent to the PaaS, so that the PaaS decides whether the target service needs to be terminated according to the specific situation, so as to terminate the target service on demand.

It should be noted that the MANO entity may determine that the target service tenant no longer needs to invoke the target service in the following two scenarios, that is, in the embodiment of the present application, the target service may be terminated in the following two scenarios. .

Scenario 1: When the descriptor file of the target service tenant is updated, since the target service tenant's descriptor file defines the service that the target service tenant can invoke, when the target service tenant's descriptor file is updated, It may be necessary to terminate the services that the target service tenant can call.

Specifically, when the MANO entity determines that the descriptor file of the target service tenant is updated, the descriptor file of the target service tenant after the update is obtained. When the MANO entity determines that the target service needs to be deleted from the service list used by the target service tenant according to the updated descriptor file of the target service tenant, the service configuration request is sent to the PaaS.

At this time, since the target service needs to be deleted from the service list used by the target service tenant, that is, the target service tenant will not invoke the target service again, the MANO entity needs to request the PaaS to release the target service tenant and the target. Contract binding relationship between services.

In the actual application, the service configuration request carries a configuration type in order to distinguish service configuration requests in different scenarios. Therefore, in scenario 1, the configuration type carried by the service configuration request is a release contract, and the service configuration request further carries the identifier of the target service tenant and the identifier of the target service, so that the PaaS cancels the target service tenant according to the service configuration request. Contract binding relationship between target services.

The identifier of the target service tenant is used to uniquely identify the target service tenant. Specifically, when the target service tenant is a VNF, the identifier of the target service tenant may be the name of the VNF.

For example, when the VNF vendor updates the descriptor file of the VNF, after obtaining the descriptor file after the update, the VNFM determines that it is necessary to delete a service from the service list of the VNF according to the descriptor file after the update. The VNFM determines the service to be deleted as the target service, and sends the service configuration request in the scenario one to the PaaS. The service configuration request carries the configuration type, the identifier of the VNF, and the identifier of the service that needs to be deleted, where the configuration type is the contract cancellation.

Scenario 2: When the MANO entity deletes the identifier of the target service tenant instance, it indicates that the target service tenant instance will no longer invoke the target service instance. Therefore, when deleting the target service tenant instance, the target may need to be terminated. service.

It should be noted that, in scenario 2, since only the identifier of the instance of the target service tenant is deleted, it merely indicates that the instance of the target service tenant no longer calls the target service, but does not represent other instances of the target service tenant. The target service is no longer called. Therefore, in order to prevent the PaaS from immediately terminating the target service, other instances of the target service tenant cannot continue to invoke the target service, and the target service tenant is further provided with a lag time, which is a PaaS delay to release the target service tenant and target. The time of the contract binding relationship between services.

Wherein, for any service tenant, the preset delay time is included in the descriptor file of the service tenant.

Therefore, when the MANO entity needs to delete the identifier of the instance of the target service tenant, the descriptor file of the target service tenant is obtained; the lag time is determined according to the descriptor file of the target service tenant, and the service configuration request is sent to the PaaS.

At this time, since only the identifier of the instance of the target service tenant is to be deleted, it merely indicates that the instance of the target service tenant no longer calls the target service, but other instances of the target service tenant are not called to call the target service. Therefore, the MANO entity only needs to request the PaaS to release the binding relationship between the instance of the target service tenant and the instance of the target service.

That is, in scenario 2, the configuration type carried by the service configuration request is de-use, and the service configuration request further carries an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time.

For example, when the VNFM in the NFV architecture receives the instance ID deletion request sent by the NFVO or the EM for a certain VNF, the VNFM locally deletes the identifier of the instance of the VNF, and sends the identifier to the PaaS according to the service list of the VNF. VNF service configuration request. The service configuration request carries a configuration type, an identifier of an instance of the VNF, an identifier of an instance of a service invoked by an instance of the VNF, and a lag time, wherein the configuration type is de-use.

Step 304: The PaaS receives the service configuration request sent by the MANO entity for the target service, and cancels the contract binding relationship between the target service tenant and the target service based on the service configuration request.

It can be seen from step 303 that the MANO entity may send a service configuration request for the target service to the PaaS in two different scenarios, and accordingly, step 304 is also specifically divided into the following two cases:

For the scenario 1 in step 303: when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is a release contract, so the PaaS can identify the target service tenant carried according to the service configuration request and An identifier of the target service, searching for a contract binding relationship between the target service tenant and the target service that has been established, and releasing a contract binding relationship between the target service tenant and the target service.

After releasing the contract binding relationship between the target service tenant and the target service, the PaaS also needs to send a first type service configuration response message to the MANO entity, where the first type service configuration response message is used to indicate the target service and the target service. The contract binding relationship between tenants has been lifted.

That is, when the MANO entity receives the first type of service configuration response message, it is determined that the PaaS has released the contract binding relationship between the target service and the target service tenant.

For the scenario 2 in step 303, when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is deactivated, so the PaaS can perform the instance of the target service tenant carried according to the service configuration request. The identifier of the instance of the identifier and the target service, finds a usage binding relationship between the instance of the target service tenant that has been established and the instance of the target service, and releases the usage binding relationship.

After disabling the binding relationship between the instance of the target service tenant and the instance of the target service, the PaaS also needs to send a second type of service configuration response message to the MANO entity, and the second type of service configuration response message is used to indicate the target. The binding relationship between the instance of the service and the instance of the target service tenant has been removed.

That is, when the MANO entity receives the second type of service configuration response message, it is determined that the PaaS has released the use binding relationship between the instance of the target service and the instance of the target service tenant.

Since in the second scenario, the MANO entity service configuration request further includes a lag time, after the PaaS releases the use binding relationship between the target service instance and the target service tenant instance, in order to avoid the PaaS immediately terminating the The target service causes the other instances of the target service tenant to continue to call the target service, and the PaaS can start timing. The time of the timing is the lag time, and it is determined during the lag time whether the target service tenant calls the target service again. If the target service tenant does not invoke the target service within the lag time after the current time, the PaaS may cancel the contract binding relationship between the target service tenant and the target service, and determine whether according to step 305 below. Need to end the target service.

Correspondingly, if the target service tenant is still calling the target service within the lag time after the current time, the PaaS does not need to release the contract binding relationship between the target service tenant and the target service, that is, the PaaS will The target service will not be terminated.

Step 305: Terminate all instances of the target service when the PaaS determines that there is no contract binding relationship between the other service tenants in the NFV architecture and the target service.

In the embodiment of the present application, in order to avoid termination due to the termination of the instance of the VNF that invokes the service, the instance of the service needs to be instantiated each time the service is invoked. When the PaaS releases the contract binding relationship between the target service tenant and the target service according to step 304, the PaaS does not immediately terminate the target service, but first determines whether there are other service tenants who need to invoke the target service.

If there are still other service tenants that need to call the target service, if the target service is directly terminated, the other service tenants will need to re-instantiate the target service when they continue to call the target service. Therefore, in the embodiment of the present application, the PaaS will not terminate the target service immediately, but will terminate the target service when the PaaS determines that there is no other service tenant that needs to invoke the target service.

Specifically, the PaaS may determine whether there is a service tenant that needs to invoke the target service by determining whether there is currently another service tenant that has a contract binding relationship with the target service, that is, when there is currently no service with the target service. When the other service tenants of the contract binding relationship determine that there are no other service tenants that need to call the target service, the PaaS terminates the target service.

Accordingly, when there are currently other service tenants that have a contractual relationship with the target service, at this time, PaaS will not terminate the target service.

Among them, PaaS terminates the target service, that is, PaaS deletes all instances of the target service and releases resources occupied by all instances of the target service.

In the embodiment of the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.

Referring to FIG. 4A, an embodiment of the present application provides a PaaS management apparatus 400, which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the apparatus 400 includes a first receiving module 401. , the release module 402 and the termination module 403:

a first receiving module 401, configured to perform the step of receiving, by the PaaS in step 304 of the embodiment of FIG. 3, a service configuration request for the target service sent by the MANO entity;

The releasing module 402 is configured to perform the step of canceling the contract binding relationship between the target service tenant and the target service based on the service configuration request in step 304 of the embodiment of FIG. 3;

The termination module 403 is configured to perform step 305 of the embodiment of FIG. 3.

Optionally, the apparatus 400 further includes:

The third sending module is configured to send a first type of service configuration response message to the MANO entity, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.

Optionally, the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, and the configuration type is decommissioning;

Correspondingly, the releasing module 402 is specifically configured to:

Debinding the usage binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, the identifier of the instance of the target service tenant, and the identifier of the instance of the target service;

Optionally, the apparatus 400 further includes:

a fourth sending module, configured to send a second type of service configuration response message to the MANO entity, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and the instance of the target service tenant Has been lifted.

Optionally, referring to FIG. 4B, the apparatus 400 further includes a second receiving module 404 and an establishing module 405:

a second receiving module 404, configured to perform the step of receiving, by the PaaS in step 302 of the embodiment of FIG. 3, the configuration request;

The establishing module 405 is configured to perform the identifier of the instance of the target service tenant and the identifier of the target service carried in the step 302 of the embodiment of FIG. 3, and establish an instance of the target service and an instance of the target service tenant. The step of establishing a contract binding relationship between the target service tenant and the target service when the binding relationship is used and the target service tenant does not exist in the tenant list of the target service.

Optionally, the apparatus 400 further includes a third receiving module, a first sending module, and a second sending module:

a third receiving module, configured to receive an instance obtaining request sent by the MANO entity, where the instance obtains an identifier that carries the target service;

a first sending module, configured to send a first response message to the MANO entity when the identifier of the target service is determined based on the identifier of the target service, where the first response message is used to indicate that the target service has been instantiated, and The first response message carries an identifier of an instance of the target service;

a second sending module, configured to send a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, where the second response message is used to indicate that the target service is not instantiated and received a service instantiation request sent by the MANO entity, the service instantiation request carrying an identifier of the target service, instantiating the target service based on the identifier of the target service, obtaining an instance of the target service, and sending the target service instance to the MANO entity A reply message is instantiated that carries an identification of an instance of the target service.

Optionally, the second sending module is specifically configured to:

Obtaining, according to the identifier of the target service, a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe information required in the target service instantiation process;

The target service is instantiated according to the information required in the target service instantiation process in the descriptor file of the target service, and an instance of the target service is obtained.

Referring to FIG. 5A, an embodiment of the present application provides another PaaS management apparatus 500, which is applied to a MANO entity in an NFV architecture. The NFV architecture is deployed with PaaS, and the apparatus 500 includes a first sending module 501:

The first sending module 501 is configured to perform step 303 in the embodiment of FIG. 3;

The service configuration request is used to indicate that the PaaS releases the contract binding relationship between the target service tenant and the target service based on the service configuration request, and determines that there is no contract binding relationship between the other service tenant and the target service. Terminates all instances of the target service, which is one of the multiple services.

Optionally, the first sending module 501 is specifically configured to:

When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the updated descriptor file of the target service tenant, the service configuration request is sent to the PaaS, and the service configuration request carries the configuration type, The identity of the target service tenant and the identity of the target service. The configuration type is the contract cancellation.

Optionally, the apparatus 500 further includes a third receiving module:

The third receiving module is configured to receive the first type of service configuration response message sent by the PaaS, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.

Optionally, the first sending module 501 is specifically configured to:

Obtaining a descriptor file of the target service tenant when deleting the identifier of the target service tenant instance;

Determining the lag time according to the descriptor file of the target service tenant;

Sending the service configuration request to the PaaS, the service configuration request carrying a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, the configuration type being decommissioning.

Optionally, the apparatus 500 further includes a fourth receiving module:

a fourth receiving module, configured to receive a second type of service configuration response message sent by the PaaS, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and an instance of the target service tenant Has been lifted.

Optionally, referring to FIG. 5B, the apparatus 500 further includes a second sending module 502:

The second sending module 502 is configured to perform step 301 in the embodiment of FIG. 3.

Optionally, the apparatus 500 further includes a third sending module, a first receiving module, and a second receiving module:

a third sending module, configured to send an instance obtaining request to the PaaS when the instance of the target service tenant needs to invoke the target service, where the instance obtaining request carries the identifier of the target service;

a first receiving module, configured to receive a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;

a second receiving module, configured to receive a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target An identifier of the service, receiving an instantiation response message sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.

It should be noted that, when the management device of the PaaS provided by the foregoing embodiment manages the service on the PaaS, only the division of the foregoing functional modules is illustrated. In actual applications, the functions may be allocated differently according to requirements. The function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the management device of the PaaS provided by the foregoing embodiment is the same as the embodiment of the method for managing the PaaS in the embodiment of FIG. 3, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. 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 (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above description of the embodiments of the present application is not intended to limit the application, and any modifications, equivalents, improvements, etc. made within the spirit and principles of the present application are included in the scope of the present application. Inside.

Claims

A platform-as-a-service PaaS management method is applied to a PaaS deployed in a network function virtualization NFV architecture, wherein a plurality of services are deployed on the PaaS, and the method includes:

Receiving a service configuration request for the target service sent by the management and orchestration function MANO entity in the NFV architecture, where the service configuration request is that the target service tenant in the NFV architecture does not invoke the target The target service is sent by the service, and the target service is any one of the multiple services;

Determining, by the service configuration request, a contract binding relationship between the target service tenant and the target service, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;

When it is determined that there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated.
The method of claim 1, wherein the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, the configuration type being a contract cancellation.
The method of claim 1, wherein the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, the configuration type being released use;

Correspondingly, the canceling a contract binding relationship between the target service tenant and the target service based on the service configuration request includes:

Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;

When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
The method of claim 1, wherein before receiving the service configuration request for the target service sent by the MANO entity in the NFV architecture, the method further includes:

Receiving a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;

Establishing a usage binding relationship between an instance of the target service tenant and an instance of the target service based on an identifier of an instance of the target service tenant and an identifier of an instance of the target service, and determining the target service Establishing a contract binding relationship between the target service tenant and the target service when the target service tenant does not exist in the tenant list.
The method of claim 4, wherein before receiving the configuration request sent by the MANO entity, the method further includes:

Receiving an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;

Sending a first response message to the MANO entity when the instance of the target service is determined to be present based on the identifier of the target service, the first response message is used to indicate that the target service has been instantiated, and the A response message carries an identifier of an instance of the target service;

Sending a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, the second response message is used to indicate that the target service is not instantiated, and receiving the a service instantiation request sent by the MANO entity, where the service instantiation request carries an identifier of the target service, and the target service is instantiated based on the identifier of the target service, and an instance of the target service is obtained. The MANO entity sends an instantiation response message, the instantiated response message carrying an identification of an instance of the target service.
The method according to claim 5, wherein the instantiating the target service based on the identifier of the target service to obtain an instance of the target service comprises:

Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;

And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.
A platform-as-a-service PaaS management method is applied to a network function virtualization MNV architecture management and orchestration function MANO entity, wherein the NFV architecture is deployed with PaaS, wherein the PaaS is deployed with multiple services. The method includes:

When it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS;

The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
The method of claim 7, wherein when the target service tenant in the NFV architecture is determined to no longer invoke the target service, the service configuration request for the target service is sent to the PaaS, including:

When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;

When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
The method of claim 7, wherein when the target service tenant in the NFV architecture is determined to no longer invoke the target service, the service configuration request for the target service is sent to the PaaS, including:

Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;

Determining a lag time according to the descriptor file of the target service tenant;

And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
The method of claim 7, wherein before the sending the service configuration request for the target service to the PaaS, the method further comprises:

Sending a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to instruct the PaaS to establish an instance of the target service tenant A binding relationship with the instance of the target service.
The method of claim 10, wherein before the sending the configuration request to the PaaS, the method further comprises:

When it is determined that the instance of the target service tenant needs to invoke the target service, sending an instance obtaining request to the PaaS, where the instance obtaining request carries an identifier of the target service;

Receiving a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;

Receiving a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target service And an identifier that is sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
A platform-as-a-service PaaS management device is applied to a PaaS deployed in a network function virtualization NFV architecture, wherein a plurality of services are deployed on the PaaS, and the device includes:

a first receiving module, configured to receive a service configuration request for a target service sent by a management and orchestration function MANO entity in the NFV architecture, where the service configuration request is a target service of the MANO entity in determining the NFV architecture When the tenant no longer invokes the target service, the target service is any one of the multiple services;

a release module, configured to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;

And a terminating module, configured to terminate all instances of the target service when it is determined that there is no contract binding relationship between the other service tenants in the NFV architecture and the target service.
The apparatus according to claim 12, wherein the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, and the configuration type is a contract cancellation.
The apparatus according to claim 12, wherein the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, and the configuration type is use;

Correspondingly, the releasing module is specifically configured to:

Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;

When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
The device of claim 12, wherein the device further comprises:

a second receiving module, configured to receive a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;

Establishing a module, configured to establish, according to an identifier of an instance of the target service tenant and an identifier of an instance of the target service, a binding relationship between an instance of the target service tenant and an instance of the target service, and When it is determined that the target service tenant does not exist in the tenant list of the target service, establishing a contract binding relationship between the target service tenant and the target service.
The device of claim 15 wherein said device further comprises:

a third receiving module, configured to receive an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;

a first sending module, configured to send a first response message to the MANO entity when determining that an instance of the target service exists based on an identifier of the target service, where the first response message is used to indicate that the target service has been Instantiating, and the first response message carries an identifier of an instance of the target service;

a second sending module, configured to send a second response message to the MANO entity when the instance of the target service does not exist based on the identifier of the target service, where the second response message is used to indicate the target service Not instantiating, receiving a service instantiation request sent by the MANO entity, carrying the identifier of the target service in the service instantiation request, instantiating the target service based on the identifier of the target service, obtaining a An instance of the target service, sending an instantiation response message to the MANO entity, the instantiated response message carrying an identifier of an instance of the target service.
The device according to claim 16, wherein the second sending module is specifically configured to:

Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;

And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.
A platform-as-a-service PaaS management device is applied to a management and orchestration function MANO entity in a network function virtualization NFV architecture, wherein the NFV architecture is deployed with PaaS, wherein a plurality of services are deployed on the PaaS. The device includes:

a first sending module, configured to send a service configuration request for the target service to the PaaS when determining that the target service tenant in the NFV architecture no longer invokes the target service;

The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
The device according to claim 18, wherein the first sending module is specifically configured to:

When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;

When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
The device according to claim 18, wherein the first sending module is specifically configured to:

Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;

Determining a lag time according to the descriptor file of the target service tenant;

And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
The device of claim 18, wherein the device further comprises:

a second sending module, configured to send a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to indicate that the PaaS is established A binding relationship between the instance of the target service tenant and the instance of the target service.
The device of claim 21, wherein the device further comprises:

a third sending module, configured to send an instance obtaining request to the PaaS when the instance of the target service tenant needs to invoke the target service, where the instance obtaining request carries the identifier of the target service;

a first receiving module, configured to receive a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an instance of the target service Identification

a second receiving module, configured to receive a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service is instantiated The request carries an identifier of the target service, and receives an instantiation response message sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.