Request processing method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a request processing method and device, electronic equipment and a storage medium, and the method comprises the steps: receiving an interaction request initiated by a first account to a second account; obtaining summary information of the second account in response to the interaction request; if the summary information of the second account comprises the first mark, refusing the interaction request, and sending first prompt information to the first account; the first prompt information is used for prompting that the second account is in a logout retention period; within the logout retention period of the second account number, the second account number is in a state of allowing login; the first mark is added in summary information of the second account by the server in response to an account logout request for the second account; according to the method and the device, a rollback mechanism is ensured to exist in account logout, and invalid waiting in a process of interaction between the initiator and the account in the logout retention period can be avoided.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a request processing method, device, electronic device and storage medium. Background Art

[0002] In the related art, for deregistration of an account in an application, the server will deregister the account after receiving a deregistration request for the account, and then the account will be in a state where it cannot log into the application. If the user wants to log into the application again after requesting to deregister an account, the user needs to re-register the account in the application before logging in. In this way, the user has to perform more steps and it takes a long time. Summary of the invention

[0003] In view of the above problems, the embodiments of the present application propose a request processing method, device, electronic device and storage medium to solve the problem in the related art that after a user initiates an account cancellation request for an account, he needs to re-register the account before logging in.

[0004] According to one aspect of an embodiment of the present application, a request processing method is provided, characterized in that it is applied to a server, and includes: receiving an interaction request initiated by a first account to a second account; in response to the interaction request, obtaining summary information of the second account; if the summary information of the second account includes a first mark, rejecting the interaction request, and sending a first prompt information to the first account; the first prompt information is used to prompt that the second account is in a cancellation retention period; during the cancellation retention period of the second account, the second account is in a state of allowing login; the first mark is added by the server in the summary information of the second account in response to the account cancellation request for the second account.

[0005] According to one aspect of an embodiment of the present application, a request processing method is provided, which is applied to a client that logs in to a first account, including: in response to an interactive operation initiated to a second account, sending an interactive request for the second account to a server; receiving first prompt information returned by the server in response to the interactive request; the first prompt information is processed and returned by the server according to the above method; and the first prompt information is displayed.

[0006] According to one aspect of an embodiment of the present application, a request processing device is provided, characterized in that it is applied to a server and includes: a receiving module, used to receive an interaction request initiated by a first account to a second account; an acquisition module, used to obtain summary information of the second account in response to the interaction request; a processing module, used to reject the interaction request if the summary information of the second account includes a first mark, and send a first prompt message to the first account; the first prompt message is used to prompt that the second account is in a cancellation reservation period; during the cancellation reservation period of the second account, the second account is in a state of allowing login; the first mark is added by the server in the summary information of the second account in response to the account cancellation request for the second account.

[0007] In some embodiments, the request processing device further includes: an account cancellation request receiving module, used to receive an account cancellation request, wherein the account cancellation request is used to request cancellation of the second account; a first processing module, used to set the second account to enter a cancellation retention period according to the account cancellation request, and add the first mark to the summary information of the second account.

[0008] In some embodiments, the first processing module is configured to: according to the account cancellation request, set the second account to enter the cancellation retention period, and assign the first field in the summary information of the second account to the first time; the value of the first field after the assignment is used as the first mark, and the first time is the time when the account cancellation request is received; the cancellation retention period of the second account starts with the first time, and the duration of the cancellation retention period is the set duration.

[0009] In some embodiments, the request processing device also includes: a second processing module, which is used to delete the first mark in the summary information of the second account and release the cancellation retention period of the second account if it is detected that the second account is in a logged-in state before the end of the cancellation retention period; or, if a cancellation revocation request for the second account is received before the end of the cancellation retention period, delete the first mark in the summary information of the second account and release the cancellation retention period of the second account.

[0010] In some embodiments, the request processing device also includes: a third processing module, which is used to cancel the second account and add a second mark to the summary information of the second account if it is determined that the summary information of the second account still includes the first mark at the end time of the cancellation retention period of the second account; the second mark is used to indicate that the account has been cancelled.

[0011] In some embodiments, the request processing device further includes: an offline processing module, configured to offline the second account in response to the account deregistration request if the second account is in a logged-in state.

[0012] In some embodiments, the account cancellation request includes a third account and a first application identifier, the first application indicated by the first application identifier is an application to which the second account belongs; the third account is an account in the second application, and the first application and the second application are different applications; in this embodiment, the request processing device also includes: a second account determination module, which is used to determine the second account associated with the third account in the first application based on the association relationship between the account in the first application and the account in the second application according to the third account in the account cancellation request.

[0013] In some embodiments, the request processing device further includes: an association deletion module, configured to delete the association between the second account and the third account if it is determined that the summary information of the second account still includes the first mark at the end time of the cancellation retention period of the second account.

[0014] In some embodiments, the request processing device further includes: a second prompt information sending module, configured to send a second prompt information to the third account, wherein the second prompt information is used to prompt that the account associated with the third account in the first application has been cancelled.

[0015] According to one aspect of an embodiment of the present application, a request processing device is provided, which is applied to a client that logs in to a first account, and includes: a first sending module, which is used to send an interaction request for the second account to a server in response to an interaction operation initiated to the second account; a first receiving module, which is used to receive first prompt information returned by the server in response to the interaction request; the first prompt information is processed and returned by the server according to the above method; and a display module, which is used to display the first prompt information.

[0016] In some embodiments, the request processing device also includes: a second sending module, used to send a first summary request to the server, the first summary request is used to request to obtain summary information of each fourth account in the communication list of the first account; a second receiving module, used to receive the summary information of the fourth account returned by the server in response to the first summary request; a deletion module, used to delete the fourth account from the communication list of the first account if the summary information of the fourth account includes a second mark; the second mark is used to indicate that the account has been cancelled.

[0017] In some embodiments, the request processing device also includes: a third sending module, used to send a second summary request to the server, the second summary request is used to request to obtain summary information of each fifth account participating in the target historical game with the first account; a third receiving module, used to receive the summary information of the fifth account returned by the server; a logout mark display module, used to display a logout mark for the fifth account in the game record display interface if the summary information of the fifth account includes a second mark; the logout mark is used to prompt that the account has been logged out.

[0018] In some embodiments, the request processing device further includes: a third prompt information display module, configured to display a third prompt information in response to a detail access operation initiated on an account displaying a deregistration mark, wherein the third prompt information is used to prompt that the detail information of the deregistered account cannot be accessed.

[0019] According to one aspect of an embodiment of the present application, an electronic device is provided, including: a processor; a memory, wherein computer-readable instructions are stored in the memory, and when the computer-readable instructions are executed by the processor, the above request processing method is implemented.

[0020] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the above request processing method is implemented.

[0021] According to one aspect of an embodiment of the present application, a computer program product is provided, including computer instructions, which implement the above request processing method when executed by a processor.

[0022] In the present application, for the second account that requests to be deregistered, the second account is configured to first enter the deregistration retention period, during which the second account is in a state of being allowed to log in, and a first mark for identifying that it is in the deregistration retention period is added to the summary information of the second account, so that during the deregistration retention period of the second account, the second account can be selectively used as needed to ensure that there is room for fallback in account deregistration, and the situation that if you want to log in to the application again after submitting the account deregistration request can be avoided. In addition, after the server receives the interaction request initiated by the first account to the second account, the summary information of the second account is obtained in response to the interaction request, and when it is determined that the summary information of the second account includes the first mark, the interaction request is rejected, and the first prompt information is returned to the first account, so that the user can know that the second account is in the deregistration retention period based on the first prompt information. The server rejects the interaction request, which can avoid the situation where the initiator of the interaction request waits ineffectively because the second account does not log in during the deregistration retention period. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 It is a schematic diagram of an application scenario of the present application according to an embodiment of the present application.

[0025] Figure 2 It is a flowchart of a request processing method according to an embodiment of the present application.

[0026] Figure 3 It is a schematic diagram showing a first prompt message displayed in a display interface of a client according to an embodiment of the present application.

[0027] Figure 4 It is a schematic diagram of an account logout entry in a client of a game application according to an embodiment of the present application.

[0028] Figure 5 It is a schematic diagram of a logout interface of an account management platform according to an embodiment of the present application.

[0029] Figure 6 It is a timing diagram of the deregistration process of the second account according to an embodiment of the present application.

[0030] Figure 7 yes Figure 6 The processing flow chart of canceling the retention period in the corresponding embodiment.

[0031] Figure 8 yes Figure 6 The processing flow chart of the formal cancellation stage in the corresponding embodiment.

[0032] Fig. 9 It is a timing diagram of a request processing method according to another embodiment of the present application.

[0033] Fig.10 It is a schematic diagram showing the display of a communication list according to an embodiment of the present application.

[0034] Fig.11 It is a schematic diagram of a game record display interface according to an embodiment of the present application.

[0035] Fig.12 It is a block diagram of a request processing device according to an embodiment of the present application.

[0036] Fig.13It is a block diagram of a request processing device according to another embodiment of the present application.

[0037] Fig.14 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0038] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0039] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0040] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0041] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0042] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0043] Figure 1 is a schematic diagram of an application scenario of the present application according to an embodiment of the present application, such as Figure 1 As shown, the application scenario includes at least one terminal and a server 120, Figure 1111 and the second terminal 112 are exemplarily shown, and each terminal is connected to the server 120 via a wired or wireless network. The terminal can be a smart phone, a tablet computer, a laptop, a desktop computer, a smart TV, a car terminal, or other interactive devices. The server 120 can be a physical server or a cloud server, which is not specifically limited here.

[0044] The terminal can run the client program of the application, and as the carrier of the client of the application, the application can be a game application, an instant messaging application, a live broadcast application, a payment application, a video application, etc. The server 120 can provide services for the applications running on the terminal. Assume that the account logged in on the client running on the first terminal 111 is the first account, and the account logged in on the client running on the second terminal 112 is the second account.

[0045] The logged-in first account in the client running on the first terminal 111 can initiate an interaction request to other accounts (such as a second account), for example, based on the interactive controls in the display interface of the client, the interaction request is sent to the server, so that the server processes it according to the method provided in this application.

[0046] Taking the terminal running a game application as an example, the terminal can display a game interface, and the game interface can provide game interactive controls, such as gift controls, game invitation controls, etc. Figure 1 exemplarily shows a schematic diagram of a gift giving interface 113 displayed on the first terminal 111, and the gift giving interface 113 includes a gift control 114. After the user selects the second account to be interacted with and the gift to be given (the gift may be a prop, an electronic voucher, etc.) in the display interface of the client running on the first terminal 111, the first terminal 111 may send an interaction request (gift giving request) to the second account in response to a trigger operation on the gift control 114, and the interaction request is first routed to the server 120; after receiving the interaction request, the server 120 obtains summary information of the second account in response to the interaction request, and if the summary information of the second account includes a first mark, rejects the interaction request and sends a first prompt information to the first account, and the first prompt information is used to prompt that the second account is in a cancellation cooling-off period; the gift giving interface 113 of the first terminal 111 may display the first prompt information accordingly.

[0047] In some embodiments, the server 120 may receive an account cancellation request initiated for an account. For example, the second terminal 112 may send an account cancellation request for the second account to the server 120. Afterwards, the server 120 may respond to the account cancellation request, set the second account to enter a cancellation retention period, and add a first mark to the summary information of the second account; if at the end time of the cancellation retention period of the second account, it is determined that the summary information of the second account still includes the first mark, the second account is cancelled; further, a second mark may be added to the summary information of the second account, and the second mark is used to indicate that the account has been cancelled.

[0048] The implementation details of the technical solution of the embodiment of the present application are described in detail below:

[0049] Figure 2 This is a flowchart of a request processing method according to an embodiment of the present application. The method can be executed by a server, which can include one or more physical servers. If the server includes multiple physical servers, the method provided by the present application can be implemented by the interaction of multiple physical servers in the server. The server can also be a cloud server, which is not specifically limited here. Figure 2 As shown, the method at least includes steps 210 to 230, which are described in detail as follows:

[0050] Step 210: receiving an interaction request initiated by the first account to the second account.

[0051] The first account refers to the account of the initiator of the interaction request, and the second account refers to the account of the recipient of the interaction request. The applications to which the first account and the second account belong may be instant messaging applications, game applications, video applications, live broadcast applications, shopping applications, payment applications, and other applications that provide interaction functions between different accounts, which are not specifically limited here.

[0052] The interaction request is used to request interaction with the second account. The interaction request can be a message sending request, a voice call request, a video call request, a transfer request, a virtual resource interaction request (such as a gift giving request, etc.), a game invitation request, a group invitation request, etc., which are not specifically limited here.

[0053] Step 220: In response to the interaction request, obtain summary information of the second account.

[0054] The account summary information, also known as the account brief information, refers to the information required to display the account in the display interface. The account summary information may include the nickname and avatar corresponding to the account. In different applications, the account summary information may include different information other than the nickname and avatar. For example, in a game application, the account summary information may also include the rank, level, and number of diamonds corresponding to the account; in an enterprise-level instant messaging application, the account summary information may also include the enterprise and department to which the user corresponding to the account belongs.

[0055] In some embodiments, a database may be deployed in the server to store summary information of each account. Correspondingly, the server responds to the interaction request and obtains summary information of the second account from the first database based on the second account carried in the interaction request.

[0056] The server acts as an intermediary for communication between different clients. The interaction request initiated by the first account to the second account is first routed to the server, and then the interaction request is sent to the client where the second account is located through the server. In this application, after receiving the interaction request, the server determines whether it is necessary to send the interaction request to the client corresponding to the second account based on the summary information of the second account. That is, if the summary information of the second account includes the first mark, the interaction request is rejected and the first prompt information is sent to the second account.

[0057] Step 230: If the summary information of the second account includes the first mark, the interaction request is rejected, and a first prompt message is sent to the first account; the first prompt message is used to prompt that the second account is in a cancellation retention period; during the cancellation retention period of the second account, the second account is in a state of allowing login; the first mark is added by the server in the summary information of the second account in response to the account cancellation request for the second account.

[0058] In this application, after receiving a cancellation request for an account, the server does not directly cancel the account, but first puts the account into a cancellation retention period, and adds a first mark indicating that it is in the cancellation retention period in the summary information of the account, and the account in the cancellation retention period is in a state of allowing login. It can be understood that during the cancellation retention period of the account, the application-related data of the account in the server is retained.

[0059] For an account requested to be cancelled, if the account cancellation request is not revoked before the end of the cancellation retention period of the account, or the account has not been logged in during the cancellation retention period of the account, the account will be cancelled after the cancellation retention period of the account ends, and the account will be in a state where it cannot be logged in after cancellation.

[0060] It is understandable that since the account in the cancellation retention period is in a state where login is allowed, and other registered accounts that have not submitted cancellation applications are also in a state where login is allowed, the first mark in the summary information can be used to distinguish and identify the account in the cancellation cooling-off period.

[0061] In some embodiments, a first field may be set in the summary information of an account, and different marks may be indicated by the value of the first field. For example, the value of the first field is set to 1 as the first mark. If the value of the first field in the summary information of the second account is 1, it is determined that the summary information of the second account includes the first mark. It is understandable that the value of the first field in the summary information of the account is different for an account in the cancellation retention period and an account that has not requested cancellation. For example, the value of the first field may be set to 0 to indicate that the account is an account that has not requested cancellation. If the value of the first field is a value other than 0, it is used as the first mark to indicate that the account is in the cancellation retention period; or, the value of the first field is 1 as the first mark. Of course, in other embodiments, the value of the first field is not limited to identifying an account in the cancellation retention period and an account that has not requested cancellation, and may also be used to distinguish other accounts, for example, it may also be used to identify a cancelled account.

[0062] For the account requested to be deregistered, the operation object corresponding to the account (the user corresponding to the account) may not log in to the account again subsequently. Therefore, in this application, in order to avoid the user waiting in vain for the interaction response when interacting with the account requested to be deregistered, the server rejects the interaction request when it is determined that the summary information of the second account includes the first mark, and sends a first prompt message to the initiator of the interaction request (i.e., the first account), so that the initiator of the interaction request knows that the second account has applied for account deregistration.

[0063] In addition, if the interaction request initiated by the first account to the second account involves a request for resources (virtual resources or money), such as an interaction request to give a gift (such as props, energy, goods, etc. in the game), if the second account that has requested to be deregistered does not log in to the account after the deregistration request, it will not only cause invalid operations for the user on the first account side, but also cause resource loss for the user on the first account side.

