Method and device for generating interface object identifier

Through communication between different network elements in the transmission network, the mapping relationship between temporary identification and target identification is used to solve the problem of interface object identification conflict, and the service configuration efficiency and system stability are improved.

CN114363286BActive Publication Date: 2024-11-08CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011054786.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-27
Publication Date
2024-11-08
Estimated Expiration
2040-09-27

AI Technical Summary

Technical Problem

In the transmission network, interface object identifiers generated by different network elements are likely to cause conflicts, affecting system stability and business configuration efficiency.

Method used

The request information is sent to the second network element through the first network element, including a temporary identifier, the second network element generates a target identifier and establishes a mapping relationship, and the first network element replaces the temporary identifier and stores the target identifier to avoid conflicts.

Benefits of technology

有效避免了接口对象标识的冲突,提高了业务配置的效率和系统稳定性,减少了人工干预的需求。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114363286B_ABST
    Figure CN114363286B_ABST
Patent Text Reader

Abstract

The present invention provides a method and device for generating an interface object identifier, the method comprising: a first network element sends a request message to a second network element through a first interface, the request message includes 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 that requires a target identifier to be generated by the second network element, the second network element generates a target identifier of the target first interface object, and the type of the target identifier is different from the type of the temporary identifier; the second network element sends a response message to the first network element, the response message includes a mapping relationship between the target identifier of the target first interface object and the temporary identifier; the first network element replaces the temporary identifier of the target first interface object with the target identifier, and stores the target identifier in a database. The present invention can avoid the problem of interface object identifier conflicts caused by different network elements generating the same type of interface object identifiers.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of transmission technology, and in particular to a method and device for generating an interface object identifier. Background Art

[0002] See also Figure 1 The existing transport network Slicing Packet Network (SPN) manages the network and distributes services based on the network management and maintenance center (OMC). The OMC interacts with the upper-level integrated resource management system and reports information based on the northbound collection interface.

[0003] Currently, services are issued in the form of work orders, that is, the integrated resource management system issues a service configuration work order, and after receiving the work order, the operation and maintenance personnel manually configure it on the OMC. After the service configuration is completed, the completion status of the work order is manually returned to the upper-level integrated resource management system. Because the entire process uses manual intervention, it is necessary to coordinate multiple personnel to perform manual operations, which leads to a long service configuration time and low activation efficiency.

[0004] The existing transport network SPN is undergoing network transformation towards the Software Defined Network (SDN) architecture, and is implementing automated service configuration based on the Super Controller (SC). Figure 2 As shown in the figure. Under the SDN-oriented SPN network structure, single-domain service management and control are implemented based on OMC, and cross-domain service management and control are implemented based on SC. SC interacts with OMCs of different manufacturers based on the standard northbound service configuration interface. After SC receives service provisioning requirements from the integrated resource management system, it calls multiple OMCs based on the northbound service configuration interface to automatically distribute services without manual intervention, which can greatly improve service distribution efficiency and enhance service experience.

[0005] In the existing transport network SPN northbound collection interface, the OMC northbound interface object identifier (ID) is automatically generated by the OMC and is required to be globally unique.

[0006] After SC is deployed, many northbound interface object IDs need to be generated by SC. A large number of northbound interface object IDs already exist on the existing OMC. The new interface object IDs generated by SC are likely to conflict with the existing northbound interface object IDs of OMC, resulting in non-unique northbound interface object IDs and system errors.

[0007] In the transport network, in addition to the SC and OMC, if different network elements need to generate the same type of interface object identifier, it is also easy to cause the problem of interface object identifier conflict. Summary of the invention

[0008] The embodiment of the present invention provides a method and device for generating an interface object identifier, which are used to solve the problem of interface object identifier conflicts caused by different network elements generating the same type of interface object identifiers.

[0009] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:

[0010] 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, including:

[0011] Sending a request message to the second network element through the first interface, wherein the request message includes a temporary identifier of the target first interface object, and the temporary identifier is generated by the first network element;

[0012] receiving a response message sent by the second network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, wherein 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;

