WO2015085735A1

WO2015085735A1 - Information requesting method and system

Info

Publication number: WO2015085735A1
Application number: PCT/CN2014/079648
Authority: WO
Inventors: Hongwen WU
Original assignee: Tencent Technology (Shenzhen) Company Limited
Priority date: 2013-12-09
Filing date: 2014-06-11
Publication date: 2015-06-18
Also published as: CN104702647A; CN104702647B; TW201521844A

Abstract

Methods and systems for requesting information are provided.The system includes a first server,a second server,and a third server.The first server receives a request message for obtaining information sent by a user.In response to the request message,the first server determines whether the user has a permission to obtain the information.After determining the user has the permission to obtain the information,the first server can request for acquiring the information from the second server.When the first server fails to request for acquiring the information from the second server, the first server can request for re-sending the information from the third server.When the first server succeeds in requesting for re-sending the information from the third server,the first server can forward the information received from the third server to the user.

Description

INFORMATION REQUESTING METHOD AND SYSTEM

CROS S-REFERENCES TO RELATED APPLICATIONS

[0001] This application claims priority to Chinese Patent Application No. 201310662372.6, filed on December 9, 2013, the entire contents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

[0002] The present disclosure generally relates to the field of communications and, more particularly, relates to methods and systems for requesting information.

BACKGROUND

[0003] In current online games, game props are important elements for enriching game content and improving user experience. A process for claiming or obtaining game props typically involves access to multiple databases and communications among multiple servers. For the convenience of centralized management on assigning game props to users, a claiming webpage for the game props is usually set on an official website server of the game. Methods for issuing game props are associated with game contents, hence such methods are usually set on a game server.

[0004] FIG. 1 illustrates a conventional method for claiming game props. In the method, a user sends a request for claiming props to an official website server (SI 02 of FIG. 1). The official website server checks whether the user who sends the request has permission to claim props (SI 04 of FIG. 1). When the user has the permission, the official website server sends a request for issuing the props to a game server and performs Step SI 10 (S 106 of FIG. 1). When the user sending the request does not have the permission to claim the props, an instruction indicating that there is no permission for claiming the props is returned to the user (S108 of FIG. 1). In Step SI 10 of FIG. 1, when the game server has successfully sent corresponding props after receiving the request for issuing the game props, an instruction indicating a successful claiming of props is returned to the user. When the game server fails to issue corresponding props after receiving the request for issuing the props, a rollback operation is performed to again check the user's permission for claiming the game props (SI 12 of FIG. 1) and an instruction indicating a failure to claim the props is returned to the user (SI 14 of FIG. 1).

[0005] In the conventional method, the claiming process is completed regardless of success or failure of the claiming for game props. When the issuing of the game props fails, the user usually resends a request for claiming the game props when receiving a feedback indicating a failed claiming of the game props. The official website server then needs to respond to this request message again, and to check the user's permission again to process the operations. Considering the large user base for an online game, the conventional method significantly increases the workload on the official website server and increases pressure on accessing the database that stores user's permissions. On the other hand, the rollback operation performed after a failed claiming of the game props also increases the workload to read and write the database. Consequently, a negative impact can occur on the operational status of the online game, which affects user experience.

BRIEF SUMMARY OF THE DISCLOSURE

[0006] One aspect of the present disclosure includes an information requesting method. A first server receives a request message for obtaining information sent by a user. In response to the request message, the first server determines whether the user has a permission to obtain the information. When the user has the permission to obtain the information, the first server requests for acquiring the information from a second server. When the first server fails to request for acquiring the information from the second server, the first server requests for re-sending the information from a third server. When the first server succeeds in requesting for re-sending the information from the third server, the first server forwards the information received from the third server to the user.

[0007] When the first server forwards the information received from the third server to the user after the first server succeeds in requesting for re-sending the information from the third server, the first server acquires the information sent by the third server on a first re-sending time set by the third server, and forwards the information received from the third server to the user.

[0008] When the first server requests for re -sending the information from the third server, the third server sets a first re-sending time and sends the information to the first server on the first re- sending time; determines whether a current number of times for re-sending the information reaches a preset threshold value, when the third server fails to re-send the information to the first server on the first re-sending time; and sets a second re-sending time and sends the information to the first server on the second re-sending time, when the third server determines that the current number of times for re-sending the information does not reach the preset threshold value. In this case, during requesting for re-sending the information from the third server, the third server stops re-sending the information to the first server and sends an alarming message to a management device configured to manage the information, when the third server determines that the current number of times for re-sending the information reaches the preset threshold value.

[0009] The third server sets the first re-sending time and the second re-sending time according to at least one of: a business type corresponding to the information; whether the second server stops working; and a workload of the third server. The information includes information indicating props of a game program. The information indicating the props of the game program includes at least one of: a game business name, a role ID, a prop ID, and a quantity of the props.

[0010] Another aspect of the present disclosure includes an information requesting system. The system includes a first server, a second server, and a third server. The first server includes a receiving unit, a first determining unit, a first requesting unit, a second requesting unit, and a forwarding unit.

[0011 ] The receiving unit is configured to receive a request message for obtaining information sent by a user. The first determining unit is configured, in response to the request message, to determine whether the user has a permission to obtain the information. The first requesting unit is configured to request for acquiring the information from the second server, when the user has the permission to obtain the information. The second requesting unit is configured to request for re-sending the information from the third server, when the first server fails to request for acquiring the information from the second server. The forwarding unit is configured to forward the information received from the third sever to the user, when the first server succeeds in requesting for re-sending the information from the third server.

[0012] In the system, the forwarding unit includes: an acquiring module, and a forwarding module. The acquiring module is configured to acquire the information sent by the third server on a first re-sending time set by the third server when the first server succeeds in requesting for re-sending the information from the third server. The forwarding module is configured to forward the information received from the third server to the user.

[0013] The third sever includes: a sending unit and a second determining unit. The sending unit is configured to set a first re-sending time and to send the information to the first server on the first re-sending time. The second determining unit is configured to determine whether a current number of times for re-sending the information reaches a preset threshold value, when the sending unit of the third server fails to re-send the information to the first server on the first re-sending time. The sending unit is further configured to set a second re-sending time and send the information to the first server on the second re-sending time when the third server determines that the current number of times for re-sending information does not reach a preset threshold value.

[0014] The third server further includes an alarming unit configured to stop re-sending the information to the first server and to send an alarming message to a management device configured to manage the information when the second determining unit determines that the current number of times for re-sending the information reaches the preset threshold value.

[0015] The sending unit of the third server sets the first re-sending time and the second re- sending time according to at least one of: a business type corresponding to the information; whether the second server stops working; and a workload of the third server. The information includes information indicating props of a game program and the information indicating props of the game program includes at least one of: a game business name, a role ID, a prop ID, and a quantity of the props.

[0016] Other aspects of the present disclosure can be understood by those skilled in the art in light of the description, the claims, and the drawings of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The following drawings are merely examples for illustrative purposes according to various disclosed embodiments and are not intended to limit the scope of the present disclosure.

[0018] FIG. 1 is a schematic of a conventional information requesting system; [0019] FIG. 2 depicts an exemplary information requesting method consistent with various disclosed embodiments;

[0020] FIG. 3 depicts another exemplary information requesting method consistent with various disclosed embodiments;

[0021] FIG. 4 depicts another exemplary information requesting method consistent with various disclosed embodiments;

[0022] FIG. 5 depicts another exemplary information requesting method consistent with various disclosed embodiments;

[0023] FIG. 6 depicts an exemplary information requesting system consistent with various disclosed embodiments;

[0024] FIG. 7 depicts another exemplary information requesting system consistent with various disclosed embodiments;

[0025] FIG. 8 depicts another exemplary information requesting system consistent with various disclosed embodiments;

[0026] FIG. 9 depicts another exemplary information requesting system consistent with various disclosed embodiments;

[0027] FIG. 10 depicts another exemplary information requesting system consistent with various disclosed embodiments;

[0028] FIG. 11 depicts an exemplary environment incorporating certain disclosed embodiments; and

[0029] FIG. 12 depicts an exemplary computer system consistent with the disclosed embodiments.

DETAILED DESCRIPTION

[0030] Reference will now be made in detail to exemplary embodiments of the disclosure, which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

[0031] FIGS. 1-10 depict exemplary methods and systems for requesting information in accordance with various disclosed embodiments. The exemplary methods and systems can be implemented, for example, in an exemplary environment 1100 as shown in FIG. 11.

[0032] As shown in FIG. 11, the environment 1100 can include a server 1104, a terminal 1106, and a communication network 1102. The server 1104 and the terminal 1106 may be coupled through the communication network 1102 for information exchange, for example, Internet searching, webpage browsing, etc. Although only one terminal 1106 and one server 1104 are shown in the environment 1100, any number of terminals 1106 or servers 1104 may be included, and other devices may also be included. [0033] The communication network 1102 may include any appropriate type of communication network for providing network connections to the server 1104 and terminal 1106 or among multiple servers 1 104 or terminals 1106. For example, the communication network 1102 may include the Internet or other types of computer networks or telecommunication networks, either wired or wireless.

[0034] A terminal, as used herein, may refer to any appropriate user terminal device with certain computing capabilities, for example, a personal computer (PC), a work station computer, a notebook computer, a car computer (e.g., carrying in a car or other vehicles), a server computer, a hand-held computing device (e.g., a tablet computer), a mobile terminal (e.g., a mobile phone, a smart phone, an iPad, and/or an aPad), a POS (i.e., point of sale) device, or any other user-side computing device. In various embodiments, the terms "terminal" and "terminal device" can be used interchangeably. In various embodiments, the terminal 1106 can include a client or a browser installed therein, e.g., for users to play on-line games.

[0035] A server, as used herein, may refer one or more server computers configured to provide certain server functionalities, for example, search engines and database management. A server may also include one or more processors to execute computer programs in parallel. As used herein, the server can include a game server, an official webpage server, etc.

[0036] The server 1104 and the terminal 1106 may be implemented on any appropriate computing platform. FIG. 12 shows a block diagram of an exemplary computer system 1200 capable of implementing the server 1104 (and/or the terminal 1106). As shown in FIG. 12, the exemplary computer system 1200 may include a processor 1202, a storage medium 1204, a monitor 1206, a communication module 1208, a database 1210, peripherals 1212, and one or more bus 1214 to couple the devices together. Certain devices may be omitted and other devices may be included.

[0037] The processor 1202 can include any appropriate processor or processors. Further, the processor 1202 can include multiple cores for multi-thread or parallel processing. The storage medium 1204 may include memory modules, for example, ROM, RAM, and flash memory modules, and mass storages, for example, CD-ROM, U-disk, removable hard disk, etc. The storage medium 1204 may store computer programs for implementing various processes, when executed by the processor 1202.

[0038] Further, the peripherals 1212 may include I/O devices, for example, keyboard and mouse, and the communication module 1208 may include network devices for establishing connections through the communication network 1102. The database 1210 may include one or more databases for storing certain data and for performing certain operations on the stored data, for example, webpage browsing, database searching, etc.

[0039] In operation, the terminal 1106 may cause the server 1104 to perform certain actions, for example, an Internet search or other database operations. The server 1 104 may be configured to provide structures and functions for such actions and operations. More particularly, the server 1104 may include a data searching system for real-time database searching. In various embodiments, a terminal, for example, a mobile terminal involved in the disclosed methods and systems can include the terminal 1106.

[0040] FIG. 2 depicts an exemplary information requesting method consistent with various disclosed embodiments.

[0041] As shown in FIG. 2, a first server receives a request message for obtaining information sent by a user (Step S202). In response to the request message, the first server determines whether the user has a permission to obtain the information (Step S204). When the user has the permission to obtain the information, the first server requests for acquiring the information from a second server (Step S206). When the first server fails to request for acquiring the information from the second server, the first server requests for re-sending the information from a third server (Step S208). When the first server succeeds in requesting for re-sending the information from the third server, the first server forwards the information received from the third server to the user (Step S210).

[0042] Note that one aspect of the present disclosure is to provide a method for responding to the request message for obtaining the information sent by the user. Once the user is determined that has the permission to access to the information, the first server is promoted as much as possible to successfully return the information to the user during this one response to the request message sent by the user. The number of operations on a database can therefore be reduced by the server(s). Consequently, the workload (e.g., for accesses to database and operations of server) of server and database can be reduced. In various embodiments, the information may be any information related to game props (e.g., prop ID). However, the information disclosed herein is not to be limited to the game props, any suitable information mentioned in online games can be encompassed within the scope of the present disclosure.

[0043] In the exemplary Step S202 of the information requesting method of FIG. 2, the first server receives the request message for obtaining the information sent by the user. The request message for obtaining the information can include an http (Hypertext Transfer Protocol) request, an ftp (File Transfer Protocol) request, or any other requests that meets suitable text transfer formats. For example, for an http request, the corresponding request message can include a request line, a message header, and a message body. Optionally, in Step S202, the request message may carry an identifier that corresponds to the information to be requested by the request message and is able to be identified by the first server. For example, when game props are used as the requested information, the message can contain a prop ID of the game props.

[0044] In various embodiments, the first server can be a server dedicated to processing such requests. The first server can be, e.g., an official website server. However, it should be appreciated that the first server (e.g., the official website server) may also be used to perform any other suitable operations. Further, in various embodiments, the present disclosure is not limited to the first, second and/or third server.

[0045] In Step S204 of the information requesting method of FIG. 2, in response to the request message, the first server determines whether the user has a permission to obtain the information. That is, an authentication operation can be performed by the first server to determine whether the user is authorized to obtain the requested information. In one embodiment, the exemplary Step S204 may be performed using an authentication mode similar to any suitable conventional technology. For example, the first server can access a database that stores

authentication information corresponding to the requested information, and decides whether the authentication information is included in the request message sent by the user. When the authentication information is included, it is then determined that the user has a permission to obtain the requested information. When the authentication information is not included, the user then has no permission to obtain the requested information.

[0046] Further, in one embodiment, when the user is determined in Step S204 to have the permission to obtain/access the requested information, then in Step S206 the first server can request the second server to deliver the requested information (i.e., to obtain the information from the second server). In this scenario, the request sent by the first server to the second server can be a different request, that differs from the aforementioned request message sent by the user and that is able to be identified by the second server. In other cases, the request sent by the first server may be the same request as the request message sent by the user in Step 202 (this can thus be considered to be the request that is forwarded by the first server to the second server).

[0047] In an exemplary application of online games, the second server can be a game server. Thus the second server (e.g., the game server) can allot the requested information to the user based on the received request. For example, the game server can issue (or release) game props

corresponding to the request to the user. In one embodiment, the second server can issue the requested information in a variety of manners. In online games, the game server as the second server can directly issue the game props to be claimed to the game user, or can correspondingly add the prop ID of the game props to a data record (e.g., including attributes or properties of the game props) of the user. In other embodiments, the requested information returned from the second server may not be sent directly to the user, but forwarded to the user via the first server. The scope of present disclosure is not limited.

[0048] Further, in one embodiment, after the second server has responded the request sent by the first server, it is determined whether the second server can successfully issue the requested information. In the example of an online game, after the game server as the second server responds to the request and issues the corresponding game props, the game server itself can check the database to determine whether the user requesting the game props has successfully claimed the props. Such database can be stored on the game server or on a third-party server connected to the game server.

[0049] In various embodiments, any other suitable methods can be used to determine whether the second server successfully issues the requested information. For example, in the aforementioned circumstances of returning the requested information by the second server to the user via the first server, the first server can be used to check whether the requested information is received and/or sent out, and this determination result can be used for determining whether the second server successfully releases the requested information. In other words, the operation of issuing the requested information by the second server can be considered as a response made by the second server to the request sent by the first server. Therefore, the above determination result can also be used to express whether the first server successfully requests for obtaining the information from the second server.

[0050] Based on the above determination result and according to the information requesting method disclosed, in exemplary Step S208, when the first server fails to request for acquiring the information from the second server, the first server can request a third server for re-sending the information.

[0051 ] As disclosed, the requested information that is failed to be issued or released from the second server can be re-issued or re-sent from a third server or from a re-sending system on the third server, which is contrary to conventional technologies where operations simply rolling back to the first server and database, and returning to the user with an instruction indicating a failure of obtaining information are performed. In various embodiments, the disclosed re-sending system on the third server can correspond to an information issuing system stored on the second server. For example, more complex re-sending mechanisms can be included in accordance with various embodiments.

[0052] In various embodiments, the third server can only be used as a server for storing the disclosed re-sending system. In some embodiments, the re-sending system can be wholly or partially stored on the second server (e.g., the game server). In other embodiments, the third server and the second server can be integrally combined.

[0053] Further, in Step S210, when the first server succeeds in requesting for re-sending the information from the third server, the first server forwards the information received from the third server to the user.

[0054] A variety of methods for forwarding the information can be included herein. For example, as shown in FIG. 3, the Step S210 may include: the first server obtains the requested information sent by the third server at a first re-sending time set by the third server (Step S302 of FIG. 3). The first server then forwards the requested information received from the third server to the user (Step S304 of FIG. 3).

[0055] In this case, the first server can be used as a transit server for the requested information corresponding to the request to forward the received information to the user after receiving the requested information from the third server in Step S302. In this manner, the interaction between the user and the first server, the interaction between the first server and the second server, and the interaction between the first server and the third server can have a logic that can be decoupled, thereby simplifying maintenance of the information requesting system. In addition, similar determination processes can be made about whether the information requested from the second server is successful and whether the information requested from the third server is successful, and the determination logic can be unified and set on a same server, e.g., the first server, which further simplifies the maintenance of the information requesting system.

[0056] Of course, the above described are for example only, various embodiments can include any suitable implementing methods. For example, similar to the issuing of the requested information by the second server as described above, in some embodiments, the third server can re- send the requested information directly to the user, followed by the user or the third server to determine whether the re-sending is successful.

[0057] Further, in Step S302, the re-sent information can be obtained at a first re-sending time set by the third server. Through this setting, the re-sending operation can be conducted after a period of time when the issuing of the requested information fails, thereby avoiding occurrence of same failure again to some extent. Of course, the first re-sending time may be delayed for a relatively short time, to avoid a longer waiting time that can affect user experience.

[0058] Optionally, as shown in FIG. 4, Step S208 can include: setting a first re-sending time by the third server and sending the requested information to the first server on the first re-sending time (Step S402 of FIG. 4); determining by the third server whether the current number of times for re-sending the information reaches a predetermined threshold value, when the third server fails to re- send the requested information to the first server on the first re-sending time (Step S404 of FIG. 4); and setting a second re-sending time by the third server and sending the requested information to the first server on the second re-sending time when the third server determines that the current number of times for re-sending the information does not reach a predetermined threshold value (S406 of FIG. 4).

[0059] The third server can send the requested information to the first server on a first re- sending time that is delayed for a period of time, and can re-send the information again on a second re-sending time set in Step S406 in the case when the first re-sending of information fails. As described in Step S404, the overall number of times for re-sending from the third server can be limited within a predetermined threshold value, users thus do not need to wait for extended

(sometimes unlimited) period of time to obtain the requested information. This limited re-sending mechanism can avoid over usage of the re-sending process due to possible system loopholes.

[0060] In one embodiment, as shown in FIG. 5, when the third server determines that the current number of re-sending the information does not reach a predetermined threshold value, exemplary Step S208 can further include: stopping re-sending the information by the third server to the first sever and also sending an alarming message to a management device configured to manage the information.

[0061 ] In one embodiment, the third server may set the first re-sending time and the second re-sending time according to at least one of the following: the business type corresponding to the information; whether the second server stops working; and/or workload of the third server. The third server can reasonably set a first re-sending time and a second re-sending time according to working status of the information requesting system, to avoid excessive operation workload.

[0062] As disclosed, a re-sending mechanism of the requested information can be used when the second server fails to issue the requested information. In one embodiment, to a certain extent, the information requested by the user can be returned to the user in a single response by the first server. Thus, conventional rollback operations performed after the issuing of the information fails can be avoided. Further, processes including that the user needs to resend the request for obtaining the information due to the failure of issuing information can be avoided. In addition, the re- authentication process of the first server can be avoided to reduce workload of the first server and to reduce workload of the database corresponding to the rollback operations and authentication operations. The disclosed methods for requesting information thus solve the problems due to significant workload of the server and the significant pressure of writing and reading processes of the database caused by the rollback operations after issuing of the props fails as known in conventional methods for claiming game props.

[0063] In a specific embodiment for information requesting method in an online game, the information requested by a user may include information indicating props in a game program, and more specifically, may include at least one of the following: a game business name, a role ID, a prop ID, and/or a number of the props.

[0064] FIG. 6 depicts an exemplary information requesting system consistent with various disclosed embodiments. In this exemplary embodiment, the information requesting system may include a first server (e.g., an official website server), a second server (e.g., a game server), and/or an information re-sending system (e.g., stored on the second server and/or a third server).

[0065] In one embodiment, a user sends a request for obtaining or claiming props from the official website server (Step S602). The official website server checks the user's authority (Step S604). When the user that sends the request message has the authority (or permission) for obtaining the props, the official website server then sends a request for releasing (or issuing) the props to the game server; and the method proceeds to perform Step S610 (Step S606). When the user that sends the request message does not have the authority for obtaining the props, an instruction is then returned to the user indicating that the user does not have the authority (Step S608).

[0066] When the game server successfully returns the corresponding game props after receiving the request for issuing the props, an instruction is then returned to the user indicating a successful obtaining of the props (Step S610). When the game server fails to return the corresponding game props after receiving the request for issuing the props, a request for re-sending the props is then sent to a re-sending system (Step S612). When game props are successfully re-sent, an instructing is returned to the user indicating a successful obtaining of the props (Step S614). When a number of times for re-sending the props reaches or exceeds a predetermined threshold value and the game props are still unsuccessfully re-sent, an instruction can be returned to the user indicating a failure of obtaining the information (e.g., the props) (Step S616).

[0067] FIG. 7 depicts another exemplary information requesting system consistent with various disclosed embodiments. The exemplary information requesting system can include a first sever, a second server, and/or a third server.

[0068] As shown in FIG. 7, the first server includes a receiving unit 702, a first determining unit 704, a first requesting unit 706, a second requesting unit 708, and/or a forwarding unit 710.

[0069] The receiving unit 702 is configured to receive a request message for obtaining information sent by a user. The first determining unit 704 is configured, in response to the request message, to determine whether the user has a permission to obtain the information. The first requesting unit 706 is configured to request for acquiring the information from the second server, when the user has the permission to obtain the information.

[0070] The second requesting unit 708 is configured to request for re-sending the information from the third server, when the first server fails to request for acquiring the information from the second server. The forwarding unit 710 is configured to forward the information received from the third sever to the user, when the first server succeeds in requesting for re-sending the information from the third server.

[0071 ] As disclosed, a re-sending mechanism of the requested information can be used when the second server fails to issue the requested information. In one embodiment, to a certain extent, the information requested by the user can be returned to the user in a single response by the first server. Thus, conventional rollback operations performed after the issuing of the information fails can be avoided. Further, processes including that the user needs to resend the request for obtaining the information due to the failure of issuing information can be avoided. In addition, the re- authentication process of the first server can be avoided to reduce workload of the first server and to reduce workload of the database corresponding to the rollback operations and authentication operations. The disclosed systems for requesting information thus solve the problems due to significant workload of the server and the significant pressure of writing and reading processes of the database caused by the rollback operations after issuing of the props fails as known in conventional methods for claiming game props. In various embodiments, the information may be information related to game props including, e.g., prop ID without limitation. [0072] By the receiving unit 702 of the information requesting system, the first server receives the request message for obtaining the information sent by the user. The request message for obtaining the information can include an http (Hypertext Transfer Protocol) request, an ftp (File Transfer Protocol) request, or any other requests that meets suitable text transfer formats. For example, for an http request, the corresponding request message can include a request line, a message header, and a message body. Optionally, by the receiving unit 702, the request message may carry an identifier that corresponds to the information to be requested by the request message and is able to be identified by the first server. For example, when game props are used as the requested information, the message can contain a prop ID of the game props.

[0073] In various embodiments, the first server can be a server dedicated to processing such requests. The first server can be, e.g., an official website server. However, it should be appreciated that the first server (e.g., the official website server) may also be used to perform any other suitable operations. Further, in various embodiments, the present disclosure is not limited to the first, second and/or third server.

[0074] In the determining unit 704 of the information requesting system, in response to the request message, the first server determines whether the user has a permission to obtain the information. That is, an authentication operation can be performed by the first server to determine whether the user is authorized to obtain the requested information. In one embodiment, the exemplary the determining unit 704 may be performed using an authentication mode similar to any suitable conventional technology. For example, the first server can access a database that stores authentication information corresponding to the requested information, and decides whether the authentication information is included in the request message sent by the user. When the authentication information is included, it is then determined that the user has a permission to obtain the requested information. When the authentication information is not included, the user then has no permission to obtain the requested information.

[0075] Further, in one embodiment, when the user is determined by the determining unit 704 to have the permission to obtain/access the requested information, then the first requesting unit 706 of the first server can request the second server to deliver the requested information (i.e., to obtain the information from the second server). In this scenario, the request sent by the first server to the second server can be a different request, that differs from the aforementioned request message sent by the user and that is able to be identified by the second server. In other cases, the request sent by the first server may be the same request as the request message sent by the user (this can thus be considered to be the request that is forwarded by the first server to the second server).

[0076] In an exemplary application of online games, the second server can be a game server. Thus the second server (e.g., the game server) can allot the requested information to the user based on the received request. For example, the game server can issue (or release) game props corresponding to the request to the user. In one embodiment, the second server can issue the requested information in a variety of manners. In online games, the game server as the second server can directly issue the game props to be claimed to the game user, or can correspondingly add the prop ID of the game props to a data record (e.g., including attributes or properties of the game props) of the user. In other embodiments, the requested information returned from the second server may not be sent directly to the user, but forwarded to the user via the first server. The scope of present disclosure is not limited.

[0077] Further, in one embodiment, after the second server has responded the request sent by the first server, it is determined whether the second server can successfully issue the requested information. In the example of an online game, after the game server as the second server responds to the request and issues the corresponding game props, the game server itself can check the database to determine whether the user requesting the game props has successfully claimed the props. Such database can be stored on the game server or on a third-party server connected to the game server.

[0078] In various embodiments, any other suitable methods can be used to determine whether the second server has successfully issued the requested information. For example, in the

aforementioned circumstances of returning the requested information by the second server to the user via the first server, the first server can be used to check whether the requested information is received and/or sent out, and this determination result can be used for determining whether the second server successfully releases the requested information. In other words, the operation of issuing the requested information by the second server can be considered as a response made by the second server to the request sent by the first server. Therefore, the above determination result can also be used to express whether the first server successfully requests for obtaining the information from the second server.

