CN110543317A - transaction request processing method, device, gateway and storage medium - Google Patents
transaction request processing method, device, gateway and storage medium Download PDFInfo
- Publication number
- CN110543317A CN110543317A CN201910806443.2A CN201910806443A CN110543317A CN 110543317 A CN110543317 A CN 110543317A CN 201910806443 A CN201910806443 A CN 201910806443A CN 110543317 A CN110543317 A CN 110543317A
- Authority
- CN
- China
- Prior art keywords
- transaction request
- version
- application
- user
- determining
- 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.)
- Pending
Links
- 238000003860 storage Methods 0.000 title claims abstract description 20
- 238000003672 processing method Methods 0.000 title claims abstract description 14
- 238000012545 processing Methods 0.000 claims abstract description 24
- 238000011217 control strategy Methods 0.000 claims abstract description 9
- 238000000034 method Methods 0.000 claims description 36
- 230000000694 effects Effects 0.000 claims description 11
- 238000004891 communication Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 8
- 230000009286 beneficial effect Effects 0.000 abstract description 5
- 230000008569 process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application discloses a transaction request processing method, a transaction request processing device, a gateway and a storage medium, and relates to the technical field of computers. The transaction request processing method comprises the following steps: receiving a transaction request of a user; determining an application version matched with the transaction request according to a gray level version control strategy; and if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server, wherein the gray release server is used for running the gray release version of the application. The transaction request processing method, the transaction request processing device, the gateway and the storage medium can provide the new version application for the loyal users to experience in advance, so that the application can be issued to all users as soon as possible, and meanwhile, the beneficial effects of reducing customer complaints, loss and financial risk can be achieved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a transaction request processing method, an apparatus, a gateway, and a storage medium.
Background
With the development of the internet, a short-frequency and fast-frequency development mode is more and more widely applied to the development of various applications, such as the service application of direct-selling bank micro-service, and the service application of the short-frequency and fast-frequency development mode is updated and upgraded frequently.
frequent version updating and upgrading of the application can cause frequent system shutdown, and because the application of the new version does not pass a large amount of use verification, application instability and even accounting problems can occur, so that each time the application is upgraded or a new service is brought online, complaints, losses and even accounting safety problems of a user and the like can be caused due to poor user transaction experience.
therefore, it is urgent to provide an effective solution to avoid the customer complaints, loss and even financial problems caused by frequent version updating and upgrading while ensuring that the user is provided with a new version experience.
Disclosure of Invention
The embodiment of the application adopts the following technical scheme:
The embodiment of the application provides a transaction request processing method, which is deployed at a gateway and comprises the following steps:
Receiving a transaction request of a user;
determining an application version matched with the transaction request according to a gray level version control strategy;
And if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server, wherein the gray release server is used for running the gray release version of the application.
Optionally, the determining, according to a grayscale version control policy, an application version matched with the transaction request includes:
And determining the application version matched with the transaction request according to the history of the user.
Optionally, the determining the application version matching the transaction request according to the history of the user includes:
And determining the application version matched with the transaction request according to the historical transaction data volume of the user and/or the historical activity degree of the user.
Optionally, the determining, according to the historical transaction data amount of the user and/or the historical activity degree of the user, an application version matched with the transaction request includes:
And when the historical transaction amount data of the user is higher than a set transaction amount threshold value and/or the historical activity degree of the user is higher than a set activity threshold value, determining that the application version matched with the transaction request is a gray release version.
Optionally, the determining, according to a grayscale version control policy, an application version matched with the transaction request includes:
And determining the application version matched with the transaction request according to a request interface in the transaction request.
optionally, the determining, according to a request interface in the transaction request, an application version matched with the transaction request includes:
And if the request interface in the transaction request is matched with a predefined white list interface, judging that the application version matched with the transaction request is a gray release version.
Optionally, the method further includes:
and forwarding the processing result of the gray scale issuing server to the transaction request to the user.
An embodiment of the present application further provides a transaction request processing apparatus, where the transaction request processing apparatus includes:
the receiving module is used for receiving a transaction request of a user;
The determining module is used for determining the application version matched with the transaction request according to a gray level version control strategy;
And the forwarding module is used for forwarding the transaction request to a gray release server if the application version matched with the transaction request is a gray release version, wherein the gray release server is used for running the gray release version of the application.
The embodiment of the application also provides a gateway, which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the bus;
A memory for storing a computer program;
A processor for executing the program stored in the memory to implement any of the above method steps.
An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and the computer program, when executed by a processor, implements any of the method steps described above.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
the transaction request processing method, the transaction request processing device, the gateway and the storage medium can customize personalized services for different users, provide the new version application for the user meeting the transaction conditions of the gray release server to experience in advance, so that the application can be released to all users as soon as possible, and meanwhile, the beneficial effects of reducing customer complaints, loss and financial risk can be achieved.
Drawings
the accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
Fig. 1 is a schematic diagram of an application environment provided in the embodiment of the present application.
fig. 2 is a flowchart of a transaction request processing method according to an embodiment of the present disclosure.
fig. 3 is a schematic block diagram of a gateway according to an embodiment of the present application.
fig. 4 is a block diagram illustrating a transaction request processing apparatus according to an embodiment of the disclosure.
icon: 100-a gateway; 110-a processor; 120-internal bus; 130-a network interface; 140-a memory; 150-transaction request processing means; 151-a receiving module; 153-a determination module; 155-a forwarding module; 200-a user terminal; 300-grey release server; 400-ordinary server.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Referring to fig. 1, which is a schematic view of an application environment of a transaction request processing method, apparatus, gateway and storage medium provided in the embodiments of the present application, a user terminal 200 communicates with a server through a gateway 100, and can initiate a transaction request to the server through the gateway 100. The server comprises a gray release server 300 and a common server 400, wherein the gray release server 300 is used for running a gray release version, namely a latest experience version, of the application, the common server 400 is used for running an old version before the latest experience version of the application, and the number of the common server 400 and the gray release server 300 can be adjusted according to specific situations.
in this embodiment, the user terminal 200 may be, but is not limited to, a smart phone, a Personal Computer (PC), a tablet PC, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), and the like.
referring to fig. 2, it is a flowchart of a transaction request processing method provided in this embodiment of the application, where the transaction request processing method is applied to the gateway 100, and is used for transaction requests of various new version applications, such as transaction requests of a direct sales bank microservice application.
It is to be understood that the above described subject matter of execution is not to be construed as limiting the present application.
For convenience of description, unless otherwise specified, the embodiment of the method of the present application is described by taking an execution subject as an example of the gateway 100.
specifically, the implementation process of the method comprises the following steps:
In step S11, a transaction request from a user is received.
In the embodiment of the present application, the transaction request may be, but is not limited to, various requests for transferring money, borrowing money, purchasing bank products, and the like initiated by the user. When a user of the user terminal 200 needs to perform a transaction, a transaction request may be initiated through the user terminal 200, and the gateway 100 receives the transaction request of the user initiated by the user terminal 200.
And step S13, determining the application version matched with the transaction request according to the gray level version control strategy.
in one embodiment, determining the application version for which the transaction request matches according to a grayscale version control policy may be based on a user's history.
specifically, the transaction request of the user includes identification information for uniquely identifying the user, and when the transaction request of the user is obtained, the user can be identified according to the unique identification code in the transaction request. The unique identification code may be, but is not limited to, account number information or identity information of the user, for example, the unique identification code may be a bank card account number, an identification number of the user, and the like.
When a user initiates a request to access the server, the access record, the transaction record and the like of the user are recorded. The gateway 100 is predefined with a grayscale version control policy based on the user's history, including but not limited to at least one of historical traffic data and historical activity level of the user. When a user initiates a transaction request, determining an application version matched with the transaction request according to historical information of the user, if historical transaction amount data is higher than a set transaction amount threshold and/or historical activity degree is higher than a set activity threshold, indicating that the user is a white list client, and judging that the application version matched with the transaction request is a gray release version.
for example, for the direct marketing bank micro-service application, the transaction number in the direct marketing bank micro-service application exceeds a preset number, or the transaction amount in the direct marketing bank micro-service application exceeds a preset amount, or the frequency of accessing the direct marketing bank micro-service application exceeds a preset frequency threshold, it may be determined whether the user is a white list client, that is, the application version matched with the transaction request is a grayscale release version.
In one embodiment, determining the application version that the transaction request matches according to the grayscale version control policy may be determining whether the request interface in the transaction request matches a whitelist interface.
Specifically, one or more Application Programming Interfaces (APIs) may be defined to match the white list Interface through which the gray publication server 300 is accessible. After receiving a transaction request of a user, a request interface (API interface) in the transaction request may be matched with a predefined white list interface, and if the request interface in the transaction request is matched with the predefined white list interface, it is determined that an application version matched with the transaction request is a grayscale release version, and the user may access the grayscale release server 300 to perform a transaction.
and step S15, if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server.
If the application version matched with the transaction request is the gray release version, the transaction request of the user is forwarded to the gray release server 300, and after the gray release server 300 responds to the transaction request, the user can use the new version service application and the new online service in the new version service application.
In an embodiment, if the number of transaction requests initiated at the same time is multiple and the number of transaction requests matching the grayscale release version exceeds a set threshold, the grayscale release server 300 may not be able to respond to the transaction requests of the multiple users in time. Therefore, one part of the transaction requests can be forwarded to the gray scale distribution server 300 through the balance loader, and the other part of the transaction requests can be forwarded to the common server 400. Therefore, excessive transaction requests can be shared by the common server 400, so that timely response to the user can be ensured, better service is provided for the user, and user experience is improved.
In step S17, the result of the processing of the transaction request by the grayscale issuing server is forwarded to the user.
After the gray scale publishing server 300 processes the received transaction request, the processing result is fed back to the gateway 100, and the gateway 100 forwards the processing result of the transaction request to the user of the user terminal 200, thereby completing the whole transaction process.
In summary, the transaction request processing method provided by the present application may determine whether the application version initiating the transaction request matching is the gray release version by identifying whether the user is a white list client with high loyalty and determining whether the request interface in the transaction request is matched with the predefined white list interface, and forward the transaction request to the gray release server 300 installed with the new version (gray release version) to be released when the application version matched with the transaction request is the gray release version. Therefore, the new version application can be provided for the user with high loyalty to experience in advance, and the customers with enough magnitude can be ensured to carry out sufficient production verification, so that the application can be released to all customers as soon as possible. Meanwhile, the method provides the user with high loyalty to experience in advance, and can achieve the beneficial effects of reducing customer complaints, reducing customer loss and reducing financial risks. In addition, when the number of the transaction requests matching the gray release version exceeds a set threshold, too many transaction requests can be shared by the common server 400, so that the user can be ensured to respond to the transaction requests in time, better service is provided for the user, and the user experience is improved.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
fig. 3 is a block diagram illustrating a gateway 100 according to an embodiment of the present application. Referring to fig. 3, at a hardware level, the gateway 100 includes a processor 110, and optionally further includes an internal bus 120, a network interface 130, and a memory 140. The Memory 140 may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the gateway 100 may also include hardware required for other services.
the processor 110, the network interface 130, and the memory 140 may be connected to each other by an internal bus 120, and the internal bus 120 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 3, but this does not indicate only one bus or one type of bus.
And a memory 140 for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory 140 may include memory and non-volatile storage and provides instructions and data to the processor 110.
the processor 110 reads a corresponding computer program from the non-volatile memory into the memory and then runs the computer program to form the transaction request processing device 150 on a logic level. The processor 110 executes the program stored in the memory 140, and is specifically configured to perform the following operations:
Receiving a transaction request of a user;
Determining an application version matched with the transaction request according to a gray level version control strategy;
and if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server, wherein the gray release server is used for running the gray release version of the application.
The method executed by the transaction request processing device 150 according to the embodiment shown in fig. 3 of the present application can be applied to the processor 110, or implemented by the processor 110. The processor 110 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 110. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 140, and the processor 110 reads the information in the memory 140 and completes the steps of the method in combination with the hardware thereof.
The gateway may also execute the method shown in fig. 2 and implement the functions of the transaction request processing device 150 in the embodiment shown in fig. 2, which is not described herein again in this embodiment of the present application.
of course, besides the software implementation, the gateway of the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution main body of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
An embodiment of the present application further provides a computer-readable storage medium storing one or more programs, where the one or more programs include instructions, which when executed by a gateway including a plurality of application programs, enable the gateway to perform the method of the embodiment shown in fig. 2, and are specifically configured to perform the following operations:
Receiving a transaction request of a user;
determining an application version matched with the transaction request according to a gray level version control strategy;
And if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server, wherein the gray release server is used for running the gray release version of the application.
Fig. 4 is a block diagram illustration of a transaction request processing device 150 according to an embodiment of the present application. Referring to fig. 4, in one software implementation, the transaction request processing device 150 may include:
the receiving module 151 is configured to receive a transaction request of a user.
It is understood that the receiving module 151 may be configured to execute the step S11 described above.
And the determining module 153 is used for determining the application version matched with the transaction request according to the grayscale version control strategy.
It is understood that the determining module 153 may be configured to perform the step S13 described above.
and the forwarding module 155 is configured to forward the transaction request to the grayscale issuing server when the application version matched with the transaction request is a grayscale issuing version, where the grayscale issuing server is used to run the grayscale issuing version of the application.
It is understood that the forwarding module 155 may be configured to perform the step S15 described above.
In summary, the transaction gateway, the storage medium, and the easy request processing device 150 provided by the present application can determine whether the application version initiating the transaction request matching is the gray release version by identifying whether the user is a white list client with high loyalty and by determining whether the request interface in the transaction request matches with the predefined white list interface, and forward the transaction request to the gray release server 300 installed with the new version application to be released when the application version matching the transaction request is the gray release version. Therefore, the new version application can be provided for the user with high loyalty to experience in advance, and the customers with enough magnitude can be ensured to carry out sufficient production verification, so that the application can be released to all customers as soon as possible. Meanwhile, the method provides the user with high loyalty to experience in advance, and can achieve the beneficial effects of reducing customer complaints, reducing customer loss and reducing financial risks.
In short, the above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, 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.
computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Claims (10)
1. a transaction request processing method deployed at a gateway, the method comprising:
Receiving a transaction request of a user;
Determining an application version matched with the transaction request according to a gray level version control strategy;
and if the application version matched with the transaction request is a gray release version, forwarding the transaction request to a gray release server, wherein the gray release server is used for running the gray release version of the application.
2. the method of claim 1, wherein determining the application version that the transaction request matches according to a grayscale version control policy comprises:
And determining the application version matched with the transaction request according to the history of the user.
3. the method of claim 2, wherein determining the application version that the transaction request matches based on the user history comprises:
And determining the application version matched with the transaction request according to the historical transaction data volume of the user and/or the historical activity degree of the user.
4. the method of claim 3, wherein determining the application version that the transaction request matches based on the historical transaction data volume of the user and/or the historical activity of the user comprises:
And when the historical transaction amount data of the user is higher than a set transaction amount threshold value and/or the historical activity degree of the user is higher than a set activity threshold value, determining that the application version matched with the transaction request is a gray release version.
5. The method of claim 1, wherein determining the application version that the transaction request matches according to a grayscale version control policy comprises:
And determining the application version matched with the transaction request according to a request interface in the transaction request.
6. The method of claim 5, wherein determining the application version matching the transaction request according to a request interface in the transaction request comprises:
And if the request interface in the transaction request is matched with a predefined white list interface, judging that the application version matched with the transaction request is a gray release version.
7. The method of claim 1, further comprising:
And forwarding the processing result of the gray scale issuing server to the transaction request to the user.
8. a transaction request processing apparatus, characterized in that the transaction request processing apparatus comprises:
The receiving module is used for receiving a transaction request of a user;
the determining module is used for determining the application version matched with the transaction request according to a gray level version control strategy;
and the forwarding module is used for forwarding the transaction request to a gray release server if the application version matched with the transaction request is a gray release version, wherein the gray release server is used for running the gray release version of the application.
9. A gateway is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the communication interface through the bus;
A memory for storing a computer program;
A processor for executing a program stored in the memory to perform the method steps of any of claims 1 to 7.
10. A computer-readable storage medium, characterized in that a computer program is stored in the storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910806443.2A CN110543317A (en) | 2019-08-29 | 2019-08-29 | transaction request processing method, device, gateway and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910806443.2A CN110543317A (en) | 2019-08-29 | 2019-08-29 | transaction request processing method, device, gateway and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110543317A true CN110543317A (en) | 2019-12-06 |
Family
ID=68712218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910806443.2A Pending CN110543317A (en) | 2019-08-29 | 2019-08-29 | transaction request processing method, device, gateway and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543317A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111815401A (en) * | 2020-06-16 | 2020-10-23 | 上海悦易网络信息技术有限公司 | Method and device for ordering flow control |
| CN113391823A (en) * | 2021-06-15 | 2021-09-14 | 中国工商银行股份有限公司 | Gray scale publishing method, device and system |
| CN114840249A (en) * | 2022-05-18 | 2022-08-02 | 吉林银行股份有限公司 | Gray level publishing method, device and equipment for centralized business system |
| CN115022398A (en) * | 2022-07-14 | 2022-09-06 | 中国工商银行股份有限公司 | Interface calling method and device based on API open platform and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104993946A (en) * | 2015-06-01 | 2015-10-21 | 华为技术有限公司 | Evaluation method, device and system for gated launch |
| US20170088600A1 (en) * | 2012-11-01 | 2017-03-30 | La Jolla Institute For Allergy And Immunology | Novel crystal structure and ligand binding sites of trail receptor |
| CN108768875A (en) * | 2018-05-31 | 2018-11-06 | 康键信息技术（深圳）有限公司 | Gray scale dissemination method, device and the computer readable storage medium of application |
| CN108920160A (en) * | 2018-05-31 | 2018-11-30 | 深圳壹账通智能科技有限公司 | Upgrade method, device, server and the computer storage medium of application APP |
| CN110046083A (en) * | 2018-01-17 | 2019-07-23 | 北京京东尚科信息技术有限公司 | Automate gray scale dissemination method and device |
-
2019
- 2019-08-29 CN CN201910806443.2A patent/CN110543317A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170088600A1 (en) * | 2012-11-01 | 2017-03-30 | La Jolla Institute For Allergy And Immunology | Novel crystal structure and ligand binding sites of trail receptor |
| CN104993946A (en) * | 2015-06-01 | 2015-10-21 | 华为技术有限公司 | Evaluation method, device and system for gated launch |
| CN110046083A (en) * | 2018-01-17 | 2019-07-23 | 北京京东尚科信息技术有限公司 | Automate gray scale dissemination method and device |
| CN108768875A (en) * | 2018-05-31 | 2018-11-06 | 康键信息技术（深圳）有限公司 | Gray scale dissemination method, device and the computer readable storage medium of application |
| CN108920160A (en) * | 2018-05-31 | 2018-11-30 | 深圳壹账通智能科技有限公司 | Upgrade method, device, server and the computer storage medium of application APP |
Non-Patent Citations (1)
| Title |
|---|
| 刘军 等: "《电子商务系统的规划与设计》", 人民邮电出版社 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111815401A (en) * | 2020-06-16 | 2020-10-23 | 上海悦易网络信息技术有限公司 | Method and device for ordering flow control |
| CN111815401B (en) * | 2020-06-16 | 2024-02-13 | 上海万物新生环保科技集团有限公司 | Order flow control method and equipment |
| CN113391823A (en) * | 2021-06-15 | 2021-09-14 | 中国工商银行股份有限公司 | Gray scale publishing method, device and system |
| CN114840249A (en) * | 2022-05-18 | 2022-08-02 | 吉林银行股份有限公司 | Gray level publishing method, device and equipment for centralized business system |
| CN114840249B (en) * | 2022-05-18 | 2023-08-08 | 吉林银行股份有限公司 | Gray scale release method, device and equipment of centralized service system |
| CN115022398A (en) * | 2022-07-14 | 2022-09-06 | 中国工商银行股份有限公司 | Interface calling method and device based on API open platform and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110543317A (en) | transaction request processing method, device, gateway and storage medium | |
| TWI722256B (en) | Business processing method and device | |
| US10902415B2 (en) | Payment card binding method, trust evaluation method, apparatus, and electronic device | |
| CN109658238B (en) | Data processing method and device | |
| US10742582B2 (en) | Launching a client application based on a message | |
| CN110020846B (en) | Transfer service processing method and system | |
| US20240232932A1 (en) | Stake sharing processing method and apparatus | |
| CN109146493B (en) | Consumption data processing method and device | |
| US11461503B2 (en) | Service processing method and apparatus | |
| CN111930786A (en) | Resource acquisition request processing system, method and device | |
| US11144947B2 (en) | Managing user loyalty groups at point-of-sale accesses | |
| CN111582872A (en) | Abnormal account detection model training method, abnormal account detection device and abnormal account detection equipment | |
| CN111709748B (en) | Transaction execution method and device with business attribute and electronic equipment | |
| CN107528822B (en) | Service execution method and device | |
| CN112418864A (en) | Data sending method and device | |
| CN107169752B (en) | Resource transfer method and device | |
| CN110443291B (en) | Model training method, device and equipment | |
| CN110278241B (en) | Registration request processing method and device | |
| US12099623B2 (en) | Computer-implemented method for removing access to data | |
| CN113485758A (en) | Micro-service issuing method and device, electronic equipment and storage medium | |
| US20180288575A1 (en) | Tracking system | |
| CN109829268B (en) | Method and device for determining relevance of terminals of different applications | |
| CN112184074A (en) | Prompt message output method and device | |
| CN112016915B (en) | Method and device for providing service for user | |
| CN111798235A (en) | Method and device for storing wind control information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Room 306, No. 799, Ximen Road, Chengqiao Town, Chongming District, Shanghai 202150 Applicant after: SHANGHAI I2FINANCE SOFTWARE CO.,LTD. Address before: Room 2076, area C, building 8, No.2, Guanshan Road, Chengqiao Town, Chongming District, Shanghai 202150 Applicant before: SHANGHAI I2FINANCE SOFTWARE CO.,LTD. |
|
| CB02 | Change of applicant information | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191206 |
|
| RJ01 | Rejection of invention patent application after publication |