Method and device for multi-device classification proxy configuration based on SIP Phone

By confirming the device role and mapping the root node in the SIP Phone environment, using broadcast automatic discovery and multi-node recording technology, the network bandwidth consumption problem caused by concurrent requests for large batches of devices is solved, the deployment efficiency and stability are improved, and efficient Configuration download.

CN119094340APending Publication Date: 2024-12-06上海贝尔企业通信有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411068122.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-06
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the SIP Phone environment deployed in the cloud, when large batches of devices request to download files concurrently, it will increase network bandwidth consumption, affecting the deployment experience and business execution, especially when the files are large, the download time is too long, resulting in excessive system resources occupied.

Method used

Confirm the device role through the resource table, the slave device discovers and maps the root node, obtains data from the root node, reduces the number of connections between the device and the server, and uses the automatic broadcast discovery method. The administrator can specify a small number of root nodes to complete the automatic table building of large-scale devices. , supports multi-node recording and configuration distribution, forms a backup formula for configuring multi-path downloads, and uses the intranet high-speed forwarding feature to speed up the configuration download speed of Slave devices.

Benefits of technology

Reduces external bandwidth consumption, improves connection stability and traffic load balancing capabilities, reduces equipment configuration and maintenance costs, and improves deployment efficiency and configuration download speed.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094340A_ABST
    Figure CN119094340A_ABST
Patent Text Reader

Abstract

The invention provides a multi-device classification proxy configuration method and device based on an SIP Phone. The method comprises the following steps: carrying out resource classification on the SIP Phone and creating resource allocation; an administrator appoints at least one device as a root device, and the other devices are slave devices; when the slave device receives broadcast information of the root device, the message is analyzed, and the root device of the same type is connected according to the SIP Phone resource classification type; after receiving the updating event, the equipment judges whether the equipment is root equipment or slave equipment, and if the equipment is the root equipment, the equipment is connected with a cloud Autop server for updating; and if the equipment is the slave equipment, requesting to obtain an update event from the root equipment to which the slave equipment belongs, and finishing update. In this way, the types to which different resources or parameters belong are indicated based on the mapping table, the role of the device is confirmed, and the data is acquired from the root node, so that the number of times of connection between the device and the server is reduced, the consumption of external bandwidth is reduced, and the connection stability and the traffic load balancing capacity are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention generally relate to the technical field of phone configuration, and more particularly to a multi-device classification proxy configuration method and apparatus based on SIP Phone. Background Art

[0002] At present, the main way to cover batch devices in the SIP Phone industry is through Autop, that is, after deploying a unified server, the Phone devices uniformly apply for configuration to the device. This can achieve high-speed download in the intranet environment, but now is the cloud era. In order to better let users experience the convenience of zero deployment, manufacturers have launched cloud deployment servers. Although this reduces the configuration method of user servers, it requires the use of network bandwidth, which will incur additional costs for billing users. At the same time, a large number of devices concurrently request to download files. If the files are large and numerous, it will seriously affect the deployment experience and take a long time to complete the download and configuration. The time the phone system resources are occupied will also be longer, affecting the execution of the business. Summary of the invention

[0003] To solve the above problems, the present invention indicates the types of different resources or parameters based on the resource table, confirms the role of the device, confirms the root node, indicates the need to support forwarding capability, confirms the corresponding root node at the same time, discovers and maps the root node through the slave device, obtains data from the root node, reduces the number of connections between a large number of devices and the server, reduces the consumption of external bandwidth, and uses the broadcast automatic discovery method. The administrator only needs to specify a small number of root nodes to complete the automatic table building of large-scale internal devices, reducing the cost of device configuration and maintenance. The role of each device is confirmed by exchanging data information between devices, and multi-node recording is supported, which improves connection stability and traffic load balancing capabilities. Configuration distribution is initiated by the slave device, and the root device is notified to apply for and forward data. It mainly retains the existing deployment method while adding a more efficient method, forming a backup formula for configuring multi-path downloading, and at the same time utilizes the high-speed forwarding characteristics of the intranet to speed up the configuration download speed of the Slave device and improve the deployment efficiency.

[0004] According to an embodiment of the present invention, a method and apparatus for configuring a multi-device classification proxy based on a SIP Phone are provided.

[0005] In a first aspect of the present invention, a method for configuring a multi-device classification proxy based on a SIP Phone is provided. The method comprises:

[0006] S01: Classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list;

[0007] S02: The administrator designates at least one device as the root device and the rest as slave devices, and updates the resource allocation table and relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root device, and the slave devices listen to the broadcast information during operation.

[0008] S03: When the slave device receives the broadcast information from the root device, it parses the message and matches the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the slave device discards the broadcast information. If they are the same, the SIP Phone resource classification type is matched. If the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a subordinate device of the root device of the same device type.

[0009] S04: After receiving the update event, the device determines whether it is a root device or a slave device. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests to obtain the update event from the root device to which it belongs and completes the update.

[0010] Furthermore, the SIP Phone resource classification types described in S01 include: Class A, Class B, and Class O, where Class A is a general resource classification, Class B is a type resource classification, and Class C is a stand-alone resource classification, wherein updates to Class O require a separate download request.

[0011] Furthermore, as described in S03, if the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, then the SIP Phone resource classification type in the mapping relationship table is updated, and the root node list of the slave device is filled with its subordinate root device IP, and the child node list of the root device in the resource allocation table is updated at the same time.

[0012] Furthermore, the slave device described in S04 requests update events from the root device to which it belongs. If the slave device request fails, the slave device attempts to connect to other root devices to which it belongs. If the connection is successful, the update event is obtained from the root device. If the slave device cannot obtain configurations from all root nodes, the slave device actively initiates a request to the server and downloads relevant configuration files.

[0013] Furthermore, the slave device described in S04 requests update events from the root device to which it belongs. If the slave device to which it belongs rejects the request due to full load, the slave device attempts to connect to other root devices to which it belongs to request update events. If the SIP Phone resource classification types of other root devices to which it belongs are not exactly the same as the SIP Phone resource classification type of the slave device, update events of different SIP Phone resource classification types need to wait for other root devices with the same SIP Phone resource classification type and to which the slave device belongs to be sent.

[0014] In a second aspect of the present invention, a device for configuring a multi-device classification proxy based on a SIP Phone is provided. The device comprises:

[0015] Resource allocation module: used to classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list;

[0016] Device classification module: used by the administrator to designate at least one device as the root device and the rest as slave devices, and to update the resource allocation table and relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root, and the slave devices listen to the broadcast information during operation.

[0017] Type matching module: used to parse the message after the slave device receives the broadcast information from the root device. The slave device matches the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the broadcast information is discarded. If they are the same, the SIP Phone resource classification type is matched. If the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a subordinate device of the root device of the same device type.

[0018] Event update module: used for the device to determine whether it is a root device or a slave device after receiving an update event. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests the update event from the root device to which it belongs and completes the update.

[0019] Furthermore, the SIP Phone resource classification types described in the resource allocation module include: Class A, Class B, and Class O, where Class A is a general resource classification, Class B is a type resource classification, and Class C is a stand-alone resource classification, wherein updates to Class O require separate download requests.

[0020] Furthermore, in the type matching module, if the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, then the SIP Phone resource classification type in the mapping relationship table is updated, and the root node list of the slave device is filled with its subordinate root device IP, and the child node list of the root device in the resource allocation table is updated at the same time.

[0021] Furthermore, the slave device described in the event update module requests update events from the root device to which it belongs. If the slave device request fails, the slave device attempts to connect to other root devices to which it belongs. If the connection is successful, the update event is obtained from the root device. If the slave device cannot obtain configurations from all root nodes, the slave device actively initiates a request to the server and downloads relevant configuration files.

[0022] Furthermore, the slave device described in the event update module requests update events from the root device to which it belongs. If the slave device to which it belongs rejects the request due to full load, the slave device attempts to connect to other root devices to which it belongs to request update events. If the SIP Phone resource classification type of other root devices to which it belongs is not exactly the same as the SIP Phone resource classification type of the slave device, update events of different SIP Phone resource classification types need to wait for other root devices with the same SIP Phone resource classification type and to which the slave device belongs to be issued.

[0023] The meanings of the above mentioned English abbreviations:

[0024] SIP Phone: A terminal phone based on SIP protocol transmission, which can realize audio and video calls

[0025] Autop: Automated configuration for multi-device configuration management

[0026] root: root, indicating the root node device, used as a forwarding role

[0027] slave: slave device, indicating that the role is passive, used to listen to root broadcast information

[0028] The present invention indicates the types of different resources or parameters based on the resource table, confirms the role of the device, confirms the root node, indicates the need to support forwarding capability, confirms the child node, and needs to record the corresponding root node at the same time. The root node is discovered and mapped by the slave device, and data is obtained from the root node, which reduces the number of connections between a large number of devices and the server, reduces the consumption of external bandwidth, and uses the broadcast automatic discovery method. The administrator only needs to specify a small number of root nodes to complete the automatic table building of large-scale internal devices, reducing the cost of device configuration and maintenance. The role of each device is confirmed by exchanging data information between devices, and multi-node recording methods are supported, which improves connection stability and traffic load balancing capabilities. Configuration distribution is initiated by the slave device, and the root device is notified to apply for and forward data. It mainly retains the existing deployment method while adding a more efficient method, forming a backup formula for configuring multi-path downloading, and at the same time utilizes the high-speed forwarding characteristics of the intranet to speed up the configuration download speed of the Slave device and improve deployment efficiency.

[0029] It should be understood that the contents described in the summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The above and other features, advantages and aspects of the embodiments of the present invention will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings.

[0031] Figure 1 A flowchart of a method for configuring a multi-device classification proxy based on a SIP Phone according to an embodiment of the present invention is shown;

[0032] Figure 2 A block diagram of a device for configuring a multi-device classification proxy based on a SIP Phone according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0034] According to the implementation mode of the present invention, a method and apparatus for multi-device classification proxy configuration based on SIP Phone are proposed. The resource table indicates the types of different resources or parameters, confirms the role of the device, confirms the root node, indicates the need to support forwarding capability, confirms the child node, and records the corresponding root node at the same time. The root node is discovered and mapped by the slave device, and the data is obtained from the root node, which reduces the number of connections between a large number of devices and the server, reduces the consumption of external bandwidth, and uses the broadcast automatic discovery method. The administrator only needs to specify a small number of root nodes to complete the automatic table building of large-scale internal devices, reducing the cost of device configuration and maintenance. The role of each device is confirmed by exchanging data information between devices, and the multi-node recording method is supported, which improves the connection stability and traffic load balancing capability. Configuration distribution is initiated by the slave device, and the root device is notified to apply for and forward data. It mainly retains the existing deployment method while adding a more efficient method, forming a backup formula for configuring multi-path download, and at the same time utilizes the high-speed forwarding characteristics of the intranet to speed up the configuration download speed of the slave device and improve the deployment efficiency.

[0035] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0036] Figure 1 The present invention is a flowchart of a method for configuring a multi-device classification proxy based on a SIP Phone according to an embodiment of the present invention. The method includes:

[0037] S01: Classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list;

[0038] S02: The administrator designates at least one device as the root device and the rest as slave devices, and updates the resource allocation table and relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root device, and the slave devices listen to the broadcast information during operation.

[0039] S03: When the slave device receives the broadcast information from the root device, it parses the message and matches the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the slave device discards the broadcast information. If they are the same, the SIP Phone resource classification type is matched. If the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a subordinate device of the root device of the same device type.

[0040] S04: After receiving the update event, the device determines whether it is a root device or a slave device. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests to obtain the update event from the root device to which it belongs and completes the update.

[0041] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0042] In order to explain the above-mentioned method for configuring a multi-device classification proxy based on SIP Phone more clearly, a specific embodiment is described below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.

[0043] The following is a specific example to further explain the method of configuring multiple device classification proxy based on SIP Phone in more detail:

[0044] SIP Phone resources are classified into the following types:

[0045] Category A - General resource classification: such as time zone, DNS, WiFi signal, network mode, wallpaper, ringtone, language, server information, contact information;

[0046] Category B - Type resource classification: such as software version, layout configuration;

[0047] Class O - Single-machine resource classification: For example, extension number information. Class O instructions need to be downloaded separately and do not use the proxy forwarding mode.

[0048] Create a resource allocation table, as shown in Table 1:

[0049] Table 1

[0050]

[0051] Create a mapping relationship table, as shown in Table 2:

[0052] Table 2

[0053]

[0054] The administrator specifies devices A1, A2, and A3 as root devices and the remaining devices as slave devices, and updates the resource allocation table, as shown in Table 3:

[0055] Table 3

[0056]

[0057] Update the relationship mapping table, as shown in Table 4:

[0058] Table 4

[0059]

[0060] After all devices are started, devices A1, A2, and A3 periodically broadcast message headers to declare themselves as root, and devices B1, B2, B3, and B4 listen to the broadcast information during operation.

[0061] When devices B1, B2, B3, and B4 receive the broadcast information from devices A1, A2, and A3, they parse the message and find that the Autop servers to which devices B1, B2, B3, and B4 belong are the same as those to which devices A1, A2, and A3 belong, and thus the SIP Phone resource classification type is matched.

[0062] Specifically, if the received Autop server is different from the Autop server to which the user belongs, the broadcast information is discarded.

[0063] Device B1 matches the SIP Phone resource classification type of devices A1, A2, and A3, and finds that it has the same type as device A3, so device B1 is a subordinate device of device A3;

[0064] Device B2 matches the SIP Phone resource classification type of devices A1, A2, and A3, and finds that it has the same type as device A2, so device B2 is a subordinate device of device A2;

[0065] Device B3 matches the SIP Phone resource classification type of devices A1, A2, and A3, and finds that it has the same type as device A1, so device B3 is a subordinate device of device A1;

[0066] Device B4 matches the SIP Phone resource classification type of devices A1, A2, and A3, and is found to have the same type as devices A1, A2, and A3. Therefore, device B4 is a subordinate device of devices A1, A2, and A3.

[0067] Update the SIP Phone resource classification type in the mapping table, and fill in the slave device's root node list with its slave root device IP, as shown in Table 5:

[0068] Table 5

[0069]

[0070] Update the child node list of the root device in the resource allocation table, as shown in Table 6:

[0071] Table 6

[0072]

[0073]

[0074] After receiving the update event, the device determines whether it is a root device or a slave device. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests the update event from the root device to which it belongs and completes the update.

[0075] Specifically, after receiving the update event, devices A1, A2 and A3 determine that they are root devices, connect to the cloud Autop server for update, and after the update is completed, update the timestamp of the resource allocation table and send the update event to their respective slave devices. The updated resource allocation table is shown in Table 7:

[0076] Table 7

[0077]

[0078] After receiving the update event, devices B1, B2, B3, and B4 determine that they are slave devices, and then wait for the update of the root device to which they belong to be completed. The slave device requests the update event from the root device to which it belongs and completes the update.

[0079] Device B1 requests to obtain the type A update event from device A3 to which it belongs and completes the update.

[0080] Device B2 requests to obtain the Class B update event from device A2 to which it belongs and completes the update.

[0081] Device B3 is subordinate to device A1, but its update event is type O, so it directly initiates a request to the server to download the relevant configuration file.

[0082] If device B4 fails to obtain a Class A update event from device A1 to which it belongs, device B4 attempts to connect to another subordinate device A3. Device A3 rejects the request because it is fully loaded. Then device B4 successfully requests a Class B update event from device A2 to which it belongs. The device downloads the Class B update event to complete the update. After the Class B event update is completed, the device again requests a Class A update event from device A3. If the request is successful, the device receives the update event sent by device A3 and completes the update. If the request to obtain a Class A update event from device A3 fails, the device actively initiates a request to the server to download the relevant configuration file.

[0083] Based on the same inventive concept, the present invention also proposes a device for configuring a multi-device classification proxy based on SIP Phone. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated.

[0084] like Figure 2As shown, the device 100 includes:

[0085] Resource allocation module 101: used to classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list;

[0086] Device classification module 102: used for the administrator to designate at least one device as the root device and the rest of the devices as slave devices, and to update the resource allocation table and the relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root, and the slave devices listen to the broadcast information during operation.

[0087] Type matching module 103: used for parsing the message after the slave device receives the broadcast information from the root device, and matching the slave device with the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the broadcast information is discarded. If they are the same, the SIP Phone resource classification type is matched. If the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a slave device of the root device of the same device type.

[0088] Event update module 104: used for the device to determine whether it is a root device or a slave device after receiving an update event. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests to obtain the update event from the root device to which it belongs and completes the update.

[0089] The present invention proposes a device for multi-device classification proxy configuration based on SIP Phone. The device confirms the role of the device based on the resource table indicating the types of different resources or parameters. If it is confirmed as a root node, it indicates that it needs to support forwarding capability. If it is confirmed as a child node, the corresponding root node needs to be recorded at the same time. The root node is discovered and mapped by the slave device. Obtaining data from the root node reduces the number of connections between a large number of devices and the server, reduces the consumption of external bandwidth, and uses a broadcast automatic discovery method. The administrator only needs to specify a small number of root nodes to complete the automatic table building of large-scale internal devices, reducing the cost of device configuration and maintenance. The role of each device is confirmed by exchanging data information between devices. At the same time, a multi-node recording method is supported, and the connection stability and traffic load balancing capability are improved. Configuration distribution is initiated by the slave device, and the root device is notified to apply for and forward data. It mainly retains the existing deployment method while adding a more efficient method to form a backup formula for configuring multi-path downloading. At the same time, the high-speed forwarding characteristics of the intranet are utilized to speed up the configuration download speed of the slave device and improve the deployment efficiency.

[0090] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.

[0091] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for configuring a multi-device classification proxy based on SIP Phone, characterized in that: The method includes: S01: Classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list; S02: The administrator designates at least one device as the root device and the rest as slave devices, and updates the resource allocation table and relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root device, and the slave devices listen to the broadcast information during operation. S03: When the slave device receives the broadcast information from the root device, it parses the message and matches the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the slave device discards the broadcast information. If they are the same, the SIP Phone resource classification type is matched. If the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a subordinate device of the root device of the same device type. S04: After receiving the update event, the device determines whether it is a root device or a slave device. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests to obtain the update event from the root device to which it belongs and completes the update.

2. According to a method for configuring a multi-device classification proxy based on SIP Phone according to claim 1, it is characterized in that: The SIP Phone resource classification types described in S01 include: Class A, Class B, and Class O. Class A is a general resource classification, Class B is a type resource classification, and Class C is a stand-alone resource classification. The update of Class O needs to be downloaded separately.

3. A method for configuring a multi-device classification proxy based on SIP Phone according to claim 1, characterized in that: As described in S03, if the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, then the SIP Phone resource classification type in the mapping relationship table is updated, and the root node list of the slave device is filled with its subordinate root device IP, and the child node list of the root device in the resource allocation table is updated at the same time.

4. The method for configuring a multi-device classification proxy based on SIP Phone according to claim 1, characterized in that: The slave device described in S04 requests to obtain update events from the root device to which it belongs. If the request of the slave device fails, the slave device attempts to connect to other root devices to which it belongs. If the connection is successful, the slave device obtains update events from the root device. If the slave device cannot obtain configuration from all root nodes, the slave device actively initiates a request to the server and downloads the relevant configuration files.

5. The method for configuring multiple device classification agents based on SIP Phone according to claim 1, characterized in that: The slave device described in S04 requests update events from the root device to which it belongs. If the slave device to which it belongs rejects the request due to full load, the slave device attempts to connect to other root devices to which it belongs to request update events. If the SIP Phone resource classification types of other root devices to which it belongs are not exactly the same as the SIP Phone resource classification type of the slave device, update events of different SIP Phone resource classification types need to wait for other root devices with the same SIP Phone resource classification type and to which the slave device belongs to be sent.

6. A device for configuring multiple device classification agents based on SIP Phone, characterized in that: The device includes: Resource allocation module: used to classify resources for SIP Phone and create a resource allocation table, the information of which includes: device name, device role, device MAC address, device model, device IP, Autop server, timestamp and child node list; create a mapping relationship table, the mapping relationship table includes: device name, device role, resource classification information, SIP Phone resource classification type, request name and root node list; Device classification module: The administrator designates at least one device as the root device and the rest as slave devices, and updates the resource allocation table and relationship mapping table. After all devices are started, the root device regularly broadcasts a message header to declare itself as the root device, and the slave devices listen to the broadcast information during operation. Type matching module: used to parse the message after the slave device receives the broadcast information from the root device. The slave device matches the Autop server to which it belongs. If the received Autop server is different from its own Autop server, the broadcast information is discarded. If they are the same, the SIP Phone resource classification type is matched. If the SIPPhone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type, and the slave device is a subordinate device of the root device of the same device type. Event update module: used for the device to determine whether it is a root device or a slave device after receiving an update event. If it is a root device, it connects to the cloud Autop server for update. After the update is completed, the timestamp of the resource allocation table is updated and the update event is sent to the subordinate slave device; if it is a slave device, it waits for the update of the root device to which it belongs to be completed. The slave device requests the update event from the root device to which it belongs and completes the update.

7. The apparatus for configuring multiple device classification agents based on SIP Phone according to claim 6, characterized in that: The SIP Phone resource classification types described in the resource allocation module include: Class A, Class B, and Class O. Class A is a general resource classification, Class B is a type resource classification, and Class C is a stand-alone resource classification. The update of Class O requires a separate download request.

8. The apparatus for configuring multiple device classification agents based on SIP Phone according to claim 6, characterized in that: In the type matching module, if the SIP Phone resource classification type received by the slave device is the same as its own SIP Phone resource classification type, they belong to the same device type. Then, the SIP Phone resource classification type in the mapping relationship table is updated, and the root node list of the slave device is filled with its subordinate root device IP, and the child node list of the root device in the resource allocation table is updated.

9. The apparatus for configuring multiple device classification agents based on SIP Phone according to claim 6, characterized in that: The slave device described in the event update module requests to obtain update events from the root device to which it belongs. If the request of the slave device fails, the slave device attempts to connect to other root devices to which it belongs. If the connection is successful, the update event is obtained from the root device. If the slave device cannot obtain configuration from all root nodes, the slave device actively initiates a request to the server and downloads the relevant configuration files.

10. The apparatus for configuring multiple device classification agents based on SIP Phone according to claim 6, characterized in that: The slave device described in the event update module requests update events from the root device to which it belongs. If the slave device to which it belongs rejects the request due to full load, the slave device attempts to connect to other root devices to which it belongs to request update events. If the SIP Phone resource classification type of other root devices to which it belongs is not exactly the same as the SIP Phone resource classification type of the slave device, update events of different SIP Phone resource classification types need to wait for other root devices with the same SIP Phone resource classification type and to which the slave device belongs to be issued.