Method and device for multi-strategy automatic upgrading of SIP (Session Initiation Protocol) phone

Abstract

The invention provides an SIP telephone multi-strategy automatic upgrading method and device, and the method comprises the steps: an upgrading server administrator newly adds a software version upgrading rule according to an agent requirement, and a client SIP telephone is powered on and accessed to a client network environment; the SIP phone sends an HTTPS upgrading request containing User-Agent information to the upgrading server, and the upgrading server extracts the User-Agent information and matches an upgrading rule to carry out SIP phone software upgrading request response; and after the SIP telephone becomes effective after being restarted, confirming that the version of the telephone is upgraded to a new software version. In this way, unified access is achieved through the cloud upgrading server, the automatic upgrading function of the stock SIP telephone of a non-latest version of a client is achieved, and the deployment cost and time of a user are reduced.

Description

Technical Field

[0001] Embodiments of the present invention generally relate to the technical field of SIP phones, and in particular, to a multi-strategy automatic upgrade method and device for SIP phones. Background Art

[0002] When SIP phone devices leave the factory, they come with a default production software version. There is a certain inventory time cycle from the production of this batch of phones to the hands of agents or customers and subsequent actual deployment. As a result, when actually deployed, the default version of the phone is no longer the latest version, does not support the latest functions or does not meet the new requirements of customers, and a new version needs to be upgraded to meet the deployment requirements. Based on this situation, in the current implementation and deployment, agents arrange technical personnel to assist customers on-site to complete the software version upgrade work before deployment. The main upgrade methods adopted are: for a single phone, through the web upgrade method and setting up a local upgrade environment, and configuring each phone to connect to the local upgrade environment to complete the upgrade to the specified software version.

[0003] However, in terms of deployment flexibility, for the software update of factory-produced phones, before each phone deployment, additional manual configuration of the software upgrade process is required, and it is impossible to achieve the plug-and-play of phone devices when powered on. Especially for deployment situations in multiple batches at different times, multiple manual configurations are required, lacking flexibility.

[0004] In terms of the selection of upgraded software versions, for different SIP phones, only the same software version can be selected for simultaneous upgrade, and it is impossible to distinguish the multi-version upgrade requirements of general versions and customized versions. Customers can only manually divide SIP phones with different requirements into multiple batches and adjust the upgrade environment in sequence to meet the upgrade requirements of different software versions, lacking flexibility, and increasing additional manual classification and configuration costs. Moreover, there may also be upgrade errors due to misoperations, lacking flexibility and operability.

[0005] In terms of deployment environment requirements, for the batch Autop deployment method, in addition to requiring customers to set up the environment on-site, it is also necessary to manually configure the upgrade server path on each SIP phone one by one or rely on the DHCP Option option method to specify the server address information to be upgraded for the SIP phone. For the manual configuration method, it is necessary to operate one by one, increasing the difficulty and workload of configuration; for the DHCP Option batch method, it will be necessary to modify the DHCP environment of the office network currently used by customers, lacking convenience.

[0006] In terms of deployment costs, for the software update of factory-produced phones, customers need to provide additional servers to set up a local upgrade environment, increasing the additional cost of the servers; agents need to provide additional on-site support each time and the cooperation of customers, increasing the human operation costs of agents and customers. Summary of the Invention

[0007] To solve the above problems, the present invention uses a cloud upgrade server for unified access to meet the automatic upgrade function of the inventory SIP phones of customers with non-latest versions, reducing the deployment cost and time of users; uses the customer number field in the version information in the upgrade request HTTPS request actively sent by the SIP phone to the cloud unified upgrade server when powered on to identify customer information, and the device MAC address information to identify a specific device, and the upgrade server selects the corresponding software version to complete the upgrade; uses the upgrade request HTTPS request sent by the SIP phone to the cloud unified upgrade server according to the software activation code input by the user after the SIP phone starts up, and the upgrade server selects the corresponding software version to complete the upgrade according to the software activation code; solves the problem that the software version of the inventory SIP phones in the hands of agents is too old, resulting in the inability to support new functions and new deployment methods during actual customer deployment, reducing the server deployment cost and operation and maintenance cost of agents and customers; simplifies the difficulty of upgrading factory SIP phones. Only by unified configuration on the server side can the SIP phone be automatically updated to the target software version when powered on, achieving plug-and-play, reducing the difficulty of customer deployment and improving deployment efficiency; adopts a multi-strategy software upgrade configuration method to meet the specific needs of different customers and improve the flexibility of the solution.

