WO2017173928A1 - 业务处理系统、业务处理方法以及业务更新方法 - Google Patents

业务处理系统、业务处理方法以及业务更新方法 Download PDF

Info

Publication number
WO2017173928A1
WO2017173928A1 PCT/CN2017/077996 CN2017077996W WO2017173928A1 WO 2017173928 A1 WO2017173928 A1 WO 2017173928A1 CN 2017077996 W CN2017077996 W CN 2017077996W WO 2017173928 A1 WO2017173928 A1 WO 2017173928A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
instance
routing
service instance
routing information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/077996
Other languages
English (en)
French (fr)
Inventor
朱哲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Publication of WO2017173928A1 publication Critical patent/WO2017173928A1/zh
Priority to US16/153,616 priority Critical patent/US20190042276A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/656—Updates while running
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/59—Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service processing system, a service processing method, and a service update method.
  • each service platform carries many different types of services, and these services are frequently updated. Therefore, it is necessary to frequently update existing service instances on the service platform.
  • no reasonable correspondence is established between the service request and the service instance, and each service instance accepts the management and call of the service processing platform as a whole. Therefore, when a service content is updated (that is, a service instance needs to be updated), the entire service platform needs to be redeployed, and the related service process needs to be restarted, which seriously affects the normal service process of each service instance on the platform.
  • the PaaS (Plain-as-a-Service, PaaS) platform adopts code delivery, and the process restarts to update the service content. That is, when the service content update is detected, the PaaS platform stops the related process of the service. And re-loading the new service instance. If the service-related process needs to be restarted after the loading is completed, the normal service processing can be performed.
  • the prior art has at least the following drawbacks: when performing service update, the platform needs to stop the running of the related process of the service until the new service content is successfully loaded, which may cause long-term service interruption, and also exists during the restart process. Various risks may cause business interruption and affect the stability of business operations.
  • the present invention provides a service processing system, a service processing method, and a service update method, so as to reduce the impact on platform operation when updating service content.
  • the present invention provides a service processing method, including: receiving a service request; extracting service instance routing information included in a URL of the service request; and invoking the service instance routing information according to the service instance routing information
  • the corresponding service instance processes the service request, where each of the service instances corresponds to at least one service instance routing information.
  • the present invention also provides a service processing method, where the service processing method is executed on a service processing system, where the service processing system includes a service processing server, and the service processing server includes a routing layer and a service layer, where the routing layer is A routing module is run, and the service layer runs a plurality of service instances for performing service processing, and the service processing method includes:
  • the routing module receives the service request, extracts the service instance routing information included in the URL of the service request, and invokes the service instance corresponding to the routing information of the service instance according to the routing information of the service instance, and processes the service request.
  • each of the service instances corresponds to at least one service instance routing information.
  • the present invention also provides a service processing system, including a service processing server, where the service processing server includes a routing layer and a service layer, and a routing module is run in the routing layer, and multiple services are run in the service layer.
  • a service processing server includes a routing layer and a service layer, and a routing module is run in the routing layer, and multiple services are run in the service layer.
  • the routing module is configured to receive a service request, extract the service instance routing information included in the URL of the service request, and invoke the service instance corresponding to the routing information of the service instance according to the routing information of the service instance, where Each of the service instances corresponds to at least one service instance routing information; the service instance is configured to perform service processing corresponding to the service request.
  • the present invention also provides a service update method, where the service update method is performed on a service processing system, where the service processing system includes a service processing server and a configuration server.
  • the service processing server includes a routing layer and a service layer, wherein the routing layer runs a routing module, and the service layer runs multiple service instances for performing service processing.
  • the service layer includes a first instance running space and a second instance running space, where the service instance in the first instance running space can accept the call of the routing module, and the service in the second instance running space The instance does not accept the call of the routing module.
  • the service processing server generates a new service instance according to the new service content, and replaces the corresponding old service instance with the new service instance.
  • a direct correspondence between a service request for each service and a specific service instance is established, and the URL is included in the process of processing the service request.
  • the business instance routing information finds and completes the call of the business instance. Through such a calling mechanism, When a specific service call is made, the URL (Uniform Resource Locator) information in the service request can directly locate a specific service instance.
  • URL Uniform Resource Locator
  • Such a call mechanism makes the call relationship of the service request to the service instance very clear, and each service is clearly defined. Relatively independent, it is convenient for business management and deployment. Especially when updating business content, it only involves the update operation of the business instance corresponding to the business content, without affecting other business instances, and will not affect the entire business processing. The operation of the system.
  • FIG. 1 is a flowchart of a service processing method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic structural diagram of a service processing system according to Embodiment 2 of the present invention.
  • FIG. 3 is a second schematic structural diagram of a service processing system according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic structural diagram of a service processing system according to Embodiment 3 of the present invention.
  • FIG. 5 is a second schematic structural diagram of a service processing system according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic structural diagram of a service processing system according to Embodiment 4 of the present invention.
  • FIG. 7 is a second schematic structural diagram of a service processing system according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic flowchart of a service update method according to Embodiment 6 of the present invention.
  • FIG. 1 it is a flowchart of a service processing method according to Embodiment 1 of the present invention, and the method includes:
  • Step 101 Receive a service request.
  • Step 102 Extract the service instance routing information included in the URL (Uniform Resource Locator) of the service request.
  • the field information of the URL is redesigned and the service instance routing information is added.
  • Step 103 In accordance with the service instance routing information, invoke the service instance corresponding to the routing information of the service instance, and process the service request.
  • the “instance path” may be established in advance with the service instance in the service processing system. Mapping the relationship, so that the service processing system can find the corresponding service instance according to the "instance path". For example, in the URL of the previous example, the "testpay" can be mapped with the service instance that processes the payment, thereby implementing the service for processing the payment. The invocation of the instance.
  • Each service instance corresponds to at least one service instance routing information.
  • the business processing content associated with each other is designed in a service instance from a design perspective of the service instance, so that the service instance can be more effectively utilized. System resources, and also facilitate the management of business instances.
  • the name of the service instance can be called for the service instance. Therefore, in the foregoing step 103, the corresponding service instance name can be obtained according to the service instance routing information, and then Then, the business instance is invoked through the business instance name.
  • Each service instance name corresponds to at least one service instance routing information, and the corresponding relationship may be pre-stored in the service processing system.
  • the plurality of service instances running in the business layer are independent of one another and the name of the business instance is unique.
  • service parameters such as user information parameters.
  • service parameters may be included in the URL, or may be included in the data packet of the service request, or may be pre-stored in the business processing system.
  • the foregoing service processing method may further include the step of sending a service parameter to the service instance, specifically, the following situations:
  • the first service parameter mentioned here is a parameter derived from a service request, such as user information for issuing a service request.
  • Second business parameter is the default service parameter of the system.
  • the second service parameter may be a parameter such as a key.
  • the system default parameter that can only be called a predetermined number of times in one minute is set.
  • the corresponding relationship between the service instance routing information and the service instance name and the second service parameter may be represented as a corresponding form, and the corresponding relationship is stored in the service processing system, and is used for calling and processing the service instance:
  • the service routing information in the URL of the different service request is different.
  • the different service requests may be processed by the same service instance.
  • the service request 1 and the service request 2 in the above table are all processed by the service instance corresponding to the service instance name 1.
  • the second service parameter is a default service parameter of the system, and is preset according to different service requests. Different service requests may correspond to the same second service parameter, or may correspond to different second service parameters.
  • the system service may not configure the system default parameters in advance, and completely rely on the service parameters carried in the service request for service processing, such as the service request 5 in the above table.
  • a layer of index structure may be added between the service instance and the service instance routing information, which is referred to as a routing name in this embodiment, as shown in the following Table 2:
  • the route name is first found through the service routing information, and then the service instance name or the second service parameter is obtained through the route name.
  • the configuration server has certain rules for data storage and indexing. Therefore, information such as the route name and the service instance name are pre-stored according to the index rule of the configuration server itself, and then the mapping relationship between the service routing information and the route name is added.
  • FIG. 2 it is a schematic structural diagram of a service processing system according to Embodiment 2 of the present invention.
  • the service processing system includes a service processing server 1 including a routing layer 11 and a service layer 12 in a routing layer. Running the routing module 111, running multiple service instances 121 in the service layer,
  • the routing module 111 is configured to receive the service request, extract the service instance routing information included in the URL of the service request, and use the service instance routing information corresponding to the service instance routing information corresponding to the service instance routing information (the service instance number is 1 in the figure)
  • the service instance 121 is used to perform the service processing corresponding to the service request.
  • Each service instance may have a one-to-one or one-to-many relationship between the service instance and the service instance routing information, and each service instance may have multiple different specific services.
  • the function that is, can be used to process a plurality of different service requests, which can trigger the service instance to perform different business processes by different service parameters used in the call.
  • the figure exemplarily shows a case where n service requests are in one-to-one correspondence with n service instances. In fact, the service requests 1 to n in the figure may have less than n service instances to perform service processing.
  • the payment-related functions for example, calculating the total price function and the transfer payment function
  • the client After clicking the "Billing" button, the client first sends a service request for calculating the total price to the business processing system, and carries the relevant business parameters such as the selected product information in the service request, and the business processing system passes the above-mentioned business.
  • the method calls the payment service instance to calculate the total price, and returns the data to the user.
  • the client sends a “transfer payment” service request to the business processing system again, and in the business request. Carrying the user payment related parameters, the service processing system calls the payment service instance again to perform the transaction processing of the transfer payment, thereby completing the entire payment process.
  • the correspondence between the service instance and the service instance routing information may be stored in a separately configured configuration server.
  • the service processing system of this embodiment may further include a configuration server 2, where the service instance routing information and each service are stored in the configuration server 2.
  • the service instance can be called as long as the name of the service instance is known. Therefore, each service instance is registered in the configuration server, and the service instance routing information and the service instance are pre-configured.
  • the first correspondence information between the service instance names are stored in a separately configured configuration server.
  • n service instance routing information may correspond to a name of a service instance that is less than n.
  • the routing module 111 extracts the service instance routing information included in the URL of the service request, and then accesses the configuration server 2 to obtain the corresponding information according to the service instance routing information and the first correspondence relationship information.
  • the name of the business instance, and the business instance in the business layer is invoked to perform the corresponding business process through the business instance name.
  • the service parameters required for invoking the service instance to perform the service processing may be included in the URL or the data packet of the service request, and for some system default parameters may be stored in the configuration server,
  • the service instance routing information is obtained.
  • FIG. 3 which is a schematic structural diagram of a service processing system according to Embodiment 2 of the present invention
  • a second service parameter which is a default parameter of the system, is stored in advance in the configuration server, and the second service parameter is stored.
  • the second correspondence information between the service instance routing information is shown in the figure. In fact, the n service instance routing information may be corresponding to less than n second. Business parameters.
  • the routing module can access the configuration server, obtain the second service parameter, and send the second service parameter according to the service instance routing information and the second correspondence relationship information, if the service request needs to invoke the default second service parameter of the system. Give a business instance.
  • the routing module may also extract the first service parameter from the URL and/or the data packet of the service request according to the situation, and send the first service parameter to the service instance.
  • the service processing system in this embodiment adopts a layered architecture, and the service instance is uniformly placed in the service layer, and the function for finding and invoking the service instance is placed in the routing layer, and the service instance route is set in the URL.
  • the information and the corresponding relationship between the service instance routing information and the service instance are established in the service processing system, so that the specific service instance can be located through the URL, which facilitates the management and deployment of the service.
  • the service content is updated, only the update operation of the service instance corresponding to the service content is involved, and the other service instances are not affected. It will not affect the operation of the entire business processing system.
  • the first configuration information between the service instance routing information and the service instance name is stored by setting up an independent configuration server, so that the routing module can directly obtain the service instance name, thereby completing the calling.
  • the second corresponding relationship between the second service parameter and the service instance routing information is also stored in the configuration server, so that the routing module can obtain the system default parameter corresponding to the current service request while obtaining the service instance name. So that it can be passed directly to the business instance during the invocation of the business instance.
  • This embodiment adds the structure of the service layer to the second embodiment.
  • FIG. 4 it is one of the structural diagrams of the service processing system according to the third embodiment of the present invention.
  • the service processing server of the embodiment further includes a service.
  • Layer 10 the service instance routing information includes a service category field and a service routing field, the service category field identifies the service category, and the routing layer is configured with multiple routing modules, and each routing module can correspond to one service category respectively. among them,
  • URL structure For example, the following URL structure can be used:
  • ⁇ app ⁇ represents the service category field
  • ⁇ path ⁇ represents the routing field of the specific service instance under the service category, that is, all the routing instances are classified by the ⁇ app ⁇ field, and then in each category. The following uses the ⁇ path ⁇ field to establish a route for a specific service instance.
  • the service layer can perform service distribution according to the service category field.
  • the service layer 10 includes a distribution module 101, configured to receive a service request, and distribute the service request to the corresponding routing module 111 according to the service category field included in the URL of the service request.
  • the corresponding routing module 111 can access the configuration server 2 according to the method in the second embodiment, and search for the corresponding information according to the service instance routing information, that is, according to “ ⁇ app ⁇ / ⁇ path ⁇ ”.
  • the routing diagram exemplarily shows two routing modules. After the service distribution, the two routing modules correspond to service instances 1 to m and service instances m+1 to n, respectively.
  • the service layer may further include a rights authentication module for requesting a service before routing is distributed.
  • Line authority authentication if the service request does not have the service invocation right, directly block the service request or return a rejection response to the sender of the service request.
  • the service layer may further include a protocol parsing module for performing protocol parsing on the service request.
  • the service layer is the top layer of the service processing system. The service layer needs to support multiple network protocols to receive and forward corresponding service requests to the lower layer. For example, the service layer can access at least regular network access such as HTTP and HTTPS. The agreement provides support.
  • the call processing of the service request is implemented through the layered structure of the three layers. Accordingly, the corresponding design of the service instance routing information is also performed, and the service instance routing information is divided into service category fields that can identify the service category and The service routing field of the specific service instance route under the large class is divided into two parts.
  • the service processing system are firstly distributed according to the service class at the service layer, and the traffic request after the traffic distribution is handed over to the routing module of the routing layer for further processing. Routing operations to locate specific business instances and make calls, while actual business processing is done entirely by business instances running in the business layer.
  • the service request can be quickly and accurately invoked, and the classification management of the service instance is facilitated.
  • FIG. 5 it is the second schematic structural diagram of the service processing system according to the third embodiment of the present invention, and may be in the service layer 12
  • the running space of the business instance is divided into a first instance running space and a second instance running space, and the business instance in the first instance running space can accept the calling of the routing module, and the business instance in the second instance running space does not accept the routing module. Call.
  • the configuration server 2 may further include a monitoring module 21, which may further include a service instance updating module 15.
  • the monitoring module 21 is configured to monitor the update of the service content, and notify the service instance update module 15; the service instance update module 15 is configured to generate a new service instance according to the new service content, and replace the corresponding operation with the new service instance.
  • the old business instance in the first running space, and puts the old business instance into the second instance running space, and the old business instance can continue to perform the business request received before the update in the second instance running space.
  • Business processing after the completion of business processing, the system will be logged off.
  • the business instance can be updated and replaced without affecting the previous business processing.
  • FIG. 6 it is a schematic structural diagram of a service processing system according to Embodiment 4 of the present invention.
  • the storage layer 13 is added, and service data required for service processing is stored in the storage.
  • the service instance 121 retrieves the required service data from the storage layer 13 during the process of performing the service processing.
  • the business process logic is encapsulated in the business layer execution, and the business data involved in the business process is placed in the storage layer, thereby separating the business logic and the business data, which is more convenient. Make changes to business logic or business data without having an excessive impact on the entire business processing system. In practical applications, in the business processing system, the business processing logic is more updated. Based on the above architecture, if the update of the business content only involves the update of the business processing logic, then the business instance in the business layer may be updated instead of Will affect the business data in the storage tier.
  • FIG. 7 is the second schematic structural diagram of the service processing system according to the fourth embodiment of the present invention
  • the data interface layer 14 disposed between the service layer 12 and the storage layer 13 may also be included.
  • the service data of the storage layer 13 has multiple data storage formats, and the data interface layer is used to perform data between the service layer 12 and the storage layer 13.
  • the format is converted and provides a common data access interface to the business instance 121 of the business layer.
  • the data in the storage layer 13 may use a common data system such as an Oracle database system, a Sybase database system, or an MS SQL Server.
  • the data interface layer is used to convert the data format between the service layer and the storage layer, and provides a common data access interface to the service instance of the service layer.
  • the business logic and the business data can be completely separated.
  • different data storage formats can be adopted, thereby being compatible with various platform data, and the data format conversion work can be This is done by the data interface layer.
  • the business instance running in the business layer can directly face the data interface layer, and the unified data interface can be used to call the data of the storage layer, thereby shielding the underlying data difference.
  • the embodiment is related to the service processing method of the service processing system according to the second to fourth embodiments, the service processing method is executed on the service processing system, and the service processing system includes at least a service processing server, and the service processing server includes a routing layer and a service layer.
  • a routing module runs in the routing layer, and multiple service instances that perform business processing are run in the service layer.
  • the service processing method includes: the routing module receives the service request, extracts the service instance routing information included in the URL of the service request, and invokes the service instance corresponding to the routing information of the service instance according to the routing information of the service instance, and processes the service request, where Each business instance corresponds to at least one business instance routing information.
  • the URL in the service request is passed (uniform resource)
  • the locator information can be directly located to a specific business instance.
  • Such a calling mechanism makes the calling relationship of the business request to the business instance very clear, and each service is relatively independent, which facilitates the management and deployment of the business.
  • the service processing system may further include a configuration server, where the configuration server stores the first correspondence information between the service instance routing information and the service instance name of each service instance, and each service instance name and at least one service instance route The information corresponds.
  • the operation of the service instance corresponding to the routing information of the service instance may be specifically performed according to the routing information of the service instance, and the routing module accesses the configuration server, and obtains the corresponding information according to the routing information of the service instance and the first correspondence information.
  • the configuration server stores in advance a second service parameter as a default parameter of the system, and stores second correspondence information between the second service parameter and the service instance routing information.
  • the service processing method may further include:
  • the routing module accesses the configuration server, obtains the second service parameter according to the service instance routing information and the second correspondence information, and sends the second service parameter to the service instance; and/or extracts the first service from the URL and/or the service request packet. Parameters and sent to the business instance.
  • the service processing server may further include a service layer, the service instance routing information includes a service category field and a service routing field, the service category field identifies the service category, and the routing layer is configured with multiple routing modules, and each service module corresponds to one service category.
  • the service processing method may further include: the service layer receiving the service request, and distributing the service request to the corresponding routing module according to the service category field included in the URL of the service request.
  • the call processing of the service request is implemented through the hierarchical structure of the three layers, and correspondingly, the corresponding design is also performed on the routing information of the service instance, and firstly, a large number of service requests received by the service processing system are performed on the service layer.
  • the traffic is diverted according to the service class, and the traffic request after the traffic is forwarded to the routing module of the routing layer to perform further routing operations, thereby locating and calling the specific service instance, and the actual service processing is completely in the service layer. Run the business instance to complete.
  • the service request can be quickly and accurately invoked, and the classification management of the service instance is facilitated.
  • the embodiment relates to a service update method of the service processing system based on the foregoing embodiments, where the service processing system includes at least a service processing server and a configuration server.
  • the service processing server includes a routing layer and a service layer.
  • the routing layer runs a routing module, and the service layer runs multiple service instances for performing service processing.
  • the configuration server stores the first correspondence information between the service instance routing information and the service instance name of each service instance, where each service instance name corresponds to at least one service instance routing information,
  • the service layer may further include a first instance running space and a second instance running space, where the service instance in the first instance running space can accept the calling of the routing module, and the service instance in the second instance running space does not accept the routing module. transfer,
  • FIG. 8 it is a schematic flowchart of a service update method according to Embodiment 6 of the present invention.
  • the service update method in this embodiment includes:
  • Step 201 In the configuration server, the update of the service content is monitored, and the service processing server is notified.
  • the service content may be a program code for executing a specific service content.
  • Step 202 The service processing server generates a new service instance according to the new service content, and replaces the corresponding old service instance with the new service instance.
  • the replacement operation of the new and old service instances may be specifically: replacing the corresponding old service instance running in the first running space with the new service instance, and placing the old service instance into the second In the instance run space.
  • the service update method of this embodiment only involves the update operation of the service instance corresponding to the service content, without affecting other service instances, and does not affect the operation of the entire service processing system. And, the old service instance is placed in the second instance running space that does not accept the routing module call to continue the business processing, and the new business instance is placed in the first instance running space that can accept the call of the routing module, so that the new and old business Instances can coexist and enable smooth business instance updates.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明涉及一种业务处理系统、业务处理方法以及业务更新方法，其中，业务处理方法包括：接收业务请求；提取业务请求的URL中包含的业务实例路由信息；根据业务实例路由信息，调用业务实例路由信息对应的业务实例，对业务请求进行处理，其中，每个所述业务实例与至少一个业务实例路由信息相对应。本实施例在进行具体业务调用的时，通过业务请求中的URL信息就能够直接定位到具体的业务实例，这样的调用机制使得业务请求到业务实例的调用关系非常清晰，每项业务相对独立，便于业务的管理和部署，尤其在进行业务内容更新时，仅涉及与该业务内容对应的业务实例的更新操作，而不会影响到其他的业务实例，也不会影响到整个业务处理系统的运行。

