A method and apparatus for cross-device communication

Abstract

The embodiment of the present application provides a kind of cross-device communication method and device, by responding to the service trigger interactive operation for target service, to intermediate server, the session registration application of target service is initiated, receive the communication ticket returned based on session registration application of intermediate server, and by communication ticket, first service context data of target service is sent to intermediate server, communication ticket is transferred to service cooperation end, to make service cooperation end obtain first service context data from intermediate server by communication ticket, and based on first service context data, complete the service processing interactive operation for target service, it is realized by intermediate server to realize cross-device communication, to complete the interactive operation of service, and by registration mode initiation, once communication interaction can avoid interaction between equipment in the case where data interaction is not needed, save the performance and resource of intermediate server.

Description

Technical Field

[0001] This application relates to the field of cross-device communication technology, and in particular to a method and apparatus for cross-device communication, an electronic device, and a storage medium. Background Technology

[0002] On TV and PC platforms, some interactive operations are not convenient. For example, payments are usually completed by scanning a QR code using a mobile app, but filling in information may be inconvenient because operating a TV remote control is very difficult, and the interaction may lead users to scan a QR code to fill in information on their mobile phones.

[0003] This presents a scenario of continuous interactive operation across devices and platforms. However, in practical applications, due to inconsistencies in hardware and communication protocols between devices, direct information exchange between devices may not be possible. Summary of the Invention

[0004] The purpose of this application is to provide a method and apparatus for cross-device communication, thereby solving the problem that devices cannot directly exchange information due to inconsistencies in hardware and communication protocols. The specific technical solution is as follows: In a first aspect of this application, a method for cross-device communication is provided, applied to a service response end, the method comprising: In response to a business-triggered interactive operation targeting a specific business, a session registration request for the target business is initiated to the intermediate server; Receive the communication ticket returned by the intermediate server based on the session registration request, and send the first service context data of the target service to the intermediate server through the communication ticket; The communication ticket is transmitted to the business collaboration end so that the business collaboration end can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

[0005] Optionally, the step of initiating a session registration request for the target service to the intermediate server in response to a service-triggered interaction operation for the target service includes: In response to a business-triggered interactive operation targeting a specific business, the business type of the target business is determined; Based on the business type, determine whether to process the target business through the business collaboration terminal; If it is determined that the target service needs to be processed through the business collaboration terminal, a session registration request for the target service is initiated to the intermediate server.

[0006] Optionally, transmitting the communication ticket to the business collaboration terminal includes: Based on the communication ticket, a cross-platform communication QR code is generated; The communication ticket is transmitted to the business collaboration terminal via the cross-terminal communication QR code.

[0007] Optionally, after transmitting the communication ticket to the business collaboration terminal, the method further includes: The intermediate server is periodically queried using the communication ticket to obtain second business context data; wherein, the second business context data is the business context data of the business processing interaction operation sent by the business collaboration terminal to the intermediate server.

[0008] Optionally, after periodically querying the intermediate server using the communication ticket to obtain the second business context data, the method further includes: Based on the second business context data, business association information for the target business is displayed.

[0009] Optionally, after displaying preset prompt information for the target service based on the second service context data, the method further includes: An unregistration request is initiated to the intermediate server so that the intermediate server can clean up the second business context data and cancel the communication ticket.

[0010] A cross-device communication method is also provided, applied to the business response end, the method including: Obtain the communication ticket transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration request for the target service to the intermediate server; The first service context data of the target service is obtained from the intermediate server through the communication ticket; wherein, the first service context data of the target service is sent by the service response end to the intermediate server through the communication ticket. Based on the first business context data, complete the business processing interaction operation for the target business.

[0011] Optionally, the step of completing the business processing interaction operation for the target business based on the first business context data includes: Based on the first business context data, obtain the business data of the target business from the business server; Based on the business data, complete the business processing interaction operation for the target business.

[0012] In a second aspect of this application, an apparatus for cross-device communication, including an application service response terminal, is also provided, the apparatus comprising: The device, applied to the business response end, includes: The registration module is used to initiate a session registration request for the target service to the intermediate server in response to a business-triggered interactive operation for the target service. The ticket receiving module is used to receive the communication ticket returned by the intermediate server based on the session registration application, and send the first service context data of the target service to the intermediate server through the communication ticket; The ticket delivery module is used to deliver the communication ticket to the business collaboration terminal, so that the business collaboration terminal can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

[0013] A cross-device communication apparatus is also provided, applied to a business collaboration terminal, the apparatus comprising: The ticket acquisition module is used to acquire communication tickets transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration application for the target service to the intermediate server; The data acquisition module is used to acquire the first service context data of the target service from the intermediate server through the communication ticket; wherein the first service context data of the target service is sent by the service response terminal to the intermediate server through the communication ticket; The business processing module is used to complete the business processing interaction operation for the target business based on the first business context data.

[0014] In another aspect of this application, an electronic device is also provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used to store computer programs; and the processor, when executing the program stored in the memory, implements any of the aforementioned cross-device communication methods applied to the service response end.

[0015] In another aspect of this application, a computer-readable storage medium is also provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform any of the aforementioned methods for cross-device communication applied to a service response end.

[0016] In another aspect of this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to perform any of the aforementioned methods for cross-device communication applied to a business response end.

[0017] In this embodiment, in response to a service-triggered interaction operation targeting a specific service, a session registration request for the target service is initiated to an intermediate server. A communication ticket returned by the intermediate server based on the session registration request is received, and the first service context data of the target service is sent to the intermediate server via the communication ticket. The communication ticket is then transmitted to the service collaboration end, enabling the service collaboration end to obtain the first service context data from the intermediate server through the communication ticket and complete the service processing interaction operation targeting the target service based on the first service context data. This achieves cross-device communication through the intermediate server to complete service interaction operations. Furthermore, a single communication interaction initiated through registration avoids interaction between devices when no data exchange is needed, saving the intermediate server's performance and resources. Simultaneously, communication through the intermediate server prevents data hijacking by malicious actors during cross-device communication, thus preventing the acquisition of useful information. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0019] Figure 1 This is a flowchart illustrating the steps of an embodiment of a cross-device communication method according to this application; Figure 2 This is a flowchart illustrating the steps of another embodiment of the cross-device communication method of this application; Figure 3 This is a schematic diagram of the overall architecture of an embodiment of a cross-device communication method according to this application; Figure 4 This is a structural block diagram of an embodiment of a service response terminal device according to this application; Figure 5 This is a structural block diagram of an embodiment of a business collaboration terminal device according to this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0020] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0021] Reference Figure 1This is a flowchart illustrating the steps of an embodiment of a cross-device communication method according to this application. The method is applied to a service response end and includes the following steps: Step 101: In response to the business trigger interaction operation for the target business, initiate a session registration request for the target business to the intermediate server.

[0022] As an example, the business response end can be a video client on a video presentation device, where the video presentation device can be a TV device, a PC device, etc., and the video client can be an application installed on the video presentation device.

[0023] In step 101, when a user performs a target service operation on the video client of the video presentation device, the video client responds to the user's service trigger interaction operation for the target service. Under the current target service scenario, it can initiate a session registration request for the target service to the intermediate server. The target service being processed on the video client can be obtained from the service server.

[0024] In practical applications, the target business could be payment processing, questionnaire surveys, personal information entry, document viewing, etc. Redis (Remote Dictionary Server) can be used as the core supporting server. Redis is an open-source key-value store written in ANSI C, supporting network access and various data persistence methods, combining high-performance memory storage with reliable data persistence capabilities.

[0025] In some embodiments of this application, the step of initiating a session registration request for the target service to the intermediate server in response to a service-triggered interaction operation for the target service includes: Sub-step 11: In response to a business trigger interaction operation for the target business, determine the business type of the target business.

[0026] In sub-step 11, when a user performs an operation on the target service on the service response end, i.e., the video client on the video presentation device, the video client responds to the user's service trigger interaction operation for the target service, and the service type of the target service can be determined.

[0027] Sub-step 12: Based on the business type, determine whether to process the target business through the business collaboration terminal.

[0028] In sub-step 12, after determining the business type of the target business, a judgment can be made based on the business type of the target business to determine whether the target business is inconvenient to process at the business response end and needs to be processed through the business collaboration end.

[0029] As an example, the business collaboration end can be a mobile terminal device, such as a mobile phone or tablet.

[0030] Sub-step 13: If it is determined that the target service needs to be processed through the business collaboration terminal, a session registration request for the target service is initiated to the intermediate server.

[0031] In sub-step 13, if it is determined that the target service needs to be processed through a mobile terminal device based on the service type of the target service, a session registration request for the target service can be initiated to the intermediate server.