[0079] Based on the above determination result and according to the information requesting method disclosed, by the second requesting unit 708, when the first server fails to request for acquiring the information from the second server, the first server can request a third server for re- sending the information.

[0080] As disclosed, the requested information that is failed to be issued or released from the second server can be re-issued or re-sent from a third server or from a re-sending system on the third server, which is contrary to conventional technologies where operations simply rolling back to the first server and database, and returning to the user with an instruction indicating a failure of obtaining information are performed. In various embodiments, the disclosed re-sending system on the third server can correspond to an information issuing system stored on the second server. For example, more complex re-sending mechanisms can be included in accordance with various embodiments.

[0081 ] In various embodiments, the third server can only be used as a server for storing the disclosed re-sending system. In some embodiments, the re-sending system can be wholly or partially stored on the second server (e.g., the game server). In other embodiments, the third server and the second server can be integrally combined.

[0082] Further, by the forwarding unit 710, when the first server succeeds in requesting for re-sending the information from the third server, the first server forwards the information received from the third server to the user.

[0083] A variety of methods for forwarding the information can be included herein. For example, as shown in FIG. 8, the forwarding unit 710 may include: an acquiring module 802 and/or a forwarding module 804. The acquiring module 802 is configured to acquire the information sent by the third server on a first re-sending time set by the third server when the first server succeeds in requesting for re-sending the information from the third server. The forwarding module 804 is configured to forward the information received from the third server to the user.

[0084] In this case, the first server can be used as a transit server for the requested information corresponding to the request to forward the received information to the user after receiving the requested information from the third server by the acquiring module 802. In this manner, the interaction between the user and the first server, the interaction between the first server and the second server, and the interaction between the first server and the third server can have a logic that can be decoupled, thereby simplifying maintenance of the information requesting system. In addition, similar determination processes can be made about whether the information requested from the second server is successful and whether the information requested from the third server is successful, and the determination logic can be unified and set on a same server, e.g., the first server, which further simplifies the maintenance of the information requesting system.

[0085] Of course, the above described are for example only, various embodiments can include any suitable implementing methods. For example, similar to the issuing of the requested information by the second server as described above, in some embodiments, the third server can re- send the requested information directly to the user, followed by the user or the third server to determine whether the re-sending is successful.

[0086] Further, by the acquiring unit 802, the re-sent information can be obtained at a first re- sending time set by the third server. Through this setting, the re-sending operation can be conducted after a period of time when the issuing of the requested information fails, thereby avoiding occurrence of same failure again to some extent. Of course, the first re-sending time may be delayed for a relatively short time, to avoid a longer waiting time that can affect user experience.

[0087] Optionally, as shown in FIG. 9, the third server can include: a sending unit 902 and/or a second determining unit 904. The sending unit 902 is configured to set a first re -sending time and to send the information to the first server on the first re-sending time. The second determining unit 904 is configured to determine whether a current number of times for re-sending the information reaches a preset threshold value, when the sending unit 902 of the third server fails to re-send the information to the first server on the first re-sending time. The sending unit 902 is further configured to set a second re-sending time and send the information to the first server on the second re-sending time when the third server determines that the current number of times for re-sending information does not reach a preset threshold value.

[0088] The third server can send the requested information to the first server on a first re- sending time that is delayed for a period of time, and can re-send the information again on a second re-sending time set by the sending unit 902 in the case when the first re-sending of information fails. By the second determining unit 904, the overall number of times for re-sending from the third server can be limited within a predetermined threshold value, users thus do not need to wait for extended (sometimes unlimited) period of time to obtain the requested information. This limited re-sending mechanism can avoid over usage of the re-sending process due to possible system loopholes.

[0089] In one embodiment, as shown in FIG. 10, when the third server determines that the current number of re-sending the information does not reach a predetermined threshold value, the third server can further include: an alarming unit 1002 configured to stop re-sending the information to the first sever and to send an alarming message to a management device configured to manage the information.

[0090] In one embodiment, the sending unit 902 may set the first re-sending time and the second re-sending time according to at least one of the following: the business type corresponding to the information; whether the second server stops working; and/or workload of the third server. The third server can reasonably set a first re-sending time and a second re-sending time according to working status of the information requesting system, to avoid excessive operation workload.

[0091 ] As disclosed, a re-sending mechanism of the requested information can be used when the second server fails to issue the requested information. In one embodiment, to a certain extent, the information requested by the user can be returned to the user in a single response by the first server. Thus, conventional rollback operations performed after the issuing of the information fails can be avoided. Further, processes including that the user needs to resend the request for obtaining the information due to the failure of issuing information can be avoided. In addition, the re- authentication process of the first server can be avoided to reduce workload of the first server and to reduce workload of the database corresponding to the rollback operations and authentication operations. The disclosed methods for requesting information thus solve the problems due to significant workload of the server and the significant pressure of writing and reading processes of the database caused by the rollback operations after issuing of the props fails as known in conventional methods for claiming game props.

[0092] In a specific embodiment for information requesting system in an online game, the information requested by a user may include information indicating props in a game program, and more specifically, may include at least one of the following: a game business name, a role ID, a prop ID, and/or a number of the props.

[0093] As shown in FIG. 6, in the exemplary embodiment, the information requesting system may include a first server (e.g., an official website server), a second server (e.g., a game server), and/or an information re-sending system (e.g., stored on the second server and/or a third server).

