CN114363286A - Interface object identifier generation method and device - Google Patents
Interface object identifier generation method and device Download PDFInfo
- Publication number
- CN114363286A CN114363286A CN202011054786.7A CN202011054786A CN114363286A CN 114363286 A CN114363286 A CN 114363286A CN 202011054786 A CN202011054786 A CN 202011054786A CN 114363286 A CN114363286 A CN 114363286A
- Authority
- CN
- China
- Prior art keywords
- target
- interface object
- identifier
- network element
- interface
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 230000004044 response Effects 0.000 claims abstract description 38
- 238000013507 mapping Methods 0.000 claims abstract description 22
- 238000004590 computer program Methods 0.000 claims description 14
- 238000007726 management method Methods 0.000 description 19
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 7
- 230000000694 effects Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for generating an interface object identifier, wherein the method for generating the interface object identifier comprises the following steps: the first network element sends request information to the second network element through the first interface, the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element; if the target first interface object is the first interface object needing to be generated by the second network element into the target identifier, the second network element generates the target identifier of the target first interface object, and the type of the target identifier is different from that of the temporary identifier; the second network element sends response information to the first network element, wherein the response information comprises a mapping relation between a target identifier of the target first interface object and the temporary identifier; and the first network element replaces the temporary identifier of the target first interface object with the target identifier and stores the target identifier in the database. The invention can avoid the problem of interface object identification conflict caused by generating the same type of interface object identification by different network elements.
Description
Technical Field
The embodiment of the invention relates to the technical field of transmission, in particular to a method and a device for generating an interface object identifier.
Background
Referring to fig. 1, a Slicing Packet Network (SPN) of the existing Network transport Network implements management and service delivery to a Network based on an Operation and Maintenance Center (OMC), and the OMC interacts with an upper-layer integrated resource management system upwards and reports information based on a northbound acquisition interface.
At present, service issuing is realized in a work order mode, namely, a comprehensive resource management system issues a service configuration work order, operation and maintenance personnel manually perform configuration on an OMC after receiving the work order, and manually return the completion condition of the work order to an upper comprehensive resource management system after completing the service configuration. Because the whole process adopts a manual intervention mode, a plurality of personnel need to be coordinated for manual operation, and therefore, the service configuration time is long, and the opening efficiency is low.
An existing Network transport Network (SPN) is performing Network transformation in a Software Defined Network (SDN) -oriented architecture, and realizes automatic configuration of services based on a Super Controller (SC), as shown in fig. 2. Under the SPN network structure facing the SDN, single-domain service management and control are realized based on the OMC, cross-domain service management and control are realized based on the SC, and the SC realizes interaction with OMCs of different manufacturers based on a standard northbound service configuration interface. After the SC receives the service opening requirement from the comprehensive resource management system, a plurality of OMCs are called based on the northbound service configuration interface to realize automatic service issuing without manual intervention, so that the service issuing efficiency can be greatly improved, and the service experience is improved.
In the SPN northbound acquisition interface of the existing network transmission network, object Identification (ID) of an OMC northbound interface is automatically generated by the OMC, and the requirement is globally unique.
After deployment of the SC, many northbound interface object IDs need to be generated by the SC. There are already a large number of northbound interface object IDs on the existing network OMC. The new interface object ID generated by the SC is easy to collide with the existing stock north interface object ID of the OMC, so that the north interface object ID is not unique, and the system is in error.
In the transport network, except for SC and OMC, if interface object identifiers of the same type need to be generated by different network elements, the problem of interface object identifier collision is also easily caused.
Disclosure of Invention
The embodiment of the invention provides a method and a device for generating interface object identifiers, which are used for solving the problem of interface object identifier conflict caused by generating the same type of interface object identifiers by different network elements.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a method for generating an interface object identifier, which is applied to a first network element, and includes:
sending request information to a second network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
receiving response information sent by the second network element, wherein the response information comprises a mapping relation between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and the type of the target identifier is different from that of the temporary identifier;
and replacing the temporary identifier of the target first interface object with the target identifier, and storing the target identifier in a database.
Optionally, the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
Optionally, the target first interface object is a service or a tunnel that needs to be created by the super controller.
Optionally, the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
Optionally, the temporary identifier is a universal unique identification code.
Optionally, the target identifier is a resource management global identity.
In a second aspect, an embodiment of the present invention provides a method for generating an interface object identifier, which is applied to a second network element, and includes:
receiving request information sent by a first network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
if the target first interface object is a first interface object requiring the second network element to generate a target identifier, generating the target identifier of the target first interface object, wherein the type of the target identifier is different from that of the temporary identifier;
and sending response information to the first network element, wherein the response information comprises the mapping relation between the target identifier and the temporary identifier of the target first interface object.
Optionally, the method further includes:
recording a first interface object information table, wherein the first interface object information table records information of all first interface objects needing to be generated by the second network element into a target identifier;
if the target first interface object is a first interface object for which a target identifier needs to be generated by the second network element, before generating the target identifier of the target first interface object, the method further includes:
and judging whether the target first interface object is recorded in the first interface object information table, if so, judging that the target first interface object is the first interface object needing to be generated into a target identifier by the second network element.
Optionally, the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
Optionally, the target first interface object is a service or a tunnel that needs to be created by the super controller.
Optionally, the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
Optionally, the temporary identifier is a universal unique identification code.
Optionally, the target identifier is a resource management global identity.
In a third aspect, an embodiment of the present invention provides a first network element, including:
a sending module, configured to send request information to a second network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a receiving module, configured to receive response information sent by the second network element, where the response information includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and a type of the target identifier is different from a type of the temporary identifier;
and the replacing module is used for replacing the temporary identifier of the target first interface object with the target identifier and storing the target identifier in a database.
In a fourth aspect, an embodiment of the present invention provides a second network element, including:
a receiving module, configured to receive request information sent by a first network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a generating module, configured to generate a target identifier of the target first interface object if the target first interface object is a first interface object for which a target identifier needs to be generated by the second network element, where a type of the target identifier is different from a type of the temporary identifier;
a sending module, configured to send response information to the first network element, where the response information includes a mapping relationship between a target identifier and a temporary identifier of the target first interface object.
In a fifth aspect, an embodiment of the present invention provides a network element, including: a processor, a memory and a program stored on the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method for generating an interface object identifier of the first aspect; alternatively, the program realizes the steps of the interface object identifier generation method of the second aspect when executed by the processor.
In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements the steps of the method for generating an interface object identifier according to the first aspect; alternatively, the computer program, when executed by a processor, implements the steps of the interface object identifier generation method of the second aspect.
In the embodiment of the present invention, when a first network element needs to generate a target identifier for a target first interface object, a temporary identifier serving as an intermediate process identifier is generated and sent to a second network element, the second network element generates the target identifier, and a mapping relationship between the target identifier and the temporary identifier is created, the first network element replaces the temporary identifier with the target identifier according to the mapping relationship, and since the target identifiers are generated by the second network element, a problem that the target identifiers of the target first interface object are likely to conflict with the target identifiers of the first interface object stored in the second network element when the first network element generates the target identifiers of the target first interface object is avoided.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic diagram of an existing transport network SPN network architecture;
fig. 2 is a schematic diagram of an SDN-oriented SPN network architecture;
fig. 3 is a schematic flowchart of a method for generating an interface object identifier applied to a first network element according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a method for generating an interface object identifier applied to an SC according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a method for generating an interface object identifier applied to a second network element according to an embodiment of the present invention;
fig. 6 is a schematic flowchart of a method for generating an interface object identifier applied to an OMC according to an embodiment of the present invention;
FIG. 7 is a schematic flow diagram of a method of generating an rmUID according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a first network element according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a second network element according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a first network element according to another embodiment of the present invention;
fig. 11 is a schematic structural diagram of a second network element according to another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 3, an embodiment of the present invention provides a method for generating an interface object identifier, which is applied to a first network element, and includes:
step 31: sending request information to a second network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
that is, the first network element and the second network element communicate with each other through the first interface, and the first interface object is an object interactively involved between the first network element and the second network element.
The temporary identifier is globally unique and is used for uniquely identifying the target first interface object, and meanwhile, the temporary identifier is an intermediate process identifier and is only stored in the memory without being stored in the database.
Step 32: receiving response information sent by the second network element, wherein the response information comprises a mapping relation between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and the type of the target identifier is different from that of the temporary identifier;
the target identification is an identification which is required for communication between the first network element and the second network element and can uniquely identify the first interface object, and the target identification is generated by the second network element and is globally unique.
Step 33: and replacing the temporary identifier of the target first interface object with the target identifier, and storing the target identifier in a database.
In this embodiment of the present invention, optionally, a plurality of target identifiers of a first interface object are stored in a second network element, and when a first network element needs to generate a target identifier for a target first interface object, a temporary identifier serving as an intermediate process identifier is generated and sent to the second network element, and the second network element generates the target identifier and creates a mapping relationship between the target identifier and the temporary identifier, and the first network element replaces the temporary identifier with the target identifier according to the mapping relationship.
The first network element and the second network element may be any network element in a transport network.
In some embodiments of the present invention, optionally, the first network element is a Super Controller (SC), the second network element is a network management Operation and Maintenance Center (OMC), and the first interface is a northbound interface.
Referring to fig. 4, an embodiment of the present invention provides a method for generating an interface object identifier, which is applied to an SC and includes:
step 41: sending request information to an OMC through a northbound interface, wherein the request information comprises a temporary identifier of a target northbound interface object, and the temporary identifier is generated by the SC;
optionally, the target northbound interface object is an object such as a service or a tunnel that needs to be created by the SC.
The temporary identifier is globally unique and is used for uniquely identifying the target northbound interface object, and meanwhile, the temporary identifier is an intermediate process identifier and is stored in the memory without being stored in the database.
Optionally, the temporary Identifier is a Universal Unique Identifier (UUID). The UUID refers to a character string generated on one machine, which is guaranteed to be unique to all machines in the same space-time, and RFC4122 makes standard definition on the generation method and the representation method of the UUID. The standard format of UUID contains 32 16 carry digits, divided into five segments with hyphen numbers, 32 characters in the form of 8-4-4-4-12. For example, the following are: 550e8400-e29b-41d4-a 716-446655440000. Based on the generation mode of the UUID, the SC can ensure that a globally unique ID is generated.
Of course, in the embodiment of the present invention, except for the UUID, it is not excluded that other types of identification groups are used as the temporary identification, as long as the target northbound interface object can be uniquely identified.
Step 42: receiving response information sent by an OMC, wherein the response information comprises a mapping relation between a target identifier of the target northbound interface object and the temporary identifier, the target identifier is generated by the OMC, and the type of the target identifier is different from that of the temporary identifier;
the target identification is an identification which is finally required by communication between the SC and the OMC and can uniquely identify the northbound interface object, and is generated by the OMC and globally unique.
Optionally, the target identifier is a resource management global identity (rmUID). The rmUID format requires the following: the 1 st to 4 th bits represent city codes of provinces and provinces managed by the OMC, the 5 th to 6 th bits represent OMC manufacturer codes, the 7 th to 8 th bits represent OMC professional codes, the 9 th bits represent OMC numbers, the 10 th to 12 th bits represent resource object types for short, the 13 th to 28 th bits are resource object numbers, and the OMC automatically generates the codes at random to ensure the uniqueness in the OMC. The value range of each bit is as follows: 0-9, A-Z.
Based on the generation rule of the rmUID, the 13 th bit to the 28 th bit is randomly generated, if the rmUID of the northbound interface object is generated by the SC, the rmUID is easy to collide with the existing rmUID stock of the OMC, the rmUID is not unique, and the system is in error. Taking service issuing as an example, when SC is not deployed, service creation is completed by manual operation on OMC, service rmUID is generated automatically by OMC, and then service operation is performed based on the rmUID generated by OMC. After the SC is deployed, service creation is initiated by the SC, if the generation of the rmUID of the service is completed by the SC, the SC creates the service ID based on the rmUID generation rule, and because a large amount of stock services exist in the current network, namely a large amount of service rmUIDs exist, the SC is easy to conflict with the existing rmUIDs when generating the rmUIDs, so that the service creation failure is caused, and the service creation efficiency is greatly influenced.
In the embodiment of the invention, the rmUID is generated by the OMC, so that the conflict of the rmUID stocks can be avoided.
Step 43: replacing the temporary identifier of the target northbound interface object with the target identifier, and storing the target identifier in a database.
In the embodiment of the present invention, optionally, the request information is service creation request information or tunnel creation request information; the response information is service creation result information or tunnel creation result information.
That is, the SC may obtain the target identifier of the service or the tunnel in the process of requesting the OMC to create the service or the tunnel, so that a separate obtaining process is not required, thereby saving implementation cost.
Referring to fig. 5, an embodiment of the present invention further provides a method for generating an interface object identifier, which is applied to a second network element, and includes:
step 51: receiving request information sent by a first network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
step 52: if the target first interface object is a first interface object requiring the second network element to generate a target identifier, generating the target identifier of the target first interface object, wherein the type of the target identifier is different from that of the temporary identifier;
step 53: and sending response information to the first network element, wherein the response information comprises the mapping relation between the target identifier and the temporary identifier of the target first interface object.
In this embodiment of the present invention, optionally, a plurality of target identifiers of the first interface object are stored in the second network element, and when the first network element needs to generate a target identifier for the target first interface object, the second network element generates a temporary identifier serving as an intermediate process identifier and requests the first network element to generate the target identifier, and generates the target identifier of the target interface object, and sends a mapping relationship between the target identifier of the target interface object and the temporary identifier to the first network element, thereby avoiding a problem that the target identifier of the target first interface object is likely to conflict with the target identifier of the first interface object stored in the second network element when the first network element itself generates the target identifier of the target first interface object.
In this embodiment of the present invention, optionally, the method for generating the interface object identifier further includes:
step 50: recording a first interface object information table, wherein the first interface object information table records information of all first interface objects needing to be generated by the second network element into a target identifier;
at this time, before step 52 (if the target first interface object is the first interface object that needs to be generated by the second network element to generate the target identifier of the target first interface object), the method further includes:
step 52': and judging whether the target first interface object is recorded in the first interface object information table, if so, judging that the target first interface object is the first interface object needing to be generated into a target identifier by the second network element.
In some embodiments of the present invention, optionally, the first network element is a Super Controller (SC), the second network element is a network management Operation and Maintenance Center (OMC), and the first interface is a northbound interface.
Referring to fig. 6, an embodiment of the present invention provides a method for generating an interface object identifier, which is applied to an OMC, and includes:
step 61: receiving request information sent by an SC (service center) through a northbound interface, wherein the request information comprises a temporary identifier of a target northbound interface object, and the temporary identifier is generated by the SC;
optionally, the target first interface object is an object such as a service or a tunnel that needs to be created by the SC.
The temporary identifier is an intermediate process identifier and is globally unique. Optionally, the temporary identifier is a Universal Unique Identifier (UUID).
Step 62: if the target northbound interface object is a northbound interface object needing to be generated with a target identifier by the OMC, generating the target identifier of the target northbound interface object, wherein the type of the target identifier is different from that of the temporary identifier;
the target identification is the target identification finally needed by communication between the SC and the OMC, is generated by the OMC and is globally unique. Optionally, the target identifier is a resource management global identity (rmUID).
And step 63: and sending response information to the SC, wherein the response information comprises the mapping relation between the target identifier and the temporary identifier of the target first interface object.
In the embodiment of the present invention, optionally, the request information is service creation request information or tunnel creation request information; the response information is service creation result information or tunnel creation result information.
That is, the SC may obtain the target identifier of the service or the tunnel in the process of requesting the OMC to create the service or the tunnel, so that a separate obtaining process is not required, thereby saving implementation cost.
The following describes an example of a method for generating a service rmUID in a service creation process.
Referring to fig. 7, the method of generating the rmUID includes:
step 71: the OMC records a northbound interface object information table, and the northbound interface object information table records information of all northbound interface objects needing to be generated into the rmUID by the OMC;
step 72: an SC sends service creation request information to an OMC through a northbound interface, wherein the service creation request information comprises a UUID of a target service, the UUID is generated by the SC based on a UUID rule in RFC4122, the ID of the whole network is unique, and the UUID does not need to be stored in a database and only needs to be stored in a memory;
optionally, the service creation request information may further include at least one of the following: the type of service, the protection type, the information of the network element and the interface of the service access point, the service bandwidth, the VLAN ID and other information.
Step 73: after receiving the service creation request information, the OMC judges whether the target service is recorded in a northbound interface object information table, if so, the OMC judges that the target service is a northbound interface object needing to generate the rmUID by the OMC, and the OMC generates the rmUID of the target service based on an rmUID generation rule to ensure that the rmUID of the target service is globally unique;
step 74: the OMC interacts with the forwarding layer equipment based on a service creation request issued by the SC to create a service;
step 75: the OMC receives a service creation result returned by the forwarding layer equipment;
step 76: OMC sends service creating result information to SC, the service creating result information includes UUID of target service and rmUID mapping relation, and service creating success identification;
step 77: and after the SC receives the successful service creation identifier reported by the OMC, replacing the UUID of the target service with the rmUID based on the mapping relation between the UUID and the rmUID of the target service reported by the OMC, and storing the unique identifier of the target service into a database by using the rmUID.
Step 78: and the SC performs subsequent service operation based on the rmUID stored in the database as the unique identifier of the target service.
Referring to fig. 8, an embodiment of the present invention further provides a first network element 80, including:
a sending module 81, configured to send request information to a second network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a receiving module 82, configured to receive response information sent by the second network element, where the response information includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and a type of the target identifier is different from a type of the temporary identifier;
and a replacing module 83, configured to replace the temporary identifier of the target first interface object with the target identifier, and store the target identifier in a database.
Optionally, the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
Optionally, the target first interface object is a service or a tunnel that needs to be created by the super controller.
Optionally, the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
Optionally, the temporary identifier is a universal unique identification code.
Optionally, the target identifier is a resource management global identity.
Referring to fig. 9, an embodiment of the present invention further provides a second network element 90, including:
a receiving module 91, configured to receive request information sent by a first network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a generating module 92, configured to generate a target identifier of the target first interface object if the target first interface object is a first interface object that needs to be generated by the second network element, where a type of the target identifier is different from a type of the temporary identifier;
a sending module 93, configured to send response information to the first network element, where the response information includes a mapping relationship between a target identifier and a temporary identifier of the target first interface object.
Optionally, the second network element 90 further includes:
a recording module, configured to record a first interface object information table, where information of all first interface objects requiring generation of a target identifier by the second network element is recorded in the first interface object information table;
and a judging module, configured to judge whether the target first interface object is recorded in the first interface object information table, and if so, judge that the target first interface object is a first interface object for which a target identifier needs to be generated by the second network element.
Optionally, the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
Optionally, the target first interface object is a service or a tunnel that needs to be created by the super controller.
Optionally, the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
Optionally, the temporary identifier is a universal unique identification code.
Optionally, the target identifier is a resource management global identity.
Referring to fig. 10, an embodiment of the present invention further provides a first network element 100, which includes a processor 101, a memory 102, and a computer program stored in the memory 102 and capable of running on the processor 101, where the computer program, when executed by the processor 101, implements the processes of the above-mentioned embodiment of the method for generating an interface object identifier applied to the first network element, and can achieve the same technical effects, and therefore, in order to avoid repetition, details are not repeated here.
Referring to fig. 11, an embodiment of the present invention further provides a first network element 110, which includes a processor 111, a memory 112, and a computer program stored in the memory 112 and capable of running on the processor 111, where the computer program, when executed by the processor 111, implements the processes of the above-mentioned embodiment of the method for generating an interface object identifier applied to a second network element, and can achieve the same technical effects, and therefore, in order to avoid repetition, details are not repeated here.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements each process of the above embodiment of the method for generating an interface object identifier applied to a first network element, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements each process of the above embodiment of the method for generating an interface object identifier applied to a second network element, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (17)
1. A method for generating an interface object identifier is applied to a first network element, and is characterized by comprising the following steps:
sending request information to a second network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
receiving response information sent by the second network element, wherein the response information comprises a mapping relation between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and the type of the target identifier is different from that of the temporary identifier;
and replacing the temporary identifier of the target first interface object with the target identifier, and storing the target identifier in a database.
2. The method of claim 1, wherein the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
3. The method of claim 2, wherein the target first interface object is a traffic or tunnel to be created by the hypervisor.
4. The method of claim 3,
the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
5. The method according to any one of claims 1 to 4, wherein the temporary identifier is a universally unique identification code.
6. The method according to any one of claims 1 to 4, wherein the target identifier is a resource management global identity.
7. A method for generating an interface object identifier is applied to a second network element, and is characterized by comprising the following steps:
receiving request information sent by a first network element through a first interface, wherein the request information comprises a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
if the target first interface object is a first interface object requiring the second network element to generate a target identifier, generating the target identifier of the target first interface object, wherein the type of the target identifier is different from that of the temporary identifier;
and sending response information to the first network element, wherein the response information comprises the mapping relation between the target identifier of the target first interface object and the temporary identifier.
8. The method of claim 7, further comprising:
recording a first interface object information table, wherein the first interface object information table records information of all first interface objects needing to be generated by the second network element into a target identifier;
if the target first interface object is a first interface object for which a target identifier needs to be generated by the second network element, before generating the target identifier of the target first interface object, the method further includes:
and judging whether the target first interface object is recorded in the first interface object information table, if so, judging that the target first interface object is the first interface object needing to be generated into a target identifier by the second network element.
9. The method of claim 7, wherein the first network element is a super controller, the second network element is a network management operation and maintenance center, and the first interface is a northbound interface.
10. The method of claim 9, wherein the target first interface object is a traffic or tunnel to be created by the hypervisor.
11. The method of claim 10,
the request information is service creation request information or tunnel creation request information;
the response information is service creation result information or tunnel creation result information.
12. The method according to any of claims 7 to 11, wherein the temporary identification is a universally unique identification code.
13. The method according to any of claims 7 to 11, wherein the target identifier is a resource management global identity.
14. A first network element, comprising:
a sending module, configured to send request information to a second network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a receiving module, configured to receive response information sent by the second network element, where the response information includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, the target identifier is generated by the second network element, and a type of the target identifier is different from a type of the temporary identifier;
and the replacing module is used for replacing the temporary identifier of the target first interface object with the target identifier and storing the target identifier in a database.
15. A second network element, comprising:
a receiving module, configured to receive request information sent by a first network element through a first interface, where the request information includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;
a generating module, configured to generate a target identifier of the target first interface object if the target first interface object is a first interface object for which a target identifier needs to be generated by the second network element, where a type of the target identifier is different from a type of the temporary identifier;
a sending module, configured to send response information to the first network element, where the response information includes a mapping relationship between a target identifier and a temporary identifier of the target first interface object.
16. A network element, comprising: a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the method of generating an interface object identification according to any one of claims 1 to 6; alternatively, the program realizes the steps of the method for generating an interface object identifier according to any one of claims 7 to 13 when executed by the processor.
17. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method for generating an interface object identification according to any one of claims 1 to 6; alternatively, the computer program realizes the steps of the method for generating an interface object identification according to any one of claims 7 to 13 when being executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011054786.7A CN114363286A (en) | 2020-09-27 | 2020-09-27 | Interface object identifier generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011054786.7A CN114363286A (en) | 2020-09-27 | 2020-09-27 | Interface object identifier generation method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114363286A true CN114363286A (en) | 2022-04-15 |
Family
ID=81090044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011054786.7A Pending CN114363286A (en) | 2020-09-27 | 2020-09-27 | Interface object identifier generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114363286A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103052098A (en) * | 2012-11-21 | 2013-04-17 | 大唐移动通信设备有限公司 | Method and device for north orientation performance test |
| CN110536283A (en) * | 2019-09-02 | 2019-12-03 | 百度在线网络技术（北京）有限公司 | Terminal identifier acquisition method, device, electronic equipment and medium |
-
2020
- 2020-09-27 CN CN202011054786.7A patent/CN114363286A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103052098A (en) * | 2012-11-21 | 2013-04-17 | 大唐移动通信设备有限公司 | Method and device for north orientation performance test |
| CN110536283A (en) * | 2019-09-02 | 2019-12-03 | 百度在线网络技术（北京）有限公司 | Terminal identifier acquisition method, device, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8077334B2 (en) | Method and apparatus for managing printing solutions in a local area network | |
| US11265210B2 (en) | Network slice configuration method, apparatus, and system | |
| EP2334024B1 (en) | Method and device for terminal management based on right control | |
| CN109861861B (en) | Rapid configuration method and system for network communication equipment | |
| US20210075711A1 (en) | Cluster wide packet tracing | |
| US20050086332A1 (en) | Network device management method, network device management program, and network control apparatus | |
| CN109714239B (en) | Management message issuing method, VNFM (virtual network management frequency) equipment and server | |
| CN112152826B (en) | Asset management method, device, system and medium | |
| CN112953774B (en) | Network topology generation method, system, equipment and computer storage medium | |
| CN111901317B (en) | Access control policy processing method, system and equipment | |
| CN105049546B (en) | A kind of Dynamic Host Configuration Protocol server is the method and device of client distribution IP address | |
| CN112491941A (en) | Data management method, related product and communication system | |
| CN101677441A (en) | Method, device and system of authorization control | |
| CN101572621A (en) | Error cause return method and system capable of realizing network management | |
| KR20060040335A (en) | Network managing device and method thereof | |
| CN113301378B (en) | Broadcast signaling transmission method, device, system, electronic device and storage medium | |
| CN114363286A (en) | Interface object identifier generation method and device | |
| CN110213365B (en) | User access request processing method based on user partition and electronic equipment | |
| CN116719868A (en) | Network asset identification method, device and equipment | |
| CN106899429B (en) | SNMP-based equipment management method and device | |
| CN107493181B (en) | Indication method and device of virtual expansion port | |
| CN115567388A (en) | Method, system, device and storage medium for automatically updating network slice configuration | |
| CN112367413A (en) | Method for embedding MAC address into DHCPv6 stateful address allocation | |
| CN113407546A (en) | Rule configuration method suitable for various scenes | |
| CN114697291A (en) | Method, device, server and storage medium for acquiring available IP address field |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |