Cross-screen control method and related device

Abstract

The embodiments of the present application relate to the field of communications. Provided are a cross-screen control method and a related device. The method can be executed by a first device or executed by a chip in the first device. The first device is configured with a first display screen and a second display screen. A first operating system runs on the first display screen and the second display screen; the first display screen corresponds to a first user space, and the second display screen corresponds to a second user space. The method comprises: acquiring a first request sent to the first user space, wherein the first request is used for requesting that a first task is executed by means of the second display screen; using the first display screen to determine a target file corresponding to the first task; and by means of a headless system user, control the second display screen to output the target file, wherein the headless system user is used for hosting system services. In the solution, on the basis of the headless system user and on the first display screen, the second display screen can be controlled in a cross-screen mode to execute the first task, without the need for deploying an application in each display screen of the first device; thus, the implementation solution is simple.

Description

Cross-screen control method and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 28, 2023, with application number 202311294981.0 and application name “Cross-screen control method and related equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and in particular to a cross-screen control method and related equipment. Background Art

[0003] With the gradual development of smart cockpits, manufacturers are deploying more screens in the cockpit to support richer audio, video and entertainment capabilities, in order to build the cockpit into a "mobile home."

[0004] As an important application in the cockpit, the voice assistant can greatly simplify various operations in the cockpit and enhance the user experience. For example, referring to Figure 1A, Figure 1A is a schematic diagram of a voice assistant controlling rear-row audio and video entertainment content provided by an embodiment of the present application; when the whole family is traveling (children are sitting in the back row), the co-pilot (parent) controls the audio and video entertainment content on the rear screen through the voice assistant on the co-pilot screen, which becomes a just-needed scenario. Correspondingly, referring to Figure 1B, Figure 1B is a specific flow diagram of a voice assistant controlling rear-row audio and video entertainment content provided by an embodiment of the present application; the user can complete the target video selection on the video aggregation page by having a voice conversation with the co-pilot's voice assistant; and then through cross-screen distribution and cross-system communication, the target video can be played on the rear-row video application (Application, APP) on the rear screen. Among them, the resources of the video aggregation page can be obtained through method 1 and method 2. However, in the voice control solution shown in Figure 1B, each screen needs to deploy its own application, such as a video APP, to support cross-screen operations under multiple screens, and the implementation solution is complicated.

[0005] Summary of the Invention

[0006] The present application provides a cross-screen control method and related devices, which can achieve cross-screen control without deploying applications on each screen of the first device, and the implementation solution is simple.

[0007] In a first aspect, a cross-screen control method is provided. The method can be executed by a first device or a chip in the first device. The first device is configured with a first display and a second display. A first operating system runs on the first and second displays, the first display corresponding to a first user space, and the second display corresponding to a second user space.

[0008] The cross-screen control method includes the following operations: obtaining a first request sent to a first user space. The first request is used to request execution of a first task on a second display screen. Using the first display screen, a target file corresponding to the first task is determined. Using a headless system user, the second display screen is controlled to output the target file. The headless system user is used to host system services. The target file is outputted via a first application.

[0009] As can be seen, in this solution, based on a headless system, users can use the first display to control the second display to perform the first task across screens, without having to deploy the application on each display of the first device, making the solution simple to implement. The first task can be any task, and there is no limitation on the first task.

[0010] In one possible implementation of the first aspect, determining the target file corresponding to the first task using the first display screen specifically includes the following steps: a headless system user moves a content interface of the first application to the first display screen for display. The first application is configured in the second user space, and the content interface corresponds to the first request. The target file is determined based on the content interface.

[0011] In this solution, the first application runs in the second user space. Cross-screen control is achieved by first moving the first application's content interface to the first display, then determining the target file based on the content interface, and then allowing the headless system user to control the second display to output the target file. Cross-screen control only requires the first application to be configured on the second display to execute the first task, making the solution simple to implement.

[0012] In one possible implementation of the first aspect, determining the target file corresponding to the first task using the first display screen specifically includes the following steps: determining a content interface through interaction between a headless system user and a first application. The first application is configured in a first user space, and the content interface corresponds to the first request. The target file is determined based on the content interface.

[0013] In this solution, the first application runs in the first user space. A headless system user interacts with the first application to determine the content interface. Based on the content interface, the target file is determined. The headless system user then controls the second display to output the target file, achieving cross-screen control. Cross-screen control only requires the first display to be configured with the application; the first task can be executed on the second display, making the solution simple to implement.

[0014] In one possible implementation of the first aspect, determining the target file based on the content interface specifically includes the following steps: obtaining call stack information of the first application based on the content interface; obtaining control information of the first application based on the call stack information; and determining the target file based on the control information and at least one control operation command.

[0015] Among them, the call stack information of the first application includes the process information of the first application (such as the process stack), the source display screen of the first application or the user space unique code corresponding to the source display screen, and the package name of the first application. The above-mentioned controls include function menus, various buttons, texts, etc. Based on the control information of the first application and at least one control operation command, a simulated click can be performed to determine the target file. The control operation commands include but are not limited to selecting the target function, pressing a button, or selecting the target file. The target file can be determined based on the content interface through the interface-level visible and speakable technology, which effectively simplifies the operations that the user needs to perform when determining the target file, which is conducive to improving the user experience.

[0016] In one possible implementation of the first aspect, determining a target file corresponding to the first task using the first display screen specifically includes the following steps: interacting with an aggregation page on the first display screen to determine the target file. The aggregation page displays at least one candidate file corresponding to the first request.

[0017] In this solution, the target file can be determined by interacting with the aggregate page on the first display screen. The above interaction can be voice interaction, touch interaction, key interaction, etc. This application provides an aggregate page to determine the target file, and the user does not need to frequently switch between different applications to determine the target file, which saves user operations and improves the user experience.

[0018] In a possible implementation of the first aspect, the cross-screen control method further includes the following steps: obtaining at least one candidate file from an application on the first display screen and / or the second display screen by a headless system user, and generating an aggregate page based on the at least one candidate file.

[0019] In this solution, the candidate files can be obtained from the local application of the first device, and then the aggregate page is generated, which provides a possible method for generating the aggregate page.

[0020] In a possible implementation of the first aspect, the cross-screen control method further includes the following steps: obtaining at least one candidate file from the second device, and generating an aggregate page based on the at least one candidate file.

[0021] In this solution, when the first device cannot obtain the candidate file, it can obtain the candidate file from the second device and then generate the aggregate page, which provides another possible method for generating the aggregate page.

[0022] In one possible implementation of the first aspect, the cross-screen control method further includes the following steps: obtaining at least one first candidate file from a second device; obtaining at least one second candidate file from an application on the first display and / or the second display via a headless system user; and generating an aggregate page based on the at least one first candidate file and the at least one second candidate file.

[0023] In this solution, candidate files can be obtained from the local application of the first device and the second device to generate an aggregate page, which provides another possible method for generating an aggregate page.

[0024] In one possible implementation of the first aspect, interacting with the aggregated page on the first display screen to determine the target file specifically includes the following steps: obtaining call stack information of the aggregated page; obtaining control information of the aggregated page based on the call stack information; and determining the target file based on the control information and at least one control operation command.

[0025] In this solution, the target file can be determined through the interface-level visible and speakable technology based on the aggregate page, which effectively simplifies the operations required by the user when determining the target file and is conducive to improving the user experience.

[0026] In a possible implementation of the first aspect, the controlling the second display screen to output the target file through the headless system user specifically includes the following steps: controlling the first application to output the target file through the headless system user. The first application is configured on the second display screen.

[0027] In this solution, when the first application is configured on the second display screen, after determining the target file, the headless system user can directly control the first application to output the target file, and the cross-screen control solution is simple to implement.

[0028] In a possible implementation of the first aspect, the step of controlling the second display screen to output the target file by the headless system user specifically includes the following steps: moving the content interface of the first application to the second display screen for display; and controlling the first application to output the target file by the headless system user.

[0029] In this solution, when the first application is configured on the first display screen, after determining the target file, the content interface of the first application can be moved to the second display screen for display, and then the first application can be controlled to output the target file; a possible method for outputting the target file through the second display screen is provided.

[0030] In a possible implementation of the first aspect, the step of controlling the second display screen to output the target file by the headless system user specifically includes the following steps: controlling the first application to output the target file by the headless system user, and moving the content interface of the first application to the second display screen for display.

[0031] In this solution, when the first application is configured on the first display screen, after determining the target file, the first application can be controlled to output the target file first, and then the content interface of the first application can be moved to the second display screen for display; another possible method of outputting the target file through the second display screen is provided.

[0032] In a second aspect, the present application also provides a first device, which includes a unit or module for executing the cross-screen control method described in the first aspect.

[0033] In a third aspect, the present application also provides a first device comprising a processor and a memory, wherein the processor and the memory are connected, wherein the memory is used to store program code, and the processor is used to call the program code to execute the cross-screen control method as described in the first aspect.

[0034] In a fourth aspect, the present application also provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the cross-screen control method as described in the first aspect.

[0035] In a fifth aspect, the present application also provides a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the cross-screen control method described in the first aspect.

[0036] In the sixth aspect, the present application also provides a chip, which includes a processor and a data interface. The processor reads instructions stored in the memory through the data interface to execute the cross-screen control method described in the first aspect.

[0037] Optionally, as an implementation method, the chip may further include a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the cross-screen control method described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The following is an introduction to the drawings used in the embodiments of this application.

[0039] FIG1A is a schematic diagram of a voice assistant controlling rear-seat audio and video entertainment content provided by an embodiment of the present application;

[0040] FIG1B is a schematic diagram of a specific process of controlling rear-seat audio and video entertainment content using a voice assistant according to an embodiment of the present application;

[0041] FIG1C is a schematic diagram of a first device provided in an embodiment of the present application;

[0042] FIG1D is a schematic diagram of a second display screen provided in an embodiment of the present application;

[0043] FIG2 is a schematic flow chart of a cross-screen control method provided in an embodiment of the present application;

[0044] FIG3A is a schematic diagram of a specific flow of a cross-screen control method provided by an embodiment of the present application;

[0045] FIG3B is a schematic diagram of a specific flow chart of a cross-screen control method provided in an embodiment of the present application;

[0046] FIG3C is a schematic diagram of a specific flow of a cross-screen control method provided in an embodiment of the present application;

[0047] FIG3D is a schematic diagram of a specific flow of step 202 provided in an embodiment of the present application;

[0048] FIG3E is a schematic diagram of a specific flow chart of step 222 provided in an embodiment of the present application;

[0049] FIG3F is a schematic diagram of a specific flow chart of step 203 provided in an embodiment of the present application;

[0050] FIG3G is a schematic diagram of another specific flow chart of step 203 provided in an embodiment of the present application;

[0051] FIG3H is a schematic diagram of another specific flow chart of step 202 provided in an embodiment of the present application;

[0052] FIG3I is a schematic diagram of an aggregation page provided in an embodiment of the present application;

[0053] FIG4 is a schematic structural diagram of a first device provided in an embodiment of the present application;

[0054] FIG5 is a schematic structural diagram of another first device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The technical solution in this application will be described below with reference to the accompanying drawings.

[0056] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0057] The "at least one" mentioned in the embodiments of this application refers to one or more, and "plurality" refers to two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can be represented by: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, c can be single or multiple. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can be represented by: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. The serial numbers of the steps in the embodiments of this application (such as step S1, step S21, etc.) are only for distinguishing different steps and do not limit the order of execution between the steps.

[0058] Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority, or importance of multiple objects. For example, the first device and the second device are only for ease of description and do not indicate differences in structure, importance, etc. between the first and second devices. In some embodiments, the first device and the second device can also be the same device.

[0059] In the above embodiments, the term "when" can be interpreted to mean "if...", "after...", "in response to determining...", or "in response to detecting...", depending on the context. The above are merely optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the concepts and principles of the present application shall be included in the scope of protection of the present application.

[0060] Due to the applications involved in the embodiments of the present application, in order to facilitate understanding, the relevant terms and other related concepts involved in the embodiments of the present application are first introduced below.

