Service collaboration methods, devices, terminal equipment and storage media

Abstract

This application relates to the field of information technology and provides a service collaboration method, apparatus, terminal device, and storage medium. The method generates corresponding data nodes based on data provided by any service; the data nodes employ a preset encoding architecture; when the first service runs and generates the first target data, collaborative data is sent to the second service via a data collaboration link, and the second service is invoked to output the second target data based on the collaborative data. Generating data nodes through the preset encoding structure ensures that different data nodes use the same encoding architecture, achieving standardized data reading. This facilitates the service collaboration model's accurate analysis of the first and second data nodes based on the preset encoding architecture, thereby improving the accuracy of data format conversion. Furthermore, by constructing a data collaboration link through the service collaboration model, the second service can accurately obtain information about the operation of the first service, improving service collaboration while lowering the operational threshold for service collaboration.

Description

Technical Field

[0001] This application belongs to the field of information processing technology, and in particular relates to a service collaboration method, apparatus, terminal equipment and storage medium. Background Technology

[0002] With the rapid development of electronic technology, terminal devices can provide users with increasingly diverse services. Taking travel services as an example, they can provide users with a full range of services such as ticket purchase, accommodation booking, navigation, and travel advice, improving the convenience of life, work, or entertainment.

[0003] Currently, different services use different code during development, making data transfer and sharing between them difficult. This results in services operating independently at runtime, limiting their collaborative operation and consequently hindering further improvements in service convenience. Therefore, improving the ability for different services to collaborate has become an urgent problem to solve. Summary of the Invention

[0004] In view of this, embodiments of this application provide a service collaboration method, apparatus, terminal device, and storage medium to solve the problem of poor existing service collaboration capabilities.

[0005] A first aspect of this application provides a service collaboration method, the method comprising:

[0006] Data nodes are generated based on the data available from any service; the data nodes adopt a preset encoding architecture.

[0007] The first data node and the second data node are input into the service collaboration model to obtain a data collaboration link; wherein, the first data node is used to read the first target data that the first service can provide, the second data node is used to read the second target data that the second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data;

[0008] When the first service is running and generating the first target data, the collaborative data is sent to the second service through the data collaboration link, and the second service is invoked to output the second target data based on the collaborative data.

[0009] The first aspect of this application provides a service collaboration method, which generates corresponding data nodes based on data provided by any service; the data nodes adopt a preset encoding architecture; when the first service runs and generates the first target data, collaborative data is sent to the second service through a data collaboration link, and the second service is called to output the second target data according to the collaborative data. By generating data nodes through the preset encoding structure, it can be ensured that different data nodes adopt the same encoding architecture, realize the standardized reading of data, facilitate the service collaboration model to accurately analyze the first data node and the second data node according to the preset encoding architecture, thereby improving the accuracy of data format conversion, and constructing a data collaboration link through the service collaboration model, so that the second service can accurately know the running status of the first service, thereby improving service collaboration while reducing the operating threshold of service collaboration.

[0010] A second aspect of this application provides a service collaboration device, including:

[0011] A generation module is used to generate corresponding data nodes based on data available from any service; the data nodes adopt a preset encoding architecture.

[0012] An assembly module is used to input a first data node and a second data node into a service collaboration model to obtain a data collaboration link; wherein, the first data node is used to read first target data that a first service can provide, the second data node is used to read second target data that a second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data;

[0013] The collaboration module is used to send the collaboration data to the second service through the data collaboration link when the first service is running and generating the first target data, and to call the second service to output the second target data according to the collaboration data.

[0014] A third aspect of this application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the service collaboration method provided in the first aspect of this application.

[0015] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the service collaboration method provided in the first aspect of this application.

[0016] It is understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0019] Figure 2 This is a schematic diagram of the architecture of an operating system running on a terminal device provided in an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of the first type of service collaboration method provided in the embodiments of this application;

