CN114138393A

CN114138393A - Business data entry method and device

Info

Publication number: CN114138393A
Application number: CN202111472855.0A
Authority: CN
Inventors: 柏昊; 汤仲喆; 刘垚; 王涛
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2022-03-04

Abstract

The application provides a business data entry method and a device, which can be used in the financial field or other fields, and the method comprises the following steps: receiving a data entry request sent by a target service page, wherein the target service page comprises: a plurality of sub-pages, wherein the plurality of sub-pages are corresponding to different applications; determining a subpage to be entered in the plurality of subpages according to the data entry request, and acquiring currently input service data of the subpage to be entered; and sending preset related data and the service data to the application corresponding to the sub-page to be recorded, and executing the recording operation of the service data. The method and the device can improve the efficiency and flexibility of business data entry, and further can improve the business handling efficiency.

Description

Business data entry method and device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for inputting service data.

Background

For a complex service entry scene involving multiple applications, multiple functions and multiple fields, the traditional service data entry needs to be switched among multiple different applications according to the sequence of service flows and according to a certain sequence, and the entry of respective corresponding services is completed in sequence.

The serial service handling mode can prolong the whole service handling time, and is not beneficial to the rapid processing of the service; a plurality of functions need to access different applications in sequence, which brings certain difficulty to business operation; a large number of field entries easily results in a long time, causing system timeouts.

Disclosure of Invention

Aiming at least one problem in the prior art, the application provides a business data entry method and a business data entry device, which can improve the efficiency and flexibility of business data entry and further improve the business handling efficiency.

In order to solve the technical problem, the present application provides the following technical solutions:

in a first aspect, the present application provides a service data entry method, including:

receiving a data entry request sent by a target service page, wherein the target service page comprises: a plurality of sub-pages, wherein the plurality of sub-pages are corresponding to different applications;

determining a subpage to be entered in the plurality of subpages according to the data entry request, and acquiring currently input service data of the subpage to be entered;

and sending preset related data and the service data to the application corresponding to the sub-page to be recorded, and executing the recording operation of the service data.

Further, after the determining, according to the data entry request, a subpage to be entered in the subpages, and acquiring the currently input service data of the subpage to be entered, the method further includes:

and storing preset related data and the service data into a local cache file corresponding to the sub-page to be recorded.

Further, before the receiving of the data entry request sent by the target business page, the method further includes:

receiving a user login request;

according to the user login request, obtaining initial service data corresponding to each sub-page from the application corresponding to the sub-page and generating a corresponding local cache file;

and carrying out data reloading on each subpage according to the cache file corresponding to each subpage.

Further, the method for logging service data further includes:

receiving a login logout request of a user;

and destroying the local cache file according to the login quitting request of the user.

In a second aspect, the present application provides a service data entry device, including:

a receiving module, configured to receive a data entry request sent by a target service page, where the target service page includes: a plurality of sub-pages, wherein the plurality of sub-pages are corresponding to different applications;

the acquisition module is used for determining a subpage to be input in the subpages according to the data input request and acquiring currently input service data of the subpage to be input;

and the entry module is used for sending preset associated data and the service data to the application corresponding to the sub-page to be entered and executing the entry operation of the service data.

Further, the service data entry device further includes:

and the cache module is used for storing preset related data and the service data into a local cache file corresponding to the sub-page to be recorded.

Further, the service data entry device further includes:

the login module is used for receiving a user login request;

the generating module is used for acquiring initial service data corresponding to each sub-page from the application corresponding to the sub-page according to the user login request and generating a corresponding local cache file;

and the reloading module is used for reloading the data of each subpage according to the cache file corresponding to each subpage.

Further, the service data entry device further includes:

the log-out module is used for receiving a log-out request of a user;

and the destroying module is used for destroying the local cache file according to the login quitting request of the user.

In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the service data entry method when executing the program.

In a fourth aspect, the present application provides a computer-readable storage medium, on which computer instructions are stored, and when executed, the instructions implement the business data entry method.

