Information processing method and device, equipment and storage medium

Abstract

Embodiments of the present application disclose an information processing method, device and equipment, and a storage medium, wherein the method comprises: receiving a login request for an application program, the login request comprising a first account assigned by a target platform for a target user on the target platform, the first account being generated by the target platform according to login information of the target user on the target platform or terminal information of the target user; obtaining platform information corresponding to the target platform and application information corresponding to the application program, and performing encoding processing based on the platform information, the application information and the first account to obtain a second account of a target length; and logging into the application program through the second account. When logging into the application program through different platforms, a unified form of account can be generated for logging into the application program, which facilitates account management in the application program.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an information processing method, apparatus, device and storage medium. Background Technology

[0002] Currently, there are various open platforms in China, such as WeChat, QQ, and Kuaishou. To facilitate user login and use of certain applications, many applications support authorized login through these open platforms. Typically, when an application integrates with an open platform for authorized login, the platform assigns a unique OpenID (or account) to the application. The application can then directly use this OpenID as its account. However, different open platforms use different rules for generating OpenIDs, resulting in multiple different login accounts within the same application, which is inconvenient for account management. This is especially problematic when applications expand overseas, as privacy requirements necessitate that application accounts comply with laws such as GDPR to protect user privacy.

[0003] Therefore, how to assign accounts to applications when logging in through an open platform has become one of the hot research topics today. Summary of the Invention

[0004] This invention provides an information processing method, apparatus, device, and storage medium that encodes accounts provided by a platform to obtain fixed-length accounts for use in logging into applications. This ensures that the account lengths logged into the application are consistent, facilitating application management.

[0005] On one hand, embodiments of the present invention provide an information processing method, including:

[0006] Receive a login request for the application, the login request including a first account assigned to the target user by the target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information;

[0007] Obtain the platform information corresponding to the target platform and the application information corresponding to the application, and perform encoding processing based on the platform information, the application information and the first account to obtain a second account of the target length;

[0008] Log in to the application using the second account.

[0009] In one aspect, embodiments of the present invention also provide an information processing apparatus, comprising:

[0010] The receiving unit is configured to receive a login request for an application, the login request including a first account assigned to a target user by the target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information;

[0011] The acquisition unit is used to acquire platform information corresponding to the target platform and application information corresponding to the application.

[0012] The processing unit is used to perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length;

[0013] The processing unit is also used to log in to the application using the second account.

[0014] On one hand, embodiments of the present invention provide an information processing device, characterized in that it includes:

[0015] A processor, suitable for implementing one or more computer programs; and a computer storage medium storing one or more computer programs adapted to be loaded and executed by the processor:

[0016] Receive a login request for an application, the login request including a first account assigned to a target user by a target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; obtain platform information corresponding to the target platform and application information corresponding to the application, and perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; log in to the application using the second account.

[0017] On one hand, embodiments of the present invention provide a computer storage medium storing a computer program, which, when executed by a processor, is used to perform:

[0018] Receive a login request for an application, the login request including a first account assigned to a target user by a target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; obtain platform information corresponding to the target platform and application information corresponding to the application, and perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; log in to the application using the second account.

[0019] On one hand, embodiments of the present invention provide a computer program product or a computer program, the computer program product including a computer program stored in a computer storage medium; a processor of an information processing device reads the computer program from the computer storage medium, and the processor executes the computer program, causing the information processing device to perform:

[0020] Receive a login request for an application, the login request including a first account assigned to a target user by a target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; obtain platform information corresponding to the target platform and application information corresponding to the application, and perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; log in to the application using the second account.

[0021] In this embodiment of the invention, after receiving a login request for an application, the information processing device retrieves a first account assigned to the target user by the target platform from the login request. Then, it obtains the platform information of the target platform and the application information corresponding to the application. Further, based on the platform information, application information, and the first account, it performs encoding processing to obtain a second account with a length equal to the target length. Finally, it logs into the application using this second account. As can be seen from the above steps, this embodiment of the invention does not directly use the first account assigned by the platform as the login account in the application. Instead, it processes the first account through encoding to obtain a second account of the target length, and then logs into the application using the second account. Compared with the prior art, this embodiment of the invention can ensure that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. Furthermore, the encoding process for the first account references the platform information and application information, making the second account self-resolving. When decoding the second account subsequently, it can accurately locate which platform account the account was generated from, facilitating the management of the association between the platform and the application. Attached Figure Description

[0022] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a schematic diagram of the structure of an account management system provided in an embodiment of the present invention;

[0024] Figure 2 This is a flowchart illustrating an information processing method provided in an embodiment of the present invention;

[0025] Figure 3 This is a schematic diagram of a login interface for an application provided in an embodiment of the present invention;

[0026] Figure 4 This is a schematic diagram of a process for determining a hash account provided in an embodiment of the present invention;

[0027] Figure 5 This is a schematic diagram of the structure of data to be encoded provided in an embodiment of the present invention;

[0028] Figure 6 This is a flowchart illustrating another information processing method provided in an embodiment of the present invention;

[0029] Figure 7a This is a schematic diagram illustrating the mapping relationship between a first account and a second account, provided in an embodiment of the present invention.

[0030] Figure 7b This is a schematic diagram illustrating the mapping relationship between platform information and a second account, provided by an embodiment of the present invention.

[0031] Figure 8 This is a framework diagram of an account management system provided in an embodiment of the present invention;

[0032] Figure 9 This is a schematic diagram of the structure of an information processing device provided in an embodiment of the present invention;

[0033] Figure 10 This is a schematic diagram of the structure of an information processing device provided in an embodiment of the present invention. Detailed Implementation

[0034] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0035] This invention provides an information processing solution, primarily applied to scenarios involving authorized login to applications via an open platform. Common open platforms can be categorized into two types: first, application-based platforms, such as social applications like WeChat and QQ, and payment applications; second, non-application-based platforms, such as guest login platforms. Common scenarios for authorized login to applications via open platforms include logging into a game application via WeChat, or logging into a shopping application via a payment platform. As mentioned above, when logging into an application via an open platform, the open platform needs to assign an open platform account to the user. In the information processing solution of this invention, the information processing device encodes the open platform account assigned by the open platform to process it into an account with a fixed length. That is, regardless of how complex the accounts provided by various platforms are, the information processing solution provided by this invention will process them into accounts of uniform length.

[0036] In existing technologies, there are generally two ways to generate another account from one account. The first is encryption technology. In the application scenario of this invention, the open platform account provided by the open platform is encrypted again using encryption technology to obtain a new result, which is then used as the user's login account in the application. The advantage of this method is that it does not require storing the newly generated result, because the result obtained by encrypting the same account each time is the same, and the open platform account can be obtained after decrypting the new result. However, the disadvantage of this method is that the new result is not numerical and cannot be used directly. Furthermore, the length of the new result depends on the length of the original open platform account. The longer the original open platform account, the more exponentially the length of the new result after encryption will increase. As a result, the length of the encrypted account will be inconsistent for open platform accounts of different lengths, causing many problems for application account management.

[0037] Another method is random mapping and auto-incrementing mapping. In the application scenarios of this invention, this requires storing the mapping relationship between the open platform account and the newly generated account to achieve a one-to-one correspondence. The advantage of this method is that it can map out digital accounts for direct use by the application, but the problem of inconsistent account lengths remains unresolved. Moreover, because it requires storing the mapping relationship, the storage medium introduces new risks, such as irreparable damage to the account information if the storage medium is damaged.

[0038] Compared to the two existing methods mentioned above, the information processing method provided in this embodiment of the invention can generate an account of uniform length regardless of the platform. In this way, the application does not need to care about the differences in accounts across different platforms, which is beneficial for the application's account management.

[0039] Based on the above information processing scheme, embodiments of the present invention provide an account management system, see below. Figure 1 This is a schematic diagram of the structure of an account management system provided in an embodiment of the present invention. Figure 1 The account management system shown may include a platform management device 101, a target user terminal 102, and an information processing device 103. The target user terminal 102 can be connected to the platform management device 101 and the information processing device 103 via wired or wireless means, respectively.

[0040] The platform management device 101 is used to manage the corresponding open platform, such as supporting the operation of services within the platform. In this embodiment of the invention, unless otherwise specified, the platform management device 101 refers to the platform management device corresponding to the target platform. It should be noted that in this embodiment of the invention, the target platform can refer to a social application, a payment application, or other applications; alternatively, the target platform can also refer to guest login. If the target platform is a social application, a payment application, or other applications, then the platform management device 101 can refer to the server corresponding to the social application or payment application; if the target platform is guest login, then the platform management device 101 can be the server corresponding to the application to be logged into in this invention.