[0032] For example, when the target task involves payment, the video client is not convenient to make payments directly, so the collaboration of the business collaboration end, i.e., the mobile terminal device, is required to complete the payment. When the target task involves document surveys, the video client of the video presentation device faces the scenario of inputting long characters, which is cumbersome to operate with a remote control. The collaboration of the business collaboration end is required to complete the questionnaire on the mobile terminal device, and so on.

[0033] Specifically, if the target service needs to be processed through a mobile terminal device, a scenario of continuous interactive operation across devices and terminals arises. In reality, video presentation devices and mobile terminal devices may be unable to directly exchange information due to inconsistencies in hardware and communication protocols. Therefore, this application employs a "medium" to complete bidirectional communication, and the communication data can also be recorded, tracked, queried, and monitored on the "medium." This "medium" is an intermediate server.

[0034] Step 102: Receive the communication ticket returned by the intermediate server based on the session registration application, and send the first service context data of the target service to the intermediate server through the communication ticket.

[0035] In step 102, the intermediate server sends a communication ticket for the target service to the video client based on the session registration request sent by the video client (service response end). After receiving the communication ticket sent by the intermediate server, the video client can use the communication ticket to send the first service context data of the current target service to the intermediate server, and then the intermediate server can store the first service context data.

[0036] As an example, the core index for initiating cross-platform business interactions varies depending on the target business. That is, the first business context data can be different types of data depending on the specific business. For instance, if the target business is a payment business, the first business context data could be the unique number of the order to be paid, the payment type, and the token; if the target business is a questionnaire survey business, the first business context data could be the questionnaire template ID, the batch number, and the temporary identifier of the respondent; if the target business is personal information entry, the first business context data could be the business code of the form to be filled out, the user session token, and the key list of required fields; if the target business is document viewing, the first business context data could be the document's resource ID, access authorization code, and version hash.

[0037] Step 103: Transmit the communication ticket to the business collaboration terminal so that the business collaboration terminal can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

[0038] In step 103, after the video client receives the communication ticket returned by the intermediate server, it can transmit the communication ticket to the mobile terminal device (service collaboration end) so that the mobile terminal device can obtain the first service context data of the target service from the intermediate server through the communication ticket. After the mobile terminal device obtains the first service context data of the target service, it can obtain the service data that needs to be interactively processed by the target service from the service server based on the first service context data, thereby completing the service processing interaction operation for the target service.

[0039] In some embodiments of this application, transmitting the communication ticket to the business collaboration terminal includes: Sub-step 21: Generate a cross-terminal communication QR code based on the communication ticket.

[0040] In sub-step 21, the video client can generate a cross-platform communication QR code for cross-platform communication information based on the received communication ticket. As an example, the cross-platform communication QR code can be a URL link, and the communication ticket can exist in the URL link as a URL link parameter.

[0041] Sub-step 22: The communication ticket is transmitted to the business collaboration terminal via the cross-terminal communication QR code.

[0042] In sub-step 22, after generating the cross-platform communication QR code, the video client can display it on the screen. The mobile terminal device can scan this QR code using a relevant application installed on the device to obtain a URL link containing a communication ticket, transmitted by the video client via the QR code. In one example, if the target business is a payment service, the relevant application could be a payment application; if the target business is a personal information entry service, the relevant application could be a video client installed on the mobile terminal device or other applications capable of scanning QR codes.

[0043] In some embodiments of this application, after transmitting the communication ticket to the business collaboration terminal, the method further includes: The intermediate server is periodically queried using the communication ticket to obtain second business context data; wherein, the second business context data is the business context data of the business processing interaction operation sent by the business collaboration terminal to the intermediate server.

[0044] Specifically, after completing the business processing interaction operation for the target business, the mobile terminal device (business collaboration end) can obtain the second business context data for the target business. Then, the mobile terminal device can send the second business context data to the intermediate server through the communication ticket to modify the first business context data of the target business in the intermediate server.

[0045] However, since the video client and the mobile terminal device cannot communicate directly, the video client is unaware of when the mobile terminal device will send the second business context data after the business processing interaction to the intermediate server. Therefore, the video client can periodically query the intermediate server through communication tickets, that is, listen for changes in the data located on the intermediate server. If a change is found, the video client can obtain the second business context data after the business processing interaction from the intermediate server. The periodic query period can be once per second.

[0046] It should be further explained that when a target service may require multiple communications between the video client and the mobile terminal device—that is, when the processing of a target service includes multiple stages, with one stage handled by the video client and another by the mobile terminal device—the second service context data sent by the mobile terminal device to the intermediate server before the target service is finally completed can be considered new service context data. This allows the video client to continue processing the target service based on the second service context data sent by the mobile terminal device. Conversely, if a target service only requires one communication between the video client and the mobile terminal device, or if the mobile terminal device's interaction with the target service is in the final stage, the second service context data sent by the mobile terminal device can be the operation result for the target service. This result could be service completion, service failure, service timeout, etc.

[0047] In some embodiments of this application, after periodically querying the intermediate server using the communication ticket to obtain the second business context data, the method further includes: Based on the second business context data, business association information for the target business is displayed.

[0048] After the video client periodically queries the intermediate server using communication tickets to obtain the second business context data, the video client can display business association information for the target business based on the second business context data.

[0049] Specifically, the video client can access the business server based on the second business context data to obtain business-related information for the target business. One type is prompt information to encourage the user to continue with subsequent interactive operations, as well as subsequent business information of the target business that requires further interactive operations. At this time, the user can continue to process the subsequent business information of the target business based on the prompt information. The other type is status information such as business processing completion, business processing timeout, and business processing failure. After obtaining this type of business-related information, the video client can directly present this status information.

[0050] In one example, the second context data can be the corresponding information for the target business obtained from the business server after the target business has been processed at the business collaboration end. For example, if the target business is a payment business, the second context data can be the transaction serial number, payment result status, and payment completion time; if the target business is a questionnaire survey business, the second context data can be the answer record ID, submission timestamp, and answer summary; if the target business is personal information entry business, the second context data can be the submission record ID, the structured data entered by the user, and the submission status; if the target business is document viewing business, the second context data can be the reading progress, the list of annotations, and the reading time.

[0051] In some embodiments of this application, after displaying preset prompt information for the target service based on the second service context data, the method further includes: An unregistration request is initiated to the intermediate server so that the intermediate server can clean up the second business context data and cancel the communication ticket.

[0052] Specifically, after the video client periodically queries the intermediate server using communication tickets to obtain the second business context data, if the second business context data is the processing result of the target business interaction operation, the video client can initiate an unregistration request to the intermediate server using communication tickets, so that the intermediate server can clean up the second business context data and cancel the communication tickets.

[0053] It should be noted that communication tickets can also be used for processing multiple services. That is, if the second service context data is the processing result of the target service interaction operation, the video client does not need to initiate an unregistration request to the intermediate server, and when processing new services obtained from the service server, it can continue to use the communication ticket to communicate with the mobile terminal device across devices to process the new services.

[0054] In this embodiment, in response to a service-triggered interaction operation targeting a specific service, a session registration request for the target service is initiated to an intermediate server. A communication ticket returned by the intermediate server based on the session registration request is received, and the first service context data of the target service is sent to the intermediate server via the communication ticket. The communication ticket is then transmitted to the service collaboration end, enabling the service collaboration end to obtain the first service context data from the intermediate server through the communication ticket and complete the service processing interaction operation targeting the target service based on the first service context data. This achieves cross-device communication through the intermediate server to complete service interaction operations. Furthermore, a single communication interaction initiated through registration avoids interaction between devices when no data exchange is needed, saving the intermediate server's performance and resources. Simultaneously, communication through the intermediate server prevents data hijacking by malicious actors during cross-device communication, thus preventing the acquisition of useful information.

[0055] Reference Figure 2 This is a flowchart illustrating the steps of another embodiment of a cross-device communication method according to this application. The method is applied to a service collaboration end and includes the following steps: Step 201: Obtain the communication ticket transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration application for the target service to the intermediate server.

[0056] In step 201, the service collaboration end can be a mobile terminal device. The mobile terminal device can scan the cross-terminal communication QR code on the screen of the video presentation device through the relevant application installed on the mobile terminal device, thereby obtaining the URL link containing the communication ticket transmitted by the video client through the cross-terminal communication QR code.

[0057] The video client (service response end) can respond to service-triggered interactive operations targeting a specific service by initiating a session registration request for that service to the intermediate server. The intermediate server then returns a communication ticket based on this request. The video client can then generate a cross-platform communication QR code for cross-platform communication information based on the obtained communication ticket.

