Equipment linkage data processing method and device

Abstract

The invention discloses an equipment linkage data processing method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: intercepting a data synchronization request sent by an application client; the application client is installed in a first device, and the data synchronization request is generated by the application client in response to a login operation and comprises first account information and first identification information of the first device; executing an authentication operation for the data synchronization request; a data synchronization request is sent to the application server side, and the application server side sends target data of the first account information to the first device based on the first identification information under the condition that the authentication result is passed, and performs data synchronization on the application client side; the target data is data of the application client in the second equipment which has a binding relationship with the first equipment. According to the embodiment, the authentication mechanism is introduced into the data synchronization process, and accurate issuing of the data is realized based on the equipment binding relationship, so that the security and controllability of data synchronization are effectively improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for device linkage data processing. Background Technology

[0002] Currently, many enterprises primarily audit user operations using security software. While this logs user behavior, it has significant shortcomings in data access control: it cannot verify the ownership relationship between login accounts and devices. For example, employee X1 can log into employee X2's account using their own device and access sensitive corporate data based on X2's account permissions. Therefore, the existing method lacks a mechanism for binding user accounts to trusted devices, resulting in lax data access control and raising risks of data being left unattended, leaked, and misused. Therefore, it is urgent to introduce authentication mechanisms in critical scenarios such as data synchronization to improve the security and controllability of data access. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a device linkage data processing method and apparatus, which can at least solve the problem in the prior art where the lack of a trust authentication mechanism for user accounts and devices in data synchronization leads to the arbitrary landing, leakage and abuse of data.

[0004] To achieve the above objectives, according to one aspect of the present invention, a device linkage data processing method is provided, applied to an authentication terminal, comprising:

[0005] Intercept the data synchronization request sent by the application client; wherein the data synchronization request is generated by the application client in response to the login operation, including the application client's first account information and the first identification information of the first device on which the application client is installed;

[0006] An authentication operation is performed on the data synchronization request to obtain the authentication result;

[0007] The application server sends the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0008] To achieve the above objectives, according to one aspect of the present invention, a device linkage data processing method is provided, applied to an application server, comprising:

[0009] The authentication terminal receives a data synchronization request sent by the authentication terminal, wherein the authentication terminal intercepts the data synchronization request sent by the application client. The data synchronization request is generated by the application client in response to the login operation and includes the application client's first account information and the first identification information of the first device on which the application client is installed.

[0010] In response to the authentication result obtained by the authentication terminal in performing the authentication operation on the data synchronization request being passed, the target data corresponding to the first account information is obtained, and the target data is sent to the first device based on the first identification information; wherein, the target data is data uploaded by the application client in the second device that has a binding relationship with the first device to the application server.

[0011] To achieve the above objectives, according to another aspect of the present invention, a device linkage data processing apparatus is provided, applied at an authentication end, comprising:

[0012] The first receiving module is used to intercept data synchronization requests sent by the application client; wherein the application client is installed in the first device, and the data synchronization request is generated by the application client in response to a login operation, including the application client's first account information and the first identification information of the first device;

[0013] The authentication module is used to perform authentication operations on the data synchronization request and obtain the authentication result;

[0014] The sending module is used to send the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0015] To achieve the above objectives, according to another aspect of the present invention, a device linkage data processing apparatus is provided, applied to an application server, comprising:

[0016] The second receiving module is used to receive a data synchronization request sent by the authentication terminal. The authentication terminal intercepts the data synchronization request sent by the application client. The data synchronization request is generated by the application client in response to the login operation and includes the first account information of the application client and the first identification information of the first device. The application client is installed on the first device.

[0017] The processing module is configured to, in response to the authentication result obtained by the authentication end in performing an authentication operation on the data synchronization request and passing the authentication, acquire the target data corresponding to the first account information, and send the target data to the first device based on the first identification information; wherein, the target data is the data of the application client in the second device that has a binding relationship with the first device.

[0018] To achieve the above objectives, according to another aspect of the present invention, a device linkage data processing system is provided, including an application client, an application server, and an authentication terminal;

[0019] The application client is used to generate a data synchronization request in response to a login operation; wherein, the data synchronization request includes the application client's first account information and the first identification information of the first device on which the application client is installed;

[0020] The authentication terminal is used to perform an authentication operation on the data synchronization request after intercepting the data synchronization request, obtain an authentication result, and send the data synchronization request to the application server.

[0021] The application server is configured to send target data corresponding to the first account information to the first device based on the first identification information when the authentication result is successful, so as to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0022] To achieve the above objectives, according to another aspect of the present invention, a device-linked data processing electronic device is provided.

[0023] The electronic device of this invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the device linkage data processing methods described above.

[0024] To achieve the above objectives, according to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements any of the device linkage data processing methods described above.

[0025] To achieve the above objectives, according to another aspect of the present invention, a computing program product is provided. The computing program product of the present invention includes a computer program, which, when executed by a processor, implements the device linkage data processing method provided in the present invention.

[0026] According to the solution provided by the present invention, one embodiment of the invention has the following advantages or beneficial effects: by introducing an authentication mechanism into the data synchronization process and achieving accurate data distribution based on device binding relationships, the security and controllability of data synchronization are effectively improved. The authentication end verifies the user account information and device legitimacy to ensure that only authenticated devices can synchronize application data; the application server sends application data to the requesting device based on device identification information and device binding relationships to prevent unauthorized devices from synchronizing the data, strictly controlling access to application data, and ensuring the secure flow of enterprise data in a multi-device environment. This effectively solves the problem of "data synchronization lacking a trust authentication mechanism for user accounts and devices, leading to arbitrary data landing, leakage, and abuse" in the existing technology.

[0027] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0028] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0029] Figure 1 This is a schematic diagram of the main flow of a device linkage data processing method applied to the authentication end according to an embodiment of the present invention;

[0030] Figure 2 This is a flowchart illustrating an optional device linkage data processing method according to an embodiment of the present invention;

[0031] Figure 3 This is a schematic diagram of the main process of a device linkage data processing method applied to an application server according to an embodiment of the present invention;

[0032] Figure 4 This is a schematic diagram of a specific device linkage data processing flow according to an embodiment of the present invention;

[0033] Figure 5 This is a schematic diagram of the main modules of a device linkage data processing device applied to an authentication terminal according to an embodiment of the present invention;

[0034] Figure 6 This is a schematic diagram of the main modules of a device linkage data processing device applied to an application server according to an embodiment of the present invention;

