Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In the technical scheme of the disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the user accord with the regulations of related laws and regulations, and the public order colloquial is not violated.
FIG. 1 illustrates an exemplary architecture 100 in which the data verification methods and apparatus of the present disclosure may be applied.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The communication connection between the terminal devices 101, 102, 103 constitutes a topology network, the network 104 being the medium for providing the communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The terminal devices 101, 102, 103 interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may be hardware devices or software supporting network connections for data interaction and data processing. When the terminal device 101, 102, 103 is hardware, it may be various electronic devices supporting network connection, information acquisition, interaction, display, processing, etc., including but not limited to smartphones, tablet computers, electronic book readers, laptop and desktop computers, etc. When the terminal devices 101, 102, 103 are software, they can be installed in the above-listed electronic devices. It may be implemented as a plurality of software or software modules, for example, for providing distributed services, or as a single software or software module. The present invention is not particularly limited herein.
The server 105 may be a server that provides various services, for example, a background processing server that receives a data upload request sent by the terminal devices 101, 102, 103, collects device information, location information, and time information of the terminal devices, performs multiple checks on the data upload request, and determines whether to receive target data corresponding to the data upload request according to the obtained check result. As an example, the server 105 may be a cloud server.
It should be noted that, the server may be hardware, or may be software. When the server is hardware, the server may be implemented as a distributed server cluster formed by a plurality of servers, or may be implemented as a single server. When the server is software, it may be implemented as a plurality of software or software modules (e.g., software or software modules for providing distributed services), or as a single software or software module. The present invention is not particularly limited herein.
It should also be noted that, the data verification method provided by the embodiment of the present disclosure may be executed by a server, may be executed by a terminal device, or may be executed by the server and the terminal device in cooperation with each other. Accordingly, each part (for example, each unit) included in the data verification device may be all disposed in the server, all disposed in the terminal device, or disposed in the server and the terminal device respectively.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. When the electronic device on which the data verification method is run does not need to perform data transmission with other electronic devices, the system architecture may include only the electronic device (e.g., server or terminal device) on which the data verification method is run.
Referring to fig. 2, fig. 2 is a flowchart of a data verification method according to an embodiment of the disclosure, where the flowchart 200 includes the following steps:
in step 201, in response to determining that the data upload request of the target device is received, device information, location information, and time information of the target device are collected.
In this embodiment, the execution body of the data verification method (for example, the terminal device or the server in fig. 1) may receive the data upload request of the target device, and collect the device information, the location information, and the time information of the target device in response to determining that the data upload request of the target device is received.
The data upload request may be request information requesting to upload target data, which may be any form of data carrying any content. As an example, the target data may be various word, excel, powerPoint format data in the instant communication field, and may be video data in the short video field.
The device information of the target device may include hardware information and software information of the device, where the hardware information may be, for example, identification information capable of distinguishing the device, specifically, IMEI (International Mobile Equipment Identity ).
The location information is the location information of the location where the target device sent the data upload request. As an example, the location information of the target device may be determined based on GPS (Global Positioning System ).
The time information is the time information when the target device sends out the data uploading request. As an example, after receiving the data upload request, the execution subject determines the local time, and determines the determined local time as time information of the target device.
In some optional implementations of this embodiment, the foregoing execution body may execute step 201 by:
First, in response to determining that a data uploading request of a target device is received, front-end verification is performed on target data corresponding to the data uploading request.
Front-end verification, namely front-end validity verification, is performed, after the front-end selects target data, the target data can be temporarily cached in the front-end, and the front-end can acquire data information such as file names, file sizes, file contents and the like. The front end analyzes the file content to perform validity verification, wherein the verification content comprises file extension names, file sizes, file numbers, empty files and the like.
Taking a file extension as an example, the extension of the uploaded data can be checked through a javascript for performing extension check, and the extension has a white list form and a black list form. When the white list mode is adopted, the extension of the target data is in the white list, namely passing the verification, and when the black list mode is adopted, the extension of the target data is not in the black list, namely passing the verification.
Then, in response to determining that the data upload request passes the front-end verification, device information, location information, and time information are collected.
In the implementation mode, the front-end verification and the multiple verification based on the equipment information, the position information and the time information are combined, the front-end verification is firstly carried out, and the multiple verification is carried out after the front-end verification is passed, so that the verification accuracy and the comprehensiveness of target data are further improved.
Step 202, performing multiple checks of the device dimension, the position dimension and the time dimension on the data uploading request according to the device information, the position information and the time information.
In this embodiment, the execution body may perform multiple checks of the device dimension, the location dimension, and the time dimension on the data upload request according to the device information, the location information, and the time information.
As an example, the execution body may check the corresponding dimension of the data upload request for each of the device information, the location information, and the time information, respectively.
For the device information, the executing body can determine whether the device information set which sends the account number authorized login of the file uploading request comprises the currently acquired device information, when the device information set comprises the currently acquired device information, the verification of the device information is indicated, and otherwise, the verification of the device information is indicated not to be passed. For each account, the executing body or the electronic device in communication with the executing body is provided with a device information set corresponding to the account.
For the location information, the execution body may determine whether the currently acquired location information is included in the location information set of the target device that issued the file upload request. Wherein the set of location information characterizes a location range where the terminal device is located. When the position information set comprises the currently acquired position information, the verification of the position information is indicated to be passed, and otherwise, the verification of the position information is indicated to be not passed. For each account, the executing body or the electronic device in communication with the executing body is provided with a position information set corresponding to the account.
In some special scenarios, each location information in the sequence of location information corresponding to a plurality of data upload requests issued by the target device is fixed. The execution body may determine whether the position information at each time of issuing the data upload request and the position information in the position information sequence match. In response to determining that the location information matches, determining that the verification passed; otherwise, the verification is not passed.
For the time information, the executing body may determine whether the currently acquired time information is included in the time information set of the target device that issues the file upload request. The time information set indicates a time range in which the terminal device frequently performs file uploading operation. When the time information set comprises the currently acquired time information, the verification of the time information is indicated to be passed, and otherwise, the verification of the time information is indicated to be not passed. For each account, the executing body or the electronic device in communication with the executing body is provided with a time information set corresponding to the account.
In some special scenarios, each time information in the time information sequence corresponding to the target device issuing the data upload request multiple times is fixed. The execution body may determine whether the time information at each time of issuing the data upload request and the time information in the time information sequence match. And determining that the time information is matched and passing the verification is determined in response to the fact that the time information is matched, otherwise, failing the verification.
As yet another example, the execution body may perform multiple checks of multiple dimensions on the data upload request in combination with the device information, the location information, and the time information. For example, for two data upload requests sent out by the same target device at different locations, the execution body may determine, according to a time interval between the two data upload requests, a possibility that the target setting is transferred from the location where the data upload request is sent out for the first time to the location where the data upload request is sent out for the second time. In response to determining that the likelihood exists, determining that the check is passed, otherwise, failing the check.
For another example, in some specific scenarios, the location information and the time information corresponding to each time the target device issues a data upload request are in one-to-one correspondence. The execution body may determine whether the correspondence between the position information and the time information is correct each time a data upload request is issued. And determining that the corresponding relation between the position information and the time information is correct in response to determining that the verification is passed, and otherwise, determining that the verification is not passed.
When the data uploading request is checked in a plurality of modes according to the device information, the position information and the time information, each mode is required to pass the check to be determined that the data uploading request passes the check.
In some optional implementations of this embodiment, the executing body may execute the step 202 as follows:
and carrying out multiple verification on the equipment dimension, the position dimension and the time dimension of the data uploading request by combining the equipment information, the position information and the time information corresponding to each time of sending the data uploading request by the user account to obtain a verification result.
As an example, a location information sequence composed of location information each time a user account issues a data upload request, a time information sequence composed of time information, and a device information sequence in the case where a user account binds a plurality of devices are determined within a preset period of time. Determining whether abnormal information exists in the equipment information sequence, the position information sequence and the time information sequence according to the corresponding relation among corresponding information in the preset equipment information sequence, the position information sequence and the time information sequence, and obtaining a verification result which fails to pass the verification in response to the abnormal information, or else obtaining a verification result which passes the verification.
In the implementation manner, multiple checks are performed by combining the corresponding equipment information, the position information and the time information when the user account sends the data uploading request each time, so that the checking accuracy is further improved.
In some optional implementation manners of this embodiment, the executing body may perform multiple verification by first determining, for a user account corresponding to the data upload request, whether the user account has a preset unreasonable condition in a device dimension, a position dimension and a time dimension in combination with device information, position information and time information corresponding to each time the user account issues the data upload request, and then, in response to determining that the user account has the preset unreasonable condition, determining that the data upload request fails the multiple verification.
The preset irrational condition is used for characterizing the condition which should not occur in the logic aspect or the aspect determined based on the manually specified related judging parameters about the equipment information, the position information and the time information.
By way of example, the unreasonable presets include issuing multiple data upload requests at the same location at the same time based on multiple target devices exceeding a preset number of thresholds, and issuing multiple data upload requests at different times and/or at different locations based on multiple target devices exceeding a preset number of thresholds.
In the implementation mode, the method for conveniently carrying out multiple verification on the data uploading request based on the preset unreasonable condition is provided, and the convenience and accuracy of data verification are further improved.
In some optional implementations of this embodiment, the executing entity determines that the data upload request passes the multiple checks in response to determining that there is no unreasonable condition.
In this implementation manner, in order to prevent the problem that the multiple verification is inaccurate due to incomplete setting of the preset unreasonable situation, the execution main body may also set the preset reasonable situation. As an example, preset reasonable conditions include:
(1) A data upload request is issued at a location based on a target device at a time, e.g., the account number issues the data upload request for the first time based on a target device.
(2) Based on the same target equipment, a plurality of data uploading requests are sent at different positions at different times, for example, according to the record data corresponding to the account, the plurality of data uploading requests sent by the account pass through the same target equipment all the time, and only the time information and the position information corresponding to the different data uploading requests are different.
(3) For example, the account number allows multiple devices to log in simultaneously, but the number of the multiple devices logged in simultaneously is limited by the preset number threshold, wherein the preset number threshold can be specifically set according to actual situations and is not limited herein.
(4) Based on a plurality of target devices not more than a preset number of thresholds, a plurality of data upload requests are issued at different times and/or at different locations, e.g., a plurality of target devices not more than a preset number of thresholds, a plurality of data upload requests issued at different times, or a plurality of target devices not more than a preset number of thresholds, a plurality of data upload requests issued at different locations
In this implementation manner, the executing body may count device information, location information, and time information when each account sends a data upload request, so as to determine whether an account corresponding to the currently received data upload request has one of the above situations.
Then, in response to determining that the presence, determining that the data upload request passes the multiple check.
In the implementation manner, in response to determining that any account corresponding to the data uploading request exists, the data uploading request is determined to pass through multiple verification.
In the implementation manner, specific condition data of the data uploading request passing through multiple verification is provided, the data uploading request is subjected to multiple verification based on various listed conditions, and the verification accuracy is further improved.
Step 203, determining whether to receive the target data corresponding to the data uploading request according to the checking result.
In this embodiment, the executing body may receive the target data corresponding to the data upload request in response to determining that the data upload request passes the multiple verification.
As an example, when the verification result indicates that the data uploading request passes the multiple verification, the target data is received and stored by the designated storage device, otherwise, the target data corresponding to the data uploading request is forbidden.
The execution body may further execute a data processing task based on the target data after receiving the target data. For example, in the instant communication field, the object data in word, excel, powerPoin format is updated and modified based on the received editing operation, and in the short video field, the video data is clipped and synthesized according to the received editing operation.
In some optional implementations of this embodiment, the executing body may execute the step 203 as follows:
firstly, in response to determining that the data uploading request passes multiple checks, performing server side checks on target data corresponding to the data uploading request.
The server side check includes, for example, file header content-type field check, file content header check, suffix name blacklist check, suffix name whitelist check, custom regular check, WAF (Web Application Firewall, web application protection system) device check.
In this implementation manner, the execution body may verify the target data by using one or more server verification manners according to actual situations.
And then, receiving target data corresponding to the data uploading request in response to the fact that the data uploading request passes the verification of the server side.
In this implementation manner, the execution body combines multiple verification based on the device information, the position information and the time information and service end verification, and after the multiple verification, the service end verification is further performed, so that the accuracy and the comprehensiveness of the verification on the target data are further improved.
With continued reference to fig. 3, fig. 3 is a schematic diagram 300 of an application scenario of the data verification method according to the present embodiment. In the application scenario of fig. 3, the target device 301 sends a data upload request to the server 302. Firstly, the server 302 collects device information 303, position information 304 and time information 305 of a target device in response to determining that a data uploading request of the target device 301 is received, then performs multiple checks on the device dimension, the position dimension and the time dimension of the data uploading request according to the device information 303, the position information 304 and the time information 305 to obtain a check result, and finally determines whether to receive target data corresponding to the data uploading request according to the check result.
In this embodiment, a data verification method is provided, where device information, location information and time information of a target device sending a data upload request are collected, so as to perform multiple verification of a device dimension, a location dimension and a time dimension on the data upload request, determine whether to receive target data corresponding to the data upload request according to a verification result, and improve accuracy of data verification and safety of a data upload process.
In some optional implementations of this embodiment, the executing body may further perform, in response to determining that the data upload request fails the verification, disabling the receiving of the target data corresponding to the data upload request.
In this implementation manner, when the target data fails any one of the front-end check and the multiple check and the server check, it is determined that the data upload request fails the check, and at this time, the execution body disables the target data corresponding to the data upload request.
In this implementation manner, the executing body may display, through the target device, a specific reason that the data upload request fails to pass verification.
In the implementation manner, when the target data does not pass any one of front-end verification and multiple verification and server verification, the target data corresponding to the file uploading request is forbidden to be received, so that the safety of the target data uploading process is improved.
With continued reference to fig. 4, there is shown a schematic flow 400 of yet another embodiment of a data verification method according to the present disclosure, including the steps of:
in step 401, in response to determining that the data uploading request of the target device is received, front-end verification is performed on the target data corresponding to the data uploading request.
In step 402, device information, location information, and time information are collected in response to determining that the data upload request passes the front-end verification.
Step 403, performing multiple checks of the device dimension, the position dimension and the time dimension on the data uploading request according to the device information, the position information and the time information.
Step 404, in response to determining that the data uploading request passes the multiple verification, performing a server verification on the target data corresponding to the data uploading request.
In step 405, in response to determining that the data upload request passes the server side verification, target data corresponding to the data upload request is received.
In step 406, in response to determining that the data upload request fails the verification, the target data corresponding to the data upload request is disabled.
As can be seen from this embodiment, compared with the embodiment corresponding to fig. 2, the flow 400 of the data verification method in this embodiment specifically illustrates the process of verifying the data uploading by combining the three verification modes of front-end verification and multiple verification and service-side verification, thereby further improving the verification accuracy and the security of the data uploading process.
With continued reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of a data verification apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 5, the data verification apparatus includes an acquisition unit 501 configured to acquire device information, location information, and time information of a target device in response to determining that a data upload request of the target device is received, a verification unit 502 configured to perform multiple verification of a device dimension, a location dimension, and a time dimension on the data upload request according to the device information, the location information, and the time information, and a determination unit 503 configured to determine whether to receive target data corresponding to the data upload request according to a verification result.
In some optional implementations of this embodiment, the verification unit 502 is further configured to, for a user account corresponding to the data upload request, perform multiple verification of the device dimension, the position dimension and the time dimension on the data upload request in combination with the device information, the position information and the time information corresponding to each time the user account issues the data upload request, to obtain a verification result.
In some optional implementations of this embodiment, the verification unit 502 is further configured to determine, for a user account corresponding to the data upload request, whether a preset unreasonable condition exists in the device dimension, the position dimension and the time dimension of the user account in combination with the device information, the position information and the time information corresponding to each time the user account issues the data upload request, and determine that the data upload request fails the multiple verification in response to determining that the preset unreasonable condition exists.
In some alternative implementations of the present embodiment, the verification unit 502 is further configured to determine that the data upload request passes the multiple verification in response to determining that no data upload request exists.
In some optional implementations of this embodiment, the collecting unit 501 is further configured to perform front-end verification on target data corresponding to the data upload request in response to determining that the data upload request of the target device is received, and collect device information, location information, and time information in response to determining that the data upload request passes the front-end verification.
In some optional implementations of this embodiment, the determining unit 503 is further configured to perform a server-side check on the target data corresponding to the data upload request in response to determining that the data upload request passes the multiple checks, and receive the target data corresponding to the data upload request in response to determining that the data upload request passes the server-side check.
In some optional implementations of this embodiment, the determining unit 503 is further configured to disable, in response to determining that the data upload request fails the check, the target data corresponding to the data upload request.
In this embodiment, a data verification apparatus is provided, which collects device information, location information and time information of a target device sending a data upload request, so as to perform multiple verification of a device dimension, a location dimension and a time dimension on the data upload request, so as to determine whether to receive target data corresponding to the data upload request according to a verification result, thereby improving accuracy of data verification and security of a data upload process.
According to an embodiment of the present disclosure, there is further provided an electronic device including at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor, when executed, to implement the data verification method described in any of the embodiments above.
According to an embodiment of the present disclosure, there is also provided a readable storage medium storing computer instructions for enabling a computer to implement the data verification method described in any of the above embodiments when executed.
The disclosed embodiments provide a computer program product that, when executed by a processor, enables the data verification method described in any of the above embodiments.
Fig. 6 illustrates a schematic block diagram of an example electronic device 600 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 6, the apparatus 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 may also be stored. The computing unit 601, ROM 602, and RAM 603 are connected to each other by a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Various components in the device 600 are connected to the I/O interface 605, including an input unit 606, e.g., keyboard, mouse, etc., an output unit 607, e.g., various types of displays, speakers, etc., a storage unit 608, e.g., magnetic disk, optical disk, etc., and a communication unit 609, e.g., network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as a data verification method. For example, in some embodiments, the data verification method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into the RAM 603 and executed by the computing unit 601, one or more steps of the data verification method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the data verification method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be a special or general purpose programmable processor, operable to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user, for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a Local Area Network (LAN), a Wide Area Network (WAN), and the Internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, is a host product in a cloud computing service system, and is used for solving the defects of large management difficulty and weak service expansibility in the traditional physical host and Virtual special server (VPS, virtual PRIVATE SERVER) service, and can also be a server of a distributed system or a server combined with a blockchain.
According to the technical scheme of the embodiment of the disclosure, the data verification method is provided, the device information, the position information and the time information of the target device sending the data uploading request are collected, so that multiple verification of the device dimension, the position dimension and the time dimension is performed on the data uploading request, whether the target data corresponding to the data uploading request are received or not is determined according to the verification result, and the accuracy of data verification and the safety of the data uploading process are improved.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions provided by the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.