Network system architecture, data processing method of network system and electronic equipment

Abstract

The invention provides a network system architecture, a data processing method of a network system and electronic equipment. Relates to the technical field of communication. In view of the problems of complex development and fragmentation of state management of an existing network system architecture, the network system architecture provided by the invention comprises an application layer, a platform layer and a hardware layer, and the platform layer is located between the application layer and the hardware layer; the application layer is configured to send a configuration instruction to the platform layer and monitor hardware information fed back to the platform layer by the hardware layer; the platform layer is configured to obtain hardware configuration information based on a configuration instruction and send the hardware configuration information to the hardware layer; the hardware configuration information is represented based on a preset layered object model; and the hardware layer is configured to perform hardware configuration based on the hardware configuration information and feed back configuration result information to the platform layer. According to the embodiment of the invention, the problems of hardware state management fragmentation and hardware equipment interface heterogeneity can be solved, the performance of hardware state unified management is improved, and the development complexity is reduced.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a network system architecture, a data processing method for a network system, and an electronic device. Background Art

[0002] With the development of communication technology, large-scale network architecture, as the core infrastructure supporting global communication and data interaction, needs to be highly scalable, flexible, and fault-tolerant to cope with growing business needs and increasingly complex network environments.

[0003] Currently, large-scale network architectures often employ a deeply coupled setup between hardware devices (such as routers and switches) and software systems, limiting the flexibility and scalability of network systems. Related technologies employ network architectures with centralized controllers or middleware to decouple software and hardware.

[0004] However, the network system architecture based on a centralized controller has the heterogeneity of hardware interfaces, which requires the software system to adapt to multiple hardware drivers, resulting in high development complexity and high maintenance costs; while the network system architecture based on middleware has the defect of fragmented hardware status management. Summary of the Invention

[0005] According to various embodiments of the present application, a network system architecture, a data processing method for a network system, and an electronic device are provided; while achieving decoupling of software and hardware, the software can be adapted to multiple hardware drivers and the performance of unified management of hardware status can be improved.

[0006] In the first aspect, the present application provides a network system architecture, including: an application layer, a platform layer and a hardware layer. The application layer and the hardware layer are independently layered and isolated from each other, and the platform layer is located between the application layer and the hardware layer; the application layer is configured to send configuration instructions to the platform layer and monitor the hardware information fed back by the hardware layer to the platform layer; the platform layer is configured to obtain hardware configuration information based on the configuration instructions and send the hardware configuration information to the hardware layer; the hardware configuration information is represented based on a preset hierarchical object model; the hardware layer is configured to perform hardware configuration based on the hardware configuration information and feed back configuration result information to the platform layer.

[0007] Through the above method, the platform layer is set between the application layer and the hardware layer to achieve mutual isolation between the application layer and the hardware layer, and realize the decoupling of software and hardware; by adopting a layered object model to represent hardware configuration information, the resources of the hardware device are abstracted into standardized data entities, which solves the problems of fragmentation of hardware status management and heterogeneity of hardware device interfaces, and improves the performance of unified management of hardware status; through the platform layer forwarding the hardware configuration information represented by the layered object model, the hardware configuration information represented by the unified layered object model can be parsed for different hardware devices, without the need to adapt to the private interfaces of different manufacturers, reducing development complexity, and can adapt to multiple hardware drivers at the hardware layer; it has strong ease of use and practicality.

[0008] In an implementation manner of the first aspect, the platform layer is provided with a database and a data synchronization component, the application layer is connected to the database, the database is connected to the data synchronization component, and the data synchronization component is connected to the hardware layer; the database is used to store the configuration instructions as database transactions to be processed, and to store the hardware configuration information; the data synchronization component is used to obtain the configuration instructions and the hardware configuration information from the database, and forward the hardware configuration information to the hardware layer.

[0009] In an implementation method of the first aspect, the data synchronization component is also used to obtain hardware information sent by the hardware layer and forward the hardware information to the database; the database is also used to store the hardware information forwarded by the data synchronization component and feed back the hardware information to the application layer.

[0010] In an implementation method of the first aspect, the hardware layer is provided with a hardware adaptation layer and a software development kit, and the hardware adaptation layer is connected to the data synchronization component; the hardware adaptation layer is used to convert the hardware configuration information forwarded by the data synchronization component into hardware configuration information recognizable by the hardware device, and call the standardized interface provided by the software development kit to transmit the recognizable hardware configuration information to the hardware device for hardware configuration; the hardware adaptation layer is also used to obtain hardware information of the hardware device and send the recognizable hardware information to the data synchronization component.

[0011] In an implementation method of the first aspect, the hardware layer is provided with a hardware adaptation layer and a software development kit, and the hardware adaptation layer is connected to the data synchronization component; the hierarchical object model includes: object identification, attribute pattern and belonging module; the data synchronization component is also used to determine the configuration dependency based on the object identification, attribute pattern or belonging module; and based on the configuration dependency, obtain each hardware information object from the database, and forward each hardware information object to the hardware layer; the hardware adaptation layer is also used to convert each hardware information object forwarded by the data synchronization component into a hardware information object recognizable by the hardware device, and call the standardized interface corresponding to each hardware information object provided by the software development kit, and transmit the recognizable hardware information object to the hardware device to perform hardware configuration; wherein, the hardware configuration information represented based on the hierarchical object model includes each hardware information object.

[0012] In an implementation method of the first aspect, the data synchronization component is also used to obtain hardware configuration information corresponding to the hardware device from the database when it is detected that the hardware device of the hardware layer is restarted, and send the hardware configuration information to the hardware layer; the hardware layer is used to restore the configuration of the hardware device based on the hardware configuration information and complete the restart.

[0013] In an implementation method of the first aspect, the data synchronization component is further used to send a transaction rollback request to the database and send configuration recovery information to the hardware layer when receiving configuration failure information feedback from the hardware layer; the database is further used to undo the modifications to the hardware information of the hardware device based on the received transaction rollback request and restore the hardware information to the state before the configuration; the hardware layer is further used to restore the hardware device to the state before the configuration based on the received configuration recovery information.

[0014] In an implementation method of the first aspect, the platform layer is further provided with a platform application, which is connected to the database; the platform application is used to obtain hardware information in the database, manage the configuration of hardware devices based on the obtained hardware information, and write updated hardware configuration information into the database; the platform application is also used to monitor the hardware event information fed back by the data synchronization component in the database, and send configuration instructions to the database based on the hardware event information.

[0015] In an implementation manner of the first aspect, the platform layer further includes a database abstraction layer and a data synchronization component abstraction layer; the database abstraction layer is located between the application layer and the database, and the data synchronization component abstraction layer is located between the data synchronization component and the hardware layer.

[0016] In a second aspect, the present application provides a data processing method for a network system, the method comprising:

[0017] The application layer sends configuration instructions to the platform layer and monitors the hardware information fed back by the hardware layer to the platform layer; the platform layer obtains hardware configuration information based on the configuration instructions and sends the hardware configuration information to the hardware layer; the hardware configuration information is represented based on a preset hierarchical object model; the hardware layer performs hardware configuration based on the hardware configuration information and feeds back the configuration result information to the platform layer.

[0018] In a third aspect, the present application provides an electronic device, one or more processors; and a memory on which one or more programs are stored. When the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described in the first aspect.

[0019] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method according to any one of the first aspects is implemented.

[0020] In a fifth aspect, the present application provides a computer program product, which, when executed on a device, enables the device to execute any of the methods described in the first aspect.

[0021] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0023] Figure 1 A schematic diagram of the network system architecture provided in an embodiment of the present application;

[0024] Figure 2 Another schematic diagram of the network system architecture provided by an embodiment of the present application;

[0025] Figure 3 A schematic diagram of the network system software and hardware interaction process provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the implementation flow of the data processing method of the network system provided in an embodiment of the present application;

[0027] Figure 5 Schematic diagram of the hardware synchronization and hot restart process provided in the embodiment of the present application;

[0028] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following embodiments of the technical solution of the present application will be described in detail with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present application and are therefore only examples and are not intended to limit the scope of protection of the present application.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned figure descriptions are intended to cover non-exclusive inclusions.

[0031] In the description of the embodiments of this application, the technical terms "first" and "second" are used only to distinguish different objects and should not be understood to indicate or imply relative importance or implicitly specify the quantity, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, the meaning of "plurality" is more than two, unless otherwise clearly and specifically defined.

[0032] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0033] In the description of the embodiments of this application, the term "and / or" is simply a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0034] The traditional switch architecture has deep coupling between software and hardware. This can be achieved through a software-defined networking (SDN) architecture based on the separation of the control plane and forwarding plane, or an embedded system architecture based on models and middleware.

[0035] However, the software-defined networking architecture suffers from heterogeneous interfaces in the underlying hardware devices. Software development kit (SDK) interfaces vary significantly between vendors, requiring upper-layer applications to adapt to multiple hardware drivers, resulting in high development and maintenance costs. In a distributed environment, asynchronous messaging makes state synchronization difficult and prone to state inconsistencies. Furthermore, a hot restart requires the controller to fully retransmit the flow table, which is costly and prone to timing conflicts. Embedded system architectures based on models and middleware lack model abstraction, leading to fragmented hardware state management. Furthermore, in a distributed environment, the lack of a state synchronization mechanism makes it difficult to cope with large-scale network scenarios and hardware hot restart scenarios.

[0036] In response to the above technical problems, an embodiment of the present application provides a network system architecture that adopts a layered design architecture of application layer, platform layer and hardware layer to achieve decoupling of software and hardware, and abstractly represents the corresponding hardware information based on a layered object model. It can achieve adaptation of upper-layer applications to different underlying hardware based on a unified interface design, reduce the difficulty of development and maintenance, and improve the performance of unified management of hardware status.

[0037] The following describes the specific form of the network system architecture and the implementation process of data processing based on the network system architecture through embodiments.

[0038] See Figure 1 , Figure 1 This is a schematic diagram of the network system architecture provided in the embodiment of the present application. Figure 1 As shown, the network system architecture 10 includes an application layer 101, a platform layer 102 and a hardware layer 103; wherein the application layer and the hardware layer are independently layered and isolated from each other, and the platform layer is located between the application layer and the hardware layer.

[0039] Exemplarily, the application layer is configured to send configuration instructions to the platform layer and monitor the hardware information fed back by the hardware layer to the platform layer; the platform layer is configured to obtain hardware configuration information based on the configuration instructions and send the hardware configuration information to the hardware layer, and the hardware configuration information is represented based on a preset hierarchical object model; wherein the hierarchical object model is a model that performs hierarchical abstraction based on the hardware characteristics and functional modules of the network device, and a unified representation of hardware information, such as hardware configuration information and hardware information, can be obtained through the hierarchical object model.

