WO2022073354A1 - 业务审核通知方法及网关、电子设备、可读介质 - Google Patents

业务审核通知方法及网关、电子设备、可读介质 Download PDF

Info

Publication number
WO2022073354A1
WO2022073354A1 PCT/CN2021/098031 CN2021098031W WO2022073354A1 WO 2022073354 A1 WO2022073354 A1 WO 2022073354A1 CN 2021098031 W CN2021098031 W CN 2021098031W WO 2022073354 A1 WO2022073354 A1 WO 2022073354A1
Authority
WO
WIPO (PCT)
Prior art keywords
audit
message
notification
notified
gateway
Prior art date
Application number
PCT/CN2021/098031
Other languages
English (en)
French (fr)
Inventor
刘源旭
张昊
喻聪
陶柯
Original Assignee
百度(中国)有限公司
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 百度(中国)有限公司 filed Critical 百度(中国)有限公司
Priority to KR1020217042890A priority Critical patent/KR102651156B1/ko
Priority to EP21823720.4A priority patent/EP4009611A4/en
Priority to US17/597,084 priority patent/US20230188620A1/en
Priority to JP2021578248A priority patent/JP2023501850A/ja
Publication of WO2022073354A1 publication Critical patent/WO2022073354A1/zh

Links

Images

Classifications

    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/55—Push-based network services
    • 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

