CN109905258A - Management method, device and the storage medium of PaaS - Google Patents

Management method, device and the storage medium of PaaS Download PDF

Info

Publication number
CN109905258A
CN109905258A CN201711288701.XA CN201711288701A CN109905258A CN 109905258 A CN109905258 A CN 109905258A CN 201711288701 A CN201711288701 A CN 201711288701A CN 109905258 A CN109905258 A CN 109905258A
Authority
CN
China
Prior art keywords
service
destination service
tenant
mark
paas
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201711288701.XA
Other languages
Chinese (zh)
Other versions
CN109905258B (en
Inventor
夏海涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201711288701.XA priority Critical patent/CN109905258B/en
Priority to PCT/CN2018/119367 priority patent/WO2019109948A1/en
Publication of CN109905258A publication Critical patent/CN109905258A/en
Application granted granted Critical
Publication of CN109905258B publication Critical patent/CN109905258B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5064—Customer relationship management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

This application discloses the management method of PaaS a kind of, device and storage mediums, belong to field of cloud computer technology.The described method includes: sending the service configuration request for being directed to the destination service to PaaS when MANO entity is when determining that destination service tenant no longer needs to call the destination service.PaaS is based on the service configuration request, releases the contract binding relationship between destination service tenant and the destination service, and when determining that not depositing other services the contract binding relationship between tenants and the destination service, all examples for the destination service that terminates.Therefore, service provided by the present application terminates with the termination of the example of service tenant like that not necessarily like proprietary service, improve the reusabilities of the example of service between multiple service tenants, significant increase efficiency of the PaaS platform to the resource management of service.

Description

Management method, device and the storage medium of PaaS
Technical field
This application involves field of cloud computer technology, in particular to a kind of platform services (Platform as a Service, PaaS) management method, apparatus and storage medium.
Background technique
PaaS, which refers to, is supplied to user for server as a kind of service, allows the user to realize out on the internet The network functions such as hair, test and online disposing application program.Currently, mainly virtualizing (Network by network function Function Virtualization, NFV) technology realizes PaaS, that is, PaaS is deployed in NFV framework, as the NFV Virtual network function (Virtualized Network Function, VNF) in framework needs to adjust during instantiation When with the service being deployed on PaaS, by instantiating the service to realize the corresponding network function of the service.Wherein, it instantiates Refer to through network function virtualized infrastructure (the Network Function Virtualization in NFV framework Infrastructure, NFVI) it is the process that service or VNF configure virtual resource.Wherein, the VNF for calling some to service can be with The referred to as service tenant of the service.
In the related technology, the service being deployed on PaaS is divided into two kinds, and one kind is public service, and another kind is proprietary clothes Business.Wherein, the life cycle of the VNF of the life cycle of public service and the calling public service is mutually indepedent, that is, public clothes Business is always maintained at online, when some VNF in the NFV framework needs to call the public affairs during instantiation after instantiation When servicing altogether, the corresponding example of the public service only need to be called, and the example of the public service is not with the reality of the VNF Example termination and terminate.And the life cycle of proprietary service and the life cycle for the VNF for calling the proprietary service are closely related, I.e. proprietary service is instantiated with the instantiation for the VNF for calling the proprietary service, with the reality for the VNF for calling the proprietary service Example termination and terminate.
In the management method of above-mentioned PaaS, for public service, regardless of whether needing to call the public clothes there are VNF Business, the example of the public service are always maintained at the resource occupation burden increased on PaaS online；And for proprietary service, by It will terminate with the termination of the example for the VNF for calling the proprietary service in the example of the proprietary service, therefore calling every time should When proprietary service, all needs to instantiate the proprietary service, reduce the application flexibility of the proprietary service.
Summary of the invention
In order to solve the problems, such as the relevant technologies it is proprietary be served by that flexibility is low, this application provides the pipes of PaaS a kind of Manage method, apparatus and storage medium.The technical solution is as follows:
In a first aspect, the management method of PaaS a kind of is provided, applied to the PaaS being deployed in NFV framework, feature It is, multiple services is deployed on the PaaS, which comprises
Receive the management in the NFV framework and layout function (Management and Orchestration, MANO) The service configuration request for destination service that entity is sent, the service configuration request are the MANO entity described in the determination Destination service tenant in NFV framework does not recall to be sent when the destination service, and the destination service is the multiple clothes Any of business；
Based on the service configuration request, the contract binding between the destination service tenant and the destination service is released Relationship, the contract binding relationship, which is used to indicate the destination service tenant, can call the destination service；
It is closed when determining to bind there is no the contract between the service tenant of other in the NFV framework and the destination service When being, all examples for the destination service that terminates.
In the embodiment of the present application, when destination service tenant no longer invocation target services, destination service tenant is first released Contract binding relationship between destination service, and determining that there is no the service tenant of other in NFV framework and destination services Between contract binding relationship when, all examples for the destination service that terminates, rather than in destination service tenant no longer invocation target When service, all examples for the destination service that directly terminates.Therefore, it is provided by the present application service not necessarily like it is proprietary service like that with It services the termination of the example of tenant and terminates, improve the application flexibility of the service on PaaS.
Optionally, the service configuration request carries the mark and the target of Configuration Type, the destination service tenant The mark of service, the Configuration Type are to release contract.
Due to needing to release the contract binding relationship between destination service tenant and destination service in certain scenes, and It needs to release in certain scenes and uses binding relationship between the example of destination service tenant and the example of destination service, therefore, In this application, any relationship that needs to terminate can be determined by the Configuration Type carried in service configuration request.
Optionally, described to be based on the service configuration request, release the destination service tenant and the destination service it Between contract binding relationship after, further includes:
First kind service configuration response message is sent to the MANO entity, the first kind service configuration response message is used Contract binding relationship between the instruction destination service and the destination service tenant has released.
After PaaS releases the contract binding relationship between destination service tenant and destination service, MANO need to be notified in time The entity contract binding relationship has released.
Optionally, the service configuration request carry Configuration Type, the destination service tenant example mark, described The mark and lag time of the example of destination service, the Configuration Type are to release to use；
Correspondingly, described to be based on the service configuration request, release the destination service tenant and the destination service it Between contract binding relationship, comprising:
The mark of example based on the Configuration Type, the mark of the example of the destination service tenant and the destination service Know, releases and use binding relationship between the example of the destination service and the example of the destination service tenant；
The destination service tenant is without described in calling again in lag time after determining in current time When destination service, the contract binding relationship between the destination service and the destination service tenant is released.
Specifically, when Configuration Type be release in use, show the example of MANO entity destination service tenant to be released with Binding relationship is used between the example of destination service, and PaaS is in the reality for the example and destination service for releasing destination service tenant After use binding relationship between example, the conjunction between destination service tenant and destination service can also be released through the above way About binding relationship.
Optionally, the use between the example for releasing the destination service and the example of the destination service tenant is tied up After determining relationship, further includes:
The second class service configuration response message is sent to the MANO entity, the second class service configuration response message is used Having been released using binding relationship between the example of example and the destination service tenant for indicating the destination service.
Similarly, it is released as PaaS and uses binding relationship between the example of destination service tenant and the example of destination service Later, need to notify in time MANO entity this released using binding relationship.
Optionally, the service configuration for destination service that the MANO entity received in the NFV framework is sent is asked Before asking, further includes:
Receive the configuring request that the MANO entity is sent, the example that the configuring request carries the destination service tenant Mark and the destination service example mark；
The mark of the example of the mark and destination service of example based on the destination service tenant, establishes the mesh Binding relationship is used between the example of mark service tenant and the example of the destination service, and is determining the destination service When the destination service tenant being not present in tenant's list, the conjunction between the destination service tenant and the destination service is established About binding relationship.
Specifically, in this application, PaaS can establish destination service tenant's when MANO entity sends configuring request Binding relationship is used between example and the example of destination service, and establishes destination service tenant and mesh according to the actual situation simultaneously Contract binding relationship between mark service.
Optionally, before the configuring request for receiving the MANO entity transmission, further includes:
The case-based system request that the MANO entity is sent is received, the case-based system request carries the destination service Mark；
When the mark based on the destination service determines that Xiang Suoshu MANO entity is sent out there are when the example of the destination service Send the first response message, it is instantiated that first response message is used to indicate the destination service, and first response Message carries the mark of the example of the destination service；
When the mark based on the destination service determines the example that the destination service is not present, Xiang Suoshu MANO entity Send the second response message, it is uninstantiated that second response message is used to indicate the destination service, and it is real to receive the MANO The service instantiation that body is sent is requested, and the mark of the destination service is carried in the service instantiation request, is based on the mesh The mark for marking service, instantiates the destination service, the example for obtaining the destination service, Xiang Suoshu MANO entity hair Instantiation response message is sent, the instantiation response message carries the mark of the example of the destination service.
Specifically, MANO entity can obtain the mark of the example of destination service by sending case-based system request to PaaS Know.Wherein, when PaaS determines that there is currently no targets to MANO Entity feedback there is currently no also needing when the example of destination service The example of service, so that MANO entity sends the instantiation request for the destination service.
Optionally, the mark based on the destination service, instantiates the destination service, obtains the mesh The example for marking service, comprising:
Based on the mark of the destination service, retouching for the destination service is obtained from the descriptor file of the service of storage Symbol file is stated, the descriptor file of the destination service is for describing the required letter in the destination service instantiation process Breath；
It is right according to information required in destination service instantiation process described in the descriptor file of the destination service The destination service is instantiated, the example for obtaining the destination service.
Specifically, PaaS can by the above process instantiate destination service, with the example for obtaining destination service.
Optionally, the MANO entity be the NFV framework in virtual network function manager (VNF Manager, VNFM)。
Wherein, in this application, MANO entity can be the VNFM in NFV framework.
Second aspect provides the management method of another PaaS, applied in network function virtualization NFV framework MANO entity is deployed with PaaS in the NFV framework, which is characterized in that multiple services, the method are deployed on the PaaS Include:
When determining that the no longer invocation target of the destination service tenant in the NFV framework services, Xiang Suoshu PaaS sends needle To the service configuration request of the destination service；
The service configuration request is used to indicate the PaaS and is based on the service configuration request releasing destination service Contract binding relationship between tenant and the destination service, and determining that there is no other service tenants and the destination services Between contract binding relationship when terminate all examples of the destination service, the destination service is in the multiple service Any service.
In the embodiment of the present application, when destination service tenant no longer invocation target services, MANO entity can be to PaaS Service configuration request is sent, so that PaaS first releases the contract binding relationship between destination service tenant and destination service, and Determine that terminate destination service there is no when the contract binding relationship between the service tenant of other in NFV framework and destination service All examples, rather than destination service tenant no longer invocation target service when, directly termination destination service all examples. Therefore, service provided by the present application terminates with the termination of the example of service tenant like that not necessarily like proprietary service, improves The application flexibility of service on PaaS.
Optionally, described when determining that the no longer invocation target of the destination service tenant in the NFV framework services, Xiang Suoshu PaaS sends the service configuration request for being directed to the destination service, comprising:
When the descriptor file for determining the destination service tenant is updated, the destination service after updating is obtained The descriptor file of tenant；
The descriptor file of destination service tenant after according to update, determine need by the destination service from When deleting in the service list that the destination service tenant uses, Xiang Suoshu PaaS sends service configuration request, and the service is matched Setting request carrying Configuration Type, the mark of the destination service tenant and the mark of the destination service, the Configuration Type is Release contract.
Specifically, when the descriptor file of destination service tenant is updated, MANO entity can be triggered and sent to PaaS Service configuration request.
Optionally, after the transmission service configuration request to the PaaS, further includes:
The first kind service configuration response message that the PaaS is sent is received, the first kind service configuration response message is used Contract binding relationship between the instruction destination service and the destination service tenant has released.
When MANO entity receives the first kind service configuration response message, show PaaS released destination service with Contract binding relationship between destination service tenant.
Optionally, described when determining that the no longer invocation target of the destination service tenant in the NFV framework services, Xiang Suoshu PaaS sends the service configuration request for being directed to the destination service, comprising:
When deleting the mark of example of the destination service tenant, the descriptor text of the destination service tenant is obtained Part；
According to the descriptor file of the destination service tenant, lag time is determined；
The service configuration request is sent to the PaaS, the service configuration request carries Configuration Type, the target The mark of example, the mark of the example of the destination service and the lag time of tenant are serviced, the Configuration Type is solution Except use.
Specifically, when the mark of the example of delete target service tenant, MANO entity can be triggered to PaaS and send clothes Business configuring request.
Optionally, after the transmission service configuration request to the PaaS, further includes:
The second class service configuration response message that the PaaS is sent is received, the second class service configuration response message is used Having been released using binding relationship between the example of example and the destination service tenant for indicating the destination service.
When MANO entity receives the second class service configuration response message, show that PaaS has released destination service Binding relationship is used between example and the example of destination service tenant.
It is optionally, described to be sent before being directed to the service configuration request of the destination service to the PaaS, further includes:
To the PaaS send configuring request, the configuring request carry the example of the destination service tenant mark and The mark of the example of the destination service, the configuring request are used to indicate the reality that the PaaS establishes the destination service tenant Binding relationship is used between example and the example of the destination service.
In this application, the example for the ease of succeeding target service tenant is capable of the example of invocation target service, MANO Entity can send configuring request to PaaS, so that PaaS is established between the example of destination service tenant and the example of destination service Use binding relationship.
Optionally, before the transmission configuring request to the PaaS, further includes:
When the example for determining the destination service tenant needs invocation target to service, Xiang Suoshu PaaS sends case-based system Request, the case-based system request carry the mark of the destination service；
The first response message that the PaaS is sent is received, first response message has been used to indicate the destination service It is instantiated, and first response message carries the mark of the example of the destination service；
The second response message that the PaaS is sent is received, second response message is used to indicate the destination service not Instantiation, Xiang Suoshu PaaS send service instantiation request, the mark of the destination service are carried in the service instantiation request Know, receives the instantiation response message that the PaaS is sent, the example that the instantiation response message carries the destination service Mark.
Specifically, MANO entity can also obtain destination service by above two mode before sending configuring request Example mark.Wherein, when the example of the destination service is not present in PaaS, MANO entity can also be by sending example Change the mark that the mode requested obtains the example of destination service.
Optionally, the MANO entity is the virtual network function manager VNFM in the NFV framework.
Wherein, in this application, MANO entity can be the VNFM in NFV framework.
The third aspect provides the managing device of PaaS a kind of, and the managing device of the PaaS, which has, realizes above-mentioned first The function of the management method behavior of PaaS in aspect.The managing device of the PaaS includes at least one module, this at least one Module for realizing PaaS provided by above-mentioned first aspect management method.
Fourth aspect, provides the managing device of another PaaS, and the managing device of the PaaS, which has, realizes above-mentioned the The function of the management method behavior of PaaS in two aspects.The managing device of the PaaS includes at least one module, this at least one A module for realizing PaaS provided by above-mentioned second aspect management method.
5th aspect provides the managing device of another PaaS, includes place in the structure of the managing device of the PaaS Device and memory are managed, the memory, which is used to store, supports the managing device of PaaS to execute PaaS provided by above-mentioned first aspect Management method program, and store number involved in management method for realizing PaaS provided by above-mentioned first aspect According to.The processor is configured to for executing the program stored in the memory.The operating device of the storage equipment is also It may include communication bus, the communication bus is for establishing connection between the processor and memory.
6th aspect provides the managing device of another PaaS, includes place in the structure of the managing device of the PaaS Device and memory are managed, the memory, which is used to store, supports the managing device of PaaS to execute PaaS provided by above-mentioned second aspect Management method program, and store number involved in management method for realizing PaaS provided by above-mentioned second aspect According to.The processor is configured to for executing the program stored in the memory.The operating device of the storage equipment is also It may include communication bus, the communication bus is for establishing connection between the processor and memory.
7th aspect, provides a kind of computer readable storage medium, is stored in the computer readable storage medium Instruction, when run on a computer, so that computer executes the management method of PaaS described in above-mentioned first aspect.
Eighth aspect provides another computer readable storage medium, stores in the computer readable storage medium There is instruction, when run on a computer, so that computer executes the management method of PaaS described in above-mentioned second aspect.
9th aspect, provides a kind of computer program product comprising instruction, when run on a computer, so that Computer executes the management method of PaaS described in above-mentioned first aspect.
Tenth aspect, provides a kind of computer program product comprising instruction, when run on a computer, so that Computer executes the management method of PaaS described in above-mentioned second aspect.
In the above-mentioned third aspect, the 5th aspect, the 7th aspect and the 9th aspect technical effect obtained and first aspect The technical effect that corresponding technological means obtains is approximate, repeats no more herein.
In above-mentioned fourth aspect, the 6th aspect, eighth aspect and the tenth aspect technical effect obtained and second aspect The technical effect that corresponding technological means obtains is approximate, repeats no more herein.
Technical solution provided by the present application has the benefit that
In this application, multiple services are deployed on PaaS, when MANO entity is determining destination service tenant no longer When needing to call the destination service, the service configuration request for being directed to the destination service is sent to PaaS.PaaS is based on the service and matches Request is set, releases the contract binding relationship between destination service tenant and the destination service, and do not deposit other services in determination When contract binding relationship between tenant and the destination service, all examples for the destination service that terminates.Therefore, it is mentioned in the application The service of confession remains online like that not necessarily like public service, cannot release for a long time so as to cause the resource that public service occupies It puts, enhances the dynamic availability of resource in PaaS platform, while service provided by the present application is also such not necessarily like proprietary service It terminates with the termination of the example of service tenant, improves reusability of the example of service between multiple service tenants, Significant increase efficiency of the PaaS platform to the resource management of service.
Detailed description of the invention
Fig. 1 is a kind of NFV configuration diagram provided by the embodiments of the present application；
Fig. 2A is a kind of NFV configuration diagram for being deployed with PaaS provided by the embodiments of the present application；
Fig. 2 B is the structural schematic diagram of PaaS provided by the embodiments of the present application a kind of；
Fig. 3 is the management method flow chart of PaaS provided by the embodiments of the present application a kind of；
Fig. 4 A is the managing device block diagram of PaaS provided by the embodiments of the present application a kind of；
Fig. 4 B is the managing device block diagram of another kind PaaS provided by the embodiments of the present application；
Fig. 5 A is the managing device block diagram of another kind PaaS provided by the embodiments of the present application；
Fig. 5 B is the managing device block diagram of another kind PaaS provided by the embodiments of the present application.
Specific embodiment
To keep the purposes, technical schemes and advantages of the application clearer, below in conjunction with attached drawing to the application embodiment party Formula is described in further detail.
Before being described in further detail to the embodiment of the present application, first the application scenarios of the embodiment of the present application are carried out It introduces.
Since the PaaS of the embodiment of the present application is deployed in NFV framework, first NFV framework is introduced herein.Figure 1 is a kind of NFV configuration diagram provided by the embodiments of the present application, which can be applied to various types of networks In, for example, it can be applied to operators communication network or local area network be medium.
As shown in Figure 1, the NFV framework mainly includes MANO entity 110, NFVI 120, multiple VNF 130, multiple nets Member management (Element Management, EM) 140 and business support management system (Operation Support System/Business Support System, OSS/BSS) 150 etc..Wherein, which further includes having network function Composer (NFV Orchestrator, NFVO) 110a, one or more VNFM110b and virtualization basis can be virtualized Infrastructure manager (Virtualized Infrastructure Manager, VIM) 110c.
In order to subsequent convenient for explanation, next the function of the modules in Fig. 1 in NFV framework is introduced.
NFVO 110a for realizing network service descriptor (Network Service Descriptors, NSD), and The management and processing of virtual network function forwarding figure (VNF Forwarding Graph, VNFFG), network service lifecycle Management realizes the life cycle management of VNF and the global view function of virtual resource with VNFM cooperation.
VNFM 110b for realizing VNF life cycle management, including virtualization network function descriptor (VNF Descriptor, VNFD) management of file, the instantiation of VNF, VNF example elastic telescopic (including dilatation Scaling out/ Up and capacity reducing Scaling in/down), the healing (healing) of VNF example and the termination of VNF example.VNFM also supports to connect Elastic telescopic (scaling) strategy that NFVO is issued is received, realizes the VNF elastic telescopic of automation.
VIM 110b be used to be responsible for infrastructure layer hardware resource, virtualization resource management (including reserved and distribution), The monitoring of virtual resource state and failure report, provide virtualization resource pond towards upper layer application.
OSS/BSS 150 refers to the currently running maintenance system OSS/BSS of operator.
EM 140 is used to execute traditional failure, configuration, user, performance and safety management (Fault for VNF 130 Management、Configuration Management、Account Management、Performance Management, Security Management, FCAPS) function.
VNF 130 corresponds to physical network function (the Physical Network in the non-virtualized network of tradition Function, PNF), such as 4G core network (Evolved Packet Core, EPC) EPC node of virtualization, such as moving tube Manage entity (Mobility Management Entity, MME), gateway (Serving Gate Way, SGW), packet count According to gateway (Packet Data Network Gateway, PGW) etc..Wherein, the function sexual behavior and state of network function and void Unrelated whether quasi-ization, the demand of NFV technology is desirable to VNF and PNF and possesses identical function sexual behavior and external interface.
In addition, VNF 130 can be by multiple VNF components (VNF Component, VNFC) Lai Zucheng, therefore, practical application In, a VNF 130 can be deployed on multiple virtual machines (Virtual Machine, VM), and each VM carries a VNF group The function of part.Certainly, a VNF 130 can also be deployed on a VM.
NFVI 120 is made of hardware resource and virtual resource and virtualization layer, empty for the angle of VNF 130 Quasi-ization layer and hardware resource look like the complete entity for being capable of providing required virtual resource.
In addition, the embodiment of the present application is mainly the management method realized to the service on PaaS, it is therefore, flat to PaaS at this Platform is also simply introduced.
PaaS is using server platform as a kind of business model of service.For example, by the corresponding cloud meter of cloud computing era Platform or exploitation environment are calculated as service and is supplied to user, is exactly a type of PaaS.In addition, in the typical layers of cloud computing In grade, PaaS layers service (Software as a Service, SaaS) and infrastructure between software and service Between (Infrastructure as a Service, IaaS).
Wherein, PaaS platform should have the following characteristics that
Application runtime environment: including distributed computing running environment, the storage of a plurality of types of data, the flexible function of dynamic resource Energy.
Supported using Life cycle: including provide Software Development Kit (Software Development Kit, SDK), the quickenings such as Integrated Development Environment (Integrated Develop Environment, IDE) application exploitation, test and Deployment etc..
Public service: it is mentioned in Application Programming Interface (Application Programming Interface, API) form For public service, such as queue service, storage service and buffer service.
Monitoring, management and metering: resource pool, the management of application system and monitoring function, accurate measurement are provided.
Integrated, Application of composite structuring capacity: including connectivity services, integrated service, messaging service and flow services etc..
Also, with the continuous development of NFV technology, the presentation form of VNF of original building on the basis of NFVI layers of VM New characteristic is incorporated, the cloud framework of the VNF and fusion PaaS platform service that support cloud primary (Cloud-native) will be at For the new trend of telecom cloud development.The management method of PaaS provided by the embodiments of the present application is just applied to be deployed with the NFV of PaaS In framework.
Fig. 2A is a kind of NFV configuration diagram for being deployed with PaaS provided by the embodiments of the present application, as shown in Figure 2 A, relatively Further include PaaS 160 in NVF framework shown in Fig. 2A in NFV framework shown in FIG. 1, includes multiple services in the PaaS 160 With the PaaS management for managing multiple service.
Wherein, the VNF 130 in NFV framework can realize the VNF's by way of calling the service in PaaS 160 Instantiation.
It should be noted that can call in addition to VNF the service in PaaS in NFV framework, other modules can also be called The module for the service called in PaaS is referred to as service tenant in order to subsequent convenient for explanation by the service in PaaS.That is, In the embodiment of the present application, service tenant can be the VNF in NFV framework.
In addition, the MANO entity in PaaS the and NFV framework being deployed in NFV framework is mentioned for executing the embodiment of the present application The management method of the PaaS of confession, specifically executing the application by the PaaS management in PaaS and the MANO entity in NFV framework The management method for the PaaS that embodiment provides.
Wherein, PaaS management is also referred to as PaaS management entity or PaaS chain of command, and MANO entity specifically can be with For the VNFM in NFV framework.
Fig. 2 B is the structural schematic diagram of PaaS provided by the embodiments of the present application a kind of.The function of PaaS in Fig. 2A can lead to Computer equipment shown in Fig. 2 B is crossed to realize.B referring to fig. 2, the computer equipment include at least one processor 201, communication Bus 202, memory 203 and at least one communication interface 204.
Processor 201 can be general central processor (Central Processing Unit, CPU), micro process Device, application-specific integrated circuit (application-specific integrated circuit, ASIC) or one or more A integrated circuit executed for controlling application scheme program.
Communication bus 202 may include an access, and information is transmitted between said modules.
Memory 203 can be read-only memory (read-only memory, ROM) or can store static information and instruction Other types of static storage device, random access memory (random access memory, RAM) or letter can be stored The other types of dynamic memory of breath and instruction, is also possible to Electrically Erasable Programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), CD-ROM (Compact Disc Read- Only Memory, CD-ROM) or other optical disc storages, optical disc storage (including compression optical disc, laser disc, optical disc, digital universal Optical disc, Blu-ray Disc etc.), magnetic disk storage medium or other magnetic storage apparatus or can be used in carrying or store to have referring to Enable or data structure form desired program code and can by any other medium of computer access, but not limited to this. Memory 203, which can be, to be individually present, and is connected by communication bus 202 with processor 201.Memory 203 can also and be located Reason device 201 integrates.
Communication interface 204, using the device of any transceiver one kind, for other equipment or communication, such as Ethernet, wireless access network (Radio Access Network, RAN) or WLAN (Wireless Local Area Networks, WLAN) etc..
In the concrete realization, as one embodiment, processor 201 may include in one or more CPU, such as Fig. 2 B Shown in CPU0 and CPU1.
In the concrete realization, as one embodiment, computer equipment may include institute in multiple processors, such as Fig. 2 B The processor 201 and processor 205 shown.Each of these processors can be monokaryon (single-CPU) processing Device is also possible to multicore (multi-CPU) processor.Here processor can refer to one or more equipment, circuit, And/or the processing core for handling data (such as computer program instructions).
In the concrete realization, as one embodiment, computer equipment can also include output equipment 206 and input equipment 207.Output equipment 206 and processor 201 communicate, and can show information in many ways.For example, output equipment 206 can be with It is liquid crystal display (liquid crystal display, LCD), Light-Emitting Diode (light emitting diode, LED) Show that equipment, cathode-ray tube (cathode ray tube, CRT) show equipment or projector (projector) etc..Input Equipment 207 and processor 201 communicate, and can receive the input of user in many ways.For example, input equipment 207 can be mouse Mark, keyboard, touch panel device or sensing equipment etc..
Above-mentioned computer equipment can be a general purpose computing device either dedicated computing machine equipment.Having During body is realized, computer equipment can be desktop computer, portable computer, network server, palm PC (Personal Digital Assistant, PDA), cell phone, tablet computer, wireless terminal device, communication equipment or embedded device. The unlimited type for determining computer equipment of the embodiment of the present application.
Wherein, memory 203 is used to store the program code for executing application scheme, and is held by processor 201 to control Row.Processor 201 is for executing the program code 208 stored in memory 203.May include in program code 208 one or Multiple software modules.
The embodiment of the present application also provides the structure of MANO entity, which includes at least one processor, communication Bus, memory and at least one communication interface.Wherein, MANO entity includes processor, communication bus, memory and logical Believe that the function of interface and processor in Fig. 2 B, communication bus, memory and communication interface is essentially identical, no longer explains in detail herein It states.
Next explanation is explained in detail to the management method of PaaS provided by the embodiments of the present application.
Fig. 3 is the management method flow chart of PaaS provided by the embodiments of the present application a kind of, is applied to dispose shown in Fig. 2A Have in the NFV framework of PaaS, as shown in Figure 2 A, multiple services is deployed on the PaaS.Specifically, as shown in figure 3, this method packet Include following steps:
Step 301:MANO entity sends configuring request to PaaS, which carries the example of destination service tenant The mark of the example of mark and destination service.
In the embodiment of the present application, being managed main to the PaaS being deployed in NFV framework includes in two aspects Hold, first aspect is the instantiation to the service being deployed in PaaS, and second aspect is the end to the service being deployed in PaaS Knot.Wherein, step 301 and step 302 will be used for content expansion explanation to first aspect, step 303 to step 305 for pair Explanation is unfolded in the content of second aspect.
It should be noted that for the destination service tenant in NFV framework, in order to ensure the example of destination service tenant The example that the destination service being deployed on PaaS can be called, MANO entity the example for obtaining the destination service mark it Afterwards, need to PaaS send configuring request so that PaaS according to the configuring request carry destination service tenant example mark and The mark of the example of destination service, the use binding established between the example of destination service tenant and the example of destination service are closed System.
Wherein, the example that the mark of the example of the destination service is used for the unique identification destination service, the destination service are rented The example that the mark of the example at family is used for unique identification destination service tenant.
Further, after MANO entity sends configuring request to PaaS, in order to ensure the reality of destination service tenant The example that example can smoothly call the destination service, MANO entity also needs to establish the example of destination service tenant and the target takes Binding relationship is used between the example of business.
In addition, the mark that MANO entity obtains the example of the destination service specifically can be by the possible realization of following two Mode is realized:
The first possible implementation:When the example that MANO entity determines destination service tenant needs invocation target to take When business, case-based system request is sent to PaaS, case-based system request carries the mark of the destination service；It is real that PaaS receives MANO The case-based system request that body is sent sends the first response message to MANO entity when there is currently the example of the destination service, First response message is used to indicate that the destination service is instantiated, and first response message carries the reality of the destination service The mark of example.
It should be noted that the service may exist multiple examples, multiple for any service being deployed on PaaS Example may be occupied by the example of service tenant, and there may also be the example of the unserviced tenant of certain embodiments occupancy.Therefore, When the example that MANO entity determines the tenant of destination service needs to call the destination service, it first can send to be directed to PaaS and be somebody's turn to do The case-based system of destination service is requested, to determine the example that whether there is the unappropriated destination service in PaaS.
That is, in the embodiment of the present application, when the example that MANO entity determines destination service tenant needs to call the target When service, MANO entity sends the case-based system request for the destination service to PaaS, and case-based system request carries the mesh Mark the mark of service.When PaaS receives case-based system request, according to the mark of the destination service, determine whether to deposit In the example of the destination service, so as to the example for sending the destination service to MANO entity according to the first possible implementation Mark.
In addition, when MANO entity receives first response message, since MANO entity is to determine destination service rent When the example at family needs to call the destination service, the case-based system request sent to PaaS, therefore MANO entity at this time can root According to the mark of the example of the destination service of first response message carrying, the example and the target of destination service tenant are established Binding relationship is used between the example of service, so that the example of destination service tenant can call the reality of the destination service Example.
Specifically, case-based system request can be life cycle state inquiry request, at this point, first response message is taken Life cycle state with the destination service, and the life cycle state is to have instantiated, and has been used to indicate the destination service Instantiation, and there is currently the examples of the destination service.
Optionally, MANO entity can also determine the reality that whether there is the destination service in PaaS in other way Example, for example, determining the example that whether there is the destination service in PaaS by way of subscription.
Second of possible implementation:When the example that MANO entity determines destination service tenant needs invocation target to take When business, case-based system request is sent to PaaS, case-based system request carries the mark of the destination service.PaaS receives the MANO The case-based system request that entity is sent sends the second response to MANO entity when there is currently no the example of the destination service Message, it is uninstantiated which is used to indicate the destination service.MANO entity receives second response message, and to PaaS sends the service instantiation request for the destination service, and service instantiation request carries the mark of the destination service. When PaaS receives the service instantiation request of MANO entity transmission, the mark based on the destination service takes the target Business is instantiated, the example for obtaining the destination service, and sends instantiation response message, the instantiation response to MANO entity Message carries the mark of the example of the destination service.
In the second possible implementation, due to there is currently no the example of the destination service, PaaS to MANO entity sends the second response message and determines and do not deposit in current PaaS when MANO entity receives second response message In the example of the destination service.At this point, MANO entity can in order to allow the example of destination service tenant to call the destination service To send the service instantiation request for the destination service to PaaS, with the example for obtaining the destination service.
For example, second response message carries the mesh when case-based system request is life cycle state inquiry request Mark the life cycle state of service, and the life cycle state be it is uninstantiated, it is uninstantiated to be used to indicate the destination service, I.e. there is currently no the examples of the unappropriated destination service.
Specifically, the implementation that PaaS instantiates the destination service can be with are as follows: PaaS is from the service of storage The descriptor file of the destination service is obtained in descriptor file, the descriptor file of the destination service is for describing in the target Information required for during service instantiation.PaaS is instantiated according to the destination service in the descriptor file of the destination service Required information in the process instantiates the destination service, the example for obtaining the destination service.
Wherein, the mark of the destination service carried in request is requested and instantiated to case-based system for the unique identification target Service, specifically, the mark of the destination service can be the title of the destination service.
In addition, required information is pre-set information in the destination service instantiation process, the destination service is real Instance parameter, example quantity or scale when information required for during exampleization mainly includes the initial deployment destination service. Instance parameter, instance number when PaaS instantiates the destination service namely PaaS is according to the initial deployment destination service Amount or scale, complete the configuration of the example of the destination service and the distribution of resource.
That is, in the embodiment of the present application, for any service being deployed on PaaS, be stored in the PaaS with The corresponding descriptor file of the service can be according to description corresponding with the service when needing to instantiate the service Symbol file instantiates the service.
From the first above-mentioned possible implementation and second of possible implementation it is found that MANO entity is to PaaS After sending the case-based system request for destination service, no matter currently whether there is the example of the destination service, PaaS is In the example for determining the destination service and then the mark for the example for sending to MANO entity the destination service, to ensure this The example that the example of destination service tenant can call the destination service.
It should be noted that the mark for the example that PaaS sends the destination service to MANO entity can be destination service The mark of one example, or the mark of multiple examples of destination service, that is, PaaS can be distributed according to the actual situation It is not specifically limited herein to the example or multiple examples, the embodiment of the present application of the destination service tenant destination service.
In addition, by the first above-mentioned possible implementation and second of possible implementation it is found that MANO entity is equal It is to send the example for being directed to the destination service when the example for determining destination service tenant needs invocation target to service to PaaS and obtain Take request.
Wherein, the example that MANO entity determines destination service tenant needs invocation target service, and there may be following two fields Scape, that is, in the embodiment of the present application, can be instantiated in following two scene to the service in PaaS:
Scene one,The mark of the example of MANO entity set-up destination service tenant, and determine that destination service tenant makes When including destination service in service list, the example for determining destination service tenant needs invocation target service.
It should be noted that servicing tenant for any one, all there is descriptor file corresponding with service tenant, it should The corresponding user that services tenant and can call will be defined in descriptor file.In addition, MANO entity is rented in one service of creation After the mark of the example at family, the example of service tenant will be called during instantiating later to be defined in descriptor file Service example.
Therefore, when mark of the MANO entity in the example of creation destination service tenant, it may indicate that the destination service The example that tenant needs to call the destination service.
That is, when MANO entity is when creating the mark of example of destination service tenant, according to destination service tenant Descriptor file, by the service that destination service tenant can call defined in the descriptor file be determined as target clothes Business, and the case-based system request for the destination service is sent to PaaS.
When PaaS receives case-based system request, sent according to above two possible implementation to MANO entity For the mark of the example of the destination service, in order to MANO entity the example for receiving the destination service mark according to step Rapid 301 send configuring request to PaaS.
In scene one, MANO entity is after completing the creation to the mark of the example of destination service tenant, when the mesh When the example of mark service tenant needs to instantiate, binding relationship can be used according to foundation, called directly and the destination service The example of the corresponding destination service of the example of tenant, to complete the instantiation process of the example of destination service tenant.
Specifically, which is VNFM, when the VNFM receives the reality for the destination service tenant that NFVO or EM is sent When example mark request to create, VNFM is rented in the instance identification for localling create a destination service tenant, and from the destination service The mark for the destination service that destination service tenant can call is obtained in the description service document at family, and according to the destination service Mark send examples detailed above acquisition request.
It should be noted that in scene one, before MANO entity sends the case-based system request for the destination service Propose condition are as follows: the destination service is registered in PaaS, and is explicitly defined in the descriptor file of destination service tenant The service that destination service tenant can call.
Scene two,When the MANO entity instantiates the example of destination service tenant, and determine the destination service When including destination service in the service list that tenant uses, the example for determining destination service tenant needs invocation target service.
In scene two, for MANO entity when creating the mark of example of destination service tenant, there is no image field scapes one Example of the case-based system request to obtain destination service is sent to PaaS like that, but in the example of creation destination service tenant Mark after, during the example of destination service tenant instantiates, to PaaS send be directed to the destination service The case-based system for the destination service that tenant can call is requested.
That is, MANO entity creation destination service tenant example mark after, when destination service tenant's When example currently needs to instantiate, the descriptor file of destination service tenant is determined, will be somebody's turn to do defined in the descriptor file The service that destination service tenant can call is determined as destination service, and the case-based system for being directed to the destination service is sent to PaaS Request.
It, equally can be according to above two possible implementation to MANO when PaaS receives case-based system request Entity sends the mark of the example for the destination service, in order to which MANO entity is in the mark for the example for receiving the destination service Know and configuring request is sent to PaaS according to step 301.
Obviously, in scene two, MANO entity sends the precondition requested for the case-based system of the destination service are as follows: The destination service is registered in PaaS, and MANO entity has created the mark of the example of destination service tenant, and The service that destination service tenant can call is exactly defined in the descriptor file of destination service tenant.
Step 302:PaaS receives the configuring request, the mark of the example of the destination service tenant based on configuring request carrying Know and the mark of the example of destination service, the use established between the example of the destination service and the example of destination service tenant are tied up Determine relationship, and establishes destination service tenant there is no when destination service tenant in the tenant's list for determining destination service Contract binding relationship between the destination service.
When PaaS receives the configuring request, in order to ensure the example of destination service tenant can call the destination service Example, PaaS need to establish between the example of the destination service and the example of destination service tenant use binding relationship.
That is, after sending the mark of the example of the destination service to MANO entity in PaaS, in order to ensure target clothes The example example that can call the destination service of business tenant is stored with destination service tenant's in PaaS and MANO entity Binding relationship is used between example and the example of the destination service.
Significantly, since different service tenants can call the same service, therefore, in present example In, when destination service tenant for the first time instantiates the destination service, that is, PaaS is created according to destination service tenant When the example of first destination service, PaaS need to establish the contract binding relationship between destination service tenant and the destination service. Later, when deserving destination service tenant second and being instantiated to the destination service, without resettling destination service tenant With the contract binding relationship after the destination service.That is, when servicing between service tenant there are when contract binding relationship, table Bright service tenant can call the service.
Therefore, when PaaS receives service configuration request, and example and the destination service tenant of the destination service are established Between example using binding relationship when, whether the example that can determine the destination service is destination service tenant for the first time to mesh Example when service instantiation is marked, if it is then also needing the conjunction established between destination service tenant and destination service at this time About binding relationship.
It should be noted that PaaS is that the service maintains tenant's list for any service being deployed on PaaS, Record has the mark for the service tenant for having called up the service in tenant's list.
Therefore, PaaS uses binding relationship between the example for establishing the destination service and the example of destination service tenant When, it can also determine in tenant's list of destination service and be rented with the presence or absence of the destination service according to the mark of destination service tenant The destination service is then established if it does not, showing is currently example that destination service tenant creates the destination service for the first time in family Contract binding relationship between tenant and destination service.
It is further to note that by step 302 it is found that there are two different binding relationships in the embodiment of the present application, Using binding relationship and contract binding relationship, in order to avoid obscuring, at this to using relationship and contract binding relationship to explain Illustrate:
For PaaS, in order to ensure service tenant can call service, it need to establish between service tenant and service Corresponding relationship；And in order to ensure the example that the example of service tenant can call service, the example and clothes of service tenant need to be established Corresponding relationship between the example of business.Therefore, for ease of description, the corresponding relationship between tenant and service will be serviced to be known as taking The contract binding relationship being engaged between tenant and service, the corresponding relationship between the example for servicing the example and service of tenant is known as It services and uses binding relationship between the example of tenant and the example of service.That is, what is established between service tenant and service is Contract binding relationship, servicing establish between the example of tenant and the example of service is using binding relationship.
Since a service tenant usually has multiple examples, and a service also usually has multiple examples, and therefore, contract is tied up The example that the example of presence service tenant calls service can only be shown by determining relationship, but not can be shown which for specifically servicing tenant The example that a example has invoked service, and can be clearly indicated that using binding relationship be service tenant which example have invoked clothes The example of business.
For example, for destination service tenant and destination service, if example there are three destination service tenants, respectively A1, A2 and A3, also there are three examples, respectively B1, B2 and B3 for destination service, and the example of the destination service of current A1 calling is B1, The example for the destination service that A2 is called is B2, and the example for the destination service that A3 is called is B3.At this point, in PaaS, for target Tenant and destination service are serviced, a contract binding relationship, i.e. contract between destination service tenant and destination service are only existed Binding relationship.But there are three use binding relationship, between respectively A1 and B1 using between binding relationship, A2 and B2 Binding relationship is used using between relationship, A3 and B3.
Above-mentioned steps 301 and step 302 are used to that the instantiation process of service provided by the embodiments of the present application to be introduced, It will be introduced below by terminating procedures of the step 303 to step 305 to service provided by the embodiments of the present application.
Step 303: when MANO entity determines that the destination service tenant in NFV framework does not recall the destination service, to PaaS sends the service configuration request for being directed to the destination service.
In the embodiment of the present application, in order to avoid cause because of the termination for calling the service tenant of the service service end Knot, when MANO entity determines that destination service tenant no longer needs to call the destination service, for the destination service that terminates, MANO entity needs first to send the service configuration request for being directed to the destination service to PaaS, to be determined as the case may be by PaaS Whether the terminate destination service is needed, to realize the destination service that terminates on demand.
It should be noted that MANO entity may determine that destination service tenant no longer needs to adjust in following two scene With the destination service, that is, in the embodiment of the present application, may need to carry out eventually destination service in following two scene Knot.
Scene one:When the descriptor file of destination service tenant is updated, due to the descriptor of destination service tenant The service that destination service tenant can call is defined in file, therefore, in the descriptor file quilt of destination service tenant When update, it may be necessary to the service that the destination service tenant that terminates can call.
Specifically, it when MANO entity determines that the descriptor file of destination service tenant is updated, obtains after updating The descriptor file of destination service tenant.The descriptor file of destination service tenant after MANO entity is according to update, When determining that needs delete the destination service from the service list that destination service tenant uses, service configuration is sent to the PaaS Request.
At this point, due to needing to delete the destination service from the service list that destination service tenant uses, that is, the mesh Mark service tenant will not call the destination service again, therefore MANO entity needs that PaaS is requested to release destination service tenant Contract binding relationship between the destination service.
In practical application, in order to distinguish the service configuration request under different scenes, configuration is carried in service configuration request Type.Therefore, in scene one, the Configuration Type which carries is to release contract, and service configuration request is also The mark of destination service tenant and the mark of destination service are carried, so that PaaS releases target clothes according to the service configuration request The contract binding relationship being engaged between tenant and the destination service.
Wherein, the mark of destination service tenant is used for unique identification destination service tenant, specifically, when the destination service When tenant is VNF, the mark of destination service tenant can be the title of the VNF.
For example, when VNF manufacturer has updated the descriptor file of VNF, descriptor text of the VNFM after obtaining the update After part, need to delete some service from the service list of the VNF if being determined according to the descriptor file after the update When, VNFM will need the service deleted to be determined as destination service, and send the service configuration request in scene one to PaaS.The clothes Business configuring request carries Configuration Type, the mark of the VNF, the mark for the service for needing to delete, wherein Configuration Type is to release to close About.
Scene two:When MANO entity deletes the mark of the example of destination service tenant, show destination service tenant Example by the example for the destination service not recalled, therefore when delete destination service tenant example when, it may be necessary to eventually Tie the destination service.
It should be noted that in scene two, the mark of the example due to being intended merely to delete destination service tenant, only It is to show this example no longer invocation target service of destination service tenant, but can not represent destination service tenant's Other examples do not recall the destination service.Therefore, in order to avoid the PaaS destination service that terminates immediately leads to the destination service Other examples of tenant cannot continue to call the destination service, for destination service tenant, be additionally provided with lag time, this is late The stagnant time is the time that PaaS delay releases the contract binding relationship between destination service tenant and destination service.
Wherein, tenant is serviced for any one, includes pre-set slow in the descriptor file of service tenant The stagnant time.
Therefore, when MANO entity need to delete the mark of the example of destination service tenant, destination service tenant is obtained Descriptor file；According to the descriptor file of destination service tenant, lag time is determined, and send service configuration to PaaS Request.
At this point, simply indicating that the destination service is rented due to the mark for the example for being intended merely to delete destination service tenant This example no longer invocation target service at family, but other examples that can not represent destination service tenant do not recall this Destination service.Therefore, the reality of MANO entity only needs that PaaS is requested to release destination service tenant example and the destination service Binding relationship is used between example.
That is, the Configuration Type that the service configuration request carries is to release to use, and the service configuration is asked in scene two Ask the mark and lag time of the example of the mark, the destination service that also carry the example of destination service tenant.
For example, being asked when the VNFM in NFV framework receives the instance identification deletion for some VNF that NFVO or EM is sent When asking, VNFM deletes the mark of the example of the VNF in local, and according to the service list of the VNF, sends to be directed to PaaS and be somebody's turn to do The service configuration request of VNF.The service configuration request carries the example tune of Configuration Type, the mark of the example of the VNF, the VNF The mark and lag time of the example of service, wherein Configuration Type is to release to use.
Step 304:PaaS receives the service configuration request for the destination service that MANO entity is sent, and is based on the clothes Business configuring request, releases the contract binding relationship between destination service tenant and destination service.
From step 303 it is found that MANO entity may be sent to PaaS for the destination service in two different scenes Service configuration request, therefore, correspondingly, step 304 is also specifically divided into following two situation:
For the scene one in step 303:When PaaS receives the service configuration request of the destination service, due to the clothes The Configuration Type that configuring request of being engaged in carries is to release contract, therefore the target that PaaS can be carried according to the service configuration request takes The mark of tenant of being engaged in and the mark of destination service, search the conjunction between the destination service tenant having built up and the destination service About binding relationship, and release the contract binding relationship between destination service tenant and the destination service.
PaaS is also needed after releasing the contract binding relationship between destination service tenant and the destination service to MANO Entity sends first kind service configuration response message, which is used to indicate destination service and target Contract binding relationship between service tenant has released.
That is, determining that PaaS takes target when MANO entity receives the first kind service configuration response message Contract binding relationship between business and destination service tenant releases.
For the scene two in step 303:When PaaS receives the service configuration request of the destination service, due to the clothes The Configuration Type that configuring request of being engaged in carries is to release to use, therefore the target that PaaS can be carried according to the service configuration request takes Be engaged in tenant example mark and destination service example mark, search the example of the destination service tenant having built up with Binding relationship is used between the example of the destination service, and releases this and uses binding relationship.
PaaS release destination service tenant example and the destination service example between using binding relationship it Afterwards, it also needs to send the second class service configuration response message to MANO entity, which is used to indicate Having been released using binding relationship between the example of destination service and the example of destination service tenant.
That is, determining that PaaS takes target when MANO entity receives the second class service configuration response message Being released using binding relationship between the example of business and the example of destination service tenant.
Since in second of scene, MANO entity services configuring request further includes a lag time, and therefore, PaaS exists After between the example of destination service and the example of destination service tenant using binding relationship releasing, in order to avoid PaaS is vertical The destination service that terminates causes other examples of destination service tenant that cannot continue to call the destination service, and PaaS can be opened Beginning timing, the time of the timing are lag time, and determine whether destination service tenant adjusts again in the lag time With the destination service.If destination service tenant does not recall the destination service in the lag time after current time, PaaS can release the contract binding relationship between destination service tenant and the destination service at this time, and according to following step 305 decide whether the destination service that terminates.
Correspondingly, if destination service tenant is also calling target clothes in the lag time after current time Business, PaaS is not necessarily to release the contract binding relationship between destination service tenant and the destination service at this time, that is, PaaS will not Can terminate the destination service.
Step 305: when PaaS determines that there is no the contracts between the service tenant of other in NFV framework and destination service to tie up When determining relationship, all examples for the destination service that terminates.
In the embodiment of the present application, in order to avoid the example due to service is with the end of the example for the VNF for calling the service When tying and terminate, and causing to call the service every time, the case where instantiating to proprietary service appearance is all needed.When PaaS root When releasing the contract binding relationship between destination service tenant and the destination service according to step 304, PaaS is not whole immediately The destination service is tied, but first judges whether there is other service tenants for needing to call the destination service.
If there are still other service tenants for needing to call the destination service, if the destination service that directly terminates at this time, Other service tenants be will lead to when continuing to call the destination service, the destination service need to be instantiated again.Therefore, in this Shen Please be in embodiment, PaaS will not terminate the destination service immediately, but determine that there is no need to call the destination service in PaaS Other service tenant when, can just terminate the destination service.
Specifically, PaaS can by judge currently with the presence or absence of with the destination service there are contract binding relationship other Service tenant, Lai Shixian determines whether there is the service tenant for needing to call the destination service, that is, when there is currently no with this Destination service determines that there is no other clothes for needing to call the destination service there are when other services tenant of contract binding relationship Be engaged in tenant, and PaaS terminates the destination service at this time.
Correspondingly, when there is currently with the destination service there are contract binding relationship other service tenant when, at this point, PaaS will not terminate the destination service.
Wherein, PaaS terminates the destination service, that is, PaaS deletes all examples of the destination service, and discharges the mesh Mark the occupied resource of all examples of service.
In the embodiment of the present application, multiple services are deployed on PaaS, when MANO entity is determining destination service rent When family no longer needs to call the destination service, the service configuration request for being directed to the destination service is sent to PaaS.PaaS is based on should Service configuration request releases the contract binding relationship between destination service tenant and the destination service, and does not deposit it in determination When he services the contract binding relationship between tenant and the destination service, all examples for the destination service that terminates.Therefore, this Shen Please in provide service remained like that not necessarily like public service online, so as to cause public service occupy resource long-time It cannot discharge, enhance the dynamic availability of resource in PaaS platform, while service provided by the present application is also not necessarily like proprietary clothes Business terminates with the termination of the example of service tenant like that, improves example the weighing between multiple service tenants of service With property, significant increase efficiency of the PaaS platform to the resource management of service.
A referring to fig. 4, the embodiment of the present application provide the managing device 400 of PaaS a kind of, applied to being deployed in NFV framework In PaaS, which is characterized in that multiple services are deployed on the PaaS, the device 400 include the first receiving module 401, release Module 402 and termination block 403:
First receiving module 401, the PaaS in the step 304 for executing Fig. 3 embodiment receive what MANO entity was sent For the destination service service configuration request the step of；
Release module 402, in the step 304 for executing Fig. 3 embodiment based on the service configuration request, release target The step of servicing the contract binding relationship between tenant and destination service；
Termination block 403, for executing the step 305 of Fig. 3 embodiment.
Optionally, which carries Configuration Type, the mark of destination service tenant and the destination service Mark, the Configuration Type are to release contract.
Optionally, the device 400 further include:
Third sending module, for sending first kind service configuration response message, the first kind service to the MANO entity Configuration response message is used to indicate the contract binding relationship between the destination service and destination service tenant and has released.
Optionally, which carries Configuration Type, the mark of the example of destination service tenant, target clothes The mark and lag time of the example of business, the Configuration Type are to release to use；
Correspondingly, the releasing module 402, is specifically used for:
The mark of example based on the Configuration Type, the mark of the example of destination service tenant and the destination service, solution Except the use binding relationship between the example of the destination service and the example of destination service tenant；
Destination service tenant does not call the target to take again in lag time after determining in current time When business, the contract binding relationship between the destination service and destination service tenant is released.
Optionally, the device 400 further include:
4th sending module, for sending the second class service configuration response message, the second class service to the MANO entity Configuration response message is used to indicate between the example of the destination service and the example of destination service tenant and uses binding relationship It has released.
Optionally, B, the device 400 further include the second receiving module 404 and establish module 405 referring to fig. 4:
Second receiving module 404, the PaaS in step 302 for executing Fig. 3 embodiment receive the step of the configuring request Suddenly；
Module 405 is established, the target clothes carried based on the configuring request in the step 302 for executing Fig. 3 embodiment The mark of the example of the mark and destination service of the example of business tenant establishes the example of the destination service with destination service tenant's Binding relationship is used between example, and is built in the tenant's list for determining destination service there is no when destination service tenant The step of founding the contract binding relationship between destination service tenant and the destination service.
Optionally, which further includes third receiving module, the first sending module and the second sending module:
Third receiving module, for receiving the case-based system request of MANO entity transmission, case-based system request is carried The mark of the destination service；
First sending module, for determining there are when the example of the destination service when the mark based on the destination service, to The MANO entity sends the first response message, and it is instantiated which is used to indicate the destination service, and this One response message carries the mark of the example of the destination service；
Second sending module, for when based on the destination service mark determine be not present the destination service example when, The second response message is sent to the MANO entity, it is uninstantiated which is used to indicate the destination service, and receiving should The service instantiation that MANO entity is sent is requested, and the mark of the destination service is carried in service instantiation request, is based on the mesh The mark for marking service, instantiates the destination service, the example for obtaining the destination service, sends example to the MANO entity Change response message, which carries the mark of the example of the destination service.
Optionally, second sending module, is specifically used for:
Mark based on the destination service obtains the descriptor of the destination service from the descriptor file of the service of storage File, the descriptor file of the destination service is for describing the required information in the destination service instantiation process；
According to required information in the destination service instantiation process in the descriptor file of the destination service, to the mesh Mark service is instantiated, the example for obtaining the destination service.
Optionally, which is the virtual network function manager VNFM in the NFV framework.
In the embodiment of the present application, multiple services are deployed on PaaS, when MANO entity is determining destination service rent When family no longer needs to call the destination service, the service configuration request for being directed to the destination service is sent to PaaS.PaaS is based on should Service configuration request releases the contract binding relationship between destination service tenant and the destination service, and does not deposit it in determination When he services the contract binding relationship between tenant and the destination service, all examples for the destination service that terminates.Therefore, this Shen Please in provide service remained like that not necessarily like public service online, so as to cause public service occupy resource long-time It cannot discharge, enhance the dynamic availability of resource in PaaS platform, while service provided by the present application is also not necessarily like proprietary clothes Business terminates with the termination of the example of service tenant like that, improves example the weighing between multiple service tenants of service With property, significant increase efficiency of the PaaS platform to the resource management of service.
Referring to Fig. 5 A, the embodiment of the present application provides the managing device 500 of another PaaS, applied in NFV framework MANO entity is deployed with PaaS in the NFV framework, which includes the first sending module 501:
First sending module 501, for executing the step 303 in Fig. 3 embodiment；
The service configuration request is used to indicate the PaaS and is released destination service tenant based on the service configuration request and be somebody's turn to do Contract binding relationship between destination service, and determining that there is no the contracts between other service tenants and the destination service to tie up Determine to terminate when relationship all examples of the destination service, which is any service in multiple service.
Optionally, first sending module 501, is specifically used for:
When the descriptor file for determining destination service tenant is updated, the destination service tenant after updating is obtained Descriptor file；
The descriptor file of destination service tenant after according to update is determined and is needed the destination service from the mesh When deleting in the service list that mark service tenant uses, service configuration request is sent to the PaaS, which carries The mark of Configuration Type, the mark of destination service tenant and the destination service, the Configuration Type are to release contract.
Optionally, which further includes third receiving module:
Third receiving module, for receiving the first kind service configuration response message of PaaS transmission, the first kind service Configuration response message is used to indicate the contract binding relationship between the destination service and destination service tenant and has released.
Optionally, first sending module 501, is specifically used for:
When deleting the mark of example of destination service tenant, the descriptor file of destination service tenant is obtained；
According to the descriptor file of destination service tenant, lag time is determined；
The service configuration request is sent to the PaaS, which carries Configuration Type, destination service tenant The mark of example, the mark of the example of the destination service and the lag time, the Configuration Type be release use.
Optionally, which further includes the 4th receiving module:
4th receiving module, for receiving the second class service configuration response message of PaaS transmission, the second class service Configuration response message is used to indicate between the example of the destination service and the example of destination service tenant and uses binding relationship It has released.
Optionally, referring to Fig. 5 B, which further includes the second sending module 502:
Second sending module 502, for executing the step 301 in Fig. 3 embodiment.
Optionally, which further includes third sending module, the first receiving module and the second receiving module:
Third sending module, for when the example for determining destination service tenant needs invocation target to service, to this PaaS sends case-based system request, and case-based system request carries the mark of the destination service；
First receiving module, for receiving the first response message of PaaS transmission, which is used to indicate The destination service is instantiated, and first response message carries the mark of the example of the destination service；
Second receiving module, for receiving the second response message of PaaS transmission, which is used to indicate The destination service is uninstantiated, sends service instantiation request to the PaaS, target clothes are carried in service instantiation request The mark of business receives the instantiation response message of PaaS transmission, the example which carries the destination service Mark.
Optionally, which is the virtual network function manager VNFM in the NFV framework.
In the embodiment of the present application, multiple services are deployed on PaaS, when MANO entity is determining destination service rent When family no longer needs to call the destination service, the service configuration request for being directed to the destination service is sent to PaaS.PaaS is based on should Service configuration request releases the contract binding relationship between destination service tenant and the destination service, and does not deposit it in determination When he services the contract binding relationship between tenant and the destination service, all examples for the destination service that terminates.Therefore, this Shen Please in provide service remained like that not necessarily like public service online, so as to cause public service occupy resource long-time It cannot discharge, enhance the dynamic availability of resource in PaaS platform, while service provided by the present application is also not necessarily like proprietary clothes Business terminates with the termination of the example of service tenant like that, improves example the weighing between multiple service tenants of service With property, significant increase efficiency of the PaaS platform to the resource management of service.
It should be understood that the managing device of PaaS provided by the above embodiment is managed to the service on PaaS When, only the example of the division of the above functional modules, in practical application, it can according to need and divide above-mentioned function With being completed by different functional modules, i.e., the internal structure of equipment is divided into different functional modules, to complete above description All or part of function.In addition, the pipe of the PaaS in the managing device of PaaS provided by the above embodiment and Fig. 3 embodiment Reason embodiment of the method belongs to same design, and specific implementation process is detailed in embodiment of the method, and which is not described herein again.
In the above-described embodiments, can come wholly or partly by software, hardware, firmware or its any combination real It is existing.When implemented in software, it can entirely or partly realize in the form of a computer program product.The computer program Product includes one or more computer instructions.It is all or part of when loading on computers and executing the computer instruction Ground is generated according to process or function described in the embodiment of the present application.The computer can be general purpose computer, special purpose computer, Computer network or other programmable devices.The computer instruction may be stored in a computer readable storage medium, or Person is transmitted from a computer readable storage medium to another computer readable storage medium, for example, the computer instruction Can from a web-site, computer, server or data center by it is wired (such as: coaxial cable, optical fiber, data use Family line (Digital Subscriber Line, DSL)) or wireless (such as: infrared, wireless, microwave etc.) mode to another net Website, computer, server or data center are transmitted.The computer readable storage medium can be computer can Any usable medium of access either includes the data storage such as one or more usable mediums integrated server, data center Equipment.The usable medium can be magnetic medium (such as: floppy disk, hard disk, tape), optical medium (such as: digital versatile disc (Digital Versatile Disc, DVD)) or semiconductor medium (such as: solid state hard disk (Solid State Disk, SSD)) etc..
Those of ordinary skill in the art will appreciate that realizing that all or part of the steps of above-described embodiment can pass through hardware It completes, relevant hardware can also be instructed to complete by program, the program can store in a kind of computer-readable In storage medium, storage medium mentioned above can be read-only memory, disk or CD etc..
The above is embodiment provided by the present application, all in spirit herein and original not to limit the application Within then, any modification, equivalent replacement, improvement and so on be should be included within the scope of protection of this application.

Claims (22)

1. a kind of platform be service PaaS management method, applied to be deployed in network function virtualization NFV framework in PaaS, It is characterized in that, being deployed with multiple services on the PaaS, which comprises
The service configuration for destination service that the management in the NFV framework is sent with layout function MANO entity is received to ask It asks, the service configuration request is determining that the destination service tenant in the NFV framework do not recall institute for the MANO entity It is sent when stating destination service, the destination service is any of the multiple service；
Based on the service configuration request, the contract binding released between the destination service tenant and the destination service is closed System, the contract binding relationship, which is used to indicate the destination service tenant, can call the destination service；
Contract binding relationship between determining other service tenants being not present in the NFV framework and the destination service When, all examples for the destination service that terminates.
2. the method as described in claim 1, which is characterized in that the service configuration request carries Configuration Type, the target The mark of tenant and the mark of the destination service are serviced, the Configuration Type is to release contract.
3. the method as described in claim 1, which is characterized in that the service configuration request carries Configuration Type, the target Mark, the mark and lag time of the example of the destination service of the example of tenant are serviced, the Configuration Type is to release to make With；
Correspondingly, described to be based on the service configuration request, it releases between the destination service tenant and the destination service Contract binding relationship, comprising:
The mark of example based on the Configuration Type, the mark of the example of the destination service tenant and the destination service, It releases and uses binding relationship between the example of the destination service and the example of the destination service tenant；
The destination service tenant does not call the target again in lag time after determining in current time When service, the contract binding relationship between the destination service and the destination service tenant is released.
4. the method as described in claim 1, which is characterized in that the MANO entity received in the NFV framework was sent Before the service configuration request of destination service, further includes:
The configuring request that the MANO entity is sent is received, the configuring request carries the mark of the example of the destination service tenant Know the mark with the example of the destination service；
The mark of the example of the mark and destination service of example based on the destination service tenant establishes the target clothes It is engaged in using binding relationship between the example of tenant and the example of the destination service, and in the tenant for determining the destination service When the destination service tenant being not present in list, the contract established between the destination service tenant and the destination service is tied up Determine relationship.
5. method as claimed in claim 4, which is characterized in that it is described receive configuring request that the MANO entity is sent it Before, further includes:
The case-based system request that the MANO entity is sent is received, the case-based system request carries the mark of the destination service Know；
When the mark based on the destination service is determined there are when the example of the destination service, Xiang Suoshu MANO entity sends the One response message, it is instantiated that first response message is used to indicate the destination service, and first response message Carry the mark of the example of the destination service；
When the mark based on the destination service determines the example that the destination service is not present, Xiang Suoshu MANO entity is sent Second response message, it is uninstantiated that second response message is used to indicate the destination service, receives the MANO entity hair The service instantiation sent is requested, and the mark of the destination service is carried in the service instantiation request, is taken based on the target The mark of business instantiates the destination service, the example for obtaining the destination service, and Xiang Suoshu MANO entity sends real Exampleization response message, the instantiation response message carry the mark of the example of the destination service.
6. method as claimed in claim 5, which is characterized in that the mark based on the destination service, to the target Service is instantiated, the example for obtaining the destination service, comprising:
Based on the mark of the destination service, the descriptor of the destination service is obtained from the descriptor file of the service of storage File, the descriptor file of the destination service is for describing the required information in the destination service instantiation process；
According to information required in destination service instantiation process described in the descriptor file of the destination service, to described Destination service is instantiated, the example for obtaining the destination service.
7. a kind of platform is the management method for servicing PaaS, applied to the management and layout in network function virtualization NFV framework Function MANO entity is deployed with PaaS in the NFV framework, which is characterized in that multiple services are deployed on the PaaS, it is described Method includes:
When determining that the no longer invocation target of the destination service tenant in the NFV framework services, Xiang Suoshu PaaS, which is sent, is directed to institute State the service configuration request of destination service；
The service configuration request is used to indicate the PaaS and is based on the service configuration request releasing destination service tenant Contract binding relationship between the destination service, and determining that there is no between other service tenants and the destination service Contract binding relationship when terminate all examples of the destination service, the destination service is any in the multiple service Service.
8. the method for claim 7, which is characterized in that the destination service tenant when in the determining NFV framework When no longer invocation target services, Xiang Suoshu PaaS sends the service configuration request for being directed to the destination service, comprising:
When the descriptor file for determining the destination service tenant is updated, the destination service tenant after updating is obtained Descriptor file；
The descriptor file of destination service tenant after according to update is determined and is needed the destination service from described When deleting in the service list that destination service tenant uses, Xiang Suoshu PaaS sends service configuration request, and the service configuration is asked It asks and carries Configuration Type, the mark of the destination service tenant and the mark of the destination service, the Configuration Type is to release Contract.
9. the method for claim 7, which is characterized in that the destination service tenant when in the determining NFV framework When no longer invocation target services, Xiang Suoshu PaaS sends the service configuration request for being directed to the destination service, comprising:
When deleting the mark of example of the destination service tenant, the descriptor file of the destination service tenant is obtained；
According to the descriptor file of the destination service tenant, lag time is determined；
The service configuration request is sent to the PaaS, the service configuration request carries Configuration Type, the destination service The mark of the example of tenant, the mark of the example of the destination service and the lag time, the Configuration Type are to release to make With.
10. the method for claim 7, which is characterized in that described to send to the PaaS for the destination service Before service configuration request, further includes:
Configuring request is sent to the PaaS, and the configuring request carries the mark of the example of the destination service tenant and described The mark of the example of destination service, the configuring request be used to indicate the PaaS establish the example of the destination service tenant with Binding relationship is used between the example of the destination service.
11. method as claimed in claim 10, which is characterized in that before the transmission configuring request to the PaaS, also wrap It includes:
When the example for determining the destination service tenant needs invocation target to service, Xiang Suoshu PaaS sends case-based system and asks It asks, the case-based system request carries the mark of the destination service；
The first response message that the PaaS is sent is received, it is real that first response message is used to indicate the destination service Exampleization, and first response message carries the mark of the example of the destination service；
The second response message that the PaaS is sent is received, second response message is used to indicate the non-example of the destination service Change, Xiang Suoshu PaaS sends service instantiation request, and the mark of the destination service is carried in the service instantiation request, is connect The instantiation response message that the PaaS is sent is received, the instantiation response message carries the mark of the example of the destination service Know.
12. a kind of platform is the managing device for servicing PaaS, virtualized in NFV framework applied to network function is deployed in PaaS, which is characterized in that multiple services are deployed on the PaaS, described device includes:
First receiving module, for receiving the management in the NFV framework with the transmission of layout function MANO entity for target The service configuration request of service, the service configuration request are that the MANO entity is determining the target clothes in the NFV framework Business tenant does not recall to be sent when the destination service, and the destination service is any of the multiple service；
Module is released, for being based on the service configuration request, is released between the destination service tenant and the destination service Contract binding relationship, the contract binding relationship, which is used to indicate the destination service tenant, can call the destination service；
Termination block, for when between determining other service tenants being not present in the NFV framework and the destination service When contract binding relationship, all examples for the destination service that terminates.
13. device as claimed in claim 12, which is characterized in that the service configuration request carries Configuration Type, the mesh The mark of mark service tenant and the mark of the destination service, the Configuration Type is to release contract.
14. device as claimed in claim 12, which is characterized in that the service configuration request carries Configuration Type, the mesh Mark, the mark and lag time of the example of the destination service of the example of mark service tenant, the Configuration Type are to release It uses；
Correspondingly, the releasing module, is specifically used for:
The mark of example based on the Configuration Type, the mark of the example of the destination service tenant and the destination service, It releases and uses binding relationship between the example of the destination service and the example of the destination service tenant；
The destination service tenant does not call the target again in lag time after determining in current time When service, the contract binding relationship between the destination service and the destination service tenant is released.
15. device as claimed in claim 12, which is characterized in that described device further include:
Second receiving module, the configuring request sent for receiving the MANO entity, the configuring request carry the target Service the mark of the mark of the example of tenant and the example of the destination service；
Module is established, the mark of the example of the mark and destination service for the example based on the destination service tenant, It establishes between the example of the destination service tenant and the example of the destination service and uses binding relationship, and described in the determination When the destination service tenant being not present in tenant's list of destination service, establishes the destination service tenant and the target takes Contract binding relationship between business.
16. device as claimed in claim 15, which is characterized in that described device further include:
Third receiving module, the case-based system request sent for receiving the MANO entity, the case-based system request carry The mark of the destination service；
First sending module, for determining there are when the example of the destination service when the mark based on the destination service, to The MANO entity sends the first response message, and it is instantiated that first response message is used to indicate the destination service, And first response message carries the mark of the example of the destination service；
Second sending module, for when based on the destination service mark determine be not present the destination service example when, The second response message is sent to the MANO entity, it is uninstantiated that second response message is used to indicate the destination service, The service instantiation request that the MANO entity is sent is received, the mark of the destination service is carried in the service instantiation request Know, based on the mark of the destination service, the destination service is instantiated, the example for obtaining the destination service, to The MANO entity sends instantiation response message, and the instantiation response message carries the mark of the example of the destination service Know.
17. device as claimed in claim 16, which is characterized in that second sending module is specifically used for:
Based on the mark of the destination service, the descriptor of the destination service is obtained from the descriptor file of the service of storage File, the descriptor file of the destination service is for describing the required information in the destination service instantiation process；
According to information required in destination service instantiation process described in the descriptor file of the destination service, to described Destination service is instantiated, the example for obtaining the destination service.
18. a kind of platform is the managing device for servicing PaaS, applied to the management and layout in network function virtualization NFV framework Function MANO entity is deployed with PaaS in the NFV framework, which is characterized in that multiple services are deployed on the PaaS, it is described Device includes:
First sending module, for when determine the destination service tenant in the NFV framework no longer invocation target service when, to institute It states PaaS and sends the service configuration request for being directed to the destination service；
The service configuration request is used to indicate the PaaS and is based on the service configuration request releasing destination service tenant Contract binding relationship between the destination service, and determining that there is no between other service tenants and the destination service Contract binding relationship when terminate all examples of the destination service, the destination service is any in the multiple service Service.
19. device as claimed in claim 18, which is characterized in that first sending module is specifically used for:
When the descriptor file for determining the destination service tenant is updated, the destination service tenant after updating is obtained Descriptor file；
The descriptor file of destination service tenant after according to update is determined and is needed the destination service from described When deleting in the service list that destination service tenant uses, Xiang Suoshu PaaS sends service configuration request, and the service configuration is asked It asks and carries Configuration Type, the mark of the destination service tenant and the mark of the destination service, the Configuration Type is to release Contract.
20. device as claimed in claim 18, which is characterized in that first sending module is specifically used for:
When deleting the mark of example of the destination service tenant, the descriptor file of the destination service tenant is obtained；
According to the descriptor file of the destination service tenant, lag time is determined；
The service configuration request is sent to the PaaS, the service configuration request carries Configuration Type, the destination service The mark of the example of tenant, the mark of the example of the destination service and the lag time, the Configuration Type are to release to make With.
21. device as claimed in claim 18, which is characterized in that described device further include:
Second sending module, for sending configuring request to the PaaS, the configuring request carries the destination service tenant Example mark and the destination service example mark, the configuring request is used to indicate the PaaS and establishes the mesh Binding relationship is used between the example of mark service tenant and the example of the destination service.
22. device as claimed in claim 21, which is characterized in that described device further include:
Third sending module, for when the example for determining the destination service tenant needs invocation target to service, Xiang Suoshu PaaS sends case-based system request, and the case-based system request carries the mark of the destination service；
First receiving module, the first response message sent for receiving the PaaS, first response message are used to indicate The destination service is instantiated, and first response message carries the mark of the example of the destination service；
Second receiving module, the second response message sent for receiving the PaaS, second response message are used to indicate The destination service is uninstantiated, and Xiang Suoshu PaaS sends service instantiation request, carries institute in the service instantiation request The mark for stating destination service, receives the instantiation response message that the PaaS is sent, described in the instantiation response message carrying The mark of the example of destination service.
CN201711288701.XA 2017-12-07 2017-12-07 PaaS management method, device and storage medium Active CN109905258B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201711288701.XA CN109905258B (en) 2017-12-07 2017-12-07 PaaS management method, device and storage medium
PCT/CN2018/119367 WO2019109948A1 (en) 2017-12-07 2018-12-05 Paas management method and device, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711288701.XA CN109905258B (en) 2017-12-07 2017-12-07 PaaS management method, device and storage medium