According to the technical scheme, the application provides a business data entry method and a business data entry device. Wherein, the method comprises the following steps: receiving a data entry request sent by a target service page, wherein the target service page comprises: receiving a data entry request sent by a target service page, wherein the target service page comprises: a plurality of sub-pages, wherein the plurality of sub-pages are corresponding to different applications; determining a subpage to be entered in the plurality of subpages according to the data entry request, and acquiring currently input service data of the subpage to be entered; and sending the preset common associated data and the service data to the application corresponding to the sub-page to be recorded, executing the recording operation of the service data, and improving the efficiency and flexibility of recording the service data and further improving the efficiency of handling the service.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a schematic flow chart of a serial service process in the prior art;

FIG. 2 is a flow chart of a business data entry method in an embodiment of the present application;

fig. 3 is a schematic flow chart of

steps

011 and 013 of the business data entry method in the embodiment of the present application;

FIG. 4 is a logic diagram of common associated data extraction in an application example of the present application;

FIG. 5 is a schematic structural diagram of a business data entry device in an embodiment of the present application;

fig. 6 is a schematic block diagram of a system configuration of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

As shown in fig. 1, in the prior art, in a scenario where there is a precedence order between a service 1 and a service N, that is, there is an internal association between services, a conventional service processing flow is to complete a service-save-complete next service according to a certain order according to an internal logic of service handling, and there may not be a strict precedence order between individual services, but the services are still serial as a whole, which affects efficiency of service data entry; meanwhile, for business processing of different applications, different applications need to be logged in to execute business processing flows, and the automation degree is low. For example, a general service for one service application requires a customer information filling service, a service application information filling service, a warranty chaining service, and a submission approval service to be completed in order.

Based on this, in order to improve the efficiency and flexibility of service data entry and further improve the efficiency of service handling, an embodiment of the present application provides a service data entry apparatus, where the apparatus may be a server or a client device, and the client device may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), a vehicle-mounted device, an intelligent wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch and intelligent bracelet etc..

In practical applications, the part for performing the business data entry may be executed on the server side as described in the above, or all the operations may be completed in the client device. The selection may be specifically performed according to the processing capability of the client device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. The client device may further include a processor if all operations are performed in the client device.

The client device may have a communication module (i.e., a communication unit), and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.

The server and the client device may communicate using any suitable network protocol, including network protocols not yet developed at the filing date of this application. The network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, or the like. Of course, the network Protocol may also include, for example, an RPC Protocol (Remote Procedure Call Protocol), a REST Protocol (Representational State Transfer Protocol), and the like used above the above Protocol.

It should be noted that the business data entry method and the business data entry device disclosed by the application can be used in the technical field of finance, and can also be used in any field except the technical field of finance, and the application field of the business data entry method and the business data entry device disclosed by the application is not limited.

The following examples are intended to illustrate the details.

In order to improve the efficiency and flexibility of service data entry and further improve the efficiency of service handling, the embodiment provides a service data entry method in which the execution subject is a service data entry device, where the service data entry device includes but is not limited to a server, and as shown in fig. 2, the method specifically includes the following contents:

step 100: receiving a data entry request sent by a target service page, wherein the target service page comprises: the system comprises a plurality of sub-pages, wherein the sub-pages correspond to different applications.

Specifically, a part of sub-pages in the target business page may belong to the same application, and another part of sub-pages may belong to other applications; different applications may represent servers with different domain names; the target service page may include: a support layer page and a plurality of sub-pages embedded in the support layer page.

Step 200: and determining a subpage to be entered in the plurality of subpages according to the data entry request, and acquiring the currently input service data of the subpage to be entered.

Specifically, the service data currently input to the sub-page to be input by the user can be obtained; a storage button click event in a sub-page and a storage button click event of a support page can be monitored, and if the storage button click event of the sub-page is monitored, the sub-page is taken as the sub-page to be input; and if a storage button click event of the support page is monitored, taking each sub-page in the target business page as the sub-page to be recorded respectively. Wherein, the service data input by different sub-pages can be different; the currently input service data of the to-be-entered sub-page can represent the currently displayed service data of the to-be-entered sub-page.

Step 300: and sending preset related data and the service data to the application corresponding to the sub-page to be recorded, and executing the recording operation of the service data.

Specifically, the preset common associated data may indicate that none of the fields and field values in the service data table corresponding to each sub-page may be empty, and may be set according to actual needs.