[0021] Figure 4 This is a schematic diagram of the architecture of the first data node and the second data node using the same data transfer protocol, as provided in the embodiments of this application.

[0022] Figure 5 This is a schematic diagram of the architecture of the first data node and the second data node using different data transfer protocols provided in the embodiments of this application;

[0023] Figure 6 This is a schematic diagram of the second process of the service collaboration method provided in the embodiments of this application;

[0024] Figure 7 This is a schematic diagram of the third process of the service collaboration method provided in the embodiments of this application;

[0025] Figure 8 This is a schematic diagram of the first interface provided in this application embodiment for displaying collaborative information via gesture instructions;

[0026] Figure 9 This is a schematic diagram of a second interface provided in this application embodiment for displaying collaborative information via gesture instructions;

[0027] Figure 10 This is a schematic diagram of a service collaboration device provided in an embodiment of this application;

[0028] Figure 11 This is a timing diagram illustrating the interaction between the service collaboration device and the server provided in this application embodiment to achieve service collaboration functions. Detailed Implementation

[0029] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0030] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0031] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0032] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0033] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0034] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0035] In applications, different services are developed with distinct code, making data transfer and sharing between them difficult. This results in services operating independently at runtime, limiting their collaborative operation and consequently hindering further improvements in service convenience. Therefore, improving the ability for different services to collaborate has become a pressing issue.

[0036] To address the aforementioned technical issues, this application provides a service collaboration method. This method generates corresponding data nodes based on data provided by any service. The data nodes employ a preset encoding architecture. When the first service runs and generates first target data, collaborative data is sent to the second service via a data collaboration link. The second service then outputs second target data based on the collaborative data. Generating data nodes through the preset encoding structure ensures that different data nodes use the same encoding architecture, enabling standardized data reading. This facilitates accurate analysis of the first and second data nodes by the service collaboration model based on the preset encoding architecture, thereby improving the accuracy of data format conversion. Furthermore, by constructing a data collaboration link through the service collaboration model, the second service can accurately obtain information about the operation of the first service, thus improving service collaboration while lowering the operational threshold for service collaboration.

[0037] The service collaboration method provided in this application can be applied to terminal devices. Terminal devices can be mobile phones, tablets, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc. This application does not impose any restrictions on the specific type of terminal device.

[0038] Figure 1An exemplary structural diagram of terminal device 1 is shown. Terminal device 1 includes a processor 10, a memory 20, an audio module 30, a camera module 40, a sensor module 50, an input module 60, a display module 70, a wireless communication module 80, and a power module 90. The audio module 30 may include a speaker 31 and a microphone 32, the camera module 40 may include a short-focus camera 41, a long-focus camera 42, and a flash 43, the sensor module 50 may include an infrared sensor 51, an accelerometer 52, a position sensor 53, a fingerprint sensor 54, and an iris sensor 55, the input module 60 may include a touch panel 61 and an external input unit 62, and the wireless communication module 80 may include wireless communication units such as Bluetooth, optical wireless, mobile communications, wireless local area network (WLAN), near field communication (NFC), and ZigBee.

[0039] In applications, processor 10 can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0040] In applications, memory 20 may be an internal storage unit of the terminal device in some embodiments, such as the hard drive or memory of the terminal device. In other embodiments, memory 20 may be an external storage device of the terminal device, such as a plug-in hard drive, smart media card (SMC), secure digital card (SD), flash card, etc., provided on the terminal device. Furthermore, memory 20 may include both internal and external storage units of the terminal device. Memory 20 is used to store computer programs 21 such as operating system, application programs, and bootloader. Memory 20 may also be used to temporarily store data that has been output or will be output.

[0041] In the application, the display module 70 can be a flat screen, a curved screen, or a flexible screen. Specifically, it can be a foldable screen. A foldable screen can include at least one flexible screen, or it can include at least one flexible screen and at least one flat screen or a curved screen. This application embodiment does not impose any restrictions on the specific type of the display module 70.