[0035] Figure 7 This is a schematic diagram of the main framework of a device linkage data processing system according to an embodiment of the present invention;

[0036] Figure 8 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0037] Figure 9 This is a schematic diagram of the structure of a computer system suitable for implementing the embodiments of the present invention, such as a mobile device or server. Detailed Implementation

[0038] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0039] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, they do not mean that the applicant has used or necessarily used the solution.

[0040] Where there is no conflict, the embodiments and features in the embodiments of this invention can be combined with each other. The acquisition, transmission, storage, use, and processing of data in the technical solutions of this invention all comply with relevant national laws and regulations, are used for legal and reasonable purposes, and are not shared, disclosed, or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities.

[0041] Regarding user information, necessary measures should be taken to prevent unauthorized access to such personal information data, ensure that personnel authorized to access such data comply with relevant laws and regulations, and safeguard the security of user personal information. Once this user personal information data is no longer needed, risks should be minimized by restricting or even prohibiting data collection and / or deleting the data. Where applicable, including in certain relevant applications, user privacy should be protected through data de-identification, such as by removing specific identifiers (e.g., date of birth), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the specific address level), controlling how data is stored, and / or other de-identification methods.

[0042] See Figure 1 The diagram shows the main flowchart of a device linkage data processing method for authentication terminals provided by an embodiment of the present invention, which includes the following steps:

[0043] S101: Intercept the data synchronization request sent by the application client; wherein the application client is installed on the first device, and the data synchronization request is generated by the application client in response to a login operation, including the first account information of the application client and the first identification information of the first device;

[0044] S102: Perform an authentication operation on the data synchronization request to obtain the authentication result;

[0045] S103: Send the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0046] In existing technologies, data synchronization between application clients and application servers typically involves the application client directly sending a data synchronization request to the application server. This lack of a mechanism to verify the legitimacy of the request source poses certain security risks, especially in scenarios involving sensitive enterprise data. This data synchronization method, lacking security control, struggles to effectively manage data access permissions and device usage scope for enterprises. The method provided in this invention introduces an independent authentication terminal, thereby establishing a collaborative working mechanism among the application client, authentication terminal, and application server. This forms a more complete data synchronization process system, enhancing overall security and controllability.

[0047] This solution integrates the authentication process into the data synchronization workflow. When a user logs into the application and generates a data synchronization request, the authentication server first performs an authentication operation on the request. Only data synchronization requests that pass authentication are sent to the application server for processing, effectively preventing unauthorized access and ensuring data security. Furthermore, this solution's data synchronization relies on device binding. A binding relationship between devices is pre-established based on device identification information, ensuring that application data is synchronized only between devices associated with the user's account. This prevents data leakage or misuse and enhances data privacy and isolation. Device identification information typically refers to the device's unique code. For example, on Windows devices, a combination of the motherboard serial number and the BIOS (Basic Input Output System) serial number can be used as the device's unique identifier; for Mac devices, the unique serial number provided by the device is usually used as the binding basis.

[0048] Furthermore, this solution fully leverages the key user login action as a trigger point to automatically initiate the data synchronization process without manual user intervention, enhancing ease of use and user experience. It is particularly suitable for scenarios where employees within an enterprise use the same application on multiple devices, enabling users to seamlessly continue working on any authorized device, thus contributing to efficient data access and business continuity. Overall, this solution enhances granular control over the enterprise's data access process while ensuring data security, demonstrating promising application prospects.

[0049] To differentiate account usage in different scenarios, the following definitions are provided in this solution:

[0050] First account information: refers to the account information used by users when logging into the application client, which usually includes username and password.

[0051] Second account information: This refers to the account information used by the user when logging into the authentication terminal, and may include only the username. In this solution, the authentication terminal includes an authentication client and an authentication server, and the same account information is required to log in to the authentication client and the authentication server.

[0052] Third account information: refers to the account information used by the user when logging into the device, which may include only the username.

[0053] The three types of account information mentioned above correspond to different usage scenarios and can be obtained through the human-computer interaction controls in the device. The usernames can be different in different scenarios to avoid confusion during multi-terminal interaction, thereby improving the clarity and security of the authentication logic.

[0054] In one optimized implementation, this solution can perform multi-dimensional login verification control based on the aforementioned first account information, second account information, and third account information. Specifically, when a user attempts to log in to the authentication terminal using the second account information, if a binding relationship is detected between the second account information and the third account information of the current device, then the user is allowed to complete the login using the second account information; otherwise, login is denied to prevent others from using the current device to access the authentication terminal. For application client login operations, a binding relationship must further be required between the first account information and the third account information. Only when the binding is valid is the user allowed to log in to the application client using the first account information, and the authentication terminal is allowed to perform corresponding authentication operations on subsequent data synchronization requests, thereby achieving multi-layered security control from device to user to application.

[0055] In one implementation, the authentication terminal performs an authentication operation on the data synchronization request to obtain an authentication result, including: obtaining the second account information used by the user to log in to the authentication terminal; and performing an authentication operation on the data synchronization request based on the device binding relationship corresponding to the second account information and a list of target application information corresponding to the device binding relationship to obtain an authentication result. The device binding relationship is determined based on the first identification information of the first device and the second account information used by the user to log in to the authentication terminal. Through this device binding relationship, other devices (i.e., second devices) that are bound to the first device can be further identified, and the second identification information of these second devices can be obtained. Subsequently, based on the second account information, the first identification information, and the second identification information, a list of target application information that can be used for data synchronization is determined. If the application information (e.g., application name or identifier) ​​of the application client logged in by the user on the first device is included in the list of target application information, then the data synchronization request is considered to have passed authentication.

[0056] In this solution, the authentication client needs to be installed and running on the device. Taking the first device as an example, this first device can be either an enterprise device provided to the user or a user's personal device. The method of obtaining the authentication client installation package differs depending on the device type: For enterprise devices, the authentication client installation package can be obtained directly from the enterprise's preset system image, enabling one-click deployment on the enterprise device; for personal devices, users can obtain the authentication client installation package by accessing the official download link, which also provides an operation manual, allowing users to complete the installation locally based on the manual. After installation, the user can start and run the authentication client on the first device to participate in the entire data synchronization and authentication process. The authentication operation can be performed in one of the following ways:

[0057] Example 1: The authentication client performs the authentication operation. In this case, the authentication client needs to synchronize the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship from the authentication server. Then, based on the device binding relationship and the target application information list, the client performs the authentication operation on the data synchronization request to obtain the authentication result.

[0058] Example 2: The authentication server performs the authentication operation. In this case, the authentication client needs to generate an authentication request for the data synchronization request; the authentication request includes the first identification information of the first device, the second account information of the user logging into the authentication server, and the application information of the application client logged into by the user on the first device. After receiving the authentication request, the authentication server processes the authentication request based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, and obtains the authentication result.

[0059] As an optimized implementation, the authentication server can receive the authentication request directly from the authentication client. After the authentication server sends the authentication result to the authentication client, the authentication client, upon confirming that the authentication result is successful, then sends the data synchronization request to the application server.

[0060] As another optimized implementation, in addition to receiving the authentication request, the authentication server can also receive a data synchronization request. That is, the authentication client sends the data synchronization request and the authentication request together to the authentication server. If the authentication server processes the authentication request and obtains a successful authentication result, it will automatically send the data synchronization request to the application server.

[0061] In another optimized implementation, the authentication server receives the authentication request transmitted by the application server. That is, the authentication client sends the data synchronization request and the authentication request together to the application server, which then forwards the authentication request to the authentication server. The application server will only process the data synchronization request if the authentication server returns a successful authentication result to the application server. If the authentication result is unsuccessful, the application server will not process the data synchronization request.

[0062] The above describes the authentication and data synchronization processes of this solution in practical application. Prior to this, the solution includes a configuration phase for pre-establishing device binding relationships related to the second account information and a list of target application information matching these binding relationships. Specifically, the user specifies which devices need to be bound through the authentication terminal and further configures the list of target application information that can synchronize data based on the applications on these bound devices. This ensures that data synchronization requests can be accurately processed according to this list during the authentication process, thereby achieving secure management and fine-grained control over enterprise data access. Specifically:

[0063] S201: In response to the selection operation of the information collection option, the authentication client obtains the first application information list in the first device and sends the first identification information, the second account information and the first application information list to the authentication server.

[0064] S202: The authentication server receives the first identification information, the second account information, and the first application information list from the authentication client, and establishes a correspondence between the first identification information and the second account information;

[0065] S203: In response to the user's login authentication server operation, the authentication server queries the set of identifier information corresponding to the second account information;

[0066] S204: The authentication server determines the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information.

[0067] For steps S201 and S202, the authentication client is installed on the device. After installation and initial login, the authentication client automatically performs device information collection and authentication initiation operations. Taking the first device as an example, the collected information includes the first identification information of the first device, the second account information used by the user to log in to the authentication client, and a list of the first applications installed on the first device. After receiving the above information, the authentication server first establishes the correspondence between the first identification information and the second account information. If the second account information is associated with multiple device identification information, an identification information set can be generated for subsequent management of device binding relationships and data synchronization control.

[0068] It should be noted that the application information list can be continuously changed. For example, if the current application information list includes 1, 2, and 3, and the enterprise has independently developed enterprise application 4, then the user can click the "Collect Information" option in the authentication client to re-collect the application information list 1, 2, 3, and 4 from the device, and re-upload it to the authentication server for device binding and application selection operations, such as only updating applications that can synchronize data.

[0069] In one optional implementation, for enterprise devices, the information uploaded by their authentication client may also include relevant information about the enterprise, such as the enterprise name and enterprise code. After receiving this information, the authentication server can use the enterprise information as a tag to mark the identification information set corresponding to the second account information, which will facilitate subsequent classification management and policy configuration.

[0070] In one optimized implementation, the authentication client only uploads the device's identification information without explicitly identifying whether the device is an enterprise device or a personal device. To address this, the authentication server pre-stores a list of enterprise device identification information. Upon receiving device identification information, it compares this information to determine if the device belongs to an enterprise. For example, if the first identification information of a first device exists in the enterprise device identification information list, it is considered an enterprise device; otherwise, it is considered a personal device. Since enterprise devices are typically managed centrally by the enterprise, their binding process requires no additional verification; the enterprise devices corresponding to the same second account information can be directly bound. For personal devices, for security reasons, a further confirmation process is required before binding, thus achieving differentiated management.

[0071] As a further optimization of the above implementation method, this solution supports providing services to multiple enterprises. Therefore, the authentication server stores a list of enterprise device identification information for each of the multiple enterprises. When the first device is an enterprise device, the information it uploads also includes the corresponding enterprise information. The authentication server locates the corresponding enterprise device identification information list based on the enterprise information and determines whether the first device is a legitimate device under that enterprise based on the enterprise device identification information list, thereby realizing a cross-enterprise, fine-grained device identification and management mechanism.

[0072] For steps S203 and S204, the user can obtain the access address of the authentication server by operating the enterprise device, and access the authentication server login page accordingly, logging into the authentication server using the same second account information as the login authentication client. The authentication server responds to the user's login operation, obtains and displays the set of device identification information corresponding to the second account information, and can further display the device type corresponding to each identification information, i.e., enterprise device or personal device. For "determining the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information," various implementation methods can be adopted:

[0073] Example 1: Step-by-step filtering mechanism. When a user selects two devices (such as first identification information and second identification information) from the device identification information set on the authentication server interface and performs a binding operation, the authentication server will establish a device binding relationship between the two devices. Subsequently, the authentication server extracts common application information based on the first application information list of the first device and the second application information list of the second device, and the user selects one or more target application information as allowed data synchronization, forming a target application information list. Finally, the target application information list is associated with the aforementioned device binding relationship to complete the configuration.

[0074] Example 2: Select Device and Application First, Then Match Other Devices. The user first selects a device (e.g., the first identification information of a first device) from the device identification information set on the authentication server interface. The authentication server automatically displays a list of first application information for that first device. The user then selects one or more application information items that need data synchronization, forming a target application information list. The authentication server then filters out devices whose application information list contains the target application information from the remaining device identification information and generates a candidate identification information set for the user to choose from. After the user makes a selection, the authentication server establishes a device binding relationship between the first device and the selected second device, and associates this device binding relationship with the aforementioned target application information list to achieve more precise binding control.

[0075] Both of the above implementation methods support users in flexibly configuring device binding relationships and applications that require data synchronization, taking into account both ease of use and security, and are suitable for multi-device collaborative management needs in different scenarios.

