WO2017206925A1 - Resource id configuration method and device - Google Patents

Abstract

Discloses in the present application are a RESOURCE ID configuration method and device, the method comprising: generating a RESOURCE ID for a resource, and issuing the same to a device; receiving the RESOURCE ID reported by the device and forwarding the same to an upper application. The RESOURCE ID includes type information of the resource and corresponding entity information. The present invention may reduce the number of interactive interfaces, solving the problem wherein various types of resources correspond to different entity structures, which removes the need to centrally allocate RESOURCE IDs. The present invention is beneficial for the development of applications, improves deployment flexibility as well as efficiency.

Description

RESOURCE ID configuration method and device Technical field

The present application relates to the field of communications, for example, to a resource identification (RESOURCE ID) configuration method and apparatus.

Background technique

Software Defined Network (SDN) is a new type of network architecture that constructs an open and programmable network architecture by decoupling network control from network forwarding. SDN aims to define the network interconnection and network behavior and open interfaces to support future innovations in various new network architectures and new services. Software-defined network SDN makes the network more agile and flexible. The biggest value brought by SDN is cost savings, improved network performance, improved network efficiency, and ultimately enabling users to respond quickly to changing business needs.

The Open Flow Configuration (OF-CONFIG) protocol is one of the SDN southbound interface technologies developed by the Open Network Foundation (ONF). Its essence is to provide an open interface for remote configuration and control of OpenFlow. All hardware and software (such as ports, queues, etc.) involved in data forwarding on the switch and OpenFlow switch can be regarded as network resources, and the role of OF-CONFIG is to manage these resources. At present, eight types of resources have been defined in the OF-CONFIG 1.2. A RESOURCE ID of a URI (Uniform Resource Identifier) type is uniquely identified for each resource to facilitate unified management.

The current standard progress only specifies that the type of RESOURCE ID is URI, that is, as long as the URI syntax rules (as specified by RFC3986) are met, the URI syntax is defined by the URI protocol name (eg "http", "ftp", "mailto" or " File"), a colon, and the content of the protocol. A specific protocol defines the syntax and semantics of the protocol content, and all protocols must follow certain URI grammar general rules, that is, retain some special characters for some special purposes. The URI protocol name corresponding to the RESOURCE ID must be applied to a separate standard organization. The content-specific grammar rules of the protocol are not defined at present, but the grammar rule definition common to URIs is subject to all URI protocols.

Figure 1 shows the flow of RESOURCE ID data in related technical practices in the SDN system. Figure 1 It can be seen that, after receiving the RESOURCE ID information, the controller must first request the configuration point to resolve the RESOURCE ID of the corresponding entity, and the configuration point returns the corresponding entity information to the controller, so that the controller can report the entity information of the corresponding resource to the upper layer.

Since the content of the RESOURCE ID is not currently specified, the general practice is to define a meaningless string ID and establish a table associated with the corresponding entity at the configuration point. The problem with this approach is that each RESOURCE ID is received. The upper-layer application needs to request the corresponding entity information from the configuration point. The process is complicated, and the interconnection and intercommunication of different device vendors is difficult. In order to ensure the uniqueness, the RESOURCE ID can only be uniformly distributed by one module in the configuration point. When multiple upper-layer application requests, information congestion and low efficiency are inevitable.

Summary of the invention

In order to solve the above technical problem, an embodiment of the present disclosure provides a RESOURCE ID configuration method and apparatus.

The present disclosure provides a RESOURCE ID configuration method, including: generating a RESOURCE ID for a resource and delivering it to a device; receiving a RESOURCE ID reported by the device and forwarding the RESOURCE ID to an upper layer application; wherein the RESOURCE ID includes resource type information and Corresponding entity information.

The method for generating a RESOURCE ID for a resource is: a configuration point generates a corresponding RESOURCE ID for each resource;

The method for receiving the RESOURCE ID reported by the device is: the controller receives the RESOURCE ID reported by the device.