[0013] The temporary identifier of the target first interface object is replaced with the target identifier, and the target identifier is stored in a database.

[0014] 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.

[0015] Optionally, the target first interface object is a service or tunnel that needs to be created by the super controller.

[0016] Optionally, the request information is service creation request information or tunnel creation request information;

[0017] The response information is service creation result information or tunnel creation result information.

[0018] Optionally, the temporary identifier is a universal unique identification code.

[0019] Optionally, the target identifier is a resource management global identifier.

[0020] 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, including:

[0021] Receiving, through the first interface, a request message sent by the first network element, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0022] 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, a target identifier of the target first interface object is generated, and a type of the target identifier is different from a type of the temporary identifier;

[0023] Sending a response message to the first network element, wherein the response message includes a mapping relationship between a target identifier and a temporary identifier of the target first interface object.

[0024] Optionally, the method further includes:

[0025] Recording a first interface object information table, wherein the first interface object information table records information of all first interface objects for which a target identifier needs to be generated by the second network element;

[0026] 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:

[0027] Determine whether the target first interface object is recorded in the first interface object information table, and if so, determine that the target first interface object is a first interface object that requires the second network element to generate a target identifier.

[0028] 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.

[0029] Optionally, the target first interface object is a service or tunnel that needs to be created by the super controller.

[0030] Optionally, the request information is service creation request information or tunnel creation request information;

[0031] The response information is service creation result information or tunnel creation result information.

[0032] Optionally, the temporary identifier is a universal unique identification code.

[0033] Optionally, the target identifier is a resource management global identifier.

[0034] In a third aspect, an embodiment of the present invention provides a first network element, including:

[0035] A sending module, configured to send a request message to a second network element through a first interface, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0036] a receiving module, configured to receive a response message sent by the second network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, wherein 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;

[0037] A replacement module is used to replace the temporary identifier of the target first interface object with the target identifier, and store the target identifier in a database.

[0038] In a fourth aspect, an embodiment of the present invention provides a second network element, including:

[0039] A receiving module, configured to receive a request message sent by a first network element through a first interface, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0040] 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, wherein a type of the target identifier is different from a type of the temporary identifier;

[0041] The sending module is used to send response information to the first network element, and the response information includes a mapping relationship between the target identifier and the temporary identifier of the target first interface object.

[0042] In the fifth aspect, an embodiment of the present invention provides a network element, comprising: a processor, a memory, and a program stored in 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 mentioned above; or, the program, when executed by the processor, implements the steps of the method for generating an interface object identifier of the second aspect mentioned above.

[0043] In the sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method for generating an interface object identifier of the first aspect are implemented; or, when the computer program is executed by a processor, the steps of the method for generating an interface object identifier of the second aspect are implemented.

[0044] In an embodiment of the present invention, when the first network element needs to generate a target identifier for a target first interface object, a temporary identifier is generated as an intermediate process identifier and sent to a second network element. The second network element generates a target identifier and creates a mapping relationship between the target identifier and the temporary identifier. The first network element replaces the temporary identifier with the target identifier based on the mapping relationship. Since the target identifiers are all generated by the second network element, the problem of conflict between the target identifier of the target first interface object stored in the second network element and the target identifier of the first interface object generated by the first network element itself is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0046] Figure 1 This is a schematic diagram of the SPN network architecture of the existing transport network;

[0047] Figure 2 This is a schematic diagram of the SPN network architecture for SDN;

[0048] Figure 3 A schematic diagram of a flow chart of a method for generating an interface object identifier applied to a first network element according to an embodiment of the present invention;

[0049] Figure 4 A schematic diagram of a flow chart of a method for generating an interface object identifier applied to an SC according to an embodiment of the present invention;

[0050] Figure 5 A schematic flow chart of a method for generating an interface object identifier applied to a second network element according to an embodiment of the present invention;

[0051] Figure 6 A schematic flow chart of a method for generating an interface object identifier applied to OMC according to an embodiment of the present invention;

[0052] Figure 7 Schematic diagram of the flow of the method for generating rmUID according to an embodiment of the present invention;

[0053] Figure 8 A schematic diagram of the structure of a first network element according to an embodiment of the present invention;

[0054] Fig. 9 A schematic diagram of the structure of a second network element according to an embodiment of the present invention;

[0055] Fig.10 A schematic diagram of the structure of a first network element according to another embodiment of the present invention;

[0056] Fig.11 A schematic diagram of the structure of a second network element according to another embodiment of the present invention. DETAILED DESCRIPTION

[0057] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0058] Please refer to Figure 3 The embodiment of the present invention provides a method for generating an interface object identifier, which is applied to a first network element and includes:

[0059] Step 31: Sending a request message to the second network element through the first interface, wherein the request message includes a temporary identifier of the target first interface object, and the temporary identifier is generated by the first network element;

[0060] 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 involved in the interaction between the first network element and the second network element.

[0061] The temporary identifier is globally unique and is used to uniquely identify the target first interface object. At the same time, the temporary identifier is an intermediate process identifier and can be stored in the memory without being stored in the database.

[0062] Step 32: 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, where 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;

[0063] The target identifier is an identifier that is ultimately required for communication between the first network element and the second network element and can uniquely identify the first interface object. It is generated by the second network element and is globally unique.

[0064] Step 33: Replace the temporary identifier of the target first interface object with the target identifier, and store the target identifier in a database.

[0065] In an embodiment of the present invention, optionally, target identifiers of multiple first interface objects are stored in the second network element. When the first network element needs to generate a target identifier for the target first interface object, a temporary identifier is generated as an intermediate process identifier and sent to the second network element. The second network element generates the target identifier and creates a mapping relationship between the target identifier and the temporary identifier. The first network element replaces the temporary identifier with the target identifier based on the mapping relationship. Since the target identifiers are all generated by the second network element, the problem of conflict between the target identifier of the target first interface object stored in the second network element and the target identifier of the first interface object generated by the first network element itself is avoided.

[0066] The first network element and the second network element may be any network elements in the transport network.

[0067] 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.

[0068] Please refer to Figure 4 The embodiment of the present invention provides a method for generating an interface object identifier, which is applied to an SC and includes:

[0069] Step 41: Send a request message to the OMC through the northbound interface, wherein the request message includes a temporary identifier of the target northbound interface object, and the temporary identifier is generated by the SC;

[0070] Optionally, the target northbound interface object is an object such as a service or tunnel that needs to be created by the SC.

[0071] The temporary identifier is globally unique and is used to uniquely identify the target northbound interface object. At the same time, the temporary identifier is an intermediate process identifier and can be stored in the memory without being stored in the database.

[0072] Optionally, the temporary identifier is a Universally Unique Identifier (UUID). UUID refers to a string generated on a machine, which is guaranteed to be unique for all machines in the same space and time. RFC4122 has made a standard definition for the generation and representation methods of UUID. The standard format of UUID contains 32 hexadecimal digits, divided into five segments by hyphens, in the form of 32 characters of 8-4-4-4-12. For example: 550e8400-e29b-41d4-a716-446655440000. Based on the generation method of UUID, SC can ensure the generation of a globally unique ID.

[0073] Of course, in the embodiment of the present invention, in addition to UUID, it is not excluded to use other types of identification groups as the temporary identification, as long as they can uniquely identify the target northbound interface object.

[0074] Step 42: receiving a response message sent by the OMC, wherein the response message includes a mapping relationship between a target identifier of the target northbound interface object and the temporary identifier, wherein the target identifier is generated by the OMC, and a type of the target identifier is different from a type of the temporary identifier;

[0075] The target identifier is an identifier that is ultimately required for communication between the SC and the OMC and can uniquely identify the northbound interface object. It is generated by the OMC and is globally unique.

[0076] Optionally, the target identifier is the resource management global identifier (rmUID). The rmUID format requirements are as follows: the 1st to 4th digits represent the province, city, and district code of the OMC, the 5th to 6th digits represent the OMC manufacturer code, the 7th to 8th digits represent the OMC professional code, the 9th digit represents the OMC number, the 10th to 12th digits represent the resource object category abbreviation, and the 13th to 28th digits are the resource object number, which is automatically randomly generated by the OMC to ensure that it is unique in this OMC. The value range of each digit from 13th to 28th digit is: 0-9, AZ.

[0077] Based on the rmUID generation rules, the 13th to 28th bits are randomly generated. If the SC generates the rmUID of the northbound interface object, it is easy to conflict with the existing rmUID of the OMC, resulting in non-unique rmUID and system errors. Taking service delivery as an example, when the SC is not deployed, service creation is completed by manual operation on the OMC, and the service rmUID is automatically generated by the OMC. Subsequent service operations are based on the rmUID generated by the OMC. After the SC is deployed, service creation is initiated by the SC. If the rmUID generation of the service is completed by the SC, the SC creates the service ID based on the rmUID generation rules. Because there are already a large number of existing services in the existing network, that is, there are already a large number of service rmUIDs, when the SC generates the rmUID, it is easy to conflict with the existing rmUID, resulting in service creation failure, which greatly affects the efficiency of service creation.

[0078] However, in the embodiment of the present invention, the rmUID is generated by the OMC, which can avoid conflicts among the existing rmUIDs.

[0079] Step 43: Replace the temporary identifier of the target northbound interface object with the target identifier, and store the target identifier in a database.

[0080] In the embodiment of the present invention, optionally, the request information is service creation request information or tunnel creation request information; and the response information is service creation result information or tunnel creation result information.

[0081] That is, the SC can obtain the target identifier of the service or tunnel in the process of requesting the OMC to create the service or tunnel, so that a separate acquisition process is not required, thereby saving implementation costs.

[0082] Please refer to Figure 5 The 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:

[0083] Step 51: receiving a request message sent by a first network element through a first interface, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0084] Step 52: 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, generate a target identifier of the target first interface object, wherein the type of the target identifier is different from the type of the temporary identifier;

[0085] Step 53: Send response information to the first network element, where the response information includes a mapping relationship between the target identifier and the temporary identifier of the target first interface object.

[0086] In an embodiment of the present invention, optionally, target identifiers of multiple first interface objects are stored in the second network element. 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 as an intermediate process identifier and requests the first network element to generate the target identifier. The second network element generates the target identifier of the target interface object and sends the mapping relationship between the target identifier of the target interface object and the temporary identifier to the first network element, thereby avoiding the problem that when the first network element itself generates the target identifier of the first interface object, it is easy to conflict with the target identifier of the first interface object stored in the second network element.

[0087] In the embodiment of the present invention, optionally, the method for generating the interface object identifier further includes:

[0088] Step 50: Record a first interface object information table, wherein the first interface object information table records information of all first interface objects for which the second network element needs to generate a target identifier;

[0089] At this time, the above step 52 (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, generating a target identifier of the target first interface object) also includes:

[0090] Step 52': Determine whether the target first interface object is recorded in the first interface object information table, and if so, determine that the target first interface object is a first interface object that requires the second network element to generate a target identifier.

[0091] 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.

[0092] Please refer to Figure 6 The embodiment of the present invention provides a method for generating an interface object identifier, which is applied to OMC and includes:

[0093] Step 61: receiving a request message sent by the SC through the northbound interface, wherein the request message includes a temporary identifier of a target northbound interface object, and the temporary identifier is generated by the SC;

[0094] Optionally, the target first interface object is an object such as a service or tunnel that needs to be created by the SC.

[0095] The temporary identifier is an intermediate process identifier and is globally unique. Optionally, the temporary identifier is a universal unique identifier (UUID).

[0096] Step 62: If the target northbound interface object is a northbound interface object for which a target identifier needs to be generated by the OMC, generate a target identifier for the target northbound interface object, where the type of the target identifier is different from the type of the temporary identifier;

[0097] The target identifier is the target identifier ultimately required for communication between the SC and the OMC, generated by the OMC, and globally unique. Optionally, the target identifier is a resource management global identifier (rmUID).

[0098] Step 63: Send response information to the SC, wherein the response information includes a mapping relationship between the target identifier and the temporary identifier of the target first interface object.

[0099] In the embodiment of the present invention, optionally, the request information is service creation request information or tunnel creation request information; and the response information is service creation result information or tunnel creation result information.

[0100] That is, the SC can obtain the target identifier of the service or tunnel in the process of requesting the OMC to create the service or tunnel, so that a separate acquisition process is not required, thereby saving implementation costs.

[0101] The following takes the method for generating a service rmUID during service creation as an example to illustrate the method of the embodiment of the present invention.

[0102] Please refer to Figure 7 , the generation methods of rmUID include:

[0103] Step 71: OMC records a northbound interface object information table, wherein the northbound interface object information table records information of all northbound interface objects for which rmUIDs need to be generated by OMC;

[0104] Step 72: The SC sends a service creation request message to the OMC through the northbound interface. The service creation request message includes the UUID of the target service. The UUID is generated by the SC based on the UUID rule in RFC4122 to ensure that the ID is unique in the entire network. The UUID does not need to be stored in the database, but only in the memory.

[0105] Optionally, the service creation request information may further include at least one of the following: service type, protection type, service access point network element and interface information, service bandwidth, VLAN ID and other information.

[0106] Step 73: After receiving the service creation request information, the OMC determines whether the target service is recorded in the northbound interface object information table. If so, the target service is determined to be a northbound interface object for which the OMC needs to generate an rmUID. The OMC generates the rmUID of the target service based on the rmUID generation rule to ensure that the rmUID of the target service is globally unique.

[0107] Step 74: The OMC interacts with the forwarding layer device to create the service based on the service creation request issued by the SC;

[0108] Step 75: OMC receives the service creation result returned by the forwarding layer device;

[0109] Step 76: OMC sends service creation result information to SC, where the service creation result information includes a mapping relationship between the UUID and rmUID of the target service and a service creation success flag;

[0110] Step 77: After the SC receives the service creation success identifier reported by the OMC, based on the mapping relationship between the UUID and rmUID of the target service reported by the OMC, it replaces the UUID of the target service with rmUID, uses the rmUID as the unique identifier of the target service, and stores it in the database.

[0111] Step 78: The SC performs subsequent business operations based on the rmUID stored in the database as the unique identifier of the target business.

[0112] Please refer to Figure 8 The embodiment of the present invention further provides a first network element 80, including:

[0113] A sending module 81, configured to send a request message to a second network element through a first interface, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0114] A receiving module 82 is configured to receive a response message sent by the second network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, wherein 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;

[0115] The replacement module 83 is used to replace the temporary identifier of the target first interface object with the target identifier, and store the target identifier in a database.

[0116] 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.

[0117] Optionally, the target first interface object is a service or tunnel that needs to be created by the super controller.

[0118] Optionally, the request information is service creation request information or tunnel creation request information;

[0119] The response information is service creation result information or tunnel creation result information.

[0120] Optionally, the temporary identifier is a universal unique identification code.

[0121] Optionally, the target identifier is a resource management global identifier.

[0122] Please refer to Fig. 9 The embodiment of the present invention further provides a second network element 90, including:

[0123] A receiving module 91, configured to receive a request message sent by a first network element through a first interface, wherein the request message includes a temporary identifier of a target first interface object, and the temporary identifier is generated by the first network element;

[0124] A generating module 92 is 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, wherein the type of the target identifier is different from the type of the temporary identifier;

[0125] The sending module 93 is used to send response information to the first network element, where the response information includes a mapping relationship between the target identifier and the temporary identifier of the target first interface object.

[0126] Optionally, the second network element 90 further includes:

[0127] A recording module, used to record a first interface object information table, wherein the first interface object information table records information of all first interface objects for which a target identifier needs to be generated by the second network element;

[0128] The judgment module is used to judge whether the target first interface object is recorded in the first interface object information table. If so, it is determined that the target first interface object is a first interface object that needs to generate a target identifier by the second network element.

[0129] 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.

[0130] Optionally, the target first interface object is a service or tunnel that needs to be created by the super controller.