Description

业务处理系统、业务处理方法以及业务更新方法
本申请要求2016年04月06日递交的申请号为201610211061.1、发明名称为“业务处理系统、业务处理方法以及业务更新方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种业务处理系统、业务处理方法以及业务更新方法。
背景技术
目前，各业务平台承载着众多不同类型的业务，并且这些业务更新频繁，因此，需要经常更新业务平台上已有的业务实例。传统的业务平台中，业务请求与业务实例之间没有建立合理的对应关系，各个业务实例作为整体接受业务处理平台的管理和调用。因此，当对一项业务内容进行更新(即需要更新业务实例)时，需要对整个业务平台进行重新部署，需要重新启动相关业务进程，严重影响平台上各业务实例的正常服务进程。
例如，PaaS(Platform-as-a-Service，简称PaaS)平台采用代码下发，进程重启方式来实现业务内容的更新，即当检测到有业务内容更新时，PaaS平台停止该业务的相关进程运行，并重新加载新的业务实例，若加载完成后，需要重新启动该业务相关进程后，才能进行正常的业务处理。
因此，现有技术至少存在如下缺陷：当进行业务更新时，平台需停止该业务的相关进程的运行直至新的业务内容成功加载，这样会造成长时间的业务中断，且在重启过程中也存在各种风险，可能会导致业务中断，影响业务运行的稳定性。
发明内容
本发明提供一种业务处理系统、业务处理方法以及业务更新方法，以实现在更新业务内容时，减少对平台运行的影响。
为达到上述目的，本发明提供了一种业务处理方法，包括：接收业务请求；提取业务请求的URL中所包含的业务实例路由信息；根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例，对所述业务请求进行处理，其中，所述每个所述业务实例与至少一个业务实例路由信息相对应。
本发明还提供了一种业务处理方法，所述业务处理方法在业务处理系统上执行，所述业务处理系统包括业务处理服务器，所述业务处理服务器包括路由层和业务层，所述路由层中运行有路由模块，所述业务层中运行有多个执行业务处理的业务实例，所述业务处理方法包括：
所述路由模块接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例，对所述业务请求进行处理，其中，所述每个所述业务实例与至少一个业务实例路由信息相对应。
本发明还提供了一种业务处理系统，包括业务处理服务器，所述业务处理服务器中包括路由层和业务层，在所述路由层中运行有路由模块，所述业务层中运行有多个业务实例，
所述路由模块用于接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据所述业务实例路由信息，对与所述业务实例路由信息对应的业务实例进行调用，其中，所述每个所述业务实例与至少一个业务实例路由信息相对应；所述业务实例用于执行所述业务请求对应的业务处理。
本发明还提供了一种业务更新方法，所述业务更新方法在业务处理系统上执行，所述业务处理系统包括业务处理服务器和配置服务器，
所述业务处理服务器包括路由层和业务层，所述路由层中运行有路由模块，所述业务层中运行有多个执行业务处理的业务实例，
在所述配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，所述每个所述业务实例名称与至少一个业务实例路由信息相对应，
所述业务层中包括第一实例运行空间和第二实例运行空间，在所述第一实例运行空间中的业务实例能够接受所述路由模块的调用，在所述第二实例运行空间中的业务实例不接受所述路由模块的调用，
业务更新方法包括：
在所述配置服务器中，监听业务内容的更新，并通知所述业务处理服务器；
所述业务处理服务器根据新的业务内容生成新的业务实例，用该新的业务实例替换对应的旧的业务实例。
在本发明的业务处理系统、业务处理方法以及业务更新方法的技术方案中，将针对每项业务的业务请求与具体业务实例建立直接的对应关系，在业务请求的处理过程中，通过URL中包含业务实例路由信息找到并完成业务实例的调用。通过这样的调用机制， 在进行具体业务调用时，通过业务请求中的URL(统一资源定位符)信息就能够直接定位到一个具体的业务实例，这样的调用机制使得业务请求到业务实例的调用关系非常清晰，每项业务相对独立，便于业务的管理和部署，尤其在进行业务内容更新时，仅涉及与该业务内容对应的业务实例的更新操作，而不会影响到其他的业务实例，也不会影响到整个业务处理系统的运行。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本发明的限制。而且在整个附图中，用相同的参考符号表示相同的部件。
图1为本发明实施例一的业务处理方法的流程图；
图2为本发明实施例二的业务处理系统的结构示意图之一；
图3为本发明实施例二的业务处理系统的结构示意图之二；
图4为本发明实施例三的业务处理系统的结构示意图之一；
图5为本发明实施例三的业务处理系统的结构示意图之二；
图6为本发明实施例四的业务处理系统的结构示意图之一；
图7为本发明实施例四的业务处理系统的结构示意图之二；
图8为本发明实施例六的业务更新方法的流程示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。下面结合附图对本发明实施例进行详细描述。
实施例一
如图1所示，其为本发明实施例一的业务处理方法的流程图，该方法包括：
步骤101：接收业务请求。
步骤102：提取业务请求的URL(统一资源定位符)中所包含的业务实例路由信息。本实施例对URL的字段信息进行重新的设计定义，在其中加入了业务实例路由信息。本实施例的URL的结构可以采用如下结构：http：{host}/{instancepath}？auth[token]，其中， “http”为网路协议部分，“host”为服务器的IP地址和主机名，“auth[token]”为URL的参数部分，“instancepath”是业务实例路由信息。例如：http：//www.test.com/test pay？auth[token]＝xxxx&。其中，这里的“testpay”就是业务实例路由信息。
步骤103：根据业务实例路由信息，调用业务实例路由信息对应的业务实例，对业务请求进行处理，与上面的URL结构相对应地，可以预先将“instancepath”与在业务处理系统中的业务实例建立映射关系，从而使得业务处理系统根据“instancepath”就可以找到对应的业务实例，例如前面的示例的URL中，可以将“testpay”与处理支付的业务实例建立映射关系，从而实现对处理支付的业务实例的调用。其中，每个业务实例与至少一个业务实例路由信息相对应，这是因为一般从业务实例的设计角度来说，会将彼此关联的业务处理内容设计在一个业务实例中，这样能够更加有效地利用系统资源，并且也便于业务实例的管理。
具体地，在实际的程序处理过程中，只要获知了业务实例的名称就可以针对该业务实例进行调用，因此，在上述步骤103中，可以先根据业务实例路由信息获取对应的业务实例名称，然后，再通过业务实例名称，调用业务实例。其中，每个业务实例名称与至少一个业务实例路由信息相对应，该对应关系可以预先存储在业务处理系统中。优选地，在业务层中运行的多个业务实例之间彼此相互独立，并且业务实例的名称是唯一的。
在上述的业务实例调用机制中，将针对每项业务的业务请求与具体业务实例建立直接的对应关系，在业务请求的处理过程中，通过URL中包含业务实例路由信息找到并完成业务实例的调用。通过这样的调用机制，在进行具体业务调用时，通过业务请求中的URL(统一资源定位符)信息就能够直接定位到一个具体的业务实例，这样的调用机制使得业务请求到业务实例的调用关系非常清晰，每项业务相对独立，便于业务的管理和部署，尤其在进行业务内容更新时，仅涉及与该业务内容对应的业务实例的更新操作，而不会影响到其他的业务实例，也不会影响到整个业务处理系统的运行。
此外，在调用业务实例执行业务处理时，还需要使用业务参数，例如用户信息参数等。这些业务参数可以包含在URL中，也可以包含在业务请求的数据包，也可以预先存储在业务处理系统中。
因此，上述的业务处理方法还可以包括向业务实例发送业务参数的步骤，具体地，包括如下几种情况：
1)从URL中和/或业务请求的数据包中提取第一业务参数，并发送给业务实例。这里所说的第一业务参数是来自于业务请求自带的参数，例如发出业务请求的用户信息等。
2)根据业务实例路由信息获取预先存储的作为系统默认参数的第二业务参数，并发送给业务实例。在这种情况下，上述的业务实例路由信息除了可以指向业务实例名称之外，还指向了用于业务处理的系统默认的第二业务参数，从而使得在调用业务实例的同时也能获取到该第二业务参数。这里所说的第二业务参数为系统默认的业务参数，例如，业务实例有些私密数据，需要进行加密处理，那么第二业务参数可以是密钥这样的参数。再例如，对某个业务实例不希望太频繁的调用，设置了1分钟内只能调用预定次数的系统默认参数。
3)也可以结合上述1)和2)的情形，除了从URL中和/或业务请求的数据包获取第一业务参数以外，同时还调用系统默认的第二业务参数，用于业务实例执行业务处理。
综上所述，上述的业务实例路由信息与业务实例名称以及第二业务参数的对应关系可以表示为如下对应形式，该对应关系存储在业务处理系统中，用于业务实例的调用和业务处理：
表一
Figure PCTCN2017077996-appb-000001
从上面的表一中可以看出，业务请求与业务路由信息之间是一一对应的，也就是说不同的业务请求的URL中的业务路由信息是不同的。而不同的业务请求可能会由同一个业务实例来处理，如上表中的业务请求1和业务请求2均由“业务实例名称1”对应的业务实例来进行处理。此外，第二业务参数为系统默认的业务参数，会根据业务请求的不同而预先设定，不同的业务请求可以对应相同的第二业务参数，也可以对应不同的第二业务参数。当然，针对部分业务请求，系统业务可以不预先配置系统默认参数，完全依靠业务请求中携带的业务参数进行业务处理，例如上表中的业务请求5。
在实际应用中，在业务实例和业务实例路由信息之间，还可以增加一层索引结构，在本实施例中称为路由名字，例如下表二中所示：
表二
Figure PCTCN2017077996-appb-000002
即通过业务路由信息先找到路由名字，然后再通过路由名字获取业务实例名称或者第二业务参数。在实际应用中，配置服务器会存在一定的数据存储和索引的规则。因此，会按照配置服务器本身的索引规则将路由名字和业务实例名称等信息进行预先存储，然后再增加业务路由信息和路由名字之间的映射关系。
实施例二
如图2所示，其为本发明实施例二业务处理系统的结构示意图之一，该业务处理系统包括业务处理服务器1，该业务处理服务器中包括路由层11和业务层12，在路由层中运行有路由模块111，业务层中运行有多个业务实例121，
路由模块111用于接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据业务实例路由信息，对与业务实例路由信息对应的业务实例121(图中将业务实例编号为1至n)进行调用，业务实例121用于执行业务请求对应的业务处理。
其中，每个业务实例与至少一个业务实例路由信息相对应，即业务实例与业务实例路由信息之间可以是一对一或者一对多的关系，每个业务实例可以具有处理多个不同具体业务的功能，即可以用来处理多个不同的业务请求，这些业务请求可以通过调用时使用的业务参数的不同来触发业务实例执行不同的业务处理。图中仅示例性地表示出n个业务请求与n个业务实例一一对应的情形，实际上，图中的业务请求1～n可以有小于n个的业务实例来执行业务处理。
例如，以网购的业务处理系统为例，在进行业务实例设计时，可以将支付相关的功能(例如，计算总价功能和转账支付功能)设计为由一个业务实例完成，用户在完成购物选择后，可以在点击“结算”按键后，客户端首先会向业务处理系统发出“计算总价”的业务请求，并在业务请求中携带已选商品信息等相关业务参数，业务处理系统通过上述的业务方法调用支付业务实例进行总价计算，并返回数据呈献给用户，之后，在用户点击“确认”按键后，客户端会再次向业务处理系统发出“转账支付”的业务请求，并在业务请求中携带用户支付相关的参数，业务处理系统再次调用支付业务实例进行转账支付的业务处理，从而完成整个支付过程。
进一步地，业务实例与业务实例路由信息之间的对应关系可以存储在单独设置的配置服务器中。如图3所示，其为本发明实施例二业务处理系统的结构示意图之二，本实施例的业务处理系统还可以包括配置服务器2，在配置服务器2中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个业务实例名称与至少一个业务实例路由信息相对应。如实施例一中所说明的，只要获知了业务实例的名称就可以对业务实例进行调用，因此，每个业务实例都会在配置服务器中进行注册，预先配置好业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息。需要说明的是，图中仅示出了n个业务实例路由信息与n个业务实例的名称之间的一一对应关系，实际上在配置服务器所存储的第一对应关系中，n个业务实例路由信息可以对应于与小于n个的业务实例的名称。
通过设置配置服务器2，路由模块111在接收业务请求后，会提取业务请求的URL中所包含的业务实例路由信息，然后访问配置服务器2，根据业务实例路由信息和第一对应关系信息，获取对应的业务实例名称，并通过业务实例名称，调用业务层中的业务实例执行对应的业务处理。
进一步地，如实施例一中所说明的，在调用业务实例执行业务处理所需要业务参数可以包含在URL中或者业务请求的数据包中，而对于一些系统默认参数可以存储在配置服务器中，通过业务实例路由信息来进行获取。具体地，如图3所示，其为本发明实施例二的业务处理系统的结构示意图之二，配置服务器中预先存储有作为系统默认参数的第二业务参数，并存储有第二业务参数与业务实例路由信息之间的第二对应关系信息。需要说明的是，图中仅示出了n个业务实例路由信息与n个第二业务参数之间的一一对应关系，实际上，也可以是n个业务实例路由信息对应小于n个第二业务参数。
基于上述配置服务器的设置，在业务请求需要调用系统默认的第二业务参数的情况下，路由模块可以访问配置服务器，根据业务实例路由信息和第二对应关系信息，获取第二业务参数，并发送给业务实例。此外，如上面实施例一中所说明的，路由模块还会根据情形，从URL中和/或业务请求的数据包中提取第一业务参数，并发送给业务实例。
本实施例中的业务处理系统采用了分层架构，将业务实例统一放在业务层中，而用于查找和调用业务实例的功能放在了路由层中，并且在URL中设置了业务实例路由信息，同时在业务处理系统的内部建立了业务实例路由信与业务实例的对应关系，从而能够通过URL定位到具体的业务实例，便于业务的管理和部署。尤其在进行业务内容更新时，仅涉及与该业务内容对应的业务实例的更新操作，而不会影响到其他的业务实例， 也不会影响到整个业务处理系统的运行。
进一步地，通过设立独立的配置服务器来存储业务实例路由信息与业务实例名称之间的第一对应关系信息，使得路由模块能够直接获取到业务实例名称，从而完成调用。此外，在配置服务器中还存储了第二业务参数与业务实例路由信息之间的第二对应关系，使得路由模块在获取业务实例名称的同时还能获取到与本次业务请求对应的系统默认参数，从而可以在业务实例的调用过程中直接传递给业务实例。
实施例三
本实施例在实施例二的基础上增加了服务层的结构，如图4所示，其为本发明实施例三的业务处理系统的结构示意图之一，本实施例的业务处理服务器还包括服务层10。相应地，业务实例路由信息包括业务类别字段和业务路由字段，业务类别字段标识业务类别，路由层设置有多个路由模块，每个路由模块可以分别对应一个业务类别对应。其中，
举例来说，可以采用如下URL结构：
http：{host}/{app}/{path}？auth[token]
其中，“http”为网路协议部分，“host”为服务器的IP地址和主机名，“auth[token]”为URL的参数部分，而业务实例路由信息由“{app}/{path}”这里两部分构成，其中{app}代表业务类别字段，{path}代表该业务类别下面的具体业务实例的路由字段，即通过{app}字段将所有全部路由实例进行了分类，然后在每个类别下面利用{path}字段建立具体业务实例的路由。
例如：http：//www.test.com/test/pay？auth[token]＝xxxx&。这里的“test”就是业务类别，而“pay”则标识着在“test”大的业务类别下的和支付相关的业务实例的路由信息。
基于上述的业务实例路由信息结构，服务层就可以根据业务类别字段进行业务分发。具体地，如图4所示，服务层10包括分发模块101，用于接收业务请求，并根据业务请求的URL中所包含的业务类别字段将该业务请求分发给对应的路由模块111。相应地，对应的路由模块111，接收到业务请求后，可以再按照实施例二中的方式，访问配置服务器2，根据业务实例路由信息，即根据“{app}/{path}”来查找对应业务实例的名称，并进行后续调用处理。从图在路由层示例性的示出了两个路由模块，在进行业务分发后，两个路由模块分别对应了业务实例1～m和业务实例m+1～n。
另外，服务层还可以包括权限认证模块，用于在进行路由分发之前，对业务请求进 行权限认证，如果业务请求不具备业务调用权限，则直接屏蔽该业务请求或者向该业务请求的发送方返回拒绝应答。此外，服务层还可以包括协议解析模块，用于对业务请求进行协议解析。服务层作为业务处理系统的最上层，服务层需要对多种网路协议进行支持，从而能够接收并向下层转发相应的业务请求，例如，服务层可以至少对HTTP、HTTPS等常规的网路访问协议提供支持。
本实施例通过三层的分层结构来实现业务请求的调用处理，相应地，在业务实例路由信息方面也进行了对应设计，将业务实例路由信息分为能够标识业务大类的业务类别字段和该大类下面的具体业务实例路由的业务路由字段两部分。通过上述的架构设计和URL字段的设计，首先在服务层上将业务处理系统接收到的大量业务请求按照业务大类进行分流，分流后的业务请求再交给路由层曾的路由模块，进行进一步的路由操作，从而定位到具体的业务实例并进行调用，而实际的业务处理则完全由业务层中运行的业务实例来完成。通过上述侧分层处理机制，能够让业务请求快速准确地进行调用，并且便于业务实例的分类管理。
进一步地，为了便于在业务实例更新的过程中，进行平滑的业务实例更新，如图5所示，其为本发明实施例三的业务处理系统的结构示意图之二，在业务层12中可以将业务实例的运行空间划分为第一实例运行空间和第二实例运行空间，在第一实例运行空间中的业务实例能够接受路由模块的调用，在第二实例运行空间中的业务实例不接受路由模块的调用。
相应地，配置服务器2还可以包括监听模块21，业务处理服务器还可以包括业务实例更新模块15。监听模块21，用于监听业务内容的更新，并通知业务实例更新模块15；业务实例更新模块15，用于根据新的业务内容生成新的业务实例，用该新的业务实例替换对应的运行在第一运行空间中的旧的业务实例，并将该旧的业务实例放入第二实例运行空间中，这些旧的业务实例可以在第二实例运行空间中继续进行更新前接收到的业务请求的业务处理，待完成业务处理后，再由系统进行注销。
通过在业务层中设置两个实例运行空间，在进行业务实例的更新时，能够在不影响之前的业务处理的前提下，完成业务实例的更新替换。
实施例四
如图6所示，其为本发明实施例四的业务处理系统的结构示意图之一，本实施例在实施例三的基础上，增加了存储层13，业务处理所需要的业务数据存储在存储层13中， 业务实例121在进行业务处理的过程中，从存储层13中调取所需的业务数据。
通过设计存储层和业务层的结构，将业务处理逻辑封装在业务层执行，而将业务处理中涉及的业务数据放在存储层，从而将业务逻辑和业务数据进行了分离，这样能够更加方便地对业务逻辑或者业务数据进行变更，而不会对整个业务处理系统造成过多的影响。在实际应用中，业务处理系统中，更新较多的是业务处理逻辑，基于上述架构，如果业务内容的更新仅仅涉及业务处理逻辑的更新，那么只要更新业务层中的业务实例即可，而不会影响存储层中的业务数据。
另外，为了更好的解决底层数据存储格式和业务层的数据调用的问题，如图7所示，其为本发明实施例四的业务处理系统的结构示意图之二，本实施例的业务处理系统还可以包括设置在业务层12与存储层13之间的数据接口层14，存储层13的业务数据具有多种数据存储格式，数据接口层用于在业务层12与存储层13之间进行数据格式的转换，并向业务层的业务实例121，提供通用的数据访问接口。
例如，如图7所示，在存储层13中的数据可以采用Oracle数据库系统、Sybase数据库系统或者MS SQL Server等常见的数据系统。数据接口层用于在业务层与存储层之间进行数据格式的转换，并向业务层的业务实例，提供通用的数据访问接口。
通过设置数据接口层，可以彻底地将业务逻辑和业务数据进行分离，在存储层中，可以采用不同的数据存储格式，从而能够兼容各种不同的平台数据等，而数据格式的转换工作，可以交由数据接口层来完成。此外，从业务层的角度来看，业务层中运行的业务实例直接面对数据接口层即可，可以采用统一的数据接口对存储层的数据进行调用，从屏蔽掉了底层数据差异性。
实施例五
本实施例涉及基于上述实施例二至四的业务处理系统的业务处理方法，该业务处理方法在业务处理系统上执行，业务处理系统至少包括业务处理服务器，业务处理服务器包括路由层和业务层，路由层中运行有路由模块，业务层中运行有多个执行业务处理的业务实例，
业务处理方法包括：路由模块接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据业务实例路由信息，调用业务实例路由信息对应的业务实例，对业务请求进行处理，其中，每个业务实例与至少一个业务实例路由信息相对应。
通过这样的调用机制，在进行具体业务调用时，通过业务请求中的URL(统一资源 定位符)信息就能够直接定位到一个具体的业务实例，这样的调用机制使得业务请求到业务实例的调用关系非常清晰，每项业务相对独立，便于业务的管理和部署。
进一步地，业务处理系统还可以包括配置服务器，在配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个业务实例名称与至少一个业务实例路由信息相对应。
在引入配置服务器后，上述的根据业务实例路由信息，调用业务实例路由信息对应的业务实例的操作可以具体为：路由模块访问配置服务器，根据业务实例路由信息和第一对应关系信息，获取对应的业务实例名称；路由模块通过业务实例名称，调用业务实例。
更进一步地，配置服务器中预先存储有作为系统默认参数的第二业务参数，并存储有第二业务参数与业务实例路由信息之间的第二对应关系信息。相应地，该业务处理方法还可以进一步包括：
路由模块访问配置服务器，根据业务实例路由信息和第二对应关系信息，获取第二业务参数，并发送给业务实例；和/或，从URL中和/或业务请求的数据包中提取第一业务参数，并发送给业务实例。
此外，业务处理服务器还可以包括服务层，业务实例路由信息包括业务类别字段和业务路由字段，业务类别字段标识业务类别，路由层设置有多个路由模块，每个业务模块分别对应一个业务类别对应。相应地，业务处理方法还可以包括：服务层接收业务请求，并根据业务请求的URL中所包含的业务类别字段将该业务请求分发给对应的路由模块。
本实施例中，通过三层的分层结构来实现业务请求的调用处理，相应地，在业务实例路由信息方面也进行了对应设计，首先在服务层上将业务处理系统接收到的大量业务请求按照业务大类进行分流，分流后的业务请求再交给路由层曾的路由模块，进行进一步的路由操作，从而定位到具体的业务实例并进行调用，而实际的业务处理则完全由业务层中运行的业务实例来完成。通过上述侧分层处理机制，能够让业务请求快速准确地进行调用，并且便于业务实例的分类管理。
实施例六
本实施例涉及基于上述各实施例的业务处理系统的业务更新方法，业务处理系统至少包括业务处理服务器和配置服务器，
业务处理服务器包括路由层和业务层，路由层中运行有路由模块，业务层中运行有多个执行业务处理的业务实例，
在配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个业务实例名称与至少一个业务实例路由信息相对应，
业务层中可以进一步包括第一实例运行空间和第二实例运行空间，在第一实例运行空间中的业务实例能够接受路由模块的调用，在第二实例运行空间中的业务实例不接受路由模块的调用，
如图8所示，其为本发明实施例六的业务更新方法的流程示意图，本实施例的业务更新方法包括：
步骤201：在配置服务器中，监听业务内容的更新，并通知业务处理服务器，这里所说是业务内容可以是执行具体业务内容的程序代码等。
步骤202：业务处理服务器根据新的业务内容生成新的业务实例，用该新的业务实例替换对应的旧的业务实例。具体地，在该步骤中，新旧业务实例的替换操作可以具体为：用新的业务实例替换对应的运行在第一运行空间中的旧的业务实例，并将该旧的业务实例放入第二实例运行空间中。
本实施例的业务更新方法，仅涉及与该业务内容对应的业务实例的更新操作，而不会影响到其他的业务实例，也不会影响到整个业务处理系统的运行。并且，通过旧的业务实例置于不接受路由模块调用的第二实例运行空间继续进行业务处理，而将新的业务实例置于能够接受路由模块的调用的第一实例运行空间中，使得新旧业务实例能够并存，实现平滑地进行业务实例更新。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (17)

  1. 一种业务更新方法，其特征在于，所述业务更新方法在业务处理系统上执行，所述业务处理系统包括业务处理服务器和配置服务器，
    所述业务处理服务器包括路由层和业务层，所述路由层中运行有路由模块，所述业务层中运行有多个执行业务处理的业务实例，
    在所述配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个所述业务实例名称与至少一个业务实例路由信息相对应，
    业务更新方法包括：
    在所述配置服务器中，监听业务内容的更新，并通知所述业务处理服务器；
    所述业务处理服务器根据新的业务内容生成新的业务实例，用该新的业务实例替换对应的旧的业务实例。
  2. 根据权利要求1所述的业务更新方法，其特征在于，
    所述业务层中包括第一实例运行空间和第二实例运行空间，在所述第一实例运行空间中的业务实例能够接受所述路由模块的调用，在所述第二实例运行空间中的业务实例不接受所述路由模块的调用，
    所述用该新的业务实例替换对应的旧的业务实例包括：
    用该新的业务实例替换对应的运行在所述第一实例运行空间中的旧的业务实例，并将该旧的业务实例放入第二实例运行空间中。
  3. 一种业务处理方法，其特征在于，所述业务处理方法在业务处理系统上执行，所述业务处理系统包括业务处理服务器，所述业务处理服务器包括路由层和业务层，所述路由层中运行有路由模块，所述业务层中运行有多个执行业务处理的业务实例，
    所述业务处理方法包括：
    所述路由模块接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例，对所述业务请求进行处理，其中，每个所述业务实例与至少一个业务实例路由信息相对应。
  4. 根据权利要求3所述的业务处理方法，其特征在于，所述业务处理系统还包括配置服务器，在所述配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个所述业务实例名称与至少一个业务实例路由信息相对应，
    所述根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例包 括：
    所述路由模块访问所述配置服务器，根据所述业务实例路由信息和所述第一对应关系信息，获取对应的业务实例名称；
    通过所述业务实例名称，调用所述业务实例。
  5. 根据权利要求4所述的业务处理方法，其特征在于，还包括：
    所述配置服务器中预先存储有作为系统默认参数的第二业务参数，并存储有所述第二业务参数与所述业务实例路由信息之间的第二对应关系信息，
    所述路由模块访问所述配置服务器，根据所述业务实例路由信息和所述第二对应关系信息，获取所述第二业务参数，并发送给所述业务实例，和/或
    从所述URL中和/或所述业务请求的数据包中提取第一业务参数，并发送给所述业务实例。
  6. 根据权利要求4所述的业务处理方法，其特征在于，所述业务处理服务器还包括服务层，所述业务实例路由信息包括业务类别字段和业务路由字段，所述业务类别字段标识业务类别，所述路由层设置有多个路由模块，每个业务模块分别对应一个业务类别对应，
    所述业务处理方法还包括：
    所述服务层接收所述业务请求，并根据所述业务请求的URL中所包含的业务类别字段将该业务请求分发给对应的路由模块。
  7. 一种业务处理系统，其特征在于，包括业务处理服务器，所述业务处理服务器中包括路由层和业务层，在所述路由层中运行有路由模块，所述业务层中运行有多个业务实例，
    所述路由模块用于接收业务请求，提取业务请求的URL中所包含的业务实例路由信息，并根据所述业务实例路由信息，对与所述业务实例路由信息对应的业务实例进行调用，其中，每个所述业务实例与至少一个业务实例路由信息相对应；
    所述业务实例用于执行所述业务请求对应的业务处理。
  8. 根据权利要求7所述的业务处理系统，其特征在于，所述业务处理系统还包括配置服务器，在所述配置服务器中存储有业务实例路由信息与各个业务实例的业务实例名称之间的第一对应关系信息，每个所述业务实例名称与至少一个业务实例路由信息相对应，
    在所述路由模块中，根据所述业务实例路由信息，对与所述业务实例路由信息对应 的业务实例进行调用的处理包括：访问所述配置服务器，根据所述业务实例路由信息和所述第一对应关系信息，获取对应的业务实例名称，并通过所述业务实例名称，调用所述业务实例。
  9. 根据权利要求8所述的业务处理系统，其特征在于，
    所述配置服务器中预先存储有作为系统默认参数的第二业务参数，并存储有所述第二业务参数与所述业务实例路由信息之间的第二对应关系信息，
    所述路由模块还用于访问所述配置服务器，根据所述业务实例路由信息和所述第二对应关系信息，获取所述第二业务参数，并发送给所述业务实例，和/或
    从所述URL中和/或所述业务请求的数据包中提取第一业务参数，并发送给所述业务实例。
  10. 根据权利要求8所述的业务处理系统，其特征在于，
    所述业务处理服务器还包括服务层，所述业务实例路由信息包括业务类别字段和业务路由字段，所述业务类别字段标识业务类别，所述路由层设置有多个路由模块，每个路由模块分别对应一个业务类别对应，
    所述服务层包括分发模块，用于接收所述业务请求，并根据所述业务请求的URL中所包含的业务类别字段将该业务请求分发给对应的路由模块。
  11. 根据权利要求8所述的业务处理系统，其特征在于，
    所述业务层中包括第一实例运行空间和第二实例运行空间，在所述第一实例运行空间中的业务实例能够接受所述路由模块的调用，在所述第二实例运行空间中的业务实例不接受所述路由模块的调用。
  12. 根据权利要求11所述的业务处理系统，其特征在于，
    所述配置服务器还包括监听模块，所述业务处理服务器还包括业务实例更新模块，
    所述监听模块，用于监听业务内容代码的更新，并通知所述业务实例更新模块；
    所述业务实例更新模块，用于根据新的业务内容代码生成新的业务实例，用该新的业务实例替换对应的运行在所述第一实例运行空间中的旧的业务实例，并将该旧的业务实例放入第二实例运行空间中。
  13. 根据权利要求7至12任一所述的业务处理系统，其特征在于，
    所述业务处理服务器还包括存储层，所述业务处理所需要的业务数据存储在所述存储层中，所述业务实例在进行业务处理的过程中，从所述存储层中调取所需的业务数据。
  14. 根据权利要求13所述的业务处理系统，其特征在于，所述业务处理服务器还 包括设置在所述业务层与所述存储层之间的数据接口层，所述存储层的业务数据具有多种数据存储格式，所述数据接口层用于在所述业务层与所述存储层之间进行数据格式的转换，并向所述业务层的业务实例，提供通用的数据访问接口。
  15. 一种业务处理方法，其特征在于，包括：
    接收业务请求；
    提取业务请求的URL中所包含的业务实例路由信息；
    根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例，对所述业务请求进行处理，其中，每个所述业务实例与至少一个业务实例路由信息相对应。
  16. 根据权利要求15所述的业务处理方法，其特征在于，
    所述根据所述业务实例路由信息，调用所述业务实例路由信息对应的业务实例包括：
    根据所述业务实例路由信息获取对应的业务实例名称，其中，每个所述业务实例名称与至少一个业务实例路由信息相对应；
    通过所述业务实例名称，调用所述业务实例。
  17. 根据权利要求16所述的业务处理方法，其特征在于，还包括：
    从所述URL中和/或所述业务请求的数据包中提取第一业务参数，并发送给所述业务实例；和/或
    根据所述业务实例路由信息获取预先存储的作为系统默认参数的第二业务参数，并发送给所述业务实例。
PCT/CN2017/077996 2016-04-06 2017-03-24 业务处理系统、业务处理方法以及业务更新方法 Ceased WO2017173928A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/153,616 US20190042276A1 (en) 2016-04-06 2018-10-05 Service processing system, service processing method, and service update method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610211061.1A CN107277086B (zh) 2016-04-06 2016-04-06 业务处理系统、业务处理方法以及业务更新方法
CN201610211061.1 2016-04-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/153,616 Continuation US20190042276A1 (en) 2016-04-06 2018-10-05 Service processing system, service processing method, and service update method

Publications (1)

Publication Number Publication Date
WO2017173928A1 true WO2017173928A1 (zh) 2017-10-12

Family

ID=60000841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077996 Ceased WO2017173928A1 (zh) 2016-04-06 2017-03-24 业务处理系统、业务处理方法以及业务更新方法

Country Status (4)

Country Link
US (1) US20190042276A1 (zh)
CN (1) CN107277086B (zh)
TW (1) TWI751139B (zh)
WO (1) WO2017173928A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10437645B2 (en) * 2017-07-14 2019-10-08 Sap Se Scheduling of micro-service instances
CN108234653A (zh) * 2018-01-03 2018-06-29 马上消费金融股份有限公司 一种处理业务请求的方法及装置
CN110740046B (zh) * 2018-07-18 2023-08-08 北京京东尚科信息技术有限公司 分析服务契约的方法和装置
CN109167811B (zh) 2018-07-27 2020-05-05 阿里巴巴集团控股有限公司 一种基于区块链的跨链数据访问方法和装置
CN109145205B (zh) 2018-07-27 2020-09-01 阿里巴巴集团控股有限公司 一种基于区块链的跨链数据操作方法和装置
CN113507416B (zh) * 2018-10-27 2022-05-10 华为技术有限公司 报文处理方法、相关设备及计算机存储介质
CN110505269A (zh) * 2019-06-21 2019-11-26 广州虎牙科技有限公司 业务处理系统、业务处理方法以及服务器
CN110311867A (zh) * 2019-07-02 2019-10-08 江苏满运软件科技有限公司 应用模块化管理方法、装置、电子设备、存储介质
CN110825796B (zh) * 2019-10-09 2021-01-19 车轮互联科技(上海)股份有限公司 数据获取的方法、装置及系统
CN110995829B (zh) * 2019-11-29 2022-07-22 广州市百果园信息技术有限公司 实例调用方法、装置及计算机存储介质
CN112887390B (zh) * 2021-01-20 2023-02-17 上海易校信息科技有限公司 一种网络请求方法
CN114816589B (zh) * 2022-04-14 2025-11-28 上海众源网络有限公司 业务处理方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101136927A (zh) * 2007-10-15 2008-03-05 北京千家悦网络科技有限公司 一种网络论坛实现方法和系统
US20110270691A1 (en) * 2008-03-21 2011-11-03 Nhn Business Platform Corporation Method and system for providing url possible new advertising
CN103399754A (zh) * 2013-08-19 2013-11-20 银联商务有限公司 软件架构
CN105022630A (zh) * 2015-06-30 2015-11-04 中标软件有限公司 一种组件管理系统及组件管理方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2390348A1 (en) * 2002-06-10 2003-12-10 Ibm Canada Limited-Ibm Canada Limitee Systems, methods and computer programs for implementing and accessing webservices
CN201109937Y (zh) * 2007-10-30 2008-09-03 李圣龙 防臭大便器
CN101272337B (zh) * 2007-12-27 2010-08-25 华为技术有限公司 业务数据处理方法与业务数据处理系统
US8327019B2 (en) * 2009-08-18 2012-12-04 Verisign, Inc. Method and system for intelligent routing of requests over EPP
CN104144149A (zh) * 2013-05-10 2014-11-12 中国电信股份有限公司 传感物联网数据的传输处理方法、系统和网关
CN103605551A (zh) * 2013-11-28 2014-02-26 金蝶软件（中国）有限公司 一种基于ios程序的插件更新方法、系统及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101136927A (zh) * 2007-10-15 2008-03-05 北京千家悦网络科技有限公司 一种网络论坛实现方法和系统
US20110270691A1 (en) * 2008-03-21 2011-11-03 Nhn Business Platform Corporation Method and system for providing url possible new advertising
CN103399754A (zh) * 2013-08-19 2013-11-20 银联商务有限公司 软件架构
CN105022630A (zh) * 2015-06-30 2015-11-04 中标软件有限公司 一种组件管理系统及组件管理方法

Also Published As

Publication number Publication date
TWI751139B (zh) 2022-01-01
TW201737110A (zh) 2017-10-16
US20190042276A1 (en) 2019-02-07
CN107277086B (zh) 2020-08-14
CN107277086A (zh) 2017-10-20

Similar Documents

Publication Publication Date Title
CN107277086B (zh) 业务处理系统、业务处理方法以及业务更新方法
US11394805B1 (en) Automatic discovery of API information
EP3695563B1 (en) Apparatus, method, and computing device for selectively granting permissions to group-based objects in a group-based communication system
US11082226B2 (en) Zero-knowledge identity verification in a distributed computing system
US9672053B2 (en) Service request processing
US20210385087A1 (en) Zero-knowledge identity verification in a distributed computing system
CN109995713B (zh) 一种微服务框架中的服务处理方法及相关设备
US11394794B2 (en) Fast ingestion of records in a database using data locality and queuing
US9069984B2 (en) On-demand authorization management
US10148527B2 (en) Dynamic network component placement
US8813225B1 (en) Provider-arbitrated mandatory access control policies in cloud computing environments
US20110302277A1 (en) Methods and apparatus for web-based migration of data in a multi-tenant database system
US8683545B2 (en) Federating policies from multiple policy providers
US12164676B2 (en) Enabling an action based on a permission identifier for real-time identity resolution in a distributed system
US11533538B2 (en) Streaming event content based filtering
US9706007B2 (en) System and method for querying disparate data sources in real time
US11876875B2 (en) Scalable fine-grained resource count metrics for cloud-based data catalog service
WO2016131171A1 (zh) 一种针对vnf包进行操作的方法及装置
CN114401319B (zh) 一种请求处理方法、装置、服务器及存储介质
CN112105026B (zh) 一种授权控制的方法、装置以及存储介质
CN101764791B (zh) 一种业务链中的用户身份验证方法、设备及系统
CN107306247A (zh) 资源访问控制方法及装置
CN106789965A (zh) 一种物联网数据交换方法及系统
CN108833357A (zh) 信息查看方法及装置
CN106776079A (zh) 一种管理用户数据的方法及系统

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17778592

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17778592

Country of ref document: EP

Kind code of ref document: A1