WO2023220853A1

WO2023220853A1 - Service operation method and apparatus, and chip, storage medium and computer program

Info

Publication number: WO2023220853A1
Application number: PCT/CN2022/092973
Authority: WO
Inventors: 张军
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-05-16
Filing date: 2022-05-16
Publication date: 2023-11-23

Abstract

Provided are a service operation method and apparatus, and a chip, a storage medium and a computer program. The service operation method comprises: a first device sending a first request, wherein the first request is used for requesting a second device to perform a service handover. In the embodiments of the present application, a first device may hand over a service of the first device to a second device on the basis of a first request, such that the execution of the service performed by the first device can be automatically continued with the current progress on the second device, thereby reducing user operations and improving the user experience.

Description

Business operation methods, devices, chips, storage media and computer programs

Technical field

The present application relates to the field of communication technology, and more specifically, to a service operation method, device, chip, storage medium and computer program.

Background technique

With the development of communication technology, interactions between multiple electronic devices owned by users have become more and more frequent. In some scenarios, screen projection can be performed between multiple devices of the user, for example, mobile phone applications/services can be displayed on a car device.

However, when displaying screens between devices, users need to perform multiple manual operations. Taking the application/service of a mobile phone to a car-mounted device as an example, the user needs to select the trigger screen casting function on the mobile phone, manually establish a connection between the mobile phone and the car-mounted device, or even manually drag the progress of the application/service of the car-mounted device. As for the location corresponding to the mobile application/service, etc., the overall operation is complicated and the user experience is poor.

Contents of the invention

This application provides a business operation method, device, chip, storage medium and computer program. Various aspects involved in the embodiments of this application are introduced below.

In a first aspect, a service operation method is provided, including: a first device sending a first request, where the first request is used to request a second device to perform service connection.

In a second aspect, a service operation method is provided, including: a second device receiving a second request, where the second request is used to request the second device to perform service connection.

In a third aspect, a service operation method is provided, including: a cloud server receiving a first request sent by a first device, where the first request is used to request a second device to perform service connection.

In a fourth aspect, a service operation device is provided. The device is configured on a first device. The device includes: a first sending module for sending a first request. The first request is used for requesting a second device to perform a service operation. Business continues.

In a fifth aspect, a service operation device is provided. The device is configured on a second device. The device includes: a first receiving module for receiving a second request, and the second request is used for requesting the second The device performs business connection.

In a sixth aspect, a business running device is provided, including a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is used to call the computer program in the memory so that the The device performs some or all of the steps in the methods of the above aspects.

In a seventh aspect, embodiments of the present application provide a communication system, which includes the above-mentioned service operation device. In another possible design, the system may also include other devices that interact with the business operation device in the solution provided by the embodiments of this application.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium that stores a computer program. The computer program causes a business operation device to execute some or all of the steps in the methods of the above aspects. .

In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a business operation device to execute Some or all of the steps in the methods of the above aspects. In some implementations, the computer program product can be a software installation package.

In a tenth aspect, embodiments of the present application provide a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

In the embodiment of the present application, the first device can connect the service of the first device to the second device based on the first request, so that the service performed on the first device can automatically continue to be executed on the second device following the current progress, reducing user operations. , thereby improving user experience.

Description of the drawings

FIG. 1 is an architectural example diagram of a wireless communication system applicable to embodiments of the present application.

Figure 2 is a schematic flowchart of a service operation method provided by an embodiment of the present application.

Figure 3 is a schematic flowchart of a service operation method provided by another embodiment of the present application.

Figure 4 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application.

FIG. 5 is a schematic flowchart of a possible implementation of step S420 in FIG. 4 .

Figure 6 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application.

Figure 7 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application.

Figure 8 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application.

Figure 9 is a schematic structural diagram of a service operation device provided by an embodiment of the present application.

Figure 10 is a schematic structural diagram of a service operating device provided by another embodiment of the present application.

Figure 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose and advantages of the present application clearer and clearer, the technical solutions in the present application will be described below in conjunction with the accompanying drawings.

With the rapid development of communication technology, more and more users can own multiple electronic devices. Driven by the networking and intelligence of electronic devices, interactions between multiple electronic devices owned by users have become increasingly frequent.

In scenarios where multiple electronic devices interact, screen projection can be performed between multiple devices of the user. Screen projection may refer to placing an application/service in a first device (for example, it may be called a delivery end) to a second device (for example, it may be called a receiving end) for display. For example, the mobile phone's applications/services are placed on the car's in-vehicle device for display, or the mobile phone's applications/services are placed on the TV for display, etc. In this example, the mobile phone is the first device, or is called the transmitting end; the car device or the TV is the second device, or is called the receiving end.

In some embodiments, the applications/services in the first device may refer to multimedia applications/services such as audio, video, and calls in the first device. In some embodiments, the application/service in the first device may refer to an application/service in the first device for controlling an Internet of Things (IoT) device.

In some embodiments, when the first device and the second device perform screencasting, the applications/services in the first device can continue to be displayed on the second device, but the actual applications/services displayed on the second device are associated with each other. The data flow is still in the first device, that is, the data flow associated with the application/service in the first device will not be transmitted to the second device.

In the related art, there are various technical solutions for realizing screen projection display between the first device and the second device. The following are examples of two common technical solutions for screen projection.

In one technical solution, after the first device establishes a screen projection connection with the second device, the second device is only used to display the main interface screen of the first device. When using this technical solution, the user needs to manually trigger the screen casting function on the first device, and then manually establish a screen casting connection between the first device and the second device, so that the main interface screen of the first device is displayed on the second device. on the second device. In addition, when this technical solution is adopted, the usage status of the application/service on the first device cannot be synchronized to the second device. If the user wants to continue using the application/service on the first device, he needs to perform active operations on the second device, for example, reopen the corresponding application/service on the second device, and change the application/service Drag and drop the progress to the position corresponding to the application/service of the first device, etc.

In another technical solution, after the first device establishes a screen projection connection with the second device, the second device can only be used to display the content currently displayed on the screen of the first device, for example, by recording the screen on the second device. Display content currently displayed on the first device. When this technical solution is adopted, the function of the second device is only equivalent to the projection device. The screen projection simply projects the screen of the first device to the second device. The user still needs to perform some additional operations manually, such as on the first device. Trigger the screen casting function on the device, manually establish the screen casting connection between the first device and the second device, etc. In addition, when using this technical solution, if the first device stops running certain applications/services, for example, because the screen is turned off or shut down, the second device will also stop displaying the screen content of the first device.

Taking the first device as a mobile phone and the second device as an in-vehicle device of a car as an example, the technical solution of screen projection display in the related art will be exemplified below.

As cars become more connected and intelligent, cars can interact with mobile phones through interconnection and collaboration. At present, the main scenarios for car-machine collaboration are digital car keys, car-machine screen projection, etc. In some embodiments, the smart cockpit of a car can provide users with in-vehicle applications and services (for example, Apple's CarPlay, Google's Android Auto, etc.), and realize digital car keys, car screen projection, etc. through the provided in-vehicle applications and services. In some embodiments, in-vehicle applications and services may use the digital car key protocol of the Car Connectivity Consortium (CCC) or the Miracast screencasting protocol (a screencasting protocol developed by the Wireless Fidelity (WiFi) Alliance). ) and other solutions for digital car keys and multimedia content delivery on mobile phones and cars, realizing functions such as digital car keys and car screen projection.

Taking car screen projection as an example, in some embodiments, when a user interacts with a mobile phone and a vehicle-mounted device through vehicle-mounted applications and services, both the mobile phone and the vehicle-mounted device are presented in the form of an application (APP). The user can project the mobile APP on the screen of the vehicle-mounted device through some manual operations (that is, the vehicle-mounted device is used to display the main interface screen of the phone). In this case, if a piece of music is being played on the user's mobile phone and the user wants to continue playing the music on the car device, the user needs to open the car app on the car device, select the same music in the car app, and drag to play Move the progress bar to the corresponding position, set the same playback mode, etc., so that the music on the mobile phone can continue to be played on the car device. In other embodiments, the user can project the mobile phone screen onto the screen of the vehicle-mounted device through some manual operations (that is, the vehicle-mounted device is only used to display the content currently displayed on the mobile phone screen). In this case, the user still needs to trigger the screencasting function on the mobile phone and establish a screencasting connection between the mobile phone and the vehicle-mounted device. The overall operation is relatively complicated, and if the phone stops playing the music because the screen is turned off or shut down, , the car device will also terminate playback immediately.

In summary, when performing screen projection between devices, the user needs to perform multiple manual operations, which results in a poor user experience.

In addition, the existing technology can only project the applications/services of the first device to the second device for sharing. With the diversification of user needs, users have demands for interconnection and collaboration between the first device and the second device. It can be more complicated. Therefore, a new business model is urgently needed to meet the diversification of user needs.

In order to solve the above problems, embodiments of the present application provide a service operation method, device, chip, storage medium and computer program to reduce user operations and improve user experience.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings provided in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency Frequency division duplex (FDD) system, LTE time division duplex (TDD), WiFi system, Bluetooth system, etc. The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication systems, and so on. The following is an exemplary description of a wireless communication system applicable to the embodiment of the present application with reference to FIG. 1 .

Referring to Figure 1, Figure 1 is an architectural example diagram of a wireless communication system 100 that can be applied to embodiments of the present application. As shown in FIG. 1 , the wireless communication system 100 may include a first device 110 and a second device 120 . The first device 110 can communicate with the second device 120 . In some embodiments, the first device 110 and the second device 120 may establish a connection for communication through a wired or wireless network (eg, Bluetooth or mobile network).

Figure 1 exemplarily shows a first device 110 and a second device 120, but the embodiment of the present application is not limited thereto. Optionally, the wireless communication system 100 may include multiple first devices and/or second devices. For example, the first device may select one of the multiple second devices to establish a connection for subsequent communication.

In some embodiments, the first device and the second device in the embodiments of the present application may be referred to as the first terminal device and the second terminal device respectively. Among them, the terminal equipment can also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station , remote terminal, mobile device, user terminal, terminal, wireless communications device, user agent or user device.

The first device and the second device in the embodiment of the present application may be devices that provide voice and/or data connectivity to users, and may be used to connect people, things, and machines, such as handheld devices and vehicle-mounted devices with wireless connection functions. wait. Illustratively, the first device and the second device in the embodiments of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a notebook computer, a handheld computer, a mobile internet device (mobile internet device, MID), or a mobile Internet device (MID). Wearable devices, IoT devices, virtual reality (VR) devices, augmented reality (AR) devices, etc. Optionally, IoT devices may include smart vehicles, smart TVs, or other devices with screen display capabilities. For example, when the first device or the second device is a smart vehicle, the smart vehicle may be, for example, a family car, a taxi, a bus, a motorcycle, etc. This is not specifically limited in the embodiments of the present application.

In the embodiment of the present application, the scene in which the first device and the second device are located is not limited. For example, the first device and the second device may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted.

Continuing to refer to FIG. 1 , in some embodiments, the wireless communication system 100 may also include a cloud server 130 , and the cloud server 130 may refer to a server in a cloud platform, for example. The cloud server 130, the first device 110, and the second device 120 can establish connections with each other through a wireless network (eg, Bluetooth, mobile network, WiFi). Optionally, the connection method between the cloud server 130 and the first device 110 may be different from the connection method between the cloud server 130 and the second device 120. For example, the cloud server 130 and the first device 110 establish a connection through WiFi. , and the cloud server 130 and the second device 120 establish a connection through the mobile network. Optionally, the connection method between the cloud server 130 and the first device 110 may be the same as the connection method between the cloud server 130 and the second device 120, for example, the cloud server 130 and the first device 110, and the cloud server 130 and the second device 110. The second device 120 can establish a connection through the mobile network.

In some embodiments, the cloud server 130 may store data streams associated with applications/services in the first device 110 and/or the second device 120 . In this scenario, data transmission between the first device 110 and the second device 120 can be implemented through the cloud server 130 .

In some embodiments, the first device 110 and/or the second device 120 can access the cloud server 130 by logging in with an account. For example, the same data or resources stored on the cloud server 130 can be accessed by logging in with the same account.

It should be understood that the vehicle-mounted equipment mentioned in the embodiments of this application may refer to the abbreviation of vehicle-mounted infotainment products installed on the car. In-vehicle equipment can functionally realize information communication between people and vehicles, and between vehicles and the outside world (for example, vehicles and vehicles, vehicles and mobile phones, etc.). In some embodiments, the vehicle-mounted device may also be called a vehicle-mounted terminal, a vehicle-mounted system, a vehicle machine, a central control system, a navigation system, a navigation screen, etc., which are not limited in the embodiments of the present application. In the embodiment of the present application, the vehicle-mounted equipment may also be replaced by vehicle equipment, vehicle-machine equipment, etc., and the present application is not limited to this.

It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

The communication method provided by the embodiment of the present application will be described in detail below in conjunction with the system architecture shown in Figure 1.

Figure 2 is a schematic flowchart of a service operation method provided by an embodiment of the present application. The method shown in Figure 2 is described from the perspective of interaction between the first device and the second device (or cloud server). The first device and the second device may be, for example, the first device 110 and the second device 120 in FIG. 1 , and the cloud server may be, for example, the cloud server 130 in FIG. 1 . Specifically, the first device or the second device may refer to, for example, a mobile phone, a tablet computer, a notebook computer, a vehicle-mounted device, a television, and other devices. The embodiments of the present application are not limited to this, as long as the first device and the second device can communicate with each other. Just realize business continuity or screen projection. As a specific example, the second device may refer to a vehicle-mounted device, and the first device may refer to a terminal device that performs business connection with the vehicle-mounted device, such as a mobile phone, a laptop, etc. The method shown in Figure 2 may include step S210, which will be described in detail below.

In step S210, the first device sends a first request, and the first request is used to request the second device to perform service connection.

Service connection refers to connecting the services of the first device (for example, running applications, services, etc.) of the first device to the second device, so that the services of the first device are automatically switched (or transferred) to the second device. And the service can continue to be automatically executed on the second device according to the current progress. In other words, service connection allows the services of the first device to be automatically switched to the second device, ensuring that users can seamlessly continue ongoing services between different devices.

Based on this, in some embodiments, service connection can be understood as service switching, service transfer, service relay, etc., connecting/switching/transferring/relaying the service of the first device to the second device, so that the user can connect to different devices on different devices. seamlessly continue ongoing business.

It should be understood that the first device and the second device being able to realize service connection may mean that the first device and the second device can support the service connection service (or support the service connection function, support the service connection event, etc.). When the first device and the second device support the service connection service, the first device can connect the business (application, service, etc.) of the first device to the second device. In some embodiments, the business connection service can be replaced by business connection, and the embodiments of this application do not make a clear distinction between this.

In some embodiments, the first device may directly send the first request to the second device to request the second device to perform service connection. In some embodiments, the first device may send the first request to the cloud server. After the cloud server determines the corresponding second request based on the first request, the second request is sent to the second device. The second request is used to request The second device performs service connection. This will be described in detail later and will not be described here.

In some embodiments, the services of the first device may refer to services running on the first device, such as running applications or services. As a specific example, the service of the first device may refer to a video (or music, call, etc.) being played on the first device, or an application that is playing the video (or music, call, etc.). As another specific example, the service of the first device may refer to an application or service running on the first device for controlling the IoT device.

In some embodiments, the service connection implementation process may include: a discovery process of the second device (or a search process of the second device), a connection process between the first device and the second device, and a data transmission process. The relevant description of the implementation process of business connection can be found later, and will not be repeated here.

In some embodiments, the service connection is based on a local communication connection between the first device and the second device. In some embodiments, service connection is performed based on a cloud server, which is not limited by the embodiments of the present application. The connection method and data transmission method corresponding to the service connection between the first device and the second device will be described in detail later and will not be described here.

It should be understood that the local communication connection method may mean that the first device and the second device transmit and receive information through the local communication connection between them without forwarding through the server. Optionally, the first device and the second device can establish a local communication connection using Bluetooth, WiFi, infrared and other technologies.

In some embodiments, the first request may include the type of service connection. The type of service connection refers to the type of service that the device (for example, the first device, the second device, etc.) supports the connection. For example, the type of service connection may include one or more of the following types: Video services This application does not specifically limit the connection, audio service connection, call service connection, IoT device control service connection, etc., that is, the types of service connection may also include other types besides the listed ones. That is to say, the first request may be used to indicate that the type of service connection is a video-type service connection, or the first request may be used to indicate that the type of the service connection is an audio-type service connection. Of course, the present application is not limited to this. For example, the type of service connection may also be a call-type service connection, or an IoT device control-type service connection, etc.

In some embodiments, the first request may include identification information of a service that supports connecting the service. In other words, the first device may specify a specific service (for example, a specific application) for performing the service connection in the first request. Optionally, the identification information of the service that supports the connection of the service may include the type of application that supports the connection of the service, such as a video application, a call application, etc.; or the identification information of the service that supports the connection of the service may include the type of application that supports the connection of the service. The specific application for business connection, such as the first application.

In some embodiments, the first device may indicate a specific application that supports the service connection by carrying an application identifier (for example, the first application is the A application) in the first request. In some embodiments, the first device may indicate a specific application that supports the service connection by carrying the application ID in the first request (for example, the application ID of the first application is 10001).

In some embodiments, the first request may include both a type of service connection and identification information of a service that supports connection of the service. That is to say, the first device can specify the type of business connection and the specific service at the same time in the first request, indicating the corresponding type of business connection and the specific service (for example, a specific application) that supports the business connection.

In some embodiments, the first request may include (or carry) synchronization information of service connection. For example, when the type of service connection is a video or audio service connection, in order to continue (seamlessly continue) the playback of the video or audio on the second device, the first request may include the streaming media information of the current video or audio. and play time.

In some embodiments, the first request may include first indication information, and the first indication information may be used to indicate the transmission channel type of the service connection supported by the first device. The embodiments of this application do not limit the types of transmission channels for service connections that the first device can support. For example, the types of transmission channels for service connections that the first device can support may include one or more of the following: Bluetooth, low power consumption Bluetooth (bluetooth low energy, BLE), ultra wide band (ultra wide band, UWB), WiFi point-to-point (peer to peer, P2P), WiFi LAN, cellular network, etc.

In some embodiments, the first request may include identification information of the second device. For example, when the first device sends a first request to the cloud server, the first request may include the identification information of the second device, so that the cloud server sends the second request to the second device.

In some embodiments, the first device and the second device may be of different types. For example, the first device may be a handheld device (such as a mobile phone), and the second device may be a vehicle-mounted device. Alternatively, the first device may be a handheld device, and the second device may be an Internet of Things device capable of business connection, such as a smart TV. Of course, the application is not limited to this. For example, the first device may be a vehicle-mounted device, and the second device may be a handheld device, etc.

In the embodiment of this application, the first device can connect the service of the first device to the second device based on the first request, so that the service performed by the first device can automatically continue to be executed on the second device following the current progress, reducing user operations. Thereby improving the user experience.

The communication connection method and data transmission process during service connection between the first device and the second device will be introduced in detail below with reference to Figures 3 and 4.

Figure 3 is a schematic flowchart of a service operation method provided by another embodiment of the present application. In the embodiment shown in FIG. 3 , the service connection is based on the local connection mode between the first device and the second device. As shown in Figure 3, the method may include steps S310 to S330.

In step S310, the first device sends a first request to the second device. The first request is used to request the second device to perform service connection. Correspondingly, the second device receives the second request, which is the first request sent by the first device.

For details of step S310, please refer to the previous description of step S210, which will not be described again here.

In step S320, the second device sends a response message to the first request (or a response message to the second request) to the first device. The response message is used to indicate starting the business connection service.

Step S310 and step S320 can be understood as a connection process between the first device and the second device. The response message to the first request sent by the second device can be used to indicate that the second device has started the business connection service. In other words, the response message to the first request can be used to indicate that the connection between the two is successful and subsequent operations can be performed. Data is transferred. However, the embodiments of the present application are not limited to this. In some embodiments, the response message of the first request sent by the second device can also be used to indicate a failure to start the service connection, that is, the connection was not successfully established this time.

In step S330, the first device and the second device perform data transmission for service connection.

The first device and the second device perform data transmission for service connection, so that the service of the first device can be continued on the second device. For example, the first device sends a multimedia stream of video or audio connection to the second device, so that the video or audio connection can be continued on the second device. The audio continues playing on the second device following the playback progress of the first device.

When the first device and the second device perform service connection based on the local connection mode, the data corresponding to the service connection may be sent by the first device to the second device.

In some embodiments, the second device may select a corresponding transmission channel type according to the type of service connection and/or the connected application, for example, the optimal transmission channel corresponding to the service connection type and/or the connected application. For example, if the type of service connection is video service connection or video application, WiFi P2P or WiFi LAN can be used as the transmission channel (or WiFi P2P or WiFi LAN connection is used); if the type of service connection is For audio business continuity or audio applications, BLE or Bluetooth can be used as the transmission channel (or BLE or Bluetooth connection).

The first device and the second device perform business connection data transmission based on local connection, with fast transmission speed and high transmission security.

Figure 4 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application. In the embodiment shown in Figure 4, service connection is performed based on the cloud server. As shown in Figure 4, the method may include steps S410 to S430.

In step S410, the first device sends a first request to the cloud server. The first request is used to request the second device to perform service connection.

In some embodiments, the first request may include identification information of the second device, and the identification information is used to indicate information of the second device for performing service connection.

In addition to the identification information of the second device, the first request may also include other information. For other information included in the first request, please refer to the related content of the first request mentioned above, which will not be described again here.

In step S420, the cloud server sends a second request to the second device.

The embodiment of this application does not specifically limit the implementation of step S420. In some embodiments, the second request sent by the cloud server to the second device is the first request. In other words, the cloud server sending the second request to the second device may mean that after the first device sends the first request to the cloud server, the cloud server forwards the first request to the second device. In some embodiments, the second request sent by the cloud server to the second device may be determined by the cloud server based on the first request. In other words, the cloud server sending the second request to the second device may mean that the first device may send the first request to the cloud server, and the cloud server generates a corresponding second request based on the first request and sends it to the second device.

For example, Figure 5 shows a possible implementation of step S420. Referring to FIG. 5 , step S420 may include steps S422 to S426.

In step S422, the first device sends a first request to the cloud server. The first request is used to request the second device to perform service connection. The information of the first request may include, for example, the device identification of the second device.

In some embodiments, the first request may include a type of service connection and/or identification information of a service that supports connection of the service.

In some embodiments, the first request may include synchronization information of service connection.

In step S424, the cloud server determines the second request according to the first request.

For example, the cloud server may generate a second request based on the first request sent by the first device. The second request may not include the device identification of the second device, but may include other information in the first request other than the device identification of the second device. information.

In step S426, the cloud server sends a second request to the second device. The second request is used to request the second device to perform service connection. The second request may include, for example, the type of service connection, identification information of a service that supports the service connection, synchronization information of the service connection, etc.

Optionally, before step S426, step S425 may also be included. In step S425, the cloud server sends a response message to the first request to the first device. The response message may be used to indicate that the service connection of the cloud server is started, for example, it is started successfully. Alternatively, the response message may be used to indicate that the cloud server's business connection service has failed to start.

Regarding other contents of step S420, such as the information included in the second request, please refer to the previous description of the information included in the first request in S210, which will not be described again here.

In step S430, the second device sends a response message of the second request to the cloud server, where the response message is used to indicate starting the business connection service. In other words, the second device can send the response message of the first request to the first device through the cloud server. The response message to the first request sent by the second device may be used to indicate that the second device has started the business connection service. In some embodiments, the response message to the first request sent by the second device may also be used to indicate failure to start the business connection service.

In step S440, the cloud server and the second device perform data transmission for business connection.

The cloud server and the second device perform service connection data transmission, so that the service of the first device can be continued on the second device. For example, the cloud server sends a multimedia stream of video or audio connection to the second device, so that the video or audio can be continued on the second device. The second device continues to play according to the playback progress of the first device.

In this embodiment, when the service connection between the first device and the second device is performed based on the cloud server, on the one hand, the cloud server is used to respond to the service connection request of the first device; on the other hand, after the response is completed, the cloud server It is also used for data transmission for business connection with the second device.

In some embodiments, step S440 may be replaced by the first device and the second device performing data transmission for service connection. That is to say, when the service connection between the first device and the second device is performed based on the cloud server, the cloud server can only be used to respond to the service connection request of the first device. After the response is completed, the data transmission process corresponding to the actual service connection is It is completed by the first device and the second device, that is, the data corresponding to the actual service connection is sent from the first device to the second device, and the cloud server does not participate in the actual transmission of the final data.

The first device and the second device perform business connection data transmission based on the cloud server, which can save local storage space.

It should be understood that in the embodiments of Figures 3 and 4, the steps are listed to facilitate understanding of the technical solutions of the embodiments of the present application, but not all the steps listed are necessary. In actual implementation, the required steps may only include the steps listed. some of the steps, or may include steps other than those listed.

As mentioned above, the implementation process of service connection may also include a discovery process of the second device. The embodiment of this application does not specifically limit the discovery process between the first device and the second device. By way of example, the discovery process between the first device and the second device is introduced below with reference to FIG. 6 . As shown in Figure 6, in some embodiments, the discovery process between the first device and the second device may include step S610 and step S620. It should be understood that step S610 and step S620 may be performed before step S210 is performed, for example. Step S610 and step S620 are described in detail below.

In step S610, the first device sends a third request, and the third request is used to discover a device that supports service connection.

In some embodiments, the third request is sent by the first device to the second device. In some embodiments, the first device may send the third request to a plurality of devices, including a second device, and the second device may, for example, refer to a target device among the plurality of devices.

In some embodiments, the third request is sent by the first device when it determines that service connection is required, and whether service connection is required is determined by the first device based on the second information.

The embodiment of this application does not specifically limit the content of the second information. Exemplarily, the second information may include one or more of the following information: an application/service running on the first device, a type of application/service running on the first device, and auxiliary information.

The application/service running on the first device may refer to the specific application/service running. For example, the first device is running application A.

In some embodiments, the type of application/service being run by the first device may mean that the type of application/service is a video application, an audio application, or an IoT device control application, etc. In some embodiments, the type of application/service being run by the first device may mean that the type of application/service is an application/service that supports business connection, or an application/service that does not support business connection.

For example, the auxiliary information may include one or more of the following information: the enabling status of the business continuity mode of the first device, the status of the application/service running on the first device, and the status of the first device and the second device. Positional relationship. As an example, whether the service connection is required can be determined according to the enabled status of the service connection mode of the first device. For example, when the service connection mode of the first device is enabled, it is determined that the service connection is required; or, in the first device, the service connection mode is enabled. When the service connection mode is enabled and the application running on the first device is a video application, it is determined that service connection is required. As another example, whether business continuity is required can be determined based on the status of the application/service running on the first device. For example, the application running on the first device is an IoT device-type application. When a change in the status of the application is detected, (For example, the application running on the first device is a digital car key application, and when a change in the status of the digital car key is detected), it is determined that business connection is required. As another example, whether service connection is required can be determined based on the location relationship between the first device and the second device, for example, when the distance between the first device and the second device is less than a certain threshold or the spatial location relationship between the two. When a certain condition is met (for example, the first device is located inside the second device, the first device is located at the target location of the second device, etc.), it is determined that service connection is required; or, between the first device and the second device, When the distance is less than a certain threshold or the spatial position relationship between the two meets a certain condition, and the type of application running on the first device is a type that supports service connection, it is determined that service connection is required.

In some embodiments, the third request may be sent in a unicast or multicast manner. For example, the third request may be sent in a Bluetooth broadcast message.

In some embodiments, the third request may include a type of service connection, and/or identification information of a service that supports connection of the service.

In step S620, the second device sends a first response to the first device, where the first response is used to indicate that the second device supports connecting to the service.

In some embodiments, the business connection service information may include device information of the second device, and/or business connection service capability information of the second device. The device information of the second device may include identification information of the second device, such as a device identification of the second device. The business connection service capability information of the second device may include information on the type of business connection supported by the second device and/or application information associated with the business connection service supported by the second device. For example, the business connection service capability information of the second device may It is: the type of business connection supported by the second device includes video/audio/IoT device control type business connection services; or, the business connection service capability information of the second device can be: the application associated with the business connection service supported by the second device Identified as A application or APP ID is 10001.

In some embodiments, in the case where the first device sends a third request to multiple devices, if the first device receives the first response sent by the multiple devices, the first device may determine the second device based on the first response. (target device).

In some embodiments, the first response may also be used to indicate the transmission channel type of the service connection supported by the second device. For example, the transmission channel type of the service connection supported by the second device includes Bluetooth, BLE, UWB, WiFi P2P, and cellular network. wait.

It should be understood that when the first device determines to perform service connection on the second device, the first device may run an application that can perform service connection, such as related applications for playing video, audio, or controlling IoT devices.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, two specific examples are given below, taking service connection between a mobile phone and an on-board device of a car as an example. It should be understood that if the mobile phone service is continued on the vehicle-mounted device (for example, after the user gets in the car, the videos, music, calls, etc. currently playing on the phone are streamed to the screen of the vehicle-mounted device), the first device refers to the mobile phone, and the second device refers to the mobile phone. The second device refers to the on-board equipment of the car; if the business in the car is continued on the mobile phone (for example, when the user gets off the car, the videos, music, calls, etc. currently playing in the car are streamed to the mobile phone), the first device refers to the on-board equipment of the car, and the second device refers to the mobile phone.

Example 1 (based on local connection method):

Figure 7 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application. Referring to Figure 7, the service operation method may include steps S710 to S760.

In step S710, an application capable of business connection is run on the first device, such as an application for playing video/audio, controlling IoT devices, etc.

In step S720, the first device sends a service connection discovery request (please refer to the third request mentioned above) to discover other devices that support the business connection service, such as the second device.

In some embodiments, the first device may enable the business continuity mode based on the currently running application/application type and auxiliary conditions (for example, the user operates on the first device to enable the business continuity mode, detects changes in the status of the application on the first device, the first device and The location relationship of the second device, etc.) determines the need for service connection discovery. Specifically, when the first device is a mobile phone and the second device is a vehicle-mounted device of a car, the auxiliary conditions may be, for example, that the user operates on the mobile phone to activate the business connection mode, detects a change in the status of the digital car key on the mobile phone, or the mobile phone is in the car. wait.

In some embodiments, the first device may send the service connection discovery request in a broadcast or unicast manner, for example, sending a service connection discovery request in a Bluetooth broadcast message.

In some embodiments, the first device may specify the type of service connection in the service connection discovery request message to discover devices that meet the connection service capabilities of the corresponding type. As an example, in order to discover devices that support video/music/IoT device control connection service capabilities, the service connection discovery request message may carry discovery conditions for video/music/IoT device control connection service capabilities.

In some embodiments, the first device may specify a specific application in the service connection discovery request to discover devices that support the specific application for service connection.

In some embodiments, the first device may simultaneously specify the type of connection service and the specific application in the service connection discovery request to discover devices that support the corresponding type of connection service capability and the specific application that supports the connection service.

In step S730, the second device sends a service connection discovery response to provide service connection service information of the second device.

In some embodiments, the business connection service information of the second device may include device information and/or business connection service capability information of the second device. The business connection service capability information of the second device may include, for example, the type of business connection service supported by the second device and the identification information of the service supported by the second device to connect the business.

In some embodiments, the service connection discovery response message may indicate the transmission channel type of the service connection. For example, the transmission channel type of the service connection is Bluetooth, BLE, UWB, WiFi P2P, WiFi LAN, cellular network, etc.

In step S740, the first device initiates a service connection request to the second device (please refer to the first request mentioned above), requesting service connection on the second device.

According to the business connection service information of the second device obtained in step S730, the first device sends a message of a message type of a service connection request to the second device to perform service connection.

In some embodiments, the first device may specify the type of service connection in the service connection request. For example, the business connection request message carries information about the video/audio/IoT device control connection service, indicating that this type of business connection service is to be performed.

In some embodiments, the first device may specify a specific application for service connection in the service connection request.

In some embodiments, the first device may simultaneously specify the type of service connection and a specific application in the service connection request, indicating a corresponding type of connection service and a specific application that supports the connection service.

In some embodiments, the first device may also carry service connection synchronization information in the service connection request. For example, in order to continue the playback of video/audio on the on-board device of the car, the request message carries the streaming media information of the current video/music and play time.

In some embodiments, the first device may indicate the transmission channel type of the service connection in the service connection request. For example, the transmission channel type of the service connection is Bluetooth, BLE, UWB, WiFi P2P, WiFi LAN, cellular network, etc.

In step S750, the second device sends a service connection response, indicating that the service connection service is successfully started.

In step S760, data transmission for service connection is performed between the first device and the second device. The service on the first device is continued on the second device. For example, the first device sends a video/audio connected multimedia stream to the second device. .

In some embodiments, the second device can select the optimal transmission channel according to the type and/or application of the service connection. For example, video connection uses WiFi P2P/WiFi LAN connection, and audio connection uses BLE/Bluetooth connection.

Example 2 (based on cloud connection method):

Figure 8 is a schematic flowchart of a service operation method provided by yet another embodiment of the present application. Referring to Figure 8, the service operation method may include steps S810 to S880.

In step S810, the user account is logged in on the first device and applications capable of business connection are running, such as applications for playing video/audio, controlling IoT devices, etc.

In step S820, the first device sends a service connection discovery request (see the third request above) to discover other devices that support the business connection service.

In some embodiments, the first device may specify a specific application in the service connection discovery request to discover devices that support the specific application of the business connection service.

In step S830, the second device sends a service connection discovery response to provide service connection service information of the second device.

In some embodiments, the business connection service information of the second device may include device information and/or business connection service capability information of the second device. The service connection service capability information of the second device may include, for example, the type of service connection supported by the second device and the identification information of the service supported by the second device to connect the service. .

In step S840, the first device initiates a first service connection request to the cloud server, requesting the cloud server and the second device to perform service connection.

In some embodiments, the first device may carry the device identification of the second device in the first service connection request message (the device identification may be obtained, for example, according to the device information of the second device obtained in step S830), indicating that the service is to be performed. Secondary device for connecting services.

In some embodiments, the first device may specify the type of service connection in the first service connection request. For example, the first service connection request message carries information about the video/audio/IoT device control connection service, indicating that this type of service connection is to be performed.

In some embodiments, the first device may specify a specific application for service connection in the first service connection request.

In some embodiments, the first device may simultaneously specify the type of service connection and a specific application in the first service connection request, indicating a corresponding type of connection service and a specific application that supports the connection service.

In some embodiments, the first device may also carry service connection synchronization information in the first service connection request. For example, in order to continue the playback of video/audio on the vehicle-mounted device, the request message carries the streaming media information of the current video/music and play time.

In step S850, the cloud server sends a first service connection request response to the first device, indicating that the business connection service of the cloud server is successfully started.

In step S860, the cloud server initiates a second service connection request to the second device, requesting service connection on the vehicle. For example, the cloud server may send a service connection request to the second device according to the device identification of the second device obtained in step S840 to perform service connection.

In some embodiments, the first device may specify the type of service connection in the second service connection request. For example, the service connection request message carries information about the video/audio/IoT device control connection service, indicating that this type of service connection is to be carried out.

In some embodiments, the first device may specify a specific application for service connection in the second service connection request.

In some embodiments, the first device may simultaneously specify the type of service connection and the specific application in the second service connection request, indicating the corresponding type of connection service and the specific application that supports the connection service.

In some embodiments, the first device may also carry service connection synchronization information in the second service connection request. For example, in order to continue playing video/audio on the car end, the request message carries the streaming media information and playback time of the current video/music. .

In step S870, the second device sends a second service connection response, indicating that the service connection service is successfully started.

In step S880, data transmission for service connection is performed between the second device and the cloud server. The service on the first device is continued on the second device. For example, the cloud server sends a multimedia stream of video/audio connection to the second device.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 8 , and the device embodiments of the present application are described in detail below with reference to FIGS. 9 to 11 . It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.

Figure 9 is a schematic structural diagram of a service operation device provided by an embodiment of the present application. The service running device may be configured on the first device mentioned above. The service running device 900 shown in FIG. 9 may include a first sending module 910.

The first sending module 910 may be configured to send a first request, where the first request is used to request the second device to perform service connection.

Optionally, the service connection is based on a local communication connection mode between the first device and the second device.

Optionally, data corresponding to the service connection is sent from the first device to the second device.

Optionally, the service connection is based on the cloud server.

Optionally, the first sending module is further configured to: send the first request to the cloud server.

Optionally, data corresponding to the service connection is sent by the cloud server to the second device.

Optionally, the first request includes identification information of the second device.

Optionally, the first request includes a type of service connection, and/or identification information of a service that supports connection of the service.

Optionally, the first request includes synchronization information of service connection.

Optionally, the first request includes first indication information, and the first indication information is used to indicate the transmission channel type of the service connection supported by the first device.

Optionally, the device 900 shown in FIG. 9 also includes a first receiving module 920. The first receiving module 920 may be configured to receive a response message of the first request, and the response message of the first request is used to indicate starting the connection service of the business.

Optionally, the apparatus 900 shown in Figure 9 also includes a second sending module, used to send a third request, the third request is used to discover a device that supports connecting to the service; a second receiving module, used to receive a message sent by the second device. The first response is used to indicate that the second device supports connecting to the service.

Optionally, the third request is sent by the first device when it determines that service connection is required, and whether service connection is required is determined by the first device based on the second information.

Optionally, the second information includes one or more of the following information: an application running on the first device, a type of application running on the first device, and auxiliary information.

Optionally, the auxiliary information includes one or more of the following information: the enabling status of the service connection mode of the first device, the status of the application running on the first device, and the location relationship between the first device and the second device.

Optionally, the third request is sent in a unicast or multicast manner.

Optionally, the third request includes a type of service connection, and/or identification information of a service that supports connection of the service.

Optionally, the first response includes business continuity service information of the second device, and the business continuity service information includes device information of the second device, and/or business continuity service capability information of the second device.

Optionally, the first response is also used to indicate the transmission channel type of the service connection supported by the second device.

Optionally, the second device is a vehicle-mounted device.

Figure 10 is a schematic structural diagram of a service operating device provided by another embodiment of the present application. The service running device can be configured on the aforementioned second device. The service operation device 1000 shown in FIG. 10 may include a first receiving module 1010.

The first receiving module 1010 may be configured to receive a second request, where the second request is used to request the second device to perform service connection.

Optionally, the second request is a first request sent by the first device, and the first request is used to request the second device to perform service connection.

Optionally, the service connection is based on the cloud server.

Optionally, the first receiving module is further configured to: receive a second request sent by the cloud server, where the second request is determined by the cloud server based on the first request sent by the first device.

Optionally, the device 1000 shown in Figure 10 also includes a first sending module 1020. The first sending module 1020 may be configured to send a response message to the second request, and the response message to the second request is used to indicate starting a continuation service of the service.

Optionally, the apparatus 1000 in Figure 10 further includes a second receiving module, configured to receive a third request sent by the first device, where the third request is used to discover a device that supports connecting the service; and a second sending module, configured to send a request to the first device. A device sends a first response, and the first response is used to indicate that the second device supports connecting to the service.

Optionally, the third request is sent in a unicast or multicast manner.

Figure 11 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dashed line in Figure 11 indicates that the unit or module is optional. The device 1100 can be used to implement the method described in the above method embodiment. The device 1100 may be a chip, a first device or a second device.

Apparatus 1100 may include one or more processors 1110. The processor 1110 can support the device 1100 to implement the method described in the foregoing method embodiments. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