[0076] As an optimized implementation, this solution reasonably limits the number of devices that can be bound together. This ensures user flexibility in using multiple devices while controlling data access boundaries and enhancing security management. In practice, there is generally no hard limit on the number of enterprise devices that can be bound together. For example, most users may only have one enterprise device, but some users may use multiple enterprise devices such as Windows and Mac devices simultaneously. Although the number of enterprise devices is usually configured and managed centrally by the company and generally does not exceed two, since these devices are all under the company's control, they are bound together by default and support data exchange.

[0077] In contrast, due to the higher security risks posed by personal devices, this solution preferably limits the number of devices that can be bound to a maximum of two. This limitation aims to prevent the uncontrolled growth of the number of personal devices, thereby reducing the possibility of data leakage. In some embodiments, a hard limit may not be set, and the binding operation can continue as long as it meets the requirements. If the number of personal devices in the first and second devices that the user attempts to bind exceeds a preset threshold (e.g., two), the authentication server will display a prompt message on the front-end interface, reminding the user that the current number of personal devices has exceeded the allowed range, thus achieving proactive intervention and compliance control over device binding behavior.

[0078] As another optimized implementation, when a user initiates a device binding operation (e.g., clicks the binding button), the selected personal device to be bound will receive binding verification information (such as a verification code) to further confirm the authenticity of the binding request and the user's intention. This mechanism is mainly aimed at personal device binding scenarios to enhance security. For example, when the first device is a personal device, the authentication server generates unique binding verification information and pushes this binding verification information, along with an access link for entering verification information, to the authentication client on the first device. Upon receiving the link, the authentication client automatically opens the interface for entering binding verification information, or opens it only in response to the user's click, allowing the user to manually enter the received binding verification information. The user-entered binding verification information is then sent back to the authentication server. Only after the authentication server successfully receives binding verification information matching the current binding request is the device binding relationship between the first device's first identifier and the second device's second identifier formally established, thus completing the entire binding process. This method, by introducing a dynamic verification code mechanism, effectively prevents unauthorized binding of devices, improving overall security and controllability.

[0079] See Figure 3 The diagram illustrates a process flow chart of a device linkage data processing method applied to a server according to an embodiment of the present invention, including the following steps:

[0080] S301: Receive a data synchronization request sent by the authentication terminal, wherein the authentication terminal intercepts the data synchronization request sent by the application client, the data synchronization request is generated by the application client in response to the login operation, including the first account information of the application client and the first identification information of the first device, and the application client is installed on the first device;

[0081] S302: In response to the authentication result obtained by the authentication terminal in performing the authentication operation for the data synchronization request being passed, the target data corresponding to the first account information is obtained, and the target data is sent to the first device based on the first identification information; wherein, the target data is the data of the application client in the second device that has a binding relationship with the first device.

[0082] The method provided in this embodiment receives a data synchronization request sent by an authentication terminal. If the authentication result is successful, it sends the target data uploaded by the second device bound to the first device based on the identification information of the first device. This enhances the application server's security control and accuracy during data synchronization. The application server no longer directly responds to the original data synchronization request from the application client, but relies on the authentication terminal to complete the legitimate authentication of the request, effectively preventing unauthorized access and data leakage. Simultaneously, it achieves targeted data synchronization based on device binding relationships, ensuring that data flows only within authorized devices, improving the controllability and security of data management. Furthermore, this method enables the application client to automatically trigger the data synchronization process based on user login behavior, improving the efficiency and consistency of data synchronization in multi-device environments and enhancing overall intelligent management and service capabilities.

[0083] In this solution, the authentication end includes an authentication client and an authentication server, with the authentication client installed on the device. As one implementation, the data synchronization request is sent from the authentication client to the application server. Specifically, the authentication client may perform an authentication operation on the data synchronization request, obtain an authentication result, and if the authentication result is successful, send the data synchronization request to the application server. Alternatively, the authentication client may generate an authentication request for the data synchronization request, send the authentication request to the authentication server, and if the authentication server returns a successful authentication result, send the data synchronization request to the application server. Or, the authentication client may send both the data synchronization request and the authentication request to the application server, and the application server may send the authentication request to the authentication server to receive the authentication result returned by the authentication server.

[0084] In another implementation, the data synchronization request is sent from the authentication server to the application server. Specifically, the authentication client generates an authentication request in response to the data synchronization request, and sends both the authentication request and the data synchronization request to the authentication server. If the authentication server processes the authentication request and the authentication result is successful, it then sends the data synchronization request to the application server.

[0085] See Figure 4 This diagram illustrates a specific device linkage data processing flow according to an embodiment of the present invention, including a first device (enterprise device A), a second device (personal device B), an application client, an application server, and an authentication terminal. The authentication terminal includes an authentication client and an authentication server, and both the first and second devices have an authentication client installed. This embodiment includes the following steps:

[0086] 1. For enterprise device A, user X can obtain the authentication client installation package from the enterprise's pre-set system image, enabling one-click deployment on the enterprise device. For personal device B, user X can obtain the authentication client installation package by accessing the official download link. This download link also provides an operation manual, which users can use to complete the local installation. After successful installation, the authentication client will run normally on both enterprise device A and personal device B.

[0087] 2. When user X logs into the authentication client for the first time using the second account information, the authentication client will automatically collect the device's identification information and a list of applications on the device, and upload the second account information, identification information, and application information list to the authentication server. Alternatively, user X can trigger the information collection and upload operation by clicking the "Collect Information" option in the authentication client. For enterprise device A, the uploaded information is identification information A, application information list A, and second account information; for personal device B, the uploaded information is identification information B, application information list B, and second account information. That is, user X uses the same second account information to log into the authentication client on both enterprise device A and personal device B.

[0088] 3. The authentication server pre-stores a list of enterprise equipment identification information. If identification information A exists in the list of enterprise equipment identification information, identification information A is determined to be the identification information of an enterprise equipment. If identification information B does not exist in the list of enterprise equipment identification information, identification information B is determined to be the identification information of a personal device.

[0089] Initially, users can view all enterprise devices under their name (i.e., secondary account information) on the authentication server, such as the identifier information A for enterprise device A. At this time, there are no personal devices. After receiving information uploaded by a personal device, the authentication server can query the identifier information B for personal device B.

[0090] 4. User X obtains the access address of the authentication server by operating enterprise device A, and accesses the authentication server login page accordingly, logging into the authentication server using the same second account information as the login authentication client. The authentication server responds to the user's login operation, obtains and displays the set of device identification information corresponding to the second account information, such as identification information A of enterprise device A and identification information B of personal device B.