[0008] According to an embodiment of the present invention, there is provided a method and device for multi-strategy automatic upgrade of a SIP phone.

[0009] In the first aspect of the present invention, there is provided a method for multi-strategy automatic upgrade of a SIP phone. The method includes:

[0010] S01: The upgrade server administrator adds software version upgrade rules according to the agent's requirements. The customer SIP phone is powered on and connected to the customer network environment, where the software versions include: general versions and user-specific customized versions;

[0011] S02: The SIP phone sends an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the SIP phone's HTTPS request and matches the upgrade rules to respond to the SIP phone software upgrade request. The upgrade rules include: upgrade based on the customer number information in the SIP phone's HTTPS request, upgrade based on the MAC address information in the SIP phone's HTTPS request, and upgrade based on the software version activation code included in the SIP phone's HTTPS request;

[0012] S03: Wait for the SIP phone to take effect after restarting and confirm that the phone version has been upgraded to the new software version.

[0013] Further, the general version and the user-specific customized version described in S01 are distinguished by software version naming. The software version naming rule is: <Product Number>.<Major Version Number>.<Minor Version Number>.<Customer Number>. If the customer number is "000", it represents the general version number; if the customer number is non-"000", it represents the user-specific customized version number.

[0014] Further, the content format of the HTTPS upgrade request described in S02 is:

[0015] GET / sip9000N?activate_code=XXXXXX HTTP / 1.1

[0016] Host: cloud.firmware.aledevice.com

[0017] Range: bytes=0-255

[0018] User-Agent: ALE SIP phone model Adapted software version of the series of phones corresponding to this phone model. Series software major version. Software specific version number. Customer number MAC address

[0019] Accept: * / *。

[0020] Further, the steps for upgrading based on the customer number information in the SIP phone HTTPS request described in S02 are: extract the version number information and the phone model in the User-Agent information. If the customer number in the version number information is non-"000", check whether there is a rule in the upgrade rules that contains the customer number corresponding to this phone model. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, obtain the corresponding software version storage path, and transmit the software version data to the SIP phone side through the standard HTTPS response to complete the software version upgrade; if there is no such customer number, skip the customer number matching rule and continue to match other rules;

[0021] The steps for upgrading based on the MAC address information in the SIP phone HTTPS request described in S02 are: extract the MAC address information and the phone model in the User-Agent information, and retrieve the MAC address range rule corresponding to this phone model in the upgrade rules according to the rule priority ranking. If the MAC address matches the MAC address range rule and the current SIP phone version is inconsistent with the target upgrade software version, obtain the corresponding software version storage path, and transmit the software version data to the SIP phone side through the standard HTTPS response to complete the software version upgrade; if there is no upgrade rule that matches this MAC address, continue to match other rules;

[0022] The steps for software version activation code upgrade included in the HTTPS request based on the SIP phone described in S02 are as follows: The customer inputs and confirms the activation code, and the SIP phone sends an HTTPS upgrade request containing the software version activation code information to the upgrade server. The upgrade server extracts the software version activation code and the phone model information in the HTTPS, and retrieves whether there is a rule in the upgrade rules that corresponds to the phone model and the software version activation code. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, the corresponding software version storage path is obtained, and the software version data is transmitted to the SIP phone side through a standard HTTPS response to complete the software version upgrade.

[0023] Further, if there is no rule in the upgrade rules described in S03 that corresponds to the phone model and the software version activation code, other rules continue to be matched.

[0024] In the second aspect of the present invention, a device for automatic multi-strategy upgrade of SIP phones is provided. The device includes:

[0025] Rule addition module: used for the upgrade server administrator to add software version upgrade rules according to proxy requirements. The customer SIP phone is powered on and connected to the customer network environment, where the software versions include: general version and user-specific customized version;

[0026] Request sending module: used for the SIP phone to send an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the SIP phone's HTTPS request and matches the upgrade rules to respond to the SIP phone software upgrade request. The upgrade rules include: upgrade based on the customer number information in the SIP phone's HTTPS request, upgrade based on the MAC address information in the SIP phone's HTTPS request, and upgrade based on the software version activation code included in the SIP phone's HTTPS request;

[0027] Upgrade effect module: used to wait for the SIP phone to take effect after restarting and confirm that the phone version has been upgraded to the new software version.

[0028] Further, the general version and the user-specific customized version described in the rule addition module are distinguished by software version naming. The software version naming rule is: <product number>.<major version number>.<minor version number>.<customer number>, where the customer number being "000" represents the general version number; the customer number being non-"000" represents the user-specific customized version number.

[0029] Further, the content format of the HTTPS upgrade request described in the request sending module is:

[0030] GET / sip9000N?activate_code=XXXXXX HTTP / 1.1

[0031] Host: cloud.firmware.aledevice.com

[0032] Range: bytes=0-255

[0033] User-Agent: ALE SIP phone model adaptation software version of the series of phones corresponding to this phone model. Series software major version. Specific software version number. Customer number MAC address

[0034] Accept: * / *。

[0035] Furthermore, the steps for upgrading based on the customer number information in the SIP phone HTTPS request in the request sending module are as follows: Extract the version number information and phone model in the User-Agent information. If the customer number in the version number information is not "000", retrieve whether there is a rule in the upgrade rules that contains the customer number corresponding to this phone model. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, obtain the corresponding software version storage path, and transmit the software version data to the SIP phone side through a standard HTTPS response to complete the software version upgrade; if there is no such customer number, skip the customer number matching rule and continue to match other rules;

[0036] The steps for upgrading based on the MAC address information in the SIP phone HTTPS request in the request sending module are as follows: Extract the MAC address information and phone model in the User-Agent information, and retrieve the MAC address range rule corresponding to this phone model in the upgrade rules according to the rule priority sorting. If the MAC address matches the MAC address range rule and the current SIP phone version is inconsistent with the target upgrade software version, obtain the corresponding software version storage path, and transmit the software version data to the SIP phone side through a standard HTTPS response to complete the software version upgrade; if there is no upgrade rule that matches this MAC address, continue to match other rules;

[0037] The steps of including the software version activation code upgrade in the HTTPS request based on the SIP phone described in the request sending module are: the customer enters the activation code for confirmation, the SIP phone sends the HTTPS upgrade request containing the software version activation code information to the upgrade server, the upgrade server extracts the software version activation code and phone model information in the HTTPS, and searches the upgrade rules for whether there is a rule containing the corresponding phone model and software version activation code. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, the corresponding software version storage path is obtained, and the software version data is transmitted to the SIP phone side through a standard HTTPS response to complete the software version upgrade.

[0038] Furthermore, if there is no rule including the activation code corresponding to the phone model and software version in the upgrade rules described in the upgrade validation module, other rules will continue to be matched.

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

[0040] SIP: Session initialization Protocol

[0041] MAC address: Media Access Control Address, media access control address

[0042] HTTP: Hypertext Transfer Protocol, Hypertext Transfer Protocol

[0043] HTTPS: Hypertext Transfer Protocol Secure, Hypertext Transfer Protocol Secure

[0044] PBX: Private Branch Exchange

[0045] DHCP: Dynamic Host Configuration Protocol

[0046] The present invention utilizes unified access to a cloud upgrade server to meet the automatic upgrade function of inventory SIP phones of customers that are not of the latest version, reducing the deployment cost and time of users; uses the customer number field in the version information in the upgrade request HTTPS request actively sent by the SIP phone to the cloud unified upgrade server when powered on to identify customer information, and the device MAC address information to identify a specific device, and the upgrade server selects the corresponding software version to complete the upgrade; uses the upgrade request HTTPS request sent by the SIP phone to the cloud unified upgrade server according to the software activation code input by the user after the SIP phone starts up, and the upgrade server selects the corresponding software version to complete the upgrade according to the software activation code; solves the problem that the software version of the inventory SIP phones in the hands of agents is too old, resulting in the inability to support new functions and new deployment methods during actual customer deployment, reducing the server deployment cost and operation and maintenance cost of agents and customers; simplifies the difficulty of upgrading factory SIP phones. Only by unified configuration on the server side can the SIP phone be automatically updated to the target software version when powered on, achieving plug-and-play, reducing the difficulty of customer deployment and improving the deployment efficiency; adopts a multi-strategy software upgrade configuration method to meet the specific needs of different customers and improve the flexibility of the solution.

[0047] It should be understood that the content described in the summary of the invention section is not intended to limit the key or important features of the embodiments of the present invention, nor to limit the scope of the present invention. Other features of the present invention will become easily understandable through the following description. Brief Description of the Drawings

[0048] In combination with the accompanying drawings and with reference to the following detailed description, the above and other features, advantages, and aspects of the embodiments of the present invention will become more apparent. Among them:

[0049] Figure 1 Shows a flowchart of a method for multi-strategy automatic upgrade of a SIP phone according to an embodiment of the present invention;

[0050] Figure 2 Shows a block diagram of a device for multi-strategy automatic upgrade of a SIP phone according to an embodiment of the present invention;

[0051] Figure 3 Shows a flowchart of an upgrade method based on a customer number and a phone MAC address according to an embodiment of the present invention;

[0052] Figure 4 Shows a flowchart of an upgrade method based on a software activation code according to an embodiment of the present invention. Detailed Description of the Embodiments

[0053] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0054] According to an embodiment of the present invention, a method and device for multi-strategy automatic upgrade of SIP phones are proposed. By uniformly accessing through a cloud upgrade server, the automatic upgrade function of inventory SIP phones of customers with non-latest versions is satisfied, reducing the deployment cost and time of users. The customer information is identified by the customer number field in the version information in the upgrade request HTTPS request actively sent by the SIP phone to the cloud unified upgrade server when the SIP phone is powered on and started, and the specific device is identified by the device MAC address information. The upgrade server selects the corresponding software version to complete the upgrade. The upgrade request HTTPS request sent by the SIP phone to the cloud unified upgrade server according to the software activation code input by the user after the SIP phone is started is used, and the upgrade server selects the corresponding software version to complete the upgrade according to the software activation code. The problem that the software version of the inventory SIP phones in the hands of agents is too old, resulting in the inability to support new functions and new deployment methods during actual customer deployment, is solved, and the server deployment cost and operation and maintenance cost of agents and customers are reduced. The difficulty of upgrading factory SIP phones is simplified. Only by uniformly configuring the server side can the SIP phone be automatically updated to the target software version when powered on, achieving plug-and-play, reducing the difficulty of customer deployment and improving the deployment efficiency. A multi-strategy software upgrade configuration method is adopted to meet the specific needs of different customers and improve the flexibility of the solution.

[0055] Next, with reference to several representative embodiments of the present invention, the principles and spirit of the present invention will be elaborated in detail.

[0056] Figure 1 It is a schematic flowchart of a method for multi-strategy automatic upgrade of SIP phones according to an embodiment of the present invention.

[0057] The method includes:

[0058] S01: The upgrade server administrator adds software version upgrade rules according to the requirements of the agent. The customer SIP phone is powered on and connected to the customer network environment, where the software versions include: general versions and user-specific customized versions;

[0059] S02: The SIP phone sends an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the SIP phone's HTTPS request and matches the upgrade rules to respond to the SIP phone software upgrade request. The upgrade rules include: upgrading based on the customer number information in the SIP phone's HTTPS request, upgrading based on the MAC address information in the SIP phone's HTTPS request, and upgrading based on the software version activation code included in the SIP phone's HTTPS request.

[0060] S03: Wait for the SIP phone to take effect after restarting, and confirm that the phone version has been upgraded to the new software version.

[0061] 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 accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution.

[0062] In order to more clearly explain the above method for automatic multi-policy upgrade of SIP phones, the following will be described in conjunction with a specific embodiment. However, it should be noted that this embodiment is only for better explaining the present invention and does not constitute an improper limitation to the present invention.

[0063] The following will further illustrate the method for automatic multi-policy upgrade of SIP phones in more detail with a specific example:

[0064] For the SIP phone software version, it includes a general version and a user-specific customized version.

[0065] General version: It includes the latest functions supported by the SIP phone and meets the needs of general customers. Users can achieve different functional usage requirements through different phone settings.

[0066] User-specific customized version: For users who meet a certain number of SIP phones, a special customized software version can be provided according to user needs. For example, default language selection, built-in company logo, customer-defined configuration requirements, support for special functions, etc.

[0067] In order to distinguish between the general version and the user-specific customized version, the software version naming includes customer number information. For the customized version of customers with special customization requirements, a specific customer number is assigned. The version naming rule is as follows:

[0068] <Product number>.<Major version number>.<Minor version number>.<Customer number>, where the customer number "000" represents the general version number; a customer number other than "000" represents a specific customer number.

[0069] For example:

[0070] 2.14.10.000: represents the general version;

[0071] 2.14.20.100: represents the customized version number for Customer A;

[0072] 2.14.30.101: represents the customized version number for Customer B.

[0073] The administrator on the server side of the upgrade configures different rules to define the target upgrade software version, which is saved in the server-side database. The table structure is defined as follows:

[0074] TB_FIRMWARE_INFO is shown in Table 1:

[0075] Table 1

[0076] Field Type Description Id Int Auto-increment primary key Phone_model Varchar Applicable SIP phone model Version Varchar Software version number information Firmware_path Varchar Software version storage path Create_date Datetime Creation time

[0077] TB_UPGRADE_RULE is shown in Table 2:

[0078] Table 2

[0079] Field Type Description Id Int Auto-increment primary key Rule_type Int Rule type Phone_model Varchar Phone type applicable to the rule Mac_range Varchar SIP phone MAC address range Customer_number Varchar Customer number Activate_code Varchar Software version activation code Firmware_id Int Id associated with the TB_FIRMWARE_INFO table Create_date DateTime Creation time Rule_rank Int Rule sorting

[0080] The software upgrade version application strategy includes:

[0081] 1. Based on the customer number information in the SIP phone HTTPS request, retrieve whether there is a target software upgrade version that matches the customer number in the SIP phone HTTPS request. If there is and the current SIP phone version is different from the target upgrade software version, select the software version corresponding to the matching rule to complete the SIP phone version upgrade; if not, continue to match other strategies.

[0082] 2. Based on the MAC address information in the SIP phone HTTPS request, retrieve whether there is a target software upgrade version that matches the MAC address of this SIP phone. If there is and the current SIP phone version is different from the target upgrade software version, select the corresponding software version to complete the SIP phone version upgrade; if not, continue to match other strategies.

[0083] 3. If the HTTPS request of the SIP phone contains a software version activation code, retrieve whether there is a target software upgrade version corresponding to the activation code. If there is and the current SIP phone version is inconsistent with the target upgrade software version, select the corresponding software version to complete the SIP phone version upgrade; if not, continue to match other policies.

[0084] The upgrade server administrator adds a software version upgrade rule according to the proxy requirements, and the customer SIP phone is powered on and connected to the customer network environment.

[0085] The SIP phone sends an HTTPS upgrade request containing User-Agent information to the upgrade server. The content format of the HTTPS request sent by the SIP phone is:

[0086] GET / sip9000N?activate_code=xxxxxx HTTP / 1.1

[0087] Host: cloud.firmware.aledevice.com

[0088] Range: bytes=0-255

[0089] User-Agent: ALE M32.14.01.1003c28a612003f

[0090] Accept: * / *

[0091] Where:

[0092] The SIP phone model is M3

[0093] The software version information is 2.14.01.100:

[0094] The product number "2" indicates that this is a software version adapted to the M series phone types

[0095] The major version number "14" indicates that this is the major software version of the R140 series

[0096] The minor version number "01" indicates the specific software version number, which increases sequentially under the same series (major version number)

[0097] The customer number "100" indicates that this is a customized software version for the special customer with the customer number 100

[0098] Customer number information: Obtain the customer number content in the software version information from the HTTPS User-Agent field, such as "100" in 2.14.01.100.

[0099] MAC address information: Used to uniquely identify the IP phone, extracted from the HTTPS User-Agent field. For example, the MAC address corresponding to 3c28a612003f is "3C:28:A6:12:00:3F".

[0100] Input of Activate_code value: After the SIP phone starts up successfully, input "*#" + the activation code.

[0101] As Figure 3 shown, the upgrade server extracts the User-Agent information in the HTTPS request of the SIP phone and matches the upgrade rules to respond to the SIP phone software upgrade request:

[0102] Extract the version number information and phone model in the User-Agent information. If the customer number in the version number information is not "000", check whether there is a rule in the upgrade rules that contains the customer number corresponding to this phone model. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, obtain the storage path of the corresponding software version, and transmit the software version data to the SIP phone side through a standard HTTPS response to complete the software version upgrade; if there is no such customer number, skip the customer number matching rule and continue to match other rules;

[0103] Extract the SIP phone MAC address information and phone model in the User-Agent information, and retrieve the MAC address range rule corresponding to this phone model in the upgrade rules according to the rule priority. If this MAC address matches the MAC address range rule and the current SIP phone version is inconsistent with the target upgrade software version, obtain the storage path of the corresponding software version, and transmit the software version data to the SIP phone side through a standard HTTPS response to complete the software version upgrade; if there is no upgrade rule that matches this MAC address, continue to match other rules.

[0104] As Figure 4As shown, after the SIP phone is started, after the customer enters "*#" + "software version activation code" and confirms, the SIP phone sends an HTTPS upgrade request containing the software version activation code information to the upgrade server: https: / / cloud.firmware.aledevice.com / sip9000N?activate_code=xxxxxx. The upgrade server extracts the activate_code information in the HTTPS URL and the phone model in the User-Agent, and retrieves whether there is a rule in the upgrade rules that contains the corresponding phone model and software activation code. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, obtain the corresponding software version storage path, and transmit the software version data to the SIP phone side through a standard HTTPS response to complete the software version upgrade; if it does not exist, continue to match other rules.

[0105] Specifically, for example, Company A purchases a batch of SIP phones from an agent. Due to inventory reasons, the built-in software version of these phones is Firmware_A, which is relatively old and cannot support the function of accessing the PBX environment of Company A's customers. This function is only supported on the new general version Firmware_B. Before the agent provides a solution for deployment, the SIP phone version needs to be upgraded to the new version Firmware_B. Then the agent contacts the cloud upgrade server administrator to provide the information of this batch of SIP phones, including: phone model, phone MAC address, and the expected target software version Firmware_B; after the cloud upgrade server administrator confirms that the information is correct, create an upgrade rule based on the MAC address of this batch of SIP phones and upload the target upgrade software version Firmware_B; the customer opens the packaging of the SIP phone and directly powers on the SIP phone to access the network;. Wait for the SIP phone to take effect after restarting and confirm that the phone version has been upgraded to the new software version Firmware_B; the SIP phone is deployed and connected to the customer's PBX environment and can be used normally.

[0106] Specifically, for example, Company B purchases a batch of special customized phones from an agent. The built-in software version of the phones is Firmware_111_A. By the time of deployment, the software version of the customized phones is no longer the latest version, and the newly added customized requirements and default configuration behaviors no longer meet the requirements of Company B's customers. Company B requests the agent to upgrade to the latest customized version, Firmware_111_B. The customer number of the customized version is 111. Then the agent contacts the cloud upgrade server administrator to provide information about this batch of SIP phones, including: phone model, customer number, phone MAC address, and the expected target software version, Firmware_111_B. After the cloud upgrade server administrator confirms that the information is correct, the administrator creates an upgrade rule based on the MAC addresses of this batch of SIP phones and uploads the target upgrade software version, Firmware_111_B. The customer opens the packaging of the SIP customized phone and directly powers on the SIP phone to connect to the network. After waiting for the SIP customized phone to be automatically upgraded and the phone to restart and take effect, it is confirmed that the phone version has been upgraded to the new customized software version, Firmware_111_B, for this customer. The SIP customized phone is deployed and connected to the customer environment and can be used normally.

[0107] Specifically, for example, Company C purchases SIP phones from an agent in small batches at irregular intervals. The software versions of different batches of SIP phones are different due to inventory reasons. Due to business relationships, Company C has a small purchase volume each time but a large number of batches. Company C needs the agent to assist its customers in upgrading each purchase batch to the new general software version, Firmware_B. Then the agent contacts the cloud upgrade server administrator to apply for creating a software activation code for Firmware_B. After the cloud upgrade server administrator confirms that the information is correct, the administrator randomly generates a software activation code, 45310, establishes an association between the upgrade rule and the target upgrade software version, Firmware_B, uploads the target upgrade software version, Firmware_B, and informs the agent of the software activation code corresponding to this software version. The agent tells the software version activation code to the customer. Each time the customer needs to deploy the purchased SIP phone, the customer opens the packaging of the SIP phone and directly powers on the SIP phone to connect to the network. After the SIP phone starts, the customer inputs "*#45310" and confirms. Then the SIP phone automatically requests the cloud upgrade server to upgrade the software version. After waiting for the phone to be automatically upgraded and the phone to restart and take effect, it is confirmed that the phone version has been upgraded to the new software version, Firmware_B. The SIP phone is deployed and connected to the customer environment and can be used normally.

[0108] Based on the same inventive concept, the present invention also proposes a device for automatic multi-strategy upgrade of SIP phones. The implementation of this device can refer to the implementation of the above method, and the repeated parts will not be described again. As Figure 2 shown, the device 100 includes:

[0109] Rule addition module 101: It is used for the server administrator to add software version upgrade rules according to the agent's requirements. When the customer's SIP phone is powered on, it is connected to the customer's network environment. The software versions include: general version and user-specific customized version;

[0110] Request sending module 102: It is used for the SIP phone to send an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the SIP phone's HTTPS request and matches the upgrade rules to respond to the SIP phone software upgrade request. The upgrade rules include: upgrading based on the customer number information in the SIP phone's HTTPS request, upgrading based on the MAC address information in the SIP phone's HTTPS request, and upgrading based on the software version activation code included in the SIP phone's HTTPS request;