[0064] The server rejects the interaction request. On the one hand, it means that the server does not forward the interaction request to the client where the second account is located. On the other hand, if the interaction request involves resource transactions (such as gifting props, etc.), the server will not process the resource transactions involved in the interaction request, making the resource transactions corresponding to the current interaction request invalid.

[0065] The server sends the first prompt information to the first account, so that the user of the first account can know the status of the second account in time, and the client of the first account can also display the first prompt information.

[0066] Figure 3 is a schematic diagram showing a first prompt message displayed in a display interface of a client according to an embodiment of the present application. Figure 3 In the example, the account corresponding to the user with the nickname "AABB" is the first account, and the account corresponding to the user with the nickname "QAAQ" is the second account. When the first account initiates an interactive request to send a gift to the second account (for example, by triggering the gift control 114 to send an interactive request to send a gift to the server), if the server determines that the summary information of the second account includes the first mark, it sends the first prompt information to the client corresponding to the first account, and the first prompt information 310 is correspondingly displayed in the interface of the client where the first account is located. Figure 3 The first prompt message 310 is specifically "the other party's account is in the cancellation retention period and cannot receive your gift for the time being."

[0067] In some embodiments, in order to ensure that the user on the first account side knows the response status to the interaction request initiated to the second account, the first prompt information can also be used to prompt that the interaction request has been rejected.

[0068] In the present application, for the second account requested to be deregistered, the second account is configured to enter the deregistration retention period first, and the second account is in a state of being allowed to log in during the deregistration retention period, and a first mark for identifying that it is in the deregistration retention period is added to the summary information of the second account, so as to ensure that there is room for rollback of the account deregistration, that is, to avoid the situation where the user needs to re-register to log in to the account again after submitting the account deregistration request. On this basis, after the server receives the interaction request initiated by the first account to the second account, the summary information of the second account is obtained in response to the interaction request, and when it is determined that the summary information of the second account includes the first mark, the interaction request is rejected, and the first prompt information is returned to the first account, so that the user can know that the second account is in the deregistration retention period based on the first prompt information. Moreover, the server rejects the interaction request, which can avoid the situation where the initiator of the interaction request waits in vain because the second account does not log in during the deregistration retention period.

[0069] In addition, in order to ensure that the displayed content of the second account requesting interaction in the client is consistent with the content in the summary information of the second account, the server responds to the interaction request and obtains the summary information of the second account, which is also convenient for sending the summary information of the second account to the first account later, so that the client of the first account can display the content related to the second account according to the summary information of the second account. In this way, in the present application, the first mark is added to the summary information of the account, not only in the interaction process, it is judged whether the interaction request is processed normally based on the summary information of the account, but also the summary information of the account obtained in response to the interaction request can be sent to the initiator of the interaction request to update the displayed content. If the first mark is added to other data related to the account, if the server wants to send the summary information of the second account to the first account, and obtain the first mark for the second account, the server needs to read multiple data, and adopts the solution of the present application, the server does not need to read multiple data, and only needs to read the summary data of the account, which can reduce the data reading pressure of the server.

[0070] In some embodiments, after step 220, the method further includes: sending summary information of the second account to the first account, so that the client where the first account is located updates the display content for the second account according to the summary information of the second account.

[0071] In some embodiments, the server may package the summary information of the second account and the first prompt information, and send them to the first account at one time.

[0072] For example, if the avatar or nickname of the second account is changed, the display content of the first account's client for the second account can be updated based on the latest summary information of the second account, so as to ensure that the display content of the first account's client for the second account is consistent with the content in the latest summary information of the second account. In this way, when an interaction request is initiated to an account, the display content of the second account in the first account's client is updated according to the summary information of the second account.

[0073] In other embodiments, based on the summary information of the second account, the server may send the summary information of the second account to the first account even if it is determined that the interaction request needs to be processed normally.

[0074] In some embodiments, after step 220, the method further includes: if the summary information of the second account does not include the first tag, processing the interaction request according to the normal processing logic corresponding to the interaction request, and forwarding the interaction request to the second account.

[0075] In some embodiments, the server may process different types of interaction requests differently. Specifically, step 230 includes: if the summary information of the second account includes a first tag, and the interaction type to which the interaction request belongs is a resource interaction type, rejecting the interaction request and sending a first prompt message to the first account.

[0076] Among them, resource interaction type refers to the interaction type involving resource transactions. Interaction requests belonging to the resource interaction type include resource donation requests (resources that can be donated include virtual resources such as game props, points, electronic coupons, etc.), transfer requests, red envelope sending requests, etc.

[0077] Since the interactive request belonging to the resource interaction type involves resource transactions, if the second account is not logged in during the cancellation retention period, it may cause resource loss on the side of the first account as the initiator of the interactive request. Therefore, in this case, if the summary information of the second account includes the first tag, and the interactive type to which the interactive request belongs is the resource interaction type, rejecting the interactive request can avoid resource loss on the side of the first account as the initiator of the interactive request.

[0078] In some embodiments, if the interaction type to which the interaction request belongs is not a resource interaction type, the server may forward the interaction request to the second account after processing the normal processing logic corresponding to the interaction request. Examples of interaction requests that do not belong to the resource interaction type include game invitation requests, group entry request requests, voice call requests, video call requests, and the like. In the case where the summary information of the second account includes the first tag, if the interaction type to which the interaction request belongs is not a resource interaction type, the interaction request is forwarded to the second account, so that if the user on the second account side logs in to the second account during the cancellation retention period, the user on the second account side can process the interaction request.

[0079] In some embodiments, before step 210, the method further includes the following steps A1 and A2, which are described in detail as follows: Step A1, receiving an account cancellation request, where the account cancellation request is used to request cancellation of the second account.

[0080] In some embodiments, the account cancellation request may be initiated by the client where the second account is located, and correspondingly, the account cancellation request includes the second account. An account cancellation entry may be provided in the display interface of the client, so that the user can initiate an account cancellation request to the server by triggering the account cancellation entry. Figure 4 is a schematic diagram of an account logout entry in a client of a game application according to an embodiment of the present application. Figure 4In the example, the “game account logout” control 410 in the setting page of the game application is the account logout entry. The client of the game application can send an account logout request to the game server in response to the triggering operation of the “game account logout” control 410.

[0081] In some embodiments, in order to facilitate unified management of account cancellation, the account cancellation request may be initiated through a unified account management platform instead of directly initiating the account cancellation from the client where the second account is located. In this case, the account management platform may be jumped from the client interface where the second account is located, wherein the client where the second account is located may send the third account associated with the second account in the second application and the first application identifier of the first application to which the second account belongs to the account management platform, and then the account management platform may send the account cancellation request to the server based on the third account and the first application identifier of the first application.

[0082] In this case, the corresponding account cancellation request includes the third account and the first application identifier, the first application indicated by the first application identifier is the application to which the first account belongs; the third account is an account in the second application, and the first application and the second application are different applications; after step A1, the method further includes: based on the association relationship between the account in the first application and the account in the second application, according to the third account in the account cancellation request, determining the second account in the first application that is associated with the third account. Since the client where the second account is located does not transmit the second account to the account management platform, the server needs to determine the second account based on the third account and the first application identifier in the account cancellation request.

[0083] In some embodiments, when an application is published on platforms with different operating systems (such as Android system, IOS system, etc.), and the user has registered accounts on platforms with different operating systems for the same application, if the user needs to cancel the account in the application on platforms with multiple operating systems, if the account cancellation request is initiated by the client of the application, the account cancellation request needs to be initiated on the clients corresponding to the platforms with different operating systems respectively. If the method of this embodiment is adopted, the account cancellation request is initiated by the account management platform as the intermediary of the account cancellation, and the first application identifier and the third account that may be associated with multiple applications on platforms with different operating systems are transmitted to the account management platform, so that the server can query all accounts associated with the third account in the first application based on the first application identifier and the third account. The account associated with the third account in the first application that is queried can all be used as the second account in this application. If there are multiple accounts associated with the third account in the first application, the multiple accounts can be processed according to the method provided in this application, without the user initiating an account cancellation request for each account separately, thereby shortening the time used to cancel multiple accounts on platforms with different operating systems in the same application and reducing user operations.