Definitions

  • the present application relates to the field of computer technologies, in particular to cloud computing and cloud platform technologies, and in particular to a business audit notification method and gateway, electronic device, and readable medium.
  • the applet can save the user's time cost and mobile phone memory space, and at the same time greatly reduce the developer's R&D cost and promotion cost.
  • Mini Program developers and third-party service providers provide a variety of access methods to enrich Mini Program capabilities, such as Mini Program package management, basic information settings, information flow/search material services, order/payment services, message services, etc. It can not only support operations through the platform interface, but also use the capabilities by calling the open application programming interface (Application Programming Interface, API) provided by the platform.
  • API Application Programming Interface
  • a business audit notification method including:
  • a business audit notification method including:
  • the service review request is a message sent by the gateway in response to an operation request of the user terminal;
  • the audit result is acquired and stored, so that the gateway can generate an audit notification message based on the audit result and the message to be notified; wherein the message to be notified is a message generated by the gateway for the service audit request.
  • a gateway comprising:
  • a submission module configured to send a business audit request to the audit platform in response to an operation request of the user terminal, and generate a message to be notified based on the audit task identifier returned by the audit platform;
  • a push module is configured to generate an audit notification message based on the obtained audit result and the to-be-notified message, and push the audit notification message to the user terminal.
  • an electronic device comprising:
  • the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method described in any one of the service audit notification methods. method.
  • a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute any one of the above-mentioned business audit notification methods.
  • a computer program product including a computer program, which, when executed by a processor, implements the service audit notification method described in any one of the above distributed storage methods.
  • the business audit notification method provided by this application sends a business audit request to an audit platform in response to an operation request initiated by a user terminal; generates a to-be-notified message based on the audit task identifier returned by the audit platform; generates an audit notification message based on the audit result and the to-be-notified message; The notification message is pushed to the user terminal.
  • This method is versatile and can support any type of business review (such as the review of small program capabilities), while reducing the labor cost of developers, reducing code redundancy, and improving the maintainability of business code. sex.
  • FIG. 1 is a schematic diagram of an application scenario of a service audit notification method provided by an embodiment of the present application
  • FIG. 2 is a flowchart of a service audit notification method provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of sending a business audit request to an audit platform in response to a user's operation request provided by the embodiment of the present application;
  • FIG. 4 is a flowchart of pushing an audit notification message to a user terminal provided by an embodiment of the present application
  • FIG. 5 is a flowchart of a service audit notification method provided by an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a gateway provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a submission module provided by an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of an authentication unit provided by an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a push module provided by an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of another push module provided by an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a review platform provided by an embodiment of the present application.
  • FIG. 13 is a block diagram of an electronic device used to implement the service audit notification method according to the embodiment of the present application.
  • the applet referred to in the embodiments of the present application refers to an application program that can be run on an instant messaging application without downloading and installing, and is usually loaded in a third-party application. Most of the modification or operation behaviors of Mini Programs need to be manually reviewed by the review platform. Therefore, Mini Program developers or third-party service providers cannot immediately obtain the review results when calling the Open API Gateway, and an asynchronous notification mechanism is required to notify the review results. .
  • the current open API gateway cannot support the asynchronous notification mechanism. Therefore, in the development process of the applet capability, it is necessary to customize the asynchronous notification function for each operation scenario involving auditing, which wastes R&D manpower. It also leads to code redundancy and affects the maintainability of the overall server architecture. Moreover, since the asynchronous notification codes developed by different developers do not have a unified mechanism to ensure the definiteness of notification messages, there may be missing notification messages, which affects the ability of the applet developers or third-party service providers to use the applet capabilities.
  • the present application provides a business audit notification method, which is used to realize the function closed-loop of API gateway invocation and asynchronous notification, reduce the labor cost of developers, reduce code redundancy, and improve the performance of business code. maintainability.
  • FIG. 1 is a schematic diagram of an application scenario of a service audit notification method provided by an embodiment of the present application.
  • the application scenario may include: at least one user terminal 11, a gateway 12 and an audit platform 13, and the user terminal 11, the gateway 12 and the audit platform 13 communicate through a network.
  • the user terminal 11 may be a terminal used by a small program developer or a third-party service provider.
  • the applet developer and the third-party service provider can develop one or more applet programs on the user terminal 11, and can also modify the existing applet programs.
  • applet developers and third-party service providers can modify applet capabilities through the applet development platform.
  • the applet development platform may be a platform independently operated by the operator of the application (Application, APP) carrying the applet, or a third-party applet development platform that has a cooperative relationship with the operator of the APP carrying the applet.
  • the applet development platform is also called applet developer tool, which is a tool for producing and modifying applet programs. This application does not limit the specific embodiment of the applet development platform.
  • the gateway 12 receives the operation request for the applet capability submitted by the user terminal 11, such as the release of the applet package, the modification of the applet name, etc., and sends a business audit request to the audit platform based on the operation request, so as to verify whether the operation request of the applet complies with the requirements. Relevant regulations; at the same time, a to-be-notified message is generated, so that an audit notification message is generated after the audit result is obtained.
  • the audit platform 13 audits whether the applet capability is legal according to the specific content of the business audit request, and stores the audit result in the message queue.
  • the auditing platform 13 may be a cloud server.
  • the embodiment of the present application does not limit the specific form of the audit platform, which can be determined according to actual needs, and will not be repeated here.
  • the gateway 11 obtains the audit result from the message queue, concatenates the audit result and the message to be notified to obtain the audit notification message, and then sends the audit notification message to the user terminal, and the user can obtain the audit result from the user terminal.
  • an embodiment of the present application provides a service audit notification method, and the method can be applied to a gateway, and the gateway can be an API gateway or other gateways that can be used to transmit signals.
  • FIG. 2 is a flowchart of a service review notification method provided by an embodiment of the present application.
  • the service audit notification method provided by the embodiment of the present application includes:
  • Step 201 in response to a user terminal initiating an operation request, send a service review request to the review platform.
  • the user initiates the operation request through the user terminal used by the user.
  • the operation request can be a request for applet services or a request for other applications.
  • the operation request includes, but is not limited to, modifying the basic information of the applet (such as name, avatar, profile, industry category, etc.), publishing the applet package, submitting distribution materials (search/recommendation feed), and opening payment services Wait.
  • modifying the basic information of the applet such as name, avatar, profile, industry category, etc.
  • publishing the applet package submitting distribution materials (search/recommendation feed)
  • opening payment services Wait includes, but is not limited to, modifying the basic information of the applet (such as name, avatar, profile, industry category, etc.), publishing the applet package, submitting distribution materials (search/recommendation feed), and opening payment services Wait.
  • the user initiates an operation request through a user terminal as an operation request initiated by the user terminal.
  • the user terminal may be a terminal with a communication function, such as a mobile phone, a palmtop computer, a personal computer (Personal Computer, PC) machine, and an all-in-one machine.
  • a communication function such as a mobile phone, a palmtop computer, a personal computer (Personal Computer, PC) machine, and an all-in-one machine.
  • the user may be a small program developer or a third-party service provider.
  • the applet developer is the owner or manager of the applet.
  • a third-party service provider is a third-party service provider authorized by the Mini Program developer or a third-party service provider authorized by the administrator.
  • the applet developer or manager can authorize all the use rights of the third-party service providers, or only part of the use rights.
  • the third-party service provider manages the Mini Program capabilities within the authorization authority of the Mini Program developer or manager.
  • the applet developer or manager needs to submit an audit to the audit platform, so that the audit platform can verify the legitimacy of the applet capability.
  • the applet platform provides multiple access and usage methods to enrich the applet capabilities, such as applet package management, basic information setting, information flow/search material service, order/payment service, message service, etc. You can operate through the Mini Program platform interface, or use the capabilities by calling the open API provided by the Mini Program platform.
  • the user initiates an operation request to the gateway, wherein the operation request includes but is not limited to modifying the basic information of the applet (such as name, avatar, profile, industry category, etc.), publishing the applet package, submitting the distribution materials ( search/recommend feed) and payment service activation, etc.
  • the user ID and the application ID are carried in the operation request.
  • the application identifier may be an applet identifier in any form.
  • the user identity identifier is an identifier used to identify the user identity
  • the applet identifier is an identifier used to identify the applet identity.
  • Operation types include, but are not limited to, applet packages, basic information settings, information flow/search material services, order/payment services, and message services.
  • Operation parameters are related to operation types, and each operation type corresponds to different parameters. For example, when publishing the applet package, it is necessary to provide the parameters of the applet package identifier (package_id) and the applet package version (package_version), and when modifying the applet name, the parameter of the applet name (app_name) needs to be provided.
  • the gateway after receiving the operation request initiated by the user terminal, the gateway sends a service audit request to the audit platform.
  • the review platform can review Mini Programs through manual or a combination of machine and manual review.
  • the audit request corresponds to the operation request.
  • the types of review requests include, but are not limited to, applet package review, name review, industry category review, avatar and profile review, (recommended/search) material review, payment account review, and the like.
  • step 202 a message to be notified is generated based on the audit task identifier returned by the audit platform.
  • the audit task identifier is an identifier assigned by the audit platform to the business audit request.
  • the audit platform after receiving the service audit request from the gateway, the audit platform returns the audit task identifier to the gateway. After the gateway receives the audit task ID, it generates a message to be notified.
  • the message to be notified is stored in a message database to be notified, and the fields involved in the message to be notified include an audit task identifier, a user identity identifier, the time for submitting a business audit, an audit notification template, operation parameters, and audit result message items.
  • the audit notification template can be configured in advance, and the audit notification template is configured separately for each operation type.
  • Each audit notification template can include an audit pass sub-template and an audit rejection sub-template.
  • the audit notification template may use a json structure, for example, the applet package audit rejection sub-template may use the following format:
  • a string in the form of $ ⁇ ... ⁇ represents the field to be filled.
  • the fields to be filled can be filled by extracting the corresponding field values from the submit request parameters and the audit result message.
  • app_id indicates the applet ID
  • developer_id and tp_developer_id indicate the developer identification ID and the third-party service provider identification ID, respectively
  • the reason field indicates the reason for the audit failure
  • package_id and package_version indicate the applet package identification ID and applet package version, respectively.
  • Step 203 Generate an audit notification message based on the obtained audit result and the message to be notified.
  • the audit results include audit approval and audit rejection. For example, when the audit platform believes that the Mini Program's capabilities meet the set requirements, the audit result is passed. When the review platform considers that the Mini Program's capabilities do not meet the set requirements, the review result will be review rejection.
  • the review platform conducts manual reviews on pages of the review platform by reviewers.
  • the audit result is passed.
  • the audit result is audit rejection.
  • the gateway assembles the audit result and the message to be notified to generate the audit notification message. For example, after obtaining the audit result, the gateway adds the audit result to the corresponding field of the message to be notified to obtain the audit notification message.
  • an audit notification message can take the following format:
  • the ID of the applet is "1452365”
  • the ID of the developer is "17328232”
  • the time of submission for review is "2019-01-14 12:45:10”
  • the type of review is "PACKAGE_AUDIT_FAIL”
  • the reason for the failure of the review is "The name does not match the actual opened name”
  • the identity of the applet is "745815”
  • the version of the applet is "1.3.46”.
  • Step 204 push the audit notification message to the user terminal.
  • the gateway After the gateway generates the audit notification message, it pushes the audit notification message to the user terminal, and the user views the audit result through the user terminal.
  • sending a business audit request to the audit platform in response to the user's operation request includes:
  • Step 301 parse the operation request to obtain the user identity identifier and the applet identifier.
  • the gateway parses the operation request to obtain the user identity, the applet identifier, the operation type and the operation parameters.
  • the operation types include, but are not limited to, applet package management, basic information settings, information flow/search material services, order/payment services, and message services.
  • Operation parameters are related to operation types, and each operation type corresponds to different parameters.
  • the operation request initiated by the user terminal is to modify the name of the applet
  • the operation request includes the user ID, applet identification, operation type (name modification) and name parameter (new name of the applet).
  • the operation parameter further includes a timestamp, which is used to identify the authorization time for the third-party service provider, that is, the third-party service provider can develop and modify the applet within the authorization time.
  • Step 302 verify the user identity based on the user identity identifier and the applet identifier.
  • the user identity is authenticated based on the user identity and the applet identity.
  • the gateway verifies the permission relationship with the applet ID based on the user ID. If the user does not have the operation authority for the applet corresponding to the applet identifier, a no-authority message is directly returned to the user terminal; if the user has the operation authority for the applet corresponding to the applet identifier, follow-up operations are performed.
  • Step 303 in the case of passing the user identity verification, send a business audit request to the audit platform.
  • the gateway sends a business audit request to the audit platform.
  • the service audit request includes the applet identifier, the operation type (name modification), and the name parameter (the new name of the applet).
  • the audit platform after receiving the business audit request, returns the audit task identifier ID to the gateway.
  • the gateway After receiving the audit task identifier, the gateway obtains the audit notification template corresponding to the operation type from the notification template library, and based on the audit notification template .
  • the audit task identifier generates a message to be notified, and stores the message to be notified in the message database to be notified.
  • the to-be-notified message includes the audit task identifier, the user identity identifier, the time for submitting the business audit, the audit notification template, the operation parameters, and the audit result message item.
  • the audit notification template is a template preset and stored in a notification template library.
  • each operation type corresponds to an audit notification template.
  • the audit notification template is a template determined according to the type of operation and is universal. Store the audit notification template in the notification template library, and extract the audit notification template at any time when needed, which can improve the efficiency of generating messages to be notified and reduce the probability of errors.
  • the gateway When the gateway receives the operation request, it queries the audit notification template library based on the type of the operation request to obtain the matching audit notification template, and then based on the audit task ID, user ID, time for submitting business audit, audit notification template, operation parameters and The audit result message item generates a to-be-notified message.
  • the review platform sends the review result to a message queue after reviewing the content to be reviewed in the service review request.
  • the message queue is a queue for storing audit results, and each message in the message queue includes an audit task identifier and an audit result.
  • the same audit result may be pushed more than once.
  • both the applet developer and the third-party service provider need to obtain the audit result.
  • the audit result should be sent not only to the applet developer, but also to the third-party service provider.
  • the use of message queues can isolate the gateway from the audit platform, and achieve the purpose of pushing and consuming the results of one audit to multiple parties.
  • the gateway subscribes the audit result from the message queue, and obtains the audit notification message by splicing the audit result and the message to be notified.
  • the gateway obtains the audit result from the message queue and the to-be-notified message from the to-be-notified message base according to the audit task identifier, and assembles the audit result into the audit result message item in the to-be-notified message, thereby obtaining the audit notification message.
  • the gateway can subscribe to the audit results from the message queue multiple times, so as to push the audit notification message to the user terminal multiple times, thereby effectively avoiding the problem of missed pushes.
  • the gateway may push the audit notification message to the user terminal multiple times according to preset time intervals and preset push times.
  • the preset maximum number of pushes is 5 times
  • the preset time interval is 1 minute, 5 minutes, 15 minutes, 1 hour or 6 hours.
  • the first supplementary push is performed at an interval of 1 minute; after the first supplementary push is completed, the second supplementary push is performed at an interval of 5 minutes; after the second supplementary push is completed, the interval 15 minutes for the third supplementary push; after the third supplementary push, the fourth supplementary push is performed at an interval of 1 hour; after the fourth supplementary push is completed, the fifth supplementary push is performed at an interval of 6 hours.
  • the success rate of push can be improved.
  • pushing the audit notification message to the user terminal includes:
  • Step 401 Obtain the push address of the user terminal from the push address library.
  • the push address library is a database for storing push addresses.
  • the address of the user terminal is stored in the push address database, so that the gateway can push the audit notification message to the user terminal according to the push address.
  • the user stores his own address in the push address library in advance through the user terminal, so that the gateway can call from the push address library when needed.
  • Step 402 Push the audit notification message to the user terminal according to the push address.
  • the gateway subscribes the corresponding audit result from the message queue according to the audit task identifier, obtains the corresponding to-be-notified message from the to-be-notified message base according to the audit task identifier, and assembles the audit result corresponding to the audit task identifier and the to-be-notified message to obtain the audit notification message .
  • the gateway obtains the push address of the user terminal from the push address library, and sends an audit notification message to the user terminal according to the push address.
  • the gateway pushes the audit notification message to the user terminal multiple times according to the push address, which can improve the success rate of push.
  • the gateway can directly query the audit platform to obtain the audit result, and push the audit result and the to-be-notified message together after assembly to the user terminal, so as to avoid missing messages.
  • the business audit notification method sends a business audit request to an audit platform in response to an operation request initiated by a user terminal; generates a to-be-notified message based on the audit task identifier returned by the audit platform; obtains an audit result, and generates an audit based on the audit result and the to-be-notified message Notification message; push the audit notification message to the user terminal, this method can support the asynchronous notification mechanism of any applet capability, while reducing the labor cost of developers, reducing code redundancy, and improving the maintainability of business code .
  • an embodiment of the present application provides a service audit notification method, which is applied to an audit platform.
  • FIG. 5 is a flowchart of a service audit notification method provided by an embodiment of the present application.
  • an embodiment of the present application provides a service audit notification method, including:
  • Step 501 receiving a service review request.
  • the service review request is a request sent by the gateway in response to an operation request initiated by the user terminal.
  • the gateway initiates a service review request to the review platform after receiving the operation request initiated by the user terminal.
  • the operation request includes but is not limited to modifying the basic information of the applet (such as name, avatar, profile, industry category, etc.), publishing the applet package, submitting the distribution materials (search/recommendation feed), and opening the payment service, etc.
  • the business audit request is based on the operation request, that is, the business audit request corresponds to the operation request.
  • the types of business audit requests include applet package audit, name audit, industry category audit, avatar and profile audit, (feed/search) material audit, and payment account number audit, etc.
  • Step 502 Acquire and store the audit result for the gateway to generate an audit notification message based on the audit result and the message to be notified.
  • the message to be notified is a message generated by the gateway in response to the service review request.
  • the review platform is reviewed by reviewers. Therefore, after receiving the service review request, the review platform can display the service review request to reviewers through a display device.
  • the reviewers review the review types in the business review request, approve the review types that meet the relevant regulations, and reject the review types that do not meet the relevant regulations.
  • the audit platform after obtaining the audit results of the auditors, the audit platform sends the audit results to the message queue for the gateway to obtain the audit results when needed, or the message queue actively pushes the audit results to the gateway.
  • the audit platform after receiving the service audit request, the audit platform returns the audit task identifier to the gateway, where the audit task identifier is the unique identifier of the audit task.
  • the gateway obtains the message to be notified and the audit task identifier with the audit task identifier. Audit results.
  • the gateway subscribes the corresponding audit result from the message queue according to the audit task identifier, obtains the corresponding to-be-notified message from the to-be-notified message base according to the audit task identifier, and assembles the audit result and the to-be-notified message to obtain the audit notification message.
  • the service audit notification method receives a service audit request, receives an audit result, and stores the audit result for the gateway to generate an audit notification message based on the audit result and the message to be notified; pushes the audit notification message to the user terminal, the The method can support the asynchronous notification mechanism of any business review, while reducing the labor cost of developers, reducing code redundancy, and improving the maintainability of business code.
  • FIG. 6 is a schematic block diagram of a gateway according to an embodiment of the present application.
  • the gateway provided by the embodiment of the present application includes:
  • the submitting module 601 is configured to send a service audit request to the audit platform in response to an operation request of the user terminal, and generate a message to be notified based on the audit task identifier returned by the audit platform.
  • the push module 602 is configured to generate an audit notification message based on the obtained audit result and the message to be notified, and push the audit notification message to the user terminal.
  • audit results are obtained from a message queue.
  • the auditing platform After the auditing platform obtains the auditing result, it stores the auditing result in the message queue, and after receiving the auditing result, the message queue transmits the auditing result to the push module 602 .
  • the pushing unit 602 may actively pull the audit result from the message queue according to preset conditions. For example, the time for pulling is preset to be from 8:00 to 18:00 every day, the time interval for pulling is 30 minutes, and the push unit 602 pulls the audit results according to the preset time and time interval.
  • the submission module 700 includes:
  • the review unit 701 is configured to send a service review request to the review platform.
  • the review unit 701 sends a service review request to the review platform based on the operation request initiated by the user terminal.
  • the user terminal is a terminal used by the applet developer or the third-party service provider to develop the applet. Users develop or modify Mini Programs to enrich Mini Program capabilities, such as Mini Program package management, basic information settings, information flow/search material services, order/payment services, message services, etc. All developments and modifications need to be reviewed by the review platform.
  • the operation request includes but is not limited to modifying the basic information of the applet (such as name, avatar, profile, industry category, etc.), publishing the applet package, submitting the distribution materials (search/recommendation feed), and opening the payment service, etc.
  • business audit request corresponds to the operation request relative to the operation request
  • different operation requests correspond to different business audit requests.
  • Business review requests include but are not limited to small program package review, name review, industry category review, avatar and profile review, (recommended/search) material review, payment account review, etc.
  • the first generating unit 702 is configured to generate a message to be notified based on the audit task identifier returned by the audit platform.
  • the audit platform after receiving the service audit request from the gateway, the audit platform returns the audit task identifier to the gateway.
  • the audit task identifier is an identifier assigned by the audit platform to the business audit request.
  • the first generating unit 702 After the gateway receives the audit task identifier, the first generating unit 702 generates a message to be notified.
  • the first generating unit 702 obtains an audit notification template based on the type of the operation request, and generates a pending notification based on the user ID, the audit task identifier, the time for submitting the business audit, the audit notification template, the operation parameters, and the audit result message item. notification message.
  • the user identity identifier is a unique identifier representing the user identity.
  • the time to submit the business review is the time when the review unit submits the review task to the review platform.
  • Audit notification templates can be configured in advance, and notification templates are configured separately for each operation type. Each notification template can include an Approval Pass sub-template and an Approval Reject sub-template.
  • the operation parameter is the requested content in the operation request, and the operation parameter is different according to the operation type. For example, when publishing the applet package, it is necessary to provide the parameters of the applet package identifier (package_id) and the applet package version (package_version), and when modifying the applet name, the parameter of the applet name (app_name) needs to be provided.
  • the audit result message item is the item used to populate the audit result. In the message to be notified generated by the first generating unit 702, the audit result message item is empty.
  • the submission module 601 further includes an authentication unit configured to authenticate the identity of the user terminal.
  • the authentication unit 800 includes:
  • the parsing subunit 801 is configured to parse the operation request to obtain the user identity and the applet identity.
  • the operation request includes the user ID and the applet ID
  • the parsing subunit 801 can obtain the user ID and the applet ID by parsing the operation request.
  • the verification subunit 802 is configured to verify the user's identity based on the user's identity and the applet's identity.
  • the verification subunit 802 verifies the authority relationship with the applet identifier according to the user identity identifier. If the user does not have the operation authority for the applet corresponding to the applet ID, a no-authority message is directly returned to the user terminal; if the user has the operation authority for the applet corresponding to the applet ID, follow-up operations are performed. .
  • the push module 900 includes:
  • the second generating unit 901 is configured to generate an audit notification message based on the obtained audit result and the message to be notified.
  • the audit results include audit approval and audit rejection.
  • the auditing platform gets the auditing result that is approved; when the auditing standards are not met, the auditing platform gets the auditing result that the auditing rejects.
  • the second generating unit 901 fills the audit result into the audit notification message item in the to-be-notified message to generate the audit notification message.
  • the pushing unit 902 is configured to push the audit notification message to the user terminal.
  • the push unit 902 obtains the address of the developer or the third-party service provider from the push address library, and pushes the audit notification message to the developer or the third-party service provider.
  • the push module 1000 includes a second generation unit 1001 , a push unit 1002 and a subscription unit 1003 , wherein the principles and functions of the second generation unit 1001 and the push unit 1002 are the same as those of the second generation unit 901 is the same as the push unit 902, and details are not repeated here.
  • the subscribing unit 1003 is configured to subscribe the audit result from the message queue, and transmit the audit result to the second generating unit.
  • the message queue is a queue for storing audit results.
  • the message queue can be set on the audit platform, or on the gateway, or independent from the audit platform and gateway. Use the message queue to decouple the audit platform and the gateway, so as to achieve the purpose of pushing multiple places at one time.
  • the gateway also includes a notification template repository 1004 configured to store audit notification templates.
  • Audit notification templates may be preconfigured and stored in notification template library 1004 .
  • the audit notification template matches the type of operation request, and each operation type corresponds to two audit notification templates, namely, the audit pass template and the audit rejection template.
  • the setting forms of the review pass template and the review rejection template have been mentioned in the method section of this application, and will not be repeated here.
  • notification template library 1004 can be set in the gateway or in other units or modules independent of the gateway, as long as the notification template can be stored and the notification template library can be accessed by the submission module and the push module.
  • the push address library 1005 is configured to store the push addresses of the user terminal.
  • the push address is an address preconfigured by the user to receive the notification.
  • the applet developer and the third-party service provider can set their respective addresses in the push address library in advance, so that the push module can obtain the address of the applet developer or the third-party service provider when needed.
  • the push address library 1005 can be set in the gateway, or in other units or modules independent of the gateway, as long as the address can be stored and the submission module and the push module can access the push address library.
  • the gateway uses the submission module to send a business audit request to the audit platform after receiving the operation request from the user terminal, and generates a message to be notified based on the audit task identifier returned by the audit platform; the audit result and the to-be-notified message obtained by the push module are used.
  • the message generates an audit notification message, and pushes the audit notification message to the user terminal.
  • the gateway is versatile and can support any type of business audit (such as the audit of small program capabilities), while reducing the labor cost of developers and reducing code redundancy. degree, and improve the maintainability of business code.
  • the embodiments of the present application provide an auditing platform, which can audit the business of an application program, such as the business of a small program.
  • FIG. 11 is a schematic block diagram of an audit platform provided by an embodiment of the present application. As shown in Figure 11, the auditing platform 1100 includes:
  • the receiving module 1101 is configured to receive a service review request.
  • the service review request is a message sent by the gateway in response to the operation request of the user terminal.
  • the obtaining module 1102 is configured to obtain the audit result.
  • the review platform is a manual review by reviewers.
  • the audit result is the result obtained by the auditor after auditing the audit request.
  • the review platform displays the review request to the reviewer, that is, the review items in the review request are displayed, and the reviewer reviews the review item, obtains the review result, and transmits the review result to the review platform.
  • the auditing platform may also conduct auditing in other manners, such as conducting auditing manually combined with machines.
  • the storage module 1103 is configured to store the audit result.
  • the storage module 1103 stores the audit results in the form of a message queue.
  • the storage module 1103 may be set in the audit platform, or may be set in other modules or units independent of the audit platform.
  • the auditing platform further includes:
  • the task identification generation module is configured to return the audit task identification to the gateway.
  • the audit task identifier is the unique identifier of the audit task.
  • the audit platform uses a receiving module to receive a business audit request, an acquisition module to obtain audit results, and a storage module to store the audit results, the audit platform can audit any type of business, and can reduce the cost of gateway developers. reduce labor costs, reduce code redundancy, and improve the maintainability of business code.
  • the service review notification method is further introduced below in combination with the user terminal, the gateway, and the review platform.
  • FIG. 12 is a flowchart of the service audit notification method provided in this embodiment.
  • the business audit notification method includes:
  • Step 1201 the user terminal sends an operation request to the submission module of the gateway.
  • the operation request includes the user ID, the applet identifier, the operation type (name modification), and the name parameter (the new name of the applet).
  • Step 1202 the gateway authenticates the user identity.
  • the gateway parses the user identification and the applet identification from the operation request, and verifies the authority relationship with the applet identification according to the user identification.
  • a verification failure message is returned to the user terminal.
  • a verification passed message is returned to the user terminal, and subsequent steps are performed; or, the subsequent steps are directly performed without returning a verification passed message to the user terminal.
  • Step 1203 the review unit of the gateway sends a business review task to the review platform.
  • the business audit task is the audit task obtained by the gateway based on the operation request.
  • Business audit tasks include applet identification, operation type (name modification), and name parameters.
  • the gateway sends a business audit request to the audit platform.
  • Step 1204 the audit platform returns the audit task identifier to the gateway.
  • the audit platform after receiving the business audit task, the audit platform assigns a unique identifier to the business audit task for use in the subsequent process.
  • Step 1205 the gateway obtains the audit notification template from the notification template library.
  • the audit notification template is a template preset by a developer or a third-party service provider and stored in a notification template library.
  • Step 1206 Generate a to-be-notified message based on the audit task identifier, the user identity identifier, the time for submitting the business audit, the audit notification template, the operation parameters, and the audit result message item.
  • the gateway obtains the audit notification template from the notification template library based on the audit task identifier returned by the audit platform, and generates the pending notification based on the user identifier sent by the user terminal, the time and operation parameters for submitting the business audit, and the audit result message item. information.
  • Step 1207 the audit platform receives the audit result of the auditor.
  • the auditing platform displays the operation parameters to the auditing personnel, and the auditing personnel audits the business auditing request according to the operating parameters, and transmits the auditing result to the auditing platform.
  • Step 1208 the audit platform stores the audit result in the message queue.
  • Step 1209 the gateway obtains the audit result from the message queue.
  • Step 1210 the gateway obtains the corresponding message to be notified from the message database to be notified according to the audit task identifier, and assembles the audit result and the message to be notified to obtain the notification message.
  • Step 1211 the gateway obtains the push address of the user terminal from the push address database.
  • the push address of the user terminal is pre-configured by the user in the push address library.
  • Step 1212 the gateway pushes the notification message to the user terminal according to the push address.
  • the present application further provides an electronic device and a readable storage medium.
  • FIG. 13 is a block diagram of an electronic device for a method for service audit notification according to an embodiment of the present application.
  • electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers.
  • Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices.
  • the components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the application described and/or claimed herein.
  • the electronic device includes: one or more processors 1301, a memory 1302, and interfaces for connecting various components, including a high-speed interface and a low-speed interface.
  • the various components are interconnected using different buses and may be mounted on a common motherboard or otherwise as desired.
  • the processor may process instructions for execution within the electronic device, including storing in or on memory to display a Graphical User Interface (GUI) on an external input/output device, such as a display device coupled to the interface ) instructions for graphics information.
  • GUI Graphical User Interface
  • multiple processors and/or multiple buses may be used with multiple memories and multiple memories, if desired.
  • multiple electronic devices may be connected, each providing some of the necessary operations (eg, as a server array, a group of blade servers, or a multiprocessor system).
  • a processor 1301 is used as an example.
  • the memory 1302 is the non-transitory computer-readable storage medium provided by the present application.
  • the memory stores instructions executable by at least one processor, so that the at least one processor executes the method for service audit notification provided by the present application.
  • the non-transitory computer-readable storage medium of the present application stores computer instructions for causing a computer to execute the method for business audit notification provided by the present application.
  • the memory 1302 can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as program instructions/modules corresponding to the method for service audit notification in the embodiments of the present application.
  • the processor 1301 executes various functional applications and data processing of the server by running the non-transitory software programs, instructions and modules stored in the memory 1302, that is, the method for realizing the service audit notification in the above method embodiments.
  • the memory 1302 may include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function; the stored data area may store data created according to the use of the electronic device notified by the business audit, etc. . Additionally, memory 1302 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 1302 may optionally include memory located remotely from processor 1301, which may be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the electronic device for the method of business audit notification may further include: an input device 1303 and an output device 1304 .
  • the processor 1301 , the memory 1302 , the input device 1303 and the output device 1304 may be connected by a bus or in other ways, and the connection by a bus is taken as an example in FIG. 13 .
  • the input device 1303 can receive input numerical or character information, and generate key signal input related to user settings and function control of the electronic device of the business audit notification method, such as touch screen, keypad, mouse, trackpad, touchpad, and pointer , one or more mouse buttons, trackballs, joysticks and other input devices.
  • Output devices 1304 may include display devices, auxiliary lighting devices (eg, LEDs), haptic feedback devices (eg, vibration motors), and the like.
  • the display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.
  • Various implementations of the systems and techniques described herein can be implemented in digital electronic circuitry, integrated circuit systems, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that The processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.
  • the processor which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.
  • machine-readable medium and “computer-readable medium” refer to any computer program product, apparatus, and/or apparatus for providing machine instructions and/or data to a programmable processor ( For example, magnetic disks, optical disks, memories, programmable logic devices (PLDs), including machine-readable media that receive machine instructions as machine-readable signals.
  • machine-readable signal refers to any signal used to provide machine instructions and/or data to a programmable processor.
  • the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer.
  • a display device eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and pointing device eg, a mouse or trackball
  • Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input) to receive input from the user.
  • the systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user's computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system.
  • the components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
  • a computer system can include clients and servers.
  • Clients and servers are generally remote from each other and usually interact through a communication network.
  • the relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other.
  • An embodiment of the present application provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing service audit notification methods is implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请提供了一种业务审核通知方法，涉及计算机领域，具体涉及云计算和云平台技术领域。具体实现方案为：响应于用户终端的操作请求向审核平台发送业务审核请求；基于所述审核平台返回的审核任务标识生成待通知消息；基于获得的审核结果和所述待通知消息生成审核通知消息；将所述审核通知消息推送至所述用户终端。该方法具有通用性，可以减少开发人员的人力成本，降低代码冗余度，以及提升业务代码的可维护性。本申请还提供了一种网关、电子设备、可读介质。

Description

业务审核通知方法及网关、电子设备、可读介质 技术领域
本申请涉及计算机技术领域，具体涉及云计算和云平台技术，尤其涉及一种业务审核通知方法及网关、电子设备、可读介质。
背景技术
小程序作为一种不需下载安装即可使用的应用，能够节约用户的时间成本和手机内存空间，同时大大降低开发者的研发成本和推广成本。
小程序开发者和第三方服务商为丰富小程序能力，例如小程序包管理、基本信息设置、信息流/搜索物料服务、订单/支付服务、消息服务等，提供了多种接入使用方式，既可以支持通过平台界面来进行操作，也可以通过调用平台提供的开放应用程序编程接口(Application Programming Interface，API)进行能力的使用。
发明内容
根据第一方面，提供了一种业务审核通知方法，包括：
响应于用户终端的操作请求向审核平台发送业务审核请求；
基于所述审核平台返回的审核任务标识生成待通知消息；
基于获得的审核结果和所述待通知消息生成审核通知消息；
将所述审核通知消息推送至所述用户终端。
根据第二方面，提供了一种业务审核通知方法，包括：
接收业务审核请求；其中，所述业务审核请求是网关响应用户终端的操作请求发出的消息；
获取并存储审核结果，以供所述网关基于所述审核结果和待通知消息生 成审核通知消息；其中，所述待通知消息是网关针对所述业务审核请求生成的消息。
根据第三方面，提供了一种网关，包括:
提交模块，被配置为响应于用户终端的操作请求向审核平台发送业务审核请求，以及基于所述审核平台返回的审核任务标识生成待通知消息；
推送模块，被配置为基于获得的审核结果和所述待通知消息生成审核通知消息,并将所述审核通知消息推送至所述用户终端。
根据第四方面，提供了一种电子设备，其包括：
至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；其中，
所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行业务审核通知方法中任一项所述的方法。
根据第五方面，提供了一种存储有计算机指令的非瞬时计算机可读存储介质，所述计算机指令用于使计算机执行上述任意一种业务审核通知方法。
根据第六方面，提供了一种计算机程序产品，包括计算机程序，计算机程序在被处理器执行时实现上述分布式存储方法中任一项所述业务审核通知方法。
本申请提供的业务审核通知方法，响应用户终端发起操作请求向审核平台发送业务审核请求；基于审核平台返回的审核任务标识生成待通知消息；基于审核结果和待通知消息生成审核通知消息；将审核通知消息推送至用户终端，该方法具有通用性，可以支持任何类型的业务审核(如小程序能力的审核)，同时减少开发人员的人力成本，降低代码冗余度，以及提升业务代码的可维护性。
应当理解，本部分所描述的内容并非旨在标识本公开的实施例的关键或 重要特征，也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
附图说明
附图用于更好地理解本方案，不构成对本申请的限定。其中：
图1为本申请实施例提供的一种业务审核通知方法的应用场景示意图；
图2本申请实施例提供的一种业务审核通知方法的流程图；
图3本申请实施例提供的响应用户的操作请求向审核平台发送业务审核请求的流程图；
图4是本申请实施例提供的将审核通知消息推送至用户终端的流程图；
图5为本申请实施例提供的一种业务审核通知方法的流程图；
图6为本申请实施例提供的一种网关的原理框图；
图7为本申请实施例提供的一种提交模块的原理框图；
图8为本申请实施例提供的一种鉴权单元的原理框图；
图9为本申请实施例提供的一种推送模块的原理框图；
图10为本申请实施例提供的另一种推送模块的原理框图；
图11为本申请实施例提供的一种审核平台的原理框图；
图12为本实施例提供的业务审核通知方法的流程图；
图13是用来实现本申请实施例的业务审核通知方法的电子设备的框图。
具体实施方式
以下结合附图对本申请的示范性实施例做出说明，其中包括本申请实施例的各种细节以助于理解，应当将它们认为仅仅是示范性的。因此，本领域普通技术人员应当认识到，可以对这里描述的实施例做出各种改变和修改，而不会背离本申请的范围和精神。同样，为了清楚和简明，以下的描述中省略了对公知功能和结构的描述。
在不冲突的情况下，本申请各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本申请。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
本申请实施例所指的小程序是指不需要下载安装就可以在即时通讯应用上运行的应用程序，通常加载在第三方应用中。大多数对小程序的修改或操作行为需要经过审核平台的人工审核，因此，小程序开发者或第三方服务商在调用开放API网关时无法立刻获取审核结果，需要由异步通知机制来告知审核结果。
然而，目前的开放API网关不能支持异步通知机制，因此，在小程序能力的研发过程中，需要为每一种涉及审核的操作场景，定制化地开发异步通知功能，这既浪费了研发人力，也导致了代码冗余，影响了整体服务端架构的可维护性。而且，由于不同开发人员开发的异步通知代码没有统一机制保证通知消息的必达性，可能存在通知消息的漏推情况，影响了小程序开发者或第三方服务商对小程序能力的使用。
针对开放API网关存在的上述问题，本申请提供一种业务审核通知方法，用以实现API网关调用和异步通知的功能闭环，减少开发人员的人力成本，降低代码冗余度，以及提升业务代码的可维护性。
示例性的，图1为本申请实施例提供的一种业务审核通知方法的应用场景示意图。如图1所示，该应用场景可以包括：至少一个用户终端11、网关 12和审核平台13，用户终端11、网关12和审核平台13通过网络进行通信。其中，用户终端11可以是小程序开发者或第三方服务商使用的终端。小程序开发者和第三方服务商可以在用户终端11开发一个或多个小程序，也可以对已经存在的小程序进行修改。
在一些实施例中，小程序开发者和第三方服务商可以通过小程序开发平台对小程序能力进行修改。小程序开发平台可以是搭载小程序的应用程序(Application，APP)运营方独立运营的平台，也可以是与搭载小程序的APP的运营方具有合作关系的第三方小程序开发平台。可选地，该小程序开发平台也称为小程序开发者工具，其是用于生产小程序和修改小程序的工具。关于小程序开发平台的具体体现形式，本申请不对其进行限定。
网关12接收用户终端11提交的针对小程序能力的操作请求，例如，小程序包发布、修改小程序名称等，并基于操作请求向审核平台发送业务审核请求，以审核小程序的操作请求是否符合相关规定；同时生成待通知消息，以便在获得审核结果后，生成审核通知消息。
审核平台13根据业务审核请求的具体内容，审核小程序能力是否合法，并将审核结果存储于消息队列。在实际应用中，该审核平台13可以是云端服务器。本申请实施例不对审核平台的具体形式进行限定，其可以根据实际需求确定，此处不再赘述。
网关11从消息队列获得审核结果，将审核结果和待通知消息拼接获得审核通知消息，再将审核通知消息发送至用户终端，用户从用户终端可以获知审核结果。
下面，通过具体实施例对本申请的技术方案进行详细说明。需要说明的是，下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
第一方面，本申请实施例提供一种业务审核通知方法，该方法可以应用 于网关，该网关可以是API网关，也可以是其它可用于传输信号的网关。
图2为本申请实施例提供的一种业务审核通知方法的流程图。参照图2，本申请实施例提供的业务审核通知方法，包括：
步骤201，响应于用户终端发起操作请求向审核平台发送业务审核请求。
其中，用户是通过其使用的用户终端发起操作请求。操作请求可以是针对小程序业务的请求，也可以是针对其它应用程序的请求。
在一些实施例中，操作请求包括但不限于修改小程序的基本信息(如名称、头像、简介、行业类目等)、小程序包发布、分发物料提交(搜索/推荐feed)以及支付服务开通等。
为了便于描述，本申请实施例将用户通过用户终端发起操作请求表述为用户终端发起操作请求。其中，用户终端可以是手机、掌上电脑、个人计算机(Personal Computer，PC)机、一体机等具有通讯功能的终端。
在一些实施例中，用户可以是小程序开发者，也可以是第三方服务商。其中，小程序开发者是小程序的所有者或管理者。第三方服务商是小程序开发者授权的第三方服务商或管理者授权的第三方服务商。小程序开发者或管理者可以授权第三方服务商所有使用权限，也可以仅授权部分使用权限。第三方服务商在小程序开发者或管理者的授权权限内对小程序能力进行管理。
在一些实施例中，小程序开发者或管理者在开发、修改小程序能力的研发过程中，需要向审核平台提请审核，以供审核平台审核小程序能力的合法性。
在一些实施例中，小程序平台为丰富小程序能力，例如小程序包管理、基本信息设置、信息流/搜索物料服务、订单/支付服务、消息服务等，提供了多种接入使用方式，既可以通过小程序平台界面进行操作，也可以通过调用小程序平台提供的开放API进行能力的使用。
在一些实施例中，用户向网关发起操作请求，其中，操作请求包括但不 限于修改小程序的基本信息(如名称、头像、简介、行业类目等)、小程序包发布、分发物料提交(搜索/推荐feed)以及支付服务开通等。在操作请求中携带有用户身份标识和应用程序标识。在本实施例中，应用程序标识可以是任意形式的小程序标识。
其中，用户身份标识是用于识别用户身份的标识，小程序标识是用于识别小程序身份的标识。操作类型包括但不限于小程序包、基本信息设置、信息流/搜索物料服务、订单/支付服务和消息服务。操作参数与操作类型相关，每种操作类型会对应不同的参数。例如，在发布小程序包时需要提供小程序包标识(package_id)和小程序包版本(package_version)参数，在修改小程序名称时需要提供小程序名称(app_name)参数。
在一些实施例中，当网关收到用户终端发起的操作请求后，向审核平台发送业务审核请求。审核平台可以通过人工或机器和人工组合的审核方式对小程序进行审核。
其中，审核请求与操作请求相对应。在一些实施例中，审核请求的类型包括但不限于小程序包审核、名称审核、行业类目审核、头像和简介审核、(推荐/搜索)物料审核、支付账号审核等。
步骤202，基于审核平台返回的审核任务标识生成待通知消息。
其中，审核任务标识是审核平台为业务审核请求分配的标识。
在一些实施例中，审核平台收到网关的业务审核请求后，向网关返回审核任务标识。网关收到审核任务标识后，生成待通知消息。
在一些实施例中，待通知消息存储在待通知消息库中，待通知消息涉及的字段包括审核任务标识、用户身份标识、提交业务审核的时间、审核通知模板、操作参数以及审核结果消息项。
其中，审核通知模板可以提前配置，每种操作类型单独配置审核通知模板。每种审核通知模板可以包括审核通过子模板和审核拒绝子模板。
在一些实施例中，审核通知模板可以采用json结构，例如，小程序包审核拒绝子模板可以采用如下格式：
Figure PCTCN2021098031-appb-000001
其中，形如${…}的字符串代表待填充的字段。待填充的字段可以从提交请求参数和审核结果消息中提取相应的字段值来填充。例如，app_id表示小程序标识ID，developer_id和tp_developer_id分别表示开发者标识ID和第三方服务商标识ID，reason字段表示审核失败原因，package_id和package_version分别表示小程序包标识ID和小程序包版本。
步骤203，基于获得的审核结果和待通知消息生成审核通知消息。
其中，审核结果包括审核通过和审核拒绝。例如，当审核平台认为小程序能力符合设定的要求时，审核结果为审核通过。当审核平台认为小程序能力不符合设定要求时，审核结果为审核拒绝。
在一些实施例中，审核平台通过审核员在审核平台的页面上进行人工审核。当审核员认为小程序能力的符合设定的要求时，审核结果为审核通过。当审核员认为小程序能力的不符合设定的要求时，审核结果为审核拒绝。
在一些实施例中，网关将审核结果和待通知消息拼装，生成审核通知消息。例如，网关获得审核结果后，将审核结果添加至待通知消息的对应字段中，获得审核通知消息。
例如，审核通知消息可以采用如下格式：
Figure PCTCN2021098031-appb-000002
其中，小程序的标识为"1452365"，开发者标识为"17328232"，提交审核的时间为"2019-01-14 12:45:10"，审核的类型为"PACKAGE_AUDIT_FAIL"，审核失败的原因是"名称与实际打开后的名称不符"，小程序包的标识是"745815"，小程序包的版本为"1.3.46"。
步骤204，将审核通知消息推送至用户终端。
当网关生成审核通知消息后，将审核通知消息推送至用户终端，用户通过用户终端查看审核结果。
在一些实施例中，如图3所示，响应用户的操作请求向审核平台发送业务审核请求包括：
步骤301，解析操作请求获得用户身份标识和小程序标识。
在一些实施例中，网关收到操作请求后，对操作请求进行解析，获得用户身份、小程序标识、操作类型和操作参数。
其中，操作类型包括但不限于小程序包管理、基本信息设置、信息流/搜索物料服务、订单/支付服务和消息服务。操作参数与操作类型相关，每种操作类型会对应不同的参数。
例如，用户终端发起的操作请求是修改小程序名称的请求，则在操作请 求中包含用户身份标识、小程序标识、操作类型(名称修改)以及名称参数(小程序的新名称)。
在一些实施例中，操作参数还包括时间戳，用于标识对第三方服务商的授权时间，即第三方服务商可以在授权时间内对小程序进行开发和修改。
步骤302，基于用户身份标识和小程序标识对用户身份进行验证。
在一些实施例中，基于用户身份标识和小程序标识对用户身份进行鉴权。例如，网关根据用户身份标识验证与小程序标识的权限关系。若该用户不具有对该小程序标识对应的小程序的操作权限，则直接向用户终端返回无权限消息；若该用户具有对该小程序标识对应的小程序的操作权限，则进行后续操作。
步骤303，在对用户身份验证通过的情况下，向审核平台发送业务审核请求。
在对用户身份验证通过的情况下，网关向审核平台发送业务审核请求。在业务审核请求中包括小程序标识、操作类型(名称修改)以及名称参数(小程序的新名称)。
在一些实施例中，审核平台收到业务审核请求后，向网关返回审核任务标识ID，网关收到审核任务标识后，从通知模板库获得与操作类型对应的审核通知模板，并基于审核通知模板、审核任务标识生成待通知消息，并将待通知消息存储于待通知消息库中。其中，待通知消息包括审核任务标识、用户身份标识、提交业务审核的时间、审核通知模板、操作参数以及审核结果消息项。
在一些实施例中，审核通知模板是预先设置并存储于通知模板库的模板。其中，每个操作类型对应一个审核通知模板。审核通知模板是根据操作类型确定的模板，具有通用性。将审核通知模板存储在通知模板库，在需要时随时提取审核通知模板，可以提高待通知消息生成的效率，而且可以降低 错误的概率。
当网关收到操作请求后，基于操作请求的类型查询审核通知模板库获得与之匹配的审核通知模板，再基于审核任务标识、用户身份标识、提交业务审核的时间、审核通知模板、操作参数以及审核结果消息项生成待通知消息。
在一些实施例中，审核平台对业务审核请求中的待审核内容审核完毕后，将审核结果发送至消息队列中。其中，消息队列是用于存储审核结果的队列，消息队列中的每条消息均包括审核任务标识和审核结果。
在一些实施例中，同一审核结果可能存在一次多推的情况。例如，小程序开发者和第三方服务商都需要获得审核结果，此时，该审核结果不仅要发送给小程序的开发者，还可以发送给第三方服务商。利用消息队列可将网关与审核平台隔离，实现一次审核结果多方推送消费的目的。
在一些实施例中，网关从消息队列中订阅审核结果，并将审核结果和待通知消息拼接获得审核通知消息。
例如，网关依据审核任务标识从消息队列中获得审核结果以及从待通知消息库中获得待通知消息，并将审核结果拼装在待通知消息中的审核结果消息项中，从而获得审核通知消息。
在实际应用中，若出现审核通知消息丢失的情况，需要再次向用户终端推送审核通知消息。将审核结果存储在消息队列中，网关可以多次从消息队列订阅审核结果，以实现向用户终端多次推送审核通知消息，从而有效地避免漏推问题。
在一些实施例中，用户终端存在因网络故障等原因而导致无法接收到审核通知消息，因此，网关可以按照预设的时间间隔、预设的推送次数向用户终端多次推送审核通知消息。例如，预设的最大推送次数为5次，预设的时间间隔为1分钟、5分钟、15分钟、1小时或6小时。网关在向用户终端完成首次推送审核通知消息后，间隔1分钟进行第一次补推；完成第一次补推 后，间隔5分钟进行第二次补推；完成第二次补推后，间隔15分钟进行第三次补推；完成第三次补推后，间隔1小时进行第四次补推；完成第四次补推后，间隔6小时进行第五次补推。通过设置推送次数和推送时间间隔，可以提高推送的成功率。
在一些实施例中，如图4所示，将审核通知消息推送至用户终端，包括：
步骤401，从推送地址库获取用户终端的推送地址。
其中，推送地址库是存储推送地址的数据库。用户终端的地址存储在推送地址库内，以方便网关按照推送地址向用户终端推送审核通知消息。
在一些实施例中，用户通过用户终端将自己的地址预先存储于推送地址库，以供网关在需要时从推送地址库调用。
步骤402，依据推送地址将审核通知消息推送至用户终端。
网关依据审核任务标识从消息队列订阅对应的审核结果，依据审核任务标识从待通知消息库获得对应的待通知消息，并将该审核任务标识对应的审核结果和待通知消息拼装，获得审核通知消息。网关从推送地址库获得用户终端的推送地址，并按照推送地址将审核通知消息发送至用户终端。
在一些实施例中，网关按照推送地址向用户终端多次推送审核通知消息，可以提高推送的成功率。
在一些实施例中，当待通知消息库中的待通知消息在较长时间内未有审核结果的记录，网关可以直接查询审核平台，获得审核结果，并将审核结果和待通知消息拼装后推送至用户终端，从而避免消息漏推。
本实施例提供的业务审核通知方法响应用户终端发起操作请求向审核平台发送业务审核请求；基于审核平台返回的审核任务标识生成待通知消息；获得审核结果，并基于审核结果和待通知消息生成审核通知消息；将审核通知消息推送至用户终端，该方法可以支持任何小程序能力的异步通知机制，同时减少了开发人员的人力成本，降低了代码冗余度，以及提升了业务 代码的可维护性。
第二方面，本申请实施例提供一种业务审核通知方法，该方法应用于审核平台。
图5为本申请实施例提供的一种业务审核通知方法的流程图。参照图5，本申请实施例提供一种业务审核通知方法，包括：
步骤501，接收业务审核请求。
其中，业务审核请求是网关响应用户终端发起的操作请求而发出的请求。
在一些实施例中，网关收到用户终端发起的操作请求后向审核平台发起业务审核请求。其中，操作请求包括但不限于修改小程序的基本信息(如名称、头像、简介、行业类目等)、小程序包发布、分发物料提交(搜索/推荐feed)以及支付服务开通等。业务审核请求基于操作请求，即业务审核请求与操作请求对应，业务审核请求的类型包括小程序包审核、名称审核、行业类目审核、头像和简介审核、(feed/搜索)物料审核以及支付账号审核等。
步骤502，获取并存储审核结果，以供网关基于审核结果和待通知消息生成审核通知消息。
其中，待通知消息是网关针对业务审核请求生成的消息。
在一些实施例中，审核平台是通过审核人员进行审核，因此，审核平台在收到业务审核请求后，可以通过显示装置向审核人员展示业务审核请求。审核人员对业务审核请求中的审核类型进行审核，对符合相关规定的审核类型给予审核通过，对不符合相关规定的审核类型给予审核拒绝。
在一些实施例中，审核平台获得审核人员的审核结果后，将审核结果发送至消息队列，以供网关需要时获取审核结果，或者消息队列主动将审核结果推送至网关。
在一些实施例中，审核平台收到业务审核请求后，向网关返回审核任务 标识，其中，审核任务标识是审核任务的唯一标识，在后续的步骤中，网关以审核任务标识获得待通知消息和审核结果。
例如，网关依据审核任务标识从消息队列中订阅对应的审核结果，以及依据审核任务标识从待通知消息库获得对应的待通知消息，并将审核结果和待通知消息拼装，获得审核通知消息。
本实施例提供的业务审核通知方法，接收业务审核请求，接收审核结果，并将审核结果存储，以供网关基于审核结果和待通知消息生成审核通知消息；将审核通知消息推送至用户终端，该方法可以支持任何业务审核的异步通知机制，同时减少了开发人员的人力成本，降低了代码冗余度，以及提升了业务代码的可维护性。
第三方面，本申请实施例提供一种网关。图6为本申请实施例提供一种网关的原理框图。
参阅图6，本申请实施例提供的网关包括：
提交模块601，被配置为响应于用户终端的操作请求向审核平台发送业务审核请求，以及基于审核平台返回的审核任务标识生成待通知消息。
推送模块602，被配置为基于获得审核结果和待通知消息生成审核通知消息,并将审核通知消息推送至用户终端。
在一些实施例中，审核结果从消息队列中获得。审核平台获得审核结果后，将审核结果存放于消息队列中，消息队列收到审核结果后，将审核结果传送至推送模块602。或者，推送单元602可以按照预设的条件主动从消息队列中拉取审核结果。例如，预先设置拉取的时间为每日8:00至18:00，拉取的时间间隔为30分钟，推送单元602按照该预设时间和时间间隔拉取审核结果。
在一些实施例中，如图7所示，提交模块700包括：
提审单元701，被配置为向审核平台发送业务审核请求。
在一些实施例中，提审单元701基于用户终端发起的操作请求向审核平台发送业务审核请求。
其中，用户终端是小程序开发者或第三方服务商使用的开发小程序的终端。用户为丰富小程序能力，例如小程序包管理、基本信息设置、信息流/搜索物料服务、订单/支付服务、消息服务等，开发或修改小程序。所有的开发和修改都需要经审核平台审核。
其中，操作请求包括但不限于修改小程序的基本信息(如名称、头像、简介、行业类目等)、小程序包发布、分发物料提交(搜索/推荐feed)以及支付服务开通等。
其中，业务审核请求相对于操作请求，与操作请求相对应，不同的操作请求对应不同的业务审核请求。业务审核请求包括但不限于小程序包审核、名称审核、行业类目审核、头像和简介审核、(推荐/搜索)物料审核、支付账号审核等。
第一生成单元702，被配置为基于审核平台返回的审核任务标识生成待通知消息。
在一些实施例中，审核平台收到网关的业务审核请求后，向网关返回审核任务标识。其中，审核任务标识是审核平台为业务审核请求分配的标识。网关收到审核任务标识后，第一生成单元702生成待通知消息。
在一些实施例中，第一生成单元702基于操作请求的类型获得审核通知模板，并基于用户身份标识、审核任务标识、提交业务审核的时间、审核通知模板、操作参数以及审核结果消息项生成待通知消息。
其中，用户身份标识是表示用户身份的唯一标识。提交业务审核的时间是提审单元向审核平台提交审核任务的时间。审核通知模板可以提前配置，每种操作类型单独配置通知模板。每种通知模板可以包括审核通过子模板和审核拒绝子模板。操作参数是操作请求中请求内容，根据操作类型的不同， 操作参数也不相同。例如，在发布小程序包时需要提供小程序包标识(package_id)和小程序包版本(package_version)参数，在修改小程序名称时需要提供小程序名称(app_name)参数。审核结果消息项是用于填充审核结果的项目。第一生成单元702生成的待通知消息中，审核结果消息项为空。
在一些实施例中，提交模块601还进一步包括鉴权单元，被配置为对用户终端的身份进行鉴权。
如图8所示，鉴权单元800包括：
解析子单元801，被配置为解析操作请求，获得用户身份标识和小程序标识。
在一些实施例中，操作请求中包含有用户身份标识和小程序标识，解析子单元801通过解析操作请求，可以获得用户身份标识和小程序标识。
验证子单元802，被配置为基于用户身份标识和小程序标识对用户身份进行验证。
在一些实施例中，验证子单元802根据用户身份标识验证与小程序标识的权限关系。若该用户不具有对该小程序标识对应的小程序的操作权限，则直接向用户终端返回无权限消息；若该用户具有对该小程序标识对应的小程序的操作权限，则进行后续的操作。
如图9所示，推送模块900包括：
第二生成单元901，被配置为基于获得审核结果和待通知消息生成审核通知消息。
其中，审核结果包括审核通过和审核拒绝。当符合审核标准时，审核平台得到审核通过的审核结果；不符审核标准时，审核平台得到审核拒绝的审核结果。
在一些实施例中，第二生成单元901获得审核结果后，将审核结果填入待通知消息中的审核通知消息项，生成审核通知消息。
推送单元902，被配置为将审核通知消息推送至用户终端。
在一些实施例中，推送单元902从推送地址库获得开发者或第三方服务商的地址，并将审核通知消息推送至开发者或第三方服务商。
在一些实施例中，如图10所示，推送模块1000包括第二生成单元1001、推送单元1002和订阅单元1003，其中，第二生成单元1001和推送单元1002的原理和功能与第二生成单元901和推送单元902相同，在此不再赘述。
订阅单元1003，被配置为从消息队列订阅审核结果，并将审核结果传送至第二生成单元。
需要说明的是，消息队列是用于存储审核结果的队列。消息队列可以设置在审核平台，或者设置在网关，也可以设置在独立于审核平台和网关。利用消息队列将审核平台和网关解耦合，从而实现一次推送多地消费的目的。
在一些实施例中，网关还包括通知模板库1004，被配置为存储审核通知模板。审核通知模板可以预先配置并存储在通知模板库1004中。审核通知模板与操作请求的类型相匹配，而且，每个操作类型对应两个审核通知模板，即审核通过模板和审核拒绝模板。审核通过模板和审核拒绝模板的设置形式在本申请的方法部分已经提及，在此不再赘述。
需要说明的是，通知模板库1004可以设置在网关，也可以设置在独立于网关的其它单元或模块中，只要能够存储通知模板，并使提交模块和推送模块能够访问该通知模板库即可。
推送地址库1005，被配置为存储用户终端的推送地址。其中，推送地址是用户预先配置的接收通知的地址。
在一些实施例中，小程序开发者和第三方服务商可以预先将各自的地址设置在推送地址库，以便于推送模块在需要时获得小程序开发者或第三方服务商的地址。
需要说明的是，推送地址库1005可以设置在网关，也可以设置在独立 于网关的其它单元或模块中，只要能够存储地址，并使提交模块和推送模块能够访问该推送地址库即可。
本实施例提供的网关，利用提交模块在收到用户终端的操作请求向审核平台发送业务审核请求，以及基于审核平台返回的审核任务标识生成待通知消息；利用推送模块获得的审核结果和待通知消息生成审核通知消息,并将审核通知消息推送至用户终端，该网关具有通用性，可以支持任何类型的业务审核(如小程序能力的审核)，同时减少开发人员的人力成本，降低代码冗余度，以及提升业务代码的可维护性。
第四方面，本申请实施例提供一种审核平台，该审核平台可以对应用程序的业务进行审核，如对小程序的业务进行审核。
图11为本申请实施例提供的一种审核平台的原理框图。如图11所示，审核平台1100包括：
接收模块1101，被配置为接收业务审核请求。
其中，业务审核请求是网关响应用户终端的操作请求发出的消息。
获取模块1102，被配置为获取审核结果。
在一些实施例中，审核平台是审核人员进行人工审核。审核结果是审核人员对审核请求审核后得到的结果。例如，审核平台向审核人员展示审核请求，即展示审核请求中的审核事项，审核人员对审核事项进行审核，得到审核结果，并将该审核结果传输至审核平台。
在一些实施例中，审核平台还可以通过其他方式进行审核，例如通过人工结合机器的方式进行审核。
存储模块1103，被配置为存储审核结果。
在一些实施例中，存储模块1103以消息队列的形式存储审核结果。存储模块1103可以设置在审核平台，也可以设置在独立于审核平台的其它模块或单元中。
在一些实施例中，审核平台还包括：
任务标识生成模块，被配置为向网关返回审核任务标识。其中，审核任务标识是审核任务的唯一标识。
本申请实施例提供的审核平台，利用接收模块接收业务审核请求，利用获取模块获取审核结果，并利用存储模块存储审核结果，该审核平台可以对任何类型的业务进行审核，而且可以降低网关开发人员的人力成本，降低代码冗余度，以及提升业务代码的可维护性。
为了更好地理解本申请实施例提供的业务审核通知方法，下面结合用户终端、网关和审核平台对业务审核通知方法做进一步介绍。
图12为本实施例提供的业务审核通知方法的流程图。参阅图12所示，业务审核通知方法包括：
步骤1201，用户终端向网关的提交模块发送操作请求。
其中，操作请求包括用户身份标识、小程序标识、操作类型(名称修改)以及名称参数(小程序的新名称)。
步骤1202，网关对用户身份进行鉴权。
在本实施例中，网关从操作请求中解析出用户身份标识、小程序标识，并根据用户身份标识验证与小程序标识的权限关系。当用户身份标识无权限操作时，向用户终端返回验证不通过消息。当用户身份标识有操作权限时，向用户终端返回验证通过消息，并进行后续步骤；或者，直接进行后续步骤，不向用户终端返回验证通过消息。
步骤1203，网关的提审单元向审核平台发送业务审核任务。
业务审核任务是网关基于操作请求得到的审核任务。业务审核任务包括小程序标识、操作类型(名称修改)以及名称参数。在对用户身份验证通过的情况下，网关向审核平台发送业务审核请求。
步骤1204，审核平台向网关返回审核任务标识。
在本实施例中，审核平台收到业务审核任务后，为该业务审核任务分配一个唯一的标识，以供后续流程中使用。
步骤1205，网关从通知模板库获得审核通知模板。
在本实施例中，审核通知模板是开发者或第三方服务商预先设定并存储于通知模板库的模板。
步骤1206，基于审核任务标识、用户身份标识、提交业务审核的时间、审核通知模板、操作参数以及审核结果消息项生成待通知消息。
在本实施例中，网关基于审核平台返回的审核任务标识，从通知模板库获得审核通知模板，结合用户终端发送的用户身份标识、提交业务审核的时间和操作参数以及审核结果消息项生成待通知消息。
步骤1207，审核平台接收审核人员的审核结果。
在本实施例中，审核平台向审核人员展示操作参数，审核人员依据操作参数对业务审核请求进行审核，并将审核结果传送给审核平台。
步骤1208，审核平台将审核结果存储于消息队列中。
步骤1209，网关从消息队列获得审核结果。
步骤1210，网关根据审核任务标识从待通知消息库中获得对应的待通知消息，并将审核结果和待通知消息拼装，获得通知消息。
步骤1211，网关从推送地址库获得用户终端的推送地址。
在本实施例中，用户终端的推送地址是用户预先配置在推送地址库。
步骤1212，网关将通知消息按照推送地址推送给用户终端。
根据本申请的实施例，本申请还提供了一种电子设备和一种可读存储介质。
图13是根据本申请实施例的业务审核通知的方法的电子设备的框图。如图13所示，电子设备旨在表示各种形式的数字计算机，诸如，膝上型计算机、台式计算机、工作台、个人数字助理、服务器、刀片式服务器、大型计 算机、和其它适合的计算机。电子设备还可以表示各种形式的移动装置，诸如，个人数字处理、蜂窝电话、智能电话、可穿戴设备和其它类似的计算装置。本文所示的部件、它们的连接和关系、以及它们的功能仅仅作为示例，并且不意在限制本文中描述的和/或者要求的本申请的实现。
如图13所示，该电子设备包括：一个或多个处理器1301、存储器1302，以及用于连接各部件的接口，包括高速接口和低速接口。各个部件利用不同的总线互相连接，并且可以被安装在公共主板上或者根据需要以其它方式安装。处理器可以对在电子设备内执行的指令进行处理，包括存储在存储器中或者存储器上以在外部输入/输出装置(诸如，耦合至接口的显示设备)上显示图形用户界面(Graphical User Interface，GUI)的图形信息的指令。在其它实施方式中，若需要，可以将多个处理器和/或多条总线与多个存储器和多个存储器一起使用。同样，可以连接多个电子设备，各个设备提供部分必要的操作(例如，作为服务器阵列、一组刀片式服务器、或者多处理器系统)。图13中以一个处理器1301为例。
存储器1302即为本申请所提供的非瞬时计算机可读存储介质。其中，存储器存储有可由至少一个处理器执行的指令，以使至少一个处理器执行本申请所提供的业务审核通知的方法。本申请的非瞬时计算机可读存储介质存储计算机指令，该计算机指令用于使计算机执行本申请所提供的业务审核通知的方法。
存储器1302作为一种非瞬时计算机可读存储介质，可用于存储非瞬时软件程序、非瞬时计算机可执行程序以及模块，如本申请实施例中的业务审核通知的方法对应的程序指令/模块。处理器1301通过运行存储在存储器1302中的非瞬时软件程序、指令以及模块，从而执行服务器的各种功能应用以及数据处理，即实现上述方法实施例中的业务审核通知的方法。
存储器1302可以包括存储程序区和存储数据区，其中，存储程序区可 存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据业务审核通知的电子设备的使用所创建的数据等。此外，存储器1302可以包括高速随机存取存储器，还可以包括非瞬时存储器，例如至少一个磁盘存储器件、闪存器件、或其他非瞬时固态存储器件。在一些实施例中，存储器1302可选包括相对于处理器1301远程设置的存储器，这些远程存储器可以通过网络连接至电子设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
业务审核通知的方法的电子设备还可以包括：输入装置1303和输出装置1304。处理器1301、存储器1302、输入装置1303和输出装置1304可以通过总线或者其他方式连接，图13中以通过总线连接为例。
输入装置1303可接收输入的数字或字符信息，以及产生与业务审核通知方法的电子设备的用户设置以及功能控制有关的键信号输入，例如触摸屏、小键盘、鼠标、轨迹板、触摸板、指示杆、一个或者多个鼠标按钮、轨迹球、操纵杆等输入装置。输出装置1304可以包括显示设备、辅助照明装置(例如，LED)和触觉反馈装置(例如，振动电机)等。该显示设备可以包括但不限于，液晶显示器(LCD)、发光二极管(LED)显示器和等离子体显示器。在一些实施方式中，显示设备可以是触摸屏。
此处描述的系统和技术的各种实施方式可以在数字电子电路系统、集成电路系统、专用ASIC(专用集成电路)、计算机硬件、固件、软件、和/或它们的组合中实现。这些各种实施方式可以包括：实施在一个或者多个计算机程序中，该一个或者多个计算机程序可在包括至少一个可编程处理器的可编程系统上执行和/或解释，该可编程处理器可以是专用或者通用可编程处理器，可以从存储系统、至少一个输入装置、和至少一个输出装置接收数据和指令，并且将数据和指令传输至该存储系统、该至少一个输入装置、和该至少一个输出装置。
这些计算程序(也称作程序、软件、软件应用、或者代码)包括可编程处理器的机器指令，并且可以利用高级过程和/或面向对象的编程语言、和/或汇编/机器语言来实施这些计算程序。如本文使用的，术语“机器可读介质”和“计算机可读介质”指的是用于将机器指令和/或数据提供给可编程处理器的任何计算机程序产品、设备、和/或装置(例如，磁盘、光盘、存储器、可编程逻辑装置(PLD))，包括，接收作为机器可读信号的机器指令的机器可读介质。术语“机器可读信号”指的是用于将机器指令和/或数据提供给可编程处理器的任何信号。
为了提供与用户的交互，可以在计算机上实施此处描述的系统和技术，该计算机具有：用于向用户显示信息的显示装置(例如，CRT(阴极射线管)或者LCD(液晶显示器)监视器)；以及键盘和指向装置(例如，鼠标或者轨迹球)，用户可以通过该键盘和该指向装置来将输入提供给计算机。其它种类的装置还可以用于提供与用户的交互；例如，提供给用户的反馈可以是任何形式的传感反馈(例如，视觉反馈、听觉反馈、或者触觉反馈)；并且可以用任何形式(包括声输入、语音输入或者、触觉输入)来接收来自用户的输入。
可以将此处描述的系统和技术实施在包括后台部件的计算系统(例如，作为数据服务器)、或者包括中间件部件的计算系统(例如，应用服务器)、或者包括前端部件的计算系统(例如，具有图形用户界面或者网络浏览器的用户计算机，用户可以通过该图形用户界面或者该网络浏览器来与此处描述的系统和技术的实施方式交互)、或者包括这种后台部件、中间件部件、或者前端部件的任何组合的计算系统中。可以通过任何形式或者介质的数字数据通信(例如，通信网络)来将系统的部件相互连接。通信网络的示例包括：局域网(LAN)、广域网(WAN)和互联网。
计算机系统可以包括客户端和服务器。客户端和服务器一般远离彼此并 且通常通过通信网络进行交互。通过在相应的计算机上运行并且彼此具有客户端-服务器关系的计算机程序来产生客户端和服务器的关系。
本申请实施例提供一种计算机可读介质，其上存储有计算机程序，程序被处理器执行时实现上述任意一种业务审核通知方法。
应该理解，可以使用上面所示的各种形式的流程，重新排序、增加或删除步骤。例如，本发申请中记载的各步骤可以并行地执行也可以顺序地执行也可以不同的次序执行，只要能够实现本申请公开的技术方案所期望的结果，本文在此不进行限制。
上述具体实施方式，并不构成对本申请保护范围的限制。本领域技术人员应该明白的是，根据设计要求和其他因素，可以进行各种修改、组合、子组合和替代。任何在本申请的精神和原则之内所作的修改、等同替换和改进等，均应包含在本申请保护范围之内。