[0041] In one embodiment, the target user terminal 102 can be used to run applications and a target platform. The information processing device 103 can be a server providing support for the application or a terminal device running the application. It should be noted that when the information processing device 103 is a terminal device running the application, the information processing device 103 and the target user terminal 102 can be the same device. In the following description, unless otherwise specified, the information processing device can refer to a server. The target user terminal or terminal device can be a smartphone, tablet, laptop, desktop computer, smart speaker, smart vehicle, or smartwatch, but is not limited to these. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0042] In one embodiment, a target user can enter an authorization login operation on the target user terminal 102 to log in to the application through the target platform. The target user terminal 102 notifies the platform management device 101 corresponding to the target platform of the authorization login operation. The platform management device 101 assigns an Open Platform account OpenID to the target user based on the target user's login information on the target platform. In the following description, this Open Platform account can be referred to as the first account. Then, the platform management device 101 sends a login request for the application to the information processing device 103. After receiving the login request, the information processing device 103 obtains the first account carried in the login request, and then encodes it based on the first account, the platform information of the target platform, and the application information of the application to obtain a second account with a length equal to the target length. Then, the second account is used to log in to the application.

[0043] In this embodiment of the invention, regardless of the complexity of the open platform accounts provided by each platform, the information processing scheme provided by this embodiment will process them into accounts of uniform length. This facilitates unified management of application accounts. Furthermore, during the encoding process of the first account, platform information and application information are referenced, thus enabling the second account to be self-resolving. When decoding the second account subsequently, it is possible to accurately locate which platform account the account was generated from, facilitating the management of the association between platforms and applications.

[0044] Based on the above information processing scheme and account management system, this invention provides an information processing method, see [link to relevant documentation]. Figure 2 This is a flowchart illustrating an information processing method provided in an embodiment of the present invention. Figure 2 The information processing method shown can be executed by an information processing device, specifically by the processor of the information processing device. Figure 2 The information processing method shown may include the following steps:

[0045] Step S201: Receive a login request for the application, which includes a first account assigned to the target user by the target platform.

[0046] In one embodiment, the application can be any application that requires user login, such as a game application or a shopping application. The target platform can refer to an application that can provide authorization login for other applications, such as a social application, a payment application, a Google Chrome account, or a Face ID account. The target platform can also refer to a non-application, such as guest login.

[0047] In one embodiment, the login request received by the information processing device may be sent by the platform management device. Specifically, the implementation method of the platform management device sending a login request to the information processing device may include the following steps:

[0048] (1) The target user enters the authorization login operation to log in to the application through the target platform on the target user terminal;

[0049] The implementation method for a target user to enter an authorization login operation on their terminal can be as follows: the target user terminal displays the application's login interface, which may include multiple platform authorization login options; when the target platform authorization login option is selected among the multiple platform authorization login options, it is determined that the target user has entered an authorization login operation. For example, see... Figure 3 This invention provides a login interface for an application, which includes multiple platform authorization login options, such as the WeChat application authorization login option, which can be represented as "Play with WeChat friends". Figure 3 As shown in Figure 31, for example, the QQ application's authorized login option can be represented as "Play with QQ friends". Figure 3 As shown in Figure 32, for example, the guest login option... Figure 3 As shown in Figure 33, assuming "Play with WeChat friends" is the target platform's authorized login option, when the target user triggers this option, it indicates that the target user has entered an authorized login operation.

[0050] (2) The target user terminal sends a notification to the platform management device based on the authorized login operation. After receiving the notification, the platform management device generates a first account based on the target user's login information in the target platform or the target user terminal information, and sends the first account in the login request to the information processing device.

[0051] In practice, after receiving a notification from the target user's terminal, the platform management device can determine the target platform type and then decide how to generate a primary account for the target user based on that type. Optionally, if the target platform is an application such as a social application or a payment application, the platform management device can generate a primary account based on the target user's login information on the target platform. For example, the login information can be encrypted, and the encrypted login information can be used as the primary account. If the target platform is a non-application, such as guest login, the platform management device can generate a primary account based on the target user's terminal information. For example, the terminal identifier of the target user's terminal can be encrypted, and the encrypted terminal identifier can be used as the primary account.

[0052] After the login request is generated through the above steps (1) and (2), the platform management device sends the login request to the information processing device, which then generates a second account for the target user to log in to the application through the following steps S202 and S203.

[0053] Step S202: Obtain the platform information corresponding to the target platform and the application information corresponding to the application, and perform encoding processing based on the platform information, application information and the first account to obtain the second account of the target length.

[0054] As mentioned above, existing technologies for generating a second account based on a first account include encryption and random or auto-incrementing mapping. However, the second account obtained through these two methods does not contain application information or platform-related information, resulting in poor self-resolving capability of the second account, or in other words, hindering the management of the association between the application and the platform. In this embodiment of the invention, to improve the self-resolving capability of the second account, the embodiments also reference the platform information of the target platform and the application information of the application while generating the second account based on the first account. In other words, this embodiment of the invention obtains a second account of target length based on the platform information of the target platform, the application information of the application, and the first account through encoding processing.

[0055] In one embodiment, step S202, which involves encoding based on platform information, application information, and a first account to obtain a second account of a target length, may include: performing a hash operation on the first account to obtain a hash account; obtaining data to be encoded of the target length, the data to be encoded including a platform information field, an application information field, and a hash account field; filling the data to be encoded based on the platform information, the application information, and the hash account; and performing Uniform Resource Locator (URL) encoding on the filled data to obtain the second account.

[0056] The information processing device performs a hash operation on the first account to obtain a hash account, which may include the following steps s1-s4, which are described in detail below.

[0057] Step s1: Obtain the hash operation size and hash value lookup table;

[0058] Commonly used hash operations include 32-bit hash operations and 64-bit hash operations. Based on existing hash operations, this invention independently designs 48-bit hash and 56-bit hash, which can meet the needs of larger account capacity while reserving space for applications, so that application developers can further encode the accounts logged into the application.

[0059] Optionally, the size of the hash operation is obtained by dividing the capacity of the hash operation by 8 bits. For example, the capacity of a 32-bit hash is 32 bits, and the result of dividing 32 bits by 8 bits is 4, so the size of the 32-bit hash operation is 4. Similarly, the capacity of a 56-bit hash is 56 bits, and the result of dividing 56 bits by 8 bits is 7, so the size of the 56-bit hash operation is 7.

[0060] Optionally, the hash value lookup table may include M hash values, where M is an integer greater than 1. The M hash values ​​can be 0, 1, 2, 3...255. Each hash value corresponds to an index identifier, which is used to indicate the position of the corresponding hash value in the hash value lookup table.

[0061] Table 1 Hash Value Reference Table

[0062] Index identifier Hash value 0 2 1 0 2 5 3 4 4 3 5 1

[0063] In a hash value lookup table, multiple hash values ​​can be randomly arranged. That is, hash value 1 might correspond to index 3, meaning hash value 1 might be in the third position. For example, see Table 1, which provides a hash value lookup table according to an embodiment of the present invention. As can be seen from Table 1, taking the hash lookup table containing six hash values ​​(0, 1, 2, 3, 4, 5) as an example, hash value 0 can correspond to index 1, so hash value 0 is in the second position in Table 1; hash value 2 corresponds to index 0, so hash value 2 is in the first position in Table 1.

[0064] Step s2: Based on the first account, perform a table lookup to determine a sub-hash account from the hash value lookup table;

[0065] In a specific implementation, the first account may include N characters, where N is an integer greater than 1. The process of searching for a sub-hash account from a hash value lookup table based on the first account may include: ① converting the i-th character among the N characters to a numerical value, and then performing a modulo operation on the i-th character after the numerical conversion with M to obtain a first index identifier corresponding to the i-th character; ② determining an initial hash value from the M hash values ​​based on the first index identifier; ③ obtaining the target character currently being traversed from the N characters; ④ performing an XOR operation between the target character and the initial hash value to obtain a second index identifier, and determining an updated hash value from the M hash values ​​based on the second index identifier; ⑤ if there are no untraversed characters among the N characters, then the updated hash value is used as the sub-account; ⑥ if there are untraversed characters among the N characters, then the updated hash value is used as the initial hash value, and the process returns to step ③.

[0066] In step ①, i is greater than or equal to 1 and less than or equal to N. The i-th character can be considered any one of the N characters. Converting the i-th character to a numerical value and taking the remainder after dividing by M will result in a value between 1 and M. In step ②, determining the initial hash value from the M hash values ​​based on the first index identifier corresponding to the i-th character can be done by searching a hash value lookup table for an index identifier that matches the first index identifier. The hash value corresponding to the matching index identifier is then determined as the initial hash value. After determining an initial hash value, step ③ updates this initial hash value sequentially based on the characters in the first account until all characters in the N characters have been traversed. The last updated hash value is then determined as a sub-hash account corresponding to the first account.

[0067] It should be understood that in step ① above, the i-th character is any character in the first account, and the process of updating the initial hash value based on the characters in the first account in steps ③-⑥ is to randomly traverse from N characters. In practical applications, the i-th character can be set to be the first or last character in the first account according to different needs, and other characters can be traversed in the order of front to back or back to front.

[0068] For example, assuming the i-th character is the first character in the first account, steps ③-⑥ iterate through N characters in reverse order. The hash value lookup table contains 256 hash values. The process of generating a sub-hash account based on the first account can be roughly as follows: Convert the first character in the first account to a numerical value, take the remainder when divided by 256, and use the remainder as the index of the first character. Use this index to look up the hash value lookup table to obtain the initial hash value A. Iterate through each character in the first account in reverse order, XORing each character with the initial hash value A to obtain B. Then, use this B as the new index to obtain the new hash value A from the hash value lookup table. Use the new hash value obtained after iterating through the first character as a sub-hash account. Optionally, the sub-hash account has a capacity of 8 bits.

[0069] It should be noted that one bit can be considered as a binary code, which includes 0 or 1. The number of binary codes in binary data determines the value that binary data can represent. For example, if the number of binary codes is 2, then the binary data can represent values ​​from 1 to 4. Similarly, if the number of binary codes is 4, then the binary data can represent values ​​from 1 to 16. In this embodiment of the invention, the maximum hash value in the hash value lookup table is 256, meaning that 8 binary codes are needed to represent the maximum value 256. In other words, a sub-hash account can be a binary data consisting of 8 bits. Therefore, for the sake of consistency, in this embodiment of the invention, unless otherwise specified, in the following descriptions involving features converted to binary data, the number of binary codes included in the binary data can be a multiple of 8.

[0070] Step s3: If the number of sub-hash accounts is less than the size of the hash operation, then update the first account to obtain the first updated account, use the first updated account as the first account, and return to execute step s2;

[0071] Step s4: If the number of sub-hash accounts is equal to the size of the hash operation, then the multiple sub-hash accounts are concatenated in the order of generation to obtain the hash account.

[0072] Optionally, if the number of sub-hash accounts is equal to the hash operation size, it indicates that the hash operation on the first account is complete. The resulting sub-hash accounts are then concatenated in the order they were generated to obtain the hash account. If the number of sub-hash accounts is less than the hash operation size, it indicates that further hash operations need to be performed on the first account. To ensure that the sub-hash accounts obtained from each hash operation are different, in this embodiment of the invention, instead of directly performing a secondary hash operation on the original first account, the first account is updated. The updated first account replaces the initial first account, and then step s2 is performed on the replaced first account.

[0073] In one embodiment, updating the first account essentially involves updating the i-th character in the first account. Specifically, updating the i-th character can include: converting the i-th character to a numerical value and adding it to the loop count of step s2. If s2 loops once, the count is increased by 1; if it loops twice, the count is increased by 2, and so on.

[0074] As described above, determining the hash account corresponding to the first account involves two loops, which can be called the inner loop and the outer loop, respectively. The inner loop refers to the process of traversing the N characters of the first account to determine a sub-hash account, while the outer loop refers to the process of looking up the hash account based on the first account. Below... Figure 4To illustrate the above process of determining the hash account, in Figure 4 The assumptions are as follows: the i-th character is the last character in the first account; characters are selected from other characters in reverse order to update the initial hash value; the update method for the first account is to convert the i-th character into a numerical value and add the loop count; the hash value lookup table includes 256 randomly arranged hash values, and the index identifier can be represented by table, for example, table[1] represents the hash value in the first position in the hash value lookup table.

[0075] First, obtain the first account, which can be represented as OpenID, the size of the hash operation, and the hash lookup table; then initialize the number of iterations of the outer loop to 0, and use the array sum[] to store the sub-hash accounts obtained during the process of determining the hash account; start the first outer loop, the inner loop process included in the outer loop is as follows: first, obtain the last character in the first account OpenID, represented as i = length(OpenID) - 1, then use the statement int(OpenID[i]) + count) % 256 to perform a numerical operation on the last character and take the remainder after dividing by 256, and obtain the first index identifier, then look up the initial hash value A from the hash value lookup table using the first index identifier, this process can The process is represented by the statement A = table[(int(OpenID[i]) + count) % 256]. Next, the last character is XORed with the determined initial hash value A to obtain B, which is used as the new index identifier. Based on the new index, the updated hash value is searched from the hash value lookup table, represented as A = table[B]. At this time, A represents an updated hash value. Further, it is determined whether all characters in the N characters have been traversed. If not, the traversal continues in order. If the traversal is completed, the updated hash value is used as the sub-hash value obtained in the loop of this sub-hash account, and the sub-hash value is stored in the array sum[]. Specifically, it can be represented as sum[count] = A.

[0076] The first outer loop ends here. Next, the relationship between the number of outer loop iterations and the hash operation size is checked. If the number of outer loop iterations is less than the hash operation size, the second outer loop begins. The process of the second outer loop is the same as the first, and will not be repeated here. The outer loop continues until the number of outer loop iterations is greater than or equal to the hash operation size. Then, the outer loop ends, and the values ​​in the array sum[] obtained during the outer loop are concatenated to obtain the hash account corresponding to the first account.

[0077] Optionally, after obtaining the hash account corresponding to the first account through steps s21-s24 above, the data to be encoded of the target length is obtained. Then, based on the platform information, the application information, and the hash account, the data to be encoded is padded, and the padded data to be encoded is subjected to Uniform Resource Locator (URL) encoding to obtain the second account. The target length can be a pre-set length suitable for accounts in the application, and can be set to different values ​​in different application scenarios. For example, in a game application, this embodiment of the invention can set the target length to 192 bits. The platform information may include a platform identifier, and the application information may include any one or more of the application identifier and application version number.

[0078] In the specific implementation, the data to be encoded includes a platform information field, an application information field, and a hash account field. To facilitate subsequent custom encoding operations on the second account and to ensure that any platform information, application information, and hash accounts obtained from the platform account can be completely filled into the data to be encoded, each field in this embodiment can be set to a relatively large length. For example, since the maximum size of the hash operation is 8, the sub-hash account obtained from each size of the hash operation can include 8 bits, so the maximum length of the hash account is 64 bits. To reserve space for custom encoding, the length of the hash account field can be set to 64 bits. The platform information field and the application information field are set in the same way. For example, in multiple platforms, the platform information is at most 32 bits, so the length of the platform information field can be set to 32 bits; similarly, in multiple applications, the application information is at most 32 bits, so the length of the application information field can also be set to 32 bits. It should be noted that if the application information includes an application identifier and an application version number, the application information field in the data to be encoded also includes an application identifier field and an application version number field, which are used to store the application identifier and the application version number, respectively.

[0079] Optionally, the platform information field, application information field, and hash account field can be randomly ordered in the data to be encoded, or the hash account field can be placed at the lowest position. In practical applications, the arrangement of these fields in the data to be encoded can be set according to different needs, and this embodiment of the invention does not impose any limitations.

[0080] In one embodiment, padding the data to be encoded based on the platform information, the application information, and the hash account may include: converting the platform information into binary data in 8-bit units, padding the high-order bits with 0s if the resulting binary data is less than the length of the platform information field; converting the application information into binary data in 8-bit units, padding the high-order bits with 0s if the resulting binary data is less than the length of the application information field; and converting the hash account into binary data in 8-bit units, padding the high-order bits with 0s if the resulting binary data is less than the length of the hash account field. It should be understood that, for ease of reading, after padding the data to be encoded, the content of each field can be converted into decimal form and stored in the data to be encoded.