Publications (2)

Publication Number Publication Date
CN109905258A true CN109905258A (en) 2019-06-18
CN109905258B CN109905258B (en) 2020-11-17

Family

ID=66751302

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711288701.XA Active CN109905258B (en) 2017-12-07 2017-12-07 PaaS management method, device and storage medium

Country Status (2)

Country Link
CN (1) CN109905258B (en)
WO (1) WO2019109948A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111240868A (en) * 2020-01-22 2020-06-05 阿里巴巴集团控股有限公司 Instance processing and calling method, device, system and storage medium
WO2021136074A1 (en) * 2019-12-31 2021-07-08 华为技术有限公司 Virtual network function deployment method, apparatus and system
CN114040021A (en) * 2021-11-05 2022-02-11 光大科技有限公司 Development processing method and device for application program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105577779A (en) * 2015-12-21 2016-05-11 用友网络科技股份有限公司 Method and system for containerized deployment of large enterprise private cloud
US20160226913A1 (en) * 2015-02-04 2016-08-04 Kapil Sood Technologies for scalable security architecture of virtualized networks
CN106254154A (en) * 2016-09-19 2016-12-21 杭州华三通信技术有限公司 A kind of resource share method and device
CN107404485A (en) * 2017-08-02 2017-11-28 北京天翔睿翼科技有限公司 A kind of self-validation cloud connection method and its system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101794226B (en) * 2010-03-08 2012-11-07 山东大学 Service software construction method and system adapting to multiple business abstraction levels
US8799898B2 (en) * 2011-05-31 2014-08-05 Adobe Systems Incorporated Methods and apparatus for binding applications to a cloud computing environment
CN102333115A (en) * 2011-09-01 2012-01-25 杭州湾云计算技术有限公司 Method and device for transforming existing Web application into SaaS multi-tenant application
CN103561310B (en) * 2013-10-23 2017-01-18 深圳创维数字技术有限公司 Method, device and system for data processing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160226913A1 (en) * 2015-02-04 2016-08-04 Kapil Sood Technologies for scalable security architecture of virtualized networks
CN105577779A (en) * 2015-12-21 2016-05-11 用友网络科技股份有限公司 Method and system for containerized deployment of large enterprise private cloud
CN106254154A (en) * 2016-09-19 2016-12-21 杭州华三通信技术有限公司 A kind of resource share method and device
CN107404485A (en) * 2017-08-02 2017-11-28 北京天翔睿翼科技有限公司 A kind of self-validation cloud connection method and its system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MOHAMMAD ABU-LEBDEH,SAMI YANGUI: "A Virtual Network PaaS for 3GPP 4G and Beyond Core Network Services", 《5TH IEEE INTERNATIONAL CONFERENCE ON CLOUD NETWORKING》 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021136074A1 (en) * 2019-12-31 2021-07-08 华为技术有限公司 Virtual network function deployment method, apparatus and system
CN113127138A (en) * 2019-12-31 2021-07-16 西安华为技术有限公司 Method, device and system for deploying virtualized network function
CN113127138B (en) * 2019-12-31 2024-04-16 西安华为技术有限公司 Virtualized network function deployment method, device and system
CN111240868A (en) * 2020-01-22 2020-06-05 阿里巴巴集团控股有限公司 Instance processing and calling method, device, system and storage medium
CN111240868B (en) * 2020-01-22 2024-04-02 阿里巴巴集团控股有限公司 Instance processing and calling method, device, system and storage medium
CN114040021A (en) * 2021-11-05 2022-02-11 光大科技有限公司 Development processing method and device for application program
CN114040021B (en) * 2021-11-05 2024-01-30 光大科技有限公司 Development processing method and device for application program

Also Published As

Publication number Publication date
CN109905258B (en) 2020-11-17
WO2019109948A1 (en) 2019-06-13

Similar Documents

Publication Publication Date Title
CN105812171B (en) A kind of the network function VNF control method and equipment of virtualization
CN110569101B (en) Method and device for managing container service
WO2018024059A1 (en) Method and device for service deployment in virtualized network
CN113641457B (en) Container creation method, device, apparatus, medium, and program product
CN104123151B (en) The plug-in management method of application program, device and mobile terminal in mobile terminal
CN106375101B (en) A kind of life cycle management method and device
WO2020135799A1 (en) Vnf service instantiation method and device
WO2016117697A1 (en) Method, device, and program for management and orchestration of network functions virtualization
CN110166407A (en) QoS flow processing method, equipment and system
WO2018072612A1 (en) Method for managing slice instance and apparatus
CN110032413A (en) A kind of desktop virtualization method, relevant device and computer storage medium
WO2019086011A1 (en) Method and device for managing services in network function virtualization architecture
CN111949364A (en) Deployment method of containerized VNF and related equipment
WO2019047821A1 (en) Service routing method, device and storage medium
WO2020103925A1 (en) Method and apparatus for deploying containerization virtualized network function
CN109905258A (en) Management method, device and the storage medium of PaaS
CN109995552B (en) VNF service instantiation method and device
CN109428764B (en) Virtual network function instantiation method
CN108347343A (en) A kind of policy management method, device and system
CN108399331A (en) Application process trial method and system
CN108628660A (en) A kind of virtual machine expands capacity reduction method and virtual management equipment
WO2018184504A1 (en) Virtual resource allocation method, nfvo, and system
CN108595331A (en) Test method, medium, device and the computing device of asynchronous interface
CN109347661A (en) The instantiation method and device of consumer VNF
CN109347716A (en) The instantiation method and device of consumer VNF

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant