WO2017120814A1 - 一种管理资源对象的方法和系统 - Google Patents

一种管理资源对象的方法和系统 Download PDF

Info

Publication number
WO2017120814A1
WO2017120814A1 PCT/CN2016/070893 CN2016070893W WO2017120814A1 WO 2017120814 A1 WO2017120814 A1 WO 2017120814A1 CN 2016070893 W CN2016070893 W CN 2016070893W WO 2017120814 A1 WO2017120814 A1 WO 2017120814A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource object
managed
identifier
uuid
fdn
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/070893
Other languages
English (en)
French (fr)
Inventor
胡永健
张许宝
刘凯
杨洋
禹亮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2016/070893 priority Critical patent/WO2017120814A1/zh
Priority to CN201680000607.7A priority patent/CN107710196B/zh
Priority to JP2018536788A priority patent/JP6567776B2/ja
Priority to EP16884377.9A priority patent/EP3392784B1/en
Priority to KR1020187023236A priority patent/KR102082282B1/ko
Publication of WO2017120814A1 publication Critical patent/WO2017120814A1/zh
Priority to US16/035,462 priority patent/US20180322118A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G06F16/211—Schema design and management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • 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/04—Network management architectures or arrangements
    • 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5006—Creating or negotiating SLA contracts, guarantees or penalties
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method and system for managing resource objects.
  • the SDN technology is used to separate the SDN control plane of the network equipment from the SDN data plane.
  • UUID Universally Unique Identifier
  • the current mainstream SDN control plane uses a Universally Unique Identifier (UUID) to identify resource objects and uniquely identifies all resource objects in the distributed SDN system.
  • UUID Universally Unique Identifier
  • the existing inventory network system is huge, the number of network management systems based on the existing network system, and the number of applications based on the network management system are also huge. How to make the inventory network system smoothly evolve to the future-oriented SDN system, as far as possible Reusing existing network management systems and a large number of applications in the network management system to manage resource objects in the SDN system is a current technical problem.
  • the present application provides a method and apparatus for managing resource objects in an SDN system, so that a small number of transformations are performed on the network management system and the network management system based application in the inventory network system, that is, the resource objects in the SDN system can be performed. Management, thereby achieving a smooth evolution of the inventory network system to the SDN system.
  • an embodiment of the present application provides a method for managing a resource object in an SDN system, where the SDN system includes a management system, an application system, and a control system; the control system uses a universal unique identifier UUID identifier to identify a resource object. , the method includes:
  • the management system acquires a UUID identifier of the newly discovered resource object
  • the management system generates a corresponding complete identification name FDN identifier for the newly discovered resource object
  • the mapping relationship between the UUID identifier of the newly discovered resource object and the FDN identifier of the newly discovered resource object may be added to the resource object identifier mapping relationship table by using the management system, where the resource is
  • the object identifier mapping relationship table stores a mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the management system receives a first query request of the resource object to be managed sent by the application system, where the first query request includes the to-be-managed Basic information of the resource object, the first query request is used to obtain an FDN identifier of the resource object to be managed;
  • the management system acquires an FDN identifier of the resource object to be managed according to the basic information of the resource object to be managed;
  • the management system returns an FDN identifier of the resource object to be managed to the application system.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management in the inventory network system can be performed.
  • the system and the application based on the network management system are slightly modified, that is, the resource objects in the SDN system can be managed by the application system, and the smooth evolution of the inventory network system to the SDN system is realized.
  • the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, and the smooth evolution of the inventory network system to the SDN system.
  • the first or the second possible implementation manner in the third possible implementation manner, when the newly discovered resource object is a newly discovered physical resource object,
  • the acquiring the UUID identifier of the newly discovered resource object specifically includes: the management system newly discovering the physical resource object; and the management system assigning the UUID identifier to the newly discovered physical resource object;
  • the generating, by the management system, the corresponding FDN identifier for the newly discovered resource object specifically includes: The management system generates a corresponding FDN identifier for the newly discovered physical resource object;
  • mapping relationship between the UUID identifier of the newly discovered resource object and the FDN identifier of the newly discovered resource object specifically includes: the management system will find the new discovery
  • the mapping relationship between the UUID identifier of the physical resource object and the FDN identifier of the newly discovered physical resource object is added to the resource object identifier mapping relationship table.
  • the first or the second possible implementation manner when the newly discovered resource object is a physical resource object,
  • the obtaining the UUID identifier of the newly discovered resource object specifically includes: the management system acquiring, by the control system, the UUID identifier of the newly discovered physical resource object;
  • the generating, by the management system, the corresponding FDN identifier for the newly discovered resource object specifically includes: the management system generating a corresponding FDN identifier for the newly discovered physical resource object;
  • mapping relationship between the UUID identifier of the newly discovered resource object and the FDN identifier of the newly discovered resource object specifically includes: the management system will find the new discovery
  • the mapping relationship between the UUID identifier of the physical resource object and the FDN identifier of the newly discovered physical resource object is added to the resource object identifier mapping relationship table.
  • any one of the first to fifth possible implementation manners, in the sixth possible implementation manner when the newly discovered resource object is a service resource object, the acquiring The UUID identifier of the newly discovered resource object specifically includes: the management system acquiring the UUID identifier of the service resource object from the control system; and the generating, by the management system, the corresponding FDN identifier for the newly discovered resource object, specifically: The management system queries the control system for a corresponding service according to the UUID identifier of the service resource object, and generates an FDN identifier for the service resource object according to the query result;
  • mapping relationship between the UUID identifier of the newly discovered resource object and the FDN identifier of the newly discovered resource object specifically includes: the management system uses the service resource The mapping relationship between the UUID identifier of the object and the FDN identifier of the service resource object is added to the resource object identifier mapping relationship table.
  • the method may further include:
  • the management system acquires the UUID identifier of the resource object to be managed according to the FDN identifier of the resource object to be managed and the resource object identifier mapping relationship table, and returns the UUID of the resource object to be managed to the application system.
  • the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the resource object to be managed. Details or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource objects in the SDN system, for example, query, modify, delete, etc., through the FDN identifier, thereby enhancing management of resources in the SDN system.
  • the management system acquires the resource object to be managed according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table.
  • the UUID further includes: before returning the UUID of the resource object to be managed to the application system:
  • the management system receives the second query request sent by the application system, where the second query request is used to obtain the UUID identifier of the resource object to be managed, and the second query request carries the to-be-managed The FDN ID of the resource object.
  • the method when the detailed information of the resource object to be managed to be queried is the detailed information of the service resource object to be managed, when the detailed information of the service resource object to be managed includes the physical resource object that is associated with the service resource object to be managed that is identified by the UUID, the method further includes:
  • the management system queries the resource object identifier mapping relationship table according to the UUID identifier of the physical resource object associated with the service resource object to be managed, and acquires the association with the service resource object to be managed.
  • An FDN identifier of the physical resource object where the resource object identifier mapping relationship table includes the UUID identifier of the physical resource object associated with the service resource object to be managed, and the associated with the service resource object to be managed. The mapping relationship between the FDN identifiers of the physical resource objects;
  • the management system returns an FDN identifier of the physical resource object associated with the service resource object to be managed to the application system.
  • the management system acquires The FDN of the resource object to be managed that is returned to the application system is an FDN identifier of the physical resource object to be managed, and the method further includes:
  • the management system receives the fourth query request sent by the application system, where the fourth query request carries the FDN identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed;
  • the management system queries the detailed information of the physical resource object to be managed by using the FDN identifier of the physical resource object to be managed;
  • the management system returns detailed information of the physical resource object to be managed to the application system.
  • the management system acquires The FDN of the resource object to be managed that is returned to the application system is an FDN identifier of the physical resource object to be managed, and the method further includes:
  • the physical resource object information modification request carries the FDN identifier of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed;
  • the management system modifies the detailed information of the physical resource object to be managed according to the physical resource object information modification request.
  • the management system when the resource object to be managed is a physical resource object, the management system
  • the FDN of the resource object to be managed that is obtained and returned to the application system is an FDN identifier of the physical resource object to be managed, and the method further includes:
  • the management system receives the physical resource object information deletion request sent by the application system, where the physical resource object information modification request carries the FDN identifier of the physical resource object to be managed, and is used to delete the physical resource object to be managed.
  • the management system deletes the detailed information of the physical resource object to be managed according to the physical resource object information deletion request.
  • the management system when the resource object to be managed is a physical resource object, the management system The UUID of the resource object to be managed that is returned to the application system is identified as a UUID identifier of the physical resource object to be managed, and the method further includes:
  • the management system receives the fifth query request sent by the application system, where the fifth query request carries the UUID identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed;
  • the management system queries the detailed information of the physical resource object to be managed by using the UUID identifier of the physical resource object to be managed;
  • the management system returns detailed information of the physical resource object to be managed to the application system.
  • the management The UUID of the resource object to be managed that is returned to the application system is the UUID identifier of the physical resource object to be managed, and the method further includes:
  • the management system receives a physical resource object information modification request sent by the application system, where the physical resource object information modification request carries a UUID identifier of the physical resource object to be managed, and is used to modify the physical resource object to be managed.
  • the physical resource object information modification request carries a UUID identifier of the physical resource object to be managed, and is used to modify the physical resource object to be managed.
  • the management system queries the detailed information of the physical resource object to be managed by using the UUID identifier of the physical resource object to be managed;
  • the management system modifies the detailed information of the physical resource object to be managed according to the physical resource object information modification request.
  • the management system when the resource object to be managed is a physical resource object, the management system
  • the UUID of the resource object to be managed that is returned to the application system is identified as a UUID identifier of the physical resource object to be managed, and the method further includes:
  • the management system receives the physical resource object information deletion request sent by the application system, where the physical resource object information modification request carries the UUID identifier of the physical resource object to be managed, and is used to delete the physical resource object to be managed.
  • the management system deletes the detailed information of the physical resource object to be managed according to the physical resource object information deletion request.
  • an embodiment of the present application provides a method for managing a resource object in an SDN system, where the SDN system includes: a management system, an application system, and a control system; and the control system uses a universal unique identifier UUID identifier to identify the resource.
  • the management system saves a resource object identifier mapping relationship table between the FDN identifier of the resource object and the UUID identifier of the resource object, where the method includes:
  • the application system sends a first query request to the management system, where the first query request includes basic information of a resource object to be managed, and the first query request is used to obtain an FDN of the resource object to be managed.
  • the application system receives the FDN identifier of the resource object to be managed returned by the management system, and the resource object identifier mapping relationship table stores the FDN identifier of the resource object to be managed;
  • the application system manages the resource object to be managed by using an FDN identifier of the resource object to be managed.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management system in the inventory network system and A small number of transformations are performed based on the application of the network management system, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the method may further include:
  • the UUID identifier of the resource object to be managed acquired by the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table, and the resource object identifier mapping relationship
  • the table saves a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the resource object to be managed. Details or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource object in the SDN system by using the FDN identifier of the resource object to be managed, for example, query, modify, and delete (see the following implementation manner), etc., thereby Strengthen the management of resources in the SDN system.
  • the application system receives an FDN identifier returned by the management system according to the to-be-managed resource object, and the resource object identifier mapping relationship table is obtained.
  • the method of the UUID of the resource object to be managed before the method Further includes:
  • the application system sends a second query request to the management system, where the second query request carries the FDN identifier of the resource object to be managed, and is used to obtain the UUID identifier of the resource object to be managed.
  • the resource object to be managed is a service resource object to be managed
  • the first query request sent by the application system to the management system is used to obtain an FDN identifier of the service resource object to be managed;
  • the application system receives an FDN identifier of the to-be-managed service resource object returned by the management system.
  • the resource object to be managed is a service resource object to be managed
  • the application system by using the FDN identifier of the resource object to be managed, to manage the resource object to be managed includes:
  • the application system sends a second query request to the management system, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, and the second query request carries the to-be-managed The FDN identifier of the business resource object;
  • the application system receives the UUID identifier of the to-be-managed service resource object that is found by the management system and is searched according to the resource object identifier mapping relationship table.
  • the UUID identifier of the service resource object to be managed is used by the application system to manage the detailed information of the service resource object to be managed, and the specific information may include querying the detailed information of the service resource object to be managed, and modifying the Describe the detailed information of the managed service resource object or delete the detailed information of the resource object to be managed.
  • the application system manages the resource object to be managed by using an FDN identifier of the resource object to be managed Specifically include:
  • the application system sends a resource object sixth query request to the control system, where the sixth query request carries the UUID identifier of the service resource object to be managed to query the detailed information of the service resource object to be managed.
  • the application system receives detailed information of the to-be-managed service resource object returned by the control system.
  • the method further includes:
  • the application system sends a third query request to the management system, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, and is used to obtain the An FDN identifier of a physical resource object associated with the service resource object to be managed;
  • the application system receives the FDN identifier of the physical resource object associated with the to-be-managed service resource object that is searched by the management system and returned according to the resource object identifier mapping relationship table.
  • the application system manages the resource object to be managed by using an FDN identifier of the resource object to be managed Specifically include:
  • the application system sends a service resource object information modification request to the control system, where the service resource object information modification request carries the UUID identifier of the service resource object to be managed to modify the service resource object to be managed. details.
  • the application system manages the resource object to be managed by using an FDN identifier of the resource object to be managed Specifically include:
  • the application system sends a service resource object information deletion request to the control system, where the service resource object information deletion request carries the UUID identifier of the service resource object to be managed to delete the service resource object to be managed. details.
  • the first query request sent by the application system to the management system is used to obtain an FDN identifier of the physical resource object to be managed;
  • the application system receives an FDN identifier of the physical resource object to be managed returned by the management system.
  • the application system uses the FDN identifier of the resource object to be managed to manage the to-be-managed
  • the managed resource objects specifically include:
  • the application system sends a fourth query request to the management system, where the fourth query request carries the FDN identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed;
  • the application system receives detailed information of the physical resource object to be managed returned by the management system.
  • the application system manages the FDN identifier of the resource object to be managed
  • the resource objects to be managed specifically include:
  • the application system sends a physical resource object information modification request to the management system, where the physical resource object information modification request carries an FDN identifier of the physical resource object to be managed, and is used to modify the physical resource object to be managed. details.
  • the application system utilizes an FDN identifier management office of the resource object to be managed
  • the resource objects to be managed specifically include:
  • the physical resource object information deletion request carries the FDN identifier of the physical resource object to be managed, and is used to delete the detailed information of the physical resource object to be managed.
  • the method further includes:
  • the application system sends a second query request to the management system, where the second query request is used to obtain a UUID identifier of the physical resource object to be managed, and the second query request carries the to-be-managed The FDN identifier of the physical resource object;
  • the application system receives the UUID identifier of the physical resource object to be managed that is searched according to the resource object identifier mapping relationship table returned by the management system.
  • the method further includes:
  • the application system sends a fifth query request to the management system, where the fifth query request carries the UUID identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed;
  • the application system receives the UUID identifier of the physical resource object to be managed, which is returned by the management system, and acquires the detailed information of the physical resource object to be managed.
  • the application system manages the to-be-managed resource by using an FDN identifier of the resource object to be managed
  • the object specifically includes:
  • the application system sends a physical resource object information modification request to the management system, where the physical resource object information modification request carries a UUID identifier of the physical resource object to be managed, and is used to modify the physical resource object to be managed. details.
  • the application system manages the to-be-managed resource by using an FDN identifier of the resource object to be managed
  • the object specifically includes:
  • the application system sends a physical resource object information deletion request to the management system, where the physical resource object information deletion request carries a UUID identifier of the physical resource object to be managed, and is used to delete the physical resource object to be managed. details.
  • an embodiment of the present application provides a management system for managing resource objects in an SDN system, where the SDN system includes: the management system, an application system, and a control system; and the control system uses a universal unique identifier UUID identifier. Identifying a resource object; the management system includes: a receiving unit, a processing unit, and a sending unit; wherein
  • the processing unit is configured to acquire a UUID identifier of the newly discovered resource object, generate a corresponding complete identifier FDN identifier for the newly discovered resource object, and identify the UUID of the newly discovered resource object with the new identifier
  • the mapping relationship of the FDN identifier of the discovered resource object is added to the resource object identifier mapping relationship table, where the resource object identifier mapping relationship table stores the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the receiving unit is configured to receive a first query request of the resource object to be managed sent by the application system, where the first query request includes basic information of the resource object to be managed, and the first query request An FDN identifier used to obtain the resource object to be managed;
  • the processing unit is further configured to acquire an FDN identifier of the to-be-managed resource object according to the basic information of the resource object to be managed;
  • the sending unit is configured to return an FDN identifier of the to-be-managed resource object to the application system.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management system in the inventory network system can be A small number of transformations are made with the application of the network management system, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is a small number of transformations are made with the application of the network management system, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the processing unit is configured to allocate a UUID identifier to the newly discovered physical resource object, generate a corresponding FDN identifier for the newly discovered physical resource object, and identify and identify a UUID of the newly discovered physical resource object.
  • the mapping relationship of the newly discovered physical resource object's FDN identifier is added to the resource object identifier mapping relationship table.
  • the receiving unit is configured to acquire, from the control system, a UUID identifier of the newly discovered physical resource object;
  • the processing unit is configured to generate a corresponding FDN identifier for the newly discovered physical resource object, and identify the UUID of the newly discovered physical resource object and the FDN identifier of the newly discovered physical resource object.
  • the mapping relationship is added to the resource object identifier mapping relationship table.
  • any one of the first to the third possible implementation manners in the fourth possible implementation manner, when the newly discovered resource object is a service resource object, the processing unit, And obtaining, by the control system, a UUID identifier of the service resource object, querying, by the control system, a corresponding service according to the UUID identifier of the service resource object, and generating an FDN identifier for the service resource object according to the query result,
  • the mapping relationship between the UUID identifier of the service resource object and the FDN identifier of the service resource object is added to the resource object identifier mapping relationship table.
  • the processing unit is further configured to: according to the FDN identifier of the to-be-managed resource object, and the resource object
  • the identifier mapping relationship table acquires a UUID identifier of the resource object to be managed, where the resource object identifier mapping relationship table includes a mapping between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the sending unit is configured to return, to the application system, a UUID identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the resource object to be managed The details of.
  • the user can further manage the detailed information of the resource objects in the SDN system, for example, query, modify, delete, etc., through the FDN identifier, thereby enhancing management of resources in the SDN system.
  • the receiving unit is further configured to receive a second query request sent by the application system, where the second The query request is used to obtain the UUID identifier of the resource object to be managed, and the second query request carries the FDN identifier of the resource object to be managed;
  • the processing unit further acquires the UUID identifier of the resource object to be managed according to the FDN identifier of the resource object to be managed carried in the second query request.
  • the detailed information of the resource object to be managed to be queried is the detailed information of the service resource object to be managed
  • the detailed information of the service resource object to be managed includes the physical resource object associated with the service resource object to be managed identified by the UUID
  • the receiving unit is further configured to receive a third query request sent by the application system, where the third query request carries a UUID identifier of the physical resource object associated with the service resource object to be managed, And acquiring an FDN identifier of the physical resource object associated with the service resource object to be managed;
  • the processing unit is further configured to query the resource object identifier mapping relationship table according to the UUID identifier of the physical resource object associated with the service resource object to be managed, and acquire the service resource to be managed An FDN identifier of the physical resource object associated with the object, the resource object identifier mapping relationship table including the UUID identifier of the physical resource object associated with the service resource object to be managed, and the service to be managed a mapping relationship between FDN identifiers of physical resource objects associated with resource objects;
  • the sending unit is further configured to return, to the application system, the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the processing unit is configured to acquire the FDN identifier of the physical resource object to be managed
  • the sending unit is configured to return the physical resource object FDN identifier to be managed to the application system.
  • the receiving unit is further configured to receive a fourth query request sent by the application system,
  • the fourth query request carries the FDN identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed;
  • the processing unit is further configured to query, by using an FDN identifier of the physical resource object to be managed, detailed information of the physical resource object to be managed;
  • the sending unit is further configured to return, to the application system, detailed information of the physical resource object to be managed.
  • the processing unit is further configured to acquire, according to the FDN identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table, a UUID identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table. And a mapping relationship between the UUID identifier of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed, where the UUID identifier of the physical resource object to be managed is used by the application system to be used by the application system. Details of the physical resource object to be managed.
  • the receiving unit is further configured to receive a fifth query request sent by the application system, where the The five-query request carries the UUID identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed.
  • the processing unit is further configured to obtain, by using a UUID identifier of the physical resource object to be managed. Detailed information of the physical resource object to be managed;
  • the sending unit is further configured to return, to the application system, detailed information of the physical resource object to be managed.
  • the receiving unit is further configured to receive physical resource object information modification sent by the application system 101
  • the request, the physical resource object information modification request carries the FDN identifier of the physical resource object to be managed and/or the UUID of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed;
  • the processing unit is further configured to modify the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • the receiving unit is configured to receive a physical resource object information deletion request sent by the application system,
  • the physical resource object information deletion request carries the FDN identifier of the physical resource object to be managed and/or the UUID of the physical resource object to be managed, and is used to delete the detailed information of the physical resource object to be managed;
  • the processing unit is further configured to delete the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • an embodiment of the present application provides an application system for managing a resource object in a software-defined network SDN system, where the SDN system includes: a management system, the application system, and a control system; and the control system uses a universal unique identifier.
  • the UUID identifier is used to identify the resource object, and the management system saves the resource object identifier mapping relationship table of the mapping between the FDN identifier of the resource object and the UUID identifier of the resource object, where the application system includes: a sending unit, a processing unit, Receiving unit, wherein
  • the sending unit is configured to send a first query request to the management system, where the first query request includes basic information of a resource object to be managed, and the first query request is used to acquire the resource to be managed.
  • the FDN identifier of the object
  • the receiving unit is configured to receive an FDN identifier of the resource object to be managed returned by the management system, where the resource object identifier mapping relationship table stores an FDN identifier of the resource object to be managed;
  • the processing unit is configured to manage the resource object to be managed by using an FDN identifier of the resource object to be managed.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved by creating the resource object identifier relationship table in the management system, and the network management system in the inventory network system is based on
  • the application of the network management system is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the receiving unit is further configured to receive, by the management system, a UUID identifier of the resource object to be managed acquired according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table, where the resource is
  • the object identifier mapping relationship table stores a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource object in the SDN system by using the FDN identifier of the resource object to be managed, for example, query, modify, and delete (see the following implementation manner), etc., thereby Strengthen the management of resources in the SDN system.
  • the sending unit is further configured to send a second query request to the management system, where the second query
  • the request carries the FDN identifier of the resource object to be managed, and is used to obtain the UUID identifier of the resource object to be managed.
  • the resource object to be managed is a service resource object to be managed
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed
  • the FDN identifier of the resource object to be managed is an FDN identifier of the service resource object to be managed.
  • the resource object to be managed is a service resource object to be managed
  • the sending unit is further configured to send a second query request to the management system, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, where the second query request carries The FDN identifier of the service resource object to be managed;
  • the receiving unit is further configured to receive, by the management system, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the UUID identifier of the service resource object to be managed is used by the application system to manage the detailed information of the service resource object to be managed, and the specific information may include querying the detailed information of the service resource object to be managed, and modifying the Describe the detailed information of the managed service resource object or delete the detailed information of the resource object to be managed.
  • the sending unit is further configured to send a sixth query request to the control system, where the sixth query is The request carries the UUID identifier of the service resource object to be managed to query the detailed information of the service resource object to be managed;
  • the receiving unit is further configured to receive detailed information of the service resource object to be managed returned by the control system.
  • the detailed information of the service resource object to be managed includes the identifier identified by using the UUID
  • the physical resource object associated with the business resource object to be managed is
  • the processing unit is further configured to generate a third query request, where the third query request carries a UUID identifier of the physical resource object associated with the service resource object to be managed, and is used to obtain the An FDN identifier of the physical resource object associated with the service resource object to be managed;
  • the sending unit is further configured to send the third query request to the management system
  • the receiving unit is further configured to receive, by the management system, the FDN identifier of the physical resource object associated with the service resource object to be managed returned by the management system;
  • the FDN identifier of the physical resource object associated with the service resource object to be managed and the UUID identifier of the physical resource object associated with the service resource object to be managed are saved in a resource object of the management system Identify the mapping relationship table.
  • the sending unit is further configured to send a service resource object information modification request to the control system, where the service resource object information modification request carries a UUID identifier of the service resource object to be managed to modify the to-be-managed Details of the business resource object.
  • the sending unit is further configured to send a service resource object information deletion request to the control system, where
  • the service resource object information deletion request carries the UUID identifier of the service resource object to be managed to delete the detailed information of the service resource object to be managed.
  • the first query request is used to obtain an FDN identifier of the physical resource object to be managed
  • the FDN identifier of the resource object to be managed is an FDN identifier of the physical resource object to be managed.
  • the sending unit is further configured to send a fourth query request to the management system, where the fourth query request carries the to-be-managed The FDN identifier of the physical resource object is used to query the detailed information of the physical resource object to be managed.
  • the receiving unit is further configured to receive detailed information about the physical resource object to be managed returned by the management system.
  • the sending unit is further configured to send a physical resource object information modification request to the management system, where
  • the physical resource object information modification request carries the FDN identifier of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed.
  • the sending unit is configured to send a physical resource object information deletion request to the management system, where
  • the physical resource object information deletion request carries the FDN identifier of the physical resource object to be managed, and is used to delete the detailed information of the physical resource object to be managed.
  • the sending unit is configured to send a second query request to the management system, where the The second query request is used to obtain the UUID identifier of the physical resource object to be managed, and the second query request carries the FDN identifier of the physical resource object to be managed.
  • the receiving unit is configured to receive, by the management system, a UUID identifier of the physical resource object to be managed, which is searched according to the resource object identifier mapping relationship table.
  • the sending unit is further configured to send a fifth query request to the management system, where the fifth query request carries a UUID identifier of the physical resource object to be managed, and is used to query the physical resource object to be managed. details;
  • the sending unit is further configured to send a physical resource object information modification request to the management system, where the physical resource object information modification request carries a UUID identifier of the physical resource object to be managed, and is used to modify the to-be-managed The details of the physical resource object.
  • the sending unit is further configured to send a physical resource object information deletion request to the management system, where the physical resource object information deletion request carries a UUID identifier of the physical resource object to be managed, and is used to delete the to-be-managed Details of the physical resource object.
  • an embodiment of the present application provides a management system for managing resource objects in a software-defined network SDN system, where the SDN system includes: the management system, an application system, and a control system; and the control system uses a universal unique identifier.
  • a UUID identifier to identify a resource object;
  • the management system includes a processor and a network interface, and a memory;
  • the processor is configured to obtain a UUID identifier of the newly discovered resource object, generate a corresponding complete identifier FDN identifier for the newly discovered resource object, and identify the UUID of the newly discovered resource object with the new identifier
  • the mapping relationship of the FDN identifier of the discovered resource object is added to the resource object identifier mapping relationship table, where the resource object identifier mapping relationship table stores the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object;
  • the memory is configured to store the resource object identifier mapping relationship table.
  • the network interface is configured to receive a first query request of the resource object to be managed sent by the application system, where the first query request includes basic information of the resource object to be managed, and the first query request An FDN identifier used to obtain the resource object to be managed;
  • the processor is further configured to acquire an FDN identifier of the to-be-managed resource object according to the basic information of the resource object to be managed;
  • the network interface is configured to return an FDN identifier of the to-be-managed resource object to the application system.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management system in the inventory network system can be A small number of transformations are made with the application of the network management system, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the processor when the newly discovered resource object is a newly discovered physical resource object, the processor is configured to use the The control system acquires the UUID identifier of the newly discovered physical resource object, generates a corresponding FDN identifier for the newly discovered physical resource object, and identifies the UUID of the newly discovered physical resource object with the newly discovered physics.
  • the mapping relationship of the FDN identifier of the resource object is added to the resource object identifier mapping relationship table.
  • the processor when the newly discovered resource object is a newly discovered physical resource object, the processor is used to: Allocating a UUID identifier for the newly discovered physical resource object, generating a corresponding FDN identifier for the newly discovered physical resource object, and identifying a UUID identifier of the newly discovered physical resource object and the newly discovered physical resource object The mapping relationship of the FDN identifier is added to the resource object identifier mapping relationship table.
  • any one of the first to the third possible implementation manners when the newly discovered resource object is a service resource object, the processor uses Obtaining the UUID identifier of the service resource object from the control system, querying the corresponding service according to the UUID identifier of the service resource object, and generating an FDN identifier for the service resource object according to the query result, and using The mapping relationship between the UUID identifier of the service resource object and the FDN identifier of the service resource object is added to the resource object identifier mapping relationship table. Said The UUID of the service resource object can be delivered by the application system to the control system through the northbound interface.
  • the processor is further configured to: according to the FDN identifier of the to-be-managed resource object and the resource object identifier
  • the mapping relationship table acquires a UUID identifier of the resource object to be managed, where the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage detailed information of the resource object to be managed, and the network interface is configured to return the resource object to be managed to the application system. UUID identifier.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource objects in the SDN system, for example, query, modify, delete, etc., through the FDN identifier, thereby enhancing management of resources in the SDN system.
  • the network interface is further configured to receive a second query request sent by the application system, where the second The query request is used to obtain the UUID identifier of the resource object to be managed, and the second query request carries the FDN identifier of the resource object to be managed;
  • the processor is further configured to acquire, according to the FDN identifier of the resource object to be managed carried in the second query request, the UUID identifier of the resource object to be managed.
  • the detailed information of the resource object to be managed to be queried is the detailed information of the service resource object to be managed
  • the detailed information of the service resource object to be managed includes the physical resource object associated with the service resource object to be managed identified by the UUID
  • the network interface is further configured to receive a third query request sent by the application system, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, and is used for Obtaining an FDN identifier of the physical resource object associated with the service resource object to be managed;
  • the processor is further configured to query the resource object identifier mapping relationship table according to the UUID identifier of the physical resource object that is associated with the service resource object to be managed, and acquire the service resource to be managed An FDN identifier of the physical resource object associated with the object, the resource object identifier mapping relationship table including the UUID identifier of the physical resource object associated with the service resource object to be managed, and the service to be managed a mapping relationship between FDN identifiers of physical resource objects associated with resource objects;
  • the network interface is further configured to return, to the application system, the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the resource object to be managed is a physical resource object to be managed
  • the processor is configured to acquire the FDN identifier of the physical resource object to be managed
  • the network interface is configured to return the physical resource object FDN identifier to be managed to the application system.
  • the network interface is further configured to receive a fourth query request sent by the application system, where the fourth query request carries the to-be-managed The FDN identifier of the physical resource object, used to index the detailed information of the physical resource object to be managed;
  • the processor is further configured to: by using an FDN identifier of the physical resource object to be managed, index the detailed information of the physical resource object to be managed;
  • the network interface is further configured to return detailed information of the physical resource object to be managed to the application system.
  • the processor is further configured to acquire, according to the FDN identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table, a UUID identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table. And a mapping relationship between the UUID identifier of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed, where the UUID identifier of the physical resource object to be managed is used by the application system to be used by the application system. Details of the physical resource object to be managed.
  • the network interface is configured to return a UUID identifier of the physical resource object to be managed to the application system, and receive a fifth query request sent by the application system, where the fifth query request carries the to-be-managed A UUID identifier of the physical resource object, configured to query detailed information of the physical resource object to be managed;
  • the processor is further configured to acquire, by using a UUID identifier of the physical resource object to be managed, detailed information of the physical resource object to be managed;
  • the network interface is further configured to return detailed information of the physical resource object to be managed to the application system.
  • the network interface is further configured to receive a physical resource object information modification request sent by the application system And the physical resource object information modification request carries the FDN identifier of the physical resource object to be managed and/or the UUID of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed;
  • the processor is further configured to modify the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • the network interface is configured to receive a physical resource object information deletion request sent by the application system,
  • the physical resource object information deletion request carries the physical resource object to be managed
  • the FDN identifier and/or the UUID of the physical resource object to be managed are used to delete the detailed information of the physical resource object to be managed;
  • the processor is further configured to delete the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • the memory is for storing program instruction code
  • the processor is configured to execute the instruction code in the memory to complete the method of the embodiment corresponding to FIG. 2-8.
  • an embodiment of the present application provides an application system for managing resource objects in a software-defined network SDN system, where the SDN system includes: a management system, an application system, and a control system.
  • the control system uses the universally unique identifier UUID identification to identify the resource object.
  • the management system saves the resource object identifier mapping relationship table of the mapping relationship between the FDN identifier of the resource object and the UUID identifier of the resource object.
  • the application system may include: a processor and a network interface.
  • the processor and network interface communicate over bus 704.
  • the processor communicates with the management system and the control system through a network interface;
  • the network interface is configured to send a first query request to the management system, where the first query request includes basic information of a resource object to be managed, and is used to obtain an FDN identifier of the resource object to be managed;
  • the network interface is further configured to receive an FDN identifier of the resource object to be managed returned by the management system, where the resource object identifier mapping relationship table stores an FDN identifier of the resource object to be managed;
  • the processor is configured to manage the resource object to be managed by using an FDN identifier of the resource object to be managed.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved by creating the resource object identifier relationship table in the management system, and the network management system in the inventory network system is based on
  • the application of the network management system is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user performs the resource object through the management interface of the application system.
  • the user can present the visualized resource object information through the management interface, so that the user can query the basic index information of the resource object.
  • the network interface is further configured to receive, by the management system, a UUID identifier of the resource object to be managed acquired according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table, where the resource is
  • the object identifier mapping relationship table stores a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the resource object to be managed. Details or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource object in the SDN system by using the FDN identifier of the resource object to be managed, for example, query, modify, and delete (see the following implementation manner), etc., thereby Strengthen the management of resources in the SDN system.
  • the network interface is further configured to send a second query request to the management system, where the second query request carries an FDN identifier of the resource object to be managed, and is used to obtain a UUID of the resource object to be managed. logo.
  • the first query request is used to obtain the service resource object to be managed.
  • An FDN identifier where the FDN identifier of the resource object to be managed is an FDN identifier of the service resource object to be managed.
  • the resource object to be managed is a service resource object to be managed
  • the network interface is further configured to send the second query request to the control system, where the second query request carries an FDN identifier of the service resource object to be managed, and is used to obtain the to-be-managed The UUID identifier of the service resource object;
  • the network interface is further configured to receive, by the management system, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the UUID identifier of the service resource object to be managed is used by the application system to manage the service resource object to be managed, and the specific information may include querying the detailed information of the service resource object to be managed, and modifying the to-be-managed Details of the business resource object or delete the details of the resource object to be managed.
  • the network interface is further configured to send the sixth query request to the control system, where the sixth query request carries the UUID identifier of the service resource object to be managed to manage the service resource to be managed.
  • the network interface is further configured to receive detailed information about the service resource object to be managed returned by the control system.
  • the detailed information of the service resource object to be managed includes the service resource object that is identified by using the UUID and the to-be-managed When the associated physical resource object is
  • the network interface is further configured to send a third query request to the management system, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, Obtaining an FDN identifier of the physical resource object associated with the service resource object to be managed;
  • the network interface is further configured to receive, by the management system, the FDN identifier of the physical resource object associated with the to-be-managed service resource object, where the management system is associated with the service resource object to be managed.
  • the FDN identifier of the physical resource object and the UUID identifier of the physical resource object associated with the service resource object to be managed are saved in the resource object identifier mapping relationship table of the management system.
  • the network interface is further configured to send a service resource object information modification request to the control system, where the service resource object information modification request carries a UUID identifier of the service resource object to be managed to manage the to-be-managed Details of the business resource object.
  • the network interface is further configured to send a service resource object information deletion request to the control system, where the service resource object information deletion request carries a UUID identifier of the service resource object to be managed to manage the to-be-managed Details of the business resource object.
  • the ninth possible implementation manner when the resource object to be managed is a physical resource object, the first query request is used to acquire the The FDN identifier of the physical resource object to be managed is the FDN identifier of the physical resource object to be managed.
  • the network interface is further configured to send a fourth query request to the management system, where the fourth query request carries an FDN identifier of the physical resource object to be managed, and is used to query the physical resource object to be managed. details;
  • the network interface is further configured to receive detailed information about the physical resource object to be managed returned by the management system.
  • the network interface is further configured to send the physical resource object information modification request to the management system, where the physical resource object information modification request carries an FDN identifier of the physical resource object to be managed, and is used to modify the Details of managed physical resource objects;
  • the network interface is further configured to send a physical resource object information deletion request to the management system,
  • the physical resource object information deletion request carries the FDN identifier of the physical resource object to be managed, and is used to delete the detailed information of the physical resource object to be managed.
  • the network interface is configured to send a second query request to the management system, where the second query request is used to obtain a UUID identifier of the physical resource object to be managed, where the second query request carries the The FDN identifier of the physical resource object to be managed;
  • the network interface is configured to receive, by the management system, a UUID identifier of the physical resource object to be managed, which is searched according to the resource object identifier mapping relationship table.
  • the network interface is further configured to send a fifth query request to the management system, where the fifth query request carries a UUID identifier of the physical resource object to be managed, and is used to query the physical resource object to be managed. details;
  • the network interface is further configured to receive, by the management unit, detailed information of the physical resource object to be managed obtained by using a UUID identifier of the physical resource object to be managed;
  • the network interface is further configured to send a physical resource object information modification request to the management system, where the physical resource object is
  • the information modification request carries the UUID identifier of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed.
  • the network interface is further configured to send a physical resource object information deletion request to the management system system, where the physical resource object information deletion request carries a UUID identifier of the physical resource object to be managed, and is used to delete the to-be-managed Details of the physical resource object.
  • the application system includes a memory, a processor, and a network interface, where the memory is used to store program instruction code, and the processor is configured to execute The instruction code in the memory is executed to complete the method of the embodiment corresponding to FIGS. 2-8.
  • a seventh aspect provides an SDN communication system, comprising the management system of the third aspect or the fifth aspect, comprising the application system of the fourth aspect or the sixth aspect.
  • the communication system is configured to perform the methods of the first aspect and the second aspect.
  • a computer readable storage medium for storing computer software instructions for performing the functions of the first to fourth aspects described above, comprising a method for performing the above first and second aspects Designed program.
  • FIG. 1 is a schematic structural diagram of an SDN system according to an embodiment of the present application.
  • FIG. 2 is a flowchart of a method for managing a resource object according to an embodiment of the present application
  • FIG. 3 is a flowchart of establishing a resource object identifier mapping relationship table according to an embodiment of the present application
  • FIG. 4 is a flowchart of a method for managing a service resource object according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of a method for querying detailed information of a service resource object according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of a method for modifying detailed information of a service resource object according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a method for deleting detailed information of a service resource object according to an embodiment of the present application.
  • FIG. 8 is a flowchart of a method for managing a physical resource object according to an embodiment of the present application.
  • 9A is a schematic structural diagram of hardware of a management system according to an embodiment of the present application.
  • 9B is a schematic structural diagram of hardware of an application system according to an embodiment of the present application.
  • FIG. 10A is a schematic diagram of a management system according to an embodiment of the present application.
  • FIG. 10B is a schematic structural diagram of an application according to an embodiment of the present application.
  • SDN network management system SDN management system
  • SDN management system network management system
  • management system management system
  • tube tube "face” or “SDN management plane”
  • application system or “SDN application system” and “application surface” or “SDN application surface” are used interchangeably
  • SDN control system or “control system” and “control surface” Or “SDN control plane” alternately used
  • SDN data forwarding system SDN forwarding system
  • data forwarding system data forwarding system
  • forwarding system data forwarding system
  • forwarding system data forwarding system
  • forwarding system data forwarding system
  • forwarding system data forwarding system
  • forwarding system forwarding system
  • forwarding system forwarding system
  • forwarding system data forwarding system
  • forwarding plane forwarding plane
  • forwarding plane forwarding plane
  • an SDN system 100 is provided in an embodiment of the present application.
  • the SDN system 100 mainly includes an application system 101, a control system 102, a data forwarding system 103, and a management system 104.
  • Application systems, control systems, data forwarding systems, and management systems are also referred to in the art as application, control, data, and management planes.
  • the application system 101 is connected to the control system 102 via an SDN northbound interface (English name: Northbound Interface, NBI for short) 105.
  • the SDN northbound interface is also referred to as an application-control plane interface (English-name: Application-Controller Plane Interface, A-CPI).
  • the application system 101 includes a plurality of applications, and sends network requirements to the control system 102 through the A-CPI.
  • the control system 102 includes a plurality of controllers, each of which is responsible for controlling resource information of one or more network elements in the data forwarding system 103, and transmitting the network requirements sent by the received application system 101 to the data forwarding system 103.
  • the network element device in the data forwarding system 103 such as a switch, a router, and the like, is sent to the application system 101 to provide network services for the application system 101.
  • the control system 102 can optimally configure limited network resources to meet application requirements through control strategies.
  • the data forwarding system 103 is coupled to the control system 102 via an SDN Southbound Interface (SBI) 106.
  • SDN southbound interface 106 is also referred to as a data-control plane interface (English name: Data-Controller Plane Interface, D-CPI).
  • the data forwarding system 103 includes a plurality of network elements (English name: Network Element, NE), and the plurality of network elements include switches and routes. , firewall, packet transport network equipment, etc.
  • Each network element includes multiple physical resource objects, including sub-frames, slots, boards, sub-slots, ports, and so on.
  • the management system 104 is connected to the application system 101, the control system 102, and the data forwarding system 103, respectively, through a logical management function interface.
  • the management function in the management system 104 may be through a commercial or operational support system (BSS/OSS), a network management system (NMS) or a network element network management system in the inventory network.
  • BSS/OSS commercial or operational support system
  • NMS network management system
  • EMS network element network management system
  • the specific structure and functional modules of existing BSS/OSS, NMS or EMS operated by different operators may vary with different operational requirements.
  • the management system 104 also performs certain management functions for the SDN system.
  • the management system 104 is responsible for configuring a service level agreement (SLAs) between the network service provider and the customer.
  • SLAs include the following items: minimum bandwidth allocated to the customer, Customer bandwidth limits, number of customers that can serve simultaneously, notification schedules prior to network changes that may affect user behavior, dial-in access availability, lowest-level network utilization capabilities supported by service providers, traffic control for various customers, and more.
  • the management system 104 needs to configure a related policy for the control range of the specified application system 101.
  • the management system 104 is responsible for initializing the network elements.
  • the resource objects used by related services include physical resource objects and business resource objects. Since the control plane of the SDN system uses the UUID to identify the resource object, the UUID identifier uses a string of digital identifiers to identify the information of the resource object, and the application in the application system 101 cannot directly present the detailed information of the visualized resource object based on the UUID identifier. .
  • the embodiment of the present application provides a method for managing a resource object in an SDN system, by which an existing network management system and an application in a network management system (for example, management non-SDN) can be reused.
  • the network management system manages the SDN to smoothly evolve the inventory network system to the future-oriented SDN system, so that the resource objects in the SDN system can be managed by using a large number of applications in the existing network management system and the network management system.
  • the user can use the application that can only identify the FDN identifier in the inventory network to manage the resource objects in the SDN system, present the user with detailed resource information that the user can understand, and then manage the resource objects.
  • the management system in the inventory network used herein is not limited to the existing management system, and may be a subsequent improved management system developed by the existing management system.
  • the method for managing resource objects in the SDN system is described in detail below with reference to FIG.
  • the method is applied to the SDN system 100 shown in FIG. 1.
  • the SDN system 100 includes an application system 101, a control system 102, and a management system 104.
  • the control system 102 uses the UUID identification to identify resource objects.
  • the method includes:
  • the management system acquires a UUID identifier of the newly discovered resource object.
  • the UUID identifier refers to a universal unique identifier, which is a software construction standard, and is used by the Open Network Foundation (ONF) organization in designing an SDN system.
  • the UUID identifier uniquely identifies all resource objects in the SDN system and does not repeat.
  • the UUID identifier is a string of numbers generated by the server, similar to a label, which guarantees unique identification of network resources in the same time and space. It guarantees that all elements in the SDN distributed scenario have unique identification information.
  • the UUID universal unique identifier is not limited to the UUID specified by the ONF.
  • identifier forms such as an identifier that uniquely identifies a resource object by using an element that does not have directly identifiable content, may also be referred to as a UUID.
  • UUID User User Interface
  • the management system generates a corresponding complete identification name FDN identifier for the newly discovered resource object.
  • the management system uses the full distinguished name (English: full distinguished name, FDN) identifier Identify resource objects.
  • the index information of the resource object carried in the FDN identifier can be directly viewed by the application in the application system 101 by using the index information of the resource object in the FDN identifier. If the user wants to view the details of the resource object, the FDN identifier can be used to index the details of the corresponding resource object. Thereby, it is ensured that when the user manages the resource object, the user can present information of the resource object that can be understood to the user on the application interface of the application system 101.
  • the resource object identifier only allows single-byte characters and is case-sensitive.
  • the character set that TYPE and VALUE can use includes: all visible ASCII characters and spaces; TYPE is represented by a string abbreviation, and pure numbers are not allowed.
  • the interstage separator uses a half-width comma (,), and the separator for multiple pieces of information in VALUE uses a half-width vertical bar (
  • the sub-card 2 belongs to the sub-slot 4 under the board 2 in the slot 3 in the chassis 1 of the network element 3145951. It can be known from the above example that the visualized resource information can be embodied in the user interface by the FDN identifier.
  • SECS stands for Secure VPN Service
  • SECS Service Type
  • SECSTUNNEL means Secure VPN Service Tunnel
  • SECSTUNNEL Local Device ID
  • the management system adds a mapping relationship between the UUID identifier of the newly discovered resource object and the FDN identifier of the newly discovered resource object to the resource object identifier mapping relationship table, where the resource object identifier mapping relationship table saves the UUID of the resource object.
  • a mapping relationship with the FDN identifier of the resource object is identified.
  • the resource object identifier mapping relationship table is established by: the management system acquiring a UUID identifier of the resource object; the management system generating a corresponding FDN identifier for the resource object; the management system Adding a mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object to the resource object identifier mapping relationship table.
  • the specific form of the resource object mapping relationship table may be implemented in a plurality of different manners, and the corresponding relationship may be expressed in the form of a table or other manners. Any means for establishing such a correspondence relationship that can be conceived by those skilled in the art is covered in the resource object identifier mapping relationship table in the embodiment of the present application.
  • the resource object identifier mapping relationship table may be a mapping relationship structure that does not fill in specific content, or may be a mapping relationship table that already contains specific content.
  • the specific content in the resource object identifier mapping relationship table may include only the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object; or further include basic information of the resource object; or Based on this, a mapping relationship between the basic information of the resource object and the FDN identifier of the resource object is further included.
  • the present application is not limited thereto, and may be referred to as a resource object identifier mapping relationship table in the present application as long as the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is included.
  • the basic information of the resource object may be, for example, a number, a name, or other identifier of the resource object.
  • the resource object includes a physical resource object or a service resource object, and the manner in which the management system obtains the UUID identifier of the physical resource object is different from the manner in which the UUID identifier of the service resource object is obtained.
  • the following steps 301-308 are provided to obtain the UUID identifier of the physical resource object, generate the FDN identifier of the physical resource object, and establish a physical resource including the mapping relationship between the physical resource object UUID identifier and the physical resource object FDN identifier.
  • the management system 104 discovers a new physical resource object.
  • the management system discovers the new physical resource object through automatic discovery or user configuration.
  • the management system 104 allocates a UUID identifier to the newly discovered physical resource object.
  • the UUID identifier may be generated by the management system 104 for the newly discovered physical resource object, and the specific generation process may be automatic random generation and other existing methods, and the UUID identifier and the physical resource object may be Association.
  • the management system 104 generates an FDN identifier corresponding to the UUID identifier.
  • the FDN identifier may be generated by the management system 104 for the newly discovered physical resource object, and the specific generation process may be automatic random generation and other existing methods, and the FDN identifier and the physical resource object may be Association.
  • the goal of the management system 104 is to provide an abstract, unified physical resource object identification for the SDN control system. Therefore, the management system 104 can generally be used as an execution entity for finding physical resource objects to ensure functional cohesion of the SDN control system.
  • the search function of the physical resource object may be completed by the control system 102.
  • the following steps 304-305 provide the discovery and search function of the physical resource object by the control system 102 provided by the control system, as follows:
  • the control system 102 discovers a new physical resource object.
  • the control system 102 allocates a UUID identifier to the newly discovered physical resource object.
  • the UUID identifier may be generated by the control system 102 for the newly discovered physical resource, and the specific generation process may be automatic random generation and other existing methods, and associate the UUID identifier with the physical resource object. .
  • the control system 102 sends the UUID of the newly discovered physical resource object to the management system 104.
  • the management system 104 obtains a UUID identifier of the newly discovered physical resource object.
  • the management system generates an FDN identifier corresponding to the UUID identifier of the newly discovered physical resource object.
  • step 303 The specific manner is the same as step 303 above, and details are not described herein again.
  • the management system 104 establishes a resource object identifier mapping relationship table, where the mapping relationship between the UUID identifier of the physical resource object and the FDN identifier of the physical resource object is saved in the resource object mapping relationship table.
  • the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier and the FDN identifier corresponding to each newly discovered physical resource object.
  • the following steps 309-315 are the service resource object UUID identifier and the service resource object FDN identifier provided by the embodiment of the present application, and the service resource object identifier mapping including the mapping relationship between the service resource object UUID identifier and the service resource object FDN identifier is established.
  • the application system 101 allocates a UUID identifier to the service resource object.
  • the application system 101 when the application system 101 sends a new service request to the control system 102, the corresponding service resource object is configured, and the application system 101 allocates a corresponding UUID to the service resource object when configuring the service resource object.
  • logo when the application system 101 sends a new service request to the control system 102, the corresponding service resource object is configured, and the application system 101 allocates a corresponding UUID to the service resource object when configuring the service resource object.
  • the application system 101 sends the service request and the corresponding UUID identifier of the service resource object to the control system 102 through the northbound interface.
  • the control system 102 receives a UUID identifier of the service resource object, and the service request.
  • the control system 102 notifies the management system 104 of the UUID identifier of the service resource object.
  • the management system 104 obtains a UUID identifier of the service resource object.
  • the management system 104 queries the control system 102 for the service corresponding to the UUID identifier of the service resource object by using the UUID identifier of the service resource object.
  • the management system can query the control system 102 for the service corresponding to the service resource UUID identifier by using the UUID identifier of the service resource, and obtain detailed information of the service, such as a service category, a service content, a service attribute, a service name, and the like.
  • the management system 104 generates a corresponding FDN identifier for the service resource object according to the query result.
  • the management system 104 determines the FDN identifier for the service resource object according to the query result, for example, according to the acquired information of the service resource, such as the service category, the name, and/or the service attribute.
  • the management system 104 adds the mapping relationship between the UUID identifier of the service resource object and the FDN identifier of the service resource object to the resource object identifier mapping relationship table.
  • the generated resource object identifier mapping relationship table described in the foregoing step 303 or 315 only takes the resource object identifier mapping relationship table as a mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the management system may further add basic information of the resource object and/or detailed information of the resource object to the UUID of the resource object.
  • mapping a relationship between the identifier and the FDN identifier of the resource object, thereby generating basic information of the resource object and/or detailed information of the resource object, a UUID identifier of the resource object, and an FDN identifier of the resource object.
  • the application system sends a first query request to the management system, where the first query request carries the basic information of the resource object to be managed, and is used to obtain the FDN identifier of the resource object to be managed.
  • the management system receives the first query request sent by the application system, where the first query request is used to obtain an FDN identifier of the resource object to be managed.
  • the first query request may generate a corresponding query request message according to a message protocol (for example, a RESTCONF protocol) that is exchanged between the existing application system and the management system, where the query request message carries the resource to be managed.
  • a message protocol for example, a RESTCONF protocol
  • the basic information of the object such as the number or name of the resource object to be managed, for example, when the FDN identifier of the board is queried, the query request message carries the network element number, the slot number, and the board number.
  • the management system returns an FDN identifier of the to-be-managed resource object to the application system.
  • the management system 104 may perform basic information about the resource object to be managed carried in the first query request, for example, the above mentioned The number or name of the resource object to be managed is found, and the FDN identifier corresponding to the resource object to be managed is found.
  • the resource object mapping relationship table includes a mapping relationship between the basic information of the resource object to be managed and the FDN identifier of the resource object to be managed, where the management system After receiving the first query request sent by the application system 101, the basic information of the resource object to be managed carried in the first query request, for example, the number of the resource object to be managed mentioned above or The name and the like, and the resource object identifier mapping relationship table finds an FDN identifier corresponding to the resource object to be managed.
  • the management system may directly query the FDN identifier of the resource object that is saved, and determine the FDN of the resource object.
  • the FDN identifier of the resource object may be determined as the FDN identifier of the resource object to be managed.
  • the application system receives an FDN identifier of the to-be-managed resource object returned by the management system.
  • the application system receives the FDN identifier of the resource object to be managed returned by the management system 104, and the user can view the resource object to be managed carried by the FDN identifier through the application interface of the application system 101.
  • Index information For example, when the resource object to be managed is a child card, the index information corresponding to the FDN identifier of the child card that can be viewed by the user through the application interface includes: the number of the network element corresponding to the daughter card, the number of the chassis, and the slot number. The number, the number of the board, and the number of the daughter card.
  • the management system 104 may first obtain the UUID identifier of the resource object to be managed according to the basic information of the resource object to be managed in the first query request, and map the resource object according to the resource object.
  • the relation table obtains the FDN identifier of the resource object to be managed.
  • the application system 101 may manage the resource object to be managed according to the UUID identifier of the resource object to be managed, and further manage the resource object.
  • the method specifically includes:
  • the management system 104 may find, in the resource object identifier mapping relationship table, a UUID identifier corresponding to the FDN identifier of the resource object to be managed, according to the FDN identifier of the resource object to be managed, and The FDN identifier of the resource object to be managed and the UUID identifier of the resource object to be managed are returned to the application system 101.
  • the application system 101 may manage the resource object to be managed according to the UUID identifier of the resource object to be managed, and further manage the resource object.
  • the management system 104 returns the FDN identifier of the to-be-managed resource object and the UUID identifier of the to-be-managed resource object to the application system 101, and may further include:
  • the application system sends a second query request to the management system according to the obtained FDN identifier of the resource object to be managed returned by the management system, where the second query request is used to obtain the resource object to be managed.
  • the UUID identifier, where the second query request carries the FDN identifier of the resource object to be managed.
  • the management system receives the second query request, and queries the resource object identifier mapping relationship table according to the FDN identifier of the resource object to be managed to obtain the UUID identifier of the resource object to be managed.
  • the management system returns a UUID identifier of the to-be-managed resource object to the application system.
  • the management system 104 queries the resource object identifier mapping relationship table according to the FDN identifier of the service resource object to be managed, and obtains a UUID identifier of the service resource object to be managed, and the resource object identifier mapping relationship.
  • the table includes a mapping relationship between the UUID identifier of the service resource object to be managed and the FDN identifier of the service resource object to be managed.
  • the application system receives the UUID identifier of the to-be-managed resource object returned by the management system.
  • the management system 104 receives the application system 101. After the first query request is sent, the FDN identifier of the resource object to be managed and the UUID of the resource object to be managed may be returned to the application system 101.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the resource object to be managed. Details or delete the details of the resource object to be managed.
  • the application system 101 After the application system 101 obtains the FDN identifier of the to-be-managed resource object, the user can view the index information of the to-be-managed resource object identified by the FDN identifier by using the application of the application system 101. Further, the application system may manage the detailed information of the resource object to be managed according to the FDN identifier and/or the UUID identifier of the resource object to be managed, for example, query, modify, delete, etc., thereby enhancing resources in the SDN system. Management of objects.
  • the resource object to be managed includes a physical resource object to be managed or a service resource object to be managed.
  • the method for managing service resource objects in the SDN system provided by the embodiment of the present application is described below with reference to FIG. 4, which applies the SDN system 100 shown in FIG.
  • the application system sends a first query request to the management system, where the first query request message carries the basic information of the service resource object to be managed, and is used to obtain the FDN identifier of the service resource object to be managed.
  • the application system generates a first query request, where the first query request is used to obtain a complete identification name FDN identifier of the service resource object to be managed.
  • the first query request may generate a corresponding query request message according to a message protocol (for example, a RESTCONF protocol) that is exchanged between the existing application system and the management system, where the first query request message carries the service resource to be managed.
  • a message protocol for example, a RESTCONF protocol
  • Basic information of the object such as the service type of the service resource object to be managed, source/sink node information, and the like.
  • the FDN identifiers for the physical resource objects and the service resource objects are all stored in the management system 104. Therefore, when the user manages the service resource object through the application plane, the user first selects a corresponding service resource object to be managed on the application plane, and the application system 101 generates a first query of the service resource object to be managed according to the service resource object to be managed selected by the user. Request for obtaining the The FDN ID of the business resource object to be managed. The application system 101 sends the first query request to the management system 104.
  • the management system receives the first query request sent by the application system.
  • the management system returns an FDN identifier of the service resource object to be managed to the application system.
  • the management plane system 104 After receiving the first query request sent by the application system 101, the management plane system 104, according to the basic information of the resource object to be managed in the first query request, for example, the above mentioned The service type, the node information, and the like of the service resource object to be managed are searched for, and the FDN identifier corresponding to the service resource object to be managed is found, and the FDN identifier is returned to the application system 101.
  • the resource object mapping relationship table stores a mapping relationship between the basic information of the service resource object to be managed and the FDN identifier of the service resource object to be managed, where the management After receiving the first query request sent by the application system 101, the system 104 may use the basic information of the service resource object to be managed carried in the first query request, for example, the service resource object to be managed mentioned above.
  • the service type, the node information, and the like, and the resource object identifier mapping relationship table find the FDN identifier corresponding to the service resource object to be managed.
  • the application system receives an FDN identifier of the to-be-managed service resource object returned by the management system.
  • the application system 101 receives the FDN identifier corresponding to the to-be-managed service resource object returned by the management system 104, and the user can view the FDN identifier through the application interface of the application system 101.
  • the security VNP service is used as an example.
  • the index information corresponding to the FDN identifier of the service that can be viewed by the user through the application interface includes: service type, interface name, and the like.
  • the management system 104 may first obtain the UUID identifier of the service resource object to be managed according to the basic information of the service resource object to be managed in the first query request, and correspondingly according to the resource object.
  • the mapping relationship table acquires the business resource object to be managed FDN logo.
  • the application system 101 may manage the detailed information of the service resource object to be managed according to the UUID identifier of the service resource object to be managed, and strengthen the management of the service resource object.
  • the method specifically includes:
  • the management system 104 may find, in the resource object identifier mapping relationship table, a UUID identifier corresponding to the FDN identifier of the service resource object to be managed, according to the FDN identifier of the service resource object to be managed, and The FDN identifier of the service resource object to be managed and the UUID identifier of the service resource object to be managed are returned to the application system 101.
  • the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier of the service resource object to be managed and the FDN identifier of the service resource object to be managed.
  • the application system 101 may manage the detailed information of the resource object to be managed according to the UUID identifier of the resource object to be managed, and further manage the resource object.
  • the management system 104 returns the FDN identifier of the to-be-managed resource object and the UUID identifier of the to-be-managed resource object to the application system 101, and may further include steps 403-405, steps 503-505:
  • the application system sends a second query request to the management system according to the obtained FDN identifier of the to-be-managed service resource object, where the second query request is used to obtain the UUID identifier of the service resource object to be managed.
  • the second query request carries the FDN identifier of the service resource object to be managed.
  • the FDN identifier of the service resource object is stored in the management system 104, and the detailed information of the service resource object is stored in the control system 102, and the control system 102 identifies the UUID of the service resource object.
  • Index the details of a business resource object.
  • the index information corresponding to the service resource object to be managed can be viewed through the FDN identifier of the service resource object to be managed.
  • the user needs to obtain the corresponding UUID identifier through the FDN identifier of the service resource object to be managed, so as to obtain the detailed information of the service resource object from the control system 102 according to the acquired UUID identifier.
  • the management system receives the second query request sent by the application system.
  • the management system returns, to the application system, the UUID identifier of the service resource object to be managed.
  • the management system 104 queries the resource object identifier mapping relationship table according to the FDN identifier of the service resource object to be managed, and obtains the UUID identifier of the service resource object to be managed, and the resource object identifier mapping.
  • the relationship table includes a mapping relationship between the UUID identifier of the service resource object to be managed and the FDN identifier of the service resource object to be managed.
  • the application system receives, by the management system, a UUID identifier of the to-be-managed service resource object that is obtained according to the resource object identifier mapping relationship table.
  • the management system 104 may identify the FDN of the service resource object to be managed and the to-be-managed The UUID of the service resource object is returned to the application system 101 together.
  • the application system determines, by using a UUID of the service resource object to be managed, the control system to manage detailed information of the service resource object to be managed.
  • the control system 102 stores detailed information of the service resource object to be managed.
  • the application system 101 can query, modify, or delete the detailed information of the service resource object to be managed in the control system 102 by using the UUID identifier of the service resource object to be managed.
  • the application system may obtain detailed information of the service resource object to be managed, and the detailed information is visual information that the user can understand.
  • the application side presents the above information to the user, so that the user can present the visualization information that the user can understand when viewing and managing the detailed information of the service resource object.
  • the following describes the management behaviors of the user to query, modify, or delete the detailed information of the service resource object in the embodiment of the present application.
  • the detailed information of the user querying the service resource object is used as an example, and the service resource object is, for example, an Ethernet service resource object.
  • the user queries the detailed information of the service resource object the user selects the corresponding service resource object through the application interface of the application system 101, and requests to query the detailed information of the service resource object, such as the service category, service content, service attribute, and service. Name and so on.
  • the application system 101 sends the first query request to the management system 104 for acquiring the FDN identifier of the service resource object.
  • the application system 101 receives the FDN identifier of the service resource object to be managed returned by the management system.
  • the application system 101 sends a second query request to the management 104, where the second query request is used to obtain the UUID identifier of the service resource object to be managed, and the second query request carries the service resource object to be managed.
  • the FDN logo The application system 101 receives the UUID identifier of the to-be-managed service resource object that is found by the management system 104 and is found according to the resource object identifier mapping relationship table.
  • the application system 101 sends a sixth query request to the control system 102, where the sixth query request carries the UUID identifier of the service resource object to be managed to query the detailed information of the service resource object to be managed.
  • the application system 101 receives the detailed information of the service resource object to be managed returned by the control system 102.
  • the user may access the resource object to be managed through the application interface of the application system 101. Detailed information for viewing, modifying or deleting related management.
  • the application system 101 sends a third query request to the management system 104, where the third query request carries the information related to the to-be-served Ethernet service resource object to be managed.
  • the UUID identifier of the associated physical resource object is used to obtain the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the application system 101 receives the FDN identifier of the physical resource object associated with the to-be-managed service resource object that is found by the management system 104 according to the resource object identifier mapping relationship table.
  • the application system 101 presents the user with detailed information of the service resource object through the application interface.
  • the service resource object is, for example, an Ethernet service resource object.
  • the user selects a corresponding service resource object through the application interface of the application system 101, and requests to modify detailed information of the service resource object, such as a service category and a service content. Business attributes, business names, and more.
  • the application system 101 sends a first query request to the management system 104 for acquiring the FDN identifier of the service resource object.
  • the application system 101 receives the FDN identifier of the service resource object to be managed returned by the management system.
  • the application system 101 sends a second query request to the management 104, where the second query request is used to obtain the UUID identifier of the service resource object to be managed, and the second query request carries the service resource object to be managed.
  • the FDN logo receives the UUID identifier of the to-be-managed service resource object that is found by the management system 104 and is found according to the resource object identifier mapping relationship table.
  • the application system 101 sends a service resource object information modification request to the control system 102, where the service resource object information modification request carries the UUID identifier of the service resource object to be managed to modify the detailed information of the service resource object to be managed. .
  • the control system 102 configures the modified service resource for the data forwarding system and updates the database to save the detailed information of the modified service resource object.
  • the service resource object may be, for example, a Tailord Line Service Resource Object.
  • the user selects a corresponding service resource object through the application interface of the application system 101, and requests to delete detailed information of the service resource object, such as a service category, a service content, a service attribute, a service name, and the like.
  • the application system 101 sends the first query request to the management system 104 for acquiring the FDN identifier of the service resource object.
  • the application system 101 receives the FDN identifier of the service resource object to be managed returned by the management system.
  • the application system 101 sends the second query request to the management 104, where the second query request is used to obtain the UUID identifier of the service resource object to be managed, and the second query request carries the service to be managed.
  • the FDN ID of the resource object receives the UUID identifier of the to-be-managed service resource object that is found by the management system 104 and is found according to the resource object identifier mapping relationship table.
  • the application system 101 sends a service resource object information deletion request to the control system 102, where the service resource object information deletion request carries the UUID identifier of the service resource object to be managed to delete the detailed information of the service resource object to be managed.
  • the control system 102 deletes the detailed information of the service resource object, the service resource configured for the data forwarding system is deleted and the database is updated.
  • the method for managing physical resource objects in the SDN system provided by the embodiment of the present application is as follows with reference to FIG. The method illustrates that the method uses the SDN system 100 shown in FIG.
  • the application system sends a first query request to the management system, where the first query request carries basic information of the physical resource object to be managed, and is used to obtain a complete identification name FDN identifier of the physical resource object to be managed.
  • the application system 101 generates a first query request, where the first query request may be a corresponding query according to a message protocol (eg, RESTCONF protocol) between the existing application system and the management system.
  • a request message where the first query request message carries the basic information of the resource object to be managed, for example, the number or the name of the physical resource object to be managed, for example, when the FDN identifier of the board is queried, the query request message is Basic information such as the NE number, slot number, and board number of the card.
  • the FDN identifiers for the physical resource objects and the service resource objects are all stored in the management system 104. Therefore, when the user manages the physical resource object through the application plane, the corresponding physical resource object to be managed is first selected on the application surface, and the application system 101 generates a first query of the physical resource object to be managed according to the physical resource object to be managed selected by the user. The request is used to obtain an FDN identifier of the physical resource object to be managed. The application system 101 sends the first query request to the management system 104.
  • the management system receives the first query request sent by the application system.
  • the management system returns an FDN identifier of the physical resource object to be managed to the application system.
  • the management plane system 104 after receiving the first query request sent by the application system 101, the management plane system 104 searches and manages the basic information of the physical resource object to be managed in the first query request.
  • the physical resource object corresponds to the FDN identifier, and the FDN identifier is returned to the application system 101.
  • the application system receives an FDN identifier of the physical resource object to be managed returned by the management system.
  • the application system 101 receives the FDN identifier corresponding to the physical resource object to be managed returned by the management system 104, and the user can pass the application system 101.
  • the application interface views the index information of the service resource object to be managed corresponding to the FDN identifier.
  • the sub-card is used as an example.
  • the index information of the FDN ID of the sub-card that the user can view through the application interface includes: the number of the NE corresponding to the sub-card, the number of the sub-chassis, the number of the slot, and the board number. The number and the number of the daughter card.
  • the resource object mapping relationship table stores a mapping relationship between the basic information of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed.
  • the management system 104 may, according to the basic information of the physical resource object to be managed carried in the first query request, for example, the foregoing mentioned The number or name of the managed physical resource object, and the resource object identifier mapping relationship table finds an FDN identifier corresponding to the resource object to be managed.
  • the method further includes:
  • the application system generates a fourth query request, where the fourth query request carries the FDN identifier of the physical resource object to be managed, and is used to query the management system for detailed information of the physical resource object to be managed.
  • the management system receives the fourth query request, and queries the detailed information of the physical resource object to be managed by using the FDN identifier of the physical resource object to be managed.
  • the management system returns detailed information of the physical resource object to be managed to the application system.
  • the application system receives detailed information about the physical resource object to be managed.
  • the detailed information of the physical resource object to be managed is also queried by the UUID of the physical resource object to be managed, and the method specifically includes:
  • the management system 104 may find, in the resource object identifier mapping relationship table, a UUID identifier corresponding to the FDN identifier of the physical resource object to be managed, according to the FDN identifier of the physical resource object to be managed, and The FDN identifier of the physical resource object to be managed and the UUID identifier of the physical resource object to be managed are returned to the application system 101.
  • the shot relationship table includes a mapping relationship between the UUID identifier of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed.
  • the application system 101 sends a fifth query request to the management system, where the fifth query request carries the UUID identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed.
  • the fifth query request carries the UUID identifier of the physical resource object to be managed, and is used to query the detailed information of the physical resource object to be managed.
  • Receiving, by the management system, the fifth query request acquiring detailed information of the physical resource object to be managed according to the UUID identifier of the physical resource object to be managed, and returning detailed information of the physical resource object to be managed to operating system.
  • the application system is configured to query detailed information of the resource object to be managed, and further manage the resource object.
  • the management system 104 returns the FDN identifier of the physical resource object to be managed and the UUID identifier of the physical resource object to be managed to the application system 101, and may further include:
  • the management system 104 In response to receiving the first query request, the management system 104 returns an FDN identifier of the physical resource object to be managed to the application system 101;
  • the application system 101 receives the FDN identifier of the physical resource object to be managed returned by the management system 104, and generates a second query request, where the second query request is used to obtain the UUID identifier of the physical resource object to be managed.
  • the second query request carries the FDN identifier of the physical resource object to be managed;
  • the management system 104 receives the second query request, and queries the resource object identifier mapping relationship table according to the FDN identifier of the physical resource object to be managed, and obtains the UUID identifier of the physical resource object to be managed.
  • the management system 104 returns the UUID identification of the physical resource object to be managed to the application system 101.
  • the user can view the index information of the physical resource object to be managed identified by the FDN identifier by using the application of the application system 101.
  • the application system 101 may modify or delete the details of the physical resource object to be managed according to the FDN identifier and/or the UUID identifier of the physical resource object to be managed. Information, further management of the physical resource object to be managed.
  • the application system 101 modifies the detailed information of the physical resource object to be managed according to the FDN identifier and/or the UUID identifier of the resource object to be managed, and performs the physical resource object to be managed. Further management, including:
  • the application system sends a physical resource object information modification request to the management system, where the physical resource object information modification request carries the FDN of the physical resource object to be managed and/or the UUID identifier of the physical resource object to be managed. For modifying the detailed information of the physical resource object to be managed.
  • the application system 101 deletes the detailed information of the physical resource object to be managed according to the FDN identifier and/or the UUID identifier of the resource object to be managed, and performs the physical resource object to be managed. Further management, including:
  • the application system sends a physical resource object information deletion request to the management system, where the physical resource object information deletion request carries the FDN of the physical resource object to be managed and/or the physical resource object UUID identifier to be managed, And deleting detailed information of the physical resource object to be managed.
  • the mapping relationship between the UDN ID of the resource object and the FDN identifier of the resource object is saved by establishing a mapping relationship between the FDN identifier of the resource object and the UUID identifier in the management system.
  • the relationship between the existing network management system and the application based on the network management system is slightly modified, that is, the resource object in the SDN system can be managed by the application system, thereby realizing the smooth evolution of the inventory network system to the future SDN system.
  • the user when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object Further, the user may query, modify, or delete the detailed information of the resource object by using the FDN identifier to implement further management of the resource object.
  • FIG. 9A is a tube for managing resource objects in the SDN system shown in FIG. 1 according to an embodiment of the present application.
  • a schematic diagram of the hardware structure of the system which is a management system 104 as shown in FIG. 9A, which is used to perform the methods in the embodiments of FIGS. 2-8.
  • a management system for managing resource objects in a software-defined network SDN system comprising: the management system 104, an application system 101, and a control system 102; the control system 102 identifies using a universally unique identifier UUID identifier
  • the resource object; the management system 104 includes a processor 601 and a network interface 602, a memory 603.
  • the processor 601 communicates with the application system 101 and the control system 102 via the network interface 602.
  • Processor 601, memory 603, and network interface 602 can communicate over bus 604.
  • the processor 601 is configured to obtain a UUID identifier of the newly discovered resource object, generate a corresponding complete identifier FDN identifier for the newly discovered resource object, and identify the UUID of the newly discovered resource object with the The mapping relationship of the FDN identifier of the newly discovered resource object is added to the resource object identifier mapping relationship table, where the resource object identifier mapping relationship table stores the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the memory 603 is configured to store the resource object identifier mapping relationship table.
  • the network interface 602 is configured to receive a first query request of the resource object to be managed sent by the application system, where the first query request includes basic information of the resource object to be managed, and the first query Requesting an FDN identifier for obtaining the resource object to be managed.
  • the processor 601 is further configured to acquire an FDN identifier of the to-be-managed resource object according to the basic information of the resource object to be managed.
  • the network interface 602 is configured to return an FDN identifier of the to-be-managed resource object to the application system 101.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management system in the inventory network system can be
  • the application of the network management system that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user accesses the resource through the management interface of the application system.
  • the FDN identifier of the resource object is obtained, and the user can present the visualized resource object information through the management interface, so that the user can query the basic index information of the resource object.
  • the processor 601 when the newly discovered resource object is a newly discovered physical resource object, the processor 601 is configured to acquire, from the control system 102, a UUID identifier of the newly discovered physical resource object. And generating a corresponding FDN identifier for the newly discovered physical resource object, and adding a mapping relationship between the UUID identifier of the newly discovered physical resource object and the FDN identifier of the newly discovered physical resource object to the resource object identifier Mapping relational tables.
  • the processor 601 when the newly discovered resource object is a newly discovered physical resource object, the processor 601 is configured to allocate a UUID identifier to the newly discovered physical resource object, where the new The discovered physical resource object generates a corresponding FDN identifier, and adds a mapping relationship between the UUID identifier of the newly discovered physical resource object and the FDN identifier of the newly discovered physical resource object to the resource object identifier mapping relationship table.
  • the processor 601 when the newly discovered resource object is a service resource object, the processor 601 is configured to acquire, from the control system 102, a UUID identifier of the service resource object, according to the service.
  • the UUID identifier of the resource object queries the control system 102 for the corresponding service, and generates an FDN identifier for the service resource object according to the query result, and is used to identify the UUID of the service resource object and the FDN identifier of the service resource object.
  • the mapping relationship is added to the resource object identifier mapping relationship table.
  • the UUID of the service resource object can be sent by the application system 101 to the control system 102 through the northbound interface.
  • the processor 601 is further configured to acquire, according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table, a UUID identifier of the resource object to be managed.
  • the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed, and the UUID identifier of the resource object to be managed is used by the application system. For managing the detailed information of the resource object to be managed;
  • the network interface 602 is configured to return, to the application system, a UUID identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource objects in the SDN system, for example, query, modify, delete, etc., through the FDN identifier, thereby enhancing management of resources in the SDN system.
  • the network interface 602 is further configured to receive a second query request sent by the application system, where the second query request is used to obtain a UUID identifier of the resource object to be managed, The second query request carries the FDN identifier of the resource object to be managed;
  • the processor 601 is further configured to acquire, according to the FDN identifier of the resource object to be managed carried in the second query request, the UUID identifier of the resource object to be managed.
  • the detailed information of the resource object to be managed that is to be queried is the detailed information of the service resource object to be managed, and the detailed information of the service resource object to be managed includes the identifier identified by using the UUID.
  • the network interface 602 is further configured to receive a third query request sent by the application system 101, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, And an FDN identifier used to obtain the physical resource object associated with the service resource object to be managed.
  • the processor 601 is further configured to query the resource object identifier mapping relationship table according to the UUID identifier of the physical resource object associated with the service resource object to be managed, and obtain the service to be managed.
  • An FDN identifier of a physical resource object associated with the resource object, the resource object identifier mapping relationship table including the physical resource pair associated with the service resource object to be managed A mapping relationship between the UUID identifier of the image and the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the network interface 602 is further configured to return, to the application system 101, the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the resource object to be managed is a physical resource object to be managed
  • the processor 601 is configured to acquire the FDN identifier of the physical resource object to be managed.
  • the network interface 602 is configured to return the physical resource object FDN identifier to be managed to the application system 101, and receive a fourth query request sent by the application system, where the fourth query request carries the to-be-managed The FDN identifier of the physical resource object, used to index the detailed information of the physical resource object to be managed;
  • the processor 601 is further configured to: by using an FDN identifier of the physical resource object to be managed, index the detailed information of the physical resource object to be managed;
  • the network interface 602 is further configured to return, to the application system 101, detailed information of the physical resource object to be managed.
  • the resource object to be managed is a physical resource object to be managed
  • the processor 601 is specifically configured to acquire the physical resource object FDN identifier to be managed.
  • the network interface 602 is specifically configured to return the physical resource object FDN identifier to be managed to the application system 101.
  • the processing unit is further configured to acquire, according to the FDN identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table, a UUID identifier of the physical resource object to be managed, and the resource object identifier mapping relationship table. And a mapping relationship between the UUID identifier of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed, where the UUID identifier of the physical resource object to be managed is used by the application system 101 for querying The detailed information of the physical resource object to be managed.
  • the network interface 602 is configured to return a UUID identifier of the physical resource object to be managed to the application system 101, and receive a fifth query request sent by the application system 101, where the fifth query request carries the The UUID identifier of the physical resource object to be managed is used to query the detailed information of the physical resource object to be managed.
  • the processor 601 is further configured to acquire detailed information of the physical resource object to be managed by using a UUID identifier of the physical resource object to be managed.
  • the network interface 602 is further configured to return, to the application system 101, detailed information of the physical resource object to be managed.
  • the network interface 602 is further configured to receive a physical resource object information modification request sent by the application system 101, where the physical resource object information modification request carries the physical resource object to be managed.
  • the FDN identifier and/or the UUID of the physical resource object to be managed are used to modify the detailed information of the physical resource object to be managed.
  • the processor 601 is further configured to modify the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • the network interface 602 is configured to receive a physical resource object information deletion request sent by the application system 101, where the physical resource object information deletion request carries an FDN of the physical resource object to be managed.
  • the UUID of the physical resource object that is identified and/or to be managed is used to delete the detailed information of the physical resource object to be managed.
  • the processor 601 is further configured to delete the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • the processor 601 may be one or more central processing units (CPUs).
  • the CPU may be a single core CPU or a multi-core CPU.
  • the network interface 602 can be a wired interface, such as a Fiber Distributed Data Interface (FDDI) or a Gigabit Ethernet (GE) interface.
  • FDDI Fiber Distributed Data Interface
  • GE Gigabit Ethernet
  • the memory 603 may be, but not limited to, one of a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM), a compact disk read only memory (CD-ROM), a hard disk, or the like. A variety.
  • RAM random access memory
  • ROM read only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • hard disk or the like.
  • the memory 603 is used to store program instruction code
  • the processor 601 is configured to execute the instruction code in the memory 603 to complete the method of the embodiment corresponding to FIG. 2-8.
  • FIG. 9B is a schematic diagram showing the hardware structure of an application system for managing resource objects in the SDN system shown in FIG. 1 according to an embodiment of the present application.
  • the application system is the application system 101 shown in FIG. 9B.
  • the application system 101 is for performing the methods of the embodiments of Figures 2-8.
  • An application system 101 for managing resource objects in a software-defined network SDN system 100 comprising: a management system 104, an application system 101, and a control system 102.
  • Control system 102 identifies the resource object using a universally unique identifier UUID identification.
  • the management system 104 maintains a resource object identifier mapping relationship table of the FDN identifier of the resource object and the UUID identifier mapping relationship of the resource object.
  • the application system 101 can include a processor 701 and a network interface 702.
  • the processor 701 and the network interface 702 communicate via the bus 704.
  • the processor 701 communicates with the management system 104, the control system 102 via the network interface 702.
  • the processor 701 is configured to generate a first query request, where the first query request includes basic information of a resource object to be managed, and the first query request is used to obtain an FDN identifier of the resource object to be managed.
  • the network interface 702 is configured to send the first query request to the management system 104.
  • the network interface 702 is further configured to receive an FDN identifier of the resource object to be managed returned by the management system 104, where the resource object identifier mapping relationship table stores an FDN identifier of the resource object to be managed.
  • the processor 701 is configured to manage the resource object to be managed by using an FDN identifier of the resource object to be managed.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, and the inventory network is
  • the network management system and the application based on the network management system in the network system are slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the network interface 702 is further configured to receive, by the management system, the to-be-managed according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the resource object to be managed. Details or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource object in the SDN system by using the FDN identifier of the resource object to be managed, for example, query, modify, and delete (see the following implementation manner), etc., thereby Strengthen the management of resources in the SDN system.
  • the network interface is further configured to send a second query request to the management system, where the second query request carries the FDN identifier of the resource object to be managed, and is used to obtain the The UUID identifier of the resource object to be managed.
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed;
  • the FDN identifier of the resource object is the FDN identifier of the service resource object to be managed.
  • the processor 701 is further configured to generate the second query request, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, where the second query request carries the The FDN ID of the managed business resource object.
  • the network interface 702 is further configured to send the second query request to the control system 102.
  • the network interface 702 is further configured to receive, by the management system 104, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the processor 701 is further configured to generate a sixth query request, where the sixth query request carries the UUID identifier of the service resource object to be managed to query the to-be-managed Details of the business resource object.
  • the network interface 702 is further configured to send the sixth query request to the control system 102.
  • the network interface is further configured to receive detailed information about the service resource object to be managed returned by the control system 102.
  • the detailed information of the service resource object to be managed includes a physical resource object that is associated with the service resource object to be managed identified by the UUID
  • the processor 701 is further configured to generate a third query request, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, and is used to obtain the An FDN identifier of a physical resource object associated with the service resource object to be managed.
  • the network interface 702 is further configured to send the third query request to the management system 104, and receive the physical resource object associated with the service resource object to be managed returned by the management system 104.
  • An FDN identifier; the FDN identifier of the physical resource object associated with the to-be-managed service resource object and the UUID identifier of the physical resource object associated with the to-be-managed service resource object are saved in the management system
  • the resource object is identified in the mapping relationship table.
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed;
  • the FDN identifier of the resource object is the FDN identifier of the service resource object to be managed.
  • the network interface 702 is further configured to send the second query request to the control system 102, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, and the second query request
  • the FDN identifier of the service resource object to be managed is carried in the middle.
  • the network interface 702 is further configured to receive, by the management system 104, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the network interface 702 is further configured to send a service resource object information modification request to the control system 102, where the service resource object information modification request carries a UUID identifier of the service resource object to be managed to manage the to-be-managed Details of managed business resource objects.
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed;
  • the FDN identifier of the resource object is the FDN identifier of the service resource object to be managed.
  • the network interface 702 is further configured to send the second query request to the control system 102, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, and the second query request
  • the FDN identifier of the service resource object to be managed is carried in the middle.
  • the network interface 702 is further configured to receive, by the management system 104, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the network interface 702 is further configured to send a service resource object information deletion request to the control system 102, where the service resource object information deletion request carries a UUID identifier of the service resource object to be managed to manage the to-be-managed Details of managed business resource objects.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; the resource object to be managed The FDN identifier is an FDN identifier of the physical resource object to be managed.
  • the network interface 702 is further configured to send a fourth query request to the management system 104, where the fourth query request carries an FDN identifier of the physical resource object to be managed, and is used to query the physical resource to be managed. The details of the object.
  • the network interface 702 is further configured to receive detailed information about the physical resource object to be managed returned by the management system 104.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; the resource object to be managed The FDN identifier is an FDN identifier of the physical resource object to be managed.
  • the processor 701 is further configured to generate a physical resource object information modification request, where the physical resource is
  • the object information modification request carries the FDN identifier of the physical resource object to be managed, and is used to modify the detailed information of the physical resource object to be managed.
  • the network interface 702 is further configured to send the physical resource object information modification request to the management system 104.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; the resource object to be managed The FDN identifier is an FDN identifier of the physical resource object to be managed.
  • the processor 701 is further configured to generate a physical resource object information deletion request, where the physical resource object information deletion request carries an FDN identifier of the physical resource object to be managed, and is used to delete the physical resource object to be managed. details.
  • the network interface 702 is further configured to send a physical resource object information deletion request to the management system.
  • the network interface 702 is configured to send a second query request to the management system 104, where the second query request is used for Obtaining a UUID identifier of the physical resource object to be managed, where the second query request carries an FDN identifier of the physical resource object to be managed.
  • the network interface 702 is configured to receive, by the management system 104, a UUID identifier of the physical resource object to be managed that is searched according to the resource object identifier mapping relationship table.
  • the network interface 702 is further configured to send a fifth query request to the management system 104, where the fifth query request carries a UUID identifier of the physical resource object to be managed, and is used to Query the detailed information of the physical resource object to be managed.
  • the network interface 702 is further configured to receive, by the management unit 104, detailed information about the physical resource object to be managed acquired by the UUID identifier of the physical resource object to be managed.
  • the network interface 702 is further configured to send a physical resource object information modification request to the management system 104, where the physical resource object information modification request carries the UUID of the physical resource object to be managed.
  • An identifier configured to modify the physical resource object to be managed details.
  • the network interface 702 is further configured to send a physical resource object information deletion request to the management system 104, where the physical resource object information deletion request carries the UUID of the physical resource object to be managed.
  • the identifier is used to delete the detailed information of the physical resource object to be managed.
  • the application system 101 can include a processor 701, a network interface 702, and a memory 703.
  • Processor 701, network interface 702, and memory 703 communicate over bus 704.
  • the processor 701 communicates with the management system 104, the control system 102 via the network interface 702.
  • the memory 703 is used to store the program instruction code, and the processor 701 is configured to execute the instruction code in the memory 603 to complete the method of the embodiment corresponding to FIG. 2-8.
  • the memory 703 may be, but not limited to, one of a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM), a compact disk read only memory (CD-ROM), a hard disk, or the like. A variety.
  • RAM random access memory
  • ROM read only memory
  • EPROM erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • hard disk or the like.
  • the memory 603 and the memory 703 are used to store program codes.
  • the processor 701 can be one or more central processing units (English: Central Processing Units, CPUs). In the case where the processor 701 is a CPU, the CPU may be a single core CPU or a multi-core CPU.
  • CPUs Central Processing Units
  • the network interface 702 can be a wired interface, such as a Fiber Distributed Data Interface (FDDI) or a Gigabit Ethernet (GE) interface.
  • FDDI Fiber Distributed Data Interface
  • GE Gigabit Ethernet
  • the management system and the application system of the management resource object in the SDN system establish a mapping relationship table between the FDN identifier and the UUID identifier of the resource object in the management system, and save the UUID identifier of the resource object and the resource object.
  • the mapping relationship between the FDN identifiers and the existing network management system and the application based on the network management system are smallly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing the inventory network system to the future SDN system. Smooth evolution.
  • the user when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can be visualized through the management interface.
  • Resource object information for the user to query the basic index information of the resource object. Further, the user may query, modify, or delete the detailed information of the resource object by using the FDN identifier to implement further management of the resource object.
  • FIG. 10A is a schematic diagram of a management system for managing resource objects in the SDN system shown in FIG. 1 according to an embodiment of the present application.
  • the management system is a hardware having the function of performing the method in the embodiment shown in FIG. 2-8. device.
  • a management system for managing resource objects in the SDN system includes: the management system, an application system, and a control system; the control system 102 uses a universally unique identifier UUID identifier to identify a resource object
  • the system includes: a receiving unit 1001, a processing unit 1002, and a sending unit 1003;
  • the processing unit 1002 is configured to acquire a UUID identifier of the newly discovered resource object, generate a corresponding complete identifier FDN identifier for the newly discovered resource object, and identify the UUID of the newly discovered resource object with the The mapping relationship of the FDN identifier of the newly discovered resource object is added to the resource object identifier mapping relationship table, where the resource object identifier mapping relationship table stores the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the receiving unit 1001 is configured to receive a first query request of the resource object to be managed sent by the application system 101, where the first query request includes basic information of the resource object to be managed, the first The query request is used to obtain the FDN identifier of the resource object to be managed.
  • the processing unit 1002 is further configured to acquire an FDN identifier of the to-be-managed resource object according to the basic information of the resource object to be managed.
  • the sending unit 1003 is configured to return an FDN identifier of the to-be-managed resource object to the application system 101.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved, so that the network management system in the inventory network system can be And a small number of transformations based on the application of the network management system, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing the inventory network system Smooth evolution to the SDN system.
  • the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object.
  • the newly discovered resource object is a newly discovered physical resource object
  • the processing unit 1002 is configured to allocate a UUID identifier for the newly discovered physical resource object, generate a corresponding FDN identifier for the newly discovered physical resource object, and identify a UUID of the newly discovered physical resource object.
  • the mapping relationship of the FDN identifier of the newly discovered physical resource object is added to the resource object identifier mapping relationship table.
  • the newly discovered resource object is a newly discovered physical resource object
  • the receiving unit 1001 is configured to acquire, from the control system 102, a UUID identifier of the newly discovered physical resource object.
  • the processing unit 1002 is configured to generate a corresponding FDN identifier for the newly discovered physical resource object, and identify the UUID of the newly discovered physical resource object and the FDN identifier of the newly discovered physical resource object.
  • the mapping relationship is added to the resource object identifier mapping relationship table.
  • the processing unit 1002 is configured to acquire, from the control system 102, a UUID identifier of the service resource object, according to the service.
  • the UUID identifier of the resource object queries the control system 102 for the corresponding service, and generates an FDN identifier for the service resource object according to the query result, and identifies the UUID of the service resource object and the FDN identifier of the service resource object.
  • the mapping relationship is added to the resource object identifier mapping relationship table.
  • the processing unit 1002 is further configured to acquire, according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table, a UUID identifier of the resource object to be managed,
  • the resource object identifier mapping relationship table includes the resource object to be managed A mapping relationship between the UUID identifier and the FDN identifier of the resource object to be managed, and the UUID identifier of the resource object to be managed is used by the application system 101 to index the detailed information of the resource object to be managed.
  • the sending unit 1003 is configured to return, to the application system 101, a UUID identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource objects in the SDN system, for example, query, modify, delete, etc., through the FDN identifier, thereby enhancing management of resources in the SDN system.
  • the receiving unit 1001 is further configured to receive a second query request sent by the application system 101, where the second query request is used to obtain a UUID identifier of the resource object to be managed.
  • the second query request carries the FDN identifier of the resource object to be managed.
  • the processing unit 1002 further acquires the UUID identifier of the resource object to be managed according to the FDN identifier of the resource object to be managed carried in the second query request.
  • the detailed information of the resource object to be managed that is to be queried is the detailed information of the service resource object to be managed, and the detailed information of the service resource object to be managed includes the UUID identifier.
  • the physical resource object associated with the business resource object to be managed is associated with
  • the receiving unit 1001 is further configured to receive a third query request sent by the application system 101, where the third query request carries the UUID of the physical resource object associated with the service resource object to be managed. And an identifier, configured to acquire the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the processing unit 1002 is further configured to be associated with the service resource object to be managed according to the
  • the UUID identifier of the physical resource object queries the resource object identifier mapping relationship table, and acquires the FDN identifier of the physical resource object associated with the service resource object to be managed, where the resource object identifier mapping relationship table includes the a mapping relationship between a UUID identifier of the physical resource object associated with the service resource object to be managed and an FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the sending unit 1003 is further configured to return, to the application system 101, the FDN identifier of the physical resource object associated with the service resource object to be managed.
  • the resource object to be managed is a physical resource object to be managed
  • the processing unit 1002 is configured to acquire the physical resource object FDN identifier to be managed.
  • the sending unit 1003 is configured to return the physical resource object FDN identifier to be managed to the application system 101.
  • the receiving unit 1001 is further configured to receive a fourth query request sent by the application system 101, where the fourth query request carries an FDN identifier of the physical resource object to be managed, and is used to query the physics to be managed. The details of the resource object.
  • the processing unit 1002 is further configured to query, by using an FDN identifier of the physical resource object to be managed, detailed information of the physical resource object to be managed;
  • the sending unit 1003 is further configured to return, to the application system 101, detailed information of the physical resource object to be managed.
  • the resource object to be managed is a physical resource object to be managed
  • the processing unit 1002 is configured to acquire the physical resource object FDN identifier to be managed.
  • the sending unit 1003 is configured to return the physical resource object FDN identifier to be managed to the application system 101.
  • the processing unit 1002 is further configured to acquire, according to the FDN identifier of the physical resource object to be managed and the resource object identifier mapping relationship table, a UUID identifier of the physical resource object to be managed.
  • the resource object identifier mapping relationship table includes a mapping relationship between the UUID identifier of the physical resource object to be managed and the FDN identifier of the physical resource object to be managed, and the UUID of the physical resource object to be managed. The detailed information used by the application system 101 to query the physical resource object to be managed is identified.
  • the sending unit 1003 is configured to return, to the application system 101, a UUID identifier of the physical resource object to be managed.
  • the receiving unit 1001 is further configured to receive a fifth query request sent by the application system 101, where the fifth query request carries a UUID identifier of the physical resource object to be managed, and is used to query the physics to be managed. The details of the resource object.
  • the processing unit 1002 is further configured to acquire detailed information of the physical resource object to be managed by using a UUID identifier of the physical resource object to be managed.
  • the sending unit 1003 is further configured to return, to the application system 101, detailed information of the physical resource object to be managed.
  • the receiving unit 1001 is further configured to receive a physical resource object information modification request sent by the application system 101, where the physical resource object information modification request carries the physical resource object to be managed.
  • the FDN identifier and/or the UUID of the physical resource object to be managed are used to modify the detailed information of the physical resource object to be managed.
  • the processing unit 1002 is further configured to modify the detailed information of the physical resource object to be managed by the FDN identifier of the physical resource object to be managed and/or the UUID of the physical resource object to be managed.
  • the receiving unit 1001 is configured to receive a physical resource object information deletion request sent by the application system 101, where the physical resource object information deletion request carries an FDN of the physical resource object to be managed.
  • the UUID of the physical resource object that is identified and/or to be managed is used to delete the detailed information of the physical resource object to be managed.
  • the processing unit 1002 is further configured to delete the detailed information of the physical resource object to be managed by using an FDN identifier of the physical resource object to be managed and/or a UUID of the physical resource object to be managed.
  • FIG. 10B shows a management resource object in the SDN system shown in FIG. 1 according to an embodiment of the present application.
  • the application system is a hardware device having the functions of the method in the embodiment shown in Figures 2-8.
  • an application system for managing resource objects in the SDN system includes a management system, the application system, and a control system; the control system uses a universally unique identifier UUID identifier to identify a resource object,
  • the resource system identifier mapping relationship table in which the management system 104 holds the mapping between the FDN identifier of the resource object and the UUID identifier of the resource object includes: a sending unit 2001, a processing unit 2002, and a receiving unit 2003, where
  • the processing unit 2002 is configured to generate a first query request, where the first query request includes basic information of the resource object to be managed, and the first query request is used to obtain an FDN identifier of the resource object to be managed. .
  • the sending unit 2001 is configured to send the first query request to the management system 104.
  • the receiving unit 2003 is configured to receive an FDN identifier of the resource object to be managed returned by the management system 104, where the resource object identifier mapping relationship table stores an FDN identifier of the resource object to be managed.
  • the processing unit 2002 is configured to manage the resource object to be managed by using an FDN identifier of the resource object to be managed.
  • the mapping relationship between the UUID identifier of the resource object and the FDN identifier of the resource object is saved by creating the resource object identifier relationship table in the management system, and the network management system in the inventory network system is based on
  • the application of the network management system is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the user when the user manages the resource object through the management interface of the application system, by acquiring the FDN identifier of the resource object, the user can present the visualized resource object information through the management interface, so that the user can query the resource.
  • the basic index information of the object is slightly modified, that is, the resource objects in the SDN system can be managed by the application system, thereby implementing a smooth evolution of the inventory network system to the SDN system.
  • the receiving unit is further configured to receive, by the management system, the to-be-managed resource obtained according to the FDN identifier of the to-be-managed resource object and the resource object identifier mapping relationship table.
  • UUID identifier of the object, the resource object identifier mapping relationship table saves the package And a mapping relationship between the UUID identifier of the resource object to be managed and the FDN identifier of the resource object to be managed.
  • the UUID identifier of the resource object to be managed is used by the application system to manage the detailed information of the resource object to be managed, and the specific information may include querying the detailed information of the resource object to be managed, and modifying the to-be-managed Details of the resource object or delete the details of the resource object to be managed.
  • the user can further manage the detailed information of the resource object in the SDN system by using the FDN identifier of the resource object to be managed, for example, query, modify, and delete (see the following implementation manner), etc., thereby Strengthen the management of resources in the SDN system.
  • the sending unit is further configured to send a second query request to the management system, where the second query request carries an FDN identifier of the resource object to be managed, and is used to obtain a The UUID identifier of the resource object to be managed.
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed;
  • the FDN identifier of the resource object is the FDN identifier of the service resource object to be managed.
  • the processing unit 2002 is configured to generate the second query request, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, where the second query request carries the to-be-managed The FDN identifier of the business resource object.
  • the sending unit 2001 is further configured to send a second query request to the control system 102.
  • the receiving unit 2003 is further configured to receive, by the management system 104, a UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table;
  • the processing unit 2002 is further configured to generate a sixth query request, where the sixth query request carries the UUID identifier of the service resource object to be managed to manage the detailed information of the service resource object to be managed.
  • the sending unit 2001 is further configured to send a sixth query request to the control system 102.
  • the receiving unit 2003 is further configured to receive the to-be-managed industry returned by the control system 102. Details of the resource object.
  • the detailed information of the service resource object to be managed includes a physical resource object that is associated with the service resource object to be managed identified by the UUID
  • the processing unit 2002 is further configured to generate a third query request, where the third query request carries the UUID identifier of the physical resource object associated with the service resource object to be managed, and is used to obtain the An FDN identifier of a physical resource object associated with the service resource object to be managed.
  • the sending unit 2001 is further configured to send the fourth query request to the management system 104.
  • the receiving unit 2003 is further configured to receive the FDN identifier of the physical resource object associated with the service resource object to be managed returned by the management system 104.
  • the FDN identifier of the physical resource object associated with the service resource object to be managed and the UUID identifier of the physical resource object associated with the service resource object to be managed are saved in the resource of the management system 104.
  • the object ID is mapped in the relationship table.
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed;
  • the FDN identifier of the resource object is an FDN identifier of the service resource object to be managed;
  • the processing unit 2002 is further configured to generate the second query request, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, where the second query request carries the The FDN ID of the managed business resource object.
  • the sending unit 2001 is further configured to send the second query request to the control system 102.
  • the receiving unit 2003 is further configured to receive, by the management system 104, the UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the processing unit 2002 is further configured to generate the service resource object information modification request, where the service resource object information modification request carries the UUID identifier of the service resource object to be managed to manage the service resource to be managed. The details of the object.
  • the sending unit 2001 is further configured to send the service resource object information modification request to the control system 102.
  • the resource object to be managed is a service resource object to be managed
  • the first query request is used to obtain an FDN identifier of the service resource object to be managed.
  • the FDN identifier of the resource object to be managed is an FDN identifier of the service resource object to be managed.
  • the processing unit 2002 is further configured to generate the second query request, where the second query request is used to obtain a UUID identifier of the service resource object to be managed, where the second query request carries the The FDN ID of the managed business resource object.
  • the sending unit 2001 is further configured to send the second query request to the control system 102.
  • the receiving unit 2003 is further configured to receive, by the management system 104, the UUID identifier of the to-be-managed service resource object that is found according to the resource object identifier mapping relationship table.
  • the processing unit 2002 is further configured to generate a service resource object information deletion request, where the service resource object information deletion request carries the UUID identifier of the service resource object to be managed to manage the service resource object to be managed. details.
  • the sending unit 2001 is further configured to send the service resource object information deletion request to the control system 102.
  • the resource object to be managed is a physical resource object
  • the first query request is used to obtain an FDN identifier of the physical resource object to be managed.
  • the FDN identifier of the resource object to be managed is an FDN identifier of the physical resource object to be managed.
  • the processing unit 2002 is further configured to generate a fourth query request, where the fourth query request carries an FDN identifier of the physical resource object to be managed, and is used to query detailed information of the physical resource object to be managed.
  • the sending unit 2001 is further configured to send the fourth query request to the management system 104.
  • the receiving unit 2003 is further configured to receive detailed information about the physical resource object to be managed returned by the management system 104.
  • the resource object to be managed is a physical resource object
  • the first query request is used to obtain an FDN identifier of the physical resource object to be managed
  • the FDN identifier of the resource object to be managed is an FDN identifier of the physical resource object to be managed.
  • the processing unit 2002 is further configured to generate a physical resource object information modification request, where the physical resource object information modification request carries an FDN identifier of the physical resource object to be managed, and is used to modify the physical resource object to be managed. details.
  • the sending unit 2001 is further configured to send the physical resource object information modification request to the management system 104.
  • the resource object to be managed is a physical resource object
  • the first query request is used to obtain an FDN identifier of the physical resource object to be managed
  • the FDN identifier of the resource object to be managed is an FDN identifier of the physical resource object to be managed.
  • the processing unit 2002 is further configured to generate a physical resource object information deletion request, where the physical resource object information deletion request carries an FDN identifier of the physical resource object to be managed, and is used to delete the physical resource object to be managed. details.
  • the sending unit 2001 is further configured to send the physical resource object information deletion request to the management system 104.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; the resource object to be managed The FDN identifier is an FDN identifier of the physical resource object to be managed.
  • the sending unit 2001 is configured to send a second query request to the management system 104, where the second query request is used to obtain a UUID identifier of the physical resource object to be managed, where the second query request carries The FDN identifier of the physical resource object to be managed.
  • the receiving unit 2003 is configured to receive, by the management system 104, a UUID identifier of the physical resource object to be managed that is searched according to the resource object identifier mapping relationship table.
  • the sending unit 2001 is further configured to send a fifth query request to the management system 104, where the fifth query request carries a UUID identifier of the physical resource object to be managed, and is used to query the physical resource to be managed. The details of the object.
  • the receiving unit 2003 receives the detailed information of the physical resource object to be managed acquired by the UUID identifier of the physical resource object to be managed returned by the management unit.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; and the resource object to be managed
  • the FDN identifier is an FDN identifier of the physical resource object to be managed.
  • the sending unit 2001 is configured to send a second query request to the management system 104, where the second query request is used to obtain a UUID identifier of the physical resource object to be managed, where the second query request carries The FDN identifier of the physical resource object to be managed.
  • the receiving unit 2003 is configured to receive, by the management system 104, a UUID identifier of the physical resource object to be managed that is searched according to the resource object identifier mapping relationship table.
  • the sending unit 2001 is further configured to send a physical resource object information modification request to the management system 104, where the physical resource object information modification request carries a UUID identifier of the physical resource object to be managed, and is used to modify the to-be-modified Details of managed physical resource objects.
  • the first query request is used to acquire an FDN identifier of the physical resource object to be managed; and the resource object to be managed The FDN identifier is an FDN identifier of the physical resource object to be managed; the method further includes:
  • the sending unit 2001 is configured to send a second query request to the management system 104, where the second query request is used to obtain a UUID identifier of the physical resource object to be managed, where the second query request carries The FDN identifier of the physical resource object to be managed.
  • the receiving unit 2003 is configured to receive, by the management system 104, a UUID identifier of the physical resource object to be managed that is searched according to the resource object identifier mapping relationship table.
  • the sending unit 2001 is further configured to send a physical resource object letter to the management system 104 system.
  • the content deletion request, the physical resource object information deletion request carries the UUID identifier of the physical resource object to be managed, and is used to delete the detailed information of the physical resource object to be managed.
  • the management system embodiment provided in FIG. 10A and the application system embodiment provided in FIG. 10B are applied to the SDN system shown in FIG. 1 to implement the functions of the management system and the application system.
  • the processing unit 1002 in FIG. 10A can be implemented by the processor 601 of FIG. 9A, and one or more of the receiving unit 1001 and the sending unit 1003 can be implemented by the network interface 602 of FIG. 9A.
  • the processing unit 2002 in FIG. 10B can be implemented with the processor 701 of FIG. 9B, and one or more of the receiving unit 2003 and the transmitting unit 2001 can be implemented by the network interface 702 of FIG. 9B.
  • the steps implemented by the processing unit 1002 in FIG. 10A may be performed by other hardware than the processor, such as a dedicated logic circuit or a specific integrated circuit (English name: Application Specific Integrated Circuit, ASIC) or field editable logic gate array (English full name: Field Programmable Gate Array, FPGA); or through other hardware; can also be implemented by other hardware or firmware combined with a general purpose processor.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the steps implemented by the processing unit 2002 in FIG. 10B may be performed by other hardware than the processor, see the description of the processing unit 1002 in FIG. 10A, and details are not described herein again.
  • the management system and the application system provided in the above embodiments of the present application are only illustrated by the division of the above functional modules.
  • the functions may be assigned with different functional modules as needed, that is, the internals of the device.
  • the structure is divided into different functional modules to perform all or part of the functions described above.
  • the plurality of units or components described above may be combined or integrated into another system, or some features may be omitted or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the embodiment of the present application further provides an SDN communication system, including a management system and an application system
  • the management system may be the management system provided by the embodiment corresponding to FIG. 9A and FIG. 10A.
  • the application system may be the application system provided by the embodiment corresponding to FIG. 9B and FIG. 10B.
  • the management system and the application system are for performing the methods of the embodiments corresponding to FIGS. 2-8.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Human Computer Interaction (AREA)
  • Computational Linguistics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种SDN系统中管理资源对象的方法和装置，该方法包括：管理系统将新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表。管理系统接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求用于获取所述待管理的资源对象的FDN标识。管理系统向应用系统返回所述待管理的资源对象的FDN标识。该方法对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以使用应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。

Description

一种管理资源对象的方法和系统 技术领域
本申请涉及通信技术领域，尤其涉及一种管理资源对象的方法和系统。
背景技术
近年来，软件定义网络(英文全称：Software Define Network，SDN)的价值已经得到电信网络运营商的认可，是未来网络的演进方向，采用SDN技术，将网络设备SDN控制面与SDN数据面分离开来，实现网络流量的灵活控制，加快了网络业务的创新。当前主流SDN控制面采用通用唯一识别码(英文全称：Universally Unique Identifier，UUID)标识资源对象，能够唯一标识分布式SDN系统中所有资源对象。在存量网中，现有存量网络系统规模庞大，基于现有网络系统的网管系统数量，以及基于网管系统的应用的数量同样庞大，如何使存量网络系统平滑演进到面向未来的SDN系统，尽可能复用现有的网管系统及网管系统中的大量应用对SDN系统中的资源对象进行管理，是目前存在的技术难题。
发明内容
有鉴于此，本申请提供了一种SDN系统中管理资源对象的方法和装置，使得对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。
本申请实施例提供的技术方案如下。
第一方面，本申请实施例提供了一种SDN系统中管理资源对象的方法，所述SDN系统包括管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象，所述方法包括：
所述管理系统获取新发现的资源对象的UUID标识；
所述管理系统为所述新发现的资源对象生成对应的完整识别名FDN标识；
建立所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系。
一种可能的实施方式中，可以通过所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存所述资源对象的UUID标识与所述资源对象的FDN标识的映射关系。
结合第一方面，在第二种可能的实施方式中，所述管理系统接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
所述管理系统根据所述待管理的资源对象的基本信息获取所述待管理的资源对象的FDN标识；
所述管理系统向所述应用系统返回所述待管理的资源对象的FDN标识。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识映射关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，从而可以对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过应用系统对SDN系统中的资源对象进行管理，实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第一方面、第一或第二种可能的实施方式，在第三种可能的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，
所述获取新发现的资源对象的UUID标识具体包括：所述管理系统新发现物理资源对象；所述管理系统为所述新发现的物理资源对象分配UUID标识；
所述管理系统为所述新发现的资源对象生成对应的FDN标识具体包括：所 述管理系统为所述新发现的物理资源对象生成对应的FDN标识；
所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表具体包括：所述管理系统将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第一方面、第一或第二种可能的实施方式，在第四种可能的实施方式中，当所述新发现的资源对象为物理资源对象时，
所述获取新发现的资源对象的UUID标识具体包括：所述管理系统从所述控制系统获取所述新发现的物理资源对象的UUID标识；
所述管理系统为所述新发现的资源对象生成对应的FDN标识具体包括：所述管理系统为所述新发现的物理资源对象生成对应的FDN标识；
所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表具体包括：所述管理系统将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第一方面、第一至第五种可能的实施方式中的任一种实施方式，在第六种可能的实施方式中，当所述新发现的资源对象为业务资源对象时，所述获取新发现的资源对象的UUID标识具体包括：所述管理系统从所述控制系统获取所述业务资源对象的UUID标识；所述管理系统为所述新发现的资源对象生成对应的FDN标识具体包括：所述管理系统根据所述业务资源对象的UUID标识向所述控制系统查询对应的业务，并根据查询结果为所述业务资源对象生成FDN标识；
所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表具体包括：所述管理系统将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第一至第六种可能的实施方式中的任一种实施方式，在第七种可能的实施方式中，所述方法还可以包括：
所述管理系统根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识并向所述应用系统返回所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述FDN标识管理SDN系统中资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源的管理。
结合第七种可能的实施方式，在第八种可能的实施方式中，所述管理系统根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID并向所述应用系统返回所述待管理的资源对象的UUID之前进一步包括：
所述管理系统接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识。
结合第七种或第八种可能的实施方式，在第九种可能的实施方式中，当所要查询的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，所述方法还包括：
所述管理系统接收所述应用系统发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID 标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述管理系统根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系；
所述管理系统向所述应用系统返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
结合第一种至第九种可能的实施方式中的任一种实施方式，在第十种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理系统获取和返回给所述应用系统的所述待管理的资源对象的FDN为所述待管理的物理资源对象的FDN标识，所述方法还包括：
所述管理系统接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
所述管理系统通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息；
所述管理系统向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第一至第十种可能的实施方式中的任一种实施方式，在第十一种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理系统获取和返回给所述应用系统的所述待管理的资源对象的FDN为所述待管理的物理资源对象的FDN标识，所述方法还包括：
所述管理系统接收所述应用系统发送的物理资源对象信息修改请求，所述 物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息；
所述管理系统根据所述物理资源对象信息修改请求修改所述待管理的物理资源对象的详细信息。
结合第一至第第十一种可能的实施方式中的任一种实施方式，在第十二种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理系统获取和返回给所述应用系统的所述待管理的资源对象的FDN为所述待管理的物理资源对象的FDN标识，所述方法还包括：
所述管理系统接收所述应用系统发送的物理资源对象信息删除请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息；
所述管理系统根据所述物理资源对象信息删除请求删除所述待管理的物理资源对象的详细信息。
结合第七种至第十二种可能的实施方式中的任一种实施方式，在第十三种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理系统返回给所述应用系统的所述待管理的资源对象的UUID标识为所述待管理的物理资源对象的UUID标识，所述方法还包括：
所述管理系统接收所述应用系统发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述管理系统通过所述待管理的物理资源对象的UUID标识查询所述待管理的物理资源对象的详细信息；
所述管理系统向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第七种至第十三种可能的实施方式中的任一种实施方式，在第十四种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理 系统返回给所述应用系统的所述待管理的资源对象的UUID标识为所述待管理的物理资源对象的UUID标识，所述方法还包括：
所述管理系统接收所述应用系统发送的物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的详细信息；
所述管理系统通过所述待管理的物理资源对象的UUID标识查询所述待管理的物理资源对象的详细信息；
所述管理系统根据所述物理资源对象信息修改请求修改所述待管理的物理资源对象的详细信息。
结合第七种至第十四种可能的实施方式中的任一种实施方式，在第十五种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述管理系统返回给所述应用系统的所述待管理的资源对象的UUID标识为所述待管理的物理资源对象的UUID标识，所述方法还包括：
所述管理系统接收所述应用系统发送的物理资源对象信息删除请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息；
所述管理系统根据所述物理资源对象信息删除请求删除所述待管理的物理资源对象的详细信息。
第二方面，本申请实施例提供了一种SDN系统中管理资源对象的方法，所述SDN系统包括：管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象，所述管理系统保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表，所述方法包括：
所述应用系统向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
所述应用系统接收所述管理系统返回的所述待管理的资源对象的FDN标识，所述资源对象标识映射关系表保存所述待管理的资源对象的FDN标识；
所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，使得对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第二方面，在第一种可能的实施方式中，所述方法还可以包括：
所述应用系统接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表保存包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述待管理的资源对象的FDN标识管理SDN系统中资源对象的详细信息，例如，查询、修改和删除(参见下面的实施方式)等等，从而加强对SDN系统中资源的管理。
结合第一种可能的实施方式，在第二种可能的实施方式中，所述应用系统接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识之前，该方法 进一步包括：
所述应用系统向所述管理系统发送第二查询请求，所述第二查询请求中携带所述待管理的资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
结合第二方面、第一或第二种可能的实施方式，在第三种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述应用系统向所述管理系统发送的所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；
所述应用系统接收所述管理系统返回的所述待管理的业务资源对象的FDN标识。
结合第二种或第三种可能的实施方式，在第四种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识；
所述应用系统接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述待管理的业务资源对象的UUID标识被所述应用系统用于管理所述待管理的业务资源对象的详细信息，具体的可以包括查询所述待管理的业务资源对象的详细信息、修改所述待管理的业务资源对象的详细信息或删除所述待管理的资源对象的详细信息。
结合第一种至第四种中任何一种可能的实施方式，在第五种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述控制系统发送资源对象第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息；所述应用系统接收所述控制系统返回的所述待管理的业务资源对象的详细信息。
结合第五种可能的实施方式，在第六种可能的实施方式中，当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，所述方法还包括：
所述应用系统向所述管理系统发送第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述应用系统接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
结合第一种至第六种中任何一种可能的实施方式，在第七种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述控制系统发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以修改所述待管理的业务资源对象的详细信息。
结合第一种至第七种中任何一种可能的实施方式，在第八种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述控制系统发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以删除所述待管理的业务资源对象的详细信息。
结合第二方面、第一种至第八种中任何一种可能的实施方式，在第九种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，
所述应用系统向所述管理系统发送的所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；
所述应用系统接收所述管理系统返回的所述待管理的物理资源对象的FDN标识。
结合第二方面，第一种至第九种中任何一种可能的实施方式，在第十种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述管理系统发送第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
所述应用系统接收所述管理系统返回的所述待管理的物理资源对象的详细信息。
结合第二方面，第一种至第十种中任何一种可能的实施方式，在第十一种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息。
结合第二方面，第一种至第十一种中任何一种可能的实施方式，在第十二种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息。
结合第一种至第十二种中任一种可能的实施方式，在第十三种可能的实施方式中，所述方法还包括：
所述应用系统向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识；
所述应用系统接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
结合第一种至第十三种中任一种可能的实施方式，第十四种可能的实施方式中，所述方法还包括：
所述应用系统向所述管理系统发送第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述应用系统接收所述管理系统返回的通过所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息。
结合第一种至第十四种中任一种可能的实施方式，第十五种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的详细信息。
结合第一种至第十五种中任一种可能的实施方式，第十六种可能的实施方式中，所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
所述应用系统向所述管理系统发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息。
第三方面，本申请实施例提供了一种SDN系统中管理资源对象的管理系统，所述SDN系统包括：所述管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；所述管理系统包括：接收单元，处理单元和发送单元；其中，
所述处理单元，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识，并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系。
结合第三方面，在第一种可能的实施方式中，
所述接收单元，用于接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
所述处理单元，还用于根据所述待管理的资源对象的基本信息获取所述待管理资源对象的FDN标识；
所述发送单元，用于向所述应用系统返回所述待管理资源对象的FDN标识。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，从而可以对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第三方面，在第二种可能的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，
所述处理单元，用于为所述新发现的物理资源对象分配UUID标识，为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第三方面，在第三种可能的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，
所述接收单元，用于从所述控制系统获取所述新发现的物理资源对象的UUID标识；
所述处理单元，用于为所述新发现的物理资源对象生成对应的FDN标识，并将并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第三方面、第一种至第三种中任一种可能的实施方式，在第四种可能的实施方式中，当所述新发现的资源对象为业务资源对象时，所述处理单元，用于从所述控制系统获取所述业务资源对象的UUID标识，根据所述业务资源对象的UUID标识向所述控制系统查询对应的业务，并根据查询结果为所述业务资源对象生成FDN标识，并将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第一种至第四种中任何一种可能的实施方式，在第五种可能的实施方式中，所述处理单元，还用于根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系；所述发送单元，用于向所述应用系统返回所述待管理的资源对象的UUID标识。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象 的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述FDN标识管理SDN系统中资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源的管理。
结合第一种至五种中任何一种可能的实施方式，在第六种可能的实施方式中，所述接收单元，还用于接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识；
所述处理单元，进一步根据所述第二查询请求中携带的所述待管理的资源对象的FDN标识获取所述待管理的资源对象的UUID标识。
结合第五种或第六种可能的实施方式，在第七种可能的实施方式中，当所要查询的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述接收单元，还用于接收所述应用系统发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述处理单元，还用于根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系；
所述发送单元，还用于向所述应用系统返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
结合第三方面、第一种至第七种中任何一种可能的实施方式，在第八种可能的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理单元，用于获取所述待管理的物理资源对象FDN标识；
所述发送单元，用于向所述应用系统返回所述待管理的物理资源对象FDN标识。
结合第一种至第八种中任何一种可能的实施方式中，在第九种可能的实施方式中，所述接收单元，还用于接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
所述处理单元，还用于通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息；
所述发送单元，还用于向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第一种至第九种中任何一种可能的实施方式，在第十种可能的实施方式中，
所述处理单元，还用于根据所述待管理的物理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的物理资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的物理资源对象的UUID标识和所述待管理的物理资源对象的FDN标识之间的映射关系，所述待管理的物理资源对象的UUID标识被所述应用系统用于管理所述待管理的物理资源对象的详细信息。
结合第五种至第十种任何一种可能的实施方式，在第十一种可能的实施方式中，所述接收单元，还用于接收所述应用系统发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述处理单元，还用于通过所述待管理的物理资源对象的UUID标识获取 所述待管理的物理资源对象的详细信息；
所述发送单元，还用于向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第一种至第十一种中任何一种可能的实施方式，在第十二种可能的实施方式中，所述接收单元，还用于接收所述应用系统101发送的物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于修改所述待管理的物理资源对象的详细信息；
所述处理单元，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID修改所述待管理的物理资源对象的详细信息。
结合第一种至第十二种中任何一种可能的实施方式，在第十三种可能的实施方式中，所述接收单元，用于接收所述应用系统发送的物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于删除所述待管理的物理资源对象的详细信息；
所述处理单元，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID删除所述待管理的物理资源对象的详细信息。
第四方面，本申请实施例提供了一种软件定义网络SDN系统中管理资源对象的应用系统，所述SDN系统包括：管理系统、所述应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；其特征在于，所述管理系统保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表，所述应用系统包括：发送单元、处理单元，接收单元，其中，
所述发送单元，用于向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
所述接收单元，用于接收所述管理系统返回的所述待管理的资源对象的FDN标识，所述资源对象标识映射关系表保存所述待管理的资源对象的FDN标识；
所述处理单元，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第四方面，在第一种可能的实施方式中，
所述接收单元，还用于接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表保存包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述待管理的资源对象的FDN标识管理SDN系统中资源对象的详细信息，例如，查询、修改和删除(参见下面的实施方式)等等，从而加强对SDN系统中资源的管理。
结合第一种可能的实施方式，在第二种可能的实施方式中，
所述发送单元，还用于向所述管理系统发送第二查询请求，所述第二查询 请求中携带所述待管理的资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
结合第四方面、第一或第二种可能的实施方式，在第三种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；
所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
结合第一种至第三种中任一种可能的实施方式，在第四种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述发送单元，还用于向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识；
所述接收单元，还用于接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。所述待管理的业务资源对象的UUID标识被所述应用系统用于管理所述待管理的业务资源对象的详细信息，具体的可以包括查询所述待管理的业务资源对象的详细信息、修改所述待管理的业务资源对象的详细信息或删除所述待管理的资源对象的详细信息。
结合一种至第四种中任何一种可能的实施方式，在第五种可能的实施方式中，所述发送单元，还用于向所述控制系统发送第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息；
所述接收单元，还用于接收所述控制系统返回的所述待管理的业务资源对象的详细信息。
结合第一种至第五种中任何一种可能的实施方式，在第六种可能的实施方式中，，当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与 所述待管理的业务资源对象相关联的物理资源对象时，
所述处理单元，还用于生成第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述发送单元，还用于向所述管理系统发送所述第三查询请求；
所述接收单元，还用于接收所述管理系统返回的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识和所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识保存在所述管理系统的资源对象标识映射关系表中。
结合第四种至第六种中任何一种可能的实施方式，在第七种可能的实施方式中，
所述发送单元，还用于向所述控制系统发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以修改所述待管理的业务资源对象的详细信息。
结合第四种至第七种中任何一种可能的实施方式，在第八种可能的实施方式中，所述发送单元，还用于向所述控制系统发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以删除所述待管理的业务资源对象的详细信息。
结合第四方面、第一种至第八种中任何一种可能的实施方式，在第九种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，
所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；
所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
结合第九种可能的实施方式，在第十种可能的实施方式中，所述发送单元，还用于向所述管理系统发送第四查询请求，所述第四查询请求携带所述待管 理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
所述接收单元，还用于接收所述管理系统返回的所述待管理的物理资源对象的详细信息。
结合第九种或第十种中一种可能的实施方式，在第十一种可能的实施方式中，所述发送单元，还用于向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息。
结合第九种至第十一种中任何一种可能的实施方式，在第十二种可能的实施方式中，所述发送单元，用于向所述管理系统发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息。
结合第九种至第十二种中任何一种可能的实施方式，在第十三种可能的实施方式中，所述发送单元，用于向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识；
所述接收单元，用于接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
结合第九种至第十三种中任何一种可能的实施方式，第十四种可能的实施方式中，
所述发送单元，还用于向所述管理系统发送第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述接收单元，接收所述管理单元返回的通过所述待管理的物理资源对象的UUID标识获取的所述待管理的物理资源对象的详细信息；
结合第九种至第十四种中任何一种可能的实施方式，第十五种可能的实施 方式中，
所述发送单元，还用于向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的详细信息。
结合第九种至第十五种中任何一种可能的实施方式，第十六种可能的实施方式中，
所述发送单元，还用于向所述管理系统系统发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息。
第五方面，本申请实施例提供了一种软件定义网络SDN系统中管理资源对象的管理系统，所述SDN系统包括：所述管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；所述管理系统包括处理器和网络接口，存储器；
所述处理器，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识；并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系；
所述存储器，用于存储所述资源对象标识映射关系表。
结合第五方面，在第一种可能的实施方式中，
所述网络接口，用于接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
所述处理器，还用于根据所述待管理的资源对象的基本信息获取所述待管理资源对象的FDN标识；
所述网络接口，用于向所述应用系统返回所述待管理资源对象的FDN标识。 在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，从而可以对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第五方面或第一种可能的实施方式，在第二种可能的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，所述处理器，用于从所述控制系统获取所述新发现的物理资源对象的UUID标识，为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第五方面、第一或第二种可能的实施方式，在第三种可能的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，所述处理器，用于为所述新发现的物理资源对象分配UUID标识、为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
结合第五方面、第一至第三种中任何一种可能的实施方式，在第四种可能的实施方式中，当所述新发现的资源对象为业务资源对象时，所述处理器，用于从所述控制系统获取所述业务资源对象的UUID标识，根据所述业务资源对象的UUID标识向所述控制系统查询对应的业务，并根据查询结果为所述业务资源对象生成FDN标识，并用于将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。所述 业务资源对象的UUID可以由所述应用系统通过北向接口下发至所述控制系统。
结合第一种至第四种任何一种可能的实施方式，在第五种可能的实施方式中，所述处理器，还用于根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系，所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息；所述网络接口，用于向所述应用系统返回所述待管理的资源对象的UUID标识。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述FDN标识管理SDN系统中资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源的管理。
结合第一种至第五种任何一种可能的实施方式，在第六种可能的实施方式中，所述网络接口，还用于接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识；
所述处理器，还用于根据所述第二查询请求中携带的所述所述待管理的资源对象的FDN标识获取所述所述待管理的资源对象的UUID标识。
结合第五种或第六种可能的实施方式，在第七种可能的实施方式中，当所要查询的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述网络接口，还用于接收应用系统发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述处理器，还用于根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系；
所述网络接口，还用于向所述应用系统返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
结合第一种至第七种中任何一种可能的实施方式，在第八种可能的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理器，用于获取所述待管理的物理资源对象FDN标识；
所述网络接口，用于向所述应用系统返回所述待管理的物理资源对象FDN标识。
结合第八种可能的实施方式，在第九种可能的实施方式中，所述网络接口，还用于接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于索引所述待管理的物理资源对象的详细信息；
所述处理器，还用于通过所述待管理的物理资源对象的FDN标识索引所述待管理的物理资源对象的详细信息；
所述网络接口，还用于向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第八种或第九种中一种可能的实施方式，在第十种可能的实施方式中，
所述处理器，还用于根据所述待管理的物理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的物理资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的物理资源对象的UUID标识和所述待管理的物理资源对象的FDN标识之间的映射关系，所述待管理的物理资源对象的UUID标识被所述应用系统用于管理所述待管理的物理资源对象的详细信息。
结合第八种至第十种中任何一种可能的实施方式，在第十一种可能的实施方式中，
所述网络接口，用于向所述应用系统返回所述待管理的物理资源对象的UUID标识；并接收所述应用系统发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述处理器，还用于通过所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息；
所述网络接口，还用于向所述应用系统返回所述待管理的物理资源对象的详细信息。
结合第八种至第十一种中任何一种可能的实施方式，在第十二种可能的实施方式中，所述网络接口，还用于接收所述应用系统发送的物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于修改所述待管理的物理资源对象的详细信息；
所述处理器，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID修改所述待管理的物理资源对象的详细信息。
结合第八种至第十二种中任何一种可能的实施方式，在第十三种可能的实施方式中，所述网络接口，用于接收所述应用系统发送的物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象 的FDN标识和/或待管理的物理资源对象的UUID，用于删除所述待管理的物理资源对象的详细信息；
所述处理器，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID删除所述待管理的物理资源对象的详细信息。
结合第五方面，在第十四中可能的实施方式中，存储器用于存储程序指令代码，处理器用于执行存储器中的指令代码，完成图2-图8所对应的实施例的方法。
第六方面，本申请实施例提供了一种软件定义网络SDN系统中管理资源对象的应用系统，所述SDN系统包括：管理系统、应用系统和控制系统。控制系统使用通用唯一标识符UUID标识来标识资源对象。管理系统保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表。所述应用系统可以包括：处理器、网络接口。处理器、网络接口通过总线704通信。处理器通过网络接口与管理系统、控制系统通信；
所述网络接口，用于向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，用于获取待管理的资源对象的FDN标识；
所述网络接口，还用于接收所述管理系统返回的所述待管理的资源对象的FDN标识，所述资源对象标识映射关系表保存所述待管理的资源对象的FDN标识；
所述处理器，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行 管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
结合第六方面，在第一种可能的实施方式中，
所述网络接口，还用于接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表保存包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。通过该实施方式，用户可以通过应用系统进一步通过所述待管理的资源对象的FDN标识管理SDN系统中资源对象的详细信息，例如，查询、修改和删除(参见下面的实施方式)等等，从而加强对SDN系统中资源的管理。
结合第一种可能的实施方式，在第二种可能的实施方式中，
所述网络接口，还用于向所述管理系统发送第二查询请求，所述第二查询请求中携带所述待管理的资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
结合第六方面，在第三种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
结合第二种或第三种可能的实施方式，在第四种可能的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述网络接口，还用于向所述控制系统发送所述第二查询请求，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识，用于获得所述待管理的业务资源对象的UUID标识；
所述网络接口，还用于接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述待管理的业务资源对象的UUID标识被所述应用系统用于管理所述待管理的业务资源对象，具体的可以包括查询所述待管理的业务资源对象的详细信息、修改所述待管理的业务资源对象的详细信息或删除所述待管理的资源对象的详细信息。
结合第二种或第三种可能的实施方式，在第四种可能的实施方式中，
所述网络接口，还用于向所述控制系统发送所述第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息；
所述网络接口，还用于接收所述控制系统返回的所述待管理的业务资源对象的详细信息。
结合第四种或第五种可能的实施方式，在第六种可能的实施方式中，当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述网络接口，还用于向所述管理系统发送第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
所述网络接口，还用于接收所述管理系统返回的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识和所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识保存在所述管理系统的资源对象标识映射关系表中。
结合第四种至第六种中任何一种可能的实施方式，在第七种可能的实施方式中，
所述网络接口，还用于向所述控制系统发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
结合第四种至第七种中任何一种可能的实施方式，在第八种可能的实施方式中，
所述网络接口，还用于向所述控制系统发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
结合第一种至第八种任何一种可能的实施方式，在第九种可能的实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
结合第九种可能的实施方式，在第十种可能的实施方式中，
所述网络接口，还用于向所述管理系统发送第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
所述网络接口，还用于接收所述管理系统返回的所述待管理的物理资源对象的详细信息。
结合第九种或第十种中一种可能的实施方式，在第十一种可能的实施方式中，
所述网络接口，还用于向所述管理系统发送所述物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息；
结合第九种至第十一种中任何一种可能的实施方式，在第十二种可能的实施方式中，
所述网络接口，还用于向所述管理系统发送物理资源对象信息删除请求， 所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息。
结合第九种至第十二种中任何一种可能的实施方式，在第十三种可能的实施方式中，
所述网络接口，用于向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识；
所述网络接口，用于接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
结合第十三种可能的实施方式，第十四种可能的实施方式中，
所述网络接口，还用于向所述管理系统发送第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
所述网络接口，还用于接收所述管理单元返回的通过所述待管理的物理资源对象的UUID标识获取的所述待管理的物理资源对象的详细信息；
结合第十三种或第十四可能的实施方式，第十五种可能的实施方式中，所述网络接口，还用于向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的详细信息。
结合第十三种至第十五种中任何一种可能的实施方式，第十六种可能的实施方式中，
所述网络接口，还用于向所述管理系统系统发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息。
结合第六方面，在第十七种可能的实施方式中，所述应用系统包括存储器，处理器和网络接口，所述存储器用于存储程序指令代码，所述处理器用于执 行所述存储器中的指令代码，完成图2-图8所对应的实施例的方法。
第七方面，提供了一种SDN通信系统，包括第三方面或第五方面所述的管理系统，包括第四方面或第六方面所述的应用系统。所述通信系统，用于执行第一方面和第二方面所述的方法。
第八方面，提供了一种计算机可读存储介质，用于存储为执行上述第一方面至第四方面功能所用的计算机软件指令，其包含用于执行上述第一方面和第二方面的方法所设计的程序。
附图说明
图1为本申请实施例所涉及的一种SDN系统的结构示意图；
图2为本申请实施例所涉及的一种管理资源对象的方法流程图；
图3为本申请实施例所涉及的一种建立资源对象标识映射关系表的流程图
图4为本申请实施例所涉及的一种管理业务资源对象的方法流程图；
图5为本申请实施例所涉及的一种查询业务资源对象详细信息的方法示意图；
图6为本申请实施例所涉及的一种修改业务资源对象详细信息的方法示意图；
图7为本申请实施例所涉及的一种删除业务资源对象详细信息的方法示意图；
图8本申请实施例所涉及的一种管理物理资源对象的方法流程图；
图9A为本申请实施例所涉及的一种管理系统的硬件结构示意图；
图9B为本申请实施例所涉及的一种应用系统的硬件结构示意图；
图10A为本申请实施例所涉及的一种管理系统的示意图；
图10B为本申请实施例所涉及的一种应用的结构示意图。
具体实施方式
本申请实施例描述的应用场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。需要说明的是，在本申请中，“SDN网管系统”、“SDN管理系统”、“网管系统”或“管理系统”和“管 理面”或“SDN管理面”交替使用；“应用系统”或“SDN应用系统”和“应用面”或“SDN应用面”交替使用；“SDN控制系统”或“控制系统”和“控制面”或“SDN控制面”交替使用；“SDN数据转发系统”、“SDN转发系统”、“数据转发系统”或“转发系统”和“数据面”、“SDN数据面”、“转发面”或“SDN转发面”交替使用。
本申请实施例中提到的第一查询的“第一”只是用来做名字标识，并不代表顺序上的第一。该规则同样适用于“第二”、“第三”、“第四”、“第四”、“第五”、“第六”。
如图1所示，为本申请实施例提供的一种SDN系统100，该SDN系统100主要包括应用系统101、控制系统102、数据转发系统103和管理系统104。应用系统、控制系统、数据转发系统和管理系统，在本领域中也被称之为应用面、控制面、数据面和管理面。
应用系统101通过SDN北向接口(英文全称：Northbound Interface，简称NBI)105与控制系统102连接。SDN北向接口也称之为应用-控制面接口(英文全称：Application-Controller Plane Interface，A-CPI)，应用系统101包括多个应用，通过A-CPI向控制系统102发送网络需求。
控制系统102中包括多个控制器，每个控制器负责控制数据转发系统103中一个或多个网元的资源信息，并将接收到的应用系统101发送的网络需求下发数据转发系统103，控制数据转发系统103中的网元设备，例如交换机、路由器等设备，并将相关资源信息上发给应用系统101，为应用系统101提供网络服务。控制系统102可以通过控制策略将有限的网络资源进行优化配置以满足应用需求。
数据转发系统103通过SDN南向接口(英文全称：Southbound Interface，SBI)106与控制系统102连接。SDN南向接口106也称之为数据-控制面接口(英文全称：Data-Controller Plane Interface,D-CPI)。数据转发系统103中包括多个网元(英文全称：Network Element，NE)，所述多个网元包括交换机、路由 器、防火墙、分组传送网设备等。每个网元包括多个物理资源对象，包括子框、槽位、板卡、子槽、端口等等。
管理系统104通过逻辑管理功能接口与应用系统101、控制系统102以及数据转发系统103分别连接。在本申请实施例中，所述管理系统104中的管理功能可以通过存量网中的商业或运营支持系统(BSS/OSS)、网络网管系统(英文全称：Network Management System，NMS)或者网元网管系统(英文全称：Element Management System，EMS)来实现。现有的不同运营商运作的BSS/OSS、NMS或EMS的具体结构以及功能模块可能随不同的运营需求不同而有所不同。管理系统104除了执行常规的管理功能以外，对于SDN系统，还执行某些特定的管理功能。例如，对于应用系统101，管理系统104负责配置网络服务提供商和客户之间达成的服务等级协议(英文全称：Service Level Agreements，SLAs)，典型的SLAs包括以下项目：分配给客户的最小带宽、客户带宽极限、能同时服务的客户数目、在可能影响用户行为的网络变化之前的通知安排、拨入访问可用性、服务供应商支持的最下网络利用性能、各类客户的流量控制权等。对于控制系统102，管理系统104需要配置指定的应用系统101的控制范围的相关策略。对于数据转发系统103，管理系统104负责对网元进行初始化设置。
用户通过应用系统101的某些应用来对SDN系统中相关业务所使用的资源对象进行管理时(比如对SDN系统中一些业务的的资源对象进行查询，修改或删除等管理)，需要给用户呈现可视化的资源信息管理界面。相关业务所使用的资源对象包括物理资源对象和业务资源对象。由于SDN系统的控制面采用UUID对资源对象进行标识，UUID标识使用一串数字标识符来标识资源对象的信息，应用系统101中的应用无法基于UUID标识为用户直接呈现可视化的资源对象的详细信息。
针对上述情况，本申请实施例提供了一种SDN系统中管理资源对象的方法，通过该方法，可以复用现有的网管系统及网管系统中的应用(例如管理非SDN 的网管系统)来管理SDN，以使存量网络系统平滑演进到面向未来的SDN系统，从而可以利用现有网管系统及网管系统中的大量应用对SDN系统中的资源对象进行管理。并可以使得用户能够使用存量网中某些只能识别FDN标识的应用对SDN系统中的资源对象进行管理，给用户呈现用户能够理解的详细的资源信息，进而对资源对象进行管理。需要说明的是，这里所用的存量网络中的管理系统并不局限于现有的管理系统，可以是现有管理系统的发展出来的后续改进性管理系统。
下面结合图2-4对本申请实施例所提供的SDN系统中管理资源对象的方法进行详细说明。该方法应用于图1所示的SDN系统100，SDN系统100包括应用系统101、控制系统102、管理系统104，控制系统102使用UUID标识来标识资源对象。如图2所示,所述方法包括：
201、管理系统获取新发现的资源对象的UUID标识。
在一个具体实施方式中，所述UUID标识是指通用唯一识别码，是一个软件构建的标准，开放网络基金会(英文全称：Open Networking Foundation，ONF)组织在设计SDN系统时所采用的用于标识资源对象的唯一标识。UUID标识能够唯一标识SDN系统中所有的资源对象，不会重复。UUID标识是由服务器生成的一串数字，类似标签，它能保证在同一时空中对网络资源的唯一标识。它能保证在SDN分布式场景下的所有元素都有唯一的标识信息。需要说明的是，这里用UUID通用唯一识别码并不仅仅限于ONF所规范的UUID，其他标识形式，例如采用不具有直接可识别内容的元素来唯一标识资源对象的标识，也可以称为UUID。另外需要说明的是，上述“新发现的资源对象”术语中的“新”这一表述主要是为了语言表达习惯以及描述一个具体流程方便性的考虑，其可以指任何时候“发现的资源对象”，并没有对“发现”这一动作有任何时间或者其他方面的限制。
202、管理系统为所述新发现的资源对象生成对应的完整识别名FDN标识。
管理系统使用完整识别名(英文：full distinguished name，FDN)标识来 标识资源对象。FDN标识中包含了用于索引资源对象详细信息的索引信息，用户通过应用系统101中的应用可以直接查看到该FDN标识中携带的资源对象的索引信息。如果用户想要查看资源对象的详细信息，可以通过该FDN标识，索引到相对应的资源对象的详细信息。从而确保用户在对资源对象进行管理时，能够在应用系统101的应用界面上，为用户呈现可以被理解的资源对象的信息。
在一个具体的实施方式中，FDN标识是一个长度小于等于255的ASCII字符串，其格式为：“TYPE＝VALUE,TYPE＝VALUE,……”。资源对象标识只允许单字节字符，并区分大小写，TYPE和VALUE可以使用的字符集包括：所有可见ASCII字符以及空格；TYPE采用字符串缩写表示，不允许使用纯数字。级间分隔符使用半角逗号(,)，VALUE中多段信息的分隔符使用半角竖杠(|)。TYPE和VALUE的组合能够在上层资源对象下唯一确定本级的资源对象。
对于物理资源对象，以一个子卡的FDN标识示例：
“NE＝3145951,FR＝1,S＝3,CP＝2,SS＝4,SC＝2”。
上述NE表示网元ID，NE＝网元ID；FR表示该网元下的机框，FR＝机框编号；S表示该机框下的槽位编号，S＝槽位编号；CP表示该槽位中的某块单板，CP＝单板ID；SS表示子槽位，SS＝子槽位编号；SC表示子卡，SC＝子卡ID。通过该FDN标识可以得知，该子卡2属于网元3145951下的机框1下的槽位3中的单板2下的子槽位4。由上述示例可以得知，通过FDN标识就可以使得用户界面中体现可视化的资源信息。
对于业务资源对象，以一个安全VPN业务隧道的FDN标识作为示例：
“SECS＝5|100,SECSTUNNEL＝3145768|Ethernet1/0/1|1|3145859|Ethernet1/0/2/0/1|1”。
其中，SECS表示安全VPN业务，SECS＝业务类型|业务ID，其中5表示基于安全套接层的虚拟专用网络SSL VPN业务；SECSTUNNEL表示安全VPN业务隧道，SECSTUNNEL＝本端设备ID|本端接口名称|本端隧道ID|远端设备ID| 远端接口名称|远端隧道ID。
203、管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系。
在一个具体实施方式中，所述资源对象标识映射关系表通过以下方式建立：所述管理系统获取资源对象的UUID标识；所述管理系统为所述资源对象生成对应的FDN标识；所述管理系统将所述资源对象的UUID标识与所述资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。需要说明的是，所述资源对象映射关系表的具体形式可以以多种不同的方式实现，可以以表格的形式，也可以是其他的方式表达该对应关系，本申请对此不做限定，本领域技术人员可以想到的任何用来建立这种对应关系的手段都涵盖在本申请实施例中的资源对象标识映射关系表中。而且，该资源对象标识映射关系表可以是一个没有填入具体内容的映射关系结构，也可以是已经含有具体内容的映射关系表。所述资源对象标识映射关系表中的具体内容可以仅包括所述资源对象的UUID标识与所述资源对象的FDN标识的映射关系；或者在此基础上进一步包括所述资源对象的基本信息；或者在此基础上进一步包括所述资源对象的基本信息与所述资源对象的FDN标识之间的映射关系。本申请对此不做限制，只要包括了所述资源对象的UUID标识与所述资源对象的FDN标识的映射关系的都可以称为本申请中的资源对象标识映射关系表。其中，所述资源对象的基本信息例如可以是所述资源对象的编号，名称，或者其他标识。
在一个具体实施方式中，所述资源对象包括物理资源对象或业务资源对象，管理系统获取物理资源对象的UUID标识与获取业务资源对象的UUID标识的方式有所不同。
下面结合图3，对本申请实施例中的管理系统获取资源对象的UUID标识、生成资源对象的FDN标识以及建立资源对象标识映射关系的过程分别进行说 明。
以下步骤301-308为本申请实施例提供的获取物理资源对象的UUID标识、生成物理资源对象的FDN标识以及建立包含有物理资源对象UUID标识和物理资源对象FDN标识之间的映射关系的物理资源对象标识映射关系表的方法：
301、管理系统104发现新的物理资源对象。
一个具体的实施方式中，管理系统通过自动发现或者用户配置，发现所述新的物理资源对象。
302、管理系统104为所述新发现的物理资源对象分配UUID标识。
一个具体的实施方式中，可以由管理系统104为所述新发现的物理资源对象生成UUID标识，具体的生成过程可以是自动随机生成以及其他现有方式，并将该UUID标识与该物理资源对象关联。
303、管理系统104生成与所述UUID标识对应的FDN标识。
一个具体的实施方式中，可以由管理系统104为所述新发现的物理资源对象生成FDN标识，具体的生成过程可以是自动随机生成以及其他现有方式，并将该FDN标识与该物理资源对象关联。
管理系统104的目标是为SDN控制系统提供抽象、归一的物理资源对象标识，因此，通常可以由管理系统104来作为查找物理资源对象的执行主体，确保SDN控制系统的功能内聚。
一种具体的实施方式中，也可以由控制系统102来完成物理资源对象的查找功能，以下步骤304-305为本申请提供的由控制系统102实施物理资源对象的发现查找功能，具体如下：
304、控制系统102发现新的物理资源对象。
305、控制系统102为所述新发现的物理资源对象分配UUID标识。
一个具体的实施方式中，可以由控制系统102为所述新发现的物理资源生成UUID标识，具体的生成过程可以是自动随机生成以及其他现有方式，并将该UUID标识与该物理资源对象关联。
306、控制系统102将所述新发现的物理资源对象的UUID标识发送管理系统104。
307、管理系统104获得所述新发现的物理资源对象的UUID标识。
308、管理系统生成与所述新发现的物理资源对象的UUID标识对应的FDN标识。
具体方式同上述步骤303，此处不再赘述。
管理系统104建立有一个资源对象标识映射关系表，所述资源对象映射关系表中保存所述物理资源对象的UUID标识和所述物理资源对象的FDN标识的映射关系。所述资源对象标识映射关系表中包含每个新发现的物理资源对象所对应的所述UUID标识和所述FDN标识的映射关系。以下步骤309-315为本申请实施例提供的生成业务资源对象UUID标识和业务资源对象FDN标识以及建立包含有业务资源对象UUID标识和业务资源对象FDN标识之间的映射关系的业务资源对象标识映射关系表的方法：
309、应用系统101为业务资源对象分配UUID标识。
一个具体的实施方式中，应用系统101向控制系统102下发新的业务请求时配置相应的业务资源对象，应用系统101在配置所述业务资源对象时，为所述业务资源对象分配相应的UUID标识。
310、应用系统101将所述业务请求以及对应的所述业务资源对象的UUID标识通过北向接口下发控制系统102。
311、控制系统102接收所述业务资源对象的UUID标识，以及所述业务请求。
312、控制系统102将所述业务资源对象的UUID标识通告给管理系统104。
313、管理系统104获得所述业务资源对象的UUID标识。
314、管理系统104通过所述业务资源对象的UUID标识向控制系统102查询与所述业务资源对象的UUID标识对应的业务。
在一个具体的实施方式中，由于控制系统102保存有业务资源对象的详细 信息，管理系统可以通过业务资源的UUID标识向控制系统102查询业务资源UUID标识对应的业务，获取业务的详细信息，例如业务类别，业务内容，业务属性，业务名称等等。
315、管理系统104根据查询结果为所述业务资源对象生成相应的FDN标识。
在一个具体的实施方式中，管理系统104根据所述查询结果，例如根据获取的业务资源的信息，例如业务类别、名称和/或业务属性等信息为该业务资源对象等成相应的FDN标识。
所述管理系统104将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。需要说明的是，在上述步骤303或315之后所描述的生成的资源对象标识映射关系表仅以资源对象标识映射关系表包括资源对象的UUID标识和所述资源对象的FDN标识的映射关系为例，进行举例说明。根据上述步骤203中关于资源对象标识映射关系表的说明，本领域技术人员可以理解，所述管理系统还可以将资源对象的基本信息和/或资源对象的详细信息加入到所述资源对象的UUID标识和所述资源对象的FDN标识的映射关系中，从而生成所述资源对象的基本信息和/或资源对象的详细信息、所述资源对象的UUID标识以及所述资源对象的FDN标识三者之间的映射关系。
204’、应用系统向管理系统发送第一查询请求，所述第一查询请求携带待管理的资源对象的基本信息，用于获取所述待管理的资源对象的FDN标识。
204、管理系统接收所述应用系统发送的第一查询请求，所述第一查询请求用于获取待管理的资源对象的FDN标识。
具体实施方式中，所述第一查询请求可以按照现有的应用系统与管理系统之间交互的消息协议(例如RESTCONF协议)生成相应的查询请求消息，所述查询请求消息中携带待管理的资源对象的基本信息，例如待管理的资源对象的编号或名称等信息，例如查询单板的FDN标识时，所述查询请求消息中携带网元编号，槽位编号和单板编号。
205、管理系统向所述应用系统返回所述待管理资源对象的FDN标识。
一个具体的实施方式中，管理系统104在接收到所述应用系统101发送的第一查询请求后，会根据第一查询请求中携带的待管理的资源对象的基本信息，例如上述提到的所述待管理的资源对象的编号或名称等，查找到与所述待管理的资源对象相对应的FDN标识。
在另外的具体的实施方式中，所述资源对象映射关系表中包括有所述待管理的资源对象的基本信息与所述待管理的资源对象的FDN标识之间的映射关系，所述管理系统104在接收到所述应用系统101发送的第一查询请求后，会根据第一查询请求中携带的待管理的资源对象的基本信息，例如上述提到的所述待管理的资源对象的编号或名称等，以及所述资源对象标识映射关系表查找到与所述待管理的资源对象相对应的FDN标识。另外，当所述资源对象的FDN标识中已经包含有所述资源对象的基本信息时，所述管理系统可以通过直接查询其保存的所述资源对象的FDN标识，并确定所述资源对象的FDN标识包括有所述待管理的资源对象的基本信息时，即可确定所述资源对象的FDN标识为所述待管理的资源对象的FDN标识。
205’、应用系统接收所述管理系统返回的所述待管理的资源对象的FDN标识。
一个具体的实施方式中，应用系统接收到管理系统104返回的所述待管理的资源对象的FDN标识，则用户可以通过应用系统101的应用界面查看到该FDN标识所携带的待管理的资源对象的索引信息。例如待管理的资源对象是子卡时，用户通过应用界面能查看到的该子卡的FDN标识所对应的索引信息包括：该子卡所对应的网元的编号，机框的编号，槽位的编号，单板的编号以及子卡的编号。在另一个具体的实施方式中，该管理系统104也可以先根据所述第一查询请求中的待管理的资源对象的基本信息获取该待管理的资源对象的UUID标识，并相应根据资源对象映射关系表获取该待管理的资源对象的FDN标识。
在另一个具体的实施方式中，所述应用系统101可以根据待管理的资源对象的UUID标识去管理所述待管理的资源对象，对所述资源对象进行进一步的管理。所述方法具体包括：
根据所述待管理的资源对象的FDN标识，管理系统104可以在所述资源对象标识映射关系表中，查找到与所述待管理的资源对象的FDN标识相对应的UUID标识，并将所述待管理的资源对象的FDN标识以及所述待管理的资源对象的UUID标识返回给所述应用系统101。所述应用系统101可以根据待管理的资源对象的UUID标识去管理所述待管理的资源对象，对所述资源对象进行进一步的管理。
在另一具体实施方式中，管理系统104向应用系统101返回所述待管理资源对象的FDN标识以及所述待管理资源对象的UUID标识，还可以包括：
206’、应用系统根据获得的管理系统返回的所述待管理的资源对象的FDN标识，向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识。
206、管理系统接收所述第二查询请求，根据所述待管理的资源对象的FDN标识查询所述资源对象标识映射关系表，获取所述待管理的资源对象的UUID标识。
207、管理系统向应用系统返回所述待管理资源对象的UUID标识。
一个具体的实施方式中，管理系统104根据所述待管理的业务资源对象的FDN标识查询资源对象标识映射关系表，获取所述待管理的业务资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的业务资源对象的UUID标识和所述待管理的业务资源对象的FDN标识之间的映射关系。
207’、应用系统接收所述管理系统返回的所述待管理资源对象的UUID标识。
需要说明的是，在另外的实施方式中，管理系统104在接收到应用系统101 发送的所述第一查询请求后，可以将所述待管理的资源对象的FDN标识和所述待管理的资源对象的UUID一起返回给应用系统101。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过上述实施方式，应用系统101获得所述待管理资源对象的FDN标识后，用户即可通过应用系统101的应用查看到该FDN标识所标识的所述待管理的资源对象的索引信息。进一步的，应用系统可以根据待管理的资源对象的FDN标识和/或UUID标识去管理所述待管理的资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源对象的管理。
在本申请实施例中，所述待管理的资源对象包括待管理的物理资源对象或待管理的业务资源对象。下面结合图4对本申请实施例提供的SDN系统中管理业务资源对象的方法进行说明，该方法应用图1所示的SDN系统100。
401、应用系统向管理系统发送第一查询请求，所述第一查询请求消息中携带待管理的业务资源对象的基本信息，用于获取待管理的业务资源对象的FDN标识。
一个具的体实施方式中，应用系统生成第一查询请求，所述第一查询请求用于获取待管理的业务资源对象的完整识别名FDN标识。所述第一查询请求可以是按照现有的应用系统与管理系统之间交互的消息协议(例如RESTCONF协议)而生成相应的查询请求消息，所述第一查询请求消息中携带待管理的业务资源对象的基本信息，例如待管理的业务资源对象的业务类型、源/宿节点信息等。
SDN系统100中，关于物理资源对象和业务资源对象的FDN标识，全部保存在管理系统104中。因此，用户通过应用面管理业务资源对象时，首先在应用面选取相应的待管理的业务资源对象，应用系统101根据用户选取的待管理的业务资源对象生成待管理的业务资源对象的第一查询请求，用于获取所述 待管理的业务资源对象的FDN标识。应用系统101向管理系统104发送所述第一查询请求。
501、管理系统接收所述应用系统发送的所述第一查询请求。
502、管理系统向应用系统返回所述待管理的业务资源对象的FDN标识。
一个具体的实施方式中，管理面系统104在接收到应用系统101发送的所述第一查询请求后，根据所述第一查询请求中待管理的资源对象的基本信息，例如上述提到的所述待管理的业务资源对象的业务类型、节点信息等，查找到与待管理的业务资源对象相对应的FDN标识，并把该FDN标识返回给所述应用系统101。
另一个具体的实施方式中，所述资源对象映射关系表中存储有所述待管理的业务资源对象的基本信息与所述待管理的业务资源对象的FDN标识之间的映射关系，所述管理系统104在接收到所述应用系统101发送的第一查询请求后，会根据第一查询请求中携带的待管理的业务资源对象的基本信息，例如上述提到的所述待管理的业务资源对象的业务类型、节点信息等，以及所述资源对象标识映射关系表查找到与所述待管理的业务资源对象相对应的FDN标识。
402、应用系统接收所述管理系统返回的所述待管理的业务资源对象的FDN标识。
一个具体的实施方式中，应用系统101接收到所述管理系统104返回的所述待管理的业务资源对象相对应的FDN标识，则用户就可以通过应用系统101的应用界面查看到与该FDN标识所对应的待管理的业务资源对象的索引信息，以安全VNP业务为例，例如用户通过应用界面能查看到的该业务的FDN标识所对应的索引信息包括：业务类型、接口名称等等。
在另外的具体实施方式中，该管理系统104也可以先根据所述第一查询请求中的待管理的业务资源对象的基本信息获取该待管理的业务资源对象的UUID标识，并相应根据资源对象映射关系表获取该待管理的业务资源对象的 FDN标识。
另一个具体的实施方式中，所述应用系统101可以根据待管理的业务资源对象的UUID标识去管理所述待管理的业务资源对象的详细信息，加强对所述业务资源对象的管理。所述方法具体包括：
根据所述待管理的业务资源对象的FDN标识，管理系统104可以在所述资源对象标识映射关系表中，查找到与所述待管理的业务资源对象的FDN标识相对应的UUID标识，并将所述待管理的业务资源对象的FDN标识以及所述待管理的业务资源对象的UUID标识返回给所述应用系统101。所述资源对象标识映射关系表包括所述待管理的业务资源对象的UUID标识和所述待管理的业务资源对象的FDN标识之间的映射关系。所述应用系统101可以根据待管理的资源对象的UUID标识去管理所述待管理的资源对象的详细信息，对所述资源对象进行进一步的管理。
在另一具体实施方式中，管理系统104向应用系统101返回所述待管理资源对象的FDN标识以及所述待管理资源对象的UUID标识，还可以包括步骤403-405，步骤503-505：
403、应用系统根据获得的所述待管理的业务资源对象的FDN标识，向所述管理系统发送第二查询请求，第二查询请求用于获取所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
一个具体的实施方式中，SDN系统100中，业务资源对象的FDN标识保存在管理系统104中，而业务资源对象的详细信息则保存在控制系统102中，控制系统102通过业务资源对象的UUID标识索引业务资源对象的详细信息。用户要对待管理业务资源对象进行管理时，通过所述待管理的业务资源对象的FDN标识可以查看到与所述待管理的业务资源对象相对应的索引信息。用户需要通过待管理的业务资源对象的FDN标识进一步获取对应的UUID标识，从而根据所获取的UUID标识到控制系统102获取业务资源对象的详细信息。
503、管理系统接收应用系统发送的所述第二查询请求。
504、管理系统向应用系统返回所述待管理的业务资源对象的UUID标识。
在一个具体的实施方式中，管理系统104根据所述待管理的业务资源对象的FDN标识查询资源对象标识映射关系表，获取所述待管理的业务资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的业务资源对象的UUID标识和所述待管理的业务资源对象的FDN标识之间的映射关系。
404、应用系统接收管理系统返回的根据资源对象标识映射关系表获取的所述待管理的业务资源对象的UUID标识。
需要说明的是，在另外的实施方式中，管理系统104在接收到应用系统101发送的所述第一查询请求后，可以将所述待管理的业务资源对象的FDN标识和所述待管理的业务资源对象的UUID一起返回给应用系统101。
405、应用系统通过所述待管理的业务资源对象的UUID标识到控制系统管理所述待管理的业务资源对象的详细信息。
在一个具体的实施方式中，控制系统102中保存有所述待管理的业务资源对象的详细信息。应用系统101通过所述待管理的业务资源对象的UUID标识，即可在控制系统102中查询、修改或者删除所述待管理的业务资源对象的详细信息。应用系统可以获取所述待管理的业务资源对象的详细信息，该些详细信息是用户能够理解的可视化的信息。应用面将上述信息呈现给用户，使得用户可以在对业务资源对象的详细信息进行查看管理时，在管理界面呈现用户可以理解的可视化信息。
下面结合图5-7说明本申请实施例中用户对业务资源对象的详细信息进行查询，修改或删除等管理行为分别进行说明。
如图5所示，以用户查询业务资源对象的详细信息为例进行说明，所述业务资源对象例如是以太专线业务资源对象。当用户查询业务资源对象的详细信息时，用户通过应用系统101的应用界面选取相应的业务资源对象，要求查询该业务资源对象的详细信息，例如业务类别，业务内容，业务属性，业务 名称等等。应用系统101向管理系统104发送所述第一查询请求，用于获取所述业务资源对象的FDN标识。应用系统101接收所述管理系统返回的所述待管理的业务资源对象的FDN标识。应用系统101向管理104发送第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。应用系统101接收管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。应用系统101向控制系统102发送第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息。应用系统101接收控制系统102返回的所述待管理的业务资源对象的详细信息。
在一个具体的实施方式中，所述应用系统101接收所述控制系统102返回的所述待管理的资源对象的详细信息后，用户可以通过应用系统101的应用界面对所述待管理的资源对象的详细信息进行查看，修改或删除等相关管理。
在另一个具体的方式中，若查询到的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的以太专线业务资源对象相关联的物理资源对象的详细信息时，即查询到的业务资源对象的详细信息中引用物理资源UUID标识，则应用系统101向管理系统104发送第三查询请求，所述第三查询请求中携带有所述与所述待管理的以太专线业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。应用系统101接收管理系统104返回的根据所述资源对象标识映射关系表查找到的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
应用系统101通过应用界面向用户呈现所述业务资源对象的详细信息。如图6所示，当用户要求修改业务资源对象的详细信息时，所述业务资源对象例如是以太专线业务资源对象。用户通过应用系统101的应用界面选取相应的业务资源对象，要求修改业务资源对象的详细信息，例如业务类别，业务内容， 业务属性，业务名称等等。应用系统101向管理系统104发送第一查询请求，用于获取所述业务资源对象的FDN标识。应用系统101接收所述管理系统返回的所述待管理的业务资源对象的FDN标识。应用系统101向管理104发送第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。应用系统101接收管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。应用系统101向控制系统102发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以修改所述待管理的业务资源对象的详细信息。控制系统102修改所述业务资源对象的详细信息后，为数据转发系统配置修改后的业务资源并更新数据库保存修改后的业务资源对象的详细信息。
如图7所示，当用户要求删除业务资源对象的详细信息时，所述业务资源对象例如可以是以太专线业务资源对象。用户通过应用系统101的应用界面选取相应的业务资源对象，要求删除业务资源对象的详细信息，例如业务类别，业务内容，业务属性，业务名称等等。应用系统101向管理系统104发送所述第一查询请求，用于获取所述业务资源对象的FDN标识。应用系统101接收所述管理系统返回的所述待管理的业务资源对象的FDN标识。应用系统101向管理104发送所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。应用系统101接收管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。应用系统101向控制系统102发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以删除所述待管理的业务资源对象的详细信息控制系统102将所述业务资源对象的详细信息删除后，删除为数据转发系统配置的所述业务资源并更新数据库。
下面结合图8，对本申请实施例提供的SDN系统中管理物理资源对象的方 法进行说明，该方法应用图1所示的SDN系统100。
801、应用系统向管理系统发送第一查询请求，所述第一查询请求中携带待管理的物理资源对象的基本信息，用于获取待管理的物理资源对象的完整识别名FDN标识。
一个具体的体实施方式中，应用系统101生成第一查询请求，所述第一查询请求可以是按照现有的应用系统与管理系统之间交互的消息协议(例如RESTCONF协议)而生成相应的查询请求消息，所述第一查询请求消息中携带待管理的资源对象的基本信息，例如待管理的物理资源对象的编号或名称等信息，例如查询单板的FDN标识时，所述查询请求消息中携带该单板所在的网元编号，槽位编号和单板编号等基本信息。
SDN系统100中，关于物理资源对象和业务资源对象的FDN标识，全部保存在管理系统104中。因此，用户通过应用面管理物理资源对象时，首先在应用面选取相应的待管理的物理资源对象，应用系统101根据用户选取的待管理的物理资源对象生成待管理的物理资源对象的第一查询请求，用于获取所述待管理的物理资源对象的FDN标识。应用系统101向管理系统104发送所述第一查询请求。
901、管理系统接收所述应用系统发送的所述第一查询请求。
902、管理系统向应用系统返回所述待管理的物理资源对象的FDN标识。
在一个具体的实施方式中，管理面系统104在接收到应用系统101发送的所述第一查询请求后，根据所述第一查询请求中待管理的物理资源对象的基本信息查找到与待管理的物理资源对象相对应的FDN标识，并把该FDN标识返回给所述应用系统101。
803、应用系统接收所述管理系统返回的所述待管理的物理资源对象的FDN标识。
一个具体的实施方式中，应用系统101接收到所述管理系统104返回的所述待管理的物理资源对象相对应的FDN标识，则用户就可以通过应用系统101 的应用界面查看到与该FDN标识所对应的待管理的业务资源对象的索引信息。以子卡为例，用户通过应用界面能查看到的子卡的FDN标识所对应的索引信息包括：该子卡所对应的网元的编号，机框的编号，槽位的编号，单板的编号以及子卡的编号。
在另外的具体的实施方式中，所述资源对象映射关系表中存储有所述待管理的物理资源对象的基本信息与所述待管理的物理资源对象的FDN标识之间的映射关系，所述管理系统104在接收到所述应用系统101发送的所述第一查询请求后，会根据所述第一查询请求中携带的待管理的物理资源对象的基本信息，例如上述提到的所述待管理的物理资源对象的编号或名称等，以及所述资源对象标识映射关系表查找到与所述待管理的资源对象相对应的FDN标识。
进一步的，当用户想要查询所述待管理的物理资源对象的详细信息时，所述方法还包括：
804、应用系统生成第四查询请求，所述第四查询请求中携带所述待管理的物理资源对象的FDN标识，用于在管理系统中查询所述待管理的物理资源对象的详细信息。
903、管理系统接收所述第四查询请求，通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息。
904、管理系统向应用系统返回所述待管理的物理资源对象的详细信息。
805、应用系统接收所述待管理的物理资源对象的详细信息。
在另一具体实施方式中，也可以通过待管理的物理资源对象的UUID标识查询所述待管理的物理资源对象的详细信息，所述方法具体包括：
根据所述待管理的物理资源对象的FDN标识，管理系统104可以在所述资源对象标识映射关系表中，查找到与所述待管理的物理资源对象的FDN标识相对应的UUID标识，并将所述待管理的物理资源对象的FDN标识以及所述待管理的物理资源对象的UUID标识返回给应用系统101。所述资源对象标识映 射关系表包括所述待管理的物理资源对象的UUID标识和所述待管理的物理资源对象的FDN标识之间的映射关系。应用系统101向管理系统发送第五查询请求，所述第五查询请求中携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息。所述管理系统接收所述第五查询请求，根据所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息，并将待管理的物理资源对象的详细信息返回给应用系统。使得所述应用系统可以查询所述待管理的资源对象的详细信息，对所述资源对象进行进一步的管理。
在另一具体实施方式中，管理系统104将所述待管理的物理资源对象的FDN标识以及所述待管理的物理资源对象的UUID标识返回给所述应用系统101，还可以包括：
响应于接收到所述第一查询请求，管理系统104向应用系统101返回所述待管理的物理资源对象的FDN标识；
应用系统101接收管理系统104返回的所述待管理的物理资源对象的FDN标识，并生成第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识；
管理系统104接收所述第二查询请求，根据所述待管理的物理资源对象的FDN标识查询所述资源对象标识映射关系表，获取所述待管理的物理资源对象的UUID标识；
管理系统104向应用系统101返回所述待管理的物理资源对象的UUID标识。
应用系统101获得所述待管理的物理资源对象的FDN标识后，用户即可通过应用系统101的应用查看到该FDN标识所标识的所述待管理的物理资源对象的索引信息。
在一个具体的实施方式中，应用系统101可以根据待管理的物理资源对象的FDN标识和/或UUID标识去修改或删除所述待管理的物理资源对象的详细 信息，对所述待管理的物理资源对象做进一步的管理。
在一个具体的实施方式中，应用该系统101根据待管理的资源对象的FDN标识和/或UUID标识去修改所述待管理的物理资源对象的详细信息，对所述待管理的物理资源对象做进一步的管理，具体包括：
所述应用系统向所述管理系统发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN和/或所述待管理的物理资源对象UUID标识，用于修改所述待管理的物理资源对象的详细信息。
另外一个具体的实施方式中，应用该系统101根据待管理的资源对象的FDN标识和/或UUID标识去删除所述待管理的物理资源对象的详细信息，对所述待管理的物理资源对象做进一步的管理，具体包括：
所述应用系统向所述管理系统发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN和/或所述待管理的物理资源对象UUID标识，用于删除所述待管理的物理资源对象的详细信息。
本申请实施例提供的SDN系统中的资源对象的管理方法，通过管理系统中建立资源对象的FDN标识与UUID标识的映射关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对现有的网管系统和基于网管系统的应用进行少量改造，即可以通过应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向未来SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。进一步的，用户可以通过所述FDN标识查询、修改或删除所述资源对象的详细信息，以实现对资源对象的进一步管理。
图9A为本申请实施例提供的如图1所示的SDN系统中管理资源对象的管 理系统的硬件结构示意图，所述管理系统是如图9A所示的管理系统104，该管理系统104用于执行图2-图8实施例中的方法。
一种软件定义网络SDN系统中管理资源对象的管理系统，所述SDN系统100包括：所述管理系统104、应用系统101和控制系统102；所述控制系统102使用通用唯一标识符UUID标识来标识资源对象；所述管理系统104包括处理器601和网络接口602，存储器603。处理器601通过网络接口602与应用系统101、控制系统102通信。处理器601、存储器603和网络接口602可以通过总线604通信。
所述处理器601，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识；并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系。
所述存储器603，用于存储所述资源对象标识映射关系表。
所述网络接口602，用于接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识。
所述处理器601，还用于根据所述待管理的资源对象的基本信息获取所述待管理资源对象的FDN标识。
所述网络接口602，用于向所述应用系统101返回所述待管理资源对象的FDN标识。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，从而可以对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源 对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
一个具体的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，所述处理器601，用于从所述控制系统102获取所述新发现的物理资源对象的UUID标识，为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
另一个具体的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，所述处理器601，用于为所述新发现的物理资源对象分配UUID标识，为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
一种具体的实施方式中，当所述新发现的资源对象为业务资源对象时，所述处理器601，用于从所述控制系统102获取所述业务资源对象的UUID标识，根据所述业务资源对象的UUID标识向所述控制系统102查询对应的业务，并根据查询结果为所述业务资源对象生成FDN标识，并用于将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。所述业务资源对象的UUID可以由所述应用系统101通过北向接口下发至所述控制系统102。
一种具体的实施方式中，所述处理器601，还用于根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系，所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息；
所述网络接口602，用于向所述应用系统返回所述待管理的资源对象的UUID标识。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述FDN标识管理SDN系统中资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源的管理。
一个具体的实施方式中，所述网络接口602，还用于接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识；
所述处理器601，还用于根据所述第二查询请求中携带的所述所述待管理的资源对象的FDN标识获取所述所述待管理的资源对象的UUID标识。
一个具体的实施方式中，当所要查询的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述网络接口602，还用于接收应用系统101发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
所述处理器601，还用于根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对 象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系。
所述网络接口602，还用于向所述应用系统101返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
在一个具体的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理器601，用于获取所述待管理的物理资源对象FDN标识；
所述网络接口602，用于向所述应用系统101返回所述待管理的物理资源对象FDN标识；并接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于索引所述待管理的物理资源对象的详细信息；
所述处理器601，还用于通过所述待管理的物理资源对象的FDN标识索引所述待管理的物理资源对象的详细信息；
所述网络接口602，还用于向所述应用系统101返回所述待管理的物理资源对象的详细信息。
在一个具体的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理器601，具体用于获取所述待管理的物理资源对象FDN标识。
所述网络接口602，具体用于向所述应用系统101返回所述待管理的物理资源对象FDN标识。
所述处理单元，还用于根据所述待管理的物理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的物理资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的物理资源对象的UUID标识和所述待管理的物理资源对象的FDN标识之间的映射关系，所述待管理的物理资源对象的UUID标识被所述应用系统101用于查询所述待管理的物理资源对象的详细信息。
所述网络接口602，用于向所述应用系统101返回所述待管理的物理资源对象的UUID标识；并接收所述应用系统101发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息。
所述处理器601，还用于通过所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息。
所述网络接口602，还用于向所述应用系统101返回所述待管理的物理资源对象的详细信息。
在一个具体的实施方式中，所述网络接口602，还用于接收所述应用系统101发送的物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于修改所述待管理的物理资源对象的详细信息。
所述处理器601，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID修改所述待管理的物理资源对象的详细信息。
在一个具体的实施方式中，所述网络接口602，用于接收所述应用系统101发送的物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于删除所述待管理的物理资源对象的详细信息。
所述处理器601，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID删除所述待管理的物理资源对象的详细信息。
在本申请中，处理器601可以是一个或多个中央处理器(英文：Central Processing Unit，CPU)。在处理器601是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
网络接口602可以是有线接口，例如光纤分布式数据接口(英文：Fiber Distributed Data Interface，FDDI)，千兆以太网(英文：Gigabit Ethernet，GE)接口。
存储器603可以是但不限于随机存储存储器(RAM)、只读存储器(ROM)，可擦除可编程只读存储器(EPROM)、光盘只读存储器(CD-ROM)、硬盘等中的一种或多种。
在本申请提供的另外的实施方式中，存储器603用于存储程序指令代码，处理器601用于执行存储器603中的指令代码，完成图2-图8所对应的实施例的方法。
图9B为本申请实施例提供的如图1所示的SDN系统中管理资源对象的应用系统的硬件结构示意图，所述应用系统是如图9B所示的应用系统101。该应用系统101用于执行图2-图8实施例的方法。
一种软件定义网络SDN系统100中管理资源对象的应用系统101，所述SDN系统包括：管理系统104、应用系统101和控制系统102。控制系统102使用通用唯一标识符UUID标识来标识资源对象。管理系统104保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表。所述应用系统101可以包括：处理器701、网络接口702。处理器701、网络接口702通过总线704通信。处理器701通过网络接口702与管理系统104、控制系统102通信。
所述处理器701，用于生成第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取待管理的资源对象的FDN标识。
所述网络接口702，用于向所述管理系统104发送所述第一查询请求。
所述网络接口702，还用于接收所述管理系统104返回的所述待管理的资源对象的FDN标识，所述资源对象标识映射关系表保存所述待管理的资源对象的FDN标识。
所述处理器701，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对存量网 络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
一种具体的实施方式中，所述网络接口702，还用于接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表保存包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述待管理的资源对象的FDN标识管理SDN系统中资源对象的详细信息，例如，查询、修改和删除(参见下面的实施方式)等等，从而加强对SDN系统中资源的管理。
一种具体的实施方式中，所述网络接口，还用于向所述管理系统发送第二查询请求，所述第二查询请求中携带所述待管理的资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
所述处理器701，还用于生成所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述网络接口702，还用于向所述控制系统102发送所述第二查询请求。
所述网络接口702，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。一种具体的实施方式中，所述处理器701，还用于生成第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息。
所述网络接口702，还用于向所述控制系统102发送所述第六查询请求。
所述网络接口，还用于接收所述控制系统102返回的所述待管理的业务资源对象的详细信息。
一种具体的实施方式中，当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述处理器701，还用于生成第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
所述网络接口702，还用于向所述管理系统104发送所述第三查询请求，并接收所述管理系统104返回的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识和所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识保存在所述管理系统的资源对象标识映射关系表中。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
所述网络接口702，还用于向所述控制系统102发送所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述网络接口702，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述网络接口702，还用于向所述控制系统102发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
所述网络接口702，还用于向所述控制系统102发送所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述网络接口702，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述网络接口702，还用于向所述控制系统102发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述网络接口702，还用于向所述管理系统104发送第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息。
所述网络接口702，还用于接收所述管理系统104返回的所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述处理器701，还用于生成物理资源对象信息修改请求，所述物理资源 对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息。
所述网络接口702，还用于向所述管理系统104发送所述物理资源对象信息修改请求。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述处理器701，还用于生成物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息。
所述网络接口702，还用于向所述管理系统发送物理资源对象信息删除请求。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，所述网络接口702，用于向所述管理系统104发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识。
所述网络接口702，用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
一种具体的实施方式中，所述网络接口702，还用于向所述管理系统104发送第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息。
所述网络接口702，还用于接收所述管理单元104返回的通过所述待管理的物理资源对象的UUID标识获取的所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，所述网络接口702，还用于向所述管理系统104发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的 详细信息。
一种具体的实施方式中，所述网络接口702，还用于向所述管理系统104发送物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息。
在另一种具体的实施方式中，如图9B所示，应用系统101可以包括处理器701、网络接口702、存储器703。处理器701、网络接口702和存储器703通过总线704通信。处理器701通过网络接口702与管理系统104、控制系统102通信。
存储器703用于存储程序指令代码，处理器701用于执行存储器603中的指令代码，完成图2-图8所对应的实施例的方法。
存储器703可以是但不限于随机存储存储器(RAM)、只读存储器(ROM)，可擦除可编程只读存储器(EPROM)、光盘只读存储器(CD-ROM)、硬盘等中的一种或多种。存储器603和存储器703用于存储程序代码。
处理器701可以是一个或多个中央处理器(英文：Central Processing Unit，CPU)。在处理器701是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
网络接口702可以是有线接口，例如光纤分布式数据接口(英文：Fiber Distributed Data Interface，FDDI)，千兆以太网(英文：Gigabit Ethernet，GE)接口。
通过本申请提供的SDN系统中的管理资源对象的管理系统和应用系统，在所述管理系统中建立资源对象的FDN标识与UUID标识的映射关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对现有的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向未来SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化 的资源对象信息，以供用户查询所述资源对象的基本索引信息。进一步的，用户可以通过所述FDN标识查询、修改或删除所述资源对象的详细信息，以实现对资源对象的进一步管理。
图10A示出了本申请实施例提供的如图1所示的SDN系统中管理资源对象的管理系统的示意图，该管理系统为具有执行图2-图8所示实施例中的方法功能的硬件设备。
具体实施方式中，该SDN系统中管理资源对象的管理系统(所述SDN系统包括：所述管理系统、应用系统和控制系统；所述控制系统102使用通用唯一标识符UUID标识来标识资源对象)包括：接收单元1001，处理单元1002和发送单元1003；其中，
所述处理单元1002，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识，并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系。
所述接收单元1001，用于接收所述应用系统101发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识。
所述处理单元1002，还用于根据所述待管理的资源对象的基本信息获取所述待管理资源对象的FDN标识。
所述发送单元1003，用于向所述应用系统101返回所述待管理资源对象的FDN标识。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，从而可以对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系 统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
一种具体的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，
所述处理单元1002，用于为所述新发现的物理资源对象分配UUID标识，为所述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
一种具体的实施方式中，当所述新发现的资源对象为新发现的物理资源对象时，
所述接收单元1001，用于从所述控制系统102获取所述新发现的物理资源对象的UUID标识。
所述处理单元1002，用于为所述新发现的物理资源对象生成对应的FDN标识，并将并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
一种具体的实施方式中，当所述新发现的资源对象为业务资源对象时，所述处理单元1002，用于从所述控制系统102获取所述业务资源对象的UUID标识，根据所述业务资源对象的UUID标识向所述控制系统102查询对应的业务，并根据查询结果为所述业务资源对象生成FDN标识，并将所述业务资源对象的UUID标识与所述业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
一种具体的实施方式中，所述处理单元1002，还用于根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的 UUID标识和所述待管理的资源对象的FDN标识之间的映射关系，所述待管理的资源对象的UUID标识被所述应用系统101用于索引所述待管理的资源对象的详细信息。
所述发送单元1003，用于向所述应用系统101返回所述待管理的资源对象的UUID标识。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述FDN标识管理SDN系统中资源对象的详细信息，例如，查询，修改，删除等等，从而加强对SDN系统中资源的管理。
一种具体的实施方式中，所述接收单元1001，还用于接收所述应用系统101发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识。
所述处理单元1002，进一步根据所述第二查询请求中携带的所述所述待管理的资源对象的FDN标识获取所述所述待管理的资源对象的UUID标识。
一种具体的实施方式中，当所要查询的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述接收单元1001，还用于接收所述应用系统101发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
所述处理单元1002，还用于根据所述与所述待管理的业务资源对象相关联 的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系。
所述发送单元1003，还用于向所述应用系统101返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
一种具体的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理单元1002，用于获取所述待管理的物理资源对象FDN标识。
所述发送单元1003，用于向所述应用系统101返回所述待管理的物理资源对象FDN标识。
所述接收单元1001，还用于接收所述应用系统101发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息。
所述处理单元1002，还用于通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息；
所述发送单元1003，还用于向所述应用系统101返回所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，当所述待管理的资源对象是待管理的物理资源对象时，
所述处理单元1002，用于获取所述待管理的物理资源对象FDN标识。
所述发送单元1003，用于向所述应用系统101返回所述待管理的物理资源对象FDN标识。
所述处理单元1002，还用于根据所述待管理的物理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的物理资源对象的UUID标 识，所述资源对象标识映射关系表包括所述待管理的物理资源对象的UUID标识和所述待管理的物理资源对象的FDN标识之间的映射关系，所述待管理的物理资源对象的UUID标识被所述应用系统101用于查询所述待管理的物理资源对象的详细信息。
所述发送单元1003，用于向所述应用系统101返回所述待管理的物理资源对象的UUID标识。
所述接收单元1001，还用于接收所述应用系统101发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息。
所述处理单元1002，还用于通过所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息。
所述发送单元1003，还用于向所述应用系统101返回所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，所述接收单元1001，还用于接收所述应用系统101发送的物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于修改所述待管理的物理资源对象的详细信息。
所述处理单元1002，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID修改所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，所述接收单元1001，用于接收所述应用系统101发送的物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID，用于删除所述待管理的物理资源对象的详细信息。
所述处理单元1002，还用于通过待管理的物理资源对象的FDN标识和/或待管理的物理资源对象的UUID删除所述待管理的物理资源对象的详细信息。
图10B示出了本申请实施例提供的如图1所示的SDN系统中管理资源对象 的应用系统的示意图。该应用系统为具有执行图2-图8所示实施例中的方法功能的硬件设备。
具体实施方式中，该SDN系统中管理资源对象的应用系统(所述SDN系统包括管理系统、所述应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象，所述管理系统104保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表)包括：发送单元2001、处理单元2002，接收单元2003，其中，
所述处理单元2002，用于生成第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取待管理的资源对象的FDN标识。
所述发送单元2001，用于向所述管理系统104发送所述第一查询请求。
所述接收单元2003，用于接收所述管理系统104返回的所述待管理的资源对象的FDN标识，所述资源对象标识映射关系表保存所述待管理的资源对象的FDN标识。
所述处理单元2002，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
在上述技术方案中，通过在所述管理系统中创建所述资源对象标识关系表，保存资源对象的UUID标识和所述资源对象的FDN标识的映射关系，对存量网络系统中的网管系统和基于网管系统的应用进行少量改造，即可以通过所述应用系统对SDN系统中的资源对象进行管理，从而实现存量网络系统向SDN系统的平滑演进。进一步的，用户通过应用系统的管理界面对资源对象进行管理时，通过获取所述资源对象的FDN标识，就可以通过所述管理界面为用户呈现可视化的资源对象信息，以供用户查询所述资源对象的基本索引信息。
一种具体的实施方式中，所述接收单元，还用于接收所述管理系统返回的根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表保存包 括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系。
所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息，具体的可以包括查询所述待管理的资源对象的详细信息、修改所述待管理的资源对象的详细信息或删除所述待管理的资源对象的详细信息。
通过该实施方式，用户可以通过应用系统进一步通过所述待管理的资源对象的FDN标识管理SDN系统中资源对象的详细信息，例如，查询、修改和删除(参见下面的实施方式)等等，从而加强对SDN系统中资源的管理。
一种具体的实施方式中，所述发送单元，还用于向所述管理系统发送第二查询请求，所述第二查询请求中携带所述待管理的资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
所述处理单元2002，用于生成所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述发送单元2001，还用于向所述控制系统102发送第二查询请求。
所述接收单元2003，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识；
所述处理单元2002，还用于生成第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
所述发送单元2001，还用于向所述控制系统102发送第六查询请求；
所述接收单元2003，还用于接收所述控制系统102返回的所述待管理的业 务资源对象的详细信息。
一种具体的实施方式中，当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
所述处理单元2002，还用于生成第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
所述发送单元2001，还用于向所述管理系统104发送所述第四查询请求。
所述接收单元2003，还用于接收所述管理系统104返回的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识和所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识保存在所述管理系统104的资源对象标识映射关系表中。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识；所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识；
所述处理单元2002，还用于生成所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述发送单元2001，还用于向所述控制系统102发送所述第二查询请求。
所述接收单元2003，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述处理单元2002，还用于生成所述业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
所述发送单元2001，还用于向所述控制系统102发送所述业务资源对象信息修改请求。
一种具体的实施方式中，当所述待管理的资源对象是待管理的业务资源对象时，
所述第一查询请求用于获取所述待管理的业务资源对象的FDN标识。
所述待管理的资源对象的FDN标识是所述待管理的业务资源对象的FDN标识。
所述处理单元2002，还用于生成所述第二查询请求，所述第二查询请求用于获得所述待管理的业务资源对象的UUID标识，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识。
所述发送单元2001，还用于向所述控制系统102发送所述第二查询请求。
所述接收单元2003，还用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的业务资源对象的UUID标识。
所述处理单元2002，还用于生成业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以管理所述待管理的业务资源对象的详细信息。
所述发送单元2001，还用于向所述控制系统102发送所述业务资源对象信息删除请求。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，
所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识。
所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述处理单元2002，还用于生成第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息。
所述发送单元2001，还用于向所述管理系统104发送所述第四查询请求。
所述接收单元2003，还用于接收所述管理系统104返回的所述待管理的物理资源对象的详细信息。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，
所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；
所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述处理单元2002，还用于生成物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的FDN标识，用于修改所述待管理的物理资源对象的详细信息。
所述发送单元2001，还用于向所述管理系统104发送所述物理资源对象信息修改请求。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，
所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；
所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述处理单元2002，还用于生成物理资源对象信息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的FDN标识，用于删除所述待管理的物理资源对象的详细信息。
所述发送单元2001，还用于向所述管理系统104发送所述物理资源对象信息删除请求。
一种具体的实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述发送单元2001，用于向所述管理系统104发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识。
所述接收单元2003，用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
所述发送单元2001，还用于向所述管理系统104发送第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息。
所述接收单元2003，接收所述管理单元返回的通过所述待管理的物理资源对象的UUID标识获取的所述待管理的物理资源对象的详细信息。
一种具体实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识。
所述发送单元2001，用于向所述管理系统104发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识。
所述接收单元2003，用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
所述发送单元2001，还用于向所述管理系统104发送物理资源对象信息修改请求，所述物理资源对象信息修改请求携带所述待管理的物理资源对象的UUID标识，用于修改所述待管理的物理资源对象的详细信息。
一种具体实施方式中，当所述待管理的资源对象是物理资源对象时，所述第一查询请求用于获取所述待管理的物理资源对象的FDN标识；所述待管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识；所述方法还包括：
所述发送单元2001，用于向所述管理系统104发送第二查询请求，所述第二查询请求用于获得所述待管理的物理资源对象的UUID标识，所述第二查询请求中携带有所述待管理的物理资源对象的FDN标识。
所述接收单元2003，用于接收所述管理系统104返回的根据所述资源对象标识映射关系表查找到的所述待管理的物理资源对象的UUID标识。
所述发送单元2001，还用于向所述管理系统104系统发送物理资源对象信 息删除请求，所述物理资源对象信息删除请求携带所述待管理的物理资源对象的UUID标识，用于删除所述待管理的物理资源对象的详细信息。
需要说明的是，图10A所提供的管理系统实施例以及图10B提供的应用系统实施例，应用于图1所示的SDN系统中，实现管理系统和应用系统的功能。一个具体的实施方式中，图10A中的处理单元1002可以用图9A的处理器601实现，接收单元1001和发送单元1003中的一个或多个可以由图9A的网络接口602实现，同理，图10B中的处理单元2002可以用图9B的处理器701实现，接收单元2003和发送单元2001中的一个或多个可以由图9B的网络接口702实现。
需要说明的是，在另外的实施方式中，图10A中的处理单元1002实施的步骤可以由处理器之外的其他硬件，例如专门的逻辑电路、特定集成电路(英文全称：Application Specific Integrated Circuit，ASIC)或现场可编辑逻辑闸阵列(英语全称：Field Programmable Gate Array,FPGA)予以实现；或者通过其他硬件予以实现；也可以由其他硬件或固件结合通用处理器实现。具体实施方式本申请不做限制。同理，图10B中的处理单元2002实施的步骤可以由处理器之外的其他硬件，参见对于图10A中的处理单元1002的说明，此处不再赘述。
本申请上述实施例中提供的管理系统和应用该系统，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配有不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或部分功能。而且，上述多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实 施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
本申请实施例还提供了一种SDN通信系统，包括管理系统和应用系统，所述管理系统可以是图9A、图10A对应的实施例所提供的管理系统。所述应用系统可以是图9B、图10B对应的实施例所提供的应用系统。所述管理系统和所述应用系统用于执行图2-图8对应的实施例的方法。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质中的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中，通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
本说明书的各个部分均采用递进的方式进行描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点介绍的都是与其他实施例不同之处。尤其，对于装置和系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例部分的说明即可。
最后，需要说明的是：以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。显然，本领域技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (34)

  1. 一种软件定义网络SDN系统中管理资源对象的方法，所述SDN系统包括：管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象，其特征在于，所述方法包括：
    所述管理系统获取新发现的资源对象的UUID标识；
    所述管理系统为所述新发现的资源对象生成对应的完整识别名FDN标识；
    所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存所述资源对象的UUID标识与所述资源对象的FDN标识的映射关系；
    所述管理系统接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述管理系统根据所述待管理的资源对象的基本信息获取所述待管理的资源对象的FDN标识；
    所述管理系统向所述应用系统返回所述待管理的资源对象的FDN标识。
  2. 根据权利要求1所述的方法，其特征在于：当所述新发现的资源对象为新发现的物理资源对象时，
    所述获取新发现的资源对象的UUID标识具体包括：所述管理系统新发现物理资源对象，并为所述新发现的物理资源对象分配UUID标识；
    所述管理系统为所述新发现的资源对象生成对应的FDN标识具体包括：所述管理系统为所述新发现的物理资源对象生成对应的FDN标识；
    所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表具体包括：所述管理系统将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
  3. 根据权利要求1或2所述的方法，其特征在于：当所述新发现的资源对象为新发现的业务资源对象时，
    所述获取新发现的资源对象的UUID标识具体包括：所述管理系统从所述控制系统获取所述新发现的业务资源对象的UUID标识；
    所述管理系统为所述新发现的资源对象生成对应的FDN标识具体包括：所述管理系统根据所述新发现的业务资源对象的UUID标识向所述控制系统查询对应的业务，并根据查询结果为所述新发现的业务资源对象生成对应的FDN标识；
    所述管理系统将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表具体包括：所述管理系统将所述新发现的业务资源对象的UUID标识与所述新发现的业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法进一步包括：
    所述管理系统根据所述待管理的资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识并向所述应用系统返回所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系，所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息。
  5. 根据权利要求4所述的方法，其特征在于，所述管理系统根据所述待管理的资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID并向所述应用系统返回所述待管理的资源对象的UUID之前进一步包括：
    所述管理系统接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所 述待管理的资源对象的FDN标识。
  6. 根据权利要求4或5所述的方法，其特征在于，当所要管理的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，所述方法还包括：
    所述管理系统接收所述应用系统发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
    所述管理系统根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系；
    所述管理系统向所述应用系统返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，当所述待管理的资源对象是物理资源对象时，所述管理系统获取和返回给所述应用系统的所述待管理的资源对象的FDN为所述待管理的物理资源对象的FDN标识，所述方法还包括：
    所述管理系统接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
    所述管理系统通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息；
    所述管理系统向所述应用系统返回所述待管理的物理资源对象的详细信息。
  8. 根据权利要求4-6中任一项所述的方法，其特征在于：当所述待管理的资源对象是物理资源对象时，所述管理系统返回给所述应用系统的所述待管理的资源对象的UUID标识为所述待管理的物理资源对象的UUID标识，所述方法还包括：
    所述管理系统接收所述应用系统发送的第五查询请求，所述第五查询请求携带所述待管理的物理资源对象的UUID标识，用于查询所述待管理的物理资源对象的详细信息；
    所述管理系统通过所述待管理的物理资源对象的UUID标识获取所述待管理的物理资源对象的详细信息；
    所述管理系统向所述应用系统返回所述待管理的物理资源对象的详细信息。
  9. 一种软件定义网络SDN系统中管理资源对象的方法，所述SDN系统包括：管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象，其特征在于，所述管理系统保存所述资源对象的FDN标识与所述资源对象的UUID标识映射关系的资源对象标识映射关系表，所述方法包括：
    所述应用系统向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述应用系统接收所述管理系统根据所述待管理的资源对象的基本信息返回的所述待管理的资源对象的FDN标识；
    所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述应用系统接收所述管理系统返回的根据所述待管理的资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识。
  11. 根据权利要求10所述的方法，其特征在于，所述应用系统接收所述所述管理系统返回的根据所述待管理的资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识之前，所述方法进一步包括：
    所述应用系统向所述管理系统发送第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识。
  12. 根据权利要求10或11所述的方法，当所述待管理的资源对象是待管理的业务资源对象时，所述应用系统接收的所述待管理的资源对象的FDN标识为待管理的业务资源对象的FDN标识，所述应用系统接收的所述待管理的资源对象的UUID标识为所述待管理的业务资源对象的UUID标识；
    所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
    所述应用系统向所述控制系统发送第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息；
    所述应用系统接收所述控制系统返回的所述待管理的业务资源对象的详细信息。
  13. 根据权利要求12所述的方法，其特征在于：当所述待查询的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，所述方法还包括：
    所述应用系统向所述管理系统发送第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识， 用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
    所述应用系统接收所述管理系统返回的根据所述资源对象标识映射关系表查找到的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
  14. 根据权利要求10或11所述的方法，其特征在于，当所述待管理的资源对象是待管理的业务资源对象时，所述应用系统接收的所述待管理的资源对象的FDN标识为待管理的业务资源对象的FDN标识，所述应用系统接收的所述待管理的资源对象的UUID标识为所述待管理的业务资源对象的UUID标识；
    所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
    所述应用系统向所述控制系统发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以修改所述待管理的业务资源对象的详细信息。
  15. 根据权利要求10或11所述的方法，其特征在于，
    当所述待管理的资源对象是待管理的业务资源对象时，所述应用系统接收的所述待管理的资源对象的FDN标识为待管理的业务资源对象的FDN标识，所述应用系统接收的所述待管理的资源对象的UUID标识为所述待管理的业务资源对象的UUID标识；
    所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
    所述应用系统向所述控制系统发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以删除所述待管理的业务资源对象的详细信息。
  16. 根据权利要求9-15中任一项所述的方法，其特征在于，当所述待管理的资源对象是物理资源对象时，所述应用系统接收所述管理系统返回的所述待 管理的资源对象的FDN标识为所述待管理的物理资源对象的FDN标识；
    所述应用系统利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象具体包括：
    所述应用系统向所述管理系统发送第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
    所述应用系统接收所述管理系统返回的所述待管理的物理资源对象的详细信息。
  17. 一种软件定义网络SDN系统中管理资源对象的管理系统，所述SDN系统包括：所述管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；其特征在于，所述管理系统包括：接收单元，处理单元和发送单元；其中：
    所述处理单元，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识，并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系；
    所述接收单元，用于接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述处理单元，还用于根据所述待管理的资源对象的基本信息获取所述待管理的资源对象的FDN标识；
    所述发送单元，用于向所述应用系统返回所述待管理资源对象的FDN标识。
  18. 根据权利要求17所述的管理系统，其特征在于：当所述新发现的资源对象为新发现的物理资源对象时，
    所述处理单元，用于为所述新发现的物理资源对象分配UUID标识，为所 述新发现的物理资源对象生成对应的FDN标识，并将所述新发现的物理资源对象的UUID标识与所述新发现的物理资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
  19. 根据权利要求17或18所述的管理系统，其特征在于，当所述新发现的资源对象为新发现的业务资源对象时，所述处理单元，用于从所述控制系统获取所述新发现的业务资源对象的UUID标识，根据所述新发现的业务资源对象的UUID标识向所述控制系统查询对应的业务，并根据查询结果为所述新发现的业务资源对象生成对应的FDN标识，并将所述新发现的业务资源对象的UUID标识与所述新发现的业务资源对象的FDN标识的映射关系加入所述资源对象标识映射关系表。
  20. 根据权利要求17-19任一项所述的管理系统，其特征在于：所述处理单元还用于根据所述待管理资源对象的FDN标识以及所述资源对象标识映射关系表获取所述待管理的资源对象的UUID标识，所述资源对象标识映射关系表包括所述待管理的资源对象的UUID标识和所述待管理的资源对象的FDN标识之间的映射关系，所述待管理的资源对象的UUID标识被所述应用系统用于管理所述待管理的资源对象的详细信息；
    所述发送单元还用于向所述应用系统返回所述待管理的资源对象的UUID标识。
  21. 根据权利要求20所述的管理系统，其特征在于：
    所述接收单元还用于接收所述应用系统发送的第二查询请求，所述第二查询请求用于获得所述待管理的资源对象的UUID标识，所述第二查询请求中携带有所述待管理的资源对象的FDN标识；
    所述处理单元进一步根据所述第二查询请求中携带的所述待管理的资源对象的FDN标识获取所述待管理的资源对象的UUID标识。
  22. 根据权利要求20或21所述的管理系统，其特征在于：当所要管理的待管理的资源对象的详细信息为待管理的业务资源对象的详细信息时，且所述 待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，
    所述接收单元还用于接收所述应用系统发送的第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
    所述处理单元还用于根据所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识查询所述资源对象标识映射关系表，获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识，所述资源对象标识映射关系表包括所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识和所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识之间的映射关系；
    所述发送单元，还用于向所述应用系统返回所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识。
  23. 根据权利要求17-21任一项所述的管理系统，其特征在于：当所述待管理的资源对象是待管理的物理资源对象时，
    所述待管理的资源对象的FDN标识为待管理的物理资源对象的FDN标识；
    所述接收单元还用于接收所述应用系统发送的第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
    所述处理单元还用于通过所述待管理的物理资源对象的FDN标识查询所述待管理的物理资源对象的详细信息；
    所述发送单元，还用于向所述应用系统返回所述待管理的物理资源对象的详细信息。
  24. 一种软件定义网络SDN系统中管理资源对象的应用系统，所述SDN系统包括：管理系统、所述应用系统和控制系统；所述控制系统使用通用唯一 标识符UUID标识来标识资源对象；所述管理系统保存资源对象的FDN标识与资源对象的UUID标识映射关系的资源对象标识映射关系表，其特征在于，所述应用系统包括：发送单元、处理单元，接收单元，其中：
    所述发送单元，用于向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述接收单元，用于接收所述管理系统根据所述待管理的资源对象的基本信息返回的所述待管理的资源对象的FDN标识；
    所述处理单元，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
  25. 根据权利要求24所述的应用系统，其特征在于：
    所述接收单元还用于接收所述管理系统返回的根据所述待管理的资源对象的FDN标识以及所述资源对象标识映射关系表获取的所述待管理的资源对象的UUID标识。
  26. 根据权利要求25所述的应用系统，其特征在于：
    所述发送单元还用于向所述管理系统发送第二查询请求，所述第二查询请求中携带有所述待管理的业务资源对象的FDN标识，用于获得所述待管理的资源对象的UUID标识。
  27. 根据权利要求25或26所述的应用系统，其特征在于：当所述待管理的资源对象是待管理的业务资源对象时，
    所述待管理的资源对象的UUID标识为待管理的业务资源对象的UUID标识；
    所述发送单元还用于向所述控制系统发送第六查询请求，所述第六查询请求中携带有所述待管理的业务资源对象的UUID标识以查询所述待管理的业务资源对象的详细信息；
    所述接收单元还用于接收所述控制系统返回的所述待管理的业务资源对 象的详细信息。
  28. 根据权利要求27所述的应用系统，其特征在于：当所述待管理的业务资源对象的详细信息中包括使用UUID标识的与所述待管理的业务资源对象相关联的物理资源对象时，所述发送单元，还用于向所述管理系统发送所述第三查询请求，所述第三查询请求中携带有所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识，用于获取所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
    所述接收单元，还用于接收所述管理系统返回的所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识；
    所述与所述待管理的业务资源对象相关联的物理资源对象的FDN标识和所述与所述待管理的业务资源对象相关联的物理资源对象的UUID标识保存在所述资源对象标识映射关系表中。
  29. 根据权利要求25或26所述的应用系统，其特征在于：当所述待管理的资源对象是待管理的业务资源对象时，所述待管理的资源对象的UUID标识为所述待管理的业务资源对象的UUID标识；
    所述发送单元，还用于向所述控制系统发送业务资源对象信息修改请求，所述业务资源对象信息修改请求中携带有所述待管理的业务资源对象的UUID标识以修改所述待管理的业务资源对象的详细信息。
  30. 根据权利要求25-29中任一项所述的应用系统，其特征在于：当所述待管理的资源对象是待管理的业务资源对象时，所述待管理的资源对象的UUID标识为待管理的业务资源对象的UUID标识；
    所述发送单元还用于向所述控制系统发送业务资源对象信息删除请求，所述业务资源对象信息删除请求中携带有所述待管理的业务资源对象的UUID标识以删除所述待管理的业务资源对象的详细信息。
  31. 根据权利要求22-30任一项所述的应用系统，其特征在于：当所述待管理的资源对象是物理资源对象时，所述待管理的资源对象的FDN标识为待 管理的物理资源对象的FDN标识；
    所述发送单元还用于向所述管理系统发送第四查询请求，所述第四查询请求携带所述待管理的物理资源对象的FDN标识，用于查询所述待管理的物理资源对象的详细信息；
    所述接收单元，还用于接收所述管理系统返回的所述待管理的物理资源对象的详细信息。
  32. 一种软件定义网络SDN系统中管理资源对象的管理系统，所述SDN系统包括：所述管理系统、应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；其特征在于，所述管理系统包括：处理器、存储器和网络接口；其中：
    所述处理器，用于获取新发现的资源对象的UUID标识，为所述新发现的资源对象生成对应的完整识别名FDN标识；并将所述新发现的资源对象的UUID标识与所述新发现的资源对象的FDN标识的映射关系加入资源对象标识映射关系表，所述资源对象标识映射关系表保存资源对象的UUID标识与所述资源对象的FDN标识的映射关系；
    所述存储器，用于存储所述资源对象标识映射关系表；
    所述网络接口，用于接收所述应用系统发送的待管理的资源对象的第一查询请求，所述第一查询请求中包括所述待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述处理器，还用于根据所述待管理的资源对象的基本信息获取所述待管理的资源对象的FDN标识；
    所述网络接口，还用于向所述应用系统返回所述待管理的资源对象的FDN标识。
  33. 一种软件定义网络SDN系统中管理资源对象的应用系统，所述SDN系统包括：管理系统、所述应用系统和控制系统；所述控制系统使用通用唯一标识符UUID标识来标识资源对象；所述管理系统保存资源对象的FDN标识与 资源对象的UUID标识映射关系的资源对象标识映射关系表，其特征在于，所述应用系统包括：网络接口、处理器，其中，
    所述网络接口，用于向所述管理系统发送第一查询请求，所述第一查询请求中包括待管理的资源对象的基本信息，所述第一查询请求用于获取所述待管理的资源对象的FDN标识；
    所述网络接口，还用于接收所述管理系统返回的所述待管理的资源对象的FDN标识，所述待管理的资源对象的FDN标识保存在所述资源对象标识映射关系表中；
    所述处理器，用于利用所述待管理的资源对象的FDN标识管理所述待管理的资源对象。
  34. 一种软件定义网络SDN通信系统，其特征在于：包括权利要求17-23、32中任一项所述的管理系统以及权利要求24-31、33中任一项所述的应用系统。
PCT/CN2016/070893 2016-01-14 2016-01-14 一种管理资源对象的方法和系统 Ceased WO2017120814A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
PCT/CN2016/070893 WO2017120814A1 (zh) 2016-01-14 2016-01-14 一种管理资源对象的方法和系统
CN201680000607.7A CN107710196B (zh) 2016-01-14 2016-01-14 一种管理资源对象的方法和系统
JP2018536788A JP6567776B2 (ja) 2016-01-14 2016-01-14 リソースオブジェクトを管理するための方法およびリソースオブジェクトを管理するためのシステム
EP16884377.9A EP3392784B1 (en) 2016-01-14 2016-01-14 Method and system for managing resource objects
KR1020187023236A KR102082282B1 (ko) 2016-01-14 2016-01-14 자원 객체를 관리하는 방법 및 시스템
US16/035,462 US20180322118A1 (en) 2016-01-14 2018-07-13 Method and system for managing resource object

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/070893 WO2017120814A1 (zh) 2016-01-14 2016-01-14 一种管理资源对象的方法和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/035,462 Continuation US20180322118A1 (en) 2016-01-14 2018-07-13 Method and system for managing resource object

Publications (1)

Publication Number Publication Date
WO2017120814A1 true WO2017120814A1 (zh) 2017-07-20

