WO2017206925A1 - Resource id配置方法及装置 - Google Patents

Resource id配置方法及装置 Download PDF

Info

Publication number
WO2017206925A1
WO2017206925A1 PCT/CN2017/086776 CN2017086776W WO2017206925A1 WO 2017206925 A1 WO2017206925 A1 WO 2017206925A1 CN 2017086776 W CN2017086776 W CN 2017086776W WO 2017206925 A1 WO2017206925 A1 WO 2017206925A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
type
information
defining
upper layer
Prior art date
Application number
PCT/CN2017/086776
Other languages
English (en)
French (fr)
Inventor
涂晓平
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017206925A1 publication Critical patent/WO2017206925A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting

Definitions

  • the present application relates to the field of communications, for example, to a resource identification (RESOURCE ID) configuration method and apparatus.
  • REOURCE ID resource identification
  • SDN 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.
  • URI Uniform Resource Identifier
  • RESOURCE ID is URI
  • the URI syntax is defined by the URI protocol name (eg "http", "ftp", "mailto” or " File"), a colon, and the content of the protocol.
  • URI protocol name eg "http", "ftp", "mailto” or " File”
  • 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.
  • the controller 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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 At least one processor
  • 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 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;
  • 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.
  • the version information is added to the RESOURCE ID.
  • 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.
  • FIG. 1 is a schematic diagram of data flow of a RESOURCE ID in the related art
  • FIG. 2 is a schematic flowchart of a method for configuring a RESOURCE ID according to an embodiment of the present disclosure
  • FIG. 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.
  • 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.
  • the RESOURCE ID configuration method 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • RESOURCE ID 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.
  • 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.
  • 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.
  • 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.
  • the method implementation process of the embodiment of the present disclosure may include:
  • 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.
  • 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.
  • the device 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)
  • the controller 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.
  • the upper application of the controller takes out the value of the RESOURCE ID " ⁇ 1 ⁇ 7 ⁇ 5 ⁇ 2 ⁇ 11 ⁇ 6 ⁇ 3 ⁇ 18".
  • the value of the RESOURCE ID can be parsed.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请公布了一种RESOURCE ID配置方法及装置，所述方法包括：为资源生成RESOURCE ID并下发给设备；接收所述设备上报的RESOURCE ID并转发给上层应用；其中，所述RESOURCE ID包括资源的类型信息和对应的实体信息。减少了交互接口，解决了各种类型资源对应实体结构不同的问题，不需要集中分配RESOURCE ID，有利于应用开发，提高了部署的灵活性，而且能够提升效率。

Description

