Device management method, electronic device, server, and readable storage medium

Abstract

The application discloses a device management method, an electronic device, a server and a readable storage medium, and belongs to the technical field of electronic devices. The method is applied to a first device and comprises the following steps: in the case that a first connection condition is met by the first device and a second device, the first device and the second device establish a connection, and a device interaction interface corresponding to the second device is displayed in the first device; wherein the first connection condition comprises that the first device and the second device are in the same local area network, the Bluetooth of the first device and the Bluetooth of the second device are both in an open state, and the screen of the first device and the screen of the second device are both in an unlocked and bright screen state.

Description

Technical Field

[0001] This application belongs to the field of electronic equipment technology, specifically relating to a device management method, electronic equipment, server, and readable storage medium. Background Technology

[0002] With the rapid development of technology, users typically own multiple electronic devices that may run different operating systems, such as iOS and Android. Data sharing, file transfer, and collaborative work between these electronic devices have become an important part of modern digital life.

[0003] Currently, the main ways to connect electronic devices operating systems for data sharing, file transfer, and collaborative work include: providing a data transfer channel for file sharing over a network through cloud storage services (such as Google Drive, OneDrive, iCloud, etc.); connecting devices to personal computers via data cables; and establishing file transfer connections between different platforms through third-party file transfer applications. However, the connection operations in these methods are relatively cumbersome and require a significant amount of time and effort from users. Summary of the Invention

[0004] The purpose of this application is to provide a device management method, electronic device, server, and readable storage medium that can solve the problem of cumbersome connection operations between existing electronic devices.

[0005] In a first aspect, embodiments of this application provide a device management method applied to a first device, the method comprising:

[0006] When the first device and the second device meet the first connection conditions, the first device establishes a connection with the second device, and displays the device interaction interface corresponding to the second device on the first device;

[0007] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0008] Secondly, embodiments of this application provide a cross-device management method applied to a server, the method comprising:

[0009] Identify the second account that matches the first account on the first device;

[0010] The device status information of the second device is determined based on the second account;

[0011] Send the device status information of the second device to the first device; wherein, the device status information is used to determine whether the first device and the second device meet the first connection condition;

[0012] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0013] Thirdly, embodiments of this application provide a device management method applied to a second device, the method comprising:

[0014] When the first device and the second device meet the first connection conditions, the second device establishes a connection with the first device; wherein, the first connection conditions include: the first device and the second device are on the same local area network, both the Bluetooth of the first device and the Bluetooth of the second device are turned on, and both the screens of the first device and the screens of the second device are unlocked and on.

[0015] Fourthly, embodiments of this application provide a device management apparatus applied to a first device, the apparatus comprising:

[0016] The first processing module is configured to establish a connection between the first device and the second device when the first device and the second device meet the first connection conditions, and to display the device interaction interface corresponding to the second device on the first device.

[0017] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0018] Fifthly, embodiments of this application provide a device management apparatus applied to a server, the apparatus comprising:

[0019] The second determining module is used to determine a second account that matches the first account of the first device;

[0020] The third determining module is used to determine the device status information of the second device based on the second account;

[0021] A first sending module is configured to send device status information of the second device to the first device; wherein the device status information is used to determine whether the first device and the second device meet the first connection condition;

[0022] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0023] Sixthly, embodiments of this application provide a device management apparatus applied to a second device, the apparatus comprising:

[0024] The fourth processing module is used to establish a connection between the second device and the first device when the first device and the second device meet the first connection conditions; wherein the first connection conditions include: the first device and the second device are on the same local area network, the Bluetooth of the first device and the Bluetooth of the second device are both turned on, and the screens of the first device and the second device are both unlocked and on.

[0025] In a seventh aspect, embodiments of this application provide an electronic device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0026] Eighthly, embodiments of this application provide a server including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0027] A ninth aspect is an electronic device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect. A tenth aspect is a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the method as described in the first, second, or third aspect.

[0028] In a tenth aspect, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the methods described in the first, second, or third aspects.

[0029] Eleventhly, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first, second, or third aspect.

[0030] In this embodiment, when the first device and the second device meet the first connection conditions, a connection is established between the first device and the second device, and the device interaction interface corresponding to the second device is displayed on the first device. The first connection conditions include: the first device and the second device are on the same local area network; both the Bluetooth of the first device and the Bluetooth of the second device are enabled; and both the screens of the first device and the screen of the second device are unlocked and on. Thus, when the first connection conditions are met, a seamless connection is achieved between the first device and the second device, eliminating the need for the user to switch between different applications, cloud services, or physical connection methods, thereby reducing the complexity of connection operations between electronic devices. Attached Figure Description

[0031] Figure 1 This is one of the flowcharts of the device management method provided in the embodiments of this application;

[0032] Figure 2 This is one of the schematic diagrams of the device interaction interface provided in the embodiments of this application;

[0033] Figure 3 This is a second schematic diagram of the device interaction interface provided in the embodiments of this application;

[0034] Figure 4 This is a schematic diagram showing the image recognition information provided in an embodiment of this application;

[0035] Figure 5 This is a schematic diagram of the screen area of ​​the second device displayed on the first device provided in the embodiments of this application;

[0036] Figure 6 This is one of the schematic diagrams of the display interface of the first device provided in the embodiments of this application;

[0037] Figure 7 This is a second schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0038] Figure 8 This is the third schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0039] Figure 9 This is the fourth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0040] Figure 10 This is the fifth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0041] Figure 11 This is the sixth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0042] Figure 12This is the seventh schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0043] Figure 13 This is the eighth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0044] Figure 14 This is the ninth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0045] Figure 15 This is the tenth schematic diagram of the display interface of the first device provided in the embodiments of this application;

[0046] Figure 16 This is eleventh of the schematic diagrams of the display interface of the first device provided in the embodiments of this application;

[0047] Figure 17 This is the second flowchart of the device management method provided in the embodiments of this application;

[0048] Figure 18 This is the third flowchart of the device management method provided in the embodiments of this application;

[0049] Figure 19 This is one of the structural block diagrams of the device management device provided in the embodiments of this application;

[0050] Figure 20 This is a second structural block diagram of the device management apparatus provided in the embodiments of this application;

[0051] Figure 21 This is the third structural block diagram of the device management device provided in the embodiments of this application:

[0052] Figure 22 This is one of the hardware structure diagrams of the first device provided in the embodiments of this application;

[0053] Figure 23 This is a second schematic diagram of the hardware structure of the first device provided in the embodiments of this application;

[0054] Figure 24 This is one of the hardware structure diagrams of the server provided in the embodiments of this application;

[0055] Figure 25 This is the second schematic diagram of the hardware structure of the server provided in the embodiments of this application;

[0056] Figure 26 This is one of the hardware structure diagrams of the second device provided in the embodiments of this application;

[0057] Figure 27 This is the second schematic diagram of the hardware structure of the second device provided in the embodiments of this application. Detailed Implementation

[0058] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0059] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0060] The device management method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0061] It should be noted that the device management method provided in this application can be executed by electronic devices such as mobile phones, tablets, laptops, PDAs, and in-vehicle electronic devices. Some embodiments of this application use electronic devices as the executing entity to illustrate the device management method provided in this application.

[0062] See Figure 1 This application provides a device management method applied to a first device, the method comprising:

[0063] Step 101: If the first device and the second device meet the first connection conditions, the first device and the second device establish a connection, and the device interaction interface corresponding to the second device is displayed on the first device;

[0064] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0065] In some exemplary application scenarios, when the first device and the second device meet the first connection conditions, the first device and the second device actively trigger a connection process and establish a communication connection between them. This allows users to achieve seamless connection without having to perform complex connection operations. Moreover, by displaying the device interface corresponding to the second device on the first device, users can manage the second device based on the device interface, improving device management efficiency.

[0066] The device interface corresponding to the second device displayed on the first device can be regarded as the control center of the second device. The device management functions that the device interface can realize include, but are not limited to, multi-dimensional management functions such as connection status management between the first device and the second device, data sharing management, data transmission management, and collaborative work management.

[0067] For example, users on the first device side can learn about the connection status and connection quality of the second device through the device's corresponding interface.

[0068] For example, a user on the first device can share or transfer files with the second device through the device's interface.

[0069] For example, a user on the first device can coordinate and edit files and synchronize information with the second device through the device's interface.

[0070] In some embodiments of this application, the first account of the first device is matched with the second account of the second device. The first account can be a device login account or an application login account, and the second account can be a device login account or an application login account.

[0071] In the above embodiments, users can achieve a seamless connection between the first device and the second device without switching between different applications, cloud services, or physical connection methods, provided the first connection condition is met. This reduces the complexity of connection operations between electronic devices with different operating systems. Furthermore, by displaying the second device's interface on the first device, the second device can be managed through the first device, lowering the barrier to cross-device management.

[0072] Optionally, the first device can be an iOS device or an OS device; the iOS device interface can be in the Office Suite application, while the OS device interface can be a standalone device management application or in the Office Suite application.

[0073] In practice, the first device has an office suite application installed. After the user opens the office suite application, the device's interactive interface will be triggered based on the input operations of the function entry points provided by the application.

[0074] In some embodiments of this application, the first device and the second device belong to different operating systems; the first account of the first device is matched with the second account of the second device; the first account of the first device is a device login account, and the second account of the second device is an application login account; or, the first account of the first device is an application login account, and the second account of the second device is a device login account.

[0075] In this context, the first account and the second account are a unified identity created by the same user on a specific service provider or application platform, used for authentication and access to its various services and resources. Matching the first account on one device with the second account on another device indicates a connection between the two accounts. For example, the first account is created or verified based on the first account; although the two accounts may exist independently, their identity originates from the same user account. Alternatively, the first and second accounts may be associated with the same user information, such as the same phone number or email address.

[0076] In this embodiment, if the first account on the first device matches the second account on the second device, and if the first device and the second device meet the aforementioned first connection condition, then the first device and the second device establish a connection, and the device interaction interface corresponding to the second device is displayed on the first device. In this way, a seamless connection can be achieved between two devices with matching accounts when the first connection condition is met.

[0077] In some embodiments of this application, the first account of the first device is matched with the second account of the second device; the above device management method further includes:

[0078] The first device receives device status information of the second device sent by the server; wherein, the device status information includes: network connection information of the second device, Bluetooth status information of the second device, and screen status information of the second device; the server determines a second account that matches the first account of the first device, and determines the device status information of the second device based on the second account;

[0079] The first device determines whether the first device and the second device meet the first connection condition based on the device status information of the second device.

[0080] In practice, the server can obtain device status information of each device under a matching user account. The device status information includes, but is not limited to, Bluetooth connection status, WLAN connection status, screen unlock status, network environment status, etc. When the server determines that the first account of the first device matches the second account of the second device based on the device status information, and the first device and the second device meet the first connection conditions, the server sends a connection command to the first device and the second device. The first device and the second device establish a connection according to the connection command.

[0081] Optionally, when a device fails to meet the necessary conditions, the device conditions can be read through the server, and the details of the reasons for the connection failure and the corresponding guidance can be displayed in the first device.

[0082] In some embodiments of this application, when the first device and the second device meet the first connection condition, establishing a connection between the first device and the second device includes:

[0083] If the first device and the second device meet the first connection conditions, the first device establishes a connection with the second device through a local area network;

[0084] The above-mentioned equipment management methods also include:

[0085] The first device maintains a connection with the second device by transmitting heartbeat information via Bluetooth.

[0086] In some application scenarios, due to the limitation of the iOS operating system automatically freezing applications in the background, in order to ensure the connection and communication channel between devices, Bluetooth connection can be selected adaptively and heartbeats can be sent to keep the iOS device system active in the background, so as to ensure the activation and connection status between devices.

[0087] For example, the first device and the second device establish a connection via Bluetooth or Wi-Fi.

[0088] It's important to note that within the same local area network, the connection and communication between two electronic devices (such as a mobile phone connecting to a computer, or a smart home device connecting to a controller) primarily relies on the Transmission Control Protocol (TCP) / IP / Internet Protocol (IP) protocol suite. This process can be understood as "two people in the same room wanting to chat," requiring the following stages: verifying identities, calling each other (discovery / handshake), and initiating dialogue (data transmission).

[0089] The principle by which the first device establishes a connection with the second device via a local area network includes:

[0090] 1) In a local area network (LAN), the router acts as the "administrator." When device A and device B connect to Wi-Fi or are connected to the network cable, the router assigns them unique IP addresses within the LAN via the DHCP protocol (e.g., device A is '192.168.1.100', and device B is '192.168.1.105'). Through the subnet mask (usually '255.255.255.0'), the devices know that as long as the first three segments of the other device's IP address are the same as their own, they are in the same "room" (i.e., the LAN) and can communicate directly without needing to go through the external network.

[0091] 2) Although devices know each other's IP addresses, the physical address (Media Access Control Address, MAC address) is required for data transmission at the local area network (LAN) level. For example, device A wants to send data to device B. It knows B's IP address but not B's network card physical address. In this case, device A sends an ARP broadcast: "Who is '192.168.1.105'? Please tell me your MAC address." All devices on the LAN can hear this, but only device B will respond: "I am '192.168.1.105', and my MAC address is 'xx:xx:xx:xx:xx:xx'." Device A stores this mapping in its cache (ARP Cache), and subsequent communications will directly encapsulate data packets using the MAC address.

[0092] In specific implementations, depending on the application scenario, two implementation examples of establishing a connection between the first and second devices via a local area network include:

[0093] Example of implementation: Device B starts listening on a specific port (e.g., 8080), like waiting for mail at a specific window. Device A knows Device B's IP address and port, and actively sends a SYN packet to request a connection.

[0094] Through a three-way handshake, the two parties establish a reliable virtual channel and can begin bidirectional data transmission.

[0095] Example 2 of implementation: When the IP address of the other party is unknown, a connection can be established using multicast or broadcast. Specifically, this can include the following steps:

[0096] Step 1: Device A sends a broadcast packet to all devices on the local area network: "There is a printer service here, who needs to connect?"

[0097] Step 2, or device A queries a specific service discovery protocol (such as mDNS / Bonjour or UPnP / SSDP).

[0098] Step 3: After receiving the broadcast, if device B needs the service, it will parse the information in the packet, obtain the IP address and port of device A, and then initiate a TCP connection.

[0099] In some embodiments of this application, the above-described device management method further includes:

[0100] Obtain the device connection information of the second device through image recognition information;

[0101] Based on the device connection information of the second device, the first device establishes a connection with the second device, and displays the device interaction interface corresponding to the second device on the first device.

[0102] Optionally, the image recognition information is used to provide the second device with device connection information for establishing a communication connection with the first device, so that the second device can establish a communication connection with the first device by scanning the image recognition information.

[0103] In this embodiment, the first device can quickly establish a temporary near-field communication connection with the first device based on the image recognition information, even if the second device has not logged into a matching user account, and display the device interaction interface corresponding to the second device. This not only reduces the complexity of user operation, but also expands the scope of application of cross-device management.

[0104] For example, when the first and second devices are on the same local area network, the second device, running an Android operating system, can establish a near-field connection by scanning a QR code provided by the first device, running an iOS operating system. Figure 4 The image shows a device connectivity prompt card, which displays a QR code generated by the iOS device and operation prompts, such as... Figure 4 The instructions are: "1. Connect the Android device and iOS device to the same WLAN network 'XXX'. 2. On the Android device's home screen, swipe down to bring up the 'Global Search', tap the scan icon in the upper right corner, and scan the QR code." It should be noted that... Figure 4 This is merely an example and is not intended to limit the scope of the application. In specific implementations, examples of methods for the first device to generate image recognition information may include:

[0105] Step 1: The first device generates a string containing all the necessary information internally, and then converts it into a QR code.

[0106] QR codes typically contain the following core information (example in JSON format):

[0107] json

[0108] {

[0109] "ip": "192.168.1.105", / / The IP address of the iOS device within the local network

[0110] "port": 5000, / / The port that the iOS device app is listening on.

[0111] "id": "device_12345", / / Unique device identifier

[0112] "token": "9x8y7z", / / Temporary session key (Token)

[0113] "protocol": "tcp_udp" / / Communication protocol type

[0114] }".

[0115] Step 2: After scanning the QR code, the Android device uses its camera to recognize and decode the information. The Android device obtains the IP address and port of the first device. The token in the QR code (e.g., "9x8y7z") is usually a short-lived random number. For example, the Android device uses this token to initiate a TCP connection request to the first device: "I am the scanner, my password is 9x8y7z." The first device checks if this token matches the one it generated.

[0116] Step 3: If they match, the token verification is successful, and both parties have confirmed their identities. At this point, according to the strategy agreed upon in the QR code, one of the following two connection methods can be selected:

[0117] Method 1: TCP three-way handshake to achieve direct connection in standard local area networks.

[0118] In this method 1, the existing router's Wi-Fi bandwidth is utilized, resulting in fast speeds, and the two devices do not need to be particularly close, as long as they are on the same Wi-Fi network.

[0119] Method 2: After receiving the verification, the iOS device tells the Android device through the previously established TCP channel: "Disconnect from the router and connect to a hotspot named iOS device_Share_123 with the password 'abcde'." The Android device automatically switches its Wi-Fi connection to the hotspot signal emitted by the first device. At this point, the two devices bypass the router and communicate directly point-to-point via the Wi-Fi chip, which is typically faster and has extremely low latency than going through a router.

[0120] In some embodiments of this application, when the first device and the second device meet the first connection condition, establishing a connection between the first device and the second device includes:

[0121] A connection is established with the second device when the first device and the second device meet the first connection conditions and a device connection trigger operation is detected.

[0122] Optionally, the connection triggering operation includes, but is not limited to:

[0123] The office suite in the first device is activated;

[0124] The office suite in the first device switches from running in the background to running in the foreground;

[0125] The application function pages in the office suite on the first device switch.

[0126] The application homepage of the office suite in the first device runs in the foreground.

[0127] For example, if both the first and second devices have Bluetooth enabled, are connected to the same local area network, and are both in an unlocked, on-screen state, the first device will initiate an automatic connection with the second device if it is currently displaying the homepage of the office suite application. If the office suite application is running in the background, or the first device is displaying other application content, then this automatic connection process will not be initiated. This ensures that the automatic connection is relevant to the user's current operating context.

[0128] In practice, once the office suite's homepage is in the foreground, the first device immediately begins a periodic scan / check. For example, it automatically performs a "polling" every minute. In each poll, the first device checks its list of known or discoverable "second devices" (e.g., previously connected mobile phones); obtains the current device status of these devices; and in each poll, if the first device detects a second device that meets the connection criteria, it will proactively initiate an automatic connection, without requiring the user to manually click the connection button.

[0129] In some embodiments of this application, when the first device and the second device meet the first connection condition, the device interaction interface corresponding to the second device is displayed on the first device, including:

[0130] When the first device and the second device meet the first connection conditions, the device identifier corresponding to the second device is displayed on the device management interface of the first device.

[0131] Receive the user's first input;

[0132] In response to the first input, the device interaction interface corresponding to the second device is displayed in the device management interface.

[0133] For example, Figure 2 The device interface is displayed in card format, and includes identification information for multiple secondary devices, such as... Figure 2 The “X90”, “X100”, and “X110” in the text are the identification information of three different second devices, used to distinguish between different second devices; Figure 2 The "File Management" icon in the middle corresponds to the file management function entry point, which is used to trigger the display of the file directory of the second device.

[0134] Optionally, the first input can be a first operation. Exemplarily, the first input includes, but is not limited to: touch input by the user to the device identifier corresponding to the second device, or a voice command input by the user, or a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not impose limitations. The specific gesture in this application embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this application embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the first input mentioned above can be: a click input by the user to the device identifier corresponding to the second device.

[0135] For example, suppose Figure 2 If “X90” and “X100” are in a near-field communication connection state with the first device, and “X110” is in a disconnected communication connection state with the first device, then the first input is the user’s click operation on the device identifier corresponding to “X90” or “X100”.

[0136] In some embodiments of this application, the above-described device management method further includes:

[0137] Upon receiving a call request from a second device, the call request is displayed on the call request interface.

[0138] Receive the second input for the call request;

[0139] In response to the second input, a request for transmission of audio and video calls is sent to the second device;

[0140] Upon receiving the call audio and video data sent by the second device in response to the call audio and video transmission request, the call audio and video data is output.

[0141] Optionally, the second input can be a second operation. Exemplarily, the second input includes, but is not limited to: touch input from the user regarding a call request, a voice command input by the user, a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not impose limitations. The specific gesture in this embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the second input described above can be: a click input from the user regarding a call request acceptance control.

[0142] In this application embodiment, the call continuation can be a VoIP (Voice over Internet Protocol), audio stream, or video stream forwarding process.

[0143] In some exemplary scenarios, the first device is an iOS tablet and the second device is an Android phone. When the Android phone and tablet are already connected, and the Android phone receives a call, the tablet displays a pop-up window indicating a call request. After the user answers the call based on a second input on the tablet, the tablet sends a request to the Android phone to transmit the audio and video data. The tablet receives the audio and video data from the Android phone and plays it through its speaker / microphone. This enables cross-device call continuation.

[0144] Optionally, call status capture can be achieved by using "TelephonyManager" to monitor the call status of the Android phone (such as idle, ringing, or off-hook). When the call status changes to "ringing," the incoming call number is retrieved, and the caller's name is matched using "CallLog" or the address book.

[0145] For example, such as Figure 13 In this setup, the first device is a tablet computer, and the second device is an Android phone (such as "X90"). The user taps the "Answer" or "Hang Up" control on the call request notification bar displayed on the tablet computer. In response to the "Answer" operation, the tablet computer sends a command to the Android phone via a local area network socket, instructing the Android phone to "Answer the call and enable audio stream forwarding." Subsequently, in the uplink direction, the tablet computer activates its microphone to record audio and video data and transmits the call audio and video data to the Android phone via the network. In the downlink direction, the Android phone acquires the call audio and video data, compresses it, and transmits it to the tablet computer. The tablet computer receives the call audio and video data sent by the Android phone and plays it through its speaker.

[0146] For example, such as Figure 14In the process, when the user chooses to answer a call, the first device displays the answer status through a notification window and also displays a "hang up" control in the notification window, so that the user can manage the call status on the second device based on the first device.

[0147] In some embodiments of this application, the above-described device management method further includes at least one of the following:

[0148] Upon receiving a first image sent by a second device, a notification message corresponding to the first image is displayed in the notification bar area; the first image is a screenshot, a captured image, or an edited image.

[0149] Upon receiving copy-paste information or verification code information from a second device, add the copy-paste information or verification code information to the clipboard control.

[0150] For example, the first device is an iOS tablet, and the second device is an Android phone. With the Android phone and tablet already connected, if the user takes a screenshot or photo using the Android phone, the Android phone listens for changes in the system's "media database" or registers a "ContentObserver" in the background. When a screenshot or photo is added to the system's photo album, the Android phone immediately detects and reads the file. The Android phone then transmits the image data to the tablet; the tablet receives the image data and displays a notification in the notification bar corresponding to the screenshot. The user can then save or copy the image based on input in the notification message. This enables cross-device photo taking or screenshot taking task continuation.

[0151] For example, the first device is a tablet running iOS, and the second device is an Android phone. When the Android phone and tablet are connected, if the user copies a text message on the Android phone, the tablet's clipboard automatically syncs. If the Android phone receives a verification code via SMS, the tablet displays the verification code in a pop-up window. This enables cross-device text task continuation functionality.

[0152] Optionally, the Android phone's system can run a background service to periodically or via callbacks listen for changes in the clipboard content. Once new text is received, it immediately captures and copies the information. Similarly, the Android phone's system monitors SMS messages, identifying verification codes and extracting the code information. Correspondingly, the tablet utilizes the "UIPasteboard API" to directly write received text to the tablet's system clipboard. This allows users to paste text by long-pressing in any application on the tablet.

[0153] In the above embodiments, images captured, photos taken, copied text, and received verification codes on the second device can all be displayed in real time on the first device and processed directly on the first device. This improves the continuity and smoothness of the user's work in multi-device scenarios.

[0154] In some embodiments of this application, the device interface includes a screen mirroring function entry point corresponding to the second device; the above-mentioned device management method further includes:

[0155] Receive third-party input from the user regarding the screen mirroring function entry;

[0156] In response to a third input, a screen mirror of the second device is displayed on the first device.

[0157] For example, such as Figure 13 In the interface of the second device "X90", a "Screen Mirroring" control is displayed as the entry point for the screen mirroring function; after the user clicks the "Screen Mirroring" control, the screen will be displayed on the first device as shown below. Figure 5 A schematic diagram of the screen mirror interface of the second device "X90" shown.

[0158] Optionally, the third input can be a third operation. For example, the aforementioned third input includes, but is not limited to: user touch input to the screen mirroring function entry point, or a voice command input by the user, or a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not impose limitations. The specific gesture in this application embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this application embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the aforementioned third input can be: user click input to the screen mirroring function entry point.

[0159] In practice, after the first and second devices have established a connection, the screen mirroring function of the second device can be enabled and disabled through the screen mirroring function entry provided on the first device. When the screen mirroring function is enabled, screen content is captured on the second device, creating a screen capture session and acquiring screen frame data. By continuously capturing screen frames and converting them into a transmittable video stream format, the second device transmits the captured screen video stream data to the first device through the established Wi-Fi direct connection channel. During transmission, the TCP protocol is used to ensure data reliability and avoid packet loss that could cause stuttering or errors in the projected screen. Correspondingly, after receiving the video stream data transmitted by the second device, the first device uses a framework to decode and render it, displaying the decoded video frames on the first device's screen in real time according to the original screen size and resolution, thus achieving a mirrored display of the second device's screen content on the first device.

[0160] In addition, the first device also supports the following functions during the display screen mirroring process:

[0161] 1) Screen interaction function.

[0162] The video stream data of the second device displayed on the first device supports interactive operations such as gesture clicks, swipe interactions, and external mouse connections on the first device; it also supports responses to the virtual keyboard and external keyboard of the first device and injects this behavior into the Android device to achieve real-time task operation.

[0163] 2) Audio control function.

[0164] The first device can control the switching of the screen audio output device.

[0165] 3) Cross-screen drag-and-drop file transfer function.

[0166] Within the first device, you can use drag-and-drop gestures or an external mouse to select files or images from the file manager, image manager, etc. within the Android mirror screen and drag them to the first device for quick file transfer.

[0167] For example, the first device is a tablet running iOS, and the second device is an Android phone. With the Android phone and tablet already connected, upon receiving a third input from the user regarding the screen mirroring function, the iOS device sends a screen capture request to the Android phone in response to the third input. The Android phone then records the screen as a video stream and transmits it to the tablet for playback via the local area network. The user on the tablet can control the Android phone's interface using fingers, a mouse, and a keyboard, just like touching an Android phone. For example, they can drag files from the Android phone to the tablet's desktop, just like dragging files on a computer.

[0168] In this application example, Android provides a screenshot interface. After the application requests permission, the system starts a virtual "screen recorder." The application on the Android phone captures the image data of each frame and compresses it into an H.264 or H.265 video stream using the phone's hardware encoder. The video stream data is then segmented into packets, timestamped, and sent to the tablet via the local network. Correspondingly, the iOS device receives the video stream data, decodes it using iOS's hardware decoder, restores it to image data, and then directly draws it onto a UIView on the iOS device.

[0169] Optionally, the implementation logic for controlling the Android phone's interface via a tablet can be as follows: The tablet detects that the user's finger has clicked a specified location on the projection window. The iOS device sends a JSON command via Socket, such as: {"action":"click","x":100,"y":200}. After receiving the command, the Android phone uses AccessibilityService or InputManager to simulate a system-level click event.

[0170] In this embodiment, users can complete screen sharing within the device's interface on the second device. Users do not need to exit the current application or find another screen-sharing application, which simplifies the user's operation path and improves the user's operating efficiency.

[0171] In some embodiments of this application, after displaying a screen mirror interface of the second device on the first device, the above-described device management method further includes:

[0172] Receive the user's fourth input on the first file in the screen mirror interface;

[0173] In response to the fourth input, the first file is displayed using the application of the first device.

[0174] In practice, users on the first device can open files directly by calling local applications on the first device through the file manager, image manager, etc., within the mirrored screen of the second device.

[0175] The fourth input can be a fourth operation. For example, the fourth input includes, but is not limited to: touch input by the user to the icon or name of the first file, or a voice command input by the user, or a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not limit it. The specific gesture in this embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the fourth input mentioned above can be: a click input by the user to the icon or name of the first file.

[0176] It should be noted that traditional screen mirroring is only a one-way display; users only see an image stream on the screen mirrored interface and cannot directly interact with the mirrored content. However, in this embodiment, the user can directly click or select a file icon on the mirrored screen of the second device (e.g., a mobile phone) from the first device (e.g., a tablet). This eliminates the need for the user to search and operate on the second device; the first device can directly display the file from the second device, improving interactivity and operational efficiency.

[0177] In some embodiments of this application, displaying a screen mirror interface of the second device on the first device includes at least one of the following:

[0178] When the second device is in privacy protection mode, update the screen mirror interface to protect the privacy information of the second device.

[0179] For example, when the second device is in a privacy-protected state, the notification messages included in the screen area are hidden; or, the screen area is displayed as a black screen.

[0180] For example, an internal privacy mode can be enabled during screen mirroring. When privacy mode is enabled, floating notifications, incoming calls, notification bars, and other private content will not be displayed in the screen mirror interface on the first device. If a mobile device receives a call in full screen, is in a call interface, or enters a password or account input page during screen mirroring, the screen mirror interface will be blacked out.

[0181] It should be noted that the device management method provided in this application can be applied to scenarios where files need to be transferred between devices with different operating systems. For example, user A owns multiple electronic devices with different operating systems, including: a tablet with iOS operating system, a mobile phone 1 with Android operating system, and a mobile phone 2 with Android operating system. User A frequently needs to transfer photos, documents, videos, and other files between these devices. Traditionally, photos on the Android phone 1 need to be uploaded to a cloud server and then downloaded from the cloud server using the tablet, or the Android phone 2 needs to be connected to a computer and then copied from the computer to the tablet. This requires switching between different devices, which is cumbersome, time-consuming, and inefficient. Based on this, this application provides a device management method that simplifies the user's operation process and improves the efficiency of cross-device file management by providing a centralized device interaction interface on the tablet.

[0182] In some embodiments of this application, the device interface further includes a file import function entry; the above-mentioned device management method also includes:

[0183] Receive a fifth input from the user, which is used to select a first file in the first device;

[0184] Receives the user's sixth input for the file import function entry;

[0185] In response to the sixth input, the first file is transferred to the second device.

[0186] For example, such as Figure 15 In the process, when the user clicks the "Import File" button, they can enter the file selection process on the first device. After the user selects the file and completes the operation, the first file on the first device can be transferred to the second device.

[0187] In some embodiments of this application, the device interface includes a file directory and a file export function entry for the second device; the above-mentioned device management method further includes:

[0188] Receive the user's seventh input regarding the file directory, which is used to select the second file in the second device;

[0189] Receive the user's eighth input for the file export function entry;

[0190] In response to the eighth input, the second file is downloaded and saved to the first device.

[0191] For example, such as Figure 15In this system, once the first device (tablet computer) and the second device (X90) establish a connection, a device interface is built within the first device's system. Using the system file management API, a list of files stored on the device is retrieved. The device interface displays the folder hierarchy in a tree structure, allowing users to expand or collapse folders and select single or multiple files. For example... Figure 15 The file directory shown may include folder categories including, but not limited to: Recent, Pictures, Videos, Audio, Documents, Instant Messaging Application 1, Instant Messaging Application 2, Phone Storage, etc.

[0192] For example, such as Figure 16 In the process, after the user selects multiple video files based on the file directory corresponding to the second device, clicking the "Export Files" button will transfer the video files from the second device to the first device for storage.

[0193] It should be noted that during file transfer, the transfer progress bar, estimated remaining time, and number of bytes transferred are displayed in real time on both devices' interfaces. Optionally, breakpoint resume technology can be used, so if the transfer is unexpectedly interrupted, it can resume from the point of interruption after the network is restored, avoiding the time wasted due to repeated transfers.

[0194] In addition, the file manager built on the first device supports operations on local files on the second device, including functions such as selecting other opening methods, renaming, deleting, and fast transfer, and the operations are returned to the second device in real time.

[0195] In some exemplary application scenarios, suppose a user has the following three devices: the first device is an iOS tablet, and the two second devices are an Android phone 1 and an Android phone 2. The user took a set of photos with phone 1 and a video with phone 2, and wants to quickly transfer these photos and video to the tablet for editing. Then, with a near-field communication connection established between the first and second devices, a device management interface is displayed on the tablet. This interface displays the identification information of phone 1 and phone 2 and provides file management access points for both phones. In response to the user's input to the file management access point on phone 1, the internal file directory structure of phone 1 is displayed. The user can browse the files on phone 1 through the file directory structure displayed on the tablet to copy or export files to their local machine. Similarly, in response to the user's input to the file management access point on phone 2, the internal file directory structure of phone 2 is displayed. The user can browse the files on phone 2 through the file directory structure displayed on the tablet to copy or export files to their local machine. Throughout the entire process, users do not need to switch between multiple applications or use physical connection cables. They can switch devices and manage files within a unified interface, which greatly reduces the barrier to entry and learning cost of cross-operating system file management.

[0196] In the above embodiments, displaying a centralized device interface on the first device greatly simplifies the user operation process and improves the efficiency of cross-device file management. Simultaneously, it enhances file management efficiency when handling interoperability between devices with different operating systems.

[0197] In some embodiments of this application, the above-described device management method further includes:

[0198] Receive the task continuation data packet sent by the second device;

[0199] Display the first notification window, which includes the task continuation function entry point;

[0200] Receive the ninth input to the task continuation function entry;

[0201] In response to the ninth input, display the data content extracted from the task continuation data packet.

[0202] The ninth input can be a ninth operation. For example, the ninth input includes, but is not limited to: touch input from the user to the task continuation function entry point, or a voice command input by the user, or a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not impose limitations. The specific gesture in this embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the ninth input mentioned above can be: a click input from the user to the task continuation function entry point.

[0203] In this embodiment, the first device displays a first notification window, allowing the user to clearly perceive that a task is available for continuation. The user can then selectively decide whether to continue the task based on the task continuation function entry. The task continuation function provided in this application embodiment, by displaying the data content extracted from the task continuation data packet, can improve the continuity and smoothness of the user's work in multi-device scenarios.

[0204] In some embodiments of this application, the above-mentioned task continuation data packet includes at least one of the following:

[0205] (1) The first data packet generated when the second device triggers the photo taking or screenshot operation.

[0206] In practice, when the second device triggers the photo taking and screenshot operation, the system of the second device obtains the image information to form a first data packet; after receiving the first data packet, the first device first parses the identification information in it, and displays the data content in the first data packet through the notification capability of the native system, and provides a function entry for task continuation.

[0207] For example, such as Figure 6 As shown, this is a schematic diagram of the first device displaying the first notification window, as follows: Figure 6 In the first notification window, the user is notified that an image relay has been received from "X90". When the user performs a first touch operation on the first notification window (such as a long press), the image information is displayed on the desktop, such as... Figure 7 As shown; when the user performs a second touch operation (such as a click) on the first notification window, the system redirects to the application interface of the office suite to display the image information, such as... Figure 8 As shown.

[0208] Optionally, quick save and copy buttons are provided so that users can choose to save the image information to the local device.

[0209] (2) The second data packet generated when the clipboard copy operation is triggered by the second device.

[0210] In practice, when a clipboard copy operation is triggered on the second device, the system of the second device obtains text and / or image information to form a second data packet. After receiving the second data packet, the first device first parses the identification information in it, and displays the data content in the second data packet through the notification capability of the native system, and provides a function entry point for task continuation.

[0211] (3) The third data packet generated when the second device receives the verification code.

[0212] In practice, when the second device receives an external SMS notification and it is identified as a verification code, the system of the second device obtains the numeric string to form a third data packet. After the first device receives the third data packet, it first parses the identification information in it, and displays the data content in the third data packet through the notification capability of the native system, and provides a function entry point for task continuation.

[0213] For example, such as Figure 9 As shown, this is a schematic diagram of the first device displaying the first notification window, as follows: Figure 9 In the first notification window, the user is notified that an SMS message has been received from "X90". When the user performs a first touch operation on the first notification window (such as a long press), a verification code is displayed on the desktop. Figure 10 As shown; when the user performs a second touch operation (such as a click) on the first notification window, the system redirects to the application interface of the office suite to display the verification code, such as... Figure 11 As shown.

[0214] Optionally, a button control for quickly saving and copying the verification code can be provided.

[0215] (4) The fourth data packet generated when the second device receives the incoming call notification.

[0216] In practice, when the second device receives an external call notification, the system of the second device obtains the audio information to form a fourth data packet; after the first device receives the fourth data packet, it first parses the identification information in it, and displays the data content in the fourth data packet through the notification capability of the native system, and provides a function entry point for task continuation.

[0217] For example, such as Figure 12 As shown, this is a schematic diagram of the first device displaying the first notification window, as follows: Figure 12 In the first notification window, the user is notified of an incoming call from "X90". When the user performs a touch operation (such as clicking) on ​​the first notification window, the following will be displayed: Figure 13The incoming call notification window is shown; when the user answers the call based on the incoming call notification window, the answering status window is displayed.

[0218] In practice, the native system notification of the first device displays an audio data packet. The core data includes, but is not limited to, at least one of the following: the specific contact person, the unknown number's caller ID, and the carrier. By clicking on the first notification window to expand this notification, it can be divided into call reminder status and answer status. In the call reminder status, answering and hanging up are supported; in the answer status, hanging up and muting are supported; when the user selects to answer, the call audio will be output to the player on the first device.

[0219] In some embodiments, when there are multiple second devices, the sorting rules for the second devices in the device interaction interfaces corresponding to the multiple second devices may include at least one of the following:

[0220] If there are already connected devices, they will be listed first.

[0221] If no devices are currently connected, the most recently connected device will be listed first and displayed with a "Recently Connected" label.

[0222] The remaining devices are arranged in reverse chronological order of their most recent activity time, meaning the more recent the activity time is, the earlier it appears in the list.

[0223] In some embodiments, when the first device and the second device are disconnected, a quick connection function entry is also displayed in the device interface corresponding to the second device; the above device management method further includes:

[0224] Receive the user's tenth input for the connection entry;

[0225] In response to the tenth input, it is determined whether the first device and the second device meet the connection conditions, and if the connection conditions are met, a connection is established between the first device and the second device.

[0226] The tenth input can be the tenth operation. For example, the tenth input includes, but is not limited to: user touch input to the quick connection entry, or a voice command input by the user, or a specific gesture input by the user, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not impose limitations. The specific gesture in this embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture; the click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input. For example, the tenth input can be: user click input to the quick connection entry.

[0227] For example, such as Figure 2 In the diagram, the second device displays a "Quick Connect" function entry. When the user clicks on the "Quick Connect" function entry, a connection condition check between the first and second devices ("X90") is initiated. If the connection conditions are met, a near-field communication connection is established between the first and second devices ("X90"). Figure 3 In the middle, each second device also has a corresponding "Disconnect" function entry. When the user clicks the function control corresponding to "Disconnect", the communication connection between the first device and "X90" will be disconnected.

[0228] Optionally, the connection conditions include: Bluetooth being enabled simultaneously; accessing the same local area network; maintaining a lit and unlocked screen; and an office suite installed on the first device being in operation, the office suite being used by the user to manage other devices connected to the first device and display the device management interface.

[0229] In this embodiment, users are allowed to actively initiate or terminate near-field communication connections between devices when needed, which supplements the shortcomings of automatic connection schemes and enables users to manage near-field communication connections between devices more efficiently according to actual needs.

[0230] See Figure 17 This application provides a device management method applied to a server. The device management method includes:

[0231] Step 201: Determine the second account that matches the first account on the first device;

[0232] In this context, the first account and the second account are created by the same user on a service provider or application platform, serving as a unified identity for authentication and access to its various services and resources. Matching the first account on one device with the second account on another device can mean that the first and second accounts are directly related. For example, the first account is created or verified based on the first account; although the two accounts may exist independently, their identity originates from the same user account. Alternatively, the first and second accounts may be associated with the same user information, such as the same mobile phone number or email address.

[0233] Step 202: Determine the device status information of the second device based on the second account;

[0234] The device status information includes: the network connection information of the second device, the Bluetooth status information of the second device, and the screen status information of the second device.

[0235] Step 203: Send the device status information of the second device to the first device; wherein, the device status information is used to determine whether the first device and the second device meet the first connection condition;

[0236] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0237] Optionally, in specific implementation, the server can obtain the device status information of each device under the matching user account. The device status information includes, but is not limited to, Bluetooth connection status, WLAN connection status, screen unlock status, network environment status, etc. When the server determines that the first account of the first device matches the second account of the second device based on the device status information, and the first device and the second device meet the first connection condition, the server sends the device status information of the second device to the first device.

[0238] Optionally, when a device fails to meet the necessary conditions, the device conditions can be read through the server, and the details of the reasons for the connection failure and the corresponding guidance can be displayed in the first device.

[0239] In this embodiment, when the server determines that the first account on the first device matches the second account on the second device, it determines the device status information of the second device based on the second account and sends the device status information of the second device to the first device. This facilitates the establishment of a connection between the first and second devices, and the corresponding device interface of the second device is displayed on the first device. In this way, a seamless connection can be achieved between two devices with matched accounts.

[0240] As some implementation methods, when the first device and the second device meet the first connection condition, the server sends the device status information of the second device to the first device; the first device determines whether the first device and the second device meet the first connection condition based on the device status information of the second device, and if the first connection condition is met, the first device initiates a communication connection with the second device.

[0241] In some other implementations, when the first device and the second device meet the first connection conditions, the server sends connection instructions to the first device and the second device respectively. The connection instructions are used to instruct the first device and the second device to establish a near-field communication connection.

[0242] See Figure 18 This application provides a device management method applied to a second device, the method comprising:

[0243] Step 301: If the first device and the second device meet the first connection conditions, the second device establishes a connection with the first device; wherein, the first connection conditions include: the first device and the second device are on the same local area network, the Bluetooth of the first device and the Bluetooth of the second device are both turned on, and the screens of the first device and the second device are both unlocked and on.

[0244] As one implementation, the second device receives a connection request initiated by the first device and establishes a connection with the first device.

[0245] In some other implementations, the second device receives a connection command sent by the server and establishes a near-field communication connection with the first device according to the connection command. The connection command instructs the first device to establish a communication connection with the second device, and is sent by the server after determining that the first and second devices meet the connection conditions.

[0246] In the above embodiments, a seamless connection between two devices can be achieved.

[0247] In some embodiments of this application, the above-described device management method further includes:

[0248] Upon detecting a call request, a call request is sent to the first device;

[0249] Upon receiving a call audio / video transmission request sent by the first device in response to a call request, call audio / video data is sent to the first device.

[0250] This embodiment corresponds to the solution on the first device side and can achieve the same technical effect. It can be referred to in the introduction of the first device side, and will not be repeated here.

[0251] In some embodiments of this application, the above-described device management method further includes:

[0252] Upon detecting the first image, a notification message corresponding to the first image is sent to the first device; the first image is a screenshot, a captured image, or an edited image.

[0253] If copy-paste information or verification code information is detected, the copy-paste information or verification code information is sent to the first device.

[0254] This embodiment corresponds to the solution on the first device side and can achieve the same technical effect. It can be referred to in the introduction of the first device side, and will not be repeated here.

[0255] In some embodiments of this application, the above method further includes:

[0256] Send a task continuation data packet to the first device;

[0257] The task continuation data packet includes at least one of the following:

[0258] The first data packet generated when the second device triggers a photo or screenshot operation;

[0259] The second data packet generated when the clipboard copy operation is triggered by the second device;

[0260] The third data packet generated when the second device receives the verification code;

[0261] The fourth data packet is generated when the second device receives an incoming call notification.

[0262] This embodiment corresponds to the solution on the first device side and can achieve the same technical effect. It can be referred to in the introduction of the first device side, and will not be repeated here.

[0263] The device management method provided in this application can be executed by a device management device. This application uses a file management device executing the device management method as an example to illustrate the device management device provided in this application.

[0264] See Figure 19 This application provides a device management apparatus for a first device. The apparatus 1900 includes:

[0265] The first processing module 1901 is used to establish a connection between the first device and the second device when the first device and the second device meet the first connection conditions, and to display the device interaction interface corresponding to the second device in the first device.

[0266] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0267] Optionally, the first device and the second device belong to different operating systems; the first account of the first device matches the second account of the second device; the first account of the first device is the device login account, and the second account of the second device is the application login account; or, the first account of the first device is the application login account, and the second account of the second device is the device login account.

[0268] Optionally, the first account of the first device is matched with the second account of the second device; device 1900 also includes:

[0269] The first receiving module is used to receive device status information of the second device sent by the server; wherein, the device status information includes: network connection information of the second device, Bluetooth status information of the second device, and screen status information of the second device; the server determines a second account that matches the first account of the first device, and determines the device status information of the second device based on the second account;

[0270] The first determining module is used to determine whether the first device and the second device meet the first connection condition based on the device status information of the second device.

[0271] Optionally, the first processing module 1901 is specifically used for:

[0272] If the first device and the second device meet the first connection conditions, a connection with the second device is established through the local area network;

[0273] Device 1900 also includes:

[0274] A connection-maintaining module is used to maintain the connection with a second device by transmitting heartbeat information via Bluetooth.

[0275] Optionally, the device 1900 also includes:

[0276] The first acquisition module is used to acquire device connection information of the second device through image recognition information;

[0277] The second processing module is used to establish a connection between the first device and the second device based on the device connection information of the second device, and to display the device interaction interface corresponding to the second device on the first device.

[0278] Optionally, the first processing module 1901 is specifically used for:

[0279] A connection is established with the second device when the first device and the second device meet the first connection conditions and a device connection trigger operation is detected.

[0280] Optionally, the first processing module 1901 is specifically used for:

[0281] When the first device and the second device meet the first connection conditions, the device identifier corresponding to the second device is displayed on the device management interface of the first device.

[0282] Receive the user's first input;

[0283] In response to the first input, the device interaction interface corresponding to the second device is displayed in the device management interface.

[0284] Optionally, the device 1900 also includes:

[0285] The first display module is used to display the call request on the call request interface when a call request is received from the second device.

[0286] The second receiving module is used to receive a second input for a call request;

[0287] The first response module is used to respond to the second input and send a call audio and video transmission request to the second device;

[0288] Upon receiving call audio and video data sent by the second device in response to the call audio and video transmission request, the call audio and video data is output.

[0289] Optionally, the device 1900 further includes at least one of the following:

[0290] The second display module is used to display notification information corresponding to the first image in the notification bar area when the first image sent by the second device is received; the first image is a screenshot, a captured image, or an edited image;

[0291] The third processing module is used to add the copy-paste information or verification code information to the clipboard control when it receives the copy-paste information or verification code information sent by the second device.

[0292] Optionally, the device interface includes an entry point for the screen mirroring function corresponding to the second device;

[0293] The device further includes:

[0294] The third receiving module is used to receive the user's third input for the screen mirroring function entry;

[0295] The second response module is used to respond to the third input and display the screen mirror interface of the second device on the first device.

[0296] Optionally, the device 1900 also includes:

[0297] The fourth receiving module is used to receive the user's fourth input on the first file in the screen mirror interface;

[0298] The third response module is used to respond to the fourth input and display the first file using the application of the first device.

[0299] Optionally, the second response module is specifically used for:

[0300] When the second device is in privacy protection mode, update the screen mirror interface to protect the privacy information of the second device.

[0301] The file management device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0302] The file management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0303] The file management device provided in this application embodiment can achieve... Figure 1 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0304] See Figure 20 This application provides a device management apparatus for use on a server. The apparatus 2000 includes:

[0305] The second determining module 2001 is used to determine a second account that matches the first account of the first device;

[0306] The third determination module 2002 is used to determine the device status information of the second device based on the second account;

[0307] The first sending module 2003 is used to send device status information of the second device to the first device; wherein, the device status information is used to determine whether the first device and the second device meet the first connection condition;

[0308] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0309] The file management device in this application embodiment can be an electronic device or a component of an electronic device, such as an integrated circuit or a chip. For example, the electronic device can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc., and this application embodiment does not specifically limit it.

[0310] The file management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0311] The file management device provided in this application embodiment can achieve... Figure 17 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0312] See Figure 21 This application provides a device management apparatus for a second device. The apparatus 2100 includes:

[0313] The fourth processing module 2101 is used to establish a connection between the second device and the first device when the first device and the second device meet the first connection conditions; wherein, the first connection conditions include: the first device and the second device are on the same local area network, the Bluetooth of the first device and the Bluetooth of the second device are both turned on, and the screens of the first device and the second device are both unlocked and on.

[0314] Optionally, the device 2100 further includes:

[0315] The second sending module is used to send the call request to the first device when a call request is detected;

[0316] The fifth receiving module is used to send call audio and video data to the first device when it receives a call audio and video transmission request sent by the first device in response to the call request.

[0317] Optionally, the device 2100 further includes:

[0318] The third sending module is used to send notification information corresponding to the first image to the first device when the first image is detected; the first image is a screenshot, a captured image, or an edited image;

[0319] The fourth sending module is used to send the copy-paste information or verification code information to the first device when copy-paste information or verification code information is detected.

[0320] The file management device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0321] The file management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0322] The file management device provided in this application embodiment can achieve... Figure 18 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0323] Optionally, such as Figure 22 As shown, this application embodiment also provides an electronic device 2200, which serves as a first device. The device includes a processor 2201 and a memory 2202. The memory 2202 stores a program or instructions that can run on the processor 2201. When the program or instructions are executed by the processor 2201, they implement the various steps of the above-described device management method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0324] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0325] Figure 23A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0326] The electronic device 2300, as the first device, includes, but is not limited to, the following components: radio frequency unit 2301, network module 2302, audio output unit 2303, input unit 2304, sensor 2305, display unit 2306, user input unit 2307, interface unit 2308, memory 2309, and processor 2310.

[0327] Those skilled in the art will understand that the electronic device 2300 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 310 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 23 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0328] The processor 2310 is used to establish a connection between the first device and the second device when the first device and the second device meet the first connection conditions, and to display the device interaction interface corresponding to the second device in the first device.

[0329] The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

[0330] Optionally, the first device and the second device belong to different operating systems; the first account of the first device matches the second account of the second device; the first account of the first device is the device login account, and the second account of the second device is the application login account; or, the first account of the first device is the application login account, and the second account of the second device is the device login account.

[0331] Optionally, the first account of the first device is matched with the second account of the second device; the radio frequency unit 2301 is used to receive the device status information of the second device sent by the server; wherein, the device status information includes: the network connection information of the second device, the Bluetooth status information of the second device, and the screen status information of the second device; the server determines the second account that matches the first account of the first device, and determines the device status information of the second device based on the second account;

[0332] The processor 2310 is used to determine whether the first device and the second device meet the first connection condition based on the device status information of the second device.

[0333] Optionally, the processor 2310 is specifically used to establish a connection with the second device via a local area network when the first device and the second device meet the first connection conditions;

[0334] The processor 2310 is also used to maintain a connection with a second device via heartbeat information transmitted via Bluetooth.

[0335] Optionally, the processor 2310 is further configured to obtain device connection information of the second device through image recognition information; based on the device connection information of the second device, the first device establishes a connection with the second device, and displays the device interaction interface corresponding to the second device in the first device.

[0336] Optionally, the processor 2310 is specifically configured to establish a connection with the second device when the first device and the second device meet the first connection condition and a device connection trigger operation is detected.

[0337] Optionally, the display unit 2306 is used to display the device identifier corresponding to the second device on the device management interface of the first device when the first device and the second device meet the first connection conditions;

[0338] User input unit 2307 is used to receive the user's first input;

[0339] The display unit 2306 is also used to respond to the first input by displaying the device interaction interface corresponding to the second device in the device management interface.

[0340] Optionally, the display unit 2306 is configured to display a call request on a call request interface upon receiving a call request sent by the second device;

[0341] User input unit 2307 is used to receive a second input for a call request;

[0342] The radio frequency unit 2301 is used to send a call audio / video transmission request to the second device in response to the second input;

[0343] The processor 2310 is configured to output the called audio and video data upon receiving call audio and video data sent by the second device in response to a call audio and video transmission request.

[0344] Optionally, the display unit 2306 includes at least one of the following:

[0345] Upon receiving a first image sent by a second device, a notification message corresponding to the first image is displayed in the notification bar area; the first image is a screenshot, a captured image, or an edited image.

[0346] Upon receiving copy-paste information or verification code information from a second device, add the copy-paste information or verification code information to the clipboard control.

[0347] Optionally, the device interface includes an entry point for the screen mirroring function corresponding to the second device;

[0348] User input unit 2307 is used to receive third input from the user for the screen mirroring function entry;

[0349] The display unit 2306 is also configured to display a screen mirror interface of the second device on the first device in response to the third input.

[0350] Optionally, the user input unit 2307 is used to receive a fourth input from the user on the first file in the screen mirror interface;

[0351] Display unit 2306 is configured to display a first file using an application program of the first device in response to a fourth input.

[0352] Optionally, the display unit 2306 is also configured to update the display screen mirror interface when the second device is in a privacy protection state, so as to protect the privacy information of the second device.

[0353] In the above embodiments, users can achieve a seamless connection between the first device and the second device without switching between different applications, cloud services, or physical connection methods, provided the first connection condition is met. This reduces the complexity of connection operations between electronic devices with different operating systems. Furthermore, by displaying the second device's interface on the first device, the second device can be managed through the first device, lowering the barrier to cross-device management.

[0354] It should be understood that, in this embodiment, the input unit 2304 may include a graphics processing unit (GPU) 23041 and a microphone 23042. The GPU 23041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 2306 may include a display panel 23061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 2307 includes at least one of a touch panel 23071 and other input devices 23072. The touch panel 23071 is also called a touch screen. The touch panel 23071 may include a touch detection device and a touch controller. Other input devices 23072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0355] The memory 2309 can be used to store software programs and various data. The memory 2309 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 2309 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 2309 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0356] Processor 2310 may include one or more processing units; optionally, processor 2310 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 2310.

[0357] Optionally, such as Figure 24As shown, this application embodiment also provides a server 2400, including a processor M01 and a memory 2402. The memory 2402 stores a program or instructions that can run on the processor 2401. When the program or instructions are executed by the processor 2401, they implement the various steps of the above-described device management method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0358] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0359] Figure 25 A schematic diagram of the hardware structure of a server to implement an embodiment of this application.

[0360] The server 2500 includes, but is not limited to, the following components: radio frequency unit 2501, network module 2502, audio output unit 2503, input unit 2504, sensor 2505, display unit 2506, user input unit 2507, interface unit 2508, memory 2509, and processor 2510.

[0361] Those skilled in the art will understand that the server 2500 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 2510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 25 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0362] The processor 2510 is configured to determine a second account that matches a first account on the first device; determine device status information of the second device based on the second account; and send the device status information of the second device to the first device. The device status information is used to determine whether the first device and the second device meet a first connection condition. The first connection condition includes: the first device and the second device are on the same local area network; both Bluetooth on the first device and Bluetooth on the second device are enabled; and both the screens of the first device and the second device are unlocked and on.

