Business operation method and device, chip, storage medium and computer program

Abstract

The invention provides a business operation method and device, a chip, a storage medium and a computer program. The service operation method comprises the following steps: a first device sends a first request, wherein the first request is used for requesting a second device to carry out service connection; in the embodiment of the invention, the first equipment can connect the service of the first equipment to the second equipment based on the first request, so that the service carried out by the first equipment can be automatically and continuously executed on the second equipment following the current progress, the user operation is reduced, and the user experience is further improved.

Description

Business operation method, device, chip, storage medium and computer program Technical Field

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

[0002] With the development of communication technology, users are increasingly interacting with multiple electronic devices. In some scenarios, users can mirror screens between multiple devices, for example, by displaying applications / services on a mobile phone on a car device.

[0003] However, mirroring between devices requires multiple manual operations. For example, when mirroring a mobile app or service to a car device, the user must trigger the mirroring function on the phone, manually establish a connection between the phone and the car device, and even manually drag the progress of the car device's app or service to the corresponding position on the phone's app or service. This overall operation is complex and the user experience is poor.

[0004] Summary of the Invention

[0005] The present application provides a service operation method, device, chip, storage medium and computer program. The following introduces various aspects involved in the embodiments of the present application.

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

[0007] 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 continuation.

[0008] According to a third aspect, a service operation method is provided, including: a cloud server receives a first request sent by a first device, wherein the first request is used to request a second device to perform service continuation.

[0009] In a fourth aspect, a service operation apparatus is provided, which is configured on a first device and includes: a first sending module, configured to send a first request, wherein the first request is used to request a second device to perform service continuation.

[0010] In a fifth aspect, a service operation apparatus is provided, which is configured on a second device and includes: a first receiving module for receiving a second request, wherein the second request is used to request the second device to perform service continuation.

[0011] In the sixth aspect, a business operation device is provided, including a processor, a memory and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the device executes part or all of the steps in the methods of the above aspects.

[0012] In a seventh aspect, an embodiment of the present application provides 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 service operation device in the solution provided in the embodiment of the present application.

[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a business operation device to execute part or all of the steps in the methods of the above aspects.

[0014] 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, wherein the computer program is operable to cause a service operation device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0015] In the tenth aspect, an embodiment of the present application provides 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.

[0016] In an embodiment of the present application, the first device can connect the business of the first device to the second device based on the first request, so that the business on the first device can automatically continue to be executed on the second device according to the current progress, reducing user operations and thereby improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG1 is a diagram illustrating an example architecture of a wireless communication system applicable to an embodiment of the present application.

[0018] FIG2 is a flow chart of a business operation method provided in an embodiment of the present application.

[0019] FIG3 is a flow chart of a business operation method provided in another embodiment of the present application.

[0020] FIG4 is a flow chart of a business operation method provided in another embodiment of the present application.

[0021] FIG5 is a flowchart of a possible implementation of step S420 in FIG4 .

[0022] FIG6 is a flow chart of a business operation method provided in another embodiment of the present application.

[0023] FIG7 is a flow chart of a business operation method provided in another embodiment of the present application.

[0024] FIG8 is a flow chart of a business operation method provided in another embodiment of the present application.

[0025] FIG9 is a schematic diagram of the structure of a service operation device provided in an embodiment of the present application.

[0026] FIG10 is a schematic structural diagram of a service operation device provided in another embodiment of the present application.

[0027] FIG11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the purpose and advantages of this application clearer and more understandable, the technical solutions in this application will be described below in conjunction with the accompanying drawings.

[0029] 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, the scenarios in which users' multiple electronic devices interact with each other are becoming more frequent.

[0030] In a scenario where multiple electronic devices interact, screen projection can be performed between multiple devices of the user. Screen projection can refer to the application / service in the first device (for example, it can be called the delivery end) being delivered to the second device (for example, it can be called the receiving end) for display. For example, the application / service of a mobile phone is delivered to the on-board device of a car for display, or the application / service of a mobile phone is delivered to the TV for display, etc. In this example, the mobile phone is the first device, or the delivery end; the on-board device or TV is the second device, or the receiving end.

[0031] In some embodiments, the application / service 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.

[0032] In some embodiments, when screen projection is performed between a first device and a second device, the application / service in the first device can continue to be displayed on the second device, but the data stream associated with the application / service displayed on the second device is still in the first device, that is, the data stream associated with the application / service in the first device will not be transmitted to the second device.

[0033] In the related art, there are many technical solutions for implementing screen projection display between a first device and a second device. The following exemplifies two commonly used technical solutions for screen projection display.

[0034] 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 projection function on the first device, and then manually establish a screen projection connection between the first device and the second device, etc., so that the main interface screen of the first device is displayed on the second device. In addition, when using this technical solution, 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 take active actions on the second device, for example, reopen the corresponding application / service on the second device, drag and drop the progress of the application / service to the corresponding position of the application / service on the first device, etc.

[0035] In another technical solution, after the first device establishes a screen projection connection with the second device, the second device can be used only to display the content currently displayed on the screen of the first device, for example, by using screen recording to display the content currently displayed on the first device on the second device. When using this technical solution, the function of the second device is only equivalent to a projection device, and the screen projection display simply projects the screen of the first device to the second device. The user still needs to manually perform some additional operations, such as triggering the screen projection function on the first device, manually establishing a screen projection connection between the first device and the second device, etc. In addition, when using this technical solution, if the first device terminates the operation of certain applications / services, for example, because the screen is turned off or the power is turned off, the second device will also stop displaying the screen content of the first device accordingly.

[0036] Below, 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 technology is exemplified.

[0037] With the networking and intelligence of automobiles, cars can interact with mobile phones through interconnected collaboration and other means. At present, the main scenarios of car-machine collaboration are digital car keys, car-machine screen projection, etc. In some embodiments, the smart cockpit of the car can provide users with in-vehicle applications and services (for example, Apple's CarPlay, Google's AndroidAuto, etc.), and realize digital car keys, car-machine screen projection, etc. through the provided in-vehicle applications and services. In some embodiments, in-vehicle applications and services can adopt the digital car key protocol of the Car Connectivity Consortium (CCC) or the Miracast screen projection protocol (a screen projection protocol developed by the Wireless Fidelity (WiFi) Alliance) to solve the digital car keys and multimedia content projection of mobile phones and cars, and realize functions such as digital car keys and car-machine screen projection.

[0038] Taking car screen projection as an example, in some embodiments, when the user interacts with the mobile phone and the car device through the car application and service, the mobile phone side and the car device side are both presented in the form of an application (APP), and the user can project the mobile phone side APP on the screen of the car device through some manual operations (that is, the car device is used to display the main interface screen of the mobile phone). In this case, if a piece of music is playing 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 application on the car device, select the same music in the car application, drag the playback progress bar to the corresponding position, set the same playback mode, etc., so that the music on the mobile phone can continue to play on the car device. In other embodiments, the user can project the mobile phone screen on the screen of the car device through some manual operations (that is, the car 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 screen projection function on the mobile phone side and establish a screen projection connection between the mobile phone and the car device, etc. The overall operation is relatively complicated, and if the mobile phone stops playing the music because the screen is turned off or turned off, the car device will also stop playing immediately.

[0039] In summary, when screen projection is performed between devices, users are required to perform multiple manual operations, which results in a poor user experience.

[0040] Furthermore, existing technologies can only mirror applications / services on a first device to a second device for sharing. However, as user needs diversify, the need for interconnection and collaboration between the first and second devices may become more complex. Therefore, a new business model is urgently needed to meet the diverse needs of users.

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

[0042] The following is a clear and complete description of the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings provided in the embodiments of the present application. Obviously, the embodiments described are only part of the embodiments of the present application, not all of the embodiments.

[0043] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, WiFi system, Bluetooth system, etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc. The following is an exemplary description of the wireless communication system to which the embodiments of the present application can be applied, with reference to FIG1.

[0044] Referring to Figure 1 , Figure 1 is a diagram illustrating an exemplary architecture of a wireless communication system 100 applicable to embodiments of the present application. As shown in Figure 1 , the wireless communication system 100 may include a first device 110 and a second device 120. The first device 110 may communicate with the second device 120. In some embodiments, the first device 110 and the second device 120 may establish a connection for communication via a wired or wireless network (e.g., Bluetooth or a mobile network).

[0045] Figure 1 exemplarily shows a first device 110 and a second device 120, but the embodiments of the present application are 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.

[0046] In some embodiments, the first device and the second device in the embodiments of the present application may be referred to as a first terminal device and a second terminal device, respectively. The terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0047] The first device and the second device in the embodiment of the present application can be devices that provide voice and / or data connectivity to users, and can be used to connect people, objects and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc. For example, the first device and the second device in the embodiment of the present application can be mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, IoT devices, virtual reality (VR) devices, augmented reality (AR) devices, etc. Optionally, the IoT device can include a smart vehicle, a smart TV or other device with a screen display function. For example, in the case where the first device or the second device is a smart vehicle, the smart vehicle can be, for example, a family car, a taxi, a bus, a motorcycle, etc., and the embodiment of the present application does not specifically limit this.

[0048] In the embodiments of the present application, there is no limitation on the scenarios in which the first device and the second device are located. For example, the first device and the second device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted.

[0049] Continuing to refer to FIG1 , in some embodiments, the wireless communication system 100 may further include a cloud server 130, which may, for example, refer to a server in a cloud platform. The cloud server 130 and the first device 110 and the second device 120 may establish a connection with each other via a wireless network (e.g., 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 via WiFi, while the cloud server 130 and the second device 120 establish a connection via a 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 120 may both establish a connection via a mobile network.

[0050] 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 may be implemented through the cloud server 130.

[0051] In some embodiments, the first device 110 and / or the second device 120 can access the cloud server 130 by logging in to an account. For example, they can access the same data or resources stored on the cloud server 130 by logging in to the same account.

[0052] It should be understood that the vehicle-mounted equipment mentioned in the embodiments of the present application may refer to the abbreviation of the vehicle-mounted infotainment product installed on the car. The vehicle-mounted equipment is functionally capable of realizing information communication between people and vehicles, and vehicles and the outside world (for example, vehicles and vehicles, vehicles and mobile phones, etc.). In some embodiments, the vehicle-mounted equipment may also be referred to as a vehicle-mounted terminal, a vehicle-mounted system, a vehicle machine, a central control system, a navigation system, a navigation screen, etc., and the embodiments of the present application are not limited to this. In the embodiments 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.

[0053] 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).

[0054] The communication method provided in the embodiment of the present application is described in detail below in conjunction with the system architecture shown in FIG1 .