[0058] In one example, the cross-platform communication QR code can be a URL link, and the communication ticket can exist as a URL link parameter within the URL link. Furthermore, if the target business is a payment business, the relevant application can be a payment application; if the target business is a personal information entry business, the relevant application can be a video client installed on a mobile terminal device or other applications capable of scanning QR codes. The mobile terminal device or video client can generate a cross-platform communication QR code for cross-platform communication information based on the received communication ticket. As an example, the cross-platform communication QR code can be a URL link, and the communication ticket can exist as a URL link parameter within the URL link.

[0059] Step 202: Obtain the first service context data of the target service from the intermediate server through the communication ticket; wherein, the first service context data of the target service is sent by the service response end to the intermediate server through the communication ticket.

[0060] In step 202, after the mobile terminal device (business collaboration end) obtains the URL link containing the communication ticket transmitted by the video client through the cross-terminal communication QR code, it can access the intermediate server based on the URL link to obtain the first business context data of the target business from the intermediate server.

[0061] The first business context data of the target service is sent by the video client to the intermediate server via a communication ticket.

[0062] Step 203: Based on the first business context data, complete the business processing interaction operation for the target business.

[0063] In step 203, after the mobile terminal device obtains the first service context data from the intermediate server, the mobile terminal device can perform service processing on the target service based on the first service context data to complete the service processing interaction operation for the target service.

[0064] In some embodiments of this application, the step of completing the business processing interaction operation for the target business based on the first business context data includes: Sub-step 31: Based on the first business context data, obtain the business data of the target business from the business server.

[0065] In sub-step 31, the mobile terminal device can access the business server based on the first business context data obtained from the intermediate server, so as to obtain the business data that the target business currently needs to be processed on the mobile terminal device.

[0066] Sub-step 32: Based on the business data, complete the business processing interaction operation for the target business.

[0067] In sub-step 32, the user processes the business data of the target service on the mobile terminal device and sends the processed business data to the business server. The business server returns the second context data for the target service to the mobile terminal device, thereby completing the business processing interaction operation for the target service.

[0068] After obtaining the second context data for the target service, the mobile terminal device can send the second context data for the target service to the intermediate server through a communication ticket, so as to modify the first service context data of the target service in the intermediate server.

[0069] However, since the video client and the mobile terminal device cannot communicate directly, the video client is unaware of when the mobile terminal device will send the second business context data after the business processing interaction to the intermediate server. Therefore, the video client needs to periodically query the intermediate server using communication tickets, that is, to listen for changes in the data located on the intermediate server. If a change is found, the video client can obtain the second business context data after the business processing interaction from the intermediate server and continue with subsequent processing steps. The periodic query period can be once per second.

[0070] In some embodiments of this application, after the business collaboration end sends the second context data for the target business to the intermediate server via a communication ticket to modify the first business context data of the target business in the intermediate server, the method further includes: An unregistration request is initiated to the intermediate server so that the intermediate server can clean up the second business context data and cancel the communication ticket.

[0071] Specifically, after the mobile terminal device sends the second context data for the target service to the intermediate server through a communication ticket to modify the first service context data of the target service in the intermediate server, if the second service context data is the processing result of the target service interaction operation, the mobile terminal device can initiate an unregistration application to the intermediate server through the communication ticket, so that the intermediate server can clean up and cancel the communication ticket corresponding to the data (i.e. the second service context data).

[0072] It should be noted that communication tickets can also be used for processing multiple services. That is, if the second service context data is the processing result of the target service interaction operation, the mobile terminal device may not initiate an unregistration application to the intermediate server. This allows the video client to continue using the communication ticket to communicate with the mobile terminal device across devices when processing new services obtained from the service server, in order to process the new services, or to wait for the intermediate server to automatically rescind and clear the service at regular intervals.

[0073] Furthermore, as discussed earlier, the deregistration request can be initiated by either the video client (business response end) or the mobile terminal device (business collaboration end). However, this deregistration request only needs to be initiated once; that is, one end, either the video client or the mobile terminal device, needs to send the deregistration request to the intermediate server, and the other end does not need to send a separate deregistration request to the intermediate server. Alternatively, neither end can send a deregistration request, so that the communication ticket can be used for processing new tasks.

[0074] In this embodiment, in response to a service-triggered interaction operation targeting a specific service, a session registration request for the target service is initiated to an intermediate server. A communication ticket returned by the intermediate server based on the session registration request is received, and the first service context data of the target service is sent to the intermediate server via the communication ticket. The communication ticket is then transmitted to the service collaboration end, enabling the service collaboration end to obtain the first service context data from the intermediate server through the communication ticket and complete the service processing interaction operation targeting the target service based on the first service context data. This achieves cross-device communication through the intermediate server to complete service interaction operations. Furthermore, a single communication interaction initiated through registration avoids interaction between devices when no data exchange is needed, saving the intermediate server's performance and resources. Simultaneously, communication through the intermediate server prevents data hijacking by malicious actors during cross-device communication, thus preventing the acquisition of useful information.

[0075] Reference Figure 3 This is a schematic diagram of the overall architecture of a cross-device communication method embodiment of this application, specifically including the overall architecture of cross-device communication and the interaction process of cross-device communication.

[0076] First, as attached Figure 3 As shown, the cross-platform communication interaction process specifically includes the following steps: On the business response side, this can be the video client of the video presentation device: 1. Business scenario initiation: On the TV or PC, in response to a business-triggered interactive operation targeting the target business, a session registration application for the target business under the business scenario is initiated to the intermediate server. 2. The intermediate server returns a communication ticket to the TV or PC client based on the session registration request, and the TV or PC client receives the communication ticket; 3. The TV or PC terminal generates a cross-terminal communication QR code based on the communication ticket and transmits the communication ticket to the mobile terminal device through the cross-terminal communication QR code; 4. Automatic status polling, which means periodically querying the intermediate server through communication tickets to obtain the second business context data. The second business context data is the business context data of the business processing interaction operation sent by the mobile terminal to the intermediate server. 5. Business layer processing, which is based on the second business context data, displays business association information for the target business, so that the user can continue to process the subsequent target business in the business association information based on the prompts in the business association information, or learn about the operation status information of the target business; 6. Interaction complete, that is, the target business processing is completed. After the target business processing is completed, the video client can send an unregistration request to the intermediate server so that the intermediate server can clean up the data corresponding to the communication ticket and cancel the communication ticket.

[0077] On the business collaboration end, i.e., mobile terminal devices: 1. Obtain the communication ticket sent, that is, obtain the communication ticket transmitted by the video client. The communication ticket is the video client's response to the business trigger interaction operation for the target service, which is obtained by initiating a session registration request for the target service to the intermediate server; 2. Perform business processing interaction operations. Obtain the first business context data of the target business from the intermediate server through communication tickets, and complete the business processing interaction operations for the target business based on the first business context data. 3. Operation complete, communication ticket cancellation: The mobile terminal device can also initiate an unregistration request to the intermediate server, allowing the server to clean up and cancel the data corresponding to the communication ticket. It's important to note that the unregistration request only needs to be sent by either the mobile terminal device or the video client; neither end needs to send the request.

[0078] Secondly, regarding the architecture of the intermediate server and database: To address memory release, server resource recycling, and periodic resource reclamation, the intermediate server can add an additional layer of automatic timed data cleanup and reclamation capabilities. That is, even if neither the video client nor the mobile terminal device sends an unregistration request, the intermediate server can periodically clean up the relevant data and communication tickets of the business types that need to be cleaned up, thereby releasing memory and enabling the intermediate server to periodically reclaim server resources so that server resources can be recycled.

[0079] The database connected to the intermediate service needs to be used for subsequent integration with four major system modules: monitoring / risk control, user behavior analysis, AI data supplementation, and customer service. Specifically, a high-performance database can be set up behind the intermediate server to persistently store data. Here, persistent data refers to user actions during cross-device communication. When users communicate across devices through the intermediate server, in addition to fulfilling the functions mentioned above, the intermediate server can also record user actions related to business operations and persistently store these actions in the database.

[0080] After recording user actions, the database can observe the user's account based on these actions, thereby enabling account monitoring and risk control. For example, if a user conducts multiple surveys during cross-device communication through an intermediary server, the database can detect potential fraudulent activity related to order placement. Furthermore, user actions can be analyzed, and customer service systems can use the database to investigate anomalies.

[0081] Furthermore, based on user behavior records in the database, AI can intelligently identify and fill in information gaps or behavioral sequence breaks in key business scenarios, thereby forming a more complete and coherent record of user behavior. This AI-assisted data supplementation can improve the accuracy and real-time performance of user behavior records in areas such as risk warnings, behavior predictions, and personalized services, providing a more reliable data foundation for overall business decision-making.

[0082] As can be seen, setting up a high-performance database behind the intermediate server for persistent data storage can further improve the utilization rate of communication data and enhance the value of data use.

