WO2017211161A1 - 基于软件定义网络的资源管理方法及装置 - Google Patents

基于软件定义网络的资源管理方法及装置 Download PDF

Info

Publication number
WO2017211161A1
WO2017211161A1 PCT/CN2017/083999 CN2017083999W WO2017211161A1 WO 2017211161 A1 WO2017211161 A1 WO 2017211161A1 CN 2017083999 W CN2017083999 W CN 2017083999W WO 2017211161 A1 WO2017211161 A1 WO 2017211161A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
user
network
request
resource management
Prior art date
Application number
PCT/CN2017/083999
Other languages
English (en)
French (fr)
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 WO2017211161A1 publication Critical patent/WO2017211161A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic

Definitions

  • This application relates to, but is not limited to, the field of communication technology.
  • SDN Software Defined Network
  • OpenFlow OpenFlow
  • the management mode of the related technology is relatively extensive, so that all users manage the network resources in the same management manner. This method may cause some users to fail to manage the resources they need, causing inconvenience to the users, even giving them Some economic losses are caused; and some users will configure network resources that they do not need because of improper management methods, resulting in wasted precious network resources.
  • the network resource management scheme of related technologies carries out resource management in a relatively general manner, which causes a problem of wasted resources.
  • the SDN-based network resource management scheme in the related art allows the user to touch the network resource management, but since the management scheme is not set based on the users participating in the management, it may cause waste of expensive network resources and reduce resource utilization. .
  • This paper provides a resource management method and device based on software-defined network to solve the technical problem that the network resources are wasted and the resource utilization rate is low when the user participates in the network resource management without considering the difference of each user. .
  • a resource management method based on a software defined network comprising:
  • Corresponding execution policies are matched according to the user type and the object from a preset resource management rule;
  • the resource management rule includes: an execution policy corresponding to a different type of user requesting to manage different objects;
  • the object is processed according to the matching execution policy.
  • the user type includes an administrator user and a common user, where the object includes a user information resource and a network resource, and the execution policy includes performing the user information resource. Policy and network resource execution strategy.
  • the execution policy corresponding to the administrator user requesting management of the user information resource includes one or more of the following:
  • the resource management request initiated by the administrator user to the user information resource is a creation request
  • the corresponding creation operation is performed according to the information carried in the creation request
  • the resource management request initiated by the administrator user to the user information resource is a deletion request, performing a corresponding deletion operation according to the information carried by the deletion request;
  • the resource management request initiated by the administrator user to the user information resource is a query request, performing a corresponding query operation according to the information carried by the query request;
  • the resource management request initiated by the administrator user for the user information resource is a modification request
  • the corresponding modification operation is performed according to the information carried by the modification request.
  • the execution policy corresponding to the normal user requesting to manage the user information resource includes one of the following Kind or more:
  • the resource management request initiated by the ordinary user to the user information resource is a creation request or a deletion request, the corresponding creation or deletion operation is prohibited;
  • the resource management request initiated by the common user to the user information resource is a query request, determining whether the object to be queried is the ordinary user itself, and determining that the object to be queried is the ordinary user itself And performing a query operation and feeding back the user information of the ordinary user, and when it is determined that the object to be queried is not the ordinary user itself, prohibiting the performing the query operation;
  • the modification operation is performed.
  • the modification operation is prohibited.
  • the execution policy corresponding to the administrator user requesting to manage the network resource includes one or more of the following:
  • the resource management request initiated by the administrator user is a network resource application request, and is used to determine whether the basic resource of the to-be-applied resource has been configured for the common user when the network resource is applied for the common user; When it is determined that the configuration is performed, the network resource to be applied is configured for the common user according to the network resource application request; when it is determined that the configuration is not configured, the application operation is prohibited;
  • the resource management request initiated by the administrator user is a network resource release request, and is used to determine, when the network user releases the network resource, whether the common user has released the bearer resource deployed on the to-be-released resource. When it is determined that the network resource has been released, the network resource to be released is released; when it is determined that the release is not released, the release operation is prohibited;
  • the resource management request initiated by the administrator user is a network resource query request or a network resource modification request
  • the corresponding query or modify operation is performed according to the information carried by the network resource query request or the network resource modification request.
  • the common use The execution policy corresponding to the user requesting management of network resources includes one or more of the following:
  • determining, by the common user, that the resource management request initiated by the network resource is a network resource application request, determining whether the common user has configured the basic resource of the to-be-applied resource;
  • the network resource application request is configured to configure the network resource to be applied for the common user; when it is determined that there is no configuration, the application operation is prohibited;
  • the resource management request initiated by the common user for the network resource is a network resource release request, it is determined whether the common user has released the bearer resource deployed on the to-be-released resource; when it is determined that the resource has been released Release the network resource to be released; when it is determined that there is no release, the release operation is prohibited;
  • the resource management request initiated by the common user for the network resource is a network resource query request or a network resource modification request
  • the corresponding query or modification operation is performed according to the information carried by the network resource query request or the network resource modification request.
  • the basic resource of the port resource is a port;
  • the basic resource of the port is a node;
  • the bearer resource of the node is a port; when the to-be-released resource is a port, the bearer resource of the port is a port resource.
  • the method further includes:
  • Determining whether the network resource to be applied for is a line-side resource, and determining that the network resource to be applied is not the line-side resource, directly determining whether the resource to be applied for the common user has been configured.
  • a resource when it is determined that the network resource to be applied is the line side resource, determining whether the network resource to be applied for is a group user application in the ordinary user; when determining that the ordinary user is When the group user is applying, it is determined whether the basic resource of the to-be-applied resource has been configured for the common user, and when it is determined that the application is not for the group user of the ordinary user, the application operation is prohibited.
  • a resource management device based on a software defined network comprising:
  • the request receiving module is configured to: receive a resource management request initiated by the user, where the resource management request includes a user type and an object requested by the user to be managed;
  • the policy determining module is configured to: match the user type received by the request receiving module and the object to the corresponding execution policy from the preset resource management rule; the resource management rule includes: The execution strategy corresponding to the management of different objects;
  • the resource management module is configured to: process the object according to an execution policy matched by the policy determining module.
  • the user type includes an administrator user and a common user
  • the object includes a user information resource and a network resource
  • the execution policy includes performing the user information resource. Policy and network resource execution strategy.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions for executing the software defined network based resource according to any of the foregoing Management method.
  • the software-defined network-based resource management method and device obtaineds a user type and a user request management object from the resource management request by receiving a resource management request initiated by the user, and pre-requires according to the user type and the object.
  • the resource management rule is matched with an execution policy corresponding to the resource management request of the user, and then the object requested by the user is processed according to the determined execution policy. Since the execution policy is determined according to the user type, the resource-defined network-based resource management method provided by the embodiment of the present invention allows different types of users to manage resources in different ways, taking into account differences between users, and allowing participating resources.
  • the managed users can manage the network resources according to the management scheme adapted to their needs, avoiding the waste of resources caused by the general management in the related technologies, reducing the waste of network resources and improving the utilization of resources.
  • FIG. 1 is a flow chart of a resource management method based on a software-defined network according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a resource management device based on a software-defined network according to an embodiment of the present invention
  • FIG. 3 is a flowchart of another resource-based network-based resource management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • the embodiment of the present invention provides a resource management based on a software-defined network.
  • the method as shown in FIG. 1 is a flowchart of a resource management method based on a software-defined network according to an embodiment of the present invention.
  • the method provided in this embodiment may include the following steps, that is, S101-S103:
  • the information included in the resource management request initiated by the user includes a user type and an object that the user requests to manage.
  • the user in order to implement different management of resources by different types of users, the user may be divided into an administrator user and an ordinary user. Alternatively, the ordinary user may be classified into a group user and a tenant user. .
  • the resource management method based on the software-defined network provided by the embodiment of the present invention can be implemented on the SDN controller, and the resource management request of the administrator user or the ordinary user can be delivered through the northbound interface of the SDN controller.
  • the northbound interface is the interface for the manufacturer or operator to access and manage the network, that is, the interface provided upward.
  • the format of the resource management request may adopt a JavaScript object notation (JavaScript Object Notation, referred to as: JSON) Data Format
  • JSON is a lightweight data exchange format based on a subset of the European Computer Manufacturers Association (ECMA) Script.
  • JSON uses a completely language-independent text format, but also uses a habit similar to the C language family (including C, C++, C#, Java, JavaScript, Perl, Python, etc.), which makes JSON an ideal data exchange language.
  • related information may be recorded by using a character string.
  • the user type may include an administrator user and a normal user, and the division between the administrator user and the ordinary user is based on different rights that the two have in resource management. Since the execution policy is determined according to resource management rules, it includes different types of user requests to manage execution strategies corresponding to different objects. Therefore, even if the object managed by the administrator user and the normal user initiated the resource management request is the same, the determined execution policy will not be the same because the user types of the two are different.
  • the resources that the user can manage include at least two types of network resources and user information resources, and the network resources include, for example, a node, a port, a port resource, a link, a link resource, and the like.
  • the user information resources include, for example, ordinary users in the network, that is, group users and tenant users.
  • the resource management policy may include at least two network resource execution policies for managing network resources according to the resource management request of the user, and user information execution policies for managing user information resources according to the resource management request of the user. .
  • the administrator user can create, delete, query, and modify the information of the ordinary user, that is, the user information resource, and the resource management request sent by the administrator user from the northbound interface is
  • the user information resource performs any of the foregoing management modes
  • the corresponding operation may be performed according to the related information carried in the resource management request delivered by the administrator user.
  • the resource management request includes a method of request management, that is, management of the creation type.
  • the resource management request may also include related to the user to be created. Information, for example, the user name, password, user level, user type, etc. of the user to be created.
  • the corresponding resource management request may be directly initiated, and the software-defined network-based resource management method provided by the embodiment of the present invention may be run.
  • a device such as an SDN controller, responds to these resource management requests.
  • the user information resource and the network resource are included in the resource that the user can manage, but for the administrator user, in addition to managing the user information resource of the ordinary user, You can also manage some of it yourself. It can be understood that although an administrator user can manage the creation, deletion, modification, and query of an ordinary user, an administrator user cannot perform the above operation on another administrator user, and the administrator user can only perform the above operation. If the information is changed, the user's password can be modified. The administrator user's operation on other administrator users or other operations on the user is illegal.
  • the user type may further include a super administrator, and the super administrator may perform operations such as creating, querying, deleting, and modifying the administrator user.
  • the administrator user can apply for network resources, release network resources, modify network resources, and query the network resources of common users or the remaining network topology by issuing resource management requests. Resources.
  • the resource management request initiated by the administrator user is a network resource application request, and the network resource application request is carried in the network resource request request.
  • the type of the network resource to be applied for example, the network resource to be applied for is a node, a port or a port resource, or a link resource. It can be understood that since the link is the path between the two ports, the link resources can be represented by the port and port resources at both ends of the link, even when displayed to the user as the link and link resources. Form, but in the underlying resource management, the link and link resources are essentially port and port resources.
  • a node is a basic resource of a port
  • a port is a basic resource of a port resource
  • a port is a bearer resource of a node
  • a port resource is deployed on a port
  • the port is A resource is a bearer resource for a port.
  • the resource management request initiated by the administrator user is a network resource application request, and you want to apply for a certain type of network resource for a common user, first determine whether the common user has been configured.
  • the basic resource of the resource to be applied for when it is determined that the network resource request is configured, the network resource to be applied is configured for the common user according to the network resource application request; when it is determined that the configuration is not configured, the application operation is prohibited.
  • the network resource to be applied for is a port resource, it is first determined whether the ordinary user has applied for the node.
  • the ordinary user has applied for the node, it is determined whether it has applied for the port that deploys the port resource, if If the user has not applied for a node or a port, the current user does not have the requirement to apply for the port resource.
  • the execution policy determined at this time should prohibit the ordinary user from applying for the network resource, and at the same time, it can also be sent from the northbound interface.
  • the administrator user of the resource management request returns a prompt message to inform the administrator that the user should apply for the network resources of the preset resource structure and the network resources to be applied for.
  • the initiated resource management request is a network resource release request.
  • the SDN controller needs to first determine whether the ordinary user has released the deployment. The bearer resource on the resource is released; when it is determined that the network resource is released, the network resource to be released is released; when it is determined that the release is not released, the release operation is prohibited. For example, if the network resource to be released is a node, the ports deployed on the node should be released first. To release each port, all port resources deployed on each port should be released first.
  • the administrator user desires to query or modify the network resource, and may directly request the resource management according to the resource management request.
  • the information carried in the query performs the query operation.
  • the resource management request of the query type may include a Uniform Resource Locator (URL) of the network resource to be queried, and the URL information may include node information, port information, and resource ID of the network resource to be queried.
  • URL Uniform Resource Locator
  • an administrator may require an administrator user to allocate a corresponding resource when creating a normal user. In this case, the administrator user needs to query the remaining resources in the network topology.
  • the user information resource thereof The administrative authority is lower than the administrator user.
  • the administrator user can create and delete ordinary users.
  • the execution policy may be prohibited from executing the corresponding creation. Or delete the operation.
  • the resource management request initiated by the ordinary user from the northbound interface is to query the user information resource, it is necessary to determine whether the object to be queried is the ordinary user itself, and when it is determined that the object to be queried is the ordinary user itself, execute the query.
  • the user information of the ordinary user is operated and fed back. When it is determined that the object to be queried is not the ordinary user itself, the query operation is prohibited.
  • an ordinary user When an ordinary user initiates a modification request to the user information resource, it determines whether the object to be modified is its own user password. When it is determined that the object to be modified is the user password of the ordinary user, the modification operation is performed, and when it is determined that the object to be modified is to be modified When the object is not the user password of the ordinary user, the modification operation is prohibited.
  • the way in which ordinary users manage user information resources is similar to how administrator users manage administrator users.
  • a resource management request initiated by a common user for a network resource is a request for a network resource request, the same as the administrator's request for the application, the basic resource of the resource to be applied is also determined.
  • the network resource to be applied is configured for the common user according to the network resource application request; when it is determined that there is no configuration, the application operation is prohibited.
  • the resource management request initiated by the common user for the network resource is a network resource release request
  • the ordinary user requests for the network resource and the release request are similar. The biggest difference is that the keyword in the resource management request changes.
  • the resource management request initiated by the ordinary user for the network resource is a network resource query or modification request
  • the corresponding query or modification operation is performed according to the information carried in the resource management request.
  • the resource modification is not modifying the resource of the application itself, but modifying the description information of the resource; for example, when the resource management request initiated by the user is to modify the network resource, the resource management request may include Resource name, resource number, resource type, user name, etc.
  • the user may also include the following processing manner: determining whether the network resource to be applied for is a line side resource. Because the line side resources are special, only the group users have the right to apply for the line side resources. Therefore, when it is determined that the network resource to be applied for is not the line side resource, the current network resources to be applied are not special, and any type of common The user can apply for the application, so the application can be performed directly according to the information carried in the resource management request.
  • the network resource to be applied for is a line-side resource
  • the user applies; when it is determined that the application is for the group user of the ordinary user, the subsequent judgment process is performed, that is, whether the basic resource of the resource to be applied for the ordinary user has been configured, and when it is determined that the group is not the ordinary user, When the user applies, it is forbidden to perform the application operation.
  • the ordinary user when an administrator user or a normal user initiates an application request for a network resource, for example, when an administrator user creates a normal user, the ordinary user may be allocated according to an operator's request. Resources, at this time, it is necessary to determine whether the remaining network resources in the network meet the application request of the administrator user, that is, whether the network can provide the network resources to be applied, and when it is judged that the network resources can be satisfied, the application operation is performed, and when it is determined that the application cannot be performed, When it is satisfied, it is forbidden to perform the application operation. For example, it is determined whether the bandwidth requested by the ordinary user is less than the bandwidth reserved by the port, or whether the applied time slot is smaller than the time slot remaining in the port, and if the determination result is no, the application operation is prohibited.
  • the resource management request sent by the user may be responded to according to the corresponding execution policy, and the object of the request management carried in the resource management request is processed accordingly.
  • the resource management method based on the software-defined network obtaineds the user type and the object requested by the user from the resource management request by receiving the resource management request initiated by the user, and according to the user type in the resource management request And the object that the user requests to manage matches the corresponding execution policy from the preset resource management rule, and then processes the object that the user requests to manage according to the matching execution policy; the method provided by the embodiment of the present invention allows different types of users Different ways of managing resources, taking into account the differences between users, allowing users involved in resource management to manage network resources according to the management scheme adapted to their needs, avoiding the waste of resources caused by general management in related technologies. Problem, improve the utilization of resources, and thus reduce the network The operating costs of the network resources.
  • the device provided by the embodiment of the present invention can provide a resource-based network-based resource management method according to any embodiment shown in FIG.
  • the resource management device 20 of the software-defined network provided by the embodiment of the present invention includes a request receiving module 201, a policy determining module 202, and a resource management module 203.
  • the request receiving module 201 is configured to: receive a resource management request initiated by the user.
  • the information included in the resource management request initiated by the user includes a user type and an object that the user requests to manage.
  • the user in order to implement different management of resources by different types of users, the user may be divided into an administrator user and an ordinary user. Alternatively, the ordinary user may be classified into a group user and a tenant user. .
  • the resource management device 20 based on the software-defined network provided by the embodiment of the present invention can be deployed on the SDN controller, and the resource management request of the administrator user or the ordinary user can be delivered through the northbound interface of the SDN controller.
  • the request receiving module 201 can also naturally receive a resource management request initiated by each user from the northbound interface.
  • the northbound interface is the interface for the manufacturer or operator to access and manage the network, that is, the interface provided upward.
  • the format of the resource management request received by the request receiving module 201 may adopt a JSON (JavaScript Object Notation) data format, and the JSON is a lightweight data exchange format, which is based on one of ECMA Script. Subset.
  • JSON uses a completely language-independent text format, but also uses a habit similar to the C language family (including C, C++, C#, Java, JavaScript, Perl, Python, etc.), which makes JSON an ideal data exchange language.
  • the related request information of the user may be recorded by using a character string.
  • the policy determining module 202 is configured to: match the corresponding execution policy from the preset resource management rule according to the user type and the object received by the request receiving module 201; the resource management rule includes: when different types of users request to manage different objects The corresponding execution strategy.
  • the user type may include an administrator user and a normal user, and the division between the administrator user and the ordinary user is based on the resource management. Different permissions.
  • the execution policy matched by the policy determination module 202 is determined according to the resource management rule, and includes an execution policy corresponding to different types of users requesting management of different objects. Therefore, even if the object managed by the administrator user and the normal user initiated the resource management request is the same, the determined execution policy will not be the same because the user types of the two are different.
  • the resources that the user can manage include at least two types of network resources and user information resources, and the network resources include, for example, a node, a port, a port resource, a link, a link resource, and the like.
  • the user information resources include, for example, ordinary users in the network, that is, group users and tenant users.
  • the resource management policy may include at least two network resource execution policies for managing network resources according to the resource management request of the user, and user information execution policies for managing user information resources according to the resource management request of the user. .
  • the administrator user can create, delete, query, and modify the information of the ordinary user, that is, the user information resource, and the resource management request sent by the administrator user from the northbound interface is
  • the user information resource performs any of the foregoing management modes
  • the corresponding operation may be performed according to the related information carried in the resource management request delivered by the administrator user.
  • the resource management request includes a method of request management, that is, management of the creation type.
  • the resource management request may further include related information of the user to be created, for example, a user name, a password, a user level, a user type, and the like of the user to be created.
  • related information of the user to be created for example, a user name, a password, a user level, a user type, and the like of the user to be created.
  • the corresponding resource management request may be directly initiated.
  • the user information resource and the network resource are included in the resource that the user can manage, but for the administrator user, in addition to managing the user information resource of the ordinary user, You can also manage some of it yourself. It can be understood that although an administrator user can manage the creation, deletion, modification, and query of an ordinary user, an administrator user cannot perform the above operation on another administrator user, and the administrator user can only perform the above operation. If the information is changed, it can only be used for its own user password. Modification, the administrator user's operation on other administrator users or other operations on itself is illegal.
  • the user type may further include a super administrator, and the super administrator may perform operations such as creating, querying, deleting, and modifying the administrator user.
  • the administrator user can apply for network resources, release network resources, modify network resources, and query common network resources or remaining resources in the network topology for common users.
  • the resource management request initiated by the administrator user is a network resource application request, and the network resource application request is carried in the network resource request request.
  • the type of the network resource to be applied for example, the network resource to be applied for is a node, a port or a port resource, or a link, a link resource, or the like. It can be understood that since the link is the path between the two ports, the link and link resources can be represented by the port and port resources at both ends of the link, even when displayed to the user as a link and a link.
  • the form of road resources, but in the management of the underlying resources, the link and link resources are essentially port and port resources.
  • a port is a basic resource of a port
  • a port is a basic resource of a port resource
  • a port is a bearer resource of a node
  • a port resource is deployed on a port
  • the port resource is a bearer resource of the port.
  • the resource management request sent by the administrator user is a network resource application request, and you want to apply for a certain type of network resource for a common user, first determine whether the ordinary user has been configured.
  • the network resource to be applied for is a port resource, it is first determined whether the ordinary user has applied for the node.
  • the ordinary user has applied for the node, it is determined whether it has applied for the port that deploys the port resource, if If the user has not applied for a node or a port, the current user does not have the requirement to apply for the port resource.
  • the execution policy determined at this time should prohibit the ordinary user from applying for the network resource, and at the same time, it can also be sent from the northbound interface.
  • the administrator user of the resource management request returns a prompt message to inform the administrator user You should first apply to the common user for each network resource in the preset resource structure that is above the network resources to be applied for.
  • the initiated resource management request is a network resource release request.
  • the SDN controller needs to first determine whether the ordinary user has released the deployment. The bearer resource on the resource is released; when it is determined that the network resource is released, the network resource to be released is released; when it is determined that the release is not released, the release operation is prohibited. For example, if the network resource to be released is a node, the ports deployed on the node should be released first. To release each port, all port resources deployed on each port should be released first.
  • the administrator user desires to query or modify the network resource, and may directly request the resource management according to the resource management request.
  • the information carried in the query performs the query operation.
  • the resource management request of the query type may include a URL of the network resource to be queried, and the URL information may include node information, port information, and resource ID of the network resource to be queried. It can be understood that an administrator may require an administrator user to allocate a corresponding resource when creating a normal user. In this case, the administrator user needs to query the remaining resources in the network topology.
  • the management authority for the user information resource is lower than that of the administrator user, for example, the administrator user can create and delete the ordinary user, but the ordinary user initiates the resource management request.
  • the execution strategy may be to prohibit the execution of the corresponding creation or deletion.
  • an ordinary user When an ordinary user initiates a modification request to the user information resource, it determines whether the object to be modified is its own user password. When it is determined that the object to be modified is the user password of the ordinary user, the modification operation is performed, and when it is determined that the object to be modified is to be modified When the object is not the user password of the ordinary user, the modification operation is prohibited.
  • the way in which ordinary users manage user information resources is similar to how administrator users manage administrator users.
  • a resource management request initiated by a common user for a network resource is a request for a network resource request, the same as the administrator's request for the application, the basic resource of the resource to be applied is also determined.
  • the network resource to be applied is configured for the common user according to the network resource application request; when it is determined that there is no configuration, the application operation is prohibited.
  • the resource management request initiated by the common user for the network resource is a network resource release request
  • the ordinary user requests for the network resource and the release request are similar. The biggest difference is that the keyword in the resource management request changes.
  • the resource management request initiated by the ordinary user for the network resource is a network resource query or modification request
  • the corresponding query or modification operation is performed according to the information carried in the resource management request.
  • the resource modification is not modifying the resource of the application itself, but modifying the description information of the resource; for example, when the resource management request initiated by the user is to modify the network resource, the resource management request may include Resource name, resource number, resource type, user name, etc.
  • the method may further include: determining whether the network resource to be applied for is a line-side resource. Because the line side resources are special, only the group users have the right to apply for the line side resources.
  • the current network resources to be applied are not special, and any type of common
  • the user can apply for the application, so the application can be performed directly according to the information carried in the resource management request.
  • the network resource to be applied for is a line-side resource
  • it is necessary to determine whether the network resource to be applied is a group of ordinary users.
  • the user applies; when it is determined that the application is for the group user of the ordinary user, the subsequent judgment process is performed, that is, whether the basic resource of the resource to be applied for the ordinary user has been configured, and when it is determined that the group is not the ordinary user, When the user applies, it is forbidden to perform the application operation.
  • the ordinary user may be allocated resources according to the requirements of the operator.
  • the resource management device 20 based on the software-defined network needs to determine the remaining network resources in the network. Whether the application request of the administrator user is satisfied, that is, whether the software-defined network can provide the network resource to be applied, and when it is judged that the application can be satisfied, the application operation is performed, and when it is determined that the application cannot be satisfied, the application operation is prohibited. For example, it is determined whether the bandwidth requested by the ordinary user is less than the bandwidth reserved by the port, or whether the applied time slot is smaller than the time slot remaining in the port, and if the determination result is no, the application operation is prohibited.
  • the resource management module 203 is configured to process the object requested by the user according to the execution policy matched by the policy matching module 202.
  • the resource management request sent by the user may be responded to according to the corresponding execution policy, and the object of the request management carried in the resource management request is processed accordingly.
  • the resource management device based on the software-defined network provided by the embodiment of the present invention may be deployed in an SDN controller, and the SDN controller deployed with the resource management device based on the software-defined network may be run on the terminal or the server, where the request receiving module is 201.
  • the functions of the policy determination module 202 and the resource management module 203 can be implemented by a processor in a terminal or a server. After receiving the resource management request sent by the user, the processor determines an execution policy corresponding to the resource management request according to the type of the user that initiated the request and the object that is requested to be managed in the resource management request, and then the processor is matched according to the The execution strategy manages the objects requested by the user.
  • the embodiment of the present invention provides a resource management device based on a software-defined network.
  • the request receiving module 201 receives a resource management request initiated by a user, and obtains an object type and a user request management object from the resource management request, and is determined by the policy determining module 202 according to the policy.
  • the user type in the resource management request received by the request receiving module 201 and the object requested by the user request match the corresponding execution policy from the preset resource management rule, and then the resource management module 203 determines the execution policy pair matched by the policy determining module 202.
  • the user requests the managed object to be processed; the device provided by the embodiment of the present invention allows the users participating in the resource management to adapt to the requirements by allowing different types of users to manage the resources in different ways, taking into account the differences between the users.
  • the management plan manages network resources, avoids the waste of resources caused by general management in related technologies, and improves resources. Utilization, which in turn reduces the operating costs of network resources.
  • FIG. 3 it is a flowchart of another resource-based network-based resource management method according to an embodiment of the present invention.
  • the process of creating, deleting, querying, and modifying common users is similar.
  • the process shown in Figure 3 is based on the case where the resource management request initiated by the administrator user is used to create the user information resource.
  • the method provided in this embodiment includes the following steps, namely, S301 to S305:
  • the resource management device based on the software-defined network in this embodiment may be deployed in the SDN controller, and the resource management request of the administrator user may be sent in the northbound interface of the SDN controller, and the delivered data is in the JSON format.
  • the resource management request includes, for example, information such as a user name, a password, a user level, and a user type of the ordinary user to be created.
  • the administrator user wants to create a user with the user name A, the user password of 12212, the user level of 02, the user type is 001, the resource ID number is 01, and the resource type is 01.
  • the administrator user is on the SDN controller.
  • the resource management request delivered by the northbound interface can be referred to the following form:
  • the data sent by the administrator user from the northbound interface of the SDN controller is in ISON format
  • the data in JSON format needs to be converted into internal data that the SDN controller can recognize.
  • the type of the user who issues the resource request is an administrator user, and what kind of management operation the user desires to perform.
  • the SDN controller obtains the type of the user to which the request is issued is the administrator user type according to the resource management request issued by the administrator user, and the object that the user requests to manage is to create the user information resource. Based on these two pieces of information, the SDN controller can match the corresponding execution policy from the preset resource management rules.
  • the SDN controller may have to perform the following judgment processes:
  • the SDN controller determines if the user has permission to create a normal user.
  • the resource management request does not include the information of the resource application, it may be determined at this time that the execution policy is to allow the user to perform the creation process. However, since the resource management request further includes information for allocating resources for the user to be created, it is also determined whether the resource to be allocated is a line side resource, because the line side resource is special, and only the group user has the application for the line side resource. permission.
  • the application operation can be directly performed according to the information carried in the resource management request;
  • the resource to be allocated is a line-side resource, it is required to determine whether the network resource to be applied for is a group user in the ordinary user; and when it is determined that the network resource to be applied for is a group user in the ordinary user, the application operation is performed.
  • the application operation is prohibited.
  • the resource management request performs corresponding processing on the object of the request management carried in the resource management request.
  • FIG. 4 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • the application layer there are an application (Application, abbreviated as: APP) 411 and a Hypertext Transfer Protocol (abbreviated as: HTTP) protocol stack 412.
  • the APP is installed on the terminal device 410.
  • the terminal device 410 can be a personal computer (PC), a tablet computer, a mobile phone, a personal digital assistant (PDA), etc., and the terminal device 410 can include a display.
  • the screen can be used to display the visual interface of the APP. All operations of the user in this embodiment, such as an administrator user or a normal user, are completed on the APP.
  • the terminal device 410 communicates with other terminal devices or servers deploying the SDN controller 420 in this embodiment through the HTTP protocol 412.
  • an HTTP protocol stack (412 or 421) is provided. Used to create a session between the application layer and the control layer, transferring data between the two.
  • the Representational State Transfer Stub (REST STUB) module 422 is mainly to complete the adaptation between data.
  • the User Management (URM) module 423 is mainly for user management.
  • the resource management device based on the software-defined network provided by the embodiment of the present invention obtains the user type of the request by parsing the information in the received resource management request, and determines, according to the user type and the object that the user requests to manage,
  • the execution strategy of the resource management request takes into account the differences between users, so that users participating in resource management can manage network resources according to the management scheme adapted to their needs, thereby avoiding waste of resources caused by general management in related technologies.
  • the problem is to improve the utilization of resources, thereby reducing the operating costs of network resources.
  • the embodiment of the invention further provides a computer readable storage medium, where the computer readable storage medium stores computer executable instructions, which are executed by the processor to implement the following steps:
  • the corresponding execution policy is matched from the preset resource management rule according to the user type and the object;
  • the resource management rule includes: an execution strategy corresponding to when different types of users request to manage different objects;
  • the user type may include an administrator user and a common user, where the object includes a user information resource and a network resource, and the execution policy includes a user information resource execution policy and a network resource execution policy.
  • the implementation manner of the execution policy corresponding to the user type and the object in the embodiment of the present invention is related to the actual application scenario in which the different user types request to manage different objects, which has been described in detail in the foregoing embodiment of the present invention, and therefore is no longer Narration.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the present invention obtains the user type and the object requested by the user from the resource management request by receiving the resource management request initiated by the user, and matches the resource of the user from the preset resource management rule according to the user type and the object.
  • the execution policy corresponding to the request is managed, and then the object requested by the user is processed according to the determined execution policy. Since the execution policy is determined according to the user type, the resource-defined network-based resource management method provided by the embodiment of the present invention allows different types of users to manage resources in different ways, taking into account differences between users, and allowing participating resources.
  • the managed users can manage the network resources according to the management scheme adapted to their needs, avoiding the waste of resources caused by the general management in the related technologies, reducing the waste of network resources and improving the utilization of resources.

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

一种基于软件定义网络的资源管理方法及装置，其中，该基于软件定义网络的资源管理方法包括：接收用户发起的资源管理请求，该资源管理请求中包括用户类型和用户请求管理的对象，并根据用户类型和对象从预设的资源管理规则中匹配出与该用户类型的资源管理请求对应的执行策略，然后根据匹配到的执行策略对用户请求管理的对象进行处理。

Description

基于软件定义网络的资源管理方法及装置 技术领域
本申请涉及但不限于通信技术领域。
背景技术
随着互联网业务的快速发展，网络变得越来越拥堵和低效，如何有效降低网络运行成本、提高网络资源利用率变成了用户和运营商共同关注的问题。要提高网络资源的利用率，就应当实现资源按需分配。但在相关技术的网络架构中，普通用户几乎无法参与网络资源管理，网络资源对于普通用户来说是封闭的，用户只能使用运营商配置给自己的资源。
为了让用户参与资源管理，需要引入开放式的网络体系结构，例如软件定义网络(Software Defined Network，简称为：SDN)体系。SDN是一种新型网络创新架构，其核心技术开放流(OpenFlow)通过使用控制器将网络控制平面与数据平面分离开来，从而实现了网络流量的灵活控制，为核心网络及其应用的创新提供了良好的平台。
在相关技术的SDN体系当中，允许用户对网络资源进行管理，以实现资源的动态分配。但是相关技术的管理模式比较粗放，让所有的用户都以相同的管理方式对网络资源进行管理，这种方式可能会导致部分用户无法对其需要的资源进行管理，造成用户的不便，甚至给其造成一些经济上的损失；而部分用户又会因为管理方式的不当而为自己配置并不需要的网络资源，导致珍贵的网络资源被浪费。总体来说，相关技术的网络资源管理方案进行资源管理的方式比较笼统，会造成在资源浪费的问题。
因此，相关技术中基于SDN的网络资源管理方案虽然允许用户可以触及网络资源管理，但因为管理方案没有基于参与管理的用户来设置，所以可能会造成昂贵网络资源的浪费，降低了资源的利用率。
发明概述
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种基于软件定义网络的资源管理方法及装置，以解决相关技术中让用户参与网络资源管理的时候没有考虑到各用户的差异性而导致了网络资源浪费，资源利用率低的技术问题。
一种基于软件定义网络的资源管理方法，包括：
接收用户发起的资源管理请求，所述资源管理请求包含用户类型和用户请求管理的对象；
根据所述用户类型和所述对象从预设的资源管理规则中匹配出对应的执行策略；所述资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
根据匹配到的执行策略对所述对象进行处理。
可选地，如上所述的基于软件定义网络的资源管理方法中，所述用户类型包括管理员用户和普通用户，所述对象包括用户信息资源和网络资源，所述执行策略包括用户信息资源执行策略和网络资源执行策略。
可选地，如上所述的基于软件定义网络的资源管理方法中，所述管理员用户请求对用户信息资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
所述管理员用户对所述用户信息资源发起的所述资源管理请求为创建请求时，根据所述创建请求所携带的信息执行相应的创建操作；
所述管理员用户对所述用户信息资源发起的所述资源管理请求为删除请求时，根据所述删除请求所携带的信息执行相应的删除操作；
所述管理员用户对所述用户信息资源发起的所述资源管理请求为查询请求时，根据所述查询请求所携带的信息执行相应的查询操作；
所述管理员用户对所述用户信息资源发起的所述资源管理请求为修改请求时，根据所述修改请求所携带的信息执行相应的修改操作。
可选地，如上所述的基于软件定义网络的资源管理方法中，所述普通用户请求对用户信息资源进行管理时所对应的执行策略包括以下几种中的一 种或多种：
所述普通用户对所述用户信息资源发起的所述资源管理请求为创建请求或删除请求时，禁止执行相应的创建或删除操作；
所述普通用户对所述用户信息资源发起的所述资源管理请求为查询请求时，判断待查询的对象是否为所述普通用户本身，当判断出所述待查询的对象是所述普通用户本身时，执行查询操作并反馈所述普通用户的用户信息，当判断出所述待查询的对象不是所述普通用户本身时，禁止执行查询操作；
所述普通用户对所述用户信息资源发起的所述资源管理请求为修改请求时，判断待修改的对象是否为所述普通用户的用户密码，当判断出所述待修改的对象是所述普通用户的用户密码时，执行修改操作，当判断出所述待修改的对象不是所述普通用户的用户密码时，禁止执行修改操作。
可选地，如上所述的基于软件定义网络的资源管理方法中，所述管理员用户请求对网络资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
所述管理员用户发起的所述资源管理请求为网络资源申请请求，用于为所述普通用户申请网络资源时，判断是否已经为所述普通用户配置了所述待申请资源的基础资源；当判断出已经配置时，根据所述网络资源申请请求为所述普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作；
所述管理员用户发起的所述资源管理请求为网络资源释放请求，用于为所述普通用户释放网络资源时，判断所述普通用户是否已经释放了部署在所述待释放资源上的承载资源；当判断出已经释放时，释放所述待释放的网络资源；当判断出没有释放时，禁止执行释放操作；
所述管理员用户发起的所述资源管理请求为网络资源查询请求或网络资源修改请求时，根据所述网络资源查询请求或网络资源修改请求携带的信息执行相应的查询或修改操作。
可选地，如上所述的基于软件定义网络的资源管理方法中，所述普通用 户请求对网络资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
所述普通用户对所述网络资源发起的所述资源管理请求为网络资源申请请求时，判断所述普通用户是否已经配置了所述待申请资源的基础资源；当判断出已经配置时，根据所述网络资源申请请求为所述普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作；
所述普通用户对所述网络资源发起的所述资源管理请求为网络资源释放请求时，判断所述普通用户是否已经释放了部署在所述待释放资源上的承载资源；当判断出已经释放时，释放所述待释放的网络资源；当判断出没有释放时，禁止执行释放操作；
所述普通用户对所述网络资源发起的所述资源管理请求为网络资源查询请求或网络资源修改请求时，根据所述网络资源查询请求或网络资源修改请求携带的信息执行相应的查询或修改操作。
可选地，如上所述的基于软件定义网络的资源管理方法中，当所述待申请资源为端口资源时，所述端口资源的基础资源为端口；当所述待申请资源为端口时，所述端口的基础资源为节点；
当所述待释放资源为节点时，所述节点的承载资源为端口；当所述待释放资源为端口时，所述端口的承载资源为端口资源。
可选地，如上所述的基于软件定义网络的资源管理方法中，在接收所述管理员用户或所述普通用户对所述网络资源发起的网络资源申请请求之后，且在判断是否已经为所述普通用户配置了所述待申请资源的基础资源之前，所述方法还包括：
判断所述待申请的网络资源是否为线路侧资源，当判断出所述待申请的网络资源不是所述线路侧资源时，直接判断是否已经为所述普通用户配置了所述待申请资源的基础资源，当判断出所述待申请的网络资源是所述线路侧资源时，判断所述待申请的网络资源是否是为所述普通用户中的集团用户申请；当判断出是为所述普通用户中的集团用户申请时，判断是否已经为所述普通用户配置了所述待申请资源的基础资源，当判断出不是为所述普通用户中的集团用户申请时，禁止执行申请操作。
一种基于软件定义网络的资源管理装置，包括：
请求接收模块，设置为：接收用户发起的资源管理请求，所述资源管理请求包含用户类型和用户请求管理的对象；
策略确定模块，设置为：根据所述请求接收模块接收的所述用户类型和所述对象从预设的资源管理规则中匹配出对应的执行策略；所述资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
资源管理模块，设置为：根据所述策略确定模块匹配到的执行策略对所述对象进行处理。
可选地，如上所述的基于软件定义网络的资源管理装置中，所述用户类型包括管理员用户和普通用户，所述对象包括用户信息资源和网络资源，所述执行策略包括用户信息资源执行策略和网络资源执行策略。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行前述的任一项的基于软件定义网络的资源管理方法。
本发明实施例提供的基于软件定义网络的资源管理方法及装置，通过接收用户发起的资源管理请求，从资源管理请求中获取到用户类型和用户请求管理的对象，并根据用户类型和对象从预设的资源管理规则中匹配出与该用户的资源管理请求对应的执行策略，然后根据确定的执行策略对用户请求管理的对象进行处理。由于执行策略是根据用户类型确定的，所以本发明实施例提供的基于软件定义网络的资源管理方法可以让不同类型的用户对资源进行不同方式的管理，考虑到了用户间的差异性，让参与资源管理的用户都能根据与其需求适配的管理方案对网络资源进行管理，避免了相关技术中笼统管理所造成的资源浪费的问题，降低了网络资源的浪费，提高了资源的利用率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例提供的一种基于软件定义网络的资源管理方法的流 程图；
图2为本发明实施例提供的一种基于软件定义网络的资源管理装置的结构示意图；
图3为本发明实施例提供的另一种基于软件定义网络的资源管理方法的流程图；
图4为本发明实施例提供的一种SDN控制器的结构示意图。
详述
下文中将结合附图对本发明的实施方式进行详细说明。需要说明的是，在不冲突的情况下，本文中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸根据一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
为了解决相关技术中因资源管理方法没有考虑到各用户之间的差异性而造成了资源管理不合理，网络资源利用率低的技术问题，本发明实施例提供一种基于软件定义网络的资源管理方法，如图1所示，为本发明实施例提供的一种基于软件定义网络的资源管理方法的流程图，本实施例提供的方法可以包括如下步骤，即S101～S103：
S101、接收用户发起的资源管理请求。
在本发明实施例中，用户发起的资源管理请求中包括的信息有用户类型和用户请求管理的对象。在本发明实施例中，为了实现不同类型的用户对资源进行不同管理这一目的，可以将用户划分为管理员用户和普通用户，可选地，普通用户又可以被区分为集团用户和租户用户。
本发明实施例提供的基于软件定义网络的资源管理方法可以在SDN控制器上实施，无论是管理员用户还是普通用户的资源管理请求都可以通过SDN控制器的北向接口下发。北向接口是为厂家或运营商进行接入和管理网络的接口，即向上提供的接口。另外，在本发明实施例中，资源管理请求的格式可以采用JavaScript对象表示法(JavaScript Object Notation，简称为： JSON)数据格式，JSON是一种轻量级的数据交换格式，它基于欧洲计算机制造商协会(European Computer Manufacturers Association，简称为：ECMA)Script的一个子集。JSON采用完全独立于语言的文本格式，但是也使用了类似于C语言家族(包括C、C++、C#、Java、JavaScript、Perl、Python等)的习惯，这些特性使JSON成为理想的数据交换语言。本发明实施例的资源管理请求中可以通过字符串来记录相关信息。
S102、根据用户类型和对象从预设的资源管理规则中匹配出对应的执行策略。
根据上述介绍可知，在本发明实施例中，用户类型可以包括管理员用户和普通用户，管理员用户和普通用户的划分是基于二者在资源管理方面拥有的不同权限。由于执行策略是根据资源管理规则确定的，其中包含不同类型用户请求管理不同对象所对应的执行策略。因此，即使管理员用户和普通用户发起的资源管理请求中包含的请求管理的对象相同，但是由于这二者的用户类型不同，所以确定出来的执行策略也不会相同。
在本发明实施例中，用户可进行管理的资源至少可以包括网络资源和用户信息资源两种，网络资源例如包括节点、端口、端口资源、链路、链路资源等。而用户信息资源例如包括网络中的普通用户，即集团用户与租户用户。可选地，资源管理策略至少可以包括用于根据用户的资源管理请求对网络资源进行管理的网络资源执行策略和用于根据用户的资源管理请求对用户信息资源进行管理的用户信息执行策略两种。
为了便于说明，下面将分别通过管理员用户和普通用户对不同资源的管理进行描述：
可选地，在本发明实施例中，管理员用户可以对普通用户的信息(即用户信息资源)进行创建、删除、查询以及修改，当管理员用户从北向接口下发的资源管理请求是对用户信息资源进行上述管理方式中的任意一种时，可以根据管理员用户下发的资源管理请求中携带的相关信息执行相应的操作。例如，当管理员用户希望进行普通用户的创建时，在资源管理请求中除了会携带管理员用户的用户类型和管理对象以外，还会包括请求管理的方式，即创建类型的管理。当然，在资源管理请求当中还可以包括待创建用户的相关 信息，例如，待创建用户的用户名、密码、用户等级、用户类型等信息。再例如，当管理员用户需要对普通用户进行删除、查询或者修改等操作的时候，也可以直接发起对应的资源管理请求，由可以运行本发明实施例提供的基于软件定义网络的资源管理方法的装置，例如SDN控制器来对这些资源管理请求进行响应。
可选地，在本发明实施例中，将用户信息资源和网络资源纳入了用户可以进行管理的资源之中，但对于管理员用户来说，除了可以对普通用户的用户信息资源进行管理以外，还可以对其自身进行一些管理。可以理解的是，管理员用户虽然可以对普通用户进行创建、删除、修改、查询等方式的管理，但是一个管理员用户却不能对另一个管理员用户进行上述操作，管理员用户只能对其自身的信息进查询，若是修改信息，也只能对自身的用户密码进行修改，该管理员用户对其他管理员用户的操作或者对自身的其他操作都属于不合法操作。可选地，在本发明实施例的一些可能的实现方式中，用户类型还可以包括超级管理员，超级管理员可以对管理员用户进行创建、查询、删除、修改等操作。
当管理员用户对网络资源进行管理时，管理员用户可以通过下发资源管理请求来为普通用户申请网络资源、释放网络资源、修改网络资源以及查询普通用户的网络资源或网络拓扑结构中的剩余资源。
可选地，在本发明实施例中，如果管理员用户需要为普通用户申请网络资源，那么在管理员用户发起的资源管理请求则为网络资源申请请求，在网络资源申请请求当中，会携带待申请的网络资源的类型，例如待申请网络资源是节点、端口或者端口资源，又或者是链路资源等。可以理解的是，由于链路就是两个端口之间的通路，所以链路资源可以分别用链路两端的端口和端口资源来表示，即使展示给用户的时候是以链路和链路资源的形式，但是在底层资源管理上，链路和链路资源实质就是端口和端口资源。
网络资源的部署会遵循一些规律，例如，节点资源应当部署在节点上，端口资源应当部署在端口上，而端口又应当部署在节点上，这就是网络资源的部署要遵循预设资源架构。节点是端口的基础资源，端口是端口资源的基础资源；相应的，端口是节点的承载资源，端口资源部署在端口上，则端口 资源是端口的承载资源。
可选地，在本发明实施例中，如果管理员用户发起的资源管理请求是网络资源申请请求，想要为某一个普通用户申请某类型的网络资源，则首先要判断该普通用户是否已经配置了该待申请资源的基础资源；当判断出已经配置时，根据网络资源申请请求为普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作。例如，如果待申请的网络资源是端口资源，则要先判断该普通用户是否已经申请了节点，如果该普通用户已经申请了节点，则要判断其是否申请了部署该端口资源的端口，如果该普通用户还未申请节点或者端口，则其当前还不具备申请端口资源的条件，此时确定出来的执行策略应当是禁止该普通用户申请该网络资源，与此同时还可以从北向接口向下发资源管理请求的管理员用户返回提示信息，告知管理员用户应当先为该普通用户申请预设资源架构中、处于待申请的网络资源之上的各网络资源。
与网络资源申请流程类似，当管理员用户需要为普通用户释放资源管理请求的时候，发起的资源管理请求为网络资源释放请求，首先，SDN控制器需要先判断普通用户是否已经释放了部署在待释放资源上的承载资源；当判断出已经释放时，释放待释放的网络资源；当判断出没有释放时，禁止执行释放操作。例如，若待释放网络资源为节点，则应当先将部署在该节点上的各个端口都释放掉，而为了释放每一个端口，应当先释放部署在各个端口上的全部端口资源。
可选地，在本发明实施例中，如果管理员用户下发的资源管理请求是网络资源查询请求或网络资源修改请求，管理员用户期望对网络资源进行查询或者修改，可以直接根据资源管理请求中携带的信息执行查询操作。查询类型的资源管理请求中可以包含待查询网络资源的统一资源定位符(Uniform Resource Locator，简称为：URL)，在URL信息中可以包括待查询网络资源的节点信息、端口信息和资源ID等。可以理解的是，运营商可能会要求管理员用户在创建普通用户的时候就为其分配对应的资源，这时，管理员用户需要对网络拓扑结构中的剩余资源进行查询。
可选地，在本发明实施例中，对于普通用户而言，其对用户信息资源的 管理权限要低于管理员用户，例如管理员用户可以创建、删除普通用户，但是普通用户发起资源管理请求，请求进行普通用户的创建、删除的时候，得到的执行策略可能是禁止执行相应的创建或删除操作。而当普通用户从北向接口发起的资源管理请求是对用户信息资源进行查询的时候，需要判断待查询的对象是否为普通用户本身，当判断出待查询的对象是该普通用户本身时，执行查询操作并反馈普通用户的用户信息，当判断出待查询的对象不是该普通用户本身时，禁止执行查询操作。当普通用户对用户信息资源发起修改请求时，判断待修改的对象是否为其本身的用户密码，当判断出待修改的对象是该普通用户的用户密码时，执行修改操作，当判断出待修改的对象不是该普通用户的用户密码时，禁止执行修改操作。普通用户对用户信息资源的管理方式与管理员用户对管理员用户的管理方式类似。
可选地，在本发明实施例中，说明普通用户对网络资源的管理方式：
当普通用户对网络资源发起的资源管理请求为网络资源申请请求时，同管理员发起申请请求一样，也需要判断普通用户是否已经配置了该待申请资源的基础资源；当判断出已经配置时，根据网络资源申请请求为普通用户配置该待申请的网络资源；当判断出没有配置时，禁止执行申请操作。
当普通用户对网络资源发起的资源管理请求为网络资源释放请求时，判断普通用户是否已经释放了部署在待释放资源上的承载资源；当判断出已经释放时，释放待释放的网络资源；当判断出没有释放时，禁止执行释放操作。如果暂时还不满足资源释放的条件，则可以向普通用户发出提示信息，普通用户对网络资源的申请请求和释放请求类似，最大的不同在于资源管理请求中的关键字发生了变化。
当普通用户对网络资源发起的资源管理请求为网络资源查询或修改请求时，根据资源管理请求携带的信息执行相应的查询或修改操作。在本发明实施例的一种实现方式中，资源修改并不是修改申请的资源本身，而是修改资源的描述信息；例如，用户发起的资源管理请求为修改网络资源时，资源管理请求中可以包括资源的名称、资源编号、资源类型、用户名称等信息。
可选地，在本发明实施例中，无论用户为管理员用户还是普通用户，当接收到对网络资源进行申请的资源管理请求之后，且在判断是否已经为普通 用户配置了待申请资源的基础资源之前，还可以包括如下处理方式：判断待申请的网络资源是否为线路侧资源。因为线路侧资源比较特殊，只有集团用户才具备申请线路侧资源的权限，因此，当判断出待申请的网络资源不是线路侧资源时，说明当前的待申请的网络资源不特殊，任何类型的普通用户都可以申请，所以可以直接根据资源管理请求中携带的信息执行申请操作；当判断出待申请的网络资源是线路侧资源时，则需要判断待申请的网络资源是否是为普通用户中的集团用户申请；当判断出是为普通用户中的集团用户申请时，才执行后续的判断流程，即判断是否已经为普通用户配置了待申请资源的基础资源，当判断出不是为普通用户中的集团用户申请时，禁止执行申请操作。
可选地，在本发明实施例中，当管理员用户或普通用户对网络资源发起申请请求时，例如，当管理员用户创建普通用户的时候，可能会根据运营商的要求为该普通用户分配资源，这时候，需要判断网络中剩余的网络资源是否满足该管理员用户的申请请求，即网络能否提供待申请的网络资源，当判断出能够满足时，才执行申请操作，当判断出不能满足时，禁止执行申请操作。例如，判断为普通用户申请的带宽是否小于端口所剩带宽，或者申请的时隙是否小于端口所剩时隙，如果判断结果为否，则禁止执行申请操作。
S103、根据确定的执行策略对对象进行处理。
当执行策略确定下来之后，就可以根据对应的执行策略来响应用户下发的资源管理请求，对资源管理请求中携带的请求管理的对象进行相应的处理。
本发明实施例提供的基于软件定义网络的资源管理方法，通过接收用户发起的资源管理请求，从资源管理请求中获取到用户类型和用户请求管理的对象，并根据该资源管理请求中的用户类型和用户请求管理的对象从预设的资源管理规则中匹配出对应的执行策，然后根据匹配到的执行策略对用户请求管理的对象进行处理；本发明实施例提供的方法通过让不同类型的用户对资源进行不同方式的管理，考虑到了用户间的差异性，让参与资源管理的用户都能根据与其需求适配的管理方案对网络资源进行管理，避免了相关技术中笼统管理所造成的资源浪费的问题，提高了资源的利用率，进而降低了网 络资源的运营成本。
图2为本发明实施例提供的一种基于软件定义网络的资源管理装置的结构示意图，本发明实施例提供的装置能够根据图1所示任一实施例提供的基于软件定义网络的资源管理方法对网络中的资源进行管理，如图2所示，本发明实施例提供的基于软件定义网络的资源管理装置20中包括请求接收模块201、策略确定模块202和资源管理模块203。
请求接收模块201，设置为：接收用户发起的资源管理请求。
在本发明实施例中，用户发起的资源管理请求中包括的信息有用户类型和用户请求管理的对象。在本发明实施例中，为了实现不同类型的用户对资源进行不同管理这一目的，可以将用户划分为管理员用户和普通用户，可选地，普通用户又可以被区分为集团用户和租户用户。
本发明实施例提供的基于软件定义网络的资源管理装置20可以部署在SDN控制器上，无论是管理员用户还是普通用户的资源管理请求都可以通过SDN控制器的北向接口下发。请求接收模块201也自然可以从北向接口接收到各个用户发起的资源管理请求。北向接口是为厂家或运营商进行接入和管理网络的接口，即向上提供的接口。另外，在本发明实施例中，请求接收模块201接收到的资源管理请求的格式可以采用JSON(JavaScript Object Notation)数据格式，JSON是一种轻量级的数据交换格式，它基于ECMA Script的一个子集。JSON采用完全独立于语言的文本格式，但是也使用了类似于C语言家族(包括C、C++、C#、Java、JavaScript、Perl、Python等)的习惯，这些特性使JSON成为理想的数据交换语言。本发明实施例的请求接收模块201接收到的资源管理请求中可以通过字符串来记录用户的相关请求信息。
策略确定模块202，设置为：根据请求接收模块201接收的用户类型和对象从预设的资源管理规则中匹配出对应的执行策略；该资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略。
根据上述介绍可以，在本发明实施例中，用户类型可以包括管理员用户和普通用户，管理员用户和普通用户的划分是基于二者在资源管理方面拥有 的不同权限。由于策略确定模块202匹配出的执行策略是根据资源管理规则确定的，其中包含不同类型用户请求管理不同对象所对应的执行策略。因此，即使管理员用户和普通用户发起的资源管理请求中包含的请求管理的对象相同，但是由于这二者的用户类型不同，所以确定出来的执行策略也不会相同。
在本发明实施例中，用户可进行管理的资源至少可以包括网络资源和用户信息资源两种，网络资源例如包括节点、端口、端口资源、链路、链路资源等。而用户信息资源例如包括网络中的普通用户，即集团用户与租户用户。可选地，资源管理策略至少可以包括用于根据用户的资源管理请求对网络资源进行管理的网络资源执行策略和用于根据用户的资源管理请求对用户信息资源进行管理的用户信息执行策略两种。
为了便于说明，下面将分别通过管理员用户和普通用户对不同资源的管理进行描述：
可选地，在本发明实施例中，管理员用户可以对普通用户的信息(即用户信息资源)进行创建、删除、查询以及修改，当管理员用户从北向接口下发的资源管理请求是对用户信息资源进行上述管理方式中的任意一种时，可以根据管理员用户下发的资源管理请求中携带的相关信息执行相应的操作。例如，当管理员用户希望进行普通用户的创建时，在资源管理请求中除了会携带管理员用户的用户类型和管理对象以外，还会包括请求管理的方式，即创建类型的管理。当然，在资源管理请求当中还可以包括待创建用户的相关信息，例如，待创建用户的用户名、密码、用户等级、用户类型等信息。再例如，当管理员用户需要对普通用户进行删除、查询或者修改等操作的时候，也可以直接发起对应的资源管理请求。
可选地，在本发明实施例中，将用户信息资源和网络资源纳入了用户可以进行管理的资源之中，但对于管理员用户来说，除了可以对普通用户的用户信息资源进行管理以外，还可以对其自身进行一些管理。可以理解的是，管理员用户虽然可以对普通用户进行创建、删除、修改、查询等方式的管理，但是一个管理员用户却不能对另一个管理员用户进行上述操作，管理员用户只能对其自身的信息进查询，若是修改信息，也只能对自身的用户密码进行 修改，该管理员用户对其他管理员用户的操作或者对自身的其他操作都属于不合法操作。可选地，在本发明实施例的一些可能的实现方式中，用户类型还可以包括超级管理员，超级管理员可以对管理员用户进行创建、查询、删除、修改等操作。
当管理员用户对网络资源进行管理时，管理员用户可以为普通用户申请网络资源、释放网络资源、修改网络资源以及查询普通用户的网络资源或网络拓扑结构中的剩余资源。
可选地，在本发明实施例中，如果管理员用户需要为普通用户申请网络资源，那么在管理员用户发起的资源管理请求则为网络资源申请请求，在网络资源申请请求当中，会携带待申请的网络资源的类型，例如待申请网络资源是节点、端口或者端口资源，又或者是链路、链路资源等。可以理解的是，由于链路就是两个端口之间的通路，所以链路和链路资源可以分别用链路两端的端口和端口资源来表示，即使展示给用户的时候是以链路和链路资源的形式，但是在底层资源管理上，链路和链路资源实质就是端口和端口资源。
网络资源的部署会遵循一些规律，例如，节点资源应当部署在节点上，端口资源应当部署在端口上，而端口又应当部署在节点上，这就是网络资源的部署要遵循预设资源架构。节点是端口的基础资源，端口是端口资源的基础资源；相应的，端口是节点的承载资源，端口资源部署在端口上，则端口资源是端口的承载资源。
可选地，在本发明实施例中，如果管理员用户发送的资源管理请求是网络资源申请请求，想要为某一个普通用户申请某类型的网络资源，则首先要判断该普通用户是否已经配置了该待申请资源的基础资源；当判断出已经配置时，根据网络资源申请请求为普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作。例如，如果待申请的网络资源是端口资源，则要先判断该普通用户是否已经申请了节点，如果该普通用户已经申请了节点，则要判断其是否申请了部署该端口资源的端口，如果该普通用户还未申请节点或者端口，则其当前还不具备申请端口资源的条件，此时确定出来的执行策略应当是禁止该普通用户申请该网络资源，与此同时还可以从北向接口向下发资源管理请求的管理员用户返回提示信息，告知管理员用户 应当先为该普通用户申请预设资源架构中、处于待申请的网络资源之上的各网络资源。
与网络资源申请流程类似，当管理员用户需要为普通用户释放资源管理请求的时候，发起的资源管理请求为网络资源释放请求，首先，SDN控制器需要先判断普通用户是否已经释放了部署在待释放资源上的承载资源；当判断出已经释放时，释放待释放的网络资源；当判断出没有释放时，禁止执行释放操作。例如，若待释放网络资源为节点，则应当先将部署在该节点上的各个端口都释放掉，而为了释放每一个端口，应当先释放部署在各个端口上的全部端口资源。
可选地，在本发明实施例中，如果管理员用户下发的资源管理请求是网络资源查询请求或网络资源修改请求，管理员用户期望对网络资源进行查询或者修改，可以直接根据资源管理请求中携带的信息执行查询操作。查询类型的资源管理请求中可以包含待查询网络资源的URL，在URL信息中可以包括待查询网络资源的节点信息、端口信息和资源ID等。可以理解的是，运营商可能会要求管理员用户在创建普通用户的时候就为其分配对应的资源，这时，管理员用户需要对网络拓扑结构中的剩余资源进行查询。
可选地，在本发明实施例中，对于普通用户而言，其对用户信息资源的管理权限要低于管理员用户，例如管理员用户可以创建、删除普通用户，但是普通用户发起资源管理请求，请求进行普通用户的创建、删除的时候，得到的执行策略可能是禁止执行相应的创建或删除操作。而当普通用户从北向接口发起的资源管理请求是对用户信息资源进行查询的时候，需要判断待查询的对象是否为普通用户本身，当判断出待查询的对象是该普通用户本身时，执行查询操作并反馈普通用户的用户信息，当判断出待查询的对象不是该普通用户本身时，禁止执行查询操作。当普通用户对用户信息资源发起修改请求时，判断待修改的对象是否为其本身的用户密码，当判断出待修改的对象是该普通用户的用户密码时，执行修改操作，当判断出待修改的对象不是该普通用户的用户密码时，禁止执行修改操作。普通用户对用户信息资源的管理方式与管理员用户对管理员用户的管理方式类似。
可选地，在本发明实施例中，说明普通用户对网络资源的管理方式：
当普通用户对网络资源发起的资源管理请求为网络资源申请请求时，同管理员发起申请请求一样，也需要判断普通用户是否已经配置了该待申请资源的基础资源；当判断出已经配置时，根据网络资源申请请求为普通用户配置该待申请的网络资源；当判断出没有配置时，禁止执行申请操作。
当普通用户对网络资源发起的资源管理请求为网络资源释放请求时，判断普通用户是否已经释放了部署在待释放资源上的承载资源；当判断出已经释放时，释放待释放的网络资源；当判断出没有释放时，禁止执行释放操作。如果暂时还不满足资源释放的条件，则可以向普通用户发出提示信息，普通用户对网络资源的申请请求和释放请求类似，最大的不同在于资源管理请求中的关键字发生了变化。
当普通用户对网络资源发起的资源管理请求为网络资源查询或修改请求时，根据资源管理请求携带的信息执行相应的查询或修改操作。在本发明实施例的一种实现方式中，资源修改并不是修改申请的资源本身，而是修改资源的描述信息；例如，用户发起的资源管理请求为修改网络资源时，资源管理请求中可以包括资源的名称、资源编号、资源类型、用户名称等信息。
可选地，在本发明实施例中，无论用户为管理员用户还是普通用户，当基于软件定义网络的资源管理装置20的请求接收模块201接收到对网络资源进行申请的资源管理请求之后，且在策略确定模块202判断是否已经为普通用户配置了待申请资源的基础资源之前，还可以包括如下处理方式：判断待申请的网络资源是否为线路侧资源。因为线路侧资源比较特殊，只有集团用户才具备申请线路侧资源的权限，因此，当判断出待申请的网络资源不是线路侧资源时，说明当前的待申请的网络资源不特殊，任何类型的普通用户都可以申请，所以可以直接根据资源管理请求中携带的信息执行申请操作；当判断出待申请的网络资源是线路侧资源时，则需要判断待申请的网络资源是否是为普通用户中的集团用户申请；当判断出是为普通用户中的集团用户申请时，才执行后续的判断流程，即判断是否已经为普通用户配置了待申请资源的基础资源，当判断出不是为普通用户中的集团用户申请时，禁止执行申请操作。
可选地，在本发明实施例中，当管理员用户或普通用户对网络资源发起 申请请求时，例如，当管理员用户创建普通用户的时候，可能会根据运营商的要求为该普通用户分配资源，这时候，基于软件定义网络的资源管理装置20需要判断网络中剩余的网络资源是否满足该管理员用户的申请请求，即软件定义网络能否提供待申请的网络资源，当判断出能够满足时，才执行申请操作，当判断出不能满足时，禁止执行申请操作。例如，判断为普通用户申请的带宽是否小于端口所剩带宽，或者申请的时隙是否小于端口所剩时隙，如果判断结果为否，则禁止执行申请操作。
资源管理模块203，设置为：根据策略匹配模块202匹配到的执行策略对用户请求管理的对象进行处理。
当执行策略确定下来之后，就可以根据对应的执行策略来响应用户下发的资源管理请求，对资源管理请求中携带的请求管理的对象进行相应的处理。
本发明实施例提供的基于软件定义网络的资源管理装置可以部署在SDN控制器中，而部署有基于软件定义网络的资源管理装置的SDN控制器又可以运行在终端或者服务器上，其中请求接收模块201、策略确定模块202以及资源管理模块203的功能都可以通过终端或者服务器中的处理器来实现。当处理器接收到用户发出的资源管理请求后，会根据发起请求的用户的类型以及资源管理请求中请求管理的对象确定出与该资源管理请求相对应的执行策略，然后处理器在根据匹配到的执行策略对用户请求的对象进行管理。
本发明实施例提供基于软件定义网络的资源管理装置，通过请求接收模块201接收用户发起的资源管理请求，从资源管理请求中获取到用户类型和用户请求管理的对象，并由策略确定模块202根据请求接收模块201接收的资源管理请求中的用户类型和用户请求管理的对象从预设的资源管理规则中匹配出对应的执行策，然后资源管理模块203根据策略确定模块202匹配到的执行策略对用户请求管理的对象进行处理；本发明实施例提供的装置通过让不同类型的用户对资源进行不同方式的管理，考虑到了用户间的差异性，让参与资源管理的用户都能根据与其需求适配的管理方案对网络资源进行管理，避免了相关技术中笼统管理所造成的资源浪费的问题，提高了资源 的利用率，进而降低了网络资源的运营成本。
以下结合实际应用场景，对本发明实施例提供的基于软件定义网络的资源管理装置进行说明：
如图3所示，为本发明实施例提供的另一种基于软件定义网络的资源管理方法的流程图。由于管理员用户创建、删除、查询、修改普通用户的流程比较相似，图3所示流程以管理员用户发起的资源管理请求是对用户信息资源进行创建为例进行说明。本实施例提供的方法包括以下步骤，即S301～S305：
S301、接收创建普通用户的资源管理请求。
本实施例中的基于软件定义网络的资源管理装置可以部署在SDN控制器中，管理员用户的资源管理请求可以在SDN控制器北向接口下发，且下发的数据为JSON格式。在资源管理请求当中例如包含待创建的普通用户的用户名、密码、用户等级、用户类型等信息。
管理员用户希望创建一个用户名为A，用户密码为12212，用户等级为02级，用户类型为001，资源ID号为01，资源类型为01的普通用户，则管理员用户在SDN控制器的北向接口下发的资源管理请求可以参考如下所示的形式：
POST/rest/json/USER_API/user HTTP/1.x
{
"userName":"A",
"password":"12212",
"userClass":02,
"userType":001,
"sourceId":01,
"sourceType":01
}
S302、对接收到的资源管理请求进行数据适配。
由于管理员用户从SDN控制器的北向接口下发的数据都是ISON格式的，所以，需要将JSON格式的数据转化为SDN控制器能识别的内部数据。
S303、确定用户的用户类型和用户请求管理的对象。
根据资源管理请求可以确定下发该资源请求的用户的类型为管理员用户，以及该用户期望对何种资源执行何种管理操作。
S304、根据用户类型和请求管理的对象匹配出对应的执行策略。
SDN控制器根据管理员用户下发的资源管理请求，从中获取到下发请求的用户类型为管理员用户类型，以及该用户请求管理的对象为对用户信息资源进行创建。根据这两个信息，SDN控制器能够从预设的资源管理规则中匹配出对应的执行策略。
在匹配执行策略的时候，SDN控制器可能要执行以下几个判断流程：
首先，SDN控制器确定该用户是否具备创建普通用户的权限。
如果资源管理请求中不包含资源申请的信息，则此时可以确定执行策略为允许该用户执行创建流程。但由于在上述资源管理请求当中还包含为待创建用户分配资源的信息，所以，还要判断该待分配资源是否是线路侧资源，因为线路侧资源比较特殊，只有集团用户才具备申请线路侧资源的权限。因此，当判断出待分配资源不是线路侧资源时，说明当前的待申请的网络资源不特殊，任何类型的普通用户都可以申请，所以可以直接根据资源管理请求中携带的信息执行申请操作；当判断出待分配资源是线路侧资源时，需要判断待申请网络资源是否是为普通用户中的集团用户申请；当判断出待申请网络资源是为普通用户中的集团用户申请时，才执行申请操作，当判断出待申请网络资源不是为普通用户中的集团用户申请时，禁止执行申请操作。
可选地，在本实施例中，可能还需要判断网络中剩余的网络资源是否满足该管理员用户的申请请求，即网络能否提供待申请的网络资源，当判断出满足时，才执行申请操作，当判断出不满足时，禁止执行申请操作。
S305、根据匹配到的执行策略对对象进行处理。
当执行策略确定下来之后，就可以根据对应的执行策略来响应用户下发 的资源管理请求，对资源管理请求中携带的请求管理的对象进行相应的处理。
在图3所示创建普通用户的流程中所涉及到的SDN控制器的模块可以参考图4所示，为本发明实施例提供的一种SDN控制器的结构示意图。
在应用层，存在应用程序(Application，简称为：APP)411和超文本传送协议(Hypertext transfer protocol，简称为：HTTP)协议栈412。APP安装在终端设备410上，终端设备410可以是个人电脑(personal computer，简称为：PC)、平板电脑、手机、掌上电脑(Personal Digital Assistant，简称为：PDA)等，终端设备410可以包括显示屏，可以用于展示APP的可视化的界面。本实施例中的用户，例如管理员用户或者普通用户的所有操作都在APP上完成。
终端设备410与部署了本实施例中SDN控制器420的其他终端设备或者服务器通过HTTP协议412进行通信，在终端设备410和SDN控制器420中，都设置有HTTP协议栈(412或421)，用来创建应用层和控制层之间的会话，传输两者之间的数据。表述性状态传递程序桩(Representational State Transfer Stub，简称为：REST STUB)模块422主要是完成数据之间的适配。统一资源监控(User Management，简称为：URM)模块423主要是进行用户的管理。
本发明实施例提供的基于软件定义网络的资源管理装置，通过对接收到的资源管理请求中的信息进行解析，获得发起请求的用户类型，根据用户类型和用户请求管理的对象来确定对应于该资源管理请求的执行策略，考虑到了用户间的差异性，让参与资源管理的用户都能根据与其需求适配的管理方案对网络资源进行管理，避免了相关技术中笼统管理所造成的资源浪费的问题，提高了资源的利用率，进而降低了网络资源的运营成本。
本发明实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机可执行指令，该计算机可执行指令被处理器执行，以实现以下步骤：
S1，接收用户发起的资源管理请求，该资源管理请求包含用户类型和用户请求管理的对象；
S2，根据用户类型和对象从预设的资源管理规则中匹配出对应的执行策略；该资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
S3，根据匹配到的执行策略对用户请求管理的对象进行处理。
可选地，在本发明实施例中，上述用户类型可以包括管理员用户和普通用户，该对象包括用户信息资源和网络资源，该执行策略包括用户信息资源执行策略和网络资源执行策略。
本发明实施例中匹配出与用户类型和对象对应的执行策略的实现方式，与不同用户类型请求管理不同对象的实际应用场景相关，在本发明上述实施例中已经详细说明，故在此不再赘述。
以上内容是结合实际应用中的实施方式对本发明实施例和可选实施方式所作的详细说明，不能认定本发明的实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(根据系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过接收用户发起的资源管理请求，从资源管理请求中获取到用户类型和用户请求管理的对象，并根据用户类型和对象从预设的资源管理规则中匹配出与该用户的资源管理请求对应的执行策略，然后根据确定的执行策略对用户请求管理的对象进行处理。由于执行策略是根据用户类型确定的，所以本发明实施例提供的基于软件定义网络的资源管理方法可以让不同类型的用户对资源进行不同方式的管理，考虑到了用户间的差异性，让参与资源管理的用户都能根据与其需求适配的管理方案对网络资源进行管理，避免了相关技术中笼统管理所造成的资源浪费的问题，降低了网络资源的浪费，提高了资源的利用率。

Claims (12)

  1. 一种基于软件定义网络的资源管理方法，包括：
    接收用户发起的资源管理请求，所述资源管理请求包含用户类型和用户请求管理的对象；
    根据所述用户类型和所述对象从预设的资源管理规则中匹配出对应的执行策略；所述资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
    根据匹配到的执行策略对所述对象进行处理。
  2. 根据权利要求1所述的基于软件定义网络的资源管理方法，其中，所述用户类型包括管理员用户和普通用户，所述对象包括用户信息资源和网络资源，所述执行策略包括用户信息资源执行策略和网络资源执行策略。
  3. 根据权利要求2所述的基于软件定义网络的资源管理方法，其中，所述管理员用户请求对用户信息资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
    所述管理员用户对所述用户信息资源发起的所述资源管理请求为创建请求时，根据所述创建请求所携带的信息执行相应的创建操作；
    所述管理员用户对所述用户信息资源发起的所述资源管理请求为删除请求时，根据所述删除请求所携带的信息执行相应的删除操作；
    所述管理员用户对所述用户信息资源发起的所述资源管理请求为查询请求时，根据所述查询请求所携带的信息执行相应的查询操作；
    所述管理员用户对所述用户信息资源发起的所述资源管理请求为修改请求时，根据所述修改请求所携带的信息执行相应的修改操作。
  4. 根据权利要求2所述的基于软件定义网络的资源管理方法，其中，所述普通用户请求对用户信息资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
    所述普通用户对所述用户信息资源发起的所述资源管理请求为创建请求或删除请求时，禁止执行相应的创建或删除操作；
    所述普通用户对所述用户信息资源发起的所述资源管理请求为查询请求时，判断待查询的对象是否为所述普通用户本身，当判断出所述待查询的对象是所述普通用户本身时，执行查询操作并反馈所述普通用户的用户信息，当判断出所述待查询的对象不是所述普通用户本身时，禁止执行查询操作；
    所述普通用户对所述用户信息资源发起的所述资源管理请求为修改请求时，判断待修改的对象是否为所述普通用户的用户密码，当判断出所述待修改的对象是所述普通用户的用户密码时，执行修改操作，当判断出所述待修改的对象不是所述普通用户的用户密码时，禁止执行修改操作。
  5. 根据权利要求2所述的基于软件定义网络的资源管理方法，其中，所述管理员用户请求对网络资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
    所述管理员用户发起的所述资源管理请求为网络资源申请请求，用于为所述普通用户申请网络资源时，判断是否已经为所述普通用户配置了所述待申请资源的基础资源；当判断出已经配置时，根据所述网络资源申请请求为所述普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作；
    所述管理员用户发起的所述资源管理请求为网络资源释放请求，用于为所述普通用户释放网络资源时，判断所述普通用户是否已经释放了部署在所述待释放资源上的承载资源；当判断出已经释放时，释放所述待释放的网络资源；当判断出没有释放时，禁止执行释放操作；
    所述管理员用户发起的所述资源管理请求为网络资源查询请求或网络资源修改请求时，根据所述网络资源查询请求或网络资源修改请求携带的信息执行相应的查询或修改操作。
  6. 根据权利要求2所述的基于软件定义网络的资源管理方法，其中，所述普通用户请求对网络资源进行管理时所对应的执行策略包括以下几种中的一种或多种：
    所述普通用户对所述网络资源发起的所述资源管理请求为网络资源申请请求时，判断所述普通用户是否已经配置了所述待申请资源的基础资源； 当判断出已经配置时，根据所述网络资源申请请求为所述普通用户配置所述待申请的网络资源；当判断出没有配置时，禁止执行申请操作；
    所述普通用户对所述网络资源发起的所述资源管理请求为网络资源释放请求时，判断所述普通用户是否已经释放了部署在所述待释放资源上的承载资源；当判断出已经释放时，释放所述待释放的网络资源；当判断出没有释放时，禁止执行释放操作；
    所述普通用户对所述网络资源发起的所述资源管理请求为网络资源查询请求或网络资源修改请求时，根据所述网络资源查询请求或网络资源修改请求携带的信息执行相应的查询或修改操作。
  7. 根据权利要求5或6所述的基于软件定义网络的资源管理方法，其中，
    当所述待申请资源为端口资源时，所述端口资源的基础资源为端口；当所述待申请资源为端口时，所述端口的基础资源为节点；
    当所述待释放资源为节点时，所述节点的承载资源为端口；当所述待释放资源为端口时，所述端口的承载资源为端口资源。
  8. 根据权利要求5或6所述的基于软件定义网络的资源管理方法，其中，在接收所述管理员用户或所述普通用户对所述网络资源发起的网络资源申请请求之后，且在判断是否已经为所述普通用户配置了所述待申请资源的基础资源之前，所述方法还包括：
    判断所述待申请的网络资源是否为线路侧资源，当判断出所述待申请的网络资源不是所述线路侧资源时，直接判断是否已经为所述普通用户配置了所述待申请资源的基础资源，当判断出所述待申请的网络资源是所述线路侧资源时，判断所述待申请的网络资源是否是为所述普通用户中的集团用户申请；当判断出是为所述普通用户中的集团用户申请时，判断是否已经为所述普通用户配置了所述待申请资源的基础资源，当判断出不是为所述普通用户中的集团用户申请时，禁止执行申请操作。
  9. 一种基于软件定义网络的资源管理装置，包括：
    请求接收模块，设置为：接收用户发起的资源管理请求，所述资源管理请求包含用户类型和用户请求管理的对象；
    策略确定模块，设置为：根据所述请求接收模块接收的所述用户类型和所述对象从预设的资源管理规则中匹配出对应的执行策略；所述资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
    资源管理模块，设置为：根据所述策略确定模块匹配到的执行策略对所述对象进行处理。
  10. 根据权利要求9所述的基于软件定义网络的资源管理装置，其中，所述用户类型包括管理员用户和普通用户，所述对象包括用户信息资源和网络资源，所述执行策略包括用户信息资源执行策略和网络资源执行策略。
  11. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令被处理器执行，以实现以下步骤：
    接收用户发起的资源管理请求，所述资源管理请求包含用户类型和用户请求管理的对象；
    根据所述用户类型和所述对象从预设的资源管理规则中匹配出对应的执行策略；所述资源管理规则包括：不同类型用户请求对不同对象进行管理时所对应的执行策略；
    根据匹配到的执行策略对所述对象进行处理。
  12. 根据权利要求11所述的计算机可读存储介质，其中，所述用户类型包括管理员用户和普通用户，所述对象包括用户信息资源和网络资源，所述执行策略包括用户信息资源执行策略和网络资源执行策略。
PCT/CN2017/083999 2016-06-06 2017-05-11 基于软件定义网络的资源管理方法及装置 WO2017211161A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610398524.XA CN107465633A (zh) 2016-06-06 2016-06-06 基于软件定义网络的资源管理方法及装置
CN201610398524.X 2016-06-06

Publications (1)

Publication Number Publication Date
WO2017211161A1 true WO2017211161A1 (zh) 2017-12-14

Family

ID=60545700

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083999 WO2017211161A1 (zh) 2016-06-06 2017-05-11 基于软件定义网络的资源管理方法及装置

Country Status (2)

Country Link
CN (1) CN107465633A (zh)
WO (1) WO2017211161A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116522316A (zh) * 2023-02-23 2023-08-01 武汉禾正丰科技有限公司 一种基于分布式网络的业务管理系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112688955A (zh) * 2020-12-28 2021-04-20 紫光云技术有限公司 一种资源组授权管理的方法
CN113222466A (zh) * 2021-05-28 2021-08-06 深圳市大恩信息科技有限公司 一种基于erp的会计项目流程监控方法及系统
CN115460022B (zh) * 2022-11-11 2023-03-07 广州中长康达信息技术有限公司 一种对智能辅助平台的资源管理方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166173A (zh) * 2006-10-20 2008-04-23 北京直真节点技术开发有限公司 一种单点登录系统、装置及方法
CN102231693A (zh) * 2010-04-22 2011-11-02 北京握奇数据系统有限公司 访问权限的管理方法及装置
CN102571745A (zh) * 2011-11-16 2012-07-11 烽火通信科技股份有限公司 针对大容量对象的用户访问权限管理方法
CN103856356A (zh) * 2014-03-19 2014-06-11 北京工业大学 一种基于用户自管控的家庭网络实现方法
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166173A (zh) * 2006-10-20 2008-04-23 北京直真节点技术开发有限公司 一种单点登录系统、装置及方法
CN102231693A (zh) * 2010-04-22 2011-11-02 北京握奇数据系统有限公司 访问权限的管理方法及装置
CN102571745A (zh) * 2011-11-16 2012-07-11 烽火通信科技股份有限公司 针对大容量对象的用户访问权限管理方法
US20140301192A1 (en) * 2013-04-05 2014-10-09 Futurewei Technologies, Inc. Software Defined Networking (SDN) Controller Orchestration and Network Virtualization for Data Center Interconnection
CN103856356A (zh) * 2014-03-19 2014-06-11 北京工业大学 一种基于用户自管控的家庭网络实现方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116522316A (zh) * 2023-02-23 2023-08-01 武汉禾正丰科技有限公司 一种基于分布式网络的业务管理系统
CN116522316B (zh) * 2023-02-23 2023-11-14 武汉禾正丰科技有限公司 一种基于分布式网络的业务管理系统

Also Published As

Publication number Publication date
CN107465633A (zh) 2017-12-12

Similar Documents

Publication Publication Date Title
US10075540B2 (en) Network function virtualization (NFV) hardware trust in data communication systems
WO2022033121A1 (zh) 一种kubernetes中资源暴露方法、系统、设备以及介质
CA2936956C (en) An entity handle registry to support traffic policy enforcement
US8887296B2 (en) Method and system for object-based multi-level security in a service oriented architecture
WO2017211161A1 (zh) 基于软件定义网络的资源管理方法及装置
WO2017035735A1 (zh) 一种网络服务的部署方法及装置
US20170171144A1 (en) Management of domain name systems in a large-scale processing environment
US11336735B2 (en) Method and apparatus for managing service access authorization using smart contracts
US10491542B2 (en) Dynamic allocation of network bandwidth
US10237252B2 (en) Automatic creation and management of credentials in a distributed environment
US20190334913A1 (en) Method and apparatus for native authentication to cloud services with identity management of on-premise applications from the cloud
WO2016131171A1 (zh) 一种针对vnf包进行操作的方法及装置
JP2020514863A (ja) 証明書取得方法、認証方法及びネットワークデバイス
US10785056B1 (en) Sharing a subnet of a logically isolated network between client accounts of a provider network
US20240012700A1 (en) Governing Access To Third-Party Application Programming Interfaces
CN116956247B (zh) 一种基于bim的信息处理系统
CN113840013B (zh) 一种分级管理的文档系统
CN115766123A (zh) 数据跨域授权方法及装置和电子设备
Demchenko et al. Access control infrastructure for on-demand provisioned virtualised infrastructure services
WO2021159706A1 (zh) 物联网终端的网络业务控制方法、装置和存储介质
US20160057213A1 (en) Coupling application data with network connectivity
WO2023246287A1 (zh) 安全通道建立方法、系统及存储介质
US20230412643A1 (en) Method and apparatus for policy attributes exchange between security policy management platforms and 5g as a service platforms
TWI668973B (zh) 基於軟件定義網路的可排程安全防護系統及其方法
KR102034528B1 (ko) 다중 채널 기반 데이터 송수신 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1