CN112860454A - Service processing system and method - Google Patents
Service processing system and method Download PDFInfo
- Publication number
- CN112860454A CN112860454A CN202110163775.0A CN202110163775A CN112860454A CN 112860454 A CN112860454 A CN 112860454A CN 202110163775 A CN202110163775 A CN 202110163775A CN 112860454 A CN112860454 A CN 112860454A
- Authority
- CN
- China
- Prior art keywords
- service
- class
- flow
- event
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a service processing system and a service processing method, and belongs to the technical field of software architecture. The system comprises a model layer, a view layer and a service logic control layer, wherein the service logic control layer comprises a context environment class for external interaction, the context environment class comprises a plurality of service flows of a service processing system, and a single service flow comprises a plurality of service state classes; the context environment class is used for acquiring the service processing events from the view layer and/or the model layer and distributing the service processing events to the service flow for processing; the service flow is used for switching the service state class based on the received service processing event; and the service state class is used for executing the service logic corresponding to the service processing event and updating the user interface and/or the service data. The embodiment of the application can improve the maintainability and the expansibility of the service processing system by aggregating the service state classes in the service logic control layer into the service flow and then aggregating the service flow into the context environment class.
Description
Technical Field
The embodiment of the application relates to the technical field of software architecture, in particular to a service processing system and a service processing method.
Background
Currently, in the development process of a service processing system, a common service processing system includes an MVC (Model-View-Controller) mode, an MVP (Model-View-Presenter) mode, and an MVVM (Model-View Model) mode.
Taking the MVP mode as an example, in the MVP mode, the host layer is responsible for processing the service logic, the model layer is responsible for providing data, and the view layer is responsible for displaying the user interface, that is, all the service logic is deployed in the host layer.
With the iteration of the service versions, the service functions required to be implemented by the service processing system gradually increase, which results in the gradual increase of service logic in a service logic control layer (such as a moderator layer), further resulting in the overstaffed accumulation of the service logic, and poor maintainability and expansibility of the service processing system.
Disclosure of Invention
The embodiment of the application provides a business processing system and a business processing method, which can reduce the coupling between business logics, improve the cohesion between the business logics and increase the maintainability and the expansibility of the business processing system by providing a business state class for executing business logics, aggregating the business state class into a plurality of business flows and aggregating the plurality of business flows into a context environment class. The technical scheme is as follows:
according to an aspect of an embodiment of the present application, a service processing system is provided, where the system includes a model layer, a view layer, and a service logic control layer, where the service logic control layer includes a context environment class for external interaction, where the context environment class includes a plurality of service flows of the service processing system, and a single service flow includes a plurality of service state classes;
the model layer is used for storing the service data of the service processing system;
the view layer is used for displaying a user interface of the business processing system based on the business data;
the context environment class is used for acquiring the service processing event from the view layer and/or the model layer and distributing the service processing event to the service flow for processing;
the service flow is used for switching the service state class based on the received service processing event;
and the service state class is used for executing the service logic corresponding to the service processing event and updating the user interface and/or the service data.
According to an aspect of an embodiment of the present application, a service processing method is provided, where the method is applied to a service processing system, and the system includes a model layer, a view layer, and a service logic control layer, where the service logic control layer includes a context environment class for external interaction, the context environment class includes multiple service flows of the service processing system, and a single service flow includes multiple service state classes;
the method comprises the following steps:
the model layer stores the service data of the service processing system;
the view layer displays a user interface of the business processing system based on the business data;
the context environment class acquires a service processing event from the view layer and/or the model layer, and distributes the service processing event to the service flow for processing;
the service flow switches the service state class based on the received service processing event;
and the service state class executes the service logic corresponding to the service processing event and updates the user interface and/or the service data.
According to an aspect of the embodiments of the present application, a service processing apparatus is provided, which is applied to a service processing system, where the system includes a model layer, a view layer, and a service logic control layer, where the service logic control layer includes a context environment class for external interaction, the context environment class includes multiple service flows of the service processing system, and a single service flow includes multiple service state classes;
the device comprises:
the service data storage module is used for storing the service data of the service processing system through the model layer;
the user interface display module is used for displaying a user interface of the business processing system based on the business data through the view layer;
the processing event distribution module is used for acquiring the service processing event from the view layer and/or the model layer through the context environment class and distributing the service processing event to the service flow for processing;
a service state class switching module, configured to switch the service state class based on the received service processing event through the service flow;
and the service logic execution module is used for executing the service logic corresponding to the service processing event through the service state class and updating the user interface and/or the service data.
According to an aspect of the embodiments of the present application, there is provided a terminal, the terminal includes a processor and a memory, the memory stores a computer program, and the computer program is loaded and executed by the processor to implement the service processing method.
According to an aspect of the embodiments of the present application, there is provided a computer-readable storage medium, in which a computer program is stored, and the computer program is loaded and executed by a processor to implement the service processing method.
According to an aspect of embodiments herein, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the terminal reads the computer instruction from the computer readable storage medium, and the processor executes the computer instruction, so that the terminal executes the service processing method.
The technical scheme provided by the embodiment of the application can bring the following beneficial effects:
the service state classes for executing the service logic are provided, the plurality of service state classes are aggregated into the service flow, and the plurality of service flows are aggregated into the context environment class, so that the high aggregation among the service logics is realized, the overall process of the service flow can be known through the service state classes, the service function of the corresponding service flow can be known through the context environment class, the reading and understanding are facilitated, and the maintainability of the service processing system is improved.
In addition, each service state class is used for executing service logic corresponding to each service state class, each service flow is used for switching the service state class corresponding to each service flow, low coupling among the service state classes and low coupling among the service flows are realized, and thus each state flow or each service state class can be assembled and disassembled at low cost, and further the service processing system has good expansibility.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is an architecture diagram of a business processing system provided by one embodiment of the present application;
FIG. 2 is a flow diagram of an active switching of a traffic state class according to an embodiment of the present application;
FIG. 3 is a schematic diagram of internal interactions of a business processing system provided by one embodiment of the present application;
FIG. 4 is a schematic diagram of an interaction starting point of a business processing system provided by an embodiment of the present application;
fig. 5 is a schematic diagram of an interface relationship in a code architecture corresponding to a service logic control layer according to an embodiment of the present application;
fig. 6 is a flowchart of a service processing method according to an embodiment of the present application;
fig. 7 is a block diagram of a service processing apparatus according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Referring to fig. 1, an architecture diagram of a business processing system provided by an embodiment of the present application is shown. The service processing system may include: the service logic control layer 103 comprises a context environment class used for external interaction, the context environment class comprises a plurality of service flows of the service processing system, and a single service flow comprises a plurality of service state classes.
The model layer 101 is used for storing service data of the service processing system. The service data refers to data required by the service processing system to execute the service logic, and may include code data corresponding to the service logic, data required by the service processing system to display, and the like. For example, the data required for the business processing system display may be data such as pictures, words, symbols and the like required for the user interface, page and the like display. Optionally, the service processing system refers to a system for processing service events according to a series of service logics. For example, a task system of an application such as a video class, a live class, a music class, etc. may be implemented based on the business processing system. The business events may be, for example, display of a user interface, user interaction, data changes of the system, and the like. The service processing system executes the service logic to process the service event, and generates a service logic execution result, which may include change display data of the user interface, update adjustment data of the page, and the like. Optionally, the model layer 101 can also be used for loading of business data. For example, the model layer 101 obtains business data from a network or local database.
The view layer 102 is used to display a user interface of the business processing system based on the business data. The view layer 102 displays the service data visually through a user interface. For example, the view layer 102 constructs content of a user interface based on the business data, and the user interface displays the constructed content to the user. The view layer 102 may also update the display user interface based on the business logic execution results described above. Optionally, the viewing layer 102 may also provide a user with an interactive mode through a user interface. In response to a user interaction with respect to the user interface, such as clicking, pressing, sliding, and the like, the view layer 102 displays display content corresponding to the interaction through the user interface. For example, in response to a user interaction with respect to playing of a video in the user interface, the viewing layer 102 displays the corresponding video through the user interface.
Optionally, when the view layer 102 needs to show some service data, the required service data can be obtained from the model layer 101 through the service logic control layer 103.
The service logic control layer 103 is configured to process service logic of the service processing system. The business logic refers to rules and flows of data processing, such as data operation logic, data acquisition logic, data display logic and the like. For example, the service logic control layer 103 executes service data acquisition logic, and calls the model layer 101 to acquire corresponding service data.
Optionally, the context environment class in the business logic control layer 103 is an interaction portal of the business logic control layer 103. The context environment class may be used to obtain the business process events from the view layer 102 and/or the model layer 101 and distribute the business process events to the business flow for processing. For example, the context environment class may be used to obtain user interaction operations (e.g., gesture clicks, etc.) from the view layer 102, the context environment class may be used to obtain data change notifications, etc. from the model layer 101, which is not limited in this embodiment of the present application.
The view layer 102 or the model layer 101 may obtain service flow deployment and a service state class corresponding to the service flow in the service logic control layer 103 through the context environment class. For example, referring to fig. 1, the view layer 102 may obtain, through context environment classes, that the logical control layer 103 includes at least 2 service flows, and each service flow includes at least 3 service state classes.
The context environment class is an aggregate class of traffic flows. A context class may include multiple traffic streams, each having uniqueness, any two traffic streams being independent of each other. For example, a context class includes service flow a and service flow B, and whether service flow a is invoked does not affect service flow B.
Optionally, different contextual environment classes correspond to different types of traffic flow sets. For example, taking a service processing system corresponding to a video application as an example, a first context environment class of the service processing system may include service flows such as praise, forward, comment, and the like for an existing video. The second context environment class of the service processing system may include service flows for recording, adjusting, uploading, etc. of videos.
The service flow refers to a service chain, and has a complete service function. A traffic flow may include multiple traffic state classes, each traffic state class having uniqueness. For example, referring to fig. 1, traffic flow a may include a plurality of traffic state classes, traffic state class 1, traffic state class 2, traffic state class 3, and so on. The traffic flow may be used to switch traffic state classes based on the received traffic handling events. For example, taking the above comment service flow as an example, the comment service flow may include a select service status class, an edit service status class, and a publish service status class. The current service state class of the service flow is a selected service state class, and if the service flow receives a service processing event input by a processing user, the selected service state class is switched into an edited service state class by the service flow.
Optionally, the traffic flow further comprises an observable data storage class. The observable data storage class is used for driving service state class switching in the service flow, and the specific content of the observable data storage class can be as follows: the service flow is used for executing a state class switching method of the service flow and updating data in the observable data storage class; the observable data storage class is used for responding to a data updating event in the observable data storage class and generating updating callback information, and the updating callback information is used for acquiring the first service state class; the service flow is used for switching the current service state class of the service flow to the first service state class based on the updated callback information. The first traffic state class may be any traffic state class in the traffic flow. The observable data store class may be user-defined. For example, the observable data store class LiveData (real-time data) may be used in the application component Activity.
In an example, the service state class may also actively perform service state class switching through a service flow, and the specific content thereof is as follows: the service state class is used for executing switching logic in the service state class, sending the identification information of the second service state class to the service flow, and updating data in the observable data storage class by calling a state class switching method of the service flow; the observable data storage class is used for responding to a data updating event in the observable data storage class and generating the updating callback information, and the updating callback information comprises identification information of the second service state class; the service flow is used for switching the current service state class of the service flow to the second service state class based on the updated callback information. The second traffic state class may be any traffic state class in the traffic flow.
For example, referring to fig. 2, in a flow 201, the service state class a executes a switching logic of the service state class a, acquires identification information of the service state class B, and sends the identification information of the service state class B to a service flow, and meanwhile, the service state class a executes a service state class a release method to release held service data. Then, the service state class A updates the data in the observable data storage class of the service flow by calling a state class switching method in the service flow. And generating update callback information by observing the data storage class, acquiring a corresponding service state class B by the service flow based on the update callback information, and executing a hit method of the service state class B to enable the service state class B to start executing corresponding service logic.
Optionally, one traffic flow corresponds to one context class. For example, the service flow a cannot exist in both context environment class 1 and context environment 2, the service flow a exists only in context environment class 1 or only in context environment 2, and the service flow a only receives the service processing event corresponding to the context environment class.
The service state class is an interactive outlet, and can be used for executing service logic corresponding to the service processing event and updating the user interface and/or the service data. For example, taking the above-mentioned selection of the service state class as an example, if the current service state class of the service flow is the selection service state class, the selection service state class executes the service logic corresponding to the user-selected interactive operation, processes the user-selected interactive operation, and controls the user interface to display the interface effect corresponding to the user-selected interactive operation. Optionally, the service status class may also include user interface logic, data update logic, and the like. The user interface logic is used for processing the service data corresponding to the user interface, and the data updating logic is used for processing the service data in the model layer.
Optionally, one traffic state class corresponds to one traffic flow. For example, traffic state class a cannot exist in both traffic flow 1 and traffic flow 2, and traffic state class a exists in either traffic flow 1 or traffic flow 2, and traffic state class a only responds to the handoff process of the corresponding traffic flow.
Optionally, the service data is shared between the service state class and the service state through the service flow. For example, comment traffic is taken as an example. And part of comment data is shared among the selected service state class, the edited service state class and the published service state class through comment service streams.
In summary, according to the technical scheme provided by the embodiment of the present application, the service state classes for executing the service logic are provided, the plurality of service state classes are aggregated into the service flow, and the plurality of service flows are aggregated into the context environment class, so that high aggregation between the service logics is achieved, the overall flow of the service flow can be known through the service state classes, the service function of the corresponding service flow can be known through the context environment class, and the service processing system is convenient to read and understand, and the maintainability of the service processing system is improved.
In addition, each service state class is used for executing service logic corresponding to each service state class, each service flow is used for switching the service state class corresponding to each service flow, low coupling among the service state classes and low coupling among the service flows are realized, and thus each state flow or each service state class can be assembled and disassembled at low cost, and further the service processing system has good expansibility.
In addition, the data can be observed in the service flow to drive the service state class to be switched, so that the automatic switching of the service state class is realized, manual switching is not needed, and the efficiency of the service processing system for processing the service event is improved.
In an exemplary embodiment, referring to fig. 3, the interaction between the model layer, the view layer, and the business logic control layer may be as follows:
the model layer 301 and the service logic control layer 303 are in a bidirectional interaction relationship, and the service logic control layer 303 can obtain service data from the model layer 301. The model layer 301 may send traffic handling events to the traffic logic control layer 303.
The view layer 302 and the service logic control layer 303 are in a bidirectional interaction relationship. The view layer 302 may send the service handling event to the service logic control layer 303, and the service logic control layer 303 may control the view layer 302 to update the user interface of the display service handling system.
It should be noted that model layer 301 does not directly interact with view layer 302. The view layer 302 obtains the business data from the model layer 301 through the business logic control 303.
Optionally, the interaction relationship between the view layer, the model layer, the context environment class, the service flow and the service state class may be as follows:
there is a one-way interaction between the view layer 302 and the context class 304. The context environment class 304 is provided with an interactive interface for interaction of the view layer 302, and the view layer 302 obtains a current service state class of each service flow in the context environment class 304 through the corresponding interactive interface, and sends a service processing event to the context environment class 304 to notify the context environment class 304 of switching the service state class. The contextual environment class 304 cannot actively operate on the view layer 302.
There is a one-way interaction between the context class 304 and the traffic flow 305. Context class 304 may actively operate traffic flow 305. For example, the context environment class 304 may obtain or update the current traffic state class of the traffic flow 305. Traffic flow 305 cannot actively operate on context class 304.
The service flow 305 and the service status class 306 are in a bidirectional interaction relationship. The traffic flow 305 may actively switch the traffic state flow 306, and the traffic state flow 306 may also be actively switched through the traffic flow 305.
Optionally, the traffic flow 305 also has a one-way interaction relationship with the model layer 301. The service flow 305 needs corresponding service data in the model layer 301 when constructing a new service flow or adjusting a service flow. Traffic flow 305 may actively update traffic data in the model layer and may also operate methods in model layer 301 such as resource loading, lookup, modification, deletion, and the like. The model layer 301 cannot actively operate on the traffic flow 305.
There is a one-way interaction between the business state class 306 and the model layer 301. The service state class 305 may actively update service data in the model layer and may also operate methods in the model layer 301, such as resource loading, lookup, modification, deletion, and the like. The model layer 301 cannot actively operate on the traffic state class 306.
Optionally, the business state class 306 also has a one-way interaction relationship with the view layer 302. The business state class 306 executes the corresponding user interface logic to display the user interface for updating through the viewing layer 302. The view layer 302 cannot actively operate on the traffic status class 306.
There is a one-way interaction between the model layer 301 and the context swap environment class 304. The model layer 301 may actively send business process events to the context switch environment class 304. For example, when data (e.g., service data required for displaying a user interface) in the model layer 301 changes, the model layer 301 sends a corresponding data change event to the context environment class 304, and notifies the context environment class 304 to invoke a target service state class in a corresponding service flow.
In an exemplary embodiment, referring to fig. 4, the interaction starting point of the business processing system may include at least the following three points:
1. the interaction starting point 401 corresponds to an interface operation event of a view layer, and the specific interaction process is as follows:
the context environment class is used for acquiring interface operation events from the view layer; determining a first traffic flow associated with an interface operation event from a plurality of traffic flows; and distributing the interface operation event to the first service flow for processing. The interface operation event refers to the interactive operation of a user aiming at the user interface. For example, the user may perform a trigger operation on a resource download control, perform a trigger operation on a video play control, and the like, which is not limited in the embodiment of the present application.
For example, a user's trigger operation for a resource download control is taken as an example. And the view layer informs the interface operation event to the context environment class through a corresponding interface in the context environment class. The context environment class distributes the interface operation event to the corresponding service flow. The business flow is switched to a corresponding business state class, corresponding business resource obtaining logic is executed, a model layer is called to load corresponding resources, after the resources are loaded, the model layer can inform a context environment class that the resources are loaded, the context environment class calls the data from the model layer through the business state class, then the context environment class controls the business flow to be switched to the business state class used for executing the user interface logic, and finally the data is displayed to a user through a view layer.
2. The interaction starting point 402 corresponds to a data update event of the application model layer, and the specific interaction process is as follows:
the context environment class is used for acquiring data updating events from the model layer; determining a second traffic flow associated with the data update event from the plurality of traffic flows; and distributing the data updating event to a second service flow for processing. The data update event may refer to an update event of code data corresponding to the service logic, data required for displaying by the service processing system, and the like.
For example, take the case of a business processing system displaying desired data. And the model layer informs the data updating event to the context environment class through a corresponding interface in the context environment class. The context environment class distributes the interface operation event to the corresponding service flow. And switching the service flow to a corresponding service state class, executing corresponding user interface logic, and updating a user interface through a view layer.
3. The interaction starting point 403 corresponds to a system (or application) triggered global event, and the specific interaction process is as follows:
the service flow is used for acquiring a global event triggered by the system, the global event is registered in the service flow in advance, and the service state class is switched based on the global event; the service state class is used for executing the service logic corresponding to the global event and updating the user interface and/or the service data. Wherein, the global event is used to prompt the service flow system (or application) to change. Different global events are registered in different traffic flows. For example, a Global event such as a GPS (Global Positioning System) or a network may be registered in a traffic flow for Positioning. Events such as network and foreground and background switching can be registered in the service flow for resource downloading. Optionally, the registration and the counterregistration of the global event are both in the traffic flow, and when the global event is triggered, the traffic flow directly receives the corresponding global event.
For example, a network global event (such as a network outage, etc.) is taken as an example. The context environment class distributes the network global event to the corresponding traffic flow after receiving the network global event. And switching the service flow to a corresponding service state class, executing a corresponding user interface logic, and displaying the network global event to a user through a view layer.
In an exemplary embodiment, referring to fig. 5, the interface relationship in the code architecture corresponding to the service logic control layer may be as follows:
in the corresponding code of the service logic control layer, a context environment class interface 501 is represented by an IContext interface, a service flow interface 502 is represented by an IFlow interface, a service state class interface 504 is represented by an IState interface, and a model layer interface 503 is represented by an IData interface. The IContext interface comprises a plurality of IFlow interfaces, and the IFlow interfaces comprise a plurality of ISTATE interfaces. Meanwhile, the IFlow interface and the IState interface depend on the IData interface.
The method and properties of the IFlow interface may be as follows:
1. map < UniqueKey, state > attribute, which is used to define the service state class set contained in the current service flow, and each specific service flow may contain different service state class sets. This attribute needs to be implemented in a specific traffic flow.
2. An IData attribute, which is used to represent a specific model object. The service logic control layer needs to construct a complete service flow from IData, which can be implemented in AbsFlow (base class service flow).
3. And the ISTATE attribute is used for representing the current service state class of the service flow. This attribute needs to be updated when switching traffic state classes.
4. The UniqueKey attribute, which is used to mark the uniqueness of a traffic flow, can be implemented in a specific traffic flow.
5. And the Destroy method is used for controlling the current service flow to release the held resources and destroying the current service flow. The method can be realized in AbsFlow, and can also be specifically realized in specific service flows according to actual conditions.
6. The SetState method, which is used to switch traffic state classes, can be implemented in AbsFlow.
7. An ObservableData attribute, which defines observable data storage classes, may be used to drive traffic state class switching. Alternatively, LiveData may be used as the observable data class, or the user may customize the observable data storage class. This attribute may be implemented in AbsFlow.
The method and properties of the IState interface may be as follows:
1. the UniqueKey attribute, which is used to mark the uniqueness of the service state class, can be implemented in a specific service state class.
2. The IFlow attribute is used to indicate the service flow to which the current service state class belongs, and is implemented in AbsState (base class service state class).
3. And the Hit method is used for hitting the target service state class and executing the service logic corresponding to the target service state class, wherein each service state class corresponds to different service logic. The method can be implemented in a specific service state class.
4. And the Next method is used for expressing switching logic from the current service state class to the Next service state class, and each service state class corresponds to different switching logic. The method can be implemented in a specific service state class.
5. The Destroy method is used for controlling the current service state class to release the held resources, can be realized in the AbsState, and can also be specifically realized in a specific service state class according to the actual situation.
In the code architecture corresponding to the business logic control layer, the most core part is to construct universal AbsFlow and AbsState. After the two base classes are constructed, if a new simple service flow needs to be constructed, only the corresponding service flow and the code corresponding to the service state class need to be simply filled. Alternatively, the code implementation may be based on the programming language Kotlin (cottlin).
It can be known from the interface methods and attributes of IFlow and IState that when AbsFlow and AbsState are perfect, adding a simple service chain only needs to simply fill Map < UniqueKey, IState > attribute in IFlow, and Hit method and Next method in IState.
For example, the model layer further includes a base class service flow and a base class service state class, the base class service flow refers to a universal service flow, the base class service state class refers to a universal service state class, and specific contents of the service processing system for constructing a new service flow may be as follows: the context environment class is used for acquiring the base class service flow and the base class service state class from the model layer, determining a base class service state class set included by the base class service flow, and determining service logic and switching logic corresponding to each base class service state class in the base class service state class set respectively to generate a new service flow.
In summary, according to the technical scheme provided by the embodiment of the present application, the service state classes for executing the service logic are provided, the plurality of service state classes are aggregated into the service flow, and the plurality of service flows are aggregated into the context environment class, so that high aggregation between the service logics is achieved, the overall flow of the service flow can be known through the service state classes, the service function of the corresponding service flow can be known through the context environment class, and the service processing system is convenient to read and understand, and the maintainability of the service processing system is improved.
In addition, each service state class is used for executing service logic corresponding to each service state class, each service flow is used for switching the service state class corresponding to each service flow, low coupling among the service state classes and low coupling among the service flows are realized, and thus each state flow or each service state class can be assembled and disassembled at low cost, and further the service processing system has good expansibility.
In addition, by setting the base class service flow and the base class service state class, the service flow can be added conveniently.
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings.
Referring to fig. 6, a flowchart of a service processing method according to an embodiment of the present application is shown. The method can be applied to the service processing system described in the above embodiment. The method comprises the following steps (601-605):
In one example, the specific processing content of the context environment class on the business processing event from the view layer may be as follows: the context environment class acquires an interface operation event from a view layer; determining a first service flow associated with the interface operation event from a plurality of service flows by the context environment class; the context environment class distributes the interface operation event to the first service flow for processing.
In one example, the specific processing content of the context environment class on the business process event from the model layer can be as follows: the context environment class acquires a data updating event from the model layer; determining a second traffic flow associated with the data update event from the plurality of traffic flows by the context environment class; the context environment class distributes the data update event to the second traffic flow for processing.
Optionally, the service flow may further include an observable data storage class, and the service flow may perform switching processing on the service state through the observable data storage class, where the specific content may be as follows: the service flow executes the state class switching method of the service flow, and data in the observable data storage class is updated; the observable data storage class responds to a data updating event in the observable data storage class and generates updating callback information, and the updating callback information is used for acquiring the first service state class; and the service flow switches the current service state class of the service flow to the first service state class based on the updated callback information.
Optionally, the service flow may also switch the service state class based on a global event triggered by the system, and the specific content may be as follows: and the service flow acquires a global event triggered by the system, wherein the global event is registered in the service flow in advance, and the service state class is switched based on the global event. The service state class executes the service logic corresponding to the global event and updates the user interface and/or the service data.
In an example, the service state class may also actively perform service state class switching through a service flow, and the specific content may be as follows: the service state class executes the switching logic in the service state class, sends the identification information of the second service state class to the service flow, and updates the data in the observable data storage class by calling the state class switching method of the service flow; the observable data storage class responds to a data updating event in the observable data storage class and generates updating callback information, and the updating callback information comprises identification information of the second service state class; and the service flow switches the current service state class of the service flow to a second service state class based on the updated callback information.
In an example, the model layer further includes a base class service flow and a base class service state class, the base class service flow refers to a universal service flow, and the base class service state class refers to a universal service state class. The context environment class may construct a new service flow through the base class service flow and the base class service state class, and the specific content may be as follows: the context environment class acquires the base class service flow and the base class service state class from the model layer, determines a base class service state class set included by the base class service flow, and determines service logics and switching logics corresponding to the base class service state classes in the base class service state class set respectively to generate a new service flow.
Optionally, any two traffic flows are independent of each other.
Optionally, one traffic flow corresponds to one context environment class; one traffic state class corresponds to one traffic flow.
In summary, according to the technical scheme provided by the embodiment of the present application, the service state classes for executing the service logic are provided, the plurality of service state classes are aggregated into the service flow, and the plurality of service flows are aggregated into the context environment class, so that high aggregation between the service logics is achieved, the overall flow of the service flow can be known through the service state classes, the service function of the corresponding service flow can be known through the context environment class, and the service processing system is convenient to read and understand, and the maintainability of the service processing system is improved.
In addition, each service state class is used for executing service logic corresponding to each service state class, each service flow is used for switching the service state class corresponding to each service flow, low coupling among the service state classes and low coupling among the service flows are realized, and thus each state flow or each service state class can be assembled and disassembled at low cost, and further the service processing system has good expansibility.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the system of the present application.
Referring to fig. 7, a block diagram of a service processing apparatus according to an embodiment of the present application is shown. The device has the function of realizing the service processing method example, and the function can be realized by hardware or by hardware executing corresponding software. The apparatus may be the terminal described above, or may be provided in the terminal. The apparatus 700 may include: a service data storage module 701, a user interface display module 702, a processing event distribution module 703, a service state class switching module 704 and a service logic execution module 705.
A service data storage module 701, configured to store the service data of the service processing system through the model layer.
A user interface display module 702, configured to display a user interface of the service processing system based on the service data through the view layer.
A processing event distributing module 703 is configured to obtain a service processing event from the view layer and/or the model layer through the context environment class, and distribute the service processing event to the service flow for processing.
A service state class switching module 704, configured to switch the service state class based on the received service processing event through the service flow.
The service logic executing module 705 is configured to execute the service logic corresponding to the service processing event through the service state class, and update the user interface and/or the service data.
In an exemplary embodiment, any two of the traffic flows are independent of each other.
In an exemplary embodiment, the processing event distribution module 703 is configured to:
acquiring an interface operation event from the view layer through the context environment class;
determining a first business flow associated with the interface operation event from the plurality of business flows through the context environment class;
and distributing the interface operation event to the first service flow for processing through the context environment class.
In an exemplary embodiment, the processing event distribution module 703 is further configured to:
acquiring a data updating event from the model layer through the context environment class;
determining a second traffic flow associated with the data update event from the plurality of traffic flows through the context environment class;
and distributing the data updating event to the second service flow for processing through the context environment class.
In an exemplary embodiment, the traffic state class switching module 704 is configured to:
acquiring a global event triggered by a system through the service flow, wherein the global event is registered in the service flow in advance, and switching the service state class based on the global event;
the service logic executing module 705 is further configured to execute the service logic corresponding to the global event through the service state class, and update the user interface and/or the service data.
In an exemplary embodiment, the traffic flow further includes an observable data storage class;
the service status class switching module 704 is further configured to:
executing a state class switching method of the service flow through the service flow, and updating data in the observable data storage class;
responding to a data updating event in the observable data storage class through the observable data storage class, and generating updating callback information, wherein the updating callback information is used for acquiring a first service state class;
and switching the current service state class of the service flow to the first service state class based on the updated callback information through the service flow.
In an exemplary embodiment, the service status class switching module 704 is further configured to:
executing switching logic in the service state class through the service state class, sending identification information of a second service state class to the service flow, and updating data in the observable data storage class by calling a state class switching method of the service flow;
responding to a data updating event in the observable data storage class through the observable data storage class, and generating the updating callback information, wherein the updating callback information comprises identification information of the second service state class;
and switching the current service state class of the service flow to the second service state class based on the updated callback information through the service flow.
In an exemplary embodiment, a traffic flow corresponds to a context environment class; one traffic state class corresponds to one traffic flow.
In an exemplary embodiment, the model layer further includes a base class service flow and a base class service state class, where the base class service flow refers to a universal service flow, and the base class service state class refers to a universal service state class;
the processing event distribution module 703 is further configured to obtain the base class service flow and the base class service state class from the model layer through the context environment class, determine a base class service state class set included in the base class service flow, and determine service logic and switching logic corresponding to each base class service state class in the base class service state class set, so as to generate a new service flow.
In summary, according to the technical scheme provided by the embodiment of the present application, the service state classes for executing the service logic are provided, the plurality of service state classes are aggregated into the service flow, and the plurality of service flows are aggregated into the context environment class, so that high aggregation between the service logics is achieved, the overall flow of the service flow can be known through the service state classes, the service function of the corresponding service flow can be known through the context environment class, and the service processing system is convenient to read and understand, and the maintainability of the service processing system is improved.
In addition, each service state class is used for executing service logic corresponding to each service state class, each service flow is used for switching the service state class corresponding to each service flow, low coupling among the service state classes and low coupling among the service flows are realized, and thus each state flow or each service state class can be assembled and disassembled at low cost, and further the service processing system has good expansibility.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus provided by the above embodiment and the system embodiment belong to the same concept, and the specific implementation process thereof is described in the system embodiment, which is not described herein again.
In an exemplary embodiment, there is also provided a terminal comprising a processor and a memory, wherein the memory stores a computer program, and the computer program is loaded by the processor and executed to implement the service processing method.
In an exemplary embodiment, a computer readable storage medium is also provided, in which a computer program is stored, which when executed by a processor, implements the above-described service processing method.
Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State drive), or optical disk. The Random Access Memory may include a ReRAM (resistive Random Access Memory) and a DRAM (Dynamic Random Access Memory).
In an exemplary embodiment, a computer program product or a computer program is also provided, which comprises computer instructions, which are stored in a computer-readable storage medium. And the processor of the terminal reads the computer instruction from the computer readable storage medium, and executes the computer instruction, so that the terminal executes the service processing method.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (13)
1. A service processing system is characterized in that the system comprises a model layer, a view layer and a service logic control layer, wherein the service logic control layer comprises a context environment class for external interaction, the context environment class comprises a plurality of service flows of the service processing system, and a single service flow comprises a plurality of service state classes;
the model layer is used for storing the service data of the service processing system;
the view layer is used for displaying a user interface of the business processing system based on the business data;
the context environment class is used for acquiring the service processing event from the view layer and/or the model layer and distributing the service processing event to the service flow for processing;
the service flow is used for switching the service state class based on the received service processing event;
and the service state class is used for executing the service logic corresponding to the service processing event and updating the user interface and/or the service data.
2. The system of claim 1, wherein any two of the traffic streams are independent of each other.
3. The system of claim 1, wherein the context class is configured to:
acquiring an interface operation event from the view layer;
determining a first traffic flow associated with the interface operation event from the plurality of traffic flows;
and distributing the interface operation event to the first service flow for processing.
4. The system of claim 1, wherein the context class is configured to:
acquiring a data updating event from the model layer;
determining a second traffic flow associated with the data update event from the plurality of traffic flows;
and distributing the data updating event to the second service flow for processing.
5. The system of claim 1,
the service flow is also used for acquiring a global event triggered by the system, wherein the global event is registered in the service flow in advance and is used for switching the service state class based on the global event;
and the service state class is used for executing the service logic corresponding to the global event and updating the user interface and/or the service data.
6. The system of claim 1, wherein the traffic flow further comprises an observable data storage class;
the service flow is also used for executing a state class switching method of the service flow and updating data in the observable data storage class;
the observable data storage class is used for responding to a data updating event in the observable data storage class and generating updating callback information, and the updating callback information is used for acquiring a first service state class;
and the service flow is also used for switching the current service state class of the service flow to the first service state class based on the updated callback information.
7. The system of claim 6,
the service state class is also used for executing switching logic in the service state class, sending identification information of a second service state class to the service flow, and updating data in the observable data storage class by calling a state class switching method of the service flow;
the observable data storage class is configured to generate the update callback information in response to a data update event in the observable data storage class, where the update callback information includes identification information of the second service state class;
and the service flow is also used for switching the current service state class of the service flow to the second service state class based on the updated callback information.
8. The system according to any of claims 1 to 7, wherein a traffic flow corresponds to a context class; one traffic state class corresponds to one traffic flow.
9. The system according to any one of claims 1 to 7, wherein the model layer further includes a base class service flow and a base class service status class, the base class service flow refers to a universal service flow, and the base class service status class refers to a universal service status class;
the context environment class is further configured to obtain the base class service flow and the base class service state class from the model layer, determine a base class service state class set included in the base class service flow, and determine service logic and switching logic corresponding to each base class service state class in the base class service state class set, so as to generate a new service flow.
10. A service processing method is applied to a service processing system, the system comprises a model layer, a view layer and a service logic control layer, the service logic control layer comprises a context environment class for external interaction, the context environment class comprises a plurality of service flows of the service processing system, and a single service flow comprises a plurality of service state classes;
the method comprises the following steps:
the model layer stores the service data of the service processing system;
the view layer displays a user interface of the business processing system based on the business data;
the context environment class acquires a service processing event from the view layer and/or the model layer, and distributes the service processing event to the service flow for processing;
the service flow switches the service state class based on the received service processing event;
and the service state class executes the service logic corresponding to the service processing event and updates the user interface and/or the service data.
11. A service processing device is applied to a service processing system, wherein the system comprises a model layer, a view layer and a service logic control layer, the service logic control layer comprises a context environment class for external interaction, the context environment class comprises a plurality of service flows of the service processing system, and a single service flow comprises a plurality of service state classes;
the device comprises:
the service data storage module is used for storing the service data of the service processing system through the model layer;
the user interface display module is used for displaying a user interface of the business processing system based on the business data through the view layer;
the processing event distribution module is used for acquiring the service processing event from the view layer and/or the model layer through the context environment class and distributing the service processing event to the service flow for processing;
a service state class switching module, configured to switch the service state class based on the received service processing event through the service flow;
and the service logic execution module is used for executing the service logic corresponding to the service processing event through the service state class and updating the user interface and/or the service data.
12. A terminal, characterized in that it comprises a processor and a memory, in which a computer program is stored, which computer program is loaded and executed by the processor to implement the service processing method according to claim 10.
13. A computer-readable storage medium, in which a computer program is stored, which is loaded and executed by a processor to implement the service processing method according to claim 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110163775.0A CN112860454B (en) | 2021-02-05 | 2021-02-05 | Service processing system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110163775.0A CN112860454B (en) | 2021-02-05 | 2021-02-05 | Service processing system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112860454A true CN112860454A (en) | 2021-05-28 |
| CN112860454B CN112860454B (en) | 2024-04-19 |
Family
ID=75989402
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110163775.0A Active CN112860454B (en) | 2021-02-05 | 2021-02-05 | Service processing system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112860454B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1556490A (en) * | 2004-01-08 | 2004-12-22 | 上海复旦光华信息科技股份有限公司 | Multi surce audit data business uniformity judging method based on state conversion table |
| US20060036448A1 (en) * | 2001-06-13 | 2006-02-16 | Caminus Corporation | System architecture and method for energy industry trading and transaction management |
| US20080052664A1 (en) * | 2006-08-25 | 2008-02-28 | Ritwik Batabyal | e-ENABLER PRESCRIPTIVE ARCHITECTURE |
| US20080320486A1 (en) * | 2003-06-12 | 2008-12-25 | Reuters America | Business Process Automation |
| CN101526906A (en) * | 2008-03-07 | 2009-09-09 | 上海汇和信息技术有限公司 | Management system for running maintenance services |
| US20130159898A1 (en) * | 2011-12-14 | 2013-06-20 | Holger Knospe | Launch of target user interface features based on specific business process instances |
| US20140026120A1 (en) * | 2012-07-19 | 2014-01-23 | International Business Machines Corporation | Unit testing an enterprise javabeans (ejb) bean class |
| CN103745399A (en) * | 2014-01-22 | 2014-04-23 | 长沙钢为网络科技有限公司 | Auction processing system and method |
| CN104346412A (en) * | 2013-08-09 | 2015-02-11 | 中国科学院沈阳自动化研究所 | Semantic information based RFID (Radio Frequency Identification Device) complex event processing method |
| US20160239770A1 (en) * | 2015-02-13 | 2016-08-18 | Wipro Limited | Method and system for dynamically changing process flow of a business process |
| CN107239324A (en) * | 2017-05-22 | 2017-10-10 | 阿里巴巴集团控股有限公司 | Work flow processing method, apparatus and system |
| CN107656821A (en) * | 2016-07-25 | 2018-02-02 | 武汉票据交易中心有限公司 | The processing method and relevant apparatus and server of a kind of operation flow |
| CN108241487A (en) * | 2016-12-26 | 2018-07-03 | 北京中普达科技股份有限公司 | The system architecture of mobile equipment performance can be improved |
| CN108460516A (en) * | 2018-01-22 | 2018-08-28 | 深圳前海数创人工智能有限公司 | A kind of weather warning forecasts services intelligent management system and method |
| CN109101223A (en) * | 2018-07-26 | 2018-12-28 | 北京大米未来科技有限公司 | A kind of Business Process Control method, Business Process Control engine and system |
| CN109672582A (en) * | 2018-09-25 | 2019-04-23 | 平安普惠企业管理有限公司 | Complete trails monitoring method, equipment, storage medium and device |
| CN110399429A (en) * | 2019-07-30 | 2019-11-01 | 阿里巴巴集团控股有限公司 | A kind of distributed transaction processing method and system |
| CN111694555A (en) * | 2020-06-18 | 2020-09-22 | 国网宁夏电力有限公司营销服务中心(国网宁夏电力有限公司计量中心) | Business system construction method and device, electronic equipment and storage medium |
| CN111897815A (en) * | 2020-07-15 | 2020-11-06 | 中国建设银行股份有限公司 | Service processing method and device |
-
2021
- 2021-02-05 CN CN202110163775.0A patent/CN112860454B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060036448A1 (en) * | 2001-06-13 | 2006-02-16 | Caminus Corporation | System architecture and method for energy industry trading and transaction management |
| US20080320486A1 (en) * | 2003-06-12 | 2008-12-25 | Reuters America | Business Process Automation |
| CN1556490A (en) * | 2004-01-08 | 2004-12-22 | 上海复旦光华信息科技股份有限公司 | Multi surce audit data business uniformity judging method based on state conversion table |
| US20080052664A1 (en) * | 2006-08-25 | 2008-02-28 | Ritwik Batabyal | e-ENABLER PRESCRIPTIVE ARCHITECTURE |
| CN101526906A (en) * | 2008-03-07 | 2009-09-09 | 上海汇和信息技术有限公司 | Management system for running maintenance services |
| US20130159898A1 (en) * | 2011-12-14 | 2013-06-20 | Holger Knospe | Launch of target user interface features based on specific business process instances |
| US20140026120A1 (en) * | 2012-07-19 | 2014-01-23 | International Business Machines Corporation | Unit testing an enterprise javabeans (ejb) bean class |
| CN104346412A (en) * | 2013-08-09 | 2015-02-11 | 中国科学院沈阳自动化研究所 | Semantic information based RFID (Radio Frequency Identification Device) complex event processing method |
| CN103745399A (en) * | 2014-01-22 | 2014-04-23 | 长沙钢为网络科技有限公司 | Auction processing system and method |
| US20160239770A1 (en) * | 2015-02-13 | 2016-08-18 | Wipro Limited | Method and system for dynamically changing process flow of a business process |
| CN107656821A (en) * | 2016-07-25 | 2018-02-02 | 武汉票据交易中心有限公司 | The processing method and relevant apparatus and server of a kind of operation flow |
| CN108241487A (en) * | 2016-12-26 | 2018-07-03 | 北京中普达科技股份有限公司 | The system architecture of mobile equipment performance can be improved |
| CN107239324A (en) * | 2017-05-22 | 2017-10-10 | 阿里巴巴集团控股有限公司 | Work flow processing method, apparatus and system |
| CN108460516A (en) * | 2018-01-22 | 2018-08-28 | 深圳前海数创人工智能有限公司 | A kind of weather warning forecasts services intelligent management system and method |
| CN109101223A (en) * | 2018-07-26 | 2018-12-28 | 北京大米未来科技有限公司 | A kind of Business Process Control method, Business Process Control engine and system |
| CN109672582A (en) * | 2018-09-25 | 2019-04-23 | 平安普惠企业管理有限公司 | Complete trails monitoring method, equipment, storage medium and device |
| CN110399429A (en) * | 2019-07-30 | 2019-11-01 | 阿里巴巴集团控股有限公司 | A kind of distributed transaction processing method and system |
| CN111694555A (en) * | 2020-06-18 | 2020-09-22 | 国网宁夏电力有限公司营销服务中心(国网宁夏电力有限公司计量中心) | Business system construction method and device, electronic equipment and storage medium |
| CN111897815A (en) * | 2020-07-15 | 2020-11-06 | 中国建设银行股份有限公司 | Service processing method and device |
Non-Patent Citations (5)
| Title |
|---|
| FANGFANG LIU ET AL.: "Discovery of Web Service Flow based on Service Context", INTERNATION JOURNAL OF WEB SERVICE RESEARCH * |
| 吕磊;杨雪;朱礼鹏;谢俊虎;金元;: "基于UC客户端的MVVM应用与研究", 计算机与网络, no. 05 * |
| 胡杰;周鹏飞;郭乔进;: "基于MVC设计模式的SSH框架的研究", 信息化研究, no. 01 * |
| 邹晶;刘毅敏;: "基于有限状态机的工作流引擎的设计", 计算机应用与软件, no. 08 * |
| 郭广丰;邬海燕;: "基于开源工作流引擎的电子审批系统开发", 阴山学刊(自然科学版), no. 04 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112860454B (en) | 2024-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104484189B (en) | The structure and design method of a kind of application interface | |
| US20180060055A1 (en) | Application containers with dynamic sub-package loading | |
| KR101478134B1 (en) | File management method for mobile device and mobile device using thereof | |
| CN104504106B (en) | A kind of map covering zone rendering method and relevant device | |
| US11561675B2 (en) | Method and apparatus for visualization of public welfare activities | |
| TWI388992B (en) | System and method for producing and communicating requested data among networked application programs | |
| CN112711728B (en) | Page layout frame, page loading method, device, equipment and storage medium | |
| CN116139485B (en) | Virtual resource exchange method, device, electronic device and storage medium | |
| CN114363679B (en) | Display equipment, server and media asset playing method | |
| CN112860454A (en) | Service processing system and method | |
| CN111970192A (en) | Information editing method and device based on session group | |
| US11908049B2 (en) | Data processing device and method, electronic apparatus for data visualization | |
| CN114357093A (en) | Regional resource management and application system based on digital live-action map | |
| CN111381976B (en) | Method and device for updating message prompt data, storage medium and computer equipment | |
| CN116257719B (en) | Page updating method, page updating device, computer equipment and storage medium | |
| CN110908745B (en) | Data analysis display method and system, storage medium, server and client | |
| CN116233217B (en) | Page jump method and device based on route, electronic equipment and storage medium | |
| CN115599880A (en) | Map legend configuration management method and terminal | |
| Capilla et al. | Addressing usability requirements in mobile software development | |
| CN114416250A (en) | Page display control method, device, equipment and storage medium | |
| KR102750107B1 (en) | Method and apparatus for managing to-do list | |
| CN112395384A (en) | Map configuration method and device, intelligent robot and storage medium | |
| CN114653061B (en) | Data processing method, device, electronic device and storage medium | |
| CN115080030B (en) | Method, medium and device for interactive linkage between browser chart and UE4 three-dimensional scene based on webrtc | |
| CN112667410A (en) | Cross-process communication method, terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |