A business processing method, apparatus, electronic device, and storage medium
By introducing an architecture that includes an intermediate content layer, a data processing layer, and a business processing layer into mobile applications, the problems of long data transmission links and high maintenance difficulty in existing technologies are solved, achieving the effects of simplified data transmission and easy maintenance.
Patent Information
- Application Number
- CN202210277882.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-21
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-03-21
AI Technical Summary
The lack of a unified standard in the development architecture of existing mobile applications leads to long data transmission links and high maintenance difficulty, with the amount of code increasing with each iteration and update.
The mobile architecture consists of a view layer, a middle content layer, a data processing layer, and a business processing layer. The middle content layer handles business and data processing calls for UI events, sends requests to the business processing layer and the data processing layer respectively, and returns the results to the view layer.
It simplifies the data transfer path, reduces code redundancy, and is easy to maintain, especially during application iterations and updates, maintaining a lightweight page controller layer structure.
Smart Images

Figure CN116820406B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and more specifically to a business processing method, apparatus, electronic device, and storage medium. Background Technology
[0002] With the continuous development of mobile technology, mobile applications are becoming more and more widespread. Mobile devices run a variety of applications to achieve corresponding functions.
[0003] Currently, mobile application development architectures include MVC, MVP, and MVVM. Regardless of the specific architecture, there's no unified standard for business logic processing; all processes are implemented within the page container. This necessitates layer-by-layer data transfer, resulting in long data chains. Furthermore, as applications iterate and update, the codebase grows, increasing the difficulty of maintenance. Summary of the Invention
[0004] The purpose of this invention is to address the shortcomings of the prior art by providing a business processing method, apparatus, electronic device, and storage medium, which is achieved through the following technical solutions.
[0005] A first aspect of the present invention provides a business processing method applied to a mobile terminal architecture comprising a view layer, an intermediate content layer, a data processing layer, and a business processing layer, the method comprising:
[0006] The view layer obtains interface events and sends the interface events to the intermediate content layer.
[0007] The intermediate content layer sends business call requests to the business processing layer and data processing requests to the data processing layer based on the interface events.
[0008] The business processing layer performs business logic processing based on the business call request and returns the business processing result to the intermediate content layer.
[0009] The data processing layer performs data logic processing according to the data processing request and returns the data processing result to the intermediate content layer.
[0010] The intermediate content layer generates a response based on the business processing result and the data processing result, and then sends it back to the view layer.
[0011] In some embodiments of this application, sending a business call request to the business processing layer based on the interface event through the intermediate content layer includes:
[0012] The intermediate content layer extracts business processing information from the interface events and initiates a business call request to the business processing layer based on the business processing information.
[0013] In some embodiments of this application, sending a data processing request to the data processing layer based on the interface event through the intermediate content layer includes:
[0014] The intermediate content layer extracts data processing information from the interface events and initiates a data processing request to the data processing layer based on the data processing information.
[0015] In some embodiments of this application, the business processing layer performs business logic processing based on the business call request, including:
[0016] The business processing layer sends a message to the corresponding business processing protocol implementer based on the business call request, so that the business processing protocol implementer can perform business logic processing.
[0017] In some embodiments of this application, the data processing layer performs data logic processing according to the data processing request, including:
[0018] The data processing layer sends messages to the corresponding data processing protocol implementer according to the data processing request, so that the data processing protocol implementer can perform data logic processing.
[0019] In some embodiments of this application, the method further includes, before obtaining interface events through the view layer:
[0020] When the page initialization method is executed, the data processing attributes and business processing attributes of the intermediate content layer are assigned values respectively, so that the intermediate content layer is bound to the data processing layer and the business processing layer respectively.
[0021] In some embodiments of this application, the method further includes, before obtaining interface events through the view layer:
[0022] The intermediate content layer is bound to each view and / or object by adding an object property to the class of each view and / or object.
[0023] A second aspect of the present invention provides a business processing apparatus applied to a mobile terminal architecture comprising a view layer, an intermediate content layer, a data processing layer, and a business processing layer, the apparatus comprising:
[0024] The event acquisition module is used to acquire interface events through the view layer and send the interface events to the intermediate content layer.
[0025] The sending module is used to send a business call request to the business processing layer and a data processing request to the data processing layer based on the interface event through the intermediate content layer.
[0026] The business processing module is used to perform business logic processing based on the business call request through the business processing layer, and return the business processing result to the intermediate content layer;
[0027] The data processing module is used to perform data logic processing according to the data processing request through the data processing layer, and return the data processing result to the intermediate content layer;
[0028] The feedback module is used to generate a response based on the business processing result and the data processing result through the intermediate content layer and send it back to the view layer.
[0029] A third aspect of the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, performs the steps of the method described in the first aspect above.
[0030] A fourth aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect above.
[0031] Based on the business processing method and apparatus described in the first and second aspects above, the present invention has at least the following beneficial effects or advantages:
[0032] By adding three abstract layers—a middle content layer, a data processing layer, and a business processing layer—the middle content layer handles the data processing calls from the view layer to the data processing layer and the business processing calls from the business processing layer for various UI events. The middle content layer then returns the processed UI events to the view layer, completing the entire business processing flow. Since business processing and data processing are implemented in different layers and called separately through the middle content layer, data transfer does not need to be layer-by-layer. The data flow is clear and straightforward, with short transmission links. Furthermore, the page controller layer only needs to store the lifecycle code of page elements, making it a lightweight VC. Even with application iterations and updates, the amount of code distributed across each layer remains minimal, facilitating future maintenance. Attached Figure Description
[0033] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings:
[0034] Figure 1This is a schematic diagram of a mobile terminal architecture according to an exemplary embodiment of the present invention;
[0035] Figure 2 This is a flowchart illustrating a business processing method according to an exemplary embodiment of the present invention;
[0036] Figure 3 This is a flowchart illustrating another business processing method according to an exemplary embodiment of the present invention;
[0037] Figure 4 This is a schematic diagram illustrating the structure of a service processing apparatus according to an exemplary embodiment of the present invention;
[0038] Figure 5 This is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment of the present invention;
[0039] Figure 6 This is a schematic diagram illustrating the structure of a storage medium according to an exemplary embodiment of the present invention. Detailed Implementation
[0040] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.
[0041] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular forms “a,” “the,” and “the” used in this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.
[0042] It should be understood that although the terms first, second, third, etc., may be used in this invention to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of this invention, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."
[0043] To reduce the event propagation chain, this application proposes an improved business layering design pattern, which adds three abstract layers—data processing layer, business processing layer, and intermediate content layer—in addition to the conventional view layer, model layer, and page controller layer.
[0044] The specific business processing flow is as follows: First, the view layer obtains the interface events and sends them to the intermediate content layer. The intermediate content layer sends a business call request to the business processing layer and a data processing request to the data processing layer based on the interface events. Then, the business processing layer performs business logic processing based on the business call requests and returns the business processing results to the intermediate content layer. The data processing layer performs data logic processing based on the data processing requests and returns the data processing results to the intermediate content layer. Finally, the intermediate content layer generates a response based on the business processing results and the data processing results and sends it back to the view layer.
[0045] The technical effects that can be achieved based on the above description are:
[0046] By adding three abstract layers—a middle content layer, a data processing layer, and a business processing layer—the middle content layer handles the data processing calls from the view layer to the data processing layer and the business processing calls from the business processing layer for various UI events. The middle content layer then returns the processed UI events to the view layer, completing the entire business processing flow. Since business processing and data processing are implemented in different layers and called separately through the middle content layer, data transfer does not need to be layer-by-layer. The data flow is clear and straightforward, with short transmission links. Furthermore, the page controller layer only needs to store the lifecycle code of page elements, making it a lightweight VC. Even with application iterations and updates, the amount of code distributed across each layer remains minimal, facilitating future maintenance.
[0047] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
[0048] Example 1:
[0049] Figure 1 This is a schematic diagram illustrating a mobile terminal architecture according to an exemplary embodiment of the present invention. The mobile terminal architecture includes a view layer, a context layer, a data handling layer, a business handling layer, a model layer, and a view controller layer. The mobile terminal architecture interacts with the backend for data exchange.
[0050] The Context layer, acting as middleware between the View layer and the Data Handle and Business Handle layers, is primarily responsible for initiating calls to the Data Handle and Business Handle layers respectively for UI events transmitted from the View layer, and returning the processing results to the View layer to complete the business logic required by the UI events. Therefore, before performing business processing, the Context layer needs to be bound to the Data Handle and Business Handle layers, as well as to various views and / or objects. The Data Handle layer implements data logic processing, such as data creation, deletion, modification, and retrieval logic. Data logic processing code is managed in a unified class file (XXX Data Handler). The Business Handle layer implements business logic processing, such as message sending and page switching logic. Business logic processing code is managed in a unified class file (XXX Business Object). The View layer is responsible for all tasks related to the visual interface. The Model layer provides different model data, which can be called by the Data Handle layer to implement corresponding functions. The View Controller layer manages the entire lifecycle of page views and / or objects and can be called by the middle content layer.
[0051] As can be seen from the above business layering, since business processing and data processing are implemented in different layers and are called separately through the intermediate content layer, data transmission does not need to be transmitted layer by layer. The data flow is single and clear, the transmission link is short, and the page controller layer only needs to store the lifecycle code of page elements. It can be made into a lightweight VC. Even with the iterative updates of the application, the amount of code distributed to each layer will not be much, making it easy to maintain later.
[0052] Specifically, the view layer is used to acquire UI events and send them to the intermediate content layer. These UI events contain certain UI event information, such as the business processing information and data processing information required for the current event.
[0053] The intermediate content layer is used to send business call requests to the business processing layer and data processing requests to the data processing layer based on UI events.
[0054] Specifically, the middle content layer extracts business processing information from UI events and initiates a business call request to the business processing layer based on the business processing information. Simultaneously, the middle content layer extracts data processing information from UI events and initiates a data processing request to the data processing layer based on the data processing information.
[0055] Specifically, the business call request carries the function name of the business processing logic corresponding to the business processing information. The data processing request carries the function name of the data processing logic corresponding to the data processing information.
[0056] The business processing layer is used to perform business logic processing based on business call requests and return the business processing results to the intermediate content layer.
[0057] Specifically, the business processing layer can predefine business processing protocols, which are used to send messages to the corresponding business processing protocol implementers based on business call requests, so that the business processing protocol implementers can perform business logic processing. This protocol-oriented approach, which implements business processing by sending messages to the protocol implementers, is more readable than object-oriented approaches.
[0058] The data processing layer is used to perform data logic processing according to data processing requests and return the data processing results to the intermediate content layer.
[0059] Specifically, the data processing layer can predefine data processing protocols, which are used to send messages to the corresponding data processing protocol implementers based on data processing requests, so that the data processing protocol implementers can perform data logic processing. This protocol-oriented approach, which achieves data processing by sending messages to the protocol implementers, is more readable than object-oriented approaches.
[0060] The intermediate content layer is also used to generate responses based on business processing results and data processing results and send them back to the view layer. In this case, the business processing results returned by the business processing layer and / or the data processing results returned by the data processing layer may not be data that the view layer can directly access. The intermediate content layer can then process the business processing results and data processing results to generate a response, which is then returned to the view layer. The view layer then displays this response to the user.
[0061] It should be noted that before obtaining UI events through the view layer, the intermediate content layer needs to be bound to the data processing layer and the business processing layer respectively. The specific binding process is as follows: when executing the page initialization method, the data processing attributes and business processing attributes of the intermediate content layer are assigned values respectively, so that the intermediate content layer is bound to the data processing layer and the business processing layer respectively. This allows the intermediate content layer to directly call the business processing logic in the business processing layer and the data processing logic in the data processing layer.
[0062] Furthermore, all views and / or objects need to be bound to the intermediate content layer. The specific binding process is as follows: add an object property of the intermediate content layer to the class of each view and / or object, thus binding the intermediate content layer to each view and / or object. In this way, when using views and / or objects, the business logic has access to the properties of the intermediate content layer, allowing it to directly call the data processing layer for data-related operations and the business logic processing layer for business-related operations, reducing data transfer paths.
[0063] To illustrate the specific business processing flow of the business layered architecture proposed in this application, the following explanation is provided in conjunction with a specific flowchart.
[0064] Example 2:
[0065] Figure 2 This is a flowchart illustrating an embodiment of a business processing method according to an exemplary embodiment of the present invention. This business processing method is applied to a mobile terminal architecture including a view layer, an intermediate content layer, a data processing layer, a business processing layer, a model layer, and a page controller layer. For a detailed description of this mobile terminal architecture, please refer to the relevant description in Embodiment 1 above, which will not be repeated here. The business processing method includes the following steps:
[0066] Step 201: Obtain UI events through the view layer and send UI events to the intermediate content layer.
[0067] Among them, interface events can be click, swipe up, swipe down, etc.
[0068] Step 202: Send business call requests to the business processing layer and data processing requests to the data processing layer based on interface events through the intermediate content layer.
[0069] Step 203: The business processing layer performs business logic processing based on the business call request and returns the business processing result to the intermediate content layer.
[0070] Step 204: The data processing layer performs data logic processing according to the data processing request and returns the data processing result to the intermediate content layer.
[0071] It is understandable that the execution of steps 203 and 204 above is not in any particular order, and of course, they can be executed in parallel.
[0072] Step 205: Generate a response based on the business processing results and data processing results through the intermediate content layer and send it back to the view layer.
[0073] For the specific implementation of steps 201 to 205 above, please refer to the relevant description in Embodiment 1 above, which will not be repeated here.
[0074] This completes the above. Figure 2 The processing flow shown illustrates the use of three abstract layers: an intermediate content layer, a data processing layer, and a business processing layer. The intermediate content layer handles the data processing calls from the view layer to the data processing layer and the business processing calls from the business processing layer for various UI events. The intermediate content layer then returns the processed UI events to the view layer, completing the entire business processing flow. Because business processing and data processing are implemented in different layers and called separately through the intermediate content layer, data transfer does not need to be layer-by-layer. The data flow is clear and straightforward, with short transmission links. Furthermore, the page controller layer only needs to store the lifecycle code of page elements, allowing for a lightweight VC architecture. Even with application iterations and updates, the amount of code distributed across each layer remains minimal, facilitating future maintenance.
[0075] Example 3:
[0076] Figure 3 This is a flowchart illustrating another business processing method according to an exemplary embodiment of the present invention. Based on the above embodiment, the method includes the following steps:
[0077] Step 301: Bind the intermediate content layer to the data processing layer and the business processing layer respectively.
[0078] Specifically, when the page initialization method is executed, the data processing attributes and business processing attributes of the intermediate content layer are assigned values respectively, so that the intermediate content layer is bound to the data processing layer and the business processing layer respectively.
[0079] The page initialization method is a method in the base class of the page controller layer. By executing the page initialization method, a storage space can be allocated for each view and / or object to be cached for direct invocation.
[0080] Step 302: Bind each view and / or object to the intermediate content layer.
[0081] Specifically, by adding an object property of the intermediate content layer to the class of each view and / or object, the intermediate content layer is bound to each view and / or object. This way, when a business application uses a view and / or object, it has access to the properties of the intermediate content layer. It can then directly call the data processing layer for data-related operations and the business processing layer for business-related operations, reducing data transfer paths.
[0082] Step 303: Obtain UI events through the view layer and send UI events to the intermediate content layer.
[0083] Step 304: Send business call requests to the business processing layer and data processing requests to the data processing layer based on interface events through the intermediate content layer.
[0084] Step 305: The business processing layer performs business logic processing based on the business call request and returns the business processing result to the intermediate content layer.
[0085] Step 306: The data processing layer performs data logic processing according to the data processing request and returns the data processing result to the intermediate content layer.
[0086] Step 307: Generate a response based on the business processing results and data processing results through the intermediate content layer and send it back to the view layer.
[0087] It should be noted that for any similarities or differences between this embodiment and the embodiments described above, please refer to the corresponding descriptions in the embodiments described above, which will not be repeated here.
[0088] This demonstrates that by binding the intermediate content layer to the data processing layer and the business processing layer, and also binding it to each view and / or object, the business logic, when using views and / or objects, possesses the attributes of the intermediate content layer. It can directly call the data processing layer for data-related operations and the business processing layer for business-related operations through the intermediate content layer, reducing data transfer paths. Furthermore, because business processing and data processing are implemented in different layers, the separation of data, logic, and interface is clearer, code redundancy is lower, and maintenance is easier in the future.
[0089] Corresponding to the embodiments of the aforementioned business processing methods, the present invention also provides embodiments of business processing apparatus.
[0090] Figure 4 This is a schematic diagram illustrating the structure of a service processing apparatus according to an exemplary embodiment of the present invention. The apparatus is used to execute the service processing method provided in any of the above embodiments, such as... Figure 4 As shown, the service processing device includes:
[0091] Event acquisition module 410 is used to acquire interface events through the view layer and send the interface events to the intermediate content layer;
[0092] The sending module 420 is used to send a business call request to the business processing layer and a data processing request to the data processing layer based on the interface event through the intermediate content layer.
[0093] The business processing module 430 is used to perform business logic processing on the business call request through the business processing layer and return the business processing result to the intermediate content layer.
[0094] Data processing module 440 is used to perform data logic processing according to the data processing request through the data processing layer, and return the data processing result to the intermediate content layer;
[0095] Feedback module 450 is used to generate a response based on the business processing result and the data processing result through the intermediate content layer and send it back to the view layer.
[0096] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.
[0097] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the present invention according to actual needs. Those skilled in the art can understand and implement this without creative effort.
[0098] The present invention also provides an electronic device corresponding to the business processing method provided in the foregoing embodiments, for executing the above-described business processing method.
[0099] Figure 5 This is a hardware structure diagram of an electronic device according to an exemplary embodiment of the present invention. The electronic device includes: a communication interface 601, a processor 602, a memory 603, and a bus 604; wherein the communication interface 601, the processor 602, and the memory 603 communicate with each other through the bus 604. The processor 602 can execute the business processing method described above by reading and executing machine-executable instructions corresponding to the control logic of the business processing method in the memory 603. The specific content of the method is described in the above embodiment and will not be repeated here.
[0100] The memory 603 mentioned in this invention can be any electronic, magnetic, optical, or other physical storage device, and can contain stored information such as executable instructions, data, etc. Specifically, the memory 603 can be RAM (Random Access Memory), flash memory, storage drive (such as hard disk drive), any type of storage disk (such as optical disc, DVD, etc.), or similar storage media, or combinations thereof. Communication between this system network element and at least one other network element is achieved through at least one communication interface 601 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc., can be used.
[0101] Bus 604 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 603 is used to store programs, and the processor 602 executes the programs after receiving execution instructions.
[0102] Processor 602 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 602 or by instructions in software form. The processor 602 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), an On-Premises Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor.
[0103] The electronic devices and business processing methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.
[0104] This application also provides a computer-readable storage medium corresponding to the business processing method provided in the foregoing embodiments. Please refer to... Figure 6 As shown, the computer-readable storage medium is an optical disc 30, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it executes the business processing method provided in any of the foregoing embodiments.
[0105] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.
[0106] The computer-readable storage medium provided in the above embodiments of this application and the business processing method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the application stored therein.
[0107] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.
[0108] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0109] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
Claims
1. A business processing method, characterized in that, The method is applied to a mobile terminal architecture that includes a view layer, a middle content layer, a data processing layer, and a business processing layer. The method includes: The view layer obtains interface events and sends the interface events to the intermediate content layer. The intermediate content layer sends business call requests to the business processing layer and data processing requests to the data processing layer based on the interface events, including: the intermediate content layer extracts business processing information from the interface events and initiates a business call request to the business processing layer based on the business processing information; simultaneously, the intermediate content layer extracts data processing information from the interface events and initiates a data processing request to the data processing layer based on the data processing information; wherein, the business call request carries the function name of the business processing logic corresponding to the business processing information, and the data processing request carries the function name of the data processing logic corresponding to the data processing information; The business processing layer performs business logic processing based on the business call request and returns the business processing result to the intermediate content layer. The data processing layer performs data logic processing according to the data processing request and returns the data processing result to the intermediate content layer. The intermediate content layer processes the business processing results and the data processing results, generates a response, and sends it back to the view layer. Before obtaining interface events through the view layer, the method further includes: when executing the page initialization method, assigning values to the data processing attributes and business processing attributes of the intermediate content layer respectively, so that the intermediate content layer is bound to the data processing layer and the business processing layer respectively; and binding the intermediate content layer to each view and / or object by adding object attributes of the intermediate content layer to the class of each view and / or object.
2. The method according to claim 1, characterized in that, The business processing layer performs business logic processing based on the business call request, including: The business processing layer sends a message to the corresponding business processing protocol implementer based on the business call request, so that the business processing protocol implementer can perform business logic processing.
3. The method according to claim 1, characterized in that, The data processing layer performs data logic processing based on the data processing request, including: The data processing layer sends messages to the corresponding data processing protocol implementer according to the data processing request, so that the data processing protocol implementer can perform data logic processing.
4. A business processing device, characterized in that, The device is applied to a mobile terminal architecture that includes a view layer, a middle content layer, a data processing layer, and a business processing layer. The device includes: The event acquisition module is used to acquire interface events through the view layer and send the interface events to the intermediate content layer. The sending module is configured to send a business call request to the business processing layer and a data processing request to the data processing layer based on the interface event through the intermediate content layer. The intermediate content layer extracts business processing information from the interface event and initiates a business call request to the business processing layer based on the business processing information. Simultaneously, the intermediate content layer extracts data processing information from the interface event and initiates a data processing request to the data processing layer based on the data processing information. The business call request carries the function name of the business processing logic corresponding to the business processing information, and the data processing request carries the function name of the data processing logic corresponding to the data processing information. The business processing module is used to perform business logic processing based on the business call request through the business processing layer, and return the business processing result to the intermediate content layer; The data processing module is used to perform data logic processing according to the data processing request through the data processing layer, and return the data processing result to the intermediate content layer; The feedback module is used to process the business processing results and the data processing results through the intermediate content layer, generate a response, and send it back to the view layer; The device further includes: a binding module, configured to assign values to the data processing attributes and business processing attributes of the intermediate content layer respectively when executing the page initialization method before obtaining interface events through the view layer, so that the intermediate content layer is bound to the data processing layer and the business processing layer respectively; and to bind the intermediate content layer to each view and / or object by adding object attributes of the intermediate content layer to the class of each view and / or object.
5. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method as described in any one of claims 1-3.
6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the steps of the method as described in any one of claims 1-3.