Family

ID=59310673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/070893 Ceased WO2017120814A1 (zh) 2016-01-14 2016-01-14 一种管理资源对象的方法和系统

Country Status (6)

Country Link
US (1) US20180322118A1 (zh)
EP (1) EP3392784B1 (zh)
JP (1) JP6567776B2 (zh)
KR (1) KR102082282B1 (zh)
CN (1) CN107710196B (zh)
WO (1) WO2017120814A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019152518A1 (en) 2018-01-31 2019-08-08 University Of Pittsburgh-Of The Commonwealth System Of Higher Education Pneumatic powered mobility control systems
CN115484174A (zh) * 2022-09-13 2022-12-16 建信金融科技有限责任公司 基于智能识别的纳管方法、装置、设备及存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019516781A (ja) 2016-04-07 2019-06-20 ツェーエムブルー プロイェクト アーゲー スルホン化芳香族化合物
US11788228B2 (en) 2017-02-13 2023-10-17 Cmblu Energy Ag Methods for processing lignocellulosic material
US11450854B2 (en) 2017-02-13 2022-09-20 Cmblu Energy Ag Redox flow battery electrolytes
AU2019220364A1 (en) 2018-02-13 2020-07-30 Cmblu Energy Ag Aminated lignin-derived compounds and uses thereof
CA3088242A1 (en) 2018-02-13 2019-08-22 Cmblu Projekt Ag Redox flow battery electrolytes
CN112567689A (zh) * 2018-08-10 2021-03-26 瑞典爱立信有限公司 被管理对象的备选寻址
US10805182B2 (en) * 2018-12-04 2020-10-13 Sap Se Provisioner disaster-recovery framework for platform-as-a-service offering
CN110489786A (zh) * 2019-07-04 2019-11-22 广西汽车集团有限公司 一种处理工艺资源数据模型的方法及装置
CN113285816B (zh) * 2020-02-19 2022-10-28 华为技术有限公司 一种基于键值配置的控制请求发送方法、装置和系统
FR3119060B1 (fr) * 2021-01-20 2023-03-24 Ebos Tech Interface d’application dynamique basée sur une intention ascendante

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101114328A (zh) * 2006-07-24 2008-01-30 三星电子株式会社 创建唯一标识符的设备和方法
CN101488903A (zh) * 2009-02-18 2009-07-22 南京大学 基于统一分类接口的数据中心自动化资源管理系统及方法
CN104363159A (zh) * 2014-07-02 2015-02-18 北京邮电大学 一种基于软件定义网络的开放虚拟网络构建系统和方法
US20150163314A1 (en) * 2013-12-05 2015-06-11 Huawei Technologies Co., Ltd. Control Method, Control Device, and Process in Software Defined Network
WO2015156832A1 (en) * 2014-04-08 2015-10-15 Hewlett Packard Development Company, L.P. Pipeline table identification

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000215134A (ja) * 1999-01-26 2000-08-04 Nec Corp 抽象構文デ―タ保持装置および管理情報ベ―ス
WO2004059484A1 (fr) * 2002-12-31 2004-07-15 Zte Corporation Procede de veille et commande de charge dans un systeme a traitement reparti de donnees
WO2011049553A1 (en) * 2009-10-20 2011-04-28 Hewlett-Packard Development Company, L.P. Universally unique semantic identifiers
US9241265B2 (en) * 2011-05-13 2016-01-19 Nokia Technologies Oy Method and apparatus for handling incoming status messages
CA3047447C (en) * 2011-10-25 2022-09-20 Nicira, Inc. Chassis controllers for converting universal flows
JP6365306B2 (ja) * 2012-11-21 2018-08-01 日本電気株式会社 クラウド環境提供システム、サービス管理装置、経路制御方法及びプログラム
CN104135379B (zh) * 2013-05-03 2017-05-10 新华三技术有限公司 基于OpenFlow协议的端口控制方法及装置
US9699070B2 (en) * 2013-10-04 2017-07-04 Nicira, Inc. Database protocol for exchanging forwarding state with hardware switches
EP3090508A4 (en) * 2013-12-31 2017-08-02 Intel Corporation Capability determination for computing resource allocation

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101114328A (zh) * 2006-07-24 2008-01-30 三星电子株式会社 创建唯一标识符的设备和方法
CN101488903A (zh) * 2009-02-18 2009-07-22 南京大学 基于统一分类接口的数据中心自动化资源管理系统及方法
US20150163314A1 (en) * 2013-12-05 2015-06-11 Huawei Technologies Co., Ltd. Control Method, Control Device, and Process in Software Defined Network
WO2015156832A1 (en) * 2014-04-08 2015-10-15 Hewlett Packard Development Company, L.P. Pipeline table identification
CN104363159A (zh) * 2014-07-02 2015-02-18 北京邮电大学 一种基于软件定义网络的开放虚拟网络构建系统和方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3392784A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019152518A1 (en) 2018-01-31 2019-08-08 University Of Pittsburgh-Of The Commonwealth System Of Higher Education Pneumatic powered mobility control systems
CN115484174A (zh) * 2022-09-13 2022-12-16 建信金融科技有限责任公司 基于智能识别的纳管方法、装置、设备及存储介质
CN115484174B (zh) * 2022-09-13 2023-07-04 建信金融科技有限责任公司 基于智能识别的纳管方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107710196A (zh) 2018-02-16
KR20180103975A (ko) 2018-09-19
US20180322118A1 (en) 2018-11-08
EP3392784A4 (en) 2018-12-05
JP2019503619A (ja) 2019-02-07
EP3392784B1 (en) 2021-12-15
EP3392784A1 (en) 2018-10-24
JP6567776B2 (ja) 2019-08-28
KR102082282B1 (ko) 2020-02-27
CN107710196B (zh) 2020-12-01