[0084] For example, if the user triggers Figure 4 In the "Game Account Logout" control 410, you can jump to Figure 5 The deregistration interface 510 of the account management platform shown in Figure A in the figure can display the deregistration agreement and register information, such as the user's real name information. Figure 5 In the "Start Logout" control 511 shown in Figure A, the account management platform sends an account logout request to the server. In the logout interface 510, the application to which the account to be logged out belongs and the application to which the third account associated with the account in the application belongs are displayed. Figure 5 In the cancellation agreement shown in Figure A, "XX Game" is the game application (i.e., the first application) requesting account cancellation. Figure 4 The game interface shown jumps to Figure 5 The interface shown in Figure A is "XX Game" Figure 4 The game application to which the game client belongs is the "A application" in the logout interface 510. Figure 4 The application to which the third account associated with the account logged in by the corresponding game client (eg, the second account) belongs may be an instant messaging application or a payment application, etc., which is not specifically limited here.

[0085] Step A2: according to the account cancellation request, setting the second account to enter the cancellation retention period, and adding a first mark to the summary information of the second account.

[0086] Among them, the start time of the cancellation retention period of the second account can be the time when the account cancellation request is received, and the duration of the cancellation retention period can be a preset duration, which can be set according to actual needs, for example, the preset duration is 5 days, 7 days, 10 days, 15 days, etc.

[0087] In the case where different marks are indicated by the value of the first field, in step A2, the second field in the summary information of the second account is assigned a value representing the first mark, thereby adding the first mark to the summary information of the second account.

[0088] In some embodiments, step A2 includes: according to the account cancellation request, setting the second account to enter the cancellation retention period, and assigning the first field in the summary information of the second account to the first time; the value of the first field after assignment is used as the first mark, and the first time is the time when the account cancellation request is received; the cancellation retention period of the second account starts with the first time, and the duration of the cancellation retention period is the set duration.

[0089] In the above embodiment, the value of the first field can be set to 0, indicating that no account cancellation request has been initiated for the account; conversely, if the value of the first field is another value, the value of the first field is regarded as the first mark. In the above embodiment, in response to the account cancellation request, the first field in the summary information of the second account is assigned the first time, which is convenient for identifying that the second account is in the cancellation retention period based on the value of the first field after the assignment, and is convenient for determining whether the end time of the cancellation retention period of the second account has been reached based on the value of the first field after the assignment and the duration set for the cancellation retention period.

[0090] In some embodiments, after step A2, the server returns a response message to the initiator of the account cancellation request. The response message can be used to prompt that the current account has entered the cancellation retention period. Furthermore, the response message can also prompt the time period of the cancellation retention period corresponding to the current account.

[0091] Figure 5 FIG. B in FIG. 1 shows an exemplary schematic diagram of displaying response information in the logout interface, where the response information indicates that the application for logout of the game account has been successfully submitted, and indicates the end time of the logout retention period of the account. Of course, if the account logout request is initiated through the client where the second account is located, the response information is correspondingly displayed in the interface of the client where the second account is located.

[0092] In some embodiments, in order to facilitate immediate cancellation of the second account when the cancellation retention period of the second account ends, step A2 includes: setting the second account to enter the cancellation retention period according to the account cancellation request, adding a first mark to the summary information of the second account, and creating a cancellation scheduled task for the end time of the cancellation retention period of the second account.

[0093] Among them, the logout scheduled task created for the end time of the logout retention period of the second account is triggered at the end time of the logout retention period of the second account. The logout scheduled task is used to automatically log out the second account when the end time of the logout retention period of the second account is reached.

[0094] In some embodiments, after step A2, the method further includes: if it is detected that the second account is in a logged-in state before the end of the logout retention period, deleting the first mark in the summary information of the second account, and releasing the logout retention period of the second account; or, if a logout cancellation request for the second account is received before the end of the logout retention period, deleting the first mark in the summary information of the second account, and releasing the logout retention period of the second account.

[0095] In other words, if the user logs into the second account before the cancellation retention period of the second account ends, or the server receives a cancellation request initiated for the second account, it is deemed as a request to cancel the account cancellation request for the second account. Correspondingly, the server deletes the first mark in the summary information of the second account, cancels the cancellation retention period of the second account, and updates the summary information of the second account after deleting the first mark to the database.

[0096] The cancellation request for the second account may be initiated by the client of the second account, or by the client of an account in another application associated with the second account (such as the third account hereinafter). For example, in the case where the account cancellation request for the second account includes the third account, after the server enters the cancellation retention period, it sends the processing result of the second account entering the cancellation retention period to the third account; an entry for canceling the cancellation request may be provided in the detailed display interface of the processing result, so that the user can send a cancellation request for the second account to the server based on the entry for canceling the cancellation request.

[0097] When different values ​​of the first field in the summary information of the account represent different marks, deleting the first mark in the summary information of the second account may be to change the value of the first field to a value corresponding to the mark indicating that account cancellation is not requested.

[0098] When the first field in the summary information of the account is assigned the first time and the value of the first field after the assignment is used as the first mark, the first field is reassigned accordingly, for example, the first field is reassigned to 0. In this case, since the cancellation retention period of the second account starts at the first time, reassigning the first field to 0 can be regarded as releasing the cancellation retention period of the second account.

[0099] It is understandable that after deleting the first mark in the summary information of the second account and releasing the cancellation retention period of the second account, there is no need to cancel the second account according to the cancellation process. Since the second account in the server is still in the login allowed state, the second account can log in normally subsequently.

[0100] In some embodiments, if a logout scheduled task is created for the end time of the logout retention period of the second account, if the second account is detected to be logged in before the end of the logout retention period, or if a logout cancellation request for the second account is received before the end of the logout retention period, the logout scheduled task is deleted accordingly.

[0101] In the above embodiment, since a cancellation retention period is set during the cancellation phase, the account is cancelled after the cancellation retention period ends, rather than directly responding to the account cancellation request to cancel the account. This provides room for fallback in the account cancellation process. In this way, if the user logs into the account during the cancellation retention period or initiates a cancellation request, the cancellation retention period of the account is canceled, so that the account can be logged in normally later without the need to re-register.

[0102] In some embodiments, after step A1, the method further includes: if the second account is in a logged-in state, in response to an account deregistration request, taking the second account offline. That is, in response to the account deregistration request, the second account is forcibly taken offline to avoid misidentification that the second account needs to request cancellation of the account deregistration request because the second account is in a logged-in state.

[0103] In some embodiments, after step A2, the method further includes: if at the end time of the cancellation retention period of the second account, it is determined that the summary information of the second account still includes the first mark, canceling the second account and adding a second mark to the summary information of the second account; the second mark is used to indicate that the account has been cancelled.

[0104] It is understandable that if, at the end time of the cancellation retention period of the second account, the summary information of the second account still includes the first mark, it indicates that no request to revoke the account cancellation request for the second account has been made during the cancellation retention period of the second account. Therefore, in this case, the second account is cancelled accordingly, and the second mark is added to the summary information of the second account to indicate that the second account has been cancelled.

[0105] The server is provided with a deregistration processing logic, which indicates the processing required for deregistering an account, so that the server can deregister the second account according to the deregistration processing logic. It is understandable that after deregistering the second account, the second account is in a state where it cannot be logged in. The deregistration processing logic at least includes a processing logic for deleting an account from a set of accounts that are allowed to log in, and the set of accounts that are allowed to log in refers to a set of accounts that are in a state where they are allowed to log in.

[0106] In some embodiments, the logout processing logic may also include processing logic for application-related data of the account that needs to be logged out in the server. In this case, the server will delete the application-related data of the second account in the application. The application-related data may include UGC (User Generated Content) data in the game, user game performance data, access to other people's record data, etc. In different applications, the application-related data may correspond to different ones.

[0107] It is worth mentioning that in the present application, in the process of canceling the second account, it is not necessary to delete the summary information of the second account. In addition, a second mark indicating that the account has been cancelled is added to the summary information of the second account. The summary information with the second mark added can be used for subsequent processing of the account.

[0108] In some embodiments, when different states of an account are represented by different values ​​of the first field, the optional values ​​of the first field include at least a value representing the first mark, a value identifying the second mark, and a value representing other states except the cancellation retention period and the cancelled state. For example, if the value of the first field is set to 0 to represent the first mark (i.e., in the cancellation retention period), the value of the first field is 1 to represent the second mark (i.e., cancelled), and the value of the first field is 2 to represent other states except the cancellation retention period and the cancelled state; in this case, adding the second mark to the summary information of the second account means reassigning the first field in the second summary information to a value representing the second mark, for example, reassigning the first field to 1, and the value of the first field after the reassignment corresponds to the second mark.

[0109] In some embodiments, a second field may be further set in the summary information, and the value of the second field is used to identify whether the account has been cancelled. For example, setting the value of the second field to 0 indicates that the account has been cancelled, and setting the value of the second field to 1 indicates that the account has not been cancelled. In this case, adding a second mark to the summary information of the second account means assigning a value indicating that the second field in the summary information of the second account is a value indicating that the account has been cancelled, such as a value of 1.

[0110] In some embodiments, when the value of the first field is used to indicate whether the account is in the cancellation retention period, and the value of the second field is used to indicate whether the account is cancelled, the first field and the second field are different fields. In this case, after the second account is cancelled, the first mark in the summary information of the second account can also be deleted, and the second mark can be added to the summary information of the second account. In this way, after the second account is cancelled, the first mark is still retained in the summary information of the second account, which avoids misjudging the status of the second account.

[0111] In some embodiments, if the cancellation request for the second account is initiated by a third account associated with the second account, after step A2, the method further includes: if at the end time of the cancellation retention period of the second account, it is determined that the summary information of the second account still includes the first mark, deleting the association between the second account and the third account.

[0112] By deleting the mapping relationship between the second account and the third account, it is ensured that the second account cannot be logged in to the first application (ie, the application to which the second account belongs) through the third account in the future.

[0113] In some embodiments, if the deregistration request for the second account is initiated by a third account associated with the second account, after deleting the association between the second account and the third account, the method further includes: sending a second prompt message to the third account, the second prompt message being used to prompt that the account associated with the third account in the first application has been deregistered. In this way, the user can know that the second account associated with the third account has been deregistered based on the second prompt message received by the client where the third account is located.

[0114] If it is set that if the account logs into the application before the end of the cancellation retention period, it is regarded as a cancellation of the account cancellation request. Since the second account has not logged into the application during the cancellation retention period, after the second account is cancelled, the user on the second account side is unaware that the second account has been cancelled. In this case, the second prompt information is sent to the third account, so that the user can promptly know that the account associated with the third account in the first application (i.e., the second account) has been cancelled.

[0115] The cancellation process of the second account is now described in detail with reference to a specific embodiment.

[0116] Figure 6This is a sequence diagram of the deregistration process of the second account according to an embodiment of the present application. In this embodiment, the first application to which the second account belongs is a game application. The deregistration process can be implemented by the interaction between the account management platform and the game server, wherein the game server includes an interface platform, a parsing server and a login server, and the game server deploys a database, which can be used to store summary information of each account in the game application, game-related data of each account, and the mapping relationship between the account in the game application and the account in the second application.

[0117] The database includes a summary data table (for example, the summary data table may be RoleSimpleDataDB), an account-related data table (for example, rolekeyDB), and an in-game data table (for example, roleInDB); wherein the summary data table is used to store summary information of each account in the game application; the account-related data table is used to store the association relationship between the account in the game application and the account in the second application; and the in-game data table is used to store relevant data of each account in the game application.

[0118] Among them, the interface platform serves as a data interface bridge between the external platform (such as the account management platform) and the parsing server. Based on the interface platform, operations such as adding, deleting, modifying, and checking game data (such as props, experience, muting, etc.) can be realized.

[0119] The parsing server is used to parse and process requests from the interface platform. External platform requests and operations on data within the game application need to be processed by the parsing server.

[0120] The login server is used to provide user (player) login functions, lobby services, and main business logic based on game characters. The login server can provide services in a clustered manner. After the player logs in, the player's key data is cached on the login server and written back to the database at regular intervals. Most of the game client's requests are processed directly on the login server, and other requests can be processed by other game servers in the game server. Different servers in the game server can interact with each other according to the agreed SS (server to server) messages.

[0121] like Figure 6 As shown, specifically including:

[0122] Step 610, cancellation reservation request. That is, after the player initiates an account cancellation request based on the client of the account management platform, the server of the account management platform first sends a cancellation reservation period request to the resolution server in the game server, and the cancellation reservation period request is forwarded to the resolution server through the interface platform, so that the account first enters the account cancellation reservation period.

[0123] Step 621, update the summary information of the second account; and perform offline processing on the second account. If the second account is in a logged-in state, the logout reservation request will be sent to the login server via the resolution server, and then the login server will execute step 621. Updating the summary information of the second account means adding a first mark to the summary information of the second account.

[0124] Step 622, update the summary information of the second account. If the second account is in the login state, after the login server executes step 621, the resolution server executes step 622 in response to the response returned by the login server. If the second account is in the offline state, the cancellation reservation request will not be sent to the login server, and the resolution server executes step 622 after receiving the cancellation reservation request; in this way, it can be ensured that the summary information of the second account is updated whether the second account is online or not.

[0125] Step 630, formal cancellation request. The game server will record the initiation time of the account cancellation request. If the game application is not logged in within the set time from the initiation time of the account cancellation request, the account management platform sends a formal cancellation request to the game server, that is, after the cancellation retention period of the second account ends, the formal cancellation request is sent to the game server to cancel the second account.

[0126] Step 640, delete the association between the second account and the third account; update the game-related data of the second account; and update the summary information of the second account.

[0127] Next, combine Figure 7 and Figure 8 The processing procedures of the two stages of cancellation retention period and formal cancellation are explained. Figure 7 The flowchart of the cancellation retention period is shown. Figure 7 As shown, after receiving the cancellation retention period request, the resolution server performs the following steps: Step 710, querying the account association data table; the parameters transmitted by the cancellation retention period request (and the account cancellation request sent by the client of the account management platform) include the third account (open ID, which can be an account associated with the player in the instant messaging application), thereby, the resolution server can query the account associated with the third account in the account association data table based on the third account, and the resolution server can query the account associated with the third account of the game application on multiple operating system platforms based on the account association data table corresponding to each operating system platform, for example, querying the account associated with the third account of the game application on the Android platform in the account association data table corresponding to the Android platform and querying the account associated with the third account of the game application on the IOS platform in the account association data table corresponding to the IOS platform.

[0128] Step 720, determine whether an account associated with the third account is found. If no account associated with the third account is found, it may be that the requested third account is incorrect, and the query result is directly returned to the account management platform; if an account associated with the third account is found, the account associated with the third account is used as the second account to be cancelled in this application. Of course, if multiple accounts associated with the third account are found, each account is processed according to the following process.

[0129] When an account associated with the third account is found, the login server executes step 730 to determine whether the second account is online; if it is online, the login server executes steps 740 and 750; if it is not online, the information that the second account is offline is returned to the resolution server, and then the resolution server executes steps 760-780.

[0130] Step 740: The login server updates the first field in the summary information of the second account, where the first field may be the AccountCancelTime field, and the login server may assign the AccountCancelTime field in the summary information of the second account to the current time (the current time is regarded as the time when the account cancellation request is received).

[0131] Step 750: The login server logs off the second account. After the first field in the summary information of the second account is assigned a value, the summary information of the second account is written into the summary data table (eg, RoleSimpleDataDB) and the in-game data table (eg, roleInDB) along with the player's data.

[0132] Step 760: The resolution server queries summary information of the second account.

[0133] Step 770: The resolution server updates the first field in the summary information of the second account. The resolution server queries the summary information of the second account from the summary data table, and assigns the AccountCancelTime field therein to the current time. In this way, the AccountCancelTime field of the summary information of the second account in the summary data table is updated regardless of whether the second account is online or not.

[0134] according to Figure 7 After the process shown updates the summary information of the second account in the summary data table, the result of successful application for cancellation of the retention period is returned to the account management platform. At this point, the processing logic of the cancellation of the retention period ends.

[0135] Figure 8The process flow chart of formal cancellation is shown. The account management platform can query the summary data of the account in the cancellation retention period according to the preset cycle. If the end time of the cancellation retention period is determined based on the value of the AccountCancelTime field in the summary data and the preset duration (i.e. the duration of the cancellation retention period), the account management platform sends a formal cancellation request to the game server through the interface platform. Figure 8 As shown, after receiving the formal deregistration request, the resolution server performs the following steps:

[0136] Step 810: query the account association data table. Step 820: determine whether an account associated with the third account is found. Figure 7 Similar to step 710 and step 720, the parsing server uses the transmitted third account to query the account association data table. The specific implementation process is described above and will not be repeated here. If no account associated with the third account is found, the query result is directly returned to the account management platform; if an account associated with the third account is found, the process is processed according to the following steps 830-880.

