CN111601297B - Congestion solution, service opening method, server and terminal - Google Patents

Abstract

The invention discloses a congestion solution method, a service opening method, a server and a terminal. The congestion solution method includes: if it is determined that the service opening of the terminal fails, generating an opening failure response according to the number of terminals currently queued and the processing capacity of the operator's server , the provisioning failure response includes the queuing time; sending the provisioning failure response to the terminal, so that the terminal resends the service provisioning request according to the queuing time until the service provisioning of the terminal succeeds. Ensure that when multiple users apply for service activation at the same time, a reasonable queuing time can be allocated to each terminal, thereby reducing the processing pressure on the operator's server and reducing the risk of network congestion. At the same time, it ensures the success rate of terminal service activation and improves user experience. Spend.

Description

Congestion solution method, service provisioning method, server and terminal

technical field

The invention relates to the field of communication technology, in particular to a congestion solution method, a service activation method, a server and a terminal.

Background technique

The voice call function in the fifth generation mobile communication network (The 5th Generation Mobile Networks, 5G) can only be realized through Voice over Long-Term Evolution (VoLTE). On the mobile communication network side and Internet technology ( On the side of the Internet Technology (IT) support system, the access point (Access Point Name, APN) of the IP multimedia subsystem (Internet Protocol Multimedia Subsystem, IMS) is pre-embedded. The home subscriber server (Home Subscriber Server, HSS) supports the VoLTE automatic provisioning function, and the HSS can control the opening and closing of the automatic provisioning function through data configuration.

When the smart terminal used by the user supports the VoLTE function, after the user turns on the VoLTE switch on the smart terminal, the smart terminal will trigger a reverse contract, and the smart terminal will automatically complete the VoLTE service activation. If a large number of subscription requests for VoLTE service activation appear in a short period of time, a large number of activation requests will be formed between the application server (Application Server, AS) and the information system (Install Operate and Maintain, IOM), resulting in the presence of Severe queuing phenomenon may also cause users to fail to open VoLTE services. In the existing technology, for users who fail to open, the system will uniformly configure the user's smart terminal to initiate a re-registration request after a preset period of time (for example, 5 minutes) , but after the preset period of time, too many users in the queue will fail to activate the VoLTE service, resulting in poor user experience.

Contents of the invention

To this end, the present invention provides a congestion solution method, a service activation method, a server, and a terminal to solve the problem of network congestion in the prior art due to the large number of users who need to open a specific service and the user experience caused by the failure to open a specific service. poor degree problem.

In order to achieve the above object, the first aspect of the present invention provides a congestion solution method, including: if it is determined that the service provisioning of the terminal fails, generating a provisioning failure response according to the number of terminals currently queued and the processing capacity of the operator's server, and the provisioning failure response Including the queuing time; sending a provisioning failure response to the terminal, so that the terminal resends the service provisioning request according to the queuing time until the service provisioning of the terminal is successful.

In some specific implementations, the activation failure response is generated according to the number of terminals currently queued and the processing capability of the operator's server, including: determining the number of terminals that can be activated by the operator's server within a preset time period Queuing time: generate a provisioning failure response according to the queuing time, and the provisioning failure response includes the identification of the terminal.

In some specific implementations, the queuing time is determined according to the number of terminals currently queuing and the number of terminals that can be opened by the operator server within a preset period of time, including: calculating and obtaining the queuing time according to the following formula;

Among them, T represents the queuing time, M represents the number of terminals currently queuing, N represents the number of terminals that the operator server can open within a preset time period, N is an integer greater than or equal to 1 and less than or equal to 100, and n is greater than or equal to An integer equal to 3 and less than or equal to 100.

In some specific implementations, generating a provisioning failure response according to the queuing time includes: writing the queuing time into an attribute setting parameter in the provisioning failure response.

In some specific implementations, if it is determined that the service provisioning of the terminal has failed, before the step of generating a service provisioning failure response according to the number of terminals currently queued and the processing capacity of the operator's server, it also includes: receiving the service provisioning request sent by the terminal; judging the terminal Whether the business is opened successfully.

In order to achieve the above object, the second aspect of the present invention provides a service activation method, including: responding to the activation failure response returned by the operator server, obtaining the queuing time configured by the operator server; resending the service activation request to the operator according to the queuing time provider server until the carrier server returns a successful activation response.

In some specific implementations, in response to the activation failure response returned by the operator server, obtaining the queuing time configured by the operator server includes: if it is determined that the activation identifier in the activation failure response indicates that the queuing time is valid, then obtaining the queuing time configured by the operator server queuing time; otherwise, if it is determined that the valid flag indicates that the queuing time is invalid, then it is determined that the queuing time is equal to a preset threshold.

In some specific implementations, before the step of obtaining the queuing time configured by the operator server in response to the provisioning failure response returned by the operator server, the method further includes: sending a service provisioning request to the operator server.

In order to achieve the above object, the third aspect of the present invention provides an operator server, including: a generating module, used to generate an activation failure according to the number of terminals currently queued and the processing capacity of the operator server when it is determined that the service activation of the terminal fails. Response, the activation failure response includes queuing time; the sending module is used to send the activation failure response to the terminal, so that the terminal resends the service activation request according to the queuing time until the service of the terminal is successfully activated.

In order to achieve the above object, the fourth aspect of the present invention provides a terminal, including: an acquisition module, used to obtain the queuing time configured by the operator server in response to the activation failure response returned by the operator server; time, resend the service activation request to the operator server until the operator server returns an activation success response.

The present invention has the following advantages: when it is determined that the service provisioning of the terminal fails, according to the number of terminals currently queued and the processing capacity of the operator's server, a provisioning failure response is generated, and then the provisioning failure response including the queuing time is sent to the terminal, so that the terminal can According to the queuing time, the service activation request is resent until the operator server successfully activates the service of the terminal. Ensure that when multiple users apply for service opening at the same time and the operator's server cannot handle it, a reasonable queuing time can be allocated to each terminal, thereby reducing the processing pressure on the operator's server and reducing the risk of network congestion. At the same time, it ensures that the terminal opens the service success rate and improve user experience.

Description of drawings

The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the description, and are used together with the embodiments of the present disclosure to explain the present disclosure, and do not constitute limitations to the present disclosure. The above and other features and advantages will become more apparent to those skilled in the art by describing detailed example embodiments with reference to the accompanying drawings, in which:

FIG. 1 is a flowchart of a congestion resolution method in Embodiment 1 of the present application.

FIG. 2 is a flowchart of a congestion resolution method in Embodiment 2 of the present application.

FIG. 3 is a flow chart of a service provisioning method in Embodiment 3 of the present application.

FIG. 4 is a block diagram of an operator server in Embodiment 4 of the present application.

FIG. 5 is a block diagram of a terminal in Embodiment 5 of the present application.

FIG. 6 is a block diagram of a service processing system in Embodiment 6 of the present application.

FIG. 7 is a flow chart of the working method of the service processing system in Embodiment 6 of the present application when it is determined that congestion occurs.

In the attached picture:

401: generate module 402: send module

501: Get module 502: Resend module

610: operator server 620: terminal

611: base station 612: mobility management entity

613: Query the call session control function entity 630: The home subscriber service

640: application server

650: Safe operation and maintenance server

Detailed ways

The specific implementation manners of the present application will be described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementations described here are only used to illustrate and explain the present application, and are not intended to limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

It should be noted that, in this document, the terms "comprising", "comprising" or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or apparatus. Without further limitations, an element defined by the statement "comprising..." does not exclude the presence of additional identical elements in the process, method, article or device that includes the element.

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

Embodiment one

The embodiment of the present application provides a congestion solution method, which can be applied to an operator server. As shown in Figure 1, including:

Step 110, if it is determined that the service provisioning of the terminal fails, generate a provisioning failure response according to the number of terminals currently queued and the processing capability of the operator's server.

Wherein, the activation failure response includes queuing time. It should be noted that when the operator server receives the service activation request sent by the terminal, it will first check the number of terminals currently queued, and then judge according to its own processing capability (for example, the number of terminals that can be activated within one second). Whether the service of the terminal can be opened successfully. If the opening is not successful, a response to activation failure will be generated according to the number of terminals currently queued and the processing capacity of the operator's server. Otherwise, if the current operator's server has enough capacity to handle the current queue terminals, activate corresponding services for each terminal according to the queuing order.

Step 120, sending a activation failure response to the terminal.

It should be noted that after the terminal receives the activation failure response, the terminal will wait for 500 seconds before sending a service activation request to the operator's server until the operator's server successfully activates the terminal's service. Among them, 500 seconds is the current queuing time of the terminal. The queuing time can also be different durations such as 1 minute and 5 minutes. It can be set according to the actual situation. Other unspecified queuing times are also within the scope of protection of this application. , and will not be repeated here.

In this embodiment, when it is determined that the service provisioning of the terminal fails, according to the number of terminals currently queued and the processing capacity of the operator's server, a provisioning failure response is generated, and then the provisioning failure response including the queuing time is sent to the terminal, so that the terminal According to the queuing time, the service activation request can be resent until the operator server successfully activates the service of the terminal. Ensure that when multiple users apply for service opening at the same time and the operator's server cannot handle it, a reasonable queuing time can be allocated to each terminal, thereby reducing the processing pressure on the operator's server and reducing the risk of network congestion. At the same time, it ensures that the terminal opens the service success rate and improve user experience.

The embodiment of the present application provides another possible implementation, wherein in step 110, generating a response to activation failure based on the number of terminals currently queued and the processing capability of the operator's server can be implemented by the following steps, specifically including steps 111- 112.

Step 111: Determine the queuing time according to the number of terminals currently queuing and the number of terminals that can be activated by the operator's server within a preset time period.

Specifically, if the number of terminals currently queued is greater than the number of terminals that can be activated by the operator's server within a preset time period, subsequent new terminals need to be queued to wait for processing by the operator's server. The queuing time can be calculated according to the following formula.

Among them, T represents the queuing time, M represents the number of terminals currently queuing, N represents the number of terminals that the operator server can open within a preset time period, N is an integer greater than or equal to 1 and less than or equal to 100, and n is greater than or equal to An integer equal to 3 and less than or equal to 100. The unit of T _iretry can be seconds, minutes or other time units. Other time units that are not illustrated are also within the protection scope of the present application, and can be set according to actual conditions, and will not be described again.

For example, when M is equal to 10, N is equal to 5, and i is equal to 6, then T _iretry = 3, which means that the sixth terminal needs to resend the service activation request to the operator server after 2 seconds, so there are already 5 Terminals are waiting for processing by the operator's server, therefore, the sixth terminal needs to wait for 2 seconds.

If the number of terminals currently queued is less than or equal to the number of terminals that can be opened by the operator's server within the preset time period, it means that the operator's server can still handle it, and there is no need to generate queuing time. The operator's server The service provisioning request is processed.

Step 112, generating a provisioning failure response according to the queuing time.

Wherein, the activation failure response includes the identifier of the terminal.

In some specific implementations, the queuing time is written into the attribute setting parameter in the provisioning failure response.

For example, the activation failure response may include a subsequent retransmission (Retry-After) header field, and the Retry-After header field includes an ICSCF parameter (ICSCFPARA1), and the ICSCFPARA1 includes 32 bits (Binary Digit, BIT), wherein the 16th to 31st BIT Defined as "attribute value setting" type parameters, the queuing time can be written into the 16th to 31st BIT of ICSCFPARA1, so that when the terminal receives the activation failure response, it can obtain the queuing time by analyzing the activation failure response message. Time, reduce the number of times the terminal repeatedly sends service activation requests, thereby reducing the processing pressure on the operator's server, reducing the risk of network congestion, and at the same time, ensuring the success rate of terminal service activation and improving user experience.

Embodiment two

FIG. 2 shows a congestion solution method provided by the embodiment of the present application. The difference between this embodiment and Embodiment 1 is that before generating a provisioning failure response, it is necessary to determine whether the service of the terminal is successfully provisioned.

Specifically, the method can be applied to an operator server. As shown in Figure 2, the following steps may be included.

Step 210, receiving a service activation request sent by the terminal.

For example, the smart terminal used by the user may include a module supporting the VoLTE function during initial setup. When the user needs to use and activate the VoLTE service, he only needs to turn on the switch of the VoLTE function module on the terminal. On the network side, an access point (Access Point Name, APN) of an IP multimedia subsystem (Internet Protocol Multimedia Subsystem, IMS) needs to be embedded in advance. In order to ensure that when the user turns on the switch of the VoLTE function module on the smart terminal, the service activation request can be automatically sent to the operator's server.

Step 220, judging whether the service of the terminal is opened successfully.

It should be noted that when the operator server receives the service activation request sent by each terminal, it will first check the number of terminals currently queued, and then according to its own processing capabilities (for example, the number of terminals that can be activated within one second), It is judged whether the service of the terminal can be activated successfully, if the activation cannot be successful, then enter step 230, otherwise, activate the corresponding service for each terminal in sequence.

Step 230, if it is determined that the service provisioning of the terminal fails, generate a provisioning failure response according to the number of terminals currently queued and the processing capability of the operator's server.

Step 240, sending a activation failure response to the terminal.

It should be noted that the steps 230-240 in this embodiment are the same as the steps 110-120 in the first embodiment, and will not be repeated here.

In this embodiment, by receiving the service opening request sent by the terminal and judging whether the service of the terminal is successfully opened, it is possible to predict whether network congestion occurs in advance; number and the processing capacity of the operator’s server, generate a failed activation response, and send a failed activation response including the queuing time to the terminal, so that the terminal can resend the service activation request according to the queuing time until the operator’s server successfully activates the terminal’s business until. Ensure that when multiple users apply for service opening at the same time and the operator's server cannot handle it, a reasonable queuing time can be allocated to each terminal, thereby reducing the processing pressure on the operator's server and reducing the risk of network congestion. At the same time, it ensures that the terminal opens the service success rate and improve user experience.

Embodiment Three

The embodiment of the present application provides a method for activating a service, and the method can be applied to a terminal. As shown in FIG. 3 , it specifically includes the following steps.

Step 310, in response to the activation failure response returned by the operator's server, acquire the queuing time configured by the operator's server.

In some specific implementations, if it is determined that the activation flag in the activation failure response indicates that the queuing time is valid, the queuing time configured by the operator server is obtained; otherwise, if it is determined that the queuing time is invalid, then the queuing time is determined to be equal to the preset threshold.

Specifically, when the activation flag in the activation failure response indicates that the queuing time is valid, the terminal can analyze the activation failure response to obtain the queuing time configured by the operator's server. The queuing time can range from 0 to 65535, and the unit Seconds; when the effective flag indicates that the queuing time is invalid, use the default value (for example, 300 seconds) as the queuing time, which means that the terminal needs to wait for 300 seconds, and then resend the service activation request to the operator server again after 300 seconds .

In some specific implementations, before step 310, the method further includes: sending a service provisioning request to an operator server.

It should be noted that, when the terminal confirms that a certain service needs to be activated, it will automatically send a service activation request to the operator's server, so that the operator's server can automatically activate the corresponding service for the terminal. However, the processing capacity of the operator's server is limited. If multiple terminals apply for service activation at the same time, and the number of terminals requesting service activation exceeds the processing capacity of the operator's server, network congestion will occur, which will easily cause service activation failure and Bring bad customer experience. Therefore, it is necessary to adjust the queuing time of the terminal on the operator's server, and then perform step 320 to improve customer experience.

Step 320, according to the queuing time, resend the service provisioning request to the operator server until the operator server returns a successful provisioning response.

Specifically, after the terminal has waited for the queuing time (for example, 400 seconds), it will send the service activation request to the operator server again until the operator server successfully activates the service of the terminal.

In this embodiment, the queuing time configured by the operator server is obtained from the activation failure response fed back by the operator server, and the service activation request is sent to the operator server again according to the queuing time, so that the service activation request can be adjusted and sent Reduce the frequency of service provisioning requests, reduce the processing pressure on the operator's server, and avoid network congestion; at the same time, the success rate of service provisioning is guaranteed and user experience is improved.

Embodiment Four

FIG. 4 is a schematic structural diagram of an operator server provided in an embodiment of the present application. For the specific implementation of the server, refer to the relevant descriptions in Embodiment 1 or Embodiment 2, and repeated descriptions will not be repeated. It should be noted that the specific implementation of the server in this embodiment is not limited to the above embodiments, and other undescribed embodiments are also within the scope of protection of this server.

As shown in FIG. 4 , the operator server specifically includes: a generating module 401 for generating a failure response according to the number of terminals currently queued and the processing capability of the operator server when determining that the service activation of the terminal fails, and the activation failure response includes Queuing time; the sending module 402 is used to send a provisioning failure response to the terminal, so that the terminal resends the service provisioning request according to the queuing time until the service of the terminal is successfully provisioned.

It is not difficult to find that this embodiment is a device embodiment corresponding to Embodiment 1 or Embodiment 2, and this embodiment can be implemented in cooperation with Embodiment 1 or Embodiment 2. The relevant technical details mentioned in Embodiment 1 or Embodiment 2 are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this implementation manner may also be applied in the first or second embodiment.

Embodiment five

FIG. 5 is a schematic structural diagram of a terminal provided by the embodiment of the present application. For the specific implementation of the terminal, refer to the relevant description of Embodiment 3, and the repeated parts will not be repeated. It is worth noting that the specific implementation of the terminal in this embodiment is not limited to the above embodiments, and other undescribed embodiments are also within the scope of protection of the terminal.

As shown in Figure 5, the terminal specifically includes: an acquisition module 501 for obtaining the queuing time configured by the operator's server in response to the activation failure response returned by the operator's server; a retransmission module 502 for resending the service activation Request to the operator server until the operator server returns a successful activation response.

It is not difficult to find that this embodiment is a device embodiment corresponding to the third embodiment, and this embodiment can be implemented in cooperation with the third embodiment. The relevant technical details mentioned in the third embodiment are still valid in this embodiment, and will not be repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment mode can also be applied in the third embodiment.

It is worth mentioning that all the modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, or a part of a physical unit, or multiple physical units. Combination of units. In addition, in order to highlight the innovative part of the present application, units that are not closely related to solving the technical problems proposed in the present application are not introduced in this embodiment, but this does not mean that there are no other units in this embodiment.

Embodiment six

The embodiment of the present application provides a service processing system, as shown in FIG. 6 , including: an operator server 610, a terminal 620, a home subscriber server (Home Subscriber Server, HSS) 630, an application server (Application Server, AS) 640 and a security operation and maintenance server (Install Operate and Maintain Server, IOM) 650 . Wherein, the operator server 610 includes a base station 611 , a mobility management entity (Mobility Management Entity, MME) 612 and an interrogating call session control function entity (Interrogating CallSession Control Function, I-CSCF) 613 .

Specifically, FIG. 7 is a flow chart of the working method of the service processing system when it is determined that congestion occurs. As shown in FIG. 7 , it specifically includes the following steps.

Step 701 , the terminal 620 sends an IMS registration request to the operator server 610 .

Specifically, inside the operator server 610, the service activation request is first received by the base station 611 from the terminal 620, and then the base station 611 forwards the service activation request to the MME 612, and then the MME 612 forwards the service activation request to the I-CSCF 613 , and then the I-CSCF 613 forwards it to the HSS 630.

It should be noted that, before step 701, on the mobile communication network side and the Internet Technology (Internet Technology, IT) support system side, it is necessary to pre-embed the Access Point Name (Access Point Name) of the IP Multimedia Subsystem (Internet Protocol Multimedia Subsystem, IMS) in advance. , APN). Specifically, pre-embedding is completed through information interaction among AS 640 , HSS 630 and IOM 650 .

In step 702, the operator server 610 judges whether the service can be successfully activated for the terminal 620 according to the number of terminals currently queued and its processing capability.

It should be noted that, if it is determined that the terminal 620 fails to activate the service, then enter step 703, otherwise, end the process.

In step 703, the operator server 610 generates an activation failure response according to the number of terminals currently queued and the processing capability of the operator server 610.

It should be noted that after the operator server receives the IMS registration request, since there are many terminal users who need to activate services, if the number of terminals currently queued is greater than the processing capacity of the operator server 610, it means that the operator server 610 cannot timely To process the IMS registration request of the terminal 620, the operator server 610 will calculate the queuing time according to the following formula; then write the queuing time into the generated registration failure response "404 Not Found".

Among them, T represents the queuing time, M represents the number of terminals currently queuing, N represents the number of terminals that the operator server can open within a preset time period (for example, 1 second), i represents the i-th terminal, and N is greater than or equal to n is an integer greater than or equal to 3 and less than or equal to 100.

Step 704 , the operator server 610 sends a activation failure response carrying the queuing time to the terminal 620 .

In a specific implementation, the queuing time may be calculated by the I-CSCF 613 according to the formula in step 703, and then the I-CSCF 613 writes the queuing time into the registration failure response, and sends the registration failure response to The MME 612 makes the MME 612 forward the registration failure response to the base station 611, and then the base station 611 sends the registration failure response to the terminal 620.

Specifically, the registration failure response includes a subsequent retransmission (Retry-After) header field, and the Retry-After header field includes an ICSCF parameter (ICSCFPARA1), and the 16th to 31st bits of the ICSCFPARA1 are defined as "attribute value setting" type parameters , the queuing time can be written into the 16th to 31st BIT of ICSCFPARA1.

Among them, the "attribute value setting" type parameter is used to control the waiting time (ie, queuing time) of the terminal user in the scenario of automatic account opening of VoLTE by the I-CSCF. The waiting time takes effect only when the 6th BIT of ICSCFPARA1 is set to "1", and its value range is 0 to 65535 in seconds; when the 6th BIT of ICSCFPARA1 is set to "0", the default value ( For example, 300 seconds) as the queuing time means that the terminal 620 needs to wait for 300 seconds, and can re-initiate the IMS registration request after 300 seconds.

It should be noted that after the terminal 620 waits for the queuing time (for example, 500 seconds), it will send the IMS registration request to the operator server 610 again, that is, enter step 701 . This loops until the operator server 610 successfully activates the IMS registration service of the terminal 620 .

In this embodiment, when it is determined that the service provisioning of the terminal fails, according to the number of terminals currently queued and the processing capacity of the operator's server, a provisioning failure response is generated, and then the provisioning failure response including the queuing time is sent to the terminal, so that the terminal According to the queuing time, the service activation request can be resent until the operator server successfully activates the service of the terminal. Ensure that when multiple users apply for service activation at the same time, a reasonable queuing time can be allocated to each terminal to reduce the number of times the terminal repeatedly sends service activation requests, thereby reducing the processing pressure on the operator's server and reducing the risk of network congestion. At the same time, Ensure the success rate of terminal service activation and improve user experience.

