Parameter acquisition method, electronic equipment and storage medium

Abstract

The invention provides a parameter acquisition method, electronic equipment and a storage medium. The method comprises the following steps: determining a target parameter acquisition strategy in at least one standby parameter acquisition strategy under the condition of confirming that the terminal does not acquire a VoIP parameter; and acquiring the VoIP parameter based on the target parameter acquisition strategy. Therefore, at least under the condition that a TR069 server is not arranged or the VoIP parameter is not successfully acquired by sending a parameter acquisition request to the TR069 server, the VoIP parameter can be actively acquired through other standby parameter acquisition strategies, so that the terminal can acquire the VoIP parameter in time, and the influence on the use of the VoIP function is avoided.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a parameter acquisition method, an electronic device and a storage medium. Background Art

[0002] Voice over Internet Protocol (VoIP) is a voice call technology that uses the Internet Protocol (IP) to achieve voice calls and multimedia conferences. In actual applications, VoIP-supported devices can only achieve VoIP registration after obtaining VoIP parameters and correctly configuring VoIP parameters. At present, for obtaining VoIP parameters, the general practice of operators is to configure VoIP parameters in a specific server (such as a TR069 server). After the TR069 server detects that the terminal device is online, it sends the VoIP parameters to the device.

[0003] However, when obtaining VoIP parameters in the above manner, once an abnormality occurs in the TR069 server, or an abnormality occurs in the TR069 channel of the terminal device, or if the TR069 server is not deployed, it is easy for the device to fail to obtain the VoIP parameters in time, thereby affecting the user's use of the VoIP function. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a parameter acquisition method, an electronic device and a storage medium to solve the above problems.

[0005] In a first aspect, a parameter acquisition method is provided, which is applied to a terminal, and the method includes: when confirming that the terminal has not acquired VoIP parameters, determining a target parameter acquisition strategy in at least one backup parameter acquisition strategy; and acquiring the VoIP parameters based on the target parameter acquisition strategy.

[0006] In a second aspect, a parameter acquisition device is provided, which is applied to a terminal, and the method includes:

[0007] A determination module, configured to determine a target parameter acquisition strategy from at least one backup parameter acquisition strategy when it is confirmed that the terminal has not acquired the VoIP parameters;

[0008] An acquisition module is used to acquire the VoIP parameters based on the target parameter acquisition strategy.

[0009] In a third aspect, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0010] Memory, used to store computer programs;

[0011] The processor is used to implement any method step described in the first aspect when executing a program stored in the memory.

[0012] In a fourth aspect, a computer-readable storage medium is provided, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any method step described in the first aspect is implemented.

[0013] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute any of the parameter acquisition methods described above.

[0014] The beneficial effects of the embodiments of the present application include at least:

[0015] The embodiment of the present application provides a parameter acquisition method, an electronic device and a storage medium. In the embodiment of the present application, when it is confirmed that the terminal has not obtained the VoIP parameters, a target parameter acquisition strategy can be determined in at least one backup parameter acquisition strategy, and the VoIP parameters can be obtained based on the target parameter acquisition strategy. In this way, when the TR069 server is not deployed, or when the VoIP parameters are not successfully obtained by sending a parameter acquisition request to the TR069 server, the VoIP parameters can be obtained through other backup parameter acquisition strategies, thereby ensuring that the terminal can actively or timely obtain the VoIP parameters to avoid affecting the user's use of the VoIP function.

[0016] Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0020] Figure 1A flow chart of a parameter acquisition method provided in an embodiment of the present application;

[0021] Figure 2 A flowchart of another parameter acquisition method provided in an embodiment of the present application;

[0022] Figure 3 A flowchart of another parameter acquisition method provided in an embodiment of the present application;

[0023] Figure 4 A schematic diagram of the structure of a parameter acquisition device provided in an embodiment of the present application;

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

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

[0026] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0027] The following will describe in detail a parameter acquisition method provided by an embodiment of the present application in combination with a specific implementation method. Figure 1 As shown, the following steps may be included:

[0028] S101: When it is confirmed that the terminal has not acquired the VoIP parameters, determine a target parameter acquisition strategy from at least one standby parameter acquisition strategy.

[0029] S102: Acquire the VoIP parameters based on the target parameter acquisition strategy.

[0030] The following is a unified description of S101 and S102:

[0031] VoIP parameters may include, but are not limited to, basic parameters of VoIP registration, such as one or more of URI, AuthUserName, AuthPassword, ProxyServer, ProxyServrport, RegistrarServer, RegistrarServerPort, or UserAgentDomain, etc.

[0032] In actual applications, if the TR069 server is abnormal, or the TR069 channel of the terminal device is abnormal, or the TR069 server is not deployed, the terminal will be unable to obtain VoIP parameters, thereby affecting the user's use of the VoIP function.

[0033] In one embodiment, the situation that the terminal has not obtained the VoIP parameters can be determined by the following steps: detecting the VoIP registration state of the terminal, and sending a parameter acquisition request to a second preset server when the VoIP registration state is abnormal, wherein the parameter acquisition request is used to request to obtain the VoIP parameters, and when the parameter acquisition request fails to be sent, or the message returned by the second preset server is an error message, it is determined that the terminal has not obtained the VoIP parameters. The second preset server refers to a server for providing VoIP parameters, for example, a TR069 server.

[0034] In an exemplary embodiment, the implementation of detecting the VoIP registration status of the terminal may include: sending a status confirmation message to a VoIP registration server, so that the VoIP registration server returns corresponding registration status information based on the status confirmation message, and when the registration status information is first preset information, determining that the VoIP registration status is normal, or when the registration status information is second preset information, determining that the VoIP registration status is abnormal.

[0035] In an exemplary embodiment, the terminal can send an Option message (i.e., a status confirmation message) to the VoIP registration server every preset time interval (e.g., 30 minutes). If the VoIP registration server replies with a first preset message (e.g., "200 OK") after receiving the Option message from the terminal, the VoIP registration status is normal; if the VoIP registration server replies with a second preset message (e.g., "403 forbidden") after receiving the Option message from the terminal, the VoIP registration status is abnormal. In addition, there is also a situation where the VoIP registration server does not respond, in which case the VoIP registration status is also considered abnormal.

[0036] Based on this, in an embodiment of the present application, at least one backup parameter acquisition strategy is pre-arranged in the terminal, so that when the terminal fails to obtain the VoIP parameters, the VoIP parameters can be actively acquired by selecting a target parameter acquisition strategy from at least one backup parameter acquisition strategy.

[0037] Wherein, at least one of the backup parameter acquisition strategies includes: a text message acquisition strategy and a link acquisition strategy. In an exemplary embodiment, determining the implementation of the target parameter acquisition strategy in at least one of the backup parameter acquisition strategies may include:

[0038] Step A1, obtaining a preset policy acquisition requirement of the terminal;

[0039] Step A2, when the preset policy acquisition requirement is security, determining the SMS acquisition policy as the target parameter acquisition policy; or

[0040] Step A3: when the preset strategy acquisition requirement is efficiency, determine the link acquisition strategy as the target parameter acquisition strategy.

[0041] The preset policy acquisition requirement can be set by the user according to actual needs, that is, if the user pays more attention to security, the preset policy acquisition requirement can be set to security; if the user pays more attention to efficiency, the preset policy acquisition requirement can be set to efficiency. In other implementations, it can also be set according to the performance of the terminal.

[0042] In this embodiment, when the preset policy acquisition requirement is security, the SMS acquisition strategy with higher security is determined as the target parameter acquisition strategy; and when the preset policy acquisition requirement is efficiency, the link acquisition strategy with higher parameter acquisition efficiency is determined as the target parameter acquisition strategy. In this way, the appropriate backup parameter acquisition strategy can be automatically selected as the target parameter acquisition strategy according to user needs to achieve the acquisition of VoIP parameters.

[0043] In an exemplary implementation, there is a situation where only one standby parameter acquisition strategy is deployed in the terminal. In this case, the standby parameter acquisition strategy deployed in the terminal can be directly determined as the target parameter acquisition strategy to achieve the acquisition of VoIP parameters.

[0044] As for how to obtain the VoIP parameters based on the target parameter acquisition strategy, it will be explained in detail through the following embodiments and will not be described in detail here.

[0045] In addition, in another embodiment of the present application, the following steps may be further included: when the VoIP parameters are obtained through the parameter acquisition request, or when the VoIP parameters are obtained based on the target parameter acquisition strategy, VoIP registration is performed based on the VoIP parameters. In this way, after the VoIP parameters are obtained, VoIP registration can be automatically performed based on the VoIP parameters, thereby providing the user with the VoIP function in a timely manner.

[0046] In the embodiment of the present application, when it is confirmed that the terminal has not obtained the VoIP parameters, a target parameter acquisition strategy can be determined in at least one backup parameter acquisition strategy, and the VoIP parameters can be obtained based on the target parameter acquisition strategy. In this way, when the TR069 server is not deployed, or when the VoIP parameters are not successfully obtained by sending a parameter acquisition request to the TR069 server, the VoIP parameters can be obtained through other backup parameter acquisition strategies, thereby ensuring that the terminal can obtain the VoIP parameters in time to avoid affecting the user's use of the VoIP function.

[0047] See also Figure 2 , is a flow chart of another embodiment of a parameter acquisition method provided in an embodiment of the present application. Figure 2 The process shown in the above Figure 1 Based on the process shown in FIG. 1 , the following describes how to obtain the VoIP parameters based on the target parameter acquisition strategy when the SMS acquisition strategy is determined as the target parameter acquisition strategy. Figure 2 As shown, the process may include the following steps:

[0048] S201, obtaining a device identifier of the terminal and a user identifier of a user identification card corresponding to the terminal;

[0049] S202, generating a first SMS content in a preset format based on the device identifier and the user identifier;

[0050] S203, sending the first SMS content to a first preset server;

[0051] S204, receiving a second SMS content returned by the first preset server based on the first SMS content;

[0052] S205: Acquire the VoIP parameters based on the second SMS content.

[0053] The following is a unified description of S201-S205:

[0054] The device identifier is used to uniquely identify the terminal, for example, IMEI (International Mobile Equipment Identity), and is used to ensure that the first preset server can feed back the corresponding VoIP parameters or the backup link of the VoIP parameters to the terminal.

[0055] The subscriber identification card refers to a SIM (Subscriber Identity Module) card used in the terminal, which can be a physical identification card or an electronic identification card. The subscriber identification card is used to enable the first preset server to detect whether the SIM card of the terminal initiating the request is legal.

[0056] The user identifier can be used to uniquely identify a user identification card, for example, IMSI (International Mobile Subscriber Identity).

[0057] The first preset server can be any applicable SMS center, service platform, etc. Among them, the SMS center is called Short Message Service Center (SMSC), which is a network component used to transmit SMS in a mobile network and has the functions of SMS forwarding and SMS storage. In actual applications, VoIP parameters are pre-deployed in the first preset server, and the VoIP parameters correspond to the device identifier one by one.

[0058] In this embodiment, the terminal can generate a first SMS content in a preset format based on the device identifier and the user identifier, and send the first SMS content to the first preset server to request the VoIP parameters from the first preset server. After receiving the first SMS content, the first preset server first detects whether the SIM card of the terminal that initiates the request is legal based on the user identifier included in the first SMS content. After determining that it is legal, it searches for the corresponding VoIP parameters based on the device identifier included in the first SMS content, generates a second SMS content based on the VoIP parameters, and feeds back the VoIP parameters to the terminal by sending the second SMS content to the terminal. After receiving the second SMS content returned by the first preset server, the terminal obtains the VoIP parameters by parsing the second SMS content.

[0059] For example, the IMEI number of the terminal is 123456789012345, and the IMSI number of the SIM card corresponding to the terminal is 460199100107816, then the content of the first SMS may be IMEI:123456789012345IMSI:460199100107816.

[0060] In addition, in actual applications, the SMS destination address can also be filled in as the SMS destination address for sending SMS messages. The SMS destination address can be composed of a device identifier and a part of a user identifier. For example, if the IMEI number is 123456789012345 and the MSIN is 9100107816, then the SMS destination address can be: 1234567890123459100107816.

[0061] In this way, after receiving the text message, the first preset server can detect whether the text message is used to obtain VoIP parameters based on the text message destination address. When it is detected that the text message destination address is a combination of the IMEI number and the MSIN number, it can be determined that it is a text message used to obtain VoIP parameters, and after finding the corresponding VoIP parameters, the VoIP parameters are fed back to the terminal; of course, it is also possible to determine whether the text message is a text message used to obtain VoIP parameters based on the content of the first text message.

[0062] In the application, the first preset server can feedback VoIP parameters in two ways. When it is detected that the VoIP parameters to be configured are less than the upper limit of the number of characters in the SMS (such as 160 characters), it can directly feedback to the terminal in the form of SMS content. When it is detected that the VoIP parameters are greater than the upper limit of the number of characters in the SMS, the first backup link synchronized with the VoIP parameters can be sent to the terminal, and the terminal obtains the VoIP parameters through the backup link. In this way, it can be ensured that the terminal obtains the complete VoIP parameters at one time.

[0063] Based on this, in one embodiment, S205 may include the following steps:

[0064] Step B1, determining whether the second SMS content contains a target parameter;

[0065] Step B2: when the second SMS content includes the target parameter, determining the target parameter as the VoIP parameter; or,

[0066] Step B3: when the second SMS content does not contain the target parameter, searching for a first standby link in the second SMS content, and accessing a corresponding first storage location based on the first standby link to obtain the VoIP parameter from the first storage location.

[0067] As a possible implementation, the terminal can determine whether the target parameter is contained by identifying whether the second SMS content contains text in a specific format, where the specific format is a format pre-agreed upon by the terminal and the first preset server and is used to identify the target parameter, for example, a format such as enclosing brackets around the target parameter.

[0068] As another possible implementation, the terminal can determine whether the target parameter is included in the second SMS content by identifying whether the key field of the specific parameter is included in the second SMS content. The specific parameter here refers to VoIP parameters, such as URI, AuthUserName, AuthPassword, ProxyServer, ProxyServrport, RegistrarServer, RegistrarServerPort, UserAgentDomain, etc.

[0069] When the target parameters are included in the second SMS content, the target parameters can be directly determined as VoIP parameters. When the target parameters are not included in the second SMS content, it means that the first preset server returns the VoIP parameters in the form of a backup link. At this time, the first backup link can be searched in the second SMS content (the VoIP parameters are pre-synchronized in the first backup link), and the corresponding first storage location can be accessed based on the first backup link to obtain the VoIP parameters from the first storage location.

[0070] pass Figure 2 The process shown can obtain the VoIP parameters by requesting the VoIP parameters from the first preset server through the first SMS content generated by the device identification of the terminal and the user identification of the user identification card corresponding to the terminal, thereby obtaining the VoIP parameters through the SMS acquisition strategy.

[0071] See also Figure 3 , is a flow chart of another embodiment of a parameter acquisition method provided in an embodiment of the present application. Figure 3 The process shown in the above Figure 1 Based on the process shown in FIG. 1 , the following describes how to obtain the VoIP parameters based on the target parameter acquisition strategy when the link acquisition strategy is determined as the target parameter acquisition strategy. Figure 3 As shown, the process may include the following steps:

[0072] S301, obtaining a preset second standby link;

[0073] S302: Access a corresponding second storage location based on the second standby link to obtain the VoIP parameter from the second storage location.

[0074] In actual applications, multiple VoIP parameters can be synchronized to the second backup link in advance. The VoIP parameters in the second backup link can be in the format of a file, such as a txt file, an xml file, etc., and each file can be named with a device identifier to mark the VoIP parameters in the file, such as IMEI.txt, IMEI.xml.

[0075] Based on this, in the embodiment of the present application, the terminal can obtain the second standby link, and access the corresponding second storage location by sending a curl request to the second standby link, so as to obtain the files of all VoIP parameters pre-synchronized to the second standby link from the second storage location. After obtaining these files, the terminal can identify the file names to determine the VoIP parameters it needs. In this way, the VoIP parameters can be obtained through the link acquisition strategy.

[0076] Based on the same technical concept, the embodiment of the present application also provides a parameter acquisition device, such as Figure 4 As shown, the device may include:

[0077] A determination module 401 is used to determine a target parameter acquisition strategy from at least one backup parameter acquisition strategy when it is confirmed that the terminal has not acquired the VoIP parameters;

[0078] The acquisition module 402 is configured to acquire the VoIP parameters based on the target parameter acquisition strategy.

[0079] In a possible implementation, at least one backup parameter acquisition strategy includes: a text message acquisition strategy and a link acquisition strategy, and the determination module 401 may be used to:

[0080] Obtaining a preset policy acquisition requirement of the terminal;

[0081] In the case where the preset policy acquisition requirement is security, determining the SMS acquisition policy as the target parameter acquisition policy; or

[0082] When the preset strategy acquisition requirement is efficiency, the link acquisition strategy is determined as the target parameter acquisition strategy.

[0083] In a possible implementation, when the SMS acquisition strategy is determined as the target parameter acquisition strategy, the determination module 401 may also be used to:

[0084] Obtaining a device identification of the terminal and a user identification of a user identification card corresponding to the terminal;

[0085] Based on the device identifier and the user identifier, generating first SMS content in a preset format;

[0086] Sending the first SMS content to a first preset server;

[0087] Receiving a second SMS content returned by the first preset server based on the first SMS content;

[0088] The VoIP parameter is obtained based on the second SMS content.

[0089] In a possible implementation, the determining module 401 may also be used to:

[0090] Determining whether the second SMS content contains a target parameter;

[0091] In a case where the target parameter is included in the second SMS content, determining the target parameter as the VoIP parameter; or,

[0092] In the case that the second SMS content does not include the target parameter, a first standby link is searched in the second SMS content, and a corresponding first storage location is accessed based on the first standby link to obtain the VoIP parameter from the first storage location.

[0093] In a possible implementation, when the link acquisition strategy is determined as the target parameter acquisition strategy, the acquisition module 402 may be used to:

[0094] Get the preset second backup link;

[0095] A corresponding second storage location is accessed based on the second standby link to obtain the VoIP parameter from the second storage location.

[0096] In a possible implementation, the device further includes a detection module, which is used to:

[0097] Detecting the VoIP registration status of the terminal;

[0098] In the case where the VoIP registration state is abnormal, sending a parameter acquisition request to a second preset server, wherein the parameter acquisition request is used to request to acquire VoIP parameters;

[0099] When the parameter acquisition request fails to be sent, or the message returned by the second preset server is error information, it is determined that the terminal has not acquired the VoIP parameters.

[0100] In a possible implementation, the detection module is further used to:

[0101] Sending a status confirmation message to the VoIP registration server, so that the VoIP registration server returns corresponding registration status information based on the status confirmation message;

[0102] In a case where the registration status information is the first preset information, determining that the VoIP registration status is normal; or

[0103] When the registration status information is the second preset information, it is determined that the VoIP registration status is abnormal.

[0104] In a possible implementation, the device further includes a registration module, configured to:

[0105] When the VoIP parameters are obtained through the parameter acquisition request, or when the VoIP parameters are obtained based on the target parameter acquisition policy, VoIP registration is performed based on the VoIP parameters.

[0106] In the embodiment of the present application, when it is confirmed that the terminal has not obtained the VoIP parameters, a target parameter acquisition strategy can be determined in at least one backup parameter acquisition strategy, and the VoIP parameters can be obtained based on the target parameter acquisition strategy. In this way, when the TR069 server is not deployed, or when the VoIP parameters are not successfully obtained by sending a parameter acquisition request to the TR069 server, the VoIP parameters can be obtained through other backup parameter acquisition strategies, thereby ensuring that the terminal can obtain the VoIP parameters in time to avoid affecting the user's use of the VoIP function.

[0107] Based on the same technical concept, the embodiment of the present application also provides an electronic device, such as Figure 5 As shown, it includes a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0108] Memory 113, used for storing computer programs;