[0061] (1) Operating system

[0062] An operating system (OS) is a set of interrelated system software programs that manage and control computer operations, utilize and run hardware and software resources, and provide common services to organize user interactions. In a computer, the OS is its most basic and most important foundational system software.

[0063] (2) Application

[0064] An application is a computer program designed to perform one or more specific tasks. It runs in user mode, can interact with the user, and has a visual user interface. Each application runs in an independent process with its own independent address space. The boundary between different applications is called a process boundary.

[0065] In the embodiment of the present application, the application (ie, the first application) may be various applications, such as multimedia applications, office applications, instant messaging applications, and the like.

[0066] Multimedia is a combination of multiple media, including text, sound, and images. In computer systems, multimedia refers to a medium for interactive information exchange and dissemination between humans and computers that combines two or more media. The media used include text, images, photos, sound, animation, and video, as well as interactive features provided by programs.

[0067] Multimedia applications include video applications, audio applications, image editing applications, game applications, and text editing applications (such as Word applications and TXT applications). Video applications include video playback applications such as iQiyi, Tencent, Youku, Xiaohongshu, Kuaishou, and Douyin, or video editing applications such as Jianying, Miaojian, iZiao, and Bijian. Audio applications include audio playback applications such as QQ Music, NetEase Cloud Music, and Kugou Music, or audio editing applications such as Audio Editor and Audio Editor. Image editing applications include Meitu Xiuxiu and Tiantian Ptu.

[0068] Office applications include text editing applications, slide (PowerPoint, PPT) applications, Excel applications, etc.

[0069] Instant messaging applications include various communication applications, such as QQ, WeChat, DingTalk, Enterprise WeChat, Skype, Feishu, etc.

[0070] (3) User space

[0071] User space refers to the operating space of the user's application. In a user space, multiple application processes form a group, and the application processes in the group can communicate and share data without obstacles. In the embodiment of the present application, the applications on a display screen belong to the same user space, and applications in different user spaces cannot communicate directly. Each user space has a unique code (identity document, ID) to distinguish different user spaces.

[0072] (4) Headless system users

[0073] A headless system user, used to host all system services. A headless system user must always run in the background. This user cannot be directly deleted or accessed except during device setup. For example, a user cannot switch to this user type to perform tasks such as downloading apps or adding accounts. It can only be cleared by a factory reset.

[0074] Users of headless systems can set up and implement different functions according to actual conditions. For example, in the embodiment of the present application, functions such as instruction forwarding and / or resource integration to obtain aggregated pages can be implemented.

[0075] For example, in an embodiment of the present application, when an application is launched, the application state of the application will be registered with the headless system user. Further for example, when the application is registered, the display screen where the application is located and the user space ID corresponding to the display screen will be carried.

[0076] (5) Aggregation Page

[0077] An aggregate page is a page formed by the aggregation of content. This means that related content is integrated into a single page. There are also aggregations of article content, that is, there are many articles around a theme, which are integrated into a single content, such as typical cases or Baidu Encyclopedia.

[0078] In an embodiment of the present application, an aggregation page corresponds to a specific request, such as a first request. For example, if the first request is to play a video, the aggregation page is a video aggregation page. If the first request is to play music, the aggregation page is a music aggregation page. If the first request is to play an article, the aggregation page is an article aggregation page.

[0079] (6) Visible and Talkable

[0080] Visible and Talkable is a voice interaction method that eliminates the need for manual touch. Any function displayed on a smart terminal can be controlled through voice interaction, achieving the "mouth-only, hands-free" effect. For example, a multimedia application might have a play button on the interface. Simply saying "play video" will automatically play the video, achieving the "visible and talkable" feature.

[0081] In the voice control solution shown in Figure 1B, each screen needs to deploy its own application, such as a video APP, to support cross-screen operations under multiple screens, and the implementation solution is complicated.

[0082] Therefore, the present application provides a cross-screen control method, based on a headless system, where users can control the second display screen to perform the first task on the first display screen. Cross-screen control can be achieved without deploying applications on each screen of the first device, and the implementation solution is simple.

[0083] The first task may be any of various tasks, and there is no limitation on the first task. For example, the first task may be playing a video, playing an audio, displaying an image, editing a video, editing an audio, editing a text, modifying a PPT, editing an Excel spreadsheet, or opening a chat interface of a social friend in an instant messaging application.

[0084] The cross-screen control method of the embodiment of the present application can be executed by a first device, or by a chip in the first device. The first device is configured with a first display screen and a second display screen. A first operating system runs on the first display screen and the second display screen, the first display screen corresponds to a first user space, and the second display screen corresponds to a second user space.

[0085] The first device may be a vehicle, a computer, a television, or other device equipped with at least two display screens.

[0086] For example, referring to FIG1C , FIG1C is a schematic diagram of a first device provided by an embodiment of the present application; the first device takes a vehicle as an example, and the vehicle has a first display screen 101 and a second display screen 102, with the first display screen 101 being located on the passenger seat; referring to FIG1D , FIG1D is a schematic diagram of a second display screen provided by an embodiment of the present application; the second display screen 102 is located in the back row. Utilizing the cross-screen control method of an embodiment of the present application, a user sitting in the passenger seat can control the second display screen 102 to play a video via the first display screen 101. For example, in a family outing scenario, the parent in the front row can interact with the voice assistant on the front row screen to complete the video playback on the back row screen.

[0087] The cross-screen control method of the embodiment of the present application is described in detail below.

[0088] Referring to FIG. 2 , FIG. 2 is a flow chart of a cross-screen control method provided in an embodiment of the present application. Hereinafter, the execution subject takes the first device as an example, and the cross-screen control method 200 includes the following operations:

[0089] 201. A first device obtains a first request sent to a first user space.

[0090] Specifically, the first request is used to request execution of the first task through the second display screen.

[0091] Exemplarily, the first request may be input through voice, text, keystrokes, or touch.

[0092] The first request is sent to the first user space through voice interaction. For example, the user can send the first request by saying "Play Peppa Pig for the back row" to the voice assistant on the first display screen. For example, referring to Figures 3A, 3B, and 3C, Figure 3A is a schematic diagram of a specific flow of a cross-screen control method provided in an embodiment of the present application; Figure 3B is a schematic diagram of a specific flow of a cross-screen control method provided in an embodiment of the present application; Figure 3C is a schematic diagram of a specific flow of a cross-screen control method provided in an embodiment of the present application; wherein, the user can send the first request to the first user space by interacting with the voice assistant on the first display screen through dialogue.

[0093] For another example, the user can send the first request by inputting the text "Play Peppa Pig for the back row" in the request input box on the first display screen.

[0094] For another example, the user can send the first request by pressing a button on the first display screen. For example, when the button is a "play" button, the "play" button is used to request to play a video or music through the second display screen.

[0095] 202. The first device uses the first display screen to determine a target file corresponding to the first task.

[0096] Specifically, the first device can determine the target file using the first display screen, and the target file corresponds to the first task. In an embodiment of the present application, "file" can also be replaced by "object". When the first task is to play a video, the target file is the video file itself or information that can indicate the video file, such as the address of the video file (such as the playback address), the name and / or number of the video file, etc. When the first task is to modify a PPT, the target file is the PPT file itself or information that can indicate the PPT file, such as the address of the PPT file (such as the storage address), the name and / or number of the PPT file, etc. When the first task is to open the chat interface of a social friend of an instant messaging application, the target file is information that can indicate a social friend, such as the name and / or number of a social friend, etc.

[0097] 203. The first device controls the second display screen to output the target file through the headless system user.

[0098] Specifically, the target file is output by the first application, and the first application can be configured on the first display screen or the second display screen. When the first task is to play a video, the output target file is to output a video file (such as playing a video file). When the first task is to modify a PPT file, the output target file is to output a PPT file (such as opening a PPT file). When the first task is to open a chat interface of a social friend on an instant messaging application, the output target file is to output (or open) a chat interface of a social friend on the instant messaging application.

[0099] In the embodiment of the present application, based on the headless system, users can use the first display to control the second display to perform the first task across the screen, without having to deploy the application on each display of the first device. The implementation solution is simple and friendly to ecological expansion. In particular, multiple displays of the first device (such as the first display and the second display) run the same operating system, and different displays correspond to different user spaces.

[0100] Implementation method one:

[0101] In one possible implementation, referring to FIG. 3D , FIG. 3D is a schematic diagram of a specific flow of step 202 provided in an embodiment of the present application; the above-mentioned step 202 specifically includes the following steps:

[0102] 221. The first device moves the content interface of the first application to the first display screen for display through the headless system user.

[0103] Specifically, in an embodiment of the present application, a first application is configured in the second user space. There may be one or more first applications configured in the second user space. When there are multiple first applications, the user may be interacted with to determine which first application the user wishes to use to output the target file; or a first application may be randomly selected from the multiple first applications as the first application to output the target file.

[0104] The above-mentioned content interface corresponds to the first request. When the first request indicates the target file, the content in the content interface is the target file. For example, taking the target file as a target video file (such as Peppa Pig) as an example, when there is one target video file, the content interface is the playback page of the target video file. When there are multiple target videos (greater than or equal to two), the content interface is the result page of the target video. The result page shows multiple target videos, and the user can specify a target video as the final output target video. When the target file is not indicated in the first request, the content page is the homepage or search page of the first application, and the user can specify the target file based on the homepage or search page. For example, when the first request indicates to play a video and does not specify a target video, the content interface is the homepage or search page of the first application, and the user can interact with the homepage or search page to specify a video as the target video.

[0105] In the embodiment of the present application, moving the content interface of the first application refers to moving the controls, pop-up windows, active windows, processes, etc. of the first application to the first display screen to display the content interface of the first application on the first display screen.

[0106] 222. The first device determines a target file based on the content interface.

[0107] In this embodiment, cross-screen control is achieved by first moving the content interface of the first application to the first display screen, then determining the target file based on the content interface, and then having the headless system user control the second display screen to output the target file. This embodiment only requires that the second display screen be configured with an application, and cross-screen control can be achieved by executing the first task through the second display screen, which is a simple implementation solution.

[0108] In one possible implementation, step 221 specifically includes the following steps:

[0109] The first device sends a first request to the cross-screen transfer module of the headless system user. The cross-screen transfer module interacts with the first application based on the first request to determine the content interface of the first application. The first device uses the capabilities of the operating system to move the content interface of the first application to the first display screen for display.

[0110] Specifically, referring to Figure 3A , taking the first request as a voice request as an example, the first device sends the first request to the cross-screen transfer module of the headless system user via the voice assistant. The cross-screen transfer module interacts with the first application based on the first request to determine the content interface of the first application. The first device uses the operating system's capabilities to move the content interface of the first application to the first display screen for display.

[0111] In one possible implementation, referring to FIG. 3E , FIG. 3E is a schematic diagram of a specific flow chart of step 222 provided in an embodiment of the present application; the above-mentioned step 222 specifically includes the following steps:

[0112] S21. The first device obtains call stack information of the first application based on the content interface.

[0113] Specifically, the call stack information of the first application can be obtained through the operating system interface based on the content interface of the first application without going through the headless system user.

[0114] The call stack information of the first application includes the process information of the first application (such as the process stack), the source display screen of the first application or the user space unique code corresponding to the source display screen, and the package name of the first application. The source display screen refers to the display screen on which the first application originally runs, that is, the display screen on which the first application is installed.

[0115] S22. The first device obtains control information of the first application based on the call stack information.

[0116] Specifically, the above controls include function menus, various buttons, texts, etc.

[0117] S23. The first device determines a target file based on the control information and at least one control operation command.

[0118] Specifically, the control operation command includes but is not limited to selecting a target function, pressing a button, or selecting a target file. The specific form of the control operation command can be a voice command, a text command, or a key command. Taking a voice command as an example, when the target file is a video file, and the content interface is the playback page of the target video file, the content interface at this time displays a target video file, and the user can use voice instructions to confirm that the currently displayed target video file is the target file or to search for the video file again. When the content interface is the result page of the target video, and the content interface at this time displays multiple target video files, the user can use voice instructions to confirm that a certain target video file is the target file or to search for the video file again.