[0094] In one embodiment, a user sends a request for obtaining or claiming props from the official website server (Step S602). The official website server checks the user's authority (Step S604). When the user that sends the request message has the authority (or permission) for obtaining the props, the official website server then sends a request for releasing (or issuing) the props to the game server; and the method proceeds to perform Step S610 (Step S606). When the user that sends the request message does not have the authority for obtaining the props, an instruction is then returned to the user indicating that the user does not have the authority (Step S608). When the game server successfully returns the corresponding game props after receiving the request for issuing the props, an instruction is then returned to the user indicating a successful obtaining of the props (Step S610). When the game server fails to return the corresponding game props after receiving the request for issuing the props, a request for re-sending the props is then sent to a re-sending system (Step S612). When game props are successfully re-sent, an instructing is returned to the user indicating a successful obtaining of the props (Step S614). When a number of times for re-sending the props reaches or exceeds a predetermined threshold value and the game props are still unsuccessfully re-sent, an instruction can be returned to the user indicating a failure of obtaining the information (e.g., the props) (Step S616).

[0095] In a specific embodiment, the re-sending system can be implemented to include the following exemplary steps. For example, the props (including a game business name, a role ID, a prop ID, and a quantity of the props) that need to be re-sent can be recorded. A re-sending status value can be initialized. The props that need to be re-sent can be analyzed to process the business logic according to specific game business and props. For example, when certain game business sends game props, the game roles are not allowed to be online. A re-sending time can be selected according to one or more factors including game business type, whether the game currently stops working, and/or whether the current re-sending system is busy. Corresponding game props can be sent according to the recorded re-sending information. When the game props are successfully sent, the re-sending status value can be marked as success and removed from the re-sending queue. No re- sending is further performed. When the game props are not successfully sent, a number of times for re-sending can be checked whether a maximum value for re-sending is reached. When the number of times for re-sending does not reach the maximum value, the re-sending system can re-schedule a time for the re-sending. When the game props are not successfully sent and the number of times for re-sending has reached the maximum value for re-sending, the game developer can be informed and no re-sending can be performed for this specific record.

[0096] It should be understood that steps described in various methods of the present disclosure may be carried out in order as shown, or alternately, in a different order.

Therefore, the order of the steps illustrated should not be construed as

limiting the scope of the present disclosure. In addition, certain steps may be performed

simultaneously.

[0097] In the present disclosure each embodiment is progressively described, i.e., each embodiment is described and focused on difference between embodiments. Similar and/or the same portions between various embodiments can be referred to with each other. In addition, exemplary apparatus and/or systems are described with respect to corresponding methods.

[0098] The disclosed methods, apparatus, and/or systems can be implemented in a suitable computing environment. The disclosure can be described with reference to symbol(s) and step(s) performed by one or more computers, unless otherwise specified. Therefore, steps and/or implementations described herein can be described for one or more times and executed by computer(s). As used herein, the term "executed by computer(s)" includes an execution of a computer processing unit on electronic signals of data in a structured type. Such execution can convert data or maintain the data in a position in a memory system (or storage device) of the computer, which can be reconfigured to alter the execution of the computer as appreciated by those skilled in the art. The data structure maintained by the data includes a physical location in the memory, which has specific properties defined by the data format. However, the embodiments described herein are not limited. The steps and implementations described herein may be performed by hardware.

[0099] As used herein, the term "module" or "unit" can be software objects executed on a computing system. A variety of components described herein including elements, modules, units, engines, and services can be executed in the computing system. The methods, apparatus, and/or systems can be implemented in a software manner. Of course, the methods, apparatus, and/or systems can be implemented using hardware. All of which are within the scope of the present disclosure.

[00100] A person of ordinary skill in the art can understand that the units/modules included herein are described according to their functional logic, but are not limited to the above descriptions as long as the units/modules can implement corresponding functions. Further, the specific name of each functional module is used to be distinguished from one another without limiting the protection scope of the present disclosure.

[00101] In various embodiments, the disclosed units/modules can be configured in one apparatus (e.g., a processing unit) or configured in multiple apparatus as desired. The units/modules disclosed herein can be integrated in one unit/module or in multiple units/modules. Each of the units/modules disclosed herein can be divided into one or more sub- units/modules, which can be recombined in any manner. In addition, the units/modules can be directly or indirectly coupled or otherwise communicated with each other, e.g., by suitable interfaces.

[00102] One of ordinary skill in the art would appreciate that suitable software and/or hardware (e.g., a universal hardware platform) may be included and used in the disclosed methods, apparatus, and/or systems. For example, the disclosed embodiments can be implemented by hardware only, which alternatively can be implemented by software products only. The software products can be stored in computer-readable storage medium including, e.g., ROM/RAM, magnetic disk, optical disk, etc. The software products can include suitable commands to enable a terminal device (e.g., including a mobile phone, a personal computer, a server, or a network device, etc.) to implement the disclosed embodiments.

[00103] Note that, the term "comprising", "including" or any other variants thereof are intended to cover a non-exclusive inclusion, such that the process, method, article, or apparatus containing a number of elements also include not only those elements, but also other elements that are not expressly listed; or further include inherent elements of the process, method, article or apparatus. Without further restrictions, the statement "includes a " does not exclude other elements included in the process, method, article, or apparatus having those elements.

[00104] The embodiments disclosed herein are exemplary only. Other applications, advantages, alternations, modifications, or equivalents to the disclosed embodiments are obvious to those skilled in the art and are intended to be encompassed within the scope of the present disclosure.

INDUSTRIAL APPLICABILITY AND ADVANTAGEOUS EFFECTS