[0055] Figure 2 is a flow chart of a business operation method provided by an embodiment of the present application. The method shown in Figure 2 is described from the perspective of the 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 Figure 1, and the cloud server may be, for example, the cloud server 130 in Figure 1. Specifically, the first device or the second device may refer to, for example, a mobile phone, a tablet computer, a laptop computer, a vehicle-mounted device, a television and other devices. The embodiment of the present application is not limited to this, as long as the first device and the second device can achieve business continuity or screen projection display. As a specific example, the second device may refer to, for example, a vehicle-mounted device, and the first device may refer to, for example, a terminal device that conducts business continuity with the vehicle-mounted device, such as a mobile phone, a laptop computer, etc. The method shown in Figure 2 may include step S210, and step S210 is described in detail below.

[0056] In step S210, the first device sends a first request, where the first request is used to request the second device to perform service connection.

[0057] Service continuity refers to the process of automatically transferring a service (e.g., an application or service currently running on the first device) from one device to a second device. This automatically switches (or transfers) the service from the first device to the second device, where it can continue executing automatically at the same pace as it was at the time. In other words, service continuity allows services on the first device to be automatically transferred to the second device, ensuring that users can seamlessly continue their ongoing services across devices.

[0058] Based on this, in some embodiments, service continuity can be understood as service switching, service flow, service relay, etc., connecting / switching / flowing / relaying the service of the first device to the second device, so that users can seamlessly continue the ongoing service between different devices.

[0059] It should be understood that the ability of the first device and the second device to achieve service continuity can mean that the first device and the second device can support service continuity services (or, support service continuity functions, support service continuity events, etc.). When the first device and the second device support service continuity services, the first device can connect the services (applications, services, etc.) of the first device to the second device. In some embodiments, the service continuity service can be replaced by service continuity, and the embodiments of the present application do not make a clear distinction between the two.

[0060] In some embodiments, the first device can directly send a first request to the second device, requesting the second device to resume service. In some embodiments, the first device can send the first request to a cloud server. The cloud server determines a corresponding second request based on the first request and then sends the second request to the second device, requesting the second device to resume service. This will be described in detail later and is not detailed here.

[0061] In some embodiments, the service of the first device may refer to a service currently running on the first device, such as a running application or service. As a specific example, the service of the first device may refer to a video (or music, call, etc.) currently playing on the first device, or to an application currently playing the video (or music, call, etc.). As another specific example, the service of the first device may refer to an application or service currently running on the first device for controlling an IoT device.

[0062] In some embodiments, the implementation process of service continuity 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. A description of the implementation process of service continuity can be found later and will not be repeated here.

[0063] In some embodiments, service connection is performed 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 to this embodiment 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 repeated here.

[0064] It should be understood that the local communication connection mode may refer to the first device and the second device transmitting and receiving via the local communication connection between them without forwarding through the server. Optionally, the first device and the second device may establish a local communication connection using technologies such as Bluetooth, WiFi, and infrared.

[0065] 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. For example, the type of service connection may include one or more of the following types: video service connection, audio service connection, call service connection, IoT device control service connection, etc. This application does not specifically limit this, that is, the type of service connection may also include other types beyond the enumeration. That is, the first request may be used to indicate that the type of service connection is a video service connection, or the first request may be used to indicate that the type of service connection is an audio service connection. Of course, this application is not limited to this. For example, the type of service connection may also be a call service connection, or an IoT device control service connection, etc.

[0066] In some embodiments, the first request may include identification information of a service that supports the continuation of the service. In other words, the first device may specify a specific service (e.g., a specific application) for the continuation of the service in the first request. Optionally, the identification information of the service that supports the continuation of the service may include the type of application that supports the continuation of the service, such as a video application, a call application, etc.; or, the identification information of the service that supports the continuation of the service may include a specific application that supports the continuation of the service, such as the first application.

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

[0068] In some embodiments, the first request may include both the type of service connection and identification information of a service that supports the service connection. That is, the first device may specify both the type of service connection and a specific service in the first request, indicating that the corresponding type of service connection and the specific service (e.g., a specific application) that supports the service connection are to be performed.

[0069] In some embodiments, the first request may include (or carry) synchronization information for service connection. For example, when the service connection type 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 current video or audio streaming information and playback time.

[0070] In some embodiments, the first request may include first indication information, and the first indication information may be used to indicate a transmission channel type for a service connection supported by the first device. The embodiments of the present application do not limit the transmission channel type for a service connection supported by the first device. For example, the transmission channel type for a service connection supported by the first device may include one or more of the following: Bluetooth, Bluetooth low energy (BLE), ultra wide band (UWB), WiFi peer to peer (P2P), WiFi local area network, cellular network, etc.

[0071] 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 identification information of the second device so that the cloud server can send a second request to the second device.

[0072] 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 IoT device capable of service connection, such as a smart TV. Of course, the present 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.

[0073] In an embodiment of the present application, the first device can connect the business of the first device to the second device based on the first request, so that the business performed by the first device can automatically continue to be executed on the second device according to the current progress, reducing user operations and thereby improving user experience.

[0074] 3 and 4 , the communication connection mode and the data transmission process when the service is connected between the first device and the second device are described in detail.

[0075] Figure 3 is a flow chart of a service operation method provided by another embodiment of the present application. In the embodiment shown in Figure 3, service connection is performed based on a local connection between the first device and the second device. As shown in Figure 3, the method may include steps S310 to S330.

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

[0077] For details of step S310, please refer to the above description of step S210, which will not be repeated here.

[0078] 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, where the response message is used to indicate the start of the service continuation service.

[0079] Steps S310 and S320 can be understood as the 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 service continuation 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 data transmission can be carried out. However, the embodiments of the present application are not limited to this. In some embodiments, the response message to the first request sent by the second device can also be used to indicate that the service continuation startup failed, that is, the connection was not successfully established.

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