[0119] In one example, the first device can directly interact with the first application at the interface level based on the call stack information, that is, obtain control information based on the call stack information, and simulate clicks based on the control information and at least one control operation command to determine the target file.

[0120] For example, referring to Figure 3A, after the voice assistant obtains the call stack information, it can know from which screen the first application displayed in the foreground of the screen is projected through the call stack information of the first application, and then it can interact with the first application across the screen to achieve interface-level visibility and speech, thereby completing the selection of the target file.

[0121] In another example, the first device can also perform interface-level visible and verbal interaction with the first application through a headless system user. For example, referring to Figure 3A , the voice assistant of the first device forwards a command to obtain control information to the first application through the headless system user based on call stack information to obtain the control information of the first application. The voice assistant then simulates a click based on the control information and at least one control operation command to determine the target file. The simulated click command is forwarded to the first application through the headless system user.

[0122] The embodiment of the present application can determine the target file through the interface-level visible and speakable technology based on the content interface, effectively simplifying the operations required by the user when determining the target file, which is conducive to improving the user experience.

[0123] In one possible implementation, referring to FIG. 3F , FIG. 3F is a schematic diagram of a specific flow chart of step 203 provided in an embodiment of the present application; the above-mentioned step 203 specifically includes the following steps:

[0124] A231. The first device moves the content interface of the first application to the second display screen for display.

[0125] Specifically, the first device uses the capability of the operating system to move the content interface of the first application to the second display screen for display.

[0126] A232. The first device controls the first application to output the target file through the headless system user.

[0127] Specifically, referring to FIG3A , the first device forwards an output execution command to the first application through a headless system user to instruct the first application to output a target file.

[0128] In an embodiment of the present application, when the first application is configured on the first display screen, after determining the target file, the first device can first move the content interface of the first application to the second display screen for display, and then control the first application to output the target file; a possible method for outputting the target file through the second display screen is provided.

[0129] In another possible implementation, referring to FIG. 3G , FIG. 3G is a schematic diagram of another specific flow of step 203 provided in an embodiment of the present application; the above-mentioned step 203 specifically includes the following steps:

[0130] B231. The first device controls the first application to output a target file.

[0131] Specifically, the first device can control the first application to output the target file using interface-level visible and audible technology, without going through the headless system user. Alternatively, the first device can control the first application to output the target file through the headless system user. Please refer to the detailed description of step A232, which is not repeated here.

[0132] B232. The first device moves the content interface of the first application to the second display screen for display.

[0133] For the specific description of step B232, please refer to the specific description of step A231, which will not be repeated here.

[0134] In an embodiment of the present application, when the first application is configured on the first display screen, after determining the target file, the first device can first control the first application to output the target file, and then move the content interface of the first application to the second display screen for display; another possible method of outputting the target file through the second display screen is provided.

[0135] In the embodiment of the present application, cross-screen control is supported by multiple methods such as concurrent application of multiple instances (which can be understood as processes), application screen shifting, and interface-level visibility and speaking, without the need for applications to be deployed on each display screen.

[0136] Implementation method 2:

[0137] In one possible implementation, referring to FIG. 3H , FIG. 3H is a schematic diagram of another specific flow chart of step 202 provided in an embodiment of the present application; the above-mentioned step 202 specifically includes the following steps:

[0138] 223. The first device interacts with the first application through a headless system user to determine a content interface.

[0139] Specifically, the first application is configured in the first user space, and the content interface corresponds to the first request. For a detailed description of the first request, please refer to the relevant description of step 221, which will not be repeated here.

[0140] 224. The first device determines a target file based on the content interface.

[0141] In this embodiment, a headless system user interacts with a first application on the first device to determine a content interface. Based on the content interface, the first device then determines a target file. The headless system user then controls the second display to output the target file, thereby achieving cross-screen control. This solution is simple to implement, requiring only the first display to be configured with an application. The first task can be executed on the second display through cross-screen control.

[0142] In a possible implementation, step 223 specifically includes the following steps:

[0143] The first device sends a first request to the cross-screen transfer module of the headless system user, and the cross-screen transfer module interacts with the first application according to the first request to determine the content interface of the first application.

[0144] Referring to Figure 3B, taking the first request as a voice request as an example, the first device sends the first request to the cross-screen transfer module of the headless system user through the voice assistant. The cross-screen transfer module interacts with the first application according to the first request to determine the content interface of the first application.

[0145] In one possible implementation, referring to FIG. 3B , step 224 specifically includes the following steps:

[0146] The first device obtains call stack information of the first application based on the content interface.

[0147] The first device obtains control information of the first application based on the call stack information.

[0148] The first device determines a target file based on the control information and at least one control operation command.

[0149] Specifically, the detailed description of step 224 can refer to the relevant description of FIG3E , which will not be repeated here.

[0150] In a possible implementation, step 203 specifically includes the following steps:

[0151] The first device moves the content interface of the first application to the second display screen for display.

[0152] The first device controls the first application to output a target file through a headless system user.

[0153] In this embodiment of the present application, when a first application is configured on a first display screen, after determining a target file, the first device may first move the content interface of the first application to the second display screen for display, and then control the first application to output the target file; thus, a possible method for outputting the target file via the second display screen is provided. A detailed description of step 203 can be found in the relevant description of FIG. 3F and is not repeated here.

[0154] In one possible implementation, referring to FIG3B , step 203 specifically includes the following steps:

[0155] The first device controls the first application to output a target file.

[0156] Specifically, please refer to the relevant description of step B231 and will not be repeated here.

[0157] The first device moves the content interface of the first application to the second display screen for display.

[0158] Specifically, please refer to the relevant description of step B232 and will not be repeated here.

[0159] In an embodiment of the present application, when the first application is configured on the first display screen, after determining the target file, the first device can first control the first application to output the target file, and then move the content interface of the first application to the second display screen for display; another possible method of outputting the target file through the second display screen is provided.

[0160] Referring to Figure 3B, the embodiment of the present application deploys applications only on the first display screen, and the voice assistant only interacts with the applications on the first display screen, and is displayed on other screens (such as the second display screen) by moving the screen to achieve cross-screen control.