[0137] Step 830: Log in to the server to query the summary data table.

[0138] In step 840, the login server determines whether the first field is 0. The login server queries the summary data table to read the summary data of the second account from the summary data table, and then determines whether the value of the first field in the summary data of the second account is 0. If the value of the first field in the summary data of the second account is not 0 (for example, it is assigned to the first time), it is determined that the second account is in the cancellation cooling-off period, and then steps 850-880 are executed accordingly; if the value of the first field is 0, it indicates that the second account has not entered the cancellation retention period, and the second account should not be cancelled, and a response result is returned to the account management platform accordingly.

[0139] Step 850: The login server updates the value of the second field. The second field may be a CancelFlag field, and specifically, the value of the second field in the summary data of the second account is set to 1, and the updated summary data of the second account is written into the database.

[0140] Step 860, log in to the server to query the in-game data table.

[0141] Step 870: The login server updates the value of the second field.

[0142] In this embodiment, the game-related data of the account in the in-game data table also includes a second field. The login server queries the in-game data table to update the value of the second field in the game-related data of the second account, so that the values ​​of the second field corresponding to the second account in the in-game data table and the summary data table are the same; then the updated game-related data of the second account is written into the database accordingly.

[0143] Step 880: Login to the server and delete the mapping relationship between the second account and the third account.

[0144] The login server deletes the mapping relationship between the second account and the third account in the account association data table. In this way, if the user subsequently logs in to the first application through the third account, the game server determines that there is no account associated with the third account in the account association data table, and accordingly prompts the user that the login is not possible, and prompts the user whether to register an account. After step 880, the result of successful logout is returned to the account management platform, and the formal account logout process is completed.

[0145] In the above embodiment, based on the account cancellation request for the second account, the account is processed in stages, that is, it is first processed according to the processing logic corresponding to the cancellation retention period, and then the account is cancelled after the cancellation retention period ends, which not only ensures that there is room for fallback for the second account that requests cancellation during the account cancellation retention period, but also ensures that the account can be cancelled. Moreover, based on adding corresponding marks to the summary information of the account at different stages (cancellation retention period stage and formal cancellation stage), different processing can be performed for interactive requests to accounts in the cancellation retention period and for accounts that have been cancelled, ensuring that the cancelled account cannot be accessed, and rejecting interactive requests for accounts in the cancellation retention period, which can avoid the loss of users' virtual resources and improve user experience.

[0146] Fig. 9 is a timing diagram of a request processing method according to another embodiment of the present application, such as Fig. 9 As shown, the request processing method can be implemented by the client that logs in to the first account and the server interacting with each other. The following steps 910, 920 and 930 can be executed by the client that logs in to the first account, and steps 210 to 230 can be executed by the server. The details are as follows:

[0147] Step 910: In response to the interactive operation initiated to the second account, an interactive request for the second account is sent to the server.

[0148] Interactive controls can be displayed in the client interface, such as controls for triggering the gifting of resources (such as gifts, props, skills, etc.) Figure 3The gift control 114 in the example above is used to trigger a transfer, a control for triggering a game invitation, a control for triggering a group invitation, and a control for triggering an instant conversation (such as a video conversation, a voice conversation, a text conversation, etc.). The operation of the user triggering the interactive control is an interactive operation, such as a click operation, a long press operation, a sliding operation, etc. It is worth mentioning that before triggering the interactive control, the user selects the interactive object accordingly, so as to select the selected second account as the interactive object and initiate an interactive operation to the second account.

[0149] In some embodiments, the client where the first account is located provides a list of accounts that can be interacted with to the user, wherein the accounts in the provided list of accounts that can be interacted with can be accounts in a communication list corresponding to the first account, and the accounts in the list of accounts that can be interacted with are accounts that are in a state where login is allowed, thereby avoiding invalid interactions with accounts that are in a state where login is not allowed due to the presence of accounts in the account list that are in a state where login is not allowed. The accounts in the communication list can be accounts that have a friend relationship with the first account.

[0150] In some embodiments, since the client caches the summary information of the second account last obtained from the server, on this basis, if the time difference between the time of the summary information of the second account last obtained and the current time is less than the time difference threshold, it can be determined whether the summary information of the second account includes the first mark based on the cached summary information of the second account last obtained, and if it does, the first prompt information is displayed. On the contrary, if the time difference between the time of the summary information of the second account last obtained and the current time is not less than the time difference threshold, an interactive request for the second account is sent to the server. The time difference threshold can be set according to actual needs, for example, the time difference threshold is 1 minute, 2 minutes, etc. Therefore, when the current time is short from the last time the summary information of the second account was obtained, it is not necessary to repeatedly request the summary information of the second account from the server, which reduces the interaction process between the client and the server and avoids wasting network resources.

[0151] Step 210: receiving an interaction request initiated by the first account to the second account.

[0152] Step 220: In response to the interaction request, obtain summary information of the second account.

[0153] Step 230: If the summary information of the second account includes the first mark, reject the interaction request and send a first prompt message to the first account.

[0154] The implementation details of steps 210 to 230 are described above and will not be repeated here. The processing process of the server for the account requested to be cancelled (such as adding the first mark, day, adding the second mark, etc. to the summary information of the account) is described above and will not be repeated here.

[0155] Step 920: Receive the first prompt information returned by the server in response to the interactive request.

[0156] Step 930: Display the first prompt information. The displayed first prompt information may be as follows: Figure 3 In some embodiments, the first prompt message may also indicate that the interaction request has been rejected.

[0157] In some embodiments, after step 220, the method further includes: sending summary information of the second account to the first account, so as to display relevant content of the second account on the client where the first account is located according to the summary information of the second account. Since the server side pulls the summary information of the second account in response to the interaction request initiated by the first account to the second account, and sends the summary information of the second account to the first account, the summary information of the second account instantly updates the display content for the second account.

[0158] In some embodiments, the client that logs in to the first account may also perform the following steps B1 to B3, which are described in detail as follows:

[0159] Step B1, sending a first summary request to the server, where the first summary request is used to request to obtain summary information of each fourth account in the communication list of the first account.

[0160] The fourth account refers to an account in the communication list of the first account. The accounts in the communication list of the first account are accounts that have a friend relationship with the first account. Therefore, the fourth account can also be understood as a friend account of the first account.

[0161] In some embodiments, the client may send a first summary request to the server in response to a first trigger operation of entering the address book interface. The address book interface refers to a user interface for displaying a list of contacts. It is understandable that each account is presented in the address book interface according to the summary information of each account, that is, the address book interface can display the avatar, nickname and other content of each account in the address list, and of course, more content related to other accounts can be displayed, for example, the level and number of star diamonds of the account can also be displayed in the game application. In other embodiments, the client may send a first summary request to the server in response to an account login operation.

[0162] Step B2: receiving summary information of the fourth account returned by the server in response to the first summary request.

[0163] After receiving the first summary request, the server obtains summary information of each fourth account from the database in response to the first summary request, and sends the summary information of the fourth account to the first account.

[0164] Step B3: if the summary information of the fourth account includes the second mark, delete the fourth account from the communication list of the first account; the second mark is used to indicate that the account has been cancelled.

[0165] If the summary information of the fourth account includes the second mark, it indicates that the fourth account has been cancelled, so the fourth account is deleted from the communication list of the first account. The cancelled account in the communication list is deleted, and the cancelled friend account does not need to be presented in the communication list, thereby avoiding invalid interactions between the user and the cancelled friend. The process of adding the second mark to the summary information of the account by the server is described above and will not be repeated here.

[0166] In the above embodiment, since the client deletes the cancelled accounts in the communication list, the accounts displayed in the communication list include accounts that have not been cancelled, including accounts that have not requested cancellation and accounts in the cancellation retention period.

[0167] Fig.10 is a schematic diagram showing a display of a communication list according to an embodiment of the present application. Fig.10 FIG. 1 shows a communication list of a first account in a game application. Assume that “Player I” in the communication list 1010 of the first account is in the cancellation retention period. Fig.10 As shown in Figure A in the figure, the communication list 1010 of the first account will display the relevant content of the account based on the summary information of "Player I". If "Player I" does not request to cancel the cancellation request before the cancellation retention period ends, the server will cancel "Player I" after the cancellation retention period ends. After the cancellation, the client where the first account is located can delete the account "Player I" from the communication list 1010 of the first account according to the above steps B1 to B3. After the deletion, the account displayed in the communication list 1010 of the client where the first account is located is as follows. Fig.10 As shown in Figure B.