[0111] Upgrade effective module 103: It is used to wait for the SIP phone to take effect after restarting and confirm that the phone version has been upgraded to the new software version.

[0112] A device for automatic multi-strategy upgrade of SIP phones proposed by the present invention uses a cloud upgrade server for unified access to meet the automatic upgrade function of the customer's out-of-date inventory SIP phones, reducing the user's deployment cost and time; uses the customer number field in the version information in the upgrade request HTTPS request actively sent by the SIP phone to the cloud unified upgrade server when it is powered on to identify customer information, and the device MAC address information to identify specific devices, and the upgrade server selects the corresponding software version to complete the upgrade; uses the upgrade request HTTPS request sent by the SIP phone to the cloud unified upgrade server according to the software activation code input by the user after the SIP phone is started, and the upgrade server selects the corresponding software version to complete the upgrade according to the software activation code; solves the problem that the software version of the SIP phones in the agent's inventory is too old, resulting in the inability to support new functions and new deployment methods during actual customer deployment, reducing the server deployment cost and operation and maintenance cost of the agent and the customer; simplifies the difficulty of upgrading the factory SIP phones. Only by unified configuration on the server side can the SIP phone be automatically updated to the target software version when powered on, achieving plug-and-play, reducing the difficulty of customer deployment and improving the deployment efficiency; adopts a multi-strategy software upgrade configuration method to meet the specific needs of different customers and improve the flexibility of the solution.

[0113] Although the spirit and principles 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 each aspect does not mean that the features in these aspects cannot be combined for benefit. This division is only for the convenience of expression. The present invention aims to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

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

Claims

1. A method for automatic multi-strategy upgrade of a SIP phone, characterized in that: The method includes: S01: The upgrade server administrator adds a new software version upgrade rule according to the agent's requirements, and the customer's SIP phone is powered on and connected to the customer's network environment. The software versions include: a general version and a user-specific customized version; S02: The SIP phone sends an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the HTTPS request of the SIP phone, matches the upgrade rules and responds to the SIP phone software upgrade request. The upgrade rules include: upgrading based on the customer number information in the HTTPS request of the SIP phone, upgrading based on the MAC address information in the HTTPS request of the SIP phone, and upgrading based on the software version activation code contained in the HTTPS request of the SIP phone. S03: Wait for the SIP phone to restart and take effect, and confirm that the phone version has been upgraded to the new software version.

2. A method for automatic multi-strategy upgrade of a SIP phone according to claim 1, characterized in that: The general version and user-specific customized version described in S01 are distinguished by software version naming. The software version naming rule is: <product number>.<major version number>.<minor version number>.<customer number>, where the customer number "000" represents the general version number; the customer number other than "000" represents the user-specific customized version number.

3. A method for automatic multi-strategy upgrade of a SIP phone according to claim 1, characterized in that: The content format of the HTTPS upgrade request described in S02 is: GET / sip9000N? activate_code=XXXXXX HTTP / 1.1 Host:cloud.firmware.aledevice.com Range: bytes = 0-255 User-Agent: ALE SIP phone model. The software version of the series of phones that are compatible with this phone model. The major version of the series software. The specific software version number. The customer number MAC address Accept: * / *.

4. A method for automatic multi-strategy upgrade of a SIP phone according to claim 2 or 3, characterized in that: The step of upgrading based on the customer number information in the SIP phone HTTPS request described in S02 is: extracting the version number information and phone model in the User-Agent information, and if the customer number in the version number information is not "000", searching whether there is a rule containing the customer number corresponding to the phone model in the upgrade rules, and if so, and the current SIP phone version is inconsistent with the target upgrade software version, obtaining the corresponding software version storage path, transmitting the software version data to the SIP phone side through a standard HTTPS response, and completing the software version upgrade; if the customer number does not exist, skipping the customer number matching rule, and continuing to match other rules; The upgrade step based on the MAC address information in the HTTPS request of the SIP phone described in S02 is: extract the MAC address information and phone model in the User-Agent information, retrieve the MAC address range rule corresponding to the phone model in the upgrade rule according to the rule priority, if the MAC address matches the MAC address range rule and the current SIP phone version is inconsistent with the target upgrade software version, then obtain the corresponding software version storage path, transmit the software version data to the SIP phone side through a standard HTTPS response, and complete the software version upgrade; if there is no upgrade rule that matches the MAC address, continue to match other rules; The steps of including the software version activation code upgrade in the HTTPS request based on the SIP phone described in S02 are: the customer enters the activation code for confirmation, the SIP phone sends an HTTPS upgrade request containing the software version activation code information to the upgrade server, the upgrade server extracts the software version activation code and phone model information in HTTPS, and searches the upgrade rules for whether there is a rule containing the corresponding phone model and software version activation code. If so, and the current SIP phone version is inconsistent with the target upgrade software version, the corresponding software version storage path is obtained, and the software version data is transmitted to the SIP phone side through a standard HTTPS response to complete the software version upgrade.

