CN110417566B - Multi-head configuration method, device and system - Google Patents

Multi-head configuration method, device and system Download PDF

Info

Publication number
CN110417566B
CN110417566B CN201810393998.4A CN201810393998A CN110417566B CN 110417566 B CN110417566 B CN 110417566B CN 201810393998 A CN201810393998 A CN 201810393998A CN 110417566 B CN110417566 B CN 110417566B
Authority
CN
China
Prior art keywords
target data
forwarding
management device
management
forwarding device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810393998.4A
Other languages
Chinese (zh)
Other versions
CN110417566A (en
Inventor
冯冲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201810393998.4A priority Critical patent/CN110417566B/en
Publication of CN110417566A publication Critical patent/CN110417566A/en
Application granted granted Critical
Publication of CN110417566B publication Critical patent/CN110417566B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

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

Abstract

The embodiment of the application discloses a multi-head configuration method, equipment and a system, wherein the method comprises the following steps: the forwarding equipment receives a configuration request sent by first management equipment, wherein the configuration request is used for configuring target data on the forwarding equipment; the forwarding equipment acquires the configuration authority level of the first management equipment; the forwarding equipment acquires the configuration authority level of the second management equipment corresponding to the target data; when the configuration authority level of the first management equipment is higher than that of the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request; and when the configuration authority level of the first management device is lower than that of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request. The embodiment of the application can solve the problem of data conflict caused by the fact that a plurality of management devices are configured with the target data on the same forwarding device in parallel.

Description

Multi-head configuration method, device and system
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a multi-head configuration method, equipment and a system.
Background
In the technical context of Network management or Software Defined Networking (SDN), multi-head configuration of data on a forwarding device by multiple management devices is common. In general, a plurality of management devices may configure data on a forwarding device, and the forwarding device may record the configuration of the data by the plurality of management devices. In the following, for the sake of brevity, a management device that configures data on a forwarding device for important traffic is referred to as an important management device, and a management device that configures data on a forwarding device for general traffic is referred to as a general management device.
At present, if a plurality of management devices configure the same data on the forwarding device, it is possible that a common management device configures data belonging to an important management device, and thus an important service on the important management device cannot normally operate.
For example, it is assumed that the management device a is a management device that configures target data on a forwarding device for an important service X, that is, the management device a is an important management device, and the management device B is a management device that configures target data on a forwarding device for a normal service Y, that is, the management device B is a normal management device. The management device A configures target data on the forwarding device in a first configuration mode so that the target data meets the requirement of the important service X, and the forwarding device records the configuration condition of the management device A on the target data; then, the management device B configures the target data on the forwarding device in the second configuration manner, so that the target data meets the requirement of the common service Y, and the forwarding device may also record the configuration condition of the management device B on the target data. If the target data configured by the second configuration mode is also applicable to the important service X, the important service X and the common service Y can both run normally; if the target data configured by the second configuration mode is not suitable for the important service X, the important service X is affected, and problems such as abnormal operation or errors of the important service X may be caused.
As can be seen from the above example, the common management device may reconfigure the target data configured by the important management device on the forwarding device based on the service requirement of the common management device, so that the target data on the forwarding device cannot be adapted to the service requirement on the important management device, and further the important service on the important management device cannot operate normally or an error occurs. Therefore, the existing multi-head configuration method cannot avoid that the target data configured on the forwarding device by the important management device is reconfigured by the ordinary management device, so the related art described above lacks a protection mechanism for the target data configured on the forwarding device by the important management device.
Disclosure of Invention
The embodiment of the application provides a multi-head configuration method, device and system, so as to solve the problem of data collision caused by parallel configuration of target data on the same forwarding device by a plurality of management devices.
The embodiment of the application is realized as follows:
in a first aspect, an embodiment of the present application provides a multi-head configuration method, where the method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, the plurality of management devices include a first management device and a second management device, and the method includes:
the forwarding equipment receives a configuration request sent by first management equipment, wherein the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment acquires the configuration authority level of the first management equipment;
the forwarding equipment acquires the configuration authority level of the second management equipment corresponding to the target data;
when the configuration authority level of the first management equipment is higher than that of the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request;
and when the configuration authority level of the first management device is lower than that of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a first aspect, a plurality of management devices have respective corresponding configuration permission levels, when a first management device needs to configure target data belonging to a second management device, a forwarding device needs to determine whether the configuration permission level of the first management device is higher than that of the second management device, if so, the forwarding device will configure the target data on the forwarding device according to a configuration request, which indicates that the first management device is qualified to modify the target data; otherwise, the first management device is not qualified to modify the target data, and the forwarding device refuses to configure the target data on the forwarding device according to the configuration request. Therefore, the plurality of management devices provided in the embodiment of the present application have respective corresponding configuration permission levels, so that the management device with a higher configuration permission level can configure the target data belonging to the management device with a lower configuration permission level, and the management device with a lower configuration permission level cannot configure the target data belonging to the management device with a higher configuration permission level, thereby ensuring that the target data on the forwarding device better meets the service requirement of the management device with a higher configuration permission level.
In a technical scenario where the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the following two implementation manners may be available.
In a first implementation manner, when the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the forwarding device configures target data on the forwarding device according to the configuration request.
In a first implementation manner, in a case where the forwarding device is configured in advance that the configuration authority levels of the two management devices are equal, the target data belonging to the other management device can be configured between the two management devices.
In a second implementation manner, when the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a second implementation manner, when the forwarding device is configured in advance that the configuration authority levels of the two management devices are equal, the target data belonging to the other management device cannot be configured between the two management devices.
In a possible implementation manner, the obtaining, by the forwarding device, the configuration permission level of the first management device includes:
the forwarding device acquires a session identifier establishing a first session with the first management device, acquires a first user identifier corresponding to the session identifier, and acquires a configuration permission level of the first management device according to the first user identifier and the configuration permission levels corresponding to the plurality of management devices stored in the forwarding device;
alternatively, the first and second electrodes may be,
the forwarding equipment acquires a user name used for establishing a first session with the first management equipment, determines the user name of the first session as a first user identifier, and determines a configuration authority level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
and the forwarding equipment extracts the first user identification in the configuration request, and determines the configuration permission level corresponding to the first user identification.
The embodiment of the application provides three ways for the forwarding device to obtain the configuration permission level of the first management device.
In the first manner, the first management device may add a first user identifier for indicating an identity of the first management device to a message for establishing the first session, and the forwarding device needs to establish a correspondence between the first user identifier and a session identifier of the first session, and the forwarding device stores in advance a correspondence between user identifiers of a plurality of management devices and configuration permission levels, so that the forwarding device may find the first user identifier according to the session identifier of the first session and find the configuration permission level according to the first user identifier.
In the second mode, the forwarding device determines the user name used for establishing the first session with the first management device as the first user identifier, so that the first management device does not need to additionally send the first user identifier to the forwarding device, thereby saving the transmission resource of the first session.
In a third manner, the first management device directly adds the first user identifier to the configuration request, so that the forwarding device can directly extract the first user identifier from the configuration request, and then the forwarding device finds the configuration permission level corresponding to the first user identifier by using the pre-stored correspondence between the user identifiers of the multiple management devices and the configuration permission level.
In one possible implementation, the method further includes:
the forwarding equipment receives a message sent by first management equipment, wherein the message is used for establishing a first session and comprises a first user identifier;
the forwarding equipment obtains a session identifier of a first session;
the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier.
The first management device in the embodiment of the present application may put the first user identifier into a message for establishing the first session, and send the message to the forwarding device, so that the forwarding device obtains the session identifier of the first session, and establishes a corresponding relationship between the session identifier of the first session and the first user identifier, so that the embodiment of the present application is more suitable for a technical scenario in which a plurality of management devices share the same user identifier.
In a possible implementation manner, the obtaining, by the forwarding device, the configuration permission level of the second management device corresponding to the target data includes:
the forwarding equipment acquires a second user identifier of second management equipment corresponding to the target data;
and the forwarding equipment determines the configuration authority level corresponding to the second user identification of the second management equipment.
The forwarding device stores the corresponding relationship between the data and the user identifiers of the management devices and the configuration permission levels corresponding to the user identifiers of the management devices, so that the forwarding device can determine the second management device corresponding to the target data according to the corresponding relationship between the data and the user identifiers of the management devices, and can determine the configuration permission level corresponding to the second user identifier of the second management device according to the configuration permission levels corresponding to the user identifiers of the management devices, so that the forwarding device can obtain the configuration permission level of the second management device corresponding to the target data.
In one possible implementation, after the forwarding device configures the target data on the forwarding device according to the configuration request, the method further includes:
the forwarding equipment establishes a corresponding relation between the target data and the first management equipment;
the forwarding device deletes the correspondence between the target data and the second management device.
After the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device stores the corresponding relationship between the target data and the second management device. Since the configuration request is sent by the first management device to the forwarding device, that is, the forwarding device modifies the target data according to the request of the first management device, after the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device needs to establish a corresponding relationship between the target data and the first management device. Moreover, since the target data has already been configured by the first management device, and the target data is no longer attributed to the second management device, the forwarding device needs to delete the corresponding relationship between the target data and the second management device, so as to ensure that the corresponding relationship between the target data in the forwarding device and the first management device is unique, and the target data in the forwarding device no longer has a corresponding relationship with other management devices.
In one possible implementation, after the forwarding device configures the target data on the forwarding device according to the configuration request, the method further includes:
the forwarding device establishes a corresponding relationship between the target data and the first management device.
The forwarding device does not need to delete the corresponding relationship between the target data and the second management device, that is, the forwarding device maintains the configuration history information of the target data. For example, the correspondence relationship among one target data, the management apparatuses in which the target data has been historically configured, and the configuration authority levels corresponding to the respective management apparatuses is maintained. By maintaining the target data configuration history information, the forwarding device can well know which management devices have configured the target data historically and the configuration authority levels of the management devices.
In one possible implementation, after the forwarding device configures the target data on the forwarding device according to the configuration request, the method further includes:
the forwarding equipment acquires a notification subscription list corresponding to the target data;
the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, and the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
The target management device is a management device which needs to know that the target data in the forwarding device is reconfigured, and the number of the target management devices is at least one. The target management device may obtain the notification about the target data change sent by the forwarding device only after sending a subscription request for the target data change to the forwarding device. After the forwarding device receives a subscription request for target data sent by the target management device, the forwarding device extracts the user identifier of the target management device in the subscription request and the target data to be subscribed, and adds the user identifier of the target management device in the subscription request to a notification subscription list corresponding to the target data. If the target data in the forwarding device is reconfigured by the management device, the forwarding device finds the corresponding target management device according to the user identifier in the notification subscription list, and sends a change notification of the target data to the target management device, where the change notification may include the user identifier of the first management device, the configuration path of the target data, and the configuration parameter of the target data. Therefore, after the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device further needs to send a change notification of the target data to at least one target management device in the notification subscription list, so that the at least one target management device subscribed with the target data can know the configuration condition of the target data.
In a possible implementation manner, after the forwarding device receives the configuration request sent by the first management device, the method further includes:
the forwarding equipment judges whether target data are stored on the forwarding equipment or not;
when the target data is stored in the forwarding equipment, executing a step of acquiring the configuration authority level of the first management equipment by the forwarding equipment;
when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device extracts target data in the configuration request, and then the forwarding device judges whether the target data is stored on the forwarding device. If the forwarding device does not store the target data, it indicates that no management device has configured the target data on the forwarding device before, so the first management device is the management device that configured the target data on the forwarding device for the first time, so the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
In a possible implementation manner, after the forwarding device obtains the configuration permission level of the second management device corresponding to the target data, the method further includes:
the forwarding device judges whether the first management device is the same as the second management device;
when the first management equipment is the same as the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request;
when the first management device is different from the second management device, the forwarding device judges whether the configuration authority level of the first management device is higher than that of the second management device.
The forwarding device may determine whether the user identifier of the first management device is the same as the user identifier of the second management device. If the user identifier of the first management device is the same as the user identifier of the second management device, it indicates that the first management device and the second management device belong to the same user, and the first management device is qualified to configure the target data on the forwarding device, so that the forwarding device does not need to compare the configuration permission level of the first management device with the configuration permission level of the second management device, and the forwarding device can directly configure the target data on the forwarding device according to the configuration request; if the user identifier of the first management device is different from the user identifier of the second management device, it indicates that the first management device and the second management device belong to different users, and the forwarding device needs to determine whether the configuration permission level of the first management device is higher than that of the second management device, so as to determine whether to configure target data on the forwarding device according to the configuration request.
In a possible implementation manner, after the forwarding device receives the configuration request sent by the first management device, the method further includes:
judging whether a second management device corresponding to the target data has a configuration authority level or not;
when the second management equipment corresponding to the target data has the configuration authority level, executing a step of acquiring the configuration authority level of the first management equipment by the forwarding equipment;
and when the second management equipment corresponding to the target data does not have the configuration authority level, the forwarding equipment refuses to configure the target data on the forwarding equipment according to the configuration request.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device needs to determine whether the second management device corresponding to the target data has the configuration permission level, and if the second management device corresponding to the target data does not have the configuration permission level, it indicates that the target data is not allowed to be reconfigured by any management device, so that the forwarding device will refuse to configure the target data on the forwarding device according to the configuration request.
In a second aspect, an embodiment of the present application provides another multi-head configuration method, where the method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, and the plurality of management devices includes a first management device and a second management device, and the method includes:
the forwarding equipment receives a configuration request sent by first management equipment, wherein the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment acquires a first user identifier of first management equipment;
the forwarding equipment acquires a second user identifier of second management equipment corresponding to the target data;
when the first user identification is the same as the second user identification, the forwarding equipment configures target data on the forwarding equipment according to the configuration request;
and when the first user identification is different from the second user identification, the forwarding equipment refuses to configure the target data on the forwarding equipment according to the configuration request.
When the first management device needs to configure target data belonging to the second management device, the forwarding device needs to judge whether the first user identifier is the same as the second user identifier, if so, the first management device and the second management device belong to the same user, and the first management device has the qualification of modifying the target data, so that the forwarding device configures the target data on the forwarding device according to the configuration request; otherwise, it indicates that the first management device and the second management device belong to different users, and the first management device does not have the qualification for modifying the target data, then the forwarding device will refuse to configure the target data on the forwarding device according to the configuration request. Therefore, the forwarding device provided in the embodiment of the present application only allows the management device to configure the target data that belongs to the forwarding device, and does not allow the management device to configure the target data that does not belong to the forwarding device, so that it is possible to avoid that multiple management devices configure the target data on the forwarding device at will.
In a possible implementation manner, the obtaining, by the forwarding device, the first subscriber identity of the first management device includes:
the forwarding equipment acquires a session identifier for establishing a first session with the first management equipment, and acquires a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the forwarding equipment acquires a user name used for establishing a first session with the first management equipment, and determines the user name of the first session as a first user identifier;
alternatively, the first and second electrodes may be,
the forwarding device extracts the first subscriber identity in the configuration request.
The embodiment of the application provides three ways for the forwarding device to obtain the configuration permission level of the first management device.
In the first manner, the first management device may add a first user identifier for indicating an identity of the first management device to a packet for establishing the first session, and the forwarding device needs to establish a correspondence between the first user identifier and the session identifier of the first session, so that the forwarding device may find the first user identifier according to the session identifier of the first session.
In the second mode, the forwarding device determines the user name used for establishing the first session with the first management device as the first user identifier, so that the first management device does not need to additionally send the first user identifier to the forwarding device, thereby saving the transmission resource of the first session.
In a third manner, the first management device directly adds the first user identifier to the configuration request, so that the forwarding device can directly extract the first user identifier from the configuration request.
In a possible implementation manner, before the forwarding device obtains the session identifier for establishing the first session with the first management device, the method further includes:
the forwarding equipment receives a message sent by first management equipment, wherein the message is used for establishing a first session and comprises a first user identifier;
the forwarding equipment obtains a session identifier of a first session;
the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier.
The first management device in the embodiment of the present application may put the first user identifier into a message for establishing the first session, and send the message to the forwarding device, so that the forwarding device obtains the session identifier of the first session, and establishes a corresponding relationship between the session identifier of the first session and the first user identifier, so that the embodiment of the present application is more suitable for a technical scenario in which a plurality of management devices share the same user identifier.
In a possible implementation manner, after the forwarding device receives the configuration request sent by the first management device, the method further includes:
the forwarding equipment judges whether target data are stored on the forwarding equipment or not;
when the target data is stored in the forwarding equipment, executing a step of acquiring a first user identifier of first management equipment by the forwarding equipment;
when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, acquires the first user identifier of the first management device, and establishes a corresponding relationship between the target data and the first user identifier.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device extracts target data in the configuration request, and then the forwarding device judges whether the target data is stored on the forwarding device. If the forwarding device does not store the target data, it indicates that no management device has configured the target data on the forwarding device before, so the first management device is the management device that configured the target data on the forwarding device for the first time, so the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
In a third aspect, an embodiment of the present application provides a forwarding device, where the forwarding device is applied to a first network, the first network includes a plurality of management devices and the forwarding device, data of the forwarding device may be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, the plurality of management devices include a first management device and a second management device, and the forwarding device includes:
the first receiving module is used for receiving a configuration request sent by the first management device, wherein the configuration request is used for configuring target data on the forwarding device;
the first acquisition module is used for acquiring the configuration authority level of the first management equipment;
the second acquisition module is used for acquiring the configuration authority level of the second management equipment corresponding to the target data;
the configuration module is used for configuring target data on the forwarding equipment according to the configuration request when the configuration authority level of the first management equipment is higher than that of the second management equipment; and when the configuration authority level of the first management device is lower than that of the second management device, refusing to configure the target data on the forwarding device according to the configuration request.
In a possible implementation manner, the first obtaining module is specifically configured to obtain a session identifier for establishing a first session with a first management device, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device according to the first user identifier and configuration permission levels corresponding to a plurality of management devices stored in the first user identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically used for obtaining a user name used for establishing a first session with the first management device, determining the user name of the first session as a first user identifier, and determining a configuration authority level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to extract a first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier.
In one possible implementation, the forwarding device further includes:
the second receiving module is used for receiving a message sent by the first management device, wherein the message is used for establishing a first session and comprises a first user identifier;
an obtaining module, configured to obtain a session identifier of a first session;
the first establishing module is used for establishing the corresponding relation between the session identifier of the first session and the first user identifier.
In a possible implementation manner, the second obtaining module is specifically configured to obtain a second user identifier of the second management device corresponding to the target data; and determining a configuration authority level corresponding to a second user identification of the second management equipment.
In one possible implementation, the forwarding device further includes:
the second establishing module is used for establishing the corresponding relation between the target data and the first management equipment;
and the deleting module is used for deleting the corresponding relation between the target data and the second management equipment.
In one possible implementation, the forwarding device further includes:
the third acquisition module is used for acquiring a notification subscription list corresponding to the target data;
and the sending module is used for sending a change notification of the target data to at least one target management device in the notification subscription list, wherein the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
In one possible implementation, the forwarding device further includes:
the first judgment module is used for judging whether the forwarding equipment stores target data or not; when target data are stored in the forwarding equipment, triggering a first acquisition module; and when the target data is not stored in the forwarding equipment, configuring the target data on the forwarding equipment according to the configuration request, and establishing a corresponding relation between the target data and the first management equipment.
In one possible implementation, the forwarding device further includes:
the second judging module is used for judging whether the first management equipment is the same as the second management equipment or not; when the first management equipment is the same as the second management equipment, configuring target data on the forwarding equipment according to the configuration request; and when the first management device is different from the second management device, judging whether the configuration authority level of the first management device is higher than that of the second management device.
In one possible implementation, the forwarding device further includes:
the third judging module is used for judging whether the second management equipment corresponding to the target data has the configuration permission level or not; when the second management equipment corresponding to the target data has the configuration authority level, triggering a first acquisition module; and when the second management device corresponding to the target data does not have the configuration authority level, refusing to configure the target data on the forwarding device according to the configuration request.
In a fourth aspect, an embodiment of the present application provides another forwarding device, where the forwarding device is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, the plurality of management devices includes a first management device and a second management device, and the forwarding device includes:
the first receiving module is used for receiving a configuration request sent by the first management device, wherein the configuration request is used for configuring target data on the forwarding device;
the first acquisition module is used for acquiring a first user identifier of first management equipment;
the second obtaining module is used for obtaining a second user identifier of second management equipment corresponding to the target data;
the configuration module is used for configuring target data on the forwarding equipment according to the configuration request when the first user identification is the same as the second user identification; and when the first user identification is different from the second user identification, refusing to configure the target data on the forwarding equipment according to the configuration request.
In a possible implementation manner, the first obtaining module is specifically configured to obtain a session identifier for establishing a first session with the first management device, and obtain a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to obtain a user name used for establishing a first session with the first management device, and determine that the user name of the first session is a first user identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to extract the first user identifier in the configuration request.
In one possible implementation, the forwarding device further includes:
the second receiving module is used for receiving a message sent by the first management device, wherein the message is used for establishing a first session and comprises a first user identifier;
an obtaining module, configured to obtain a session identifier of a first session;
and the establishing module is used for establishing the corresponding relation between the session identifier of the first session and the first user identifier.
In one possible implementation, the forwarding device further includes:
the judging module is used for judging whether the target data is stored on the forwarding equipment; when target data are stored in the forwarding equipment, triggering a first acquisition module; when the target data is not stored in the forwarding device, the target data on the forwarding device is configured according to the configuration request, the first user identifier corresponding to the first management device is determined, and the corresponding relation between the target data and the first user identifier is established.
In a fifth aspect, an embodiment of the present application provides a multi-head configuration system, where the system includes multiple management devices and a forwarding device, data of the forwarding device may be configured by the multiple management devices, the multiple management devices have respective corresponding configuration authority levels, and the multiple management devices include a first management device and a second management device; wherein the content of the first and second substances,
the first management equipment is used for sending a configuration request to the forwarding equipment, and the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment is used for receiving a configuration request sent by the first management equipment; acquiring the configuration authority level of first management equipment; acquiring a configuration authority level of second management equipment corresponding to the target data; when the configuration authority level of the first management equipment is higher than that of the second management equipment, configuring target data on the forwarding equipment according to the configuration request; and when the configuration authority level of the first management device is lower than that of the second management device, refusing to configure the target data on the forwarding device according to the configuration request.
In a possible implementation manner, the forwarding device is specifically configured to obtain a session identifier for establishing a first session with the first management device, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device according to the first user identifier and configuration permission levels corresponding to multiple management devices stored in the forwarding device;
alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to acquire a user name used for establishing a first session with the first management device, determine the user name of the first session as a first user identifier, and determine a configuration permission level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
and the forwarding device is specifically configured to extract the first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier.
In a possible implementation manner, the forwarding device is further configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier; obtaining a session identifier of a first session; and establishing a corresponding relation between the session identification of the first session and the first user identification.
In a possible implementation manner, the forwarding device is further configured to obtain a notification subscription list corresponding to the target data; and sending a change notification of the target data to at least one target management device in the notification subscription list, wherein the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
In a sixth aspect, an embodiment of the present application provides another multi-head configuration system, where the system includes multiple management devices and a forwarding device, data of the forwarding device may be configured by the multiple management devices, and the multiple management devices include a first management device and a second management device; wherein the content of the first and second substances,
the first management equipment is used for sending a configuration request to the forwarding equipment, and the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment is used for receiving a configuration request sent by the first management equipment; acquiring a first user identifier of first management equipment; acquiring a second user identifier of second management equipment corresponding to the target data; when the first user identification is the same as the second user identification, configuring target data on the forwarding equipment according to the configuration request; and when the first user identification is different from the second user identification, refusing to configure the target data on the forwarding equipment according to the configuration request.
In a possible implementation manner, the forwarding device is specifically configured to obtain a session identifier for establishing a first session with the first management device, and obtain a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to acquire a user name used for establishing a first session with the first management device, and determine that the user name of the first session is a first user identifier;
alternatively, the first and second electrodes may be,
and the forwarding device is specifically configured to extract the first user identifier in the configuration request.
In a possible implementation manner, the forwarding device is further configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier; obtaining a session identifier of a first session; and establishing a corresponding relation between the session identification of the first session and the first user identification.
In a seventh aspect, an embodiment of the present application provides a further multi-head configuration method, where the method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, the plurality of management devices includes a first management device, and the method includes:
the first management device sends a configuration request to the forwarding device, wherein the configuration request is used for configuring target data on the forwarding device.
In an eighth aspect, an embodiment of the present application provides a further multi-head configuration method, where the method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, the plurality of management devices include a first management device and a second management device, and the method includes:
the first management equipment sends a configuration request to the forwarding equipment, wherein the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment receives a configuration request sent by first management equipment;
the forwarding equipment acquires the configuration authority level of the first management equipment;
the forwarding equipment acquires the configuration authority level of the second management equipment corresponding to the target data;
when the configuration authority level of the first management equipment is higher than that of the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request;
and when the configuration authority level of the first management device is lower than that of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a ninth aspect, an embodiment of the present application provides another multi-head configuration method, where the method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device may be configured by the plurality of management devices, and the plurality of management devices includes a first management device and a second management device, and the method includes:
the first management equipment sends a configuration request to the forwarding equipment, wherein the configuration request is used for configuring target data on the forwarding equipment;
the forwarding equipment receives a configuration request sent by first management equipment;
the forwarding equipment acquires a first user identifier of first management equipment;
the forwarding equipment acquires a second user identifier of second management equipment corresponding to the target data;
when the first user identification is the same as the second user identification, the forwarding equipment configures target data on the forwarding equipment according to the configuration request;
and when the first user identification is different from the second user identification, the forwarding equipment refuses to configure the target data on the forwarding equipment according to the configuration request.
In a tenth aspect, embodiments of the present application provide a further forwarding device, which includes a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver communicate with each other through an internal connection path, the memory is configured to store instructions, the processor is configured to execute the instructions stored in the memory to control the transceiver to receive and transmit signals, and when the processor executes the instructions stored in the memory, the processor executes the method in the first aspect or any possible implementation manner of the first aspect.
In an eleventh aspect, the present embodiments provide a further forwarding device, which includes a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver communicate with each other through an internal connection path, the memory is configured to store instructions, the processor is configured to execute the instructions stored in the memory to control the transceiver to receive and transmit signals, and when the processor executes the instructions stored in the memory, the processor executes the method in any possible implementation manner of the second aspect or the second aspect.
In a twelfth aspect, embodiments of the present application provide a management device, which includes a processor, a memory, and a transceiver, wherein the processor, the memory, and the transceiver communicate with each other through an internal connection path, the memory is used for storing instructions, the processor is used for executing the instructions stored in the memory to control the transceiver to receive and transmit signals, and when the processor executes the instructions stored in the memory, the processor executes the method in the seventh aspect.
In a thirteenth aspect, embodiments of the present application provide a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method of the first aspect or any of the possible implementations of the first aspect.
In a fourteenth aspect, the present application provides another computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method of the second aspect or any of the possible implementations of the second aspect.
In a fifteenth aspect, the present application provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the method in the seventh aspect.
In a sixteenth aspect, embodiments of the present application provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method of the first aspect or any of the possible implementations of the first aspect.
In a seventeenth aspect, the present application provides another computer program product containing instructions, which when executed on a computer, causes the computer to perform the method of the second aspect or any possible implementation manner of the second aspect.
In an eighteenth aspect, embodiments of the present application provide a further computer program product containing instructions, which when run on a computer, cause the computer to perform the method in the seventh aspect.
In a nineteenth aspect, embodiments of the present application provide a chip, where the chip includes a processor and/or program instructions, and when the chip runs, the method in the first aspect or any one of the possible implementation manners of the first aspect is implemented.
In a twentieth aspect, embodiments of the present application provide another chip, where the chip includes a processor and/or program instructions, and when the chip runs, the method in any possible implementation manner of the second aspect or the second aspect is implemented.
In a twenty-first aspect, embodiments of the present application provide a further chip, where the chip includes a processor and/or program instructions, and when the chip runs, the method in the seventh aspect is implemented.
Drawings
Fig. 1 is a schematic diagram illustrating a network architecture provided in an embodiment of the present application;
fig. 2 is a flowchart illustrating a multi-head configuration method according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating another multi-head configuration method according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of a forwarding device according to an embodiment of the present application;
fig. 5 is a schematic diagram of another forwarding device provided in an embodiment of the present application;
fig. 6 is a schematic diagram of a multi-head configuration system according to an embodiment of the present application;
FIG. 7 is a schematic diagram of another multi-head configuration system provided by an embodiment of the present application;
fig. 8 is a schematic diagram of another forwarding device provided in the embodiment of the present application;
fig. 9 is a schematic diagram of another forwarding device provided in the embodiment of the present application.
Detailed Description
Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present disclosure. The network architecture provided by the embodiment of the present application includes a plurality of management devices and a forwarding device 20, where the plurality of management devices include a first management device 11, a second management device 12, a third management device 13, and other management devices, and each management device has a configuration permission level, and the configuration permission levels of the management devices may be the same or different, and specifically, the configuration permission level of each management device may be set according to factors such as the importance levels of the plurality of management devices, the importance levels of services of the plurality of management devices, or the number of services of the plurality of management devices.
Several specific implementations of setting the configuration authority level of each management device are described below.
In the first mode, the configuration authority levels of a plurality of management devices are divided according to the importance degrees of the plurality of management devices.
For example, as shown in fig. 1, it is assumed that the configuration authority levels include a first level, a second level and a third level, where the first level is higher than the second level, and the second level is higher than the third level, and it is assumed that the importance level of the first management device 11 is higher than that of the second management device 12, and the importance levels of the second management device 12 and the third management device 13 are the same, the configuration authority levels of the management devices are set according to the importance levels of the management devices, the configuration authority level of the first management device 11 may be set to the first level, and the configuration authority levels of the second management device 12 and the third management device 13 may be set to the second level.
In the second mode, the configuration authority levels of a plurality of management devices are divided according to the importance degrees of the services of the plurality of management devices.
For example, as shown in fig. 1, it is assumed that the configuration permission levels include a first level, a second level and a third level, where the first level is higher than the second level, and the second level is higher than the third level, and it is assumed that the importance level of the service of the first management device 11 is higher than that of the service of the second management device 12, and the importance level of the service of the second management device 12 is higher than that of the service of the third management device 13, the configuration permission levels of the management devices are set according to the importance levels of the services of the management devices, the configuration permission level of the first management device 11 may be set to the first level, the configuration permission level of the second management device 12 may be set to the second level, and the configuration permission level of the third management device 13 may be set to the third level.
And in the third mode, the configuration permission levels of the management devices are divided according to the service quantity of the management devices.
For example, as shown in fig. 1, it is assumed that the configuration permission levels include a first level, a second level and a third level, where the first level is higher than the second level, and the second level is higher than the third level, and it is assumed that the number of services of the first management device 11 is greater than the number of services of the second management device 12, and the number of services of the second management device 12 is greater than the number of services of the third management device 13, the configuration permission levels of the management devices are set according to the importance levels of the management devices, the configuration permission level of the first management device 11 may be set to the first level, the configuration permission level of the second management device 12 may be set to the second level, and the configuration permission level of the third management device 13 may be set to the third level.
The above-mentioned ways of dividing the configuration permission levels of the plurality of management devices are only alternatives provided by the embodiments of the present application, and are not limited thereto, and other ways of dividing the configuration permission levels of the plurality of management devices may also be adopted.
It should be noted that, the management devices generally refer to those management devices that can perform data configuration on the forwarding device and can control or manage the forwarding device. It will be appreciated that in some particular cases, a forwarding device may not be provided with a configuration permission level even though some or some of the plurality of management devices may perform data configuration and control and manage the forwarding device.
In the embodiment shown in fig. 1, the forwarding device 20 comprises a configuration access layer 21, a configuration framework layer 22 and a database 23. The configuration access layer 21 is configured to establish a connection with a plurality of management devices and process configuration requests sent by the plurality of management devices; the configuration framework layer 22 is responsible for configuring data in the database 23 and exposing a uniform entry to the configuration access layer 21; the database 23 is responsible for storing the data to be configured.
In the embodiment shown in fig. 1, each of the plurality of management devices may send a configuration request to the configuration access layer 21 of the forwarding device 20 to configure the target data on the database 23. Assuming that when the configuration access layer 21 receives a configuration request sent by the first management device 11, the configuration access layer 21 parses target data to be configured in the configuration request, and obtains a configuration permission level of the first management device 11 and a configuration permission level of the second management device 12 corresponding to the target data, where in a specific example, the second management device 12 corresponding to the target data refers to that the target data is configured by the second management device 12 before receiving the configuration request, it can be understood that if tracing back is performed again, the target data may be configured by other management devices, for example, the target data may be configured by the management device 13; the configuration access layer 21 also determines whether the configuration authority level of the first management device 11 is higher than the configuration authority level of the second management device 12 corresponding to the target data, and if so, the configuration access layer 21 sends the configuration request sent by the first management device 11 to the configuration framework layer 22, so that the configuration framework layer 22 configures the target data on the database 23 according to the configuration request; otherwise, the configuration access layer 21 may refuse to configure the target data on the database 23 according to the configuration request, for example, the configuration access layer 21 may send a message to the first management device 11 to refuse to configure the target data according to the configuration request.
In the embodiment shown in fig. 1, the configuration access layer 21 of the forwarding device 20 needs to determine whether the configuration authority level of the first management device 11 is higher than the configuration authority level of the second management device 12 corresponding to the target data, and if so, the configuration access layer 21 sends the configuration request sent by the first management device 11 to the configuration framework layer 22, so that the configuration framework layer 22 can configure the target data in the database 23, and otherwise, the configuration framework layer does not allow the target data in the database 23 to be configured.
In an implementable scenario, there are a number of ways to set the configuration privilege level of a plurality of management devices.
For example, a network administrator may select one management device from a plurality of management devices through a network management platform, and set the selected management device as a super management device, so that the super management device has the capability of setting the configuration authority levels of the plurality of management devices. In an initial state, the super management device can divide the configuration permission levels of a plurality of management devices according to actual service requirements; then, the super management device sends an authority configuration result to the forwarding device, wherein the authority configuration result comprises the configuration authority levels of the management devices; after the forwarding device receives the permission configuration result sent by the super management device, the forwarding device can analyze the configuration permission levels of the multiple management devices in the permission configuration request and store the configuration permission levels of the multiple management devices.
For another example, a network manager may input the configuration authority levels of the plurality of management devices in the forwarding device through the network management platform interface according to actual service requirements, so that the forwarding device stores the configuration authority levels of the plurality of management devices.
Referring to fig. 2, fig. 2 is a flowchart illustrating a multi-head configuration method according to an embodiment of the present application. The method shown in fig. 2 can avoid that a plurality of management devices configure the target data on the forwarding device at will, thereby ensuring that the target data on the forwarding device better meets the service requirement of the management device with a higher configuration authority level. The method is applied to a first network, the first network includes a plurality of management devices and a forwarding device, data of the forwarding device can be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, and the following description takes an example that the plurality of management devices include a first management device and a second management device, and the method includes the following steps.
Step S11, the first management device sends a configuration request to the forwarding device, where the configuration request is used to configure target data on the forwarding device.
The management device mentioned in the embodiments of the present application may be a network manager or a controller. The forwarding device mentioned in the embodiment of the present application may be various network devices such as a router, a switch, or a firewall, and certainly is not limited to this, and in some cases, the forwarding device may also be a network manager or a lower controller. The first network mentioned in the embodiments of the present application may be a wide area network, a data center network, or a campus network.
When the first management device needs to configure target data on the forwarding device in order to implement its own service requirement, the first management device sends a configuration request to the forwarding device. After the forwarding device receives the configuration request, the forwarding device needs to compare the configuration permission level of the first management device with the configuration permission level of the second management device corresponding to the target data, and then determine whether to configure the target data on the forwarding device according to the configuration request based on the comparison result.
It is understood that, before step S11, the second management device has already configured the target data of the forwarding device, so the forwarding device will store the corresponding relationship between the target data and the second management device. Of course, there may be other management devices that have configured the target data before the second management device configures the target data of the forwarding device.
Specific ways of setting the configuration authority levels of a plurality of management devices can be seen in the embodiment shown in fig. 1.
Step S12, the forwarding device receives the configuration request sent by the first management device.
After the first management device sends the configuration request to the forwarding device, the forwarding device receives the configuration request sent by the first management device and analyzes the configuration request to extract the target data and the related information in the configuration request, the related information may include a configuration path and configuration parameters of the target data, the configuration path is used for finding the position of the target data in the forwarding device, and the configuration parameters of the target data are related parameters of the target data to be configured.
For example, assume that the configuration request includes at least the following:
“<top xmlns＝"http://example.com/schema/1.2/config">
<interface>
<name>Ethernet0/0</name>
<mtu>100000</mtu>
</interface>
</top>”
the forwarding device extracts the target data "Ethernet 0/0" from the configuration request, extracts the configuration path "http:// example. com/schema/1.2/config Ethernet 0/0", and extracts the configuration parameter "< mtu >100000</mtu >" of the target data. After the forwarding device extracts the target data, the configuration path, and the configuration parameters of the target data, the forwarding device may find the target data based on the configuration path and configure the target data based on the configuration parameters of the target data in step S15.
Step S13, the forwarding device obtains the configuration authority level of the first management device.
The forwarding device can acquire the configuration authority level of the first management device according to the corresponding relation between the plurality of management devices stored locally in advance and the configuration authority level; the forwarding device may also obtain the configuration permission level of the first management device according to a correspondence between the plurality of management devices stored in the other device and the configuration permission level.
In specific implementation, there are many ways for the forwarding device to obtain the configuration authority level of the first management device, and several specific ways are briefly described below.
In a first manner, the step of acquiring, by the forwarding device, the configuration authority level of the first management device may include the following steps: the forwarding device obtains a session identifier establishing a first session with the first management device, the forwarding device obtains a first user identifier corresponding to the session identifier, and the forwarding device obtains a configuration permission level of the first management device according to the first user identifier and configuration permission levels corresponding to a plurality of management devices stored in the forwarding device.
In the first manner, before step S11, the method shown in fig. 2 may further include the following steps: the forwarding equipment receives a message sent by first management equipment, wherein the message is used for establishing a first session and comprises a first user identifier; the forwarding equipment obtains a session identifier of a first session; the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier.
The message may be a data message or a control message. In addition, there are various ways for the forwarding device to obtain the session identifier of the first session, for example, the forwarding device may generate the session identifier of the first session; for another example, the forwarding device may obtain a session identifier of the first session sent by the first management device.
In a first manner, first, a first management device sends a message to a forwarding device to establish a session connection between the first management device and the forwarding device (hereinafter, the session connection is referred to as a first session), where the message further includes a first user identifier, and the first user identifier is used to indicate an identity of the first management device; secondly, the forwarding device obtains a session identifier of the first session, wherein the session identifier is used for identifying the first session; then, the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier, so that the first user identifier can be found through the session identifier in the subsequent steps; thirdly, after the forwarding device receives the configuration request sent by the first management device, the forwarding device acquires a session identifier for establishing a first session with the first management device; thirdly, the forwarding device prestores a correspondence between the session identifier of the first session and the first user identifier, and the forwarding device may determine the first user identifier corresponding to the session identifier of the first session based on the correspondence; finally, the forwarding device prestores a corresponding relationship between the user identifiers of the plurality of management devices and the configuration permission levels, and the forwarding device can determine the configuration permission level corresponding to the first user identifier based on the corresponding relationship.
In the first manner, the first management device may add a first user identifier for indicating an identity of the first management device to a message for establishing the first session, and the forwarding device needs to establish a correspondence between the first user identifier and a session identifier of the first session, and the forwarding device stores in advance a correspondence between user identifiers of a plurality of management devices and configuration permission levels, so that the forwarding device may find the first user identifier according to the session identifier of the first session and find the configuration permission level according to the first user identifier.
The first mode is more suitable for the technical scene that a plurality of management devices share the same user identifier. For example, the management device a adds the user identifier X to the packet for establishing the first session with the forwarding device H, and the management device B adds the user identifier X to the packet for establishing the second session with the forwarding device H, so that for the forwarding device H, the management device a and the management device B are the same user, and the owned configuration permission levels are the same, so the first manner is more suitable for a technical scenario in which a plurality of management devices share the same user identifier.
In a second manner, the step of acquiring, by the forwarding device, the configuration authority level of the first management device may include the following steps: the forwarding device obtains a user name used for establishing a first session with the first management device, determines the user name of the first session as a first user identifier, and determines a configuration authority level corresponding to the first user identifier.
In the second manner, before step S11, in order for the first management device to establish a session connection with the forwarding device (hereinafter, the session connection is referred to as a first session), the first management device needs to send a login request to the forwarding device, where the login request includes a user name and a password for establishing the session connection. After the forwarding device checks that the user name and the password in the login request are correct, the forwarding device sends a feedback request with correct information to the first management device, and allows a message which is sent by the first management device and used for establishing a first session with the forwarding device. After the first session is established between the first management device and the forwarding device, the first management device sends a configuration request to the forwarding device to configure target data on the forwarding device. At this time, the forwarding device obtains a user name used for establishing the first session with the first management device, determines the user name of the first session as the first user identifier, and then finds the configuration permission level corresponding to the first user identifier by using the pre-stored corresponding relationship between the user identifiers of the multiple management devices and the configuration permission level.
In the second mode, the forwarding device determines the user name used for establishing the first session with the first management device as the first user identifier, so that the first management device does not need to additionally send the first user identifier to the forwarding device, thereby saving the transmission resource of the first session.
The second method is more suitable for a technical scenario that a management device uses a user identifier. For example, before the management device a establishes a session with the forwarding device H, the management device a needs to log in the forwarding device H through the user name 123 and the password 456, and since the forwarding device H uses the user name 123 as the identity of the management device a after the management device a logs in the server using the user name 123, the management device B cannot log in the forwarding device H again using the user name 123, so the second manner is more suitable for a technical scenario in which one management device uses one user identity.
In a third manner, the "forwarding device obtains the configuration permission level of the first management device" may include the following steps: the forwarding device obtains the first user identifier from another interactive message after establishing a session with the management device, for example, the forwarding device may obtain the first user identifier from a configuration request sent to the forwarding device by the management device, and the forwarding device determines a configuration permission level corresponding to the first user identifier.
In a third manner, for example, in the scenario where the first user identifier is obtained through the configuration request, the first management device directly adds the first user identifier to the configuration request, so that the forwarding device can directly extract the first user identifier from the configuration request, and then the forwarding device finds the configuration permission level corresponding to the first user identifier by using the pre-stored correspondence between the user identifiers of the multiple management devices and the configuration permission levels.
The third mode is more suitable for a technical scenario that one management device comprises a plurality of services. For example, the management device a includes a service a1 and a service a2, and when the service a1 of the management device a sends a configuration request to the forwarding device H, the management device a adds the user identifier x1 of the service a1 in the configuration request; when the service a2 of the management device a sends a configuration request to the forwarding device H, the management device a adds the user identifier x2 of the service a2 to the configuration request, so that it can be ensured that each service in one management device cannot change the target data corresponding to other services at will, and therefore the third mode is more suitable for a technical scenario in which one management device includes multiple services.
Step S14, the forwarding device obtains the configuration authority level of the second management device corresponding to the target data.
Since there are many ways for the forwarding device to obtain the configuration permission level of the second management device corresponding to the target data, two specific ways are briefly described below.
In a first manner, the "forwarding device obtains the configuration permission level of the second management device corresponding to the target data", which may include the following steps: the forwarding equipment acquires a second user identifier of second management equipment corresponding to the target data; and the forwarding equipment determines the configuration authority level corresponding to the second user identification of the second management equipment.
In the first mode, since the forwarding device stores therein the corresponding relationship between the target data and the user identifier of the management device and the configuration permission levels corresponding to the user identifiers of the plurality of management devices, the forwarding device may determine the second management device corresponding to the target data according to the corresponding relationship between the target data and the user identifier of the management device, and may determine the configuration permission level corresponding to the second user identifier of the second management device according to the configuration permission levels corresponding to the user identifiers of the plurality of management devices, so that the forwarding device may obtain the configuration permission level of the second management device corresponding to the target data.
In the first mode, the forwarding device stores only the correspondence between the target data and the user identifier of the second management device, and the forwarding device does not store the correspondence between the user identifier of the management device, to which the target data has been historically configured, and the target data.
In a second manner, the "obtaining, by the forwarding device, the configuration permission level of the second management device corresponding to the target data" may include the following steps: the forwarding device acquires a second user identifier of a second management device corresponding to the target data in the historical configuration information, wherein the historical configuration information comprises the corresponding relation between the target data and the user identifiers of the management devices configured with the target data, and the corresponding relation between the target data and the second user identifier of the second management device is the corresponding relation established in the historical configuration information last time; and the forwarding equipment determines the configuration authority level corresponding to the second user identification of the second management equipment.
In the second manner, since the forwarding device stores the historical configuration information, and the historical configuration information includes the corresponding relationship between the target data and the user identifiers of the plurality of management devices configured with the target data, the forwarding device needs to obtain the corresponding relationship established last time in the historical configuration information, that is, obtain the corresponding relationship between the target data and the second user identifier of the second management device, at this time, the forwarding device may obtain the second user identifier of the second management device corresponding to the target data based on the corresponding relationship; then, since the forwarding device stores the configuration permission levels corresponding to the user identifiers of the multiple management devices, the forwarding device may determine the configuration permission level corresponding to the second user identifier of the second management device according to the configuration permission levels corresponding to the user identifiers of the multiple management devices.
And step S15, when the configuration authority level of the first management device is higher than that of the second management device, the forwarding device configures the target data on the forwarding device according to the configuration request.
After the forwarding device obtains the configuration permission level of the first management device and the configuration permission level of the second management device corresponding to the target data, the forwarding device needs to judge that the configuration permission level of the first management device is higher than that of the second management device. If the configuration authority level of the first management device is higher than that of the second management device, which indicates that the first management device is qualified for modifying the target data, the forwarding device configures the target data on the forwarding device according to the configuration request; if the configuration authority level of the first management device is lower than that of the second management device, which indicates that the first management device does not have the qualification for modifying the target data, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
And step S16, when the configuration authority level of the first management device is lower than that of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a technical scenario where the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the following two implementation manners may be available.
In a first implementation manner, when the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the forwarding device configures target data on the forwarding device according to the configuration request.
In a first implementation manner, in a case where the forwarding device is configured in advance that the configuration authority levels of the two management devices are equal, the target data belonging to the other management device can be configured between the two management devices.
For example, assuming that the target data is attributed to the second management device, the forwarding device may allow the first management device to configure the target data if the configuration authority level of the first management device is equal to the configuration authority level of the second management device.
In a second implementation manner, when the configuration permission level of the first management device is equal to the configuration permission level of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a second implementation manner, when the forwarding device is configured in advance that the configuration authority levels of the two management devices are equal, the target data belonging to the other management device cannot be configured between the two management devices.
For example, assuming that the target data is attributed to the second management device, if the configuration authority level of the first management device is equal to the configuration authority level of the second management device, the forwarding device may refuse the first management device to configure the target data.
In the embodiment shown in fig. 2, a plurality of management devices have respective corresponding configuration permission levels, when a first management device needs to configure target data belonging to a second management device, a forwarding device needs to determine whether the configuration permission level of the first management device is higher than that of the second management device, if so, the forwarding device will configure the target data on the forwarding device according to a configuration request, which indicates that the first management device is qualified to modify the target data; otherwise, the first management device is not qualified to modify the target data, and the forwarding device refuses to configure the target data on the forwarding device according to the configuration request. Therefore, the forwarding device provided in the embodiment of the present application may pre-store the configuration permission levels corresponding to the multiple management devices, so that the management device with the higher configuration permission level may configure the target data belonging to the management device with the lower configuration permission level, and the management device with the lower configuration permission level may not configure the target data belonging to the management device with the higher configuration permission level, thereby ensuring that the target data on the forwarding device better meets the service requirement of the management device with the higher configuration permission level.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device configures the target data on the forwarding device according to the configuration request" in step S15, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding equipment establishes a corresponding relation between the target data and the first management equipment; the forwarding device deletes the correspondence between the target data and the second management device.
Before the forwarding device configures the target data, the forwarding device stores the corresponding relationship between the target data and the second management device because the target data is configured by the second management device before. After the forwarding device reconfigures the target data according to the first management device, since the configuration request is sent to the forwarding device by the first management device, that is, the forwarding device modifies the target data according to the configuration request of the first management device, after the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device needs to establish a corresponding relationship between the target data and the first management device. Moreover, since the target data has already been configured by the first management device, and the target data is no longer attributed to the second management device, the forwarding device needs to delete the corresponding relationship between the target data and the second management device, so as to ensure that the corresponding relationship between the target data in the forwarding device and the first management device is unique, and the target data in the forwarding device no longer has a corresponding relationship with other management devices.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device configures the target data on the forwarding device according to the configuration request" in step S15, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding device establishes a corresponding relationship between the target data and the first management device.
It can be understood that, in the embodiment of the present application, the forwarding device does not need to delete the corresponding relationship between the target data and the second management device, that is, the forwarding device maintains the configuration history information of the target data. For example, the correspondence relationship among one target data, the management apparatuses in which the target data has been historically configured, and the configuration authority levels corresponding to the respective management apparatuses is maintained. By maintaining the target data configuration history information, the forwarding device can well know which management devices have configured the target data historically and the configuration authority levels of the management devices.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device configures the target data on the forwarding device according to the configuration request" in step S15, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding equipment acquires a notification subscription list corresponding to the target data; the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, and the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
The target management device is a management device which needs to know that the target data in the forwarding device is reconfigured, and the number of the target management devices is at least one. The target management device may obtain the notification about the target data change sent by the forwarding device only after sending a subscription request for the target data change to the forwarding device. After the forwarding device receives a subscription request for target data sent by the target management device, the forwarding device extracts the user identifier of the target management device in the subscription request and the target data to be subscribed, and adds the user identifier of the target management device in the subscription request to a notification subscription list corresponding to the target data. If the target data in the forwarding device is reconfigured by the management device, the forwarding device finds the corresponding target management device according to the user identifier in the notification subscription list, and sends a change notification of the target data to the target management device, where the change notification may include the user identifier of the first management device, the configuration path of the target data, and the configuration parameter of the target data. Therefore, after the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device further needs to send a change notification of the target data to at least one target management device in the notification subscription list, so that the at least one target management device subscribed with the target data can know the configuration condition of the target data.
It is to be understood that the notification that the target data is reconfigured may also obtain which management devices the target data has been configured by according to the above-mentioned target data configuration history information, and then notify the corresponding management devices. In a specific implementation, the target data after reconfiguration may be notified to the management devices through a session reestablished with the management devices or a session maintained.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device configures the target data on the forwarding device according to the configuration request" in step S15, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding equipment acquires a notification subscription list corresponding to the target data; the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, wherein the at least one target management device is a management device configured with the target data.
The target management device is a management device configured with target data, and the number of the target management devices is at least one. The forwarding device records the user identifier of each target management device configured with the target data, and adds the user identifier of the target management device to a notification subscription list corresponding to the target data. If the target data in the forwarding device is reconfigured by any management device, the forwarding device finds the corresponding at least one target management device according to the at least one user identifier in the notification subscription list, and sends a change notification of the target data to the at least one target management device, where the change notification may include the user identifier of the first management device, a configuration path of the target data, and a configuration parameter of the target data. Therefore, after the forwarding device configures the target data on the forwarding device according to the configuration request, the forwarding device further needs to send a change notification of the target data to at least one target management device in the notification subscription list, so that the at least one target management device configured with the target data can know the configuration condition of the target data.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device receives the configuration request sent by the first management device" in step S12, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding equipment judges whether target data are stored on the forwarding equipment or not; when the target data is stored in the forwarding equipment, executing a step of acquiring the configuration authority level of the first management equipment by the forwarding equipment; when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device extracts target data in the configuration request, and then the forwarding device judges whether the target data is stored on the forwarding device. If the forwarding device does not store the target data, it indicates that no management device has configured the target data on the forwarding device before, so the first management device is the management device that configured the target data on the forwarding device for the first time, so the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
In the embodiment shown in fig. 2, in an optional scheme, after "the forwarding device obtains the configuration authority level of the second management device corresponding to the target data" in step S14, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding device judges whether the first management device is the same as the second management device; when the first management equipment is the same as the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request; when the first management device is different from the second management device, the forwarding device judges whether the configuration authority level of the first management device is higher than that of the second management device.
The forwarding device may determine whether the user identifier of the first management device is the same as the user identifier of the second management device. If the user identifier of the first management device is the same as the user identifier of the second management device, it indicates that the first management device and the second management device belong to the same user, and the first management device is qualified to configure the target data on the forwarding device, so that the forwarding device does not need to compare the configuration permission level of the first management device with the configuration permission level of the second management device, and the forwarding device can directly configure the target data on the forwarding device according to the configuration request; if the user identifier of the first management device is different from the user identifier of the second management device, it indicates that the first management device and the second management device belong to different users, and the forwarding device needs to determine whether the configuration permission level of the first management device is higher than that of the second management device, so as to determine whether to configure target data on the forwarding device according to the configuration request.
In the embodiment shown in fig. 2, in an alternative scheme, after "the forwarding device receives the configuration request sent by the first management device" in step S12, the scheme provided in the embodiment of the present application may further include the following steps: judging whether a second management device corresponding to the target data has a configuration authority level or not; when the second management device corresponding to the target data has the configuration authority level, executing step S13; and when the second management equipment corresponding to the target data does not have the configuration authority level, the forwarding equipment refuses to configure the target data on the forwarding equipment according to the configuration request.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device needs to determine whether the second management device corresponding to the target data has the configuration permission level, and if the second management device corresponding to the target data does not have the configuration permission level, it indicates that the target data is not allowed to be reconfigured by any management device, so that the forwarding device will refuse to configure the target data on the forwarding device according to the configuration request.
Referring to fig. 3, fig. 3 is a flowchart illustrating another multi-head configuration method according to an embodiment of the present application. The method shown in fig. 3 can ensure that the target data on the forwarding device can only be reconfigured by the management device corresponding to the target data, and further, can prevent a plurality of management devices from configuring the target data on the forwarding device at will. The method is applied to a first network, the first network comprises a plurality of management devices and a forwarding device, data of the forwarding device can be configured by the plurality of management devices, and the plurality of management devices comprise a first management device and a second management device.
Step S21, the first management device sends a configuration request to the forwarding device, where the configuration request is used to configure target data on the forwarding device.
The management device mentioned in the embodiments of the present application may be a network manager or a controller. The forwarding device mentioned in the embodiment of the present application may be various network devices such as a router, a switch, or a firewall, and certainly is not limited to this, and in some cases, the forwarding device may also be a network manager or a lower controller. The first network mentioned in the embodiments of the present application may be the internet or a mobile network.
When the first management device needs to configure target data on the forwarding device in order to implement its own service requirement, the first management device sends a configuration request to the forwarding device. After the forwarding device receives the configuration request, the forwarding device needs to compare whether the first user identifier of the first management device is the same as the second user identifier of the second management device corresponding to the target data, if so, it indicates that the first management device and the second management device are the same management device, and the forwarding device can configure the target data on the forwarding device according to the configuration request.
Step S22, the forwarding device receives the configuration request sent by the first management device.
After the first management device sends the configuration request to the forwarding device, the forwarding device receives the configuration request sent by the first management device and analyzes the configuration request to extract the target data and the related information in the configuration request, the related information may include a configuration path and configuration parameters of the target data, the configuration path is used for finding the position of the target data in the forwarding device, and the configuration parameters of the target data are related parameters of the target data to be configured.
For an example of how the forwarding device extracts the target data and the related information in the configuration request, reference may be made to the description in the embodiment shown in fig. 2, which is not described herein again.
Step S23, the forwarding device obtains the first user identifier of the first management device.
Since there are many ways for the forwarding device to obtain the first subscriber identity of the first management device, several specific ways are briefly described below.
In a first manner, the step of acquiring, by the forwarding device, the first subscriber identity of the first management device may include the following steps: the forwarding device obtains a session identifier for establishing a first session with the first management device, and the forwarding device obtains a first user identifier corresponding to the session identifier.
In the first manner, before step S21, the method shown in fig. 3 may further include the following steps: the forwarding equipment receives a message sent by first management equipment, wherein the message is used for establishing a first session and comprises a first user identifier; the forwarding equipment obtains a session identifier of a first session; the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier.
In a first manner, first, a first management device sends a message to a forwarding device to establish a session connection between the first management device and the forwarding device (hereinafter, the session connection is referred to as a first session), where the message further includes a first user identifier, and the first user identifier is used to indicate an identity of the first management device; secondly, the forwarding device obtains a session identifier of the first session, wherein the session identifier is used for indicating the identity of the first session; then, the forwarding device establishes a corresponding relationship between the session identifier of the first session and the first user identifier, so that the first user identifier can be found through the session identifier in the subsequent steps; thirdly, after the forwarding device receives the configuration request sent by the first management device, the forwarding device acquires a session identifier for establishing a first session with the first management device; finally, the forwarding device prestores a correspondence between the session identifier of the first session and the first user identifier, and the forwarding device may determine the first user identifier corresponding to the session identifier of the first session based on the correspondence.
In the first manner, the first management device may add a first user identifier for indicating an identity of the first management device to a packet for establishing the first session, and the forwarding device needs to establish a correspondence between the first user identifier and the session identifier of the first session, so that the forwarding device may find the first user identifier according to the session identifier of the first session.
The first mode is more suitable for the technical scene that a plurality of management devices share the same user identifier. For example, the management device a adds the user identifier X to the packet for establishing the first session with the forwarding device H, and the management device B adds the user identifier X to the packet for establishing the first session with the forwarding device H, so that the management device a and the management device B are the same user for the forwarding device H, and the first manner is more suitable for a technical scenario in which a plurality of management devices share the same user identifier.
In a second manner, the step of acquiring, by the forwarding device, the first subscriber identity of the first management device may include the following steps: the forwarding device obtains a user name used for establishing a first session with the first management device, and the forwarding device determines that the user name of the first session is the first user identifier.
In the second manner, before step S21, in order for the first management device to establish a session connection with the forwarding device (hereinafter, the session connection is referred to as a first session), the first management device needs to send a login request to the forwarding device, where the login request includes a user name and a password for establishing the session connection. After the forwarding device checks that the user name and the password in the login request are correct, the forwarding device sends a feedback request with correct information to the first management device, and allows a message which is sent by the first management device and used for establishing a first session with the forwarding device. After the first session is established between the first management device and the forwarding device, the first management device sends a configuration request to the forwarding device to configure target data on the forwarding device. At this time, the forwarding device obtains the user name used for establishing the first session with the first management device, and determines that the user name of the first session is the first user identifier.
In the second mode, the forwarding device determines the user name used for establishing the first session with the first management device as the first user identifier, so that the first management device does not need to additionally send the first user identifier to the forwarding device, thereby saving the transmission resource of the first session.
The second method is more suitable for a technical scenario that a management device uses a user identifier. For example, before the management device a establishes a session with the forwarding device H, the management device a needs to log in the forwarding device H through the user name 123 and the password 456, and since the forwarding device H uses the user name 123 as the identity of the management device a after the management device a logs in the server using the user name 123, the management device cannot log in the forwarding device H again using the user name 123, so the second manner is more suitable for a technical scenario in which one management device uses one user identity.
In a third manner, the step of acquiring, by the forwarding device, the first subscriber identity of the first management device may include the following steps: the forwarding device extracts the first subscriber identity in the configuration request.
In a third manner, the first management device directly adds the first user identifier to the configuration request, so that the forwarding device can directly extract the first user identifier from the configuration request.
The third mode is more suitable for a technical scenario that one management device comprises a plurality of services. For example, the management device a includes a service a1 and a service a2, and when the service a1 of the management device a sends a configuration request to the forwarding device H, the management device a adds the user identifier x1 of the service a1 in the configuration request; when the service a2 of the management device a sends a configuration request to the forwarding device H, the management device a adds the user identifier x2 of the service a2 to the configuration request, so that it can be ensured that each service in one management device cannot change the target data corresponding to other services at will, and therefore the third mode is more suitable for a technical scenario in which one management device includes multiple services.
Step S24, the forwarding device obtains a second user identifier of the second management device corresponding to the target data.
The forwarding device stores the corresponding relationship between the target data and the user identifier of the management device, so that the forwarding device can determine the second user identifier of the second management device corresponding to the target data according to the corresponding relationship between the target data and the user identifier of the management device.
And step S25, when the first user identification is the same as the second user identification, the forwarding device configures the target data on the forwarding device according to the configuration request.
After the forwarding device obtains the first user identifier of the first management device and the second user identifier of the second management device corresponding to the target data, the forwarding device will determine whether the first user identifier and the second user identifier are the same. If the first user identification is the same as the second user identification, the first management equipment and the second management equipment belong to the same user, so that the forwarding equipment configures target data on the forwarding equipment according to the configuration request; if the first user identification is different from the second user identification, the first management device and the second management device belong to different users, so that the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
The embodiments of the present application relate to various technical scenarios, and the following brief introduction:
in a first technical scenario, the first management device and the second management device belong to the same user, and the first management device and the second management device are the same management device.
For example, assuming that the user a sends a user identifier X1 and a configuration request to the forwarding device by using the management device S1, the configuration request is used for configuring target data on the forwarding device, and the forwarding device establishes a corresponding relationship between the target data and the user identifier X1 because the target data is configured for the first time; after a certain time, the user A sends the user identification X1 and the configuration request to the forwarding device again using the managing device S1, the configuration request is used to configure the target data on the forwarding device, since the target data is not configured for the first time, therefore, when the forwarding device obtains the user identifier X1 of the management device S1, the forwarding device may determine that the user identifier X1 of the management device S1 that requires to configure the target data this time is the same as the user identifier X1 of the management device S1 corresponding to the target data, which indicates that the management device that configured the target data last time and the management device that configured the target data this time belong to the same user, and the management device which configures the target data last time and the management device which configures the target data this time are the same management device, so the forwarding device configures the target data on the forwarding device according to the configuration request.
In a second technical scenario, the first management device and the second management device belong to the same user, and the first management device and the second management device are different management devices.
For example, assuming that the user a sends a user identifier X1 and a configuration request to the forwarding device by using the management device S1, the configuration request is used for configuring target data on the forwarding device, and the forwarding device establishes a corresponding relationship between the target data and the user identifier X1 because the target data is configured for the first time; after a period of time, the user a sends a user identifier X1 and a configuration request to the forwarding device by using the management device S2, where the configuration request is used to configure target data on the forwarding device, and since the target data is not configured for the first time, the forwarding device obtains that the user identifier of the management device S2 is X1, at this time, the forwarding device may determine that the user identifier X1 of the management device S2 that requires to configure the target data this time is the same as the user identifier X1 of the management device S1 corresponding to the target data, which indicates that the management device that configured the target data last time and the management device that configured the target data this time belong to the same user, and the management device that configured the target data last time and the management device that configured the target data this time are different management devices, so that the forwarding device configures the target data on the forwarding device according to the configuration request.
In a third technical scenario, the first management device and the second management device belong to different users, and the first management device and the second management device are the same management device.
For example, assuming that the user a sends a user identifier X1 and a configuration request to the forwarding device by using the management device S1, the configuration request is used for configuring target data on the forwarding device, and the forwarding device establishes a corresponding relationship between the target data and the user identifier X1 because the target data is configured for the first time; after a while, the user A sends the user identification X2 and the configuration request to the forwarding device by using the managing device S1, the configuration request is used to configure the target data on the forwarding device, since the target data is not configured for the first time, therefore, when the forwarding device obtains the user identifier X2 of the management device S1, the forwarding device may determine that the user identifier X2 of the management device S1 that requires to configure the target data this time is different from the user identifier X1 of the management device S1 corresponding to the target data, which indicates that the management device that configured the target data last time and the management device that configured the target data this time belong to different users, and the management device which configures the target data last time and the management device which configures the target data this time are the same management devices, so that the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In a fourth technical scenario, the first management device and the second management device belong to different users, and the first management device and the second management device are different management devices.
For example, assuming that the user a sends a user identifier X1 and a configuration request to the forwarding device by using the management device S1, the configuration request is used for configuring target data on the forwarding device, and the forwarding device establishes a corresponding relationship between the target data and the user identifier X1 because the target data is configured for the first time; after a while, the user A sends the user identification X2 and the configuration request to the forwarding device by using the managing device S2, the configuration request is used to configure the target data on the forwarding device, since the target data is not configured for the first time, therefore, when the forwarding device obtains the user identifier X2 of the management device S2, the forwarding device may determine that the user identifier X2 of the management device S2 that requires to configure the target data this time is different from the user identifier X1 of the management device S1 corresponding to the target data, which indicates that the management device that configured the target data last time and the management device that configured the target data this time belong to different users, and the management device which configured the target data last time and the management device which configured the target data this time are different management devices, so the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
And step S26, when the first user identification is different from the second user identification, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
In the embodiment shown in fig. 3, when the first management device needs to configure the target data belonging to the second management device, the forwarding device needs to determine whether the first user identifier is the same as the second user identifier, and if so, it indicates that the first management device and the second management device belong to the same user, and the first management device qualifies to modify the target data, and then the forwarding device configures the target data on the forwarding device according to the configuration request; otherwise, it indicates that the first management device and the second management device belong to different users, and the first management device does not have the qualification for modifying the target data, then the forwarding device will refuse to configure the target data on the forwarding device according to the configuration request. Therefore, the forwarding device provided in the embodiment of the present application only allows the management device to configure the target data that belongs to the forwarding device, and does not allow the management device to configure the target data that does not belong to the forwarding device, so that it is possible to avoid that multiple management devices configure the target data on the forwarding device at will.
In the embodiment shown in fig. 3, in an alternative scheme, after "the forwarding device receives the configuration request sent by the first management device" in step S22, the scheme provided in the embodiment of the present application may further include the following steps: the forwarding equipment judges whether target data are stored on the forwarding equipment or not; when the target data is stored on the forwarding device, step S23 is executed; when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, acquires the first user identifier of the first management device, and establishes a corresponding relationship between the target data and the first user identifier.
After the forwarding device receives the configuration request sent by the first management device, the forwarding device extracts target data in the configuration request, and then the forwarding device judges whether the target data is stored on the forwarding device. If the forwarding device does not store the target data, it indicates that no management device has configured the target data on the forwarding device before, so the first management device is the management device that configured the target data on the forwarding device for the first time, so the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
Referring to fig. 4, fig. 4 is a schematic diagram of a forwarding device according to an embodiment of the present application. The forwarding device is applied to a first network, the first network comprises a plurality of management devices and the forwarding device, data of the forwarding device can be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, and the plurality of management devices comprise a first management device and a second management device. The forwarding device comprises the following modules:
a first receiving module 31, configured to receive a configuration request sent by a first management device, where the configuration request is used to configure target data on a forwarding device; for detailed implementation, please refer to the detailed description of step S12 in the embodiment of the method shown in fig. 2.
A first obtaining module 32, configured to obtain a configuration permission level of a first management device; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2. A second obtaining module 33, configured to obtain a configuration permission level of a second management device corresponding to the target data; for detailed implementation, please refer to the detailed description of step S14 in the embodiment of the method shown in fig. 2.
A configuration module 34, configured to configure target data on the forwarding device according to the configuration request when the configuration permission level of the first management device is higher than that of the second management device; when the configuration permission level of the first management device is lower than that of the second management device, refusing to configure the target data on the forwarding device according to the configuration request; for detailed implementation, please refer to the detailed description of steps S15 and S16 in the embodiment of the method shown in fig. 2.
Optionally, the first obtaining module 32 is specifically configured to obtain a session identifier for establishing a first session with a first management device, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device according to the first user identifier and configuration permission levels corresponding to multiple management devices stored in a forwarding device; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the first obtaining module 32 is specifically configured to obtain a user name used for establishing a first session with the first management device, the forwarding device determines that the user name of the first session is a first user identifier, and determines a configuration permission level corresponding to the first user identifier; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the first obtaining module 32 is specifically configured to extract a first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
the second receiving module 35 is configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier.
An obtaining module 36 is configured to obtain a session identifier of the first session.
The first establishing module 37 is configured to establish a correspondence between a session identifier of the first session and the first user identifier. For detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the second obtaining module 33 is specifically configured to obtain a second user identifier of the second management device corresponding to the target data. Determining a configuration authority level corresponding to a second user identifier of second management equipment; for detailed implementation, please refer to the detailed description of step S14 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
and a second establishing module 38, configured to establish a corresponding relationship between the target data and the first management device.
And a deleting module 39, configured to delete the correspondence between the target data and the second management device.
In a detailed implementation manner, please refer to the step "the forwarding device establishes a corresponding relationship between the target data and the first management device" in the embodiment of the method shown in fig. 2; the forwarding device deletes a detailed description of the correspondence relationship between the target data and the second management device.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
and a third obtaining module 40, configured to obtain a notification subscription list corresponding to the target data.
A sending module 41, configured to send a change notification of the target data to at least one target management device in the notification subscription list, where the at least one target management device is a management device that sends a subscription request for the target data to the forwarding device in advance.
In a detailed implementation manner, please refer to the step "forwarding device obtains a notification subscription list corresponding to target data" in the embodiment of the method shown in fig. 2; the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, where the at least one target management device is a detailed description of a management device that sends a subscription request for the target data to the forwarding device in advance.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
a first determining module 42, configured to determine whether the forwarding device stores the target data. When the forwarding device stores the target data, the first obtaining module 32 is triggered. And when the target data is not stored in the forwarding equipment, configuring the target data on the forwarding equipment according to the configuration request, and establishing a corresponding relation between the target data and the first management equipment.
In a detailed implementation manner, please refer to the step "the forwarding device determines whether the forwarding device stores the target data" in the embodiment of the method shown in fig. 2; when the target data is stored in the forwarding equipment, executing a step of acquiring the configuration authority level of the first management equipment by the forwarding equipment; and when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes detailed description of a corresponding relation between the target data and the first management device.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
a second judging module 43, configured to judge whether the first management device is the same as the second management device. And when the first management device is the same as the second management device, configuring target data on the forwarding device according to the configuration request. And when the first management device is different from the second management device, judging whether the configuration authority level of the first management device is higher than that of the second management device.
In a detailed implementation manner, please refer to the step "forwarding device determines whether the first management device is the same as the second management device" in the embodiment of the method shown in fig. 2; when the first management equipment is the same as the second management equipment, the forwarding equipment configures target data on the forwarding equipment according to the configuration request; when the first management device is different from the second management device, the forwarding device determines whether the configuration authority level of the first management device is higher than the configuration authority level of the second management device.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
and a third judging module 44, configured to judge whether the second management device corresponding to the target data has the configuration permission level. And when the second management device corresponding to the target data has the configuration authority level, triggering the first obtaining module 32. And when the second management device corresponding to the target data does not have the configuration authority level, refusing to configure the target data on the forwarding device according to the configuration request.
In a detailed implementation manner, please refer to the step "determining whether the second management device corresponding to the target data has the configuration permission level" in the embodiment of the method shown in fig. 2; when the second management device corresponding to the target data has the configuration authority level, executing step S13; and when the second management device corresponding to the target data does not have the configuration authority level, the forwarding device refuses to configure the detailed description of the target data on the forwarding device according to the configuration request.
Referring to fig. 5, fig. 5 is a schematic diagram of another forwarding device provided in the embodiment of the present application. The forwarding device is applied to a first network, the first network comprises a plurality of management devices and the forwarding device, data of the forwarding device can be configured by the plurality of management devices, and the plurality of management devices comprise a first management device and a second management device. The forwarding device comprises the following modules:
a first receiving module 51, configured to receive a configuration request sent by a first management device, where the configuration request is used to configure target data on a forwarding device; for detailed implementation, please refer to the detailed description of step S22 in the embodiment of the method shown in fig. 3.
A first obtaining module 52, configured to obtain a first user identifier of a first management device; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
A second obtaining module 53, configured to obtain a second user identifier of a second management device corresponding to the target data; for detailed implementation, please refer to the detailed description of step S24 in the embodiment of the method shown in fig. 3.
A configuration module 54, configured to configure the target data on the forwarding device according to the configuration request when the first subscriber identity is the same as the second subscriber identity. When the first user identification is different from the second user identification, refusing to configure target data on the forwarding equipment according to the configuration request; for detailed implementation, please refer to the detailed description of steps S25 and S26 in the embodiment of the method shown in fig. 3.
Optionally, the first obtaining module 52 is specifically configured to obtain a session identifier for establishing a first session with the first management device, and obtain a first user identifier corresponding to the session identifier; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the first obtaining module 52 is specifically configured to obtain a user name used for establishing a first session with the first management device, and determine that the user name of the first session is the first user identifier; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the first obtaining module 52 is specifically configured to extract the first user identifier in the configuration request; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
the second receiving module 55 is configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier.
An obtaining module 56 is configured to obtain a session identifier of the first session.
The establishing module 57 is configured to establish a correspondence between a session identifier of the first session and the first user identifier.
For detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device provided in this embodiment of the present application may further include:
and a judging module 58, configured to judge whether the forwarding device stores the target data. The first acquisition module 52 is triggered when the forwarding device has target data stored thereon. When the target data is not stored in the forwarding device, the target data on the forwarding device is configured according to the configuration request, the first user identifier corresponding to the first management device is determined, and the corresponding relation between the target data and the first user identifier is established.
In a detailed implementation manner, please refer to the step "the forwarding device determines whether the forwarding device stores the target data" in the embodiment of the method shown in fig. 3; when the target data is stored on the forwarding device, step S23 is executed; when the forwarding device does not store the target data, the forwarding device configures the target data on the forwarding device according to the configuration request, obtains the first user identifier of the first management device, and establishes a detailed description of a corresponding relationship between the target data and the first user identifier.
Referring to fig. 6, fig. 6 is a schematic view of a multi-head configuration system according to an embodiment of the present disclosure. The multi-head configuration system comprises a plurality of management devices and a forwarding device 61, wherein data of the forwarding device 61 can be configured by the plurality of management devices, the forwarding device 61 stores configuration authority levels corresponding to the plurality of management devices, and the plurality of management devices comprise a first management device 62 and a second management device 63. Wherein the content of the first and second substances,
a first management device 62, configured to send a configuration request to the forwarding device, where the configuration request is used to configure target data on the forwarding device. For detailed implementation, please refer to the detailed description of step S11 in the embodiment of the method shown in fig. 2.
The forwarding device 61 is configured to receive the configuration request sent by the first management device 62. The configuration authority level of the first management device 62 is acquired. The configuration authority level of the second management device 63 corresponding to the target data is acquired. When the configuration authority level of the first management device 62 is higher than that of the second management device 63, the target data on the forwarding device 61 is configured according to the configuration request. When the configuration authority level of the first management device 62 is lower than that of the second management device 63, the target data on the forwarding device 61 is refused to be configured according to the configuration request. For a detailed implementation, please refer to the detailed description of step S12 to step S16 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device 61 is specifically configured to obtain a session identifier for establishing a first session with the first management device 62, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device 62 according to the first user identifier and configuration permission levels corresponding to multiple management devices stored in the forwarding device; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device 61 is specifically configured to obtain a user name used for establishing a first session with the first management device 62, determine the user name of the first session as a first user identifier, and determine a configuration permission level corresponding to the first user identifier; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device 61 is specifically configured to extract a first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device 61 is further configured to receive a message sent by the first management device 62, where the message is used to establish a first session, and the message includes a first user identifier. A session identification for the first session is obtained. Establishing a corresponding relation between a session identifier of a first session and a first user identifier; for detailed implementation, please refer to the detailed description of step S13 in the embodiment of the method shown in fig. 2.
Optionally, the forwarding device 61 is further configured to obtain a notification subscription list corresponding to the target data, and send a change notification of the target data to at least one target management device in the notification subscription list, where the at least one target management device is a management device that sends a subscription request for the target data to the forwarding device 61 in advance.
In a detailed implementation manner, please refer to the step "forwarding device obtains a notification subscription list corresponding to target data" in the embodiment of the method shown in fig. 2; the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, where the at least one target management device is a detailed description of a management device that sends a subscription request for the target data to the forwarding device in advance.
Referring to fig. 7, fig. 7 is a schematic view of another multi-head configuration system according to an embodiment of the present disclosure. The multi-head configuration system includes a plurality of management devices and a forwarding device 71, and data of the forwarding device 71 can be configured by the plurality of management devices including a first management device 72 and a second management device 73. Wherein the content of the first and second substances,
a first management device 72, configured to send a configuration request to the forwarding device 71, where the configuration request is used to configure target data on the forwarding device 71. For detailed implementation, please refer to the detailed description of step S21 in the embodiment of the method shown in fig. 3.
The forwarding device 71 is configured to receive the configuration request sent by the first management device 72, obtain a first user identifier of the first management device 72, and obtain a second user identifier of the second management device 73 corresponding to the target data. When the first subscriber identity is the same as the second subscriber identity, the target data on the forwarding device 71 is configured according to the configuration request. And refusing to configure the target data on the forwarding equipment 71 according to the configuration request when the first user identification is different from the second user identification. For a detailed implementation, please refer to the detailed description of step S22 to step S26 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device 71 is specifically configured to obtain a session identifier for establishing a first session with the first management device 72, and obtain a first user identifier corresponding to the session identifier; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device 71 is specifically configured to obtain a user name used for establishing a first session with the first management device 72, and determine that the user name of the first session is a first user identifier; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device 71 is specifically configured to extract the first user identifier in the configuration request; for detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Optionally, the forwarding device 71 is further configured to receive a message sent by the first management device 72, where the message is used to establish a first session, where the message includes a first user identifier, obtain a session identifier of the first session, and establish a correspondence between the session identifier of the first session and the first user identifier. For detailed implementation, please refer to the detailed description of step S23 in the embodiment of the method shown in fig. 3.
Referring to fig. 8, fig. 8 is a schematic diagram of another forwarding device provided in the embodiment of the present application. The repeater comprises a processor 81, a memory 82 and a transceiver 83, wherein the processor 81, the memory 82 and the transceiver 83 communicate with each other via an internal connection path, the memory 82 is used for storing instructions, the processor 81 is used for executing the instructions stored in the memory 82 to control the transceiver 83 to receive and transmit signals, and when the processor 81 executes the instructions stored in the memory 82, the processor 81 executes the method executed by the repeater in fig. 2.
Referring to fig. 9, fig. 9 is a schematic diagram of another forwarding device provided in the embodiment of the present application. The repeater comprises a processor 91, a memory 92 and a transceiver 93, wherein the processor 91, the memory 92 and the transceiver 93 communicate with each other via an internal connection path, the memory 92 is used for storing instructions, the processor 91 is used for executing the instructions stored by the memory 92 to control the transceiver 93 to receive signals and transmit signals, and when the processor 91 executes the instructions stored by the memory 92, the processor 91 executes the method executed by the repeater in fig. 3.

Claims (33)

1. A multi-head configuration method is applied to a first network, the first network comprises a plurality of management devices and a forwarding device, data of the forwarding device can be configured by the plurality of management devices, the plurality of management devices have respective corresponding configuration authority levels, the plurality of management devices comprise a first management device and a second management device, and the method comprises the following steps:
the forwarding device receives a configuration request sent by the first management device, wherein the configuration request is used for configuring target data on the forwarding device, and the target data belongs to the second management device;
the forwarding equipment acquires the configuration authority level of the first management equipment;
the forwarding device acquires a configuration authority level of the second management device corresponding to the target data;
when the configuration authority level of the first management device is higher than that of the second management device, the forwarding device configures the target data on the forwarding device according to the configuration request;
and when the configuration authority level of the first management device is lower than that of the second management device, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
2. The multi-head configuration method according to claim 1, wherein the forwarding device obtaining the configuration permission level of the first management device comprises:
the forwarding device acquires a session identifier establishing a first session with the first management device, the forwarding device acquires a first user identifier corresponding to the session identifier, and the forwarding device acquires a configuration permission level of the first management device according to the first user identifier and the configuration permission levels corresponding to the plurality of management devices stored in the forwarding device;
alternatively, the first and second electrodes may be,
the forwarding device acquires a user name used for establishing a first session with the first management device, determines the user name of the first session as a first user identifier, and determines a configuration authority level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
and the forwarding equipment extracts the first user identification in the configuration request, and determines the configuration permission level corresponding to the first user identification.
3. The multi-head configuration method according to claim 2, wherein before the forwarding device obtains the session identifier for establishing the first session with the first management device, the method further comprises:
the forwarding device receives a message sent by the first management device, wherein the message is used for establishing a first session and comprises a first user identifier;
the forwarding device obtains a session identifier of the first session;
and the forwarding equipment establishes a corresponding relation between the session identifier of the first session and the first user identifier.
4. The multi-head configuration method according to claim 1, wherein the obtaining, by the forwarding device, the configuration permission level of the second management device corresponding to the target data includes:
the forwarding device acquires a second user identifier of the second management device corresponding to the target data;
and the forwarding equipment determines a configuration authority level corresponding to a second user identifier of the second management equipment.
5. The multi-head configuration method according to claim 1, wherein after the forwarding device configures the target data on the forwarding device according to the configuration request, the method further comprises:
the forwarding equipment establishes a corresponding relation between the target data and the first management equipment;
and the forwarding equipment deletes the corresponding relation between the target data and the second management equipment.
6. The multi-head configuration method according to claim 1, wherein after the forwarding device configures the target data on the forwarding device according to the configuration request, the method further comprises:
the forwarding equipment acquires a notification subscription list corresponding to the target data;
and the forwarding device sends a change notification of the target data to at least one target management device in the notification subscription list, wherein the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
7. The multi-head configuration method according to claim 1, wherein after the forwarding device receives the configuration request sent by the first management device, the method further comprises:
the forwarding equipment judges whether the target data is stored on the forwarding equipment or not;
when the target data is stored in the forwarding device, executing a step of acquiring a configuration authority level of the first management device by the forwarding device;
when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, and establishes a corresponding relationship between the target data and the first management device.
8. The multi-head configuration method according to claim 1, wherein after the forwarding device obtains the configuration permission level of the second management device corresponding to the target data, the method further comprises:
the forwarding device judges whether the first management device is the same as the second management device;
when the first management device is the same as the second management device, the forwarding device configures the target data on the forwarding device according to the configuration request;
when the first management device is different from the second management device, the forwarding device determines whether the configuration authority level of the first management device is higher than that of the second management device.
9. The multi-head configuration method according to claim 1, wherein after the forwarding device receives the configuration request sent by the first management device, the method further comprises:
judging whether the second management equipment corresponding to the target data has a configuration authority level or not;
when the second management device corresponding to the target data has a configuration authority level, executing a step of acquiring the configuration authority level of the first management device by the forwarding device;
and when the second management device corresponding to the target data does not have a configuration authority level, the forwarding device refuses to configure the target data on the forwarding device according to the configuration request.
10. A multi-head configuration method is applied to a first network, the first network comprises a plurality of management devices and a forwarding device, data of the forwarding device can be configured by the plurality of management devices, the plurality of management devices comprise a first management device and a second management device, and the method comprises the following steps:
the forwarding device receives a configuration request sent by the first management device, wherein the configuration request is used for configuring target data on the forwarding device, and the target data belongs to the second management device;
the forwarding device acquires a first user identifier of the first management device;
the forwarding device acquires a second user identifier of the second management device corresponding to the target data;
when the first user identification is the same as the second user identification, the forwarding device configures the target data on the forwarding device according to the configuration request;
and when the first user identification is different from the second user identification, the forwarding equipment refuses to configure the target data on the forwarding equipment according to the configuration request.
11. The multi-head configuration method according to claim 10, wherein the forwarding device obtaining the first subscriber identity of the first management device comprises:
the forwarding device acquires a session identifier for establishing a first session with the first management device, and the forwarding device acquires a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the forwarding equipment acquires a user name used for establishing a first session with the first management equipment, and the forwarding equipment determines that the user name of the first session is a first user identifier;
alternatively, the first and second electrodes may be,
and the forwarding equipment extracts the first user identification in the configuration request.
12. The multi-head configuration method according to claim 11, wherein before the forwarding device obtains the session identifier for establishing the first session with the first management device, the method further comprises:
the forwarding device receives a message sent by the first management device, wherein the message is used for establishing a first session and comprises a first user identifier;
the forwarding device obtains a session identifier of the first session;
and the forwarding equipment establishes a corresponding relation between the session identifier of the first session and the first user identifier.
13. The multi-head configuration method according to claim 10, wherein after the forwarding device receives the configuration request sent by the first management device, the method further comprises:
the forwarding equipment judges whether the target data is stored on the forwarding equipment or not;
when the target data is stored in the forwarding device, executing a step of acquiring a first user identifier of the first management device by the forwarding device;
when the target data is not stored in the forwarding device, the forwarding device configures the target data on the forwarding device according to the configuration request, obtains a first user identifier of the first management device, and establishes a corresponding relationship between the target data and the first user identifier.
14. A forwarding device applied to a first network including a plurality of management devices and a forwarding device, data of the forwarding device being configurable by the plurality of management devices, the plurality of management devices having respective corresponding configuration authority levels, the plurality of management devices including a first management device and a second management device, the forwarding device comprising:
a first receiving module, configured to receive a configuration request sent by the first management device, where the configuration request is used to configure target data on the forwarding device, and the target data belongs to the second management device;
the first acquisition module is used for acquiring the configuration permission level of the first management equipment;
the second obtaining module is used for obtaining the configuration permission level of the second management equipment corresponding to the target data;
a configuration module, configured to configure the target data on the forwarding device according to the configuration request when the configuration permission level of the first management device is higher than the configuration permission level of the second management device; and when the configuration permission level of the first management device is lower than that of the second management device, refusing to configure the target data on the forwarding device according to the configuration request.
15. The forwarding device of claim 14, wherein:
the first obtaining module is specifically configured to obtain a session identifier for establishing a first session with the first management device, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device according to the first user identifier and the configuration permission levels corresponding to the plurality of management devices stored in the forwarding device;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to obtain a user name used for establishing a first session with the first management device, determine the user name of the first session as a first user identifier, and determine a configuration permission level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to extract a first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier.
16. The forwarding device of claim 15, wherein the forwarding device further comprises:
a second receiving module, configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier;
an obtaining module, configured to obtain a session identifier of the first session;
and the first establishing module is used for establishing the corresponding relation between the session identifier of the first session and the first user identifier.
17. The forwarding device of claim 14, wherein:
the second obtaining module is specifically configured to obtain a second user identifier of the second management device corresponding to the target data; and determining a configuration authority level corresponding to a second user identification of the second management equipment.
18. The forwarding device of claim 14, wherein the forwarding device further comprises:
the second establishing module is used for establishing the corresponding relation between the target data and the first management equipment;
and the deleting module is used for deleting the corresponding relation between the target data and the second management equipment.
19. The forwarding device of claim 14, wherein the forwarding device further comprises:
a third obtaining module, configured to obtain a notification subscription list corresponding to the target data;
a sending module, configured to send a change notification of the target data to at least one target management device in the notification subscription list, where the at least one target management device is a management device that sends a subscription request for the target data to the forwarding device in advance.
20. The forwarding device of claim 14, wherein the forwarding device further comprises:
the first judging module is used for judging whether the target data is stored in the forwarding equipment; when the target data is stored in the forwarding device, triggering the first acquisition module; when the target data is not stored in the forwarding device, configuring the target data on the forwarding device according to the configuration request, and establishing a corresponding relation between the target data and the first management device.
21. The forwarding device of claim 14, wherein the forwarding device further comprises:
the second judging module is used for judging whether the first management equipment is the same as the second management equipment or not; when the first management device is the same as the second management device, configuring the target data on the forwarding device according to the configuration request; when the first management device is different from the second management device, judging whether the configuration authority level of the first management device is higher than that of the second management device.
22. The forwarding device of claim 14, wherein the forwarding device further comprises:
the third judging module is used for judging whether the second management equipment corresponding to the target data has the configuration permission level or not; when the second management device corresponding to the target data has a configuration authority level, triggering the first acquisition module; and refusing to configure the target data on the forwarding device according to the configuration request when the second management device corresponding to the target data does not have the configuration authority level.
23. A forwarding device applied to a first network including a plurality of management devices and a forwarding device, data of the forwarding device being configurable by the plurality of management devices, the plurality of management devices including a first management device and a second management device, the forwarding device comprising:
a first receiving module, configured to receive a configuration request sent by the first management device, where the configuration request is used to configure target data on the forwarding device, and the target data belongs to the second management device;
a first obtaining module, configured to obtain a first user identifier of the first management device;
a second obtaining module, configured to obtain a second user identifier of the second management device corresponding to the target data;
a configuration module, configured to configure the target data on the forwarding device according to the configuration request when the first user identifier is the same as the second user identifier; and when the first user identification is different from the second user identification, refusing to configure the target data on the forwarding equipment according to the configuration request.
24. The forwarding device of claim 23, wherein:
the first obtaining module is specifically configured to obtain a session identifier for establishing a first session with the first management device, and obtain a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to obtain a user name used for establishing a first session with the first management device, and determine that the user name of the first session is a first user identifier;
alternatively, the first and second electrodes may be,
the first obtaining module is specifically configured to extract the first user identifier in the configuration request.
25. The forwarding device of claim 24, wherein the forwarding device further comprises:
a second receiving module, configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier;
an obtaining module, configured to obtain a session identifier of the first session;
and the establishing module is used for establishing the corresponding relation between the session identifier of the first session and the first user identifier.
26. The forwarding device of claim 23, wherein the forwarding device further comprises:
the judging module is used for judging whether the target data is stored on the forwarding equipment; when the target data is stored in the forwarding device, triggering the first acquisition module; when the target data is not stored in the forwarding device, configuring the target data on the forwarding device according to the configuration request, determining a first user identifier corresponding to the first management device, and establishing a corresponding relationship between the target data and the first user identifier.
27. A multi-head configuration system is characterized in that the system comprises a plurality of management devices and forwarding devices, data of the forwarding devices can be configured by the management devices, the management devices have respective corresponding configuration authority levels, and the management devices comprise a first management device and a second management device; wherein the content of the first and second substances,
the first management device is configured to send a configuration request to the forwarding device, where the configuration request is used to configure target data on the forwarding device, and the target data belongs to the second management device;
the forwarding device is configured to receive the configuration request sent by the first management device; acquiring the configuration authority level of the first management equipment; acquiring the configuration permission level of the second management equipment corresponding to the target data; when the configuration authority level of the first management device is higher than that of the second management device, configuring the target data on the forwarding device according to the configuration request; and when the configuration permission level of the first management device is lower than that of the second management device, refusing to configure the target data on the forwarding device according to the configuration request.
28. The multi-head configuration system of claim 27, wherein:
the forwarding device is specifically configured to obtain a session identifier for establishing a first session with the first management device, obtain a first user identifier corresponding to the session identifier, and obtain a configuration permission level of the first management device according to the first user identifier and the configuration permission levels corresponding to the plurality of management devices stored in the forwarding device
Alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to acquire a user name used for establishing a first session with the first management device, determine that the user name of the first session is a first user identifier, and determine a configuration permission level corresponding to the first user identifier;
alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to extract the first user identifier in the configuration request, and determine a configuration permission level corresponding to the first user identifier.
29. The multi-head configuration system of claim 28, wherein:
the forwarding device is further configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier; obtaining a session identifier of the first session; and establishing a corresponding relation between the session identification of the first session and the first user identification.
30. The multi-head configuration system of claim 27, wherein:
the forwarding device is further configured to obtain a notification subscription list corresponding to the target data; and sending a change notification of the target data to at least one target management device in the notification subscription list, wherein the at least one target management device is a management device which sends a subscription request aiming at the target data to the forwarding device in advance.
31. A multi-head configuration system is characterized in that the system comprises a plurality of management devices and a forwarding device, the data of the forwarding device can be configured by the plurality of management devices, and the plurality of management devices comprise a first management device and a second management device; wherein the content of the first and second substances,
the first management device is configured to send a configuration request to the forwarding device, where the configuration request is used to configure target data on the forwarding device, and the target data belongs to the second management device;
the forwarding device is configured to receive a configuration request sent by the first management device; acquiring a first user identifier of the first management device; acquiring a second user identifier of the second management device corresponding to the target data; when the first user identification is the same as the second user identification, configuring the target data on the forwarding equipment according to the configuration request; and when the first user identification is different from the second user identification, refusing to configure the target data on the forwarding equipment according to the configuration request.
32. The multi-head configuration system of claim 31, wherein:
the forwarding device is specifically configured to obtain a session identifier for establishing a first session with the first management device, and obtain a first user identifier corresponding to the session identifier;
alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to acquire a user name used for establishing a first session with the first management device, and determine that the user name of the first session is a first user identifier;
alternatively, the first and second electrodes may be,
the forwarding device is specifically configured to extract the first user identifier in the configuration request.
33. The multi-head configuration system of claim 32, wherein:
the forwarding device is further configured to receive a message sent by the first management device, where the message is used to establish a first session, and the message includes a first user identifier; obtaining a session identifier of the first session; and establishing a corresponding relation between the session identification of the first session and the first user identification.
CN201810393998.4A 2018-04-27 2018-04-27 Multi-head configuration method, device and system Active CN110417566B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810393998.4A CN110417566B (en) 2018-04-27 2018-04-27 Multi-head configuration method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810393998.4A CN110417566B (en) 2018-04-27 2018-04-27 Multi-head configuration method, device and system

Publications (2)

Publication Number Publication Date
CN110417566A CN110417566A (en) 2019-11-05
CN110417566B true CN110417566B (en) 2021-11-26

Family

ID=68346731

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810393998.4A Active CN110417566B (en) 2018-04-27 2018-04-27 Multi-head configuration method, device and system

Country Status (1)

Country Link
CN (1) CN110417566B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478471A (en) * 2009-02-04 2009-07-08 中兴通讯股份有限公司 Deployment method and system for MPLS/BGP three-layer virtual private network
CN103812681A (en) * 2012-11-14 2014-05-21 中兴通讯股份有限公司 Processing method and communication system for EMS and LMT to access to network element
CN104240469A (en) * 2013-06-06 2014-12-24 鸿富锦精密工业（深圳）有限公司 Remote controller use permission setting system and method
CN106612250A (en) * 2015-10-21 2017-05-03 腾讯科技（深圳）有限公司 Resource utilization authority judgment system and method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478471A (en) * 2009-02-04 2009-07-08 中兴通讯股份有限公司 Deployment method and system for MPLS/BGP three-layer virtual private network
CN103812681A (en) * 2012-11-14 2014-05-21 中兴通讯股份有限公司 Processing method and communication system for EMS and LMT to access to network element
CN104240469A (en) * 2013-06-06 2014-12-24 鸿富锦精密工业（深圳）有限公司 Remote controller use permission setting system and method
CN106612250A (en) * 2015-10-21 2017-05-03 腾讯科技（深圳）有限公司 Resource utilization authority judgment system and method

Also Published As

Publication number Publication date
CN110417566A (en) 2019-11-05

Similar Documents

Publication Publication Date Title
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
EP3632145B1 (en) Subscription management service data feeds
US10897712B2 (en) Cyber security management system, method, and apparatus
US20200162345A1 (en) Method, system and options for multi-operator service life cycle management
KR20170119296A (en) Method and apparatus for communicating based on network slicing
CN110226308B (en) Network slice management method, management unit and system
WO2019056883A1 (en) Network slice deployment method and related device
EP3644556B1 (en) Alias management method and device
CN113206814B (en) Network event processing method and device and readable storage medium
US11729863B2 (en) Cloud-based interworking gateway service
US8521863B2 (en) Method and device for operating resource on shared network element
CN109842895B (en) Network reliability configuration method, information transmission method, device and system
CN110049031B (en) Interface security authentication method, server and authentication center server
CN113727369A (en) Management method of network component and network equipment
WO2022142740A1 (en) Network slice connection method and apparatus, storage medium, and electronic apparatus
CN114080054A (en) PDU session establishment method, terminal equipment and chip system
US10972898B2 (en) System and interface for cross administration or technology domain network functions (NFS) instantiation and configuration for roaming users
CN117561703A (en) Method and device for instantiating edge application server
US9374710B2 (en) Mediation server, control method therefor, communication device, control method therefor, communication system, and computer program
CN106604278B (en) Multi-authority mobile network sharing method
CN111147468A (en) User access method, device, electronic equipment and storage medium
US20240089178A1 (en) Network service processing method, system, and gateway device
CN108366087B (en) ISCSI service realization method and device based on distributed file system
CN113965938B (en) Slice service system and slice service processing method
US20120254393A1 (en) Device management method, device management apparatus, and device management system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant