Information processing method, device, equipment and storage medium

Abstract

The present application discloses an information processing method, the method comprising: receiving a target information identifier sent by a first device; sending the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is the user identifier of the target object in the first device; receiving a first user identifier sent by the first device; the first user identifier is the user identifier of the target object in the target second device; receiving a second user identifier sent by the first device; sending the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier. The present application also provides an information processing device, a device and a storage medium. The information processing method provided by the present application can avoid the problem that multiple third-party platforms cannot synchronously obtain accounts of instant messaging software.

Description

Technical Field

[0001] The present application relates to the field of information processing, and relates to but is not limited to an information processing method, apparatus, device and storage medium. Background Art

[0002] In the related art, when a user logs in to multiple third-party platforms through an instant messaging software account, the instant messaging software sends the instant messaging software account to the multiple third-party platforms respectively, so that the user can log in to the multiple third-party platforms through the instant messaging software account. In this way, when the instant messaging software sends the instant messaging software account to the multiple third-party platforms respectively, since there are multiple third-party platforms, the multiple third-party platforms will not be able to synchronously obtain the instant messaging software account. Summary of the invention

[0003] The embodiments of the present application provide an information processing method, apparatus, device and storage medium to solve at least one problem existing in the related art, which can avoid the problem that multiple third-party platforms cannot synchronously obtain accounts of instant messaging software.

[0004] The technical solution of this application is implemented as follows:

[0005] In a first aspect, an embodiment of the present application provides an information processing method, which is applied to a docking device, and the method includes:

[0006] Receiving a target information identifier sent by a first device;

[0007] Sending the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is a user identifier of the target object in the first device;

[0008] receiving a first user identifier sent by the first device; the first user identifier being a user identifier of the target object in the target second device;

[0009] receiving the second user identifier sent by the first device;

[0010] The first user identifier and the second user identifier are sent to the target second device, so that the target second device binds the first user identifier and the second user identifier.

[0011] In a second aspect, an embodiment of the present application provides an information processing method, which is applied to a target second device, and the method includes:

[0012] Receive a target information identifier sent by a docking device and display the target information identifier; the target information identifier is used to receive a scanning event, the scanning event is used by the first device to obtain a second user identifier, the second user identifier is a user identifier of the target object in the first device;

[0013] receiving a first user identifier and a second user identifier sent by the docking device; the first user identifier is a user identifier of the target object in the target second device;

[0014] Bind the first user identifier and the second user identifier.

[0015] In a third aspect, an embodiment of the present application provides a docking device, the docking device comprising:

[0016] A first receiving unit, configured to receive a target information identifier sent by a first device;

[0017] A first sending unit, configured to send the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is a user identifier of the target object in the first device;

[0018] A second receiving unit is configured to receive a first user identifier sent by the first device; the first user identifier is a user identifier of the target object in the target second device;

[0019] A third receiving unit, configured to receive the second user identifier sent by the first device;

[0020] The second sending unit is configured to send the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier.

[0021] In a fourth aspect, an embodiment of the present application provides a target second device, wherein the target second device includes:

[0022] a fourth receiving unit, configured to receive a target information identifier sent by the docking device and display the target information identifier; the target information identifier is used to receive a scanning event, the scanning event is used by the first device to obtain a second user identifier, the second user identifier being a user identifier of the target object in the first device;

[0023] A fifth receiving unit, configured to receive the first user identifier and the second user identifier sent by the docking device; the first user identifier is the user identifier of the target object in the target second device;

[0024] A binding unit is used to bind the first user identifier and the second user identifier.

[0025] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the information processing method described in any one of the above items is implemented.

[0026] In a sixth aspect, an embodiment of the present application provides a storage medium storing a computer program, which, when executed by a processor, implements any of the information processing methods described above.

[0027] The embodiment of the present application provides an information processing method, apparatus, device and storage medium, wherein the docking device receives a target information identifier sent by a first device; sends the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; receives a first user identifier sent by the first device, and receives a second user identifier sent by the first device, and then sends the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier, wherein the first user identifier is the user identifier of the target object in the target second device, and the second user identifier is the user identifier of the target object in the first device. In this way, in the process of docking the first device with the target second device, the first device first sends the first user identifier and the second user identifier to the docking device, and the docking device then sends the received first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier, thereby completing the docking of the first device with the target second device. In this way, since a docking device is added, during the docking process, the first user identifier and the second user identifier can be first sent to the docking device, and then the first user identifier and the second user identifier can be sent to the target second device through the docking device, so that the first device can be docked with the target second device through the docking device, thereby avoiding the problem that during the docking process between the first device and at least one second device, the at least one second device cannot synchronously obtain the second user identifier due to the at least one second device. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1A An optional structural diagram of an information processing system provided in an embodiment of the present application;

[0029] Figure 1B An optional structural diagram of an information processing system provided in an embodiment of the present application;

[0030] Figure 1C An optional structural diagram of an information processing system provided in an embodiment of the present application;

[0031] Figure 2 An optional flowchart of the information processing method provided in the embodiment of the present application;

[0032] Figure 3 An optional flowchart of the information processing method provided in the embodiment of the present application;

[0033] Figure 4 An optional flowchart of the information processing method provided in the embodiment of the present application;

[0034] Figure 5 An optional flowchart of the information processing method provided in the embodiment of the present application;

[0035] Figure 6 An optional flowchart of the information processing method provided in the embodiment of the present application;

[0036] Figure 7 An optional structural diagram of a docking device provided in an embodiment of the present application;

[0037] Figure 8 An optional structural diagram of a target second device provided in an embodiment of the present application;

[0038] Fig. 9 An optional structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the specific technical solution of the application will be further described in detail below in conjunction with the drawings in the embodiments of the present application. The following embodiments are used to illustrate the embodiments of the present application, but are not used to limit the scope of the embodiments of the present application.

[0040] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art of the technical field of the embodiments of the present application. The terms used herein in the specification of the embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to limit the embodiments of the present application. The term "and / or" used herein includes any and all combinations of one or more related listed items.

[0041] Before further explaining the present application in detail, the nouns and terms involved in the embodiments of the present application are explained. The nouns and terms involved in the embodiments of the present application are subject to the following interpretations.

[0042] 1) The first device is a device with a first application (Application, APP) installed, wherein the first APP may be an instant messaging software.

[0043] 2) The second device is a device with a second APP installed. The second APP is different from the first APP, and the user can log in to the second APP through the account of the first APP. For example, the second APP is a software for playing videos, and the first APP is an account of an instant messaging software. The user can log in to the software for playing videos through the account of the instant messaging software.

[0044] 3) A docking device is used to dock the first device with the second device. The first device sends the account number of the first APP and the account number of the second APP to the docking device, and the docking device then sends the account number of the first APP and the account number of the second APP to the second device, thereby avoiding the first device directly sending the account number of the second APP to the second device.

[0045] The information processing method provided in the embodiment of the present application can be applied to Figure 1A , Figure 1B or Figure 1C The information processing system 100 shown in FIG. Figure 1A As shown, the information processing system 100 includes: a first device 101, a second device 102, a docking device 103 and a network 104. The first device 101 and the docking device 103 communicate via the network 104, and the docking device 103 and the second device 102 communicate via the network 103.

[0046] In the embodiment of the present application, the docking device can be integrated with the first device, or the docking device can be integrated with the second device, and the embodiment of the present application does not impose any limitation on this.

[0047] like Figure 1B As shown, the information processing system 100 includes: a first device 101, multiple second devices 102, a docking device 103 and a network 104.

[0048] In the embodiment of the present application, when the information processing system includes only one second device, the second device is the target second device; when the information processing system includes at least one second device, the target second device is any second device of the at least one second device.

[0049] like Figure 1CAs shown, the information processing system 100 includes: a first device 101, at least one second device 102 and a docking device 103. The second device has a second APP installed, and a user 105 can operate a page provided by the second APP, wherein multiple users can operate the page provided by the second APP, wherein multiple users are, for example, Figure 1C User 1, User 2, and User 3 are shown.

[0050] The present application is further described in detail below through the accompanying drawings and specific embodiments.

[0051] Figure 2 A flowchart of an information processing method provided in an embodiment of the present application is provided, and the method is applied to a docking device, such as Figure 2 As shown, the method may include the following steps:

[0052] S201: The docking device receives a target information identifier sent by the first device.

[0053] Here, the target information identifier is an identifier displayed by the target second device to the target object, and the identifier carries a first user identifier, which is the user identifier of the target object in the target second device. For example, the first user identifier is the identity document (ID) in the second APP installed by the target object in the target second device. The target object is an object using the target second device, and the object can be a user.

[0054] In the embodiment of the present application, the target information identifier can be a QR code displayed by the target second device to the user, or it can be a barcode displayed by the target second device to the user. The embodiment of the present application does not impose any limitation on this.

[0055] In one example, the target information identifier is a QR code displayed to the user by the target second device, the second APP is a video player software, and the QR code carries the ID of the user's video player software.

[0056] In the embodiment of the present application, the docking device calls a callback interface and receives the target information identifier sent by the first device through the callback interface.

[0057] In actual applications, the docking device is used to dock the first device and the target second device. After the docking device receives the QR code carrying the user's video playback software ID sent by the first device, the received QR code is sent to the target second device so that the target second device displays the QR code to the user.

[0058] S202: The docking device sends the target information identifier to a target second device among at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device.

[0059] Here, the second user identification is the user identification of the target object in the first device.

[0060] In one example, the second user identifier is an ID in a first APP installed by the target object in the first device.

[0061] In an embodiment of the present application, a method for generating a second user identifier is that after the docking device sends the target information identifier to the target second device, the target second device displays the target information identifier to the target object. After the target object scans the target information identifier, the first device will obtain a scanning event that the target object has scanned the target information identifier, and after obtaining the scanning event, determine the second user identifier corresponding to the first user identifier based on the first user identifier carried by the target information identifier.

[0062] The second APP installed in each of the at least one second device may be the same or different, and this embodiment of the present application does not impose any limitation on this.

[0063] The target second device is any second device among the at least one second device. The target second device may have one second APP installed or multiple second APPs installed, and the embodiment of the present application does not impose any limitation on this.

[0064] S203: The docking device receives a first user identifier sent by the first device.

[0065] Here, the first user identifier is the user identifier of the target object in the target second device.

[0066] Here, the first user identifier can be the first user identifier input by the target object on the target second device and received by the first device, or it can be the first user identifier carried by the target information identifier obtained by the first device from the target information identifier after the target object scans the target information identifier. The embodiments of the present application do not impose any limitations on this.

[0067] For the first user identifier, which is the first user identifier input by the target object on the target second device and received by the first device, the target object may first input the first user identifier on the target second device, that is, the target second device receives the first user identifier input by the target object and sends the input first user identifier to the first device; after the first device receives the input first user identifier, the input first user identifier is sent to the docking device, so that the docking device receives the first user identifier input by the target object on the target second device and sent by the first device.

[0068] The first user identifier is the first user identifier carried in the target information identifier obtained by the first device after the target object scans the target information identifier. The target object may first scan the target information identifier displayed by the target second device, and after the scan, the target second device sends a scanning event indicating that the target object has scanned the target information identifier to the first device, and the first device then obtains the first user identifier carried by the target information identifier from the target information identifier.

[0069] S204: The docking device receives the second user identifier sent by the first device.

[0070] Here, after obtaining the second user identifier, the first device may send the second user identifier to the docking device through a callback interface between the first device and the docking device, so that the docking device receives the second user identifier sent by the first device.

[0071] S205: The docking device sends the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier.

[0072] Here, after receiving the first user identifier and the second user identifier, the docking device forwards the first user identifier and the second user identifier to the target second device, so that the target second device can bind the first user identifier and the second user identifier.

[0073] The embodiment of the present application provides an information processing method, wherein a docking device receives a target information identifier sent by a first device; sends the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; receives a first user identifier sent by the first device, and receives a second user identifier sent by the first device, and then sends the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier, wherein the first user identifier is the user identifier of the target object in the target second device, and the second user identifier is the user identifier of the target object in the first device. In this way, in the process of docking the first device with the target second device, the first device first sends the first user identifier and the second user identifier to the docking device, and the docking device then sends the received first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier, thereby completing the docking of the first device with the target second device. In this way, since a docking device is added, during the docking process, the first user identifier and the second user identifier can be first sent to the docking device, and then the first user identifier and the second user identifier can be sent to the target second device through the docking device, so that the first device can be docked with the target second device through the docking device, thereby avoiding the problem that during the docking process between the first device and at least one second device, the at least one second device cannot synchronously obtain the second user identifier due to the at least one second device.

[0074] In some embodiments, the method further includes: the docking device receiving a first request sent by the target second device, and sending the first request to the first device.

[0075] Here, the first request includes a first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier.

[0076] After the docking device sends the first request to the first device, the above S201 includes: the docking device receives the target information identifier sent by the first device for responding to the first request.

[0077] In an embodiment of the present application, after the user operates the page of the second APP, the target second device will generate a first request based on the user's operation, and after generating the first request, send the generated first request to the docking device, so that the docking device receives the first request sent by the target second device.

[0078] In one example, a user clicks a "Request Login / Bind" button on the interface of a second APP. The target second device will generate a first request for generating a target information identifier based on the user's click operation, and send the generated first request to the docking device, so that the docking device receives the first request sent by the target second device.

[0079] In some embodiments, the method further includes: the docking device receiving target interface information sent by the target second device.

[0080] Here, the target interface information corresponds to the target second device, and the target interface information is information of the target interface, and is used to characterize the target interface between the target second device and the docking device.

[0081] After receiving the target interface information, the docking device can send the first user identifier and the second user identifier received from the first device to the target second device through the target interface between the docking device and the target second device, so that the docking device and the target second device are docked.

[0082] In the embodiment of the present application, each second device in the at least one second device includes interface information, and each second device can be docked with the docking device through the interface between the second device represented by the interface information.

[0083] After the docking device receives the target interface information sent by the target second device, Figure 3 As shown, the above S205 includes:

[0084] S301: The docking device searches for the target interface information according to the first user identifier.

[0085] S302: The docking device calls a target interface corresponding to the target interface information according to the target interface information, and sends the first user identifier and the second user identifier to the target second device through the target interface.

[0086] Here, a first user identifier corresponds to a target interface information. The docking device searches for the target interface information based on the first user identifier. After determining the target interface information, the docking device calls the target interface corresponding to the target interface information based on the target interface information, and sends the first user identifier and the second user identifier to the target second device through the target interface.

[0087] In some embodiments, the above S204 includes: receiving the second user identifier through a callback interface.

[0088] Here, the docking device may receive the second user identifier sent by the first device through a callback interface.

[0089] Figure 4 FIG. 1 is a schematic diagram of an implementation flow of a data transmission method according to an embodiment of the present application. The method is applied to a target second device, such as Figure 4 As shown, the method may include the following steps:

[0090] S401: The target second device receives a target information identifier sent by a docking device, and displays the target information identifier.

[0091] Here, the target information identifier is used to receive a scanning event, and the scanning event is used by the first device to obtain a second user identifier, where the second user identifier is a user identifier of the target object in the first device.

[0092] After receiving the target information identifier sent by the first device, the docking device sends the received target information to the target second device, so that the target second device receives the target information identifier sent by the docking device and displays the target information identifier to the target object.

[0093] After the target second device displays the target information identifier to the target object, the target object can scan the target information identifier through the device. After the target object scans, the first device will obtain the user's scanning result, which includes: the target object has followed the second APP installed in the target second device, or the target object has not followed the second APP installed in the target second device. If the target object has followed the second APP, the first device sends the first user identifier and the second user identifier to the docking device; if the target object has not followed the second APP, the first device sends the scanning result that the target object has not followed the second APP to the target second device, so that the target second device displays the request interface for requesting the target object to follow the second APP to the target object.

[0094] S402: The target second device receives the first user identifier and the second user identifier sent by the docking device.

[0095] Here, the first user identifier is the user identifier of the target object in the target second device.

[0096] After receiving the first user identifier and the second user identifier sent by the first device, the docking device sends the first user identifier and the second user identifier to the target second device, so that the target second device receives the first user identifier and the second user identifier sent by the docking device.

[0097] S403: The target second device binds the first user identifier and the second user identifier.

[0098] Here, after receiving the first user identifier and the second user identifier, the target second device can bind the first user identifier and the second user identifier so that the second APP installed on the target second device can be logged in according to the second user identifier.

[0099] In some embodiments, the method further includes: the target second device sending a first request to the docking device.

[0100] Here, the first request includes the first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier.

[0101] After the user operates the interface of the second APP, the target second device will generate a first request based on the user's operation, and send the generated first request to the docking device.

[0102] In one example, the user clicks the "Request Login / Bind" button on the interface of the second APP. The target second device will generate a first request for generating a target information identifier based on the user's click operation, and send the generated first request to the docking device.

[0103] In some embodiments, the method further includes: the target second device sending target interface information to the docking device.

[0104] Here, the target interface information corresponds to the target second device, and the target interface information is used by the docking device to send the first user identifier and the second user identifier to the target second device.

[0105] After the target second device sends the target interface information to the docking device, the target second device and the docking device can be docked via the target interface corresponding to the target interface information.

[0106] In some embodiments, Figure 5 As shown, the information processing method provided in the embodiment of the present application may include the following steps:

[0107] S501: The docking device receives a target information identifier sent by a first device.

[0108] S502: The docking device sends the target information identifier to a target second device among at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device.

[0109] S503: The target second device receives the target information identifier sent by the docking device; and displays the target information identifier.

[0110] S504: The docking device receives a first user identifier sent by the first device.

[0111] S505: The docking device receives the second user identifier sent by the first device.

[0112] S506: The docking device sends the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier.

[0113] S507: The target second device receives the first user identifier and the second user identifier sent by the docking device.

[0114] S508: The target second device binds the first user identifier and the second user identifier.

[0115] Among them, for the description of S501, please refer to the description of S201 in the above embodiment; for the description of S502, please refer to the description of S202 in the above embodiment; for the description of S503, please refer to the description of S401 in the above embodiment; for the description of S504, please refer to the description of S203 in the above embodiment; for the description of S505, please refer to the description of S204 in the above embodiment; for the description of S506, please refer to the description of S205 in the above embodiment; for the description of S507, please refer to the description of S402 in the above embodiment; for the description of S508, please refer to the description of S403 in the above embodiment.

[0116] The information processing method provided in the embodiments of the present application is as follows: Figure 6 As shown, including:

[0117] S601: The target second device receives a user operation and generates a first request.

[0118] Here, the target second device may generate the first request based on an operation performed by the user on the page of the second APP.

[0119] S602: The target second device sends the first request to the docking device.

[0120] Here, the first request includes a first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier.

[0121] S603: The docking device sends the first request to the first device.

[0122] S604: The first device generates a target information identifier in response to the first request.

[0123] S605: The first device sends the target information identifier to the docking device.

[0124] S606: The docking device sends the target information identifier to the target second device, so that the target second device displays the target information identifier to the user.

[0125] S607: The first device sends the first user identifier and the second user identifier to the docking device based on a scanning event in which the user scans the displayed target information identifier.

[0126] S608: The docking device sends the first user identifier and the second user identifier to a target second device.

[0127] S609: The target second device binds the first user identifier and the second user identifier.

[0128] Below, taking the second APP as a video playback software as an example, the information processing method provided in the embodiment of the present application is introduced.

[0129] With the development of Internet technology, information has exploded, and various platforms have emerged one after another. Under the wave of mobile Internet, terminal devices have gradually become an indispensable part of people's lives. However, there are serious "login barriers" between different platforms. Users need to complete registration and login every time they use a platform. In particular, different platforms of the same Internet manufacturer cannot bind multiple accounts, which brings a very poor experience to users. In this context, the interconnection and interoperability of accounts between various platforms needs to be solved urgently, which can not only facilitate user login, but also contribute to the drainage of various platforms. Logging in by scanning the code through the mobile phone APP is a relatively popular login method at present, which can not only save the tedious process of users entering passwords, but also improve security performance to a certain extent.

[0130] As a widely used social software, instant messaging software is preferred by major platforms as an account binding object due to its huge number of users. You can directly log in to the platform by scanning the code through the instant messaging software. The current mainstream instant messaging software scanning code binding and login are widely used by major platforms due to their large number of users and high activity. At the same time, the instant messaging software public platform provides complete interfaces and technical documents so that developers can quickly access and use them. The solution of using the instant messaging software public platform with QR code to realize account binding and login is relatively mature. The specific process is: the access platform creates a QR code with parameters through the instant messaging software public platform and sends it to the user. During the user scanning the code, the instant messaging software public platform notifies the access platform of the user scanning event, and the access platform realizes account binding and login in this process.

[0131] The existing account binding and login solution based on scanning QR code of instant messaging software requires each business platform to connect with the public platform of instant messaging software respectively, which has the following problems:

[0132] First, an instant messaging software public platform can only be configured with one server address, and multiple platforms that share the same instant messaging software enterprise account cannot receive event callbacks from the instant messaging software public platform separately.

[0133] Second, the instant messaging software public platform interface call requires a global access token (Access Token). This value is only valid for two hours and is generally cached locally on the platform. And multiple platforms that share the same instant messaging software enterprise account cannot synchronously obtain a valid Access Token call interface. In other words, after the instant messaging software public platform generates an Access Token through the App ID and application password (App Secret), the instant messaging software public platform calls the callback interface configured by the instant messaging software public platform to notify the third-party platform of the user's identity using the instant messaging software. The user's identity can be represented by the open Id, but once the Access Token is refreshed, the previous Access Token will become invalid. If multiple platforms access it, the newly refreshed Access Token will replace the previous Access Token.

[0134] Third, multiple platforms are connected to the public platform of instant messaging software separately, which requires repeated development and is too cumbersome.

[0135] Fourth, the App ID and App Secret of the instant messaging software public platform are exposed on multiple platforms, posing certain security risks.

[0136] There are strict procedures and quantity requirements for applying for instant messaging software enterprise accounts, so how to support multi-platform account binding and login with only one instant messaging software enterprise account cannot be solved in the existing technology. This application proposal overcomes the problems existing in the docking process of the existing solution, uses an intermediate platform to uniformly dock the instant messaging software public platform, and provides external services such as creating QR codes, scanning codes to bind accounts and login, realizing a multi-platform access method based on instant messaging software account binding and login.

[0137] Based on the above problems, this application proposes an information processing method, which innovatively adds a support platform to the "user-third-party platform-instant messaging software public platform" account binding scheme, and adjusts the overall framework to "user-third-party platform-support platform-instant messaging software public platform". When the third-party platform needs to implement account binding and login based on instant messaging software, it no longer needs to connect with the instant messaging software public platform, but can directly connect with the support platform. On the one hand, it is more convenient to use, and on the other hand, the support platform can support multiple third-party platforms, solving the problem that an instant messaging software enterprise account cannot connect to multiple platforms, and enhancing the flexibility of use. Among them, the third-party platform can be set in the target second device, the instant messaging software public platform can be set in the first device, and the support platform can be set in the docking device.

[0138] The specific steps of the information processing method proposed in this application are as follows:

[0139] After receiving the user binding / login request, the third-party platform can apply to the support platform to generate a QR code, which carries user information (i.e., the first user identifier described in the above embodiment) and callback interface information (i.e., the target interface information described in the above embodiment). After receiving the request from the third-party platform, the support platform uses the user information as a parameter to apply to the instant messaging software public platform to create a QR code with parameters. After the instant messaging software public platform generates the QR code with parameters, the support platform transmits it to the third-party platform. At the same time, the support platform caches user information, third-party platform callback interface and other information for use when the user scans the code; the third-party platform can then display the generated QR code to the user.

[0140] After the user scans the code using the instant messaging software, the instant messaging software public platform directly returns the scan result. If the user does not follow the corresponding instant messaging software public account, he needs to follow the instant messaging software public account. After the instant messaging software server receives the code scanning event, it automatically calls back the callback interface configured in the instant messaging software public platform to notify the support platform and inform the scanning user of the open ID of the instant messaging software (i.e., the second user identifier described in the above embodiment). The support platform takes the user information and callback interface information of the third-party platform from the cache, and continues to notify the third-party platform of the user information and the instant messaging software user open ID by calling the interface. The third-party platform performs the account binding / login operation and replies to the support platform, and then replies to the instant messaging software public platform. The third-party platform returns the user account binding / login status to the user.

[0141] From the above method, we can see that the existence of the support platform simplifies the process of third-party platforms to implement instant messaging software account binding and code scanning login, and there is no need for each third-party platform to connect with the instant messaging software public platform. The support platform is responsible for connecting with the instant messaging software public platform, which also avoids the leakage of information such as App ID and App Secret of the instant messaging software public platform account, the invalid refresh of the instant messaging software public account Access Token, and solves the problem that the instant messaging software public platform cannot configure multiple callbacks.

[0142] The support platform plays a key role in this application for the following reasons:

[0143] 1. Internally, the support platform has completed the connection with the public platform of instant messaging software, and the authorization information of the public platform of instant messaging software is uniformly placed on the support platform for maintenance and management, which solves the security risks of multiple platforms maintaining and connecting with the public platform of instant messaging software, and the problem of invalidation caused by multiple platforms requesting Access Token. The support platform encapsulates the various capabilities of the public platform of instant messaging software, completes the function of generating QR codes with parameters, and receives and processes the callback of the scan code event of the public platform of instant messaging software.

[0144] 2. Externally, the support platform exposes the ability to create QR codes with parameters. Each platform can complete the generation of QR codes by calling the support platform API interface. As long as the interface call and authentication methods of the support platform are followed, security can be guaranteed. There is no need to connect with the public platform of the instant messaging software, avoiding the tediousness brought by direct connection with the instant messaging software platform, as well as the security risks and Access Token refresh problems mentioned above.

[0145] At the same time, the support platform caches the user information and callback interface information of the QR code created by the third-party platform locally, and generates the QR code with a globally unique parameter. When the user scans the QR code to trigger the callback of the scanning event of the instant messaging software public platform, the cache is obtained according to the globally unique parameter, and the user information and the instant messaging software open Id are notified to the third-party platform through the callback interface in the cache, avoiding the transmission of user information to the instant messaging software public platform and ensuring the security of user information.

[0146] In this application, the ability to create a QR code is exposed by the supporting platform. The third-party platform initiates a request when the user initiates binding / login. After processing by the supporting platform, the application is made to the public platform of the instant messaging software and the validity period is set. After the QR code is generated, the QR code image address is returned to the third-party platform for display.

[0147] During the validity period of the QR code, when the user scans the QR code with instant messaging software, an event of scanning the QR code with parameters will be triggered. The public platform of the instant messaging software will notify the support platform of the event. The support platform can obtain the parameters on the QR code and the user information of the instant messaging software who scanned the QR code through the notification. The support platform can obtain the user information and callback interface information transmitted by the third-party platform when generating the QR code from the cache through the QR code parameters. Then the support platform can notify the third-party platform of the user information of the third-party platform and the Open Id information of the instant messaging software through the callback interface. Each third-party platform that is connected only needs to implement the callback interface according to the API interface specification of the support platform and pass it to the support platform when creating the QR code, so that the correct callback can be received when the instant messaging software user scans the code.

[0148] Figure 7 A docking device provided in an embodiment of the present application, such as Figure 7 As shown, the docking device includes:

[0149] The first receiving unit 701 is used to receive a target information identifier sent by a first device;

[0150] A first sending unit 702 is configured to send the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is a user identifier of the target object in the first device;

[0151] The second receiving unit 703 is configured to receive a first user identifier sent by the first device; the first user identifier is a user identifier of the target object in the target second device;

[0152] The third receiving unit 704 is configured to receive the second user identifier sent by the first device;

[0153] The second sending unit 705 is configured to send the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier.

[0154] In some embodiments, the first receiving unit 701 is further configured to:

[0155] receiving a first request sent by the target second device; the first request includes the first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier;

[0156] The first sending unit 702 is further configured to:

[0157] sending the first request to the first device;

[0158] The first receiving unit 701 is further configured to:

[0159] Receive the target information identifier sent by the first device to respond to the first request.

[0160] In some embodiments, the first receiving unit 701 is further configured to:

[0161] receiving target interface information sent by the target second device; the target interface information corresponds to the target second device;

[0162] The second sending unit 705 is further configured to:

[0163] According to the first user identifier, searching for the target interface information;

[0164] According to the target interface information, a target interface corresponding to the target interface information is called, and the first user identifier and the second user identifier are sent to the target second device through the target interface.

[0165] In some embodiments, the third receiving unit 704 is further configured to:

[0166] The second user identifier is received through the callback interface.

[0167] Figure 8 A target second device provided in an embodiment of the present application, such as Figure 8 As shown, the target second device includes:

[0168] The fourth receiving unit 801 is used to receive a target information identifier sent by the docking device and display the target information identifier; the target information identifier is used to receive a scanning event, and the scanning event is used by the first device to obtain a second user identifier, and the second user identifier is a user identifier of the target object in the first device;

[0169] A fifth receiving unit 802 is configured to receive a first user identifier and a second user identifier sent by the docking device; the first user identifier is a user identifier of the target object in the target second device;

[0170] The binding unit 803 is used to bind the first user identifier and the second user identifier.

[0171] In some embodiments, the target second device further comprises:

[0172] The third sending unit is used to send a first request to the docking device; the first request includes the first user identifier; the first request is used to request the generation of the target information identifier, and the target information identifier carries the first user identifier.

[0173] In some embodiments, the third sending unit is further used to:

[0174] Sending target interface information to the docking device; the target interface information corresponds to the target second device, and the target interface information is used by the docking device to send the first user identifier and the second user identifier to the target second device.

[0175] An embodiment of the present application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the information processing method provided in the above embodiment is implemented.

[0176] An embodiment of the present application also provides a storage medium, that is, a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the information processing method provided in the above embodiment is implemented.

