WO2014108019A1 - Method and apparatus for releasing services in stages - Google Patents

Method and apparatus for releasing services in stages Download PDF

Info

Publication number
WO2014108019A1
WO2014108019A1 PCT/CN2013/089728 CN2013089728W WO2014108019A1 WO 2014108019 A1 WO2014108019 A1 WO 2014108019A1 CN 2013089728 W CN2013089728 W CN 2013089728W WO 2014108019 A1 WO2014108019 A1 WO 2014108019A1
Authority
WO
WIPO (PCT)
Prior art keywords
new service
releasing
access
access rate
accounts
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2013/089728
Other languages
French (fr)
Inventor
Ming Tian
Lihua Huang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Publication of WO2014108019A1 publication Critical patent/WO2014108019A1/en
Priority to US14/734,653 priority Critical patent/US10367897B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • the present invention relates to internet technologies, and more particularly to a method and apparatus for releasing services on a server in stages.
  • the new service is released in stages one server a time.
  • each server may handle large number of user accesses, there is still substantial risk in releasing the new service.
  • the risk is not well controlled; if the number of user units is large, it is not very efficient as it may take a substantial amount of time to release the new service to all users.
  • the present invention provides a method and apparatus for releasing services on a server in stages, wherein new service can be released in different ways to suit different situations to reduce the risk and improve efficiency.
  • a method for releasing services on a server in stages comprising: setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and releasing the new service to the entire server in a third time period.
  • an apparatus for releasing services on a server in stages comprising: a first releasing module for setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; a second releasing module for setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and a third releasing module for releasing the new service to the entire server in a third time period.
  • a method for releasing services on a server in stages comprising: setting an access rate for a new service and releasing the new service in accordance with the access rate; receiving a feedback from a user using the new service; and increasing the access rate for the new service if the feedback is positive.
  • an apparatus for releasing services on a server in stages comprising: an access rate setting module for setting an access rate for a new service and releasing the new service in accordance with the access rate; a receiving module for receiving a feedback from a user using the new service; and a first releasing module for increasing the access rate for the new service if the feedback is positive.
  • new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • Figure 1 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with an embodiment of the present invention.
  • Figure 2 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with another embodiment of the present invention.
  • Figure 3 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
  • Figure 4 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with an embodiment of the present invention.
  • Figure 5 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with another embodiment of the present invention.
  • Figure 6 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
  • Figure 1 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with an embodiment of the present invention.
  • the method includes the following steps.
  • Step 101 setting an access rate for a new service and releasing the new service in accordance with the access rate.
  • Step 102 receiving a feedback from a user using the new service.
  • Step 103 increasing the access rate for the new service if the feedback is positive.
  • Step 101 the server releases the new service while controlling the access rate to the new service.
  • an access rate for the new service is set, which limits the number of accesses to the new service in a time period, and the new service is released in accordance with the access rate.
  • Step 102 is next.
  • Step 102 feedbacks for the new service are received from the users.
  • the feedbacks can be received directly from the client terminals, or from the client terminals via the server.
  • Step 103 is next.
  • Step 103 if the received feedbacks for the new service are positive, then the access rate for the new service is increased to release the new service in stages.
  • the initial access rate for a server might be set as 1 access per minute, and the access rate can be gradually increased if there is no issue with the new service.
  • the new service can be tested in different situations, which helps to expose any risk in the new service. Furthermore, the scope of the risk in releasing the new service can be easily controlled.
  • the method of releasing new service by controlling the access rate for the new service can be implemented with the following pseudo code:
  • ⁇ dwTimeTmp time(NULL); if (dwTimeTmp > gsziWlimitLastTime[giSvrId]+60) #the number of accesses per minutes is set#
  • pstSvr &(pstSvrCfgList->astSvrCfgList[giSvrId]);
  • pstSvr &(pstSvrCfgList->astSvrCfgList[giSvrId]);
  • an initial access rate and a maximum access rate for the new service are set in Step 101.
  • the access rate for the new service is increased from the initial access rate gradually to the maximum access rate to release the new service in stages.
  • the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service.
  • the access rate for a new service is controlled in releasing the new service, and the number of accesses to the new service during a particular time period can be set to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • Figure 2 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with another embodiment of the present invention. As shown in Figure 2, the method includes the following steps.
  • Step 201 setting a number of accounts that can access the new service and releasing the new service to the accounts.
  • Step 202 receiving a feedback from a user using the new service.
  • Step 203 increasing the number of accounts that can access the new service if the feedback is positive.
  • Step 204 setting an access rate for the new service and releasing the new service in accordance with the access rate.
  • Step 205 receiving a feedback from a user using the new service.
  • Step 206 increasing the access rate for the new service if the feedback is positive.
  • Step 201 the server releases the new service while controlling the accounts that can access the new service.
  • the accounts that can access the new service are set, and the new service is released only to these accounts.
  • Step 202 is next.
  • Step 202 feedbacks for the new service are received from the users.
  • the feedbacks can be received directly from the client terminals, or from the client terminals via the server.
  • Step 203 is next.
  • Step 203 if the received feedbacks for the new service are positive, then the accounts that can access the new service are increased to release the new service in stages. For example, a certain number of users can be directed to a new server to receive the new service, while the remaining users will be directed to an old server that does not contain the new service, and the number of accounts directed to the new server can be gradually increased if there is no issue with the new service.
  • the new service can be tested in the initial stage using a limited number of accounts, which limits the risk of the new service to a limited number of accounts, and facilitates the identification of any issues with the new service.
  • the method of releasing new service by controlling the accounts accessing the new service can be implemented with the following pseudo code:
  • pstSvr &(pstSvrCfgList->astSvrCfgList[dwTestSvr]);
  • wTestUin is a preset user account.
  • the user account dwUsr is dwTestUin
  • Step 203 the number of accounts that can access the new service is increased from the initial number gradually to the maximum number to release the new service in stages.
  • Step 204 is next.
  • step 204 the access rate for the new service is set so that the number of accounts accessing the new service is largely the same as the maximum number of accounts in Step 203, which ensures a smooth transition from Step 203 to Step 204.
  • Step 204 in this embodiment is the same or similar to Step 101 in the embodiment above, the description of Step 101 in the embodiment above can be referenced for the implementation of Step 204.
  • Step 205 in this embodiment is the same or similar to Step 102 in the embodiment above, the description of Step 102 in the embodiment above can be referenced for the implementation of Step 205.
  • Step 206 in this embodiment is the same or similar to Step 103 in the embodiment above, the description of Step 103 in the embodiment above can be referenced for the implementation of Step 206.
  • the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service.
  • the accounts having access to a new service and the access rate for the new service are both controlled in releasing the new service, and new service can be released accordingly to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • Figure 3 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with yet another embodiment of the present invention. As shown in Figure 3, the method includes the following steps.
  • Step 301 setting a number of accounts that can access the new service and releasing the new service to the accounts.
  • Step 302 receiving a feedback from a user using the new service.
  • Step 303 increasing the number of accounts that can access the new service if the feedback is positive.
  • Step 304 setting an access rate for the new service and releasing the new service in accordance with the access rate.
  • Step 305 receiving a feedback from a user using the new service.
  • Step 306 increasing the access rate for the new service if the feedback is positive.
  • Step 307 releasing the new service to the entire server.
  • Step 301 in this embodiment is the same or similar to Step 201 in the embodiment above, the description of Step 201 in the embodiment above can be referenced for the implementation of Step 301.
  • Step 301 in this embodiment is the same or similar to Step 201 in the embodiment above, the description of Step 201 in the embodiment above can be referenced for the implementation of Step 301.
  • Step 302 in this embodiment is the same or similar to Step 202 in the embodiment above, the description of Step 202 in the embodiment above can be referenced for the implementation of Step 302.
  • Step 303 in this embodiment is the same or similar to Step 203 in the embodiment above, the description of Step 203 in the embodiment above can be referenced for the implementation of Step 303.
  • Step 304 in this embodiment is the same or similar to Step 204 in the embodiment above, the description of Step 204 in the embodiment above can be referenced for the implementation of Step 304.
  • Step 305 in this embodiment is the same or similar to Step 205 in the embodiment above, the description of Step 205 in the embodiment above can be referenced for the implementation of Step 305.
  • Step 306 in this embodiment is the same or similar to Step 206 in the embodiment above, the description of Step 206 in the embodiment above can be referenced for the implementation of Step 306.
  • step 307 if the new service is operating normally under the maximum access rate, it can be determined the new service is stable on the server, and new service can be released to the entire server.
  • the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service. , , ⁇ , , . i nus, an tne steps m the method lor releasing services on a server m stages m this embodiment are completed.
  • new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • FIG 4 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with an embodiment of the present invention.
  • the apparatus includes an access rate setting module 41, a receiving module 42, and a first releasing module 43.
  • the access rate setting module 41 is used for setting an access rate for a new service and releasing the new service in accordance with the access rate.
  • the receiving module 42 is used for receiving a feedback from a user using the new service.
  • the first releasing module 43 is used for increasing the access rate for the new service if the feedback is positive.
  • the access rate setting module 41 sets an access rate for the new service, which limits the number of accesses to the new service in a time period, and releases the new service in accordance with the access rate.
  • the receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then the first releasing module 43 increases the access rate for the new service to release the new service in stages.
  • the access rate setting module 41 sets an initial access rate and a maximum access rate for the new service
  • first releasing module 43 increase the access rate for the new service from the initial access rate gradually to the maximum access rate to release the new service in stages.
  • apparatus for releasing services on a server in stages in this embodiment can further include an error processing module (not shown in Figure 4) for stopping the release of the new service if the feedbacks indicate that there is error with the new service.
  • the access rate for a new service is controlled in releasing the new service, and the number of accesses to the new service during a particular time period can be set to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • Figure 5 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with another embodiment of the present invention. As shown in
  • the apparatus further includes an access account setting module 51, and a second releasing module 52.
  • the access account setting module 51 is used for setting a number of accounts that can access the new service and releasing the new service to the accounts.
  • the second releasing module 52 is used for increasing the number of accounts that can access the new service if the feedback is positive.
  • the access account setting module 51 set the account that can access the new service, and the new service is released only to these accounts.
  • the receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then second releasing module 52 increases the accounts that can access the new service to release the new service in stages.
  • the access rate setting module 41 sets an access rate for the new service, which limits the number of accesses to the new service in a time period, and releases the new service in accordance with the access rate.
  • the receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then the first releasing module 43 increases the access rate for the new service to release the new service in stages.
  • the access account setting module 51 sets an initial number and a maximum number of accounts that can access the new service, and first releasing module 43 increase the number of accounts that can access the new service from the initial number gradually to the maximum number to release the new service in stages.
  • the accounts that can access the new service and the access rate for the new service are both controlled in releasing the new service, and new service can be released accordingly to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
  • Figure 6 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
  • the apparatus further includes a third releasing module 61.
  • the third release module 61 is used for releasing the new service to the entire server.
  • the third releasing module 61 releases the new service to the entire server.
  • the operation of the apparatus for releasing services on a server in stages in this embodiment is the same or similar to the method embodiment in Figure 3, and the description of the method embodiment in Figure 3 can be referenced for the operation of the apparatus in this embodiment.
  • new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer And Data Communications (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A method and apparatus for releasing services on a server in stages is provided, the method comprising setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and releasing the new service to the entire server in a third time period. In accordance with the method and apparatus for releasing services on a server in stages in this embodiment, new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.

Description

METHOD AND APPARATUS FOR RELEASING SERVICES IN STAGES
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims the benefit and priority of Chinese Patent Application No. 201310007772.3, entitled "Method and Apparatus for Releasing Services in Stages" filed on January 9, 2013. The entire disclosures of each of the above applications are incorporated herein by reference.
TECHNICAL FIELD
The present invention relates to internet technologies, and more particularly to a method and apparatus for releasing services on a server in stages.
BACKGROUND
There are a wide variety of services available on the internet, such as the services on the QQ platform provided by Tencent Technology. Whenever a new version of service is released, a large number of users will be affected. Thus, the network service providers typically release new service in stages (also called gradual conversion), wherein the new service is first released to a small number of users, while the remaining users continue to use the old service; if it is proven that there is no issue for the new service as used by the small number of users, the remaining users will be gradually migrated to the new service.
There are two methods of releasing new service in stages.
In the first method, the new service is released in stages one server a time.
In the second method, all the users are divided into a number of units, and the new service is released in stages one user unit a time.
In the first method, as each server may handle large number of user accesses, there is still substantial risk in releasing the new service.
In the second method, if the number of user units is small, the risk is not well controlled; if the number of user units is large, it is not very efficient as it may take a substantial amount of time to release the new service to all users.
Thus, there is a need to provide a method and apparatus for releasing services on a server in stages of low risk and high efficiency to address the issues in the prior art.
SUMMARY OF THE INVENTION
The present invention provides a method and apparatus for releasing services on a server in stages, wherein new service can be released in different ways to suit different situations to reduce the risk and improve efficiency.
In accordance with embodiments of the present invention, a method for releasing services on a server in stages is provided, the method comprising: setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and releasing the new service to the entire server in a third time period.
In accordance with embodiments of the present invention, an apparatus for releasing services on a server in stages is provided, the apparatus comprising: a first releasing module for setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period; a second releasing module for setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and a third releasing module for releasing the new service to the entire server in a third time period.
In accordance with embodiments of the present invention, a method for releasing services on a server in stages is provided, the method comprising: setting an access rate for a new service and releasing the new service in accordance with the access rate; receiving a feedback from a user using the new service; and increasing the access rate for the new service if the feedback is positive.
In accordance with embodiments of the present invention, an apparatus for releasing services on a server in stages is provided, the apparatus comprising: an access rate setting module for setting an access rate for a new service and releasing the new service in accordance with the access rate; a receiving module for receiving a feedback from a user using the new service; and a first releasing module for increasing the access rate for the new service if the feedback is positive.
In accordance with the method and apparatus for releasing services on a server in stages in this embodiment, new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
BRIEF DESCRIPTION OF THE DRAWINGS
To better illustrate the technical features of the embodiments of the present invention, various embodiments of the present invention will be briefly described in conjunction with the accompanying drawings.
Figure 1 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with an embodiment of the present invention.
Figure 2 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with another embodiment of the present invention.
Figure 3 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
Figure 4 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with an embodiment of the present invention.
Figure 5 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with another embodiment of the present invention.
Figure 6 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
To better illustrate the purpose, technical feature, and advantages of the embodiments of the present invention, various embodiments of the present invention will be further described in conjunction with the accompanying drawings.
Figure 1 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with an embodiment of the present invention.
As shown in Figure 1, the method includes the following steps.
Step 101 : setting an access rate for a new service and releasing the new service in accordance with the access rate.
Step 102: receiving a feedback from a user using the new service.
Step 103: increasing the access rate for the new service if the feedback is positive.
The method for releasing services on a server in stages in this embodiment concludes at Step
103.
The implementation of each step in the method will be described in more details below.
In Step 101, the server releases the new service while controlling the access rate to the new service. First, an access rate for the new service is set, which limits the number of accesses to the new service in a time period, and the new service is released in accordance with the access rate.
Step 102 is next.
In Step 102, feedbacks for the new service are received from the users. The feedbacks can be received directly from the client terminals, or from the client terminals via the server.
Step 103 is next.
In Step 103, if the received feedbacks for the new service are positive, then the access rate for the new service is increased to release the new service in stages. For example, the initial access rate for a server might be set as 1 access per minute, and the access rate can be gradually increased if there is no issue with the new service.
Thus, the new service can be tested in different situations, which helps to expose any risk in the new service. Furthermore, the scope of the risk in releasing the new service can be easily controlled.
The method of releasing new service by controlling the access rate for the new service can be implemented with the following pseudo code:
if (gsziWLimit[giSvrId] > 0)
# determining whether an access rate is set; if 0, access rate is not limited#
{ if (gsziWlimitCount[giSvrId] >= gsziWLimit[giSvrId])
{ dwTimeTmp = time(NULL); if (dwTimeTmp > gsziWlimitLastTime[giSvrId]+60) #the number of accesses per minutes is set#
{gsziWlimitLastTime[giSvrId] = dwTimeTmp;
gsziWlimitCount[giSvrId] = 1 ;
pstSvr = &(pstSvrCfgList->astSvrCfgList[giSvrId]);
}
else
{ return 0; #if the number of accesses requests exceeds the set number, redirect the extra access requests to an old service#
}
}
else
{ gsziWlimitCount[giSvrId]++;
pstSvr = &(pstSvrCfgList->astSvrCfgList[giSvrId]);
# if the number of accesses requests does not exceed the set number, direct the access requests to the new service #
}
}
Preferably, an initial access rate and a maximum access rate for the new service are set in Step 101. In Step 103, the access rate for the new service is increased from the initial access rate gradually to the maximum access rate to release the new service in stages.
Also, in releasing the new service, if the feedbacks indicate that there is error with the new service, the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service.
Thus, all the steps in the method for releasing services on a server in stages in this embodiment are completed.
In accordance with the method for releasing services on a server in stages in this embodiment, the access rate for a new service is controlled in releasing the new service, and the number of accesses to the new service during a particular time period can be set to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Figure 2 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with another embodiment of the present invention. As shown in Figure 2, the method includes the following steps.
Step 201 : setting a number of accounts that can access the new service and releasing the new service to the accounts.
Step 202: receiving a feedback from a user using the new service.
Step 203: increasing the number of accounts that can access the new service if the feedback is positive.
Step 204: setting an access rate for the new service and releasing the new service in accordance with the access rate.
Step 205: receiving a feedback from a user using the new service.
Step 206: increasing the access rate for the new service if the feedback is positive.
The method for releasing services on a server in stages in this embodiment concludes at Step
206.
The implementation of each step in the method will be described in more details below.
In Step 201, the server releases the new service while controlling the accounts that can access the new service. First, the accounts that can access the new service are set, and the new service is released only to these accounts.
Step 202 is next.
In Step 202, feedbacks for the new service are received from the users. The feedbacks can be received directly from the client terminals, or from the client terminals via the server.
Step 203 is next.
In Step 203, if the received feedbacks for the new service are positive, then the accounts that can access the new service are increased to release the new service in stages. For example, a certain number of users can be directed to a new server to receive the new service, while the remaining users will be directed to an old server that does not contain the new service, and the number of accounts directed to the new server can be gradually increased if there is no issue with the new service.
Thus, the new service can be tested in the initial stage using a limited number of accounts, which limits the risk of the new service to a limited number of accounts, and facilitates the identification of any issues with the new service.
The method of releasing new service by controlling the accounts accessing the new service can be implemented with the following pseudo code:
if((dwTestUin>0)&&(dwUsr==dwTestUin)
&&(dwTestSvr>0)&&(dwTestSvr<MAX_SERVER_NUM))
{
pstSvr = &(pstSvrCfgList->astSvrCfgList[dwTestSvr]);
}
wherein wTestUin is a preset user account. When a user requests access to a server, and the user account dwUsr is dwTestUin, that user will be directed to a new server for the new service. Preferably, an initial number and a maximum number of accounts that can access the new service are set in Step 201. In Step 203, the number of accounts that can access the new service is increased from the initial number gradually to the maximum number to release the new service in stages.
Step 204 is next.
In step 204, the access rate for the new service is set so that the number of accounts accessing the new service is largely the same as the maximum number of accounts in Step 203, which ensures a smooth transition from Step 203 to Step 204.
Step 204 in this embodiment is the same or similar to Step 101 in the embodiment above, the description of Step 101 in the embodiment above can be referenced for the implementation of Step 204.
Step 205 in this embodiment is the same or similar to Step 102 in the embodiment above, the description of Step 102 in the embodiment above can be referenced for the implementation of Step 205.
Step 206 in this embodiment is the same or similar to Step 103 in the embodiment above, the description of Step 103 in the embodiment above can be referenced for the implementation of Step 206.
Also, in releasing the new service, if the feedbacks indicate that there is error with the new service, the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service.
Thus, all the steps in the method for releasing services on a server in stages in this embodiment are completed.
In accordance with the method for releasing services on a server in stages in this embodiment, the accounts having access to a new service and the access rate for the new service are both controlled in releasing the new service, and new service can be released accordingly to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Figure 3 is an exemplary flowchart for a method for releasing services on a server in stages in accordance with yet another embodiment of the present invention. As shown in Figure 3, the method includes the following steps.
Step 301 : setting a number of accounts that can access the new service and releasing the new service to the accounts.
Step 302: receiving a feedback from a user using the new service.
Step 303: increasing the number of accounts that can access the new service if the feedback is positive. Step 304: setting an access rate for the new service and releasing the new service in accordance with the access rate.
Step 305: receiving a feedback from a user using the new service.
Step 306: increasing the access rate for the new service if the feedback is positive.
Step 307: releasing the new service to the entire server.
The method for releasing services on a server in stages in this embodiment concludes at Step
307.
Step 301 in this embodiment is the same or similar to Step 201 in the embodiment above, the description of Step 201 in the embodiment above can be referenced for the implementation of Step 301.
Step 301 in this embodiment is the same or similar to Step 201 in the embodiment above, the description of Step 201 in the embodiment above can be referenced for the implementation of Step 301.
Step 302 in this embodiment is the same or similar to Step 202 in the embodiment above, the description of Step 202 in the embodiment above can be referenced for the implementation of Step 302.
Step 303 in this embodiment is the same or similar to Step 203 in the embodiment above, the description of Step 203 in the embodiment above can be referenced for the implementation of Step 303.
Step 304 in this embodiment is the same or similar to Step 204 in the embodiment above, the description of Step 204 in the embodiment above can be referenced for the implementation of Step 304.
Step 305 in this embodiment is the same or similar to Step 205 in the embodiment above, the description of Step 205 in the embodiment above can be referenced for the implementation of Step 305.
Step 306 in this embodiment is the same or similar to Step 206 in the embodiment above, the description of Step 206 in the embodiment above can be referenced for the implementation of Step 306.
In step 307, if the new service is operating normally under the maximum access rate, it can be determined the new service is stable on the server, and new service can be released to the entire server.
Also, in releasing the new service, if the feedbacks indicate that there is error with the new service, the release of the new service can be stopped. Regardless in which stage the new service has been released, the release of the new service will be stopped whenever an error occurred on the server, which reduces the risk in releasing the new service. , , , Γ , , . i nus, an tne steps m the method lor releasing services on a server m stages m this embodiment are completed.
In accordance with the method for releasing services on a server in stages in this embodiment, new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Figure 4 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with an embodiment of the present invention. As shown in Figure 4, the apparatus includes an access rate setting module 41, a receiving module 42, and a first releasing module 43. The access rate setting module 41 is used for setting an access rate for a new service and releasing the new service in accordance with the access rate. The receiving module 42 is used for receiving a feedback from a user using the new service. The first releasing module 43 is used for increasing the access rate for the new service if the feedback is positive.
During the operation of the apparatus for releasing services on a server in stages, the access rate setting module 41 sets an access rate for the new service, which limits the number of accesses to the new service in a time period, and releases the new service in accordance with the access rate. The receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then the first releasing module 43 increases the access rate for the new service to release the new service in stages.
Preferably, the access rate setting module 41 sets an initial access rate and a maximum access rate for the new service, and first releasing module 43 increase the access rate for the new service from the initial access rate gradually to the maximum access rate to release the new service in stages.
Also, apparatus for releasing services on a server in stages in this embodiment can further include an error processing module (not shown in Figure 4) for stopping the release of the new service if the feedbacks indicate that there is error with the new service.
The operation of the apparatus for releasing services on a server in stages in this embodiment is the same or similar to the method embodiment in Figure 1, and the description of the method embodiment in Figure 1 can be referenced for the operation of the apparatus in this embodiment.
In accordance with the apparatus for releasing services on a server in stages in this
embodiment, the access rate for a new service is controlled in releasing the new service, and the number of accesses to the new service during a particular time period can be set to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Figure 5 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with another embodiment of the present invention. As shown in
Figure 5, in addition to the modules in Figure 4, the apparatus further includes an access account setting module 51, and a second releasing module 52. The access account setting module 51 is used for setting a number of accounts that can access the new service and releasing the new service to the accounts. The second releasing module 52 is used for increasing the number of accounts that can access the new service if the feedback is positive.
During the operation of the apparatus for releasing services on a server in stages, the access account setting module 51 set the account that can access the new service, and the new service is released only to these accounts. The receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then second releasing module 52 increases the accounts that can access the new service to release the new service in stages. Afterwards, the access rate setting module 41 sets an access rate for the new service, which limits the number of accesses to the new service in a time period, and releases the new service in accordance with the access rate. The receiving module 42 receives feedbacks for the new service from the users. If the received feedbacks for the new service are positive, then the first releasing module 43 increases the access rate for the new service to release the new service in stages.
Preferably, the access account setting module 51 sets an initial number and a maximum number of accounts that can access the new service, and first releasing module 43 increase the number of accounts that can access the new service from the initial number gradually to the maximum number to release the new service in stages.
The operation of the apparatus for releasing services on a server in stages in this embodiment is the same or similar to the method embodiment in Figure 2, and the description of the method embodiment in Figure 2 can be referenced for the operation of the apparatus in this embodiment.
In accordance with the apparatus for releasing services on a server in stages in this
embodiment, the accounts that can access the new service and the access rate for the new service are both controlled in releasing the new service, and new service can be released accordingly to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
Figure 6 is an exemplary schematic diagram for an apparatus for releasing services on a server in stages in accordance with yet another embodiment of the present invention.
As shown in Figure 6, in addition to the modules in Figure 5, the apparatus further includes a third releasing module 61. The third release module 61 is used for releasing the new service to the entire server.
During the operation of the apparatus for releasing services on a server in stages, after the second releasing module 52 releases the new service normally under the maximum access rate, the third releasing module 61 releases the new service to the entire server.
The operation of the apparatus for releasing services on a server in stages in this embodiment is the same or similar to the method embodiment in Figure 3, and the description of the method embodiment in Figure 3 can be referenced for the operation of the apparatus in this embodiment. In accordance with the apparatus for releasing services on a server in stages in this embodiment, new service can be released in different ways to suit different situations, which reduces the risk in releasing the new service, and improves efficiency.
The various embodiments of the present invention are merely preferred embodiments, and are not intended to limit the scope of the present invention, which includes any modification, equivalent, or improvement that does not depart from the spirit and principles of the present invention.

Claims

Claims
1. A method for releasing services on a server in stages, the method comprising:
setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period;
setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and
releasing the new service to the entire server in a third time period.
2. The method of claim 2, wherein setting a number of accounts that can access the new service and releasing the new service to the accounts comprises:
setting an initial number and an maximum number of accounts that can access the new service; and
increasing the number of accounts that can access the new service from the initial number to the maximum access rate during the first time period.
3. The method of claim 1, wherein setting an access rate for a new service and releasing the new service in accordance with the access rate comprises:
setting an initial access rate and a maximum access rate for the new service; and
increasing the access rate for the new service from the initial access rate to the maximum access rate during the second time period.
4. The method of claim 1, further comprising:
redirecting an access request for the new service to an old service.
5. An apparatus for releasing services on a server in stages, comprising:
a first releasing module for setting a number of accounts that can access a new service and releasing the new service to the accounts in a first time period;
a second releasing module for setting an access rate for the new service and releasing the new service in accordance with the access rate in a second time period; and
a third releasing module for releasing the new service to the entire server in a third time period.
6. The apparatus of claim 5, wherein first releasing module is configured for
setting an initial number and an maximum number of accounts that can access the new service; and
increasing the number of accounts that can access the new service from the initial number to the maximum access rate during the first time period.
7. The method of claim 5, wherein the second releasing module is configured for:
setting an initial access rate and a maximum access rate for the new service; and increasing the access rate for the new service from the initial access rate to the maximum access rate during the second time period.
8. The apparatus of claim 5, further comprising a redirection module for redirecting an access request for the new service to an old service.
9. A method for releasing services on a server in stages, the method comprising:
setting an access rate for a new service and releasing the new service in accordance with the access rate;
receiving a feedback from a user using the new service; and
increasing the access rate for the new service if the feedback is positive.
10. The method of claim 9, further comprising, prior to the step of setting an access rate for a new service and releasing the new service in accordance with the access rate:
setting a number of accounts that can access the new service and releasing the new service to the accounts;
receiving a feedback from a user using the new service; and
increasing the number of accounts that can access the new service if the feedback is positive.
11. The method of claim 9, further comprising, after the step of increasing the access rate for the new service:
releasing the new service to the entire server.
12. The method of claim 9, wherein increasing the access rate for the new service comprises: setting an initial access rate and a maximum access rate for the new service; and
increasing the access rate for the new service from the initial access rate gradually to the maximum access rate.
13. The method of claim 10, wherein increasing the number of accounts that can access the new service comprises:
setting an initial number and an maximum number of accounts that can access the new service; and
increasing the number of accounts that can access the new service from the initial number gradually to the maximum access rate.
14. The method of claim 9, further comprising:
stopping the release of the new service if the feedback comprises an error message.
15. An apparatus for releasing services on a server in stages, comprising:
an access rate setting module for setting an access rate for a new service and releasing the new service in accordance with the access rate;
a receiving module for receiving a feedback from a user using the new service; and a first releasing module for increasing the access rate for the new service if the feedback is positive.
16. The apparatus of claim 15, further comprising:
an access account setting module for setting a number of accounts that can access the new service and releasing the new service to the accounts; and
a second releasing module for increasing the number of accounts that can access the new service if the feedback is positive.
17. The apparatus of claim 15, further comprising:
a third releasing module for releasing the new service to the entire server.
18. The apparatus of claim 15, wherein the access rate setting module is configured for:
setting an initial access rate and a maximum access rate for the new service; and
increasing the access rate for the new service from the initial access rate gradually to the maximum access rate.
19. The apparatus of claim 16, wherein the access account setting module is configured for: setting an initial number and an maximum number of accounts that can access the new service; and
increasing the number of accounts that can access the new service from the initial number gradually to the maximum access rate.
20. The apparatus of claim 15, further comprising:
an error processing module for stopping the release of the new service if the feedback comprises an error message.
PCT/CN2013/089728 2013-01-09 2013-12-17 Method and apparatus for releasing services in stages Ceased WO2014108019A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/734,653 US10367897B2 (en) 2013-01-09 2015-06-09 Method and apparatus for releasing services in stages

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310007772.3 2013-01-09
CN201310007772.3A CN103916374B (en) 2013-01-09 2013-01-09 Service gray scale dissemination method and device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/734,653 Continuation US10367897B2 (en) 2013-01-09 2015-06-09 Method and apparatus for releasing services in stages

Publications (1)

Publication Number Publication Date
WO2014108019A1 true WO2014108019A1 (en) 2014-07-17

Family

ID=51041781

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/089728 Ceased WO2014108019A1 (en) 2013-01-09 2013-12-17 Method and apparatus for releasing services in stages

Country Status (3)

Country Link
US (1) US10367897B2 (en)
CN (1) CN103916374B (en)
WO (1) WO2014108019A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106162345A (en) * 2015-04-10 2016-11-23 Tcl集团股份有限公司 The gray scale upgrade method of a kind of intelligent television system and system

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104156246B (en) * 2014-08-12 2017-06-16 小米科技有限责任公司 The method and device of gray scale upgrading
US9886258B2 (en) 2014-08-12 2018-02-06 Xiaomi Inc. Method and device for grayscale-upgrading
CN105897457A (en) * 2015-12-09 2016-08-24 乐视云计算有限公司 Service upgrade method and system of server group
CN107145347A (en) * 2017-04-27 2017-09-08 努比亚技术有限公司 One kind application gray scale dissemination method, equipment and storage medium
CN108874413A (en) * 2017-10-30 2018-11-23 北京旷视科技有限公司 Service upgrade method, apparatus, system and storage medium
CN108376118B (en) * 2018-02-09 2021-07-13 腾讯科技（深圳）有限公司 Service distribution system, method, device and storage medium
CN110297659A (en) * 2018-03-21 2019-10-01 北京京东尚科信息技术有限公司 Algorithm model disposes loading method and device
CN108574601A (en) * 2018-03-27 2018-09-25 无锡华云数据技术服务有限公司 A kind of gray scale dissemination method and system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102064954A (en) * 2009-11-17 2011-05-18 腾讯科技（深圳）有限公司 Distributed fault tolerant system, equipment and method
CN102413022A (en) * 2011-12-31 2012-04-11 北京新媒传信科技有限公司 Application debugging method and system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7178144B2 (en) * 2002-04-23 2007-02-13 Secure Resolutions, Inc. Software distribution via stages
US7334005B2 (en) * 2005-04-13 2008-02-19 Symantec Corporation Controllable deployment of software updates
US7555551B1 (en) * 2005-04-13 2009-06-30 Symantec Corporation Automatic controllable deployment of software updates
US7764615B2 (en) * 2006-07-10 2010-07-27 International Business Machines Corporation Distributing rate limits and tracking rate consumption across members of a cluster
US8566895B2 (en) * 2008-02-15 2013-10-22 Time Warner Cable Inc. System and method for incremental implementation of new service capabilities
CN102497454B (en) * 2011-12-31 2014-06-11 北京新媒传信科技有限公司 Method for realizing gray publication of application in application service platform system
US9690559B2 (en) * 2012-09-22 2017-06-27 Avaya Inc. Downloadable pluggable services

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102064954A (en) * 2009-11-17 2011-05-18 腾讯科技（深圳）有限公司 Distributed fault tolerant system, equipment and method
CN102413022A (en) * 2011-12-31 2012-04-11 北京新媒传信科技有限公司 Application debugging method and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHENG QIAN: "Research on the Technology of Massive Service in Music Box Background Music Project", CHINESE MASTER'S THESES FULL-TEXT DATABASE, INFORMATION SCIENCE AND TECHNOLOGY, 15 July 2012 (2012-07-15), pages 1138 - 280 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106162345A (en) * 2015-04-10 2016-11-23 Tcl集团股份有限公司 The gray scale upgrade method of a kind of intelligent television system and system
CN106162345B (en) * 2015-04-10 2020-02-07 Tcl集团股份有限公司 Gray scale upgrading method and system for smart television system

Also Published As

Publication number Publication date
US10367897B2 (en) 2019-07-30
CN103916374A (en) 2014-07-09
US20150281379A1 (en) 2015-10-01
CN103916374B (en) 2018-04-20

Similar Documents

Publication Publication Date Title
WO2014108019A1 (en) Method and apparatus for releasing services in stages
EP3340633A1 (en) Terminal, cache server, and method for acquiring video slices and device thereof
CN107733972B (en) A kind of short link parsing method, device and equipment
WO2019237594A1 (en) Session persistence method and apparatus, and computer device and storage medium
US8443054B2 (en) Method, system, and scheduling server for content delivery
CN105915583B (en) Method for starting service cluster and service cluster
US20150024793A1 (en) Push notification middleware
CN108989238A (en) A method for allocating service bandwidth and related equipment
EP2698730A1 (en) Data acquisition method, device and system
KR20180090184A (en) Sequence-dependent data message integration in a voice-activated computer network environment
CN102081605A (en) Data warehouse-based data encapsulation device and service data acquisition method
CN104965727B (en) A kind of method and device for restarting server
CN109889567B (en) Implementation method of IoT platform supporting massive device access
WO2016115787A1 (en) Data synchronization method and data synchronization system for multi-system device, and terminal
WO2005018254A3 (en) Provision of services by reserving resources in a communications network having resource management according to policy rules
CN106131122A (en) A kind of method and device disposing load balancing service
US10044766B2 (en) Managing mid-dialog session initiation protocol (SIP) messages
CN103188305B (en) A kind of multithread breakpoint continued transmission method and system
WO2019104974A1 (en) Dubbo platform-based automatic server starting and stopping method , server, and storage medium
US8705709B2 (en) Visual voicemail (VVM) recovery
US20170127218A1 (en) Systems and methods for machine-type communication
RU2016150414A (en) PREVIOUS CREDIT CONTROL
WO2021027474A1 (en) Positioning assistance information broadcasting method, positioning server and ran node
CN104301352B (en) The adaptation method and device of double-terminal
CN106331904A (en) Method of distributing wavelength channels in passive optical network, optical line terminal and system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13870850

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/11/2015)

122 Ep: pct application non-entry in european phase

Ref document number: 13870850

Country of ref document: EP

Kind code of ref document: A1