CN112559200A - User interface module processing method, door phone and storage medium - Google Patents
User interface module processing method, door phone and storage medium Download PDFInfo
- Publication number
- CN112559200A CN112559200A CN201910912205.XA CN201910912205A CN112559200A CN 112559200 A CN112559200 A CN 112559200A CN 201910912205 A CN201910912205 A CN 201910912205A CN 112559200 A CN112559200 A CN 112559200A
- Authority
- CN
- China
- Prior art keywords
- module
- registration
- target
- management process
- screen attribute
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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)
- Human Computer Interaction (AREA)
- Telephone Function (AREA)
Abstract
The embodiment of the application provides a processing method of a user interface module, a door phone and a storage medium, wherein the method comprises the following steps: sending an acquisition request to a management process through a User Interface (UI) process, forwarding the acquisition request to a main process through the management process, wherein the acquisition request is used for acquiring screen attribute parameters of the door phone, receiving the acquisition request and acquiring the screen attribute parameters through the main process, sending the screen attribute parameters to the management process, forwarding the screen attribute parameters to the UI process through the management process, receiving the screen attribute parameters through the UI process, and loading a target UI module corresponding to the screen attribute parameters. In the technical scheme, the UI process and the main process are mutually independent, and the UI process can be adapted to the UI module under the condition of being separated from the main process, so that the development efficiency is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of intelligent security and particularly relates to a processing method of a user interface module, a door phone and a storage medium.
Background
At present, along with the continuous improvement of the safety consciousness of users, the door phone is installed outside the building more and more generally. The door phone is a device for providing a two-way conversation between a visitor and a user, and the visitor can call and converse with the user through the door phone of the building so as to control the opening of the door lock of the building. This not only enhances security but also reduces the need to go upstairs and downstairs to unlock the lock.
In an actual application process, the door phone belongs to an embedded device, and a User Interface (UI) module provided by the door phone is embedded in the main program in a thread manner, for example, when the UI module is downloaded, the entire firmware package of the door phone needs to be downloaded.
However, in the above-described method, the UI module cannot be independently developed from the main program, which results in low development efficiency.
Disclosure of Invention
The embodiment of the application provides a processing method of a user interface module, a door phone and a storage medium, so that a UI process and a main process are mutually independent, and the development efficiency is improved.
In a first aspect, an embodiment of the present application provides a method for processing a user interface module, which is applied to an entrance machine, and the method includes:
sending an acquisition request to a management process through a User Interface (UI) process, and forwarding the acquisition request to a main process through the management process, wherein the acquisition request is used for acquiring screen attribute parameters of the doorway machine;
receiving the acquisition request and acquiring the screen attribute parameters through the main process, and sending the screen attribute parameters to the management process;
and forwarding the screen attribute parameters to the UI process through the management process, receiving the screen attribute parameters through the UI process, and loading a target UI module corresponding to the screen attribute parameters.
In a possible implementation manner, the sending, by the UI process, an acquisition request to the management process, and forwarding, by the management process, the acquisition request to the host process includes:
detecting whether the door phone has a UI function;
if the door phone has the UI function, sending a first registration request to the management process through the UI process, and sending a second registration request to the management process through the main process, wherein the first registration request comprises an address of the UI process, and the second registration request comprises the address of the main process;
returning a first registration result to the UI process through the management process, and returning a second registration result to the main process;
and if the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful, sending an acquisition request to the management process through the UI process, and forwarding the acquisition request to the main process through the management process, wherein the acquisition request comprises an address of the main process.
In one possible embodiment, the method further comprises:
if the first registration result indicates that the registration fails and/or the second registration result indicates that the registration fails, the UI process sends the first registration request to the management process after a preset time length, and/or the main process sends the second registration request to the management process after the preset time length, and the steps are repeated until the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful.
In one possible embodiment, the method further comprises:
and upgrading the target UI module on line.
In a possible implementation manner, the loading, by the UI process, the target UI module corresponding to the screen attribute parameter includes:
acquiring a target UI module corresponding to the screen attribute parameter from locally downloaded UI modules through the UI process;
and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
In one possible embodiment, the method further comprises:
acquiring any UI module except the target UI module from the locally downloaded UI modules;
and taking the UI module as the target UI module.
In a possible implementation manner, the loading, by the UI process, the target UI module corresponding to the screen attribute parameter includes:
acquiring a target UI module corresponding to the screen attribute parameter on line through the UI process;
and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
In one possible embodiment, the screen property parameter includes at least one of:
resolution, size, memory, and image bit depth supported by the doorway machine.
In a second aspect, embodiments of the present application provide an outdoor unit, a processor, a display, a memory, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement the method according to any one of the first aspect.
In a third aspect, an embodiment of the present application provides a storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method according to any one of the first aspect.
The embodiment of the application provides a processing method of a user interface module, a door phone and a storage medium, wherein the method comprises the following steps: sending an acquisition request to a management process through a User Interface (UI) process, forwarding the acquisition request to a main process through the management process, wherein the acquisition request is used for acquiring screen attribute parameters of the door phone, receiving the acquisition request and acquiring the screen attribute parameters through the main process, sending the screen attribute parameters to the management process, forwarding the screen attribute parameters to the UI process through the management process, receiving the screen attribute parameters through the UI process, and loading a target UI module corresponding to the screen attribute parameters. In the technical scheme, the UI process and the main process are mutually independent, and the UI process can be adapted to the UI module under the condition of being separated from the main process, so that the development efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a schematic diagram of an architecture of a conventional doorway machine according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of an outdoor unit according to an embodiment of the present application;
fig. 3 is a first flowchart illustrating a processing method of a user interface module according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of inter-process communication provided by an embodiment of the present application;
fig. 5 is a second flowchart illustrating a processing method of a user interface module according to an embodiment of the present application;
fig. 6 is a third schematic flowchart of a processing method of a user interface module according to an embodiment of the present application;
FIG. 7 is a schematic diagram of UI module upgrade provided by an embodiment of the application;
FIG. 8 is a schematic diagram of a replacement UI module provided in an embodiment of the application;
fig. 9 is a schematic structural diagram of an outdoor machine according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
First, terms related to the present application will be explained:
a main process: 1) the system comprises a Software Development Kit (SDK), a proprietary protocol and the like, and can perform data interaction, analysis protocol and the like through a network; 2) the method comprises the steps of including product-related capability sets, specifically including a device internal capability set, an SDK capability set and the like; 3) the system comprises a platform packaging layer, a sensor and a data Processing module, wherein the platform packaging layer is used for encryption when interacting with the platform layer, and configuring General Purpose Input/Output (GPIO), Digital Signal Processing (DSP), the sensor and the like; 4) and performing interactive execution of parameter storage and reading operation with the database.
And (3) UI process: 1) communicating with a main program through a UI protocol data packet, which may include, for example, a socket, to obtain parameters; 2) the system comprises a platform packaging layer, a user interface module and a user interface module, wherein the platform packaging layer is used for interacting with the UI module, acquiring key/touch messages of the user and the like.
Fig. 1 is a schematic structural diagram of an existing door phone according to an embodiment of the present application, and as shown in fig. 1, a UI module in an existing door phone is embedded in a main program, and cannot be developed independently from the main program in a process of developing the UI module, that is, a UI process cannot be developed independently from the main process, and for example, a whole firmware package needs to be downloaded when the UI module is downloaded.
Therefore, the defects of low development efficiency, low development quality, UI customization and the like exist, and particularly, the customized development of the UI cannot be provided for a third party, so that the UI theme presented to a user is not rich enough, and the user experience is influenced. The main process runs as a main program, the UI process runs as a program in UI modules, and each UI module corresponds to one UI theme.
In view of the above problem, an embodiment of the present application provides a door phone, and fig. 2 is a schematic structural diagram of the door phone provided in the embodiment of the present application, as shown in fig. 2, a main program and a UI module of the door phone provided in the embodiment are independent of each other, that is, the main process and the UI process are independent of each other, where the main process and the UI process establish communication through a UI protocol data packet. The n UI modules are shown in FIG. 2 and are marked as UI module-1 and UI module-2 … UI module-n, so that plug and play of the UI modules are realized, the development efficiency and the development quality are improved, UI customization is provided, the UI themes are rich and diverse, and the user experience is improved.
It can be understood that the execution main body in the embodiment of the present application may be a door phone, and may also be an embedded device similar to the door phone, which may be determined according to an actual situation, and is not described herein again.
The technical solution shown in the present application will be described in detail by the following specific examples. It should be noted that the following specific embodiments may be combined with each other, and description of the same or similar contents is not repeated in different embodiments.
Fig. 3 is a first flowchart illustrating a processing method of a user interface module according to an embodiment of the present application. As shown in fig. 3, the model obtaining method provided in the embodiment of the present application may include the following steps:
s101, sending an acquisition request to a management process through a User Interface (UI) process, and forwarding the acquisition request to a main process through the management process.
Generally, because the UI module of the door phone is embedded into the main program, the main program and the UI module refer to and call each other, so that the main process and the UI process cannot be independent of each other, and the problem of low development efficiency is caused in the development process. To solve this problem, the communication process executed when the door phone is started in this embodiment at least includes a UI process, a main process, and a management process. The UI process is used for running a program in the UI module, the main process is used for running a main program, and the management process is used for detecting the communication condition of the UI process and the main process, so that the management of the UI process and the main process is realized. The main process and the UI process are mutually independent, so that high cohesion and low coupling of the processes are realized, mutual reference among the processes is effectively avoided, and the stability, the independence and the expandability of codes can be improved.
The specific implementation of interprocess communication is described in detail below in conjunction with fig. 4.
Fig. 4 is a schematic diagram of inter-process communication provided in an embodiment of the present application. As shown in fig. 4, the management process provides a routing relay function, and when each process needs to be redirected, the request is sent to the management process, and the management process forwards the request to the receiving process. In addition, the inter-process communication adopts a client/server C/S mode, a receiving and transmitting full duplex mode is established among the processes, and the receiving process can process various requests concurrently.
Referring to fig. 4, the management process includes a first sending module, a first receiving module, a second sending module and a second receiving module, the sending process stores the request in the shared memory of the sending process and sends the request to the first sending module of the management process, the request includes the address of the receiving process and the operation to be performed by the receiving process, which may be, for example, a request to obtain certain data, which the first sending module then forwards to the second receiving module, then the second receiving module forwards the request to the shared memory of the corresponding receiving process, after the receiving process executes the corresponding operation, the returned result may be, for example, data, stored in the shared memory of the receiving process, and sent to the second sending module of the management process, then the second sending module returns the data to the first receiving module, and the first receiving module stores the data in the shared memory of the sending process. The solid lines in fig. 4 represent returned results and the dashed lines represent requests.
It should be noted that the sending process may be a UI process, and the receiving process may be a host process.
In this embodiment, the door phone sends an acquisition request to the management process through the UI process, where the acquisition request is used to acquire a screen attribute parameter of the door phone, and the acquisition request is forwarded to the host process through the management process, where the screen attribute parameter includes at least one of the following: resolution, size, memory, and image bit depth supported by the doorway machine.
Illustratively, the address of the receiving process, that is, the address of the host process, may be included in the acquisition request.
S102, receiving the acquisition request and acquiring the screen attribute parameters through the main process, and sending the screen attribute parameters to the management process.
The main process can interact with the database, and after receiving the acquisition request, the main process executes corresponding operation according to the acquisition request, namely, acquires the screen attribute parameters of the doorway machine from the data, and then sends the screen attribute parameters to the management process.
S103, the screen attribute parameters are forwarded to the UI process through the management process, the screen attribute parameters are received through the UI process, and the target UI module corresponding to the screen attribute parameters is loaded.
Correspondingly, the management process forwards the screen attribute parameters to the UI process, and the UI process loads the target UI module corresponding to the screen attribute parameters after receiving the screen attribute parameters.
The screen attribute parameters and the UI module have a mapping relationship, and the mapping relationship can be a one-to-one mapping relationship or a many-to-one mapping relationship. Optionally, in the development process, a display screen adapted to each UI module is set, that is, each UI module corresponds to at least one screen attribute parameter. Exemplarily, if the resolution is within a first preset range, the size is within a second preset range, the size is within a third preset range, and the image bit depth supported by the door phone is within a fourth preset range, the corresponding UI module is the first UI module, and in the same manner, the attribute parameters of the display screen adapted to different UI modules, that is, the screen attribute parameters, can be obtained, where each UI module corresponds to one UI theme. Then, in this embodiment, after the screen attribute parameter is obtained, the target UI module corresponding to the screen attribute parameter may be loaded according to a mapping relationship established in advance, and the theme of the door phone after the loading is the UI theme corresponding to the target UI module.
Of course, the embodiment only exemplarily illustrates the implementation process of the mapping relationship between the screen attribute parameters and the UI module, and in the actual application process, the embodiment is not limited to the above manner.
Exemplarily, step S103 may be implemented as follows:
acquiring a target UI module corresponding to the screen attribute parameters from the locally downloaded UI module through a UI process; and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
Specifically, the door phone locally downloads a plurality of UI modules in advance, and can acquire a target UI module corresponding to the screen attribute parameter from locally downloaded UI modules through a UI process, and load the target UI module to display a UI theme corresponding to the target UI module, that is, use the UI theme as a UI theme of the door phone. Therefore, data flow can be saved, and the target UI module matched with the screen attribute parameters can be directly obtained from the locally downloaded UI module.
Alternatively, step S103 can also be implemented as follows:
acquiring a target UI module corresponding to the screen attribute parameter on line through a UI process; and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
Specifically, in some scenarios, the memory of the door phone is limited, and the UI module is not pre-stored locally, and then the target UI module corresponding to the screen attribute parameter is acquired online through the UI process, and the target UI module is loaded, and the UI theme corresponding to the target UI module is displayed. Thus, the problem of limited local storage space is solved.
The processing method of the user interface module provided by the embodiment comprises the following steps: sending an acquisition request to a management process through a User Interface (UI) process, forwarding the acquisition request to a main process through the management process, wherein the acquisition request is used for acquiring screen attribute parameters of the door phone, receiving the acquisition request and acquiring the screen attribute parameters through the main process, sending the screen attribute parameters to the management process, forwarding the screen attribute parameters to the UI process through the management process, receiving the screen attribute parameters through the UI process, and loading a target UI module corresponding to the screen attribute parameters. In the technical scheme, the UI process and the main process are mutually independent, and the UI process can be adapted to the UI module under the condition of being separated from the main process, so that the development efficiency is improved.
On the basis of the foregoing embodiment, fig. 5 is a second flowchart illustrating a processing method of a user interface module according to an embodiment of the present application. As shown in fig. 5, the method provided in this embodiment specifically includes the following steps:
s201, detecting whether the door phone has a UI function.
Before sending the obtaining request, it is further required to detect whether the door phone has the UI function, and if the door phone does not have the UI function, the processing method of the user interface module provided in this embodiment is not applicable to the door phone. In this embodiment, when the door phone is started, it is detected whether the door phone has a UI function, and the implementation process of detecting the UI function is not described in detail in this embodiment, which is similar to the prior art.
S202, if the door machine has the UI function, sending a first registration request to the management process through the UI process, and sending a second registration request to the management process through the main process.
S203, returning a first registration result to the UI process through the management process, and returning a second registration result to the main process.
The management process is used for managing the UI process and the main process, and the management process can only realize data forwarding if the process successfully registered with the management process. In this embodiment, if the door phone has a UI function, before the UI process sends the acquisition request, the first registration request is sent to the management process through the UI process, and the second registration request is sent to the management process through the host process, where the first registration request includes an address of the UI process, the second registration request includes an address of the host process, and after the management process receives the first registration request and the second registration request, the first registration result may be returned to the UI process, and the second registration result may be returned to the host process.
It is noted that the first registration result and the second registration result may indicate that the registration is successful, and may also indicate that the registration is failed. Illustratively, when the management process receives a first registration request sent by the UI process, registration may fail due to a network reason, and the management process does not store the address of the UI process; if the registration is successful, the management process may save the address of the UI process.
Further, if the registration fails, when the UI process sends an acquisition request to the management process, the management process cannot forward the acquisition request to the main program process after receiving the acquisition request.
It is worth noting that the host process registers in a similar manner as the UI process.
And S204, if the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful, sending an acquisition request to the management process through the UI process, and forwarding the acquisition request to the main process through the management process.
And if the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful, sending an acquisition request to the management process through the UI process, wherein the acquisition request comprises the address of the main process, and if the management process judges that the main process corresponding to the address is registered and the registration is successful, forwarding the acquisition request to the process corresponding to the address, namely the main process.
It should be noted that this embodiment only describes communication between the UI process and the main process, and in different application processes, the embodiment may further include a serial port command process, a Session Initiation Protocol (SIP) server process, a GNU General Public License (GPL) process, and the like. Therefore, in this embodiment, the obtaining request includes the address of the receiving main program, so that after the management process receives the obtaining request, when it is determined that the corresponding receiving process is the main process according to the address, the obtaining request is forwarded to the main process.
Optionally, step S101 may further include:
if the first registration result indicates that the registration fails and/or the second registration result indicates that the registration fails, the UI process sends a first registration request to the management process after the preset time length, and/or the main process sends a second registration request to the management process after the preset time length, and the steps are repeated until the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful.
In this embodiment, after the door phone is started, the UI process sends a first registration request to the management process, the host process sends a second registration request to the management process, if the first registration result indicates that the registration fails and/or the second registration result indicates that the registration fails, the UI process sends the first registration request to the management process after a preset duration, and/or the host process sends the second registration request to the management process after the preset duration, and this step is repeated until the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful. That is, in the registration process, if the registration fails due to a network reason, the registration is performed again after a preset time period until the registration is successful, and at this time, steps S205 to S206 may be executed, so as to load the target UI module, and the theme of the door phone after the loading is completed is the UI theme corresponding to the target UI module.
S205, receiving the acquisition request and acquiring the screen attribute parameters through the main process, and sending the screen attribute parameters to the management process.
S206, the screen attribute parameters are forwarded to the UI process through the management process, the screen attribute parameters are received through the UI process, and the target UI module corresponding to the screen attribute parameters is loaded.
The implementation process of steps S206-S207 is similar to that of steps S102-S103, and is not described herein again.
The processing method of the user interface module provided by the embodiment comprises the following steps: detecting whether the door phone has a UI function, if the door phone has the UI function, sending a first registration request to the management process through the UI process, and sending a second registration request to the management process through the main process, wherein the first registration request comprises an address of the UI process, the second registration request comprises the address of the main process, returning a first registration result to the UI process through the management process, and returning a second registration result to the main process, if the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful, sending an acquisition request to the management process through the UI process, forwarding the acquisition request to the main process through the management process, and the acquisition request comprises the address of the main process. By means of registration of each process to the management process, the management process forwards the acquisition request according to the address, accuracy of data transmission is improved, and the acquisition request is prevented from being transmitted to other processes.
On the basis of the foregoing embodiment, fig. 6 is a third schematic flowchart of a processing method of a user interface module provided in the embodiment of the present application. As shown in fig. 6, the processing method of the user interface module provided in the embodiment of the present application further includes the following steps:
s301, upgrading the target UI module on line.
In this embodiment, since the UI process and the host process are independent of each other, the UI process can adapt the target UI module according to the screen property parameters. Thus, in the development process, the UI special team can only concentrate on the design of the UI module, and the customized development of a third party is realized. Compared with the prior art, the method only needs to upgrade the UI module, does not need to upgrade the firmware package, and improves the development efficiency.
Fig. 7 is a schematic diagram of UI module upgrade provided in the embodiment of the present application, and as shown in fig. 7, a UI module of a door phone is upgraded from a UI module v1 to a UI module v2, and accordingly, a theme of the door phone becomes a UI theme corresponding to the UI module v2, it should be noted that power off is not allowed in an upgrade process.
Wherein, the number of locally downloaded UI modules is multiple, and after step S103, the method may further include the steps of:
and S302, acquiring any UI module except the target UI module from the locally downloaded UI modules.
S303, taking the UI module as a target UI module.
In some scenarios, the door phone locally downloads multiple UI modules, that is, multiple UI themes, so that the user can replace the currently displayed UI theme according to the preference, specifically, acquire any UI module except the target UI module from the locally downloaded UI modules, take the UI module as the target UI module, then load the target UI module, and display the UI theme corresponding to the target UI module.
Fig. 8 is a schematic diagram of replacing a UI module according to an embodiment of the application, and as shown in fig. 8, three UI modules, that is, a UI module-1, a UI module-2, and a UI module-3, are locally downloaded by the door phone, if the currently enabled UI module-1 is used, the UI module can be switched to the UI module-2 according to a user operation, and after the switching is completed, the UI theme displayed by the door phone is the UI theme corresponding to the UI module-2.
The processing method of the user interface module provided by the embodiment further includes: upgrading the target UI module on line; and acquiring any UI module except the target UI module from the locally downloaded UI modules, and taking the UI module as the target UI module. Therefore, the personalized theme is provided for the user to select, the user experience is improved, and compared with the prior art, the development efficiency is improved only by upgrading and replacing the UI module.
Fig. 9 is a schematic structural diagram of an outdoor unit according to an embodiment of the present application, and as shown in fig. 9, the outdoor unit includes a processor, a display, a memory, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the processor implements the processing method of the user interface module provided in any implementation manner of the foregoing method embodiments.
The present invention also provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the processing method of the user interface module provided in any of the implementation manners in the foregoing method embodiments.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present application, and are not limited thereto; although the embodiments of the present application have been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the embodiments of the present application.
Claims (10)
1. A processing method of a user interface module is applied to an entrance machine, and the method comprises the following steps:
sending an acquisition request to a management process through a User Interface (UI) process, and forwarding the acquisition request to a main process through the management process, wherein the acquisition request is used for acquiring screen attribute parameters of the doorway machine;
receiving the acquisition request and acquiring the screen attribute parameters through the main process, and sending the screen attribute parameters to the management process;
and forwarding the screen attribute parameters to the UI process through the management process, receiving the screen attribute parameters through the UI process, and loading a target UI module corresponding to the screen attribute parameters.
2. The method of claim 1, wherein sending the get request to a management process through a User Interface (UI) process, and forwarding the get request to a host process through the management process comprises:
detecting whether the door phone has a UI function;
if the door phone has the UI function, sending a first registration request to the management process through the UI process, and sending a second registration request to the management process through the main process, wherein the first registration request comprises an address of the UI process, and the second registration request comprises the address of the main process;
returning a first registration result to the UI process through the management process, and returning a second registration result to the main process;
and if the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful, sending an acquisition request to the management process through the UI process, and forwarding the acquisition request to the main process through the management process, wherein the acquisition request comprises an address of the main process.
3. The method of claim 2, further comprising:
if the first registration result indicates that the registration fails and/or the second registration result indicates that the registration fails, the UI process sends the first registration request to the management process after a preset time length, and/or the main process sends the second registration request to the management process after the preset time length, and the steps are repeated until the first registration result indicates that the registration is successful and the second registration result indicates that the registration is successful.
4. The method of claim 1, further comprising:
and upgrading the target UI module on line.
5. The method according to claim 1 or 2, wherein the loading, by the UI process, the target UI module corresponding to the screen property parameter comprises:
acquiring a target UI module corresponding to the screen attribute parameter from locally downloaded UI modules through the UI process;
and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
6. The method of claim 5, further comprising:
acquiring any UI module except the target UI module from the locally downloaded UI modules;
and taking the UI module as the target UI module.
7. The method according to claim 1 or 2, wherein the loading, by the UI process, the target UI module corresponding to the screen property parameter comprises:
acquiring a target UI module corresponding to the screen attribute parameter on line through the UI process;
and loading the target UI module through the UI process, and displaying the UI theme corresponding to the target UI module.
8. The method of claim 1, wherein the screen attribute parameters comprise at least one of:
resolution, size, memory, and image bit depth supported by the doorway machine.
9. An outdoor machine, comprising:
a processor, a display, a memory and a computer program stored on the memory and executable on the processor, the processor implementing the method according to any of the claims 1-8 when executing the program.
10. A storage medium having stored therein instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910912205.XA CN112559200A (en) | 2019-09-25 | 2019-09-25 | User interface module processing method, door phone and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910912205.XA CN112559200A (en) | 2019-09-25 | 2019-09-25 | User interface module processing method, door phone and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112559200A true CN112559200A (en) | 2021-03-26 |
Family
ID=75029317
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910912205.XA Pending CN112559200A (en) | 2019-09-25 | 2019-09-25 | User interface module processing method, door phone and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559200A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590248A (en) * | 2021-07-22 | 2021-11-02 | 上汽通用五菱汽车股份有限公司 | Screen projection method and device of vehicle-mounted terminal and readable storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103345405A (en) * | 2013-06-09 | 2013-10-09 | 贝壳网际（北京）安全技术有限公司 | Application program starting method and device and client |
| CN103777862A (en) * | 2013-11-29 | 2014-05-07 | 西安Tcl软件开发有限公司 | User interface self-adapting showing method and terminal |
| US8756461B1 (en) * | 2011-07-22 | 2014-06-17 | Juniper Networks, Inc. | Dynamic tracing of thread execution within an operating system kernel |
| CN103873908A (en) * | 2012-12-13 | 2014-06-18 | 三星电子株式会社 | Display apparatus, remote control apparatus, and method for providing user interface using the same |
| CN104102495A (en) * | 2014-07-31 | 2014-10-15 | 广州华多网络科技有限公司 | Window display method and device |
| CN104376016A (en) * | 2013-08-15 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Method and device for inter-process rendering in browser |
| CN104951269A (en) * | 2015-06-12 | 2015-09-30 | 上海卓易科技股份有限公司 | Method and device for automatically matching resolution rate and mobile terminal |
| CN109101233A (en) * | 2017-06-20 | 2018-12-28 | 福建星网视易信息系统有限公司 | It is adapted to the method, storage equipment and Android device of a variety of screen resolutions |
| CN109885302A (en) * | 2019-01-29 | 2019-06-14 | 维沃移动通信有限公司 | A kind of methods of exhibiting and terminal device applied fastly |
-
2019
- 2019-09-25 CN CN201910912205.XA patent/CN112559200A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8756461B1 (en) * | 2011-07-22 | 2014-06-17 | Juniper Networks, Inc. | Dynamic tracing of thread execution within an operating system kernel |
| CN103873908A (en) * | 2012-12-13 | 2014-06-18 | 三星电子株式会社 | Display apparatus, remote control apparatus, and method for providing user interface using the same |
| CN103345405A (en) * | 2013-06-09 | 2013-10-09 | 贝壳网际（北京）安全技术有限公司 | Application program starting method and device and client |
| CN104376016A (en) * | 2013-08-15 | 2015-02-25 | 腾讯科技（深圳）有限公司 | Method and device for inter-process rendering in browser |
| CN103777862A (en) * | 2013-11-29 | 2014-05-07 | 西安Tcl软件开发有限公司 | User interface self-adapting showing method and terminal |
| CN104102495A (en) * | 2014-07-31 | 2014-10-15 | 广州华多网络科技有限公司 | Window display method and device |
| CN104951269A (en) * | 2015-06-12 | 2015-09-30 | 上海卓易科技股份有限公司 | Method and device for automatically matching resolution rate and mobile terminal |
| CN109101233A (en) * | 2017-06-20 | 2018-12-28 | 福建星网视易信息系统有限公司 | It is adapted to the method, storage equipment and Android device of a variety of screen resolutions |
| CN109885302A (en) * | 2019-01-29 | 2019-06-14 | 维沃移动通信有限公司 | A kind of methods of exhibiting and terminal device applied fastly |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590248A (en) * | 2021-07-22 | 2021-11-02 | 上汽通用五菱汽车股份有限公司 | Screen projection method and device of vehicle-mounted terminal and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10285000B2 (en) | Apparatus and method for determining a wireless device's location after shutdown | |
| US20170295265A1 (en) | Communication protocol and system for network communications | |
| JP4932842B2 (en) | Network connectivity and radio conditions in the announcement area | |
| CN107203419B (en) | Method, device and system for calling among modules in application program | |
| CN110651241A (en) | Connecting multiple mobile devices to a smart home assistant account | |
| US20130332524A1 (en) | Data service on a mobile device | |
| US9621627B2 (en) | Dynamically launching a server-based application on a mobile device | |
| CN105519141A (en) | Seamless call transitions with pre-escalation participation confirmation | |
| US8688835B2 (en) | Service enablement/disablement based on service relationships | |
| WO2021073428A1 (en) | Account number binding method, device and system | |
| JP2010500792A (en) | Method for performing management operation by communication terminal, terminal, and system thereof | |
| RU2554570C2 (en) | Method and system for executing services on server and client of client-server architecture | |
| CN110417723B (en) | Application login method, device, terminal and storage medium | |
| EP2784661B1 (en) | Computer program product, information processing method, and information processing apparatus | |
| CN114286165A (en) | Display device, mobile terminal and screen projection data transmission method | |
| WO2023030265A1 (en) | Control method and electronic device | |
| WO2021102691A1 (en) | Resource subscription method and apparatus, computer device, and storage medium | |
| US20150256446A1 (en) | Method and apparatus for relaying commands | |
| CN112559200A (en) | User interface module processing method, door phone and storage medium | |
| CN114327087A (en) | Input event processing method and device, electronic equipment and storage medium | |
| US20160380811A1 (en) | Application hierarchy specification with real-time functional selection | |
| FR2939996A1 (en) | Machine to machine platform i.e. Internet server, for managing e.g. temperature sensor and mobile telephone, has communication management unit permitting communication of communicating objects via service matched with user account | |
| CN114995591B (en) | Sensor registration method, control system and related equipment | |
| US9819725B1 (en) | System, method, and computer program for remotely controlling mobile web applications installed on a mobile device | |
| CN115480910A (en) | Multi-cluster resource management method and device and electronic equipment |
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 |