A method, server and system for contextual services

Abstract

The application provides a method, a server and a system for a scene service, relates to the field of data processing, and comprises the following steps: receiving an initial scene fusion service request sent by a first terminal in response to a first operation of a user; determining a candidate service list corresponding to the initial scene fusion service request according to a first matching relationship between a preset scene service and a service capability, and sending the candidate service list to the first terminal; receiving a target scene fusion service request sent by the first terminal in response to a second operation of the user on the candidate service list; determining a second terminal corresponding to the target scene fusion service request according to a second matching relationship between a service capability and a service terminal, and sending the target scene fusion service request to the second terminal; receiving a scene fusion service result generated by the second terminal according to the target scene fusion service request, and sending the scene fusion service result to the first terminal, so that the first terminal displays the scene fusion service result to the user.

Description

Technical Field

[0001] This application relates to the field of data processing technology and can be used in the financial sector, specifically as a method, server, and system for scenario-based services. Background Technology

[0002] Scenario-based service cooperation refers to a collaboration between a party with a specific scenario and a party providing services, using an interconnected approach to deliver scenario-based services to end customers. This collaboration involves four main tasks: demand identification, information collection, analysis framework, and decision-making recommendations. All four tasks revolve around providing information and support based on the customer's needs.

[0003] Currently, scenario-based services between scenario providers and service providers mainly include: a service provider with limited service channels and customer acquisition channels seeks business lead generation from a scenario provider with more customers and wider service channels; a scenario provider with more customers and wider service channels, but limited service capabilities due to cost and other factors, seeks a provider with complementary service capabilities to offer customers more one-stop service functions; and after a successful match between a service provider and a scenario provider in marketing, the two parties provide customers with integrated scenario-based full-process business services through interconnection.

[0004] However, the many-to-many spiderweb-like interconnection cooperation between scenario providers and service providers results in high interconnection costs, and scenario content and service functions are also limited by marketing and business expansion factors. Summary of the Invention

[0005] To address the problems in the prior art, this application provides a method, server, and system for scenario-based services, which effectively improves the interconnection and cooperation effect.

[0006] To solve the above-mentioned technical problems, this application provides the following technical solution:

[0007] Firstly, this application provides a method for scenario-based services, the method comprising:

[0008] Receive an initial scene fusion service request sent by the first terminal in response to the user's first operation, wherein the initial scene fusion service request includes multiple scene service requests;

[0009] Based on the first matching relationship of the preset scene service and service capabilities, determine the candidate service list corresponding to the initial scene fusion service request, and send the candidate service list to the first terminal;

[0010] Receive the target scene fusion service request sent by the first terminal in response to the user's second operation on the candidate service list;

[0011] Based on the pre-set service capabilities and the second matching relationship between the service terminal, the second terminal corresponding to the target scene fusion service request is determined, and the target scene fusion service request is sent to the determined second terminal;

[0012] The system receives the scene fusion service result generated by the second terminal based on the target scene fusion service request, and sends the scene fusion service result to the first terminal so that the first terminal displays the scene fusion service result to the user.

[0013] In some optional embodiments of this example, the method further includes:

[0014] The system receives a first registration operation from the first terminal, wherein the first registration operation includes: registering the scene directory that the first terminal can provide; registering the service capability directory that the first terminal needs to call; and registering the identity registration information of the first terminal.

[0015] The system receives a second registration operation from the second terminal, wherein the second registration operation includes: registering a directory of service capabilities that the second terminal can provide; registering a directory of scenarios for which the second terminal needs to redirect traffic; and registering the identity registration information of the second terminal.

[0016] In some optional embodiments of this example, receiving the initial scene fusion service request sent by the first terminal in response to the user's first operation includes:

[0017] The legitimacy of the first terminal is determined based on its identity registration information.

[0018] In response to determining that the first terminal is legitimate, the initial scene fusion service request is received.

[0019] Receiving the scene fusion service result generated by the second terminal according to the target scene fusion service request includes:

[0020] The legitimacy of the second terminal is determined based on its identity registration information.

[0021] In response to determining that the second terminal is legitimate, the scene fusion result is received.

[0022] In some optional embodiments of this example, determining the candidate service list corresponding to the initial scene fusion service request based on a pre-set first matching relationship between scene services and service capabilities includes:

[0023] The initial scene fusion service request is parsed to obtain the multiple scene service requests;

[0024] Based on the pre-set first matching relationship between scenario services and service capabilities, determine the service capabilities required for each scenario service request;

[0025] Identify the service terminal corresponding to each service capability;

[0026] A candidate service list is generated based on the service capabilities required for each scenario service request and the service terminal corresponding to each service capability.

[0027] In some optional embodiments of this example, determining the second terminal corresponding to the target scenario fusion service request based on a pre-set second matching relationship between service capabilities and service terminals includes:

[0028] Determine the service capabilities corresponding to the target scenario fusion service request;

[0029] Based on the service capabilities and the second matching relationship, the second terminal corresponding to the target scenario fusion service request is determined.

[0030] In some optional embodiments of this example, the steps of setting the first matching relationship and the second matching relationship include:

[0031] Based on the scenario directory that the first terminal can provide and the service capability directory that needs to be invoked, a first matching relationship is established between the scenario directory and the service capability that needs to be invoked.

[0032] Based on the service capability catalog that the second terminal can provide, a second matching relationship is established between the service capability catalog and the service terminal.

[0033] In some optional embodiments of this example, the method further includes:

[0034] Based on the scenario fusion service results, optimize the first matching relationship and the second matching relationship.

[0035] Secondly, this application provides a server, the server comprising:

[0036] The first receiving module is configured to receive an initial scene fusion service request sent by the first terminal in response to a first operation by the user, wherein the initial scene fusion service request includes multiple scene service requests.

[0037] The candidate service list determination and sending module is configured to determine the candidate service list corresponding to the initial scene fusion service request based on a pre-set first matching relationship of scene services and service capabilities, and send the candidate service list to the first terminal;