RESOURCE ID配置方法及装置 技术领域
本申请涉及通信领域，例如涉及一种资源标识(RESOURCE ID)配置方法及装置。
背景技术
软件定义网络(SDN，Software Define Network)是一种新型的网络体系结构，通过将网络控制与网络转发解耦合构建开放可编程的网络体系结构。SDN旨在实现网络互联和网络行为的定义和开放式的接口，从而支持未来各种新型网络体系结构和新型业务的创新。软件定义网络SDN让网络变得更敏捷和灵活，SDN带来的最大价值是节约成本、提高网络性能、提升网络效率，最终使用户能够快速响应不断变化的业务需求。
开放流配置(OF-CONFIG，Open Flow Configuration)协议是由开放式网络架构(ONF，Open Network Foundation)制定的SDN南向接口技术之一，它的本质是提供一个开放接口以远程配置和控制OpenFlow交换机，OpenFlow交换机上所有参与数据转发的软硬件(例如端口、队列等)都可被视为网络资源，而OF-CONFIG的作用就是对这些资源进行管理。目前，在OF-CONFIG1.2中已定义了8种类型资源，对于每个资源都定义了一个通用资源标志符(URI，Uniform Resource Identifier)类型的RESOURCE ID进行唯一标识，方便统一管理。
目前标准的进展只规定了RESOURCE ID的类型为URI，即只要符合URI语法规则(由RFC3986规定)即可，URI语法定义由URI协议名(例如“http”，“ftp”，“mailto”或“file”)、一个冒号、和协议对应的内容构成。特定的协议定义了协议内容的语法和语义，而所有的协议都必须遵循一定的URI文法通用规则，亦即为某些专门目的保留部分特殊字符。RESOURCE ID对应的URI协议名须向单独的标准组织申请，协议对应的内容特殊语法规则暂时没有定义，但URI通用的语法规则定义是所有URI协议都须遵守的。
图1展示了SDN***中相关技术作法的RESOURCE ID数据流向，由图1 可知，当控制器收到RESOURCE ID信息后，必须先向配置点请求解析对应实体的RESOURCE ID，配置点返回对应实体信息给控制器，控制器才能够将相应资源的实体信息向上层应用上报。
由于目前没有对RESOURCE ID的内容进行规定，一般的作法是将其定义一个无意义字符串ID，并在配置点建立一个与对应实体关联表，这种做法的问题是：每个收到RESOURCE ID的上层应用都需要向配置点请求相对应的实体信息，流程复杂，不同设备厂商互连互通较困难，并且为了保证唯一性此作法使得RESOURCE ID只能由配置点中的一个模块集中统一分配，多个上层应用请求时必然出现信息拥堵、效率低的问题。
发明内容
为了解决上述技术问题，本公开实施例提供了一种RESOURCE ID配置方法及装置。
本公开提供了一种RESOURCE ID配置方法，包括：为资源生成RESOURCE ID并下发给设备；接收所述设备上报的RESOURCE ID并转发给上层应用；其中，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
其中，所述为资源生成RESOURCE ID的方法为：配置点为每种资源生成对应的RESOURCE ID；
所述接收所述设备上报的RESOURCE ID的方法为：控制器接收所述设备上报的RESOURCE ID。
其中，为每种资源生成对应的RESOURCE ID之前，还包括：预先定义RESOURCE ID的规范并应用到所述配置点、所述控制器以及所述上层应用，所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
其中，所述配置点为每种资源生成对应的RESOURCE ID，为：所述配置点根据所述RESOURCE ID的规范为每种资源生成对应的RESOURCE ID。
其中，还包括：控制器接收所述设备上报的RESOURCE ID后，还根据所述RESOURCE ID的规范从所述RESOURCE ID解析出实体信息。
其中，还包括：所述上层应用接收所述控制器转发的RESOURCE ID，根据RESOURCE ID的规范从所述RESOURCE ID解析出所述实体信息。
本公开实施例还提供了一种配置点装置，包括：RESOURCE ID分配模块，被配置为为每种资源生成对应的RESOURCE ID并下发给设备，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
其中，所述RESOURCE ID分配模块，可以被配置为在配置点使用预先定义并发布的RESOURCE ID的规范，根据所述RESOURCE ID的规范为每种资源生成对应的RESOURCE ID；
所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
本公开实施例还提供了一种控制器，包括：应用模块，被配置为接收所述设备上报的RESOURCE ID并转发给上层应用，使得所述上层应用从所述RESOURCE ID解析出实体信息；所述RESOURCE ID包括资源的类型信息和对应的实体信息。
其中，应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范；所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
其中，所述应用模块，还被配置为在接收到所述RESOURCE ID后，根据所述RESOURCE ID的规范从所述RESOURCE ID解析出实体信息。
本公开实施例还提供了一种上层应用装置，所述上层应用装置包括上层应用模块，所述上层应用模块被配置为接收控制器转发的RESOURCE ID，所述RESOURCE ID包括资源的类型信息和对应的实体信息；以及，根据RESOURCE ID的规范从所述RESOURCE ID解析出所述实体信息。
其中，所述上层应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范；所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
本公开实施例还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述方法。
本公开实施例还提供了一种电子设备，包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器执行上述的方法。
本公开实施例提供的RESOURCE ID配置方法及装置，至少有以下几个优点：
一、控制器与配置点不再需要交互RESOURCE ID，控制器的上层应用也不需要与配置点交互RESOURCE ID，减少了交互接口；
二、RESOURCE ID中加入了RESOURCE ID类型信息，解决了各种类型资源对应实体结构不同的问题；
三、RESOURCE ID中嵌入了对应的实体信息，该实体信息具有唯一性，可以使得RESOURCE ID在配置点的不同RESOURCE ID分配模块进行资源分配，不需要集中分配，不仅有利于应用开发，提高了部署的灵活性，而且能够提升效率。
四、RESOURCE ID中加入版本信息，在设备升级导致各类资源对应的实体结构发生了变化时，新的实体结构可通过版本号进行识别和重配置。
本公开的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本公开而了解。本公开的其他优点可通过在 说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图概述
附图用来提供对本公开技术方案的理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1为相关技术中RESOURCE ID的数据流向示意图；
图2为本公开实施例RESOURCE ID配置方法的流程示意图；
图3为本公开实施例RESOURCE ID配置的数据流向及架构示意图；以及
图4为本公开实施例的电子设备的结构示意图。
具体实施方式
为使本公开的技术方案和优点更加清楚明白，下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机***中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本公开实施例的RESOURCE ID配置方法，将RESOURCE ID对应的实体信息按照一个简单规则(同时符合URI通用语法)嵌入RESOURCE ID的内容中，并通过公布这个简单通用的规范，上层应用在收到RESOURCE ID后即可根据公布的规范自行解析出相关信息，大大简化了应用流程，也符合SDN开放互通互连的技术发展方向。
如图2所示，本公开实施例提供的RESOURCE ID配置方法，包括：
步骤201，预配置RESOURCE ID的规范：
所述RESOURCE ID的规范至少包括：为OF-CONFIG协议内的各类资源类型定义类型值；根据SDN设备类型，给OF-CONFIG协议内的每种资源类型分 别定义对应实体结构。所述RESOURCE ID的规范还可以包括：定义RESOURCE ID的版本号。如此，在设备升级导致各类资源对应的实体结构发生了变化时，对于新的实体结构时可通过版本号进行识别和重配置。
本公开实施例中，按照URI的语法规则定义RESOURCE ID，定义后的RESOURCE ID包括如下的内容信息：资源的类型信息(目前有8种资源类型)、版本信息以及对应的实体信息(例如端口类型的RESOURCE ID可以包括机架号、子架号、槽位号、端口号等)，这些内容信息可以使用间隔符进行间隔(例如使用URI标准常用间隔符“/”间隔)。在设备出厂配置中包含上述规范，即可在实际交互中实现本公开实施例的RESOURCE ID配置方法，如此，上层应用根据规范即可将RESOURCE ID对应的实体信息解析出来，简化了应用流程。
本步骤中，在配置点、所述控制器以及控制器的上层应用中都配置所述RESOURCE ID的规范。
步骤202，配置点根据上述规范给每种资源生成对应的RESOURCE ID，并下发给设备。
这里，配置点生成的RESOURCE ID至少包括资源的类型信息和对应的实体信息。还可以包含资源的版本信息(如，版本号)。如此，在设备升级导致各类资源对应的实体结构发生了变化时，对于新的实体结构时可通过版本号进行识别和重配置。
步骤203，设备收到RESOURCE ID后先保存，在需要上报RESOURCE ID相关信息时，设备将相关的RESOURCE ID上报给控制器。
步骤204，控制器收到RESOURCE ID后，根据上述规范解析出该RESOURCE ID对应的实体信息。如有需要，继续将RESOURCE ID转发给上层应用。
步骤205，控制器的上层应用收到RESOURCE ID，根据公布的上述规范解析出该RESOURCE ID对应的实体信息。
相应的，本公开实施例还提供了一种配置点装置，包括：RESOURCE ID分配模块，被配置为为每种资源生成对应的RESOURCE ID并下发给设备，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
其中，所述RESOURCE ID分配模块，可以被配置为在配置点使用预先定 义并发布的RESOURCE ID的规范(如配置该规范或将该规范嵌入到***或者将该规范通过其他方式置于其中使得RESOURCE ID分配模块能够使用)，根据所述RESOURCE ID的规范为每种资源生成对应的RESOURCE ID；所述规范的内容与上述方法相关内容的记载相同，不再赘述。
相应的，本公开实施例还提供了一种控制器，包括：应用模块，被配置为接收所述设备上报的RESOURCE ID并转发给上层应用，使得所述上层应用从所述RESOURCE ID解析出实体信息；所述RESOURCE ID包括资源的类型信息和对应的实体信息。
这里，应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范(如配置该规范或将该规范嵌入到***或者将该规范通过其他方式置于其中使得应用模块能够使用)。所述规范和RESOURCE ID的内容与上述方法相关内容的记载相同，不再赘述。
其中，所述应用模块，还可被配置为在接收到所述RESOURCE ID后，根据所述RESOURCE ID的规范从所述RESOURCE ID解析出实体信息。
相应的，本公开实施例还提供了一种控制器的上层应用装置，所述上层应用装置包括上层应用模块，所述上层应用模块被配置为接收控制器转发的RESOURCE ID，所述RESOURCE ID包括资源的类型信息和对应的实体信息；以及，根据RESOURCE ID的规范从所述RESOURCE ID解析出所述实体信息。
其中，所述上层应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范(如配置该规范或将该规范嵌入到***或者将该规范通过其他方式置于其中使得上层应用模块能够使用)；所述规范和RESOURCE ID的内容与上述方法相关内容的记载相同，不再赘述。
本公开实施例中，上层应用装置被配置为提供用户界面，用户可通过上层应用装置对SDN***的网络配置及其他进行个性化配置和管理，该上层应用装置的作用相当于网管，部署在客户端侧，一个上层应用装置可具有多个上述的上层应用模块。控制器和配置点可配置在服务器上，一般来说，控制器和配置点会分开部署在不同的服务器上，实际应用时也可根据需要部署在同一服务器。控制器除具备上述方法涉及的功能外，还可被配置为将上层应用的命令传送给设备层、以及将设备层的相关信息上报给上层应用等。配置点被配置为配置OF-CONFIG协议相关的信息或内容。配置点可以是OF-CONFIG配置点或其他 具有相应功能的配置点。
如图3所示，为本公开实施例SDN***中RESOURCE ID的数据流向以及架构示意图，控制器的应用模块可以是性能上报应用模块、告警应用模块等，只是RESOURCE ID相关应用的一部分。在配置点中仅示出一个RESOURCE ID分配模块作为示意，实际应用中，配置点上可有多个RESOURCE ID分配模块，多个RESOURCE ID分配模块可以分布式架构部署。
如图3所示的架构中，本公开实施例的方法实现过程可包括：
1、定义资源类型的版本号，如初始版本定义为1。
2、给现有各类资源类型(目前OF-CONFIG只定义了八种)定义类型值，依次定义为port、queue、owned-certificate、external-certificate、flow-table、sptn-oam：Ethernet_MEG、sptn-oam：G.8113.1_MEG、sptn-oam：MLP_ProtectionGroup类型为1～8，即port类型值1，sptn-oam：MLP_ProtectionGroup为8，其他类推。
3、为每种类型的资源定义相对应的实体结构，以类型值为7的sptn-oam：G.8113.1_MEG为例，根据某SDN设备实际情况定义其对应的实体结构为：机架地址、设备号/子架号、槽位、端口号、通道号、MEGID号。其他类型的实体结构也类似，定义完成后，将它发布出去，即配置到配置点、控制器和上层应用。
4、配置点的RESOURCE ID管理分配模块根据上述步骤1、2、3定义的规范，给资源分配RESOURCE ID，例如在5号机架、2号子架、11号槽位、6号端口、通道号为3、MEGID为18的RESOURCE ID为：\1\7\5\2\11\6\3\18，并将“\1\7\5\2\11\6\3\18”这个RESOURCE ID下发给设备。
5、设备收到“\1\7\5\2\11\6\3\18”这个RESOURCE ID后，先行保存。当需要上报以“\1\7\5\2\11\6\3\18”这个RESOURCE ID相关信息时(如告警上报)，设备将先前收到“\1\7\5\2\11\6\3\18”这个RESOURCE ID上报给控制器(假如是告警上报，同时上报此RESOURCE ID关联的告警信息)
6、控制器收到包含RESOURCE ID信息后，取出RESOURCE ID的值“\1\7\5\2\11\6\3\18”，先取出版本号1和类型码7，根据发布的信息，知道对应的实体结构为机架地址、设备号/子架号、槽位、端口号、通道号、MEGID号， 并由此可解析出RESOURCE ID对应的实体信息为：5号机架、2号子架、11号槽位、6号端口、通道号为3、MEGID为18。如有需要，控制器继续将“\1\7\5\2\11\6\3\18”这个RESOURCE ID上报给控制器的上层应用。
7、控制器的上层应用收到上述RESOURCE ID后，取出RESOURCE ID的值“\1\7\5\2\11\6\3\18”，和步骤6一样，可以解析出RESOURCE ID的值“\1\7\5\2\11\6\3\18”值对应的实体信息。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本公开不限制于任何特定形式的硬件和软件的结合。
本公开实施例还提供了一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行上述任一实施例中的方法。
本公开实施例还提供了一种电子设备的结构示意图。参见图4，该电子设备包括：
至少一个处理器(processor)40，图4中以一个处理器40为例；和存储器(memory)41，还可以包括通信接口(Communications Interface)42和总线43。其中，处理器40、通信接口42、存储器41可以通过总线43完成相互间的通信。通信接口42可以用于信息传输。处理器40可以调用存储器41中的逻辑指令，以执行上述实施例的方法。
此外，上述的存储器41中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。
存储器41作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序，如本公开实施例中的方法对应的程序指令/模块。处理器40通过运行存储在存储器41中的软件程序、指令以及模块，从而执行功能应用以及数据处 理，即实现上述方法实施例中的RESOURCE ID配置方法。
存储器41可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据终端设备的使用所创建的数据等。此外，存储器41可以包括高速随机存取存储器，还可以包括非易失性存储器。
本公开实施例的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等多种可以存储程序代码的介质，也可以是暂态存储介质。
虽然本公开所揭露的实施方式如上，但所述的内容仅为便于理解本公开而采用的实施方式，并非用以限定本公开。任何本公开所属领域内的技术人员，在不脱离本公开实施例范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本公开的专利保护范围，仍须以所附的权利要求书所界定的范围为准。
工业实用性
本申请提供的RESOURCE ID配置方法及装置，减少了交互接口，解决了各种类型资源对应实体结构不同的问题，不需要集中分配RESOURCE ID，有利于应用开发，提高了部署的灵活性，而且能够提升效率。

Claims (18)

  1. 一种RESOURCE ID配置方法，包括：
    为资源生成资源标识RESOURCE ID并下发给设备；
    接收所述设备上报的RESOURCE ID并转发给上层应用；
    其中，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
  2. 根据权利要求1所述的方法，其中，
    所述为资源生成RESOURCE ID的方法为：配置点为每种资源生成对应的RESOURCE ID；
    所述接收所述设备上报的RESOURCE ID的方法为：控制器接收所述设备上报的RESOURCE ID。
  3. 根据权利要求2所述的方法，其中，为每种资源生成对应的RESOURCE ID之前，还包括：预先定义RESOURCE ID的规范并应用到所述配置点、所述控制器以及所述上层应用，所述规范包括：为开放流配置(OF-CONFIG，Open Flow Configuration)协议内的每种资源类型定义类型值；根据软件定义网络(SDN，Software Define Network)设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
  4. 根据权利要求3所述的方法，其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
  5. 根据权利要求3或4所述的方法，其中，
    所述配置点为每种资源生成对应的RESOURCE ID，为：所述配置点根据所述RESOURCE ID的规范为每种资源生成对应的RESOURCE ID。
  6. 根据权利要求3或4所述的方法，还包括：
    控制器接收所述设备上报的RESOURCE ID后，还根据所述RESOURCE ID 的规范从所述RESOURCE ID解析出实体信息。
  7. 根据权利要求1至6任一项所述的方法，还包括：
    所述上层应用接收转发的RESOURCE ID，根据RESOURCE ID规范从所述RESOURCE ID解析出所述实体信息。
  8. 一种配置点装置，包括：RESOURCE ID分配模块，被配置为为每种资源生成对应的RESOURCE ID并下发给设备，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
  9. 根据权利要求8所述的装置，其中，
    所述RESOURCE ID分配模块，被配置为在配置点使用预先定义并发布的RESOURCE ID的规范，根据所述RESOURCE ID的规范为每种资源生成对应的RESOURCE ID；
    所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
  10. 根据权利要求9所述的装置，其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
  11. 一种控制器，包括：应用模块，被配置为接收设备上报的RESOURCE ID并转发给上层应用，使得所述上层应用从所述RESOURCE ID解析出实体信息；其中，所述RESOURCE ID包括资源的类型信息和对应的实体信息。
  12. 根据权利要求11所述的控制器，其中，所述应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范；
    所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
  13. 根据权利要求12所述的装置，其中，所述规范还包括：定义RESOURCE  ID的版本号；所述RESOURCE ID还包括资源的版本信息。
  14. 根据权利要求11至13任一项所述的装置，其中，所述应用模块，还被配置为在接收到所述RESOURCE ID后，根据所述RESOURCE ID的规范从所述RESOURCE ID解析出实体信息。
  15. 一种上层应用装置，所述上层应用装置包括上层应用模块，所述上层应用模块被配置为接收控制器转发的RESOURCE ID，所述RESOURCE ID包括资源的类型信息和对应的实体信息；以及，根据RESOURCE ID的规范从所述RESOURCE ID解析出所述实体信息。
  16. 根据权利要求15所述的装置，其中，所述上层应用模块，还被配置为使用预先定义并发布的RESOURCE ID的规范；所述规范包括：为OF-CONFIG协议内的每种资源类型定义类型值；根据SDN设备类型给OF-CONFIG协议内的每种资源类型分别定义对应实体结构。
  17. 根据权利要求16所述的装置，其中，所述规范还包括：定义RESOURCE ID的版本号；所述RESOURCE ID还包括资源的版本信息。
  18. 一种非暂态计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为执行权利要求1-7中任一项的方法。
PCT/CN2017/086776 2016-06-01 2017-06-01 Resource id配置方法及装置 WO2017206925A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610383859.4A CN107453892A (zh) 2016-06-01 2016-06-01 Resource id配置方法及装置
CN201610383859.4 2016-06-01

Publications (1)

Publication Number Publication Date
WO2017206925A1 true WO2017206925A1 (zh) 2017-12-07

Family

ID=60478000

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/086776 WO2017206925A1 (zh) 2016-06-01 2017-06-01 Resource id配置方法及装置

Country Status (2)

Country Link
CN (1) CN107453892A (zh)
WO (1) WO2017206925A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108322329A (zh) * 2017-12-25 2018-07-24 深圳市泰信通信息技术有限公司 基于sdn网络的下发网络配置方法、装置及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655892A (zh) * 2009-09-22 2010-02-24 成都市华为赛门铁克科技有限公司 一种移动终端和访问控制方法
CN103338163A (zh) * 2013-07-16 2013-10-02 清华大学 支持动态弹性资源调度的软件定义网络控制器
WO2015018436A1 (en) * 2013-08-06 2015-02-12 Nec Europe Ltd. Method for operating a network and a network
US20160036601A1 (en) * 2014-08-03 2016-02-04 Oliver Solutions Ltd. Virtualization method for an access network system and its management architecture
CN105516116A (zh) * 2015-12-02 2016-04-20 浙江工商大学 一种基于ForCES控制件控制OpenFlow交换机的***及协议转换方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655892A (zh) * 2009-09-22 2010-02-24 成都市华为赛门铁克科技有限公司 一种移动终端和访问控制方法
CN103338163A (zh) * 2013-07-16 2013-10-02 清华大学 支持动态弹性资源调度的软件定义网络控制器
WO2015018436A1 (en) * 2013-08-06 2015-02-12 Nec Europe Ltd. Method for operating a network and a network
US20160036601A1 (en) * 2014-08-03 2016-02-04 Oliver Solutions Ltd. Virtualization method for an access network system and its management architecture
CN105516116A (zh) * 2015-12-02 2016-04-20 浙江工商大学 一种基于ForCES控制件控制OpenFlow交换机的***及协议转换方法