It can be understood that, the above embodiments are only exemplary embodiments adopted for illustrating the principle of the present invention, but the present invention is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also regarded as the protection scope of the present invention.

Claims (8)

1. A method of congestion resolution, the method comprising:

if the service opening failure of the terminal is determined, generating an opening failure response according to the number of the currently queued terminals and the processing capacity of the operator server, including:

determining queuing time according to the number of currently queued terminals and the number of terminals which can be opened by the operator server in a preset duration;

generating an opening failure response according to the queuing time, wherein the opening failure response comprises an identifier of the terminal, queuing time and an effective identifier, and the effective identifier represents whether the queuing time is effective or not;

if the effective mark represents that the queuing time is effective, the queuing time is determined according to the number of the terminals which can be opened by the operator server in a preset duration; if the effective mark indicates that the queuing time is invalid, the queuing time is a preset threshold value;

and sending the opening failure response to the terminal so that the terminal resends the service opening request according to the queuing time until the service opening of the terminal is successful.

2. The method of claim 1, wherein determining the queuing time based on the number of currently queued terminals and the number of terminals that the operator server can open within a preset time period comprises:

calculating to obtain the queuing time according to the following formula;

wherein T represents the queuing time, M represents the number of currently queued terminals, N represents the number of terminals that can be opened by the operator server within a preset duration, N is an integer greater than or equal to 1 and less than or equal to 100, and N is an integer greater than or equal to 3 and less than or equal to 100.

3. The method of claim 1, wherein the generating the open failure response as a function of the queuing time comprises:

and writing the queuing time into an attribute setting parameter in the opening failure response.

4. A method according to any one of claims 1 to 3, wherein before the step of generating an activation failure response in accordance with the number of currently queued terminals and the processing power of the operator server if it is determined that the activation of the service by the terminal fails, further comprising:

receiving a service opening request sent by the terminal;

judging whether the service of the terminal is successfully opened.

5. A service opening method, characterized in that the method comprises:

responding to an opening failure response returned by an operator server, acquiring queuing time configured by the operator server, and comprising the following steps:

if the effective mark in the opening failure response is determined to be effective for characterizing the queuing time, acquiring the queuing time configured by the operator server;

otherwise, if the effective identification is determined to be the mark indicating that the queuing time is invalid, determining that the queuing time is equal to a preset threshold;

and resending a service opening request to the operator server according to the queuing time until the operator server returns an opening success response.

6. The method of claim 5, further comprising, prior to the step of obtaining the operator server configured queuing time in response to an activation failure response returned by an operator server:

and sending the service opening request to an operator server.

7. An operator server, comprising:

the system comprises a generation module, a service management module and a service management module, wherein the generation module is used for generating an opening failure response according to the number of currently queued terminals and the processing capacity of an operator server when determining that the service of the terminal fails to be opened, the opening failure response comprises an identifier of the terminal, queuing time and an effective identifier, and the effective identifier represents whether the queuing time is effective or not;

the calculation module is used for determining queuing time according to the number of the currently queued terminals and the number of the terminals which can be opened by the operator server in a preset duration;

the first determining module is used for determining queuing time according to the number of the terminals which can be opened by the operator server in a preset duration if the validation identifier characterizes the queuing time to be validated; if the effective mark indicates that the queuing time is invalid, the queuing time is a preset threshold value;

and the sending module is used for sending the opening failure response to the terminal so that the terminal resends the service opening request according to the queuing time until the service of the terminal is successfully opened.

8. A terminal, comprising:

the acquisition module is used for responding to an opening failure response returned by the operator server and acquiring queuing time configured by the operator server;

the second determining module is used for acquiring the queuing time configured by the operator server if the validation identifier in the opening failure response is determined to be effective in the queuing time; otherwise, if the effective identification is determined to be the mark indicating that the queuing time is invalid, determining that the queuing time is equal to a preset threshold;

and the resending module is used for resending the service opening request to the operator server according to the queuing time until the operator server returns an opening success response.

Images