WO2018113601A1 - 一种业务处理方法及装置 - Google Patents
一种业务处理方法及装置 Download PDFInfo
- Publication number
- WO2018113601A1 WO2018113601A1 PCT/CN2017/116509 CN2017116509W WO2018113601A1 WO 2018113601 A1 WO2018113601 A1 WO 2018113601A1 CN 2017116509 W CN2017116509 W CN 2017116509W WO 2018113601 A1 WO2018113601 A1 WO 2018113601A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- server
- client
- category
- service result
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- 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
-
- 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/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the present application relates to the field of computer technologies, and in particular, to a service processing method and apparatus.
- Online systems can provide users with rich business services with the support of their back-end business systems. Some of these services may require different business systems to work together.
- the service request initiated by the user through a client such as a browser or an application (Application, APP)
- the process of processing the foregoing service request may be specifically: according to the order of the business process,
- the business system that processes the business request will generate the corresponding processing result (which can be called the intermediate result), and return it to the client.
- the client redirects to the next business system in the business process according to the intermediate result, and initiates the request.
- the next business system is post-processed, and so on, until the entire business process is completed.
- the service request is first processed by the service system A to generate an intermediate result a.
- the service system A returns the intermediate result a to the client, and the client is redirected to the service system B based on the intermediate result a.
- the business system B will process the request, generate the business result b, and return to the client.
- each service system interacts with the client through the Internet, and the stability of the network environment of the Internet is poor.
- the network delay may occur due to the influence of the network environment, causing the client to The process of sending an intermediate request to the next service system takes a long time; in addition, in the above manner, the service system only performs the corresponding processing after receiving the request from the client, and the online system usually Faced with a large number of user accesses, the workload of each business system is high, resulting in a request waiting delay in the processing queue of the business system.
- there may be a certain delay in the transmission phase and processing phase of the request which will inevitably result in a longer waiting time for the client, which makes the timeliness of the business process less.
- the embodiment of the present application provides a service processing method and device, which are used to solve the problem of poor timeliness of the existing service processing process.
- the second server receives the first service result sent by the first server, where the first service result is generated after the first server processes the first service request sent by the client;
- the second server After receiving the second service request sent by the client, the second server feeds back the generated second service result to the client.
- the first server receives the first service request sent by the client
- Transmitting the first service result to the second server so that the second server determines a category corresponding to the first service result, and generates a second that matches the category according to the first service result and the category.
- the service result and after the second server receives the second service request generated by the client according to the first service result, sends the generated second service result to the client.
- the feedback module when the second server receives the second service request sent by the client, feeds back the generated second service result to the client.
- the sending module the first service result is sent to the client, and the second server, so that the second server determines a category corresponding to the first service result, according to the first service result and category,
- the second service result is generated, and after the second server receives the second service request generated by the client according to the first service result, the generated second service result is sent to the client.
- the embodiment of the present application provides a service processing method and device.
- the first server receives the first service request sent by the client, the first server processes the first service request and generates a corresponding first service.
- the first server sends the first service result to the second server according to the service process, and the second server determines the first service result.
- the category in which the second server can process the first service result, and generate a second service result that matches the category in advance.
- the second server can generate the second service result before receiving the second service request sent by the client, and after the second server receives the second request actually sent by the client,
- the second service result that has been generated can be directly returned to the client, and the generated second service result is consistent with the service type of the first service result.
- the second server can pre-generate the second service result according to the first service result before receiving the second service request of the client, thereby effectively saving the waiting time of the client. It also improves the timeliness of processing business requests.
- FIG. 1b is a process of processing a service based on a second server side according to an embodiment of the present application
- FIG. 2 is a service processing procedure based on a first server side according to an embodiment of the present application
- FIG. 3 is a schematic diagram of a service processing procedure in an application example provided by an embodiment of the present application.
- FIG. 4 is a schematic structural diagram of a service processing apparatus based on a second server side according to an embodiment of the present application
- FIG. 5 is a schematic structural diagram of a service processing apparatus based on a first server side according to an embodiment of the present disclosure.
- the client when a user obtains a service service that needs to be completed by multiple service systems from a network system through a client, the client usually needs to receive intermediate service results returned by different service systems, and performs redirection based on the intermediate service result. , the next business system issues a request until the completion of the complete business process, but in the process, the client is vulnerable to the network environment when sending a request to the business system, resulting in transmission delay, and the business system can only After receiving the service request sent by the client, the processing will be processed.
- the service service of the online system since the user accesses the service service from the online system through the client, the service service of the online system often needs to be completed by multiple service systems, so the client will follow the business process and target different business systems. Different service requests are initiated, but it can be considered that different service requests initiated by the client are to complete the same service.
- the service processing method in the embodiment of the present application is based on the architecture shown in FIG. 1a, and can be seen in FIG. 1.
- the architecture includes a service client (hereinafter referred to as a client) used by a user, and a first server.
- the second server wherein the client may be a browser running in the terminal, an APP application, etc., the first server and the second server have different service functions, and the first server and the second server may specifically be
- the two adjacent service servers in the business process the second server may be a service server that is processed in the business process after the first server, for example, assume that three existing service servers A, B, and C are The service server needs to be completed in the order of the service servers A to B and then to C.
- the first server may be the service server A, and the second server may be the service server B;
- the first server may be the service server B, and the second server may be the service server C.
- the first server and the second server in the present application are not limited to the scenario of two servers.
- the service processing method in the present application is described below in conjunction with the architecture shown in FIG. 1a.
- the service processing procedure shown in FIG. 1b includes the following steps:
- Step S101 The second server receives the first service result sent by the first server.
- the first service result is generated after the first server processes the first service request sent by the client.
- a user when a user obtains a service service by using a client, it usually needs to send a service request to the corresponding service server. For example, after the user places an order for an item, the client sends the message to the next server.
- the order server is the first server, and the order request is the first service request.
- the first service request may be a service request received by the first server, and the first service request may be a service request sent by the client according to the operation instruction of the user, or the client may receive the business process.
- the first business result can be regarded as an intermediate result generated by the first server after corresponding processing of the first service request.
- the process of the client sending the second service request to the second server may be delayed by the network environment, and the second server may also generate the second service request and process the second service request.
- the first server sends the first service result to the client.
- the first server sends the first service result to the client.
- the first service result is directly sent to the second server, and then the second server can process in advance according to the first service result.
- the category corresponding to the first service result may be considered as the category corresponding to the first server, and it should be understood that, in actual applications, for the first server of different service providers, the category (such as There are usually differences in the types of services provided and the categories of the service providers themselves. Accordingly, there are different requirements for the categories of the second business results.
- the telecom operator at this time, the first server is the telecom carrier server
- the bank at this time, the first server is the bank server
- the business result is usually related to the telecommunication service
- the first service result generated by the bank server is usually related to the financial service. It can be understood that the categories of the second service result generated by the above two service providers should also be different.
- S103 Generate, according to the category and the first service result, a second service result that matches the category.
- the second server After the second server receives the first service result, it can process in advance to generate a second service result that matches the category.
- the second server After receiving the second service request, the second server can directly feed back the second result generated in advance to the client, thereby reducing or avoiding the waiting time of the client.
- the first server After the first server receives the first service request sent by the client, the first server processes the first service request and generates a corresponding first service result. At this time, the first server except the first service The result is returned to the client, and the first service result is sent to the second server according to the business process, and the second server determines the category corresponding to the first service result, so that the second server can A business result is processed to generate a second business result that matches the category in advance. It is the manner in which the second server can generate the second service result before receiving the second service request sent by the client, and after the second server receives the second request actually sent by the client, The second service result that has been generated can be directly returned to the client, and the generated second service result is consistent with the service type of the first service result. Obviously, the second server can pre-generate the second service result according to the first service result before receiving the second service request of the client, thereby effectively saving the waiting time of the client. It also improves the timeliness of processing business requests.
- a user uses a client of a product website to purchase an item on the product website. It can be considered that the user's purchase operation for a certain product through the client involves placing an order and paying two services, and the payment service provider (eg, a payment platform) can provide a payment service in the process (ie, the order service is performed by the The order server in the background of the product website is completed, and the payment service is completed by the payment server in the background of the payment platform).
- the first service request is an order request
- the first server includes an order server
- the first service result includes order information
- the second server includes a payment server
- the second service result includes a payment interface or an abnormal page.
- determining the category corresponding to the first service result includes: determining a category identifier of the order server included in the order data.
- the category identifier actually reflects the category identifier of the first server.
- the category identifier may include: a name of the service provider to which the first server belongs, industry category information, and The name of a server itself, the device number, and the like, are not intended to limit the application.
- the generated payment pages are usually different, so the payment server Different payment page templates are usually stored to correspond to different order servers, and the order data sent by the order server also includes the category identifier of the order server, so that the corresponding payment page template can be determined.
- the order data to be rendered may also be different.
- the payment page For example, for the payment page of a product website, the payment page needs to display the user's order number, payment amount, mailing address and the like, and
- the payment page of the mobile phone card recharge the payment page needs to display the data of the single number, the mobile phone number to be recharged, the amount and the like.
- the order data to be rendered is not the same.
- the process of the payment server determining the payment status according to the order data may be implemented based on an account pre-registered by the user, and the method is divided into two cases:
- the account registered by the user at the service provider is generally used for the order server and the payment server.
- the payment server has the right to query the user's account balance, thereby Determine if this payment can be successful.
- the order server and the payment server belong to different service providers respectively. Then, it can be understood that the accounts registered by the user at the two service providers should be related to each other, so that the payment server still has the right to query the user to place the server. The balance of the account registered in the account, and based on this, judge whether the payment can be successful.
- the method further comprises: deleting the mark of the order data, rendering and constructing an abnormal page.
- the data that is successfully rendered may also be marked for subsequent optimization of the system, where It is not described in detail.
- the order data in the embodiment of the present application further includes a client identifier
- the method further includes: establishing a correspondence between the client identifier and the payment page or the abnormal page.
- the feedback of the generated second service result to the client includes: determining a client identifier in the second service request, and generating a payment page corresponding to the client identifier or The exception page is fed back to the client.
- the payment server After the payment server receives the payment request sent by the client, the payment page or the abnormal page that is rendered and constructed in advance can be fed back to the client.
- Step S201 The first server receives the first service request sent by the client.
- Step S202 Generate, according to the first service request, a first service result corresponding to the first server self category.
- the first server After receiving the first service request, the first server processes the first service request to generate a corresponding service result, that is, the first service result, where the first service result is usually an intermediate service result.
- the first service request may carry the identifier information of the client
- the first service result generated by the first server may also include the identifier information of the client.
- Step S301 The user issues an order operation instruction to the client.
- Step S302 The client sends an order request to the single server according to the order operation instruction.
- Step S303 The ordering server processes the received order request to generate order information.
- Step S305 The ordering server sends the order information to the client. So that the client performs step S307.
- Step S306 The payment server determines a corresponding payment page template according to the order information, and further generates a payment page.
- Step S307 The client redirects to the payment server according to the order information, and issues a payment page request to the payment server.
- Step S308 The payment server returns a payment page to the client.
- the order server in the actual payment scenario, once the order server generates the order information, it will immediately send it to the payment server for processing to generate a corresponding payment page, then when the client sends a payment page to the payment server. After the request, the payment server can immediately return the generated payment page to the client. Obviously, such an approach will effectively reduce the time the client waits to generate a payment page, and further allows the user to browse to the payment page more quickly to complete the payment service in the payment page.
- the present application further provides an embodiment of the service processing apparatus, as shown in FIG. 4 .
- the service processing device of FIG. 4, the device may be disposed in a second server, the device comprising:
- the receiving module 401 is configured to receive a first service result sent by the first server, where the first service result is generated by the first server processing the first service request sent by the client;
- the category determining module 402 is configured to determine a category corresponding to the first service result
- the generating module 4033 is configured to generate, according to the category and the first service result, a second service result that matches the category;
- the feedback module 404 when the second server receives the second service request sent by the client, feeds back the generated second service result to the client.
- the first service request is an order request; the first server includes an order server; the first service result includes order data; and the second server includes a payment.
- the order data includes a category identifier of the order server; the category determining module 402 determines a category identifier of the order server included in the order data; and the generating module 403 is configured according to the pre-established category identifier.
- the page template determining a page template corresponding to the order data, marking, according to the determined interface template, order data matching the page template in the order data, and rendering according to the marked order data Build a payment page.
- the generating module 403 determines a payment status according to the order data, and when it is determined that the payment status is payable, renders and constructs a payment page according to the marked order data. .
- the generating module 403 determines that the payment status is not payable, the mark of the order data is deleted, and an abnormal page is rendered and constructed. .
- the order data carries a client identifier
- the device further includes: a relationship establishing module 405, configured to establish a correspondence between the client identifier and the payment page or the abnormal page.
- the feedback module 404 determines the client identifier in the second service request, and feeds the generated payment page or the abnormal page corresponding to the client identifier to the client.
- the application further provides a service processing device.
- the device may be disposed in the first server, including:
- the receiving module 501 receives a first service request sent by the client.
- the generating module 502 is configured to generate, according to the first service request, a first service result corresponding to the first server self category;
- the sending module 503 is configured to send the first service result to the client and the second server, so that the second server determines a category corresponding to the first service result, according to the first service result and category
- the second service result is generated, and after the second server receives the second service request generated by the client according to the first service result, the generated second service result is sent to the client.
- HDL Hardware Description Language
- the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
- computer readable program code eg, software or firmware
- examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
- the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
- Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
- a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
- the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
- a typical implementation device is a computer.
- the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
- RAM random access memory
- ROM read only memory
- Memory is an example of a computer readable medium.
- Computer readable media includes both permanent and non-persistent, removable and non-removable media.
- Information storage can be implemented by any method or technology.
- the information can be computer readable instructions, data structures, modules of programs, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
- computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
- program modules include routines, programs, objects, components, data structures, and the like that perform particular transactions or implement particular abstract data types.
- the present application can also be practiced in distributed computing environments where transactions are performed by remote processing devices that are connected through a communication network.
- program modules can be located in both local and remote computer storage media including storage devices.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Computer Networks & Wireless Communication (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims (14)
- 一种业务处理方法,其特征在于,包括:第二服务器接收第一服务器发送的第一业务结果,其中,所述第一业务结果是所述第一服务器针对客户端发送的第一业务请求进行处理后生成的;确定所述第一业务结果对应的类别;根据所述类别以及所述第一业务结果,生成与该类别相匹配的第二业务结果;当所述第二服务器接收到所述客户端发送的第二业务请求后,将已生成的第二业务结果反馈给所述客户端。
- 如权利要求1所述的方法,其特征在于,所述第一业务请求为下单请求;所述第一服务器包括下单服务器;所述第一业务结果包括订单数据;所述第二服务器包括支付服务器;所述第二业务结果包括支付页面或异常页面。
- 如权利要求2所述的方法,其特征在于,所述订单数据中包含下单服务器的类别标识;确定所述第一业务结果对应的类别,具体包括:确定所述订单数据中包含的下单服务器的类别标识;根据所述类别以及所述第一业务结果,生成与该类别相匹配的第二业务结果,具体包括:根据预先建立的类别标识与页面模板的对应关系,确定所述订单数据所对应的页面模板;根据确定出的所述页面模板,在所述订单数据中标记匹配于该页面模板的订单数据;根据标记的订单数据渲染并构建支付页面。
- 如权利要求3所述的方法,其特征在于,根据标记的订单数据渲染并构建支付页面,具体包括:根据所述订单数据判断支付状态;当判断出所述支付状态为可进行支付时,则根据标记的订单数据渲染并构建支付页面。
- 如权利要求4所述的方法,其特征在于,当判断出所述支付状态为不可进行支付时,则所述方法还包括:删除对所述订单数据的标记;渲染并构建异常页面。
- 如权利要求4或5所述的方法,其特征在于,所述订单数据中携带有客户端标识;所述方法还包括:建立所述客户端标识与所述支付页面或异常页面之间的对应关系;将已生成的第二业务结果反馈给所述客户端,具体包括:确定所述第二业务请求中的客户端标识;将已生成的且与该客户端标识对应的支付页面或异常页面反馈给所述客户端。
- 一种业务处理方法,其特征在于,包括:第一服务器接收客户端发送的第一业务请求;根据所述第一业务请求,生成对应于该第一服务器自身类别的第一业务结果;将所述第一业务结果发送给所述第二服务器,以使得所述第二服务器确定所述第一业务结果对应的类别,根据第一业务结果及类别,生成与该类别相匹配的第二业务结果,并当该第二服务器接收到客户端根据所述第一业务结果生成的第二业务请求后,将已生成的所述第二业务结果发送给客户端。
- 一种业务处理装置,其特征在于,包括:接收模块,接收第一服务器发送的第一业务结果,其中,所述第一业务结果是所述第一服务器针对客户端发送的第一业务请求进行处理后生成的;类别确定模块,确定所述第一业务结果对应的类别;生成模块,根据所述类别以及所述第一业务结果,生成与该类别相匹配的第二业务结果;反馈模块,当所述第二服务器接收到所述客户端发送的第二业务请求后,将已生成的第二业务结果反馈给所述客户端。
- 如权利要求8所述的装置,其特征在于,所述第一业务请求为下单请求;所述第一服务器包括下单服务器;所述第一业务结果包括订单数据;所述第二服务器包括支付服务器;所述第二业务结果包括支付界面或异常页面。
- 如权利要求9所述的装置,其特征在于,所述订单数据中包含下单服务器的类别标识;所述类别确定模块,确定所述订单数据中包含的下单服务器的类别标识;所述生成模块,根据预先建立的类别标识与页面模板的对应关系,确定所述订单数据所对应的页面模板,根据确定出的所述页面模板,在所述订单数据中标记匹配于该页面模板的订单数据,根据标记的订单数据渲染并构建支付页面。
- 如权利要求10所述的装置,其特征在于,所述生成模块,根据所述订单数据判断支付状态,当判断出所述支付状态为可进行支付时,则根据标记的订单数据渲染并构建支付页面。
- 如权利要求11所述的装置,其特征在于,当所述生成模块判断出所述支付状态为不可进行支付时,删除对所述订单数据的标记,渲染并构建异常页面。
- 如权利要求11或12所述的装置,其特征在于,所述订单数据中携带有客户端标识;所述装置还包括:关系建立模块,建立所述客户端标识与所述支付页面或异常页面之间的对应关系;所述反馈模块,确定所述第二业务请求中的客户端标识,将已生成的且与该客户端标识对应的支付页面或异常页面反馈给所述客户端。
- 一种业务处理装置,其特征在于,包括:接收模块,接收客户端发送的第一业务请求;生成模块,根据所述第一业务请求,生成对应于该第一服务器自身类别的第一业务结果;发送模块,将所述第一业务结果发送给所述客户端、以及第二服务器,以使得所述第二服务器确定所述第一业务结果对应的类别,根据所述第一业务结果及类别,生成第二业务结果,并当该第二服务器接收到客户端根据所述第一业务结果生成的第二业务请求后,将已生成的所述第二业务结果发送给客户端。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020197017251A KR102246394B1 (ko) | 2016-12-21 | 2017-12-15 | 서비스 처리 방법 및 장치 |
JP2019534167A JP7036826B2 (ja) | 2016-12-21 | 2017-12-15 | サービス処理方法および装置 |
MYPI2019002979A MY186646A (en) | 2016-12-21 | 2017-12-15 | Service processing method and apparatus |
EP17882785.3A EP3534585A4 (en) | 2016-12-21 | 2017-12-15 | SERVICE PROCESSING METHOD AND APPARATUS |
US16/421,188 US11132666B2 (en) | 2016-12-21 | 2019-05-23 | Service processing method and apparatus |
PH12019501204A PH12019501204A1 (en) | 2016-12-21 | 2019-05-30 | Service processing method and apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611195605.6 | 2016-12-21 | ||
CN201611195605.6A CN107070858B (zh) | 2016-12-21 | 2016-12-21 | 一种业务处理方法及装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/421,188 Continuation US11132666B2 (en) | 2016-12-21 | 2019-05-23 | Service processing method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018113601A1 true WO2018113601A1 (zh) | 2018-06-28 |
Family
ID=59619421
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/116509 WO2018113601A1 (zh) | 2016-12-21 | 2017-12-15 | 一种业务处理方法及装置 |
Country Status (9)
Country | Link |
---|---|
US (1) | US11132666B2 (zh) |
EP (1) | EP3534585A4 (zh) |
JP (1) | JP7036826B2 (zh) |
KR (1) | KR102246394B1 (zh) |
CN (1) | CN107070858B (zh) |
MY (1) | MY186646A (zh) |
PH (1) | PH12019501204A1 (zh) |
TW (1) | TWI737818B (zh) |
WO (1) | WO2018113601A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112561650A (zh) * | 2020-12-17 | 2021-03-26 | 深圳希施玛数据科技有限公司 | 一种订单服务请求的处理*** |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107070858B (zh) | 2016-12-21 | 2021-09-21 | 创新先进技术有限公司 | 一种业务处理方法及装置 |
CN109450702B (zh) * | 2018-12-10 | 2022-05-24 | 京信网络***股份有限公司 | 一种数据处理方法及装置 |
CN111582902B (zh) * | 2019-02-18 | 2023-07-21 | 阿里巴巴(北京)软件服务有限公司 | 数据处理方法、业务处理方法及装置 |
CN110263816B (zh) * | 2019-05-28 | 2024-01-19 | 创新先进技术有限公司 | 一种企业的分类方法以及装置 |
CN110413421B (zh) * | 2019-06-28 | 2024-01-30 | 创新先进技术有限公司 | 业务数据处理方法和装置、交易数据处理方法和装置 |
CN112311838B (zh) * | 2019-08-02 | 2022-07-05 | 腾讯科技(深圳)有限公司 | 业务异步交互方法及装置 |
CN111192113A (zh) * | 2019-12-30 | 2020-05-22 | 广州酷狗计算机科技有限公司 | 订单处理方法、装置、设备及存储介质 |
CN111240866B (zh) * | 2020-01-14 | 2023-06-30 | 华瑞新智科技(北京)有限公司 | 一种业务数据处理方法及装置 |
CN111880931A (zh) * | 2020-07-22 | 2020-11-03 | 北京三快在线科技有限公司 | 业务执行***、应用于业务执行***的业务执行方法 |
CN111930535B (zh) * | 2020-07-31 | 2023-08-29 | 中国工商银行股份有限公司 | 一种应用功能调用方法、装置、计算机设备及存储介质 |
CN112181928B (zh) * | 2020-09-03 | 2024-02-23 | 北京三快在线科技有限公司 | 一种业务执行的方法、装置及*** |
CN114095574B (zh) * | 2022-01-20 | 2022-04-29 | 恒生电子股份有限公司 | 数据处理方法、装置、电子设备及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102546165A (zh) * | 2010-12-31 | 2012-07-04 | ***股份有限公司 | 动态url生成器、生成方法、基于动态url的认证***和方法 |
CN103164790A (zh) * | 2011-12-09 | 2013-06-19 | 腾讯科技(深圳)有限公司 | 网络支付***及其数据处理方法 |
US9390412B2 (en) * | 2012-10-16 | 2016-07-12 | Visa International Service Association | Dynamic point of sale system integrated with reader device |
CN107070858A (zh) * | 2016-12-21 | 2017-08-18 | 阿里巴巴集团控股有限公司 | 一种业务处理方法及装置 |
CN107295052A (zh) * | 2016-04-11 | 2017-10-24 | 阿里巴巴集团控股有限公司 | 一种业务处理方法及装置 |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001344550A (ja) * | 2000-06-02 | 2001-12-14 | Nec Informatec Systems Ltd | 電子決済方法及びシステム並びに電子決済用プログラムを記憶した記憶媒体 |
KR100376246B1 (ko) * | 2000-06-23 | 2003-03-15 | 삼성물산 주식회사 | 물류 관리 시스템 및 그 관리방법 |
EP1407432B1 (en) | 2001-05-02 | 2007-08-22 | Virtual Access Limited | Secure payment method and system |
GB2400962B (en) | 2001-05-02 | 2004-12-29 | Virtual Access Ltd | Secure payment method and system |
US20060271497A1 (en) * | 2005-05-24 | 2006-11-30 | Cullen Andrew J | Payment authorisation process |
CA2578466A1 (en) | 2007-01-12 | 2008-07-12 | Truecontext Corporation | Method and system for customizing a mobile application using a web-based interface |
US20080208762A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Payments using a mobile commerce device |
US9053474B2 (en) | 2008-08-04 | 2015-06-09 | At&T Mobility Ii Llc | Systems and methods for handling point-of-sale transactions using a mobile device |
US20110208786A1 (en) | 2010-02-23 | 2011-08-25 | Microsoft Corporation | Presentation of a web-based visual representation of a structured data solution |
JP2011210171A (ja) * | 2010-03-30 | 2011-10-20 | Japan Research Institute Ltd | 決済サーバ、決済システム、決済方法および決済プログラム |
CN102761580B (zh) * | 2011-04-29 | 2015-06-17 | 阿里巴巴集团控股有限公司 | 信息安全处理的方法、处理服务器及处理客户端 |
KR101086620B1 (ko) | 2011-08-23 | 2011-11-23 | 정대영 | 스마트 오피스 시스템 및 운용을 위한 서버 및 운용 방법 |
CA2856567A1 (en) | 2011-11-30 | 2013-06-06 | Spectrum Message Services Pty Ltd | A system, payment agent and computer readable storage medium for facilitating contactless mobile payment transactions |
CN103366303A (zh) * | 2012-03-28 | 2013-10-23 | 黄金富 | 手机购物方法和相应的手机购物电子商务*** |
US20150242844A1 (en) | 2012-10-15 | 2015-08-27 | Powered Card Solutions, Llc | System and method for secure remote access and remote payment using a mobile device and a powered display card |
CN103729768B (zh) * | 2012-10-15 | 2018-10-19 | 北京京东尚科信息技术有限公司 | 一种电子交易信息处理方法和装置 |
CN103226769A (zh) * | 2013-04-12 | 2013-07-31 | 深圳市发掘科技有限公司 | 基于移动设备的餐饮管理***及方法 |
JP6431058B2 (ja) | 2013-07-02 | 2018-11-28 | ボク インコーポレイテッド | マーチャントホスト型勘定 |
CN104599125A (zh) | 2013-10-30 | 2015-05-06 | 中华电信股份有限公司 | 手机应用软件付款服务***及其方法 |
CN105607910A (zh) * | 2015-12-22 | 2016-05-25 | 北京奇虎科技有限公司 | 一种实现通用支付前端服务的方法和装置 |
US11301865B2 (en) | 2017-07-27 | 2022-04-12 | Worldline Smb Us Inc. | Secure card data entry system and method |
US20190102778A1 (en) | 2017-09-29 | 2019-04-04 | Enmax Encompass Inc. | Secure online transaction system and method therefor |
US11409948B2 (en) | 2018-12-10 | 2022-08-09 | Block, Inc. | Centralized brand asset management |
-
2016
- 2016-12-21 CN CN201611195605.6A patent/CN107070858B/zh active Active
-
2017
- 2017-09-22 TW TW106132579A patent/TWI737818B/zh active
- 2017-12-15 JP JP2019534167A patent/JP7036826B2/ja active Active
- 2017-12-15 KR KR1020197017251A patent/KR102246394B1/ko active IP Right Grant
- 2017-12-15 EP EP17882785.3A patent/EP3534585A4/en active Pending
- 2017-12-15 WO PCT/CN2017/116509 patent/WO2018113601A1/zh unknown
- 2017-12-15 MY MYPI2019002979A patent/MY186646A/en unknown
-
2019
- 2019-05-23 US US16/421,188 patent/US11132666B2/en active Active
- 2019-05-30 PH PH12019501204A patent/PH12019501204A1/en unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102546165A (zh) * | 2010-12-31 | 2012-07-04 | ***股份有限公司 | 动态url生成器、生成方法、基于动态url的认证***和方法 |
CN103164790A (zh) * | 2011-12-09 | 2013-06-19 | 腾讯科技(深圳)有限公司 | 网络支付***及其数据处理方法 |
US9390412B2 (en) * | 2012-10-16 | 2016-07-12 | Visa International Service Association | Dynamic point of sale system integrated with reader device |
CN107295052A (zh) * | 2016-04-11 | 2017-10-24 | 阿里巴巴集团控股有限公司 | 一种业务处理方法及装置 |
CN107070858A (zh) * | 2016-12-21 | 2017-08-18 | 阿里巴巴集团控股有限公司 | 一种业务处理方法及装置 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112561650A (zh) * | 2020-12-17 | 2021-03-26 | 深圳希施玛数据科技有限公司 | 一种订单服务请求的处理*** |
CN112561650B (zh) * | 2020-12-17 | 2024-02-02 | 深圳希施玛数据科技有限公司 | 一种订单服务请求的处理*** |
Also Published As
Publication number | Publication date |
---|---|
US20190279190A1 (en) | 2019-09-12 |
EP3534585A1 (en) | 2019-09-04 |
EP3534585A4 (en) | 2020-04-29 |
TW201824012A (zh) | 2018-07-01 |
JP2020502693A (ja) | 2020-01-23 |
JP7036826B2 (ja) | 2022-03-15 |
CN107070858A (zh) | 2017-08-18 |
TWI737818B (zh) | 2021-09-01 |
MY186646A (en) | 2021-08-03 |
CN107070858B (zh) | 2021-09-21 |
KR102246394B1 (ko) | 2021-04-30 |
US11132666B2 (en) | 2021-09-28 |
KR20190082920A (ko) | 2019-07-10 |
PH12019501204A1 (en) | 2019-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018113601A1 (zh) | 一种业务处理方法及装置 | |
US20210150506A1 (en) | Peer-to-peer payment systems and methods | |
TWI718232B (zh) | 業務執行方法及裝置 | |
KR102384124B1 (ko) | 가상 카드 개설 방법 및 시스템, 결제 시스템, 및 카드 발급 시스템 | |
US20150163186A1 (en) | Launching a client application based on a message | |
WO2019105138A1 (zh) | 一种多业务***下的业务标记方法、装置及设备 | |
TWI742324B (zh) | 基於掃描doi的資訊處理方法、裝置及設備 | |
WO2016101811A1 (zh) | 一种信息排序方法及装置 | |
TWI678115B (zh) | 資源傳輸方法及裝置 | |
WO2022267766A1 (zh) | 访问聚合码支付页面的方法、装置、设备及介质 | |
WO2020134654A1 (zh) | 一种电子支付方法、装置、***和存储介质 | |
US11438401B2 (en) | Service processing method and device | |
CN110992040A (zh) | 交易处理方法、装置及设备 | |
CN106817394B (zh) | 传输产品配置参数的方法和服务器 | |
WO2019109665A1 (zh) | 资源转移的验证方法、装置和电子支付验证方法、装置 | |
CN114675982A (zh) | 一种业务集成***的数据获取通用方法及*** | |
CN116503005A (zh) | 流程动态修改方法、装置、***及存储介质 | |
CN117950631A (zh) | 业务数据处理方法、装置及*** |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17882785 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017882785 Country of ref document: EP Effective date: 20190528 Ref document number: 20197017251 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2019534167 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |