A method, apparatus and system for managing services

Abstract

This disclosure provides a method, apparatus, and system for managing services, relating to the field of computer technology. One specific embodiment of the method includes: determining a target service component matching the service type based on the service type; using the target service component to call an external system corresponding to the service type to execute multiple service methods included in the service type; and storing service information provided by the management service methods. By uniformly managing calls to multiple external systems and service information obtained from external systems, the flexibility and scalability of service management are improved, the efficiency of service management is increased, and the labor and time costs of service management are reduced.

Description

Technical Field

[0001] This disclosure relates to the field of digital health technology, and more particularly to a method, apparatus and system for managing services. Background Technology

[0002] In business management, services can typically be obtained from other external systems. For example, companies can obtain different types of employee welfare services from multiple external systems, such as internet medical services, physical examination services, and family doctor services.

[0003] Currently, enterprises need to process service information from each external system separately and manage employee information and various operations performed by external systems on service information. When there are many employees or many external systems, managing service information from multiple external systems separately results in poor flexibility, poor scalability, and low efficiency, leading to a waste of human resources and time costs in managing services. Summary of the Invention

[0004] In view of this, embodiments of the present disclosure provide a method, apparatus, and system for managing services, which can determine a target service component matching the service type according to the service type; use the target service component to call an external system corresponding to the service type to execute the service method of the service type; and manage the service information provided by the service method; by uniformly managing the calls to multiple external systems and the service information obtained from external systems, the flexibility and scalability of service management are improved, the efficiency of service management is improved, and the human and time costs of service management are reduced.

[0005] To achieve the above objectives, according to one aspect of the present disclosure, a method for managing services is provided, characterized by comprising: responding to receiving a service request sent by a user, determining the service type of the service request, selecting a target service component matching the service type from a preset plurality of service components; using the target service component to call an external system corresponding to the service type to execute a service method related to the service request, so that the service method determines service information for the service request; and correspondingly managing the service information determined by the service method and the service type.

[0006] Optionally, the method for managing the service further includes:

[0007] For each service type, a corresponding service component is constructed; by registering each constructed service component, the correspondence between the service type and the service component is determined; based on the correspondence between the service type and the service component, the step of selecting the target service component that matches the service type is executed.

[0008] Optionally, constructing the service component for each service type includes:

[0009] For each service type, the following steps are performed: Based on the multiple service methods included in the service type, construct the service interface corresponding to the service method; Based on the calling relationship between the service interface of the service method and the interface of the external system associated with the service interface, construct the service component.

[0010] Optionally, the method for managing services further includes: if the service information includes allocatable information, receiving an allocation request for the service information, parsing multiple user identifiers using the service type from the allocation request, creating a service identifier corresponding to the service type for each user identifier, and binding the service identifier to the user identifier.

[0011] Optionally, determining the service type of the service request includes: when the service request indicates a user's request to use the service, parsing the user's user identifier from the request and obtaining the service identifier bound to the user identifier based on the user identifier; and determining the corresponding service type based on the service identifier.

[0012] Optionally, creating a service identifier corresponding to the service type for each user identifier includes: activating a preset distributed lock; and using the preset distributed lock to determine and create a unique service identifier corresponding to the service type for each user identifier.

[0013] Optionally, the method for managing services further includes: obtaining the allocatable quantity corresponding to the service type from the service information; determining whether the number of user identifiers included in the allocation request is not greater than the allocatable quantity; if so, performing the step of creating a service identifier corresponding to the service type for each user identifier; otherwise, returning allocation exception information.

[0014] Optionally, the corresponding management of the service information and the service type determined by the service management method includes: monitoring changes to service information in the external system corresponding to the service type, and updating the managed service type and the corresponding service information based on the results of the service information changes.

[0015] To achieve the above objectives, according to a second aspect of the present disclosure, an apparatus for managing services is provided, characterized in that it includes: a component determination module, an execution method module, and a management information module; wherein,

[0016] The component determination module is used to respond to a service request sent by a user, determine the service type of the service request, and select a target service component that matches the service type from a variety of preset service components.

[0017] The execution method module is used to call the external system corresponding to the service type using the target service component, and execute the service method related to the service request, so that the service method determines service information for the service request.

[0018] The management information module is used to manage the service information determined by the service method and the service type.