Claims (21)

  1. 一种业务审核通知方法，其特征在于，包括：
    响应于用户终端的操作请求向审核平台发送业务审核请求；
    基于所述审核平台返回的审核任务标识生成待通知消息；
    基于获得的审核结果和所述待通知消息生成审核通知消息；
    将所述审核通知消息推送至所述用户终端。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于用户终端的操作请求向审核平台发送业务审核请求，包括：
    解析所述操作请求，获得用户身份标识和小程序标识；
    基于所述用户身份标识和所述小程序标识对用户身份进行验证；
    在所述用户身份验证通过的情况下，向所述审核平台发送业务审核请求。
  3. 根据权利要求1所述的方法，其特征在于，所述基于所述审核平台返回的审核任务标识生成待通知消息，包括：
    基于所述操作请求的操作类型从通知模板库获得与所述操作类型匹配的审核通知模板；
    基于所述审核通知模板和所述审核任务标识生成待通知消息。
  4. 根据权利要求3所述的方法，其特征在于，在所述基于所述审核通知模板生成待通知消息之后，所述方法还包括：
    将所述待通知消息存储于待通知消息库。
  5. 根据权利要求4所述的方法，其特征在于，所述基于所述审核结果和所述待通知消息生成审核通知消息，包括：
    基于所述审核任务标识从所述待通知消息库获得所述审核任务标识对应的所述待通知消息；
    将所述审核结果与所述待通知消息拼装，生成所述审核通知消息。
  6. 根据权利要求1所述的方法，其特征在于，所述待通知消息涉及的字段包括审核任务标识、用户身份标识、操作参数、提交所述业务审核请求的时间、审核通知模板和审核结果消息项；其中，所述审核通知模板是与所述操作类型相匹配的模板；所述审核结果消息项是用于填充所述审核结果的字段。
  7. 根据权利要求1所述的方法，其特征在于，所述审核结果是从消息队列获得；其中，所述消息队列是用于存储所述审核结果的队列。
  8. 根据权利要求1所述的方法，其特征在于，所述将所述审核通知消息推送至所述用户终端，包括：
    从推送地址库获取所述用户终端的推送地址；
    依据所述推送地址将所述审核通知消息推送至所述用户终端。
  9. 根据权利要求1所述的方法，其特征在于，所述将所述审核通知消息推送至所述用户终端，包括：
    按照预设的推送次数和预设的时间间隔向所述用户终端推送所述审核通知消息。
  10. 一种业务审核通知方法，其特征在于，包括：
    接收业务审核请求；其中，所述业务审核请求是网关响应用户终端的操作请求发出的消息；
    获取并存储审核结果，以供所述网关基于所述审核结果和待通知消息生 成审核通知消息；其中，所述待通知消息是网关针对所述业务审核请求生成的消息。
  11. 根据权利要求10所述的方法，其特征在于，所述获取并存储所述审核结果，包括：
    接收所述的审核结果，将所述审核结果存储于消息队列中。
  12. 根据权利要求10所述的方法，其特征在于，在所述接收业务审核请求之后，所述方法还包括：
    向网关返回审核任务标识，其中，所述审核任务标识是审核任务的唯一标识。
  13. 一种网关，其特征在于，包括:
    提交模块，被配置为响应于用户终端的操作请求向审核平台发送业务审核请求，以及基于所述审核平台返回的审核任务标识生成待通知消息；
    推送模块，被配置为基于获得的审核结果和所述待通知消息生成审核通知消息,并将所述审核通知消息推送至所述用户终端。
  14. 根据权利要求13所述的网关，其特征在于，所述提交模块包括：
    提审单元，被配置为向审核平台发送业务审核请求；
    第一生成单元，被配置为基于所述审核平台返回的审核任务标识生成待通知消息。
  15. 根据权利要求14所述的网关，其特征在于，所述提交模块包括：
    解析单元，被配置为解析所述操作请求，获得用户身份标识和小程序标识；
    验证单元，被配置为基于所述用户身份标识和所述小程序标识对用户身 份进行验证。
  16. 根据权利要求13所述的网关，其特征在于，所述推送模块包括：
    第二生成单元，被配置为基于获得的审核结果和所述待通知消息生成审核通知消息；
    推送单元，被配置为将所述审核通知消息推送至所述用户终端。
  17. 根据权利要求16所述的网关，其特征在于，所述推送模块还包括：
    订阅单元，被配置为从消息队列订阅所述审核结果，并将所述审核结果传送至所述第二生成单元；其中，所述消息队列是用于存储审核结果的队列。
  18. 根据权利要求13所述的网关，其特征在于，还包括：
    通知模板库，被配置为存储审核通知模板，其中，所述审核通知模板与所述操作请求的类型相对应；
    推送地址库，被配置为存储所述用户终端的推送地址，其中，所述推送地址是用户预先配置的接收通知的地址。
  19. 一种电子设备，其特征在于，包括：
    至少一个处理器；以及
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求1-9或10-12中任一项所述的方法。
  20. 一种存储有计算机指令的非瞬时计算机可读存储介质，其特征在于，所述计算机指令用于使所述计算机执行权利要求1-9或10-12中任一项所述的方法。
  21. 一种计算机程序产品，包括计算机程序，所述计算机程序在被处理器执行时实现根据权利要求1-9或10-12中任一项所述的方法。
PCT/CN2021/098031 2020-10-10 2021-06-03 业务审核通知方法及网关、电子设备、可读介质 WO2022073354A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020217042890A KR102651156B1 (ko) 2020-10-10 2021-06-03 트랜잭션 체크 알림 방법 및 게이트웨이, 전자 기기, 판독 가능 매체, 컴퓨터 프로그램 제품
EP21823720.4A EP4009611A4 (en) 2020-10-10 2021-06-03 SERVICE AUDIT NOTIFICATION PROCESS, GATEWAY, ELECTRONIC DEVICE AND READABLE MEDIA
US17/597,084 US20230188620A1 (en) 2020-10-10 2021-06-03 Method of notifying of business audit, gateway, electronic device, and readable medium
JP2021578248A JP2023501850A (ja) 2020-10-10 2021-06-03 ビジネス監査報知方法及びゲートウェイ、電子機器、読取可能な媒体及びコンピュータプログラム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011081246.8A CN112333239B (zh) 2020-10-10 2020-10-10 业务审核通知方法及网关、电子设备、可读介质
CN202011081246.8 2020-10-10

Publications (1)

Publication Number Publication Date
WO2022073354A1 true WO2022073354A1 (zh) 2022-04-14

Family

ID=74313401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/098031 WO2022073354A1 (zh) 2020-10-10 2021-06-03 业务审核通知方法及网关、电子设备、可读介质

Country Status (2)

Country Link
CN (1) CN112333239B (zh)
WO (1) WO2022073354A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114900379A (zh) * 2022-04-28 2022-08-12 北京百度网讯科技有限公司 一种消息通知方法、装置、电子设备及存储介质
CN116579749A (zh) * 2023-07-13 2023-08-11 浙江保融科技股份有限公司 基于rpa机器人的审核流程的运行方法和装置
CN116862458A (zh) * 2023-06-06 2023-10-10 云南墨斯墨人才服务有限公司 职称申报流程动态审核方法、装置、系统及存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112333239B (zh) * 2020-10-10 2023-07-18 百度(中国)有限公司 业务审核通知方法及网关、电子设备、可读介质
CN113011769B (zh) * 2021-03-31 2023-05-09 建信金融科技有限责任公司 事项预约方法及装置
CN113034118B (zh) * 2021-04-25 2024-03-05 中国工商银行股份有限公司 业务审核方法、系统、可读存储介质和计算机程序产品
CN114124435B (zh) * 2021-09-26 2023-06-09 烽火通信科技股份有限公司 对服务接口调用进行人工授权执行的方法、系统及装置
CN114640511B (zh) * 2022-03-04 2024-01-19 上海医栗医疗科技有限公司 应用接口监控平台

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1917431A (zh) * 2006-09-15 2007-02-21 中辉世纪传媒发展有限公司 一种广电网络增值服务系统及其双向业务实现方法
US20170338949A1 (en) * 2014-08-29 2017-11-23 Box, Inc. Enhanced remote key management for an enterprise in a cloud-based environment
CN111667334A (zh) * 2020-04-27 2020-09-15 苏宁云计算有限公司 审核失败订单处理方法、装置、计算机设备和存储介质
CN112333239A (zh) * 2020-10-10 2021-02-05 百度(中国)有限公司 业务审核通知方法及网关、电子设备、可读介质

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004213422A (ja) * 2003-01-06 2004-07-29 Hitachi Ltd 情報検索サーバ及び情報検索方法
JP2005078168A (ja) * 2003-08-28 2005-03-24 Canon Inc 情報処理装置、情報処理方法、プログラム及び記憶媒体
CN102142087B (zh) * 2010-02-02 2015-09-09 腾讯数码（天津）有限公司 一种用户认证的方法及装置
US20130110943A1 (en) * 2011-11-02 2013-05-02 Apple Inc. Notification and reminder generation, distribution, and storage system
KR20140076827A (ko) * 2012-12-13 2014-06-23 에스케이플래닛 주식회사 애플릿 관리 시스템 및 방법
CN106254214B (zh) * 2016-08-04 2019-05-07 武汉票据交易中心有限公司 一种银行业务信息的主动通知系统及主动通知方法
CN107733776B (zh) * 2016-08-12 2020-12-29 阿里巴巴集团控股有限公司 账号激活消息的模板配置方法及装置
CN110113252B (zh) * 2019-04-30 2021-08-17 上海连尚网络科技有限公司 一种小程序通知消息的处理方法、设备和计算机存储介质
CN110134605A (zh) * 2019-05-16 2019-08-16 北京达佳互联信息技术有限公司 验证代码的方法、装置、计算机设备和存储介质
CN110221904B (zh) * 2019-06-17 2023-08-04 腾讯科技（深圳）有限公司 一种业务流程控制方法
CN110472934A (zh) * 2019-07-26 2019-11-19 东软集团股份有限公司 业务审核方法、装置、可读存储介质和电子设备
CN111324335A (zh) * 2020-01-04 2020-06-23 厦门二五八网络科技集团股份有限公司 一种小程序的创建方法及装置
CN111310092B (zh) * 2020-01-17 2023-11-14 西安理工大学 一种基于微信小程序的数据采集平台
CN111400310B (zh) * 2020-02-23 2023-03-21 中国平安财产保险股份有限公司 基于审批链配置的数据监控方法、服务器及存储介质
CN111597113B (zh) * 2020-05-18 2023-08-15 北京百度网讯科技有限公司 小程序的验证方法、装置、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1917431A (zh) * 2006-09-15 2007-02-21 中辉世纪传媒发展有限公司 一种广电网络增值服务系统及其双向业务实现方法
US20170338949A1 (en) * 2014-08-29 2017-11-23 Box, Inc. Enhanced remote key management for an enterprise in a cloud-based environment
CN111667334A (zh) * 2020-04-27 2020-09-15 苏宁云计算有限公司 审核失败订单处理方法、装置、计算机设备和存储介质
CN112333239A (zh) * 2020-10-10 2021-02-05 百度(中国)有限公司 业务审核通知方法及网关、电子设备、可读介质

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114900379A (zh) * 2022-04-28 2022-08-12 北京百度网讯科技有限公司 一种消息通知方法、装置、电子设备及存储介质
CN114900379B (zh) * 2022-04-28 2024-02-06 北京百度网讯科技有限公司 一种消息通知方法、装置、电子设备及存储介质
CN116862458A (zh) * 2023-06-06 2023-10-10 云南墨斯墨人才服务有限公司 职称申报流程动态审核方法、装置、系统及存储介质
CN116579749A (zh) * 2023-07-13 2023-08-11 浙江保融科技股份有限公司 基于rpa机器人的审核流程的运行方法和装置
CN116579749B (zh) * 2023-07-13 2023-11-14 浙江保融科技股份有限公司 基于rpa机器人的审核流程的运行方法和装置

Also Published As

Publication number Publication date
CN112333239A (zh) 2021-02-05
CN112333239B (zh) 2023-07-18

Similar Documents

Publication Publication Date Title
WO2022073354A1 (zh) 业务审核通知方法及网关、电子设备、可读介质
US10778542B2 (en) Rule based subscription cloning
US20210073051A1 (en) Late connection binding for bots
US10909186B2 (en) Multi-tenant customizable composites
EP3155576B1 (en) Providing a subscription for a service using an existing subscription
US11036696B2 (en) Resource allocation for database provisioning
US20150363724A1 (en) Reusable anonymous subscription
JP2022104926A (ja) グループベースコミュニケーションシステムを介して外部アクションを開始するシステム及び方法
US20210342203A1 (en) Api manager
WO2022000869A1 (zh) 小程序的批量处理方法、装置、电子设备以及可读存储介质
US11734454B2 (en) Method for providing applet service capability, electronic device, and storage medium
US11010200B2 (en) Finite state machine driven workflows
CN112764726A (zh) 一种数据合成的方法和装置
US20220012050A1 (en) Mini program batch processing method and apparatus, electronic device, and readable storage medium
US20210342194A1 (en) Computer resource allocation based on categorizing computing processes
EP4009611A1 (en) Service auditing notification method, gateway, electronic device, and readable medium
US11023672B1 (en) Dynamic service injection
CN114237765B (zh) 功能组件处理方法、装置、电子设备和介质
US20230145461A1 (en) Receiving and integrating external data into a graphical user interface of an issue tracking system
US20230267163A1 (en) Runtime completion of web component metadata
CN114666387A (zh) 接口管理系统、方法、存储介质及计算机设备
CN114189365A (zh) 基于字段映射的通用多租户业务授权方法和装置
Nguyen et al. NotX service oriented multi-platform notification system

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021578248

Country of ref document: JP

Kind code of ref document: A

Ref document number: 20217042890

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021823720

Country of ref document: EP

Effective date: 20211222

NENP Non-entry into the national phase

Ref country code: DE