[0081] For example, see Figure 5 This is a schematic diagram of the structure of data to be encoded provided in an embodiment of the present invention. Figure 5 The data to be encoded shown may include platform information fields, such as... Figure 5 As shown in Figure 51, the application information fields are as follows: Figure 5 As shown in Figures 52 and 53, it is assumed here that the application information includes the application identifier and the application version number, and different types of application information are stored in different fields; Figure 5 The data to be encoded shown also includes a hash account field, such as... Figure 5 As shown in Figure 54, each piece of information is filled into its corresponding field. Assuming the hash account field is 64 bits long and the hash account is 32 bits, the hash account needs to be converted to binary data, represented as: 00000010 00000100 00000001 00100000. To fill the hash account into the hash account field, 32 zeros are added to the high bits of the hash account. The result after padding is: 00000010 00000100 00000001 00100000 00000000 00000000 00000000 00000000. Finally, the padded binary number is converted to decimal, represented as: 24232, and this decimal data is stored in the hash account field. The other fields are processed in the same way, and will not be elaborated further.

[0082] After padding the data to be encoded, the padded data is then subjected to Uniform Resource Locator (URI) encoding to obtain the second account. Specifically, the content of each field in the padded data is converted into binary data, with each binary data containing a number of binary codes that is an integer multiple of a first number. The binary data are then concatenated to obtain the target binary data, which is then divided into n binary data segments in ascending order of bit depth. Each binary data segment contains a second number of binary codes. Each binary data segment is converted to a digital identifier to obtain a corresponding numerical identifier. The character corresponding to each numerical identifier is sequentially searched in the URI table (also known as a URL-secure base64 encoding table), and the found characters are concatenated in order to obtain the second account.

[0083] As mentioned above, the first quantity can be equal to 8. In this embodiment of the invention, based on the principle of Uniform Resource Locator (URL) encoding, the second quantity can be set to 6.

[0084] A URL-safe base64 encoding table can include 26 uppercase and 26 lowercase Latin letters, the numbers 0-9, and the characters "_" and "-". Optionally, a URL-safe base64 encoding table can be as shown in Table 2 below:

[0085] Table 2

[0086] number character number character number character number character 0 A 16 Q 32 g 48 w 1 B 17 R 33 h 49 s 2 C 18 S 34 i 50 y 3 D 19 T 35 j 51 z 4 E 20 U 36 k 52 0 5 F 21 V 37 l 53 1 6 G 22 W 38 m 54 2 7 H 23 S 39 n 55 3 8 I 24 Y 40 o 56 4 9 J 25 Z 41 p 57 5 10 K 26 a 42 q 58 6 11 L 27 b 43 r 59 7 12 M 28 c 44 s 60 8 13 N 29 d 45 t 61 9 14 O 30 e 46 u 62 _ 15 P 31 f 47 v 63 -

[0087] Optionally, if the highest-order binary data segment is less than 6 bits when dividing the binary data segment, it can be padded with 0s in the high-order bits to ensure that each binary data segment after division includes 6 bits.

[0088] For example, assuming the application information includes an application identifier and an application version number, the order of the platform information field, application identifier field, application version number field, and hash account field in the data to be encoded can be as follows: Figure 5As shown in the diagram. Assume the data to be encoded includes an application identifier field and an application version number field. Assume the platform information field stores platform information as 1, the application identifier field stores application identifier as 16255, the application version number field stores application version number as 1, and the hash account field stores hash account as 2107896000369784. The binary representation of the application version number is 00000001, the binary representation of the platform information is 00000001, the binary representation of the application identifier is 00111111 01111111, and the binary representation of the hash account is: 00000111 01111101 00011110 11001000 01010011 0101010 001111000; Then, the target binary data is obtained by concatenating the binary data corresponding to the application version number, the application identifier, the platform information, and the hash account in sequence: 00000001 0011111101111111 00000001 00000111 01111101 00011110 11001000 01010011 0101010 001111000; Divide this target binary data into n data segments, each data segment containing 6 binary codes, and the resulting binary data segments are represented as: 000000 000100 111111 011111 110000 000100 000111011111 010001 111011 The binary data segments are divided into two parts: 001000 010100 110101 010001 111000. Further, each segment is converted to a digital identifier, resulting in the following numerical identifiers: 0 4 63 3148 47 31 17 59 8 20 53 17 56. Finally, the corresponding character for each number is found in the Uniform Resource Locator (URL) table, and these characters are concatenated in order to obtain the second account. The second account obtained after processing the binary data segments is: AE_fwEHfR7IU1R4.

[0089] As illustrated by the examples above, the second account generated in this embodiment of the invention is not a purely numerical account. During the application's business operation, it may be stored as the same as a function identifier within the application. For instance, in a game application, a purely numerical account may not be easily distinguishable from an in-game character identifier. This embodiment of the invention effectively avoids this situation, improving the convenience of account management within the application.

[0090] In one embodiment, in addition to the fields mentioned above, the data to be encoded may also include a Uniform Account Identifier (UAI) field and a blank field. The UAI field stores a UAI identifier, which identifies that the second account is generated after encoding an account from another platform. This field can occupy 24 bits and can represent a GopenID, such as... Figure 5 As shown in Figure 55; the blank field can occupy 32 bits to provide more information encoding space for different users. Normally, this blank field can be occupied by 0. This blank field can be represented as follows: Figure 5 As shown in Figure 56.

[0091] When encoding the information to be encoded, the contents of the above two fields, along with the contents of the platform information field, application information field, and hash account, are processed using Uniform Resource Locator (URL) encoding. The specific encoding process is the same as described above, and will not be repeated in this embodiment. Assuming the content of the GopenID field in the data to be encoded is GOID, the application version number is 1, the application identifier is 16255, the platform information is 1, the hash account is 2107896000369784, and the blank field is 0, the second account obtained by encoding the data to be encoded is: GOODAQAAP38AAAABAAAAAAAHfR7IU1R4.

[0092] Step S203: Log in to the application using the second account.

[0093] After obtaining the second account through steps S201-S203, the information processing device can log in to the application using the second account. The target user can then run the application, such as setting a nickname, setting an avatar, and using its functions. All operations performed by the target user within the application are stored by the information processing device using the second account, which can be considered the target user's unique account identifier within the application.

[0094] In one embodiment, after generating a second account, the present invention can also provide users with account binding / unbinding, account replacement, and account reset functions, etc. The account binding function means that after generating a second account for a target user, it can be seen as a binding relationship between the first and second accounts. The account unbinding function allows the target user to unbind the first and second accounts through a target terminal. The account replacement function allows users to bind another account to the second account; this account can be an account on the target platform or an account on another platform. In this way, a user can log in to the same application account through multiple different platform accounts, achieving interoperability between accounts. The account reset function can be understood as deleting the first account bound to the second account and adding a new account to bind to the second account.

[0095] In this embodiment of the invention, after receiving a login request for an application, the information processing device retrieves the first account assigned to the target user by the target platform from the login request. Then, it obtains the platform information of the target platform and the application information corresponding to the application. Further, based on the platform information, application information, and the first account, it performs encoding processing to obtain a target account with a length equal to the target length. Finally, it determines a second account for logging into the application based on the target account. As can be seen from the above steps, this embodiment of the invention does not directly use the first account assigned by the platform as the login account in the application. Instead, it processes the first account through encoding to obtain a second account of the target length, and then logs into the application using the second account. Compared with the prior art, this embodiment of the invention can ensure that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. Furthermore, the encoding process for the first account references platform information and application information, making the second account self-resolving. When decoding the second account subsequently, it can accurately locate which platform account the account was generated from, facilitating the management of the association between the platform and the application.

[0096] Based on the above information processing method, this embodiment of the invention provides another information processing method, see [link to relevant documentation]. Figure 6 This is a flowchart illustrating an information processing method provided in an embodiment of the present invention. Figure 6 The information processing method shown can be executed by an information processing device, specifically by the processor of the information processing device. Figure 6 The information processing method shown may include the following steps:

[0097] Step S601: Receive a login request for the application, which includes a first account assigned to the target user by the target platform.

[0098] Step S602: Obtain the platform information corresponding to the target platform and the application information corresponding to the application, and perform a hash operation on the first account to obtain the hash account.

[0099] In one embodiment, some feasible implementations included in steps S601-S602 can be found in [reference needed]. Figure 2 The descriptions of the relevant steps in the embodiments will not be repeated here.