[0040] Accordingly, the hardware layer is configured to perform hardware configuration based on the hardware configuration information and to feed back configuration result information to the platform layer. Since a hierarchical object model is used to represent hardware configuration information, after the platform layer forwards the hardware configuration information to the hardware layer, the hardware layer can receive the hardware configuration information based on a unified interface design and convert the hardware configuration information into configuration information that can be recognized by different hardware, thereby completing the hardware configuration. The configuration result information includes information on the success or failure of the hardware device node configuration; after the hardware layer configuration is completed, the configuration result information is fed back to the application layer through the platform layer; for example, the platform layer obtains the configuration result information fed back by the hardware layer, stores the configuration result information in a storage unit, and the application layer can obtain the configuration result information from the storage unit.

[0041] In the network system architecture, the application layer can include various applications, responsible for providing various network services and application programming interfaces (APIs), such as browsers and clients. Applications interact with the underlying platform and hardware layers through the interfaces provided by the application layer to implement corresponding network functions. As the layer that directly interacts with users, the application layer can generate configuration instructions based on user triggers. These configuration instructions can be for underlying hardware devices to be updated or for newly added hardware devices.

[0042] Exemplarily, the configuration instruction may include information such as the hardware identification of the underlying hardware device and the corresponding hardware configuration information (i.e., the configuration parameters for actually configuring the hardware); or the configuration instruction may only include the hardware identification, and the corresponding hardware configuration information is stored in the platform layer. After receiving the configuration instruction, the platform layer obtains the hardware configuration information associated with the configuration instruction based on the correspondence between the configuration instruction and the hardware configuration information.

[0043] Exemplarily, the network system architecture includes a hierarchical structure, such as the physical layer, data link layer, and network layer, and different layers have corresponding functions and resources; the hierarchical object model abstracts various resources and functions in the network system architecture into objects at different levels, and defines unique object identifiers (oid) and attributes for these objects, thereby realizing unified management and operation of network resources in the network system architecture, effectively solving the problem of fragmentation of hardware status management.

[0044] For example, objects represented by the hierarchical object model may include ports, virtual local area networks (VLANs), and forwarding database tables (FDB tables). These objects correspond to different layers and functional modules in the network system. For example, a port object corresponds to the interface between the physical layer and the data link layer, representing a physical port on a network device and possessing attribute parameters such as port speed. A VLAN object corresponds to the virtual network division at the data link layer, representing a virtual local area network and possessing attribute parameters such as network identification. A forwarding database table object corresponds to the forwarding decision at the data link layer and stores the mapping between communication addresses and ports.

[0045] In some embodiments, each object model (such as port, VLAN, and FDB) is provided with a displaced object identifier (such as oid) and a set of predefined attributes, which can be read and written through an application programming interface (API).

[0046] The application programming interface provides a unified operation interface for creating (create), setting (set), getting (get), and deleting (remove). Through this operation interface, corresponding read and write operations can be performed on the hardware status information stored in the hierarchical object model.

[0047] For example, the hardware information fed back by the hardware layer to the platform layer may include hardware call return information and hardware event information. Hardware call return information is the return content of the call that is synchronously notified to the application layer; hardware event information is hardware events transmitted by the hardware layer through the platform layer, such as port status changes, FDB events, and daughter card insertion and removal events.

[0048] Through the hardware abstraction mechanism of the hierarchical object model, the hardware group sources (such as ports, virtual LANs, etc.) of network devices (such as switches) are abstracted into standardized data entities, and are given globally unique object identifiers (such as OID) and predefined attributes (such as mode attributes, attribute modules, etc.). This effectively solves the problems of fragmented hardware status and heterogeneous interfaces of software development kits (SDKs) from different manufacturers in traditional solutions. In a distributed system, the nodes of each hardware device can directly parse the configuration parameters through the hardware configuration information represented by a unified hierarchical object model. There is no need to write independent drivers for each type of hardware, and it can adapt to the private interfaces of different manufacturers, thereby reducing development complexity, achieving unified semantic expression, and improving the unified management capabilities of the hardware system.

[0049] In some embodiments, as Figure 2As shown, in this network system architecture, the platform layer also includes a database and data synchronization components. The database can be a database that stores and manages chip-related data, configuration information, status information, etc., such as an Application-Specific Integrated Circuit (ASIC_DB). The data synchronization component can be a Syncd synchronizer, which forwards hardware configuration information issued by the application layer to the hardware layer, or forwards hardware information fed back by the hardware layer to the application layer.

[0050] For example, Figure 2 As shown, the application layer is connected to the database, which is connected to the data synchronization component, which is then connected to the hardware layer. The database is used to store configuration instructions as pending database transactions and hardware configuration information; the data synchronization component is used to retrieve configuration instructions and hardware configuration information from the database and forward the hardware configuration information to the hardware layer.

[0051] Exemplarily, the database stores hardware status information and hardware information. The hardware information may include hardware call return information and hardware event information. The hardware status information is real-time hardware status information, including hardware configuration information, dynamic hardware information, etc. Both the hardware status information and the hardware information can be represented based on the aforementioned hierarchical object model.

[0052] In some embodiments, the data synchronization component is also used to obtain hardware information sent by the hardware layer and forward the hardware information to the database; the database is also used to store the hardware information forwarded by the data synchronization component and feed back the hardware information to the application layer.

[0053] Exemplarily, the database is used to store hardware status information, hardware call return information, and hardware event information. Hardware status information includes hardware configuration information and dynamic hardware information. The application layer, as a producer of hardware status information, sends hardware configuration information or synchronizes dynamic hardware information to the platform layer and hardware layer. The application layer, as a consumer of hardware call return information and hardware event information, obtains hardware call return information and hardware event information fed back by the hardware layer from the platform layer.

[0054] For example, the data synchronization component acts as a consumer of hardware status information and obtains the hardware status information sent by the application layer from the database; the data synchronization component acts as a producer of hardware call return information and writes the hardware call return information fed back by the hardware layer into the database for query by the application layer; the data synchronization component acts as a producer of hardware event information and writes the hardware event information fed back by the hardware layer into the database.

[0055] Among them, the operations of the application layer to read and write hardware information in the database and the operations of the data synchronization component to read and write data in the database can all be implemented based on a unified API interface.

[0056] In some embodiments, as Figure 2 As shown, the hardware layer includes a hardware adaptation layer and a software development kit (SDK). The hardware adaptation layer is connected to the data synchronization component. The hardware adaptation layer converts the hardware configuration information forwarded by the data synchronization component into hardware configuration information that can be recognized by the hardware device. It then calls the standardized interface provided by the SDK to transmit the recognizable hardware configuration information to the hardware device for hardware configuration. The hardware adaptation layer also obtains hardware information from the hardware device and sends this hardware information to the data synchronization component.

[0057] Exemplarily, the hardware adaptation layer is a component that interacts with the hardware device directly through a software development kit (SDK), which is a software toolkit for developing and managing hardware devices. The hardware information may include hardware event information and hardware call return information.

[0058] In the hardware configuration scenario, when the application layer needs to update the hardware configuration, the new hardware configuration information is written to the database of the platform layer; the data synchronization component of the platform layer detects the configuration change in the database and begins to perform the corresponding hardware configuration operation. In the process of performing the hardware configuration operation, the data synchronization component reads the hardware configuration information from the database. The hardware configuration signal describes how the hardware device is configured, operates, and the actual configuration parameters; the data synchronization component converts the hardware configuration information into a format that the hardware adaptation layer can understand, and transmits the converted hardware configuration information to the hardware adaptation layer. The hardware adaptation layer calls the interface provided by the SDK, interacts with the hardware device, applies the hardware configuration information to the hardware device, and completes the hardware configuration update. The hardware device feeds back the configured status information to the hardware adaptation layer. The hardware adaptation layer transmits the status information to the data synchronization component. The data synchronization component updates the status information to the database for query and monitoring by the application layer.

[0059] In the scenario where a hardware device triggers a hardware event, when the underlying hardware device triggers a hardware event (such as a port status change, link failure, packet processing anomaly, etc.), the hardware layer generates hardware event information; after the hardware adaptation layer monitors the hardware event triggered by the hardware device, it passes the corresponding hardware event information to the data synchronization component; after receiving the hardware event information, the data synchronization component performs format conversion, converting the hardware event information into a format that the application layer can understand, and updates the hardware event information to the database. Application layer applications (such as transaction processing services) obtain hardware event information from the database by monitoring changes in the database and perform corresponding processing. For example, when a port changes, the application layer application can adjust the network configuration based on the new port status.

[0060] In the scenario where the hardware device returns hardware call return information, the application layer can issue instructions to query hardware information. The data synchronization component calls the function provided by the SDK through the hardware adaptation layer to perform the operation corresponding to the corresponding query instruction. After the execution is completed, the hardware adaptation layer returns the execution result (i.e., hardware call return information) to the data synchronization component; the data synchronization component writes the hardware call return information to the database, and the application layer monitors the hardware call return information in the database to promptly understand the results of the hardware operation.

[0061] In some embodiments, the hierarchical object model includes: object identification, attribute pattern and belonging module; when hardware configuration information is represented based on the hierarchical object model, the hardware configuration information includes object identification information, attribute pattern information and belonging module corresponding to the hardware to be configured.

[0062] Exemplarily, the object identification (oid) information exists in the form of a string, separated by colons for each level. The object identification information may include a mode identifier (mode_id), a module identifier (mid), an object type, and an attribute combination (key1 to key N, where N is an integer greater than 1). The mode identifier is used to define the attribute mode of the hardware status information and can be set to a predefined integer data; the module identifier is used to define the module to which the hardware status information belongs and can be set to a predefined integer data; the object type is set to a predefined integer data; the attribute combination is used to uniquely identify the attribute combination of each object and can be set to a string type.

[0063] Exemplarily, the predefined attributes may include attribute modes and modules. Attribute modes may include global modes (e.g., system MAC address), interface modes (e.g., port rate configuration), and VLAN modes (e.g., 802.1Q tag policy). Modules may include port modules, virtual local area network modules, and quality of service (QoS) modules.

[0064] In some embodiments, the data synchronization component is further configured to determine configuration dependencies based on object identifiers, attribute patterns, or modules; and based on the configuration dependencies, retrieve each hardware information object from the database and forward each hardware information object to the hardware layer. The hardware configuration information represented based on the hierarchical object model includes each hardware information object.

[0065] Exemplarily, the hardware configuration information represented by the hierarchical object model includes an object identifier and predefined attributes (such as attribute mode and module). Based on the object identifier and predefined attributes, dependencies during the configuration process can be determined; these dependencies can include vertical dependencies, horizontal dependencies, and display dependencies.

[0066] For example, the object identifier includes a mode identifier (mode_id), which may include an interface mode (such as mode_id=1) and a global mode (mode_id=0); and the port configuration of object A based on the interface mode depends on the system MAC address configuration of object B based on the global mode; wherein, the dependency relationship between the configuration processes of the two can be determined by judging the size of the mode identifiers of object A and object B.