[0161] Implementation method three:

[0162] In one possible implementation, step 202 specifically includes the following steps:

[0163] The first device interacts with the aggregated page on the first display screen to determine a target file.

[0164] Specifically, the first device can obtain a corresponding aggregation page according to the first request, and the aggregation page displays at least one candidate file (or candidate object), and the candidate file corresponds to the first request. The above-mentioned interaction can be voice interaction, touch interaction, or key interaction. In an embodiment of the present application, the candidate file displayed in the aggregation page can be the candidate file itself or the information that can indicate the candidate file, such as the address of the candidate file (such as the playback address), the name and / or number of the candidate file, etc.

[0165] Taking the first request as a request to play a video as an example, when the first request is "Play Wu J's movie", refer to Figure 3I, Figure 3I is a schematic diagram of an aggregation page provided in an embodiment of the present application, and the aggregation page corresponding to "Play Wu J's movie" is shown in Figure 3I, wherein the candidate files in the aggregation page include Zhan X5, Wanli Z Tu, Zhan X, Wandering Y Qiu, etc. The upper left corner of each candidate file is the number of the candidate file, such as 1, 2, 3, 4, etc.; and when the playback application of the candidate file is not a local application, the corresponding playback application is marked in the lower left corner of the candidate file, such as B Station, Youku, etc.

[0166] Exemplarily, when the candidate file is a video file, referring to Figure 3I, only a video snapshot of each candidate file is displayed in the aggregation page. When controlling the output of the target file, the user only needs to indicate the number of the candidate file to determine the target file. The first device can obtain the name of the candidate file (that is, the target file at this time) according to the number of the candidate file, and then control the output of the target file according to the name of the target file.

[0167] For example, when the candidate files are music files, only the name and file number of each candidate file need to be displayed in the aggregation page.

[0168] In an embodiment of the present application, the target file can be determined by interacting with the aggregation page on the first display screen. The present application provides an aggregation page to determine the target file. The user does not need to frequently switch between different applications to determine the target file, which saves user operations and improves the user experience.

[0169] In a possible implementation, the cross-screen control method further includes the following steps:

[0170] S1. A first device obtains at least one candidate file from an application on a first display screen and / or a second display screen through a headless system user.

[0171] Specifically, a candidate file is obtained from a local application of the first device. In an embodiment of the present application, the obtained candidate file can be the candidate file itself or information that can indicate the candidate file, such as the address of the candidate file (such as the playback address), the name and / or number of the candidate file, etc. For example, when the candidate file is a video file, obtaining the candidate file can be understood as obtaining the playback address of the video file. When the candidate file is a music file, obtaining the candidate file can be understood as obtaining the playback address corresponding to the music file.

[0172] The type of the local application corresponds to the first request. For example, if the first request is to play a video, the local application is a local video application. If the first request is to play music, the local application is a local music application.

[0173] For example, referring to Figure 3C , the voice assistant of a first device sends a first request to the cross-screen transfer module of a headless system user. The cross-screen transfer module retrieves candidate files based on the first request and the application status of the first device. Specifically, the cross-screen transfer module first determines the application type indicated by the first request and then interacts with the first application corresponding to that application type to retrieve the candidate files from the first application.

[0174] S2. The first device generates an aggregate page based on at least one candidate file.

[0175] In an embodiment of the present application, the first device obtains a candidate file from a local application and then generates an aggregate page, providing a possible method for generating an aggregate page.

[0176] In another possible implementation, the cross-screen control method further includes the following steps:

[0177] S3. The first device obtains at least one candidate file from the second device.

[0178] Specifically, the second device may be a server or other device. In the embodiment of the present application, the candidate file may be the candidate file itself or information indicating the candidate file, such as the address of the candidate file (such as the playback address), the name and / or number of the candidate file, etc.

[0179] For example, referring to Figure 3C , a first device sends a first request to a voice cloud server via a voice assistant. The voice cloud server then retrieves a resource, namely a candidate file, from a second device based on the first request. If the candidate file is a video file, the specific form of the candidate file can be the video's playback address. Video files are large in data size, and transmitting the playback address can effectively reduce the amount of data transmitted, thereby improving the responsiveness of cross-screen control.

[0180] S4. The first device generates an aggregate page based on at least one candidate file.

[0181] In an embodiment of the present application, when the first device cannot obtain the candidate file, the candidate file can be obtained from the second device, and then an aggregate page is generated, providing another possible method for generating an aggregate page.

[0182] In another possible implementation, the cross-screen control method further includes the following steps:

[0183] S5. The first device obtains at least one first candidate file from the second device.

[0184] S6. The first device obtains at least one second candidate file from an application on the first display screen and / or the second display screen through a headless system user.

[0185] The order of step S5 and step S6 can be swapped, and the two steps can also be executed simultaneously.

[0186] S7. The first device generates an aggregate page based on at least one first candidate file and at least one second candidate file.

[0187] Specifically, after the first device obtains at least one first candidate file from the second device, it indicates the first candidate file to the cross-screen transfer module of the headless system user. Referring to Figure 3C, after the voice assistant of the first device obtains at least one first candidate file, it can carry the first candidate file when sending a first request to the headless system user. The cross-screen transfer module can obtain at least one second candidate file. In this way, the cross-screen transfer module can aggregate the first candidate file and the second candidate file to generate an aggregated page.

[0188] In an embodiment of the present application, the first candidate file and the second candidate file can be the candidate files themselves or information that can indicate the candidate files, such as the address of the candidate file (such as the playback address), the name and / or number of the candidate file, etc.

[0189] In the embodiment of the present application, candidate files can be obtained from the local application of the first device and the second device, and then an aggregate page can be generated, which provides another possible method for generating an aggregate page.

[0190] In one possible implementation, the interaction with the aggregated page on the first display screen to determine the target file specifically includes the following steps:

[0191] The first device obtains call stack information of the aggregated page.

[0192] The first device obtains control information of the aggregated page based on the call stack information.

[0193] The first device determines a target file based on the control information and at least one control operation command.

