CN116737404A - Method and terminal equipment for application connection - Google Patents

Abstract

This application provides a method and terminal device for application connection, which is beneficial to flexibly allocate communication resources to the terminal device to realize communication between the application and the connection service in the computer manager. The method includes: in response to the user's operation of clicking the icon of the first application, obtaining an identification of a target bit in the shared memory. The target bit is a bit whose value is a first preset value, and the first preset value represents the target bit. The corresponding communication channel is not used; based on the identification of the target bit, a communication identification corresponding to the target bit is determined, and the communication identification indicates at least one communication channel used for communication between the first application and the computer manager; based on the at least one communication channel, the first communication channel is implemented Data transmission between an application and computer manager.

Description

Method and terminal equipment for application connection

Technical field

The present application relates to the field of terminals, and in particular, to a method for application connection and a terminal device.

Background technique

At present, application connection across devices will become an important function in subsequent multi-device scenarios. Among them, application connection can be understood as that when a user uses an application on a personal computer (PC), the user can continue the usage status of the application on a mobile phone that meets the connection conditions and continue to use the application on the mobile phone. .

For PCs in application connection scenarios, in order to synchronize the application usage status to other devices, or to synchronize the application usage status of other devices to the PC, the PC needs to provide an external connection framework and software development kit (software). development kit, SDK) to meet this need. Among them, the connection framework provides a unified application status synchronization framework for applications. The application needs to access the connection framework through the SDK to realize data transmission with the connection service in the connection framework. The connection service relies on Computer Butler to provide external service capabilities for the application. . After the application and computer manager in the PC are started, the application and computer manager run in two different processes. The application needs to communicate with the connection service in the computer manager through interprocess communication (IPC).

Therefore, how to allocate IPC communication resources to applications on the PC side to achieve communication between the application and the connection service in the computer manager is an urgent problem that needs to be solved.

Contents of the invention

This application provides a method and terminal equipment for application connection, which is conducive to flexibly allocating IPC communication resources to the terminal equipment to realize communication between the application and the connection service in the computer manager.

In a first aspect, a method for application connection is provided, which is applied to a terminal device. The terminal device is a sending end or a receiving end of application connection. The terminal device is installed with a first application and a computer manager. The method includes: responding When the user clicks on the icon of the first application, the identification of the target bit in the shared memory is obtained. The target bit is a bit whose value is a first preset value. The first preset value indicates that the communication channel corresponding to the target bit has not been is used; based on the identification of the target bit, determine the communication identification corresponding to the target bit, the communication identification indicates at least one communication channel for communication between the first application and the computer manager; realize the communication between the first application and the computer manager based on at least one communication channel data transmission between.

In this application, the computer manager is integrated with a connection service manager (hereinafter also referred to as the connection service). The first application communicates with the computer manager, including the connection between the connection service SDK of the first application and the connection service in the computer manager. Communication. After the first application and the computer manager are started, the connection service runs in the computer manager. The first application is connected to the SDK as an independent process and runs in the third-party application. Therefore, the first application needs to perform cross-process communication with the connection service in the computer manager through the connection service SDK.

In some scenarios, there may be at least one application accessing the connection service in order to achieve application connection. In this scenario, the computer manager needs to have the ability to communicate with all applications accessing the connection service through IPC. In the technical solution provided by this application, for the first application in at least one application of the access connection service, the terminal device can obtain the identification of the target bit in the shared memory, and obtain the corresponding communication identification based on the identification of the target bit, Allocate at least one communication channel corresponding to the communication identifier to the first application, so that the first application communicates with the connection service in the computer manager through the IPC communication resource. In this way, by combining IPC communication and shared memory, the terminal device can flexibly allocate IPC communication resources to all applications accessing the connection service, realizing data transmission between the application and the computer manager in the application connection scenario.

In connection with the first aspect, in some implementations of the first aspect, the method further includes: based on obtaining the identifier of the target bit, modifying the value of the target bit from the first preset value to the second preset value , the second preset value indicates that the communication channel corresponding to the target bit has been used.

In this application, after determining the target bit, the terminal device can modify the value of the target bit from the first preset value to the second preset value to identify that the communication channel corresponding to the target bit has been applied for or has been used. use. In this way, when a new application accesses the connection service, the terminal device can apply for other communication channels corresponding to the bits whose values are the first preset values for the new application, thereby realizing flexible allocation of IPC communication resources.

Optionally, the terminal device may detect the values of multiple bits in the shared memory in response to the user's operation of clicking the icon of the first application, and determine that the value of the multiple bits is the target bit of the first preset value. Bit. After determining the target bit, the terminal device can obtain the identifier of the target bit. Moreover, after determining the target bit, the terminal device may modify the value of the target bit from the first preset value to the second preset value. The order in which the terminal device obtains the identification of the target bit and modifies the value of the target bit from the first preset value to the second preset value is not limited.

In conjunction with the first aspect, in some implementations of the first aspect, implementing data transmission between the first application and the computer manager based on at least one communication channel includes: based on the first communication channel in the at least one communication channel, Register connection services and callbacks.

In this application, each of the at least one communication channel allocated by the terminal device to the first application can transmit different types of messages to the user. The first communication channel is used for the first application registration connection service and callback. This makes data transmission in application connection scenarios more convenient and efficient.

In connection with the first aspect, in some implementations of the first aspect, the method further includes: when the process of the first application exits, modifying the value of the target bit from the second preset value to the first preset value. value.

In this application, the process exit of the first application includes two situations: normal exit and abnormal exit of the process of the first application. After the process of the first application exits, the terminal device can modify the value of the target bit from the second preset value to the first preset value and release the communication channel occupied by the first application. In this way, in the case of limited IPC communication resources Next, other applications can use the communication channel corresponding to the target bit, improving resource utilization.

In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: deregistering the connection service and callback based on the second communication channel in the at least one communication channel; deregistering the connection service and callback based on , confirm that the process of the first application exits.

In this application, when the first application exits normally, the terminal device can deregister the connection service and callback through the second communication channel allocated for the first application. After the connection service in the terminal device receives the message of deregistering the connection service and the callback, it can be determined that the process of the first application exits normally, and then the terminal device can release the communication channel allocated for the first application.

In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: after successfully registering the connection service and the callback, regularly querying whether the process of the first application has exited.

In this application, the terminal device monitors the status of the process of the first application in a timely manner by regularly querying whether the process of the first application has exited.

For example, the terminal device regularly sends a keep-alive packet to the first application through the computer manager. If the process of the first application is still running, the computer manager can successfully send the keep-alive packet; if the process of the first application exits abnormally, the computer manager The housekeeper cannot successfully send the keep-alive package. The terminal device determines whether the process of the first application has exited based on whether the computer manager successfully sends the keep-alive packet.

Combined with the first aspect, in some implementations of the first aspect, the terminal device is the sending end of the application connection; in the case where the first application is started before the computer housekeeper, or the computer housekeeper process exits abnormally, the method also includes :Broadcast communication reconnection message. The communication reconnection message is used to instruct the first application to connect to the computer manager. Registering the connection service and callback based on the first communication channel in the at least one communication channel includes: in the case of receiving a communication connection message based on the third communication channel in the at least one communication channel, registering based on the first communication channel Continuation services and callbacks.

In this application, the computer housekeeper's connection service can broadcast a communication reconnection message during the startup process. After the first application receives the communication reconnection message on the third communication channel, it can determine that the computer housekeeper has been started and can connect normally. Therefore, the first application can register the connection service and callback based on the first communication channel.

In connection with the first aspect, in some implementations of the first aspect, the terminal device is the receiving end of the application connection; in response to the operation of the user clicking the icon of the first application, the identification of the target bit in the shared memory is obtained , including: in response to the user's operation of clicking the icon of the first application located on the taskbar of the terminal device, obtaining the identification of the target bit in the shared memory.

In this application, as the application connection receiving end, the task bar of the terminal device can display the connection notification, and the connection notification can be displayed in the task bar in the form of an icon of the first application. In this way, the user can click the icon of the first application in the taskbar to start the first application on the terminal device as the receiving end, and then apply for a communication channel for the first application to communicate with the computer manager, so that the first application can connect to other The connection data of the first application on the device, for example, the editing content of the memo, audio data, etc.

Combined with the first aspect, in some implementations of the first aspect, the terminal device is the sending end of the application connection; in response to the user's operation of clicking the icon of the first application, obtaining the identification of the target bit in the shared memory includes: responding When the user clicks on the icon of the first application located on the desktop or taskbar of the terminal device, the identification of the target bit in the shared memory is obtained.

In this application, as the sender of the application connection, the terminal device can display the icon of the first application on the desktop or taskbar. When the user clicks (for example, double-clicks) the icon of the first application on the desktop or taskbar, the terminal device can start the first application on the terminal device as the sender, and perform corresponding operations in the first application, such as editing. Notes, play music, etc.

A second aspect provides a terminal device, including an acquisition module and a processing module for executing the method in any possible implementation of the first aspect.

Wherein, the acquisition module is configured to: in response to the user's operation of clicking the icon of the first application, acquire the identification of a target bit in the shared memory, where the target bit is a bit with a value of a first preset value, and the The first preset value indicates that the communication channel corresponding to the target bit is not used. The processing module is configured to: based on the identification of the target bit, determine the communication identification corresponding to the target bit, the communication identification indicating at least one communication channel for communication between the first application and the computer manager; implement the first application based on the at least one communication channel Data transfer to and from Computer Manager.

In connection with the second aspect, in some implementations of the second aspect, the processing module is configured to: based on obtaining the identifier of the target bit, modify the value of the target bit from the first preset value to the second preset value , the second preset value indicates that the communication channel corresponding to the target bit has been used.

Combined with the second aspect, in some implementations of the second aspect, the processing module is configured to: register the connection service and the callback based on the first communication channel in the at least one communication channel.

In conjunction with the second aspect, in some implementations of the second aspect, the processing module is configured to: when the process of the first application exits, modify the value of the target bit from the second preset value to the first preset value. value.

In connection with the second aspect, in some implementations of the second aspect, the processing module is configured to: deregister the connection service and the callback based on the second communication channel in the at least one communication channel; and, based on the connection service and the callback Unregister and confirm that the process of the first application exits.

Combined with the second aspect, in some implementations of the second aspect, the processing module is configured to: after successfully registering the connection service and callback, regularly query whether the process of the first application has exited.

Combined with the second aspect, in some implementations of the second aspect, the terminal device is the sender of the application connection. In the case where the first application is started before the computer manager, or the process of the computer manager exits abnormally, the processing module is used to: broadcast a communication reconnection message, and the communication reconnection message is used to instruct the first application to connect to the computer manager; and, based on When the third communication channel in at least one communication channel receives the communication connection message, the connection service and callback are registered based on the first communication channel.

Combined with the second aspect, in some implementations of the second aspect, the terminal device is the receiving end of the application connection. The processing module is configured to: in response to the user's operation of clicking the icon of the first application located on the taskbar of the terminal device, obtain the identification of the target bit in the shared memory.

Combined with the second aspect, in some implementations of the second aspect, the terminal device is the sender of the application connection. The processing module is configured to: in response to the user's operation of clicking the icon of the first application located on the desktop or taskbar of the terminal device, obtain the identification of the target bit in the shared memory.

In a third aspect, another terminal device is provided, including a processor and a memory. The processor is coupled to the memory. The memory can be used to store a computer program. The processor can be used to call and execute the computer program in the memory to achieve the above. A method in any possible implementation manner of the first aspect.

In the fourth aspect, a processor is provided, including: an input circuit, an output circuit and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the processor executes the method in any of the possible implementations of the first aspect.

In the specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times. This application does not limit the specific implementation methods of the processor and various circuits.

In a fifth aspect, a processing device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any of the possible implementations of the first aspect.

Optionally, there are one or more processors and one or more memories.

Alternatively, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

In the specific implementation process, the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, this application does not limit the type of memory and the arrangement of the memory and the processor.

It should be understood that the relevant data interaction process, for example, sending instruction information may be a process of outputting instruction information from the processor, and receiving capability information may be a process of the processor receiving input capability information. Specifically, the data output by the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and receiver can be collectively called a transceiver.

The processing device in the above fifth aspect can be a chip, and the processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, When implemented, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor, or can be located outside the processor and exist independently.

In a sixth aspect, a computer program product is provided. The computer program product includes: computer program code. When the computer program code is run, it causes the computer to execute the method in any of the possible implementations of the first aspect.

In a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is run, it causes the computer to execute the method in any of the possible implementations of the first aspect. .

Description of drawings

Figure 1 is a schematic diagram of a scenario provided by an embodiment of the present application;

Figure 2 is a schematic diagram of an application connection interface provided by an embodiment of the present application;

Figure 3 is a schematic structural diagram of a terminal device applicable to the embodiment of the present application;

Figure 4 is a software structure block diagram of a terminal device applicable to the embodiment of the present application;

Figure 5 is another software structure block diagram of a terminal device applicable to the embodiment of the present application;

Figure 6 is a schematic flow chart of an application connection method provided by an embodiment of the present application;

Figure 7 is a schematic diagram of a shared memory communication principle provided by an embodiment of the present application;

Figure 8 is a schematic diagram of an application communication channel provided by an embodiment of the present application;

Figure 9 is a schematic flow chart of a method for application connection provided by an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings.

In order to facilitate a clear description of the technical solutions of the embodiments of the present application, some terms and technologies involved in the embodiments of the present application are briefly introduced below:

1. Connection strategy: The connection strategy is used to determine the devices that can be connected, and each application can correspond to its own connection strategy. For example, the application's connection policy can be related to one or more of the following fields:

The device types supported by the application, the continuation application package name on the Android platform, the continuation process name on the Windows platform, browser startup parameters, the minimum version number and minimum version of the supported continuation application, etc.

The connection policy may correspond to a flag bit used to identify the status of the connection policy. For example, a flag of 0 indicates that connection is not supported, a flag of 1 indicates application connection, and a flag of 3 indicates browser connection. It can be understood that the specific value of the flag bit can be set arbitrarily as long as it can distinguish different states, and is not specifically limited in the embodiment of the present application.

2. Other terms

In the embodiments of the present application, words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects. For example, the first terminal device and the second terminal device are used to distinguish different terminal devices, and their order is not limited. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order.

It should be noted that in the embodiments of this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

In addition, "at least one" means one or more, and "plurality" means two or more. "And/or" describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

With the development of terminal technology, users often need to switch content between multiple terminal devices. For example, when a user edits content in a memo on a mobile phone, the user may want to use a tablet or computer due to the smaller screen of the mobile phone. Other devices with larger screens can continue to edit the contents of the memo.

In the above scenario of switching content from a mobile phone to a tablet, when the user wants to continue editing the memo content previously edited on the phone after switching to the tablet, they usually need to find and open the memo on the tablet and re-edit the memo on the phone. content, or you need to copy the memo content in the mobile phone to the tablet through a medium. For example, you can copy and paste the content through a chat tool or a USB flash drive to switch the content in the mobile phone to the tablet. However, the above operations make the content switching process between devices relatively cumbersome and time-consuming.

The continuous development of terminal technology has led to the possibility of interconnection between devices, and application connection across devices will also become an important function in subsequent multi-device scenarios. Among them, application connection can be understood as: when the user uses an application on device A, the user can continue the usage status of the application on device B that meets the connection conditions and continue to use the application. This method makes content switching between devices simpler and more efficient.

Figure 1 is a schematic diagram of a scenario provided by an embodiment of the present application. This scene shows a personal computer (PC) and a mobile phone. Among them, the PC uses the Windows system, and the mobile phone uses the Android system. Users can use their mobile phones to connect to content presented by applications on their PCs, or they can use their PCs to connect to content presented by applications on their mobile phones.

Optionally, this scene can also include more terminal devices, such as large screens, tablets, etc. For example, the user can use at least one device among a mobile phone, a large screen, and a tablet to continue the content presented by the application in the PC.

The following is an introduction based on Figure 2, taking as an example that the user edits text in the memo on the PC, and the user wants to continue editing text in the memo through the mobile phone.

Figure 2 is a schematic diagram of an application connection interface provided by an embodiment of the present application.

See the A interface in Figure 2. When the user opens the memo on the PC and edits the content, the PC broadcasts the connection notification. After the mobile phone receives the connection notification, see the B interface in Figure 2. The mobile phone passes the dock bar (or through the multitasking center ) prompts the user that there are tasks that can be continued. The dock bar can be a fixed interface at the bottom of the screen of mobile phones, PCs, etc. The user can place more commonly used applications in the dock bar. If the user needs to change the device and continue editing content, the user can click the connection notification on the dock bar of the mobile phone to open the memo on the mobile phone to continue the application. Referring to interface C in Figure 2, the content previously edited on the PC is continuously displayed in the memo interface of the mobile phone. The cursor position is displayed at the position where the cursor stayed on the PC before the connection. The user can continue to edit the content on the mobile phone.

It should be noted that the PC and mobile phone shown in Figure 2 belong to the same trust ring. Belonging to the same trust ring can be understood as the devices are logged in with the same device account, the distance between the devices meets a certain threshold, and the devices are Turn on Bluetooth or wireless fidelity (Wi-Fi) at all times. Among them, the device account can be used for device authentication when connecting between devices; Bluetooth or Wi-Fi can be used for device discovery and connection between devices.

When the user uses a PC to edit in the memo, the mobile phone belonging to the same trust ring can prompt the user to proceed with the application connection. When the user triggers the mobile phone to confirm the application connection, the memo in the mobile phone can obtain and load the memo data in the PC, so that the user can continue to edit the memo content on the mobile phone, thereby providing the user with connection services and reducing the user's cross-device cross-device process. The operation complexity during application connection is improved to improve the user experience.

Scenarios similar to Figure 2 may also include: connecting the portable document format (PDF) opened on the mobile phone to the tablet and continuing to display it; or connecting the video played on the tablet to the mobile phone to continue playing; or , connect the music played on the PC to the mobile phone to continue playing, etc.

For PCs in application connection scenarios, in order to synchronize the application usage status to other devices, or to synchronize the application usage status of other devices to the PC, the PC needs to provide an external connection framework and software development kit (software). development kit, SDK) to meet this need. Among them, the connection framework provides a unified application status synchronization framework for applications. The application needs to access the connection framework through the SDK to realize data transmission with the connection service in the connection framework. The connection service relies on computer housekeeping to provide external service capabilities for applications.

It should be understood that after the application and the connection service in the PC are started, the application and the connection service are in two different processes, so the application needs to communicate through inter-process communication (inter process communication, IPC) and the connection service.

However, if multiple applications are connected to the connection framework at the same time and rely on the computer manager to communicate with the connection service, this will occupy too many IPC communication resources. The IPC communication resources provided by the connection framework integrated in the PC's computer manager for applications are limited. When there are too many access applications, how to flexibly allocate IPC communication resources to multiple applications is an urgent problem that needs to be solved.

In the embodiment of the present application, connection applications are used as a general term for applications with connection functions. Types of connection applications may include: editing applications (or document applications/office applications), browsing applications, and audio-visual entertainment applications (also known as Multimedia playback application), etc. It should be understood that the applications that occupy Computer Manager's IPC communication resources are not all continuous applications. For example, there are some security protection applications, engine applications, etc. that also occupy Computer Manager's IPC communication resources.

In view of this, embodiments of the present application provide an application connection method. When multiple applications access the connection framework at the same time and rely on the PC's computer manager to communicate with the connection service, the PC can apply for an address in the shared memory for each application. , allocate communication resources to each application based on the applied-for shared memory address, and the application can access the connection service based on the communication resources and perform data transmission with the connection service.

Figure 3 is a schematic structural diagram of a terminal device applicable to the embodiment of the present application.