[0067] For another example, the predefined attributes include the module to which they belong, and the object identifier also includes the module identifier (mid). The dependency relationship between functional modules is determined based on the module to which they belong or the module identifier; for example, the configuration of a VLAN object (module identifier is mid=4) depends on the configuration of a port object (module identifier mid=2); wherein, if the hardware configuration information of object A references the module identifier or the module to which it belongs of object B, then it is determined that the configuration of object A depends on the configuration of object B.

[0068] For another example, the attribute mode includes a global mode and an interface mode. During hardware synchronization or hot restart, the global mode takes precedence over the interface mode, so that the interface configuration depends on the global configuration.

[0069] For another example, the predefined attributes also include an associated field, which directly points to the object identifier or key of another object. By parsing the value of the associated field in the attribute, if it contains the object identifier or key of another object, the dependency of the object configuration is determined.

[0070] Illustratively, after determining the dependency, the data synchronization component may serially load each hardware information object (or configuration parameter) from the database according to the level of the object identifier, and forward each hardware information object to the hardware layer.

[0071] For example, port objects include port1, and VLAN objects include VLAN10. The determined dependency is that VLAN configuration depends on port configuration, that is, the VLAN object can only be configured after the corresponding port object configuration is completed; the data synchronization component recognizes that port1 belongs to the port module and VLAN10 belongs to the VLAN module, and by analyzing the module dependencies, determines that the VLAN module depends on the port module, and then determines that VLAN10 depends on port1, and determines the configuration order, that is, configure port1 first and then configure VLAN10; the data synchronization component obtains hardware information objects from the database according to this configuration order and forwards them to the hardware layer.

[0072] By abstractly representing hardware resources based on hierarchical objects, the problem of fragmented hardware state management is eliminated, semantic unification is achieved, development complexity is reduced, and development efficiency is improved. By serializing the loading of hardware configuration information based on the object identifier hierarchy (for example, rebuilding the routing table first and then restoring the access control list (ACL) rules), the dependencies between the objects to be configured are dynamically parsed, eliminating the risk of omissions and rigidity in the static priority queue management process, and improving the consistency rate of state recovery.

[0073] In some embodiments, the hardware adaptation layer is also used to convert each hardware information object forwarded by the data synchronization component into a hardware information object that can be recognized by the hardware device, and call the standardized interface corresponding to each hardware information object provided by the software development kit to transmit the recognizable hardware information object to the hardware device for hardware configuration.

[0074] For example, the hardware-layer SDK performs secondary abstraction and encapsulation based on the hardware module functions (port management module, routing table management module, VLAN management module), and sets a unified set of CRUD (create, read, update, delete) interfaces for each module. These interfaces define standard methods for operating the module, such as create, read, update, and delete operations. By providing a unified standardized interface (CRUD interface) for the data synchronization component, the interface provided to the platform-layer data synchronization component is independent of the specific hardware manufacturer or model.

[0075] For example, when adding an ASIC chip from a certain manufacturer, no matter which manufacturer's ASIC chip is at the bottom, only the corresponding module interface (such as the port creation interface "port_create()") is expanded without modifying its core architecture, thus implementing a modular interface design; the data synchronization component creates a port by calling the port_create() interface without having to worry about the specific implementation of the underlying hardware, thereby shielding the differences between different underlying hardware.

[0076] The embodiments of the present application can achieve seamless collaboration of cross-brand hardware and compatibility of routing table configurations between different models of hardware in data scenarios where hardware from multiple manufacturers coexists (for example, scenarios where different types of chips are deployed in a mixed manner) through hardware information represented by a unified hierarchical object model and a unified standardized interface.

[0077] like Figure 3 As shown, the platform layer also includes a database abstraction layer (such as the redisAd layer) and a data synchronization component abstraction layer (such as the syncdAd layer); the database abstraction layer is located between the application layer and the database, and is used to shield direct interaction between the database and the application layer; the data synchronization component abstraction layer is located between the data synchronization component and the hardware layer, and is used to shield direct interaction between the data synchronization component and the abstraction layer (AD) and the hardware driver.

[0078] For example, Figure 3 The solid arrows shown correspond to the hardware calling process and the dotted arrows correspond to the hardware event notification process. The hardware calling process includes calling the hardware driver, configuring or querying the status information of the hardware device through the hardware driver.

[0079] Hardware calling process:

[0080] 1. The application writes hardware configuration information to the database through the database abstraction layer to configure the hardware or update the hardware status.

[0081] 2. The data synchronization component monitors changes in the database and obtains hardware configuration information from the database.

[0082] 3. The data synchronization component calls the abstraction layer AD through the data synchronization component abstraction layer. The abstraction layer AD encapsulates specific hardware operations to provide a unified interface for the data synchronization component. The abstraction layer further abstracts and encapsulates the SDK interface, defining a unified set of CRUD interfaces based on the hardware module's functionality. This provides a higher level of abstraction for the hardware adaptation layer, hiding the complexity of the underlying hardware device drivers.

[0083] 4. The abstract layer calls the hardware driver, which is a software component that interacts directly with the hardware device. It is responsible for converting the received hardware configuration information into instructions that the hardware can understand to complete the hardware configuration; it also processes the response of the hardware device. After the configuration is completed, the configuration result information and the configured hardware information are returned to the data synchronization component through the data synchronization component abstract layer.

[0084] 5. The data synchronization component writes the configuration result information and the configured hardware information into the database.

[0085] 6. The database can feed back configuration result information and configured hardware information to the application through the database abstraction layer, so that the application can obtain the latest hardware information.

[0086] Hardware event notification process:

[0087] 7. When a hardware event is triggered by the hardware device, the abstract layer of the hardware layer sends the corresponding hardware event information to the data synchronization component through the data synchronization component abstract layer.

[0088] 8. The data synchronization component writes the hardware event information into the database.

[0089] 9. The application monitors changes in the database. The database sends hardware event information to the application layer through the database abstraction layer. The application executes corresponding logic based on the hardware event information.

[0090] In some embodiments, when a hot restart occurs in the underlying hardware device, the data synchronization component is also used to obtain hardware configuration information corresponding to the hardware device from the database and send the hardware configuration information to the hardware layer; the hardware layer is used to restore the configuration of the hardware device based on the hardware configuration information and complete the restart.

[0091] For example, the process of restoring the configuration of a hardware device when a hot restart occurs is the same as the implementation principle of the hardware configuration process; based on the hot restart trigger instruction, the data synchronization component reads the corresponding hardware configuration information (including various hardware information objects with dependent relationships) from the database, and calls the unified standardized interface provided by the SDK to send the hardware configuration information to the hardware device; the hardware device is configured based on the dependency relationship of the hardware information objects.

[0092] During hardware synchronization or hot restart, configurations are loaded from the database serially according to the object identification level, dependencies are dynamically resolved, and the configuration order is determined, avoiding the omission risk of traditional static priority queue management.

[0093] In some embodiments, the data synchronization component is used to send a transaction rollback request to the database and configuration recovery information to the hardware layer when receiving configuration failure information feedback from the hardware layer; the database is also used to undo the modifications to the hardware information of the hardware device based on the received transaction rollback request and restore the hardware information to the state before the configuration; the hardware layer is also used to restore the hardware device to the state before the configuration based on the received configuration recovery information; the hardware information is persistently stored in the database, and even if the hardware is abnormally powered off, the complete configuration can still be restored from the database after restart without interrupting the operation of the upper-layer software business, thereby realizing business-unaware hot restart.

[0094] For example, a database is introduced in the middle platform layer, and the configuration instructions issued by the application layer are converted into transactional operations through the database. In a distributed multi-node application scenario, if the configuration of a hardware device node fails, the database can trigger a transaction rollback operation to ensure the atomicity of the multi-node configuration; it can effectively solve the problems of network splits and inconsistent state synchronization in a distributed environment, and improve the success rate in cross-node synchronization scenarios; the data synchronization component realizes the decoupling of software and hardware by monitoring database changes and calling the standardized interface provided by the hardware SDK; by batch processing transaction data in the database, the number of frequent hardware interface calls is reduced.

[0095] In some embodiments, as Figure 2 As shown, the platform layer is also provided with a platform application, which is connected to the database; the platform application is used to obtain hardware information in the database, manage the configuration of hardware devices based on the obtained hardware information, and write updated hardware configuration information into the database; the platform application is also used to monitor the hardware event information fed back by the data synchronization component in the database, and send configuration instructions to the database based on the hardware event information.

[0096] Based on the above network system architecture, the data processing process of the network system architecture is introduced below. Based on the same implementation principle as the above embodiment, it will not be repeated here. Figure 4 As shown, the data processing method of the network system architecture may include the following steps:

[0097] S401: The application layer sends configuration instructions to the platform layer, and monitors the hardware information fed back by the hardware layer to the platform layer.

[0098] S402, the platform layer obtains hardware configuration information based on the configuration instruction, and sends the hardware configuration information to the hardware layer; the hardware configuration information is represented based on a preset hierarchical object model.

[0099] S403: The hardware layer performs hardware configuration based on the hardware configuration information, and feeds back configuration result information to the platform layer.

[0100] In some embodiments, the platform layer is provided with a data synchronization component and a database, and the hardware layer is provided with a hardware adaptation layer and a software development kit; the method further comprises:

[0101] Based on the configuration instructions, the data synchronization component obtains the hardware configuration information stored in the database and forwards the hardware configuration information to the hardware layer; the hardware adaptation layer converts the hardware configuration information forwarded by the data synchronization component into hardware configuration information that can be recognized by the hardware device, and calls the standardized interface provided by the software development kit to transmit the recognizable hardware configuration information to the hardware device for hardware configuration.

[0102] In some embodiments, the hierarchical object model includes: an object identifier, an attribute schema, and a module to which it belongs; the data synchronization component obtains hardware configuration information stored in a database based on the configuration instruction, and forwards the hardware configuration information to the hardware layer, including:

[0103] The data synchronization component determines configuration dependencies based on object identifiers, attribute patterns, or modules. Based on these dependencies, the data synchronization component retrieves hardware information objects from the database and forwards them to the hardware layer. Hardware configuration information represented by the hierarchical object model includes hardware information objects.

[0104] The hardware adaptation layer converts the hardware configuration information forwarded by the data synchronization component into hardware configuration information that can be recognized by the hardware device. It then calls the standardized interface provided by the software development kit to transmit the recognizable hardware configuration information to the hardware device for hardware configuration, including:

[0105] The hardware adaptation layer converts each hardware information object forwarded by the data synchronization component into a hardware information object recognizable by the hardware device, and calls the standardized interface corresponding to each hardware information object provided by the software development kit to transmit the recognizable hardware information object to the hardware device for hardware configuration.