Apparatus 1100 may also include one or more memories 1120. The memory 1120 stores a program, which can be executed by the processor 1110, so that the processor 1110 executes the method described in the foregoing method embodiment. The memory 1120 may be independent of the processor 1110 or integrated in the processor 1110 .

Device 1100 may also include a transceiver 1130. Processor 1110 may communicate with other devices or chips through transceiver 1130. For example, the processor 1110 can transmit and receive data with other devices or chips through the transceiver 1130 .

An embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the terminal or network device provided by the embodiment of the present application, and the program causes the computer to execute the method performed by the terminal or network device in the various embodiments of the present application.

An embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

An embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

It should be understood that the terms "system" and "network" may be used interchangeably in this application. In addition, the terms used in this application are only used to explain specific embodiments of the application and are not intended to limit the application. The terms “first”, “second”, “third” and “fourth” in the description, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific sequence. . Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

In the embodiments of this application, the "instruction" mentioned may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the embodiment of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B only based on A. B can also be determined based on A and/or other information.

In the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, or it can also mean that there is an association between the two, or it can also mean indicating and being instructed, configuring and being configured, etc. relation.

In the embodiment of this application, "predefinition" or "preconfiguration" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol.

In the embodiment of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.

The term "and/or" in the embodiment of this application is only an association relationship describing associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, and A and B exist simultaneously. , there are three situations of B alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

In the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.

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

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

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center integrated with one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.

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

Claims

A business operation method, characterized by including:

The first device sends a first request, and the first request is used to request the second device to perform service connection.
The method according to claim 1, characterized in that the service connection is based on a local communication connection mode between the first device and the second device.
The method according to claim 2, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The method according to claim 1, characterized in that the service connection is performed based on a cloud server.
The method according to claim 4, characterized in that the first device sends a first request, including:

The first device sends the first request to the cloud server.
The method according to claim 4 or 5, characterized in that the data corresponding to the service connection is sent by the cloud server to the second device.
The method according to claim 4 or 5, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The method according to any one of claims 4 to 7, characterized in that the first request includes identification information of the second device.
The method according to any one of claims 1 to 8, characterized in that the first request includes the type of service connection and/or identification information of a service that supports connection of the service.
The method according to any one of claims 1 to 9, characterized in that the first request includes synchronization information of the service connection.
The method according to any one of claims 1 to 10, characterized in that the first request includes first indication information, and the first indication information is used to indicate the transmission of service connections supported by the first device. Channel type.
The method according to any one of claims 1-11, characterized in that the method further includes:

The first device receives the response message of the first request, and the response message of the first request is used to indicate starting the connection service of the service.
The method according to any one of claims 1-12, characterized in that the method further includes:

The first device sends a third request, the third request is used to discover a device that supports connecting the service;

The first device receives a first response sent by the second device, where the first response is used to indicate that the second device supports connecting the service.
The method according to claim 13, characterized in that the third request is sent by the first device when it determines that service connection is required, and whether the service connection is required is determined by the first device according to the second request. The information is certain.
The method of claim 14, wherein the second information includes one or more of the following information: an application running on the first device, a type of application running on the first device , and auxiliary information.
The method according to claim 15, wherein the auxiliary information includes one or more of the following information: the enabled status of the service connection mode of the first device, the application running on the first device. status, and the positional relationship between the first device and the second device.
The method according to any one of claims 13-16, characterized in that the third request is sent in a unicast or multicast manner.
The method according to any one of claims 13 to 17, characterized in that the third request includes the type of service connection and/or identification information of a service that supports connection of the service.
The method according to any one of claims 13 to 18, characterized in that the first response includes business connection service information of the second device, and the business connection service information includes the device of the second device. information, and/or business connection service capability information of the second device.
The method according to any one of claims 13 to 19, characterized in that the first response is also used to indicate a transmission channel type of service connection supported by the second device.
The method according to any one of claims 1-20, characterized in that the second device is a vehicle-mounted device.
A business operation method, characterized by including:

The second device receives a second request, and the second request is used to request the second device to perform service connection.
The method according to claim 22, characterized in that the service connection is based on a local communication connection mode between the first device and the second device.
The method according to claim 23, wherein the second request is a first request sent by the first device, and the first request is used to request the second device to perform service connection.
The method according to claim 23 or 24, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The method according to claim 22, characterized in that the service connection is performed based on a cloud server.
The method of claim 26, wherein the second device receiving the second request includes:

The second device receives the second request sent by the cloud server, and the second request is determined by the cloud server based on the first request sent by the first device.
The method of claim 27, wherein the first request includes identification information of the second device.
The method according to any one of claims 26 to 28, characterized in that the data corresponding to the service connection is sent by the cloud server to the second device.
The method according to any one of claims 26 to 28, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The method according to any one of claims 22 to 30, characterized in that the second request includes the type of service connection and/or identification information of a service that supports connection of the service.
The method according to any one of claims 22 to 31, characterized in that the second request includes synchronization information of the service connection.
The method according to any one of claims 22 to 32, characterized in that the second request includes first indication information, and the first indication information is used to indicate the transmission channel type of the service connection supported by the first device. .
The method according to any one of claims 22-33, characterized in that the method further includes:

The second device sends a response message to the second request, and the response message to the second request is used to indicate starting the connection service of the service.
The method according to any one of claims 22-34, characterized in that the method further includes:

The second device receives a third request sent by the first device, where the third request is used to discover a device that supports connecting the service;

The second device sends a first response to the first device, where the first response is used to indicate that the second device supports connecting the service.
The method of claim 35, wherein the third request is sent by the first device when it determines that service connection is required, and whether service connection is required is determined by the first device according to the second request. The information is certain.
The method of claim 36, wherein the second information includes one or more of the following information: an application running on the first device, a type of application running on the first device , and auxiliary information.
The method according to claim 37, characterized in that the auxiliary information includes one or more of the following information: an enabled status of the service connection mode of the first device, an application running on the first device status, and the positional relationship between the first device and the second device.
The method according to any one of claims 35-38, characterized in that the third request is sent in a unicast or multicast manner.
The method according to any one of claims 35 to 39, characterized in that the third request includes the type of service connection and/or identification information of a service that supports connection of the service.
The method according to any one of claims 35 to 40, characterized in that the first response includes business connection service information of the second device, and the business connection service information includes the device of the second device. information, and/or business connection service capability information of the second device.
The method according to any one of claims 35 to 41, characterized in that the first response is also used to indicate a transmission channel type of service connection supported by the second device.
The method according to any one of claims 22-42, characterized in that the second device is a vehicle-mounted device.
A business operation method, characterized by including:

The cloud server receives a first request sent by the first device, where the first request is used to request the second device to perform service connection.
The method of claim 44, further comprising:

The cloud server sends a second request to the second device, where the second request is determined based on the first request.
The method of claim 44, further comprising:

The cloud server sends a second request to the second device, where the second request is the first request.
The method according to any one of claims 44 to 46, characterized in that the data corresponding to the service connection is sent by the cloud server to the second device.
The method according to any one of claims 44 to 46, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The method according to any one of claims 44 to 48, characterized in that the first request includes identification information of the second device.
The method according to any one of claims 44 to 49, characterized in that the first request includes the type of service connection and/or identification information of a service that supports connection of the service.
The method according to any one of claims 44 to 50, characterized in that the first request includes synchronization information of the service connection.
The method according to any one of claims 44-51, characterized in that the method further includes:

The cloud server sends a response message to the first request to the first device. The response message to the first request is used to indicate starting the connection service of the business. The response message to the first request is based on the Determined by the response message of the second request.
A business operation device, characterized in that the device is configured on a first device, and the device includes:

The first sending module is configured to send a first request, where the first request is used to request the second device to perform service connection.
The apparatus according to claim 53, wherein the service connection is based on a local communication connection mode between the first device and the second device.
The apparatus according to claim 54, wherein the data corresponding to the service connection is sent by the first device to the second device.
The device according to claim 53, characterized in that the service connection is performed based on a cloud server.
The device according to claim 56, wherein the first sending module is further configured to send the first request to the cloud server.
The device according to claim 56 or 57, characterized in that the data corresponding to the service connection is sent by the cloud server to the second device.
The device according to claim 56 or 57, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The apparatus according to any one of claims 56-59, wherein the first request includes identification information of the second device.
The device according to any one of claims 53 to 60, wherein the first request includes the type of service connection and/or identification information of a service that supports connection of the service.
The device according to any one of claims 53-61, wherein the first request includes synchronization information of the service connection.
The apparatus according to any one of claims 53-62, characterized in that the first request includes first indication information, the first indication information is used to indicate the transmission of service connections supported by the first device. Channel type.
The device according to any one of claims 53-63, characterized in that the device further includes:

The first receiving module is configured to receive a response message of the first request, where the response message of the first request is used to indicate starting the connection service of the business.
The device according to any one of claims 53-64, characterized in that the device further includes:

a second sending module, configured to send a third request, where the third request is used to discover a device that supports connecting the service;

The second receiving module is configured to receive a first response sent by the second device, where the first response is used to indicate that the second device supports continuing the service.
The apparatus according to claim 65, wherein the third request is sent by the first device when it determines that service connection is required, and whether service connection is required is determined by the first device according to the second request. The information is certain.
The apparatus according to claim 66, wherein the second information includes one or more of the following information: an application running on the first device, a type of application running on the first device , and auxiliary information.
The apparatus according to claim 67, wherein the auxiliary information includes one or more of the following information: an enabled status of the service continuity mode of the first device, an application running on the first device status, and the positional relationship between the first device and the second device.
The apparatus according to any one of claims 65-68, wherein the third request is sent in a unicast or multicast manner.
The apparatus according to any one of claims 65 to 69, wherein the third request includes the type of service connection and/or identification information of a service that supports connection of the service.
The apparatus according to any one of claims 65 to 70, characterized in that the first response includes business connection service information of the second device, and the business connection service information includes the device of the second device. information, and/or business connection service capability information of the second device.
The apparatus according to any one of claims 65 to 71, wherein the first response is also used to indicate a transmission channel type of service connection supported by the second device.
The device according to any one of claims 53-72, characterized in that the second device is a vehicle-mounted device.
A business operation device, characterized in that the device is configured on a second device, and the device includes:

The first receiving module is configured to receive a second request, where the second request is used to request the second device to perform service connection.
The apparatus according to claim 74, wherein the service connection is based on a local communication connection mode between the first device and the second device.
The apparatus according to claim 75, wherein the second request is a first request sent by the first device, and the first request is used to request the second device to perform service connection.
The apparatus according to claim 75 or 76, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The device according to claim 74, characterized in that the service connection is performed based on a cloud server.
The device according to claim 78, characterized in that the first receiving module is further configured to: receive the second request sent by the cloud server, the second request is a request sent by the cloud server according to the first device. The first request sent is determined.
The apparatus according to claim 79, wherein the first request includes identification information of the second device.
The device according to any one of claims 78-80, characterized in that the data corresponding to the service connection is sent by the cloud server to the second device.
The device according to any one of claims 78 to 80, characterized in that the data corresponding to the service connection is sent by the first device to the second device.
The apparatus according to any one of claims 74 to 82, wherein the second request includes the type of service connection and/or identification information of a service that supports connection of the service.
The device according to any one of claims 74-83, wherein the second request includes synchronization information of the service connection.
The apparatus according to any one of claims 74-84, characterized in that the second request includes first indication information, and the first indication information is used to indicate the transmission channel type of the service connection supported by the first device. .
The device according to any one of claims 74-85, characterized in that the device further includes:

The first sending module is configured to send a response message to the second request. The response message to the second request is used to indicate starting the connection service of the business.
The device according to any one of claims 74-86, characterized in that the device further includes:

a second receiving module, configured to receive a third request sent by the first device, where the third request is used to discover a device that supports connecting the service;

The second sending module is configured to send a first response to the first device, where the first response is used to indicate that the second device supports connecting the service.
The apparatus according to claim 87, wherein the third request is sent by the first device when it determines that service connection is required, and whether service connection is required is determined by the first device according to the second request. The information is certain.
The apparatus according to claim 88, wherein the second information includes one or more of the following information: an application running on the first device, a type of application running on the first device , and auxiliary information.
The apparatus according to claim 89, wherein the auxiliary information includes one or more of the following information: an enabled status of the service continuity mode of the first device, an application running on the first device status, and the positional relationship between the first device and the second device.
The apparatus according to any one of claims 87-90, wherein the third request is sent in a unicast or multicast manner.
The apparatus according to any one of claims 87-91, wherein the third request includes the type of service connection and/or identification information of a service that supports connection of the service.
The apparatus according to any one of claims 87-92, wherein the first response includes business connection service information of the second device, and the business connection service information includes the device of the second device. information, and/or business connection service capability information of the second device.
The apparatus according to any one of claims 87-93, characterized in that the first response is also used to indicate a transmission channel type of service connection supported by the second device.
The device according to any one of claims 74-94, characterized in that the second device is a vehicle-mounted device.
A business operation device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory to execute any one of claims 1-52. method described.
A device, characterized in that it includes a processor for calling a program from a memory to execute the method according to any one of claims 1-52.
A chip, characterized in that it includes a processor for calling a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-52.
A computer-readable storage medium, characterized in that a program is stored thereon, and the program causes the computer to execute the method according to any one of claims 1-52.
A computer program product, characterized by comprising a program that causes a computer to execute the method according to any one of claims 1-52.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1-52.