[0091] The user selects the two identifiers from the device identifier set and initiates the binding operation. Simultaneously, the authentication server generates binding verification information and sends this information, along with a link to the binding verification input interface, to the authentication client of personal device B. The authentication client of personal device B accesses the binding verification input interface via the link, receives the binding verification information entered by the user, and sends it to the authentication server. Upon receiving the binding verification information from the authentication client of personal device B, the authentication server establishes a device binding relationship between identifier A of enterprise device A and identifier B of personal device B. However, if the number of personal devices selected exceeds the limit during this process, a prompt message will appear.

[0092] Determine the common application information of enterprise device A's application information list A and personal device B's application information list B, and let the user select one or more of them as target application information that allows data synchronization, such as application Y, and associate the application information of application Y with the aforementioned device binding relationship.

[0093] 5. After a user logs into application client Y on enterprise device A or personal device B, during the login process, application client Y generates a data synchronization request based on the initial account information of application client Y and the identification information of the device on which application client Y is installed, and sends it to the application server. The authentication client intercepts this data synchronization request, generates an authentication request for the data synchronization request, and sends both the authentication request and the data synchronization request to the authentication server. The authentication server performs authentication processing, and if the authentication result is successful, the authentication server sends the data synchronization request to the application server.

[0094] 6. If the authentication result is successful, it indicates that the device is an authorized bound device. Only in this case will the application server process the data synchronization request. Taking enterprise device A as an example, data generated by user X's operations on application client Y on enterprise device A will be uploaded to the application server in real time. If user X logs into application client Y on personal device B using the same initial account information, the authentication mechanism will determine that personal device B is a bound device to enterprise device A. The application server will then synchronize the data corresponding to the initial account information to application client Y on personal device B. At this point, the user can view the same data in the same application client Y on both enterprise device A and personal device B.

[0095] Taking a company-developed cloud storage service as an example, in this application, all data can only be viewed between mutually bound devices. For instance, if user X logs into the cloud storage application on company device A and uploads file Z, and device B is user X's personal device, which has been authorized and bound to company device A, then the cloud storage application running on personal device B can synchronize the content of file Z, and vice versa. This device-bound data synchronization mechanism effectively ensures the security and controllability of company data.

[0096] Taking a company's self-developed instant messaging software for internal communication as an example, sensitive information such as chat history is only synchronized and displayed between mutually bound devices. Data synchronization and access across devices are only possible when devices are bound together and the login accounts are identical (e.g., user X logs in using their own account on both their corporate device A and personal device B). For unbound devices or other personal devices, even logging in with the same account will not allow access to relevant data, thus ensuring that data circulates only within authorized scope and further enhancing system security.

[0097] This solution introduces a unified authentication terminal to achieve binding authentication between enterprise devices and personal devices. This ensures that only devices with the same account information and authorized binding can synchronize data for specific applications, thereby significantly improving security while guaranteeing user experience. Its advantages are mainly reflected in the following aspects:

[0098] First, it enables fine-grained control over enterprise data access. Through a device binding mechanism, data synchronization is only allowed between authenticated and authorized devices, effectively preventing unauthorized devices from accessing sensitive enterprise information and avoiding data leakage and misuse. This is especially suitable for application scenarios involving core enterprise data.

[0099] Secondly, it enhances the security and controllability of cross-device data synchronization. Whether it's enterprise cloud storage, instant messaging software, or other enterprise-level applications, data synchronization can only occur after device binding is completed and identity consistency is met, ensuring clear boundaries and manageable control over data flow.

[0100] Third, it provides a compliant solution for data synchronization between enterprise devices and personal devices. While taking into account the convenience of employees, it achieves integrated management of "people, devices, and data" through a binding mechanism, which not only meets the actual needs of employees to use multiple devices collaboratively, but also prevents the disorderly leakage of enterprise data.

[0101] Therefore, this solution has good versatility and scalability, and can be adapted to various types of enterprise-level applications. As a unified data synchronization and management platform, it facilitates unified deployment and management of enterprises in different business systems, thereby improving overall security governance capabilities.

[0102] See Figure 5 The diagram shows the main modules of a device linkage data processing device 500 applied to an authentication terminal according to an embodiment of the present invention, including:

[0103] The first receiving module 501 is used to intercept a data synchronization request sent by the application client; wherein the application client is installed in the first device, and the data synchronization request is generated by the application client in response to a login operation, including the first account information of the application client and the first identification information of the first device.

[0104] Authentication module 502 is used to perform authentication operations on the data synchronization request and obtain authentication results;

[0105] The sending module 503 is used to send the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0106] In the apparatus of this invention, the authentication module 502 is used for:

[0107] Obtain the second account information from the authentication terminal; based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, perform an authentication operation on the data synchronization request to obtain the authentication result;

[0108] The process includes:

[0109] Based on the first identification information and the second account information, other second devices that are bound to the first device are identified, and the second identification information of the second devices is obtained.

[0110] Determine a list of target application information that can synchronize data with the second account information, the first identification information, and the second identification information;

[0111] If the application client's application information is found in the target application information list, the authentication result is determined to be successful.

[0112] In the apparatus of this invention, the authentication module 502 is further configured to:

[0113] Obtain the third account information of the first device;

[0114] If there is a binding relationship between the second account information and the third account information, the second account information can be used to log in to the authentication terminal;

[0115] If the first account information and the third account information are bound together, the authentication terminal performs an authentication operation in response to the data synchronization request.

[0116] In the apparatus of this invention, the authentication end includes an authentication client and an authentication server, and the authentication client is installed in the first device;

[0117] The authentication module 502 is used for:

[0118] The authentication client synchronizes the device binding relationship with the second account information and the target application information list with the device binding relationship from the authentication server.

[0119] The authentication client performs an authentication operation on the data synchronization request based on the device binding relationship and the target application information list, and obtains the authentication result.

[0120] In the apparatus of this invention, the authentication end includes an authentication client and an authentication server, and the authentication client is installed in the first device;

[0121] The authentication module 502 is used for:

[0122] The authentication client generates an authentication request for the data synchronization request; wherein the authentication request includes the first identification information, the second account information, and the application information;

[0123] The authentication server receives the authentication request, processes the authentication request based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, and obtains the authentication result.

[0124] In the apparatus of this invention, the process of handling data synchronization requests and authentication requests includes one of the following scenarios:

[0125] The authentication client sends the data synchronization request and the authentication request to the authentication server. If the authentication server processes the authentication request and obtains a successful authentication result, it sends the data synchronization request to the application server.

[0126] The authentication client sends the authentication request to the authentication server. If the authentication result returned by the authentication server is successful, the client sends the data synchronization request to the application server.

[0127] The authentication client sends the data synchronization request and the authentication request to the application server; wherein, the application server sends the authentication request to the authentication server, and processes the data synchronization request if it receives an authentication result of passing from the authentication server.

[0128] In the apparatus of the present invention, before the data synchronization request sent by the intercepting application client is mentioned, the apparatus further includes a configuration module, used for:

[0129] In response to the selection of information collection options, the authentication client obtains the first application information list in the first device and sends the first identification information, the second account information and the first application information list to the authentication server.

[0130] The authentication server receives the first identification information, the second account information, and the first application information list from the authentication client, and establishes a correspondence between the first identification information and the second account information;

[0131] In response to the user's login authentication server operation, the authentication server queries the set of identifier information corresponding to the second account information;

[0132] The authentication server determines the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information.

[0133] In the apparatus of this invention, the configuration module is used for:

[0134] The authentication server responds to the user's selection and binding operation of the first identification information and the second identification information in the identification information set, and establishes a device binding relationship between the first identification information and the second identification information.

[0135] Based on the first application information list and the second application information list corresponding to the second identification information, the target application information that the first device and the second device can synchronize data is determined, the target application information list is obtained, and the correspondence between the device binding relationship and the target application information list is established.

[0136] In the apparatus of this invention, the configuration module is used for:

[0137] The authentication server determines the common application information in the first application information list and the second application information list;

[0138] One or more shared application information selected by the user from the shared application information shall be used as the target application information for which the first device and the second device can synchronize data.

[0139] In the apparatus of this invention, the configuration module is used for:

[0140] In response to the user's selection of the first identifier information in the identifier information set, the authentication server displays the first application information list corresponding to the first identifier information.

[0141] One or more application information selected by the user from the first application information list are used as target application information that can be synchronized with data, thus obtaining a target application information list.

[0142] From the remaining set of identifier information excluding the first identifier information in the identifier information set, a candidate identifier information set including the target application information is selected from the application information list, and the second identifier information selected by the user from the candidate identifier information set is received;

[0143] Establish a device binding relationship between the first identification information and the second identification information, and establish a correspondence between the device binding relationship and the target application information list.

[0144] In the apparatus of this invention, the configuration module is used for:

[0145] The authentication server identifies the personal device in the first device and the second device, generates binding verification information, and sends the binding verification information and the access link of the interface for entering the binding verification information to the authentication client of the personal device.

[0146] The authentication client of the personal device displays the input binding verification information interface through the access link, so as to receive the binding verification information entered by the user in the input binding verification information interface and send the binding verification information to the authentication server;

[0147] After receiving the binding verification information from the authentication client of the personal device, the authentication server establishes a device binding relationship between the first identification information and the second identification information.

[0148] In the device of this invention, the authentication server pre-stores a list of enterprise equipment identification information;

[0149] After the authentication server receives the first identification information from the authentication client, the configuration module is further configured to:

[0150] The authentication server responds when the first identification information exists in the enterprise equipment identification information list, and determines that the first identification information is the identification information of the enterprise equipment.

[0151] If the authentication server finds that the first identification information does not exist in the enterprise device identification information list, it determines that the first identification information is the identification information of a personal device.

[0152] In the device of this invention, the authentication server pre-stores a list of enterprise equipment identification information for each enterprise;

[0153] When the first device is an enterprise device, the configuration module is further configured to:

[0154] The authentication client obtains the enterprise information of the enterprise device and sends the enterprise information to the authentication server;

[0155] The authentication server determines a list of enterprise equipment identification information corresponding to the enterprise information.

[0156] In the apparatus of this invention, the configuration module is further configured to:

[0157] The authentication server identifies the personal device among the first device and the second device. In response to the number of personal devices exceeding a preset threshold, a prompt message is displayed.

[0158] See Figure 6 The diagram shows the main modules of a device linkage data processing device 600 applied to an application server according to an embodiment of the present invention, including:

[0159] The second receiving module 601 is used to receive a data synchronization request sent by the authentication terminal. The authentication terminal intercepts the data synchronization request sent by the application client. The data synchronization request is generated by the application client in response to the login operation and includes the first account information of the application client and the first identification information of the first device. The application client is installed in the first device.

[0160] The processing module 602 is configured to, in response to the authentication result obtained by the authentication end in performing an authentication operation on the data synchronization request and passing the authentication, obtain the target data corresponding to the first account information, and send the target data to the first device based on the first identification information; wherein, the target data is the data of the application client in the second device that has a binding relationship with the first device.

[0161] In the apparatus of the present invention, the authentication terminal includes an authentication client and an authentication server, and the authentication client is installed in the first device;

[0162] The second receiving module 601 is used for:

[0163] Receive data synchronization requests sent by the authentication client;

[0164] The authentication client performs an authentication operation on the data synchronization request, obtains an authentication result, and if the authentication result is successful, sends the data synchronization request to the application server; or

[0165] The authentication client generates an authentication request in response to the data synchronization request, sends the authentication request to the authentication server, and if the authentication server returns a successful authentication result, sends the data synchronization request to the application server; the authentication request includes the first identification information, the second account information of the authentication client, and the application information of the application client.

[0166] In the apparatus of the present invention, the authentication terminal includes an authentication client and an authentication server, and the authentication client is installed in the first device;

[0167] The second receiving module 601 is used for:

[0168] Receive data synchronization requests and authentication requests sent by the authentication client; wherein the authentication request is generated by the authentication client in response to the data synchronization request;

[0169] The authentication request is sent to the authentication server to receive the authentication result returned by the authentication server.

[0170] In the apparatus of the present invention, the authentication terminal includes an authentication client and an authentication server, and the authentication client is installed in the first device;

[0171] The second receiving module 601 is used for:

[0172] The authentication client receives a data synchronization request from the authentication server; wherein, the authentication client generates an authentication request in response to the data synchronization request, and sends the authentication request and the data synchronization request to the authentication server; if the authentication server obtains a pass result from processing the authentication request, it sends the data synchronization request to the application server.

[0173] Furthermore, the specific implementation details of the device described in the embodiments of the present invention have been described in detail in the above-described method, so the details will not be repeated here.

