Control method, sharing method, device and system

Abstract

This application provides a control method, sharing method, device, and system that improve the security of a first device while enabling Bluetooth device sharing. A first device establishes a pairing connection with a second device, and the second device and the first device exchange information with each other, enabling the second device to control the first device. Based on the second device's control of the first device, the second device shares the first device with a third device, further establishing a sharing connection between the first and third devices, enabling the third device to use or manage the first device.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a control method, sharing method, device and system in the field of communication technology. Background Art

[0002] With the rapid development of communications technology and artificial intelligence, Bluetooth-based devices (referred to as Bluetooth devices, including classic Bluetooth (BT) and Bluetooth Low Energy (BLE)) such as wearables (watches, headphones, etc.) and smart speakers have become widely used. To connect to a Bluetooth device, you first need to enter pairing mode (which requires the Bluetooth device to be discoverable and connectable), then search, pair, and connect. This process is cumbersome and can cause existing connections to be interrupted.

[0003] At the same time, regardless of whether the Bluetooth device is classic Bluetooth BT or low-power Bluetooth BLE, there is no concept of usage or management permissions for Bluetooth devices. In other words, any user who obtains a Bluetooth device and performs simple operations on the Bluetooth device (such as turning the power on and off, or long pressing a function button, etc.) can reset the Bluetooth device to enter pairing mode and obtain usage or management permissions for the Bluetooth device. In scenarios such as when a Bluetooth device is lost, the security of the Bluetooth device is relatively low.

[0004] Therefore, there is an urgent need for a technical solution that can improve the security of Bluetooth devices. Summary of the Invention

[0005] The embodiments of the present application provide a control method, a sharing method, a device, and a system, which can improve the security of Bluetooth devices and realize the sharing of Bluetooth devices.

[0006] In a first aspect, embodiments of the present application provide a control method, which may include: establishing a pairing connection between a second device (e.g., a Bluetooth-enabled smartphone A) and a first device (e.g., a Bluetooth-enabled in-vehicle device B). The second device sends a first message to the first device, and receives a second message sent by the first device based on the first message.

[0007] The first message can be used to indicate that the second device can share the connection. Here, it can be understood that the first message is used to indicate that the second device supports the secure sharing function. If the second device does not support the secure sharing function, the second device only has usage rights over the first device and does not have management rights. The second message is used to indicate that the first device can share the connection (which can be understood as the first device supports the secure sharing function), and the first device sets the second device as the management device.

[0008] It is understandable that the process of the second device sending the first message to the first device and the first device sending the second message to the second device can be considered as the interaction between the second device and the first device to perform the secure sharing function. In addition, when the first device sets the second device as the management device, the second device becomes the manager of the first device, which means that the second device has the right to use (which can be permanent) and management rights to the first device, and the first device can record the right to use and management rights of the second device.

[0009] The control method provided in the first aspect of the embodiment of the present application can realize the control of the first device by the second device on the basis of establishing a pairing connection between the first device and the second device, thereby improving the security of the first device.

[0010] For example, the first device may be in a factory-set state or an unmanaged state. Therefore, when the first device is connected to another device such as the second device as an accessory device for the first time, the second device automatically becomes a managed device of the first device.

[0011] In one possible implementation, the second device and the first device may establish a pairing connection in the following two ways:

[0012] Method 1: The first device enters the search state, the second device searches for the first device, and pairs with the first device.

[0013] Method 2: The first device and the second device establish a pairing connection through proximity discovery (such as the near field communication (NFC) function of a smartphone or broadcast scanning by the second device).

[0014] It should be noted that not only can the pairing connection between the second device and the first device be achieved through the above two methods, but other methods other than the above two methods can also be used to achieve the pairing connection between the second device and the first device, which is not limited in the embodiments of the present application.

[0015] In one possible implementation, after the second device receives the second message sent by the first device based on the first message, the second device may further send a third message to the first device. This third message may be used to instruct the first device to prohibit scanning. In other words, the purpose of the second device sending the third message to the first device is to cause the first device to disable the pairing connection function.

[0016] In another possible implementation, after the second device receives the second message sent by the first device based on the first message, the second device may further send a fourth message to the first device. The fourth message is used to instruct the first device to resume scanning. In other words, the purpose of the second device sending the fourth message to the first device is to enable the first device to resume pairing and connection functionality.

[0017] In the embodiment of the present application, the second device sends a third message to the first device to instruct the first device to prohibit scanning or a fourth message to instruct the first device to resume scanning, thereby implementing the second device's independent management and control of the first device (i.e., the second device's exclusive control over the first device). The first device can only be used under the control of the second device, and the control process is simple and easy to implement. In addition, the second device can manage all connected and paired devices of the first device.

[0018] In a second aspect, an embodiment of the present application provides a control method, which may include: establishing a pairing connection between a first device and a second device (see the above description), receiving a first message from the second device, and sending a second message to the second device based on the first message.

[0019] The detailed introduction of the first message and the second message can also be found above and will not be repeated here.

[0020] The control method provided in the second aspect of the embodiment of the present application can realize the control of the first device by the second device on the basis of establishing a pairing connection between the first device and the second device, thereby improving the security of the first device.

[0021] In one possible implementation, after the first device sends the second message to the second device, the first device may also receive a third message from the second device. This third message may be used to instruct the first device to prohibit scanning. In other words, the purpose of the second device sending the third message to the first device is to cause the first device to disable the pairing connection function.

[0022] Furthermore, after the first device receives the third message, the first device may record the third message and no longer respond to other devices except the second device. It should be noted that since the second device may still be connected to the first device, even if the first device enters a mode that prohibits scanning, the first device may still be in a connectable mode.

[0023] In another possible implementation, after the first device sends the second message to the second device, the first device may also receive a fourth message from the second device. The fourth message is used to instruct the first device to resume scanning. In other words, the purpose of the second device sending the fourth message to the first device is to enable the first device to resume pairing and connection functionality.

[0024] Furthermore, after the first device receives the fourth message, it records the fourth message and responds to the other devices except the second device again. The first device can be put into a scanning mode (which can also be considered as a pairing and connection mode) by turning the first device on and off, or long pressing a function button.

[0025] In an embodiment of the present application, the second device manages and controls the first device by sending a third message to the first device to instruct the first device to prohibit scanning or a fourth message to instruct the first device to resume scanning. The control process is simple and easy to implement.

[0026] Since the first device is an accessory device of the second device, even if the second device is the manager of the first device, the second device needs to synchronize information such as the address book every time it disconnects and reconnects with the first device. When the amount of address book and other information that needs to be synchronized is large, a longer synchronization time is required. In addition, when the user lends the first device to a third device (such as user C's smartphone C), the third device will use the first device, so that the first device will be shared. When the first device (such as vehicle-mounted device B) is shared, there is a risk of leakage of information stored in the first device, such as contacts, call logs, text messages, etc. of the second device. Therefore, it is necessary to share the first device with the third device through the second device, and set the third device's permission to use the first device (usage permission and / or management permission) to reduce the risk of information leakage of the second device.

[0027] Therefore, in the third aspect, an embodiment of the present application provides a sharing method, which may include: the second device establishes a pairing connection with the first device (refer to the above introduction). The second device sends a first message to the first device. The second device receives a second message sent by the first device based on the first message. The second device sends a first message to a third device (such as a smartphone C with Bluetooth function), sends the information of the third device fed back by the third device based on the first message to the first device, and sends the information of the first device to the third device. The second device receives connection information fed back from the third device based on the information of the first device, and sends a management instruction to the first device based on the connection information.

[0028] Among them, the detailed introduction of the first message and the second message can be found above and will not be repeated here.

[0029] It should be noted that the information of the third device may include address information and / or name information of the third device.

[0030] It should also be noted that the information of the first device may include at least one of the address information, name information, device form (such as the first device is a vehicle-mounted device, not a Bluetooth headset), device type (such as classic Bluetooth BT and / or low-power Bluetooth BLE, etc.) and device information (such as profile information and service information).

[0031] In one possible implementation, during the process of the second device sending the information of the third device fed back by the third device to the first device and sending the information of the first device to the third device, the second device can also send a verification code randomly generated by the second device to the first device and the third device, which not only improves the security of sharing, but also speeds up the sharing connection.

[0032] The sharing method provided in the embodiment of the present application can realize the control of the first device by the second device on the basis of establishing a pairing connection between the first device and the second device. Moreover, based on the control of the first device by the second device, the second device can share the first device with the third device. Only through the sharing of the second device can the third device establish a sharing connection with the first device, thereby improving the security of the first device and preventing the information stored in the first device from being leaked.

[0033] In one possible implementation, after the second device receives the second message sent by the first device based on the first message, the second device may further send a third message to the first device. This third message may be used to instruct the first device to prohibit scanning. In other words, the purpose of the second device sending the third message to the first device is to cause the first device to disable the pairing connection function.

[0034] In another possible implementation, after the second device receives the second message sent by the first device based on the first message, the second device may further send a fourth message to the first device. The fourth message is used to instruct the first device to resume scanning. In other words, the purpose of the second device sending the fourth message to the first device is to enable the first device to resume pairing and connection functionality.

[0035] In an embodiment of the present application, the second device manages and controls the first device by sending a third message to the first device to instruct the first device to prohibit scanning or a fourth message to instruct the first device to resume scanning. The control process is simple and easy to implement.

[0036] Exemplarily, the connection information may include first connection information and second connection information, wherein the first connection information may be used to indicate that the third device agrees to establish a shared connection with the first device, and the second connection information is used to indicate that the third device refuses to establish a shared connection with the first device.

[0037] Optionally, the management instruction may include a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

[0038] Furthermore, the second device sends a management instruction to the first device based on the connection information, which can be divided into the following two situations:

[0039] Case 1: When the connection information is the first connection information, the second device may send a sharing start instruction to the first device.

[0040] Case 2: When the connection information is the second connection information, the second device may send a sharing termination instruction to the first device.

[0041] In the embodiment of the present application, the second device sends a sharing start instruction / sharing end instruction to the first device based on the first connection information / second connection information sent by the third device, so that the first device performs corresponding operations according to the management instructions of the second device. The control process is highly reliable and the security of the first device is also improved.

[0042] In one possible implementation, when the connection information is first connection information, the second device receives device list information from the first device based on information feedback from the third device, and changes permission information of the third device based on the device list information. The permission information includes management permission and / or usage permission.

[0043] It should be noted that since the second device is the management device of the first device and the third device is a shared connection established between the second device and the first device, the third device often only has single-use permission (that is, the third device is a visitor of the first device).

[0044] Optionally, the above-mentioned device list information may include at least one of address information, name information, permission information (such as management permission and / or usage permission) and connection status (such as connected and disconnected) of the device paired with the first device.

[0045] The sharing method provided in the embodiment of the present application can change the permission information of the third device when other devices such as a third device use the first device (for example, the single-use permission of the third device can be changed to permanent use permission, and the single-use permission of the third device can be changed to permanent use permission and management permission (the third device also becomes the management device of the first device)), thereby avoiding the leakage of information stored in the first device and improving the security of sharing.

[0046] In a fourth aspect, an embodiment of the present application provides a sharing method, which may include: a third device receiving a first message from a second device (see above), and feeding back information about the third device (see above) to the second device based on the first message. The third device receives information about the first device from the second device (see above). The third device feeds back connection information determined based on the information from the first device to the second device.

[0047] In one possible implementation, while the third device is receiving information from the first device of the second device, the third device can also receive a randomly generated verification code from the second device, which not only improves the security of sharing but also speeds up the sharing connection.

[0048] The sharing method provided in the embodiment of the present application is based on establishing a pairing connection between the first device and the second device, and shares the first device with the third device through the second device, so that the third device can also use the first device, thereby improving the security of the first device and preventing the information stored in the first device from being leaked.

[0049] In one possible implementation, the third device may determine connection information based on information about the first device. The connection information may include first connection information and second connection information. The first connection information may indicate that the third device agrees to establish a shared connection with the first device, while the second connection information may indicate that the third device refuses to establish a shared connection with the first device.

[0050] Furthermore, if the connection information is first connection information, the third device may send the first connection information to the second device and send a connection request to the first device. If the connection information is second connection information, the third device may send the second connection information to the second device.

[0051] In a fifth aspect, an embodiment of the present application provides a sharing method, which may include: establishing a pairing connection between a first device and a second device (refer to the above description). The first device receives a first message from the second device. The first device sends a second message to the second device based on the first message. The first device receives information about a third device from the second device and enters a sharing mode. The first device receives a management instruction from the second device (refer to the above description), and determines whether to establish a sharing connection with the third device based on the management instruction.

[0052] The sharing method provided in the embodiment of the present application establishes a pairing connection between a first device and a second device, and then shares the first device with a third device through the second device, thereby achieving secure management and sharing of the first device and improving the security of the first device. Furthermore, within the time range when the first device enters sharing mode, the first device can also receive a verification code randomly generated by the second device, thereby improving the efficiency of the pairing connection between the third device and the first device. Furthermore, the first device can enter sharing mode without disconnecting from the second device, avoiding reconnection between the second device and the first device and preventing the first device from repeatedly synchronizing its own stored information.

[0053] In the embodiment of the present application, the first device is not limited to the vehicle-mounted device B with Bluetooth function illustrated in the embodiment of the present application. As long as the first device has wireless communication function, the use (or management) of the first device by the third device can be achieved through sharing with the second device.

[0054] In one possible implementation, the first device receives a management instruction from the second device and determines whether to establish a sharing connection with the third device based on the management instruction. This can be divided into the following two situations:

[0055] Case 1: When the management instruction is a sharing start instruction, the first device receives a connection request from the third device and a sharing start instruction from the second device, and establishes a sharing connection with the third device.

[0056] Case 2: When the management instruction is a sharing termination instruction, the first device exits the sharing mode. Here, it is necessary to explain it in the following two aspects:

[0057] On the one hand, if the third device unilaterally refuses to establish a sharing connection with the first device, the third device will send the second connection information to the second device. The second device will then send a sharing termination instruction to the first device based on the second connection information, and the first device will then exit the sharing mode.

[0058] On the other hand, although the third device does not reject the establishment of a sharing connection with the first device, that is, the third device agrees to establish a sharing connection with the first device, but the first device does not receive a connection request from the third device within the time range when the first device enters sharing mode. In this case, the first device can actively exit sharing mode.

[0059] Furthermore, when the management instruction received by the first device from the second device is a sharing start instruction, the first device feeds back device list information (see the above introduction) to the second device based on the information of the third device.

[0060] In the sharing method provided in the embodiment of the present application, after the third device establishes a sharing connection with the first device, the first device will feedback device list information to the second device based on the information of the third device, and change the permission information of the third device through the second device, thereby avoiding the leakage of information stored in the first device and improving the security of sharing.

[0061] In a sixth aspect, an embodiment of the present application provides a second device (such as smartphone A), which may include a connection module and a transceiver module. The connection module is used to establish a pairing connection with the first device (see above). The transceiver module is used to send a first message to the first device (see above) and receive a second message sent by the first device based on the first message (see above).

[0062] In the embodiment of the present application, based on the establishment of a pairing connection between the first device and the second device, the second device implements reliable control of the first device by the second device through message interaction between the second device and the first device (that is, the second device sends a first message to the first device, and the second device can also receive a second message sent by the first device based on the first message), thereby improving the security of the first device.

[0063] In one possible implementation, after the transceiver module of the second device receives the second message sent by the first device based on the first message, the transceiver module may further send a third message to the first device. This third message may be used to instruct the first device to prohibit scanning. In other words, the purpose of the second device sending the third message to the first device is to cause the first device to disable the pairing connection function.

[0064] In another possible implementation, after the transceiver module of the second device receives the second message sent by the first device based on the first message, the transceiver module may further send a fourth message to the first device. The fourth message is used to instruct the first device to resume scanning. In other words, the purpose of the second device sending the fourth message to the first device is to enable the first device to resume pairing and connection functionality.

[0065] In an embodiment of the present application, the second device manages and controls the first device by sending a third message to the first device to instruct the first device to prohibit scanning or a fourth message to instruct the first device to resume scanning. The control process is simple and easy to implement.

[0066] Optionally, the transceiver module of the second device sends the first message (see above) to the third device, sends the third device information (see above) fed back by the third device based on the first message to the first device (which may be the transceiver module of the first device), and sends the first device information (see above) to the third device. In addition, the transceiver module may also receive connection information fed back by the third device based on the information of the first device, and send management instructions to the first device based on the connection information.

[0067] It should be noted that the detailed description of the connection information and management instructions can be found above and will not be repeated here.

[0068] In one possible implementation, if the connection information is the first connection information, indicating that the third device agrees to establish a sharing connection with the first device, the transceiver module of the second device may send a sharing start instruction to the first device. If the connection information is the second connection information, indicating that the third device refuses to establish a sharing connection with the first device, the transceiver module of the second device may send a sharing termination instruction to the first device.

[0069] In the embodiment of the present application, the second device sends a sharing start instruction / sharing end instruction to the first device based on the first connection information / second connection information sent by the third device, so that the first device performs corresponding operations according to the management instructions of the second device. The control process is highly reliable and the security of the first device is also improved.

[0070] Optionally, if the connection information is the first connection information, the second device's transceiver can receive device list information (see above) from the first device based on information feedback from the third device, and change the permission information of the third device based on the device list information. The permission information may include management permissions and / or usage permissions.

[0071] The sharing method provided in the embodiment of the present application can change the permission information of the third device when other devices such as a third device use the first device (for example, the third device can be changed from having only single-use permission to having permanent use permission, and the third device can be changed from having only single-use permission to having permanent use permission and management permission (the third device also becomes the management device of the first device)), thereby avoiding the leakage of information stored in the first device and improving the security of sharing.

[0072] In a seventh aspect, an embodiment of the present application provides a first device (such as an in-vehicle device B), which may include a connection module and a transceiver module. The connection module may be used to establish a pairing connection with a second device (see the above description). The transceiver module may be used to receive a first message from the second device (see the above description) and send a second message to the second device based on the first message (see the above description).

[0073] In the embodiment of the present application, based on the establishment of a pairing connection between the first device and the second device, the second device implements reliable control of the first device through message interaction between the second device and the first device (that is, the first device receives the first message sent by the second device, and the first device also sends the second message to the second device based on the first message), thereby improving the security of the first device.

[0074] In a possible implementation, after the transceiver module of the first device sends the second message to the second device, the transceiver module may further receive a third message from the second device (see the above introduction).

[0075] Furthermore, after the transceiver module receives the third message, the transceiver module may record the third message and no longer respond to other devices except the second device. It should be noted that since the second device may still be connected to the first device, even if the first device enters a mode that prohibits scanning, the first device may still be in a mode that allows connection.

[0076] In another possible implementation, after the transceiver module of the first device sends the second message to the second device, the transceiver module may further receive a fourth message from the second device (see the above introduction).

[0077] Furthermore, when the transceiver module of the first device receives the fourth message, the transceiver module records the fourth message and responds to the other devices except the second device again. The first device can be put into a scanning mode (which can also be considered as a pairing and connection mode) by turning on and off the power of the first device, or long pressing a function button.

[0078] In an embodiment of the present application, the second device manages and controls the first device by sending a third message to the first device to instruct the first device to prohibit scanning or a fourth message to instruct the first device to resume scanning. The control process is simple and easy to implement.

[0079] In one possible implementation, the transceiver module of the first device may also receive information about a third device from the second device (which may be the transceiver module of the second device) (see above) to enter sharing mode. Furthermore, the transceiver module of the first device may also receive management instructions from the second device (see above) and determine whether to establish a sharing connection with the third device based on the management instructions.

[0080] Furthermore, when the management instruction is a sharing start instruction, the transceiver module of the first device can receive the connection request from the third device and the sharing start instruction from the second device, and establish a sharing connection with the third device. When the management instruction is a sharing termination instruction, the first device can exit the sharing mode. Here, it is necessary to explain in the following two aspects:

[0081] On the one hand, if the third device unilaterally refuses to establish a sharing connection with the first device, the third device will send the second connection information to the second device. The second device will then send a sharing termination instruction to the first device based on the second connection information, and the first device will then exit the sharing mode.

[0082] On the other hand, although the third device does not reject the establishment of a sharing connection with the first device, that is, the third device agrees to establish a sharing connection with the first device, but the first device does not receive a connection request from the third device within the time range when the first device enters sharing mode. In this case, the first device can actively exit sharing mode.

[0083] Optionally, the first device may further include a settings module. The settings module may set a time range for entering the sharing mode of the first device. If no connection request is received from the third device within the set time range, the first device exits the sharing mode (see above).

[0084] Furthermore, when the management instruction received by the transceiver module of the first device from the second device is a sharing start instruction, the transceiver module feeds back device list information (refer to the above introduction, which will not be repeated here) to the second device based on the information of the third device.

[0085] The sharing method provided in the embodiment of the present application allows the second device to change the permission information of the third device when other devices such as a third device use the first device (for example, the third device can be changed from having only a single-use permission to having a permanent use permission, and can also be changed from having only a single-use permission to having a permanent use permission and management permission (the third device also becomes the management device of the first device)), thereby avoiding the leakage of information stored in the first device and improving the security of sharing.

[0086] In an eighth aspect, the present application provides a third device (such as a smartphone C) that may include a receiving module and a sending module. The receiving module may be used to receive a first message (described above) from a second device (which may be a transceiver module of the second device), feed back information about the third device (described above) to the second device (which may be a transceiver module of the second device) based on the first message, and receive information about the first device (described above) sent from the second device (which may be a transceiver module of the second device). The sending module may be used to feed back connection information (described above) determined based on the information of the first device to the second device (which may be a transceiver module of the second device).

[0087] In the embodiment of the present application, based on the establishment of a pairing connection between the second device and the first device, the first device is shared with the third device through the second device, thereby enabling the third device to use (or manage) the first device and improving the security of the first device.

[0088] In one possible implementation, the sending module may determine the connection information based on the information of the first device, that is, the sending module may determine whether the connection information is the first connection information (see above) or the second connection information (see above) based on the information of the first device. If the connection information is the first connection information, the sending module sends the first connection information to the second device (which may be the transceiver module of the second device) and sends a connection request to the first device (which may be the transceiver module of the first device). If the connection information is the second connection information, the sending module sends the second connection information to the second device (which may be the transceiver module of the second device).

[0089] In the embodiment of the present application, the second device sends a sharing start instruction / sharing end instruction to the first device based on the first connection information / second connection information sent by the third device, so that the first device performs corresponding operations according to the management instructions of the second device. The control process is highly reliable and the security of the first device is also improved.

[0090] In a ninth aspect, an embodiment of the present application provides a control system, which may include the second device in the sixth aspect and its possible implementations and the first device in the seventh aspect and its possible implementations. The first device may be coupled to the second device.

[0091] In a tenth aspect, embodiments of the present application provide a sharing system, which may include the second device of the sixth aspect and its possible implementations, the first device of the seventh aspect and its possible implementations, and the third device of the eighth aspect and its possible implementations. The first device, the second device, and the third device may be coupled to each other.

[0092] In an eleventh aspect, embodiments of the present application provide a computer-readable storage medium having instructions stored therein. When the instructions are executed on a computer, the computer-readable storage medium can be used to execute the control methods provided in the first aspect and its possible implementations, and the second aspect and its possible implementations, and can also be used to execute the sharing methods provided in the third aspect and its possible implementations, through the fifth aspect and its possible implementations.

[0093] In a twelfth aspect, embodiments of the present application provide a computer program product comprising instructions. When the instructions are executed on a computer or processor, the computer or processor may implement the control methods provided in the first aspect and its possible implementations, and the second aspect and its possible implementations, and may also implement the sharing methods provided in the third aspect and its possible implementations, through the fifth aspect and its possible implementations.

[0094] It should be understood that the second aspect and the twelfth aspect of the present application are consistent with the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0095] Figure 1 This is a schematic flow chart of the control method provided in the embodiment of the present application;