[0168] In the related art, if the cancelled account is still retained in the friend list, the friend can still perform invalid offline interactive operations on the friend account, which greatly affects the user experience. If the offline interactive operation triggered for the cancelled friend account involves resource transactions, such as giving away virtual resources such as goods and props, it is also a waste of virtual resources of the initiator of the offline interactive operation. The server processing the offline interactive request initiated in response to the offline interactive operation is also a waste of server processing resources. In this embodiment, the cancelled friend account is removed from the communication list, so that other accounts will not perform invalid offline interactive operations on the friend account in the future, which can effectively solve the above problems and improve the user experience.

[0169] In some embodiments, the client that logs in to the first account may also perform the following steps C1 to C3, which are described in detail as follows:

[0170] Step C1, sending a second summary request to the server, where the second summary request is used to request to obtain summary information of each fifth account that participated in the target historical game with the first account.

[0171] In this application, the accounts other than the first account in the target historical games in which the first account has historically participated are referred to as fifth accounts. The target historical games refer to the games in which the first account currently to be displayed has participated, such as game games. It can be understood that in the target historical games, the fifth account can be one or more. In the case of more than one fifth account, the second summary request is used to request summary information of all fifth accounts in the target historical games.

[0172] In some embodiments, in response to a display operation triggered by a user on a target historical game, the client may send a second summary request to the server.

[0173] Step C2, receiving summary information of the fifth account returned by the server.

[0174] The server may obtain summary information of the fifth account from the database according to the fifth account carried in the second summary request, and send the summary information of the fifth account to the first account.

[0175] Step C3: If the summary information of the fifth account includes the second mark, a cancellation mark is displayed for the fifth account in the game record display interface; the cancellation mark is used to prompt that the account has been cancelled.

[0176] The game record display interface is used to display the basic information of each account in the target historical game, for example, the account's avatar, nickname, account level, number of star diamonds, etc. It can be understood that in the game record display interface, the content is displayed for each account based on the summary information of each account.

[0177] If the summary information of the fifth account includes the second mark, it indicates that the fifth account has been cancelled. Therefore, in order to facilitate the user to intuitively know the status of the fifth account, a cancellation mark is displayed for the fifth account in the game record display interface of the client of the first account.

[0178] Fig.11 is a schematic diagram of a game record display interface according to an embodiment of the present application. Fig.11 The game record display interface shown is an interface of a game application, and the content displayed for each account in the game record display interface includes at least the avatar and nickname corresponding to the account. The summary information of the third account on the left side of the game record display interface includes a second mark. Therefore, a logout mark 1111 is displayed for the account in the game record display interface, and the content of the logout mark 1111 is "This player does not exist." Of course, in other embodiments, the content of the logout mark is not limited to this, and can also be other content for intuitively expressing that the account has been logged out. Fig.11 In the game record display interface, for the cancelled account, the cancellation mark will be displayed in the nickname display area of ​​the account. Usually, the nickname display area is larger and the displayed content is easier for users to pay attention to. Displaying the cancellation mark in the nickname display area of ​​the account can make users quickly pay attention to the cancellation mark in the nickname display area, so that users can quickly know that the account has been cancelled.

[0179] In some embodiments, based on the summary information of the fifth account, the client displays relevant content of the fifth account on the game record display interface, such as an avatar corresponding to the fifth account, etc. In this way, the user can identify the fifth account participating in the game by the avatar.

[0180] In the above embodiment, a cancellation mark is displayed for the fifth account including the second mark in the summary information in the game record display interface, so as to distinguish and display the cancelled accounts and the non-cancelled accounts in the target historical game, so that the user can intuitively know which accounts in the target historical game have been cancelled.

[0181] In some embodiments, for the fifth account that has not initiated an account cancellation request and includes the first mark in the summary information, it is displayed normally in the game record display interface, that is, there is no need to display a cancellation mark.

[0182] In other embodiments, for the fifth account including the first mark in the summary information, a cancellation retention period mark may be displayed for the fifth account in the game record display interface, and the cancellation retention period mark is used to prompt that the account is in the cancellation retention period. In this way, accounts that have not requested account cancellation, accounts that are in the cancellation retention period, and accounts that have been cancelled are displayed differently.

[0183] In some embodiments, the method further includes: in response to a detail access operation initiated on an account displaying a cancellation mark, displaying a third prompt message, the third prompt message being used to prompt that the detail information of the cancelled account cannot be accessed. It is understandable that, when the client detects a detail access operation initiated on an account displaying a cancellation mark, the detail access initiated on the account displaying the cancellation mark is shielded, that is, the detail information of the account is not requested from the server, and the third prompt message is directly displayed to avoid subsequent users from performing invalid operations on the account, thereby improving the cancellation process of the account.

[0184] The following describes an apparatus embodiment of the present application, which can be used to execute the method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned method embodiment of the present application.

[0185] Fig.12 is a block diagram of a request processing device according to an embodiment of the present application, the request processing device is configured in an electronic device as a server, and is used to implement the request processing method provided by the present application, such as Fig.12 As shown, the request processing device includes: a receiving module 1210, which is used to receive an interaction request initiated by a first account to a second account. An acquisition module 1220, which is used to obtain summary information of the second account in response to the interaction request. A processing module 1230, which is used to reject the interaction request if the summary information of the second account includes a first mark, and send a first prompt message to the first account; the first prompt message is used to prompt that the second account is in a cancellation retention period; during the cancellation retention period of the second account, the second account is in a state of allowing login; the first mark is added by the server in the summary information of the second account in response to the account cancellation request for the second account.

[0186] In some embodiments, the request processing device also includes: an account cancellation request receiving module, used to receive an account cancellation request, the account cancellation request is used to request cancellation of the second account; a first processing module, used to set the second account to enter a cancellation retention period according to the account cancellation request, and add a first mark to the summary information of the second account.

[0187] In some embodiments, the first processing module is configured to: according to the account cancellation request, set the second account to enter the cancellation retention period, and assign the first field in the summary information of the second account to the first time; the value of the first field after assignment is used as the first mark, and the first time is the time when the account cancellation request is received; the cancellation retention period of the second account starts with the first time, and the duration of the cancellation retention period is the set duration.

[0188] In some embodiments, the request processing device also includes: a second processing module, which is used to delete the first mark in the summary information of the second account and release the cancellation retention period of the second account if it is detected that the second account is in a logged-in state before the end of the cancellation retention period; or, if a cancellation revocation request for the second account is received before the end of the cancellation retention period, delete the first mark in the summary information of the second account and release the cancellation retention period of the second account.

[0189] In some embodiments, the request processing device also includes: a third processing module, which is used to cancel the second account and add a second mark to the summary information of the second account if it is determined that the summary information of the second account still includes the first mark at the end time of the cancellation retention period of the second account; the second mark is used to indicate that the account has been cancelled.

[0190] In some embodiments, the request processing device further includes: an offline processing module, which is used to offline the second account in response to the account deregistration request if the second account is in a logged-in state.

[0191] In some embodiments, the account cancellation request includes a third account and a first application identifier, the first application indicated by the first application identifier is an application to which the second account belongs; the third account is an account in the second application, and the first application and the second application are different applications; in this embodiment, the request processing device also includes: a second account determination module, which is used to determine the second account associated with the third account in the first application based on the association relationship between the account in the first application and the account in the second application, according to the third account in the account cancellation request.

[0192] In some embodiments, the request processing device further includes: an association deletion module, configured to delete the association between the second account and the third account if it is determined that the summary information of the second account still includes the first mark at the end time of the cancellation retention period of the second account.

[0193] In some embodiments, the request processing device further includes: a second prompt information sending module, configured to send a second prompt information to the third account, wherein the second prompt information is used to prompt that the account associated with the third account in the first application has been cancelled.

[0194] Fig.13 is a block diagram of a request processing device according to another embodiment of the present application. The request processing device can be configured at a terminal where a client that logs in to a first account is located, such as Fig.13As shown, the request processing device includes: a first sending module 1310, which is used to send an interaction request for the second account to the server in response to the interaction operation initiated to the second account; a first receiving module 1320, which is used to receive the first prompt information returned by the server in response to the interaction request; the first prompt information is processed and returned by the server according to the above method; and a display module 1330, which is used to display the first prompt information.