[0019] Optionally, the management service apparatus is further configured to construct a corresponding service component for each service type; determine the correspondence between the service type and the service component by registering each constructed service component; and perform the step of selecting a target service component that matches the service type according to the correspondence between the service type and the service component.

[0020] Optionally, the management service apparatus is configured to construct the service component for each service type, including: for each service type, performing: constructing a service interface corresponding to the service method based on the multiple service methods included in the service type; and constructing the service component based on the calling relationship between the service interface of the service method and the interface of the external system associated with the service interface.

[0021] Optionally, the management service apparatus is further configured to, when the service information includes allocatable information, receive an allocation request for the service information, parse multiple user identifiers using the service type from the allocation request, create a service identifier corresponding to the service type for each user identifier, and bind the service identifier to the user identifier.

[0022] Optionally, the management service apparatus is configured to determine the service type of the service request, including: when the service request indicates a user's usage request for the service, parsing the user's user identifier from the usage request, and obtaining the service identifier bound to the user identifier based on the user identifier; and determining the corresponding service type based on the service identifier.

[0023] Optionally, the management service apparatus is configured to create a service identifier corresponding to the service type for each user identifier, including: activating a preset distributed lock; and using the preset distributed lock to determine and create a unique service identifier corresponding to the service type for each user identifier.

[0024] Optionally, the management service device is further configured to obtain the allocatable quantity corresponding to the service type from the service information; determine whether the number of user identifiers included in the allocation request is not greater than the allocatable quantity; if so, execute the step of creating a service identifier corresponding to the service type for each user identifier; otherwise, return allocation error information.

[0025] Optionally, the device for managing services is used to manage the service information and the service type determined by the service management method, including: monitoring changes to service information in the external system corresponding to the service type, and updating the managed service type and the corresponding service information based on the results of the service information changes.

[0026] To achieve the above objectives, according to a third aspect of the present disclosure, a system for managing services is provided, characterized in that it includes: the management service apparatus described in the second aspect, and a plurality of external systems.

[0027] To achieve the above objectives, according to a fourth aspect of the present disclosure, an electronic device for managing services is provided, characterized in that it includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described above for managing services.

[0028] To achieve the above objectives, according to a fifth aspect of the present disclosure, a computer-readable medium is provided having a computer program stored thereon, characterized in that, when the program is executed by a processor, it implements any of the methods described above for the management service.

[0029] One embodiment disclosed above has the following advantages or beneficial effects: it can determine the target service component that matches the service type based on the service type; use the target service component to call the external system corresponding to the service type to execute the service method of the service type; and manage the service information provided by the service method; by uniformly managing the calls to multiple external systems and the service information obtained from external systems, it improves the flexibility and scalability of service management, improves the efficiency of service management, and reduces the human and time costs of service management.

[0030] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0031] The accompanying drawings are provided to better understand this disclosure and do not constitute an undue limitation thereof. Wherein:

[0032] Figure 1This is a flowchart illustrating a method for providing a management service according to an embodiment of this disclosure;

[0033] Figure 2 This is a flowchart illustrating a management service provided in another embodiment of this disclosure;

[0034] Figure 3 This is a schematic diagram of the structure of a management service device provided in one embodiment of this disclosure;

[0035] Figure 4 This is a schematic diagram of the structure of a management service system provided in one embodiment of this disclosure;

[0036] Figure 5 This is an exemplary system architecture diagram to which embodiments of this disclosure can be applied;

[0037] Figure 6 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers in the embodiments of this disclosure. Detailed Implementation

[0038] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0039] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0040] Regardless of the foregoing, this disclosure also anticipates implementation schemes for users to selectively prevent the use or access to personal information data. That is, this disclosure anticipates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to accessing or storing health information, the technology of this disclosure can be configured to allow users to opt-in or opt-out to participate in the collection of personal information data during or at any time after registering for the service. In another example, users can choose not to provide specific types of health-related information. In yet another example, users can choose to limit the duration of maintaining health-related information or completely prohibit the storage of health-related information. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0041] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0042] Currently, companies typically provide employees with various incentive services, such as health checkups, shopping, and medical consultations. These services often come from different providers, and their use and management depend on the provider's platform. This lack of unified management hinders the company's ability to track and manage employee service usage. Furthermore, after acquiring services, companies need to assign login or usage credentials for each service to individual employees. With a large number of employees and diverse services, this increases the complexity of the management process and wastes labor costs. When employees directly access services from providers, these providers may need to use employees' personal information, compromising information security. Finally, this approach limits the flexibility of service management, reducing the manageability and efficiency of providing services to employees.