Before generating a corresponding RESOURCE ID for each resource, the method further includes: pre-defining a specification of the RESOURCE ID and applying to the configuration point, the controller, and the upper-layer application, where the specification includes: being an OF-CONFIG protocol Each type of resource within the definition defines a type value; according to the SDN device type, a corresponding entity structure is defined for each resource type in the OF-CONFIG protocol.

The specification further includes: defining a version number of the RESOURCE ID; and the RESOURCE ID further includes version information of the resource.

The configuration point generates a corresponding RESOURCE ID for each resource, and the configuration point generates a corresponding RESOURCE ID for each resource according to the specification of the RESOURCE ID.

The method further includes: after receiving the RESOURCE ID reported by the device, the controller further parses the entity information from the RESOURCE ID according to the specification of the RESOURCE ID.

The method further includes: the upper layer application receives the RESOURCE ID forwarded by the controller, and parses the entity information from the RESOURCE ID according to the specification of the RESOURCE ID.

The embodiment of the present disclosure further provides a configuration point device, including: a RESOURCE ID allocation module, configured to generate a corresponding RESOURCE ID for each resource and send the information to the device, where the RESOURCE ID includes resource type information and corresponding Entity information.

The RESOURCE ID allocation module may be configured to use a pre-defined and published RESOURCE ID specification at the configuration point, and generate a corresponding RESOURCE ID for each resource according to the RESOURCE ID specification;

The specification includes: defining a type value for each resource type in the OF-CONFIG protocol; and respectively defining a corresponding entity structure for each resource type in the OF-CONFIG protocol according to the SDN device type.

The specification further includes: defining a version number of the RESOURCE ID; and the RESOURCE ID further includes version information of the resource.

The embodiment of the present disclosure further provides a controller, including: an application module, configured to receive a RESOURCE ID reported by the device and forward the message to the upper layer application, so that the upper layer application parses the entity information from the RESOURCE ID; The RESOURCE ID includes type information of the resource and corresponding entity information.

The application module is further configured to use a pre-defined and published RESOURCE ID specification; the specification includes: defining a type value for each resource type in the OF-CONFIG protocol; and in the OF-CONFIG protocol according to the SDN device type Each resource type defines a corresponding entity structure.

The specification further includes: defining a version number of the RESOURCE ID; and the RESOURCE ID further includes version information of the resource.

The application module is further configured to parse the entity information from the RESOURCE ID according to the specification of the RESOURCE ID after receiving the RESOURCE ID.

The embodiment of the present disclosure further provides an upper layer application device, where the upper layer application device includes an upper layer application module, and the upper layer application module is configured to receive a RESOURCE ID forwarded by the controller, where the RESOURCE ID includes resource type information and corresponding Entity information; and parsing the entity information from the RESOURCE ID according to the specification of the RESOURCE ID.

The upper application module is further configured to use a pre-defined and published RESOURCE ID specification; the specification includes: defining a type value for each resource type in the OF-CONFIG protocol; and providing an OF-type according to the SDN device type. Each resource type in the CONFIG protocol defines a corresponding entity structure.

The specification further includes: defining a version number of the RESOURCE ID; and the RESOURCE ID further includes version information of the resource.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the above method.

An embodiment of the present disclosure further provides an electronic device, including:

At least one processor;

a memory communicatively coupled to the at least one processor; wherein

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.

The RESOURCE ID configuration method and apparatus provided by the embodiments of the present disclosure have at least the following advantages:

First, the controller and the configuration point no longer need to interact with the RESOURCE ID, and the upper layer application of the controller does not need to interact with the configuration point RESOURCE ID, thereby reducing the interaction interface;

Second, the RESOURCE ID is added with the RESOURCE ID type information, which solves the problem that the physical structure of each type of resource corresponds to different entities;

The corresponding entity information is embedded in the RESOURCE ID. The entity information is unique. The RESOURCE ID can allocate resources to different RESOURCE ID allocation modules at the configuration point. It does not need to be allocated in a centralized manner, which is beneficial to application development and improves deployment. Flexibility and efficiency.