[0174] See Figure 7The diagram shows the main framework of a device linkage data processing system 700 provided in an embodiment of the present invention, including:

[0175] An application client is used to generate a data synchronization request in response to a login operation; wherein, the data synchronization request includes the application client's first account information and the first identification information of the first device on which the application client is installed;

[0176] The authentication terminal is used to perform authentication operations on the data synchronization request after intercepting it, and obtain an authentication result; and to send the data synchronization request to the application server; the authentication terminal includes an authentication client and an authentication server;

[0177] The application server is configured to send target data corresponding to the first account information to the first device based on the first identification information when the authentication result is successful, so as to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

[0178] Figure 8 An exemplary system architecture 800 to which embodiments of the present invention can be applied is shown, including terminal devices 801, 802, 803, network 804, and server 805 (only an example).

[0179] Terminal devices 801, 802, and 803 can be various electronic devices with displays and web browsing capabilities, and can be equipped with various communication client applications. Users can use terminal devices 801, 802, and 803 to interact with server 805 via network 804 to receive or send messages, etc.

[0180] Network 804 is a medium used to provide a communication link between terminal devices 801, 802, 803 and server 805. Network 804 can include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0181] Server 805 can be a server providing various services, such as a backend management server supporting shopping websites browsed by users using terminal devices 801, 802, and 803 (this is just an example). The backend management server can analyze and process data such as received product information query requests, and feed back the processing results (such as target push information and product information—this is just an example) to the terminal devices. It should be noted that the method provided in this embodiment of the invention is generally executed by server 805, and correspondingly, the apparatus is generally set in server 805.

[0182] It should be understood that Figure 8The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0183] The following is for reference. Figure 9 It shows a schematic diagram of the structure of a computer system 900 suitable for implementing a terminal device of the present invention. Figure 9 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0184] like Figure 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 902 or programs loaded from storage section 908 into random access memory (RAM) 903. The RAM 903 also stores various programs and data required for the operation of the system 900. The CPU 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0185] The following components are connected to I / O interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to I / O interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 910 as needed so that computer programs read from it can be installed into storage section 908 as needed.

[0186] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by central processing unit (CPU) 901, it performs the functions defined above in the system of this invention.

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

[0188] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0189] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a first receiving module, an authentication module, and a transmitting module. The names of these modules do not necessarily limit the module itself; for example, the first receiving module can also be described as a "first transmission module."

[0190] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to perform any of the device-linked data processing methods described above.

[0191] The computer program product of the present invention includes a computer program that, when executed by a processor, implements the device linkage data processing method in the embodiments of the present invention.

[0192] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for processing equipment linkage data, characterized in that, Applied to the authentication end, the method includes: Intercepting data synchronization requests sent by application clients; wherein the application client is installed on the first device, and the data synchronization request is generated by the application client in response to a login operation, including the application client's first account information and the first identification information of the first device; An authentication operation is performed on the data synchronization request to obtain the authentication result; The application server sends the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

2. The method according to claim 1, characterized in that, The step of performing an authentication operation on the data synchronization request and obtaining an authentication result includes: Obtain the second account information from the authentication terminal; Based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, an authentication operation is performed on the data synchronization request to obtain the authentication result; The process includes: Based on the first identification information and the second account information, other second devices that are bound to the first device are identified, and the second identification information of the second devices is obtained. Determine a list of target application information that can synchronize data with the second account information, the first identification information, and the second identification information; If the application client's application information is found in the target application information list, the authentication result is determined to be successful.

3. The method according to claim 2, characterized in that, The method further includes: Obtain the third account information of the first device; If there is a binding relationship between the second account information and the third account information, the second account information can be used to log in to the authentication terminal; If the first account information and the third account information are bound together, the authentication terminal performs an authentication operation in response to the data synchronization request.

4. The method according to claim 2, characterized in that, The authentication process includes an authentication client and an authentication server, with the authentication client installed on the first device; The authentication operation is performed on the data synchronization request based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, to obtain the authentication result, including: The authentication client synchronizes the device binding relationship with the second account information and the target application information list with the device binding relationship from the authentication server. The authentication client performs an authentication operation on the data synchronization request based on the device binding relationship and the target application information list, and obtains the authentication result.

5. The method according to claim 2, characterized in that, The authentication process includes an authentication client and an authentication server, with the authentication client installed on the first device; The authentication operation is performed on the data synchronization request based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, to obtain the authentication result, including: The authentication client generates an authentication request for the data synchronization request; wherein the authentication request includes the first identification information, the second account information, and the application information; The authentication server receives the authentication request, processes the authentication request based on the device binding relationship corresponding to the second account information and the target application information list corresponding to the device binding relationship, and obtains the authentication result.

6. The method according to claim 5, characterized in that, The process of handling data synchronization requests and authentication requests includes one of the following scenarios: The authentication client sends the data synchronization request and the authentication request to the authentication server. If the authentication server processes the authentication request and obtains a successful authentication result, it sends the data synchronization request to the application server. The authentication client sends the authentication request to the authentication server. If the authentication result returned by the authentication server is successful, the client sends the data synchronization request to the application server. The authentication client sends the data synchronization request and the authentication request to the application server; wherein, the application server sends the authentication request to the authentication server, and processes the data synchronization request if it receives an authentication result of passing from the authentication server.

7. The method according to claim 4 or 5, characterized in that, Before intercepting the data synchronization request sent by the application client, the method further includes: In response to the selection of information collection options, the authentication client obtains the first application information list in the first device and sends the first identification information, the second account information and the first application information list to the authentication server. The authentication server receives the first identification information, the second account information, and the first application information list from the authentication client, and establishes a correspondence between the first identification information and the second account information; In response to the user's login authentication server operation, the authentication server queries the set of identifier information corresponding to the second account information; The authentication server determines the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information.

8. The method according to claim 7, characterized in that, The authentication server determines the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information, including: The authentication server responds to the user's selection and binding operation of the first identification information and the second identification information in the identification information set, and establishes a device binding relationship between the first identification information and the second identification information. Based on the first application information list and the second application information list corresponding to the second identification information, the target application information that the first device and the second device can synchronize data is determined, the target application information list is obtained, and the correspondence between the device binding relationship and the target application information list is established.

9. The method according to claim 8, characterized in that, The step of determining the target application information for which the first device and the second device can synchronize data based on the first application information list and the second application information list corresponding to the second identification information includes: The authentication server determines the common application information in the first application information list and the second application information list; One or more shared application information selected by the user from the shared application information shall be used as the target application information for which the first device and the second device can synchronize data.

10. The method according to claim 7, characterized in that, The authentication server determines the device binding relationship and the target application information list corresponding to the device binding relationship based on the set of identification information and the application information list corresponding to each identification information, including: In response to the user's selection of the first identifier information in the identifier information set, the authentication server displays the first application information list corresponding to the first identifier information. One or more application information selected by the user from the first application information list are used as target application information that can be synchronized with data, thus obtaining a target application information list. From the remaining set of identifier information excluding the first identifier information in the identifier information set, a candidate identifier information set including the target application information is selected from the application information list, and the second identifier information selected by the user from the candidate identifier information set is received; Establish a device binding relationship between the first identification information and the second identification information, and establish a correspondence between the device binding relationship and the target application information list.

11. The method according to claim 8 or 10, characterized in that, The establishment of the device binding relationship between the first identification information and the second identification information includes: The authentication server identifies the personal device in the first device and the second device, generates binding verification information, and sends the binding verification information and the access link of the interface for entering the binding verification information to the authentication client of the personal device. The authentication client of the personal device displays the input binding verification information interface through the access link, so as to receive the binding verification information entered by the user in the input binding verification information interface and send the binding verification information to the authentication server; After receiving the binding verification information from the authentication client of the personal device, the authentication server establishes a device binding relationship between the first identification information and the second identification information.

12. The method according to claim 11, characterized in that, The authentication server pre-stores a list of enterprise equipment identification information; After the authentication server receives the first identification information from the authentication client, the method further includes: The authentication server responds when the first identification information exists in the enterprise equipment identification information list, and determines that the first identification information is the identification information of the enterprise equipment. If the authentication server finds that the first identification information does not exist in the enterprise device identification information list, it determines that the first identification information is the identification information of a personal device.

13. The method according to claim 12, characterized in that, The authentication server pre-stores a list of enterprise equipment identification information for each company; If the first device is enterprise equipment, the method further includes: The authentication client obtains the enterprise information of the enterprise device and sends the enterprise information to the authentication server; The authentication server determines a list of enterprise equipment identification information corresponding to the enterprise information.

14. The method according to claim 11, characterized in that, The method further includes: The authentication server identifies the personal device among the first device and the second device. In response to the number of personal devices exceeding a preset threshold, a prompt message is displayed.

15. A method for processing equipment linkage data, characterized in that, Applied to the application server, the method includes: The authentication terminal receives a data synchronization request sent by the authentication terminal, wherein the authentication terminal intercepts the data synchronization request sent by the application client. The data synchronization request is generated by the application client in response to the login operation and includes the application client's first account information and the first identification information of the first device. The application client is installed on the first device. In response to the authentication result obtained by the authentication terminal in performing the authentication operation for the data synchronization request being passed, the target data corresponding to the first account information is obtained, and the target data is sent to the first device based on the first identification information; wherein, the target data is the data of the application client in the second device that has a binding relationship with the first device.

16. The method according to claim 15, characterized in that, The authentication terminal includes an authentication client and an authentication server, with the authentication client installed in the first device; The data synchronization request sent by the receiving authentication terminal includes: Receive data synchronization requests sent by the authentication client; The authentication client performs an authentication operation on the data synchronization request, obtains an authentication result, and if the authentication result is successful, sends the data synchronization request to the application server; or The authentication client generates an authentication request in response to the data synchronization request, sends the authentication request to the authentication server, and if the authentication server returns a successful authentication result, sends the data synchronization request to the application server; the authentication request includes the first identification information, the second account information of the authentication client, and the application information of the application client.

17. The method according to claim 15, characterized in that, The authentication terminal includes an authentication client and an authentication server, with the authentication client installed in the first device; The data synchronization request sent by the receiving authentication terminal includes: Receive data synchronization requests and authentication requests sent by the authentication client; wherein the authentication request is generated by the authentication client in response to the data synchronization request; The authentication request is sent to the authentication server to receive the authentication result returned by the authentication server.

18. The method according to claim 15, characterized in that, The authentication terminal includes an authentication client and an authentication server, with the authentication client installed in the first device; The data synchronization request sent by the receiving authentication terminal includes: The authentication client receives a data synchronization request from the authentication server; wherein, the authentication client generates an authentication request in response to the data synchronization request, and sends the authentication request and the data synchronization request to the authentication server; if the authentication server obtains a pass result from processing the authentication request, it sends the data synchronization request to the application server.

19. A device for processing data in conjunction with equipment, characterized in that, The device, used in authentication, includes: The first receiving module is used to intercept data synchronization requests sent by the application client; wherein the application client is installed in the first device, and the data synchronization request is generated by the application client in response to a login operation, including the application client's first account information and the first identification information of the first device; The authentication module is used to perform authentication operations on the data synchronization request and obtain the authentication result; The sending module is used to send the data synchronization request to the application server, so that if the authentication result is passed, the application server sends the target data corresponding to the first account information to the first device based on the first identification information to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

20. A device for processing data in conjunction with equipment, characterized in that, The device, used on an application server, includes: The second receiving module is used to receive a data synchronization request sent by the authentication terminal. The authentication terminal intercepts the data synchronization request sent by the application client. The data synchronization request is generated by the application client in response to the login operation and includes the first account information of the application client and the first identification information of the first device. The application client is installed on the first device. The processing module is configured to, in response to the authentication result obtained by the authentication end in performing an authentication operation on the data synchronization request and passing the authentication, acquire the target data corresponding to the first account information, and send the target data to the first device based on the first identification information; wherein, the target data is the data of the application client in the second device that has a binding relationship with the first device.

21. A device linkage data processing system, characterized in that, This includes application clients, application servers, and authentication terminals; The application client is used to generate a data synchronization request in response to a login operation; wherein, the data synchronization request includes the application client's first account information and the first identification information of the first device on which the application client is installed; The authentication terminal is used to perform an authentication operation on the data synchronization request after intercepting the data synchronization request, obtain an authentication result, and send the data synchronization request to the application server. The application server is configured to send target data corresponding to the first account information to the first device based on the first identification information when the authentication result is successful, so as to synchronize the application client data; wherein, the target data is the data of the application client in the second device that is bound to the first device.

22. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-18.

23. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-18.

24. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-18.

Images