[0043] In view of this, such as Figure 1 As shown in the embodiments of this disclosure, a method for managing services is provided, which may include the following steps:

[0044] Step S101: In response to receiving a service request sent by a user, determine the service type of the service request, and select a target service component that matches the service type from a variety of preset service components.

[0045] Specifically, the server using the method of this disclosure receives service requests sent by users. In one embodiment, the user may be a manager or employee of an enterprise. Further, the service type of the service request is determined. The service type may be various types of employee services obtained by the enterprise for its employees (e.g., internet medical services, physical examination services, family doctor services, shopping services, etc.).

[0046] Furthermore, for each service type, a target service component matching the service type is selected from a set of preset service components. These preset service components include service components built for each service type. It is understood that when a service type is added or removed, the service component can be built or removed accordingly, improving the flexibility and scalability of service management, thereby increasing the efficiency of service management.

[0047] The method for constructing service components is as follows: For each service type, abstract the various service methods contained within the service type, and construct service interfaces for these methods. For example, for an experience service, service methods include: purchase, activation, and use. Correspondingly, write code to construct purchase, activation, and use interfaces. Further, obtain the interfaces, interface parameters, and calling methods corresponding to each service interface from the service provider's platform. Add business logic to the code that uses the service interface to call the service provider's interface, and form a service component based on the business code logic of one or more service methods (i.e., the calling relationship between the service interface of the service method and the interface of the external system associated with the service interface). For example, the service component for a shopping service includes business code for calling the activation interface provided by the shopping service provider (i.e., the interface of the external system associated with the service interface), and business code for calling the purchase interface provided by the shopping service provider. Preferably, similar service methods can be abstracted for different service types. For example, purchase, activation, and use interfaces can be abstracted from shopping services, physical examination services, and medical consultation services, further improving the uniformity and scalability of management services.

[0048] That is, constructing the service component for each service type includes: for each service type, performing: constructing the service interface corresponding to the service method based on the multiple service methods included in the service type; and constructing the service component based on the calling relationship between the service interface of the service method and the interface of the external system associated with the service interface.

[0049] Furthermore, after building service components for various service types, these service components can be registered. For example, during Spring container initialization, service components containing service interfaces can be automatically scanned and registered into a specified Map data structure (a key-value pair data storage structure), forming a service pool containing a set of preset service components. When a service component is invoked, the matching service component (i.e., the target service component) is found for the service type based on the correspondence registered in the Map; that is, a corresponding service component is built for each service type; the correspondence between the service type and the service component is determined by registering each of the built service components; and based on the correspondence between the service type and the service component, the step of selecting the target service component matching the service type is executed.

[0050] Step S102: Use the target service component to call the external system corresponding to the service type to execute the service method related to the service request, so that the service method determines service information for the service request.

[0051] Specifically, the found target service component is used to call the external system corresponding to the service type. For example, if the service type is a physical examination service, the physical examination service component is used to call the physical examination service system (external system) to execute the service request for the service method of the physical examination service (e.g., activation, purchase, use, etc.). The service information is determined through the specific service method, where the service information is associated with the service type and the service method. For example, if the service type is a physical examination service and the service method is purchase, the service information may include the quantity of physical examination services purchased, one or more physical examination identifiers, the validity period of the physical examination services, etc.

[0052] Step S103: Corresponding to the service information and service type determined by the service management method.

[0053] Specifically, service information associated with service type and service method is stored in the data source to perform further operations, such as updating the data in the data source according to changes in service information for service type by employees (e.g., changes in service information before and after using a certain service type), thereby improving the flexibility and consistency of maintaining service information.

[0054] Preferably, the service information and service type determined by the management service method include: monitoring changes to service information in external systems, such as when a purchased service expires and its status changes from valid to invalid; and then managing the data in the data source corresponding to the service type and service information based on the change result. Specifically, the external system can notify the service management platform of service information changes through a registered callback interface, and the service management platform can synchronously update the service information in the data source to ensure that the service information on the service management platform (e.g., service usage status, service validity status, etc.) is synchronized with the service information of the external system.

[0055] That is, the corresponding management of the service information and the service type determined by the service management method includes: monitoring changes to the service information in the external system corresponding to the service type, and updating the managed service type and the corresponding service information according to the results of the service information changes.