5. A method for automatic multi-strategy upgrade of a SIP phone according to claim 1, characterized in that: If there is no rule including the activation code corresponding to the phone model and software version in the upgrade rules described in S03, other rules will continue to be matched.

6. A device for automatic multi-strategy upgrade of a SIP phone, characterized in that: The device includes: New rule module: used to upgrade the server administrator to add software version upgrade rules according to the agent's requirements. The customer's SIP phone is powered on and connected to the customer's network environment. The software versions include: general version and user-specific customized version; Request sending module: used for the SIP phone to send an HTTPS upgrade request containing User-Agent information to the upgrade server. The upgrade server extracts the User-Agent information in the HTTPS request of the SIP phone, matches the upgrade rules to respond to the SIP phone software upgrade request, and the upgrade rules include: upgrade based on the customer number information in the HTTPS request of the SIP phone, upgrade based on the MAC address information in the HTTPS request of the SIP phone, and upgrade based on the software version activation code included in the HTTPS request of the SIP phone; Upgrade effectiveness module: used to wait for the SIP phone to restart before taking effect, confirming that the phone version has been upgraded to the new software version.

7. A device for automatic multi-strategy upgrade of a SIP phone according to claim 6, characterized in that: The general version and user-specific customized version described in the new rule module are distinguished by software version naming. The software version naming rule is: <product number>.<major version number>.<minor version number>.<customer number>, where the customer number "000" represents the general version number; the customer number other than "000" represents the user-specific customized version number.

8. The device for automatic multi-strategy upgrade of a SIP phone according to claim 6, characterized in that: The HTTPS upgrade request content format described in the request sending module is: GET / sip9000N? activate_code=XXXXXX HTTP / 1.1 Host:cloud.firmware.aledevice.com Range: bytes = 0-255 User-Agent: ALE SIP phone model. The software version of the series of phones that are compatible with this phone model. The major version of the series software. The specific software version number. The customer number MAC address Accept: * / *.

9. A device for automatic multi-strategy upgrade of a SIP phone according to claim 7 or 8, characterized in that: The steps of upgrading based on the customer number information in the SIP phone HTTPS request described in the request sending module are: extracting the version number information and phone model in the User-Agent information, if the customer number in the version number information is not "000", searching whether there is a rule containing the customer number corresponding to the phone model in the upgrade rules, if there is and the current SIP phone version is inconsistent with the target upgrade software version, then obtaining the corresponding software version storage path, transmitting the software version data to the SIP phone side through a standard HTTPS response, and completing the software version upgrade; if the customer number does not exist, skipping the customer number matching rule, and continuing to match other rules; The upgrade step based on the MAC address information in the HTTPS request of the SIP phone described in the request sending module is: extract the MAC address information and phone model in the User-Agent information, retrieve the MAC address range rule corresponding to the phone model in the upgrade rule according to the rule priority sorting, if the MAC address matches the MAC address range rule and the current SIP phone version is inconsistent with the target upgrade software version, then obtain the corresponding software version storage path, transmit the software version data to the SIP phone side through the standard HTTPS response, and complete the software version upgrade; if there is no upgrade rule that matches the MAC address, continue to match other rules; The steps of including the software version activation code upgrade in the HTTPS request based on the SIP phone described in the request sending module are: the customer enters the activation code for confirmation, the SIP phone sends the HTTPS upgrade request containing the software version activation code information to the upgrade server, the upgrade server extracts the software version activation code and phone model information in the HTTPS, and searches the upgrade rules for whether there is a rule containing the corresponding phone model and software version activation code. If it exists and the current SIP phone version is inconsistent with the target upgrade software version, the corresponding software version storage path is obtained, and the software version data is transmitted to the SIP phone side through a standard HTTPS response to complete the software version upgrade.

10. The device for automatic multi-strategy upgrade of a SIP phone according to claim 6, characterized in that: If there is no rule containing the activation code corresponding to the phone model and software version in the upgrade rules described in the upgrade effective module, other rules will continue to be matched.

Images