4. The version information is added to the RESOURCE ID. When the device upgrade causes the physical structure corresponding to each resource to change, the new entity structure can be identified and reconfigured by the version number.

Other features and advantages of the present disclosure will be set forth in the description which follows. Other advantages of the present disclosure may be The structures specified in the description, the claims, and the drawings are realized and obtained.

BRIEF abstract

The drawings are intended to provide an understanding of the technical solutions of the present disclosure, and constitute a part of the specification, and the embodiments of the present application are used to explain the technical solutions of the present disclosure, and do not constitute a limitation of the technical solutions of the present disclosure.

1 is a schematic diagram of data flow of a RESOURCE ID in the related art;

2 is a schematic flowchart of a method for configuring a RESOURCE ID according to an embodiment of the present disclosure;

3 is a schematic diagram of data flow and architecture of a RESOURCE ID configuration according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

detailed description

In order to make the technical solutions and advantages of the present disclosure more apparent, the embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

The steps illustrated in the flowchart of the figures may be executed in a computer system such as a set of computer executable instructions. Also, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

The RESOURCE ID configuration method in the embodiment of the present disclosure embeds the entity information corresponding to the RESOURCE ID into the content of the RESOURCE ID according to a simple rule (which also conforms to the URI general syntax), and publishes the simple general specification, and the upper layer application receives the RESOURCE. After the ID, the relevant information can be parsed according to the published specifications, which greatly simplifies the application process and also conforms to the technical development direction of SDN open interworking interconnection.

As shown in FIG. 2, the RESOURCE ID configuration method provided by the embodiment of the present disclosure includes:

Step 201: Pre-configure the specification of the RESOURCE ID:

The specification of the RESOURCE ID includes at least: defining a type value for each type of resource in the OF-CONFIG protocol; and assigning each resource type in the OF-CONFIG protocol according to the SDN device type. Do not define the corresponding entity structure. The specification of the RESOURCE ID may further include: defining a version number of the RESOURCE ID. In this way, when the device upgrade causes the physical structure corresponding to each type of resource to change, the new entity structure can be identified and reconfigured by the version number.

In the embodiment of the present disclosure, the RESOURCE ID is defined according to the grammar rule of the URI, and the defined RESOURCE ID includes the following content information: resource type information (currently having 8 resource types), version information, and corresponding entity information (for example, port type) The RESOURCE ID can include a rack number, a subrack number, a slot number, a port number, etc., and the content information can be separated by a spacer (for example, using the URI standard common spacer "/" interval). The RESOURCE ID configuration method in the embodiment of the present disclosure can be implemented in the actual configuration of the device. The upper layer application can parse the entity information corresponding to the RESOURCE ID according to the specification, which simplifies the application process.

In this step, the specification of the RESOURCE ID is configured in the configuration point, the controller, and the upper layer application of the controller.

Step 202: The configuration point generates a corresponding RESOURCE ID for each resource according to the foregoing specification, and sends the corresponding RESOURCE ID to the device.

Here, the RESOURCE ID generated by the configuration point includes at least the type information of the resource and the corresponding entity information. It can also contain version information (for example, version number) of the resource. In this way, when the device upgrade causes the physical structure corresponding to each type of resource to change, the new entity structure can be identified and reconfigured by the version number.

Step 203: After receiving the RESOURCE ID, the device saves the RESOURCE ID and reports the related RESOURCE ID to the controller.

Step 204: After receiving the RESOURCE ID, the controller parses the entity information corresponding to the RESOURCE ID according to the foregoing specification. If necessary, continue to forward the RESOURCE ID to the upper application.

Step 205: The upper layer application of the controller receives the RESOURCE ID, and parses the entity information corresponding to the RESOURCE ID according to the published specification.

Correspondingly, the embodiment of the present disclosure further provides a configuration point device, including: a RESOURCE ID allocation module, configured to generate a corresponding RESOURCE ID for each resource and send the information to the device, where the RESOURCE ID includes resource type information. And corresponding entity information.

The RESOURCE ID allocation module can be configured to be pre-determined at the configuration point. The specification of the RESOURCE ID issued by the company (such as configuring the specification or embedding the specification into the system or placing the specification in other ways to enable the RESOURCE ID allocation module to be used), according to the specification of the RESOURCE ID for each resource The corresponding RESOURCE ID is generated; the content of the specification is the same as that of the above method, and details are not described herein.

Correspondingly, the embodiment of the present disclosure further provides a controller, including: an application module, configured to receive a RESOURCE ID reported by the device and forward the message to an upper layer application, so that the upper layer application parses the entity from the RESOURCE ID. Information; the RESOURCE ID includes type information of the resource and corresponding entity information.

Here, the application module is also configured to use a specification of a pre-defined and published RESOURCE ID (eg, configuring the specification or embedding the specification into the system or otherwise placing the specification therein to enable the application module to be used). The contents of the specification and the RESOURCE ID are the same as those of the above method, and are not described again.

The application module may be further configured to parse the entity information from the RESOURCE ID according to the specification of the RESOURCE ID after receiving the RESOURCE ID.

Correspondingly, an embodiment of the present disclosure further provides an upper layer application device of the controller, where the upper layer application device includes an upper layer application module, and the upper layer application module is configured to receive a RESOURCE ID forwarded by the controller, where the RESOURCE ID includes Type information of the resource and corresponding entity information; and parsing the entity information from the RESOURCE ID according to the specification of the RESOURCE ID.

The upper application module is further configured to use a pre-defined and published RESOURCE ID specification (such as configuring the specification or embedding the specification into the system or placing the specification in another manner to enable the upper application module to be used. The contents of the specification and the RESOURCE ID are the same as those of the above method, and will not be described again.

In the embodiment of the present disclosure, the upper-layer application device is configured to provide a user interface, and the user can personally configure and manage the network configuration and other functions of the SDN system through the upper-layer application device, where the function of the upper-layer application device is equivalent to the network management and is deployed in the client. On the end side, an upper application device may have a plurality of the above upper application modules. Controllers and configuration points can be configured on the server. Generally, controllers and configuration points are deployed on different servers. In actual applications, they can be deployed on the same server as needed. The controller may be configured to transmit the commands of the upper layer application to the device layer, and report related information of the device layer to the upper layer application, etc., in addition to the functions involved in the foregoing method. The configuration point is configured to configure information or content related to the OF-CONFIG protocol. The configuration point can be an OF-CONFIG configuration point or other A configuration point with corresponding functionality.

As shown in FIG. 3, the data flow direction and architecture diagram of the RESOURCE ID in the SDN system according to the embodiment of the present disclosure, the application module of the controller may be a performance reporting application module, an alarm application module, etc., but only a part of the RESOURCE ID related application. Only one RESOURCE ID allocation module is shown as a schematic in the configuration point. In actual applications, multiple RESOURCE ID allocation modules can be configured at the configuration point, and multiple RESOURCE ID allocation modules can be deployed in a distributed architecture.

In the architecture shown in FIG. 3, the method implementation process of the embodiment of the present disclosure may include:

1. Define the version number of the resource type, as the initial version is defined as 1.

2. Define the type values for the existing resource types (currently only eight are defined for OF-CONFIG), which are defined as port, queue, owned-certificate, external-certificate, flow-table, sptn-oam: Ethernet_MEG, sptn. -oam: G.8113.1_MEG, sptn-oam: The MLP_ProtectionGroup type is 1 to 8, that is, the port type value is 1, the sptn-oam: MLP_ProtectionGroup is 8, and so on.

3. Define the corresponding entity structure for each type of resource. Take the sptn-oam: G.8113.1_MEG with the value of 7 as an example. Define the corresponding entity structure according to the actual situation of an SDN device: rack address, Device number/subrack number, slot number, port number, channel number, MEGID number. Other types of entity structures are similar. Once the definition is complete, it is published, that is, configured to the configuration point, controller, and upper-layer application.

4. The RESOURCE ID management allocation module of the configuration point allocates a RESOURCE ID to the resource according to the specifications defined in the above steps 1, 2, and 3, for example, in the rack No. 5, subrack No. 2, slot No. 11, port 6, and channel. The RESOURCE ID with the number 3 and the MEGID of 18 is: \1\7\5\2\11\6\3\18, and "\1\7\5\2\11\6\3\18" The RESOURCE ID is sent to the device.

5. After the device receives the RESOURCE ID of "\1\7\5\2\11\6\3\18", it will be saved first. When you need to report the RESOURCE ID related information such as "\1\7\5\2\11\6\3\18" (such as alarm reporting), the device will receive "\1\7\5\2\11". \6\3\18" This RESOURCE ID is reported to the controller (if it is an alarm report, the alarm information associated with this RESOURCE ID is also reported)

6. After receiving the RESOURCE ID information, the controller takes out the value of the RESOURCE ID "\1\7\5\2\11\6\3\18", first removes the version number 1 and the type code 7, according to the published information. , know that the corresponding entity structure is the rack address, device number/subrack number, slot number, port number, channel number, MEGID number, Therefore, the entity information corresponding to the RESOURCE ID can be parsed as: rack 5, subrack 2, slot 11 and port 6, port number 3, MEGID 18. If necessary, the controller will continue to report the RESOURCE ID of "\1\7\5\2\11\6\3\18" to the upper application of the controller.

7. After receiving the RESOURCE ID, the upper application of the controller takes out the value of the RESOURCE ID "\1\7\5\2\11\6\3\18". As in step 6, the value of the RESOURCE ID can be parsed. The entity information corresponding to the value of "\1\7\5\2\11\6\3\18".

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware or in the form of a software function module. The present disclosure is not limited to any specific form of combination of hardware and software.

Embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of the above embodiments.

The embodiment of the present disclosure further provides a schematic structural diagram of an electronic device. Referring to FIG. 4, the electronic device includes:

At least one processor 40, which is exemplified by a processor 40 in FIG. 4; and a memory 41, may further include a communication interface 42 and a bus 43. The processor 40, the communication interface 42, and the memory 41 can complete communication with each other through the bus 43. Communication interface 42 can be used for information transmission. Processor 40 may invoke logic instructions in memory 41 to perform the methods of the above-described embodiments.

In addition, the logic instructions in the memory 41 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.

The memory 41 is used as a computer readable storage medium for storing software programs, computer executable programs, and program instructions/modules corresponding to the methods in the embodiments of the present disclosure. The processor 40 executes the function application and the data portion by running software programs, instructions, and modules stored in the memory 41. The RESOURCE ID configuration method in the foregoing method embodiment is implemented.

The memory 41 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to use of the terminal device, and the like. Further, the memory 41 may include a high speed random access memory, and may also include a nonvolatile memory.

The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in the embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like. A medium that can store program code, or a transitory storage medium.

The embodiments disclosed in the present disclosure are as described above, but are merely used to facilitate the understanding of the present disclosure, and are not intended to limit the present disclosure. Any modification and variation in the form and details of the embodiments may be made by those skilled in the art without departing from the scope of the embodiments of the present disclosure. The scope defined by the claims is subject to.

Industrial applicability

The RESOURCE ID configuration method and device provided by the application reduce the interaction interface, solve the problem that different types of resources correspond to different entity structures, do not need to centrally allocate RESOURCE ID, are beneficial to application development, improve deployment flexibility, and can Improve efficiency.

Claims (18)

A RESOURCE ID configuration method, including: Generate a resource identifier RESOURCE ID for the resource and send it to the device. Receiving the RESOURCE ID reported by the device and forwarding the RESOURCE ID to the upper layer application; The RESOURCE ID includes type information of the resource and corresponding entity information. The method of claim 1 wherein The method for generating a RESOURCE ID for a resource is: a configuration point generates a corresponding RESOURCE ID for each resource; The method for receiving the RESOURCE ID reported by the device is: the controller receives the RESOURCE ID reported by the device. The method of claim 2, wherein before generating a corresponding RESOURCE ID for each resource, the method further comprises: pre-defining a specification of the RESOURCE ID and applying to the configuration point, the controller, and the upper layer application, The specification includes: defining a type value for each resource type in the Open Flow Configuration (OF-CONFIG) protocol; each type in the OF-CONFIG protocol according to a Software Defined Network (SDN) device type The resource type defines the corresponding entity structure. The method of claim 3, wherein the specification further comprises: defining a version number of the RESOURCE ID; the RESOURCE ID further comprising version information of the resource. The method according to claim 3 or 4, wherein The configuration point generates a corresponding RESOURCE ID for each resource, and the configuration point generates a corresponding RESOURCE ID for each resource according to the specification of the RESOURCE ID. The method of claim 3 or 4, further comprising: After receiving the RESOURCE ID reported by the device, the controller further performs the RESOURCE ID according to the RESOURCE ID. The specification parses the entity information from the RESOURCE ID. A method according to any one of claims 1 to 6, further comprising: The upper layer application receives the forwarded RESOURCE ID, and parses the entity information from the RESOURCE ID according to the RESOURCE ID specification. A configuration point device, comprising: a RESOURCE ID allocation module, configured to generate a corresponding RESOURCE ID for each resource and send the information to the device, where the RESOURCE ID includes resource type information and corresponding entity information. The device according to claim 8, wherein The RESOURCE ID allocation module is configured to use a pre-defined and published RESOURCE ID specification at a configuration point, and generate a corresponding RESOURCE ID for each resource according to the specification of the RESOURCE ID; The specification includes: defining a type value for each resource type in the OF-CONFIG protocol; and respectively defining a corresponding entity structure for each resource type in the OF-CONFIG protocol according to the SDN device type. The apparatus according to claim 9, wherein the specification further comprises: defining a version number of the RESOURCE ID; and the RESOURCE ID further includes version information of the resource. A controller, comprising: an application module, configured to receive a RESOURCE ID reported by the device and forward it to an upper layer application, so that the upper layer application parses the entity information from the RESOURCE ID; wherein the RESOURCE ID includes a resource type Information and corresponding entity information. The controller of claim 11, wherein the application module is further configured to use a specification of a pre-defined and published RESOURCE ID; The specification includes: defining a type value for each resource type in the OF-CONFIG protocol; and respectively defining a corresponding entity structure for each resource type in the OF-CONFIG protocol according to the SDN device type. The apparatus of claim 12 wherein said specification further comprises: defining RESOURCE The version number of the ID; the RESOURCE ID also includes version information of the resource. The device according to any one of claims 11 to 13, wherein the application module is further configured to parse the entity information from the RESOURCE ID according to the specification of the RESOURCE ID after receiving the RESOURCE ID. . An upper layer application device, the upper layer application device includes an upper layer application module, the upper layer application module is configured to receive a RESOURCE ID forwarded by a controller, where the RESOURCE ID includes resource type information and corresponding entity information; and, according to The specification of the RESOURCE ID parses the entity information from the RESOURCE ID. The apparatus of claim 15, wherein the upper application module is further configured to use a specification of a pre-defined and published RESOURCE ID; the specification comprising: defining a type for each resource type within the OF-CONFIG protocol Value; the corresponding entity structure is defined for each resource type in the OF-CONFIG protocol according to the SDN device type. The apparatus of claim 16, wherein the specification further comprises: defining a version number of the RESOURCE ID; the RESOURCE ID further comprising version information of the resource. A non-transitory computer readable storage medium storing computer executable instructions arranged to perform the method of any of claims 1-7.

Images