[0363] In this embodiment, when the server determines that the first account on the first device matches the second account on the second device, it determines the device status information of the second device based on the second account and sends the device status information of the second device to the first device. This facilitates the establishment of a connection between the first and second devices, and the corresponding device interface of the second device is displayed on the first device. In this way, a seamless connection can be achieved between two devices with matched accounts.

[0364] It should be understood that, in this embodiment, the input unit 2504 may include a graphics processing unit (GPU) 25041 and a microphone 25042. The GPU 25041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 2506 may include a display panel 25061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 2507 includes at least one of a touch panel 25071 and other input devices 25072. The touch panel 25071 is also called a touch screen. The touch panel 25071 may include a touch detection device and a touch controller. Other input devices 25072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0365] The memory 2509 can be used to store software programs and various data. The memory 2509 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 2509 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 2509 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0366] Processor 2510 may include one or more processing units; optionally, processor 2510 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 2510.

[0367] Optionally, such as Figure 26As shown, this application embodiment also provides an electronic device 2600, which serves as a second electronic device. The device includes a processor 2601 and a memory 2602. The memory 2602 stores a program or instructions that can run on the processor 2601. When the program or instructions are executed by the processor 2601, they implement the various steps of the above-described device management method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0368] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0369] Figure 27 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0370] The electronic device 2700 includes, but is not limited to, components such as: radio frequency unit 2701, network module 2702, audio output unit 2703, input unit 2704, sensor 2705, display unit 2706, user input unit 2707, interface unit 2708, memory 2709, and processor 2710.

[0371] Those skilled in the art will understand that the electronic device 2700 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 2710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 27 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0372] The processor 2710 is configured to establish a connection between the second device and the first device when the first device and the second device meet the first connection conditions; wherein the first connection conditions include: the first device and the second device are on the same local area network, both Bluetooth of the first device and Bluetooth of the second device are turned on, and both the screens of the first device and the second device are unlocked and on.

[0373] Optionally, the radio frequency unit 2701 is configured to send a call request to the first device when a call request is detected; and to send call audio and video data to the first device when a call audio and video transmission request is received from the first device in response to the call request.

[0374] Optionally, the radio frequency unit 2701 is used to send notification information corresponding to the first image to the first device when the first image is detected; the first image is a screenshot image, a captured image, or an edited image; and to send copy-paste information or verification code information to the first device when copy-paste information or verification code information is detected.

[0375] In the above embodiments, a seamless connection can be achieved between the first device and the second device.

[0376] It should be understood that, in this embodiment, the input unit 2704 may include a graphics processing unit (GPU) 27041 and a microphone 27042. The GPU 27041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 2706 may include a display panel 27061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 2707 includes at least one of a touch panel 27071 and other input devices 27072. The touch panel 27071 is also called a touch screen. The touch panel 27071 may include a touch detection device and a touch controller. Other input devices 27072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0377] The memory 2709 can be used to store software programs and various data. The memory 2709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 2709 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 2709 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0378] Processor 2710 may include one or more processing units; optionally, processor 2710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 2710.

[0379] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described device management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0380] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0381] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described device management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0382] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0383] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described device management method embodiments, and can achieve the same technical effects. To avoid repetition, it will not be described again here.

[0384] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0385] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0386] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for managing equipment, characterized in that, Applied to a first device, the method includes: When the first device and the second device meet the first connection conditions, the first device establishes a connection with the second device, and displays the device interaction interface corresponding to the second device on the first device; The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

2. The method according to claim 1, characterized in that, The first device and the second device belong to different operating systems; the first account of the first device matches the second account of the second device; the first account of the first device is the device login account, and the second account of the second device is the application login account; or, the first account of the first device is the application login account, and the second account of the second device is the device login account.

3. The method according to claim 1, characterized in that, The first account of the first device is matched with the second account of the second device; The method further includes: The server receives device status information of the second device sent by the server; wherein the device status information includes: network connection information of the second device, Bluetooth status information of the second device, and screen status information of the second device; the server determines a second account that matches the first account of the first device, and determines the device status information of the second device based on the second account; Based on the device status information of the second device, determine whether the first device and the second device meet the first connection condition.

4. The method according to claim 1, characterized in that, The step of establishing a connection between the first device and the second device when the first connection condition is met includes: If the first device and the second device meet the first connection conditions, a connection with the second device is established through the local area network; The method further includes: The connection with the second device is maintained by transmitting heartbeat information via Bluetooth.

5. The method according to claim 1, characterized in that, The method further includes: The device connection information of the second device is obtained through image recognition information; Based on the device connection information of the second device, the first device establishes a connection with the second device, and displays the device interaction interface corresponding to the second device on the first device.

6. The method according to claim 1, characterized in that, The step of establishing a connection between the first device and the second device when the first connection condition is met includes: When the first device and the second device meet the first connection condition and a device connection trigger operation is detected, a connection is established with the second device.

7. The method according to claim 1, characterized in that, When the first device and the second device meet the first connection condition, the device interaction interface corresponding to the second device is displayed on the first device, including: When the first device and the second device meet the first connection conditions, the device identifier corresponding to the second device is displayed on the device management interface of the first device; Receive the user's first input; In response to the first input, the device interaction interface corresponding to the second device is displayed in the device management interface.

8. The method according to claim 1, characterized in that, The method further includes: Upon receiving a call request from the second device, the call request is displayed on the call request interface; Receive a second input regarding the call request; In response to the second input, a call audio / video transmission request is sent to the second device; Upon receiving the call audio and video data sent by the second device in response to the call audio and video transmission request, the call audio and video data is output.

9. The method according to claim 1, characterized in that, The method further includes at least one of the following: Upon receiving a first image sent by the second device, a notification message corresponding to the first image is displayed in the notification bar area; the first image is a screenshot, a captured image, or an edited image. Upon receiving copy-paste information or verification code information sent by the second device, the copy-paste information or verification code information is added to the clipboard control.

10. The method according to claim 1, characterized in that, The device interface includes a screen mirroring function entry point for the second device. The method further includes: Receive a third input from the user regarding the screen mirroring function entry; In response to the third input, a screen mirror interface of the second device is displayed on the first device.

11. The method according to claim 10, characterized in that, After displaying the screen mirror interface of the second device on the first device, the method further includes: Receive the user's fourth input on the first file in the screen mirror interface; In response to the fourth input, the first file is displayed using the application of the first device.

12. The method according to claim 10, characterized in that, The step of displaying a screen mirror interface of the second device on the first device includes: When the second device is in a privacy protection state, the screen mirror interface is updated to protect the privacy information of the second device.

13. A method for managing equipment, characterized in that, Applied to a server, the method includes: Identify the second account that matches the first account on the first device; The device status information of the second device is determined based on the second account; Send the device status information of the second device to the first device; wherein, the device status information is used to determine whether the first device and the second device meet the first connection condition; The first connection conditions include: the first device and the second device are on the same local area network; the Bluetooth of both the first device and the second device is turned on; and the screens of both the first device and the second device are unlocked and on.

14. A method for managing equipment, characterized in that, Applied to a second device, the method includes: When the first device and the second device meet the first connection conditions, the second device establishes a connection with the first device; wherein, the first connection conditions include: the first device and the second device are on the same local area network, both the Bluetooth of the first device and the Bluetooth of the second device are turned on, and both the screens of the first device and the screens of the second device are unlocked and on.

15. The method according to claim 14, characterized in that, The method further includes: Upon detecting a call request, the call request is sent to the first device; Upon receiving a call audio / video transmission request sent by the first device in response to the call request, call audio / video data is sent to the first device.

16. The method according to claim 14, characterized in that, The method further includes: Upon detecting the first image, a notification message corresponding to the first image is sent to the first device; the first image is a screenshot, a captured image, or an edited image. If copy-paste information or verification code information is detected, the copy-paste information or verification code information is sent to the first device.

17. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1-12.

18. A server, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as claimed in claim 13.

19. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 14-16.

20. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 12, or the steps of the method as claimed in claim 13, or the steps of the method as claimed in any one of claims 14 to 16.

Images