Service collaboration method and device, terminal equipment and storage medium

Abstract

The invention is suitable for the technical field of information, and provides a service collaboration method and device, terminal equipment and a storage medium. According to the method, the corresponding data node is generated based on the data which can be provided by any service; the data nodes adopt a preset coding architecture; when the first service runs and generates the first target data, the collaborative data is sent to the second service through the data collaborative link, the second service is called to output the second target data according to the collaborative data, and the data nodes are generated through the preset coding structure, so that different data nodes can adopt the same coding architecture; standardized reading of the data is realized, the service collaboration model can accurately analyze the first data node and the second data node according to the preset coding architecture, so that the accuracy of data format conversion is improved, the data collaboration link is constructed through the service collaboration model, the second service can accurately know the operation condition of the first service, and the user experience is improved. And the operation threshold of service collaboration is reduced while the service collaboration is improved.

Description

Technical Field

[0001] The present application belongs to the field of information processing technology, and in particular, relates to a service collaboration method, apparatus, terminal device and storage medium. Background Art

[0002] With the rapid development of electronic technology, the types of services that terminal devices can provide to users are becoming more and more diverse. Taking travel services as an example, they can provide users with full-scenario services such as ticket purchase, accommodation reservation, navigation, travel advice, etc., which improves the convenience of life, work or entertainment.

[0003] At present, different services have different codes when they are developed, so it is difficult to transfer and share data between different services, which leads to the independence of different services at runtime, limiting the collaborative operation between different services, and further limiting the further improvement of service convenience. Therefore, how to improve the ability of collaborative operation between different services has become an urgent problem to be solved. Summary of the invention

[0004] In view of this, the embodiments of the present 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 an embodiment of the present application provides a service collaboration method, the method comprising:

[0006] Generate corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture;

[0007] Inputting 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 can be provided by the first service, and the second data node is used to read the second target data that can be provided by the second service, 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 runs and generates first target data, the collaborative data is sent to the second service through the data collaborative link, and the second service is called to output second target data according to the collaborative data.

[0009] The first aspect of an embodiment of the present application provides a service collaboration method, by generating corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture; when the first service runs and generates first target data, the collaborative data is sent to the second service through a data collaboration link, and the second service is called to output second target data according to the collaborative data. The data nodes are generated by the preset coding structure, which can ensure that different data nodes adopt the same coding architecture to achieve standardized data reading, and facilitate the service collaboration model to accurately analyze the first data node and the second data node according to the preset coding 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 operation status of the first service, while improving service collaboration and lowering the operation threshold of service collaboration.

[0010] A second aspect of an embodiment of the present application provides a service collaboration device, including:

[0011] A generation module, used to generate corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture;

[0012] An assembly module, 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 can be provided by the first service, and the second data node is used to read second target data that can be provided by the second service, 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 runs and generates the first target data, and call the second service to output the second target data according to the collaboration data.

[0014] The third aspect of an embodiment of the present 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 implements the steps of the service collaboration method provided in the first aspect of the embodiment of the present application when executing the computer program.

[0015] The fourth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of the service collaboration method provided in the first aspect of the embodiments of the present application.

[0016] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present 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 the present application;

[0020] Figure 3 This is a schematic diagram of the first process of the service collaboration method provided in the embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of an architecture in which a first data node and a second data node perform data transfer through the same data transfer protocol provided by an embodiment of the present application;

[0022] Figure 5 It is a schematic diagram of an architecture in which a first data node and a second data node perform data transfer through different data transfer protocols provided by an embodiment of the present application;

[0023] Figure 6 This is a second flow chart of the service collaboration method provided in the embodiment of the present application;

[0024] Figure 7 This is a third flow chart of the service collaboration method provided in the embodiment of the present application;

[0025] Figure 8 This is a schematic diagram of a first interface in which collaborative information can be displayed through gesture indications provided in an embodiment of the present application;

[0026] Fig. 9 This is a schematic diagram of a second interface in which collaborative information can be displayed through gesture indications provided in an embodiment of the present application;

[0027] Fig.10 It is a structural diagram of a service collaboration device provided in an embodiment of the present application;

[0028] Fig.11 It is a timing diagram of the service collaboration device provided in an embodiment of the present application interacting with a server to implement a service collaboration function. DETAILED DESCRIPTION

[0029] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

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

[0031] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0032] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0033] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0034] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0035] In applications, different services have different codes when they are developed, so it is difficult to transfer and share data between different services, which leads to the independence of different services at runtime, limiting the collaborative operation between different services, and further limiting the further improvement of service convenience. Therefore, how to improve the ability of collaborative operation between different services has become an urgent problem to be solved.

[0036] In response to the above technical problems, an embodiment of the present application provides a service collaboration method, which generates corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture; when the first service runs and generates 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 according to the collaborative data. The data nodes are generated by the preset coding structure, which can ensure that different data nodes adopt the same coding architecture to achieve standardized data reading, facilitate the service collaboration model to accurately analyze the first data node and the second data node according to the preset coding 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 operation status of the first service, while improving the service collaboration and lowering the operation threshold of service collaboration.

[0037] The service collaboration method provided in the embodiment of the present application can be applied to a terminal device. The terminal device can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. The embodiment of the present application does not impose any restrictions on the specific type of the terminal device.

[0038] Figure 1The schematic diagram of the structure of the terminal device 1 is shown as an example. The 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 acceleration sensor 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 communication (Optical Wireless), mobile communication (Mobile Communications), wireless local area network (Wireless Local Area Network, WLAN), near field communication (Near Field Communication, NFC) and ZigBee protocol (ZigBee).

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

[0040] In application, the memory 20 may be an internal storage unit of the terminal device in some embodiments, such as a hard disk or memory of the terminal device. The memory 20 may also be an external storage device of the terminal device in other embodiments, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the terminal device. Further, the memory 20 may also include both an internal storage unit of the terminal device and an external storage device. The memory 20 is used to store computer programs 21 such as an operating system, an application program, and a boot loader (BootLoader). The memory 20 may also be used to temporarily store data that has been output or is to be output.

[0041] In application, the display module 70 can be a flat screen, a curved screen or a flexible screen, specifically a folding screen. The folding screen may include at least one flexible screen, or the folding screen may include at least one flexible screen and at least one flat screen or curved screen. The embodiment of the present application does not impose any restrictions on the specific type of the display module 70.

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

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

[0044] It should be noted that the type of the operating system may be an Android system, an operating system customized based on the Android system, or other different types of operating systems. The embodiments of the present application do not impose any limitation on the specific type of the operating system.

[0045] In the application, the five layers of the operating system are introduced as follows:

[0046] The application layer 100 may include built-in applications 120 built into the system and upper layer applications 110 provided by third-party application providers. The application programs of the application layer 100 may interact directly with users to implement different functions provided by the application programs. For example, the application layer 100 may specifically include built-in applications such as email, phone, calendar, camera, contacts, and Bluetooth, and upper layer applications such as map positioning, food delivery, and video playback.

[0047] The framework layer (Application Framwork) 200 may include an application programming interface (API) and a programming framework. The application programming interface may be used to provide an interface for operating system developers to develop applications, and may also be used to call corresponding basic services for applications in the application layer when implementing different functions. For example, the framework layer may include different types of application programming interfaces such as window managers, content providers, phone managers, positioning managers, and view systems.

[0048] The window manager is used to manage window programs. Specifically, it can be used to obtain the window size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0049] Content providers are 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 of the terminal device 1, such as management of call status, including answering and hanging up calls, etc.;

[0051] The positioning manager is used to obtain the location information of the 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 a network positioning service), and fused location information (obtained through a fused positioning service);

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

[0053] The system runtime layer (Native) 300 may include a C / C++ library 310 and an Android runtime library 320, wherein the C / C++ library 310 may include a drawing function library, a font engine, a rendering engine, a multimedia library, and a database engine, etc. The drawing function library may be OpenGL For Embedded Systems 3D (a 3D open graphics library running on embedded systems); the font engine is used to provide different fonts, and may be FreeType (a portable font engine); the rendering engine is used to render two-dimensional graphics or three-dimensional graphics, and may be Skia Graphics Library (an engine for rendering two-dimensional graphics); the multimedia library (Media Framework) is used to support the playback, recording, and playback of audio and video in different formats; the database engine is used to provide storage functions for different types of databases, so that different types of data can be stored in different types of databases according to actual needs, or different types of data can be stored in a unified database.

[0054] The Android runtime 320 may include core libraries (Core Libraries) and an Android runtime environment (Android Runtime, ART), wherein after the Android 5.0 system, the Dalvik virtual machine is replaced by ART. The core library provides most of the functions of the Java language core library, so that developers can use the Java language to write Android applications. Compared with the Java Virtual Machine (Java Virtual Machine, JVM), the Dalvik virtual machine is specially customized for mobile devices, allowing multiple virtual machine instances to run simultaneously in limited memory, and each Dalvik application is executed as an independent Linux process. Independent processes can prevent all programs from being closed when the virtual machine crashes. The mechanism of ART, which replaces the Dalvik virtual machine, is different from Dalvik. Under Dalvik, every time an application runs, the bytecode needs to be converted into machine code by a just-in-time compiler, which slows down the running efficiency of the application. In the ART environment, when the application is installed for the first time, the bytecode will be pre-compiled into machine code, making it a truly local application.

[0055] The Hardware Abstraction Layer (HAL) 400 is an interface layer between the operating system kernel and the hardware circuit. Its purpose is to abstract the hardware. In order to protect the intellectual property rights of hardware manufacturers, it hides the hardware interface details of a specific platform, thereby providing a virtual hardware platform for the operating system, making it hardware-independent and portable on multiple platforms. From the perspective of software and hardware testing, the testing of software and hardware can be completed based on the hardware abstraction layer, so that the testing of software and hardware can be carried out in parallel.

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

[0057] Understandably, Figure 2 The architecture diagram of an operating system is only shown by way of example. The operating system architecture can also be four-layer or six-layer, wherein the architecture of a four-layer operating system may include: an application layer, a framework layer, a system runtime 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 layer, a hardware abstraction layer, a Linux kernel layer and a hardware device layer. The embodiment of the method of the present application does not impose any limitation on the number of architecture layers and the specific architecture of the operating system.

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

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

[0060] In applications, services are programs, routines or processes that perform specified functions to support their own programs, other foreground programs or bottom / background programs. Services can be started and run based on programs, or they can be started and run based on the bottom layer of the (operating) system. For example, services can be positioning services, cellular network services, Bluetooth services or fault recovery services at the bottom layer of the system, or they can be navigation services, network sharing services, Bluetooth headset services, shutdown services, photo services or video playback services provided by the foreground program. The embodiments of the present application do not impose any restrictions on the types of services.

[0061] In an application, a service usually receives input data and provides output data when it is running. Taking a fault recovery service as an example, the input data of the fault recovery service may include the operation status of a preset key service, the operation status of the hardware, and the temperature of the battery cell, etc. The output data may be a shutdown signal or a signal to maintain operation. The data that a service can provide mentioned in the embodiments of the present application refers to the output data of the service.

[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 above services. The data node can be connected to the data output interface corresponding to any of the above services, so that the data node can collect corresponding data when the service outputs data. The data node can adopt a preset coding structure to ensure that different data nodes corresponding to different services use the same coding architecture, so that the system can uniformly manage all data nodes and realize standardized reading of data that can be provided by the service.

[0063] Among them, various parameters of the preset coding architecture can be set according to actual needs. For example, the preset coding architecture may include language type parameters (specifically, it may be c, c++, python or java, etc.), syntax parameters (specifically, it may include service name, node name, node ID, data type or data format, etc.) and interface parameters (used to support node calling), etc. The embodiment of the present application does not impose any restrictions on the specific architecture type of the preset coding architecture.

[0064] In one embodiment, step S301 includes:

[0065] If any service includes a preset generation interface for a data transfer protocol, a corresponding data transfer protocol is generated according to the preset generation interface and preset protocol parameters;

[0066] Generate corresponding data nodes according to the data flow protocol, the preset coding architecture and the data that any service can provide;

[0067] If any service does not include a preset generation interface for a data flow protocol, a corresponding data node is generated according to the preset data flow protocol, the preset coding architecture, and the data that can be provided by any service.

[0068] In the application, the service may include a preset generation interface for the data flow protocol, which may be written by the developer according to the system's development guide or by the developer himself. When generating data nodes, the system may determine whether any of the above services includes a preset generation interface for the data flow protocol. If so, the system may generate the corresponding data flow protocol by inputting the preset protocol parameters into the preset generation interface, and generate the corresponding data node according to the data flow protocol, the preset coding architecture, and the data output interface of any of the above services; if not, the preset data flow protocol may be directly applied, and the corresponding data node may be generated according to the preset data flow protocol, the preset coding architecture, and the data output interface of any of the above services.

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

[0070] Step S302: 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 can be provided by the first service, and the second data node is used to read the second target data that can be provided by the second service, 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 the application, when establishing collaboration between two services, it is possible to first determine whether the data flow protocols of the first data node and the second data node are the same; if so, a data collaboration link between the first data node and the second data node can be directly established (see Figure 4 As shown, Figure 4 The first data node and the second data node are exemplarily shown as a schematic diagram of an architecture in which the first data node and the second data node perform data flow through the same data flow protocol), and the first target data is directly converted into collaborative data through the same data flow protocol; if not, the first data node and the second data node can be input into the service collaboration model, and the data collaboration link can be obtained through the service collaboration model to convert the data format of the first target data through the data collaboration link (refer to Figure 5 As shown, Figure 5An exemplary diagram of an architecture in which a first data node and a second data node perform data flow through different data flow protocols is shown to obtain collaborative data, so that the second data node can support receiving and reading collaborative data, thereby 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 collaborative model is described below:

[0072] In the application, the service collaboration model is used to determine the data flow parameters of the first target data based on the first data flow protocol of the first data node and the second data flow protocol of the second data node, and generate a data collaboration link based on 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] Among them, the data flow path can be specifically used to indicate the interface that needs to be called when the first target data is converted into collaborative data, and the interface that needs to be called when the collaborative data is transmitted to the second service; the data format can indicate the data type (such as integer, floating point or string, etc.) and data structure (such as function type, construction type, pointer type, character set type or base type, etc.).

[0074] For example, assuming that the first service is a ticket purchasing service, the first target data is the arrival time and destination information, where the data type of the arrival time is a floating point type Float, and the data type of the destination information is a string Text; the second service is an accommodation booking service, and the second target data is the hotel name and hotel price, both of which use a string Char data type. After data format conversion, the data types of the arrival time and destination information in the collaborative data are converted to a string Char.

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

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

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

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

[0079] If the matching degree between the first data flow protocol and the second data flow protocol is lower than a preset matching degree, stop generating the data coordination link.

[0080] In the application, if the matching degree between the first data flow protocol and the second data flow protocol is lower than the preset matching degree, the generation of the data collaboration link can be stopped to avoid data format conversion errors after the two protocols are matched, thereby causing collaborative data distortion and affecting the service collaboration effect.

[0081] Step S303: When the first service runs and generates the first target data, the collaborative data is sent to the second service through the data collaborative link, and the second service is called to output the second target data according to the collaborative data.

[0082] In the application, after establishing a data collaborative link between the first data node and the second data node, the second data node can support receiving and reading collaborative data, so that the collaborative data can be sent to the second service through the data collaborative link, and the second service can be called to output the second target data according to the collaborative data, thereby realizing the collaborative call between the first service and the second service.

[0083] In the application, the corresponding data nodes are generated based on the data that can be provided by any service; the data nodes adopt a preset coding architecture; when the first service runs and generates 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 according to the collaborative data. The data nodes are generated by the preset coding structure, which can ensure that different data nodes corresponding to different services adopt the same coding architecture to achieve standardized data reading, and facilitate the service collaboration model to accurately analyze the first data node and the second data node according to the preset coding 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 operation status of the first service, while improving the service collaboration and lowering the operation 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 data that can be provided by any service; the data nodes adopt a preset coding architecture.

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

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

[0088] Step S603: sort the other data nodes in positive order according to the data association degree to obtain the second data node.

[0089] In the application, after the data node is generated and before the data coordination link is established, the data correlation between the first data node and other data nodes can be obtained. The data correlation can be determined by looking up a table to improve the fit between the data correlation and the actual application scenario, and the other data nodes are sorted in positive order according to the data correlation to obtain the second data node. It should be noted that in actual applications, the first data node can establish a data coordination link with multiple data nodes with high data correlation, and establishing a data coordination link between the first data node and the second data node is only exemplary.

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

[0091] In the application, the system can obtain the target user portrait during operation, and determine the data correlation based on big data information, so as to improve the fit between data correlation and actual application scenarios, thereby coordinating highly correlated services based on actual application scenarios, improving the practicality of data coordination links and reducing the occupation of invalid resources.

[0092] Step S604: sort the other data nodes in positive order according to the data association degree 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 a data collaboration link;

[0094] Step S606: When the first service runs and generates the first target data, the collaborative data is sent to the second service through the data collaborative link, and the second service is called to output the second target data according to the collaborative data.

[0095] In the application, the service collaboration method provided by step S404 and step S405 can refer to the relevant description of the above-mentioned step S302 and step S303, which will not be repeated here.

[0096] In the application, by screening out the second data node with a high correlation with the first data node and establishing a data collaboration link, the degree of fit between the data correlation and the actual application scenario can be improved, so that services with strong correlation can be coordinated according to the actual application scenario, thereby improving the practicality of the data collaboration link and reducing the occupation of invalid 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 data that can be provided by any service; the data nodes adopt a preset coding architecture;

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

[0100] Step S703: sort the other data nodes in positive order according to the data association degree 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 a data collaboration link.

[0102] In the application, the service collaboration method provided by steps S701 to S704 may refer to the relevant descriptions in the above steps S501 to S504, which will not be repeated here.

[0103] Step S705: when the first service runs and generates the first target data, output the 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, send the collaborative data to the second service according to the data collaborative link corresponding to the collaborative information, and call the second service 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 called through the data collaboration link to achieve intelligent service recommendation, or the user can confirm whether to call the second service by outputting collaborative information. Collaborative information can be displayed through a pop-up window or through gesture indication (see Figure 8 and Fig. 9 As shown, an exemplary interface diagram of collaborative information displayed through gesture indication is shown. When collaborative information is displayed through gesture indication, if the user operates the corresponding gesture according to the gesture indication, it is determined that the collaborative information is responded to. Among them, the gesture can be a single-finger operation, a two-finger operation, or a three-finger operation such as sliding, clicking, and long pressing. The embodiment of the present application does not impose any restrictions on the gesture type.

[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, thereby realizing the visualization and intuitiveness of service collaborative calls, and effectively improving the utilization rate of service collaborative functions; at the same time, ensuring that users allow the first target data of the first service to be transmitted to the second service, thereby improving the privacy protection capabilities of the data.

[0107] It should be understood that the size of the serial numbers of the steps in the above embodiments 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.

[0108] like Fig.10 As shown, the embodiment of the present application also provides a service collaboration device 2 for executing the steps in the service collaboration method embodiment applied to the terminal device. The service collaboration device can be a virtual appliance in the terminal device, which is run by the processor of the terminal device, or it can be the terminal device itself.

[0109] like Fig.10 As shown, the service collaboration device 2 provided in the embodiment of the present application includes:

[0110] A generating module 210 is used to generate corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture;

[0111] The 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 can be provided by the first service, and the second data node is used to read the second target data that can be provided by the second service, 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 the collaboration data to the second service through the data collaboration link when the first service runs and generates the first target data, and call the second service to output the second target data according to the collaboration data.

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

[0114] A first generating unit, configured to generate a corresponding data transfer protocol according to the preset generating interface and preset protocol parameters if any service includes a preset generating interface of the data transfer protocol;

[0115] Generate corresponding data nodes according to the data flow protocol, the preset coding architecture and the data that any service can provide.

[0116] The second generating unit is used to generate corresponding data nodes according to the preset data transfer protocol, the preset coding architecture and the data that can be provided by any service if any service does not include the preset generating interface of the data transfer protocol.

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

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

[0119] The other data nodes are sorted in positive order according to the data association degree to obtain the second data node.

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

[0121] A collaborative information output unit, 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 the collaborative data to the second service according to the data collaborative link corresponding to the collaborative information if the collaborative information is responded to, and call the second service to output the second target data according to the collaborative data.

[0123] In application, each module in the service collaboration device 2 may be a software program module, or may be implemented by different logic circuits integrated in a processor, or may be implemented by multiple distributed processors.

[0124] Fig.11 The schematic diagram exemplarily shows a timing diagram of the service collaboration device interacting with the server to realize the service collaboration function.

[0125] In the application, the service collaboration model can be trained on the server, and the trained service collaboration model can be deployed to the terminal device. The update information of the service collaboration model can also be transmitted to the terminal device. The software information of the service collaboration device can also be downloaded and updated in the cloud through the server, giving the service collaboration device iterative capabilities.

[0126] It should be noted that the information interaction, execution process and other contents between the above-mentioned modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0127] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned function allocation can be completed by 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 embodiment can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. In addition, the specific names of the functional modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the modules in the above-mentioned system can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here.

[0128] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned various service collaboration method embodiments can be implemented.

[0129] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may at least include: any entity or device that can carry 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 electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a disk or an optical disk.

[0130] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

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

[0132] In the embodiments provided in the present application, it should be understood that the disclosed terminal device and method can be implemented in other ways. For example, the terminal device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules 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 an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0133] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A service collaboration method, characterized in that: include: Generate corresponding data nodes based on data that can be provided by any service; the data nodes adopt a preset coding architecture; Inputting 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 can be provided by the first service, and the second data node is used to read the second target data that can be provided by the second service, 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 runs and generates first target data, the collaborative data is sent to the second service through the data collaborative link, and the second service is called to output second target data according to the collaborative data.

2. The service collaboration method according to claim 1, characterized in that: The generating of corresponding data nodes based on data that can be provided by any service includes: If any of the services includes a preset generation interface for a data transfer protocol, generating a corresponding data transfer protocol according to the preset generation interface and preset protocol parameters; Generate corresponding data nodes according to the data flow protocol, the preset coding architecture and the data that can be provided by any of the services.

3. The service collaboration method according to claim 1, characterized in that: The generating of corresponding data nodes based on data that can be provided by any service includes: If any of the services does not include a preset generation interface for the data flow protocol, a corresponding data node is generated according to the preset data flow protocol, the preset coding architecture and the data that can be provided by any of the services.

4. The service collaboration method according to claim 1, wherein: 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 according to claim 1, characterized in that: The method further comprises: Obtaining data association between the first data node and other data nodes; The other data nodes are sorted in positive order according to the data association degree to obtain a second data node.

6. The service collaboration method according to claim 5, characterized in that: The data relevance is determined based on big data information and target user portraits.

7. The service collaboration method according to any one of claims 1 to 6, characterized in that: When the first service runs and generates the first target data, sending the collaborative data to the second service through the data collaborative link, and calling the second service to output the second target data according to the collaborative data, includes: When the first service runs and generates the first target data, outputting the collaborative information; 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 called 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, the steps of the service collaboration method according to any one of claims 1 to 7 are implemented.

9. A service collaboration device, characterized in that: include: A generation module, used to generate corresponding data nodes based on the data that can be provided by any service; The data node adopts a preset coding architecture; An assembly module, 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 can be provided by the first service, and the second data node is used to read second target data that can be provided by the second service, 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 runs and generates the first target data, and 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, the steps of the service collaboration method according to any one of claims 1 to 7 are implemented.

Images