Cross-screen control method and related equipment

Abstract

The embodiment of the invention provides a cross-screen control method and related equipment, and relates to the field of communication. The method may be performed by a first device, or by a chip in the first device. The first device is provided with a first display screen and a second display screen. A first operation 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 the following steps: acquiring a first request sent to a first user space; the first request is used for requesting to execute the first task through the second display screen. And determining a target file corresponding to the first task by using the first display screen. And controlling the second display screen to output the target file through the headless system user. The headless system user is used for hosting system services. According to the scheme, a headless system-based user can control the second display screen to execute the first task on the first display screen in a cross-screen manner, and application does not need to be deployed on each display screen of the first equipment, so that the implementation scheme is simple.

Description

Technical Field

[0001] 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

[0002] 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."

[0003] As an important application in the cockpit, voice assistant can greatly simplify various operations in the cockpit and improve the user experience. Figure 1A , Figure 1A This is a schematic diagram of a voice assistant controlling the audio and video entertainment content on the rear seat provided by an embodiment of the present application; when the whole family is traveling (children are sitting in the back seat), the co-pilot (parent) controls the audio and video entertainment content on the rear seat screen through the voice assistant on the co-pilot screen, which becomes a rigid demand scenario. Figure 1B , Figure 1B This is a specific flow chart of a voice assistant controlling rear-seat audio-visual 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 voice assistant of the co-pilot; and then play the target video on the rear-seat video application (Application, APP) on the rear screen through cross-screen distribution and cross-system communication. Among them, the resources of the video aggregation page can be obtained through method 1 and method 2. However, Figure 1B In the voice control solution shown, 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. Summary of the invention

[0004] 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 scheme is simple.

[0005] In a first aspect, a cross-screen control method is provided, which 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 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.

[0006] 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 to perform a first task through a second display screen. Using the first display screen to determine a target file corresponding to the first task. Controlling the second display screen to output the target file through a headless system user. The headless system user is used to host system services. Among them, the target file is output through a first application.

[0007] It can be seen that in this solution, based on the headless system, the user can realize the cross-screen control of the second display screen by the first display screen to perform the first task, without the need to deploy the application on each display screen of the first device, and the implementation solution is simple. Among them, the first task can be various tasks, and there is no limitation on the first task.

[0008] In a possible implementation of the first aspect, the above-mentioned use of the first display screen to determine the target file corresponding to the first task 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.

[0009] In this solution, the first application runs in the second user space. 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 controlling the second display screen to output the target file through the headless system user, cross-screen control is achieved. As long as the second display screen is configured with the first application, cross-screen control can be achieved to execute the first task through the second display screen, and the implementation solution is simple.

[0010] In a possible implementation of the first aspect, the method of using the first display screen to determine the target file corresponding to the first task 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.

[0011] In this solution, the first application runs in the first user space. The headless system user first interacts with the first application to determine the content interface, then determines the target file based on the content interface, and then the headless system user controls the second display screen to output the target file to achieve cross-screen control. As long as the first display screen is configured with an application, cross-screen control can be achieved to execute the first task through the second display screen, and the implementation scheme is simple.

[0012] In a possible implementation of the first aspect, the above-mentioned 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.

[0013] 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 a target function, pressing a button, or selecting a target file. The target file can be determined based on the content interface through the interface-level visible and audible 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.

[0014] In a possible implementation of the first aspect, the above-mentioned use of the first display screen to determine the target file corresponding to the first task 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, and the candidate file corresponds to the first request.

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

[0016] 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 through a headless system user, and generating an aggregate page based on the at least one candidate file.

[0017] 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.

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

[0019] In this solution, when the first device cannot obtain the candidate file, the candidate file can be obtained from the second device to generate an aggregate page, which provides another possible method for generating an 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 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 through a headless system user. Generating an aggregate page based on the at least one first candidate file and the at least one second candidate file.

[0021] 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.

[0022] In a possible implementation of the first aspect, the above-mentioned interaction 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. Based on the call stack information, obtaining control information of the aggregated page. Determining the target file based on the control information and at least one control operation command.

[0023] 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 that the user needs to perform when determining the target file, and is conducive to improving the user experience.

[0024] 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.

[0025] In this solution, 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.

[0026] In a possible implementation of the first aspect, the above-mentioned 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. Controlling the first application to output the target file by the headless system user.

[0027] In this solution, when the first application is configured on the first display screen, after the target file is determined, 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.

[0028] In a possible implementation of the first aspect, the above-mentioned 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. Moving the content interface of the first application to the second display screen for display.