[0100] Step S603: Check if the database stores an account that is the same as the hash account.

[0101] Step S604: If it does not exist, obtain the data to be encoded of the target length. The data to be encoded includes the platform information field, the application information field, and the hash account field. Based on the platform information, the application information, and the hash account, the data to be encoded is filled. The filled data to be encoded is then processed by Uniform Resource Locator (URL) encoding to obtain the second account.

[0102] In this embodiment of the invention, after the information processing device determines a second account each time, it stores the mapping relationship between the first account and the second account, the mapping relationship between the second account and platform information, and the mapping relationship between the second account, platform information, and hash account. This facilitates subsequent retrieval and provides a basis for account conflict prevention. Conflict prevention refers to avoiding the generation of the same second account for different users. Since the database stores the above multiple mapping relationships, after obtaining the hash account in step S604, it can first determine whether the hash account is already stored in the database. If not, it is determined that the hash account is unique, and then step S605 is executed; if the hash account already exists in the database, it means that the hash account is not unique, and step S602 can be returned to regenerate a new hash account.

[0103] The following section details how information processing devices store the aforementioned mapping relationships in a database. Each mapping relationship is stored in key-value pair format, specifically within a string structure in a Redis database.

[0104] The mapping relationship between the first account and the second account reflects that the first account and / or other accounts are bound to the second account. The first account and other accounts can be from different platforms or from the same platform. When storing the mapping relationship between the first account and the second account, the key data can be formatted as follows: key prefix + key suffix. Specifically, the key prefix can be represented as: <application identifier>:<platform information>:<account type GopenID_Type>, and the key suffix can be represented as: <g>or <o>Here, "account type" refers to the type of the second account, which is related to the hash operation. For example, if hash64 is used, then the account type can be considered as 2. "g" indicates that the value data stores the second account, and "0" indicates that the value data stores one first account or one first account and multiple other accounts. For example, assuming the application identifier is 1111, the platform information is 2222, the account type is 2, the first account is "foo", and the second account is "bar", then the mapping relationship between the first account and the second account can be 1111:2222:2:foo:g; or 1111:2222:2:bar:o.

[0105] Value data can be encoded using JSON. The entire value can be an Object, with each field stored as a member within the Object. Optionally, the contents of the value data are shown in Table 3 below:

[0106] Table 3

[0107] field name Field type meaning val string First account or second account ts uint32 Creation time pri uint32 Is it the primary account (the first account linked)? del uint32 Has it been deleted? chn string Application registration channels

[0108] The mapping relationship between platform information and the second account reflects how many accounts on the target platform are bound to the second account. When storing this mapping relationship, the key data can be formatted as: <Application Identifier>:<Account Type GopenID_Type>:<Second Account>:pfs, where pfs represents an end-of-file character and can be replaced with any symbol as needed in practice. For example, if the application identifier is 1111, the account type is 2, and the second account is bar, then the key data in the mapping relationship between the platform information and the second account can be represented as 1111:2:bar:pfs.

[0109] The value data can include platform information and the number of accounts on the target platform that are bound to the second account. If there is one account, the number is 1; if there are two accounts, the number is 2.

[0110] The mapping between platform information and hash accounts is used to indicate that multiple accounts on the target platform have the same hash account. This mapping is mainly used to prevent hash account conflicts. The key data of this type of mapping can be in the form of: <application identifier>:<account type>:<hash account>:pfs, and the value data of this mapping is the same as the hash data.

[0111] Based on the above description, the mapping relationship between the first account and the second account includes at least one first type of key-value pair and one second type of key-value pair. The first type of key-value pair stores the correspondence between the first account and the second account, and the second type of key-value pair stores the correspondence between the second account and the first account. As mentioned above, one first account can only correspond to one second account, and one second account can correspond to multiple first accounts. Therefore, the first type of key-value pair can include first key data and first value data. The first key data can include application information, platform information, and the first account, and the first value data includes the second account. The second type of key-value pair includes second key data and second value data. The second key data includes the application information, the platform information, and the second account, and the second value data includes the first account.

[0112] For example, suppose the application information includes an application identifier of 1111, platform information of 2222, and account type of 2. See [link / reference]. Figure 7a This is a schematic diagram illustrating the mapping relationship between a first account and a second account, provided by an embodiment of the present invention. 71 represents the mapping relationship between the first account and the second account, and 72 represents the mapping relationship between the second account and the first account. 71 includes two first-type key-value pairs: 71A represents first-type key data, and 71B represents first-type value data; 72A represents second-type key data, and 72B and 72C represent second-type value data. Each first-type key-value pair includes a binding relationship between the first account and the second account, for example, the first account 123456 is bound to the second account 1528698794, and the first account 7890 is also bound to the second account 1528698794. The mapping relationship between the first account and the second account can be represented by the following symbols: First account => Second account; 72 includes a second type of key-value pair, in which the value data includes two, and each value data includes the existence of a first account and a second account bound together. 72 indicates that the second account GOODA... is bound to the first account 1524575 and the first account 16878; The mapping relationship between the second account and the first account can be represented by the following symbols: Second account => First account.

[0113] In this embodiment of the invention, the second mapping relationship between platform information and the second account may include a third type of key-value pair, wherein the third type of key-value pair has a fourth key data and a fourth value data. The fourth key data includes an application identifier, the account type to which the second account belongs, and the second account. The fourth value data includes platform information and a target quantity, wherein the target quantity is used to indicate that there is a mapping relationship between the second account and a target quantity of accounts under the target platform. The mapping relationship between platform information and hash account may include a fourth type of key-value pair, wherein the fourth type of key-value pair includes a fifth key data and the fourth value data. The fifth key data includes the application identifier, the account type to which the second account belongs, and the hash account.

[0114] For example, see Figure 7b This invention provides a mapping relationship between platform information, a second account, and a hash account. 73 represents the mapping relationship between platform information and the second account, 74 represents the mapping relationship between platform information and the hash account, 73A represents the fourth type of key data, 73B represents the fourth type of value data, and 74A represents the fifth type of key data.

[0115] In one embodiment, as mentioned above, one second account can correspond to multiple first accounts, and the mapping relationship between the second account and the first account can be as follows: Figure 7a As shown in Figure 72, when the information processing device detects an event that adds a mapping relationship, it can determine how to add a mapping relationship between the second account and the new first account in the database based on whether the platform from which the new first account comes is the same as the target platform.

[0116] In specific implementation, if other platforms are the same as the target platform, a new second value is added to the second type of key-value pair. This new second value includes the target user's new first account on the other platform. The mapping relationship addition event is used to indicate the establishment of a mapping relationship between the new first account and the second account. If other platforms are different from the target platform, a new second type of key-value pair is added. This new second type of key-value pair includes third key data and third value data. The third key data includes the other platform information, the application information, and the second account. The third value data includes the new first account. In simpler terms, if other platforms are the same as the target platform, it means that two different accounts on one platform are bound to the same second account. In this case, the key data in the second type of key-value pair does not need to change; only a new value data needs to be added. However, if other platforms are different from the target platform, it means that the second account is bound to accounts on two different platforms. In this case, a new second type of value data needs to be created to store this binding relationship.

[0117] Step S605: If an account identical to the second account exists in the database, update the first account based on the second account and trigger step S602; if an account identical to the second account does not exist in the database, log in to the application using the second account.

[0118] Optionally, after determining in step S604 that no hash account exists in the database that matches the hash account, a second account can be generated based on the hash account. To further prevent conflicts and ensure the uniqueness of the second account, it can be further determined whether an account identical to the second account exists in the database. If it does not exist, the second account is used as the unique identifier for the target user in the application; if it does exist, the first account is updated based on the second account, and then the process returns to step S602 to obtain a new second account, until a unique second account is obtained. Specifically, updating the first account based on the second account can be done by concatenating the second account to the first account to obtain a new first account.

[0119] based on Figure 2 as well as Figure 6 The description in the embodiments of the present invention Figure 1 The account management system shown can be accessed through Figure 8 The diagram illustrates this. A target user can authorize login through multiple login platforms. Then, using the information processing method or unified account system provided in this embodiment, the first account assigned to the target user by each platform is converted into a second account with a fixed length. This second account is then applied to the corresponding application. As mentioned above, the unified account system in this embodiment supports multiple functions, including one or more of the following: account generation, anti-conflict detection, account binding / unbinding, account replacement, account reset, account encoding, account parsing, account pre-allocation, account cancellation, and account encryption. Account encryption refers to encrypting the second account after its generation before using it to log in to the application. After obtaining the second account, the information processing device can also store the account, the mapping relationship between platform information and the second account, and the mapping relationship between the first account and the second account, etc.