[0096] Figure 2 is another schematic flow chart of the control method provided in an embodiment of the present application;

[0097] Figure 3 is another schematic flow chart of the control method provided in the embodiment of the present application;

[0098] Figure 4 This is a schematic flow chart of the sharing method provided in the embodiment of the present application;

[0099] Figure 5 Schematic diagram of the structure of the smartphone A provided in the embodiment of the present application;

[0100] Figure 6 Schematic diagram of the structure of the vehicle-mounted device B provided in an embodiment of the present application;

[0101] Figure 7 Schematic diagram of the structure of a smartphone C provided in an embodiment of the present application;

[0102] Figure 8 Schematic diagram of the structure of the control system CS provided in an embodiment of the present application;

[0103] Figure 9 It is a structural diagram of the sharing system SS provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0105] To make the objectives, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of this application.

[0106] The terms "first," "second," and the like in the description, embodiments, claims, and drawings of this application are used solely for descriptive purposes and are not to be construed as indicating or implying relative importance or order. Furthermore, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions, such as, for example, inclusion of a series of steps or units. A method, system, product, or apparatus is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0107] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0108] With the rapid development of communications technology and artificial intelligence, Bluetooth devices (including classic Bluetooth BT and Bluetooth Low Energy BLE) have become widely used, including wearable devices (such as Bluetooth watches and headphones) and Bluetooth audio devices (such as smart home speakers and in-car devices). To connect to a Bluetooth device, you must first put the device into pairing mode (for example, classic Bluetooth BT enters the pairing state, and Bluetooth Low Energy BLE enters the advertising state), then perform search, pairing, and connection. This entire process is cumbersome and can cause existing connections to be interrupted.

[0109] At the same time, regardless of whether the Bluetooth device is classic Bluetooth BT or low-power Bluetooth BLE, there is no concept of usage permissions or management permissions for Bluetooth devices. In other words, any user only needs to perform simple operations on the Bluetooth device (such as turning the power on and off, or long pressing a function button (some Bluetooth devices will display a blue light or red and blue lights flashing alternately by long pressing a function button), etc.) to reset the Bluetooth device to enter pairing mode, thereby obtaining usage permissions or management permissions for the Bluetooth device. In scenarios such as when a Bluetooth device is lost, the security of the Bluetooth device is relatively low.

[0110] For example, user A is the owner of Bluetooth device B (e.g., a Bluetooth-enabled headset or watch). Therefore, user A's smartphone A (which has Bluetooth functionality and can connect to Bluetooth device B via Bluetooth) is the manager of Bluetooth device B. It's understandable that smartphone A not only has management rights over Bluetooth device B, but also has usage rights (which can be permanent) over Bluetooth device B. When user C performs the simple operation described above on Bluetooth device B, they can reset Bluetooth device B and put it into pairing mode. Thus, user C's smartphone C (which has Bluetooth functionality and can connect to Bluetooth device B via Bluetooth) not only obtains usage rights but also management rights over Bluetooth device B. It can be seen that smartphone C has also become the manager of Bluetooth device B. In other words, smartphone A, the owner, and smartphone C, the guest, have no different permissions with respect to Bluetooth device B: both have usage and management rights over Bluetooth device B.

[0111] To overcome the security issues of the aforementioned Bluetooth devices, an embodiment of the present application provides a device information synchronization method based on a network cloud service. When the Bluetooth device is connected to the Internet, the user can log in to their account and automatically synchronize pairing information with the Bluetooth device. This method not only requires logging in to the user's account, but also requires the Bluetooth device to be connected to the Internet. In scenarios without Internet access, the Bluetooth device will be unusable. Furthermore, this method is only used to synchronize pairing information between multiple Bluetooth devices of an individual user, and cannot solve the problem of sharing or temporarily borrowing Bluetooth devices between multiple users.

[0112] In order to overcome the security issues and possible unusability of the above-mentioned Bluetooth devices (including the inability to use without the Internet, shared use or temporary borrowing of Bluetooth devices between multiple personal users, etc.), the embodiment of the present application provides a method for controlling a Bluetooth device with a smartphone A (i.e., a second device, which can also be other devices with a user interface UI) and a vehicle-mounted device B (i.e., a first device, which can be a vehicle-mounted speaker with Bluetooth function, as an accessory device of the second device), such as Figure 1 As shown, the control process 100 may include:

[0113] Step S101: A pairing connection is established between smartphone A and vehicle-mounted device B.

[0114] Step S102: Smartphone A sends a first message M1 to vehicle-mounted device B.

[0115] Step S103: The in-vehicle device B sends a second message M2 to the smartphone A based on the first message M1.

[0116] Furthermore, the first message M1 can be used to indicate that smartphone A can share the connection. Here, it can be understood that the first message M1 is used to indicate that smartphone A supports the secure sharing function. If smartphone A does not support the secure sharing function, smartphone A only has usage rights over vehicle-mounted device B, but does not have management rights. The second message M2 is used to indicate that vehicle-mounted device B can share the connection (which can be understood as vehicle-mounted device B supporting the secure sharing function), and vehicle-mounted device B sets smartphone A as the management device.

[0117] It is understandable that the process of smartphone A sending the first message M1 to vehicle-mounted device B and vehicle-mounted device B sending the second message M2 to smartphone A can be considered as the interaction between smartphone A and vehicle-mounted device B to perform the secure sharing function. In addition, when vehicle-mounted device B sets smartphone A as the management device, smartphone A becomes the manager of vehicle-mounted device B. In other words, smartphone A has usage rights (which can be permanent) and management rights over vehicle-mounted device B, and vehicle-mounted device B can record smartphone A's usage and management rights.

[0118] The control method provided in the embodiment of the present application can enable smartphone A to control the vehicle-mounted device B on the basis of establishing a pairing connection between the vehicle-mounted device B and the smartphone A, thereby improving the safety of the vehicle-mounted device B.

[0119] For example, the vehicle-mounted device B may be in a factory-set state or in an unmanaged state. Therefore, when the vehicle-mounted device B is connected to another device such as smartphone A as an accessory device for the first time, smartphone A automatically becomes the managed device of the vehicle-mounted device B.

[0120] In one possible implementation, smartphone A and vehicle-mounted device B may establish a pairing connection through the following two methods:

[0121] Method 1: Car device B enters the search state, smartphone A searches for smart device B, and pairs with car device B.

[0122] Method 2: The vehicle-mounted device B and the smartphone A establish a pairing connection through proximity discovery (such as the smartphone's NFC (nearfield communication) function or smartphone A performing broadcast scanning).

[0123] It should be noted that not only can the pairing connection between smartphone A and vehicle-mounted device B be achieved through the above two methods, but other methods other than the above two methods can also be used to achieve the pairing connection between smartphone A and vehicle-mounted device B. This embodiment of the present application does not limit this.

[0124] In one example, after the vehicle-mounted device B sends the second message M2 to the smartphone A, Figure 2 As shown, step S104 may also be performed: smartphone A sends a third message M3 to vehicle-mounted device B. The third message M3 may be used to instruct vehicle-mounted device B to prohibit scanning. In other words, the purpose of smartphone A sending the third message M3 to vehicle-mounted device B is to cause vehicle-mounted device B to disable the pairing connection function.

[0125] Furthermore, after receiving the third message M3, vehicle-mounted device B records the third message M3 and no longer responds to other devices except smartphone A. Vehicle-mounted device B can be put into a scan-inhibited mode by powering it on and off, or by long-pressing a function button. It should be noted that since smart device A may still be connected to vehicle-mounted device B, even if vehicle-mounted device B enters scan-inhibited mode, it can still be in a connectable mode.

[0126] In another example, after the in-vehicle device B sends the second message M2 to the smartphone A, Figure 3 As shown, step S104' can also be performed: smartphone A sends a fourth message M4 to vehicle-mounted device B. The fourth message M4 is used to instruct vehicle-mounted device B to resume scanning. In other words, the purpose of smartphone A sending the fourth message M4 to vehicle-mounted device B is to enable vehicle-mounted device B to resume pairing and connection.

[0127] Furthermore, after the vehicle-mounted device B receives the fourth message M4, the vehicle-mounted device B records the fourth message M4 and responds to other devices other than the smartphone A. The vehicle-mounted device B can be put into a scanning mode (which can also be considered a pairing and connection mode) by turning the vehicle-mounted device B on and off, or long pressing a function button.

[0128] In this embodiment of the present application, smartphone A sends a third message to vehicle-mounted device B, instructing vehicle-mounted device B to prohibit scanning, or a fourth message to instruct vehicle-mounted device B to resume scanning. This allows smartphone A to independently manage and control vehicle-mounted device B (i.e., smartphone A exclusively controls vehicle-mounted device B). Vehicle-mounted device B can only be used under the control of smartphone A, making the control process simple and easy to implement. In addition, smartphone A can manage all connected and paired devices of vehicle-mounted device B.

[0129] Because vehicle-mounted device B is an accessory device of smartphone A, even if smartphone A is the administrator of vehicle-mounted device B, smartphone A needs to synchronize its contacts and other information each time it disconnects and reconnects with vehicle-mounted device B. When a large amount of contacts and other information needs to be synchronized, the synchronization process takes a long time. Furthermore, if user A lends their vehicle to other users, those users may use vehicle-mounted device B, resulting in vehicle-mounted device B being shared. When vehicle-mounted devices are shared, there is a risk of leaking private information stored on vehicle-mounted device B, such as smartphone A's contacts, call logs, and text messages.

[0130] In order to prevent the information stored in the vehicle-mounted device B from being leaked and a large amount of duplicate data (such as the address book of smartphone A) from being transmitted, the embodiment of the present application takes smartphone A (i.e., the second device), vehicle-mounted device B (i.e., the first device) and smartphone C (i.e., the third device) as an example to provide a sharing method, such as Figure 4 The sharing process 200 may include:

[0131] Step S201: Smartphone A establishes a pairing connection with vehicle-mounted device B.

[0132] Step S202: Smartphone A sends a first message M1 to vehicle-mounted device B.

[0133] Step S203: The in-vehicle device B sends a second message M2 to the smartphone A based on the first message M1.

[0134] Step S204: Smartphone A sends a first message M1 to smartphone C.

[0135] Step S205: Smartphone C feeds back information about smartphone C to smartphone A based on the first message M1.

[0136] Step S206: Smartphone A sends the information of smartphone C to vehicle-mounted device B.

[0137] Step S207: The vehicle-mounted device B receives the information from the smartphone C and enters the sharing mode.

[0138] Step S208: Smartphone A sends the information of vehicle-mounted device B to smartphone C.

[0139] Step S209: Smartphone C determines connection information based on the information of the in-vehicle device B and sends the connection information to smartphone A.

[0140] Step S210: Smartphone A sends a management instruction to the vehicle-mounted device B based on the connection information.

[0141] Step S211: The in-vehicle device B determines whether to establish a sharing connection with the smartphone C based on the management instruction.

[0142] Furthermore, the first message M1 can be used to indicate that smartphone A can share the connection. Here, it can be understood that the first message M1 is used to indicate that smartphone A supports the secure sharing function. If smartphone A does not support the secure sharing function, smartphone A only has usage rights over vehicle-mounted device B, but does not have management rights. The second message M2 is used to indicate that vehicle-mounted device B can share the connection (which can be understood as vehicle-mounted device B supporting the secure sharing function), and vehicle-mounted device B sets smartphone A as the management device.

[0143] It is understandable that the process of smartphone A sending the first message M1 to vehicle-mounted device B and vehicle-mounted device B sending the second message M2 to smartphone A can be considered as the interaction between smartphone A and vehicle-mounted device B to perform the security sharing function. In addition, when vehicle-mounted device B sets smartphone A as the management device, smartphone A becomes the manager of vehicle-mounted device B. In other words, smartphone A has usage rights (which can be permanent) and management rights over vehicle-mounted device B, and the vehicle-mounted device can record smartphone A's usage and management rights.

[0144] In one possible implementation, the information of the vehicle-mounted device B may include at least one of the address information, name information, device form (such as the device is a vehicle-mounted device B, not a Bluetooth headset), device type (such as classic Bluetooth BT and / or low-power Bluetooth BLE, etc.) and device information (such as profile information and service information).

[0145] In another possible implementation, in the process of smartphone A sending information from smartphone C to vehicle-mounted device B and smartphone A sending information from vehicle-mounted device B to smartphone C, smartphone A can also send a verification code randomly generated by smartphone A to vehicle-mounted device B and smartphone C. This not only improves the security of sharing, but also speeds up the sharing connection.

[0146] The above-mentioned sharing method in the embodiment of the present application can realize the control of the vehicle-mounted device B by the smartphone A on the basis of establishing a pairing connection between the vehicle-mounted device B and the smartphone A. Moreover, on the basis of the control of the vehicle-mounted device B by the smartphone A, the smartphone A can share the vehicle-mounted device B with the smartphone C. Only through the sharing of the smartphone A can the smartphone C establish a sharing connection with the vehicle-mounted device B, thereby improving the security of the vehicle-mounted device B and preventing the information stored in the vehicle-mounted device B from being leaked.

[0147] Additionally, during the timeframe when vehicle device B enters sharing mode, it receives a randomly generated verification code from smartphone A, improving the connection efficiency between smartphone C and vehicle device B. Furthermore, vehicle device B can enter sharing mode without disconnecting from smartphone A, preventing reconnection between smartphone A and vehicle device B and preventing vehicle device B from repeatedly synchronizing its stored information.

[0148] In one possible implementation, smartphone A and vehicle-mounted device B may establish a pairing connection through the following two methods:

[0149] Method 1: Car device B enters the search state, smartphone A searches for smart device B, and pairs with car device B.

[0150] Method 2: The vehicle-mounted device B and the smartphone A establish a pairing connection through proximity discovery (such as the smartphone's NFC (nearfield communication) function or smartphone A performing broadcast scanning).

[0151] It should be noted that not only can the pairing connection between smartphone A and vehicle-mounted device B be achieved through the above two methods, but other methods other than the above two methods can also be used to achieve the pairing connection between smartphone A and vehicle-mounted device B. This embodiment of the present application does not limit this.

[0152] For example, the connection information LM may include first connection information LM1 and second connection information LM2, wherein the first connection information LM1 may be used to indicate that the smartphone C agrees to establish a shared connection with the vehicle-mounted device B, and the second connection information LM2 may be used to indicate that the smartphone C refuses to establish a shared connection with the vehicle-mounted device B.

[0153] Optionally, the management instruction MI may include a sharing start instruction MI1 and a sharing end instruction MI2. The sharing start instruction MI1 is used to instruct the vehicle-mounted device B to start establishing a sharing connection with the smartphone C, and the sharing end instruction MI2 is used to instruct the vehicle-mounted device B to terminate the sharing connection with the smartphone C.

[0154] Furthermore, smartphone A sends a management instruction MI to vehicle-mounted device B based on connection information LM, which can be divided into the following two situations:

[0155] Case 1: When the connection information LM is the first connection information LM1, the smartphone A sends a sharing start instruction MI1 to the vehicle-mounted device B.

[0156] Case 2: When the connection information LM is the second connection information LM2, the smartphone A sends a sharing termination instruction MI2 to the vehicle-mounted device B.

[0157] In the embodiment of the present application, smartphone A sends a sharing start instruction / sharing end instruction to the vehicle-mounted device B according to the first connection information / second connection information sent by smartphone C, so that the vehicle-mounted device B performs corresponding operations according to the management instructions of smartphone A. The control process is highly reliable and the safety of the vehicle-mounted device B is also improved.

[0158] In one possible implementation, if the management instruction MI is a sharing start instruction MI1, it means that the vehicle-mounted device B is about to establish a sharing connection with the smartphone C. Then, the smartphone C will send a connection request to the vehicle-mounted device B. The vehicle-mounted device B receives the connection request and the sharing start instruction from the smartphone A and establishes a sharing connection with the smartphone C.

[0159] In another possible implementation, if the management instruction MI is a sharing termination instruction MI2, the vehicle-mounted device B exits the sharing mode. This needs to be explained in the following two aspects:

[0160] On the one hand, smartphone C unilaterally refuses to establish a sharing connection with vehicle-mounted device B, so smartphone C will send the second connection information LM2 to smartphone A. Smartphone A will then send a sharing termination instruction MI2 to vehicle-mounted device B based on the second connection information LM2, and vehicle-mounted device B will then exit the sharing mode.

[0161] On the other hand, although smartphone C did not reject the sharing connection with vehicle-mounted device B, that is, smartphone C agreed to establish a sharing connection with vehicle-mounted device B, vehicle-mounted device B did not receive a connection request from smartphone C within the time range set by vehicle-mounted device B to enter sharing mode. In this case, vehicle-mounted device B can actively exit sharing mode.

[0162] In one example, the management instruction MI is a sharing start instruction MI1, and the vehicle-mounted device B feeds back device list information to the smartphone A based on the information of the smartphone C. The smartphone A can change the permission information of the smart device C based on the device list information. The permission information includes management permission and / or usage permission.

[0163] The sharing method provided in the embodiment of the present application can change the permission information of smartphone C (i.e., the device associated with the vehicle-mounted device B) when other devices such as smartphone C use the vehicle-mounted device B (for example, the smartphone C can be changed from having only a single-use permission to having a permanent use permission, and the smartphone C can also be changed from having only a single-use permission to having a permanent use permission and management permission (the smartphone C also becomes the management device of the vehicle-mounted device B)), thereby avoiding the leakage of information stored in the vehicle-mounted device and improving the security of sharing.

[0164] It should be noted that since smartphone A is the management device of vehicle-mounted device B, smartphone C is a shared connection established between smartphone A and vehicle-mounted device B, so smartphone C often only has single-time usage permission (that is, smartphone C is a visitor of vehicle-mounted device B).

[0165] Optionally, the above-mentioned device list information may include at least one of the address information, name information, permission information (such as management permission and / or usage permission) and connection status (such as connected and not connected) of the device paired with the vehicle-mounted device B.

[0166] Furthermore, smartphone A changes the permission information of smartphone C based on the address information, name information, permission information and connection status of the device paired with vehicle-mounted device B fed back by vehicle-mounted device B. In other words, smartphone A can increase or decrease the permission of smartphone C.

[0167] In one example, smartphone A can elevate the permissions of smartphone C. For example, smartphone A can change smartphone C's single-use permissions to permanent permissions, changing smartphone C from a guest user of vehicle-mounted device B to a regular user. Another example is smartphone A changing smartphone C's permanent permissions to permanent permissions and management permissions, changing smartphone C from a regular user of vehicle-mounted device B to an administrator.

[0168] In another example, smartphone A can downgrade smartphone C's permissions. For example, smartphone A can change smartphone C's permanent usage permissions to single-use permissions, changing smartphone C from a regular user of the vehicle-mounted device to a guest. For another example, smartphone A can change smartphone C's permanent usage permissions and management permissions to permanent usage permissions, changing smartphone C from an administrator of vehicle-mounted device B to a regular user.

[0169] The sharing method provided in the embodiment of the present application can limit the number of connections between smartphone C and the vehicle-mounted device through management instructions sent by smartphone A when other devices such as smartphone C use the vehicle-mounted device B. It can also set the permission information of smartphone C (for example, smartphone C can be set to have single-use permission or permanent use permission of vehicle-mounted device B), thereby avoiding the leakage of information stored in vehicle-mounted device B and improving the security of sharing.

[0170] The embodiment of the present application provides a smart phone A (i.e., a second device), such as Figure 5 As shown. Smartphone A may include a connection module A1 and a transceiver module A2. The connection module A1 is used to establish a pairing connection with an in-vehicle device B (described below). The transceiver module A2 is used to send a first message M1 to the in-vehicle device B and receive a second message M2 sent by the in-vehicle device B based on the first message M1.

[0171] Furthermore, the first message M1 can be used to indicate that smartphone A can share the connection. Here, it can be understood that the first message M1 is used to indicate that smartphone A supports the secure sharing function. If smartphone A does not support the secure sharing function, smartphone A only has usage rights over vehicle-mounted device B, but does not have management rights. The second message M2 is used to indicate that vehicle-mounted device B can share the connection (which can be understood as vehicle-mounted device B supporting the secure sharing function), and vehicle-mounted device B sets smartphone A as the management device.

[0172] It is understandable that the process of smartphone A's transceiver module A2 sending the first message M1 to vehicle-mounted device B and vehicle-mounted device B sending the second message M2 to smartphone A's transceiver module A2 can be considered as the interaction between smartphone A and vehicle-mounted device B to perform the secure sharing function. In addition, when vehicle-mounted device B sets smartphone A as a management device, smartphone A becomes the manager of vehicle-mounted device B. This means that smartphone A has usage rights (which can be permanent) and management rights over vehicle-mounted device B, and vehicle-mounted device B can record smartphone A's usage and management rights.

[0173] The technical solution provided in the embodiment of the present application enables smartphone A to control vehicle-mounted device B on the basis of establishing a pairing connection between smartphone A and vehicle-mounted device B, thereby improving the security of vehicle-mounted device B.

[0174] For example, the vehicle-mounted device B may be in a factory-set state or in an unmanaged state. Therefore, when the vehicle-mounted device B is connected to another device such as smartphone A as an accessory device for the first time, smartphone A automatically becomes the managed device of the vehicle-mounted device B.

[0175] In one possible implementation, the transceiver module A2 may send a third message M3 to the vehicle-mounted device B. The third message M3 may be used to instruct the vehicle-mounted device B to prohibit scanning. In other words, the purpose of the transceiver module A2 sending the third message M3 to the vehicle-mounted device B is to cause the vehicle-mounted device B to disable the pairing connection function.

[0176] In another possible implementation, the transceiver module A2 may send a fourth message M4 to the vehicle-mounted device B. The fourth message M4 is used to instruct the vehicle-mounted device B to resume scanning. In other words, the purpose of the transceiver module A2 sending the fourth message M4 to the vehicle-mounted device B is to enable the vehicle-mounted device B to resume the pairing connection function.

[0177] Furthermore, the transceiver module A2 can send a first message M1 (described above) to the smartphone C (described below), send information about the smartphone C fed back by the smartphone C based on the first message M1 to the in-vehicle device B, and send information about the in-vehicle device B to the smartphone C. Furthermore, the transceiver module A2 can also receive connection information LM fed back by the smartphone C based on information from the in-vehicle device B, and send a management instruction MI to the in-vehicle device B based on the connection information LM.

[0178] It should be noted that the information of the smartphone C may include the address information and / or name information of the smartphone C.

[0179] It should also be noted that the information of the vehicle-mounted device B may include at least one of the address information, name information, device form (such as the device is a vehicle-mounted device B, not a Bluetooth headset), device type (such as classic Bluetooth BT and / or low-power Bluetooth BLE, etc.) and device information (such as profile information and service information).

[0180] For example, the connection information LM may include first connection information LM1 and second connection information LM2, wherein the first connection information LM1 may be used to indicate that the smartphone C agrees to establish a shared connection with the vehicle-mounted device B, and the second connection information LM2 may be used to indicate that the smartphone C refuses to establish a shared connection with the vehicle-mounted device B.

[0181] Optionally, the management instruction MI may include a sharing start instruction MI1 and a sharing end instruction MI2. The sharing start instruction MI1 is used to instruct the vehicle-mounted device B to start establishing a sharing connection with the smartphone C, and the sharing end instruction MI2 is used to instruct the vehicle-mounted device B to terminate the sharing connection with the smartphone C.

[0182] Furthermore, the transceiver module A2 sends the management instruction MI to the vehicle-mounted device B based on the connection information LM, which can be divided into the following two situations:

[0183] Case 1: When the connection information LM is the first connection information LM1 , the transceiver module A2 sends a sharing start instruction MI1 to the vehicle-mounted device B.

[0184] Case 2: When the connection information LM is the second connection information LM2, the transceiver module A2 sends a sharing termination instruction MI2 to the vehicle-mounted device B.

[0185] In one possible implementation, if the connection information LM is the first connection information LM1, the transceiver module A2 receives device list information from the vehicle-mounted device B based on information feedback from the smartphone C, and changes the permission information of the smartphone C based on the device list information. The permission information includes management permissions and / or usage permissions.

[0186] It should be noted that since smartphone A is the management device of vehicle-mounted device B, smartphone C is a shared connection established between smartphone A and vehicle-mounted device B, so smartphone C often only has single-time usage permission (that is, smartphone C is a visitor of vehicle-mounted device B).

[0187] Optionally, the above-mentioned device list information may include at least one of the address information, name information, permission information (such as management permission and / or usage permission) and connection status (such as connected and not connected) of the device paired with the vehicle-mounted device B.

[0188] Furthermore, smartphone A changes the permission information of smartphone C based on the address information, name information, permission information and connection status of the device paired with vehicle-mounted device B fed back by vehicle-mounted device B. In other words, smartphone A can increase or decrease the permission of smartphone C.

[0189] In one example, smartphone A can elevate the permissions of smartphone C. For example, smartphone A can change smartphone C's single-use permissions to permanent permissions, changing smartphone C from a guest user of vehicle-mounted device B to a regular user. Another example is smartphone A changing smartphone C's permanent permissions to permanent permissions and management permissions, changing smartphone C from a regular user of vehicle-mounted device B to an administrator.

[0190] In another example, smartphone A can downgrade smartphone C's permissions. For example, smartphone A can change smartphone C's permanent usage permissions to single-use permissions, changing smartphone C from a regular user of the vehicle-mounted device to a guest. For another example, smartphone A can change smartphone C's permanent usage permissions and management permissions to permanent usage permissions, changing smartphone C from an administrator of vehicle-mounted device B to a regular user.

[0191] When smartphone C uses vehicle-mounted device B, smartphone A can change the permission information of smartphone C (for example, it can change smartphone C's single-use permission to permanent use permission, and it can also change smartphone C's single-use permission to permanent use permission and management permission (smartphone C also becomes the management device of vehicle-mounted device B)), thereby avoiding the leakage of information stored in vehicle-mounted device B and improving the security of sharing.

[0192] like Figure 6As shown, an embodiment of the present application provides an in-vehicle device B (i.e., a first device). The in-vehicle device B may include a connection module B1 and a transceiver module B2. The connection module B1 may be used to establish a pairing connection with a smartphone A (which may be the connection module A1 of smartphone A). The transceiver module B2 may be used to receive a first message M1 from smartphone A (which may be the transceiver module A2 of smartphone A) and send a second message M2 to smartphone A (which may be the transceiver module A2 of smartphone A).

[0193] Furthermore, the first message M1 can be used to indicate that smartphone A can share the connection. Here, it can be understood that the first message M1 is used to indicate that smartphone A supports the secure sharing function. If smartphone A does not support the secure sharing function, smartphone A only has usage rights over vehicle-mounted device B, but does not have management rights. The second message M2 is used to indicate that vehicle-mounted device B can share the connection (which can be understood as vehicle-mounted device B supporting the secure sharing function), and vehicle-mounted device B sets smartphone A as the management device.

[0194] It is understandable that the process of smartphone A sending the first message M1 to vehicle-mounted device B and vehicle-mounted device B sending the second message M2 to smartphone A can be considered as the interaction between smartphone A and vehicle-mounted device B to perform the secure sharing function. In addition, when vehicle-mounted device B sets smartphone A as the management device, smartphone A becomes the manager of vehicle-mounted device B. In other words, smartphone A has usage rights (which can be permanent) and management rights over vehicle-mounted device B, and vehicle-mounted device B can record smartphone A's usage and management rights.

[0195] The technical solution provided in the embodiment of the present application enables smartphone A to control vehicle-mounted device B on the basis of establishing a pairing connection between smartphone A and vehicle-mounted device B, thereby improving the security of vehicle-mounted device B.

[0196] For example, the vehicle-mounted device B may be in a factory-set state or in an unmanaged state. Therefore, when the vehicle-mounted device B is connected to another device such as smartphone A as an accessory device for the first time, smartphone A automatically becomes the managed device of the vehicle-mounted device B.

[0197] In one possible implementation, the transceiver module B2 may receive a third message M3 from smartphone A (which may be the transceiver module A2 of smartphone A). This third message M3 may be used to instruct the in-vehicle device B to prohibit scanning. In other words, the purpose of the transceiver module A2 of smartphone A sending the third message M3 to the in-vehicle device B is to cause the in-vehicle device B to disable the pairing connection function.

[0198] Furthermore, the transceiver module B2 records the third message M3 and no longer responds to other devices except smartphone A. Vehicle-mounted device B can be put into a scan-disabled mode by powering it on and off, or by long-pressing a function button. It should be noted that since smart device A may still be connected to vehicle-mounted device B, even if vehicle-mounted device B enters scan-disabled mode, it can still be connected.

[0199] In another possible implementation, the transceiver module B2 may receive a fourth message M4 from smartphone A (which may be the transceiver module A2 of smartphone A). The fourth message M4 is used to instruct the in-vehicle device B to resume scanning. In other words, the purpose of smartphone A sending the fourth message M4 to the in-vehicle device B is to enable the in-vehicle device B to resume pairing and connection.

[0200] Furthermore, when the transceiver module B2 of the vehicle-mounted device B receives the fourth message M4, the transceiver module B2 records the fourth message M4 and responds to other devices other than the smartphone A. The vehicle-mounted device B can be put into a scanning mode (which can also be considered a pairing and connection mode) by turning the vehicle-mounted device B on and off, or long pressing a function button.

[0201] Optionally, the transceiver module A2 can receive information about smartphone C from smartphone A (which can be the transceiver module A2 of smartphone A) and enter sharing mode. The transceiver module A2 can also receive management instructions from smartphone A (which can be the transceiver module A2 of smartphone A) and determine whether to establish a sharing connection with smartphone C based on the management instructions.

[0202] It should be noted that the information of the smartphone C may include the address information and / or name information of the smartphone C.

[0203] In one possible implementation, if the management instruction MI is a sharing start instruction MI1, that is, the in-vehicle device B is about to start establishing a sharing connection with the smartphone C. Then, the transceiver module B2 receives the connection request sent by the smartphone C and the sharing start instruction MI1 from the smartphone A, and establishes a sharing connection with the smartphone C.

[0204] In another possible implementation, if the management instruction MI is a sharing termination instruction MI2, the vehicle-mounted device B will exit the sharing mode. This needs to be explained in the following two aspects:

[0205] On the one hand, smartphone C unilaterally refuses to establish a sharing connection with vehicle-mounted device B, so smartphone C will send the second connection information LM2 to smartphone A. Smartphone A will then send a sharing termination instruction MI2 to the transceiver module B2 of vehicle-mounted device B based on the second connection information LM2, and vehicle-mounted device B will then exit the sharing mode.

[0206] On the other hand, although smartphone C did not refuse to establish a sharing connection with vehicle-mounted device B, that is, smartphone C agreed to establish a sharing connection with vehicle-mounted device B's connection module B2, vehicle-mounted device B's transceiver module B2 did not receive a connection request from smartphone C within the time range set by vehicle-mounted device B to enter sharing mode. In this case, vehicle-mounted device B can actively exit sharing mode.

[0207] In another possible implementation, the vehicle-mounted device B may further include a settings module B3. The settings module B3 may set a time range (e.g., 3 minutes) for the vehicle-mounted device B to enter the sharing mode. If the vehicle-mounted device B does not receive a connection request from the smart device C within the time range, the vehicle-mounted device B may exit the sharing mode (see above).

[0208] During the timeframe when vehicle-mounted device B enters sharing mode, it receives a randomly generated verification code from smartphone A, improving the connection efficiency between smartphone C and vehicle-mounted device B. Furthermore, vehicle-mounted device B can enter sharing mode without disconnecting from smartphone A, avoiding reconnection between smartphone A and vehicle-mounted device B and preventing vehicle-mounted device B from repeatedly synchronizing its stored information.

[0209] Furthermore, the management instruction MI is a sharing start instruction MI1, and the transceiver module B2 can feedback device list information to the smartphone A based on the information of the smartphone C. The smartphone A can change the permission information of the smart device C based on the device list information. The permission information includes management permission and / or usage permission.

[0210] The technical solution provided in the embodiment of the present application can change the permission information of smartphone C (i.e., the device associated with the vehicle-mounted device B) when other devices such as smartphone C use the vehicle-mounted device B (for example, the smartphone C can be changed from having only a single-use permission to having a permanent use permission, and the smartphone C can also be changed from having only a single-use permission to having a permanent use permission and management permission (the smartphone C also becomes the management device of the vehicle-mounted device B)), thereby avoiding the leakage of information stored in the vehicle-mounted device and improving the security of sharing.

[0211] The embodiment of the present application also provides a smart phone C (ie, a third device), such as Figure 7As shown in FIG. Smartphone C may include a receiving module C1 and a sending module C2. The receiving module C1 is configured to receive a first message M1 from smartphone A, feed information about smartphone C back to smartphone A based on the first message M1, and receive information about in-vehicle device B from smartphone A. The sending module C2 is configured to determine connection information LM based on the information about in-vehicle device B, and feed the connection information LM back to smartphone A.

[0212] The technical solution provided in the embodiment of the present application is based on the establishment of a pairing connection between the vehicle-mounted device B and the smartphone A. The vehicle-mounted device B is shared with the smartphone C through the smartphone A, so that the smartphone C can also use the vehicle-mounted device B, thereby improving the security of the vehicle-mounted device B and preventing the information stored in the vehicle-mounted device B from being leaked.

[0213] Furthermore, the sending module C1 may determine the connection information LM based on the information of the vehicle-mounted device B. The connection information LM may include first connection information LM1 and second connection information LM2, wherein the first connection information LM1 is used to indicate that the smartphone C agrees to establish a sharing connection with the vehicle-mounted device B, and the second connection information LM2 is used to indicate that the smartphone C refuses to establish a sharing connection with the vehicle-mounted device B.

[0214] In one possible implementation, if the connection information LM is the first connection information LM1, the sending module C1 sends the first connection information LM1 to the smartphone A, indicating that the smartphone C agrees to establish a shared connection with the vehicle-mounted device B. Then, the sending module C1 sends a connection request to the vehicle-mounted device B.

[0215] In another possible implementation, if the connection information LM is the second connection information LM2, the sending module C1 sends the second connection information LM2 to the smartphone A, indicating that the smartphone C refuses to establish a shared connection with the vehicle-mounted device B. In this case, the sending module C1 does not send a connection request to the vehicle-mounted device B.

[0216] like Figure 8 As shown, the present application provides a control system. The control system CS includes a smartphone A (i.e., a second device, such as Figure 5 As shown) and the vehicle-mounted device B (ie, the first device, as shown Figure 6 Smartphone A is coupled with vehicle-mounted device B.

[0217] The control system provided in the embodiment of the present application can enable smartphone A to control vehicle-mounted device B, thereby improving the safety of vehicle-mounted device B.

[0218] exist Figure 8 Based on the control system CS shown in FIG, the embodiment of the present application further provides a sharing system SS, such as Figure 9The sharing system SS may include a smartphone A (i.e., a second device, such as Figure 5 As shown), vehicle-mounted device B (ie, the first device, such as Figure 6 As shown) and smartphone C (ie, the third device, such as Figure 7 As shown in FIG. 1 , the vehicle-mounted device B, the smartphone A, and the smartphone C are coupled to each other. As can be understood, the sharing system SS includes the control system CS and the smartphone C.

[0219] The sharing provided in the embodiment of the present application not only enables smartphone A to control the vehicle-mounted device B, but also realizes the shared connection between smartphone C and vehicle-mounted device B through smartphone A, so that smartphone C can use (or manage) vehicle-mounted device B, thereby improving the security of vehicle-mounted device B.

[0220] In one possible implementation, the present application provides a computer-readable storage medium in which instructions are stored. When the stored instructions are executed on a computer, they can be used to execute the following: Figures 1 to 3 Any of the control methods shown in can also be used to perform the following Figure 4 Sharing method shown.

[0221] In another possible implementation, the present application provides a computer program product, which includes instructions. When the instructions are executed on a computer or processor, the computer or processor implements the following Figures 1 to 3 Any of the control methods shown in can also be implemented as follows Figure 4 Sharing method shown.

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

[0223] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0224] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0225] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0228] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. A sharing method, characterized in that: Applied to the second device, comprising: Establishing a pairing connection with the first device; Sending a first message to the first device, where the first message is used to indicate that the second device can share a connection; receiving a second message sent from the first device based on the first message, where the second message is used to indicate that the first device can share a connection, and the first device sets the second device as a management device; Sending the first message to a third device, sending information about the third device fed back by the third device based on the first message to the first device, and sending information about the first device to the third device; receiving connection information fed back by the third device based on information of the first device, and sending a management instruction to the first device based on the connection information; The information of the third device includes address information and / or name information of the third device; The information of the first device includes at least one of address information, name information, device form, device type, and device information of the first device; The connection information includes first connection information and second connection information, the first connection information is used to indicate that the third device agrees to establish a sharing connection with the first device, and the second connection information is used to indicate that the third device refuses to establish a sharing connection with the first device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

2. The method according to claim 1, characterized in that The sending a management instruction to the first device based on the connection information includes: When the connection information is the first connection information, sending a sharing start instruction to the first device; When the connection information is the second connection information, a sharing termination instruction is sent to the first device.

3. The method according to claim 1, characterized in that The method further comprises: When the connection information is the first connection information, device list information based on information feedback from the third device is received from the first device, and permission information of the third device is changed based on the device list information, where the permission information includes management permission and / or usage permission.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: A third message is sent to the first device, where the third message is used to instruct the first device to prohibit being scanned.

5. The method according to any one of claims 1 to 3, characterized in that The method further comprises: A fourth message is sent to the first device, where the fourth message is used to instruct the first device to resume being scanned.

6. The method according to claim 3, characterized in that The device list information includes at least one of address information, name information, authority information, and connection status of devices paired with the first device.

7. A sharing method, characterized in that: Applicable to third-party devices, including: receiving a first message from a second device, and feeding back information about the third device to the second device based on the first message, wherein the first message is used to indicate that the second device can share a connection; receiving information from the first device from the second device; Feedback connection information determined based on the information of the first device to the second device, where the connection information is used by the second device to send a management instruction to the first device based on the connection information; The information of the third device includes address information and / or name information of the third device; The information of the first device includes at least one of address information, name information, device form, device type, and device information of the first device; The connection information includes first connection information and second connection information, the first connection information is used to indicate that the third device agrees to establish a sharing connection with the first device, and the second connection information is used to indicate that the third device refuses to establish a sharing connection with the first device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

8. The method according to claim 7, characterized in that include: Feeding back connection information determined based on the information of the first device to the second device includes: determining the connection information based on the information of the first device; When the connection information is the first connection information, sending the first connection information to the second device and sending a connection request to the first device; When the connection information is the second connection information, the second connection information is sent to the second device.

9. A sharing method, characterized in that: Applied to a first device, comprising: Establishing a pairing connection with a second device; receiving a first message from the second device, the first message being used to indicate that the second device can share a connection; Sending a second message to the second device based on the first message, where the second message is used to indicate that the first device can share the connection, and the first device sets the second device as a management device; receiving information from the third device of the second device and entering a sharing mode; receiving a management instruction from the second device, and determining whether to establish a sharing connection with the third device based on the management instruction; The information of the third device includes address information and / or name information of the third device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

10. The method according to claim 9, characterized in that The receiving a management instruction from the second device and determining whether to establish a sharing connection with the third device based on the management instruction includes: When the management instruction is a sharing start instruction, receiving a connection request from the third device and a sharing start instruction from the second device, and establishing a sharing connection with the third device; When the management instruction is a sharing termination instruction, the sharing mode is exited.

11. The method according to claim 9 or 10, characterized in that After receiving the information of the third device from the second device and entering the sharing mode, the method further includes: Setting a time range for entering the sharing mode; If no connection request is received from the third device within the time range, exit the sharing mode.

12. The method according to claim 9 or 10, characterized in that The method further comprises: When the management instruction is a sharing start instruction, device list information is fed back to the second device based on the information of the third device.

13. A second device, characterized in that: include: A connection module, configured to establish a pairing connection with the first device; a transceiver module, configured to send a first message to the first device, and receive a second message sent by the first device based on the first message, wherein the first message is used to indicate that the second device can share a connection, and the second message is used to indicate that the first device can share a connection, and the first device sets the second device as a management device; The transceiver module is also used for: Sending the first message to a third device, sending information about the third device fed back by the third device based on the first message to the first device, and sending information about the first device to the third device; receiving connection information fed back by the third device based on information of the first device, and sending a management instruction to the first device based on the connection information; The information of the third device includes address information and / or name information of the third device; The information of the first device includes at least one of address information, name information, device form, device type, and device information of the first device; The connection information includes first connection information and second connection information, the first connection information is used to indicate that the third device agrees to establish a sharing connection with the first device, and the second connection information is used to indicate that the third device refuses to establish a sharing connection with the first device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

14. The second device according to claim 13, characterized in that The transceiver module is also used for: A third message is sent to the first device, where the third message is used to instruct the first device to prohibit being scanned.

15. The second device according to claim 13, characterized in that The transceiver module is also used for: A fourth message is sent to the first device, where the fourth message is used to instruct the first device to resume being scanned.

16. The second device according to any one of claims 13 to 15, characterized in that The transceiver module is used for: When the connection information is the first connection information, sending a sharing start instruction to the first device; When the connection information is the second connection information, a sharing termination instruction is sent to the first device.

17. The second device according to any one of claims 13 to 15, characterized in that The transceiver module is also used for: When the connection information is the first connection information, device list information based on information feedback from the third device is received from the first device, and permission information of the third device is changed based on the device list information, where the permission information includes management permission and / or usage permission.

18. The second device according to any one of claims 13 to 15, characterized in that The transceiver module is also used for: A third message is sent to the first device, where the third message is used to instruct the first device to prohibit being scanned.

19. The second device according to any one of claims 13 to 15, characterized in that The transceiver module is also used for: A fourth message is sent to the first device, where the fourth message is used to instruct the first device to resume being scanned.

20. The second device according to claim 17, characterized in that The device list information includes at least one of address information, name information, authority information, and connection status of devices paired with the first device.

21. A first device, characterized in that: include: A connection module, configured to establish a pairing connection with a second device; a transceiver module, configured to receive a first message from the second device, and send a second message to the second device based on the first message; receiving information from the third device of the second device and entering a sharing mode; receiving a management instruction from the second device, and determining whether to establish a sharing connection with the third device based on the management instruction; The first message is used to indicate that the second device can share the connection, the second message is used to indicate that the first device can share the connection, and the first device sets the second device as a management device; The information of the third device includes address information and / or name information of the third device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

22. The first device according to claim 21, characterized in that The transceiver module is also used for: A third message is received from the second device, where the third message is used to instruct the first device to prohibit scanning.

23. The first device according to claim 21, characterized in that The transceiver module is also used for: A fourth message is received from the second device, where the fourth message is used to instruct the first device to resume being scanned.

24. The first device according to any one of claims 21 to 23, characterized in that The transceiver module is used for: When the management instruction is a sharing start instruction, receiving a connection request from the third device and a sharing start instruction from the second device, and establishing a sharing connection with the third device; When the management instruction is a sharing termination instruction, the sharing mode is exited.

25. The first device according to any one of claims 21 to 23, characterized in that The first device further includes a setting module, which is configured to: Setting a time range for entering the sharing mode; If no connection request is received from the third device within the time range, exit the sharing mode.

26. The first device according to any one of claims 21 to 23, characterized in that The transceiver module is also used for: When the management instruction is a sharing start instruction, device list information is fed back to the second device based on the information of the third device.

27. A third device, characterized in that: include: a receiving module, configured to receive a first message from a second device, feed back information about the third device to the second device based on the first message, and receive information about the first device from the second device; a sending module, configured to feed back connection information determined based on the information of the first device to the second device, wherein the connection information is used by the second device to send a management instruction to the first device based on the connection information; The information of the third device includes address information and / or name information of the third device; The information of the first device includes at least one of address information, name information, device form, device type, and device information of the first device; The connection information includes first connection information and second connection information, the first connection information is used to indicate that the third device agrees to establish a sharing connection with the first device, and the second connection information is used to indicate that the third device refuses to establish a sharing connection with the first device; The management instruction includes a sharing start instruction and a sharing end instruction, wherein the sharing start instruction is used to instruct the first device to start establishing a sharing connection with the third device, and the sharing end instruction is used to instruct the first device to terminate establishing a sharing connection with the third device.

28. The third device according to claim 27, characterized in that The sending module is used for: determining the connection information based on the information of the first device; When the connection information is the first connection information, sending the first connection information to the second device and sending a connection request to the first device; When the connection information is the second connection information, the second connection information is sent to the second device.

29. A control system, characterized in that: comprising the second device according to any one of claims 13 to 20 and the first device according to any one of claims 21 to 26; The second device is coupled to the first device.

30. A sharing system, characterized in that: comprising a second device according to any one of claims 13 to 20, a first device according to any one of claims 21 to 26, and a third device according to claim 27 or 28; The first device, the second device, and the third device are coupled to each other.

31. A computer-readable storage medium having instructions stored therein, characterized in that: When the instructions are executed on a computer, the instructions are used to execute the method according to any one of claims 1 to 12.

32. A computer program product comprising instructions, characterized in that: When the instructions are executed on a computer or a processor, the computer or the processor is caused to implement the method according to any one of claims 1 to 12.

Images