CN115033737A - Live broadcast room architecture system, operation method thereof, electronic equipment and medium - Google Patents
Live broadcast room architecture system, operation method thereof, electronic equipment and medium Download PDFInfo
- Publication number
- CN115033737A CN115033737A CN202210775249.4A CN202210775249A CN115033737A CN 115033737 A CN115033737 A CN 115033737A CN 202210775249 A CN202210775249 A CN 202210775249A CN 115033737 A CN115033737 A CN 115033737A
- Authority
- CN
- China
- Prior art keywords
- layer
- data
- viewmodel
- view
- layers
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/70—Information retrieval; Database structures therefor; File system structures therefor of video data
- G06F16/74—Browsing; Visualisation therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Multimedia (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a live broadcast room architecture system, an operation method thereof, electronic equipment and a medium, wherein the live broadcast room architecture system comprises a presentation layer, a field layer and a data layer; the presentation layer comprises a View layer and a ViewModel layer; the View layer transmits a parameter to the ViewModel layer to wait for callback data; after receiving the parameters transmitted by the View layer, the View model layer acquires data through the field layer and converts the data into data required by the View layer for refreshing, and then the converted data is called back; the domain layer calls a method of the data layer and waits for the data layer to call back data; the data layer initiates a service request, acquires data through server interface routing, preprocesses the acquired data according to service logic, and returns the data to the field layer; the invention realizes the coupling between the decoupling service and the service and ensures that the codes of the live broadcasting room are convenient to maintain and expand.
Description
Technical Field
The present invention relates to the field of code architecture, and in particular, to a live broadcast room architecture system, an operating method thereof, an electronic device, and a medium.
Background
The current existing live broadcast room architecture system uses the MVC architecture mode, and uses Fragment to decouple the service logic and the player logic from Activity. When the mode faces complex live broadcast room logic, Fragment is bloated, and services are not only dependent on Fragment but also transmitted to an Activity layer, so that the logic layer is coupled layer by layer, the maintenance and reading are difficult, and a new scheme is needed to optimize the live broadcast room.
Disclosure of Invention
The technical problem to be solved by the invention is to decouple the service from the coupling between services from the perspective of engineering architecture and ensure that the codes of the live broadcast room are convenient to maintain and expand.
The invention solves the technical problems through the following technical scheme:
in a first aspect, a live broadcast room architecture system is provided, which includes a presentation layer, a domain layer, and a data layer;
the presentation layer is used for page rendering and comprises a View (displayed user interface) layer and a ViewModel (data object related to service logic corresponding to the user interface) layer; the View layer is used for displaying a page, transmitting parameters to the ViewModel layer to wait for callback data when the page needs to be refreshed, and refreshing the page according to the callback data;
the ViewModel layer is used for acquiring data through the field layer after receiving the parameters transmitted by the View layer, converting the acquired data into data required by the View layer for refreshing, and calling back the converted data to the View layer;
the field layer is used for calling the method of the data layer and waiting for the callback data of the data layer;
the data layer is used for initiating a service request, acquiring data through a server interface route, preprocessing the acquired data according to service logic and then returning the preprocessed data to the field layer.
Preferably, the View layer registers LiveData (a lifecycle aware component) events, waiting for the ViewModel layer to call back data; the ViewModel layer transmits the converted data to the LiveData, and the LiveData distributes data to refresh the View layer;
and/or the field layer is an Interface class and is inherited with at least one data layer; after the domain layer is inherited by the plurality of data layers, one of the data layers is selected to be used according to the non-service scene;
and/or the preprocessing comprises the step of storing the data obtained from the server in the data layer after analyzing the data;
and/or the data layers are independent from each other, when a plurality of data layer data are needed, each data layer calls back the data to the ViewModel layer, and the ViewModel layer processes the data in a unified manner.
Preferably, one of the View layers holds one or more of the ViewModel layers, and the ViewModel layers are independent of each other.
Preferably, the communication mode between the ViewModel layers is that one ViewModel layer notifies the View layer through LiveData, and then notifies the other ViewModel layer.
In a second aspect, an operation method of a live broadcast room architecture system is provided, where the live broadcast room architecture system includes a presentation layer, a domain layer, and a data layer; the presentation layer comprises a View layer and a ViewModel layer; the operation method comprises the following steps:
the View layer transmits parameters to the ViewModel layer;
the ViewModel layer acquires data through the field layer after receiving the parameters transmitted by the View layer;
the field layer is used for calling the method of the data layer and waiting for the callback data of the data layer;
the data layer initiates a service request, acquires data through a server interface route, preprocesses the acquired data according to service logic and returns the preprocessed data to the field layer;
the domain layer returns data to the ViewModel layer;
the View model layer converts the acquired data into data required by the View layer to refresh, and then calls back the converted data to the View layer;
and the View layer refreshes the page according to the callback data.
Preferably, the step of passing parameters from the View layer to the ViewModel layer further comprises:
registering a LiveData event by the View layer, and waiting for callback data of the ViewModel layer;
the ViewModel layer transmits the converted data to the LiveData, and the LiveData distributes data to refresh the View layer;
and/or the field layer is an Interface class and is inherited with at least one data layer; after the domain layer is inherited by the plurality of data layers, one of the data layers is selected to be used according to the non-service scene;
and/or the preprocessing comprises the step of storing the data obtained from the server in the data layer after analyzing the data;
and/or the data layers are independent from each other, when a plurality of data layer data are needed, each data layer calls back the data to the ViewModel layer, and the ViewModel layer processes the data in a unified manner.
Preferably, one of the View layers holds one or more of the ViewModel layers, and the ViewModel layers are independent of each other.
Preferably, the communication mode between the ViewModel layers is that one ViewModel layer notifies the View layer via LiveData and notifies the other ViewModel layer.
In a third aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the electronic device implements the operation method of the live broadcast architecture system as described above.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which when executed by a processor, implements an operating method of the direct broadcast room architecture system as described above.
The positive progress effects of the invention are as follows: codes among services are decoupled, each layer focuses on the service logic of the layer, maintenance and reading are convenient, developers can write codes independent of the UI, responsibility among the layers is single and definite, and data sources are convenient to trace.
Drawings
Fig. 1 is a schematic structural diagram of a live broadcast room architecture system according to embodiment 1 of the present invention.
Fig. 2 is a flowchart illustrating an operation method of a live broadcast room architecture system according to embodiment 2 of the present invention.
Fig. 3 is a schematic structural diagram of an electronic device according to embodiment 3 of the present invention.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the scope of the invention.
Example 1
The present embodiment provides a live broadcast room architecture system, as shown in fig. 1, which includes a presentation layer 1, a domain layer 2, and a data layer 3. In specific implementation, the live broadcast room architecture system can have a plurality of presentation layers, a domain layer and a data layer, and the presentation layers can have a plurality of View layers and View model layers.
The first layer, the presentation layer 1 is used for page rendering, and is used as a user operation layer for carrying out user operation, and comprises a View layer 11 and a ViewModel layer 12;
the View layer 11 is used for page display, when a page needs to be refreshed, parameters are transmitted to the ViewModel layer 12 to wait for callback data, and the page is refreshed according to the callback data;
the ViewModel layer 12 is used for acquiring data through the domain layer 2 after receiving the parameters transmitted by the View layer, converting the acquired data into data required by the View layer 11 to refresh, and calling back the converted data to the View layer 11;
it is worth noting that the function distribution is different from the prior art through the above design, specifically as follows: the View layer 11 is only used for displaying pages and does not process service data; the ViewModel layer 12 does not perform the operation of requesting data, but instead, actually delivers this operation to the data layer 3.
In specific implementation, the View layer also registers a LiveData event for waiting for the call-back data of the ViewModel layer; the ViewModel layer transmits the converted data to the LiveData, and then the LiveData distributes the data to refresh the View layer; one View layer holds one or more ViewModel layers, the ViewModel layers are independent, and the communication mode between the ViewModel layers is that one ViewModel layer informs the View layer through LiveData and then informs the other ViewModel layer.
And the second layer, the domain layer 2, is used for calling the method of the data layer 3 and waiting for the data layer 3 to call back the data.
The principle of the domain layer is that the domain layer is used as an interface layer and mainly responsible for decoupling the data layer and the presentation layer, coordinating the work between the data layer and the presentation layer, defining the responsibility of the data layer and the domain layer to complete a series of specific and defined services, and preventing the presentation layer from randomly changing data to cause data confusion, thereby causing a series of problems such as deletion errors and breakdown.
And the third layer, the data layer 3 is used for initiating a service request, acquiring data through server interface routing, and preprocessing the acquired data according to service logic, wherein the preprocessing comprises analyzing the data acquired from the server, storing the analyzed data in the data layer 3, and returning the data to the field layer 2.
In specific implementation, the data layers are independent from each other, when a plurality of data layers are needed, each data layer calls back data to the ViewModel layer, the ViewModel layer processes the data uniformly, and the field layer is an Interface type and inherits at least one data layer; and after the domain layer is inherited by the plurality of data layers, one of the data layers is selected to be used according to the non-service scene.
According to the embodiment, the functions of each layer are clearer according to the three-layer architecture and the design of the functions and the flow of the three-layer architecture, the display of the View layer can be changed only by changing data, and the multiplexing and modifying effects of the View layer are facilitated; in addition, the service logic is written in the ViewModel layer, so that the service logic is ensured to be multiplexed as much as possible, the ViewModel layer can be used as the service logic without concerning whether the data is acquired from a service or a memory, and the responsibility of the ViewModel layer is more concerned about the service logic; the data layer can be multiplexed, and when the data needs to be modified, only the data layer needs to be concerned, and the service logic is not modified; and the method is convenient to expand, and various combinations of the ViewModel and the data layer can have different service scenes. Finally, low coupling between services is realized, the services are distinguished from the services through different ViewModel and field layers by service logic on the own ViewModel layer, and the mutual calling achievement between the services can be realized by other services only through LiveData.
Example 2
The embodiment provides an operation method of a live broadcast room architecture system, wherein the live broadcast room architecture system comprises a presentation layer, a field layer and a data layer; the presentation layer includes a View layer and a ViewModel layer.
In specific implementation, the live broadcast room architecture system can be provided with a plurality of presentation layers, field layers and data layers, and the presentation layers can be provided with a plurality of View layers and ViewModel layers; one View layer holds one or more ViewModel layers, the ViewModel layers are independent, and the communication mode between the ViewModel layers is that one ViewModel layer informs the View layer through LiveData and then informs the other ViewModel layer. As shown in fig. 2, the operation method specifically includes the following steps:
in specific implementation, a user enters a live broadcast room to perform user operation, and a View layer of the live broadcast room needs to be refreshed; for example, the user operates to focus on, at this time, the focus control of the View layer starts to be loaded, and the focus control needs to be refreshed.
At this time, the View layer control receives the loading information and registers and binds the corresponding LiveData, and transmits a parameter to the ViewModel layer to wait for refreshing callback data required by the concerned control.
And 102, after receiving the parameters transmitted by the View layer, the View model layer acquires data through the field layer.
In specific implementation, the ViewModel layer informs the domain layer of one or more data layers of the adaptive interfaces to which the data needs to be accessed; for example, the data layers required after receiving the focus trigger instruction parameter include a data layer containing anchor id data, a data layer containing anchor live room play status data, and the like. The data layers are independent from each other, when a plurality of data layer data are needed, each data layer calls back data to the ViewModel layer, and the ViewModel layer processes the data in a unified mode.
And 103, calling the method of the data layer by the field layer, and waiting for the callback data of the data layer.
And 104, initiating a service request by the data layer, acquiring data through a server interface route, preprocessing the acquired data according to service logic, and returning the preprocessed data to the field layer.
For example, the data layer initiates a service request for paying attention to the required data, and the data is acquired through the network attention interface. And preprocessing the data according to the service logic after acquiring the data required by the point attention, wherein the preprocessing operation comprises storing the attention state, adding the anchor information to the data returned by the service, and returning the preprocessed data to the field layer.
And 106, converting the acquired data into data required by the View layer refreshing by the View model layer, and calling back the converted data to the View layer.
For example, the ViewModel layer processes the data into the data required for the focus button according to the service scenario. In specific implementation, the ViewModel layer refreshes the View layer by transferring the converted data to the LiveData and the LiveData distributes the data.
And step 107, the View layer refreshes the page according to the callback data.
For example, the attention control of the View layer refreshes views of attention amount, attention flag, and the like through data distributed by LiveData.
According to the embodiment, the functions of each layer are clearer according to the three-layer architecture and the operation mode thereof, the display of the View layer can be changed only by changing data, and the multiplexing and modifying effects of the View layer are facilitated; in addition, the service logic is written in the ViewModel layer, so that the service logic can be reused as much as possible, the ViewModel layer can be used as the service logic without concerning whether the data is acquired from a service or a memory, and the responsibility of the ViewModel layer is more concerned with the service logic; the data layer can be multiplexed, and when data needs to be modified, only the data layer needs to be concerned without modifying the service logic; and the method is convenient to expand, and various combinations of the ViewModel and the data layer can have different service scenes. Finally, low coupling between services is realized, the services are distinguished from the services through different ViewModel and field layers by service logic on the own ViewModel layer, and the mutual calling achievement between the services can be realized by other services only through LiveData.
Example 3
Fig. 3 is a schematic structural diagram of an electronic device provided in this embodiment, where the electronic device includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and when the processor executes the computer program, the method for running the live broadcast room architecture system in embodiment 2 is implemented. The electronic device 80 shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention. As shown in FIG. 3, the electronic device 80 may take the form of a general purpose computing device, which may be a server device, for example. The components of the electronic device 80 may include, but are not limited to: the at least one processor 81, the at least one memory 82, and a bus 83 connecting the various system components including the memory 82 and the processor 81.
The bus 83 includes a data bus, an address bus, and a control bus.
The memory 82 may include volatile memory, such as Random Access Memory (RAM)821 and/or cache memory 822, and may further include Read Only Memory (ROM) 823.
The processor 81 executes various functional applications and data processing, such as the operation method of the live broadcast architecture system in the above-described embodiment 2, by executing the computer program stored in the memory 82.
The electronic device 80 may also communicate with one or more external devices 84. Such communication may be through input/output (I/O) interfaces 85. Also, the model-generating electronic device 80 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 86. As shown in fig. 3, the network adapter 86 communicates with the other modules of the electronic device 80 via the bus 83. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 80, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.
It should be noted that although in the above detailed description several units/modules or sub-units/modules of the electronic device are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module according to embodiments of the invention. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Example 4
The present embodiment provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method for operating the live broadcast room architecture system in embodiment 2 above is implemented.
More specific examples, among others, that the readable storage medium may employ may include, but are not limited to: a portable disk, a hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible implementation manner, the present invention can also be implemented in a form of a program product, which includes program codes, and when the program product runs on a terminal device, the program codes are used for causing the terminal device to execute steps of a running method for implementing the live broadcast room architecture system in embodiment 2.
Where program code for carrying out the invention is written in any combination of one or more programming languages, the program code may execute entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device and partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and that the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention, and these changes and modifications are within the scope of the invention.
Claims (10)
1. A live broadcast room architecture system is characterized by comprising a presentation layer, a field layer and a data layer;
the presentation layer is used for page rendering and comprises a View layer and a ViewModel layer; the View layer is used for displaying a page, transmitting parameters to the ViewModel layer to wait for callback data when the page needs to be refreshed, and refreshing the page according to the callback data;
the View model layer is used for acquiring data through the field layer after receiving the parameters transmitted by the View layer, converting the acquired data into data required by the View layer to refresh, and calling back the converted data to the View layer;
the field layer is used for calling the method of the data layer and waiting for the callback data of the data layer;
the data layer is used for initiating a service request, acquiring data through a server interface route, preprocessing the acquired data according to service logic and then returning the preprocessed data to the field layer.
2. The direct cast room architecture system of claim 1 wherein the View layer registers LiveData events, waiting for the ViewModel layer callback data; the ViewModel layer transmits the converted data to the LiveData, and the LiveData distributes data to refresh the View layer;
and/or the field layer is an Interface class and is inherited with at least one data layer; after the domain layer is inherited by the plurality of data layers, one of the data layers is selected to be used according to the non-service scene;
and/or the preprocessing comprises the step of storing the data obtained from the server in the data layer after analyzing the data;
and/or the data layers are independent from each other, when a plurality of data layer data are needed, each data layer calls back the data to the ViewModel layer, and the ViewModel layer processes the data in a unified manner.
3. The live room architecture system of claim 1 wherein one of the View layers holds one or more of the View model layers, the View model layers being independent of each other.
4. The live room architecture system of claim 3 wherein the communication between the ViewModel layers is from one ViewModel layer to the View layer over LiveData and to another ViewModel layer.
5. An operation method of a live broadcast room architecture system is characterized in that the live broadcast room architecture system comprises a presentation layer, a field layer and a data layer; the presentation layer comprises a View layer and a ViewModel layer; the operation method comprises the following steps:
the View layer transmits parameters to the ViewModel layer;
the ViewModel layer receives the parameters transmitted by the View layer and then acquires data through the field layer;
the field layer is used for calling the method of the data layer and waiting for the callback data of the data layer;
the data layer initiates a service request, acquires data through a server interface route, preprocesses the acquired data according to service logic and returns the preprocessed data to the field layer;
the domain layer returns data to the ViewModel layer;
the ViewModel layer converts the acquired data into data required by the View layer to refresh, and then calls back the converted data to the View layer;
and the View layer refreshes the page according to the callback data.
6. The method of claim 5, wherein the View layer passing parameters to the ViewModel layer further comprises, after the step of passing parameters to the View layer:
registering a LiveData event by the View layer, and waiting for callback data of the ViewModel layer;
the ViewModel layer transmits the converted data to the LiveData, and the LiveData distributes data to refresh the View layer;
and/or the field layer is an Interface class and is inherited with at least one data layer; after the domain layer is inherited by the plurality of data layers, one of the data layers is selected to be used according to the non-service scene;
and/or the preprocessing comprises the step of storing the data obtained from the server in the data layer after analyzing the data;
and/or the data layers are independent from each other, when a plurality of data layer data are needed, each data layer calls back the data to the ViewModel layer, and the ViewModel layer processes the data in a unified manner.
7. The method of claim 5, wherein one of the View layers holds one or more of the ViewModel layers, and wherein the ViewModel layers are independent of each other.
8. The method of claim 7, wherein the communication between the ViewModel layers is from one ViewModel layer to another ViewModel layer via LiveData.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements a method of operating the live room architecture system of any one of claims 5-8 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of operating a live-air architecture system according to any one of claims 5-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210775249.4A CN115033737A (en) | 2022-07-01 | 2022-07-01 | Live broadcast room architecture system, operation method thereof, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210775249.4A CN115033737A (en) | 2022-07-01 | 2022-07-01 | Live broadcast room architecture system, operation method thereof, electronic equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115033737A true CN115033737A (en) | 2022-09-09 |
Family
ID=83128866
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210775249.4A Pending CN115033737A (en) | 2022-07-01 | 2022-07-01 | Live broadcast room architecture system, operation method thereof, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115033737A (en) |
-
2022
- 2022-07-01 CN CN202210775249.4A patent/CN115033737A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032706B (en) | Intelligent contract execution method, device, equipment and storage medium | |
| US11392461B2 (en) | Method and apparatus for processing information | |
| US20200057658A1 (en) | Method and system for loading resources | |
| US20110047415A1 (en) | Debugging of business flows deployed in production servers | |
| CN109445841B (en) | Interface document management method, device, server and storage medium | |
| US8832690B1 (en) | Multi-threaded virtual machine processing on a web page | |
| CN102541661B (en) | Realize the method and apparatus of wait on address synchronization interface | |
| CN110427258B (en) | Resource scheduling control method and device based on cloud platform | |
| CN111026945B (en) | Multi-platform crawler scheduling method, device and storage medium | |
| CN113296740A (en) | Service object processing method, device, equipment and machine readable medium | |
| CN112486807A (en) | Pressure testing method and device, electronic equipment and readable storage medium | |
| CN111800511A (en) | Processing method, system, equipment and readable storage medium for synchronous login state | |
| CN116089301A (en) | Component sharing method, device, electronic equipment and storage medium | |
| CN110908644A (en) | Configuration method and device of state node, computer equipment and storage medium | |
| CN116089048A (en) | Service processing method and device, storage medium and electronic equipment | |
| CN115033737A (en) | Live broadcast room architecture system, operation method thereof, electronic equipment and medium | |
| CN112506781B (en) | Test monitoring method, device, electronic equipment, storage medium and program product | |
| CN112988604B (en) | Object testing method, testing system, electronic device and readable storage medium | |
| CN114490266A (en) | Data acquisition method, device, equipment and storage medium | |
| CN111262727B (en) | Service capacity expansion method, device, equipment and storage medium | |
| CN114035864A (en) | Interface processing method, interface processing device, electronic device, and storage medium | |
| CN114968216A (en) | Application program development project generation method and device | |
| CN112597408A (en) | System fusion method, device, equipment and storage medium | |
| CN113608803A (en) | Method and equipment for realizing functional operation in multi-operation environment | |
| CN112799954B (en) | Method, apparatus and computer readable medium for quickly constructing test environment |
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 |