WO2021238718A1 - 一种响应方法、确定方法、装置、设备及介质 - Google Patents

一种响应方法、确定方法、装置、设备及介质 Download PDF

Info

Publication number
WO2021238718A1
WO2021238718A1 PCT/CN2021/094315 CN2021094315W WO2021238718A1 WO 2021238718 A1 WO2021238718 A1 WO 2021238718A1 CN 2021094315 W CN2021094315 W CN 2021094315W WO 2021238718 A1 WO2021238718 A1 WO 2021238718A1
Authority
WO
WIPO (PCT)
Prior art keywords
nsd
management
deployment
network service
operation request
Prior art date
Application number
PCT/CN2021/094315
Other languages
English (en)
French (fr)
Other versions
WO2021238718A9 (zh
Inventor
陈礼娟
潘加强
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021238718A1 publication Critical patent/WO2021238718A1/zh
Publication of WO2021238718A9 publication Critical patent/WO2021238718A9/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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/14—Network analysis or design
    • 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

Definitions

  • This application relates to the field of communication technology, for example, to a response method, determination method, device, device, and medium.
  • NSD Network Service Descriptor
  • This application provides a response method, determination method, device, equipment, and medium that effectively respond to operation management requests based on NSD.
  • an embodiment of the present application provides a response method applied to a management node, including:
  • the response result of the management operation request is associated with the deployment restriction condition included in the network service descriptor NSD.
  • the embodiments of the present application provide a determination method applied to a network service designer, including:
  • the NSD is determined, and the determination operation of the NSD is associated with the deployment restriction condition.
  • an embodiment of the present application provides a response device, which is configured in a management node, and includes:
  • the response module is configured to respond to the management operation request, and the response result of the management operation request is associated with the deployment restriction condition included in the network service descriptor NSD.
  • an embodiment of the present application provides a determining device, which is configured in a network service designer, and includes:
  • the first determining module is set to determine the deployment restriction conditions
  • the second determining module is configured to determine the NSD, and the determination operation of the NSD is associated with the deployment restriction condition.
  • an embodiment of the present application provides a device, including:
  • One or more processors are One or more processors;
  • Storage device for storing one or more programs
  • the one or more processors implement any method in the embodiments of the present application.
  • an embodiment of the present application provides a storage medium that stores a computer program, and the computer program implements any one of the methods in the embodiments of the present application when the computer program is executed by a processor.
  • FIG. 1 is a schematic flowchart of a response method provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a determining method provided by an embodiment of the present application
  • Figure 2a is a schematic diagram of a scenario for determining NSD provided by an embodiment of the present application.
  • Figure 2b is a schematic diagram of a management operation request processing flow provided by an embodiment of the present application.
  • FIG. 2c is a schematic diagram of another management operation request processing flow provided by an embodiment of the present application.
  • FIG. 2d is a schematic diagram of another management operation request processing flow provided by an embodiment of the present application.
  • FIG. 2e is a schematic diagram of yet another management operation request processing flow diagram provided by an embodiment of the present application.
  • FIG. 2f is a schematic diagram of yet another management operation request processing flow diagram provided by an embodiment of the present application.
  • Figure 2g is a schematic diagram of yet another management operation request processing flow diagram provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a response device provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a determining device provided by an embodiment of the present application.
  • Fig. 5 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • FIG. 1 is a schematic flow chart of a response method provided by an embodiment of the present application.
  • the method may be suitable for processing a management operation request.
  • the method may be executed by a response device, and the device may be executed by software. And/or hardware implementation, and integrated on the device.
  • the device can be a management node.
  • the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) specification describes that the Network Service Descriptor (NSD) can be used to deploy network services, and the European Telecommunications Sdandards Institute (ETSI) network functions
  • NSD Network Service Descriptor
  • ETSI European Telecommunications Sdandards Institute
  • NFV Network Functions Virtualisation
  • the complex actual network conditions result in different divisions of management domains or management roles in the operation and management network.
  • each network element (Managed Element, ME) belongs to a specific domain and is managed by the management system of the domain. After the virtualization technology is adopted, the structure of sub-domain and sub-authority management is also applicable.
  • the physical network function (PNF) and virtualized network function (Virtualize Network Function, VNF) of the fourth generation mobile communication technology (4G) technology are combined into a combination that is only applicable to the 4G field.
  • the NSD used to describe the constituent elements required to deploy an NS instance and the topological relationship between the constituent elements also has restrictions on the scope of application. For example, the NSD used to deploy 4G NS needs to be restricted to be operated by managers in the 4G field; The NSD deployed by A can only be used in area A and cannot be used in area B deployment.
  • the response method provided by this application includes the following steps:
  • Management operations may be NSD management operations, and NSD management operations may refer to NSD management operations in the ETSI NFV specification.
  • the management operation request may be NSD management operation request information.
  • this application can respond to it to determine whether to perform the corresponding management operation.
  • the response result of the management operation request is associated with the deployment restriction condition included in the network service descriptor NSD.
  • this step can respond to the management operation request.
  • this step can determine the response result of the management operation request based on the deployment restriction conditions included in the NSD.
  • the deployment restriction conditions can limit the restriction conditions of using NSD to process management operation requests, such as the restriction conditions of using NSD to deploy NS.
  • This application may determine the response result of the management operation request based on the deployment restriction conditions included in the NSD, and the response result may include the NSD management operation execution and rejection operation.
  • the management operation request may include information matching the deployment restriction condition, and the specific content of the information may be determined based on the specific content of the deployment restriction condition.
  • the management operation request may include the usage authority corresponding to the management operation request. This application can determine whether the usage right meets the deployment restriction conditions to determine the response result.
  • the management operation request may include the usage domain corresponding to the management operation request. This application can determine whether the use domain meets the deployment restriction conditions to determine the response result.
  • the response method provided in this application first obtains a management operation request; then responds to the management operation request, and the response result of the management operation request is associated with the deployment restriction conditions included in the network service descriptor NSD. This method can effectively respond to management operation requests based on NSD.
  • the deployment restriction conditions include one or more of the following: use permission restriction conditions; use domain range restriction conditions.
  • restriction conditions of the usage rights can be regarded as restriction conditions determined based on the usage rights.
  • restriction conditions determined based on the usage rights can be regarded as restriction conditions determined based on the use domain range.
  • the usage authority restriction conditions are determined by one or more of the following methods: a list of users allowed to use; a list of users not allowed to use; and determining the restriction conditions of user rights.
  • the list of allowed users may include users bound to the NSD, and the management node may execute the management operation request initiated by the user.
  • the list of users not allowed to use may include users bound to the NSD, and the management node may refuse to execute the management operation request initiated by the user.
  • the usage authority restriction condition can be a list of allowed users or a list of disallowed users, and the restriction condition of usage authority can be limited based on each list.
  • the restriction condition of the use right item can also be the restriction condition for determining the user authority.
  • the restriction condition for determining the user authority is not specifically limited, and can be set according to the actual situation.
  • the use domain range restriction condition is determined by one or more of the following use domain ranges: geographic range; technical field range.
  • the restriction conditions of the scope of use can be defined by the scope of the region or the scope of the technical field.
  • the geographical scope can be regarded as the scope based on the division of geographical space.
  • the scope of the technical field can be regarded as the scope based on the division of the technical field.
  • the responding to the management operation request includes:
  • the specific authentication method may be determined based on the specific content included in the deployment restriction condition.
  • Such as authority authentication based on the user's use authority and use domain.
  • the authority authentication result may include authentication passed and authentication failed. If the authentication is passed, the management operation request can be executed. If the authentication fails, the management operation request can be rejected.
  • the management node is network function virtualization management and orchestration.
  • FIG. 2 is a schematic flowchart of a determination method provided in an embodiment of the present application.
  • the method may be suitable for determining the NSD used to respond to a management operation request Condition. This method can be executed by the determining device provided in the present application, and the device can be implemented by software and/or hardware and integrated on the network service designer to determine the NSD.
  • this application provides a determination method, which includes the following steps:
  • the deployment restriction conditions can be determined automatically by the network service designer from the management node, or through interaction with the designer.
  • the specific content of the deployment restrictions is not limited, and can be set according to actual needs.
  • S220 Determine an NSD, and the determination operation of the NSD is associated with the deployment restriction condition.
  • this step can determine the NSD based on the deployment constraints. Determining the association between the operation and the deployment restriction can be considered as determining the NSD based on the deployment restriction.
  • the determined NSD may include deployment restriction conditions to respond to management operation requests based on the deployment restriction conditions.
  • the NSD in this application it can be determined based on the networking information and network service function requirements in related technologies, and the deployment restriction conditions described in this application. Compared with the NSD of related technologies, the determined NSD includes deployment restrictions.
  • This application provides a method for determining, first determining the deployment restriction condition; then determining the NSD, and the determining operation of the NSD is associated with the deployment restriction condition. Using this method, the NSD used to respond to the management operation request is determined, and the response to the management operation request is effectively performed based on the determined NSD.
  • the network service designer is integrated in the management node; or is an independent functional module; or integrated in the operation support system or business support system.
  • the NSD includes deployment restriction conditions, and the deployment restriction conditions are used to authenticate users.
  • the deployment restriction conditions can be used to authenticate the user through the corresponding information of the user corresponding to the management operation request, such as the use authority and the use domain.
  • the nested NSDs in the determined NSD are filtered and determined based on the deployment restriction conditions of the target NSD and the design requirements of the determined NSD, and the target NSD is filtered based on filtering conditions other than the deployment restriction conditions.
  • the NSD obtained.
  • the filter conditions other than the deployment restriction conditions may be filter conditions in related technologies and subsequent new filter conditions.
  • This application can perform the initial filtering based on the filtering conditions other than the deployment restriction conditions, and then filter again based on the deployment restriction conditions of the target NSD to obtain the nested NSD.
  • matching can be performed based on the design requirements of the determined NSD and the deployment restriction conditions of the target NSD, and the target NSD that meets the design requirements of the determined NSD is selected as the nested NSD.
  • the method further includes:
  • the NSD is transmitted to the management node.
  • this application can transmit the NSD to the designer, and the designer uploads the NSD to the management node through the operation support system or business support system, so that the management node can respond to the management operation request.
  • this application can transmit the NSD to the designer, from the designer to the user who meets the deployment constraints, and then the user uploads the NSD to the operation support system or business support system
  • the management node is used for the management node to respond to management operation requests.
  • a response method provided by this application can be considered as a network service design and management method.
  • network operators Before virtualization technology is adopted, network operators’ networks are deployed through dedicated hardware devices. The launch of network services usually requires the addition of new equipment. Increasing network capacity and service types have led to increasing energy consumption, capital investment challenges, and the lack of necessary skills to design, integrate, and operate increasingly complex hardware devices.
  • NFV is a software processing technology that uses general-purpose hardware and virtualization technology to carry other functions, and aims to reduce the cost of expensive network equipment.
  • NFV makes network equipment functions no longer depend on dedicated hardware, resources can be fully and flexibly shared, rapid development and deployment of new services, and automatic deployment, elastic scaling, and fault isolation based on actual business needs And self-healing etc.
  • the function carried by the physical device after virtualization is called VNF, and the traditional device implemented without virtualization is called PNF.
  • the network service ⁇ communication service NS defined by the 3GPP standard group is provided based on the network service instances and network service parameters defined by the ETSI NFV standard group. The latter is instantiated based on the NSD and resource configuration parameters defined by the ETSI NFV standard group.
  • NSD The network service instance
  • VNFD Virtualized Network Function Descriptors
  • PNFD Physical Network Function Descriptor
  • Nested Network Service Descriptor nested NSD
  • VL Virtualized Link
  • VNF and PNF In addition to the long-term coexistence of VNF and PNF, from the perspective of management, there are long-term coexistence of multiple technologies in the network environment of operators, such as the coexistence of 3G, 4G, and 5G technologies; ordinary telecommunications personal user networks, enterprise private networks, and the Internet of Things , Coexistence of the Internet of Vehicles.
  • the same network function is provided by different equipment vendors in different areas PNF, VNF, for example, the function provided by PNF in area A may be provided by VNF in area B, so equipment in different areas
  • the topological relationship of the combination of PNF and VNF of the supplier into NS will be different, and it needs to be managed and used separately.
  • the complex actual network conditions result in different management domain divisions or management role divisions when operating and managing the network.
  • each network element belongs to a specific domain and is managed by the management system of the domain. After the virtualization technology is adopted, the structure of sub-domain and sub-authority management is also applicable.
  • PNF and VNF that realize 4G technology are combined into NS that is only applicable to the 4G field; PNF and VNF provided by supplier A are combined into NS that is only applicable to the support area allocated to supplier A by the operator.
  • the NSD used to describe the constituent elements required to deploy an NS instance and the topological relationship between the constituent elements also has restrictions on the scope of application.
  • the NSD used to deploy 4G NS needs to be restricted to be operated by managers in the 4G field; The NSD deployed by A cannot be used for deployment in area B.
  • this application provides a method of NSD management, that is, a method of determining NSD, which solves the management problem of NSD by adding deployment restrictions to the NSD.
  • the deployment restriction conditions refer to the restriction conditions carried in the NSD indicating that the NSD is used to deploy the NS, including but not limited to the following three categories:
  • the restriction of use authority it indicates that the NSD can be used by users with designated authority in the operator management system.
  • the usage authority may be a list of allowed users, or may be a restriction condition for judging user authority.
  • the scope of use domain can be a geographical range, a technical field range (such as 3G, 4G, 5G), or a geographical range combined with a technical field range.
  • this information indicates that the NSD can be used by users who meet the specified authority in the designated use domain in the operator's management system.
  • the user is not limited to a specific person, but may also be a tenant or a management role defined in the operator management system.
  • NSD Life Cycle Management
  • LCM Life Cycle Management
  • Figure 2a is a schematic diagram of a scenario for determining NSD provided by an embodiment of the present application. See Figure 2a.
  • the network service designer In the NSD design phase, the network service designer generates NSD based on the input networking information, network service function requirements, and deployment constraints. The deployment restrictions contained in it indicate that the restrictions on the NSD can be used.
  • the NSD In the use phase, the NSD is uploaded to the second management node, that is, the management node. Based on the deployment restrictions carried in the NSD, it is bound to the users who can use it, and only the bound users can initiate the LCM operation of the NSD. .
  • the NSD in this application can be determined based on networking information and network service function requirements in related technologies and newly added deployment constraints.
  • the determined NSD includes the NSD and deployment constraints defined in related technologies. Designing a network service is to realize a specific function, so it is necessary to determine the NSD based on the function requirements of the network service.
  • Networking information may include network equipment and the logical relationship between the equipment.
  • the first management node may be an operation support system (OSS) or a business support system (BSS).
  • the second management node is network function virtualization management and orchestration (Network Functions Virtualisation Management and Orchestration, NFV-MANO).
  • the network service designer may be a function module of the first management node, may be a function module of the second management node, or may be an independent function module.
  • the NSD is determined according to the usage authority restriction.
  • Figure 2b is a schematic diagram of a management operation request processing flow provided by an embodiment of the present application. Referring to Figure 2b, the flow includes determining the NSD and responding to the management operation request based on the NSD.
  • NSD can only be used by users with limited permissions.
  • the designer In the network service design stage, the designer first understands the network service function requirements and the operating environment information to deploy the network service, interacts with the network service designer, and generates NSD.
  • the deployment restriction carried in the NSD is set as the usage authority (it can be a list of allowed users, or it can be a restriction condition for judging user rights, which is set by different operators).
  • the NSD is uploaded to NFV-MANO, and is bound to a designated user (in this embodiment, the user is the designer) according to deployment restrictions. Later, only the initiator who meets the restriction conditions can use the NSD to perform life cycle management operations such as instantiation.
  • This embodiment is applicable but not limited to scenarios where operators develop new services.
  • the network service designer conducts a pre-test and uploads the NSD to NFV-MANO.
  • the NSD is invisible to other management roles in the system, and only users who meet the limited conditions (such as the designer in this example) can use the NSD to deploy an NS instance to continue the work related to new business development.
  • the deployment restrictions of NSD are updated to the user permissions specified by the operator.
  • the management operation request processing flow may include the following steps:
  • the network service designer obtains the data needed to generate the NSD.
  • the network service designer can be deployed as a component module of OSS ⁇ BSS, and the network device information and status saved by OSS ⁇ BSS are visible to the network service designer.
  • the designer initiates the NSD generation process to the network service designer; the network service designer obtains network device information from OSS ⁇ BSS; the designer interacts with the network service designer to confirm the parameters required for generating NSD, and generate the required parameters for NSD (ie generate NSD required data) needs to include network service functions, networking information, that is, the logical relationship between the network equipment (PNFD, VNFD) used, and the combination of network equipment, as well as the deployment restrictions for using NSD.
  • PNFD network equipment
  • VNFD network equipment
  • This step may include steps 01a, 01b, and 01c.
  • the network service designer generates an NSD based on the received data.
  • the NSD complies with the specifications defined by ETSI NFV, and on this basis, the deployment restriction conditions are set as the authority of the user (designer) according to the requirements of the designer.
  • the designer is not limited to a specific person, but may be a tenant or a management role defined in the management system.
  • the web service designer sends the generated NSD to the designer.
  • NSD Network-Specific Virtualization Extensions
  • NFV-MANO Network-Specific Virtualization Extensions
  • the deployment restrictions carried in the NSD serve as the basis for determining the binding of the NSD to the user.
  • NSD management operations can refer to NSD management operations defined in the ETSI NFV specification.
  • the NSD management operation is executed.
  • the designer/user authority is authenticated, the operation is valid, and NFV-MANO executes the received operation request.
  • a user without permission initiates a NSD management operation request.
  • the operation initiator is not a user bound by NSD, and it is determined to be an illegal operation, and NFV-MANO refuses to perform the operation request.
  • the NSD is determined according to the use domain range.
  • Fig. 2c is a schematic diagram of another management operation request processing flow provided by an embodiment of the present application.
  • NSD can only be used in a limited domain, and the limited domain can be determined based on the applicable scope restriction conditions, which can refer to the geographical scope (such as the deployment area designated by the operator to the supplier) or the technical field scope (such as 3G technology field), it can also be a combination of geographic scope and technical scope (such as in an operator's network, different technical fields in the same geographic scope are provided by different equipment vendors VNF and PNF, then the corresponding NSD can only be used in this limited area The limited technical field).
  • the applicable scope restriction conditions can refer to the geographical scope (such as the deployment area designated by the operator to the supplier) or the technical field scope (such as 3G technology field), it can also be a combination of geographic scope and technical scope (such as in an operator's network, different technical fields in the same geographic scope are provided by different equipment vendors VNF and PNF, then the corresponding N
  • the designer understands the specific requirements of the network service (ie, the network service function requirements) and the operating environment information to deploy the network service, interacts with the network service designer, and generates the NSD.
  • the deployment restriction carried in the NSD is set as the use domain that the NSD can use.
  • the NSD is uploaded to the NFV-MANO system, and all users of the use domain in the operator management system can initiate management operations on the NSD, such as instantiating an NS instance using the NSD.
  • This embodiment is applicable but not limited to the scenario where the designated NSD carries the use domain that allows the use of the NSD, and is also applicable to the designated use domain that is not allowed to use the NSD deployment.
  • the network service designer can be deployed as a component module of OSS ⁇ BSS, and the network device information and status saved by OSS ⁇ BSS are visible to the network service designer.
  • the designer initiates the NSD generation process to the network service designer; the network service designer obtains network device information from OSS ⁇ BSS; the designer interacts with the network service designer to confirm the parameters required for generating NSD, and generate the required parameters for NSD (ie generate NSD required data) needs to include network service functions, networking information, that is, the logical relationship between the network equipment (PNFD, VNFD) used, and the combination of network equipment, as well as the deployment restrictions for using NSD.
  • PNFD network equipment
  • VNFD network equipment
  • This step can include 1a, 1b, and 1c.
  • the NSD follows the specifications defined by ETSI NFV, and on this basis, the deployment restriction conditions are set to the use domain that can use the NSD according to the designer's requirements, which means that all uses of the use domain in the operator's network convinced can use this NSD.
  • the user is not limited to a specific person, but may be a tenant or a management role defined in the management system.
  • the network service designer After the network service designer generates the NSD, it transmits the NSD to the designer, and the designer transmits it to the users in the usage domain.
  • the user uploads the NSD to NFV-MANO through the upload interface between OSS ⁇ BSS and NFV-MANO.
  • the deployment restriction conditions carried in the NSD are used as a basis for determining the binding of the NSD to the user.
  • the users are all users in the use domain defined by the deployment restriction conditions.
  • the user is not limited to a specific person, but may be a tenant or a management role defined in the management system.
  • the user in the using domain initiates a management operation request to the NSD, such as an LCM request.
  • the user is a legal user of NFV-MANO, and the target of the operation is the NSD bound to this user, and NFV-MANO executes the received operation request.
  • the NSD is determined according to the use domain and the use authority.
  • Figure 2d is a schematic diagram of another management operation request processing flow provided by an embodiment of the present application.
  • NSD can only be used by users with specific permissions in a limited domain.
  • the designer understands the specific requirements of the network service and the information about the operating environment in which the network service is to be deployed, interacts with the network service designer, and generates NSD.
  • the NSD can only be used by a limited management domain user or a specific role in the management domain, and the deployment restrictions carried in the NSD are set to "use domain range" + "use authority".
  • the use phase the NSD is uploaded to the NFV-MANO system, and the user of the use domain in the operator management system can initiate management operations on the NSD, such as instantiating an NS instance using the NSD.
  • This embodiment is applicable but not limited to designing specific service NSD usage scenarios in a specific domain, such as designing an enterprise private network service in the 4G technology field or an IP Multimedia Subsystem (IMS) service in the 3G technology field for an operator , NSD designers design NSD, the NSD can only be used by users (4G enterprise network operation and maintenance personnel or 3G IMS network operation and maintenance personnel) with specific permissions in the corresponding technical field, such as 2G network operation and maintenance personnel or home Internet operations Maintenance personnel cannot operate the NSD.
  • IMS IP Multimedia Subsystem
  • the process includes the following steps:
  • the network service designer can be deployed as a component module of OSS ⁇ BSS, and the network device information and status saved by OSS ⁇ BSS are visible to the network service designer.
  • the designer initiates the NSD generation process to the network service designer; the network service designer obtains the network device information from OSS ⁇ BSS; the designer interacts with the network service designer to confirm the parameters required to generate the NSD, and to generate the required parameters of the NSD (ie generate NSD required data) needs to include network service functions, networking information, that is, the network equipment used (PNFD, VNFD, nested NSD) and the logical relationship between the network equipment, and the deployment restrictions for using NSD.
  • PNFD network equipment used
  • VNFD nested NSD
  • This step includes 10a, 10b, and 10c.
  • the NSD complies with the specifications defined by ETSI NFV, and on this basis, according to the designer’s requirements, the deployment restriction conditions are set to "use domain range" combined with "use authority”, which means that this NSD is managed by the operator in the system It is used by users who meet the specified authority in the designated use domain.
  • the user is not limited to a specific person, but may be a tenant or a management role defined in the management system.
  • the designer gets the generated NSD and transfers it to the user, that is, the user who uses the limited authority in the domain.
  • the user uploads the NSD to NFV-MANO through the upload interface between OSS ⁇ BSS and NFV-MANO.
  • the deployment restriction condition information carried in the NSD serves as a basis for determining the binding of the NSD to the user.
  • the user is a user who meets the restriction condition.
  • NSD management operation refers to the NSD management operation defined in the ETSI NFV specification.
  • the user is a legal user of NFV-MANO, and the target NSD of the operation is the resource bound to the user, and NFV-MANO executes the received operation request.
  • a user without permission initiates a management operation request to the NSD.
  • the operation initiator is not a user bound by NSD, and it is determined to be an illegal operation, and NFV-MANO refuses to perform the operation request.
  • FIG. 2e is a schematic diagram of another management operation request processing flow diagram provided by an embodiment of the present application.
  • the designer When the designer is designing an NSD, it needs to include other NSD scenarios, and check whether the included NSD can be used or meet the functional requirements
  • the NSDs that can be used are filtered out according to the deployment restrictions carried by the NSD.
  • This embodiment is suitable for designing scenarios that include nested NSDs.
  • the network service B of a virtual operator needs to provide new services based on the network service A of the operator and other VNF ⁇ PNFs.
  • the NSD A As a nested NSD member of NSD B.
  • it is necessary to check whether it can be included and used by NSD B according to the deployment restrictions of NSD A.
  • the generated NSD B also needs to set deployment restrictions.
  • NSD A nested in NSD B comply with the restrictions on the use of NSD B. It does not affect the deployment restrictions when using NSD A directly, nor does it affect the deployment restrictions when NSD A is used as a nested NSD of another NSD C.
  • the process includes the following steps:
  • This step includes the following operations:
  • the designer initiates the NSD generation process to the web service designer.
  • Obtain network device information that is, the network service designer obtains the network device information from OSS ⁇ BSS, and forwards the designer's user information to OSS ⁇ BSS.
  • the user information can be used to determine the user's use authority.
  • OSS ⁇ BSS interacts with the network service designer to perform permission matching, and filter out the available NSD according to the designer’s use permission and/or design requirements of the design target NSD (ie the determined NSD design requirements) NSD used.
  • the designer's use authority is the super user authority of the operator management system, and all NSDs are available for use;
  • the designer's use authority is the user authority of the specified domain in the operator management system, and all NSDs of the domain are filtered for use (if there is 4G management domain user authority, the domain used in the deployment restriction conditions is filtered out as the 4G technical field All NSD);
  • NSD design requirement
  • the design target NSD needs to include the 5G data service NSD, and the data service NSD whose use domain is the 5G technical field in the deployment restriction conditions is filtered out for use, that is, the nested NSD that can be used is determined based on the deployment restriction conditions.
  • the design target NSD needs to be restricted to be deployed in the area specified by the operator, and then all NSDs in the area that are used in the deployment restriction are filtered out for use, that is, the nested NSD is filtered out based on the deployment restriction.
  • the NSD obtained by the initial filtering can be the target NSD.
  • the NSD filtered again based on the deployment restriction conditions of the target NSD can be a nested NSD.
  • the network service designer obtains network equipment information, including which network functions are provided by PNF, which network functions are provided by VNF, and which NSDs are already available.
  • NSD generates parameter interaction
  • the designer interacts with the network service designer to confirm the parameters required to generate NSD, and the parameters required to generate NSD (that is, the data required to generate NSD) need to include network service functions, networking information, and network equipment (PNFD, VNFD, nested NSD) And the combinational logical relationship between network devices, and the deployment constraints of using NSD.
  • NSD is generated.
  • NSD follows the specifications defined by ETSI NFV, and on this basis, sets deployment restrictions according to the designer's requirements.
  • the setting of the deployment restriction conditions is to set the newly generated NSD, and the conditions that can be set are the same as those in the first, second, and third embodiments, and the division into multiple embodiments will not be repeated.
  • the web service designer transmits the generated NSD to the designer.
  • the user uploads the NSD to NFV-MANO through the upload interface between OSS ⁇ BSS and NFV-MANO.
  • the deployment restrictions carried in the NSD serve as the basis for determining the binding of the NSD to the user.
  • the deployment restriction conditions of the nested NSD contained in the NSD do not affect the determination of the NSD binding operation.
  • the user in the user domain initiates a management operation request to the NSD.
  • the NSD management operation is executed.
  • the user is a legal user of NFV-MANO, and the target NSD of the operation is the resource bound to the user, and NFV-MANO executes the received operation request.
  • FIG. 2f is a schematic diagram of another management operation request processing flow diagram provided by an embodiment of this application.
  • the network service designer is an independent functional module and does not directly interact with OSS ⁇ BSS and NFV-MANO.
  • the designer is interacting with the network service designer Get the data needed to generate NSD before interaction.
  • This embodiment is applicable but not limited to offline design NSD usage scenarios.
  • the designer provides VNFs that implement network services according to design requirements, and then uses the combination of VNFs to generate NSD, which is provided to the operator's network; or the designer adopts In other ways, the network element information and the combination logic between network elements are obtained from the operator, and NSD is designed based on this information and provided to the operator's network.
  • the process includes the following steps:
  • the designer Before designing a specific network service, the designer obtains the functional requirements and network equipment information of the network service from the operator or network service provider, such as which network functions are provided by the PNF, which network services are provided by the VNF, and whether they are based on the existing network Services provide new network services, etc. Then the designer sends the NSD generation request to the network service designer, carrying NSD generation parameters (that is, the parameters required to generate NSD).
  • the NSD generation parameters need to include network service functions, networking information, that is, the network equipment used (PNFD, VNFD, nested). NSD) and the logical combination of network devices, as well as the deployment constraints of using NSD.
  • NSD is generated.
  • the designer gets the generated NSD and transmits it to users who meet the restriction conditions.
  • the user uploads the NSD to NFV-MANO through the upload interface between OSS ⁇ BSS and NFV-MANO.
  • the deployment restrictions carried in the NSD serve as the basis for determining the binding of the NSD to the user.
  • the user that is, the user who meets the restriction conditions, initiates a management operation request to the NSD.
  • the NSD management operation is executed.
  • the user is authenticated, the operation is valid, and NFV-MANO executes the received operation request.
  • FIG. 2g is a schematic diagram of yet another management operation request processing flow provided by an embodiment of the present application.
  • the network service designer is deployed as a functional module of NFV-MANO.
  • the uploaded PNFD, VNFD, and NSD information saved by NFV-MANO is visible to the network service designer.
  • the process includes the following steps:
  • the designer initiates the NSD generation process to the network service designer; the network service designer obtains network device information from NFV-MANO, and filters out the available NSDs according to the designer’s authority to match the deployment restrictions in the uploaded NSD; the designer and The network service designer interacts to confirm the parameters required to generate NSD.
  • the generated NSD parameters need to include network service functions, networking information, that is, the network equipment used (PNFD, VNFD, nested NSD) and the logical relationship between the network equipment, and the use NSD deployment restrictions.
  • the designer has the super user authority of the operator management system, then all NSDs are available for use;
  • the designer has the user authority of the specified domain in the operator management system, then all NSDs of the domain are filtered for use (if the designer has the user authority of the 4G management domain, all NSDs whose domains are 4G technology fields in the deployment restriction conditions are filtered out) ;
  • the design target NSD needs to include the NSD with the specified function, and the NSD that meets the conditions is filtered according to the function for use (if voice service NSD is required, all voice service NSDs are filtered);
  • the design target NSD needs to include the NSD with the specified function in the specified technical field, and then filter the NSD with the specified function in the technical field for use (if 5G data service NSD is required, filter out the data service NSD with the 5G technical field used in the deployment restriction conditions );
  • the design target NSD needs to be restricted to be deployed in the area specified by the operator, and then all NSDs in the deployment restriction that are used in the area are filtered out for use.
  • NSD is generated.
  • NSD follows the specifications defined by ETSI NFV, and on this basis, sets deployment restrictions according to the designer's requirements.
  • the set deployment restriction conditions are the same as those in the first, second, and third embodiments, and will not be split into multiple embodiments repeatedly.
  • the designer gets the generated NSD and transmits it to users who meet the defined conditions.
  • the user uploads the NSD to NFV-MANO through the upload interface between OSS ⁇ BSS and NFV-MANO.
  • the deployment restrictions carried in the NSD serve as the basis for determining the binding of the NSD to the user.
  • the NSD management operation is executed.
  • the user is authenticated, the operation is valid, and NFV-MANO executes the received operation request.
  • FIG. 3 is a schematic structural diagram of a response device provided in an embodiment of the application.
  • the response device can be configured on a management node, as shown in FIG. 3.
  • the response device in the embodiment of the present application includes: an acquisition module 31, configured to acquire a management operation request; a response module 32, configured to respond to the management operation request, the response result of the management operation request and the network service descriptor NSD
  • the included deployment constraints are associated.
  • the response device provided in this embodiment is used to implement the response method of the embodiment of the present application.
  • the implementation principle and technical effect of the response device provided in this embodiment are similar to the response method of the embodiment of the present application, and will not be repeated here.
  • the deployment restriction conditions include one or more of the following: use permission restriction conditions; use domain range restriction conditions.
  • the usage authority restriction conditions are determined by one or more of the following methods: a list of users allowed to use; a list of users not allowed to use; and determining the restriction conditions of user rights.
  • the use domain range restriction condition is determined by one or more of the following use domain ranges: geographic range; technical field range.
  • the response module 32 is specifically configured to:
  • the management node is network function virtualization management and orchestration.
  • FIG. 4 is a schematic structural diagram of a determining device provided in an embodiment of the present application.
  • the device can be configured in a network service designer, and the device includes :
  • the first determining module 41 is configured to determine the deployment restriction condition;
  • the second determining module 42 is configured to determine the NSD, and the determination operation of the NSD is associated with the deployment restriction condition.
  • the determining device provided in this embodiment is used to implement the determining method in the embodiment of the present application.
  • the implementation principle and technical effect of the determining device provided in this embodiment are similar to the determining method in the embodiment of the present application, and will not be repeated here.
  • the network service designer is integrated in the management node; or is an independent functional module; or integrated in the operation support system or business support system.
  • the NSD includes deployment restriction conditions, and the deployment restriction conditions are used to authenticate users.
  • the nested NSDs in the determined NSD are filtered and determined based on the deployment restriction conditions of the target NSD and the design requirements of the determined NSD, and the target NSD is filtered based on filtering conditions other than the deployment restriction conditions.
  • the NSD obtained.
  • the device further includes: a transmission module configured to:
  • the NSD is transmitted to the management node.
  • FIG. 5 is a schematic structural diagram of a device provided in an embodiment of the present application.
  • the device provided in this application includes one or more processors 51 and a storage device 52; the processors 51 in the device may be one or more.
  • one processor 51 is taken as an example; the storage device 52 is used for storage One or more programs; the one or more programs are executed by the one or more processors 51, so that the one or more processors 51 implement the methods described in the embodiments of the present application, such as response methods And determining the method.
  • the equipment also includes: a communication device 53, an input device 54 and an output device 55.
  • the processor 51, the storage device 52, the communication device 53, the input device 54 and the output device 55 in the device may be connected by a bus or other methods.
  • the connection by a bus is taken as an example.
  • the input device 54 can be used to receive input digital or character information, and generate key signal input related to user settings and function control of the device.
  • the output device 55 may include a display device such as a display screen.
  • the communication device 53 may include a receiver and a transmitter.
  • the communication device 53 is configured to perform information transceiving and communication under the control of the processor 51.
  • Information includes but is not limited to NSD.
  • the storage device 52 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the methods described in the embodiments of the present application (for example, the acquisition module 31 in the response device). And the response module 32; for another example, the first determining module 41 and the second determining module 42 in the determining device).
  • the storage device 52 may include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the storage device 52 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the storage device 52 may further include a memory provided remotely with respect to the processor 51, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the embodiment of the present application further provides a storage medium, the storage medium stores a computer program, and the computer program implements any of the methods described in the present application when the computer program is executed by a processor, the storage medium stores a computer program, and the computer When the program is executed by the processor, the method described in any of the embodiments of the present application is implemented.
  • response methods and determination methods where the response methods include:
  • the response result of the management operation request is associated with the deployment restriction condition included in the network service descriptor NSD.
  • the determination method includes: determining the deployment restriction conditions
  • the NSD is determined, and the determination operation of the NSD is associated with the deployment restriction condition.
  • the computer storage medium of the embodiment of the present application may adopt any combination of one or more computer-readable media.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • the computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above.
  • Computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination of the above .
  • the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.
  • the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium.
  • the computer-readable medium may send, propagate or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .
  • the program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
  • suitable medium including but not limited to: wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
  • the computer program code used to perform the operations of this application can be written in one or more programming languages or a combination thereof.
  • the programming languages include object-oriented programming languages—such as Java, Smalltalk, C++, and also conventional Procedural programming language-such as "C" language or similar programming language.
  • the program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network-including Local Area Network (LAN) or Wide Area Network (WAN)-or, it can be connected to an external computer (For example, use an Internet service provider to connect via the Internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the application is not limited thereto.
  • the embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FGPA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASICs application specific integrated circuits
  • FGPA programmable logic devices

Landscapes

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

Abstract

本申请提出一种响应方法、确定方法、装置、设备及介质，该响应方法应用于管理节点，包括获取管理操作请求；响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。本申请的技术方案有效的基于NSD进行操作管理请求的响应。

Description

一种响应方法、确定方法、装置、设备及介质 技术领域
本申请涉及通信技术领域，例如涉及一种响应方法、确定方法、装置、设备及介质。
背景技术
复杂的实际网络情况中，网络服务描述符(Network Service Descriptor，NSD)存在适用范围的限制，一个NSD适用于全网的情况有限。
故，如何基于NSD进行操作管理请求的响应是当前亟待解决的技术问题。
发明内容
本申请提供一种响应方法、确定方法、装置、设备及介质，有效的基于NSD进行操作管理请求的响应。
第一方面，本申请实施例提供了一种响应方法，应用于管理节点，包括：
获取管理操作请求；
响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
第二方面，本申请实施例提供了一种确定方法，应用于网络服务设计器，包括：
确定部署限制条件；
确定NSD，所述NSD的确定操作与所述部署限制条件关联。
第三方面，本申请实施例提供了一种响应装置，配置于管理节点，包括：
获取模块，设置为获取管理操作请求；
响应模块，设置为响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
第四方面，本申请实施例提供了一种确定装置，配置于网络服务设计器， 包括：
第一确定模块，设置为确定部署限制条件；
第二确定模块，设置为确定NSD，所述NSD的确定操作与所述部署限制条件关联。
第五方面，本申请实施例提供了一种设备，包括：
一个或多个处理器；
存储装置，用于存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现本申请实施例中的任一种方法。
第六方面，本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中的任意一种方法。
关于本申请的以上实施例和其他方面以及其实现方式，在附图说明、具体实施方式和权利要求中提供更多说明。
附图说明
图1是本申请实施例提供的一种响应方法的流程示意图；
图2是本申请实施例提供的一种确定方法的流程示意图；
图2a是本申请实施例提供的一种确定NSD的场景示意图；
图2b是本申请实施例提供的一种管理操作请求处理流程示意图；
图2c是本申请实施例提供的又一种管理操作请求处理流程示意图；
图2d是本申请实施例提供的另一种管理操作请求处理流程示意图；
图2e是本申请实施例提供的再一种管理操作请求处理流程示意图；
图2f是本申请实施例提供的再一种管理操作请求处理流程示意图；
图2g是本申请实施例提供的再一种管理操作请求处理流程示意图；
图3是本申请实施例提供的一种响应装置的结构示意图；
图4是本申请实施例提供的一种确定装置的结构示意图；
图5是本申请实施例提供的一种设备的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行示例性说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
在一个示例性实施方式中，图1是本申请实施例提供的一种响应方法的流程示意图，该方法可以适用于处理管理操作请求的情况，该方法可以由响应装置执行，该装置可以由软件和/或硬件实现，并集成在设备上。设备可以为管理节点。
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)规范中描述了可以使用网络服务描述符(Network Service Descriptor，NSD)来部署网络服务，欧洲电信标准协会(European Telecommunications Sdandards Institute，ETSI)网络功能虚拟化(Network Functions Virtualisation，NFV)规范定义了NSD的格式和操作接口。
复杂的实际网络情况，导致运营管理网络中存在不同的管理域划分或管理角色划分。如限制第三代移动通信技术(3rd-Generation，3G)网络运维人员对第五代移动通信技术(5th-Generation，5G)网络的操作，限制个人网络运维人员对企业专用网络的操作。限制区域A的运维人员对区域B网络的操作，等等。在3GPP的管理模型中，每一个网元(Managed Element,ME)都归属于特定的域，并由该域的管理系统管理。采用虚拟化技术后，分领域、分权限管理的架构同样适用。如实现第四代移动通信技术(the 4th generation mobile communication  technology，4G)技术的物理网络功能(physical network function,PNF)、虚拟化网络功能(Virtualize Network Function,VNF)组合成仅适用于4G领域的网络服务(Network Service，NS)；供应商A提供的PNF、VNF组合成仅适用于运营商划分给供应商A的支持区域的NS。用于描述部署NS实例所需的组成元素及各组成元素之间的拓扑关系的NSD也有适用范围的限制，如上述用于部署4G NS的NSD需要限制由4G领域的管理人员操作；用于区域A部署的NSD只能用于区域A而不能用于区域B的部署。
相关技术中规范的管理模型中，系统希望可由同一个NSD实例化出多个NS实例，NS实例生成后归属到特定的管理域。但是基于复杂的网络现状，一个NSD适用于全网的情况有限，由于存在NSD只能使用在有限的管理域和只对限定的管理员可见的限制，需要考虑NSD的管理问题。相关技术中对于NSD的限制和管理还没有方法可用。
为了解决上述技术问题，如图1所示，本申请提供的响应方法，包括如下步骤：
S110、获取管理操作请求。
管理操作可以为NSD管理操作，NSD管理操作可以指ETSI NFV规范中的NSD管理操作。管理操作请求可以为NSD管理操作的请求信息。
获取管理操作请求后，本申请可以对其进行响应，以确定是否执行对应的管理操作。
S120、响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
获取管理操作请求后，本步骤可以响应所述管理操作请求。
具体地，本步骤可以基于NSD所包括的部署限制条件，确定管理操作请求 的响应结果。其中，部署限制条件可以限定使用NSD处理管理操作请求的限制条件，如使用NSD部署NS的限制条件。
本申请基于NSD所包括的部署限制条件可以确定管理操作请求的响应结果，响应结果可以包括NSD管理操作执行和拒绝操作。
管理操作请求中可以包括与部署限制条件匹配的信息，该信息的具体内容可以基于部署限制条件的具体内容确定。
在一个实施例中，在部署限制条件包括使用权限限制条件的情况下，管理操作请求中可以包括该管理操作请求对应的使用权限。本申请可以确定该使用权限是否满足部署限制条件，以确定响应结果。
在一个实施例中，在部署限制条件包括使用域范围限制条件的情况下，管理操作请求可以包括该管理操作请求对应的使用域。本申请可以确定该使用域是否满足部署限制条件，以确定响应结果。
本申请提供的响应方法，首先获取管理操作请求；然后响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。利用该方法能够有效的基于NSD进行管理操作请求的响应。
在上述实施例的基础上，提出了上述实施例的变型实施例，在此需要说明的是，为了使描述简要，在变型实施例中仅描述与上述实施例的不同之处。
在一个实施例中，所述部署限制条件包括如下一个或多个：使用权限限制条件；使用域范围限制条件。
使用权限限制条件可以认为是基于使用权限确定的限制条件。使用域范围限制条件可以认为是基于使用域范围确定的限制条件。
在一个实施例中，使用权限限制条件通过如下一个或多个方式确定：允许使用的用户列表；不允许使用的用户列表；判断用户权限的限制条件。
允许使用的用户列表可以包括NSD绑定的用户，管理节点可以执行该用户发起的管理操作请求。不允许使用的用户列表可以包括NSD绑定的用户，管理节点可以拒绝执行该用户发起的管理操作请求。使用权限限制条件可以为允许使用的用户列表或不允许使用的用户列表，基于各列表可以限定使用权限限制条件。
使用权项限制条件也可以为判定用户权限的限制条件，判定用户权限的限制条件不作具体限定，可以根据实际情况设定。
在一个实施例中，使用域范围限制条件通过如下一个或多个使用域范围确定：地域范围；技术领域范围。
使用域范围限制条件可以通过地域范围或技术领域范围限定。地域范围可以认为是基于地域空间划分的范围。技术领域范围可以认为是基于技术领域划分的范围。
在一个实施例中，所述响应所述管理操作请求，包括：
基于所述NSD所包括的部署限制条件对所述管理操作请求对应的用户进行权限认证；
根据权限认证结果响应所述管理操作请求。
在对管理操作请求对应用户进行权限认证的情况下，可以基于部署限制条件所包括的具体内容确定认证的具体手段。如基于用户的使用权限和使用域进行权限认证。
权限认证结果可以包括认证通过和认证不通过。若认证通过可以执行该管理操作请求。若认证不通过可以拒绝该管理操作请求。
在一个实施例中，所述管理节点为网络功能虚拟化管理及编排。
在一个示例性实施方式中，本申请还提供了一种确定方法，图2是本申请 实施例提供的一种确定方法的流程示意图，该方法可以适用于确定用于响应管理操作请求的NSD的情况。该方法可以由本申请提供的确定装置执行，该装置可以由软件和/或硬件实现，并集成在网络服务设计器上，以确定NSD。
如图2所示，本申请提供了一种确定方法，包括如下步骤：
S210、确定部署限制条件。
部署限制条件可以为网络服务设计器自动从管理节点获取确定，也可以是通过与设计者交互获取确定。部署限制条件的具体内容不作限定，可以根据实际需求设定。
S220、确定NSD，所述NSD的确定操作与所述部署限制条件关联。
确定部署限制条件后，本步骤可以基于部署限制条件确定NSD。确定操作与部署限制条件关联可以认为是基于部署限制条件确定NSD。确定出的NSD可以包括部署限制条件，以基于部署限制条件响应管理操作请求。
本申请在确定NSD的情况下，可以基于相关技术中的组网信息和网络服务功能需求，及本申请所述的部署限制条件确定。所确定的NSD相较于相关技术的NSD新增包括了部署限制条件。
本申请提供了一种确定方法，首先确定部署限制条件；然后确定NSD，所述NSD的确定操作与所述部署限制条件关联。利用该方法确定了用于响应管理操作请求的NSD，以有效的基于确定的NSD进行管理操作请求的响应。
在上述实施例的基础上，提出了上述实施例的变型实施例，在此需要说明的是，为了使描述简要，在变型实施例中仅描述与上述实施例的不同之处。
在一个实施例中，所述网络服务设计器集成在管理节点；或者为独立的功能模块；或者集成在运营支撑系统或业务支撑系统。
在一个实施例中，所述NSD包括部署限制条件，所述部署限制条件用于对 用户进行权限认证。
在响应管理操作请求的情况下，部署限制条件可以通过与管理操作请求对应用户的相应信息，如使用权限和使用域对用户进行权限认证。
在一个实施例中，所确定的NSD中被嵌套的NSD基于目标NSD的部署限制条件和所确定NSD的设计需求过滤确定，所述目标NSD为基于除所述部署限制条件外的过滤条件过滤得到的NSD。
除部署限制条件外的过滤条件可以为相关技术中的过滤条件和后续新增的过滤条件。本申请可以先基于除部署限制条件外的过滤条件进行初次过滤，然后基于目标NSD的部署限制条件再次过滤得到被嵌套的NSD。
在确定目标NSD的情况下，可以基于所确定NSD的设计需求和目标NSD的部署限制条件进行匹配，选取满足所确定NSD的设计需求的目标NSD作为被嵌套的NSD。
在一个实施例中，该方法，还包括：
将所述NSD传输至管理节点。
在一个示例中，在确定NSD后，本申请可以将该NSD传输至设计者，由设计者将NSD通过运营支撑系统或业务支撑系统上传至管理节点，以供管理节点响应管理操作请求。
在一个示例中，在确定NSD后，本申请可以将该NSD传输至设计者，由设计者传输至满足部署限制条件的使用者，然后由使用者将NSD通过运营支撑系统或业务支撑系统上传至管理节点，以供管理节点响应管理操作请求。
以下对本申请进行详细描述，本申请提供的一种响应方法可以认为是一种网络服务设计和管理方法，在采用虚拟化技术之前，网络运营商的网络是通过专用硬件设备来部署，一项新网络服务的推出，通常需要增加新的设备，不断 增长的网络容量和服务类型导致能耗不断增加，资本投入存在挑战，又缺少必要的技能来设计、整合和操作日趋复杂的硬件设备。
NFV是一种通过使用通用硬件以及虚拟化技术来承载其他功能的软件处理技术，旨在降低网络昂贵的设备成本。NFV通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。实体设备虚拟化后所承载的功能称为VNF，非虚拟化实现的传统设备称为PNF。
在运营商的立场，考虑成本因素，已经部署的PNF和已经储备的设备需要继续使用,不能直接淘汰更换成VNF；考虑性能和效率，部分网络功能，采用虚拟化技术的VNF还达不到要求，仍然需要使用配备专用硬件PNF来实现。所以，在很长时间内，VNF和PNF将在运营商网络中共存，设计者基于实际的组网要求，把二者按照特定方式组合，为用户提供各种类型的NS。3GPP标准组定义的提供给用户的网络服务\通信服务NS，是基于ETSI NFV标准组定义网络服务实例及网络服务参数提供，后者是基于ETSI NFV标准组定义的NSD及资源配置参数实例化出来的网络服务实例(NS实例)。NSD是ETSI NFV标准组定义的部署模板，用于描述部署NS实例所需的各组成元素及组成元素之间的拓扑关系，在NSD中可包含虚拟化网络功能描述符(Virtualized Network Function Descriptors，VNFD)、物理网络功能描述符(Physical Network Function Descriptor，PNFD)，嵌套的网络服务描述符(nested NSD)及相互之间的虚拟链路(Virtualized Link,VL)。
除了VNF和PNF长期共存，从管理的角度看，运营商网络环境中还存在多种技术长期共存的情况，比如说3G、4G、5G技术共存；普通电信个人用户网 络、企业专用网络、物联网、车联网共存。在大型的运营商的网络中，同一网络功能在不同的区域由不同的设备商提供PNF、VNF，比如说在区域A由PNF提供的功能在区域B可能是由VNF提供，因而不同区域的设备商的PNF和VNF组合成NS的拓扑关系会有差异，需要区分管理和使用。
综上所述，复杂的实际网络情况，导致运营管理网络时存在不同的管理域划分或管理角色划分。如限制3G网络运维人员对5G网络的操作，限制个人网络运维人员对企业专用网络的操作。限制区域A的运维人员对区域B网络的操作，等等。在3GPP的管理模型中，每一个网元都归属于特定的域，并由该域的管理系统管理。采用虚拟化技术后，分领域、分权限管理的架构同样适用。如实现4G技术的PNF、VNF组合成仅适用于4G领域的NS；供应商A提供的PNF、VNF组合成仅适用于运营商划分给供应商A的支持区域的NS。用于描述部署NS实例所需的组成元素及各组成元素之间的拓扑关系的NSD也有适用范围的限制，如上述用于部署4G NS的NSD需要限制由4G领域的管理人员操作；用于区域A部署的NSD不能用于区域B的部署。
故为了解决上述技术问题，本申请提供了一种NSD管理的方法，即确定NSD的方法，通过在NSD中增加部署限制条件，解决NSD的管理问题。所述部署限制条件是指NSD中携带信息表明使用该NSD部署NS的限制条件，包括但不限于如下三类：
按使用权限限制，表明该NSD可以被运营商管理系统具备指定权限的用户使用。所述使用权限可以是罗列允许使用的用户列表，也可以是判断用户权限的限制条件。
按使用域范围限制，此信息表明该NSD可以用于在运营商管理系统中划定的使用域中部署NS。所述的使用域范围可以是地域范围，也可以是技术领域范 围(如3G、4G、5G)，也可是地域范围结合技术领域范围。
按“使用域范围”结合“使用权限”限制，此信息表明该NSD可以被运营商管理系统中划定使用域中满足指定权限的用户使用。
所述的用户不限定为具体的人员，也可以是运营商管理系统中定义的租户或管理角色。
所述的使用NSD，是指ETSI NFV规范中的定义的以NSD为参数的生命周期管理(Life Cycle Management，LCM)操作，如使用NSD实例化NS实例、删除NSD、查询NSD的内部信息等。也指把NSD作为其他NSD的嵌套组成部分的操作。
图2a是本申请实施例提供的一种确定NSD的场景示意图，参见图2a，在NSD的设计阶段，网络服务设计器基于输入的组网信息、网络服务功能需求和部署限制条件生成NSD，NSD中携带部署限制条件表明可以使用该NSD的限制条件。在使用阶段，该NSD被上传到第二管理节点，即管理节点，基于NSD中携带的部署限制条件，绑定给可以使用的用户，后续只有被绑定的用户才能发起对该NSD的LCM操作。
本申请中的NSD可以基于相关技术中的组网信息和网络服务功能需求和新增的部署限制条件确定。确定的NSD包括相关技术中定义的NSD和部署限制条件。设计一个网络服务是要实现一个具体的功能，故需要基于网络服务功能需求确定NSD。组网信息可以包括网络设备及设备间的组合逻辑关系。
所述第一管理节点可以是运营支撑系统(Operation Support System，OSS)或业务支撑系统(Business Support System，BSS)。所述第二管理节点是网络功能虚拟化管理及编排(Network Functions Virtualisation Management and Orchestration，NFV-MANO)。所述网络服务设计器可以为第一管理节点的一个 功能模块，可以为第二管理节点的一个功能模块，也可以是独立的功能模块。
实施例一
本实施例按照使用权限限制确定NSD。图2b是本申请实施例提供的一种管理操作请求处理流程示意图，参见图2b，该流程中包括了确定NSD和基于NSD响应管理操作请求。在该实施例中，NSD只能由具有限定权限的用户使用。在网络服务设计阶段，设计者先了解网络服务功能需求以及要部署网络服务的运营环境信息，与网络服务设计器交互，生成NSD。在NSD中携带的部署限制条件设为使用权限(可以是罗列允许使用的用户列表，也可以是判断用户权限的限制条件，不同运营商自行设定)。在使用阶段，该NSD被上传到NFV-MANO，根据部署限制条件绑定到指定的用户(本实施例中使用者为设计者)。后续只有满足限制条件的发起者才能使用该NSD进行实例化等生命周期管理操作。
该实施例适用但不限制于运营商开发新业务的场景，网络服务设计者设计完成后进行预测试，把NSD上传到NFV-MANO，为避免对其他用户和已经部署的网络服务的干扰，需要隔离屏蔽，该NSD对于系统中其他的管理角色不可见，只有满足限定条件的使用者(如本实例中的设计者)能使用该NSD部署NS实例，从而继续进行新业务开发相关的工作。当测试验证完成，投入正式运营前，NSD的部署限制条件更新为运营商指定的使用者权限。
需要说明的是，所述设计者、使用者，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
管理操作请求处理流程可以包括如下步骤：
01.网络服务设计器获取生成NSD所需数据。
在本实施例中网络服务设计器可以作为OSS\BSS的一个组成模块部署，OSS\BSS保存的网络设备信息和状态对网络服务设计器可见。设计者向网络服 务设计器发起生成NSD流程；由网络服务设计器从OSS\BSS获取网络设备信息；设计者与网络服务设计器交互，确认生成NSD所需参数，生成NSD所需参数(即生成NSD所需数据)需要包括网络服务功能、组网信息即所用网络设备(PNFD、VNFD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
需要说明的是，在本步骤中没有详细列举设计者与网络服务设计器之间交互的每一个环节和罗列所有参数，仅描述关键步骤和抽象的信息描述。
该步骤可以包括步骤01a、01b和01c。
02.NSD生成。
网络服务设计器依据收到的数据生成NSD。
在本步骤中，所述NSD遵循ETSI NFV定义的规范，在此基础上根据设计者要求把部署限制条件设为使用者(设计者)的权限。所述设计者，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
03.传输NSD。
网络服务设计器将生成的NSD发送至设计者。
04.上传NSD。
设计者/使用者可以通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件作为把NSD绑定给使用者的判定依据。
05.NSD LCM请求。
设计者/使用者发起对NSD的管理操作请求，如LCM请求。NSD管理操作可以指ETSI NFV规范中定成的NSD管理操作。
06.NSD管理操作执行。
设计者/使用者权限认证通过，操作有效，NFV-MANO执行收到的操作请求。
07.NSD LCM请求。
没有权限的用户发起NSD的管理操作请求。
08.拒绝操作。
操作发起者不是NSD绑定的用户，判定为非法操作，NFV-MANO拒绝执行该操作请求。
实施例二
本实施例按照使用域范围确定NSD。图2c是本申请实施例提供的又一种管理操作请求处理流程示意图。参见图2c，NSD只能在限定域使用，所述的限定域可以基于适用于范围限制条件确定，可指地域范围(如运营商指定给供应商的部署区域)，也可指技术领域范围(如3G技术领域)，也可是地域范围结合技术领域范围(如在运营商网络中，同一地域范围内不同技术领域由不同的设备商提供VNF和PNF，则对应的NSD只能使用于该限定地域的限定技术领域)。在网络服务设计阶段，设计者了解网络服务具体需求(即网络服务功能需求)以及要部署网络服务的运营环境信息，与网络服务设计器交互，生成NSD。在NSD中携带的部署限制条件设为该NSD能使用的使用域。在使用阶段，该NSD被上传到NFV-MANO系统，运营商管理系统中该使用域的用户都可以发起对该NSD的管理操作，如使用该NSD实例化出NS实例。
该实施例适用但不限制于指定NSD携带允许使用该NSD的使用域场景，也适用于通过指定不允许使用该NSD部署的使用域。
本实施例中的管理操作请求处理流程包括如下步骤：
1.获取生成NSD所需数据。
网络服务设计器可以作为OSS\BSS的一个组成模块部署，OSS\BSS保存的网络设备信息和状态对网络服务设计器可见。设计者向网络服务设计器发起生成NSD流程；由网络服务设计器从OSS\BSS获取网络设备信息；设计者与网络服务设计器交互，确认生成NSD所需参数，生成NSD所需参数(即生成NSD所需数据)需要包括网络服务功能、组网信息即所用网络设备(PNFD、VNFD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
需要说明的是，在本步骤中没有详细列举设计者与网络服务设计器之间交互的每一个环节和罗列所有参数，仅描述关键步骤和抽象的信息描述。
本步骤可以包括1a、1b和1c。
2.NSD生成。
在本步骤中，所述NSD遵循ETSI NFV定义的规范，在此基础上根据设计者要求把部署限制条件设置为能使用该NSD的使用域，即表明在运营商网络中该使用域的所有使用者都可以使用此NSD。所述使用者，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
3.传输NSD。
网络服务设计器生成NSD后，将NSD传输至设计者，由设计者传输至使用域内的使用者。
4.上传NSD。
使用者通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件作为把NSD绑定给使用者的判定依据，在本实施例中，使用者为部署限制条件限定的使用域内所有用户。所述用户，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
5.NSD LCM请求。
使用域内的使用者发起对NSD的管理操作请求，如LCM请求。
6.NSD管理操作执行。
使用者为NFV-MANO的合法用户，且操作的目标为绑定给此用户的NSD，NFV-MANO执行收到的操作请求。
实施例三
本实施例按照使用域和使用权限确定NSD。图2d是本申请实施例提供的另一种管理操作请求处理流程示意图。NSD只能在限定域中由具有特定权限的用户使用。在网络服务设计阶段，设计者了解网络服务具体需求以及要部署网络服务的运营环境信息，与网络服务设计器交互，生成NSD。该NSD只能由限定的管理域用户或管理域内特定的角色使用，则在NSD中携带的部署限制条件设为“使用域范围”+“使用权限”。在使用阶段，该NSD被上传到NFV-MANO系统，运营商管理系统中该使用域的用户才可以发起对该NSD的管理操作，如使用该NSD实例化出NS实例。
该实施例适用但不限制于设计特定域的特定服务NSD的使用场景，如为运营商设计一个4G技术领域的企业专网服务或3G技术领域的IP多媒体子系统(IP Multimedia Subsystem，IMS)服务，NSD设计者设计NSD，该NSD只能由对应技术领域中具有特定的权限用户(4G企业网运维人员或3G IMS网运维人员)才能使用，如2G网络运维人员或家庭上网的运维人员不能操作该NSD。
需要说明的是，所述设计者和使用者，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
参见图2d，该流程包括如下步骤：
10.获取生成NSD所需数据。
网络服务设计器可以作为OSS\BSS的一个组成模块部署，OSS\BSS保存的网络设备信息和状态对网络服务设计器可见。设计人员向网络服务设计器发起生成NSD流程；由网络服务设计器从OSS\BSS获取网络设备信息；设计者与网络服务设计器交互，确认生成NSD所需参数，生成NSD所需参数(即生成NSD所需数据)需要包括网络服务功能、组网信息即所用网络设备(PNFD、VNFD、nested NSD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
需要说明的是，在本步骤中没有详细列举设计者与网络服务设计器之间交互的每一个环节和罗列所有参数，仅描述关键步骤和抽象的信息描述。
该步骤包括10a、10b和10c。
20.NSD生成。
在本步骤中，所述NSD遵循ETSI NFV定义的规范，在此基础上根据设计者要求把部署限制条件设为“使用域范围”结合“使用权限”，即表明此NSD被运营商管理系统中划定使用域中满足指定权限的用户使用。所述使用者，并不限定为具体的人员，而可以是管理系统中定义的租户或管理角色。
30.传输NSD。
设计者得到生成的NSD，转交给使用者，即使用域内限定权限的用户。
40.上传NSD。
使用者通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件信息作为把NSD绑定给使用者的判定依据，在本实施例中，使用者为满足限定条件的用户。
50.NSD LCM请求。
使用者发起NSD的管理操作请求，如LCM请求。NSD管理操作是指ETSI  NFV规范中定成的NSD管理操作。
60.NSD管理操作执行。
使用者为NFV-MANO的合法用户，且操作的目标NSD是绑定给该用户的资源，NFV-MANO执行收到的操作请求。
70.NSD LCM请求。
没有权限的用户发起对NSD的管理操作请求。
80.拒绝操作。
操作发起者不是NSD绑定的用户，判定为非法操作，NFV-MANO拒绝执行该操作请求。
实施例四
本实施例示出了复合NSD的设计。图2e是本申请实施例提供的再一种管理操作请求处理流程示意图，当设计者在设计NSD的时候，需要包含其他NSD的场景，检查被包含的NSD是否可以被使用或有满足功能要求的多个NSD时，根据NSD所带的部署限制条件过滤出能被使用的NSD。
该实施例适用于设计包含嵌套NSD的场景，例如虚拟运营商的网络服务B需要基于运营商的网络服务A和其他VNF\PNF配合提供新的服务，那么在NSD B设计阶段要把NSD A作为NSD B中的nested NSD成员。在此过程中需要依据NSD A的部署限制条件来检查，是否能够被NSD B包含并使用。生成的NSD B同样需要设置部署限制条件。
需要说明的是，对NSD B内嵌套的NSD A的使用限制，遵守对NSD B的使用限制要求。不影响直接使用NSD A场景下的部署限制条件，也不影响NSD A作为另一个NSD C的嵌套NSD时的部署限制条件。
参见图2e，该流程包括如下步骤：
110.获取生成NSD所需数据。
该步骤包括如下操作：
110a.设计者向网络服务设计器发起生成NSD流程。
110b.获取网络设备信息，即网络服务设计器从OSS\BSS获取网络设备信息，把设计者的用户信息转发给OSS\BSS。其中，用户信息可以用于确定用户的使用权限。
110c.部署限制条件检查，过滤可用NSD。
过滤可用NSD的情况下，OSS\BSS与网络服务设计器交互，进行权限匹配，按设计人员的使用权限和\或设计目标NSD的设计需求(即所确定NSD的设计需求)过滤出可让其使用的NSD。
需要说明的是，在本步骤中过滤NSD时采用过滤方式和过滤条件可以有多种，包括并不限于如下所列方式和条件组合：
设计者的使用权限为具有运营商管理系统超级用户权限，则所有NSD可供使用；
设计者的使用权限为具有运营商管理系统中指定域的用户权限，则过滤该域的所有NSD，供使用(如具有4G管理域用户权限，则过滤出部署限制条件中使用域为4G技术领域的所有NSD)；
设计目标NSD的设计需求为需要包含语音服务NSD，则过滤所有的语音服务NSD，供使用。
设计目标NSD需要包含5G数据服务NSD，则过滤出部署限制条件中使用域为5G技术领域的数据服务NSD，供使用，即基于部署限制条件确定可供使用的被嵌套的NSD。
设计目标NSD需要限制在运营商指定的区域部署，则过滤出部署限制条件中使用地域为该区域的所有NSD，供使用，即基于部署限制条件过滤出被嵌套的NSD。
在确定被嵌套NSD时，基于设计者的使用权限和设计目标NSD(即所确定的NSD)的设计需求，初次过滤得到的NSD可以为目标NSD。基于目标NSD的部署限制条件再次过滤得到的NSD可以为被嵌套的NSD。
需要说明的是，在本步骤中OSS\BSS是否对PNFD和VNFD进行过滤，不是本申请的关注点，所以不做描述和限定。
110d.传输网络设备信息。
网络服务设计器得到网络设备信息，包含如哪些网络功能由PNF提供，哪些网络功能由VNF提供，已经有哪些可以使用的NSD。
110e.NSD生成参数交互。
设计人员与网络服务设计器交互，确认生成NSD所需参数，生成NSD所需参数(即生成NSD所需数据)需要包括网络服务功能、组网信息即所用网络设备(PNFD、VNFD、nested NSD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
120.NSD生成。
NSD遵循ETSI NFV定义的规范，在此基础上根据设计者要求设置部署限制条件。所述设置部署限制条件，是对新生成的NSD进行设置，可设置条件同实施例一、二、三，不再重复拆分成多个实施例。
需要说明的是，在本步骤中，不改变被嵌套的NSD的部署限制条件。
130.传输NSD。
网络服务设计器将生成的NSD传输至设计者。
140.上传NSD。
使用者通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件作为把NSD绑定给使用者的判定依据。
在本步骤中，NSD中包含的被嵌套的NSD的部署限制条件不影响对NSD的绑定操作判定。
150.NSD LCM请求。
使用域内的使用者发起对NSD的管理操作请求。
160.NSD管理操作执行。
使用者为NFV-MANO的合法用户，且操作的目标NSD是绑定给该用户的资源，NFV-MANO执行收到的操作请求。
实施例五
本实施例示出了独立部署的网络服务设计器。图2f是本申请实施例提供的再一种管理操作请求处理流程示意图，网络服务设计器是一个独立的功能模块，不直接和OSS\BSS、NFV-MANO交互，设计者在与网络服务设计器交互之前获取生成NSD所需要的数据。
该实施例适用但不限制于离线设计NSD的使用场景，NSD设计阶段由设计者依据设计需求，提供实现网络服务的VNF，然后使用VNF组合生成NSD，提供给运营商网络使用；或设计者通过其他途径从运营商获取网元信息和网元间组合逻辑，依据这些信息设计出NSD，提供给运营商网络使用。
参见图2f，该流程包括如下步骤：
210.传输NSD生成需求，NSD生成参数。
设计人员在设计具体的网络服务前，向运营商或网络服务提供商获取该网络服务的功能需求以及网络设备信息，如哪些网络功能由PNF提供，哪些网络服务由VNF提供，是否基于已有网络服务提供新的网络服务等。然后设计者向网络服务设计器发送NSD生成需求，携带NSD生成参数(即生成NSD所需参数)，所述NSD生成参数需要包括网络服务功能、组网信息即所用网络设备(PNFD、VNFD、nested NSD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
220.NSD生成。
230.传输NSD。
设计者得到生成的NSD，传输至满足限制条件的用户。
240.上传NSD。
使用者通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件作为把NSD绑定给使用者的判定依据。
250.NSD LCM请求。
使用者，即满足限制条件的用户发起对NSD的管理操作请求。
260.NSD管理操作执行。
使用者认证通过，操作有效，NFV-MANO执行收到的操作请求。
实施例六
本实施例提供了部署在NFV-MANO的网络服务设计器。图2g是本申请实施例提供的再一种管理操作请求处理流程示意图。网络服务设计器作为NFV-MANO的一个功能模块部署，在这种场景时，NFV-MANO保存的已经上 载的PNFD、VNFD、NSD信息对网络服务设计器可见。
需要说明的是，如果设计者需要查询已经上载的NSD，需要依据设计者的权限，匹配NSD的部署限制条件，过滤出能向设计者展现的NSD，供设计者选择。对于包含嵌套NSD的复合NSD，需要设置部署限制条件，过程同实施例四。
参见图2g，该流程包括如下步骤：
310.获取生成NSD所需数据。
设计者向网络服务设计器发起生成NSD流程；由网络服务设计器从NFV-MANO获取网络设备信息，依据设计人员权限匹配已上载的NSD中部署限制条件过滤出可供使用的NSD；设计人员与网络服务设计器交互，确认生成NSD所需参数，所述生成NSD参数需要包含网络服务功能、组网信息即所用网络设备(PNFD、VNFD、nested NSD)以及网络设备间的组合逻辑关系，以及使用NSD的部署限制条件。
需要说明的是，在本步骤中没有详细列举设计者与网络服务设计器之间交互的每一个环节和罗列所有参数，仅描述关键步骤和抽象的信息描述。
需要说明的是，在本步骤中是否对PNFD和VNFD进行过滤，不是本申请的关注点，所以不做描述和限定。
需要说明的是，在本步骤中过滤NSD时采用过滤方式和过滤条件可以有多种，包括并不限于如下所列方式和条件组合：
设计者具有运营商管理系统超级用户权限，则所有NSD可供使用；
设计者具有运营商管理系统中指定域的用户权限，则过滤该域的所有NSD，供使用(如具有4G管理域用户权限，则过滤出部署限制条件中使用域为4G技术领域的所有NSD)；
设计目标NSD需要包含指定功能的NSD，则根据功能过滤满足条件的NSD，供使用(如需要语音服务NSD，则过滤所有的语音服务NSD)；
设计目标NSD需要包含指定技术领域指定功能的NSD，则过滤该技术领域指定功能的NSD，供使用(如需要5G数据服务NSD，则过滤出部署限制条件中使用域为5G技术领域的数据服务NSD)；
设计目标NSD需要限制在运营商指定的区域部署，则过滤出部署限制条件中使用地域为该区域的所有NSD，供使用。
320.NSD生成。
NSD遵循ETSI NFV定义的规范，在此基础上根据设计者要求设置部署限制条件。所述设置部署限制条件，同实施例一、二、三，不再重复拆分成多个实施例。
330.传输NSD。
设计者得到生成的NSD，传输至满足限定条件的用户。
340.上传NSD。
使用者通过OSS\BSS与NFV-MANO之间的上载接口，把NSD上传到NFV-MANO。NSD中携带的部署限制条件作为把NSD绑定给使用者的判定依据。
350.NSD LCM请求。
360.NSD管理操作执行。
使用者认证通过，操作有效，NFV-MANO执行收到的操作请求。
随着5G商用进展，虚拟化的网络功能和网管服务部署增加，但是需要考虑虚拟化功能和非虚拟化功能之间的长期共存，以及新部署的部分与现网已经部署及运营中的部分的隔离和限制。复杂的实际网络情况，导致存在不同的管理 域划分或管理\使用角色划分。本申请可以使对NSD的限制融入到现网管理系统的分领域、分权限管理的架构中。
在一个示例性的实施方式中，本申请实施例提供了一种响应装置，图3是本申请实施例提供的一种响应装置的结构示意图，该响应装置可以配置于管理节点，如图3所示，本申请实施例中的响应装置包括：获取模块31，设置为获取管理操作请求；响应模块32，设置为响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
本实施例提供的响应装置用于实现本申请实施例的响应方法，本实施例提供的响应装置实现原理和技术效果与本申请实施例的响应方法类似，此处不再赘述。
在上述实施例的基础上，提出了上述实施例的变型实施例，在此需要说明的是，为了使描述简要，在变型实施例中仅描述与上述实施例的不同之处。
在一个实施例中，所述部署限制条件包括如下一个或多个：使用权限限制条件；使用域范围限制条件。
在一个实施例中，使用权限限制条件通过如下一个或多个方式确定：允许使用的用户列表；不允许使用的用户列表；判断用户权限的限制条件。
在一个实施例中，使用域范围限制条件通过如下一个或多个使用域范围确定：地域范围；技术领域范围。
在一个实施例中，响应模块32具体设置为：
基于所述NSD所包括的部署限制条件对所述管理操作请求对应的用户进行权限认证；
根据权限认证结果响应所述管理操作请求。
在一个实施例中，所述管理节点为网络功能虚拟化管理及编排。
在一个示例性的实施方式中，本申请实施例提供了一种确定装置，图4是本申请实施例提供的一种确定装置的结构示意图，该装置可以配置于网络服务设计器，该装置包括：第一确定模块41，设置为确定部署限制条件；第二确定模块42，设置为确定NSD，所述NSD的确定操作与所述部署限制条件关联。
本实施例提供的确定装置用于实现本申请实施例的确定方法，本实施例提供的确定装置实现原理和技术效果与本申请实施例的确定方法类似，此处不再赘述。
在上述实施例的基础上，提出了上述实施例的变型实施例，在此需要说明的是，为了使描述简要，在变型实施例中仅描述与上述实施例的不同之处。
在一个实施例中，所述网络服务设计器集成在管理节点；或者为独立的功能模块；或者集成在运营支撑系统或业务支撑系统。
在一个实施例中，所述NSD包括部署限制条件，所述部署限制条件用于对用户进行权限认证。
在一个实施例中，所确定的NSD中被嵌套的NSD基于目标NSD的部署限制条件和所确定NSD的设计需求过滤确定，所述目标NSD为基于除所述部署限制条件外的过滤条件过滤得到的NSD。
在一个实施例中，该装置还包括：传输模块，设置为：
将所述NSD传输至管理节点。
在一个示例性实施方式中，本申请提供了一种设备，图5是本申请实施例提供的一种设备的结构示意图。本申请提供的设备，包括一个或多个处理器51和存储装置52；该设备中的处理器51可以是一个或多个，图5中以一个处理器51为例；存储装置52用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器51执行，使得所述一个或多个处理器51实现如本申请实施例 中所述的方法，如响应方法和确定方法。
设备还包括：通信装置53、输入装置54和输出装置55。
设备中的处理器51、存储装置52、通信装置53、输入装置54和输出装置55可以通过总线或其他方式连接，图5中以通过总线连接为例。
输入装置54可用于接收输入的数字或字符信息，以及产生与设备的用户设置以及功能控制有关的按键信号输入。输出装置55可包括显示屏等显示设备。
通信装置53可以包括接收器和发送器。通信装置53设置为根据处理器51的控制进行信息收发通信。信息包括但不限于NSD。
存储装置52作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述方法对应的程序指令/模块(例如，响应装置中的获取模块31和响应模块32；又如，确定装置中的第一确定模块41和第二确定模块42)。存储装置52可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储装置52可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储装置52可进一步包括相对于处理器51远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请任一所述方法，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的方法。如响应方法和确定方法，其中，响应方法包括：
获取管理操作请求；
响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
确定方法包括：确定部署限制条件；
确定NSD，所述NSD的确定操作与所述部署限制条件关联。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式CD-ROM、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不 限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(Local Area Network，LAN)或广域网(Wide Area Network，WAN)——连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。

Claims (15)

  1. 一种响应方法，应用于管理节点，所述方法包括：
    获取管理操作请求；
    响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
  2. 根据权利要求1所述的方法，其中，所述部署限制条件包括如下至少之一：使用权限限制条件；使用域范围限制条件。
  3. 根据权利要求2所述的方法，其中，使用权限限制条件通过如下至少一个方式确定：允许使用的用户列表；不允许使用的用户列表；判断用户权限的限制条件。
  4. 根据权利要求2所述的方法，其中，使用域范围限制条件通过如下至少一个使用域范围确定：地域范围；技术领域范围。
  5. 根据权利要求1所述的方法，其中，所述响应所述管理操作请求，包括：
    基于所述NSD所包括的部署限制条件对所述管理操作请求对应的用户进行权限认证；
    根据权限认证结果响应所述管理操作请求。
  6. 根据权利要求1所述的方法，其中，所述管理节点为网络功能虚拟化管理及编排。
  7. 一种确定方法，应用于网络服务设计器，所述方法包括：
    确定部署限制条件；
    确定网络服务描述符NSD，所述NSD的确定操作与所述部署限制条件关联。
  8. 根据权利要求7所述的方法，其中，所述网络服务设计器集成在管理节点；或者所述网络服务设计器为独立的功能模块；或者所述网络服务设计器集成在运营支撑系统或业务支撑系统。
  9. 根据权利要求7所述的方法，其中，所述NSD包括部署限制条件，所述部署限制条件用于对用户进行权限认证。
  10. 根据权利要求7所述的方法，其中，所确定的NSD中被嵌套的NSD基 于目标NSD的部署限制条件和所确定NSD的设计需求过滤确定，所述目标NSD为基于除所述部署限制条件外的过滤条件过滤得到的NSD。
  11. 根据权利要求7所述的方法，还包括：
    将所述NSD传输至管理节点。
  12. 一种响应装置，配置于管理节点，所述装置包括：
    获取模块，设置为获取管理操作请求；
    响应模块，设置为响应所述管理操作请求，所述管理操作请求的响应结果与网络服务描述符NSD所包括的部署限制条件关联。
  13. 一种确定装置，配置于网络服务设计器，所述装置包括：
    第一确定模块，设置为确定部署限制条件；
    第二确定模块，设置为确定网络服务描述符NSD，所述NSD的确定操作与所述部署限制条件关联。
  14. 一种设备，包括：
    至少一个处理器；
    存储装置，设置为存储至少一个程序；
    当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现如权利要求1-11任一所述的方法。
  15. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-11任一项所述的方法。
PCT/CN2021/094315 2020-05-25 2021-05-18 一种响应方法、确定方法、装置、设备及介质 WO2021238718A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010450253.4A CN111901139A (zh) 2020-05-25 2020-05-25 一种响应方法、确定方法、装置、设备及介质
CN202010450253.4 2020-05-25

Publications (2)

Publication Number Publication Date
WO2021238718A1 true WO2021238718A1 (zh) 2021-12-02
WO2021238718A9 WO2021238718A9 (zh) 2022-01-27

Family

ID=73206609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094315 WO2021238718A1 (zh) 2020-05-25 2021-05-18 一种响应方法、确定方法、装置、设备及介质

Country Status (2)

Country Link
CN (1) CN111901139A (zh)
WO (1) WO2021238718A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901139A (zh) * 2020-05-25 2020-11-06 中兴通讯股份有限公司 一种响应方法、确定方法、装置、设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
WO2017185303A1 (zh) * 2016-04-28 2017-11-02 华为技术有限公司 一种nfv mano策略描述符的管理方法及装置
WO2019082085A1 (en) * 2017-10-24 2019-05-02 Telefonaktiebolaget Lm Ericsson (Publ) METHODS FOR DEFINING NETWORK SERVICE DESCRIPTOR (NSD) FOR NETWORK SERVICE (NS), AND NETWORK FUNCTION VIRTUALIZATION (NFV) ORCHESTRA (NFVO) USING SAID NSD
US20190363953A1 (en) * 2017-03-14 2019-11-28 Intel IP Corporation Methods and systems for instantiating and connecting radio access network virtualized network function and core network virtualized network function
CN111901139A (zh) * 2020-05-25 2020-11-06 中兴通讯股份有限公司 一种响应方法、确定方法、装置、设备及介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106161049A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 一种实现网络服务部署规格配置的方法及装置
WO2017185303A1 (zh) * 2016-04-28 2017-11-02 华为技术有限公司 一种nfv mano策略描述符的管理方法及装置
US20190363953A1 (en) * 2017-03-14 2019-11-28 Intel IP Corporation Methods and systems for instantiating and connecting radio access network virtualized network function and core network virtualized network function
WO2019082085A1 (en) * 2017-10-24 2019-05-02 Telefonaktiebolaget Lm Ericsson (Publ) METHODS FOR DEFINING NETWORK SERVICE DESCRIPTOR (NSD) FOR NETWORK SERVICE (NS), AND NETWORK FUNCTION VIRTUALIZATION (NFV) ORCHESTRA (NFVO) USING SAID NSD
CN111901139A (zh) * 2020-05-25 2020-11-06 中兴通讯股份有限公司 一种响应方法、确定方法、装置、设备及介质

Also Published As

Publication number Publication date
CN111901139A (zh) 2020-11-06
WO2021238718A9 (zh) 2022-01-27

Similar Documents

Publication Publication Date Title
EP3804282B1 (en) Native blockchain platform for improving workload mobility in telecommunication networks
US10701139B2 (en) Life cycle management method and apparatus
RU2690201C1 (ru) Система и способ для динамического управления дескрипторами функций виртуализированной сети
CN106411857B (zh) 一种基于虚拟隔离机制的私有云gis服务访问控制方法
US8813225B1 (en) Provider-arbitrated mandatory access control policies in cloud computing environments
CN108134764B (zh) 一种分布式数据共享交换方法及系统
US20180295067A1 (en) System and Method for granting Virtualized Network Function Life Cycle Management
US8782795B1 (en) Secure tenant assessment of information technology infrastructure
JP2014505960A (ja) アプリケーション証明のためのシステムおよび方法
CN111709023B (zh) 一种基于可信操作系统的应用隔离方法及系统
CN112818309A (zh) 数据访问权限的控制方法、装置以及存储介质
CN109417501B (zh) 网络资源的编排方法和设备
WO2016131171A1 (zh) 一种针对vnf包进行操作的方法及装置
CN105094996A (zh) 基于动态权限验证的Android系统安全增强方法及系统
CN107426152A (zh) 云平台虚实互联环境下多任务安全隔离系统及方法
WO2015127603A1 (zh) 一种接口管理服务实体、功能服务实体及网元管理方法
WO2021147358A1 (zh) 一种网络接口的建立方法、装置及系统
WO2021238718A1 (zh) 一种响应方法、确定方法、装置、设备及介质
Kotulski et al. New security architecture of access control in 5G MEC
CN108881460B (zh) 一种云平台统一监控的实现方法和实现装置
WO2021103657A1 (zh) 网络操作方法、装置、设备和存储介质
Naik et al. Workload monitoring in hybrid clouds
EP3893437B1 (en) Method and device for deploying virtual network function
CN116134857A (zh) 基于服务的管理框架的接入控制
CN105763532A (zh) 一种登录虚拟桌面的方法及装置

Legal Events

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

Ref document number: 21813907

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21813907

Country of ref document: EP

Kind code of ref document: A1