CN112099895A

CN112099895A - Interface notification message scheduling method, device, equipment and storage medium

Info

Publication number: CN112099895A
Application number: CN202011039487.6A
Authority: CN
Inventors: 关安杰
Original assignee: Guangzhou Huaduo Network Technology Co Ltd
Current assignee: Guangzhou Cubesili Information Technology Co Ltd
Priority date: 2020-09-28
Filing date: 2020-09-28
Publication date: 2020-12-18

Abstract

The application discloses a method, a device, equipment and a storage medium for scheduling interface notification messages, wherein the method comprises the following steps: starting to receive an interface notification message along with the starting of the application program process of the live broadcast room; shunting the view layers specified by the interface notification message to a message queue correspondingly arranged for the view layers to execute enqueue operation according to the view layers, wherein each view layer is correspondingly represented by a view container implementation interface associated with a root container; the message dequeuing module corresponding to each message queue executes dequeuing operation of the corresponding message queue according to the queue access rule; and executing display strategy control on each dequeued interface notification message, and outputting each interface notification message to the corresponding view layer to be displayed under the control of the display strategy control. The method is suitable for orderly managing the interface notification messages of various types, realizes the centralized and orderly scheduling of the view layers of different levels in the depth direction of the graphical user interface, can improve the development efficiency of the application program, and reduces the operating pressure of the operating equipment.

Description

Interface notification message scheduling method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer control technologies, and in particular, to a method, an apparatus, a device, and a storage medium for scheduling an interface notification message.

Background

With the development of network technology, people have more and more online entertainment projects, in recent years, live programs gradually come into the public view, and especially some excellent main live programs are more popular among audiences. In a live broadcast room, when a main broadcast shows a wonderful place, audiences often show the favorite of programs through actions of leaving messages, delivering gifts and the like for the main broadcast. In a live broadcast room service scene, various dynamic effects are displayed or various notifications are broadcasted in the live broadcast room according to actual services to feed back and stimulate positive behaviors of a user in the live broadcast room, for example, the user plays the exquisite dynamic effects to give visual feedback in response to the operation of the user for delivering gifts to a main broadcast, the operation result of delivering gifts or doing tasks is given the exquisite dynamic effects or the visual feedback of broadcasting and the like in the live broadcast room, the effort of the user is confirmed through the dynamic effects and the enthusiasm of the user in interaction in the live broadcast room is stimulated, and therefore the experience degree of the audience in watching live programs is improved. Similarly, the platform side often sends various notifications to the live room user, which are also presented by being sent to the user interface in the form of a broadcast.

In order to enrich the more exquisite effect of playing in a live broadcast room, a development team needs to develop more interface notification messages, and the team needs to plan the area and the display effect of the interface notification messages displayed on a graphical user interface of the live broadcast room for each interface notification message, so that a customized development mode needs to be performed on each interface notification message of different types, the difficulty of the team in developing new interface notification messages is greatly increased, the interface notification messages of different types are displayed in the graphical user interface of the live broadcast room in a messy mode, and the watching experience of audiences in the live broadcast room is seriously influenced.

It can be understood that, in a live broadcast room service scenario, when multiple types of interface notification messages are concurrent at a terminal device, the live broadcast room receives numerous interface notification messages of various types and cannot process the interface notification messages in order, so that the numerous interface notification messages are accumulated in a device cache, an application program in the live broadcast room crashes when the terminal device runs, and the experience of viewers in the live broadcast room is seriously affected.

In summary, in the prior art, there is no scheduling process with strong universality and expansibility, which is used for orderly coordinating and allocating the display of notification messages of various interfaces, and an effective solution for industrial development is urgently needed.

Disclosure of Invention

The primary object of the present application is to provide an interface notification message scheduling method, so as to process interface notification messages in a standardized manner.

As another object of the present application, there are provided an interface notification message scheduling apparatus, an electronic device, and a nonvolatile storage medium, which are adapted to the foregoing method.

In order to meet various purposes of the application, the following technical scheme is adopted in the application:

the interface notification message scheduling method provided by adapting to the primary object of the present application includes the following steps:

starting to receive an interface notification message along with the starting of the application program process of the live broadcast room;

shunting the view layers specified by the interface notification message to a message queue correspondingly arranged for the view layers to execute enqueue operation according to the view layers, wherein each view layer is correspondingly represented by a view container implementation interface associated with a root container;

the message dequeuing module corresponding to each message queue executes dequeuing operation of the corresponding message queue according to the queue access rule;

and executing display strategy control on each dequeued interface notification message, and outputting each interface notification message to the corresponding view layer to be displayed under the control of the display strategy control.

In a further embodiment, the method further comprises the following post-steps:

and responding to an exit event of the application program process of the live broadcast room, and recycling the memory occupied by executing the method.

In a further embodiment, when performing display policy control on each dequeued interface notification message, adapting to each dequeued interface notification message includes the following specific control steps:

instantiating a preset interface class for packaging the interface notification message to obtain an instance object;

acquiring interface object packaging data from the interface notification message as corresponding attribute item assignment of the instance object so as to construct an interface object to be displayed on the view layer;