[0042] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on terminal device 1. In other embodiments of this application, terminal device 1 may include more or fewer components than illustrated, or combine certain components, or different components, such as a graphics processor. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0043] like Figure 2 The diagram shows the architecture of the operating system running on the terminal device 1 provided in this application embodiment. The layered architecture can divide the operating system into multiple layers, which communicate with each other through software interfaces. In some embodiments, the operating system can be divided into an application layer 100, a framework layer 200, a system runtime library layer 300, a hardware abstraction layer 400, and a Linux kernel layer 500 from top to bottom.

[0044] It should be noted that the type of operating system can be Android, a customized operating system based on Android, or other different types of operating systems. This application embodiment does not limit the specific type of operating system.

[0045] In application, the five layers of the operating system are explained below:

[0046] Application layer 100 may include built-in applications 120 and upper-layer applications 110 provided by third-party application providers. Applications in application layer 100 can interact directly with users to realize different functions provided by the application. For example, application layer 100 may include built-in applications such as email, telephone, calendar, camera, contacts and Bluetooth, as well as upper-layer applications such as map positioning, food delivery and video playback.

[0047] The framework layer 200 may include application programming interfaces (APIs) and programming frameworks. The APIs can be used to provide operating system developers with interfaces for developing applications, and can also be used to call corresponding basic services when applications in the application layer implement different functions. For example, the framework layer may include different types of APIs such as window managers, content providers, phone managers, location managers, and view systems.

[0048] The window manager is used to manage window programs. Specifically, it can be used to get the window size, and also to determine whether there is a status bar, whether the screen is locked, and whether the screen is captured.

[0049] The content provider is used to store and retrieve data and make the data accessible to applications. The data may include videos, images, audio, call logs, contacts, browsing history, and bookmarks.

[0050] The phone manager is used to provide communication functions for terminal device 1, such as managing call status, including answering and hanging up calls;

[0051] The location manager is used to obtain the location information of terminal device 1, which may include different types of location information such as satellite location information (obtained through the Global Positioning System), network location information (obtained through network positioning services), and fused location information (obtained through fused positioning services);

[0052] The view system provides visual controls, such as controls for displaying text and controls for displaying images, and is also used to build applications for displaying application layer 100. The view system can run multiple visual controls simultaneously, allowing the terminal device to display multiple views at the same time, for example, a view displaying text and a view displaying images simultaneously.

[0053] The system runtime library layer (Native) 300 may include a C / C++ library 310 and an Android runtime library 320. The C / C++ library 310 may include a drawing function library, a font engine, a rendering engine, a multimedia library, and a database engine. Specifically, the drawing function library may be OpenGL For Embedded Systems 3D (an open 3D graphics library for embedded systems); the font engine provides different fonts, specifically FreeType (a portable font engine); the rendering engine renders 2D or 3D graphics, specifically Skia Graphics Library (an engine for rendering 2D graphics); the multimedia library (Media Framework) supports playback, recording, and replay of different audio and video formats; and the database engine provides storage functionality for different types of databases, allowing different types of data to be stored in different databases as needed, or stored uniformly in a single database.

[0054] The Android runtime library 320 includes core libraries and the Android Runtime (ART). In Android 5.0 and later, the Dalvik virtual machine was replaced by ART. The core libraries provide most of the functionality of the Java language core libraries, allowing developers to write Android applications using Java. Compared to the Java Virtual Machine (JVM), the Dalvik virtual machine is specifically designed for mobile devices, allowing multiple instances of the virtual machine to run simultaneously within limited memory, and each Dalvik application executes as an independent Linux process. Independent processes prevent all programs from being shut down in the event of a virtual machine crash. ART, which replaces the Dalvik virtual machine, uses a different mechanism. In Dalvik, bytecode needs to be converted into machine code by a just-in-time (JIT) compiler every time an application runs, which slows down application performance. In the ART environment, the bytecode is pre-compiled into machine code during the first installation, making it a truly native application.

[0055] The Hardware Abstraction Layer (HAL) 400 is an interface layer located between the operating system kernel and the hardware circuitry. Its purpose is to abstract the hardware. To protect the intellectual property of hardware manufacturers, it hides the hardware interface details of specific platforms, thereby providing the operating system with a virtual hardware platform that is hardware-independent and portable across multiple platforms. From a software and hardware testing perspective, both software and hardware testing can be performed separately based on the HAL, allowing software and hardware testing to be conducted in parallel.

[0056] Linux kernel layer 500 can be used to provide system services for the operating system, including operating system security services, memory management, process management, network protocol stack and driver model, etc.

[0057] Understandable, Figure 2 The diagram shown is merely an example of an operating system architecture. The operating system architecture can also be four-layer or six-layer. The architecture of a four-layer operating system may include: an application layer, a framework layer, a system runtime library layer, and a Linux kernel layer. The architecture of a six-layer operating system may include: an application layer, a framework layer, a system runtime library layer, a hardware abstraction layer, a Linux kernel layer, and a hardware device layer. The method embodiments of this application do not limit the number of architecture layers or the specific architecture of the operating system.

[0058] like Figure 3 As shown, the service collaboration method provided in this application embodiment is applied to a terminal device and includes the following steps S301 to S303:

[0059] Step S301: Generate corresponding data nodes based on the data provided by any service; the data nodes adopt a preset encoding architecture.

[0060] In applications, services are programs, routines, or processes that perform specified functions to support the program itself, other foreground programs, or underlying / background programs. Services can be started and run by a program or by the underlying (operating) system. For example, a service can be a system-level location service, cellular network service, Bluetooth service, or fault recovery service, or it can be a foreground program providing navigation services, network sharing services, Bluetooth headset services, power-off services, photo-taking services, or video playback services. This application's embodiments do not impose any restrictions on the type of service.

[0061] In applications, services typically receive input data and provide output data during runtime. Taking a fault recovery service as an example, the input data for a fault recovery service may include the operating status of preset critical services, hardware operating status, and battery cell temperature, while the output data may be a shutdown signal or a signal to maintain operation. The data provided by the service mentioned in this application embodiment refers to the service's output data.

[0062] In the application, after any service is connected to the system, a corresponding data node can be generated based on the data provided by any of the aforementioned services. The data node can connect to the data output interface corresponding to any of the aforementioned services, enabling the data node to collect relevant data when the service outputs data. The data node can adopt a preset encoding structure to ensure that different data nodes corresponding to different services use the same encoding architecture, thereby allowing the system to uniformly manage all data nodes and achieve standardized reading of data provided by services.

[0063] The various parameters of the preset encoding architecture can be set according to actual needs. For example, the preset encoding architecture may include language type parameters (specifically, C, C++, Python, or Java, etc.), syntax parameters (specifically, service name, node name, node ID, data type, or data format, etc.) and interface parameters (used to support node calls), etc. This application embodiment does not impose any restrictions on the specific architecture type of the preset encoding architecture.

[0064] In one embodiment, step S301 includes:

[0065] If any service contains a preset generation interface for a data flow protocol, generate the corresponding data flow protocol based on the preset generation interface and preset protocol parameters;

[0066] Generate corresponding data nodes based on the data flow protocol, the preset encoding architecture, and the data available from any service;

[0067] If any service does not include a preset generation interface for a data transfer protocol, the corresponding data node will be generated based on the preset data transfer protocol, the preset encoding architecture, and the data that any service can provide.

[0068] In applications, services can include preset generation interfaces for data flow protocols. These preset generation interfaces can be written by developers according to the system's development guidelines or written by the developers themselves. When generating data nodes, the system can determine whether any of the aforementioned services includes a preset generation interface for a data flow protocol. If so, the system can generate the corresponding data flow protocol by inputting the preset protocol parameters into the preset generation interface, and then generate the corresponding data node based on the data flow protocol, the preset encoding architecture, and the data output interface of any of the aforementioned services. If not, the system can directly apply the preset data flow protocol and generate the corresponding data node based on the preset data flow protocol, the preset encoding architecture, and the data output interface of any of the aforementioned services.

[0069] The preset protocol parameters may include the protocol type of the data flow protocol, the data format of the data stored by the data node, and the convertible data formats.

[0070] Step S302: Input the first data node and the second data node into the service collaboration model to obtain the data collaboration link; wherein, the first data node is used to read the first target data that the first service can provide, the second data node is used to read the second target data that the second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data.

[0071] In applications, when establishing collaboration between two services, it's essential to first determine if the data flow protocols of the first and second data nodes are identical. If so, a data collaboration link between the first and second data nodes can be directly established (see reference). Figure 4 As shown, Figure 4 An exemplary diagram illustrates an architecture where the first and second data nodes perform data flow through the same data flow protocol. The first target data is directly converted into collaborative data using this same protocol. Alternatively, the first and second data nodes can be input into a service collaboration model to obtain a data collaboration link, which is then used to convert the data format of the first target data (see reference). Figure 5 As shown, Figure 5An exemplary diagram illustrates the architecture of a first data node and a second data node communicating via different data transfer protocols to obtain collaborative data. This enables the second data node to receive and read collaborative data, preventing the second data node from being unable to read the first target data with a different data format. The working principle of the service collaboration model is explained below:

[0072] In the application, the service collaboration model is used to determine the data flow parameters of the first target data according to the first data flow protocol of the first data node and the second data flow protocol of the second data node, and to generate a data collaboration link according to the first data flow protocol, the second data flow protocol and the data flow parameters of the first target data; the data flow parameters are used to determine the data flow path of the first target data and the data format of the collaborative data.

[0073] The data flow path can specifically indicate the interface to be called when the first target data is converted into collaborative data, and the interface to be called when the collaborative data is transmitted to the second service; the data format can indicate the data type (e.g., integer, floating-point, or string) and data structure (e.g., function type, constructor type, pointer type, character set type, or number base type).

[0074] For example, suppose the first service is a ticket purchase service, and the first target data is the arrival time and destination information, where the data type of the arrival time is floating-point (Float) and the data type of the destination information is string (Text); the second service is an accommodation booking service, and the second target data is the hotel name and distance to the hotel, both of which are of string (Char). After data format conversion, the data types of the arrival time and destination information in the collaborative data are all converted to string (Char).

[0075] It should be noted that when the data flow protocols of the first and second data nodes are the same, the data flow path of the first target data and the data format of the collaborative data can be determined through the same data flow protocol. When the data flow protocols of the first and second data nodes are different, it is necessary to determine the matching relationship between the first and second data flow protocols through a service collaboration model. The matching relationship includes the matching degree and data flow parameters to achieve cross-protocol flow of the first target data.

[0076] In application, the service collaboration model takes two different data flow protocols as input during training and outputs a predicted matching relationship. A loss function is established based on the actual matching relationship and the predicted matching relationship to train the service collaboration model until the accuracy of the predicted matching relationship reaches the expected accuracy.

[0077] In one embodiment, step S302 further includes:

[0078] Obtain the matching degree between the first data transfer protocol and the second data transfer protocol;

[0079] If the matching degree between the first data transfer protocol and the second data transfer protocol is lower than the preset matching degree, the generation of data collaboration links will be stopped.

[0080] In application, if the matching degree between the first data transfer protocol and the second data transfer protocol is lower than the preset matching degree, the generation of data collaboration links can be stopped to avoid data format conversion errors after the two protocols are matched, which would lead to data distortion and affect the service collaboration effect.

[0081] Step S303: When the first service is running and generating the first target data, the collaborative data is sent to the second service through the data collaboration link, and the second service is called to output the second target data based on the collaborative data.