[0120] In this embodiment of the invention, upon receiving a login request for an application, the first account from the login request is obtained, and a hash operation is performed on the first account to obtain a hash account. Further, the database is checked to see if an account identical to the hash account is stored. If no identical account is found, the platform information of the target platform and the application information of the application are obtained. Then, the platform information, application information, and hash account are filled into the target length of data to be encoded. After filling, encoding is performed to obtain a second account. This ensures the uniqueness of the hash account in the database. Then, to further prevent conflicts between the generated second account and accounts already stored in the database, after obtaining the second account, the database is checked again to see if an account identical to the second account is stored. If no such account is found, the second account is used as the unique identifier for the target user in the application, and the second account is used to log in to the application. If the second account exists, the first account is updated, and the process of generating the second account is re-executed, effectively ensuring the uniqueness of the second account. Furthermore, compared with existing technologies, this embodiment of the invention ensures that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. In addition, during the encoding process of the first account, platform information and application information were referenced, which makes the second account self-resolving. When decoding the second account later, it is possible to accurately locate which platform account the account was generated from, which facilitates the management of the association between platforms and applications.

[0121] Based on the information processing method described above, embodiments of the present invention provide an information processing apparatus. See also... Figure 9 This is a schematic diagram of the structure of an information processing device provided in an embodiment of the present invention. Figure 9 The information processing device can operate the following units:

[0122] The receiving unit 901 is configured to receive a login request for an application, the login request including a first account assigned to a target user by the target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information;

[0123] The acquisition unit 902 is used to acquire platform information corresponding to the target platform and application information corresponding to the application.

[0124] Processing unit 903 is used to perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length;

[0125] The processing unit 903 logs into the application using the second account.

[0126] In one embodiment, when the processing unit 903 performs encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length, it executes the following steps:

[0127] The first account is hashed to obtain a hash account; the target length of data to be encoded is obtained, the data to be encoded includes a platform information field, an application information field, and a hash account field; the data to be encoded is filled based on the platform information, the application information, and the hash account, and the filled data to be encoded is then processed by Uniform Resource Locator (URL) encoding to obtain a second account.

[0128] In one embodiment, when the processing unit 903 performs a hash operation on the first account to obtain a hash account, it executes the following steps:

[0129] Obtain the hash operation size and hash value lookup table; perform a lookup process based on the first account to determine a sub-hash account from the hash value lookup table; if the number of sub-hash accounts is less than the hash operation size, update the first account to obtain a first updated account, and use the first updated account as the first account, triggering the step of performing a lookup process based on the first account; if the number of sub-hash accounts is equal to the hash operation size, concatenate multiple sub-hash accounts in the order of generation to obtain a hash account.

[0130] In one embodiment, the first account includes N characters, and the hash value lookup table includes M hash values, each hash value corresponding to an index identifier; when the processing unit 903 determines a sub-hash account from the hash value lookup table based on the first account, it performs the following steps:

[0131] The i-th character among the N characters is converted into a numerical value, and the i-th character after conversion is modulo M to obtain the first index identifier corresponding to the i-th character, where i is an integer greater than 1 and less than or equal to N; the initial hash value is determined from the M hash values ​​according to the first index identifier.

[0132] Obtain the target character currently being traversed from the N characters; perform an XOR operation between the target character and the initial hash value to obtain a second index identifier; and determine an update hash value from the M hash values ​​based on the second index identifier.

[0133] If each of the N characters has been traversed, the updated hash value is used as the sub-account; if there are untraversed characters among the N characters, the updated hash value is used as the initial hash value, and the step of obtaining the target character to be traversed from the N characters is triggered.

[0134] In one embodiment, when the processing unit 903 performs Uniform Resource Locator (URL) encoding on the data to be encoded after padding to obtain a second account, it performs the following steps:

[0135] The contents of each field of the data to be encoded after filling are converted into binary data, and the number of binary codes in each binary data is an integer multiple of the first number.

[0136] The target binary data is obtained by concatenating the individual binary data and dividing the target binary data into n binary data segments in order from the least significant bit to the most significant bit. Each binary data segment includes a second number of binary codes.

[0137] Each binary data segment is converted to a digital number to obtain a digital identifier corresponding to each binary data segment; the character corresponding to each digital identifier is sequentially searched in the Uniform Resource Locator (URL) table, and the found characters are concatenated in order to obtain the second account.

[0138] In one embodiment, the information processing device further includes a storage unit 904; the processing unit 903 is further configured to determine first mapping relationship information reflecting the mapping relationship between the first account and the second account; the storage unit 904 is configured to store the first mapping relationship information in a database; the first mapping relationship information includes at least one first type of key-value pair and one second type of key-value pair, each first type of key-value pair including first key data and first value data, the first key data including the application information, the platform information and the first account, and the first value data including the second account; the second type of key-value pair includes second key data and second value data, the second key data including the application information, the platform information and the second account, and the second value data including the first account.

[0139] In one embodiment, the processing unit 903 is further configured to:

[0140] When a mapping relationship addition event is detected, if other platforms are the same as the target platform, a new second value data is added to the second type of key-value pairs. The new second value data includes the target user's new first account on the other platform. The mapping relationship addition event is used to indicate the establishment of a mapping relationship between the new first account and the second account.

[0141] If other platforms are different from the target platform, a second type of key-value pair is added. The second type of key-value pair includes a third key data and a third value data. The third key data includes the other platform information, the application information, and the second account. The third value data includes the new first account.

[0142] In one embodiment, the determining unit 903 is further configured to determine a second mapping relationship between the platform information and the second account, and a third mapping relationship between the platform information and the hash account; the storage unit 904 is further configured to store the second mapping relationship information and the third mapping relationship in a database;

[0143] The second mapping relationship information includes a third type of key-value pair, which includes a fourth key data and a fourth value data. The fourth key data includes the application identifier, the account type to which the second account belongs, and the second account. The fourth value data includes the platform information and the target quantity. The target quantity is used to indicate that there is a target quantity of accounts in the target platform that have a mapping relationship with the second account.

[0144] The third type of mapping relationship includes a fourth type of key-value pair, which includes a fifth key data and the fourth value data. The fifth key data includes the application identifier, the account type to which the second account belongs, and the hash account.

[0145] In one embodiment, the processing unit 903 is further configured to determine whether the database stores an account that is the same as the hash account; if the database does not contain an account that is the same as the hash account, then the step of obtaining the data to be encoded of the target length is performed.

[0146] In one embodiment, the processing unit 903 is further configured to update the first account based on the second account if an account identical to the second account exists in the database, and trigger the step of performing a hash operation on the first account to obtain a hash account.

[0147] According to one embodiment of the present invention, Figure 2 as well as Figure 6 The information processing method shown can involve various steps that can be derived from... Figure 9 This is performed by the various units within the information processing apparatus shown. For example, Figure 2 The aforementioned step S201 can be performed by Figure 9 The receiving unit 901 in the information processing device described above performs the operation, and step S202 can be performed by... Figure 9 The information processing device shown is used to acquire unit 902 to perform step S203, which can be performed by... Figure 9 The information processing device shown executes this through processing unit 903; for example, Figure 6 The aforementioned step S601 can be performed by Figure 9 The receiving unit 901 in the information processing device executes steps S602 and S604, which can be performed by... Figure 9 The information processing device is executed by the acquisition unit 902, and steps S603 and S605 can be performed by... Figure 9 The information processing device is executed by the processing unit 903.

[0148] According to another embodiment of the present invention, Figure 9 The various units in the information processing device shown can be individually or entirely combined into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of the present invention. The above-mentioned units are divided based on logical functions. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of the present invention, the information processing device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0149] According to another embodiment of the present invention, the following can be performed by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM). Figure 2 and Figure 6 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 9 The information processing apparatus shown herein, and the information processing method for implementing embodiments of the present invention. The computer program may be recorded on, for example, a computer-readable storage medium, loaded onto the aforementioned computing device via the computer-readable storage medium, and run therein.

[0150] In this embodiment of the invention, after receiving a login request for an application, the information processing device retrieves the first account assigned to the target user by the target platform from the login request. Then, it obtains the platform information of the target platform and the application information corresponding to the application. Further, based on the platform information, application information, and the first account, it performs encoding processing to obtain a target account with a length equal to the target length. Finally, it determines a second account for logging into the application based on the target account. As can be seen from the above steps, this embodiment of the invention does not directly use the first account assigned by the platform as the login account in the application. Instead, it processes the first account through encoding to obtain a second account of the target length, and then logs into the application using the second account. Compared with the prior art, this embodiment of the invention can ensure that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. Furthermore, the encoding process for the first account references platform information and application information, making the second account self-resolving. When decoding the second account subsequently, it can accurately locate which platform account the account was generated from, facilitating the management of the association between the platform and the application.

[0151] Based on the above-described embodiments of the information processing method and the information processing apparatus, this invention provides an information processing device. See also... Figure 10 This is a schematic diagram of the structure of an information processing device provided in an embodiment of the present invention. Figure 10 The information processing device shown may include at least a processor 1001, an input interface 1002, an output interface 1003, and a computer storage medium 1004. The processor 1001, input interface 1002, output interface 1003, and computer storage medium 1004 may be connected via a bus or other means.

[0152] The computer storage medium 1004 can be stored in the memory of the information processing device. The computer storage medium 1004 is used to store computer programs, and the processor 1001 is used to execute the computer programs stored in the computer storage medium 1004. The processor 1001 (or CPU (Central Processing Unit)) is the computing and control core of the information processing device. It is suitable for implementing one or more computer programs, specifically for loading and executing one or more computer programs to achieve corresponding methods or functions.

[0153] In one embodiment, the processor 1001 described in this embodiment of the invention can be used to perform: receiving a login request for an application, the login request including a first account assigned to a target user by a target platform, the first account being generated by the target platform based on the target user's login information or target user terminal information on the target platform; obtaining platform information corresponding to the target platform and application information corresponding to the application, and performing encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; and logging into the application using the second account.

[0154] In this embodiment of the invention, after receiving a login request for an application, the information processing device retrieves a first account assigned to the target user by the target platform from the login request. Then, it obtains the platform information of the target platform and the application information corresponding to the application. Further, based on the platform information, application information, and the first account, it performs encoding processing to obtain a second account with a length equal to the target length. Finally, it logs into the application using this second account. As can be seen from the above steps, this embodiment of the invention does not directly use the first account assigned by the platform as the login account in the application. Instead, it processes the first account through encoding to obtain a second account of the target length, and then logs into the application using the second account. Compared with the prior art, this embodiment of the invention can ensure that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. Furthermore, the encoding process for the first account references the platform information and application information, making the second account self-resolving. When decoding the second account subsequently, it can accurately locate which platform account the account was generated from, facilitating the management of the association between the platform and the application.

[0155] This invention also provides a computer storage medium (memory), which is a memory device in an information processing device used to store programs and data. It is understood that the computer storage medium here can include both the built-in storage medium in the information processing device and extended storage media supported by the information processing device. The computer storage medium provides storage space that stores the operating system of the information processing device. Furthermore, this storage space also stores one or more computer programs suitable for loading and execution by the processor 1001. It should be noted that the computer storage medium here can be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer storage medium located remotely from the aforementioned processor.

[0156] In one embodiment, a computer program stored in a computer storage medium can be loaded and executed by a processor 1001 to achieve the aforementioned... Figure 2 as well as Figure 6 In the corresponding steps of the information processing method embodiment, in a specific implementation, one or more computer programs in the computer storage medium are loaded and executed by the processor 1001 as follows:

[0157] Receive a login request for an application, the login request including a first account assigned to a target user by a target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; obtain platform information corresponding to the target platform and application information corresponding to the application, and perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; log in to the application using the second account.

[0158] In one embodiment, when the processor 1001 performs encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length, it executes the following steps:

[0159] The first account is hashed to obtain a hash account; the target length of data to be encoded is obtained, the data to be encoded includes a platform information field, an application information field, and a hash account field; the data to be encoded is filled based on the platform information, the application information, and the hash account, and the filled data to be encoded is then processed by Uniform Resource Locator (URL) encoding to obtain a second account.

[0160] In one embodiment, when the processor 1001 performs a hash operation on the first account to obtain a hash account, it executes the following steps:

[0161] Obtain the hash operation size and hash value lookup table; perform a lookup process based on the first account to determine a sub-hash account from the hash value lookup table; if the number of sub-hash accounts is less than the hash operation size, update the first account to obtain a first updated account, and use the first updated account as the first account, triggering the step of performing a lookup process based on the first account; if the number of sub-hash accounts is equal to the hash operation size, concatenate multiple sub-hash accounts in the order of generation to obtain a hash account.

[0162] In one embodiment, the first account includes N characters, and the hash value lookup table includes M hash values, each hash value corresponding to an index identifier; when the processor 1001 determines a sub-hash account from the hash value lookup table based on the first account, it performs the following steps:

[0163] The i-th character among the N characters is converted into a numerical value, and the i-th character after conversion is modulo M to obtain the first index identifier corresponding to the i-th character, where i is an integer greater than 1 and less than or equal to N; the initial hash value is determined from the M hash values ​​according to the first index identifier.

[0164] Obtain the target character currently being traversed from the N characters; perform an XOR operation between the target character and the initial hash value to obtain a second index identifier; and determine an update hash value from the M hash values ​​based on the second index identifier.

[0165] If each of the N characters has been traversed, the updated hash value is used as the sub-account; if there are untraversed characters among the N characters, the updated hash value is used as the initial hash value, and the step of obtaining the target character to be traversed from the N characters is triggered.

[0166] In one embodiment, when the processor 1001 performs Uniform Resource Locator (URL) encoding on the padded data to obtain the second account, it executes the following steps:

[0167] The contents of each field of the data to be encoded after filling are converted into binary data, and the number of binary codes in each binary data is an integer multiple of the first number.

[0168] The target binary data is obtained by concatenating the individual binary data and dividing the target binary data into n binary data segments in order from the least significant bit to the most significant bit. Each binary data segment includes a second number of binary codes.

[0169] Each binary data segment is converted to a digital number to obtain a digital identifier corresponding to each binary data segment; the character corresponding to each digital identifier is sequentially searched in the Uniform Resource Locator (URL) table, and the found characters are concatenated in order to obtain the second account.

[0170] In one embodiment, after obtaining the second account, the processor 1001 is further configured to: determine first mapping relationship information reflecting the mapping relationship between the first account and the second account, and store the first mapping relationship information in a database;

[0171] The first mapping relationship information includes at least one first type of key-value pair and one second type of key-value pair. Each first type of key-value pair includes first key data and first value data. The first key data includes the application information, the platform information, and the first account, and the first value data includes the second account. The second type of key-value pair includes second key data and second value data. The second key data includes the application information, the platform information, and the second account, and the second value data includes the first account.

[0172] In one embodiment, the processor 1001 is further configured to perform: when a mapping relationship increase event is detected, if other platforms are the same as the target platform, add new second value data to the second type of key-value pairs, the new second value data including the target user's new first account on the other platform, and the mapping relationship increase event is used to indicate the establishment of a mapping relationship between the new first account and the second account;

[0173] If other platforms are different from the target platform, a second type of key-value pair is added. The second type of key-value pair includes a third key data and a third value data. The third key data includes the other platform information, the application information, and the second account. The third value data includes the new first account.

[0174] In one embodiment, the application information includes an application identifier, and after obtaining the second account, the processor 1001 is further configured to:

[0175] Determine the second mapping relationship between the platform information and the second account, and the third mapping relationship between the platform information and the hash account, and store the second mapping relationship and the third mapping relationship in the database;

[0176] The second mapping relationship information includes a third type of key-value pair, which includes a fourth key data and a fourth value data. The fourth key data includes the application identifier, the account type to which the second account belongs, and the second account. The fourth value data includes the platform information and the target quantity. The target quantity is used to indicate that there is a target quantity of accounts in the target platform that have a mapping relationship with the second account.

[0177] The third type of mapping relationship includes a fourth type of key-value pair, which includes a fifth key data and the fourth value data. The fifth key data includes the application identifier, the account type to which the second account belongs, and the hash account.

[0178] In one embodiment, before acquiring the data to be encoded of the target length, the processor 1001 is further configured to: determine whether the database stores an account that is the same as the hash account; if the database does not contain an account that is the same as the hash account, then perform the step of acquiring the data to be encoded of the target length.

[0179] In one embodiment, after obtaining the second account, the processor 1001 is further configured to perform the following steps: if an account identical to the second account exists in the database, update the first account based on the second account, and trigger the execution of a hash operation on the first account to obtain a hash account.

[0180] In this embodiment of the invention, after receiving a login request for an application, the information processing device retrieves a first account assigned to the target user by the target platform from the login request. Then, it obtains the platform information of the target platform and the application information corresponding to the application. Further, based on the platform information, application information, and the first account, it performs encoding processing to obtain a second account with a length equal to the target length. Finally, it logs into the application using this second account. As can be seen from the above steps, this embodiment of the invention does not directly use the first account assigned by the platform as the login account in the application. Instead, it processes the first account through encoding to obtain a second account of the target length, and then logs into the application using the second account. Compared with the prior art, this embodiment of the invention can ensure that the account length for logging into the application through various platforms is consistent, facilitating the management of application accounts. Furthermore, the encoding process for the first account references the platform information and application information, making the second account self-resolving. When decoding the second account subsequently, it can accurately locate which platform account the account was generated from, facilitating the management of the association between the platform and the application.

[0181] This invention provides a computer program product or computer program stored in a computer-readable storage medium. A processor of an information processing device reads the computer program from the computer-readable storage medium and executes the computer program, causing the information processing device to perform the aforementioned actions. Figure 2 or Figure 6 The illustrated information processing method embodiment. The computer-readable storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0182] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / o> < / g>

Claims

1. An information processing method, characterized in that, include: Receive a login request for the application, the login request including a first account assigned by the target platform to the target user, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; The platform information corresponding to the target platform and the application information corresponding to the application are obtained, and the platform information, the application information and the first account are encoded to obtain a second account of the target length; the first mapping relationship information used to reflect the mapping relationship between the first account and the second account includes a second type of key-value pair, the second type of key-value pair includes second key data and second value data, the second key data includes the application information, the platform information and the second account, and the second value data includes the first account; Log in to the application using the second account; When a mapping relationship addition event is detected, if the other platform is the same as the target platform, a new second value data is added to the second type of key-value pair. The new second value data includes the target user's new first account on the other platform. The mapping relationship addition event is used to indicate the establishment of a mapping relationship between the new first account and the second account. If the other platform is not the same as the target platform, a new second type of key-value pair is added. The new second type of key-value pair includes third key data and third value data. The third key data includes the other platform information, the application information, and the second account. The third value data includes the new first account.

2. The method as described in claim 1, characterized in that, The process of encoding based on the platform information, the application information, and the first account to obtain a second account of the target length includes: Perform a hash operation on the first account to obtain a hash account; Obtain the data to be encoded of the target length, the data to be encoded including platform information field, application information field and hash account field; The data to be encoded is filled based on the platform information, the application information, and the hash account, and then the filled data to be encoded is processed by Uniform Resource Locator (URL) encoding to obtain the second account.

3. The method as described in claim 2, characterized in that, The step of performing a hash operation on the first account to obtain a hash account includes: Obtain the hash value mapping table for the hash operation; Based on the first account, a table lookup process is performed to determine a sub-hash account from the hash value lookup table; If the number of sub-hash accounts is less than the size of the hash operation, then the first account is updated to obtain the first updated account, and the first updated account is used as the first account, and the step of performing a table lookup based on the first account is triggered. If the number of sub-hash accounts is equal to the size of the hash operation, then the multiple sub-hash accounts are concatenated in the order of generation to obtain the hash account.

4. The method as described in claim 3, characterized in that, The first account consists of N characters, and the hash value lookup table consists of M hash values, each hash value corresponding to an index identifier; The step of determining a sub-hash account from the hash value lookup table based on the first account includes: The i-th character among the N characters is converted into a numerical value, and the i-th character after conversion is modulo M to obtain the first index identifier corresponding to the i-th character, where i is an integer greater than 1 and less than or equal to N; An initial hash value is determined from the M hash values ​​based on the first index identifier; Obtain the target character currently being traversed from the N characters; The target character is XORed with the initial hash value to obtain a second index identifier, and an update hash value is determined from the M hash values ​​based on the second index identifier; If each of the N characters is traversed, then the updated hash value is used as the sub-account; If there are untraversed characters among the N characters, the updated hash value is used as the initial hash value, and the step of obtaining the target character to be traversed from the N characters is triggered.

5. The method as described in claim 2, characterized in that, The process of performing Uniform Resource Locator (URL) encoding on the padded data to obtain the second account includes: The contents of each field of the data to be encoded after filling are converted into binary data, and the number of binary codes in each binary data is an integer multiple of the first number. The target binary data is obtained by concatenating the individual binary data and dividing the target binary data into n binary data segments in order from the least significant bit to the most significant bit. Each binary data segment includes a second number of binary codes. Each binary data segment is converted to a digital number to obtain a digital identifier corresponding to each binary data segment; The second account is obtained by sequentially searching for the character corresponding to each numeric identifier in the Uniform Resource Locator (URL) table and then concatenating the found characters in order.

6. The method as described in claim 1, characterized in that, After obtaining the second account, the method further includes: Determine first mapping relationship information that reflects the mapping relationship between the first account and the second account, and store the first mapping relationship information in the database; The first mapping relationship information also includes at least one first type of key-value pair. Each first type of key-value pair includes first key data and first value data. The first key data includes the application information, the platform information, and the first account. The first value data includes the second account.

7. The method as described in claim 2, characterized in that, The application information includes an application identifier. After obtaining the second account, the method further includes: Determine the second mapping relationship between the platform information and the second account, and the third mapping relationship between the platform information and the hash account, and store the second mapping relationship and the third mapping relationship in the database; The second mapping relationship information includes a third type of key-value pair, which includes a fourth key data and a fourth value data. The fourth key data includes the application identifier, the account type to which the second account belongs, and the second account. The fourth value data includes the platform information and the target quantity. The target quantity is used to indicate that there is a target quantity of accounts in the target platform that have a mapping relationship with the second account. The third type of mapping relationship includes a fourth type of key-value pair, which includes a fifth key data and the fourth value data. The fifth key data includes the application identifier, the account type to which the second account belongs, and the hash account.

8. The method as described in claim 2, characterized in that, Before obtaining the data to be encoded of the target length, the method further includes: Determine whether the database stores an account that is the same as the hash account; If no account with the same hash account exists in the database, then the step of obtaining the data to be encoded of the target length is performed.

9. The method as described in claim 2 or 8, characterized in that, After obtaining the second account, the method further includes: If an account identical to the second account exists in the database, the first account is updated based on the second account, and the step of performing a hash operation on the first account to obtain a hash account is triggered.

10. An information processing device, characterized in that, include: The receiving unit is configured to receive a login request for an application, the login request including a first account assigned to a target user by the target platform, the first account being generated by the target platform based on the target user's login information on the target platform or the target user's terminal information; The acquisition unit is used to acquire platform information corresponding to the target platform and application information corresponding to the application. The processing unit is configured to perform encoding processing based on the platform information, the application information, and the first account to obtain a second account of a target length; the first mapping relationship information reflecting the mapping relationship between the first account and the second account includes a second type of key-value pair, the second type of key-value pair includes second key data and second value data, the second key data includes the application information, the platform information, and the second account, and the second value data includes the first account; The processing unit is also configured to log in to the application using the second account; The processing unit is further configured to, when a mapping relationship addition event is detected, add new second value data to the second type of key-value pair if the other platform is the same as the target platform, the new second value data including the new first account of the target user on the other platform, and the mapping relationship addition event is used to indicate the establishment of a mapping relationship between the new first account and the second account; if the other platform is not the same as the target platform, add new second type of key-value pair, the new second type of key-value pair including third key data and third value data, the third key data including the other platform information, the application information and the second account, and the third value data including the new first account.

11. An information processing device, characterized in that, include: A processor, adapted to implement one or more instructions; as well as, A computer storage medium storing one or more computer programs, said one or more computer programs being adapted to be loaded by said processor and executed as described in any one of claims 1-9.

12. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, is used to perform the information processing method as described in any one of claims 1-9.

13. A computer program product, characterized in that, The computer program product includes a computer program stored in a computer-readable storage medium, and the processor of the information processing device reads from the computer-readable storage medium and executes the computer program, causing the information processing device to perform the information processing method as described in any one of claims 1-9.

Images