acquiring a display strategy control identifier corresponding to the interface object from the interface notification message, and assigning values to corresponding attribute items of the instance object;

and transmitting the instance object to a display execution module for outputting the interface object to a view layer display, and driving the display execution module to be controlled to output the interface notification message to the corresponding view layer display.

In a preferred embodiment, the display policy control identifier includes a visibility monitoring identifier, which is used to set whether the interface notification message is visible in a specific environment, so as to control the display execution module to control the corresponding interface object to be visible or invisible in the specific environment according to the visibility monitoring identifier.

In a further embodiment, the display policy control identifier includes a display duration identifier, which is used to set a display duration of the interface object of the interface notification message, so as to control the display execution module to control the corresponding interface object to be displayed for the corresponding duration according to the display duration identifier, and then to end the display.

In some embodiments, the display execution module executes the following steps before outputting the interface notification message to the corresponding view layer for display: detecting whether an interface notification message which is currently displayed exists in a view layer designated by the interface notification message which needs to be displayed, and executing the interface notification message which needs to be displayed when the view layer has no interface notification message which is currently displayed.

In some embodiments, the method further comprises the following steps:

and monitoring the idle duration of each message queue/view layer, and when the idle duration of one message queue/view layer exceeds a preset value, recovering the memory of the message queue/view layer.

In a further embodiment, the view layers and/or the message queues specified by the interface notification message are shunted to the step of performing enqueue operation on the message queues correspondingly set for the view layers according to the view layers specified by the interface notification message, and when the view layers and/or the message queues specified by the interface notification message do not exist, corresponding view layers and/or message queues are created for the view layers and/or the message queues.

In a preferred embodiment, after the live broadcast application program process is started, in response to a user instruction generated by a user through touch control on a graphical user interface of the live broadcast application program, a corresponding interface notification message is generated, and both the interface notification message and the interface notification message received from the server are used for shunting and added to a corresponding message queue.

An interface notification message scheduling apparatus adapted to other objects of the present application includes:

the message receiving module is configured to start receiving the interface notification message along with the start of the application program process of the live broadcast room;

the message enqueuing module is used for shunting the view layers specified by the interface notification message to a message queue correspondingly arranged for the view layers to execute enqueuing operation according to the view layers, and each view layer is correspondingly represented by a view container implementation interface associated with a root container;

the message dequeuing module is independently configured for each message queue and used for executing dequeuing operation of the corresponding message queue according to the queue access rule;

and the message display module is used for executing display strategy control on each dequeued interface notification message and outputting each interface notification message to the corresponding view layer to be displayed under the control of the message display module.

Another object of the present application is to provide an electronic device, which includes a central processing unit and a memory, wherein the central processing unit is used for invoking and running a computer program stored in the memory to execute the steps of the interface notification message scheduling method described in the present application.

A non-volatile storage medium storing a computer program according to the method for scheduling an interface notification message is provided, and when the computer program is called by a computer, the computer program performs the steps included in the method.

Compared with the prior art, the application has the following advantages:

firstly, the application constructs a view layer management module of a tree structure consisting of a root container, a view container and view layers, distributes appointed view layers for various interface notification messages, fully utilizes the Z axis of a graphical user interface of a live broadcast room, intensively and uniformly manages the display of the interface messages, constructs a queue management module of a plurality of message queues which are in one-to-one correspondence with the view layers in combination with the application, controls various interface notification messages to occupy the display sequence of the appointed view layers, and controls the message queues to process the display of various interface notification messages in the graphical user interface of the live broadcast room according to the first-in first-out principle, thereby preventing the various interface notification messages from being displayed in the same view layer in a messy way and influencing the viewing experience of audiences in the live broadcast room; when different development teams need to define own interface notification messages, only the principle implemented by the application needs to be known, and the relevant view layers are designated for displaying the own interface notification messages, so that the application program implementing the scheme of the application can display the interface notification messages in order, and the application program can realize ordered coordination.

Secondly, in order to enhance and manage the display of various types of interface notification messages in a graphical user interface of a live broadcast room, display strategy control is executed on the interface notification messages dequeued from the message queue, the various types of interface notification messages are controlled to be output to corresponding view layers of the interface notification messages to be displayed, and the visualization process of the various types of interface message notifications is standardized.

In addition, the interface notification message is listed and pushed to the corresponding view layer for displaying, the technical process of processing the interface notification message in the traditional application is changed and enriched, the interface of the interface notification message is standardized, and the technical scheme is suitable for being assembled into the same application program.

Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a schematic diagram of a typical network deployment architecture related to implementing the technical solution of the present application;

FIG. 2 is a flowchart illustrating an exemplary embodiment of an interface notification message scheduling method according to the present application;

fig. 3 is a schematic specific flowchart of step S14 in the interface notification message scheduling method according to the present application;

FIG. 4 is a style diagram of a live broadcast room graphical user interface of the present application;

fig. 5 is a schematic flowchart of another embodiment of an interface notification message scheduling method according to the present application, in which a post-step is added;

fig. 6 is a schematic flowchart of a method for scheduling an interface notification message according to another embodiment of the present application, in which a post-step is added;