[0082] In the application, after establishing a data collaboration link between the first data node and the second data node, the second data node can receive and read collaborative data, thereby sending collaborative data to the second service through the data collaboration link and calling the second service to output the second target data based on the collaborative data, thus realizing collaborative calling between the first service and the second service.

[0083] In the application, corresponding data nodes are generated based on the data provided by any service. The data nodes adopt a preset encoding architecture. When the first service runs and generates the first target data, collaborative data is sent to the second service through the data collaboration link, and the second service is called to output the second target data according to the collaborative data. By generating data nodes through the preset encoding structure, it can be ensured that different data nodes corresponding to different services adopt the same encoding architecture, realize the standardized reading of data, and facilitate the service collaboration model to accurately analyze the first data node and the second data node according to the preset encoding architecture, thereby improving the accuracy of data format conversion. Furthermore, by constructing a data collaboration link through the service collaboration model, the second service can accurately know the running status of the first service, thereby improving service collaboration while reducing the operational threshold of service collaboration.

[0084] like Figure 6 As shown, in one embodiment, based on Figure 3 The corresponding embodiment includes the following steps S601 to S605:

[0085] Step S601: Generate corresponding data nodes based on the data provided by any service; the data nodes adopt a preset encoding architecture.

[0086] In application, the service collaboration method provided in step S601 can refer to the relevant description in step S301 above, and will not be repeated here.

[0087] Step S602: Obtain the data correlation degree between the first data node and other data nodes;

[0088] Step S603: Sort the other data nodes in ascending order according to the data correlation to obtain the second data node.

[0089] In application, after generating data nodes but before establishing data collaboration links, the data correlation degree between the first data node and other data nodes can be obtained. This correlation degree can be determined through a table lookup, improving the alignment between the data correlation degree and the actual application scenario. Based on the data correlation degree, other data nodes are then sorted in ascending order to obtain the second data node. It should be noted that in practical applications, the first data node can establish data collaboration links with multiple data nodes with high data correlation degrees. Establishing a data collaboration link between the first and second data nodes is merely an example.

[0090] In one embodiment, data correlation is determined based on big data information and target user profiles.

[0091] In application, the system can acquire target user profiles during operation and combine them with big data information to determine data correlation, improve the fit between data correlation and actual application scenarios, and thus coordinate highly correlated services based on actual application scenarios, improve the practicality of data collaboration links and reduce the occupation of ineffective resources.

[0092] Step S604: Sort the other data nodes in ascending order according to the data correlation to obtain the second data node.

[0093] Step S605: Input the first data node and the second data node into the service collaboration model to obtain the data collaboration link;

[0094] Step S606: When the first service is running and generating the first target data, the collaborative data is sent to the second service through the data collaboration link, and the second service is called to output the second target data based on the collaborative data.

[0095] In application, the service collaboration methods provided in steps S404 and S405 can be referred to the relevant descriptions of steps S302 and S303 above, and will not be repeated here.

[0096] In application, by selecting second data nodes with high correlation to the first data node and establishing data collaboration links, the correlation between data and the fit with actual application scenarios can be improved. This allows for the collaboration of highly correlated services based on actual application scenarios, thereby improving the practicality of data collaboration links and reducing the occupation of ineffective resources.

[0097] like Figure 7As shown, in one embodiment, based on Figure 6 The corresponding embodiment includes the following steps S701 to S706:

[0098] Step S701: Generate corresponding data nodes based on the data provided by any service; the data nodes adopt a preset encoding architecture;

[0099] Step S702: Obtain the data correlation degree between the first data node and other data nodes;

[0100] Step S703: Sort the other data nodes in ascending order according to the data correlation to obtain the second data node;

[0101] Step S704: Input the first data node and the second data node into the service collaboration model to obtain the data collaboration link.

[0102] In application, the service collaboration methods provided in steps S701 to S704 can refer to the relevant descriptions in steps S501 to S504 above, and will not be repeated here.

[0103] Step S705: When the first service runs and generates the first target data, output collaborative information; the collaborative information is used to display the second service associated with the first service on the front end;

[0104] Step S706: If the collaborative information is responded to, collaborative data is sent to the second service according to the data collaborative link corresponding to the collaborative information, and the second service is invoked to output the second target data according to the collaborative data.

[0105] In the application, when the first service runs and generates the first target data, the second service can be automatically invoked through a data collaboration link to achieve intelligent service recommendation. Alternatively, collaborative information can be output, allowing the user to confirm whether to invoke the second service. Collaborative information can be displayed through a pop-up window or a gesture indicator (see reference). Figure 8 and Figure 9 As shown in the example, a schematic diagram of an interface where collaborative information is displayed via gesture instructions is illustrated. When collaborative information is displayed via gesture instructions, if the user performs the corresponding gesture according to the gesture instructions, it is determined that the collaborative information has been responded to. The gestures can be single-finger, two-finger, or three-finger operations such as swiping, clicking, or long-pressing. This application embodiment does not impose any restrictions on the type of gesture.

[0106] In the application, by outputting collaborative information when the first service runs and generates the first target data, users can choose whether to call the second service to collaborate with the first service according to actual needs, realizing the visualization and intuitiveness of service collaboration calls, which can effectively improve the utilization rate of service collaboration functions; at the same time, it ensures that users allow the first target data of the first service to be transmitted to the second service, thus improving the data privacy protection capability.

[0107] It should be understood that the sequence number of each step in the above embodiments does not imply 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 this application.

[0108] like Figure 10 As shown in the illustration, this application also provides a service collaboration device 2 for executing the steps described in the service collaboration method embodiment applied to a terminal device. The service collaboration device can be a virtual appliance within the terminal device, run by the terminal device's processor, or it can be the terminal device itself.

[0109] like Figure 10 As shown, the service collaboration device 2 provided in this application embodiment includes:

[0110] The generation module 210 is used to generate corresponding data nodes based on the data provided by any service; the data nodes adopt a preset encoding architecture;

[0111] Assembly module 220 is used to input the first data node and the second data node into the service collaboration model to obtain a data collaboration link; wherein, the first data node is used to read the first target data that the first service can provide, the second data node is used to read the second target data that the second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data;

[0112] The collaboration module 230 is used to send collaborative data to the second service through the data collaboration link when the first service is running and generating the first target data, and to call the second service to output the second target data based on the collaborative data.

[0113] In one embodiment, the generation module 210 includes:

[0114] The first generation unit is used to generate a corresponding data flow protocol based on the preset generation interface and preset protocol parameters if any service contains a preset generation interface for a data flow protocol.

[0115] Based on the data flow protocol, the preset encoding architecture, and the data available from any service, corresponding data nodes are generated.

[0116] The second generation unit is used to generate corresponding data nodes based on the preset data flow protocol, the preset encoding architecture, and the data that any service can provide if any service does not contain a preset generation interface for the data flow protocol.

[0117] In one embodiment, the service collaboration device 2 further includes:

[0118] The association module is used to obtain the data association degree between the first data node and other data nodes;

[0119] The other data nodes are sorted in ascending order based on their data correlation to obtain the second data node.

[0120] In one embodiment, the collaboration module 230 includes:

[0121] The collaborative information output unit is used to output collaborative information when the first service runs and generates the first target data; the collaborative information is used to display the second service associated with the first service on the front end;

[0122] The collaborative response unit is used to send collaborative data to the second service according to the data collaborative link corresponding to the collaborative information if collaborative information is responded to, and to call the second service to output the second target data according to the collaborative data.

[0123] In applications, the modules in the service collaboration device 2 can be software program modules, or they can be implemented through different logic circuits integrated in the processor, or they can be implemented through multiple distributed processors.

[0124] Figure 11 An exemplary timing diagram is shown illustrating the interaction between the service collaboration device and the server to achieve service collaboration functionality.

[0125] In applications, service collaboration models can be trained on servers and deployed to terminal devices after training. Update information of service collaboration models can also be transmitted to terminal devices. Software information of service collaboration devices can also be downloaded and updated in the cloud via servers, giving service collaboration devices iterative capabilities.

[0126] It should be noted that the information interaction and execution process between the above modules are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, which will not be repeated here.

[0127] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The functional modules in the embodiments can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules can be implemented in hardware or as software functional modules. Furthermore, the specific names of the functional modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the modules in the above system can be referred to the corresponding process in the above method embodiments, and will not be repeated here.

[0128] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the above-described service collaboration method embodiments.

[0129] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable storage medium can include at least: any entity or device capable of carrying the computer program code to the camera terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0130] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0132] In the embodiments provided in this application, it should be understood that the disclosed terminal devices and methods can be implemented in other ways. For example, the terminal device embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0133] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A service collaboration method, characterized in that, include: Data nodes are generated based on the data available from any service; the data nodes adopt a preset encoding architecture. The first data node and the second data node are input into the service collaboration model to obtain a data collaboration link; wherein, the first data node is used to read the first target data that the first service can provide, the second data node is used to read the second target data that the second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data; When the first service is running and generating the first target data, the collaborative data is sent to the second service through the data collaboration link, and the second service is invoked to output the second target data based on the collaborative data.

2. The service collaboration method as described in claim 1, characterized in that, The generation of corresponding data nodes based on data available from any service includes: If any of the services includes a preset generation interface for a data transfer protocol, a corresponding data transfer protocol is generated based on the preset generation interface and preset protocol parameters; Based on the data flow protocol, the preset encoding architecture, and the data that any of the services can provide, corresponding data nodes are generated.

3. The service collaboration method as described in claim 1, characterized in that, The generation of corresponding data nodes based on data available from any service includes: If any of the services does not include a preset generation interface for a data transfer protocol, a corresponding data node is generated based on the preset data transfer protocol, the preset encoding architecture, and the data that any of the services can provide.

4. The service collaboration method as described in claim 1, characterized in that, The service collaboration model is used to determine the data flow parameters of the first target data according to the first data flow protocol of the first data node and the second data flow protocol of the second data node, and to generate a data collaboration link according to the first data flow protocol, the second data flow protocol and the data flow parameters of the first target data; the data flow parameters are used to determine the data flow path of the first target data and the data format of the collaborative data.

5. The service collaboration method as described in claim 1, characterized in that, The method further includes: Obtain the data correlation between the first data node and other data nodes; The other data nodes are sorted in ascending order based on the data correlation to obtain the second data node.

6. The service collaboration method as described in claim 5, characterized in that, The data correlation is determined based on big data information and target user profiles.

7. The service collaboration method as described in any one of claims 1 to 6, characterized in that, When the first service is running and generates the first target data, the process of sending the collaborative data to the second service through the data collaboration link, and calling the second service to output the second target data based on the collaborative data, includes: When the first service is running and generates the first target data, collaborative information is output; the collaborative information is used to display the second service associated with the first service on the front end; If the collaborative information is responded to, the collaborative data is sent to the second service according to the data collaborative link corresponding to the collaborative information, and the second service is invoked to output the second target data according to the collaborative data.

8. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the service collaboration method as described in any one of claims 1 to 7.

9. A service collaboration device, characterized in that, include: The generation module is used to generate corresponding data nodes based on the data provided by any service. The data nodes adopt a preset encoding architecture; An assembly module is used to input a first data node and a second data node into a service collaboration model to obtain a data collaboration link; wherein, the first data node is used to read first target data that a first service can provide, the second data node is used to read second target data that a second service can provide, and the data collaboration link is used to convert the data format of the first target data according to the data format of the second target data to obtain collaborative data; The collaboration module is used to send the collaboration data to the second service through the data collaboration link when the first service is running and generating the first target data, and to call the second service to output the second target data according to the collaboration data.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the service collaboration method as described in any one of claims 1 to 7.

Images