Similar Documents

Publication Publication Date Title
CN107710196B (zh) 一种管理资源对象的方法和系统
US5787252A (en) Filtering system and method for high performance network management map
CN106487869A (zh) 用于对标签化数据进行控制和标准化的多云网络代理
CN112217656B (zh) Sd-wan系统中的网络设备的配置信息同步方法和装置
CN109964507B (zh) 网络功能的管理方法、管理单元及系统
CN105827428A (zh) 资产信息的管理方法及装置
CN115118585B (zh) 一种业务的部署方法、装置及系统
WO2020224241A1 (zh) 一种云通信方法及装置、用户设备、网络设备
WO2016131171A1 (zh) 一种针对vnf包进行操作的方法及装置
CN111381820A (zh) 一种基于gui自动生成api的方法及装置
EP4191907A1 (en) Vnf instantiation method and apparatus
CN101268450A (zh) 用于部署供给服务的ems的通用框架
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20250293933A1 (en) Instantiation method and apparatus for virtualised network function vnf
WO2025228110A1 (zh) 一种拓扑更新方法、计算设备及超融合系统
US12425312B2 (en) Method, apparatus, and system for deploying service
WO2025086627A1 (zh) 云资源架构图生成方法、云管理平台及计算设备集群
US20230409371A1 (en) Method for creating network service ns and related apparatus
CN112889247B (zh) Vnf服务实例化方法及装置
CN106559454A (zh) 资源访问方法、装置及系统
JP7450072B2 (ja) 仮想化ネットワーク・サービス配備方法及び装置
CN115348187A (zh) 网络服务处理的方法和装置
US20240256344A1 (en) Management apparatus, management method and management program
CN119739456A (zh) 容器多网卡实现方法、程序产品、电子设备及存储介质
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018536788

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016884377

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016884377

Country of ref document: EP

Effective date: 20180720

Ref document number: 20187023236

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187023236

Country of ref document: KR