[0194] In the embodiment of the present application, the target file can be determined based on the aggregated page through the interface-level visible and talkable technology, which effectively simplifies the operations required by the user when determining the target file, thereby improving the user experience. For a specific description, please refer to the relevant description of Figure 3E, which will not be repeated here.

[0195] In a possible implementation, step 203 specifically includes the following steps:

[0196] The first device controls a first application to output a target file through a headless system user, and the first application is configured on a second display screen.

[0197] Specifically, the first device forwards the output execution command to the first application through the headless system user, and the first application responds to the output execution command and outputs the target file. In this embodiment, the first application can be one or more. When there are multiple first applications, the user can specify one of the first applications as the application for outputting the target file.

[0198] In an embodiment of the present application, when the first application is configured on the second display screen, after the target file is determined, the headless system user can directly control the first application to output the target file, and the cross-screen control solution is simple to implement.

[0199] In a possible implementation, step 203 specifically includes the following steps:

[0200] The first device moves the content interface of the first application to the second display screen for display.

[0201] The first device controls the first application to output a target file through a headless system user.

[0202] In an embodiment of the present application, when a first application is configured on a first display screen, after determining a target file, the first application's content interface can be first moved to a second display screen for display, and then the first application can be controlled to output the target file. This provides a possible method for outputting the target file via a second display screen. For a detailed description of step 203, please refer to the relevant description of FIG. 3F and will not be repeated here.

[0203] In one possible implementation, referring to FIG3C , step 203 specifically includes the following steps:

[0204] The first device controls the first application to output a target file (not shown in FIG. 3C ).

[0205] Specifically, please refer to the relevant description of step B231 and will not be repeated here.

[0206] The first device moves the content interface of the first application to the second display screen for display.

[0207] Specifically, please refer to the relevant description of step B232 and will not be repeated here.

[0208] In an embodiment of the present application, when the first application is configured on the first display screen, after determining the target file, the first application can be controlled to output the target file first, and then the content interface of the first application can be moved to the second display screen for display; another possible method of outputting the target file through the second display screen is provided.

[0209] Referring to Figure 3C, in this embodiment, the voice assistant only interacts with the aggregated page of the first display screen, and displays the effect on other screens by moving the screen.

[0210] The above describes in detail the method of the embodiment of the present application. The following describes the device provided by the embodiment of the present application.

[0211] The present application also provides a first device, which includes a unit or module for executing the cross-screen control method described in any of the above embodiments.

[0212] Figure 4 is a schematic diagram of the structure of a possible device provided in an embodiment of the present application. Among them, the first device shown in Figure 4 can be used to implement the functions of the above-mentioned cross-screen control method embodiment, and thus can also achieve the beneficial effects of the above-mentioned cross-screen control method embodiment. In the embodiment of the present application, the first device can be an electronic device, or it can be a module (such as a chip) used in an electronic device.

[0213] As shown in Figure 4, the first device 400 includes an acquisition module 401, a determination module 402, and an output module 403. The first device 400 is used to implement the functions of the embodiment of the cross-screen control method shown in Figure 2. Alternatively, the first device 400 may include a module for implementing any function or operation in the embodiment of the cross-screen control method shown in Figure 2, which may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

[0214] The first device 400 is configured with a first display screen and a second display screen. A first operating system is run on the first display screen and the second display screen. The first display screen corresponds to a first user space, and the second display screen corresponds to a second user space.

[0215] When the first device 400 is used to implement the functions of the method embodiment shown in Figure 2, the acquisition module 401 is used to obtain a first request sent to the first user space. The above-mentioned first request is used to request the execution of the first task through the second display screen. The determination module 402 is used to use the first display screen to determine the target file corresponding to the first task. The output module 403 is used to control the second display screen to output the target file through the headless system user. The above-mentioned headless system user is used to host system services. Among them, the target file is output through the first application.

[0216] It can be seen that in the embodiment of the present application, the first device 400 can realize cross-screen control of the second display screen on the first display screen to perform the first task based on the headless system, without the need to deploy the application on each display screen of the first device, and the implementation solution is simple.

[0217] In one possible implementation, the determining module 402 is specifically configured to: move, via a headless system user, a content interface of a first application to a first display screen for display. The first application is configured in a second user space, and the content interface corresponds to the first request. The target file is determined based on the content interface.

[0218] In one possible implementation, the determining module 402 is specifically configured to: determine a content interface through interaction between a headless system user and a first application, wherein the first application is configured in a first user space, and the content interface corresponds to the first request, and determine a target file based on the content interface.

[0219] In one possible implementation, the determination module 402, in determining the target file based on the content interface, is specifically configured to: obtain call stack information of the first application based on the content interface; obtain control information of the first application based on the call stack information; and determine the target file based on the control information and at least one control operation command.

[0220] In one possible implementation, the determining module 402 is specifically configured to interact with an aggregate page on the first display screen to determine a target file. The aggregate page displays at least one candidate file corresponding to the first request.

[0221] In one possible implementation, the acquisition module 401 is further configured to obtain at least one candidate file from an application on the first display screen and / or the second display screen via a headless system user. The first device 400 further includes a generation module. The generation module is configured to generate an aggregated page based on the at least one candidate file.

[0222] In another possible implementation, the acquisition module 401 is further configured to acquire at least one candidate file from the second device. The generation module is configured to generate an aggregate page based on the at least one candidate file.

[0223] In another possible implementation, the acquisition module 401 is further configured to acquire at least one first candidate file from a second device. A headless system user acquires at least one second candidate file from an application on the first display and / or the second display. The generation module is configured to generate an aggregated page based on the at least one first candidate file and the at least one second candidate file.

[0224] In one possible implementation, the determination module 402, in interacting with the aggregated page on the first display screen to determine the target file, is specifically configured to: obtain call stack information of the aggregated page; obtain control information of the aggregated page based on the call stack information; and determine the target file based on the control information and at least one control operation command.

[0225] In a possible implementation, the output module 403 is specifically configured to: control the first application to output the target file through the headless system user. The first application is configured on the second display screen.

[0226] In another possible implementation, the output module 403 is specifically configured to: move the content interface of the first application to the second display screen for display, and control the first application to output the target file through the headless system user.

[0227] In a possible implementation, the output module 403 is specifically configured to: control the first application to output the target file through the headless system user, and move the content interface of the first application to the second display screen for display.

[0228] For the introduction of the above modules, please refer to the description of the above embodiments, which will not be repeated here.

[0229] Referring to Figure 5, Figure 5 is a schematic diagram of the structure of another first device provided in an embodiment of the present application. The present application also provides a first device, wherein the first device 500 includes a memory 501, a processor 502, a communication interface 504, and a bus 503. The memory 501, the processor 502, and the communication interface 504 are communicatively connected to each other via the bus 503.

[0230] Optionally, the first device 500 further includes at least two display screens (not shown), such as a first display screen and a second display screen, which are communicatively connected to the memory 501, the processor 502, and the communication interface 504 via the bus 503. The display screen is used to output information and interact with the user. Optionally, the first device further includes an output module (not shown), which is communicatively connected to the memory 501, the processor 502, and the communication interface 504 via the bus 503, and the output module is used to output audio. The output module can be a speaker. Exemplarily, after the first device 500 determines the target file, the target file can be output through the output module, such as voice output or display output.

[0231] The memory 501 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 501 may store programs. When the program stored in the memory 501 is executed by the processor 502, the processor 502 and the communication interface 504 are used to perform the various steps of the cross-screen control method of any embodiment of the present application.

[0232] The processor 502 can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the unit in the first device of any embodiment of the present application, or to execute the cross-screen control method of any embodiment of the present application.

[0233] The processor 502 may also be an integrated circuit chip with signal processing capabilities. During implementation, the various steps of the cross-screen control method of any embodiment of the present application may be completed by hardware integrated logic circuits or software instructions in the processor 502. The above-mentioned processor 502 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the cross-screen control method in conjunction with any embodiment of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, or the like. The storage medium is located in the memory 501, and the processor 502 reads the information in the memory 501 and combines its hardware to complete the functions required to be performed by the unit included in the first device of any embodiment of the present application, or executes the cross-screen control method of any embodiment of the present application.

[0234] The communication interface 504 uses a transceiver such as, but not limited to, a transceiver to implement communication between the first device 500 and other devices or a communication network. For example, candidate files can be obtained through the communication interface 504.

[0235] The bus 503 may include a path for transmitting information between the various components of the first device 500 (for example, the memory 501, the processor 502, the communication interface 504). In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the apparatus embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

[0236] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0237] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0238] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a read-only memory (ROM), a random access memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a tape, a magnetic disk, or an optical medium, such as a digital versatile disc (DVD), or a semiconductor medium, such as a solid state drive (SSD).

[0239] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A cross-screen control method, characterized in that: The method is applied to a first device, the first device is configured with a first display screen and a second display screen, a first operating system is run on the first display screen and the second display screen, the first display screen corresponds to a first user space, and the second display screen corresponds to a second user space; the method includes: Acquire a first request sent to the first user space, where the first request is used to request execution of a first task through the second display screen; Using the first display screen to determine a target file corresponding to the first task; The target file is outputted by controlling the second display screen through a headless system user, and the headless system user is used for hosting system services.

2. The method according to claim 1, characterized in that The using the first display screen to determine the target file corresponding to the first task includes: The headless system user moves a content interface of a first application to the first display screen for display, wherein the first application is configured in the second user space, and the content interface corresponds to the first request; The target file is determined based on the content interface.

3. The method according to claim 1, characterized in that The using the first display screen to determine the target file corresponding to the first task includes: Determine a content interface by interacting with a first application through the headless system user, the first application being configured in the first user space, and the content interface corresponding to the first request; The target file is determined based on the content interface.

4. The method according to claim 2 or 3, characterized in that: The determining the target file based on the content interface includes: Acquire call stack information of the first application based on the content interface; Acquire control information of the first application based on the call stack information; The target file is determined based on the control information and at least one control operation command.

5. The method according to claim 1, characterized in that The using the first display screen to determine the target file corresponding to the first task includes: Interact with an aggregation page on the first display screen to determine the target file, the aggregation page showing at least one candidate file, the candidate file corresponding to the first request.

6. The method according to claim 5, characterized in that The method further comprises: Acquire the at least one candidate file from the second device; The aggregate page is generated based on the at least one candidate file.

7. The method according to claim 5, characterized in that The method further comprises: Obtaining, by the headless system user, the at least one candidate file from an application on the first display screen and / or the second display screen; The aggregate page is generated based on the at least one candidate file.

8. The method according to claim 5, characterized in that The method further comprises: Acquire at least one first candidate file from the second device; Obtaining at least one second candidate file from an application on the first display screen and / or the second display screen by the headless system user; The aggregate page is generated based on the at least one first candidate file and the at least one second candidate file.

9. The method according to any one of claims 5 to 8, characterized in that: The interacting with the aggregated page on the first display screen to determine the target file includes: Obtaining call stack information of the aggregation page; Acquire control information of the aggregate page based on the call stack information; The target file is determined based on the control information and at least one control operation command.

10. The method according to any one of claims 5 to 9, characterized in that: The step of controlling the second display screen to output the target file by a headless system user includes: The headless system user controls a first application to output the target file, and the first application is configured on the second display screen.

11. The method according to any one of claims 1 to 9, characterized in that: The step of controlling the second display screen to output the target file by a headless system user includes: Moving the content interface of the first application to be displayed on the second display screen; The headless system user controls the first application to output the target file.

12. The method according to any one of claims 1 to 9, characterized in that: The step of controlling the second display screen to output the target file by a headless system user includes: Controlling the first application to output the target file through a headless system user; The content interface of the first application is moved to be displayed on the second display screen.

13. A first device, characterized in that: The first device includes a unit or module for executing the cross-screen control method according to any one of claims 1 to 12.

14. A first device, characterized in that: It includes a processor and a memory, wherein the processor and the memory are connected, wherein the memory is used to store program code, and the processor is used to call the program code to execute the cross-screen control method as described in any one of claims 1 to 12.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the cross-screen control method according to any one of claims 1 to 12.

Images