[0081] The first device and the second device perform data transmission for service continuity, 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 continuity to the second device, so that the video or audio continues to play on the second device following the playback progress of the first device.

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

[0083] In some embodiments, the second device may select a corresponding transmission channel type based on the type of service connection and / or the application of the connection, such as the optimal transmission channel corresponding to the type of service connection and / or the application of the connection. For example, if the service connection type is a video service connection or a video application, WiFi P2P or WiFi LAN may be used as the transmission channel (or, WiFi P2P or WiFi LAN connection); if the service connection type is an audio service connection or an audio application, BLE or Bluetooth may be used as the transmission channel (or, BLE or Bluetooth connection).

[0084] The first device and the second device perform data transmission for service connection based on a local connection method, with fast transmission speed and high transmission security.

[0085] Figure 4 is a flow chart of a business operation method provided by another embodiment of the present application. In the embodiment shown in Figure 4, business continuity is performed based on a cloud server. As shown in Figure 4, the method may include steps S410 to S430.

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

[0087] In some embodiments, the first request may include identification information of the second device, where the identification information is used to indicate information of the second device for service connection.

[0088] 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 relevant content of the first request described above, which will not be repeated here.

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

[0090] The embodiments of the present application do not specifically limit the implementation method 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.

[0091] For example, a possible implementation of step S420 is shown in Fig. 5. Referring to Fig. 5, step S420 may include steps S422 to S426.

[0092] 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 continue the service. The information of the first request may include, for example, a device identifier of the second device.

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

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

[0095] In step S424, the cloud server determines a second request based on the first request.

[0096] 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 identifier of the second device, but may include other information in the first request except the device identifier of the second device.

[0097] In step S426, the cloud server sends a second request to the second device, requesting the second device to continue the service. The second request may include, for example, the type of service continued, identification information of the service that supports continuing the service, synchronization information of the service continued, etc.

[0098] Optionally, before step S426, step S425 may be further 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 continuity of the cloud server has been started, for example, successfully started. Alternatively, the response message may be used to indicate that the service continuity service of the cloud server has failed to start.

[0099] Regarding other contents of step S420, such as the information included in the second request, please refer to the description of the information included in the first request in S210 above, which will not be repeated here.

[0100] In step S430, the second device sends a response message to the cloud server for the second request, indicating that the service continuation service has been initiated. In other words, the second device may send a response message to the first request to the first device via the cloud server. The response message to the first request sent by the second device may indicate that the service continuation service has been initiated on the second device. In some embodiments, the response message to the first request sent by the second device may also indicate that the service continuation service has failed to be initiated.

[0101] In step S440 , the cloud server and the second device perform data transmission for service connection.

[0102] The cloud server and the second device perform data transmission for business continuity, so that the business of the first device can be continued on the second device. For example, the cloud server sends a multimedia stream of video or audio continuity to the second device, so that the video or audio continues to play on the second device following the playback progress of the first device.

[0103] In this embodiment, when the service connection between the first device and the second device is 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, and on the other hand, after the response is completed, the cloud server is also used to transmit data for the service connection with the second device.

[0104] In some embodiments, step S440 may be replaced by the first device and the second device performing data transmission for service connection. That is, when the service connection between the first device and the second device is performed based on a cloud server, the cloud server may only be used to respond to the service connection request of the first device. After the response is completed, the actual data transmission process corresponding to the service connection 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 data transmission process.

[0105] The first device and the second device perform data transmission for business continuity based on the cloud server, which can save local storage space.

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

[0107] As mentioned above, the process of implementing the service continuation may also include a discovery process for the second device. The embodiment of the present application does not specifically limit the discovery process between the first device and the second device. Exemplarily, the discovery process between the first device and the second device is introduced below in conjunction with Figure 6. As shown in Figure 6, in some embodiments, the discovery process between the first device and the second device may include steps S610 and S620. It should be understood that steps S610 and S620 can, for example, be performed before executing step S210. Steps S610 and S620 are described in detail below.

[0108] In step S610, the first device sends a third request, where the third request is used to discover a device that supports service continuity.

[0109] 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 multiple devices, including the second device. The second device may be a target device in the multiple devices.

[0110] In some embodiments, the third request is sent by the first device when it is determined that service connection is required, and whether service connection is required is determined by the first device according to the second information.

[0111] The embodiment of the present application does not specifically limit the content of the second information. Exemplarily, the second information may include one or more of the following information: the application / service currently running on the first device, the type of the application / service currently running on the first device, and auxiliary information.

[0112] The application / service being run by the first device may refer to a specific application / service being run, for example, the first device is running application A.

[0113] In some embodiments, the type of the application / service currently running on the first device may refer to the type of the application / service being a video application, an audio application, or an IoT device control application. In some embodiments, the type of the application / service currently running on the first device may refer to the type of the application / service being an application / service that supports service continuity or an application / service that does not support service continuity.

[0114] Exemplarily, the auxiliary information may include one or more of the following information: the activation state of the service continuation mode of the first device, the state of the application / service being run by the first device, and the positional relationship between the first device and the second device. As an example, whether service continuation is required can be determined based on the activation state of the service continuation mode of the first device. For example, when the service continuation mode of the first device is enabled, it is determined that service continuation is required; or, when the service continuation mode of the first device is enabled and the application running on the first device is a video application, it is determined that service continuation is required. As another example, whether service continuation is required can be determined based on the state of the application / service being run by the first device. For example, when the application being run by the first device is an application for controlling IoT devices, when a change in the state of the application is detected (for example, the application running on the first device is a digital car key application, and a change in the state of the digital car key is detected), it is determined that service continuation is required. As another example, whether service continuation is required can be determined based on the positional 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 positional relationship between the two meets a certain condition (for example, the first device is located inside the second device, the first device is located at the target position of the second device, etc.), it is determined that service continuation is required; or, when the distance between the first device and the second device is less than a certain threshold or the spatial positional relationship between the two meets a certain condition, and the type of application running on the first device is a type that supports service continuation, it is determined that service continuation is required.

[0115] In some embodiments, the third request may be sent in a unicast or multicast manner, for example, the third request may be sent via a Bluetooth broadcast message.

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

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

[0118] In some embodiments, the business continuation service information may include device information of the second device, and / or business continuation service capability information of the second device. The device information of the second device may include identification information of the second device, such as the device identification of the second device. The business continuation service capability information of the second device may include information on the types of business continuations supported by the second device and / or application information associated with the business continuation services supported by the second device. For example, the business continuation service capability information of the second device may be: the types of business continuations supported by the second device include video / audio / IoT device control-type business continuation services; or, the business continuation service capability information of the second device may be: the application identification associated with the business continuation services supported by the second device is application A or APP ID is 10001.

[0119] In some embodiments, when the first device sends a third request to multiple devices, if the first device receives first responses sent by the multiple devices, the first device can determine the second device (target device) based on the first responses.

[0120] In some embodiments, the first response can 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, cellular network, etc.

[0121] It should be understood that when the first device determines to perform service continuity on the second device, an application capable of performing service continuity may be running on the first device, such as an application related to playing video, audio, or controlling IoT devices.

[0122] To facilitate understanding of the technical solutions of the embodiments of the present application, two specific examples are given below, taking the 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's service is connected to the on-board device (for example, after the user gets in the car, the video, music, call, etc. currently played on the mobile phone is transferred to the screen of the on-board device), the first device refers to the mobile phone and the second device refers to the on-board device of the car; if the service in the car is connected to the mobile phone (for example, when the user gets out of the car, the video, music, call, etc. currently played in the car is transferred to the mobile phone), the first device refers to the on-board device of the car and the second device refers to the mobile phone.

[0123] Example 1 (based on local connection):

[0124] FIG7 is a flow chart of a service operation method provided by another embodiment of the present application. Referring to FIG7 , the service operation method may include steps S710 to S760.

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

[0126] In step S720, the first device sends a service continuity discovery request (see the third request above) to discover other devices supporting the service continuity service, such as the second device.

[0127] In some embodiments, the first device may determine the need for service continuity discovery based on the currently running application / application type and auxiliary conditions (e.g., a user enabling service continuity mode on the first device, detecting a change in the status of an application on the first device, the location relationship between the first device and the second device, etc.). Specifically, when the first device is a mobile phone and the second device is an in-vehicle device, the auxiliary conditions may include, for example, a user enabling service continuity mode on the mobile phone, detecting a change in the status of a digital car key on the mobile phone, or the mobile phone being inside the vehicle.

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

[0129] In some embodiments, the first device may specify the service connection type in the service connection discovery request message to discover devices that meet the corresponding type of connection service capability. As an example, to discover devices that support the video / music / IoT device control connection service capability, the service connection discovery request message may carry the discovery condition of the video / music / IoT device control connection service capability.

[0130] In some embodiments, the first device may specify a specific application in the service continuity discovery request to discover a device that supports the specific application of the service continuity.

[0131] In some embodiments, the first device may specify both the type of connection service and a 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.

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

[0133] In some embodiments, the service continuation service information of the second device may include device information and / or service continuation service capability information of the second device. The service continuation service capability information of the second device may include, for example, the type of service continuation service supported by the second device and identification information of the service that the second device supports for continuing the service.

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

[0135] In step S740, the first device initiates a service connection request (see the first request above) to the second device, requesting service connection on the second device.

[0136] The first device sends a message of a service connection request type to the second device according to the service connection service information of the second device obtained in step S730, so as to connect the service.

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

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

[0139] In some embodiments, the first device may specify both the type of service connection and a specific application in the service connection request, indicating the corresponding type of connection service and the specific application supporting the connection service.

[0140] 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 video / audio playback on the vehicle-mounted device of the car, the request message may carry the current video / music streaming information and playback time.

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

[0142] In step S750, the second device sends a service continuation response, indicating that the service continuation service is successfully started.

[0143] In step S760, data transmission of service continuity is performed between the first device and the second device, and the service on the first device is continued on the second device. For example, the first device sends a multimedia stream of video / audio continuity to the second device.

[0144] In some embodiments, the second device may select an optimal transmission channel according to the type and / or application of the service connection, for example, a video connection may use a WiFi P2P / WiFi LAN connection, and an audio connection may use a BLE / Bluetooth connection.

[0145] Example 2 (based on cloud connection):

[0146] FIG8 is a flow chart of a service operation method provided by another embodiment of the present application. Referring to FIG8 , the service operation method may include steps S810 to S880.

[0147] In step S810, a user account is logged in on the first device, and an application capable of performing service connection is run, such as an application for playing video / audio, controlling IoT devices, etc.

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

[0149] In some embodiments, the first device may determine the need for service continuity discovery based on the currently running application / application type and auxiliary conditions (e.g., a user enabling service continuity mode on the first device, detecting a change in the status of an application on the first device, the location relationship between the first device and the second device, etc.). Specifically, when the first device is a mobile phone and the second device is an in-vehicle device, the auxiliary conditions may include, for example, a user enabling service continuity mode on the mobile phone, detecting a change in the status of a digital car key on the mobile phone, or the mobile phone being inside the vehicle.

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

[0151] In some embodiments, the first device may specify the service connection type in the service connection discovery request message to discover devices that meet the corresponding type of connection service capability. As an example, to discover devices that support the video / music / IoT device control connection service capability, the service connection discovery request message may carry the discovery condition of the video / music / IoT device control connection service capability.

[0152] In some embodiments, the first device may specify a specific application in the service continuity discovery request to discover a device that supports the specific application of the service continuity service.

[0153] In some embodiments, the first device may specify both the type of connection service and a 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.

[0154] In step S830, the second device sends a service connection discovery response, providing service connection service information of the second device.

[0155] In some embodiments, the service continuity service information of the second device may include device information and / or service continuity service capability information of the second device. The service continuity service capability information of the second device may include, for example, the type of service continuity supported by the second device and identification information of the service that the second device supports for continuing the service.

[0156] In step S840, the first device initiates a first service connection request to the cloud server, requesting the cloud server to perform service connection with the second device.

[0157] In some embodiments, the first device may carry the device identification of the second device in the first service continuation request message (the device identification may be obtained according to the device information of the second device obtained in step S830, for example), indicating the second device providing the service continuation service.

[0158] 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 may carry information about a video / audio / IoT device control connection service, indicating that a service connection of this type is to be performed.

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

[0160] In some embodiments, the first device may specify both the type of service connection and a specific application in the first service connection request, indicating the corresponding type of connection service and the specific application supporting the connection service.

[0161] 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 video / audio playback on the vehicle-mounted device, the request message may carry the current video / music streaming information and playback time.

[0162] In step S850, the cloud server sends a first service continuation request response to the first device, indicating that the service continuation service of the cloud server is successfully started.

[0163] 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 the service connection request to the second device based on the device identifier of the second device obtained in step S840 to connect the service.

[0164] 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 may carry information about a video / audio / IoT device control connection service, indicating that a service connection of this type is to be performed.

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

[0166] In some embodiments, the first device may specify both the type of service connection and a specific application in the second service connection request, indicating the corresponding type of connection service and the specific application supporting the connection service.

[0167] 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 vehicle side, the request message may carry the streaming media information and play time of the current video / music.

[0168] In step S870, the second device sends a second service continuation response, indicating that the service continuation service is successfully started.

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

[0170] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 11 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0171] FIG9 is a schematic diagram of the structure of a service operation device provided in an embodiment of the present application. The service operation device can be configured in the first device described above. The service operation device 900 shown in FIG9 can include a first sending module 910.

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

[0173] Optionally, the service connection is performed based on a local communication connection between the first device and the second device.

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

[0175] Optionally, business continuity is based on a cloud server.

[0176] Optionally, the first sending module is further used to: send a first request to the cloud server.

[0177] Optionally, data corresponding to the service connection is sent from the cloud server to the second device.

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

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

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

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

[0182] Optionally, the first request includes first indication information, where the first indication information is used to indicate a transmission channel type for a service connection supported by the first device.

[0183] Optionally, the apparatus 900 shown in Fig. 9 further includes a first receiving module 920. The first receiving module 920 may be configured to receive a response message to the first request, where the response message to the first request is used to indicate starting a connection service for the service.

[0184] Optionally, the device 900 shown in Figure 9 also includes a second sending module for sending a third request, the third request is used to discover a device that supports continuing the service; a second receiving module for receiving a first response sent by the second device, the first response is used to indicate that the second device supports continuing the service.

[0185] Optionally, the third request is sent by the first device when it is determined that service connection is required, and whether service connection is required is determined by the first device according to the second information.

[0186] Optionally, the second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

[0187] Optionally, the auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a positional relationship between the first device and the second device.

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

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

[0190] Optionally, the first response includes service continuation service information of the second device, where the service continuation service information includes device information of the second device and / or service continuation service capability information of the second device.

[0191] Optionally, the first response is further used to indicate a transmission channel type for the service connection supported by the second device.

[0192] Optionally, the second device is a vehicle-mounted device.

[0193] FIG10 is a schematic diagram of the structure of a service operation device provided in another embodiment of the present application. The service operation device can be configured in the second device described above. The service operation device 1000 shown in FIG10 can include a first receiving module 1010.

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

[0195] Optionally, the service connection is performed based on a local communication connection between the first device and the second device.

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

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

[0198] Optionally, business continuity is based on a cloud server.

[0199] Optionally, the first receiving module is further used 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.

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

[0201] Optionally, data corresponding to the service connection is sent from the cloud server to the second device.

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

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

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

[0205] Optionally, the first request includes first indication information, where the first indication information is used to indicate a transmission channel type for a service connection supported by the first device.

[0206] Optionally, the apparatus 1000 shown in Fig. 10 further includes a first sending module 1020. The first sending module 1020 may be configured to send a response message to the second request, where the response message to the second request is used to indicate starting a service connection service.

[0207] Optionally, the apparatus 1000 of FIG10 further includes a second receiving module for receiving a third request sent by the first device, the third request being used to discover a device that supports continuing the service; and a second sending module for sending a first response to the first device, the first response being used to indicate that the second device supports continuing the service.

[0208] Optionally, the third request is sent by the first device when it is determined that service connection is required, and whether service connection is required is determined by the first device according to the second information.

[0209] Optionally, the second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