[0131] Optionally, the request information is service creation request information or tunnel creation request information;

[0132] The response information is service creation result information or tunnel creation result information.

[0133] Optionally, the temporary identifier is a universal unique identification code.

[0134] Optionally, the target identifier is a resource management global identifier.

[0135] Please refer to Fig.10 An embodiment of the present invention further provides a first network element 100, including a processor 101, a memory 102, and a computer program stored in the memory 102 and executable on the processor 101. When the computer program is executed by the processor 101, the various processes of the embodiment of the method for generating an interface object identifier applied to the first network element are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0136] Please refer to Fig.11 An embodiment of the present invention further provides a first network element 110, including a processor 111, a memory 112, and a computer program stored in the memory 112 and executable on the processor 111. When the computer program is executed by the processor 111, each process of the embodiment of the method for generating an interface object identifier applied to the second network element is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0137] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned embodiment of the method for generating an interface object identifier applied to the first network element are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0138] An embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned embodiment of the method for generating an interface object identifier applied to a second network element are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0139] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0140] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0141] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0142] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A method for generating an interface object identifier, applied to a first network element, characterized in that: include: Sending a request message to the second network element through the first interface, wherein the request message includes a temporary identifier of the target first interface object, and the temporary identifier is generated by the first network element; receiving a response message sent by the second network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, wherein 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; Replacing the temporary identifier of the target first interface object with the target identifier, and storing the target identifier in a database; 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; The target first interface object is a service or tunnel that needs to be created by the super controller.

2. The method according to claim 1, characterized in that 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.

3. The method according to any one of claims 1 to 2, characterized in that: The temporary identifier is a universal unique identification code.

4. The method according to any one of claims 1 to 2, characterized in that: The target identifier is a resource management global identifier.

5. A method for generating an interface object identifier, applied to a second network element, characterized in that: include: Receiving, through the first interface, a request message sent by the first network element, wherein the request message includes 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 for which a target identifier needs to be generated by the second network element, a target identifier of the target first interface object is generated, and a type of the target identifier is different from a type of the temporary identifier; Sending a response message to the first network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier; 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; The target first interface object is a service or tunnel that needs to be created by the super controller.

6. The method according to claim 5, characterized in that Also includes: Recording a first interface object information table, wherein the first interface object information table records information of all first interface objects for which a target identifier needs to be generated by the second network element; 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: Determine whether the target first interface object is recorded in the first interface object information table, and if so, determine that the target first interface object is a first interface object that requires the second network element to generate a target identifier.

7. The method according to claim 5, characterized in that 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.

8. The method according to any one of claims 5 to 7, characterized in that: The temporary identifier is a universal unique identification code.

9. The method according to any one of claims 5 to 7, characterized in that: The target identifier is a resource management global identifier.

10. A first network element, characterized in that: include: A sending module, configured to send a request message to a second network element through a first interface, wherein the request message 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 a response message sent by the second network element, wherein the response message includes a mapping relationship between a target identifier of the target first interface object and the temporary identifier, wherein 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; A replacement module, used for replacing the temporary identifier of the target first interface object with the target identifier, and storing the target identifier in a database; 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; The target first interface object is a service or tunnel that needs to be created by the super controller.

11. A second network element, characterized in that: include: A receiving module, configured to receive a request message sent by a first network element through a first interface, wherein the request message 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, wherein a type of the target identifier is different from a type of the temporary identifier; A sending module, configured to send a response message to the first network element, wherein the response message includes a mapping relationship between a target identifier and a temporary identifier of the target first interface object; 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; The target first interface object is a service or tunnel that needs to be created by the super controller.

12. A network element, characterized in that: include: A processor, a memory, and a program stored in 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 as described in any one of claims 1 to 4; or, the program, when executed by the processor, implements the steps of the method for generating an interface object identifier as described in any one of claims 5 to 9.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method for generating an interface object identifier as described in any one of claims 1 to 4; or, when executed by a processor, implements the steps of the method for generating an interface object identifier as described in any one of claims 5 to 9.