[0038] The second receiving module is configured to receive a target scenario fusion service request sent by the first terminal in response to a second operation by the user on the candidate service list.

[0039] The target scene fusion request determination and sending module is configured to determine the second terminal corresponding to the target scene fusion service request based on a pre-set second matching relationship between service capabilities and service terminals, and send the target scene fusion service request to the determined second terminal;

[0040] The scene fusion service result determination and sending module is configured to receive the scene fusion service result generated by the second terminal according to the target scene fusion service request, and send the scene fusion service result to the first terminal so that the first terminal displays the scene fusion service result to the user.

[0041] Thirdly, this application provides a system for scenario-based services, including: a first terminal, a second terminal, and a server as described in the foregoing embodiments.

[0042] Fourthly, this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method for scenario-based services.

[0043] Fifthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for scenario-based services.

[0044] Sixthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the method for scenario-based services.

[0045] To address the problems in existing technologies, this application provides a method, server, and system for scenario-based services, building a scenario-based service chain for organizations providing various services. This breaks through the limitations of individual channels and product service capabilities of organizations. On the one hand, it provides one-stop, full-process, multi-scenario, and multi-product services to scenario end customers, achieving the goal of reducing customer trips, increasing data and network traffic. On the other hand, it achieves one-to-many interconnection cooperation effects with scenario organizations or service organizations through one-to-one interconnection cooperation, greatly reducing the technical and business costs for access organizations. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, 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 the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 This is an exemplary system architecture diagram to which this application can be applied;

[0048] Figure 2 This is a flowchart of one embodiment of the method for scenario-based services according to this application;

[0049] Figure 3 This is an interactive schematic diagram of a method for scenario-based services according to an embodiment of this application;

[0050] Figure 4 This is a schematic diagram of the structure of an open service platform according to an embodiment of this application;

[0051] Figure 5 This is an interactive schematic diagram of a method for scenario-based services according to an embodiment of this application;

[0052] Figure 6 This is a schematic diagram of the structure of one embodiment of the server according to this application;

[0053] Figure 7 This is a schematic diagram of a system for scenario-based services according to an embodiment of this application;

[0054] Figure 8 This is a block diagram of an electronic device used to implement the method for scenario-based services in the embodiments of this application. Detailed Implementation

[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0056] Currently, the cooperation of scenario integration services adopts a two-to-two interconnection method, that is, the terminal of the scenario institution connects with the terminal of each service institution, and the terminal of the service institution connects with the terminal of each scenario institution. Therefore, the scenario party and the service party adopt a many-to-many interconnection cooperation method. The scenario party and the service party not only have high access costs, but also the scenario content and service functions are quite limited.

[0057] Therefore, this application proposes a method for scenario-based services. Figure 1 An exemplary system architecture is shown, representing an embodiment of the method for scenario-based services to which the application can be applied.

[0058] like Figure 1 As shown, the system architecture may include a first terminal 10, a second terminal 20, a server 30, and a network 40. The network 40 serves as a medium for providing communication links between the first terminal 10 and the server 30, and between the second terminal 20 and the server 30. The network 40 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0059] The first terminal 10 and the second terminal 20 can interact with the server 30 via the network 40. The first terminal 10 is equipped with a display screen for user operation and, in response to user operation, sends an initial scene fusion request to the server 30. The server 30 determines a candidate service list corresponding to the initial scene fusion service request based on a pre-set first matching relationship of scene services and service capabilities, and sends the candidate service list to the first terminal 10. In response to the user's selection operation of the candidate service list, the first terminal 10 sends a target scene fusion service request to the server 30. The server 30 determines the second terminal 20 corresponding to the target scene fusion service request based on a pre-set second matching relationship of service capabilities and service terminals, and sends the target scene fusion service request to the determined second terminal 20. The second terminal 20 generates a scene fusion service result based on the target scene fusion service request and sends the scene fusion service result to the first terminal 10 through the server 30. The first terminal 10 displays the scene fusion service result to the user through the display screen.

[0060] It should be noted that server 30 can be either hardware or software. When server 30 is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When server 30 is software, it can be implemented as multiple software programs or software modules (e.g., used to provide distributed services), or as a single software program or software module. No specific limitations are made here.

[0061] It should be understood that Figure 1 The number of the first terminal 10, the second terminal 20, and the server 30 shown is merely illustrative. Depending on implementation needs, there can be any number of first terminals, second terminals, and servers.

[0062] It should be noted that the method for scenario-based services provided in this application embodiment is generally executed by server 30.

[0063] See also Figure 2It illustrates a schematic flowchart of a method for scenario-based services provided in one embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0064] Step 201: Receive the initial scene fusion service request sent by the first terminal in response to the user's first operation, wherein the initial scene fusion service request includes multiple scene service requests;

[0065] Step 202: Based on the pre-set first matching relationship of scene services and service capabilities, determine the candidate service list corresponding to the initial scene fusion service request, and send the candidate service list to the first terminal;

[0066] Step 203: Receive the target scenario fusion service request sent by the first terminal in response to the user's second operation on the candidate service list;

[0067] Step 204: Based on the pre-set service capabilities and the second matching relationship between the service terminal, determine the second terminal corresponding to the target scenario fusion service request, and send the target scenario fusion service request to the determined second terminal;

[0068] Step 205: Receive the scene fusion service result generated by the second terminal based on the target scene fusion service request, and send the scene fusion service result to the first terminal so that the first terminal can display the scene fusion service result to the user.

[0069] This application provides a method for scenario-based services, which builds a scenario-based service chain for organizations providing various services, breaking through the limitations of individual channels and product service capabilities of organizations. On the one hand, it provides one-stop, full-process, multi-scenario, and multi-product services to end customers in the scenario, achieving the goal of reducing the need for customers to make trips, allowing data to travel more, and allowing the network to travel more. On the other hand, it achieves a one-to-many interconnection effect with scenario organizations or service organizations through a one-to-one interconnection cooperation method, greatly reducing the technical and business costs of access organizations.

[0070] In this embodiment, the method for scenario-based services of this application is described using the example of a scenario organization terminal 10' as the first terminal, a service organization terminal 20' as the second terminal, and an open service platform 30' as the server. The open service platform, also known as an API open platform, is responsible for publishing API services externally via the Internet and facilitating access to collaborative scenario services.

[0071] It should be understood that API services are open interfaces registered on an open platform and released externally (to partners, etc.). An API service is an interface designed for a specific business scenario, formed by packaging and combining internal transaction logic, capable of independently completing operations within that scenario, and exposed externally. Bank open API services refer to APIs that banks widely provide to partners, offering standard interfaces for use by external partners and developers.

[0072] refer to Figure 4 In this embodiment, the open service platform 30' includes a scenario-based service chain registration device 301, a scenario and service matching device 302, and a scenario-based service link entry device 303. The scenario-based service link entry device is connected to the scenario organization terminal and the service organization terminal via the Internet; the scenario-based service chain registration device, the scenario-based service link entry device, and the scenario and service matching device of the open service platform are interconnected via the open service platform's intranet.

[0073] The following is combined with Figure 3 Interactive diagram, for Figure 2 Each step is explained in detail:

[0074] Step 201: Receive the initial scene fusion service request sent by the first terminal in response to the user's first operation, wherein the initial scene fusion service request includes multiple scene service requests.

[0075] In this embodiment, the first terminal is a scenario organization, that is, a department or organization with a scenario, such as public utility organizations such as water, electricity, coal and gas, and third-party organizations such as e-commerce and social platforms. These organizations have a wealth of scenarios that customers need in their daily lives. The self-service terminals of these organizations, desktop computers that can be used by business operators of external units or customers, and various mobile device applications (APPs) are scenario organization terminals.

[0076] See Figure 3 In response to the user's first action, the scenario-based service terminal sends an initial scenario fusion request to the open service platform. This request may be for fusion of transaction requests from multiple scenarios. In other words, the initial scenario fusion service request includes multiple scenario service requests. The user's first action is an action performed by the user on the display screen interface provided by the scenario-based service terminal, such as clicking or selecting, to submit the user's scenario service request to the scenario-based service terminal.

[0077] It should be noted that when the scenario-based agency terminal starts up and initializes each day, it downloads the relevant parameter tables of service agency terminals and scenario fusion services that have a cooperative relationship with the agency through the access scenario-based service link. The internal processing of the scenario-based agency terminal will not be described in detail.

[0078] Step 202: Based on the pre-set first matching relationship of scene services and service capabilities, determine the candidate service list corresponding to the initial scene fusion service request, and send the candidate service list to the first terminal.

[0079] In this embodiment, reference Figure 3 After receiving the initial scene fusion request, the open service platform determines the candidate service list corresponding to the initial scene fusion service request based on the pre-set first matching relationship of scene services and service capabilities, and sends the candidate service list to the scene organization terminal.

[0080] It should be noted that this embodiment, based on the scenario-based service chain registration device and the scenario and service matching device, can pre-set the first matching relationship between scenario services and service capabilities. Specifically:

[0081] The scenario-based service chain registration device is responsible for providing registration services to various scenario organizations and service organizations for joining the scenario-based service chain. This registration includes registering the scenario service directories that scenario organization terminals can provide and the service capability directories they need to invoke, as well as registering the service capability directories that service organization terminals can provide and the scenario service directories that need traffic redirection. The scenario-based service chain registration device connects to the scenario-based service chain access device. Upon receiving scenario service request information or service organization response information, it verifies the legality of the business access and permissions of the scenario organization terminals and service organization terminals based on the pre-registered registration information. The scenario-based service chain registration device also connects to the scenario and service matching device. Upon receiving scenario fusion service request information, it provides a first matching relationship between scenarios and service capabilities, and a second matching relationship between service organizations and service capabilities, based on the pre-registered scenario service directories that scenario organization terminals can provide and the service capability directories that they need to invoke, and the service capability directories that service organization terminals can provide and the scenario service directories that need traffic redirection.

[0082] In other words, in this embodiment, the steps of setting the first matching relationship and the second matching relationship include:

[0083] Based on the scenario catalog that the first terminal can provide and the service capability catalog that needs to be called, establish the first matching relationship between the scenario catalog and the service capability that needs to be called.

[0084] Based on the service capability catalog that the second terminal can provide, a second matching relationship is established between the service capability catalog and the service terminal.

[0085] The scenario and service matching device is responsible for connecting to the scenario-based service linking device, receiving initial scenario fusion service request information, parsing the initial scenario fusion service request to obtain multiple scenario service requests, querying the first matching relationship between scenarios and service capabilities by connecting to the scenario-based service chain registration device, determining the service capabilities required for each scenario service request, and determining the service terminal corresponding to each service capability, further generating a candidate service list based on the service capabilities required for each scenario service request and the service terminal corresponding to each service capability, and sending the candidate service list to the scenario-based institution terminal through the scenario-based service linking device.

[0086] Step 203: Receive the target scenario fusion service request sent by the first terminal in response to the user's second operation on the candidate service list.

[0087] In this embodiment, the customer at the scenario-based terminal selects from the list of candidate services displayed on the screen to submit a request for the target scenario fusion service (the actual scenario fusion service request). See [link to relevant documentation]. Figure 3 The scene agency terminal sends the target scene fusion service request to the open service platform.

[0088] Step 204: Based on the pre-set service capabilities and the second matching relationship between the service terminal, determine the second terminal corresponding to the target scene fusion service request, and send the target scene fusion service request to the determined second terminal.

[0089] In this embodiment, reference Figure 3 After receiving a request for a fusion service for a target scenario, the open service platform first determines the service capabilities corresponding to the request. Then, based on the second matching relationship between the pre-registered service providers and service capabilities, it determines the second terminal corresponding to the request and forwards it to the service provider terminal that provides the corresponding service capabilities.

[0090] It should be noted that service providers can be commercial banks, insurance companies, and other institutions that offer services such as payment settlement, loans, and commercial insurance. These institutions require assistance from organizations with rich experience in various scenarios to conduct customer marketing and lead generation. The service provider's terminals include self-service terminals, desktop computers for external business operators or customers to register and sign contracts, various mobile applications (APPs), and application servers and database servers that provide backend business processing functions. During daily startup initialization, the service provider terminal downloads parameter tables related to scenario-based service terminals and scenario integration services through the connected scenario-based service link device. The internal processing details of the service provider terminal are not provided in detail here.

[0091] Step 205: Receive the scene fusion service result generated by the second terminal based on the target scene fusion service request, and send the scene fusion service result to the first terminal so that the first terminal can display the scene fusion service result to the user.

[0092] In this embodiment, see Figure 3 The service provider terminal accepts the target scenario fusion service request forwarded by the open service platform from the customer. After verifying the customer's identity based on the customer's pre-registration information on the service provider terminal, it processes the target scenario fusion service and returns the scenario fusion processing result to the open service platform. Furthermore, the open service platform sends the scenario fusion service result to the scenario provider terminal so that the scenario provider terminal can display the scenario fusion service result to the user.

[0093] It should be noted that the method for scenario-based services provided in this application establishes a scenario-based service chain for scenario organization terminals that provide scenario requests and service organization terminals that provide various services. The scenario-based service chain is based on building ubiquitous, innovative, and versatile "smart services," creating an integrated online and offline business development model for customer acquisition, activation, and retention. It also builds an open, cooperative, and win-win service ecosystem that seamlessly connects scenario organizations and service organizations, thereby forming a scenario-based service chain with an API open platform as the central hub, supporting one-to-one access for scenario organizations and service organizations. That is, each scenario organization terminal and each service organization terminal only needs to connect to the API open service platform.

[0094] See Figure 3 The scenario-based service method based on the scenario-based service chain in this embodiment will be further described, and its main process is as follows:

[0095] Step S1: Build an open service platform to provide maintenance and management functions to service agency terminals and scenario agency terminals that join the platform.

[0096] The open service platform includes a scenario-based service chain registration device, a scenario and service matching device, and a scenario-based service link access device.

[0097] Step S2: Each scenario organization terminal and service organization terminal registers the scenario-based service chain on the open service platform, performs scenario-based service chain registration, security authentication, etc. For example, scenario organizations register the scenario service catalog they can provide and the service capability catalog they need to call, while service organization terminals register the service capability catalog they can provide and the scenario service catalog they need to drive traffic to.

[0098] In this embodiment, the scenario-based service chain registration device includes a scenario organization registration unit, a scenario organization and required service registration unit, a service organization registration unit, a service organization and required scenario registration unit, a scenario and service relationship storage unit, a scenario and service matching relationship query unit, a scenario and service matching result feedback unit, a service organization processing result receiving unit, and a scenario and service relationship optimization unit. Wherein:

[0099] The scenario-based organization registration unit provides registration functionality to public utilities such as water, electricity, gas, and e-commerce platforms, as well as social media platforms, that have specific scenarios. Based on offline identity verification and signing of written franchise agreements with scenario-based service providers, the unit issues certificates and keys for internet access security authentication to these providers, and stores their registration information. This registration information is subsequently used as an electronic franchise agreement for verifying the legitimacy of scenario service access and permissions.

[0100] After the scenario agency terminal completes registration using the scenario agency registration unit, the scenario agency and the required service registration unit are responsible for further registering the scenario service information provided by the scenario agency, as well as the service agency terminal and its provided scenario integration service information required for each scenario service. Considering that customers may open accounts and register with multiple service agencies, each scenario service can register multiple required service agencies and their provided scenario integration service information. Subsequently, the scenario and service relationship directory is downloaded as a parameter to the scenario service system for customers to select.

[0101] In other words, the method for scenario-based services in this embodiment further includes: receiving a first registration operation from a first terminal, wherein the first registration operation includes: registering a scenario directory that the first terminal can provide; registering a service capability directory that the first terminal needs to call; and registering the identity registration information of the first terminal.

[0102] The service provider registration unit provides registration support to commercial banks, insurance companies, and other institutions with payment settlement, loan, and commercial insurance service capabilities. Based on offline identity verification and signing of a written franchise agreement with service providers within the scenario-based service chain, the unit issues certificates and keys for internet access security authentication to service providers and stores their registration information. This registration information serves as an electronic agreement used for scenario-based service link access devices to submit scenario-integrated services, implementing service access and authorization legality verification.

[0103] After the service provider terminal completes registration using the service provider registration unit, the service provider terminal and the required scenario registration unit are responsible for further registering the service information provided by the institution, as well as the traffic-generating scenario institutions and their synergistic scenario service information required for each service. Considering that customers may conduct business with multiple scenario service providers, each service can register multiple required traffic-generating scenario institutions and their synergistic scenario service information. Subsequently, the scenario and service relationship directory is downloaded as a parameter to the scenario service system for customers to select.

[0104] In other words, the method for scenario-based services in this embodiment further includes: receiving a second registration operation from a second terminal, wherein the second registration operation includes: registering a directory of service capabilities that the second terminal can provide; registering a directory of scenarios that the second terminal needs to redirect traffic to; and registering the identity registration information of the second terminal.

[0105] The scenario and service relationship storage unit is responsible for storing the scenario and service relationships registered by scenario organizations and required service registration units, as well as service organizations and required scenario registration units. On the other hand, it provides scenario and service relationship query support to the scenario and service matching relationship query unit.

[0106] The scenario and service matching relationship query unit is responsible for initiating a scenario and service relationship query to the scenario and service relationship storage unit based on the initial scenario fusion service request information submitted by the scenario organization terminal forwarded by the scenario and service matching device.

[0107] The scenario and service matching result feedback unit is responsible for feeding back the scenario and service relationship query results to the scenario and service matching device based on the queried scenario and service relationship.

[0108] The service provider processing result receiving unit is responsible for receiving and forwarding the scenario service processing results from the scenario-based service linking device.