[0083] In this embodiment, in response to a service-triggered interaction operation targeting a specific service, a session registration request for the target service is initiated to an intermediate server. A communication ticket returned by the intermediate server based on the session registration request is received, and the first service context data of the target service is sent to the intermediate server via the communication ticket. The communication ticket is then transmitted to the service collaboration end, enabling the service collaboration end to obtain the first service context data from the intermediate server through the communication ticket and complete the service processing interaction operation targeting the target service based on the first service context data. This achieves cross-device communication through the intermediate server to complete service interaction operations. Furthermore, a single communication interaction initiated through registration avoids interaction between devices when no data exchange is needed, saving the intermediate server's performance and resources. Simultaneously, communication through the intermediate server prevents data hijacking by malicious actors during cross-device communication, thus preventing the acquisition of useful information.

[0084] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of this application are not limited to the described order of actions, because according to the embodiments of this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of this application.

[0085] Reference Figure 4 The diagram illustrates a structural block diagram of an embodiment of a service response terminal device according to this application, which may specifically include the following modules: The registration module 401 is used to initiate a session registration application for the target service to the intermediate server in response to a business-triggered interactive operation for the target service. The ticket receiving module 402 is used to receive the communication ticket returned by the intermediate server based on the session registration application, and send the first service context data of the target service to the intermediate server through the communication ticket; The ticket delivery module 403 is used to deliver the communication ticket to the business collaboration terminal, so that the business collaboration terminal can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

[0086] Optionally, the registration module 401 includes: The business determination submodule is used to determine the business type of the target business in response to a business trigger interaction operation for the target business. The processing and judgment submodule is used to determine whether to process the target business through the business collaboration terminal based on the business type. The request sending submodule is used to initiate a session registration request for the target service to the intermediate server when it is determined that the target service needs to be processed through the business collaboration terminal.

[0087] Optionally, the ticket delivery module 403 includes: The QR code generation submodule is used to generate a cross-terminal communication QR code based on the communication ticket; The QR code display submodule is used to transmit the communication ticket to the business collaboration terminal via the cross-terminal communication QR code.

[0088] Optionally, after transmitting the communication ticket to the business collaboration terminal, the method further includes: The result query module is used to periodically query the intermediate server using the communication ticket to obtain second business context data; wherein, the second business context data is the business context data of the business processing interaction operation sent by the business collaboration terminal to the intermediate server.

[0089] Optionally, after periodically querying the intermediate server using the communication ticket to obtain the second business context data, the method further includes: The prompt display module is used to display business association information for the target business based on the second business context data.

[0090] Optionally, after displaying preset prompt information for the target service based on the second service context data, the method further includes: The unregistration module is used to initiate an unregistration request to the intermediate server, so that the intermediate server can clean up the second business context data and cancel the communication ticket.

[0091] Reference Figure 5 The diagram illustrates a structural block diagram of an embodiment of a business collaboration terminal according to this application, which may specifically include the following modules: The ticket acquisition module 501 is used to acquire the communication ticket transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration application for the target service to the intermediate server; The data acquisition module 502 is used to acquire the first service context data of the target service from the intermediate server through the communication ticket; wherein the first service context data of the target service is sent by the service response terminal to the intermediate server through the communication ticket; The business processing module 503 is used to complete the business processing interaction operation for the target business based on the first business context data.

[0092] Optionally, the service processing module 503 includes: The business data acquisition submodule is used to acquire the business data of the target business from the business server based on the first business context data; The business data processing submodule is used to complete business processing interaction operations for the target business based on the business data.

[0093] In this embodiment, in response to a service-triggered interaction operation targeting a specific service, a session registration request for the target service is initiated to an intermediate server. A communication ticket returned by the intermediate server based on the session registration request is received, and the first service context data of the target service is sent to the intermediate server via the communication ticket. The communication ticket is then transmitted to the service collaboration end, enabling the service collaboration end to obtain the first service context data from the intermediate server through the communication ticket and complete the service processing interaction operation targeting the target service based on the first service context data. This achieves cross-device communication through the intermediate server to complete service interaction operations. Furthermore, a single communication interaction initiated through registration avoids interaction between devices when no data exchange is needed, saving the intermediate server's performance and resources. Simultaneously, communication through the intermediate server prevents data hijacking by malicious actors during cross-device communication, thus preventing the acquisition of useful information.

[0094] This application also provides an electronic device, such as... Figure 6 As shown, it includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, wherein the processor 601, the communication interface 602, and the memory 603 communicate with each other through the communication bus 604. Memory 603 is used to store computer programs; When processor 601 executes a program stored in memory 603, it performs the following steps: In response to a business-triggered interactive operation targeting a specific business, a session registration request for the target business is initiated to the intermediate server; Receive the communication ticket returned by the intermediate server based on the session registration request, and send the first service context data of the target service to the intermediate server through the communication ticket; The communication ticket is transmitted to the business collaboration end so that the business collaboration end can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

[0095] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0096] The communication interface is used for communication between the aforementioned terminal and other devices.

[0097] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0098] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0099] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform any of the cross-device communication methods applied to a service response end in the above embodiments.

[0100] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to perform any of the cross-device communication methods applied to the business response end in the above embodiments.

[0101] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0102] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0103] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0104] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A method for cross-device communication, characterized in that, Applied to the business response end, the method includes: In response to a business-triggered interactive operation targeting a specific business, a session registration request for the target business is initiated to the intermediate server; Receive the communication ticket returned by the intermediate server based on the session registration request, and send the first service context data of the target service to the intermediate server through the communication ticket; The communication ticket is transmitted to the business collaboration end so that the business collaboration end can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

2. The method according to claim 1, characterized in that, The step of initiating a session registration request for the target service to the intermediate server in response to a service-triggered interactive operation for the target service includes: In response to a business-triggered interactive operation targeting a specific business, the business type of the target business is determined; Based on the business type, determine whether to process the target business through the business collaboration terminal; If it is determined that the target service needs to be processed through the business collaboration terminal, a session registration request for the target service is initiated to the intermediate server.

3. The method according to claim 1, characterized in that, The transmission of the communication ticket to the business collaboration terminal includes: Based on the communication ticket, a cross-platform communication QR code is generated; The communication ticket is transmitted to the business collaboration terminal via the cross-terminal communication QR code.

4. The method according to any one of claims 1-3, characterized in that, After transmitting the communication ticket to the business collaboration terminal, the process also includes: The intermediate server is periodically queried using the communication ticket to obtain second business context data; wherein, the second business context data is the business context data of the business processing interaction operation sent by the business collaboration terminal to the intermediate server.

5. The method according to claim 4, characterized in that, After periodically querying the intermediate server using the communication ticket to obtain the second business context data, the method further includes: Based on the second business context data, business association information for the target business is displayed.

6. The method according to claim 5, characterized in that, After displaying preset prompts for the target service based on the second service context data, the method further includes: An unregistration request is initiated to the intermediate server so that the intermediate server can clean up the second business context data and cancel the communication ticket.

7. A method for cross-device communication, characterized in that, Applied to business collaboration, the method includes: Obtain the communication ticket transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration request for the target service to the intermediate server; The first service context data of the target service is obtained from the intermediate server through the communication ticket; wherein, the first service context data of the target service is sent by the service response end to the intermediate server through the communication ticket. Based on the first business context data, complete the business processing interaction operation for the target business.

8. The method according to claim 7, characterized in that, The step of completing the business processing interaction operation for the target business based on the first business context data includes: Based on the first business context data, obtain the business data of the target business from the business server; Based on the business data, complete the business processing interaction operation for the target business.

9. A device for cross-device communication, characterized in that, The device, applied to the business response end, includes: The registration module is used to initiate a session registration request for the target service to the intermediate server in response to a business-triggered interactive operation for the target service. The ticket receiving module is used to receive the communication ticket returned by the intermediate server based on the session registration application, and send the first service context data of the target service to the intermediate server through the communication ticket; The ticket delivery module is used to deliver the communication ticket to the business collaboration terminal, so that the business collaboration terminal can obtain the first business context data from the intermediate server through the communication ticket, and complete the business processing interaction operation for the target business based on the first business context data.

10. A device for cross-device communication, characterized in that, The device, used in business collaboration, includes: The ticket acquisition module is used to acquire communication tickets transmitted by the service response end; wherein, the communication ticket is obtained by the service response end in response to a service trigger interaction operation for the target service by initiating a session registration application for the target service to the intermediate server; The data acquisition module is used to acquire the first service context data of the target service from the intermediate server through the communication ticket; wherein the first service context data of the target service is sent by the service response terminal to the intermediate server through the communication ticket; The business processing module is used to complete the business processing interaction operation for the target business based on the first business context data.

11. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the method as described in any one of claims 1 to 6.

12. A readable storage medium, characterized in that, A computer program is stored on the readable storage medium, which, when executed by a processor, implements the method as described in any one of claims 1 to 6.

Images