[0177] It should be noted that Fig. 9 A hardware entity diagram of an electronic device according to an embodiment of the present application is shown in FIG. Fig. 9 As shown, the electronic device 900 includes: a processor 901, at least one communication bus 902, at least one external communication interface 904 and a memory 905. The communication bus 902 is configured to achieve connection and communication between these components. In an example, the electronic device 900 also includes: a user interface 903, wherein the user interface 903 may include a display screen, and the external communication interface 904 may include a standard wired interface and a wireless interface.

[0178] The memory 905 is configured to store instructions and applications executable by the processor 901, and can also cache data to be processed or processed by the processor 901 and various modules in the electronic device (for example, image data, audio data, voice communication data, and video communication data), which can be implemented through flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0179] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in some embodiments" appearing throughout the specification may not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The above-mentioned sequence numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments.

[0180] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0181] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0182] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0183] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0184] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM), magnetic disks or optical disks, etc., various media that can store program codes.

[0185] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0186] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0187] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. An information processing method, characterized in that: Applied to a docking device, the method comprises: Receiving a target information identifier sent by a first device; Sending the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is a user identifier of the target object in the first device; receiving a first user identifier sent by the first device; the first user identifier being a user identifier of the target object in the target second device; receiving the second user identifier sent by the first device; The first user identifier and the second user identifier are sent to the target second device, so that the target second device binds the first user identifier and the second user identifier.

2. The method according to claim 1, characterized in that The method further comprises: receiving a first request sent by the target second device; the first request includes the first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier; sending the first request to the first device; The receiving the target information identifier sent by the first device includes: Receive the target information identifier sent by the first device to respond to the first request.

3. The method according to claim 2, characterized in that The method further comprises: receiving target interface information sent by the target second device; the target interface information corresponds to the target second device; The sending the first user identifier and the second user identifier to the target second device includes: According to the first user identifier, searching for the target interface information; According to the target interface information, a target interface corresponding to the target interface information is called, and the first user identifier and the second user identifier are sent to the target second device through the target interface.

4. The method according to claim 1, characterized in that: The receiving the second user identifier sent by the first device includes: The second user identifier is received through the callback interface.

5. An information processing method, characterized in that: Applied to a target second device, the method includes: Receive a target information identifier sent by a docking device and display the target information identifier; the target information identifier is used to receive a scanning event, the scanning event is used by the first device to obtain a second user identifier, the second user identifier is a user identifier of the target object in the first device; receiving a first user identifier and a second user identifier sent by the docking device; the first user identifier is a user identifier of the target object in the target second device; Bind the first user identifier and the second user identifier.

6. The method according to claim 5, characterized in that The method further comprises: A first request is sent to the docking device; the first request includes the first user identifier; the first request is used to request generation of the target information identifier, and the target information identifier carries the first user identifier.

7. The method according to claim 6, characterized in that The method further comprises: Sending target interface information to the docking device; the target interface information corresponds to the target second device, and the target interface information is used by the docking device to send the first user identifier and the second user identifier to the target second device.

8. A docking device, characterized in that: The docking device comprises: A first receiving unit, configured to receive a target information identifier sent by a first device; A first sending unit, configured to send the target information identifier to a target second device in at least one second device, so that the first device obtains a second user identifier based on the target information identifier received by the target second device; the second user identifier is a user identifier of the target object in the first device; A second receiving unit is configured to receive a first user identifier sent by the first device; the first user identifier is a user identifier of the target object in the target second device; A third receiving unit, configured to receive the second user identifier sent by the first device; The second sending unit is configured to send the first user identifier and the second user identifier to the target second device, so that the target second device binds the first user identifier and the second user identifier.

9. A target second device, characterized in that: The target second device includes: a fourth receiving unit, configured to receive a target information identifier sent by the docking device and display the target information identifier; the target information identifier is used to receive a scanning event, the scanning event is used by the first device to obtain a second user identifier, the second user identifier being a user identifier of the target object in the first device; A fifth receiving unit, configured to receive the first user identifier and the second user identifier sent by the docking device; the first user identifier is the user identifier of the target object in the target second device; A binding unit is used to bind the first user identifier and the second user identifier.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, it implements the information processing method described in any one of claims 1 to 4, or implements the information processing method described in any one of claims 5 to 7.

11. A storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the information processing method described in any one of claims 1 to 4 is implemented, or the information processing method described in any one of claims 5 to 7 is implemented.

Images