[0029] In this solution, when the first application is configured on the first display screen, after the target file is determined, 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.

[0030] 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.

[0031] 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.

[0032] 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.

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

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

[0035] 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

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

[0037] Figure 1A is a schematic diagram of a voice assistant controlling rear-seat audio-visual entertainment content provided by an embodiment of the present application;

[0038] Figure 1B This is a schematic diagram of a specific process of a voice assistant controlling rear-seat audio-visual entertainment content provided by an embodiment of the present application;

[0039] Figure 1C is a schematic diagram of a first device provided in an embodiment of the present application;

[0040] Figure 1D is a schematic diagram of a second display screen provided in an embodiment of the present application;

[0041] Figure 2 It is a flowchart of a cross-screen control method provided by an embodiment of the present application;

[0042] Figure 3A It is a specific flow chart of a cross-screen control method provided by an embodiment of the present application;

[0043] Figure 3B It is a specific flow chart of a cross-screen control method provided by an embodiment of the present application;

[0044] Figure 3C It is a specific flow chart of a cross-screen control method provided by an embodiment of the present application;

[0045] Figure 3D This is a specific flow chart of step 202 provided in an embodiment of the present application;

[0046] Figure 3E is a specific flow chart of step 222 provided in an embodiment of the present application;

[0047] Figure 3F This is a specific flow chart of step 203 provided in an embodiment of the present application;

[0048] Figure 3G is another specific flow chart of step 203 provided in an embodiment of the present application;

[0049] Figure 3H is another specific flow chart of step 202 provided in an embodiment of the present application;

[0050] Fig. 3I is a schematic diagram of an aggregation page provided in an embodiment of the present application;

[0051] Figure 4 is a structural schematic diagram of a first device provided in an embodiment of the present application;

[0052] Figure 5 It is a structural schematic diagram of another first device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0054] In the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0055] The "at least one" mentioned in the embodiments of the present application refers to one or more, and "multiple" refers to two or more. "At least one of the following" or its similar expression 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 the 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 associated objects before and after are an "or" relationship. The serial numbers of the steps of the embodiments of the present 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.

[0056] Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" used in the embodiments of the present 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 the convenience of description, and do not represent the difference in structure, importance, etc. between the first device and the second device. In some embodiments, the first device and the second device can also be the same device.

[0057] In the above embodiments, the term "when..." can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...", depending on the context. The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modification, equivalent substitution, improvement, etc. made within the concept and principle of the present application shall be included in the protection scope of the present application.

[0058] 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.

[0059] (1) Operating system

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

[0061] (2) Application

[0062] An application is a computer program that is used to complete one or more specific tasks. It runs in user mode, can interact with users, and has a visual user interface. Each application runs in an independent process and has its own independent address space. The dividing line between different applications is called a process boundary.

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

[0064] Multimedia is a combination of multiple media, including text, sound, image and other media forms. In computer systems, multimedia refers to a human-computer interactive information exchange and communication medium that combines two or more media. The media used include text, pictures, photos, sound, animation and video, as well as the interactive functions provided by the program.

[0065] Multimedia applications include video applications, audio applications, image editing applications, game applications, text editing applications (such as Word applications, TXT applications, etc.). Video applications include video playback applications such as iQiyi, Tencent, Youku, Xiaohongshu, Kuaishou, Douyin, etc., or video editing applications such as Jianying, Miaojian, iFeiYing, 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, etc.

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

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

[0068] (3) User space

[0069] User space refers to the running 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.

[0070] (4) Headless system users

[0071] Headless system user, used to host all system services. The headless system user must always run in the background. The user cannot be directly deleted or accessed except in the case of device settings. For example, the user cannot switch to this user type to perform tasks such as downloading applications or adding accounts. It can only be cleared by a factory reset.

[0072] 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.

[0073] Exemplarily, in the 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 exemplary, 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.

[0074] (5) Aggregation Page

[0075] Aggregation pages refer to pages formed by the aggregation of content. That is, some related things are integrated into a web page, and there is also the aggregation of article content, that is: there are many contents around a theme, and these contents are integrated into one content, such as typical cases or Baidu Encyclopedia.

[0076] In the embodiment of the present application, the aggregation page corresponds to a specific request, such as the 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.

[0077] (6) Visible and Talkable

[0078] Visible and Sayable is a voice interaction method that does not require manual touch by the user. As long as the function options that can be displayed on the smart terminal can be controlled through voice interaction, it realizes "only speaking, no hands". For example, a multimedia application has a play button on the interface, and the operation intention is to play the video. You only need to say "play video" to complete the automatic playback of the video, realizing the function of Visible and Sayable.