The terminal device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and user Identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device. In other embodiments of the present application, the terminal device may include more or less components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), an image signal processor ( image signal processor (ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instruction or data again, it can be directly called from the above-mentioned memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or Universal serial bus (USB) interface, etc.

It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only schematic illustrations and do not constitute structural limitations on the terminal equipment. In other embodiments of the present application, the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The terminal device implements display functions through the GPU, the display screen 194, and the application processor. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The terminal device can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area can store data created during the use of the terminal device (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the terminal device by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. For example, the application connection method in the embodiment of the present application can be executed.

The terminal device of this application can be used as a sending end or a receiving end. The software system of the terminal device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Figure 4 of the embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the terminal device of the embodiment of the present application.

As shown in Figure 4, the layered architecture divides the software into several layers, and each layer has clear roles and division of labor. Data transmission and communication are carried out between layers through software interfaces. In some embodiments, the Android system is divided into five layers, from top to bottom: application layer, application framework layer, Android runtime and system library, and hardware abstract layer (HAL). , and the kernel layer.

The application layer can include a series of application packages. As shown in Figure 4, the application package can include third-party applications, connection service SDK, Bluetooth, Wi-Fi, memo, video, games and other applications. For example, in the embodiment of this application, in the application layer, the connection application can access the connection service SDK. The connection application can be a system application in the terminal device or a third-party application. Applications such as memos, videos, and games can also be system applications. application or third-party application.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 4, the application framework layer may include a connection service manager, a communication service manager, an authentication service manager, a notification manager, a window manager, a resource manager, a content provider, a view system, etc. Among them, managers can also be called modules in some application scenarios.

The connection service manager can be responsible for the management of connection tasks and provide connection services for connection applications. It is the core of the connection framework. For example, in the embodiment of this application, the connection service manager may be responsible for the access of the connection application, the authentication of the connection application, the icon management of the connection application, and the transmission of connection data across devices.

The communication service manager can be used to realize data transmission across devices. For example, in the embodiment of this application, the communication service manager can realize security authentication and account authentication of devices with the same account, self-discovery and self-organizing network of devices, and inter-device data transmission and access to communication services, etc.

The authentication service manager may be responsible for verifying the validity of the application. For example, in the embodiment of the present application, the application may be allowed to access the connection service after the authentication service manager passes the verification.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a prompt sound is emitted, the terminal device vibrates, and the indicator light flashes, etc. For example, in the embodiment of the present application, when the terminal device receives the connection notification, the notification manager may display the connection notification in the taskbar.

A window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, capture the screen, etc.

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, and more.

Content providers are used to implement data sharing functions between different applications, allowing one program to access data in another program while ensuring the security of the accessed data.

The view system can be responsible for the application's interface drawing and event handling. For example, in this embodiment of the present application, the view system can be used to process events after the user clicks on the notification icon of the connected application.

Android runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: Media Libraries, Function Libraries, graphics processing libraries (for example: OpenGL ES), etc.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The function library provides developers with API interfaces for multiple services, making it easy for developers to quickly integrate and implement various functions.

The graphics processing library is used to implement graphics drawing, image rendering, composition, layer processing, etc.

The hardware abstraction layer is an abstract layer between the kernel layer and the Android runtime. The hardware abstraction layer can be an encapsulation of the hardware driver and provide a unified interface for calls to upper-layer applications. The hardware abstraction layer can include Bluetooth modules, Wi-Fi modules, hardware configuration modules, etc. For example, in the embodiment of this application, the Bluetooth module and Wi-Fi module in the hardware abstraction layer can shield the specific hardware implementation details of the Bluetooth driver and Wi-Fi driver in the kernel layer, and upper-layer applications do not need to know the specific implementation of the kernel layer hardware driver. In this case, the Bluetooth function and Wi-Fi function can be realized by calling the interface.

The kernel layer is the layer between hardware and software. The kernel layer can include display drivers, camera drivers, audio drivers, Bluetooth drivers, Wi-Fi drivers, central processing unit drivers, etc. For example, in the embodiment of this application, the communication service manager can perform cross-device connections through related modules such as Bluetooth drivers and Wi-Fi drivers to realize self-discovery and self-organizing networks of devices.

It can be understood that the sending end or receiving end of the embodiment of the present application can also use the Windows system, as shown in Figure 5. Different from the Android system, the layered architecture of the Windows system is mainly divided into user mode and kernel mode. The user mode It can include user application processes, as well as system processes and service processes, etc.; the kernel state can include kernel and device driver layers, as well as hardware abstraction layers, etc.

A user application process can execute a sequence of applications. The specific executable application type may be the same as the application type in the application layer in the Android system, and will not be described again here.

System processes and service processes can include connection service managers, communication service managers, authentication service managers, system processes, notification managers, window managers, etc., which can provide corresponding services for the execution of user application processes. For the specific functions of processes such as the connection service manager, communication service manager, and authentication service manager related to the embodiments of the present application, please refer to the description of the relevant managers in Android, and will not be described again here.

In addition, the system process and service process may also include a channel management server. The channel management server is used to manage the communication channel of the application, including scheduled query of the communication channel, release of the communication channel, etc.

The kernel layer and device driver layer can include Bluetooth drivers, Wi-Fi drivers, display drivers, etc., and the hardware abstraction layer can include Bluetooth modules, Wi-Fi modules, hardware configuration modules, etc. For the specific function modules, please refer to the relevant descriptions in Android and will not be repeated here. The following is an example of the connection data transmission process in the Windows system layered framework based on the scenario where connection notifications are displayed during the application connection process between terminal devices.

As shown in Figure 5, in the application layer of the sender, the application is initialized by accessing the connection service SDK. The connection service SDK applies for the shared memory address for the application program and determines the communication identification (ID) of the application program. In this way, the connection service SDK can return initialization success to the application. After determining the communication ID of the application, the application can implement data transmission with the connection service by accessing the connection service SDK. The connection service SDK can send requests for binding connection services and application registration connection services to the connection service manager on the communication channel indicated by the communication ID, thereby realizing connection application registration and binding between the application layer and the application framework layer. data transmission.

In the application framework layer, the connection service manager can complete the binding of communication services by performing signaling transmission and data transmission with the communication service manager. The connection service manager can also bind authentication services and apply authentication with the authentication service manager.

After the connection application is successfully registered, the communication service manager can call the Bluetooth module interface and Wi-Fi module interface provided by the hardware abstraction layer to realize the self-discovery and self-organizing network of the device, and use the Bluetooth driver and the device driver layer in the kernel layer and The Wi-Fi driver implements session connections, message transmission, and transmission of continued content between terminal devices.

When the receiving end receives the connection-related data passed by the sending end based on the kernel layer and device driver layer, it can transmit the data to the relevant modules in the hardware abstraction layer. In the application framework layer of the receiving end, the communication service manager can obtain the transmitted connection data through the interface provided in the hardware abstraction layer, and conduct signaling transmission and data transmission with the connection service manager. After receiving the connection-related data, the connection service manager can bind the authentication service and apply authentication with the authentication service manager. Further, the connection service manager may instruct the desktop launcher to display the connection notification in the form of an icon.

The interaction process between each module will be described in detail below in conjunction with the system that implements the application connection method between devices. The following embodiments may be combined with each other or implemented independently, and the same or similar concepts or processes may not be described again in some embodiments.

Figure 6 is a schematic flow chart of an application connection method provided by an embodiment of the present application. A system that implements a cross-device application connection method may include a first terminal device and a second terminal device. The first terminal device may serve as a sending end and have a structure as shown in Figures 3 and 5. The second terminal device may serve as a sending end. The receiving end has the structure shown in Figure 3 and Figure 4. Both the first terminal device and the second terminal device may include various functional modules for implementing the connection service. For example, they may include a connection service SDK, a connection service manager, a communication service manager, an authentication service manager, etc.

The first terminal device in the embodiment of the present application may be a device using a Windows system, such as a PC, and the second terminal device may be a device using an Android system, such as a mobile phone, a tablet computer, etc.

For the convenience of description, the connection application of the first terminal device will be called the first connection application, the connection service SDK of the first terminal device will be called the first connection service SDK, and the connection service manager of the first terminal device will be called the first connection Service Manager The channel service manager of the first terminal device is called the first channel service manager, the communication service manager of the first terminal device is called the first communication service manager, and the authentication service manager of the first terminal device is called the first channel service manager. Is the first authentication service manager.

The connection application of the second terminal device is called the second connection application, the connection service SDK of the second terminal device is called the second connection service SDK, and the connection service manager of the second terminal device is called the second connection service manager. The communication service manager of the second terminal device is called the second communication service manager, and the authentication service manager of the second terminal device is called the second authentication service manager.

The implementation process of the application connection method in the embodiment of this application can be divided into four phases. The first phase is the initialization of the connection application, the second phase is the registration and binding of the connection application, the third phase is the display of the connection notification, and the fourth phase The stage is to obtain and load the subsequent data. Each stage is introduced below with reference to Figure 6.

The first stage is initialization.

The first connection service manager of the first terminal device runs in the computer manager. The application is accessed as an independent process and runs in the third-party application after accessing the connection service SDK. Therefore, the first connection service manager needs to communicate with the first connection application across processes. . When the first connection application of the first terminal device monitors some user behaviors, the first connection application can call the initialization interface of the first connection service SDK to apply for cross-process communication between the first connection application and the first connection service manager. communication channel. After applying for the communication channel, the first connection application may receive an initialization success message returned by the first connection service SDK.

The user behavior can be for the user to click the icon of the first connection application to start the first connection application, or for the user to perform editing and other operations in the first connection application, or for the user to click the play button in the first connection application for video playback, For operations such as music playback or other media playback, the specific monitored user behavior can be customized by the subsequent application, which is not limited by the embodiments of this application.

When the first terminal device is the sender of the application connection, the icon of the first connected application may be displayed on the desktop or taskbar (or dock) of the first terminal device.

After receiving the initialization request, the first connection service SDK can read the shared memory and determine the unapplied bits in the shared memory. The communication principle of shared memory is introduced below in conjunction with Figure 7.

FIG. 7 is a schematic diagram of a shared memory communication principle provided by an embodiment of the present application. As shown in Figure 7, shared memory is one of the methods of inter-process communication, allowing multiple processes to access the same memory. Process A and process B have their own process control block (PCB) and address space (address space), and each has a corresponding page table, which is responsible for mapping the virtual address of the process to the physical address. , managed through the memory management unit (MMU). Two different virtual addresses are mapped to the same area of physical space through the page table, and the area they point to is shared memory.

When process A and process B map virtual addresses to physical addresses through page tables, there is a common memory area in the physical address, that is, shared memory. This memory can be seen by process A and process B at the same time. In this way, one process performs a write operation and another process performs a read operation, so that inter-process communication can be achieved.

Figure 8 is a schematic diagram of an application communication channel provided by an embodiment of the present application. When the first connection service SDK determines the unapplied bits in the shared memory, it reads the value of each bit in the shared memory in order. The value of each bit is the first preset value or the second preset value. The communication channel corresponding to the bit with the first preset value has not been applied for or is not used, and the communication channel corresponding to the bit with the second preset value has been applied for or has been used. For example, the first preset value may be "0" and the second preset value may be "1".

As shown in a in Figure 8, the value of the first bit and the second bit in the shared memory area is "1", indicating that the communication channel corresponding to these two bits has been occupied by application A and application B.

As shown in b in Figure 8, when the first connection application (application C) accesses the first connection service SDK, the first connection service SDK detects that the value of the third bit in the shared memory area is "0". Therefore, the first connection service SDK can determine that the third bit is the target bit, and return the identifier n of the bit gap to the first connection service SDK, that is, return the identifier of the third bit gap. Among them, the bit gap represents a bit with a value of "0".

For example, the identifier n of the first bit is 1, the identifier n of the second bit is 2, the identifier n of the third bit is 3, and so on.

After the first connection service SDK detects that the value of the third bit is "0" and determines that the third bit is the target bit, the first connection service SDK can modify the value of the target bit to "1", To indicate that the communication channel corresponding to the target bit has been applied for or has been used.

After receiving the identifier n of the bit gap, the first connection service SDK calculates the communication ID according to the identifier n of the bit gap. For example, communication ID=M+n×N, where M and N are preset values, and the value of N represents the application The number of message types supported by the communication channel.

It should be understood that the communication ID calculated by the first connection service SDK is a starting communication ID, and the communication channels identified by N consecutive communication IDs starting from the starting communication ID can all be used by the first connection service SDK. Use, N is the default value. That is to say, the first connection service SDK can determine multiple communication channels based on the calculated communication ID. The number of multiple communication channels is N. Each communication channel supports the transmission of one message type. The message types are such as: registration connection service and callback. Messages, unregistered connection service and callback messages, broadcast connection notification messages, communication return messages, etc.

The following uses N=3 and M=0 to illustrate the communication ID as an example.

For example, application A's connection service SDK reads the shared memory and detects that the value of the first bit in the shared memory area is "0", and the first bit identifier n=1, so the shared memory transfers to application A's The identifier of the bit gap returned by the connection service SDK is the identifier of the first bit n=1. The communication ID calculated by application A's connection service SDK based on communication ID=M+n×N is 3. The communication ID 3 corresponds to three communication channels, and the communication IDs of the three communication channels are 3, 4, and 5 respectively.

For example, application B's connection service SDK reads the shared memory and detects that the value of the second bit in the shared memory area is "0", and the second bit identifier n=2, so the shared memory transfers to application A's The identifier of the bit gap returned by the connection service SDK is the identifier of the second bit n=2. The communication ID calculated by application B's connection service SDK based on communication ID=M+n×N is 6. The communication ID 6 corresponds to three communication channels, and the communication IDs of the three communication channels are 6, 7, and 8 respectively.

Similarly, the communication ID calculated by the connection service SDK of the first connection application (Application C) based on communication ID=M+n×N is 9. The communication ID 9 corresponds to three communication channels, and the communication IDs of the three communication channels are respectively It's 9, 10, 11.

It should be understood that each communication channel among the multiple communication channels applied for by each application transmits a predefined message type. For example, the communication channel identified by communication ID+1 is used to transmit communication connection messages. That is, in the above example, application A can receive the communication reconnection message through the communication channel identified by the communication ID 4, application B can receive the communication reconnection message through the communication channel identified by the communication ID 7, and application C can receive the communication reconnection message through the communication channel. The communication channel identified by ID 10 receives the communication connection message.

After the first connection application receives the initialization success message, the first connection application can interact with the first connection service manager on the applied communication channel in order to perform subsequent application connection processes.

The second stage is to continue the registration and binding of the application.

The first connection application can access the connection service by calling the registration interface of the first connection service SDK. It can be understood that the first connection application may carry the package name, version number and other information of the first connection application when registering the connection service.

In a possible implementation, the first connection service SDK can interact with other function managers through the first connection service manager. Exemplarily, the first connection service SDK may send a request to bind the connection service and apply the registration connection service to the first connection service manager through the communication channel identified by the communication ID of 1. After receiving the first connection service manager, the first connection service manager After a request from the connection service SDK, the first connection service manager can interact with the first communication service manager to bind the communication service. After the binding is successful, the first connection service manager can receive a reply from the first communication service manager indicating that the binding is successful. news.

After receiving the request of the application registration connection service of the first connection service SDK, the first connection service manager may notify the first channel service manager to mark the communication ID of the communication channel sending the request, indicating that the communication ID corresponds to The communication channel is already in use.

Further, the first connection service manager can perform binding authentication service and application authentication by calling an interface provided by the first authentication service manager. After receiving the authentication request, the first authentication service manager can complete the binding and authentication of the first connection application through data interaction with the cloud authentication server. It can be understood that during the process of binding the authentication service, the cloud authentication server can obtain the user identification (UID) based on the package name of the first connected application, and then perform application authentication based on the UID. When the first authentication service manager successfully authenticates the first connection application, the cloud authentication server may store application information such as the icon of the first connection application and return the authentication result to the first connection service manager.

After receiving the authentication result of the first connection application, the first connection service manager will pass the message to the first connection application. The authentication results may include authentication success and authentication failure. If the result received by the first connection application is authentication success, it means that the application registration is successful, and the application connection method can continue to be executed; if the first connection application receives the authentication result If the result is authentication failure, it means that the application registration failed and the application connection method will not continue.

After the first connection service manager receives the first connection application authentication result, and the authentication result is successful, it will also notify the first channel service manager that the application has been registered. After receiving the message that the application has been registered, the first channel service manager starts a regular query on the status of the first connection application and sends a regular query message to the first connection service SDK. Among them, the status of the first connected application includes that the process is still alive or the process has exited. Specifically, the first channel service manager sending a scheduled query message to the first connection service SDK may include: the first channel service manager sending a keep-alive packet to the first connection service SDK regularly, and successfully sending the keep-alive packet indicates the first connection. The application process is still alive. Failure to send a keep-alive packet means that the first process connected to the application has exited.

After the application registration of the first terminal device is successful, the first communication service manager and the second communication service manager can perform self-discovery and self-organizing network through Bluetooth or Wi-Fi, and perform account authentication. Further, the first communication service manager may send information indicating that the second terminal device is online to the first connection service manager. For example, the information used to indicate that the second terminal device is online may include information such as a device identification (DeviceIdentification, DevID) of the second terminal device.

After the first connection service manager receives the information sent by the first communication service manager to indicate that the second terminal device is online, it can store and manage the information of the second terminal device in order to perform subsequent application connection. process.

The third stage is the display of the continuation notification.

When the first connection application is successfully registered, broadcast connection notifications may be periodically sent to the first connection service manager. The broadcast connection notification may carry information such as the package name of the first connection application, the connection strategy, and the connection content summary (such as title). The first connection service manager may confirm connectable devices according to the connection policy of the first connection application.

For example, when the connection policy includes device types supported by the application, for example, the connection policy includes that the first connection application can support connection services on mobile phones, tablets, TVs, computers, etc., then the first connection service When the manager confirms that the second terminal device is a mobile phone, a tablet, a television, a computer, etc., the first connection service manager may instruct the first communication service manager and the second communication service manager to establish a session path.

For example, when the connection policy includes the minimum version number or the minimum version, for example, the connection policy includes the minimum version number that the first connection application can support is A, or the minimum version is B, then the first connection service manager confirms When the version number of the second connection application is greater than or equal to A, or when the version number of the second connection application is greater than or equal to B, the first connection service manager may instruct the first communication service manager and the second communication service manager to establish a session path. .

A session path can be established between the first communication service manager and the second communication service manager to facilitate application connection-related messaging and data transmission.

After the session path is successfully established, the first communication service manager may indicate to the first connection service manager that the channel is successfully established, and the first connection service manager may send the broadcast connection notification carrying the first connection application according to the broadcast connection notification sent by the first connection application. The broadcast connection notification of the package name and the summary of the connection content and other information is sent to the first communication service manager. The first communication service manager sends the package name of the first connection application and the summary of the connection content and other information to the first communication service manager through the established session path. The second communication service manager further reports information such as the package name of the first connection application and the connection content summary to the second connection service manager.

The second connection service manager can parse the package name of the first connection application, and carry the package name information of the first connection application for binding and authentication with the second authentication service manager. The implementation of binding and authentication is the same. The authentication steps in the first terminal device are similar and will not be described again.

After the application authentication is successful, the second connection service manager can obtain the application icon through any possible implementation.

In one possible implementation, the second connection service manager may search whether the icon of the first connection application is stored locally in the second terminal device based on the obtained application information such as the package name of the first connection application. If the icon of the first connection application can be found, the second connection service manager can notify the desktop launcher to use the icon of the first connection application to display the connection notification; if the icon of the first connection application is not found, the second connection service manager The manager can obtain the icon of the first connected application and other related information through the cloud authentication server. Further, when the cloud authentication server sends the icon of the first connection application to the second connection service manager, the second connection service manager can store the icon of the first connection application and other related information locally on the second terminal device. , and the second connection service manager can notify the desktop launcher to display the connection notification on the second terminal device.

In another possible implementation, the second connection service manager can obtain the icon and other related information of the first connection application through the cloud authentication server.

In another possible implementation, the second connection service manager may search the second terminal device for a second connection application with the same package name as the first connection application. If the second connection application can be found, the second connection service manager may notify the desktop launcher to display the connection notification using the icon of the second connection application stored locally on the second terminal device; if the second connection application is not found, the second connection application may be found. The second connection service manager can obtain the icon of the first connection application and other related information by searching the application information locally on the second terminal device or in the cloud authentication server, and notify the desktop launcher to use the icon of the first connection application. Display the connection notification.

It can be understood that when the desktop launcher controls the display of the connection notification, the connection notification can be displayed in the recent task, taskbar, shortcut window or other interface entry of the second terminal device. The specific method of displaying the connection notification will not be described in the embodiment of this application. limit. The connection notification may be displayed in the form of a connection application icon, or may be displayed in the form of an application name, a prompt, or other forms. The specific display format of the connection notification is not limited by the embodiments of this application.

The fourth stage is the acquisition and loading of continued data.

After the second terminal device receives the event that the user clicks the connection application icon, in a possible implementation, if the second connection application is not installed in the second terminal device, the second terminal device may prompt the user to install the second connection application. The specific method of prompting to install the application is not limited in the embodiment of this application. If the second connection application is already installed in the second terminal device, or the installation of the second connection application is completed based on prompts, the following steps can be performed.

The second connection service manager can launch the second connection application and instruct the second connection application to load the transition animation effect. Then the second connection application can start and load the transition animation effect. The transition animation effect can include, for example, "Loading..." etc. Prompt information. Further, the second connection application can access the connection service by calling the registration interface of the second connection service SDK. It can be understood that the second connection application can carry information such as the package name of the second connection application when registering the connection service.

The second connection service SDK can send a request to bind the connection service to the second connection service manager. After receiving the request to bind the connection service, the second connection service manager can send a binding communication to the second communication service manager. Service requests. When the second communication service manager is successfully bound, the second communication service manager may send a binding success message to the second connection service SDK through the second connection service manager. After receiving the binding success message, the second connection service SDK sends a registration connection service message to the second connection service manager. After the second connection service manager successfully registers, the second connection service manager can send the registration success message through the second connection service manager. The service SDK is returned to the second connection application.

During the startup process of the second connection application, the second connection service manager may also send connection request data to the first connection service manager through the session path established between the first terminal device and the second terminal device. When the first connection service manager After receiving the request connection data, the service manager can report the request connection data to the first connection application through the first connection service SDK. Then the first connection application can package and encrypt the connection content and other related connection data, and pass the first connection service SDK to the first connection application. The connection service SDK sends the connection data to the first connection service manager. The first connection service manager can send the connection data to the second connection service manager through the session path established between the first terminal device and the second terminal device. .

Further, the second connection service manager notifies the second connection application of the connection data through the second connection service SDK. After successful registration, the second connection application can load the connection data and control the second terminal device to display the connection data, and send the connection data to the second connection application. The first connection application of a terminal device transmits information indicating successful connection, and then the first connection application can execute processes such as exiting the page of the first connection application.

During the execution of each stage described above, the following scenarios may exist.

Scenario 1: The first connected application exits normally.

For example, the first connection application may exit after receiving the connection success notification. In this scenario, the first connection application can deregister by calling the application deregistration interface of the first connection service SDK. The first connection service SDK sends an application deregistration request to the first connection service manager through the applied communication channel. After receiving the request from the first connection service SDK, the first connection service manager can notify the first channel service manager The application has exited, and the first channel service manager stops the regular query of the first connection application and clears the occupied bits in the shared memory. For example, when applying for a communication channel, the first connection service SDK changes the value of the third bit in the shared memory area to "1". Therefore, when cleaning, the first channel service manager changes the third bit in the shared memory area to "1". The value of the bit is modified to "0", indicating that the communication channel corresponding to the third bit has not been used or applied for, and can be applied for use by other applications. This is conducive to efficient use of limited IPC communication resources and improvement of communication resources. utilization rate.

Further, the first channel service manager notifies the first connection service manager that the application is disconnected successfully. After receiving the message that the application is disconnected successfully, the first connection service manager sends a message to the first connection application through the first connection service SDK. Deregistration successful message.

Scenario 2: The first connected application exits abnormally.

For example, if the first connected application freezes and exits, or the user forcibly stops the application in the background task manager, the first connected application may exit abnormally. In this scenario, the first channel service manager cannot successfully send the keep-alive packet to the first connection service SDK, and the first connection service SDK does not deregister with the first connection service manager, causing the first connection application to always occupy the communication channel. When IPC communication resources are limited, other applications may not be able to apply for available communication channels in time, resulting in a waste of communication resources.

In this embodiment of the present application, after determining that the scheduled query fails, the first channel service manager notifies the first connection service manager that the application has exited. The first channel service manager stops the scheduled query for the first connection application and clears the occupied bits in the shared memory, which helps avoid waste of communication resources.

Scenario 3: The first connection application is started before the first connection service manager.

The first connection application is started before the first connection service manager, that is, the first connection application is started before the computer manager. In this scenario, the first connection application can apply for the communication channel, but may not be able to successfully register the connection service because the first connection service manager has not been started or has exited abnormally. For example, the user can manually open the computer manager to start the first connection service manager. During the startup process of the first connection service manager, the first connection service manager stores all the connections in the shared memory that can be used to transmit communication connection messages. Send communication connection messages on the communication channel.

For example, the first connection service SDK receives the communication reconnection message broadcast by the first connection service manager on the communication channel identified by communication ID+1. If the first connection application has a requirement for cross-device application connection, the first connection service SDK The application can determine to start the registration and binding of the connection application, and the first connection service manager maintains the data in the shared memory area as the latest state according to the communication ID of the back-connected communication channel.

Scenario 4: The first connection service manager exits abnormally.

The processing flow in this scenario is similar to that in Scenario 3 and will not be described again here.

The above describes the internal interaction process of the first terminal device as the sender and the second terminal device as the receiver with reference to Figure 6. The following describes the internal interaction process of the first terminal device as the receiver and the second terminal device as the sender. The first terminal device may have a structure as shown in Figures 3 and 5, and the second terminal device may have a structure as shown in Figures 3 and 4.

The prerequisite for the first terminal device to serve as the receiving end is that the computer manager of the first terminal device must be started before the first connection application, so that the first terminal device can normally perform application connection processes related to device self-discovery and ad hoc networking.

Similar to the internal interaction of the first terminal device as the sender, the second terminal device can perform the above-mentioned process after stage 2 when it serves as the sender. Under the hierarchical architecture of Figure 4, the second connection service SDK in the second terminal device and There is no cross-process communication between the second connection service managers, so the second connection service SDK does not need to apply for a communication channel in the shared memory.

The second terminal device can open the second connection application, perform registration and binding of the connection application, broadcast connection notification, bind authentication service and application authentication, and establish a session path with the first communication service manager of the first terminal device, For the specific process, please refer to the above description of Figure 6 and will not be described again here. After the session path is established, the first communication service manager and the second communication service manager transmit messages through the established session path, and the messages include information such as the package name of the second connection application. The first connection service manager and the first authentication service manager bind the authentication service according to the package name of the second connection application and perform application authentication. After the application authentication is successful, the first connection service manager obtains the application icon and notifies the desktop launcher of the first terminal device to display the connection notification in the form of an icon.

When the first terminal device is the receiving end of the application connection, the icon of the first connected application may be displayed on the taskbar (or dock) of the first terminal device.

When the first terminal device receives the event that the user clicks the connection application icon, if the first connection application has been installed in the first terminal device and the first connection application has not been started, the first connection service manager launches the first connection application, and instructs the first connection application to load the transition animation effect, then the first connection application can start and load the transition animation effect.

Further, the first terminal device may perform a process similar to the initialization phase and the registration and binding phase of the connected application in FIG. 6 , which will not be described again here.

During the process of starting the first connection application, the first connection service manager may request connection data from the second connection service manager through the session path established between the first terminal device and the second terminal device. For the specific process of requesting data connection, please refer to the above description of FIG. 6 and will not be described again here.

Further, after receiving the connection data, the first connection service manager notifies the first connection application of the connection data through the first connection service SDK on the communication channel applied for transmitting the connection data. For example, the communication channel identified by communication ID+2 among the N communication channels corresponding to the communication ID is used to transmit connection data, then the first connection service manager can apply the first connection application to the communication channel identified by communication ID+2. Send connection data.

Based on the above description of the internal interaction process of application connection, as shown in Figure 9, the embodiment of the present application provides a method 900 for application connection. The method 900 can be executed by a terminal device. The terminal device can have the configuration shown in Figure 3 and the structure shown in Figure 5, but the embodiment of the present application is not limited to this. The terminal device is installed with the first application and computer manager. The terminal device corresponds to the above-mentioned first terminal device and can be used as a sender of the application connection or as a receiver of the application connection. Method 900 includes the following steps:

S901. In response to the user clicking the icon of the first application, obtain the identification of the target bit in the shared memory. The target bit is a bit whose value is a first preset value. The first preset value represents the target bit corresponding to The communication channel is not in use.

In this step, the first application may be the above-mentioned first subsequent application. For example, the first preset value is "0". If the value of the first bit in the shared memory is "0", then the first One bit is the target bit, and the terminal device can obtain the identifier n=1 of the first bit; if the value of the first bit in the shared memory is "1", the value of the second bit is " 0", the second bit is the target bit, and the terminal device can obtain the identifier n=2 of the second bit.

S902. Based on the identification of the target bit, determine the communication identification corresponding to the target bit. The communication identification indicates at least one communication channel used for communication between the first application and the computer manager.

Based on the above description, after the terminal device obtains the identifier of the target bit, it can calculate the communication identifier corresponding to the target bit based on the preset rules. The communication identifier corresponds to at least one communication channel. In this way, the terminal device applies for the first application. IPC communication resources that can be used to communicate with computer managers. The specific description of the communication channel can be found above and will not be repeated here.

S903: Implement data transmission between the first application and the computer manager based on the at least one communication channel.

In this step, the data transmission between the first application and the computer manager may include the above-described registration connection service and callback, broadcast connection notification, request connection data, application deregistration, broadcast communication reconnection message, etc.

In the embodiment of this application, the terminal device can combine IPC communication with shared memory to flexibly allocate IPC communication resources to at least one application that accesses the connection service in the computer manager, so as to realize the connection between the application and the connection service in the computer manager. Communication.

It should be understood that the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

Those of ordinary skill in the art can appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in each embodiment of the present application can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific implementation modes of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes within the technical scope disclosed in the embodiments of the present application. or replacement, all should be covered by the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims (13)

1. A method for application connection, applied to a terminal device, where the terminal device is a transmitting end or a receiving end of application connection, and the terminal device is installed with a first application and a computer manager, the method includes:

responding to the operation of clicking the icon of the first application by a user, and acquiring the identification of a target bit in a shared memory, wherein the target bit is a bit with a first preset value, and the first preset value indicates that a communication channel corresponding to the target bit is not used;

determining a communication identifier corresponding to the target bit based on the identifier of the target bit, wherein the communication identifier indicates at least one communication channel for the first application to communicate with the computer manager;

and realizing data transmission between the first application and the computer manager based on the at least one communication channel.

2. The method according to claim 1, wherein the method further comprises:

based on the acquisition of the identification of the target bit, modifying the value of the target bit from the first preset value to a second preset value, the second preset value representing that the communication channel corresponding to the target bit has been used.

3. The method of claim 2, wherein said enabling data transfer between the first application and the computer housekeeping based on the at least one communication channel comprises:

based on a first communication channel of the at least one communication channel, a continuation service and a callback are registered.

4. A method according to claim 3, characterized in that the method further comprises:

and under the condition that the process of the first application exits, modifying the value of the target bit from the second preset value to the first preset value.

5. The method according to claim 4, wherein the method further comprises:

de-registering the continuation service and the callback based on a second communication channel of the at least one communication channel;

and determining that the process of the first application exits based on the continuous service and the deregistration of the callback.

6. The method according to claim 4, wherein the method further comprises:

after successfully registering the continuation service and the callback, periodically inquiring whether the process of the first application exits.

7. A method according to claim 3, wherein the terminal device is a sender of an application connection; in the case that the first application is started before the computer manager or the process of the computer manager exits abnormally, the method further comprises:

Broadcasting a communication callback message, wherein the communication callback message is used for indicating the first application to connect with the computer manager;

the registering of the continued service and the callback based on the first communication channel of the at least one communication channel includes:

and registering a continuing service and callback based on the first communication channel under the condition that the communication callback message is received based on a third communication channel in the at least one communication channel.

8. The method according to any of claims 1 to 6, wherein the terminal device is a receiving end of an application connection; the responding to the operation of clicking the icon of the first application by the user obtains the identification of the target bit in the shared memory, and the method comprises the following steps:

and responding to the operation of clicking the icon of the first application positioned in the task bar of the terminal equipment by a user, and acquiring the identification of the target bit in the shared memory.

9. The method according to any of claims 1 to 7, wherein the terminal device is a sender of an application connection; the responding to the operation of clicking the icon of the first application by the user obtains the identification of the target bit in the shared memory, and the method comprises the following steps:

And responding to the operation of clicking the icon of the first application positioned on the desktop or the task bar of the terminal equipment by a user, and acquiring the identification of the target bit in the shared memory.

10. A terminal device comprising means for performing the method of any of claims 1 to 9.

11. A terminal device, comprising: a processor and a memory, wherein,

the memory is used for storing a computer program;

the processor is configured to invoke and execute the computer program to cause the terminal device to perform the method of any of claims 1 to 9.

12. A computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 9.

13. A computer program product comprising computer program code embodied therein, which when run on a computer causes the computer to carry out the method according to any one of claims 1 to 9.