[00105] Without limiting the scope of any claim and/or the specification, examples of industrial applicability and certain advantageous effects of the disclosed embodiments are listed for illustrative purposes. Various alternations, modifications, or equivalents to the technical solutions of the disclosed embodiments can be obvious to those skilled in the art and can be included in this disclosure.

[00106] Methods and systems for requesting information are provided. The system includes a first server, a second server, and a third server. The first server receives a request message for obtaining information sent by a user. In response to the request message, the first server determines whether the user has a permission to obtain the information. After determining the user has the permission to obtain the information, the first server requests for acquiring the information from the second server. When the first server fails to request for acquiring the information from the second server, the first server requests for re-sending the information from the third server. When the first server succeeds in requesting for re-sending the information from the third server, the first server forwards the information received from the third server to the user.

[00107] As disclosed, a re-sending mechanism of the requested information can be used when the second server fails to issue the requested information. In one embodiment, to a certain extent, the information requested by the user can be returned to the user in a single response by the first server. Thus, conventional rollback operations performed after the issuing of the information fails can be avoided. Further, processes including that the user needs to resend the request for obtaining the information due to the failure of issuing information can be avoided. In addition, the re- authentication processes by the first server can be avoided to reduce workload of the first server and to reduce workload of the database corresponding to the rollback operations and the authentication operations. The disclosed methods and systems for requesting information thus solve the problems due to significant workload of the server and the significant pressure of writing and reading processes of the database caused by the rollback operations when issuing of the props fails as known in conventional methods for claiming game props.

REFERENCE SIGN LIST

Claims

1. An information requesting method, comprising:

receiving, by a first server, a request message for obtaining information sent by a user; in response to the request message, determining, by the first server, whether the user has a permission to obtain the information;

requesting, by the first server, for acquiring the information from a second server, when the user has the permission to obtain the information;

requesting, by the first server, for re-sending the information from a third server, when the first server fails to request for acquiring the information from the second server; and

forwarding, by the first server, the information received from the third server to the user, when the first server succeeds in requesting for re-sending the information from the third server.

2. The method according to claim 1, wherein the step of forwarding the information received from the third server to the user, when the first server succeeds in requesting for re-sending the information from the third server comprises:

acquiring, by the first server, the information sent by the third server on a first re-sending time set by the third server; and

forwarding, by the first server, the information received from the third server to the user.

3. The method according to claim 1 , wherein the step of requesting for re-sending the information from the third server comprises:

setting a first re-sending time by the third server and sending the information to the first server on the first re-sending time;

determining, by the third server, whether a current number of times for re-sending the information reaches a preset threshold value, when the third server fails to re-send the information to the first server on the first re-sending time; and

setting, by the third server, a second re-sending time and sending the information to the first server on the second re-sending time, when the third server determines that the current number of times for re-sending the information does not reach the preset threshold value.

4. The method according to claim 3, wherein the step of requesting for re-sending the information from the third server comprises:

when the third server determines that the current number of times for re-sending the information reaches the preset threshold value, stopping, by the third server, re-sending the information to the first server and sending an alarming message to a management device configured to manage the information.

5. The method according to claim 3, wherein the third server sets the first re -sending time and the second re-sending time according to at least one of: a business type corresponding to the information; whether the second server stops working; and a workload of the third server.

6. The method according to any claim of claims 1-5, wherein the information comprises information indicating props of a game program.

7. The method according to claim 6, wherein the information indicating the props of the game program comprises at least one of: a game business name, a role ID, a prop ID, and a quantity of the props.

8. An information requesting system, comprising:

a first server, a second server, and a third server, the first server including:

a receiving unit configured to receive a request message for obtaining information sent by a user,

a first determining unit configured, in response to the request message, to determine whether the user has a permission to obtain the information,

a first requesting unit configured to request for acquiring the information from the second server, when the user has the permission to obtain the information,

a second requesting unit configured to request for re-sending the information from the third server, when the first server fails to request for acquiring the information from the second server, and a forwarding unit configured to forward the information received from the third sever to the user, when the first server succeeds in requesting for re-sending the information from the third server.

9. The system according to claim 8, wherein the forwarding unit includes:

an acquiring module configured to acquire the information sent by the third server on a first re-sending time set by the third server when the first server succeeds in requesting for re-sending the information from the third server; and

a forwarding module configured to forward the information received from the third server to the user.

10. The system according to claim 8, wherein the third sever includes: a sending unit configured to set a first re-sending time and to send the information to the first server on the first re-sending time; and

a second determining unit configured to determine whether a current number of times for re- sending the information reaches a preset threshold value, when the sending unit of the third server fails to re-send the information to the first server on the first re-sending time,

wherein the sending unit is further configured to set a second re-sending time and send the information to the first server on the second re-sending time when the third server determines that the current number of times for re-sending information does not reach a preset threshold value.

11. The system according to claim 10, wherein the third server further includes:

an alarming unit configured to stop re-sending the information to the first server and to send an alarming message to a management device configured to manage the information when the second determining unit determines that the current number of times for re-sending the information reaches the preset threshold value.

12. The system according to claim 10, wherein the sending unit sets the first re-sending time and the second re-sending time according to at least one of: a business type corresponding to the information; whether the second server stops working; and a workload of the third server.

13. The system according to any claim of claims 8-12, wherein the information includes information indicating props of a game program.

14. The system according to claim 13, wherein the information indicating props of the game program includes at least one of: a game business name, a role ID, a prop ID, and a quantity of the props.