[0195] In some embodiments, Fig.13 The request processing device of the corresponding embodiment also includes: a second sending module, used to send a first summary request to the server, the first summary request is used to request to obtain summary information of each fourth account in the communication list of the first account; a second receiving module, used to receive the summary information of the fourth account returned by the server in response to the first summary request; a deleting module, used to delete the fourth account in the communication list of the first account if the summary information of the fourth account includes a second mark; the second mark is used to indicate that the account has been cancelled.

[0196] In some embodiments, Fig.13 The request processing device of the corresponding embodiment also includes: a third sending module, used to send a second summary request to the server, the second summary request is used to request to obtain summary information of each fifth account participating in the target historical game with the first account; a third receiving module, used to receive the summary information of the fifth account returned by the server; a logout mark display module, used to display a logout mark for the fifth account in the game record display interface if the summary information of the fifth account includes a second mark; the logout mark is used to prompt that the account has been logged out.

[0197] In some embodiments, Fig.13 The request processing device of the corresponding embodiment also includes: a third prompt information display module, which is used to display third prompt information in response to a detail access operation initiated on an account that displays a deregistration mark, and the third prompt information is used to prompt that the detail information of the deregistered account cannot be accessed.

[0198] Fig.14 The schematic diagram of the structure of the computer system of the electronic device suitable for implementing the embodiment of the present application is shown. The electronic device can be the terminal as described above, or a device in the server, which is used to implement the request processing method provided by the present application. It should be noted that Fig.14 The computer system 1400 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0199] like Fig.14As shown, the computer system 1400 includes a central processing unit (CPU) 1401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1402 or the program loaded from the storage part 1408 to the random access memory (RAM) 1403, such as executing the method in the above embodiment. In RAM 1403, various programs and data required for system operation are also stored. CPU 1401, ROM 1402 and RAM 1403 are connected to each other through bus 1404. Input / output (I / O) interface 1405 is also connected to bus 1404.

[0200] The following components are connected to the I / O interface 1405: an input section 1406 including a keyboard, a mouse, etc.; an output section 1407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1408 including a hard disk, etc.; and a communication section 1409 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1409 performs communication processing via a network such as the Internet. A drive 1410 is also connected to the I / O interface 1405 as needed. A removable medium 1411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1410 as needed so that a computer program read therefrom is installed into the storage section 1408 as needed.

[0201] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1409, and / or installed from a removable medium 1411. When the computer program is executed by a central processing unit (CPU) 1401, various functions defined in the system of the present application are executed.

[0202] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0203] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0204] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0205] As another aspect, the present application further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist independently without being assembled into the electronic device. The above computer-readable storage medium carries computer-readable instructions, and when the computer-readable storage instructions are executed by a processor, the method in any of the above embodiments is implemented.

[0206] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method in any of the above embodiments.

[0207] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0208] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0209] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0210] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A request processing method, characterized in that: Applied to the server, including: Receiving an interaction request initiated by the first account to the second account; In response to the interaction request, obtaining summary information of the second account; If the summary information of the second account includes a first mark, the interaction request is rejected, and a first prompt message is sent to the first account; the first prompt message is used to prompt that the second account is in a cancellation reservation period; during the cancellation reservation period of the second account, the second account is in a state of allowing login; the first mark is added by the server to the summary information of the second account in response to the account cancellation request for the second account.

2. The method according to claim 1, characterized in that: The method further comprises: receiving an account cancellation request, wherein the account cancellation request is used to request cancellation of the second account; According to the account cancellation request, the second account is set to enter a cancellation retention period, and the first mark is added to the summary information of the second account.

3. The method according to claim 2, characterized in that The step of setting the second account to enter a cancellation retention period according to the account cancellation request and adding the first mark to the summary information of the second account includes: According to the account cancellation request, the second account is set to enter a cancellation retention period, and a first field in the summary information of the second account is assigned a first time; the value of the first field after the assignment is used as the first mark, and the first time is the time when the account cancellation request is received; the cancellation retention period of the second account starts with the first time, and the duration of the cancellation retention period is the set duration.

4. The method according to claim 2 or 3, characterized in that: After setting the second account to enter a cancellation retention period according to the account cancellation request and adding the first mark to the summary information of the second account, the method further includes: If it is detected that the second account is in a logged-in state before the cancellation retention period ends, deleting the first mark in the summary information of the second account and releasing the cancellation retention period of the second account; or, If a cancellation request for the second account is received before the cancellation retention period ends, the first mark in the summary information of the second account is deleted, and the cancellation retention period of the second account is released.

5. The method according to claim 4, characterized in that After setting the second account to enter a cancellation retention period according to the account cancellation request and adding the first mark to the summary information of the second account, the method further includes: If at the end time of the cancellation retention period of the second account, it is determined that the summary information of the second account still includes the first mark, the second account is cancelled and a second mark is added to the summary information of the second account; the second mark is used to indicate that the account has been cancelled.

6. The method according to claim 2 or 3, characterized in that: After receiving the account cancellation request, the method further includes: If the second account is in a logged-in state, in response to the account deregistration request, the second account is offlined.

7. The method according to claim 2 or 3, characterized in that: The account deregistration request includes a third account and a first application identifier, the first application indicated by the first application identifier is an application to which the second account belongs; the third account is an account in the second application, and the first application and the second application are different applications; Before setting the second account to enter a cancellation retention period according to the account cancellation request and adding the first mark to the summary information of the second account, the method further includes: Based on the association relationship between the account in the first application and the account in the second application, the second account in the first application that is associated with the third account is determined according to the third account in the account cancellation request.

8. The method according to claim 7, characterized in that After setting the second account to enter a cancellation retention period according to the account cancellation request and adding the first mark to the summary information of the second account, the method further includes: If it is determined that the summary information of the second account still includes the first mark at the end time of the cancellation retention period of the second account, the association relationship between the second account and the third account is deleted.

9. A request processing method, characterized in that: Applicable to the client that logs in to the first account, including: In response to the interactive operation initiated to the second account, sending an interactive request for the second account to the server; Receiving first prompt information returned by the server in response to the interactive request; the first prompt information is processed and returned by the server according to the method according to any one of claims 1 to 8; The first prompt information is displayed.

10. The method according to claim 9, characterized in that The method further comprises: Sending a first summary request to the server, where the first summary request is used to request summary information of each fourth account in the communication list of the first account; receiving summary information of a fourth account returned by the server in response to the first summary request; If the summary information of the fourth account includes a second mark, the fourth account is deleted from the communication list of the first account; the second mark is used to indicate that the account has been cancelled.

11. The method according to claim 9, characterized in that The method further comprises: Sending a second summary request to the server, where the second summary request is used to request summary information of each fifth account that participated in the target historical game with the first account; receiving summary information of the fifth account returned by the server; If the summary information of the fifth account includes the second mark, a cancellation mark is displayed for the fifth account in the game record display interface; the cancellation mark is used to prompt that the account has been cancelled.

12. The method according to claim 9, characterized in that The method further comprises: In response to a detail access operation initiated for an account displaying a deregistration mark, third prompt information is displayed, where the third prompt information is used to prompt that the detail information of the deregistered account cannot be accessed.

13. A request processing device, characterized in that: Applied to the server, including: A receiving module, used for receiving an interaction request initiated by the first account to the second account; an acquisition module, configured to acquire summary information of the second account in response to the interaction request; A processing module, configured to reject the interaction request and send a first prompt message to the first account if the summary information of the second account includes a first mark; the first prompt message is used to prompt that the second account is in a cancellation reservation period; during the cancellation reservation period of the second account, the second account is in a state of allowing login; the first mark is added by the server to the summary information of the second account in response to the account cancellation request for the second account.

14. A request processing device, characterized in that: Applicable to the client that logs in to the first account, including: A first sending module, configured to send an interaction request for the second account to a server in response to an interaction operation initiated to the second account; A first receiving module, configured to receive first prompt information returned by the server in response to the interactive request; the first prompt information is processed and returned by the server according to the method of any one of claims 1 to 8; A display module is used to display the first prompt information.

15. An electronic device, characterized in that: include: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 12 is implemented.

16. A computer-readable storage medium having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by a processor, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 12 is implemented.

17. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 12 is implemented.

Images