[0106] like Figure 5 As shown in the figure, the interaction process between the database, the data synchronization component and the software development kit, the data synchronization component monitors the information in the database, and when the trigger instruction of data synchronization and hot restart is detected, the various hardware information objects, such as DATA1, DATA2, and DATA3, are obtained from the database (ASIC_DB) based on the configuration dependency of the object to be configured; for example, DATA1 is the first hardware information object A for system address configuration, DATA2 is the second hardware information object B for port configuration, and DATA3 is the third hardware information object C for VLAN configuration; the configuration of C depends on the configuration of B, and the configuration of B depends on the configuration of A; after the data synchronization component obtains each hardware information object, it calls the unified annotation interface of each module provided by the SDK, for example, DATA1 calls AD1, DATA2 calls AD2, and DATA3 calls AD13 to perform hardware configuration.

[0107] In some embodiments, during the hardware configuration process, the method further includes:

[0108] When the data synchronization component receives configuration failure information from the hardware layer, it sends a transaction rollback request to the database and configuration recovery information to the hardware layer; based on the received transaction rollback request, the database undoes the modifications to the hardware information of the hardware device and restores it to the hardware information before the configuration; based on the received configuration recovery information, the hardware layer restores the hardware device to the state before the configuration.

[0109] The embodiment of the present application is based on a decoupled architecture driven by a layered object model and database. Through hardware state abstraction, unified interface design, and dynamic dependency management, it improves the flexibility of switch configuration, synchronization atomicity, and hot restart reliability, and is suitable for cloud computing, large-scale data center networks, and multi-vendor hardware compatibility scenarios.

[0110] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0111] Figure 6 A schematic diagram of the hardware structure of the electronic device 60 is shown.

[0112] like Figure 6 As shown, the electronic device 60 of this embodiment includes: at least one processor 601 ( Figure 6 Only one is shown), a memory 602, wherein the memory 602 stores a computer program 603 that can be run on the processor 601. When the processor 601 executes the computer program 603, the steps in the above method embodiment are implemented, for example Figure 4 Alternatively, the processor 601 implements the functions of the modules / units in the above-mentioned apparatus embodiments when executing the computer program 603. The electronic device may be a network device, such as a switch, a router, etc.

[0113] It should be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device 60. In other embodiments of the present application, the electronic device 60 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0114] The electronic device 60 may include, but is not limited to, a processor 601 and a memory 602. Those skilled in the art will appreciate that Figure 6It is only an example of the electronic device 60 and does not constitute a limitation of the electronic device 60. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the server may also include an input sending device, a network access device, a bus, etc.

[0115] The processor 601 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0116] Processor 601 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 601 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 601. If processor 601 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 601's latency, and thus improves system efficiency.

[0117] In some embodiments, the memory 602 may be an internal storage unit of the electronic device 60, such as a hard disk or memory of the electronic device 60. The memory 602 may also be an external storage device of the electronic device 60, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 60. Furthermore, the memory 602 may include both an internal storage unit of the electronic device 60 and an external storage device. The memory 602 is used to store an operating system, application programs, a boot loader, data, and other programs, such as program code of a computer program. The memory 602 may also be used to temporarily store data that has been sent or is about to be sent.

[0118] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0119] It should be noted that the structure of the above-mentioned electronic device is only illustrative, and based on different application scenarios, it may also include other physical structures, and the physical structure of the electronic device is not limited here.

[0120] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0121] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps in the above-mentioned various method embodiments.

[0122] An embodiment of the present application provides a computer program product. When the computer program product runs on a server, the server can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0123] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the process in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. Computer-readable media may include: any entity or device that can carry computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0124] The electronic device, computer storage medium, and computer program product provided in the above-mentioned embodiments of the present application are all used to execute the methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects corresponding to the methods provided above, and will not be repeated here.

[0125] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0126] It should be understood that the above is only to help those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Based on the above examples given, those skilled in the art can obviously make various equivalent modifications or changes. For example, certain steps in each embodiment of the above detection method may be unnecessary, or certain new steps may be added. Or a combination of any two or any multiple embodiments described above. Such modifications, changes, or combined solutions also fall within the scope of the embodiments of the present application.

[0127] It should also be understood that the division of the modes, situations, categories and embodiments in the embodiments of the present application is only for the convenience of description and should not constitute a special limitation. The features of various modes, categories, situations and embodiments can be combined without contradiction.

[0128] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0129] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0130] In the embodiments provided in this application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0131] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0132] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

[0133] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A network system architecture, characterized in that: The network system architecture includes an application layer, a platform layer and a hardware layer. The application layer and the hardware layer are independently layered and isolated from each other, and the platform layer is located between the application layer and the hardware layer. The application layer is configured to send configuration instructions to the platform layer and monitor the hardware information fed back by the hardware layer to the platform layer; The platform layer is configured to obtain hardware configuration information based on the configuration instruction and send the hardware configuration information to the hardware layer; The hardware configuration information is represented based on a preset hierarchical object model; The hardware layer is configured to perform hardware configuration based on the hardware configuration information and feed back configuration result information to the platform layer.

2. The network system architecture according to claim 1, characterized in that: The platform layer is provided with a database and a data synchronization component, the application layer is connected to the database, the database is connected to the data synchronization component, and the data synchronization component is connected to the hardware layer; The database is configured to store the configuration instructions as database transactions to be processed, and to store the hardware configuration information; The data synchronization component is used to obtain the configuration instructions and the hardware configuration information from the database, and forward the hardware configuration information to the hardware layer.

3. The network system architecture according to claim 2, characterized in that: The data synchronization component is further used to obtain hardware information sent by the hardware layer and forward the hardware information to the database; The database is further used to store the hardware information forwarded by the data synchronization component and feed back the hardware information to the application layer.

4. The network system architecture according to claim 2, wherein: The hardware layer is provided with a hardware adaptation layer and a software development kit, and the hardware adaptation layer is connected to the data synchronization component; The hardware adaptation layer is used to convert the hardware configuration information forwarded by the data synchronization component into hardware configuration information that can be identified by the hardware device, and call the standardized interface provided by the software development tool kit to transmit the identified hardware configuration information to the hardware device for hardware configuration; The hardware adaptation layer is further used to obtain hardware information of the hardware device and send identifiable hardware information to the data synchronization component.

5. The network system architecture according to claim 2, wherein: The hardware layer is provided with a hardware adaptation layer and a software development kit, and the hardware adaptation layer is connected to the data synchronization component; the layered object model includes: object identification, attribute mode and belonging module; The data synchronization component is further configured to determine configuration dependencies based on the object identifier, attribute mode, or module to which it belongs; and based on the configuration dependencies, obtain each hardware information object from the database and forward each hardware information object to the hardware layer; The hardware adaptation layer is further configured to convert each of the hardware information objects forwarded by the data synchronization component into a hardware information object recognizable by the hardware device, and call a standardized interface corresponding to each of the hardware information objects provided by the software development kit to transmit the recognizable hardware information object to the hardware device for hardware configuration; The hardware configuration information represented based on the hierarchical object model includes the hardware information objects.

6. The network system architecture according to claim 2, characterized in that: The data synchronization component is further configured to, upon detecting that a hardware device of the hardware layer has restarted, obtain hardware configuration information corresponding to the hardware device from the database and send the hardware configuration information to the hardware layer; The hardware layer is used to restore the configuration of the hardware device based on the hardware configuration information and complete the restart.

7. The network system architecture according to claim 2, wherein: The data synchronization component is further configured to send a transaction rollback request to the database and configuration recovery information to the hardware layer upon receiving configuration failure information fed back by the hardware layer; The database is further configured to undo modifications to the hardware information of the hardware device based on a received transaction rollback request and restore the hardware information to the state before the configuration; The hardware layer is further configured to restore the hardware device to a state before configuration based on the received configuration restoration information.

8. The network system architecture according to any one of claims 2 to 7, wherein the platform layer is further provided with a platform application, and the platform application is connected to the database; The platform application is configured to obtain hardware information from the database, manage configurations of hardware devices based on the obtained hardware information, and write updated hardware configuration information into the database; The platform application is further configured to monitor hardware event information fed back by the data synchronization component in the database, and send configuration instructions to the database based on the hardware event information.

9. According to the network system architecture according to any one of claims 2 to 7, the platform layer also includes a database abstraction layer and a data synchronization component abstraction layer; the database abstraction layer is located between the application layer and the database, and the data synchronization component abstraction layer is located between the data synchronization component and the hardware layer.

10. A data processing method for a network system, characterized in that: Based on the network system architecture according to any one of claims 1 to 9, the method includes: The application layer sends configuration instructions to the platform layer and monitors the hardware information fed back by the hardware layer to the platform layer; The platform layer obtains hardware configuration information based on the configuration instruction and sends the hardware configuration information to the hardware layer; the hardware configuration information is represented based on a preset hierarchical object model; The hardware layer performs hardware configuration based on the hardware configuration information and feeds back configuration result information to the platform layer; the hardware information includes the configuration result information.

11. The method according to claim 10, characterized in that The platform layer is provided with a data synchronization component and a database, and the hardware layer is provided with a hardware adaptation layer and a software development kit; the method further comprises: The data synchronization component obtains the hardware configuration information stored in the database based on the configuration instruction, and forwards the hardware configuration information to the hardware layer; The hardware adaptation layer converts the hardware configuration information forwarded by the data synchronization component into hardware configuration information recognizable by the hardware device, and calls the standardized interface provided by the software development tool kit to transmit the recognizable hardware configuration information to the hardware device for hardware configuration.

12. The method according to claim 11, characterized in that The hierarchical object model includes: object identification, attribute mode and belonging module; the data synchronization component obtains the hardware configuration information stored in the database based on the configuration instruction and forwards the hardware configuration information to the hardware layer, including: The data synchronization component determines the configuration dependency based on the object identifier, attribute mode or module to which it belongs; and based on the configuration dependency, obtains each hardware information object from the database and forwards each hardware information object to the hardware layer; The hardware adaptation layer converts the hardware configuration information forwarded by the data synchronization component into hardware configuration information that can be identified by the hardware device, and calls the standardized interface provided by the software development tool kit to transmit the identified hardware configuration information to the hardware device to perform hardware configuration, including: The hardware adaptation layer converts each of the hardware information objects forwarded by the data synchronization component into a hardware information object recognizable by the hardware device, and calls the standardized interface corresponding to each of the hardware information objects provided by the software development toolkit to transmit the recognizable hardware information object to the hardware device for hardware configuration; The hardware configuration information represented based on the hierarchical object model includes the hardware information objects.

13. The method according to claim 11, characterized in that The method further comprises: Upon receiving the configuration failure information fed back by the hardware layer, the data synchronization component sends a transaction rollback request to the database and configuration recovery information to the hardware layer; The database undoes the modification to the hardware information of the hardware device based on the received transaction rollback request and restores the hardware information to the hardware information before the configuration; The hardware layer restores the hardware device to a state before configuration based on the received configuration restoration information.

14. An electronic device, characterized in that: The electronic device comprises: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 10 to 13.

Images