Also Published As

Publication number Publication date
CN107453892A (zh) 2017-12-08

Similar Documents

Publication Publication Date Title
EP3432517B1 (en) Device configuration method and apparatus based on network configuration protocol
US9565135B2 (en) System and method for service chaining with tunnel chains in software defined network
US10541877B2 (en) Dynamic reservation protocol for 5G network slicing
US11487690B2 (en) Universal host and non-volatile memory express storage domain discovery for non-volatile memory express over fabrics
US10034222B2 (en) System and method for mapping a service-level topology to a service-specific data plane logical topology
EP3905598B1 (en) Message processing method and apparatus, control plane device, and computer storage medium
CN107733799B (zh) 一种报文传输方法和装置
EP3143511B1 (en) Method and apparatus for affinity-based network configuration
US20180063879A1 (en) Apparatus and method for interoperation between internet-of-things devices
CN115296993B (zh) 用于互连多域网络分片控制和管理的***、功能和接口
WO2017198003A1 (zh) 一种业务处理方法及***
JP6419947B2 (ja) 光ネットワークユニットｐｔｐサービスをリモート設定する方法、装置、及びシステム
US11656897B2 (en) Apparatus and method for network function virtualization in wireless communication system
US20220394010A1 (en) Method, Apparatus, and System for Sending Control Request Based on Key Value Configuration
CN111865662B (zh) 网络设备配置方法及***
CN104243198B (zh) 一种基于网络配置协议的网络管理方法和***
WO2017206925A1 (zh) Resource id配置方法及装置
CN104780229A (zh) 通过云终端设置云服务器ip地址的方法、***和云***
CN108989157B (zh) 用于智能设备控制的方法、装置
US8924520B2 (en) Method, remote access server and system for configuring a quality of service parameter
KR20190066743A (ko) 소프트웨어 정의 네트워킹 기반의 멀티 프로토콜 지원 네트워크 가상화 시스템 및 네트워크 가상화 장치의 동작 방법
WO2018145267A1 (zh) 一种转发器入网识别方法、sdn控制器及转发器
WO2017211277A1 (zh) 光网络单元onu的配置方法及装置
KR20150088462A (ko) 클라우드 환경에서 네트워크 장치의 연동 방법 및 장치
WO2018121715A1 (zh) 网络资源配置的管控方法、装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17805870

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17805870

Country of ref document: EP

Kind code of ref document: A1