(19)
(11)EP 3 131 241 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
25.03.2020 Bulletin 2020/13

(21)Application number: 15785280.7

(22)Date of filing:  15.04.2015
(51)International Patent Classification (IPC): 
G06F 13/42(2006.01)
G06F 13/40(2006.01)
(86)International application number:
PCT/CN2015/076666
(87)International publication number:
WO 2015/165329 (05.11.2015 Gazette  2015/44)

(54)

CONTROL METHOD AND CONTROL DEVICE

STEUERUNGSVERFAHREN UND STEUERUNGSVORRICHTUNG

PROCÉDÉ ET DISPOSITIF DE COMMANDE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 30.04.2014 CN 201410181775

(43)Date of publication of application:
15.02.2017 Bulletin 2017/07

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventors:
  • MA, Jiuyue
    Beijing 100190 (CN)
  • BAO, Yungang
    Beijing 100190 (CN)
  • REN, Rui
    Beijing 100190 (CN)
  • SUI, Xiufeng
    Beijing 100190 (CN)

(74)Representative: Körber, Martin Hans 
Mitscherlich PartmbB Patent- und Rechtsanwälte Sonnenstrasse 33
80331 München
80331 München (DE)


(56)References cited: : 
WO-A1-2008/074212
CN-A- 101 593 120
CN-A- 103 235 741
US-A- 5 991 824
US-A1- 2009 083 760
CN-A- 101 046 749
CN-A- 102 467 409
JP-A- H05 134 877
US-A1- 2003 196 003
US-B2- 7 343 442
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    TECHNICAL FIELD



    [0001] Embodiments of the present invention relate to computer technologies, and in particular, to a control method and a control device.

    BACKGROUND



    [0002] An input/output (I/O for short) chipset is an important component in a computer system, and its basic function is to connect a central processing unit (CPU for short) and an I/O device. The input/output chipset is a data path between the CPU and the I/O device. In the prior art, the I/O chipset includes a quick path interconnect (QPI for short) bus interface connected to a CPU, a peripheral component interconnect express (PCIE for short) bus interface connected to an I/O device, and some other functional modules, for example, a functional module that implements an encryption function. However, functions implemented by the QPI interface, the PCIE interface, and the some other functional modules are built into the chipset. That is, once an I/O chipset is manufactured, its functions cannot be modified. Therefore, the I/O chipset cannot be flexibly implemented.

    [0003] US 2009/0083760 A1 discloses a computer system capable of routing a Vendor Defined Message (VDM) from one device to another device. The routing is done by means of a VDM Filter and Router component that receives any VDM sent to a Root Complex but targeting a Bus Owner, and routes the VDM to the actual device that functions as the Bus Owner.

    [0004] US 5991824 discloses a computer system that allows peer-to-peer input and output. Data transfers from a data source device to a data sink device are handled by a packet-switched router, which implements a data pipe between the data source and the data sink.

    [0005] US 2003/196003 A1 discloses an I/O bus abstraction for a cluster interconnection fabric.

    [0006] JP H05 134877 A discloses a starting system for computer system.

    SUMMARY



    [0007] To resolve the foregoing technical problem in the prior art, embodiments of the present invention provide a control method and a control device.

    [0008] A first aspect of the embodiments of the present invention provides a control method, including:

    receiving, by a router, data sent by a first device to a second device, wherein the data carries an identifier of an I/O device, and wherein the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    determining, by the router, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device;

    sending, by the router, the data to the controller corresponding to the identifier of the I/O device, so that the controller processes the data according to firmware code stored in the controller;

    receiving, by the router, the processed data sent by the controller;

    sending the processed data to a second device; and

    before the determining of controller corresponding to the identifier of the I/O device according to the identifier of the I/O device and correspondences between I/O devices and controllers, modifying the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device.



    [0009] With reference to the first aspect, in a first possible implementation manner, the controller processes the data according to firmware code stored in the controller includes: reading the data from a queue in the controller into a buffer; and invoking the firmware code stored in a memory to process the data in the buffer.

    [0010] With reference to the first possible implementation manner, in a second possible implementation manner, before the determining, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device, the method further includes: establishing a correspondence between the I/O device and the controller according to a functional requirement of the I/O device and a function implemented by the controller.

    [0011] With reference to the first possible implementation manner, in a third possible implementation manner, the method further includes: loading the firmware code into the controller by using a basic input/output system BIOS or an operating system OS.

    [0012] With reference to any possible implementation manner of the first to third possible implementation manners, in a fourth possible implementation manner, the method further includes: modifying the correspondence between the I/O device and the controller according to the functional requirement of the I/O device.

    [0013] A second aspect of the embodiments of the present invention provides a control method, including:

    receiving, by a controller, data from a first device by using a router, and processing the data according to firmware code stored in the controller; and

    sending, by the controller, the processed data to the router, so that the router sends the processed data to a second device; wherein the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    before the processing of the data according to firmware code stored in the controller, modifying the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device.



    [0014] With reference to the second aspect, in a first possible implementation manner, the processing, by the controller, the data according to firmware code stored in the controller includes: reading the data from a queue in the controller into a buffer; and invoking the firmware code stored in a memory to process the data in the buffer.

    [0015] With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, the method further includes: loading the firmware code into the controller by using a basic input/output system BIOS or an operating system OS.

    [0016] A third aspect of the embodiments of the present invention provides a control device, including:

    a router and at least two controllers, wherein the router is configured to:

    receive data sent by a first device, where the data carries an identifier of an I/O device, and wherein the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    determine, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller, of the at least two controllers, corresponding to the identifier of the I/O device; and

    sending the data to the controller corresponding to the identifier of the I/O device;

    wherein the controller further comprises:

    a controller programming interface, configured to modify the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device, before the router determines the controller corresponding to the identifier of the I/O device according to the identifier of the I/O device and correspondences between I/O devices and controllers;

    the controller corresponding to the identifier of the I/O device is configured to process the data according to firmware code stored in the controller, so as to obtain the processed data; and send the processed data to the router;

    the router is further configured to send the processed data to a second device.



    [0017] With reference to the third aspect, in a first possible implementation manner, the controller includes: a memory, configured to store the firmware code; a buffer, configured to store the data that is read from a queue in the controller by a processor; and the processor, configured to invoke the firmware code stored in the memory to process the data in the buffer, so as to obtain the processed data; and send the processed data to the router.

    [0018] With reference to the third aspect or the first possible implementation manner, in a second possible implementation manner, the router is further configured to establish a correspondence between the I/O device and a controller according to a functional requirement of the I/O device and functions implemented by the at least two controllers.

    [0019] With reference to the third aspect or the first or the second possible implementation manner, in a third possible implementation manner, the controller is further configured to receive the firmware code loaded by a basic input/output system BIOS or an operating system OS.

    [0020] With reference to the third aspect or any possible implementation manner of the first to third possible implementation manners, in a fourth possible implementation manner, the router further includes: a router programming interface, configured to modify the correspondence between the I/O device and the controller according to the functional requirement of the I/O device.

    [0021] According to the control method and the control device that are provided in the embodiments of the present invention, a router receives data sent by a first device, where the data carries an identifier of an I/O device, determines, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device, and sends the data to the controller corresponding to the identifier of the I/O device, so that the controller processes the data according to firmware code stored in the controller; and the router receives the processed data sent by the controller, and sends the processed data to a second device, where the second device or the first device is the I/O device. In the embodiments of the present invention, the firmware code is generally programmable, and therefore a control device (which may be specifically an I/O chipset) applying the foregoing control method can be relatively flexibly implemented.

    [0022] The invention is set-out in the appended claims.

    BRIEF DESCRIPTION OF DRAWINGS



    [0023] To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.

    FIG. 1 is a schematic structural diagram of an I/O chipset in the prior art;

    FIG. 2 is a schematic flowchart of Embodiment 1 of a control method according to the present invention;

    FIG. 3 is a schematic structural diagram of a controller according to the present invention;

    FIG. 4 is a schematic flowchart of Embodiment 2 of a control method according to the present invention; and

    FIG. 5 is a schematic structural diagram of an embodiment of a control device according to the present invention.


    DESCRIPTION OF EMBODIMENTS



    [0024] The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

    [0025] Generally, a computer includes at least one I/O chipset. For example, a motherboard includes at least one I/O chipset. A major function of the I/O chipset is to forward data communicated between an I/O device and a CPU. FIG. 1 is a schematic structural diagram of an I/O chipset in the prior art. As can be seen in FIG. 1, the I/O chipset includes a CPU bus interface and an I/O bus interface. In an example in FIG. 1, the CPU bus interface is shown as a quick path interconnect (QPI for short) bus interface. The QPI bus interface is only one type of CPU bus interface, and the QPI bus interface is configured to connect a CPU. In the example in FIG. 1, the I/O bus interface is shown as a peripheral component interconnect express (PCIE for short) bus interface connected to a device. The PCIE bus interface is only one type of I/O bus interface, and is configured to connect an I/O device. Certainly, the I/O chipset may further include another interface or functional module (not shown). However, functions implemented by the QPI interface, the PCIE interface, and some other functional modules are built into the chipset. Therefore, the I/O chipset cannot be flexibly implemented.

    [0026] An I/O chipset cannot be flexibly implemented by using a solution in the prior art. In the technical solutions in the present invention, a router receives data sent by a first device, and determines, according to an identifier of an I/O device that is carried in the data and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device. The controller stores a piece of firmware code, where the firmware code can be used to implement a function or a group of functions correspondingly, for example, implementing encryption, decryption, compression, bandwidth allocation, and/or like. The router sends the data to the controller corresponding to the identifier of the I/O device; the controller processes the data, and sends the processed data to the router; and the router sends the data processed by the controller to a second device. In the embodiments of the present invention, the first device or the second device is the I/O device. That is, if the first device is a CPU, the second device is the I/O device; or if the first device is the I/O device, the second device is a CPU. In the embodiments of the present invention, the firmware code is generally programmable, and therefore a control device (which may be specifically an I/O chipset) applying the foregoing control method can be relatively flexibly implemented.

    [0027] The following describes in detail the technical solutions in the present invention by using specific embodiments. The following specific embodiments may be combined, and for a same or similar concept or process, details may be not described in some embodiments.

    [0028] FIG. 2 is a schematic flowchart of Embodiment 1 of a control method according to the present invention. As shown in FIG. 2, the method according to this embodiment includes:
    S201: A router receives data sent by a first device.

    [0029] The data sent by the first device carries an identifier of an I/O device.

    [0030] The first device may be a CPU or an I/O device. The data may be data sent by a CPU to an I/O device, or be data sent by an I/O device to a CPU. No matter whether the data is sent by a CPU to an I/O device or sent by an I/O device to a CPU, the data carries the identifier of the I/O device. The identifier of the I/O device may be a name of the I/O device or a number of the I/O device, which is not limited in the present invention, provided that the I/O device can be uniquely identified.

    [0031] S202: Determine, according to an identifier of an I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device.

    [0032] The router stores the correspondences between I/O devices and controllers. One controller can implement one function or a group of functions, for example, implement functions such as encryption, decryption, compression, and/or bandwidth allocation.

    [0033] Generally, the correspondences between I/O devices and controllers are established according to functional requirements of the I/O devices and functions implemented by the controllers. For example, if a functional requirement of an I/O device 1 is that data communicated between the I/O device 1 and the CPU needs to be encrypted, and a function implemented by a controller 1 is an encryption function, a correspondence between the I/O device 1 and the controller 1 is established; if a functional requirement of an I/O device 2 is that data communicated between the I/O device 2 and the CPU needs to be compressed, and a function implemented by a controller 3 is a compression function, a correspondence between the I/O device 2 and the controller 3 is established. A correspondence between another I/O device and a controller may be established in a similar manner, and details are not described herein.

    [0034] When a functional requirement of an I/O device changes, an implementation manner is: When a controller in an I/O chipset can implement a changed functional requirement of the I/O device, a correspondence between the I/O device and the controller is generally modified according to the functional requirement of the I/O device. For example, functions that can be implemented by four current controllers in the I/O chipset are respectively as follows: the controller 1 implements an encryption function, a controller 2 implements a bandwidth allocation function, the controller 3 implements a compression function, and a controller 4 implements a decryption function. The functional requirement of the I/O device 1 changes from an encryption requirement to a compression requirement, and the controller 3 can implement the compression function; therefore, it is only required that the correspondence between the I/O device 1 and the controller 1 be modified to a correspondence between the I/O device 1 and the controller 3.

    [0035] When a functional requirement of an I/O device changes, another implementation manner is: When a controller in an I/O chipset cannot implement a changed functional requirement of the I/O device, firmware code of the controller is generally modified according to the functional requirement of the I/O device. For example, if the functional requirement of the I/O device 1 changes from an encryption requirement to a delay control requirement, the function implemented by the controller 1 may be modified from encryption to delay control. The function implemented by the controller is generally modified by modifying firmware code stored in the controller. A memory in the controller may store different firmware code. A processor in the controller invokes different firmware code to perform processing, so that the controller can implement different functions. In addition, in this embodiment of the present invention, the firmware code is generally programmable, and therefore a control device (which may be specifically an I/O chipset) applying the foregoing control method can be relatively flexibly implemented.

    [0036] When a functional requirement of an I/O device changes, still another implementation manner is: Both a function of a controller and a correspondence between the I/O device and the controller are modified, provided that an established correspondence satisfies that the functional requirement of the I/O device is the same as the function implemented by the controller. Details are not described herein.

    [0037] For the firmware code in the controller, the firmware code is generally loaded into the controller by a basic input/output system (Basic Input/Output System, BIOS for short) or an operating system (Operating System, OS for short) when the system starts. Generally, the correspondences between I/O devices and controllers are established after the firmware code is loaded into the controller; certainly, the correspondences between I/O devices and controllers may be first established, and then corresponding code is loaded into the controller according to the correspondence, which is not limited in the present invention.

    [0038] S203: Send the data to the controller corresponding to the identifier of the I/O device, so that the controller processes the data according to firmware code stored in the controller.

    [0039] The router sends the data to the controller corresponding to the identifier of the I/O device, and the controller processes the data.

    [0040] FIG. 3 is a schematic structural diagram of a controller according to the present invention. As shown in FIG. 3, the controller includes a queue, a buffer, a processor, and a memory. The memory stores firmware code. The queue stores data sent by a router. Referring to FIG. 3, after receiving data communicated between a CPU and an I/O device, the router sends the data to the queue in the controller according to an identifier of the I/O device that is carried in the data; a processor in the controller reads the data from the queue in the controller to the buffer, invokes the firmware code stored in the memory to process the data in the buffer, and returns the processed data to the router.

    [0041] S204: Receive the processed data sent by the controller.

    [0042] After processing the data according to the stored firmware code, the controller returns the data to the router, and the router receives the processed data sent by the controller. S205: Send the processed data to a second device.

    [0043] The router sends the processed data to the second device. In this embodiment, the second device or the first device is the I/O device. That is, if the first device is the CPU, the second device is the I/O device; or if the first device is the I/O device, the second device is the CPU. Whether data is sent by the CPU to the I/O device or data is sent by the I/O device to the CPU, the technical solution in the present invention applies.

    [0044] As can be seen from the description about the foregoing steps, a controller can load different code to implement different functions, that is, a function of the controller is changeable, and a correspondence between an I/O device and a controller that is stored in the router can also be modified as a functional requirement of the I/O device changes. Therefore, an I/O chipset including the foregoing router and controller can implement different functions, and the I/O chipset can be implemented very flexibly.

    [0045] FIG. 4 is a schematic flowchart of Embodiment 2 of a control method according to the present invention. Specifically, the method according to this embodiment is as follows:
    S401: A controller receives data, and processes the data according to firmware code stored in the controller.

    [0046] For a structure of the controller, reference may be made to FIG. 3. Specifically, the controller stores the received data to a queue; a processor in the controller reads the data from the queue in the controller to a buffer, and invokes firmware code stored in a memory to process the data in the buffer.

    [0047] In an application scenario in which a router is included, the controller receives the data from the router. In an application scenario in which no router is included, the controller receives the data from a first device. The first device may be a CPU or an I/O device, where when the first device is the CPU, a second device is the I/O device; when the first device is the I/O device, the second device is the CPU.

    [0048] It should be noted that for the firmware code stored in the controller, the firmware code is generally loaded into the controller by a BIOS or an OS when the system starts. Further, the firmware code of the controller may be modified according to a functional requirement of the I/O device. For information about when and how the firmware code is modified, reference may be made to the detailed description in the embodiment shown in FIG. 2, and details are not described herein.

    [0049] S402: When the data is received from a first device, the controller sends the processed data to a second device; or when the data is received from a first device by using a router, the controller sends the processed data to the router, so that the router sends the processed data to a second device.

    [0050] That is, in a scenario in which no router is included, after processing the data, the controller directly sends the processed data to the second device. In a scenario in which a router is included, after processing the data, the controller returns the processed data to the router, and the router sends the processed data to the second device.

    [0051] In this embodiment of the present invention, a controller receives data, and processes the data according to firmware code stored in the controller. When the data is received from a first device, the controller sends the processed data to a second device; or when the data is received from a first device by using a router, the controller sends the processed data to the router, so that the router sends the processed data to a second device. In this embodiment of the present invention, the firmware code is generally programmable, and therefore a control device (which may be specifically an I/O chipset) applying the foregoing control method can be flexibly implemented.

    [0052] FIG. 5 is a schematic structural diagram of an embodiment of a control device according to the present invention. In this embodiment, the control device is disposed on an I/O chipset in a computer. In terms of structure, the control device in this embodiment includes a router 501 and at least two controllers 502. In FIG. 5, only four controllers are shown. A specific quantity of controllers may be set according to an actual application, which is not limited in the present invention. The router in the control device is configured to receive data sent by a first device, where the data carries an identifier of an I/O device. The router determines, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller that is in the at least two controllers and that is corresponding to the identifier of the I/O device, and sends the data to the controller corresponding to the identifier of the I/O device. The controller corresponding to the identifier of the I/O device processes the data according to firmware code stored in the controller, so as to obtain the processed data; and sends the processed data to the router. The router is further configured to send the processed data to a second device. The second device or the first device is the I/O device.

    [0053] FIG. 3 is a schematic structural diagram of any controller according to the embodiment shown in FIG. 5. Referring to FIG. 3, the controller includes a memory, a buffer, a queue, and a processor, where: the memory is configured to store firmware code, the queue is used to receive data sent by a router, the buffer is used to store data that is read from the queue in the controller by the processor, and the processor is configured to invoke the firmware code stored in the memory to process the data in the buffer, so as to obtain the processed data, and sends the processed data to the router. For a specific workflow of the controller, reference may be made to the detailed description in the method embodiment shown in FIG. 2, and details are not described herein.

    [0054] It should be noted that, in the foregoing embodiments, different controllers may also share a memory to store firmware code, and the processor invokes corresponding firmware code.

    [0055] In the foregoing embodiments, the router is further configured to establish the correspondences between I/O devices and controllers according to functional requirements of the I/O devices and functions implemented by the at least two controllers. For a specific establishment method, reference may be made to the detailed description in the method embodiment shown in FIG. 2, and details are not described herein.

    [0056] In the foregoing embodiments, the controller is further configured to receive firmware code loaded by a BIOS or an OS. For detailed implementation, reference may be made to the detailed description in the method embodiment shown in FIG. 2, and details are not described herein.

    [0057] In the foregoing embodiments, the router further includes a router programming interface, configured to modify a correspondence between an I/O device and a controller according to a functional requirement of the I/O device. For information about when and how the correspondence is modified, reference may be made to the detailed description in the method embodiment shown in FIG. 2, and details are not described herein.

    [0058] In the foregoing embodiments, the controller further includes a controller programming interface, configured to modify the firmware code of the controller according to the functional requirement of the I/O device. For information about when and how the firmware code is modified, reference may be made to the detailed description in the method embodiment shown in FIG. 2, and details are not described herein.

    [0059] According to the control device provided in the present invention, as can be seen from the foregoing description, a controller of the control device can load different firmware code to implement different functions, and a correspondence that is stored in a router of the control device can be modified as a user requirement changes. Therefore, an I/O chipset including the control device can implement different functions according to a requirement, and the I/O chipset can be implemented very flexibly.

    [0060] Persons of ordinary skill in the art may understand that all or some of the steps of the method embodiments may be implemented by a program instructing relevant hardware. The program may be stored in a computer-readable storage medium. When the program runs, the steps of the method embodiments are performed. The foregoing storage medium includes: any medium that can store program code, such as a ROM, a RAM, a magnetic disk, or an optical disc.

    [0061] Finally, it should be noted that the foregoing embodiments are merely intended for describing the technical solutions in the present invention, but not for limiting the present invention. Although the present invention is described in detail with reference to the foregoing embodiments, persons of ordinary skill in the art should understand that they may still make modifications to the technical solutions described in the foregoing embodiments to some or all technical features thereof, without departing from the scope of the technical solutions of the embodiments of the present invention.


    Claims

    1. A control method, comprising:

    receiving, by a router, data sent by a first device to a second device, wherein the data carries an identifier of an I/O device, and wherein the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    determining, by the router, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device;

    sending, by the router, the data to the controller corresponding to the identifier of the I/O device, so that the controller processes the data according to firmware code stored in the controller;

    receiving, by the router, the processed data sent by the controller; and

    sending, by the router, the processed data to the second device;

    before the determining of the controller corresponding to the identifier of the I/O device according to the identifier of the I/O device and correspondences between I/O devices and controllers, modifying the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device.


     
    2. The method according to claim 1, wherein that the controller processes the data according to firmware code stored in the controller comprises:

    reading the data from a queue in the controller into a buffer; and

    invoking the firmware code stored in a memory to process the data in the buffer.


     
    3. The method according to claim 1 or 2, wherein before the determining, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller corresponding to the identifier of the I/O device, the method further comprises:
    establishing a correspondence between the I/O device and the controller according to a functional requirement of the I/O device and a function implemented by the controller.
     
    4. The method according to claim 2, further comprising:
    loading the firmware code into the controller by using a basic input/output system, BIOS, or an operating system, OS.
     
    5. The method according to any one of claims 2 to 4, further comprising:
    modifying the correspondence between the I/O device and the controller according to the functional requirement of the I/O device.
     
    6. A control method, comprising:

    receiving, by a controller, data from a first device by using a router, and processing the data according to firmware code stored in the controller; and

    sending, by the controller, the processed data to the router, so that the router sends the processed data to a second device; wherein

    the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    before the processing of the data according to firmware code stored in the controller, modifying the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device.


     
    7. The method according to claim 6, wherein the processing, by the controller, the data according to firmware code stored in the controller comprises:

    reading the data from a queue in the controller into a buffer; and

    invoking the firmware code stored in a memory to process the data in the buffer.


     
    8. The method according to claim 7, further comprising:
    loading the firmware code into the controller by using a basic input/output system, BIOS, or an operating system, OS.
     
    9. A control device, comprising:

    a router and at least two controllers, wherein

    the router is configured to:

    receive data sent by a first device to a second device, wherein the data carries an identifier of an I/O device,

    wherein the first device is a CPU and the second device is the I/O device, or the first device is the I/O device and the second device is the CPU;

    determine, according to the identifier of the I/O device and correspondences between I/O devices and controllers, a controller, of the at least two controllers, corresponding to the identifier of the I/O device; and sending the data to the controller corresponding to the identifier of the I/O device;

    the controller corresponding to the identifier of the I/O device is configured to process the data according to firmware code stored in the controller, so as to obtain the processed data; and send the processed data to the router;

    the router is further configured to send the processed data to the second device;

    the controller further comprises:
    a controller programming interface, configured to modify the firmware code of the controller according to a functional requirement of the I/O device when changing the functional requirement of the I/O device, before the router determines the controller corresponding to the identifier of the I/O device according to the identifier of the I/O device and correspondences between I/O devices and controllers.


     
    10. The control device according to claim 9, wherein the controller comprises:

    a memory, configured to store the firmware code;

    a buffer, configured to store the data that is read from a queue in the controller by a processor; and

    the processor, configured to invoke the firmware code stored in the memory to process the data in the buffer, so as to obtain the processed data; and send the processed data to the router.


     
    11. The control device according to claim 9 or 10, wherein the router is further configured to establish a correspondence between the I/O device and the controller according to a functional requirement of the I/O device and functions implemented by the at least two controllers.
     
    12. The control device according to any one of claims 9 to 11, wherein the controller is further configured to receive the firmware code loaded by a basic input/output system, BIOS, or an operating system, OS.
     
    13. The control device according to any one of claims 9 to 12, wherein the router further comprises:
    a router programming interface, configured to modify the correspondence between the I/O device and the controller according to the functional requirement of the I/O device.
     


    Ansprüche

    1. Steuerverfahren, umfassend:

    Empfangen, in einem Router, von Daten, die von einer ersten Vorrichtung an eine zweite Vorrichtung gesendet werden, wobei die Daten eine Kennung einer E/A-Vorrichtung mitführen, und wobei die erste Vorrichtung eine CPU ist und die zweite Vorrichtung die E/A-Vorrichtung ist, oder die erste Vorrichtung die E/A-Vorrichtung ist und die zweite Vorrichtung die CPU ist;

    Ermitteln, durch den Router gemäß der Kennung der E/A-Vorrichtung und gemäß Übereinstimmungen zwischen E/A-Vorrichtungen und Steuereinheiten, einer Steuereinheit, die der Kennung der E/A-Vorrichtung entspricht;

    Senden, durch den Router, der Daten an die Steuereinheit, die der Kennung der E/A-Vorrichtung entspricht, sodass die Steuereinheit die Daten gemäß einem Firmwarecode verarbeitet, der in der Steuereinheit gespeichert ist;

    Empfangen der von der Steuereinheit gesendeten verarbeiteten Daten in dem Router; und

    Empfangen der verarbeiteten Daten von dem Router an die zweite Vorrichtung;

    vor dem Ermitteln, dass die Steuereinheit, gemäß der Kennung der E/A-Vorrichtung und gemäß den Übereinstimmungen zwischen den E/A-Vorrichtungen und den Steuereinheiten, der Kennung der E/A-Vorrichtung entspricht, Modifizieren des Firmwarecodes der Steuereinheit gemäß einer funktionellen Anforderung der E/A-Vorrichtung, wenn die funktionelle Anforderung der E/A-Vorrichtung verändert wird.


     
    2. Verfahren nach Anspruch 1, wobei das Verarbeiten der Daten durch die Steuereinheit gemäß dem in der Steuereinheit gespeicherten Firmwarecode umfasst:

    Auslesen der Daten aus einer Warteschlange in der Steuereinheit in einen Pufferspeicher; und

    Aufrufen des in einem Speicher gespeicherten Firmwarecodes, um die Daten in dem Pufferspeicher zu verarbeiten.


     
    3. Verfahren nach Anspruch 1 oder 2, wobei das Verfahren vor dem Ermitteln, gemäß der Kennung der E/A-Vorrichtung und gemäß den Übereinstimmungen zwischen den E/A-Vorrichtungen und den Steuereinheiten, einer Steuereinheit, die der Kennung der E/A-Vorrichtung entspricht, außerdem umfasst:
    Einrichten einer Übereinstimmung zwischen der E/A-Vorrichtung und der Steuereinheit gemäß einer funktionellen Anforderung der E/A-Vorrichtung und einer von der Steuereinheit umgesetzten Funktion.
     
    4. Verfahren nach Anspruch 2, das außerdem umfasst:
    Laden des Firmwarecodes in die Steuereinheit, indem ein Basisdatenaustauschsystem (Basic Input/Output System, BIOS) oder ein Betriebssystem (Operating System, OS) verwendet wird.
     
    5. Verfahren nach einem der Ansprüche 2 bis 4, das außerdem umfasst:
    Modifizieren der Übereinstimmung zwischen der E/A-Vorrichtung und der Steuereinheit gemäß der funktionellen Anforderung der E/A-Vorrichtung.
     
    6. Steuerverfahren, umfassend:

    Empfangen, in einer Steuereinheit, von Daten von einer ersten Vorrichtung, indem ein Router verwendet wird, und Verarbeiten der Daten gemäß einem in der Steuereinheit gespeicherten Firmwarecode; und

    Senden der verarbeiteten Daten von der Steuereinheit an den Router, sodass der Router die verarbeiteten Daten an die zweite Vorrichtung sendet; wobei

    die erste Vorrichtung eine CPU ist und die zweite Vorrichtung die E/A-Vorrichtung ist, oder die erste Vorrichtung die E/A-Vorrichtung ist und die zweite Vorrichtung die CPU ist;

    vor dem Verarbeiten der Daten gemäß dem in der Steuereinheit gespeicherten Firmwarecode, Modifizieren des Firmwarecodes der Steuereinheit gemäß einer funktionellen Anforderung der E/A-Vorrichtung, wenn die funktionelle Anforderung der E/A-Vorrichtung verändert wird.


     
    7. Verfahren nach Anspruch 6, wobei das Verarbeiten der Daten durch die Steuereinheit gemäß dem in der Steuereinheit gespeicherten Firmwarecode umfasst:

    Auslesen der Daten aus einer Warteschlange in der Steuereinheit in einen Pufferspeicher; und

    Aufrufen des in einem Speicher gespeicherten Firmwarecodes, um die Daten in dem Pufferspeicher zu verarbeiten.


     
    8. Verfahren nach Anspruch 7, das außerdem umfasst:
    Laden des Firmwarecodes in die Steuereinheit, indem ein Basisdatenaustauschsystem (Basic Input/Output System, BIOS) oder ein Betriebssystem (Operating System, OS) verwendet wird.
     
    9. Steuervorrichtung, umfassend:

    einen Router und mindestens zwei Steuereinheiten, wobei

    der Router konfiguriert ist zum:

    Empfangen von Daten, die von einer ersten Vorrichtung an eine zweite Vorrichtung gesendet werden, wobei die Daten eine Kennung einer E/A-Vorrichtung mitführen,

    wobei die erste Vorrichtung eine CPU ist und die zweite Vorrichtung die E/A-Vorrichtung ist, oder die erste Vorrichtung die E/A-Vorrichtung ist und die zweite Vorrichtung die CPU ist;

    Ermitteln, gemäß der Kennung der E/A-Vorrichtung und gemäß Übereinstimmungen zwischen E/A-Vorrichtungen und Steuereinheiten, einer Steuereinheit aus den mindestens zwei Steuereinheiten, die der Kennung der E/A-Vorrichtung entspricht;

    und Senden der Daten an die Steuereinheit, die der Kennung der E/A-Vorrichtung entspricht;

    wobei die Steuereinheit, die der Kennung der E/A-Vorrichtung entspricht, konfiguriert ist zum Verarbeiten der Daten gemäß dem in der Steuereinheit gespeicherten Firmwarecode, um die verarbeiteten Daten zu erhalten; und Senden der verarbeiteten Daten an den Router;

    wobei der Router außerdem konfiguriert ist zum Senden der verarbeiteten Daten an die zweite Vorrichtung;

    wobei die Steuereinheit außerdem umfasst:
    eine Programmierschnittstelle der Steuereinheit, die konfiguriert ist zum Modifizieren des Firmwarecodes der Steuereinheit gemäß einer funktionellen Anforderung der E/A-Vorrichtung, wenn die funktionelle Anforderung der E/A-Vorrichtung verändert wird, bevor der Router ermittelt, dass die Steuereinheit, gemäß der Kennung der E/A-Vorrichtung und gemäß den Übereinstimmungen zwischen den E/A-Vorrichtungen und den Steuereinheiten, der Kennung der E/A-Vorrichtung entspricht.


     
    10. Steuervorrichtung nach Anspruch 9, wobei die Steuereinheit umfasst:

    einen Speicher, der konfiguriert ist zum Speichern des Firmwarecodes;

    einen Pufferspeicher, der konfiguriert ist zum Speichern der Daten, die durch einen Prozessor aus einer Warteschlange in der Steuereinheit ausgelesen werden; und

    den Prozessor, der konfiguriert ist zum Aufrufen des in dem Speicher gespeicherten Firmwarecodes, um die Daten in dem Pufferspeicher so zu verarbeiten, dass die verarbeiteten Daten erhalten werden; und Senden der verarbeiteten Daten an den Router.


     
    11. Steuervorrichtung nach Anspruch 9 oder 10, wobei der Router außerdem konfiguriert ist zum Einrichten einer Übereinstimmung zwischen der E/A-Vorrichtung und der Steuereinheit gemäß einer funktionellen Anforderung der E/A-Vorrichtung und gemäß Funktionen, die von den zwei Steuereinheiten umgesetzt werden.
     
    12. Steuervorrichtung nach einem der Ansprüche 9 bis 11, wobei die Steuereinheit außerdem konfiguriert ist zum: Empfangen des Firmwarecodes, der von einem Basisdatenaustauschsystem (Basic Input/Output System, BIOS) oder einem Betriebssystem (Operating System, OS) geladen wird.
     
    13. Steuervorrichtung nach einem der Ansprüche 9 bis 12, wobei der Router außerdem umfasst:
    eine Programmierschnittstelle des Routers, die konfiguriert ist zum Modifizieren der Übereinstimmung zwischen der E/A-Vorrichtung und der Steuereinheit gemäß der funktionellen Anforderung der E/A-Vorrichtung.
     


    Revendications

    1. Procédé de commande, comprenant:

    recevoir, par un routeur, des données envoyées par un premier dispositif à un deuxième dispositif, dans lequel les données transportant un identifiant d'un dispositif d'E/S, et le premier dispositif étant un CPU et le deuxième dispositif étant le dispositif d'E/S, ou le premier dispositif étant le dispositif d'E/S et le deuxième dispositif étant le CPU ;

    déterminer, par le routeur, selon l'identifiant du dispositif d'E/S et des correspondances entre des dispositifs d'E/S et des contrôleurs, un contrôleur correspondant à l'identifiant du dispositif d'E/S ;

    envoyer, par le routeur, les données au contrôleur correspondant à l'identifiant du dispositif d'E/S, afin que le contrôleur traite les données selon un code de microprogramme stocké dans le contrôleur ;

    recevoir, par le routeur, les données traitées envoyées par le contrôleur ; et

    envoyer, par le routeur, les données traitées au deuxième dispositif ;

    avant la détermination du contrôleur correspondant à l'identifiant du dispositif d'E/S selon l'identifiant du dispositif d'E/S et des correspondances entre des dispositifs d'E/S et des contrôleurs, modifier le code de microprogramme du contrôleur selon une exigence fonctionnelle du dispositif d'E/S lors d'un changement de l'exigence fonctionnelle du dispositif d'E/S.


     
    2. Procédé selon la revendication 1, le fait que le contrôleur traite les données selon un code de microprogramme stocké dans le contrôleur comprenant :

    lire les données à partir d'une file d'attente dans le contrôleur dans une mémoire tampon ; et

    appeler le code de microprogramme stocké dans une mémoire pour traiter les données dans la mémoire tampon.


     
    3. Procédé selon la revendication 1 ou 2, avant la détermination, selon l'identifiant du dispositif d'E/S et des correspondances entre des dispositifs d'E/S et des contrôleurs, d'un contrôleur correspondant à l'identifiant du dispositif d'E/S, le procédé comprenant en outre :
    établir une correspondance entre le dispositif d'E/S et le contrôleur selon une exigence fonctionnelle du dispositif d'E/S et une fonction mise en œuvre par le contrôleur.
     
    4. Procédé selon la revendication 2, comprenant en outre :
    charger le code de microprogramme dans le contrôleur en utilisant un système d'entrée/sortie de base, BIOS, ou un système d'exploitation, OS.
     
    5. Procédé selon l'une quelconque des revendications 2 à 4, comprenant en outre :
    modifier la correspondance entre le dispositif d'E/S et le contrôleur selon l'exigence fonctionnelle du dispositif d'E/S.
     
    6. Procédé de commande, comprenant :

    recevoir, par un contrôleur, des données à partir d'un premier dispositif en utilisant un routeur, et traiter les données selon un code de microprogramme stocké dans le contrôleur ; et

    envoyer, par le contrôleur, les données traitées au routeur, afin que le routeur envoie les données traitées à un deuxième dispositif ;

    le premier dispositif étant un CPU et le deuxième dispositif étant le dispositif d'E/S, ou le premier dispositif étant le dispositif d'E/S et le deuxième dispositif étant le CPU;

    avant le traitement des données selon un code de microprogramme stocké dans le contrôleur, modifier le code de microprogramme du contrôleur selon une exigence fonctionnelle du dispositif d'E/S lors d'un changement de l'exigence fonctionnelle du dispositif d'E/S.


     
    7. Procédé selon la revendication 6, dans lequel le traitement, par le contrôleur, des données selon un code de microprogramme stocké dans le contrôleur comprend :

    lire les données à partir d'une file d'attente dans le contrôleur dans une mémoire tampon ; et

    appeler le code de microprogramme stocké dans une mémoire pour traiter les données dans la mémoire tampon.


     
    8. Procédé selon la revendication 7, comprenant en outre :
    charger le code de microprogramme dans le contrôleur en utilisant un système d'entrée/sortie de base, BIOS, ou un système d'exploitation, OS.
     
    9. Dispositif de commande, comprenant :

    un routeur et au moins deux contrôleurs,

    le routeur étant configuré pour :

    recevoir des données envoyées par un premier dispositif à un deuxième dispositif, les données transportant un identifiant d'un dispositif d'E/S, le premier dispositif étant un CPU et le deuxième dispositif étant le dispositif d'E/S, ou le premier dispositif étant le dispositif d'E/S et le deuxième dispositif étant le CPU ;

    déterminer, selon l'identifiant du dispositif d'E/S et des correspondances entre des dispositifs d'E/S et des contrôleurs, un contrôleur, des au moins deux contrôleurs, correspondant à l'identifiant du dispositif d'E/S ; et envoyer les données au contrôleur correspondant à l'identifiant du dispositif d'E/S ;

    le contrôleur correspondant à l'identifiant du dispositif d'E/S étant configuré pour traiter les données selon un code de microprogramme stocké dans le contrôleur, afin d'obtenir les données traitées ; et envoyer les données traitées au routeur ;

    le routeur étant en outre configuré pour envoyer les données traitées au deuxième dispositif ;

    le contrôleur comprenant en outre :
    une interface de programmation de contrôleur, configurée pour modifier le code de microprogramme du contrôleur selon une exigence fonctionnelle du dispositif d'E/S lors d'un changement de l'exigence fonctionnelle du dispositif d'E/S, avant que le routeur ne détermine le contrôleur correspondant à l'identifiant du dispositif d'E/S selon l'identifiant du dispositif d'E/S et des correspondances entre des dispositifs d'E/S et des contrôleurs.


     
    10. Dispositif de commande selon la revendication 9, dans lequel le contrôleur comprend :

    une mémoire, configurée pour stocker le code de microprogramme ;

    une mémoire tampon, configurée pour stocker les données qui sont lues à partir d'une file d'attente dans le contrôleur par un processeur ; et

    le processeur, configuré pour appeler le code de microprogramme stocké dans la mémoire pour traiter les données dans la mémoire tampon, afin d'obtenir les données traitées ; et envoyer les données traitées au routeur.


     
    11. Dispositif de commande selon la revendication 9 ou 10, dans lequel le routeur est en outre configuré pour établir une correspondance entre le dispositif d'E/S et le contrôleur selon une exigence fonctionnelle du dispositif d'E/S et des fonctions mises en œuvre par les au moins deux contrôleurs.
     
    12. Dispositif de commande selon l'une quelconque des revendications 9 à 11, dans lequel le contrôleur est en outre configuré pour recevoir le code de microprogramme chargé par un système d'entrée/sortie de base, BIOS, ou un système d'exploitation, OS.
     
    13. Dispositif de commande selon l'une quelconque des revendications 9 à 12, dans lequel le routeur comprend en outre :
    une interface de programmation de routeur, configurée pour modifier la correspondance entre le dispositif d'E/S et le contrôleur selon l'exigence fonctionnelle du dispositif d'E/S.
     




    Drawing














    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description