[0056] Based on the description of steps S102-S103, a process for an embodiment of purchasing services includes: Step 1: The user logs into the service management platform implemented according to an embodiment of the method disclosed herein, and then enters the service center. The service center displays a list of service types by querying a data source of service information. It can be understood that each displayed service type has a corresponding service component, and the service component has been registered in a set MAP data structure. Step 2: The user selects a service type, enters the purchase quantity, and triggers the service purchase method. Correspondingly, parameters such as the service type are passed to the service center. The service center searches for the target service component from multiple preset service components based on the service type, and then calls the purchase interface of an external system through the target service component to make the purchase. Step 3: After successful service purchase, the user receives service information returned by the external system through the interface. For example, information such as service type, quantity, and validity period. Correspondingly, storage service information and enterprise information are stored in a data source (e.g., a MySQL database) to form a service pool with enterprise attributes. Step 4: After logging into the service management platform implemented in this embodiment of the method, users can view the list of purchased service types and the corresponding service information for each service type. Enterprises can further manage the service information according to application scenarios, such as allocating one or more purchased services. The service management platform can include a front-end layer, a load balancing layer, a service layer, a cache layer, and a data source layer. The front-end layer can be developed based on the lightweight open-source framework Vue to provide user operation pages. The load balancing layer can utilize Nginx (a high-performance HTTP and reverse proxy web server) to implement reverse proxy and load balancing to handle high-concurrency scenarios. The service layer contains multiple business modules (e.g., service module, user module, message queue module, permission module, etc.), and can adopt a microservice architecture to split the internal services into different business modules, achieving loose coupling between business functions for rapid development and deployment. The cache layer can be implemented using Redis (Remote Dictionary Server), a high-performance key-value database that ensures high service availability under frequent read and write operations. The data source layer can use a MySQL database, which is small in size, fast, and can be used to build a MySQL cluster to handle massive amounts of data; furthermore, Elasticsearch can be used as a distributed data analysis engine to handle complex query scenarios for massive amounts of data.

[0057] like Figure 2 As shown in the embodiments of this disclosure, a method for managing services is provided, which may include the following steps:

[0058] Step S201: If the service information includes allocatable information, receive an allocation request for the service information; parse out multiple user identifiers that use the service type from the allocation request.

[0059] Specifically, for scenarios requiring further allocation based on service information, if the service information includes allocatable information, such as the type of service purchased, the service quantity, and the service validity period, where the service quantity indicates the allocatable quantity, then the service information includes allocatable information. Further, an allocation request is received and processed accordingly. Processing the allocation request includes parsing multiple user identifiers for the service type from the allocation request. One embodiment of sending the allocation request is that a user maintains employee information (e.g., user identifiers: name, mobile phone number, ID card number, department number, etc.) in a service management platform implemented based on the method of this disclosure. Company staff can select one or more employees based on the employee information via a page and then send an allocation request containing the employee's user identifiers to the server. This embodiment improves the efficiency of managing and allocating services.

[0060] Step S202: Create a service identifier corresponding to the service type for each user identifier, and bind the service identifier to the user identifier.

[0061] Specifically, upon receiving an allocation request, a service identifier corresponding to the service type is created for each user identifier, and the service identifier is bound to the user identifier. For example, if the received allocation request is for a physical examination service, the user identifier parsed from the allocation request (e.g., employee information used to uniquely identify employees) is used to create a physical examination service identifier for each user bid, and the physical examination service identifier is bound to the user identifier to determine the correspondence between employees and physical examination services, thus improving the flexibility and uniformity of management services. Specifically, the snowflake algorithm can be used to generate a unique distributed ID as the service identifier corresponding to the user identifier.

[0062] Preferably, when assigning services to each employee, a preset distributed lock is activated, such as a Redis distributed lock. This distributed lock prevents data anomalies (e.g., duplicate allocations) caused by abnormal operations (e.g., clicking too quickly on a page), thus ensuring that a unique service identifier is created for each user. Specifically, creating a service identifier corresponding to the service type for each user includes: activating the preset distributed lock; and using the preset distributed lock to determine that a unique service identifier corresponding to the service type is created for each user. The data source can store an allocation detail containing both the service identifier and the user identifier for each employee.

[0063] Furthermore, when processing allocation requests, service information can be validated to obtain the allocatable quantity corresponding to the service type from the service information; for example, if the allocatable quantity for a physical examination service is 10, and the number of user identifiers parsed from the allocation request is 20, then allocation error information is returned; this further improves the accuracy and efficiency of management services. Specifically, the allocatable quantity corresponding to the service type is obtained from the service information; it is determined whether the number of user identifiers included in the allocation request is not greater than the allocatable quantity; if so, the step of creating a service identifier corresponding to the service type for each user identifier is executed; otherwise, allocation error information is returned.

[0064] Preferably, after the allocation operation is completed, the allocation data can be sent to a message middleware (such as ActiveMQ) for processing. The message middleware first retrieves a service component matching the service type, and then calls the service component to invoke the allocation interface of the external system. Using the message middleware for asynchronous processing not only improves concurrency but also ensures that retry is possible if the external system's interface encounters an error, thus guaranteeing high service availability. That is, it corresponds to the service information and service type determined by the service management method.

[0065] Preferably, when synchronizing between the message middleware and the data source, binLake can be used to monitor changes in the data source and update the changed data to ES (Elasticsearch, a full-text search engine that provides distributed multi-user capabilities) and Redis. ES is used to meet complex condition queries, and its query performance is much higher than that of the database. Redis stores user allocation details composed of user identifiers and service identifiers, and uses the service identifier as the key to save the allocation details, thereby meeting the query requirements of a single allocation detail when the number of concurrent queries is large.

[0066] Step S203: When the service request indicates that the user has a request to use the service, the user identifier is parsed from the request and the service identifier bound to the user identifier is obtained based on the user identifier; the corresponding service type is determined based on the service identifier.

[0067] Specifically, employees can use all service types through the management service platform, such as using physical examination services or medical consultation services; when the service request indicates that the user has requested to use the service, the user's identifier is parsed from the request, and the service identifier bound to the user identifier is obtained based on the user identifier; the corresponding service type is determined based on the service identifier.

[0068] Furthermore, based on the service method (e.g., usage method) corresponding to the usage request, a target service component matching the service type is selected from a set of preset service components; the target service component is used to call the external system corresponding to the service type to execute the service method related to the service request, so that the service method determines service information for the service request; and the steps of managing the service information determined by the service method and the service type are described. Preferably, when user information is required when using the service, the transmitted user information can be encrypted using the RSA algorithm before calling the interface of the external system, and decrypted after receiving the service information returned by the service method, thereby improving information security.

[0069] Preferably, in response to changes in the user's status after using the service (e.g., the health check service is updated from "not used" to "used"), the service information determined by the stored service method and the service type are updated.

[0070] like Figure 3 As shown, this embodiment of the disclosure provides a management service apparatus 300, including: a component determination module 301, an execution method module 302, and a management information module 303; wherein,

[0071] The component determination module 301 is used to respond to receiving a service request sent by a user, determine the service type of the service request, and select a target service component that matches the service type from a variety of preset service components.

[0072] The execution method module 302 is used to call the external system corresponding to the service type using the target service component, and execute the service method related to the service request, so that the service method determines service information for the service request.

[0073] The management information module 303 is used to manage the service information determined by the service method and the service type.

[0074] like Figure 4 As shown, this disclosure provides a system 400 for managing services, including: a device 300 for managing services and multiple external systems.

[0075] This disclosure also provides an electronic device for managing services, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the method provided in any of the above embodiments.

[0076] This disclosure also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method provided in any of the above embodiments.

[0077] Figure 5 An exemplary system architecture 500 is shown, which can be used to implement the management services of the present disclosure.

[0078] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, and 503, a network 504, and a server 505. Network 504 serves as the medium for providing communication links between terminal devices 501, 502, and 503 and server 505. Network 504 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0079] Users can use terminal devices 501, 502, and 503 to interact with server 505 via network 504 to receive or send messages, etc. Various client applications can be installed on terminal devices 501, 502, and 503, such as e-commerce client applications, web browser applications, instant messaging tools, and enterprise management platform clients.

[0080] Terminal devices 501, 502, and 503 can be various electronic devices with displays and supporting various client applications, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0081] Server 505 can be a server that provides various services, such as a backend management server that supports client applications used by users through terminal devices 501, 502, and 503. The backend management server can process received service requests and feed back the service information obtained after processing the service requests to the terminal devices.

[0082] It should be noted that the management service method provided in this embodiment is generally executed by server 505, and correspondingly, the management service device is generally located in server 505.

[0083] It should be understood that Figure 5 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0084] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing a terminal device according to embodiments of the present disclosure. Figure 6 The terminal device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0085] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0086] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0087] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this disclosure.

[0088] It should be noted that the computer-readable medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, 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 device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0089] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0090] The modules and / or units described in the embodiments of this disclosure can be implemented in software or hardware. The described modules and / or units can also be housed in a processor; for example, a processor can be described as including a component determination module, an execution method module, and a management information module. The names of these modules do not necessarily limit the module itself; for example, the management information module can also be described as "a module corresponding to the management of service information determined by the service method and the service type."

[0091] In another aspect, this disclosure also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: in response to receiving a service request sent by a user, determining the service type of the service request; selecting a target service component matching the service type from a preset plurality of service components; using the target service component to call an external system corresponding to the service type to execute a service method related to the service request, so that the service method determines service information for the service request; and correspondingly managing the service information determined by the service method and the service type.

[0092] The embodiments of this disclosure can determine the target service component that matches the service type based on the service type; use the target service component to call the external system corresponding to the service type to execute the service method of the service type; and manage the service information provided by the service method; by uniformly managing the calls to multiple external systems and the service information obtained from external systems, the flexibility and scalability of service management are improved, the efficiency of service management is improved, and the human and time costs of service management are reduced.

[0093] 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 occur depending on 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 managing services, characterized in that, include: In response to receiving a service request from a user, the service type of the service request is determined, and a target service component matching the service type is selected from a variety of preset service components. The method for constructing the service component is as follows: for each service type, multiple service methods included in the service type are abstracted, and service interfaces are constructed for the multiple service methods; based on the calling relationship between the service interfaces of the service methods and the interfaces of external systems associated with the service interfaces, the service component is constructed. The target service component is used to call the external system corresponding to the service type to execute the service method related to the service request, so that the service method determines service information for the service request. The corresponding service information and service type determined by the service management method.

2. The method according to claim 1, characterized in that, Further includes: Build corresponding service components for each service type; By registering and constructing each of the service components, the correspondence between the service type and the service component is determined; Based on the correspondence between the service type and the service component, the step of selecting the target service component that matches the service type is executed.

3. The method according to claim 1, characterized in that, Further includes: If the service information includes assignable information, Receive an allocation request for the service information, and parse multiple user identifiers for the service type from the allocation request. Create a service identifier corresponding to the service type for each user identifier, and bind the service identifier to the user identifier.

4. The method according to claim 3, characterized in that, Determining the service type of the service request includes: In the case where the service request indicates a user's request to use the service. The user's identifier is parsed from the usage request, and the service identifier bound to the user identifier is obtained based on the user identifier; The corresponding service type is determined based on the service identifier.

5. The method according to claim 3, characterized in that, Creating a service identifier corresponding to the service type for each of the user identifiers includes: Activate the preset distributed lock; Using the preset distributed lock, a unique service identifier corresponding to the service type is created for the user identifier.

6. The method according to claim 3, characterized in that, Further includes: Obtain the allocatable quantity corresponding to the service type from the service information; Determine whether the number of user identifiers included in the allocation request is not greater than the allocatable number. If so, execute the step of creating a service identifier corresponding to the service type for each user identifier; otherwise, return allocation error information.

7. The method according to claim 1, characterized in that, The corresponding management of the service information determined by the service method and the service type include: Monitor changes to service information in external systems corresponding to the service type, and update the managed service type and its corresponding service information based on the results of the service information changes.

8. A management service device, characterized in that, include: The modules are defined as: component module, execution method module, and management information module; among them, The component determination module is used to respond to a service request sent by a user, determine the service type of the service request, and select a target service component that matches the service type from a variety of preset service components. The method for constructing the service component is as follows: for each service type, abstract a variety of service methods included in the service type, and construct service interfaces for the various service methods; construct the service component based on the calling relationship between the service interfaces of the service methods and the interfaces of external systems associated with the service interfaces. The execution method module is used to call the external system corresponding to the service type using the target service component, and execute the service method related to the service request, so that the service method determines service information for the service request. The management information module is used to manage the service information determined by the service method and the service type.

9. A system for managing services, characterized in that, include: The management service apparatus and multiple external systems as described in claim 8.

10. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

11. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

Images