[0079] Figure 1B In the voice control solution shown, 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.

[0080] Therefore, the present application provides a cross-screen control method, based on a headless system, a user can realize cross-screen control of a second display screen on the first display screen to perform a first task. Cross-screen control can be achieved without deploying an application on each screen of the first device, and the implementation scheme is simple.

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

[0082] The cross-screen control method of the embodiment of the present application can be executed by the 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 the first user space, and the second display screen corresponds to the second user space.

[0083] The first device may be a device such as a vehicle, a computer, or a television set that is equipped with at least two display screens.

[0084] For example, reference Figure 1C , Figure 1C 1 is a schematic diagram of a first device provided in an embodiment of the present application; the first device takes a vehicle as an example, the vehicle has a first display screen 101 and a second display screen 102, and the first display screen 101 is arranged on the co-pilot; Figure 1D , Figure 1D 1 is a schematic diagram of a second display screen provided in an embodiment of the present application; the second display screen 102 is arranged in the back row. Using the cross-screen control method of the embodiment of the present application, the user sitting in the front passenger seat can control the second display screen 102 to play videos through the first display screen 101. For example, in a family outing, 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.

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

[0086] refer to Figure 2 , Figure 2 2 is a flow chart of a cross-screen control method provided by 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:

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

[0088] Specifically, the first request is used to request to execute the first task through the second display screen.

[0089] Exemplarily, the first request may be input by voice, text, keystroke, or touch.

[0090] The first request is sent to the first user space by 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. Figure 3A , Figure 3B and Figure 3C , Figure 3A It is a specific flow chart of a cross-screen control method provided by an embodiment of the present application; Figure 3B It is a specific flow chart of a cross-screen control method provided by an embodiment of the present application; Figure 3C It is a specific flow chart of a cross-screen control method provided in an embodiment of the present application; wherein, the user interacts with the voice assistant on the first display screen, that is, a first request can be sent to the first user space.

[0091] 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.

[0092] 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.

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

[0094] Specifically, the first device can determine the target file using the first display screen, and the target file corresponds to the first task. In the 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 the 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 the instant messaging application, the target file is information that can indicate the social friend, such as the name and / or number of the social friend, etc.

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

[0096] 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 an output video file (such as playing a video file). When the first task is to modify a PPT, the output target file is an output PPT file (such as opening a PPT file). When the first task is to open a chat interface of a social friend of an instant messaging application, the output target file is to output (or open) a chat interface of a social friend of the instant messaging application.

[0097] In the embodiment of the present application, based on the headless system, the user can realize the cross-screen control of the second display screen on the first display screen to perform the first task, without deploying the application on each display screen of the first device, and the implementation scheme is simple and friendly to ecological expansion. Among them, multiple display screens of the first device (such as the first display screen and the second display screen) run the same operating system, and different display screens correspond to different user spaces.

[0098] Implementation method 1:

[0099] In one possible implementation, reference Figure 3D , Figure 3D 202 is a specific flow chart of step 202 provided in an embodiment of the present application; the above step 202 specifically includes the following steps:

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

[0101] Specifically, in an embodiment of the present application, the first application is configured in the second user space. The first application configured in the second user space may be one or more. When there are multiple first applications, it is possible to interact with the user to determine which first application the user wants to output the target file through; or randomly select one of the multiple first applications as the first application that outputs the target file.

[0102] 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 the video and does not specify the 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.

[0103] 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.

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

[0105] In the embodiment of the present application, the content interface of the first application is first moved to the first display screen, the target file is determined based on the content interface, and the headless system user controls the second display screen to output the target file, thereby realizing cross-screen control. This embodiment only requires that the second display screen is configured with an application, that is, cross-screen control can be realized to execute the first task through the second display screen, and the implementation scheme is simple.

[0106] In a possible implementation, the above step 221 specifically includes the following steps:

[0107] 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. The first device moves the content interface of the first application to the first display screen for display through the capability of the operating system.

[0108] Specifically, refer to Figure 3ATaking 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, 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. The first device moves the content interface of the first application to the first display screen for display through the capability of the operating system.

[0109] In one possible implementation, reference Figure 3E , Figure 3E 222 is a specific flow chart of step 222 provided in an embodiment of the present application; the above step 222 specifically includes the following steps:

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

[0111] 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.

[0112] 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 where the first application originally runs, that is, the display screen where the first application is installed.

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

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

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

[0116] 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 re-search the video file. When the content interface is the result page of the target video, when the content interface displays multiple target video files, the user can use voice instructions to confirm that a certain target video file is the target file or re-search the video file.