fig. 7 is a schematic block diagram of an exemplary embodiment of an interface notification message scheduling apparatus according to the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.

As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.

It will be understood by those within the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As will be appreciated by those skilled in the art, "client," "terminal," and "terminal device" as used herein include both devices that are wireless signal receivers, which are devices having only wireless signal receivers without transmit capability, and devices that are receive and transmit hardware, which have receive and transmit hardware capable of two-way communication over a two-way communication link. Such a device may include: cellular or other communication devices such as personal computers, tablets, etc. having single or multi-line displays or cellular or other communication devices without multi-line displays; PCS (Personal Communications Service), which may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (Personal Digital Assistant), which may include a radio frequency receiver, a pager, internet/intranet access, a web browser, a notepad, a calendar and/or a GPS (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "client," "terminal device" can be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. The "client", "terminal Device" used herein may also be a communication terminal, a web terminal, a music/video playing terminal, such as a PDA, an MID (Mobile Internet Device) and/or a Mobile phone with music/video playing function, and may also be a smart tv, a set-top box, and the like.

The hardware referred to by the names "server", "client", "service node", etc. is essentially an electronic device with the performance of a personal computer, and is a hardware device having necessary components disclosed by the von neumann principle such as a central processing unit (including an arithmetic unit and a controller), a memory, an input device, an output device, etc., a computer program is stored in the memory, and the central processing unit calls a program stored in an external memory into the internal memory to run, executes instructions in the program, and interacts with the input and output devices, thereby completing a specific function.

It should be noted that the concept of "server" as referred to in this application can be extended to the case of a server cluster. According to the network deployment principle understood by those skilled in the art, the servers should be logically divided, and in physical space, the servers may be independent from each other but can be called through an interface, or may be integrated into one physical computer or a set of computer clusters. Those skilled in the art will appreciate this variation and should not be so limited as to restrict the implementation of the network deployment of the present application.

Referring to fig. 1, the hardware basis required for implementing the related art embodiments of the present application may be deployed according to the architecture shown in the figure. The server 80 is deployed at the cloud end, and serves as a front-end application server, and is responsible for further connecting a related data server, a video streaming server, and other servers providing related support, so as to form a logically associated server cluster to provide services for related terminal devices, such as a smart phone 81 and a personal computer 82 shown in the figure. Both the smart phone and the personal computer can access the internet through a known network access mode, and establish a data communication link with the cloud server 80 so as to run a terminal application program related to the service provided by the server. In the related technical solution of the present application, the protocol packet sent by the server 80 may be received by the smart phone 81 or a personal computer (collectively referred to as a terminal device or a local device), and the terminal device runs a corresponding application program to perform corresponding processing on the protocol packet.

It should be noted that, in a server cluster supporting the live broadcast room operation, in some scenarios, a server supporting the live broadcast room message service and a server supporting the live broadcast room video stream synthesis are merged into the same server or the same network address, and sometimes, the same application server may be used independently to establish the mutual association of the whole cluster, so that the server finally responsible for the service can be pointed to by using the same network address. In this regard, those skilled in the art will appreciate.

In order to support the operation of the application program, the terminal device is equipped with a related operating system, such as an IOS (operating system), an HMS (grand Mongolian), an Android and other operating systems providing equivalent functions, and with the support of such an operating system, the application program developed adaptively can be normally operated, so that human-computer interaction and remote interaction are realized.

The method is programmed and built in a terminal device application program providing the network live broadcast as a basic service function. The live webcast refers to a live webcast room network service realized based on the network deployment architecture.

The live broadcast room is a video chat room realized by means of an internet technology, generally has an audio and video broadcast control function and comprises a main broadcast user and audience users, wherein the audience users can comprise registered users registered in a platform or unregistered tourist users; either registered users who are interested in the anchor user or registered or unregistered users who are not interested in the anchor user. The interaction between the anchor user and the audience user can be realized through known online interaction modes such as voice, video, characters and the like, generally, the anchor user performs programs for the audience user in the form of audio and video streams, and economic transaction behaviors can also be generated in the interaction process. Of course, the application form of the live broadcast room is not limited to online entertainment, and can be popularized to other relevant scenes, such as an educational training scene, a video conference scene, a product recommendation and sale scene, and any other scene needing similar interaction.

The application program running on the terminal device can trigger and display the interface notification message according to the requirement designed by the platform side, and the currently common interface notification message is mainly used for playing dynamic effect information or broadcast information, and is certainly not limited to the method. It will thus be appreciated that any action supported by the live room service that is intended to output some notification message to the graphical user interface of the live room constructed when the application is running can be understood as an interface notification message of the present application.

The dynamic effect information is also called dynamic special effect information, interface special effect information and the like, and is mainly used as a basis for playing animation in a graphical user interface of a live broadcast room so as to play a corresponding dynamic special effect and further realize a message notification effect.

The broadcast information, like the dynamic effect information, is a notification message sent to the terminal user for implementing notification of a certain message, and after reaching the terminal device, the broadcast information finally causes the related content to be displayed in the graphical user interface of the live broadcast room of the terminal device.

Similar interface notification messages are not exhaustive, and the classification criteria among various types are mainly distinguished according to the communication protocol maintained by each other, but not necessarily according to the content and form of the notification message displayed by the interface notification messages. Currently, there are multiple such communication protocols in active application products in the market provided in the industry, such as live broadcast room approach live-action communication protocol, live broadcast room anchor level upgrade live-action data communication protocol, live broadcast room user level upgrade live-action data communication protocol, live broadcast room gift live-action data communication protocol, live broadcast room banner live-action data communication protocol, other live-action classes in the live broadcast room, broadcast-class data communication protocol, and so on. It can be seen that all kinds of notification messages of the above implementations can be summarized as the interface notification message in the present application.

The person skilled in the art will know this: although the various methods of the present application are described based on the same concept so as to be common to each other, they may be independently performed unless otherwise specified. In the same way, for each embodiment disclosed in the present application, it is proposed based on the same inventive concept, and therefore, concepts of the same expression and concepts of which expressions are different but are appropriately changed only for convenience should be equally understood.

Referring to fig. 2, an interface notification message scheduling method of the present application is programmed to be implemented in a live broadcast application program to run in a terminal device, and in an exemplary embodiment, the method includes the following steps:

step S11, starting to receive an interface notification message along with the start of the live broadcast application program process:

the method and the device are mainly applied to the live broadcast application program, so that the live broadcast application program main process is responsible for receiving various types of interface notification messages, and similarly, the interface notification messages can be generated by local triggering or pushed to the local by a server. Accordingly, it can be understood that the interface notification message may be an interface notification message generated by a user instruction generated by a local live broadcast room graphical user interface touch control, or an interface notification message transmitted by a server providing a live broadcast room service received through a communication link.

The interface notification message includes type information for describing various types of interface notification messages, the type information is generally suitable for identifying different types of fields, identifying different expression forms, representing fields of different senders, and the like, and the effect of the type information is related to, for example, the application can determine the specified view layer according to the type information of the interface notification message, and add the interface notification message to a message queue corresponding to the view layer according to the identifier of the view layer, so as to classify all the received various types of interface notification messages.

The method of the present application will be programmed to function as a built-in function module of the live-air application, and will therefore be invoked to run along with the start of the live-air application process, so that when the live-air application is started, the interface notification message will begin to be received.

Step S12, according to the view layer specified by the interface notification message, shunting the view layer to a message queue correspondingly set for the view layer to perform enqueue operation, where each view layer is represented by a view container implementation interface associated with a root container:

the method comprises the steps of constructing a message queue corresponding to each view layer in a graphical user interface one by one, storing interface notification messages corresponding to the view layers on the premise of following a first-in first-out principle, and controlling the output sequence of output display of the view layers appointed by the interface notification messages occupied by the interface notification messages.

In one embodiment, the method and the device determine, according to the view layer indexes included in the type information of the interface notification message, the view layer which is designated to be output and displayed of each type of interface notification message, and add the view layer to the tail of the message queue corresponding to the designated view layer in order to complete the execution of the enqueue operation, so that the function of shunting the received interface notification messages of each type is realized.

In other embodiments, if the type information of the interface notification message does not include a plaintext description of a specific view-layer index, the type information of the interface notification message may be locally queried to determine the corresponding view-layer index locally through the type information of the interface notification message by querying a table having a mapping relationship between the type information and the view-layer index locally, so as to achieve the same effect as that in the previous embodiment.

In order to have the capacity of orderly processing a large number of interface notification messages, the method is responsible for maintaining a tree structure formed by view layers, each view layer is correspondingly represented by a view container, the view containers are used for centrally managing the view layers which are responsible for representation, and all the view containers are associated with the same root container so as to realize the tree structure organization. Therefore, the root container is suitable for centralized management of one or more view containers, and it can be understood that only one root container needs to be arranged in one live broadcast room to organize all view layers. In order to determine a specific view layer conveniently, the view layer is assigned with a corresponding index number, and the view layer can be directly called by providing the same number as the index of the view layer. Once this tree structure is created, the root container and the various view containers therein may persist in the cache unless destroyed. It is understood that the view layer may be created as needed or destroyed as needed.

The corresponding class of the root container can be customized by a developer, for example, the Android-based View or View group base class is developed by customization as required, so that the root container has the capability of View group suitable for supporting a View container (such as View) and a View group, that is, the root container is suitable for managing the View container of the next level in an associated manner, and the View container and the root container can be instantiated from the same customized class. Theoretically, since the root container has the equivalent capability of the View group, the root container can further manage the parent container of the next level in an associated manner, the parent container and the root container are derived from the same self-defined class and have the equivalent capability of the root container for supporting the View of the next level, and the tree structure constructed based on the class derivation relationship can realize the organization and calling of a great number of View containers. In general, on the basis of the root container, a single-layer view container is associated, so that the use requirements of a general number of view layers can be met. If the developer knows that the required view layers are more, multi-layer cascade connection can be realized to meet the requirement. A developer may extend some attributes or interfaces to enrich the functionality of a view container while customizing a root container and its associated classes of view containers, as long as such implementation does not affect the implementation of the present application, as will be appreciated by those skilled in the art.

It will be appreciated that the same view container may be multiplexed multiple times to serve the same type of interface notification message, or may be used a single time, as to how the application is specific, as may be flexibly determined by those skilled in the art. For example, in an embodiment of multiplexing a view layer, a target view layer that is created and used for the first time is used for displaying an interface notification message corresponding to the target view layer in a live broadcast graphical user interface, and may be used for loading other interface notification messages subsequently, where the content of type information of the interface notification message itself is completely determined, that is, as long as different interface notification messages specify the same view layer index in respective type information, or the type information may be locally queried to correspond to the view layer index, the view layer corresponding to the view layer index may be sequentially multiplexed by the different interface notification messages.

Interface notification messages are often frequent, and therefore, a large number of interface notification messages often need to be processed within the same time period. When the situation exists, because a large number of interface notification messages specify at least part of different view layer indexes, and different view layers are called according to the different indexes to display different interface objects in the step, the display positions of the large number of interface notification messages are finally displayed through different levels in the Z-axis depth direction of the graphical user interface between live broadcast, and the display process is parallel and not contradictory. Therefore, the method and the system have the scheduling service capability of displaying the notification messages of different interfaces by utilizing different levels of the Z-axis depth direction of the graphical user interface, can automatically, scientifically and reasonably organize the display of the notification messages of the interfaces, and meet the service requirements of the dynamic effect information of the notification messages of various types of interfaces which are continuously increased.

And combining the message queue and the tree structure formed by the view layers to form a view layer appointed by the interface notification message, adding the view layer appointed by the interface notification message into a message queue arranged corresponding to the view layer, finishing the initial scheduling of the interface notification message, so that a message dequeuing module corresponding to each subsequent message queue executes dequeuing operation of the message queue according to a queue access rule, and controlling the interface notification message to be output to the corresponding view layer in a graphical user interface of a live broadcast room for display through display policy control.

Step S13, the dequeue module corresponding to each message queue executes dequeue operation of its corresponding message queue according to the queue access rule:

the message dequeuing module dequeues the interface notification messages stored in the message queues according to the first-in first-out principle, that is, the interface notification messages at the head of the message queues are preferentially dequeued, so that the subsequent interface notification messages are output to the designated view layer for display.

Each message queue needs to perform corresponding dequeue operation according to a queue access rule, so that the phenomenon that interface notification messages stored in the message queues are dequeued out of order due to the fact that the message queues dequeue the interface notification messages in an unordered mode, a large number of dequeued interface notification messages cannot be processed in order and are accumulated in a memory of terminal equipment, and sending crash of application programs in a live broadcast room or the terminal equipment is caused.

The queue access rule is used for defining the sequence of the dequeue operations executed by the message queues, and as an alternative embodiment, the time of the enqueue operation executed by each message queue can be monitored, and the dequeue operation of the message queue earlier in the enqueue operation is allowed to be executed preferentially by comparing the time of the enqueue operation executed by each message queue.

In another embodiment, which can be flexibly combined with other embodiments, priorities can be set for each message queue, corresponding priority setting is performed according to the type of the interface notification message stored in the message queue, and the message queue with higher priority preferentially executes dequeue operation, so that the queue access rules are enriched, and the definition of the access rules across the message queues is realized. Specific examples under such a definition are: the priority of the stored message queue with the interface notification message of the big gift type is higher than that of the stored message queue with the interface notification message of the small gift type, dequeuing operation is preferentially carried out, and the interface notification message at the head of the queue is preferentially displayed in a graphical user interface of a live broadcast room; if the priorities of the message queues are consistent, dequeue operation is executed in parallel, and the queue head interfaces of the message queues inform that messages are displayed in a graphical user interface of a live broadcast room in parallel; the number of queues in the message queue can be flexibly designed by those skilled in the art, as long as the definition of the relevant rule in the application is met.

The various methods implemented in this step form a queue management module that can be used to process a large number of interface notification messages in combination with the shunting enqueue operation described above, and this queue management module not only sets the access rules of each message queue, but also standardizes the relevant rules for cross-message queue access, and implements systematic organization and management on multiple message queues, and through the enqueue and dequeue operations of each message queue, it manages interface notification messages of various types in order, and prevents the numerous interface notification messages from being accumulated in the memory and being unable to be processed, which results in crash of sending terminal devices running live broadcast application programs.

Step S14, performing display policy control on each dequeued interface notification message, and outputting each interface notification message to its corresponding view layer for display under the control of the display policy control:

the display strategy control can be a corresponding display strategy defined by the interface notification message, and the display strategy is suitable for implementing effective display control on the interface notification message to which the localized processing belongs, so that the direct broadcasting room application program can objectively and uniformly regulate the display of various interface notification messages while controlling the display of the interface notification message according to the display strategy. When one or more message queues execute dequeue operation on the interface notification messages stored in the message queues, the interface notification messages are generally processed locally, and when local processing is implemented, the interface notification messages can be instantiated and converted into instance objects by calling preset related interfaces, so that the interface notification messages are controlled to be displayed on the designated view layers by accessing the instance objects.

Referring to fig. 3, in an embodiment, when performing the display policy control on each interface notification message stored in a message queue for performing dequeue, the process of locally processing the interface notification message may include the following specific control steps:

step S141, instantiating a preset interface class for encapsulating the interface notification message, and acquiring an instance object:

in order to realize the local processing of the interface notification message and the conversion of the interface notification message to the instance object, so as to be subjected to objectification operation by a computer subsequently and finally realize the output of the interface, a developer adapts to the specification of a uniform protocol on a programming interface, correspondingly provides a template for the interface object, the template provides a definition specification of an interface class, an instance object can be obtained by instantiating the interface class, the instance object inherits each predefined functional interface in the interface class, and after various types of data related to the interface notification message are converted into the attribute of the instance object, the instance object can exert the function of bearing the local operation expression of the interface notification message. The visualization part contained in the interface notification message is converted into the interface object contained in the instance object, the related display strategy can be encapsulated into the instance object, and the objects or information encapsulated by the instance object can be called through the corresponding function interface of the instance object.

Step S142, obtaining the interface object encapsulation data from the interface notification message as the assignment of the corresponding attribute item of the instance object, so as to construct the interface object to be displayed in the view layer:

interface notification messages stored in each message queue for implementing localized processing of dequeue operations include information to be visually displayed on a graphical user interface, the information defining a visual object to be displayed on the graphical user interface, and thus, the visual object can be converted into an interface object by transferring the visual object to an instance object. Specifically, the definition information related to the interface object may be acquired from the interface notification message, and the definition information is assigned to the corresponding attribute item of the instance object, so as to complete data encapsulation of the interface object in the instance object, and construct the interface object to be displayed in the view layer specified by the interface notification message.

Through the localization processing, the interface notification messages are converted into the interface objects, the interface notification messages of various types can be standardized, no matter which project team develops the interface notification messages, no matter which type of expression forms the interface notification messages are in charge of, and even no matter whether the interface notification messages conform to the specification of the same format, after the interface notification messages are converted into the interface objects, the standardized specification of the visual information of the interface notification messages on local equipment is completed, and the visual information can be called in a standardized and unified mode.

Step S143, obtaining the display policy control identifier corresponding to the interface object from the interface notification message, and assigning values to the corresponding attribute items of the instance object:

as described above, the display policy control flag is predefined in the interface notification message as information related to the display policy description, and thus can be acquired from the interface notification message. The display policy control identifier is used to assign values to the respective attribute items of the instance object to control the display policy of the interface notification message in the view layer to which it is assigned.

In one embodiment, the display policy control identifier includes a visibility monitoring identifier, configured to set whether an interface notification message is visible in a specific environment, so as to control the display execution module to control, according to the visibility monitoring identifier, whether a corresponding interface object is visible or invisible in the specific environment; the specific environment generally refers to setting a trigger condition of a visibility monitoring identifier according to an actual application scene of a live broadcast room, and judging whether to trigger to change the interface object to be visible or invisible displayed in the graphical user interface, for example, the specific environment can judge whether to change a touch event of a live broadcast room user to be the trigger condition, and when the touch event is received, the related interface object enables the change of the interface object in the graphical user interface of the live broadcast room to be visible or invisible displayed according to the visibility monitoring identifier. More vividly, sometimes an interface notification message needs to be visible after the user exits a live broadcast room, in this case, the interface notification message can be realized by marking the visibility monitoring identification as a visible attribute, and the visible attribute is transmitted to the instance object here so as to be called and acted on the corresponding interface object later.

In another embodiment, which may be independent or combined with the previous embodiment, the display processing control identifier includes a display duration identifier, configured to set a display duration of the interface notification message on the graphical user interface, so as to control the display execution module to control, according to the display duration identifier, that the display of the corresponding interface object is ended when the corresponding interface object first appears in the graphical user interface until the corresponding duration arrives; the display duration can be set by a development team when developing the interface notification message so as to control the display time of the corresponding interface object in the corresponding view layer.

Step S144, transmitting the instance object to a display execution module for outputting the interface object to a view layer display, and driving the display execution module to be controlled to output the interface notification message to a corresponding view layer display:

when the dequeued interface notification message is converted into the interface object and the data encapsulation of the corresponding instance object is completed, the localized processing is completed, and then the instance object can be transmitted to the display execution module, so that the display execution module is driven to output the interface notification message to the corresponding view layer through accessing and calling the instance object, and the corresponding interface object is displayed in the graphical user interface of the live broadcast room.

Specifically, the display execution module may obtain the interface object defined by the encapsulation by calling the first functional interface of the instance object, and output the interface object to the corresponding view layer for display; the encapsulated display policy control identifier can be obtained by calling the second functional interface of the instance object, and the display activity of the interface object in the view layer is controlled according to the display policy control identifier. Similarly, if the interface notification message defines other control items, all the control items can be converted into corresponding attribute items of the instance object, and the display execution module can call the corresponding attribute items through corresponding function interfaces of the instance object, so as to control other display activities of the interface object in the view layer.

In an embodiment, in order to prevent that multiple interface notification messages specify the same view layer at the same time, which causes multiple interface notification messages to be displayed in the same view layer in a messy manner, and affects the viewing experience of a user in a live broadcast room, the display execution module may execute the following steps before outputting the interface notification messages to the corresponding view layers for display:

detecting whether an interface notification message which is currently displayed exists in a view layer designated by the interface notification message which needs to be displayed, and executing the interface notification message which needs to be displayed when the view layer has no interface notification message which is currently displayed.

For the setting of this step, it may be understood that, before outputting the interface notification message to the corresponding view layer for display, the display execution module needs to detect whether the view layer specified by the interface notification message is occupied, and when the view layer is occupied, it needs to wait for the view layer to complete the display of the interface notification message being displayed, and then outputs the next interface notification message to the view layer for display in the graphical user interface of the live broadcast room. As shown in fig. 4, the application outputs the interface object to the view layer specified by the interface object, so that the interface message to which the interface object belongs is displayed on the live broadcast graphical user interface.

In addition to the above embodiments, in order to enrich the implementation manner of the present application, other various embodiments of the present application are further disclosed as follows:

in an embodiment, in order to optimize the memory of the terminal device running the application process of the live broadcast room, referring to fig. 5, the method further includes the following subsequent steps:

step S15, in response to the exit event of the live broadcast application program process, recycling the memory occupied by executing the method:

the method is attached to a live broadcast room application program, so that the quitting event generally refers to an event generated by triggering audience users quit a live broadcast room in the live broadcast room; after the application responds to the exit event, the memory occupied by executing the method is triggered to be recovered, namely, the message queue and the tree structure constructed by the view layer container and the root container and other data information generated by executing the method are destroyed, so that the memory occupied by executing the method is recovered, and the situation that terminal equipment is blocked or even crashed is prevented.

In another embodiment, the same purpose as that of the above embodiment is also to optimize a memory of a terminal device running an application process of the live broadcast room, with reference to fig. 6, the method further includes the following steps:

step S15', monitoring the idle duration of each message queue/view layer, and when the idle duration of a message queue/view layer exceeds a predetermined value, recovering the memory of the message queue/view layer:

the method can construct a monitoring module for monitoring idle duration of each message queue and each view layer, and preset one preset value, when the monitoring module monitors that the idle duration of a certain message queue or view layer exceeds the preset value, the message queue or the view layer is destroyed so as to recycle the memory occupied by the message queue or the view layer for the terminal equipment executing the method; regarding the predetermined value, those skilled in the art can flexibly set the predetermined value according to the actual application scene of the live broadcast room.

In another embodiment, a creating module for automatically creating a message queue and a view layer is constructed, and in the step of shunting the view layer specified by the interface notification message to a message queue correspondingly arranged for the view layer to perform enqueue operation according to the view layer specified by the interface notification message, when the view layer and/or the message queue specified by the interface notification message does not exist, a corresponding view layer and/or a message queue is created for the view layer and/or the message queue.

It can be understood that, in the process of determining, according to the view layer index of the type information of the interface notification message, the view layer designated for output display of each type of interface notification message and the message queue to which the view layer or the message queue designated by a certain interface notification message is assigned, when the view layer or the message queue does not exist, the creation module automatically creates the corresponding view layer or the message queue for the interface notification message according to the view layer index or the type information of the view layer included in the type information of the interface notification message, so as to prevent the method proposed by the present application from being executed normally, and from causing that the interface notification message cannot be managed orderly and displayed in the graphical user interface in the live broadcast room.

It can be understood that, in the present embodiment, automatic creation of a message queue and/or a view layer is implemented, and in the previous example, a means for automatically recovering a message queue and/or a view layer is also disclosed, so that, by combining the two means with another embodiment of implementation, the technical solution of the present application has a memory maintenance capability of dynamically creating and recovering the message queue and/or the view layer, and background management of a large amount of interface notification messages is better implemented.

In another embodiment, after the live broadcast application program process is started, in response to a user instruction generated by a user through touch control on a graphical user interface of the live broadcast application program, a corresponding interface notification message is generated, and both the interface notification message and an interface notification message received from the server are used for shunting and added to a corresponding message queue.

It can be understood that, during the execution of the live broadcast application program process constructed by the application program process, whether the interface notification message sent from the server or the interface notification message generated from the local terminal device can be orderly managed by the application program and displayed in the graphical user interface, that is, as long as the live broadcast application program process is started, the live broadcast application program process can orderly process and display various received interface notification messages according to relevant rules.

Further, an interface notification message scheduling apparatus of the present application may be constructed by functionalizing the steps in the methods disclosed in the foregoing embodiments, and according to this idea, please refer to fig. 7, wherein in an exemplary embodiment, the apparatus includes:

a message receiving module 11 configured to start receiving an interface notification message with the start of the live broadcast application program process;

a message enqueuing module 12, configured to distribute, according to a view layer specified by the interface notification message, a view layer to a message queue correspondingly set for the view layer to perform enqueuing operation, where each view layer is represented by a view container implementation interface associated with a root container;

a message dequeue module 13, configured for each message queue independently, and configured to perform dequeue operation of the corresponding message queue according to the queue access rule;

and the message display module 14 is configured to perform display policy control on each dequeued interface notification message, and output each interface notification message to its corresponding view layer under the control of the message display module.

Further, to facilitate the implementation of the present application, the present application provides an electronic device, including a central processing unit and a memory, where the central processing unit is configured to invoke and run a computer program stored in the memory to perform the steps of the interface notification message scheduling method in the foregoing embodiments.

It can be seen that the memory is suitable for adopting a nonvolatile storage medium, the aforementioned method is implemented as a computer program and installed in an electronic device such as a mobile phone or a computer, the related program code and data are stored in the nonvolatile storage medium of the electronic device, and further the program is executed by a central processing unit of the electronic device and is called from the nonvolatile storage medium to a memory for execution, so as to achieve the desired purpose of the present application. Therefore, it is understood that in an embodiment of the present application, a non-volatile storage medium may be further provided, in which a computer program implemented according to various embodiments of the interface notification message scheduling method is stored, and when the computer program is called by a computer, the computer program executes the steps included in the method.

To sum up, the scheduling module for processing the notification messages of the interfaces of various types with strong universality and expansibility is constructed, all types of the notification messages of the interfaces are orderly managed through the message queue, meanwhile, the tree structure is constructed by combining the view layers, the view layer containers and the root containers, the centralized and ordered scheduling of the view layers of different levels in the depth direction of the graphical user interface is realized, the notification messages of the interfaces of various types are locally processed, the development of different development teams unifying the same application program project on the interface notification messages defined by the different development teams is facilitated, and the program development efficiency is improved.

As will be appreciated by one skilled in the art, the present application includes apparatus that are directed to performing one or more of the operations, methods described herein. These devices may be specially designed and manufactured for the required purposes, or they may comprise known devices in general-purpose computers. These devices have computer programs stored in their memories that are selectively activated or reconfigured. Such a computer program may be stored in a device (e.g., computer) readable medium, including, but not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magnetic-optical disks, ROMs (Read-Only memories), RAMs (Random Access memories), EPROMs (Erasable Programmable Read-Only memories), EEPROMs (Electrically Erasable Programmable Read-Only memories), flash memories, magnetic cards, or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus. That is, a readable medium includes any medium that stores or transmits information in a form readable by a device (e.g., a computer).

It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions may be implemented by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the aspects specified in the block or blocks of the block diagrams and/or flowchart illustrations disclosed herein.

Those of skill in the art will appreciate that the various operations, methods, steps in the processes, acts, or solutions discussed in this application can be interchanged, modified, combined, or eliminated. Further, other steps, measures, or schemes in various operations, methods, or flows that have been discussed in this application can be alternated, altered, rearranged, broken down, combined, or deleted. Further, steps, measures, schemes in the prior art having various operations, methods, procedures disclosed in the present application may also be alternated, modified, rearranged, decomposed, combined, or deleted.

The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims

1. A method for scheduling interface notification messages is characterized by comprising the following steps:

2. The method of claim 1, further comprising the post-step of:

3. The method according to claim 1, wherein when performing display policy control on each dequeued interface notification message, adapting to each dequeued interface notification message comprises the following specific control steps:

4. The method according to claim 3, wherein the display policy control identifier comprises a visibility monitoring identifier for setting whether the interface notification message is visible in a specific environment, so as to control the display execution module to control the corresponding interface object to be displayed in the specific environment in a visible or invisible manner according to the visibility monitoring identifier.

5. The method according to claim 3, wherein the display policy control flag includes a display duration flag, which is used to set a display duration of the interface object of the interface notification message, so as to control the display execution module to control the display of the corresponding interface object to the corresponding duration according to the display duration flag, and then to end the display.

6. The method according to claim 3, wherein the display execution module executes the following steps before outputting the interface notification message to its corresponding viewing layer display: detecting whether an interface notification message which is currently displayed exists in a view layer designated by the interface notification message which needs to be displayed, and executing the interface notification message which needs to be displayed when the view layer has no interface notification message which is currently displayed.

7. The method of claim 1, comprising the steps of:

8. The method according to claim 1, wherein the view layers specified by the interface notification message are shunted to a step of performing an enqueue operation for a message queue correspondingly set for the view layers according to the view layers specified by the interface notification message, and when the view layers and/or the message queue specified by the interface notification message do not exist, a corresponding view layer and/or a message queue are created for the view layers and/or the message queue.

9. The method according to claim 1, wherein after the live broadcast application program process is started, in response to a user instruction generated by a user through touch control on a graphical user interface of the live broadcast application program, generating the corresponding interface notification message, wherein the interface notification message and the interface notification message received from the server are used for shunting and added to the corresponding message queue.

10. An interface notification message scheduling apparatus, comprising:

11. An electronic device comprising a central processor and a memory, wherein the central processor is configured to invoke execution of a computer program stored in the memory to perform the steps of the interface notification message scheduling method according to any one of claims 1 to 9.

12. A non-volatile storage medium, characterized in that it stores a computer program implemented by the interface notification message scheduling method according to any one of claims 1 to 9, which when called by a computer, performs the steps included in the method.