WO2020000727A1 - 服务器、业务数据校验的方法及存储介质 - Google Patents

服务器、业务数据校验的方法及存储介质 Download PDF

Info

Publication number
WO2020000727A1
WO2020000727A1 PCT/CN2018/107715 CN2018107715W WO2020000727A1 WO 2020000727 A1 WO2020000727 A1 WO 2020000727A1 CN 2018107715 W CN2018107715 W CN 2018107715W WO 2020000727 A1 WO2020000727 A1 WO 2020000727A1
Authority
WO
WIPO (PCT)
Prior art keywords
attribute information
verification
verified
class
deleted
Prior art date
Application number
PCT/CN2018/107715
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 平安科技(深圳)有限公司
Publication of WO2020000727A1 publication Critical patent/WO2020000727A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/103Formatting, i.e. changing of presentation of documents

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a server, a method for verifying service data, and a storage medium.
  • the verification process for transmitted data is composed of front-end verification and background verification.
  • developers usually manually verify the uploaded data. If the R & D process is collaboratively developed by multiple developers, the data of this process is likely to be customized by the developer, and the data is not uniform. During the verification, a separate calibration is required for each developer's customized data. Verification, the workload is large, and the verification work is tedious; especially when the uploaded data is large and all verifications must be performed, it is likely to cause the problem of less verification of some data or verification errors, affecting the operation of the system .
  • the purpose of this application is to provide a server, a method for verifying business data, and a storage medium, which aim to provide a unified standard for verifying business data and reduce the workload and errors of verification.
  • the present application provides a server.
  • the server includes a memory and a processor connected to the memory.
  • the memory stores a processing system that can run on the processor.
  • the processing system is When the processor executes, the following steps are implemented:
  • the predetermined architecture layer is used to call the interface of the automatic verification class, and according to the attribute information of the automatic verification class and the verification corresponding to each attribute information
  • the standard information verifies the business object to be verified.
  • the present application further provides a method for verifying service data.
  • the method for verifying service data includes:
  • the predetermined architecture layer is used to call the interface of the automatic verification class, and corresponding to each attribute information of the automatic verification class and each attribute information.
  • the verification standard information verifies the business object to be verified.
  • the verifying the business object to be verified according to each attribute information of the automatic verification class and verification standard information corresponding to each attribute information specifically includes:
  • the business object to be verified is returned to the corresponding client.
  • the present application also provides a computer-readable storage medium on which a processing system is stored.
  • a processing system is executed by a processor, the steps of the method for verifying service data described above are implemented.
  • the beneficial effect of this application is that in this application, by constructing an automatic verification class in the background and defining the attribute information and corresponding verification standard information that need to be verified, after uploading business data on the client, the business data is first encapsulated as a pending correction.
  • Business object to be verified and then call the interface of the automatic verification class, and automatically verify the business object to be verified through the attribute information of the automatic verification class and the corresponding verification standard information.
  • This application defines a dynamic-based The automatic verification class of the agent mode provides a unified standard for the verification of business data, realizes automatic verification of business data, and reduces the workload and errors of verification.
  • FIG. 1 is a schematic diagram of an optional application environment of each embodiment of the present application.
  • FIG. 2 is a schematic diagram of a hardware architecture of an embodiment of the server in FIG. 1;
  • FIG. 3 is a schematic flowchart of a first embodiment of a method for verifying service data of this application
  • FIG. 4 is a schematic flowchart of a second embodiment of a method for verifying service data of this application.
  • FIG. 1 is a schematic diagram of an application environment of a preferred embodiment of a method for verifying service data of the present application.
  • the application environment diagram includes a server 1 and a terminal device 2.
  • the server 1 may perform data interaction with the terminal device 2 through a suitable technology such as a network and a near field communication technology.
  • the terminal device 2 includes, but is not limited to, any electronic product that can interact with a user through a keyboard, a mouse, a remote control, a touch pad, or a sound control device, such as a personal computer, a tablet computer, or a desktop computer. , Laptop, server, etc.
  • the server 1 is a device capable of automatically performing numerical calculation and / or information processing according to an instruction set or stored in advance.
  • the server 1 may be a computer, a single network server, a server group composed of multiple network servers, or a cloud composed of a large number of hosts or network servers based on cloud computing.
  • Cloud computing is a type of distributed computing.
  • a super virtual computer composed of a group of loosely coupled computers.
  • the server 1 may include, but is not limited to, a memory 11, a processor 12, and a network interface 13 that may be communicatively connected to each other through a system bus.
  • Running processing system it should be noted that FIG. 2 only shows the server 1 with components 11-13, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.
  • the memory 11 includes a memory and at least one type of readable storage medium.
  • the memory provides a cache for the operation of the server 1;
  • the readable storage medium may be, for example, a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static random access memory (SRAM) ,
  • Non-volatile storage media such as read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, etc.
  • the readable storage medium may be an internal storage unit of the server 1, such as a hard disk of the server 1.
  • the non-volatile storage medium may also be an external storage device of the server 1, For example, a plug-in hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash memory card (Flash card), etc. provided on the server 1.
  • the readable storage medium of the memory 11 is generally used to store an operating system and various types of application software installed on the server 1, for example, to store program code of a processing system in an embodiment of the present application.
  • the memory 11 can also be used to temporarily store various types of data that have been output or will be output.
  • the processor 12 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or another data processing chip.
  • the processor 12 is generally used to control the overall operations of the server 1, for example, to perform control and processing related to data interaction or communication with the terminal device 2.
  • the processor 12 is configured to run program code or process data stored in the memory 11, for example, to run a processing system.
  • the network interface 13 may include a wireless network interface or a wired network interface.
  • the network interface 13 is generally used to establish a communication connection between the server 1 and other electronic devices.
  • the network interface 13 is mainly used to connect the server 1 and one or more terminal devices 2 to establish a data transmission channel and a communication connection between the server 1 and one or more terminal devices 2.
  • the processing system is stored in the memory 11 and includes at least one computer-readable instruction stored in the memory 11, which can be executed by the processor 12 to implement the methods of the embodiments of the present application; and
  • the at least one computer-readable instruction may be divided into different logic modules according to different functions implemented by each part thereof.
  • the predetermined architecture layer is preferably a control layer or a business processing layer.
  • An automatic verification class is constructed in the predetermined architecture layer. Specifically, the attribute information to be verified and the verification standard information corresponding to each attribute information are sorted.
  • the attribute information is, for example, email, phone number, age, etc.
  • the standard information is, for example, non-empty check, mail format check, etc.
  • the check standard information of the phone number is, for example, data length, first digit value, etc.
  • the check standard information of age is, for example, data length.
  • a unified verification standard is provided for the verification of business data in the background, that is, the verification of business data in the background can be verified directly through this automatic verification class, without the need for different developers.
  • the server receives service data uploaded by each client, and the service data may include mail, phone number, age, and the like.
  • packaging the service data as a business object to be verified specifically includes:
  • one piece of business data may include one or more attributes, for example, the email may also include attributes such as phone number and name, and analyze each Whether the attribute is an attribute that needs to be verified. If so, add a verification flag to the attribute, for example, the verification flag is "1". Then, based on the business data, the attributes of the business data and the verification flag are encapsulated as pending. Inspected business objects.
  • the business object to be verified encapsulated by the service data of the phone number is, for example: ⁇ phone, 131 ..., flag (1) ⁇ .
  • the predetermined architecture layer is used to call the interface of the automatic verification class, and according to the attribute information of the automatic verification class and the verification corresponding to each attribute information
  • the standard information verifies the business object to be verified.
  • the control layer or the business processing layer calls an interface of an automatic verification class located at the layer, and according to the automatic verification class, The verified business object performs automatic verification.
  • verifying the business object to be verified according to each attribute information of the automatic verification class and verification standard information corresponding to each attribute information specifically includes:
  • the business object to be verified is returned to the corresponding client.
  • the business object to be verified is compared with each attribute information of the automatic verification class, and whether each attribute information has the same attribute information as the business object to be verified, such as
  • the business object is a telephone number, and the attribute information of the telephone number is also included in each attribute information of the automatic verification class, so the business object to be verified can be verified; if the business object to be verified is a phone number, and There is no phone number in the attribute information of the automatic verification class, so the business object to be verified cannot be verified, and the business object to be verified can be returned to the corresponding client for manual operation. Confirm or verify, or modify the automatic verification class, so that the modified automatic verification class can re-verify the business object to be verified.
  • the mail is verified. Perform a non-empty check to determine whether the message is an empty message. If it is a non-empty message, check the next attribute. If the attribute information is a message and the standard verification information is a message format check, the message is checked. Check the format of the email, including checking the format of the recipient, subject, and body of the email, and determine whether it is valid. If it is valid, check the next attribute.
  • the verification fails, the business object to be verified corresponding to the attribute information may be returned to the corresponding client for manual confirmation or verification, or the automatic verification class may be modified so that The modified automatic verification class can re-verify the business object to be verified.
  • this application constructs an automatic verification class in the background and defines the attribute information and corresponding verification standard information that need to be verified.
  • the business data After uploading the business data on the client, the business data is first encapsulated as a pending correction.
  • Business object to be verified After uploading the business data on the client, the business data is first encapsulated as a pending correction.
  • Business object to be verified and then call the interface of the automatic verification class, and automatically verify the business object to be verified through the attribute information of the automatic verification class and the corresponding verification standard information.
  • This application defines a dynamic-based The automatic verification class of the agent mode provides a unified standard for the verification of business data, realizes automatic verification of business data, and reduces the workload and errors of verification.
  • a registration function in the automatic verification class is called, and the registration function is added
  • the new attribute information and the verification standard information corresponding to the new attribute information are used to register the new attribute information and the verification standard information value corresponding to the new attribute information into the automatic verification class.
  • the new attribute information is, for example, an address
  • the verification standard information corresponding to the address is, for example, the data length of the address.
  • a registration function in an automatic verification class is called to add new attribute information and verification standard information corresponding to the new attribute information to the automatic verification class.
  • the automatic verification The class can verify the new attribute information, and it is not necessary to write complex verification logic for the new attribute information. In addition to providing a unified standard for the verification of business data, it achieves automatic verification of business data. It further reduces calibration workload and calibration errors.
  • the delete function in the automatic verification class is called, and the attribute information to be deleted and the verification standard information corresponding to the attribute information to be deleted are added to the delete function, so that the attribute information to be deleted and the attribute to be deleted are added.
  • the check standard information value corresponding to the message is deleted from the automatic check class.
  • the specific method includes calling a delete function in the automatic verification class, and then deleting the function. Add the attribute information to be deleted and the corresponding verification standard information, and execute the delete function to delete.
  • Automatic verification class improve verification efficiency.
  • FIG. 3 is a schematic flowchart of an embodiment of a method for verifying service data of this application.
  • the method for verifying service data includes the following steps:
  • step S1 an automatic verification class is constructed in a predetermined architectural layer in the background, and the attribute information to be verified and the verification standard information corresponding to each attribute information are defined in the automatic verification class;
  • the predetermined architecture layer is preferably a control layer or a business processing layer.
  • An automatic verification class is constructed in the predetermined architecture layer. Specifically, the attribute information to be verified and the verification standard information corresponding to each attribute information are sorted.
  • the attribute information is, for example, email, phone number, age, etc.
  • the standard information is, for example, non-empty check, mail format check, etc.
  • the check standard information of the phone number is, for example, data length, first digit value, etc.
  • the check standard information of age is, for example, data length.
  • a unified verification standard is provided for the verification of business data in the background, that is, the verification of business data in the background can be verified directly through this automatic verification class, without the need for different developers.
  • Step S2 Receive business data uploaded by each client, and package the business data as a business object to be verified;
  • the server receives service data uploaded by each client, and the service data may include mail, phone number, age, and the like.
  • packaging the service data as a business object to be verified specifically includes:
  • one piece of business data may include one or more attributes, for example, the email may also include attributes such as phone number and name, and analyze each Whether the attribute is an attribute that needs to be verified. If so, add a verification flag to the attribute, for example, the verification flag is "1". Then, based on the business data, the attributes of the business data and the verification flag are encapsulated as pending for calibration Inspected business objects.
  • the business object to be verified encapsulated by the service data of the phone number is, for example: ⁇ phone, 131 ..., flag (1) ⁇ .
  • Step S3 when the business object to be verified is transmitted to the predetermined architecture layer, the interface of the automatic verification class is called by using the predetermined architecture layer, and corresponding to each attribute information and attribute information of the automatic verification class The verification standard information of the verification is performed on the business object to be verified.
  • the control layer or the business processing layer calls an interface of an automatic verification class located at the layer, and according to the automatic verification class, The verified business object performs automatic verification.
  • verifying the business object to be verified according to each attribute information of the automatic verification class and verification standard information corresponding to each attribute information specifically includes:
  • the business object to be verified is returned to the corresponding client.
  • the business object to be verified is compared with each attribute information of the automatic verification class, and whether each attribute information has the same attribute information as the business object to be verified, such as
  • the business object is a telephone number, and the attribute information of the telephone number is also included in each attribute information of the automatic verification class, so the business object to be verified can be verified; if the business object to be verified is a phone number, and There is no phone number in the attribute information of the automatic verification class, so the business object to be verified cannot be verified, and the business object to be verified can be returned to the corresponding client for manual operation. Confirm or verify, or modify the automatic verification class, so that the modified automatic verification class can re-verify the business object to be verified.
  • the mail is verified. Perform a non-empty check to determine whether the message is an empty message. If it is a non-empty message, check the next attribute. If the attribute information is a message and the standard verification information is a message format check, the message is checked. Check the format of the email, including checking the format of the recipient, subject, and body of the email, and determine whether it is valid. If it is valid, check the next attribute.
  • the verification fails, the business object to be verified corresponding to the attribute information may be returned to the corresponding client for manual confirmation or verification, or the automatic verification class may be modified so that The modified automatic verification class can re-verify the business object to be verified.
  • this application constructs an automatic verification class in the background and defines the attribute information and corresponding verification standard information that need to be verified.
  • the business data After uploading the business data on the client, the business data is first encapsulated as a pending correction.
  • Business object to be verified After uploading the business data on the client, the business data is first encapsulated as a pending correction.
  • Business object to be verified and then call the interface of the automatic verification class, and automatically verify the business object to be verified through the attribute information of the automatic verification class and the corresponding verification standard information.
  • This application defines a dynamic-based The automatic verification class of the agent mode provides a unified standard for the verification of business data, realizes automatic verification of business data, and reduces the workload and errors of verification.
  • step S3 the method further includes: step S4, calling a registration function in the automatic verification class, in the registration function Add new attribute information and verification standard information corresponding to the new attribute information to register the new attribute information and the verification standard information value corresponding to the new attribute information into the automatic verification class.
  • the new attribute information is, for example, an address
  • the verification standard information corresponding to the address is, for example, the data length of the address.
  • a registration function in an automatic verification class is called to add new attribute information and verification standard information corresponding to the new attribute information to the automatic verification class.
  • the automatic verification The class can verify the new attribute information, and it is not necessary to write complex verification logic for the new attribute information. In addition to providing a unified standard for the verification of business data, it achieves automatic verification of business data. It further reduces calibration workload and calibration errors.
  • the method further includes: calling a delete function in the automatic verification class, and adding attribute information to be deleted and the wait function to the delete function.
  • the verification standard information corresponding to the deleted attribute information is to delete the attribute information to be deleted and the verification standard information value corresponding to the attribute information to be deleted from the automatic verification class.
  • the specific method includes calling a delete function in the automatic verification class, and then deleting the function. Add the attribute information to be deleted and the corresponding verification standard information, and execute the delete function to delete.
  • Automatic verification class improve verification efficiency.
  • the present application also provides a computer-readable storage medium on which a processing system is stored.
  • a processing system is executed by a processor, the steps of the method for verifying service data described above are implemented.
  • the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
  • Implementation Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请涉及一种服务器、业务数据校验的方法及存储介质,该方法包括:在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。本申请能够为业务数据的校验提供统一标准,并减少校验工作量及校验错误。

Description

服务器、业务数据校验的方法及存储介质
本申请要求于2018年6月29日提交中国专利局,申请号为201810694755.4、发明名称为“服务器、业务数据校验的方法及存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及一种服务器、业务数据校验的方法及存储介质。
背景技术
目前,在项目开发中,对于传输数据的校验处理是由前端校验和后台校验组成。在后台对数据的校验中,一般是由开发人员手动对上传的数据进行校验的处理。如果研发过程是由多位开发人员协作开发的,那么这个过程的数据很可能是开发人员自定义的,数据并不统一,在校验时需要针对每位开发人员自定义的数据进行单独的校验,工作量较大,校验工作繁琐;特别是当上传的数据量较大且必须全部进行校验时,很可能会导致少校验某些数据或者校验错误的问题,影响系统的运行。
发明内容
本申请的目的在于提供一种服务器、业务数据校验的方法及存储介质,旨在为业务数据的校验提供统一标准,并减少校验工作量及校验错误。
为实现上述目的,本申请提供一种服务器,所述服务器包括存储器及与所述存储器连接的处理器,所述存储器中存储有可在所述处理器上运行的处理系统,所述处理系统被所述处理器执行时实现如下步骤:
在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
为实现上述目的,本申请还提供一种业务数据校验的方法,所述业务数据校验的方法包括:
S1,在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
S2,接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
S3,当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
优选地,所述根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
本申请还提供一种计算机可读存储介质,所述计算机可读存储介质上存储有处理系统,所述处理系统被处理器执行时实现上述的业务数据校验的方法的步骤。
本申请的有益效果是:本申请通过在后台构建自动校验类并定义所需要 校验的属性信息及对应的校验标准信息,在客户端上传业务数据后,首先对业务数据封装为待校验的业务对象,然后调用自动校验类的接口,通过自动校验类的各属性信息及对应的校验标准信息对待校验的业务对象进行自动校验,本申请通过在后台定义一个基于动态代理模式的自动校验类,为业务数据的校验提供统一标准,实现了对业务数据的自动化校验,且减少校验工作量及校验错误。
附图说明
图1为本申请各个实施例一可选的应用环境示意图;
图2是图1中服务器一实施例的硬件架构的示意图;
图3为本申请业务数据校验的方法第一实施例的流程示意图;
图4为本申请业务数据校验的方法第二实施例的流程示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处所描述的具体实施例仅用以解释本申请,并不用于限定本申请。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
需要说明的是,在本申请中涉及“第一”、“第二”等的描述仅用于描述目的,而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此,限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外,各个实施例之间的技术方案可以相互结合,但是必须是以本领域普通技术人员能够实现为基础,当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在,也不在本申请要求的 保护范围之内。
参阅图1所示,是本申请业务数据校验的方法的较佳实施例的应用环境示意图。该应用环境示意图包括服务器1及终端设备2。服务器1可以通过网络、近场通信技术等适合的技术与终端设备2进行数据交互。
所述终端设备2包括,但不限于,任何一种可与用户通过键盘、鼠标、遥控器、触摸板或者声控设备等方式进行人机交互的电子产品,例如,个人计算机、平板电脑、台式计算机、笔记本、服务器等等的固定终端。终端设备2上有客户端,通过客户端将数据传输给服务器1,以将数据在后台进行校验。
所述服务器1是一种能够按照事先设定或者存储的指令,自动进行数值计算和/或信息处理的设备。所述服务器1可以是计算机、也可以是单个网络服务器、多个网络服务器组成的服务器组或者基于云计算的由大量主机或者网络服务器构成的云,其中云计算是分布式计算的一种,由一群松散耦合的计算机集组成的一个超级虚拟计算机。
如图2所示,在本实施例中,服务器1可包括,但不仅限于,可通过系统总线相互通信连接的存储器11、处理器12、网络接口13,存储器11存储有可在处理器12上运行的处理系统。需要指出的是,图2仅示出了具有组件11-13的服务器1,但是应理解的是,并不要求实施所有示出的组件,可以替代的实施更多或者更少的组件。
其中,存储器11包括内存及至少一种类型的可读存储介质。内存为服务器1的运行提供缓存;可读存储介质可为如闪存、硬盘、多媒体卡、卡型存储器(例如,SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等的非易失性存储介质。在一些实施例中,可读存储介质可以是服务器1的内部 存储单元,例如该服务器1的硬盘;在另一些实施例中,该非易失性存储介质也可以是服务器1的外部存储设备,例如服务器1上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。本实施例中,存储器11的可读存储介质通常用于存储安装于服务器1的操作系统和各类应用软件,例如存储本申请一实施例中的处理系统的程序代码等。此外,存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器12在一些实施例中可以是中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器12通常用于控制所述服务器1的总体操作,例如执行与所述终端设备2进行数据交互或者通信相关的控制和处理等。本实施例中,所述处理器12用于运行所述存储器11中存储的程序代码或者处理数据,例如运行处理系统等。
所述网络接口13可包括无线网络接口或有线网络接口,该网络接口13通常用于在所述服务器1与其他电子设备之间建立通信连接。本实施例中,网络接口13主要用于将服务器1与一个或多个终端设备2相连,在服务器1与一个或多个终端设备2之间建立数据传输通道和通信连接。
所述处理系统存储在存储器11中,包括至少一个存储在存储器11中的计算机可读指令,该至少一个计算机可读指令可被处理器器12执行,以实现本申请各实施例的方法;以及,该至少一个计算机可读指令依据其各部分所实现的功能不同,可被划为不同的逻辑模块。
在一实施例中,上述处理系统被所述处理器12执行时实现如下步骤:
在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
其中,预定的架构层优选为控制层或业务处理层。在该预定的架构层中 构建自动校验类,具体地,整理需要校验的属性信息及各属性信息对应的校验标准信息,属性信息例如为邮件、电话号码、年龄等,邮件的校验标准信息例如为非空校验、邮件格式校验等,电话号码的校验标准信息例如为数据长度、首位数值等,年龄的校验标准信息例如为数据长度。然后,在该自动校验类中定义所整理的属性信息及各属性信息对应的校验标准信息,以最终生成该自动校验类。
其中,通过自动校验类,为业务数据在后台的校验提供统一的校验标准,即业务数据在后台的校验可以直接通过该自动校验类进行校验,不需要针对不同开发人员自定义的业务数据编写相应的校验逻辑。
接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
其中,服务器接收各客户端上传的业务数据,该业务数据中可能包括邮件、电话号码、年龄等。在一实施例中,将该业务数据封装为待校验的业务对象具体包括:
获取该业务数据的属性(例如,该业务数据的属性为邮件还是电话号码等),一条业务数据中可能包括一个或者多个属性,例如,邮件中可能还包括电话号码、姓名等属性,分析各个属性是否为需要校验的属性,如果是,则为该属性添加校验标志,例如校验标志为“1”,然后,基于该业务数据、该业务数据的属性及校验标志封装为待校验的业务对象。电话号码的业务数据封装的待校验的业务对象例如为:{phone,131…,flag(1)}。
当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
其中,当该待校验的业务对象传输至控制层或者业务处理层时,该控制层或者业务处理层调用位于该层的自动校验类的接口,并根据该自动校验类 对该待校验的业务对象执行自动校验。
在一实施例中,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
其中,该待校验的业务对象与该自动校验类的各属性信息进行一一比对,分析各属性信息中是否有与该待校验的业务对象一致的属性信息,例如待校验的业务对象为电话号码,而自动校验类的各属性信息中也有电话号码这一属性信息,则可以对该待校验的业务对象进行校验;如果待校验的业务对象为电话号码,而自动校验类的各属性信息中没有电话号码这一属性信息,则不能对该待校验的业务对象进行校验,可将该待校验的业务对象返回至对应的客户端,供人工进行确认或校验,或者对该自动校验类进行修改,以使得修改后的自动校验类能够重新对该待校验的业务对象进行校验。
其中,根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验的过程中,例如,在判断属性信息为邮件的校验标准信息为非空校验时,则对邮件进行非空校验,以判断该邮件是否为空邮件,如果为非空邮件则进行下一属性的校验;在判断属性信息为邮件的校验标准信息为邮件格式校验时,则对邮件的格式进行校验,包括对邮件的收件人、主题及正文的格式进行校验,并判断是否合法,如果合法则进行下一属性的校验。此外,如果本次校验失败,则可将该属性信息对应的待校验的业务对象返回至对应的客户端,供人工进行确认或校验,或者对该自动校验类进行修改,以使得修改后的自动校验类能够重新对该待校验的业务对象进行校验。
与现有技术相比,本申请通过在后台构建自动校验类并定义所需要校验的属性信息及对应的校验标准信息,在客户端上传业务数据后,首先对业务数据封装为待校验的业务对象,然后调用自动校验类的接口,通过自动校验类的各属性信息及对应的校验标准信息对待校验的业务对象进行自动校验,本申请通过在后台定义一个基于动态代理模式的自动校验类,为业务数据的校验提供统一标准,实现了对业务数据的自动化校验,且减少校验工作量及校验错误。
在一优选的实施例中,在上述实施例的基础上,所述处理系统被所述处理器执行时,还实现如下步骤:调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
其中,新的属性信息例如为地址,地址对应的校验标准信息例如为地址的数据长度。本实施例通过调用自动校验类中的注册函数,以在该自动校验类中添加新的属性信息及该新的属性信息对应的校验标准信息,执行该注册函数后,该自动校验类即可对该新的属性信息进行校验,不需要编写该新的属性信息复杂的校验逻辑,在为业务数据的校验提供统一标准,实现了对业务数据的自动化校验之外,还进一步减少校验工作量及校验错误。
在一优选的实施例中,在上述实施例的基础上,所述处理系统被所述处理器执行时,还实现如下步骤:
调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
其中,如果业务数据中的某一属性信息不再需要进行校验,可以将其从自动校验类中进行删除,具体做法包括,通过调用该自动校验类中的删除函 数,在该删除函数中添加待删除的属性信息及对应的校验标准信息,执行该删除函数,以进行删除,在为业务数据的校验提供统一标准,实现了对业务数据的自动化校验之外,还简化该自动校验类,提高校验效率。
如图3所示,图3为本申请业务数据校验的方法一实施例的流程示意图,该业务数据校验的方法包括以下步骤:
步骤S1,在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
其中,预定的架构层优选为控制层或业务处理层。在该预定的架构层中构建自动校验类,具体地,整理需要校验的属性信息及各属性信息对应的校验标准信息,属性信息例如为邮件、电话号码、年龄等,邮件的校验标准信息例如为非空校验、邮件格式校验等,电话号码的校验标准信息例如为数据长度、首位数值等,年龄的校验标准信息例如为数据长度。然后,在该自动校验类中定义所整理的属性信息及各属性信息对应的校验标准信息,以最终生成该自动校验类。
其中,通过自动校验类,为业务数据在后台的校验提供统一的校验标准,即业务数据在后台的校验可以直接通过该自动校验类进行校验,不需要针对不同开发人员自定义的业务数据编写相应的校验逻辑。
步骤S2,接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
其中,服务器接收各客户端上传的业务数据,该业务数据中可能包括邮件、电话号码、年龄等。在一实施例中,将该业务数据封装为待校验的业务对象具体包括:
获取该业务数据的属性(例如,该业务数据的属性为邮件还是电话号码等),一条业务数据中可能包括一个或者多个属性,例如,邮件中可能还包括电话号码、姓名等属性,分析各个属性是否为需要校验的属性,如果是, 则为该属性添加校验标志,例如校验标志为“1”,然后,基于该业务数据、该业务数据的属性及校验标志封装为待校验的业务对象。电话号码的业务数据封装的待校验的业务对象例如为:{phone,131…,flag(1)}。
步骤S3,当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
其中,当该待校验的业务对象传输至控制层或者业务处理层时,该控制层或者业务处理层调用位于该层的自动校验类的接口,并根据该自动校验类对该待校验的业务对象执行自动校验。
在一实施例中,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
其中,该待校验的业务对象与该自动校验类的各属性信息进行一一比对,分析各属性信息中是否有与该待校验的业务对象一致的属性信息,例如待校验的业务对象为电话号码,而自动校验类的各属性信息中也有电话号码这一属性信息,则可以对该待校验的业务对象进行校验;如果待校验的业务对象为电话号码,而自动校验类的各属性信息中没有电话号码这一属性信息,则不能对该待校验的业务对象进行校验,可将该待校验的业务对象返回至对应的客户端,供人工进行确认或校验,或者对该自动校验类进行修改,以使得修改后的自动校验类能够重新对该待校验的业务对象进行校验。
其中,根据该属性信息对应的校验标准信息对该待校验的业务对象进行 校验的过程中,例如,在判断属性信息为邮件的校验标准信息为非空校验时,则对邮件进行非空校验,以判断该邮件是否为空邮件,如果为非空邮件则进行下一属性的校验;在判断属性信息为邮件的校验标准信息为邮件格式校验时,则对邮件的格式进行校验,包括对邮件的收件人、主题及正文的格式进行校验,并判断是否合法,如果合法则进行下一属性的校验。此外,如果本次校验失败,则可将该属性信息对应的待校验的业务对象返回至对应的客户端,供人工进行确认或校验,或者对该自动校验类进行修改,以使得修改后的自动校验类能够重新对该待校验的业务对象进行校验。
与现有技术相比,本申请通过在后台构建自动校验类并定义所需要校验的属性信息及对应的校验标准信息,在客户端上传业务数据后,首先对业务数据封装为待校验的业务对象,然后调用自动校验类的接口,通过自动校验类的各属性信息及对应的校验标准信息对待校验的业务对象进行自动校验,本申请通过在后台定义一个基于动态代理模式的自动校验类,为业务数据的校验提供统一标准,实现了对业务数据的自动化校验,且减少校验工作量及校验错误。
在一优选的实施例中,如图4所示,在上述实施例的基础上,所述步骤S3之后,还包括:步骤S4,调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
其中,新的属性信息例如为地址,地址对应的校验标准信息例如为地址的数据长度。本实施例通过调用自动校验类中的注册函数,以在该自动校验类中添加新的属性信息及该新的属性信息对应的校验标准信息,执行该注册函数后,该自动校验类即可对该新的属性信息进行校验,不需要编写该新的属性信息复杂的校验逻辑,在为业务数据的校验提供统一标准,实现了对业务数据的自动化校验之外,还进一步减少校验工作量及校验错误。
在一优选的实施例中,在上述实施例的基础上,所述步骤S3之后,还包括:调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
其中,如果业务数据中的某一属性信息不再需要进行校验,可以将其从自动校验类中进行删除,具体做法包括,通过调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及对应的校验标准信息,执行该删除函数,以进行删除,在为业务数据的校验提供统一标准,实现了对业务数据的自动化校验之外,还简化该自动校验类,提高校验效率。
本申请还提供一种计算机可读存储介质,所述计算机可读存储介质上存储有处理系统,所述处理系统被处理器执行时实现上述的业务数据校验的方法的步骤。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种服务器,其特征在于,所述服务器包括存储器及与所述存储器连接的处理器,所述存储器中存储有可在所述处理器上运行的处理系统,所述处理系统被所述处理器执行时实现如下步骤:
    在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
    接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
    当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
  2. 根据权利要求1所述的服务器,其特征在于,所述根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
    分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
    若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
    若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
  3. 根据权利要求1所述的服务器,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  4. 根据权利要求2所述的服务器,其特征在于,所述处理系统被所述处 理器执行时,还实现如下步骤:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  5. 根据权利要求1所述的服务器,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
  6. 根据权利要求2所述的服务器,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
  7. 根据权利要求1或2所述的服务器,其特征在于,所述预定的架构层为控制层或业务处理层。
  8. 一种业务数据校验的方法,其特征在于,所述业务数据校验的方法包括:
    S1,在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
    S2,接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
    S3,当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
  9. 根据权利要求8所述的业务数据校验的方法,其特征在于,所述根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
    分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
    若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
    若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
  10. 根据权利要求8所述的业务数据校验的方法,其特征在于,所述步骤S3之后,还包括:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  11. 根据权利要求9所述的业务数据校验的方法,其特征在于,所述步骤S3之后,还包括:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  12. 根据权利要求6所述的业务数据校验的方法,其特征在于,所述步骤S3之后,还包括:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
  13. 根据权利要求9所述的业务数据校验的方法,其特征在于,所述步骤S3之后,还包括:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
  14. 根据权利要求8或9所述的业务数据校验的方法,其特征在于,所述预定的架构层为控制层或业务处理层。
  15. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有处理系统,所述处理系统被处理器执行时实现如下步骤:
    在后台预定的架构层中构建自动校验类,并在该自动校验类中定义所需要校验的各属性信息及各属性信息对应的校验标准信息;
    接收各客户端上传的业务数据,将该业务数据封装为待校验的业务对象;
    当该待校验的业务对象传输至该预定的架构层时,利用该预定的架构层调用该自动校验类的接口,根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验。
  16. 根据权利要求15所述的计算机可读存储介质,其特征在于,所述根据该自动校验类的各属性信息及各属性信息对应的校验标准信息对该待校验的业务对象进行校验,具体包括:
    分析各属性信息中是否有与该待校验的业务对象一致的属性信息;
    若各属性信息中有与该待校验的业务对象一致的属性信息,则根据该属性信息对应的校验标准信息对该待校验的业务对象进行校验;
    若各属性信息中无与该待校验的业务对象一致的属性信息,或者当校验失败时,则将该待校验的业务对象返回至对应的客户端。
  17. 根据权利要求15所述的计算机可读存储介质,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及 该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  18. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的注册函数,在该注册函数中添加新的属性信息及该新的属性信息对应的校验标准信息,以将新的属性信息及该新的属性信息对应的校验标准信息值注册至该自动校验类中。
  19. 根据权利要求15所述的计算机可读存储介质,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
  20. 根据权利要求16所述的计算机可读存储介质,其特征在于,所述处理系统被所述处理器执行时,还实现如下步骤:
    调用该自动校验类中的删除函数,在该删除函数中添加待删除的属性信息及该待删除的属性信息对应的校验标准信息,以将该待删除的属性信息及该待删除的属性信息对应的校验标准信息值从该自动校验类中删除。
PCT/CN2018/107715 2018-06-29 2018-09-26 服务器、业务数据校验的方法及存储介质 WO2020000727A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810694755.4A CN109062870A (zh) 2018-06-29 2018-06-29 服务器、业务数据校验的方法及存储介质
CN201810694755.4 2018-06-29

Publications (1)

Publication Number Publication Date
WO2020000727A1 true WO2020000727A1 (zh) 2020-01-02

Family

ID=64818289

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107715 WO2020000727A1 (zh) 2018-06-29 2018-09-26 服务器、业务数据校验的方法及存储介质

Country Status (2)

Country Link
CN (1) CN109062870A (zh)
WO (1) WO2020000727A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109788052B (zh) * 2019-01-02 2021-11-26 郑州云海信息技术有限公司 一种服务器配置远程查询方法、装置、终端及存储介质
CN113778535B (zh) * 2021-08-10 2024-02-23 济南浪潮数据技术有限公司 一种云主机操作校验的方法、系统、设备和存储介质
CN114978426B (zh) * 2022-05-18 2024-05-03 国微集团(深圳)有限公司 数据传输方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050228711A1 (en) * 1999-10-21 2005-10-13 International Business Machines Corporation Database driven workflow management system for generating output material based on customer input
CN103077185A (zh) * 2012-12-18 2013-05-01 厦门雅迅网络股份有限公司 一种基于对象的自定义扩展信息的方法
CN103559261A (zh) * 2013-11-04 2014-02-05 深圳中兴网信科技有限公司 服务器、终端、数据校验系统和方法
CN104391934A (zh) * 2014-11-21 2015-03-04 深圳市银雁金融配套服务有限公司 数据校验方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7895574B2 (en) * 2005-01-14 2011-02-22 Microsoft Corporation System and methods for automatically verifying management packs
CN103106186A (zh) * 2013-01-22 2013-05-15 百度在线网络技术(北京)有限公司 一种表单校验方法及系统
CN105426164B (zh) * 2014-09-04 2018-12-14 北大方正集团有限公司 一种数据的校验方法及浏览器
CN105808701B (zh) * 2015-11-23 2018-07-24 江苏中威科技软件系统有限公司 实现表单自动化验证及多系统间通讯的方法及系统
CN105930409A (zh) * 2016-04-18 2016-09-07 深圳市永兴元科技有限公司 基于动态生成规则的数据校验方法及装置
CN107656910A (zh) * 2016-07-26 2018-02-02 北京京东尚科信息技术有限公司 用于生成表单的方法和装置
CN107451460A (zh) * 2017-06-28 2017-12-08 努比亚技术有限公司 接口处理方法、设备、服务器及计算机可读存储介质
CN107346590A (zh) * 2017-08-29 2017-11-14 深圳志合天成科技有限公司 一种自助终端机

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050228711A1 (en) * 1999-10-21 2005-10-13 International Business Machines Corporation Database driven workflow management system for generating output material based on customer input
CN103077185A (zh) * 2012-12-18 2013-05-01 厦门雅迅网络股份有限公司 一种基于对象的自定义扩展信息的方法
CN103559261A (zh) * 2013-11-04 2014-02-05 深圳中兴网信科技有限公司 服务器、终端、数据校验系统和方法
CN104391934A (zh) * 2014-11-21 2015-03-04 深圳市银雁金融配套服务有限公司 数据校验方法和装置

Also Published As

Publication number Publication date
CN109062870A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
WO2018188437A1 (zh) 一种多租户数据隔离方法、装置及系统
CN108055343B (zh) 用于机房的数据同步方法及装置
WO2019148722A1 (zh) 电子装置、数据迁移及调用方法及存储介质
WO2020024419A1 (zh) 业务场景的测试方法、电子装置及可读存储介质
WO2019169759A1 (zh) 模拟接口的创建装置、方法及计算机可读存储介质
WO2020000727A1 (zh) 服务器、业务数据校验的方法及存储介质
WO2019136800A1 (zh) 业务处理方法、装置、设备及计算机可读存储介质
CN108388622B (zh) Api接口动态生成方法、装置、计算机设备及存储介质
CN108287708B (zh) 一种数据处理方法、装置、服务器及计算机可读存储介质
WO2019019640A1 (zh) 订单信息的模拟处理方法、装置、存储介质和计算机设备
TW201439792A (zh) 資料庫訪問系統及方法
WO2021137757A1 (en) Authority management method and apparatus, and electronic device, and storage medium thereof
WO2019127864A1 (zh) 电子装置、基于springmvc的数据接口及其说明自动生成方法及存储介质
CN111290806A (zh) 应用程序接口的调用方法、装置、计算机设备及存储介质
WO2019148721A1 (zh) 电子装置、互联网服务系统风险预警方法及存储介质
WO2022068316A1 (zh) 数据对账方法、装置、设备及存储介质
CN108846129B (zh) 存储数据访问方法、装置及存储介质
WO2019100690A1 (zh) 电子装置、测试的方法、系统及计算机可读存储介质
US11237761B2 (en) Management of multiple physical function nonvolatile memory devices
CN104317660B (zh) 一种银行参数管理系统
CN113360299B (zh) 事务处理方法及相关产品
CN113112270B (zh) 基于区块链的数据组织方法
CN113852610A (zh) 报文处理方法、装置、计算机设备和存储介质
CN114428815A (zh) 数据存储方法、装置、电子设备和计算机可读介质
CN114637672A (zh) 自动化数据测试方法、装置、计算机设备及存储介质

Legal Events

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

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18924109

Country of ref document: EP

Kind code of ref document: A1