Further, the preset related data and the service data may be sent to the application corresponding to the sub-page to be entered, so that the application checks the service data, and if the check is passed, the preset related data and the service data are stored in the database of the application, thereby completing the operation of entering the service data. When the service data of each sub-page is input into the database of the corresponding application, the data input of one total service can be equivalently completed; the initial value of the common associated data can be preset, and when the data entry of the total service is completed for one time, the common associated data is updated, so that the next total service data entry is conveniently executed.

For example, the customer information subpage may include: business data such as customer codes, customer names, ages and professions; the service application subpage may include: service data such as service number, service type, transaction amount and transaction time; the common associated data is a client ID; in the prior art, the client ID is generated only when the service data of the client information subpage is stored in the data table, so the service data and the client ID in the client information subpage must be stored first, and then the service data and the client ID in the service application subpage must be stored; in this example, the client ID may be preset to xxxxx0, so that when the service data entry is executed, the service data and the client ID in the service application sub-page may be stored first, and then the service data and the client ID in the client information sub-page may be entered; when the data entry of the current total service is completed or the user logs in next time, the value of the client ID is increased progressively and updated to xxxxx 1; the limitation of the business data entry sequence can be avoided, and the flexibility of the business data entry is improved.

In order to facilitate page data reloading and improve the convenience degree of user operation, in an embodiment of the present application, after step 200, the method further includes:

step 400: and storing preset related data and the service data into a local cache file corresponding to the sub-page to be recorded.

Specifically, data display after page switching can be realized through the cache file; the service data can be cached in a file form locally in the service data entry device, the validity of the file can be verified through file header data, namely, the format can be matched and verified through the encrypted user name, password, service code, timestamp and the like; the data in the cache file corresponding to each sub-page may be stored in the form of a character string: the initial is page coding, then whether all the necessary items of the page are filled in marks or not, and finally the service data of the page is stored as character strings in a key value pair mode. When different sub-pages are switched, data reloading is carried out, and a local cache file is read to fill page data; the corresponding relation between the original form page and the configured heavy-load form page can be saved, the page codes before and after the change are updated according to the corresponding relation, and the page codes are updated to a local cache file and a remote database; subsequently, the service data of each sub-page is reloaded, and matching can be performed through page coding.

In order to improve the efficiency of displaying the service data and reduce the repeated input operations, referring to fig. 3, in an embodiment of the present application, before step 100, the method further includes:

step 011: and receiving a user login request.

Step 012: and according to the user login request, obtaining initial service data corresponding to each sub-page from the application corresponding to each sub-page and generating a corresponding local cache file.

Specifically, the user login request may include: a user unique identifier, such as a client code and a client ID; obtaining the related data corresponding to the user login request from an application database according to the unique user identifier; and obtaining initial service data corresponding to the user login request from a plurality of applications according to the common associated data.

Step 013: and carrying out data reloading on each subpage according to the cache file corresponding to each subpage.

It will be appreciated that the initial service data for each sub-page may represent the service data last sent to the application to which the sub-page corresponds.

In order to save a storage space, in an embodiment of the present application, the method for logging service data further includes:

step 500: and receiving a login logout request of a user.

Step 600: and destroying the local cache file according to the login quitting request of the user.

Specifically, the data of the current sub-page in the local cache file and the timestamp data in the file header can be automatically inserted or updated every n minutes, a save button is arranged in each sub-page, and when a user performs save operation, the data in the current page is inserted or updated into the database; when the user returns to log in, the local cache file is destroyed, and the database is used as a data recovery cache in the next log-in process. Real-time caching within n minutes and data saved when logging out last time can be recovered. The recovery time period may be set according to actual needs, for example, n minutes is set to 3 minutes.

In order to further explain the scheme, the present application provides an application example of a service data entry method, in the application example, as shown in fig. 4, common association data of services 1 to N in a total service may be extracted, when service data of a single sub-page is saved, common associations may be simultaneously saved, a sequence between services is completely erased, an interactive scene of the entire service data entry is supported on the basis of the common associations, and the common associations may be equivalent to the basic service data; for the sub-pages belonging to the same application, the business data can be directly input, for the sub-pages of different applications, if the pages are directly called, data interaction between the two applications cannot be directly carried out, the two applications can be brought into the same domain, the data interaction and method calling between the different applications can be completed through cross-domain calling, the business pages of the different applications can be effectively aggregated together through means such as IOC, cross-domain and packaging, intensive processing is carried out, and the input efficiency of a user can be improved; in this application example, the method for entering service data specifically includes:

step 1: abstracting a concrete service page, namely the sub-page, into a page object, wherein the page object comprises: the domain name, the application, the name, the page url, the service parameters and other technical parameters are combined in a series connection mode to obtain an object array of the current service.

Step 2: and abstracting the page of the support layer, extracting common parameters of the page, and simultaneously extracting common methods such as page loading, page refreshing, page returning, sub-page temporary storage and the like. The target service page may include: the page comprises a support layer page and a plurality of sub-pages, wherein the sub-pages are embedded into the support layer page.

And step 3: combining a common parameter, an object array and a common method according to actual service needs; in order to reduce the system coupling degree and improve the system robustness and maintainability, the Page combination can be configured by configuring an IOC (control reversal) XML configuration file, which is used for configuring a Page class, and a main attribute Page chain pagechains, wherein different sub business objects such as a client sub-Page, an application sub-Page, a guarantee sub-Page and an approval sub-Page are configured in the Page chain pagechains, and basic attributes of the sub-pages are defined, such as a presentation name, an affiliated application, a namespace, a relative path and the like, and are combined in a series combination manner.

Of services 1 through N, only a portion of the services need to operate the content of service 4 across applications. When a page is generated, a general configuration file and a user-defined configuration file are read, page objects are sequentially generated, the generated page objects comprise a page url, service parameters, other technical parameters and the like, the content operation of the service 4 is directly embedded into the service of the current application 1, the corresponding page is displayed on the foreground, so that in the service processing, the page attribution and the operation database belong to the application 2, but the display is in the application 1 and is directly connected with the operation database of the application 2, the cross-application operation sequence before combination is that the application 1-application 2-page 4-application 2-database, the application 1-page 4-application 2-database is present, the page does not need to be acquired through the application 2, and the direct data interaction cost of different applications can be reduced.

Equivalently to the reassembly of different pages, each page can be independently regarded as an independent page object which contains inherent data and dynamic configuration data of the page, a service page list required by the current service is read through a configuration file of the IOC, different applications are used for service page data interaction to pull out the page object, and the page is assembled after the configuration reading is completed through the page object formed in the step 1; and assembling the page objects according to the sequence of the configuration files, reading the configuration data belonging to different pages, and performing combined filling display of the total business. Due to the fact that different application combinations exist, in order to solve the problems that non-homologous webpages cannot read Cookie, cannot access Dom or cannot send Ajax requests and the like, JSONP, CORS, Nginx or websocket agents and the like can be adopted to realize non-homologous page interaction, and as an optimal selection, a scheme with the minimum change can be selected, namely, cross-domain access can be realized by setting the same document. Each service may correspond to a different sub-page.

And 4, step 4: after the page required by the total service is combined through the step 3, the source code of the sub-page can be modified according to the name space name obtained during the generation of the page, the parameters and the method of the service are placed in the same name space, and the mutual influence among the pages is isolated through the closure and the name domain, so that the assembly and customization of the cross-application service page under the current service are completed, and the purpose of completing the operation of all associated applications through cross-application requests is not needed.

Specifically, the support layer pages are initialized to share association, and an N-in-1 page set required by the service can be rapidly assembled by reading the configuration file; the influence among all sub-pages is isolated through a closure mode, and the internal information of the sub-pages can be read by the page of the support layer; by the method, the support layer page can uniformly call the method of each sub-page to carry out service data and associated persistent processing.

And 5: and (4) data interaction mode. After combining the pages with different functions and different applications, the support layer page provides necessary resources and parameters of each sub-page, the interaction between the non-homologous pages is realized through a cross-domain scheme in step 3, and the sub-pages can complete respective function entry under the support of the support layer page. When the data is stored, each sub-page can independently store the data, and the storage method can be sequentially called through a uniform storage entry provided by the page of the support layer through a name space to realize the storage of all the service data. The two storage modes are only different in implementation forms, and the business data recorded by each sub-page is submitted to the database of each application by the sub-page for storage.

Furthermore, the switching between the sub-pages can be carried out by adopting a pull-down mode and a step-by-step mode according to the operation habits of the user. Displaying navigation buttons of each sub-page on a supporting layer page; the navigation buttons can be customized and displayed in four directions, namely, up, down, left and right, of the page of the supporting layer.