[0109] The scenario and service relationship optimization unit collects the content information of the scenario fusion service processing result from the service organization processing result receiving unit, including fields such as scenario organization code, scenario service type, scenario fusion service organization code, scenario fusion service type, and scenario fusion service background. It identifies the service organization and service selected by the customer and optimizes the scenario and service relationship storage unit.

[0110] Step S3: The customer registers and signs a contract at the terminal of the scene institution and the terminal of the service institution.

[0111] In this embodiment, the scenario-based service linking device includes a scenario organization and service organization identity authentication unit and a scenario organization and service organization permission checking unit, wherein:

[0112] The scenario organization and service organization identity authentication unit is responsible for authenticating the connected scenario organization terminals and service organization terminals, including signature verification and security key authentication. By connecting to the scenario-based service chain registration device, it checks whether the registration status of the scenario organization terminals and service organization terminals is valid.

[0113] The scenario organization and service organization permission checking unit is responsible for checking the consistency between the permissions of the services handled by the connected scenario organization terminals and service organization terminals and the pre-registered permissions. By connecting to the scenario-based service chain registration device, it checks whether the services provided by the scenario fusion service parameter download unit and the scenario fusion service information receiving unit are consistent with the scenario organization and the required service, and whether the service organization and the required scenario are pre-registered by the scenario organization terminal and the service organization terminal.

[0114] Step S4: Open service platform, providing matching, maintenance and management functions for scenario-based institutions and service providers.

[0115] In this embodiment, the scenario-based service linking device further includes a scenario-based service parameter downloading unit, a scenario-based service information receiving unit, a service organization querying unit, a service organization receiving unit, a service organization receiving unit, a scenario-based service information forwarding unit, and a service organization receiving and forwarding unit processing results, wherein:

[0116] The scenario-integrated service parameter download unit for scenario-institutions and service-institutions downloads and feeds back the corresponding cooperation relationships between scenario-institutions and service-institutions, the scenarios and required services of scenario-institutions, and the parameters of service-institutions and required traffic-driving scenarios to scenario-institution terminals and service-institution terminals, based on the parameter download requests submitted by scenario-institution terminals and service-institution terminals during daily initialization, by connecting to the scenario-based service chain registration device.

[0117] The scene fusion service information receiving unit is responsible for receiving scene fusion service information from the scene organization terminal and forwarding the scene fusion service information to the scene and service matching device.

[0118] The system queries service providers and service units. Based on the scenario fusion service information receiving unit, the system forwards the scenario fusion service information to the scenario and service matching device to query the service providers and services that are compatible with this scenario service.

[0119] The receiving service organization and service feedback unit is responsible for forwarding the scenario fusion service information to the scenario and service matching device, and receiving the service organization and service for this scenario service adaptation.

[0120] The scenario fusion service information forwarding service unit forwards the scenario fusion service information to the corresponding service unit terminal for service processing based on the service unit and service information provided by the receiving service unit and the service feedback unit.

[0121] The receiving and forwarding service provider processing result unit is responsible for receiving the service processing result feedback from the service provider terminal and feeding back the service processing result to the original scenario provider terminal that submitted the scenario service request and the scenario-based service chain registration device.

[0122] Step S5: The customer initiates a transaction through the terminal service channel of the scenario institution.

[0123] Step S6: The scenario agency terminal accepts the customer's transaction request. If the customer's transaction request involves other related service requirements, the scenario agency terminal forwards the initial scenario fusion service request to the open service platform.

[0124] Step S7: The open service platform accepts the initial scene fusion service request submitted by the scene organization terminal. Through the pre-registered scene service and service capability matching relationship, it automatically matches the appropriate service organization terminal and service function, and then returns it to the scene organization terminal.

[0125] It should be further explained here that the scenario and service matching device is responsible for connecting to the scenario-based service chain registration device and the scenario-based service link entry device. Through connecting to the scenario-based service link entry device, it receives target scenario fusion service information; through connecting to the scenario-based service chain registration device, it queries the scenario and service matching relationship; and determines that the scenario-based service link entry device will forward the scenario fusion service information to the corresponding service provider terminal. The scenario and service matching device further includes: a scenario fusion service information receiving unit, a scenario fusion service information content parsing unit, a scenario and service matching relationship query unit, a scenario and service matching result receiving unit, and a scenario and service matching result forwarding unit, wherein:

[0126] The scene fusion service information receiving unit is responsible for receiving the target scene fusion service information forwarded by the scene-based service linking device.

[0127] The scenario organization service information content parsing unit parses the information provided by the scenario fusion service information receiving unit, and parses out fields including scenario organization code, scenario service type, scenario fusion service organization code, scenario fusion service type, scenario fusion service background, scenario fusion service purpose, scenario fusion service summary, customer name, customer identity code, and customer mobile phone number.

[0128] The scenario and service matching relationship query unit, based on the scenario organization service information content parsing unit's information such as scenario organization code, scenario service type, service organization code, and scenario integration service type, is responsible for querying elements such as the service organization address and scenario integration service content that match the scenario service by connecting to the scenario-based service chain registration device.

[0129] The scenario and service matching result receiving unit is responsible for receiving information such as the address of the service provider and the content of the scenario-integrated service from the scenario-based service chain registration device.

[0130] The scenario-organization matching result forwarding unit is responsible for forwarding the customer scenario-integrated service information provided by the scenario-service matching result receiving unit to the corresponding service organization terminal for processing, based on the service organization address, scenario-integrated service content, and other information provided by the scenario-service matching result receiving unit.

[0131] Step S8: The scenario agency presents the candidate service list of suitable alternative scenario fusion service agencies and service functions returned by the open service platform to the customer for selection and use. The scenario agency then forwards the customer's selected target scenario fusion service agency and service function request to the open service platform.

[0132] Step S9: The open service platform forwards the actual (target) scenario fusion service request submitted by the scenario organization to the service organization terminal that provides the service capability through the pre-registered service organization and service capability relationship.

[0133] Step S10: The service provider terminal accepts the service request selected by the customer forwarded by the open service platform, performs identity verification based on the customer's prior registration information with the service provider, processes the scenario-integrated service business, and returns the processing result to the open service platform.

[0134] Step S11: The open service platform forwards the actual scenario fusion service processing result returned by the service provider terminal to the scenario provider terminal that submitted the service request.

[0135] Step S12: The scenario agency terminal will display the scenario fusion service processing results forwarded by the open service platform, combined with the scenario service processing status, to the customer.

[0136] To further illustrate the method for scenario-based services in this embodiment, this application combines the unit structures mentioned in the foregoing embodiments with... Figure 5 To further explain this application, the specific process is as follows:

[0137] Step S101: The scenario agency terminal accepts the customer's scenario service request. The scenario agency terminal includes self-service terminals of public institutions, desktop computers that can be used by business operators or customers of external units, various mobile device applications (APP), and application servers and database servers that can provide scenario business function processing.

[0138] Step S102: Scene organization and service organization permission check unit, checks the consistency between the permissions of the access scene organization handling the business and the pre-registered permissions, and checks whether the scene service accepted by the scene organization terminal in step S101 meets the requirements of the pre-registered scene organization and the required scene integration service.

[0139] In other words, the legitimacy of the first terminal is determined based on its identity registration information; in response to the determination that the first terminal is legitimate, an initial scenario fusion service request is received.

[0140] Step S103: The scene organization submits scene fusion service information. The scene fusion service information receiving unit 34 receives scene fusion service information from the scene organization service device 1. The scene fusion service information content parsing unit 42 analyzes the scene service content and obtains field information such as scene type APPID, service category, service processing time, service background, service purpose, service summary, customer name, customer mobile phone number, and scene location.

[0141] Step S104: Based on the scenario-based integrated service information parsed in step S103, the service organization and the corresponding service content information of the scenario are queried through the scenario and service matching relationship query unit, according to the scenario-based integrated service information submitted by the scenario organization forwarded by the scenario and service matching device.

[0142] Step S105: Based on the service organization and service information provided by the service organization and service feedback unit in step S104, the target scenario fusion service information is submitted to the corresponding service organization terminal for service processing through the scenario fusion service information forwarding service organization unit.

[0143] Step S106: After processing the target scenario fusion service information submitted in step S105, the service provider terminal sends the processing result back to the scenario-based service linking device.

[0144] Step S107: The scenario organization and service organization permission checking unit checks the service processing results fed back by the service organization terminal in step S106 to verify the consistency between the permissions of the service handled by the service organization terminal and the prior registration.

[0145] In other words, the legitimacy of the second terminal is determined based on its identity registration information; in response to the determination that the second terminal is legitimate, the scene fusion result is received.

[0146] S108: Receive and forward service organization processing results unit, receive the service processing results from the service organization terminal, and feed back the service processing results to the original scenario organization terminal that submitted the scenario service request.

[0147] Step S109: Based on the service provider processing results provided in step S108, the scenario provider terminal displays the scenario service processing status to the customer.

[0148] Step S110: Scene and service relationship optimization unit. Based on the service organization processing results provided in step S108, the scene and service relationship storage unit in the scene-based service chain registration device is optimized. The optimized parameters will be available for download by the scene organization terminal and the service organization terminal during the initialization on the next day.

[0149] In other words, the first and second matching relationships are optimized based on the results of the scenario fusion service.

[0150] Further, refer to Figure 5 The diagram illustrates the relationship between scenarios and service optimization. The specific optimization steps are as follows:

[0151] After the scenario and service relationship is put into use, iterative optimization is carried out using the feedback data of the scenario fusion service processing results. The scenario-based service chain registration device collects feedback information on the service institutions and service content finally selected by the customer for the scenario fusion service, such as whether the scenario fusion service was selected, which service institution was selected, and which service of the service institution was selected. Each time, the ranking of the scenario and service relationship is scored and evaluated based on the scenario fusion service processing. At the end of each day, the service institutions and service catalogs in the scenario and service relationship are re-sorted based on the scoring and evaluation of the day. This allows the scenario institution terminal and the service institution terminal to obtain the optimized scenario and service relationship parameters when they initialize the next day and redeploy them to the servers of the scenario institution terminal and the service institution terminal.

[0152] The feedback data of the scenario-based integrated service processing results includes scenario organization codes, scenario service codes, scenario service status, etc. Through data accumulation, processing, statistics and analysis, it is continuously iterated and optimized. Combined with the registration of new scenario organization terminals, new service organization terminals and their scenarios and services, the relationship between scenarios and services (first matching relationship and second matching relationship) is continuously optimized. It is upgraded and optimized as customers continue to use it, and the priority of the scenario and service relationship recommended to customers is continuously adjusted. The adjusted scenario and service relationship is then stored and updated in the scenario and service relationship storage unit.

[0153] In summary, the scenario-based service method based on a scenario-based service chain provided in this embodiment builds a scenario-based service chain centered on an open service platform for various scenario-based institutional terminals and service institution terminals. This overcomes the limitations of individual institutional channels and service capabilities, providing end customers with one-stop, end-to-end, multi-scenario, and multi-product services. It achieves the goal of reducing customer trips, increasing data and network traffic, and has the following main effects and advantages:

[0154] 1. Expand customer service channels: Break through the limitations of scenario-based or service-based institutions using their own channels to provide services, make full use of various scenario-based service channels that customers like, and provide services in a scenario-based and customer service-based manner.

[0155] 2. Enhance customer experience: By building an open, cooperative, and win-win service ecosystem that seamlessly connects scenario-based institutions and service providers, we provide customers with ubiquitous, innovative, and versatile "smart services," offering them an integrated online and offline, one-stop scenario-integrated service experience.

[0156] 3. Reduced connection costs: With the API open platform as the central hub, it supports one-to-one access to scenario-based service chains for scenario-based agency terminals and service-based agency terminals. Each scenario-based agency terminal and service-based agency terminal only needs to connect to the API open platform once (i.e., register on the API open platform once). There is no need for many-to-many interconnection between each scenario-based agency terminal and service-based agency terminal. Based on the matching relationship between scenario and service capabilities and the matching relationship between service capabilities and service institutions determined during registration, it can complete a one-stop scenario-based service based on the scenario fusion service request submitted by the user.

[0157] 4. Significant Economic Benefits: The scenario-based service chain built in this embodiment provides customers with a popular, one-stop, full-process, multi-product scenario-integrated service through scenario institution terminals and service institution terminals, flexibly reflecting the organic integration of customers, scenarios, and services. By providing integrated services to scenario institution terminals and driving customer traffic to service institution terminals, appropriate access and intermediary fees can be charged to both. With the continuous expansion and enrichment of scenarios and the ever-growing service catalog, this not only benefits scenario institutions and service institutions but also brings considerable economic benefits to the builder of the scenario-based service chain (i.e., the open service platform provider).

[0158] It should be noted that the acquisition, storage, use and processing of data in the technical solution of this application all comply with the relevant provisions of laws and regulations.

[0159] Further reference Figure 6As an implementation of the methods for scenario-based services described in the above figures, this disclosure provides an embodiment of a server that is connected to... Figure 2 The method embodiments shown correspond to those described.

[0160] like Figure 6 As shown, the server includes:

[0161] The first receiving module 601 is configured to receive an initial scene fusion service request sent by the first terminal in response to a first operation by the user, wherein the initial scene fusion service request includes multiple scene service requests.

[0162] The candidate service list determination and sending module 602 is configured to determine the candidate service list corresponding to the initial scene fusion service request based on the first matching relationship of the preset scene service and service capability, and send the candidate service list to the first terminal;

[0163] The second receiving module 603 is configured to receive a target scenario fusion service request sent by the first terminal in response to the user’s second operation on the candidate service list;

[0164] The target scene fusion request determination and sending module 604 is configured to determine the second terminal corresponding to the target scene fusion service request based on the preset service capabilities and the second matching relationship between the service terminal, and send the target scene fusion service request to the determined second terminal.

[0165] The scene fusion service result determination and sending module 605 is configured to receive the scene fusion service result generated by the second terminal according to the target scene fusion service request, and send the scene fusion service result to the first terminal so that the first terminal can display the scene fusion service result to the user.

[0166] In some optional embodiments of this example, the server further includes:

[0167] The first registration module is configured to receive the first registration operation from the first terminal, wherein the first registration operation includes: registering the scene directory that the first terminal can provide; registering the service capability directory that the first terminal needs to call; and registering the identity registration information of the first terminal.

[0168] The first registration module is configured to receive the second registration operation from the second terminal. The second registration operation includes: registering the service capability catalog that the second terminal can provide; registering the scenario catalog that the second terminal needs to redirect traffic to; and registering the identity registration information of the second terminal.

[0169] In some optional embodiments of this example, the first receiving module is further configured to: determine the legitimacy of the first terminal based on the identity registration information of the first terminal; and receive an initial scene fusion service request in response to determining that the first terminal is legitimate.

[0170] The second receiving module is further configured to: determine the legitimacy of the second terminal based on the identity registration information of the second terminal; and receive the scene fusion result in response to determining that the second terminal is legitimate.

[0171] In some optional embodiments of this example, the candidate service list determination and sending module is further configured as follows:

[0172] The initial scenario fusion service request is parsed to obtain multiple scenario service requests;

[0173] Based on the pre-set first matching relationship between scenario services and service capabilities, determine the service capabilities required for each scenario service request;

[0174] Identify the service terminal corresponding to each service capability;

[0175] A candidate service list is generated based on the service capabilities required for each scenario service request and the service terminal corresponding to each service capability.

[0176] In some optional embodiments of this example, the target scene fusion service request is further configured as follows:

[0177] Determine the service capabilities corresponding to the target scenario's integrated service request;

[0178] Based on service capabilities and the second matching relationship, determine the second terminal corresponding to the target scenario fusion service request.

[0179] In some optional embodiments of this example, the steps of setting the first matching relationship and the second matching relationship include:

[0180] Based on the scenario catalog that the first terminal can provide and the service capability catalog that needs to be called, establish the first matching relationship between the scenario catalog and the service capability that needs to be called.

[0181] Based on the service capability catalog that the second terminal can provide, a second matching relationship is established between the service capability catalog and the service terminal.

[0182] In some optional embodiments of this example, the server further includes:

[0183] The optimization module is configured to optimize the first and second matching relationships based on the results of scenario fusion services.

[0184] According to embodiments of this disclosure, such as Figure 7As shown, this application also provides a system for scenario-based services, which includes: a first terminal 10, a server 30, and a second terminal 20, wherein:

[0185] The first terminal 10 and the second terminal 20 can interact with the server 30 via a network. The first terminal 10 is equipped with a display screen for user operation and, in response to user operation, sends an initial scene fusion request to the server 30. The initial scene fusion service request includes multiple scene service requests. The server 30 determines a candidate service list corresponding to the initial scene fusion service request based on a pre-set first matching relationship between scene services and service capabilities, and sends the candidate service list to the first terminal 10. In response to the user's selection operation on the candidate service list, the first terminal 10 sends a target scene fusion service request to the server 30. The server 30 determines the second terminal 20 corresponding to the target scene fusion service request based on a pre-set second matching relationship between service capabilities and service terminals, and sends the target scene fusion service request to the determined second terminal 20. The second terminal 20 generates a scene fusion service result based on the target scene fusion service request and sends the scene fusion service result to the first terminal 10 through the server 30. The first terminal 10 displays the scene fusion service result to the user through the display screen.

[0186] Since the system for scenario-based services provided in this embodiment corresponds to the method for scenario-based services provided in the above embodiments, the previous implementation methods and beneficial effects are also applicable to the method for scenario-based services provided in this embodiment, and will not be described in detail in this embodiment.

[0187] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0188] An electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method for scenario-based services described in the foregoing embodiments.

[0189] A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to perform the method for scenario-based services described in the foregoing embodiments.

[0190] A computer program product includes a computer program that, when executed by a processor, implements the method for scenario-based services described in the foregoing embodiments.

[0191] Figure 8A schematic block diagram of an example electronic device 700 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0192] like Figure 8 As shown, device 700 includes a computing unit 701, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 702 or a computer program loaded from storage unit 708 into random access memory (RAM) 703. RAM 703 may also store various programs and data required for the operation of device 700. The computing unit 701, ROM 702, and RAM 703 are interconnected via bus 704. Input / output (I / O) interface 705 is also connected to bus 704.

[0193] Multiple components in device 700 are connected to I / O interface 705, including: input unit 706, such as keyboard, mouse, etc.; output unit 707, such as various types of monitors, speakers, etc.; storage unit 708, such as disk, optical disk, etc.; and communication unit 709, such as network card, modem, wireless transceiver, etc. Communication unit 709 allows device 700 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0194] The computing unit 701 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the various methods and processes described above, such as methods for scenario-based services.

[0195] For example, in some embodiments, the method for contextual services may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and / or installed on device 700 via ROM 702 and / or communication unit 709. When the computer program is loaded into RAM 703 and executed by computing unit 701, one or more steps of the method for contextual services described above may be performed. Alternatively, in other embodiments, computing unit 701 may be configured to perform the method for contextual services by any other suitable means (e.g., by means of firmware).

[0196] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0197] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0198] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0199] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0200] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0201] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0202] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this disclosure can be achieved, and this is not limited herein.

[0203] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for scenario-based services, characterized in that, include: The system receives an initial scenario fusion service request sent by a first terminal in response to a user's first operation. The initial scenario fusion service request is a transaction request that integrates multiple scenarios and includes multiple scenario service requests. Based on a pre-set first matching relationship between scenario services and service capabilities, the system determines a candidate service list corresponding to the initial scenario fusion service request and sends the candidate service list to the first terminal. Receive the target scene fusion service request sent by the first terminal in response to the user's second operation on the candidate service list; Based on the pre-set service capabilities and the second matching relationship between the service terminal, the second terminal corresponding to the target scene fusion service request is determined, and the target scene fusion service request is sent to the determined second terminal; The system receives the scene fusion service result generated by the second terminal based on the target scene fusion service request, and sends the scene fusion service result to the first terminal so that the first terminal displays the scene fusion service result to the user. The step of determining the candidate service list corresponding to the initial scene fusion service request based on the pre-set first matching relationship of scene services and service capabilities includes: The initial scene fusion service request is parsed to obtain multiple scene service requests; Based on the pre-set first matching relationship between scenario services and service capabilities, determine the service capabilities required for each scenario service request; Identify the service terminal corresponding to each service capability; A candidate service list is generated based on the service capabilities required for each scenario service request and the service terminal corresponding to each service capability. The first terminal is a scene organization terminal, and the second terminal is a service organization terminal; The method further includes: The system receives a first registration operation from the first terminal, wherein the first registration operation includes: registering the scene directory that the first terminal can provide; registering the service capability directory that the first terminal needs to call; and registering the identity registration information of the first terminal. The system receives a second registration operation from the second terminal, wherein the second registration operation includes: registering a directory of service capabilities that the second terminal can provide; registering a directory of scenarios for which the second terminal needs to redirect traffic; and registering the identity registration information of the second terminal.

2. The method according to claim 1, characterized in that, The receiving of the initial scene fusion service request sent by the first terminal in response to the user's first operation includes: The legitimacy of the first terminal is determined based on its identity registration information. In response to determining that the first terminal is legitimate, the initial scene fusion service request is received; Receiving the scene fusion service result generated by the second terminal according to the target scene fusion service request includes: The legitimacy of the second terminal is determined based on its identity registration information. In response to determining that the second terminal is legitimate, the scene fusion result is received.

3. The method according to claim 1, characterized in that, The step of determining the second terminal corresponding to the target scenario fusion service request based on a pre-set second matching relationship between service capabilities and service terminals includes: Determine the service capabilities corresponding to the target scenario fusion service request; Based on the service capabilities and the second matching relationship, the second terminal corresponding to the target scenario fusion service request is determined.

4. The method according to claim 1, characterized in that, The steps for setting the first matching relationship and the second matching relationship include: Based on the scenario directory that the first terminal can provide and the service capability directory that needs to be invoked, a first matching relationship is established between the scenario directory and the service capability that needs to be invoked. Based on the service capability catalog that the second terminal can provide, a second matching relationship is established between the service capability catalog and the service terminal.

5. The method according to claim 1, characterized in that, Also includes: Based on the results of the scenario fusion service, optimize the first matching relationship and the second matching relationship.

6. A server for performing the steps of the method for scenario-based services according to any one of claims 1 to 5, characterized in that, include: The first receiving module is configured to receive an initial scenario fusion service request sent by the first terminal in response to the user's first operation, wherein the initial scenario fusion service request is a transaction request that integrates multiple scenarios and includes multiple scenario service requests. The candidate service list determination and sending module is configured to determine the candidate service list corresponding to the initial scene fusion service request based on a pre-set first matching relationship of scene services and service capabilities, and send the candidate service list to the first terminal; The second receiving module is configured to receive a target scenario fusion service request sent by the first terminal in response to a second operation by the user on the candidate service list. The target scene fusion request determination and sending module is configured to determine the second terminal corresponding to the target scene fusion service request based on a pre-set second matching relationship between service capabilities and service terminals, and send the target scene fusion service request to the determined second terminal; The scene fusion service result determination and sending module is configured to receive the scene fusion service result generated by the second terminal according to the target scene fusion service request, and send the scene fusion service result to the first terminal so that the first terminal displays the scene fusion service result to the user.

7. A system for scenario-based services, characterized in that, include: The first terminal, the second terminal, and the server as described in claim 6.

8. An electronic 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 program, it implements the steps of the method for scenario-based services as described in any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method for scenario-based services as described in any one of claims 1 to 5.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method for scenario-based services as described in any one of claims 1 to 5.

Images