[0210] Optionally, the auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a positional relationship between the first device and the second device.

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

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

[0213] Optionally, the first response includes service continuation service information of the second device, and the service continuation service information includes device information of the second device and / or service continuation service capability information of the second device.

[0214] Optionally, the first response is further used to indicate a transmission channel type for the service connection supported by the second device.

[0215] Figure 11 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 11 indicate that the unit or module is optional. The device 1100 may 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.

[0216] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the method embodiment above. 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 may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0217] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store programs that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the above method embodiments. The memories 1120 may be independent of the processor 1110 or integrated into the processor 1110.

[0218] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips via the transceiver 1130.

[0219] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0220] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0221] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0222] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0223] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

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

[0225] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0226] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0227] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0228] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

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

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

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

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

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

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

Claims

1. A business operation method, characterized in that: include: The first device sends a first request, where the first request is used to request the second device to perform service connection.

2. The method according to claim 1, characterized in that The service connection is performed based on a local communication connection between the first device and the second device.

3. The method according to claim 2, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

4. The method according to claim 1, wherein The business continuation is based on the cloud server.

5. The method according to claim 4, characterized in that The first device sending a first request includes: The first device sends the first request to the cloud server.

6. 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.

7. The method according to claim 4 or 5, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

8. The method according to any one of claims 4 to 7, characterized in that The first request includes identification information of the second device.

9. 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.

10. The method according to any one of claims 1 to 9, characterized in that The first request includes synchronization information of the service connection.

11. The method according to any one of claims 1 to 10, characterized in that The first request includes first indication information, where the first indication information is used to indicate a transmission channel type for a service connection supported by the first device.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: The first device receives a response message to the first request, where the response message to the first request is used to indicate starting a connection service for the service.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: The first device sends a third request, where the third request is used to discover a device that supports continuing 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 continuing the service.

14. The method according to claim 13, characterized in that The third request is sent by the first device when it is determined that service continuity is required. Whether service continuity is required is determined by the first device based on the second information.

15. The method according to claim 14, characterized in that The second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

16. The method according to claim 15, characterized in that The auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a location relationship between the first device and the second device.

17. The method according to any one of claims 13 to 16, characterized in that The third request is sent in a unicast or multicast manner.

18. 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 supporting connection of the service.

19. The method according to any one of claims 13 to 18, characterized in that The first response includes service continuity service information of the second device, and the service continuity service information includes device information of the second device and / or service continuity service capability information of the second device.

20. The method according to any one of claims 13 to 19, characterized in that The first response is further used to indicate a transmission channel type of a service connection supported by the second device.

21. The method according to any one of claims 1 to 20, characterized in that The second device is a vehicle-mounted device.

22. A business operation method, characterized in that: include: The second device receives a second request, where the second request is used to request the second device to perform service connection.

23. The method according to claim 22, characterized in that The service connection is performed based on a local communication connection between the first device and the second device.

24. The method according to claim 23, wherein The second request is the first request sent by the first device, and the first request is used to request the second device to perform service connection.

25. The method according to claim 23 or 24, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

26. The method according to claim 22, wherein The business continuation is based on the cloud server.

27. The method according to claim 26, characterized in that The second device receiving the second request includes: The second device receives the second request sent by the cloud server, where the second request is determined by the cloud server according to the first request sent by the first device.

28. The method according to claim 27, characterized in that The first request includes identification information of the second device.

29. 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.

30. The method according to any one of claims 26 to 28, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

31. The method according to any one of claims 22 to 30, characterized in that The second request includes the type of the service connection and / or identification information of a service that supports connection of the service.

32. The method according to any one of claims 22 to 31, characterized in that The second request includes synchronization information of the service connection.

33. The method according to any one of claims 22 to 32, characterized in that The second request includes first indication information, where the first indication information is used to indicate a transmission channel type of a service connection supported by the first device.

34. The method according to any one of claims 22 to 33, wherein: The method further comprises: The second device sends a response message to the second request, where the response message to the second request is used to indicate starting a connection service for the service.

35. The method according to any one of claims 22 to 34, characterized in that The method further comprises: The second device receives a third request sent by the first device, where the third request is used to discover a device that supports continuing 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 continuing the service.

36. The method according to claim 35, characterized in that The third request is sent by the first device when it is determined that service continuity is required. Whether service continuity is required is determined by the first device based on the second information.

37. The method according to claim 36, wherein The second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

38. The method according to claim 37, wherein The auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a location relationship between the first device and the second device.

39. The method according to any one of claims 35 to 38, wherein The third request is sent in a unicast or multicast manner.

40. The method according to any one of claims 35 to 39, wherein The third request includes the type of service connection and / or identification information of a service supporting connection of the service.

41. The method according to any one of claims 35 to 40, characterized in that The first response includes service continuity service information of the second device, and the service continuity service information includes device information of the second device and / or service continuity service capability information of the second device.

42. The method according to any one of claims 35 to 41, wherein: The first response is further used to indicate a transmission channel type of a service connection supported by the second device.

43. The method according to any one of claims 22 to 42, wherein: The second device is a vehicle-mounted device.

44. A business operation method, characterized in that: include: The cloud server receives a first request sent by a first device, where the first request is used to request a second device to perform service connection.

45. The method according to claim 44, wherein The method further comprises: The cloud server sends a second request to the second device, where the second request is determined based on the first request.

46. ​​The method according to claim 44, wherein The method further comprises: The cloud server sends a second request to the second device, where the second request is the first request.

47. 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.

48. The method according to any one of claims 44 to 46, wherein: The data corresponding to the service connection is sent from the first device to the second device.

49. The method according to any one of claims 44 to 48, wherein The first request includes identification information of the second device.

50. The method according to any one of claims 44 to 49, wherein The first request includes the type of service connection and / or identification information of a service that supports connection of the service.

51. The method according to any one of claims 44 to 50, wherein: The first request includes synchronization information of the service connection.

52. The method according to any one of claims 44 to 51, wherein: The method further comprises: The cloud server sends a response message to the first request to the first device, where the response message to the first request is used to indicate starting a connection service for the business, and the response message to the first request is determined based on the response message to the second request.

53. A business operation device, characterized in that: The apparatus is configured on a first device, and includes: The first sending module is used to send a first request, where the first request is used to request the second device to perform service connection.

54. The device according to claim 53, characterized in that The service connection is performed based on a local communication connection between the first device and the second device.

55. The device according to claim 54, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

56. The device according to claim 53, characterized in that The business continuation is based on the cloud server.

57. The device according to claim 56, characterized in that The first sending module is further used to: send the first request to the cloud server.

58. 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.

59. The device according to claim 56 or 57, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

60. The device according to any one of claims 56 to 59, characterized in that The first request includes identification information of the second device.

61. The device according to any one of claims 53 to 60, 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.

62. The device according to any one of claims 53 to 61, characterized in that The first request includes synchronization information of the service connection.

63. The device according to any one of claims 53 to 62, characterized in that The first request includes first indication information, where the first indication information is used to indicate a transmission channel type for a service connection supported by the first device.

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

65. The device according to any one of claims 53 to 64, characterized in that The device further comprises: A second sending module is used to send a third request, where the third request is used to discover a device that supports continuing 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.

66. The device according to claim 65, characterized in that The third request is sent by the first device when it is determined that service continuity is required. Whether service continuity is required is determined by the first device based on the second information.

67. The device according to claim 66, characterized in that The second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

68. The device according to claim 67, characterized in that The auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a location relationship between the first device and the second device.

69. The device according to any one of claims 65 to 68, characterized in that The third request is sent in a unicast or multicast manner.

70. The device according to any one of claims 65 to 69, characterized in that The third request includes the type of service connection and / or identification information of a service supporting connection of the service.

71. The device according to any one of claims 65 to 70, characterized in that The first response includes service continuity service information of the second device, and the service continuity service information includes device information of the second device and / or service continuity service capability information of the second device.

72. The device according to any one of claims 65 to 71, characterized in that The first response is further used to indicate a transmission channel type of a service connection supported by the second device.

73. The device according to any one of claims 53 to 72, characterized in that The second device is a vehicle-mounted device.

74. A business operation device, characterized in that: The apparatus is configured on a second device, and 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.

75. The device according to claim 74, characterized in that The service connection is performed based on a local communication connection between the first device and the second device.

76. The device according to claim 75, characterized in that The second request is the first request sent by the first device, and the first request is used to request the second device to perform service connection.

77. The device according to claim 75 or 76, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

78. The device according to claim 74, characterized in that The business continuation is based on the cloud server.

79. 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, where the second request is determined by the cloud server according to the first request sent by the first device.

80. The device according to claim 79, characterized in that The first request includes identification information of the second device.

81. 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 cloud server to the second device.

82. The device according to any one of claims 78 to 80, characterized in that The data corresponding to the service connection is sent from the first device to the second device.

83. The device according to any one of claims 74 to 82, characterized in that The second request includes the type of the service connection and / or identification information of a service that supports connection of the service.

84. The device according to any one of claims 74 to 83, characterized in that The second request includes synchronization information of the service connection.

85. The device according to any one of claims 74 to 84, characterized in that The second request includes first indication information, where the first indication information is used to indicate a transmission channel type of a service connection supported by the first device.

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

87. The device according to any one of claims 74 to 86, characterized in that The device further comprises: A second receiving module is configured to receive a third request sent by the first device, where the third request is used to discover a device that supports connecting to the service; The second sending module is used to send a first response to the first device, where the first response is used to indicate that the second device supports continuing the service.

88. The device according to claim 87, characterized in that The third request is sent by the first device when it is determined that service continuity is required. Whether service continuity is required is determined by the first device based on the second information.

89. The device according to claim 88, characterized in that The second information includes one or more of the following information: an application being run by the first device, a type of the application being run by the first device, and auxiliary information.

90. The device according to claim 89, characterized in that The auxiliary information includes one or more of the following information: an activation state of a service connection mode of the first device, a state of an application running on the first device, and a location relationship between the first device and the second device.

91. The device according to any one of claims 87 to 90, characterized in that The third request is sent in a unicast or multicast manner.

92. The device according to any one of claims 87 to 91, characterized in that The third request includes the type of service connection and / or identification information of a service supporting connection of the service.

93. The device according to any one of claims 87 to 92, characterized in that The first response includes service continuity service information of the second device, and the service continuity service information includes device information of the second device and / or service continuity service capability information of the second device.

94. The device according to any one of claims 87 to 93, characterized in that The first response is further used to indicate a transmission channel type of a service connection supported by the second device.

95. The device according to any one of claims 74 to 94, characterized in that The second device is a vehicle-mounted device.

96. A business operation device, characterized in that: The system comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1 to 52.

97. A device, characterized in that The device comprises a processor configured to call a program from a memory to execute the method according to any one of claims 1 to 52.

98. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 52.

99. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 52.

100. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 52.

101. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 52.

Images