[0117] 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.

[0118] For example, refer to Figure 3A After the voice assistant obtains the call stack information, through the call stack information of the first application, the voice assistant can know which screen the first application displayed in the foreground of the screen is projected from, 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.

[0119] In another example, the first device can also interact with the first application at the interface level through the headless system user. Figure 3A The voice assistant of the first device forwards a command for obtaining control information to the first application through a headless system user based on the call stack information to obtain the control information of the first application, and 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.

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

[0121] In one possible implementation, reference Figure 3F , Figure 3F 203 is a specific flow chart of step 203 provided in an embodiment of the present application; the above step 203 specifically includes the following steps:

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

[0123] Specifically, the first device moves the content interface of the first application to the second display screen for display through the capability of the operating system.

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

[0125] Specifically, refer to Figure 3A , the first device forwards the output execution command to the first application through the headless system user to instruct the first application to output the target file.

[0126] 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.

[0127] In another possible implementation, reference Figure 3G , Figure 3G 203 is another specific flow chart of step 203 provided in an embodiment of the present application; the above step 203 specifically includes the following steps:

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

[0129] Specifically, the first device can use the interface-level visible and audible technology to control the first application to output the target file, and at this time, it is not necessary to go through the headless system user. Alternatively, the first device controls the first application to output the target file through the headless system user, and the specific description of step A232 can be referred to, which will not be repeated here.

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

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

[0132] 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.

[0133] In the embodiments of the present application, cross-screen control is supported through 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.

[0134] Implementation method 2:

[0135] In one possible implementation, reference Figure 3H , Figure 3H 202 is another specific flow chart of step 202 provided in an embodiment of the present application; the above step 202 specifically includes the following steps:

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

[0137] 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, reference may be made to the relevant description of step 221, which will not be repeated here.

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

[0139] In the embodiment of the present application, the first device first interacts with the first application through the headless system user to determine the content interface, then determines the target file based on the content interface, and then controls the second display screen to output the target file through the headless system user to achieve cross-screen control. It only requires that the first display screen is configured with an application, that is, cross-screen control can be achieved to execute the first task through the second display screen, and the implementation scheme is simple.

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

[0141] 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 through an interface according to the first request to determine the content interface of the first application.

[0142] refer 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 through an interface according to the first request to determine the content interface of the first application.

[0143] In one possible implementation, reference Figure 3B , the above step 224 specifically includes the following steps:

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

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

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

[0147] Specifically, the detailed description of step 224 can be referred to Figure 3E The relevant description is not repeated here.

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

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

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

[0151] In the 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. The specific description of step 203 can be referred to Figure 3F The relevant description is not repeated here.

[0152] In one possible implementation, reference Figure 3B , the above step 203 specifically includes the following steps:

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

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

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

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

[0157] 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.

[0158] refer to Figure 3B In the embodiment of the present application, the application is deployed only on the first display screen, and the voice assistant only interacts with the application 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.

[0159] Implementation method three:

[0160] In a possible implementation, the above step 202 specifically includes the following steps:

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

[0162] 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 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 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.

[0163] 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 Fig. 3I , Fig. 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 as follows Fig. 3I As shown, the candidate files in the aggregation page include Zhan X5, Wanli Ztu, Zhan X, Liulang Yqiu, 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 at the lower left corner of the candidate file, such as B station, Youku, etc.

[0164] Exemplarily, when the candidate file is a video file, refer to Fig. 3I Only the 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.

[0165] Exemplarily, 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.

[0166] 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.

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

[0168] S1. The 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.

[0169] Specifically, a candidate file is obtained from a local application of the first device. In the embodiment of the present application, the obtained candidate file may be the candidate file itself or information that may 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 may be understood as obtaining the playback address of the video file. When the candidate file is a music file, obtaining the candidate file may be understood as obtaining the playback address corresponding to the music file.

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

[0171] For example, reference Figure 3C , the voice assistant of the first device sends a first request to the cross-screen transfer module of the headless system user, and the cross-screen transfer module obtains the candidate file according to the first request and the application status of the first device. Specifically, the application type indicated by the first request is first determined, and then the interface interaction is performed with the first application corresponding to the application type to obtain the candidate file in the first application.

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

[0173] 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.

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

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

[0176] 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.

[0177] For example, refer to Figure 3C , the first device sends a first request to the voice cloud server through the voice assistant, and the voice cloud server obtains resources, namely, candidate files, from the second device according to the first request. When the candidate file is a video file, the specific form of the candidate file can be the playback address of the video. The video file has a large amount of data, and transmitting the playback address can effectively reduce the amount of transmitted data and improve the response speed of cross-screen control.

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

[0179] 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 to generate an aggregate page, which provides another possible method for generating an aggregate page.

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

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

[0182] 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.

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

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

[0185] 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. Figure 3C After obtaining at least one first candidate file, the voice assistant of the first device 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, so that the cross-screen transfer module can aggregate the first candidate file and the second candidate file to generate an aggregate page.

[0186] 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.

[0187] 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.

[0188] In a possible implementation manner, the above-mentioned interaction with the aggregated page on the first display screen to determine the target file specifically includes the following steps:

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

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

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

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

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

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

[0195] 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 to output 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.

[0196] 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.

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

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

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

[0200] In the embodiment of the present application, 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. The specific description of step 203 can be referred to Figure 3F The relevant description is not repeated here.

[0201] In one possible implementation, reference Figure 3C , the above step 203 specifically includes the following steps:

[0202] The first device controls the first application to output the target file ( Figure 3C not shown).

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

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

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

[0206] In an embodiment of the present application, when the first application is configured on the first display screen, after the target file is determined, 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.

[0207] refer to Figure 3C In this embodiment, the voice assistant only interacts with the aggregate page of the first display screen, and displays the effect on other screens by moving the screen.

[0208] The method of the embodiment of the present application is described in detail above, and the device provided by the embodiment of the present application is introduced below.

[0209] 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.

[0210] Figure 4 A schematic diagram of a possible device structure provided in an embodiment of the present application. Figure 4 The first device shown 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 a module (such as a chip) applied to an electronic device.

[0211] like Figure 4 As shown, 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 above Figure 2 Alternatively, the first device 400 may include a device for implementing the above Figure 2 A module for any function or operation in the cross-screen control method embodiment shown in the figure may be implemented in whole or in part by software, hardware, firmware or any combination thereof.

[0212] 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.

[0213] When the first device 400 is used to implement Figure 2When performing the functions in the method embodiment shown, an acquisition module 401 is used to acquire a first request sent to a first user space. The above-mentioned first request is used to request to perform a first task through a second display screen. A determination module 402 is used to use the first display screen to determine a target file corresponding to the first task. An output module 403 is used to control the second display screen to output a target file through a 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.

[0214] 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. There is no need to deploy the application on each display screen of the first device, and the implementation solution is simple.

[0215] In a possible implementation, the determination module 402 is specifically used to: move the content interface of the first application to the first display screen for display by the headless system user. The first application is configured in the second user space, and the content interface corresponds to the first request. Determine the target file based on the content interface.

[0216] In a possible implementation, the determination module 402 is specifically configured to: determine 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 a first request. Determine a target file based on the content interface.

[0217] In a possible implementation, the determination module 402 is specifically used to determine the target file based on the content interface: 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.

[0218] In a possible implementation, the determination module 402 is specifically configured to interact with the aggregation page on the first display screen to determine the target file. The aggregation page displays at least one candidate file, and the candidate file corresponds to the first request.

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

[0220] 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.

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

[0222] In a possible implementation, the determination module 402 interacts with the aggregate page on the first display screen to determine the target file, specifically for: obtaining call stack information of the aggregate page. Obtaining control information of the aggregate page based on the call stack information. Determining the target file based on the control information and at least one control operation command.

[0223] In a possible implementation, the output module 403 is specifically used 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.

[0224] 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.

[0225] In a possible implementation, the output module 403 is specifically used 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.

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

[0227] refer to Figure 5 , Figure 5 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 connected to each other through the bus 503.

[0228] 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, and the display screen is 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), the output module is 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.

[0229] 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 a program. 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 execute the various steps of the cross-screen control method of any embodiment of the present application.

[0230] 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.

[0231] The processor 502 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the cross-screen control method of any embodiment of the present application may be completed by an integrated logic circuit of hardware or software instructions in the processor 502. The above-mentioned processor 502 may also be a general-purpose processor, a digital signal processor (Digital Signal Processing, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also 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 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, etc. 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.

[0232] 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, the candidate file can be obtained through the communication interface 504.

[0233] The bus 503 may include a path for transmitting information between various components of the first device 500 (e.g., the memory 501, the processor 502, and the communication interface 504). In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may 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.

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

[0235] 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.

[0236] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, 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 site, 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 to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available medium can be a read-only memory (ROM), or a random access memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a tape, a disk, or an optical medium, such as a digital versatile disc (DVD), or a semiconductor medium, such as a solid state drive (SSD), etc.

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

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 the second display screen for display.

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