[0109] The processor 111 is used to execute the program stored in the memory 113 to implement the following steps:

[0110] In the case of confirming that the terminal has not acquired the VoIP parameters, determining a target parameter acquisition strategy in at least one standby parameter acquisition strategy;

[0111] The VoIP parameters are acquired based on the target parameter acquisition strategy.

[0112] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0113] The communication interface is used for communication between the above electronic device and other devices.

[0114] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0115] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0116] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned parameter acquisition methods are implemented.

[0117] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any parameter acquisition method in the above embodiments.

[0118] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0119] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0120] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0121] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A parameter acquisition method, applied to a terminal, characterized in that: The method comprises: In the case of confirming that the terminal has not acquired the VoIP parameters, determining a target parameter acquisition strategy in at least one standby parameter acquisition strategy; The VoIP parameters are acquired based on the target parameter acquisition strategy.

2. The method according to claim 1, characterized in that In a case where the at least one standby parameter acquisition strategy includes a text message acquisition strategy and a link acquisition strategy, determining the target parameter acquisition strategy in the at least one standby parameter acquisition strategy includes: Obtaining a preset policy acquisition requirement of the terminal; In the case where the preset policy acquisition requirement is security, determining the SMS acquisition policy as the target parameter acquisition policy; or When the preset strategy acquisition requirement is efficiency, the link acquisition strategy is determined as the target parameter acquisition strategy.

3. The method according to claim 2, characterized in that In the case where the SMS acquisition strategy is determined as the target parameter acquisition strategy, acquiring the VoIP parameters based on the target parameter acquisition strategy includes: Obtaining a device identification of the terminal and a user identification of a user identification card corresponding to the terminal; Based on the device identifier and the user identifier, generating first SMS content in a preset format; Sending the first SMS content to a first preset server; Receiving a second SMS content returned by the first preset server based on the first SMS content; The VoIP parameter is obtained based on the second SMS content.

4. The method according to claim 3, characterized in that The acquiring the VoIP parameter based on the second SMS content includes: Determining whether the second SMS content contains a target parameter; In a case where the target parameter is included in the second SMS content, determining the target parameter as the VoIP parameter; or, In the case that the second SMS content does not include the target parameter, a first standby link is searched in the second SMS content, and a corresponding first storage location is accessed based on the first standby link to obtain the VoIP parameter from the first storage location.

5. The method according to claim 2, characterized in that: In the case where the link acquisition strategy is determined as the target parameter acquisition strategy, acquiring the VoIP parameters based on the target parameter acquisition strategy includes: Get the preset second backup link; A corresponding second storage location is accessed based on the second standby link to obtain the VoIP parameter from the second storage location.

6. The method according to claim 1, characterized in that Before determining the target parameter acquisition strategy in at least one spare parameter acquisition strategy, the method further includes: Detecting the VoIP registration status of the terminal; In the case where the VoIP registration state is abnormal, sending a parameter acquisition request to a second preset server, wherein the parameter acquisition request is used to request to acquire VoIP parameters; When the parameter acquisition request fails to be sent, or the message returned by the second preset server is error information, it is determined that the terminal has not acquired the VoIP parameters.

7. The method according to claim 6, characterized in that The detecting the VoIP registration status of the terminal includes: Sending a status confirmation message to the VoIP registration server, so that the VoIP registration server returns corresponding registration status information based on the status confirmation message; In a case where the registration status information is the first preset information, determining that the VoIP registration status is normal; or When the registration status information is the second preset information, it is determined that the VoIP registration status is abnormal.

8. The method according to claim 6, characterized in that The method further comprises: When the VoIP parameters are obtained through the parameter acquisition request, or when the VoIP parameters are obtained based on the target parameter acquisition policy, VoIP registration is performed based on the VoIP parameters.

9. An electronic device, characterized in that: It includes one or more processors, a communication interface, a memory and a communication bus, wherein the one or more processors, the communication interface and the memory communicate with each other through the communication bus; one or more memories for storing computer programs; One or more processors are used to implement the method steps described in any one of claims 1-8 when executing the program stored in the memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1 to 8 are implemented.

Images