A pull-down type: by adopting a lazy loading mode, a user can load each sub-page in sequence by rolling a mouse roller and highlight the corresponding navigation button according to the sub-page where the screen is located; the user can also directly click the navigation button, and the screen directly jumps to the corresponding sub-page.

And further displaying the data cache aiming at a pull-down operation mode, reading whether a required item in a cache file is marked as completed or not, if the required item is marked as completed or not, setting a current pull-down option as a completed color or a self-defined completed mark, otherwise, setting the option in a pull-down menu as an exclamation mark mode, reading the unfilled required item in the cache file, and reminding a user of the unfilled required item in a sub-page by setting a reminding dialog box or a mouse focusing mode. And reading all unfilled option names and corresponding service positions in the homepage of the pull-down menu, and prompting.

Step by step: only one sub-page is loaded each time, a user can only pay attention to the current sub-page, a next button and a previous button are added below the page, the sub-pages can be switched with each other through the two buttons, and the service can be switched through a navigation button in a pull-down mode; the difference between the step-by-step mode and the pull-down mode is that only one sub-page is displayed at one time in the step-by-step mode, and when the sub-page is switched, if the current sub-page is not stored, the sub-page is automatically triggered to be temporarily stored, so that the subsequent operation of the service is facilitated. The pull-down type and the step-by-step type can be switched flexibly and conveniently.

The navigation button can rapidly position the sub-page, and can drag the sub-page back and forth (or up and down) in the navigation area to form a new sequence; after dragging is finished, user-defined configuration table data can be automatically updated, a unified page data extraction method is triggered, temporary data of all pages are stored in a cache, meanwhile, the pages are reloaded, user-defined configuration is read, the pages are displayed again according to the sequence after dragging, and then the data are read from the cache and displayed again.

Further, for the distributed interaction mode, only one page can be seen at a time, if other page information needs to be seen, clicking and switching are very inconvenient, thumbnail images for previewing can be generated on the right side of the page according to the sequence of the page, the thumbnail images are divided according to sub-pages, and when a mouse of a user moves to the thumbnail images of the corresponding sub-pages, the corresponding page information can be displayed in a suspension and amplification mode, so that auxiliary previewing is achieved, and the user can conveniently view the thumbnail images; and clicking the sub-page of the thumbnail by the user, wherein the suspended page can reside, the user can move the mouse and can directly operate on the suspended page, clicking the place outside the suspended page, hiding the suspended page, and refreshing the modified information to the corresponding sub-page.

As can be seen from the above description, the data entry method provided by the application example can isolate the dependency between the sub-pages through IOC configuration, which is simple and convenient; the mutual influence among different functions in the same page can be isolated by means of closure, and the sub-pages can continue to bear independent functions after being packaged by one layer, so that additional development is not needed, the transformation cost is low, and the influence on the original functions is small; easy to expand: through good object-oriented design, the N-in-1 interactive structure can be rapidly expanded, and meanwhile, different N-in-1 services can be aggregated according to actual conditions, so that fast iteration can be realized, and aggregation is convenient; the related functions are gathered at one inlet, so that the convenience degree can be greatly improved; the content which can be recorded by the user can be selected according to the actual situation of the user through the temporary storage operation, and is recorded and stored at any time; two different interaction modes are provided, the two modes can be selected according to the actual needs of a user, and the two modes support switching, so that the method is flexible and convenient; a navigation button and a preview area are additionally arranged on the page, so that the page can be conveniently switched and positioned by a user, the user can also be supported to define the page sequence, and the convenience and the good use are realized; the preview area can solve the problem that a user frequently pulls a page or switches among sub-pages, meanwhile, the modification on the suspended amplified preview sub-page is also supported, and the efficiency can be improved.

To further explain the application example of the business data entry method provided by the present application, the method specifically includes:

inputting service data; the method comprises the steps that service data are automatically backed up to a local cache file in N minutes/page switching, namely the service data can be stored to the local cache file at regular time or when page switching operation is executed; the saving operation/page switching is to back up the service data to the server, that is, the data in the page can be inserted or updated into the database of the remote server when the saving operation or the page switching operation is executed; after the user logs out, the local cache file is automatically destroyed; after the user logs in again, a local cache file is generated according to the data cached by the remote server; carrying out data reloading according to the local cache file; and updating the cache data in the server according to the user-defined corresponding relation.

In terms of software, in order to improve efficiency and flexibility of service data entry and further improve efficiency of service handling, the present application provides an embodiment of a service data entry device for implementing all or part of contents in the service data entry method, and referring to fig. 5, the service data entry device specifically includes the following contents:

a receiving module 10, configured to receive a data entry request sent by a target service page, where the target service page includes: the system comprises a plurality of sub-pages, wherein the sub-pages correspond to different applications.

The obtaining module 20 is configured to determine, according to the data entry request, a subpage to be entered in the multiple subpages, and obtain service data currently input by the subpage to be entered.

And the entry module 30 is configured to send preset associated data and the service data to the application corresponding to the sub-page to be entered, and execute an entry operation of the service data.

In an embodiment of the present application, the service data entry apparatus further includes:

and the login module is used for receiving a user login request.

And the generating module is used for acquiring initial service data corresponding to each sub-page from the application corresponding to each sub-page according to the user login request and generating a corresponding local cache file.

and the log-out module is used for receiving a log-out request of a user.

The embodiment of the service data entry apparatus provided in this specification may be specifically configured to execute the processing flow of the embodiment of the service data entry method, and its functions are not described herein again, and refer to the detailed description of the embodiment of the service data entry method.

In terms of hardware, in order to improve efficiency and flexibility of service data entry and further improve efficiency of service handling, the present application provides an embodiment of an electronic device for implementing all or part of contents in the service data entry method, where the electronic device specifically includes the following contents:

a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the communication interface is used for realizing information transmission between the service data input device and the related equipment such as the user terminal; the electronic device may be a desktop computer, a tablet computer, a mobile terminal, and the like, but the embodiment is not limited thereto. In this embodiment, the electronic device may be implemented with reference to the embodiment for implementing the service data entry method and the embodiment for implementing the service data entry apparatus in the embodiments, and the contents of the embodiments are incorporated herein, and repeated details are not described herein.

Fig. 6 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 6, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this FIG. 6 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one or more embodiments of the present application, the business data entry functionality can be integrated into the central processor 9100. The central processor 9100 may be configured to control as follows:

As can be seen from the foregoing description, the electronic device provided in the embodiments of the present application can improve efficiency and flexibility of business data entry, and further improve efficiency of business transaction.

In another embodiment, the service data entry device may be configured separately from the central processor 9100, for example, the service data entry device may be configured as a chip connected to the central processor 9100, and the service data entry function is realized under the control of the central processor.

As shown in fig. 6, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 6; further, the electronic device 9600 may further include components not shown in fig. 6, which may be referred to in the art.

As shown in fig. 6, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

As can be seen from the above description, the electronic device provided in the embodiments of the present application can improve the efficiency and flexibility of service data entry, and thus improve the efficiency of service handling.

An embodiment of the present application further provides a computer-readable storage medium capable of implementing all the steps in the business data entry method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements all the steps in the business data entry method in the foregoing embodiment, for example, when the processor executes the computer program, implements the following steps:

As can be seen from the foregoing description, the computer-readable storage medium provided in the embodiments of the present application can improve efficiency and flexibility of business data entry, and further improve efficiency of business transaction.

In the present application, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Reference is made to the description of the method embodiments.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the present application are explained by applying specific embodiments in the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A business data entry method is characterized by comprising the following steps:

2. The business data entry method according to claim 1, wherein after the determining a subpage to be entered in the plurality of subpages according to the data entry request and acquiring the business data currently input by the subpage to be entered, further comprising:

3. The business data entry method according to claim 1, further comprising, before said receiving a data entry request sent by a target business page:

receiving a user login request;

4. A business data entry method according to claim 2 or 3 further comprising:

receiving a login logout request of a user;

5. A business data entry device, comprising:

6. The business data entry device of claim 5, further comprising:

7. The business data entry device of claim 5, further comprising:

the login module is used for receiving a user login request;

8. A business data entry device according to claim 6 or 7 further comprising:

the log-out module is used for receiving a log-out request of a user;

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the business data entry method of any one of claims 1 to 4 when executing the program.

10. A computer readable storage medium having stored thereon computer instructions, wherein the instructions, when executed, implement the business data entry method of any one of claims 1 to 4.