CN108419089B - Component data processing method, device, equipment and storage medium - Google Patents
Component data processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN108419089B CN108419089B CN201810129017.5A CN201810129017A CN108419089B CN 108419089 B CN108419089 B CN 108419089B CN 201810129017 A CN201810129017 A CN 201810129017A CN 108419089 B CN108419089 B CN 108419089B
- Authority
- CN
- China
- Prior art keywords
- component
- client
- interface
- data
- component data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/21—Server components or server architectures
- H04N21/218—Source of audio or video content, e.g. local disk arrays
- H04N21/2187—Live feed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25808—Management of client data
- H04N21/25858—Management of client data involving client software characteristics, e.g. OS identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/431—Generation of visual interfaces for content selection or interaction; Content or additional data rendering
- H04N21/4312—Generation of visual interfaces for content selection or interaction; Content or additional data rendering involving specific graphical features, e.g. screen layout, special fonts or colors, blinking icons, highlights or animations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/4508—Management of client data or end-user data
- H04N21/4516—Management of client data or end-user data involving client characteristics, e.g. Set-Top-Box type, software version or amount of memory available
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Graphics (AREA)
- Information Transfer Between Computers (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses a method, a device, equipment and a storage medium for processing component data, wherein the method comprises the following steps: the client sends a component data request to the management server; after receiving the component data request, the management server determines a target business component needing to be displayed at the client; acquiring component data through an interface corresponding to the target service component through a corresponding relation between a prestored service component and the interface, and sending the component data to a client; and the client receives the component data, and displays the target business component according to the component data if the uniform entrance aiming at the business component is triggered. The method and the device aim to solve the problem that when the business component is updated in the prior art, the client needs to be upgraded or updated.
Description
Technical Field
The application relates to the internet field, especially relates to the internet live broadcast field.
Background
With the rapid development of the live broadcast industry, more and more services are related to the live broadcast. At present, a service component is generally displayed on a live broadcast room page as an entrance, so that a user can use a service corresponding to the service component. At present, business components on the pages of the live broadcast room are more and more, and the updating frequency of the business components on the pages is higher and higher. In the prior art, component data of all service components of a client is generally stored in an electronic device for installing the client, but when the service components on a page need to be updated, a programmer is required to modify a client code, and a user downloads the client again for installation or upgrade. Therefore, in the prior art, more and more service components on the page sharply reduce the available space of the page, and the frequency of updating the client is more frequent due to the service updated with high frequency, so that the user experience is poor.
Disclosure of Invention
In view of the above, the present application provides a method, an apparatus, a device and a storage medium for processing component data to solve the above technical problems.
In order to achieve the purpose, the technical scheme adopted by the application is as follows:
according to a first aspect of embodiments of the present application, a component data processing method is provided, the method including:
the client sends a component data request to the management server;
after receiving the component data request, the management server determines a target business component needing to be displayed at the client;
acquiring component data through an interface corresponding to the target service component through a corresponding relation between a prestored service component and the interface, and sending the component data to a client;
and the client receives the component data, and displays the target business component according to the component data if the uniform entrance aiming at the business component is triggered.
In some examples, the request to obtain component data is triggered when a client page is loaded or a user clicks on a unified portal for a business component.
In some examples, the interface points to a corresponding component server;
the acquiring component data through the interface corresponding to the target service component includes:
and acquiring component data from a component server corresponding to the interface through the interface corresponding to the target service component.
In some examples, the management server obtains an update condition of a service component, and updates a corresponding relationship between the service component and an interface according to the update condition.
In some instances, it may be desirable to,
the request carries a category identification of the client;
the service components comprise at least two component types, and each type of service component corresponds to a corresponding client type identifier.
In some examples, the category identification includes at least any one of: user identity identification, live broadcast room identification and identification of the type of the live broadcast room.
According to a second aspect of the embodiments of the present application, there is provided another component data processing method, including:
after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
In some examples, the request to obtain component data is triggered when a client page is loaded or a user clicks on a unified portal for a business component.
In some examples, an update condition of a service component is obtained, and a correspondence between the service component and an interface is updated according to the update condition.
In some instances, it may be desirable to,
the request carries a category identification of the client;
the service components comprise at least two component types, and each type of service component corresponds to a corresponding client type identifier.
In some examples, the category identification includes at least any one of: user identity identification, live broadcast room identification and identification of the type of the live broadcast room.
According to a third aspect of embodiments of the present application, there is provided an element data processing apparatus, including:
after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
According to a fourth aspect of the embodiments of the present application, there is provided an element data processing system, including:
the client side is used for sending a component data request to the management server side and displaying a target business component according to the component data when a uniform entrance aiming at the business component is triggered;
and the management server is used for determining a target service component which needs to be displayed at the client after receiving the component data request, acquiring component data through an interface corresponding to the target service component through a pre-stored corresponding relation between the service component and the interface, and sending the component data to the client.
In some examples, the system further comprises a component server;
and the component server is used for providing component data to the management server through the interface.
According to a fifth aspect of embodiments of the present application, there is provided an element data processing apparatus including:
a processor; a memory for storing the processor-executable instructions;
wherein the processor is configured to perform the following operations:
after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
According to a sixth aspect of the embodiments of the present application, a machine-readable storage medium is provided, on which computer instructions are stored, and when executed, the computer instructions perform the following processes:
after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
According to the method and the device, the management server is added to manage the corresponding relation between the service components and the interfaces, when a component data request sent by the client is received, the target service components to be displayed by the client are determined, component data are requested from the interfaces corresponding to the target service components according to the corresponding relation between the service components and the interfaces, the problem that the client needs to be updated every time the service components are updated due to the fact that the component data (including the corresponding relation between the service components and the interfaces) are directly prestored by the client in the prior art is solved, the updating frequency of the client is greatly reduced, the flexibility of the client page is improved, the service components are folded under a unified entrance, and occupation of the page space is reduced.
Drawings
FIG. 1 is a schematic diagram of a prior art component data processing system;
FIG. 2 is a schematic diagram of an exemplary component data processing system according to an embodiment of the present application;
FIG. 3 is a partial flow chart of a component data processing method schematically illustrated in an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a target business component according to an embodiment of the present application;
fig. 5 is a schematic diagram of an internet live broadcast scene schematically illustrated in an embodiment of the present application;
FIG. 6 is a schematic diagram of another component data processing system shown schematically in an embodiment of the present application;
fig. 7 is a schematic frame diagram of an electronic device schematically illustrated in an embodiment of the present application;
FIG. 8a is a logic block diagram of an exemplary component data processing system according to an embodiment of the present application;
FIG. 8b is a logical block diagram of another component data processing system shown schematically in an embodiment of the present application;
fig. 9 is a logic block diagram of an assembly data processing device schematically illustrated in an embodiment of the present application.
Detailed Description
The present application will now be described in detail with reference to specific embodiments thereof as illustrated in the accompanying drawings. These embodiments are not intended to limit the present application, and structural, methodological, or functional changes made by those skilled in the art according to these embodiments are included in the scope of the present application.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
The page refers to a visual information carrier for presenting information such as characters and graphics, and can be a webpage or a client page, such as a live broadcast room page corresponding to a live broadcast client. Components, which generally refer to reusable data objects, can also be presented on a page and can perform some function and can provide a data interface to the outside to use the function. In some cases, when a user needs to use a service or a function corresponding to a component, the user may click an icon corresponding to the component, and access data through an external interface (hereinafter referred to as an interface) according to a correspondence between the component and the interface. In generating a page, it is often necessary to render the components in the page. The components are rendered in the page generation process, and in the prior art, a data file of a client is generally stored in an electronic device in which the client is installed. Wherein, the data file may include partial component data of components in the client interface, and the component data may include: icon data of the component, a corresponding relation between the component and an interface for acquiring the data, and the like. The process of rendering components in a page may generally include: the method comprises the steps of obtaining a component in a page, obtaining component data of the component from a data file of a client side, and rendering the component based on the obtained component data. Referring to FIG. 1, a diagram of a prior art component data processing system is schematically shown according to an embodiment of the present application. The client is installed on the electronic device 110, the electronic device is connected to the component server 130 through a network, and since the electronic device 110 where the client is installed stores component data of a corresponding component of the client, the component data includes corresponding relations between all business components and interfaces, when a user triggers an icon corresponding to the business component, the client directly accesses data in the component server 130 or acquires data from the component server 130. In the processing scheme of the component data in the prior art, a client page cannot be changed, and particularly, when a service component of the page needs to be updated, the client needs to be upgraded or updated, so that the user experience is very poor.
In order to solve the problems in the prior art, the present application provides a component data processing method, device, apparatus, and storage medium. Referring to fig. 2, a schematic diagram of an element data processing system according to an embodiment of the present application is schematically shown. The electronic device 210 where the client is located is connected to the management server 220 where the management server is located through a network, and the management server 220 is connected to the component servers 230, each of which stores component data corresponding to a business component, through a network. The component server 230 is further configured to store component data of corresponding services and provide related data of services corresponding to the service components. The client is used for presenting a page for interaction for a user and receiving and responding to an instruction triggered by the page for interaction by the user. The management server may be configured to pre-store a correspondence between each service component and an interface, determine a target service component corresponding to the client in response to a component data request sent by the client, and obtain component data of the target service component from an interface corresponding to the target service component according to the correspondence between each service component and the interface.
The client terminal provided by the application can be a program running on the electronic equipment, the management server terminal can be a service or a program running on the management server, and the component server terminal can be a service or a program running on the component server.
Referring to fig. 3, a partial flowchart of an assembly data processing method schematically illustrated in an embodiment of the present application is shown. The method comprises the following steps:
step S310: the client sends a component data request to the management server.
In some examples, the client sending the component data request to the management server may be triggered when the page is loaded. In some examples, a unified portal may be presented on the client page, e.g., referring to fig. 4, a unified portal 420 may be presented on the client page 410, and when the user clicks on the unified portal 420, the client may send a request to the management server.
The "component data" proposed in the embodiments of the present application may include at least any one of: icon data of the service component, the corresponding relation between the service component and the interface, state data of the service component and the like. The state data of the service component may be used to represent dynamic data of a service corresponding to the service component, for example, data representing online time of the service, data representing a user who is using the service, data representing a related behavior of the client using the service last time, and the like.
After receiving the component data request, the management server executes step S320: and determining the target business components to be displayed at the client.
Step S330: and the management server determines the interface corresponding to the target service component according to the pre-stored corresponding relationship between the service component and the interface.
Step S340: and the management server acquires the component data through the interface corresponding to the target service component. In this step, the interface corresponding to the target service component of the management server may be used to obtain component data from the corresponding component server.
Step S350: and the management server side sends the component data to the client side.
Step S360: and the client receives the component data, and displays the target business component according to the component data if the uniform entrance aiming at the business component is triggered.
Referring to fig. 4, a uniform entry 420 for a service component may be displayed on a page of a client 410, and after a user triggers the entry 420, a corresponding target service component is displayed, for example, in fig. 4, components 431 and 433 are target service components corresponding to the client.
When the target service component displayed on the page needs to be updated, the corresponding relationship between the prestored service component and the interface can be configured at the management server through an official worker, or the corresponding relationship between the prestored service component and the interface can be automatically updated when the management server receives an update instruction, wherein the update instruction can be that a new component server pushes service data corresponding to the new service component to the management server.
According to the method and the device, the management server is added to manage the corresponding relation between the service components and the interfaces, when a component data request sent by the client is received, the target service components to be displayed by the client are determined, component data are requested from the interfaces corresponding to the target service components according to the corresponding relation between the service components and the interfaces, the problem that the client needs to be updated every time the service components are updated due to the fact that the component data (including the corresponding relation between the service components and the interfaces) are directly prestored by the client in the prior art is solved, the updating frequency of the client is greatly reduced, the flexibility of the client page is improved, the service components are folded under a unified entrance, and occupation of the page space is reduced.
Further, in some examples, all clients may display the same target business component, and in other examples, different clients may display different target business components, that is, personalized target business components may be displayed for different users.
Taking an example that different clients can show different target service components, specifically, the management server may store the service components in a classified manner according to category identifiers in advance, where the category identifiers may include: identity information (such as popularity value of a main broadcast, audience and the main broadcast), identification information of a live broadcast room where the client is located, information of categories of the client and the like, wherein the live broadcast platform can be classified according to live broadcast contents on the live broadcast platform, and the classification comprises the following steps: the client sides located in different categories can carry the category identification of the category where the client sides are located. The method comprises the steps that a component data request sent by a client to a management server carries a class identifier of the client, after the management server receives the request, a target service component corresponding to the client is determined according to the class identifier carried by the request, component data corresponding to the target service component is obtained according to an interface corresponding to the target service component and sent to the client, and therefore the client can display the target service component. According to the method and the device, the service components are stored in the management server side in a classified mode according to the class identifications in advance, and when the request sent by the client side is received, the target service component corresponding to the client side is determined according to the class identification carried by the client side, so that different client sides can display different target service components, not only can the personalized target service component be displayed according to each type of client side, but also the page space of the client side can be reasonably utilized.
In another example, the client is taken as a live broadcast client for description, and with reference to fig. 5, a schematic diagram of an internet live broadcast scene provided in an exemplary embodiment of the present application is shown. The anchor client 511 and the viewer client 521 are installed on the electronic devices 510 and 520, respectively, and may establish a connection with a management server, which may be a program running on the server 500, through a network. Describing by taking the anchor client 511 and the viewer client 521 in the same live broadcast room as an example, after the anchor client 511 sends a component data request to the management server, the management server determines that a target service component of the anchor client 511 is the service component 512 plus 515 according to the category identifier of the anchor client, and after acquiring component data corresponding to the service component 512 plus 515 from a corresponding component server, the management server sends the component data corresponding to the service component 512 plus 515 to the anchor client 511, and when a user clicks a unified entry, the service component 512 plus 515 can be shown; after the viewer client 521 sends a component data request to the management server, the management server determines that a target service component of the viewer client 521 is the service component 523 plus 525 according to the category identifier of the anchor client, and after the management server obtains the component data corresponding to the service component 523 plus 525 from the corresponding component server, the management server sends the component data corresponding to the service component 523 plus 525 to the viewer client 521, when a user clicks a unified entry, the service component 523 plus 525 can be displayed, and at this time, the service component displayed by the viewer client is different from the service component displayed by the anchor client; when the user of the anchor client 511 clicks the icon of the service component 512, the anchor client 511 may send an instruction for triggering the service component 512 to the management server, and after receiving the instruction, the management server may change the target service component corresponding to the viewer client 521, and add the service component 522 as the target service component of the viewer client 521. Therefore, the anchor client triggers the service component which can control the exhibition of the audience client in the live broadcast room, so that the anchor can better control the interaction with the audience in the live broadcast, and the user experience is good.
Referring to fig. 6, which is a partial flowchart of another component data processing method according to the present application, the method may be executed by a management server, and the method includes the steps of:
s610: after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
s620: and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
The detailed description of each step in fig. 6 is provided in the embodiment corresponding to fig. 3, and is not repeated herein.
Corresponding to the embodiment of the component data processing method, the application also provides an embodiment of a component data processing device.
The embodiment of the component data processing device can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 7, the hardware structure diagram of the electronic device in which the device data processing apparatus of the present application is located is shown in fig. 7, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 7, the electronic device in which the apparatus is located in the embodiment may also include other hardware according to the actual function of the device data processing apparatus, which is not described again. Referring to fig. 7, the present application further discloses an electronic device 700, including: a memory 702 storing instructions executable by the processor 701; wherein the processor is coupled to the memory for reading program instructions stored by the memory and, in response, performing the following:
after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client through a pre-stored corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
Referring to fig. 8a, there is provided a block diagram of an assembly data processing system according to the present application, the system comprising:
the client 810 is configured to send a component data request to the management server, and when a unified entry for a business component is triggered, display a target business component according to the component data;
the management server 820 is configured to determine a target service component that needs to be displayed at the client after receiving the component data request, obtain component data through an interface corresponding to the target service component according to a pre-stored correspondence between the service component and the interface, and send the component data to the client.
Referring to FIG. 8b, the component data processing system may further include: the component server 830 is configured to provide component data to the management server through the interface.
Referring to fig. 9, an apparatus 900 for processing component data includes:
a processing module 910, configured to determine, after receiving a component data request sent by a client, an interface corresponding to a target service component that needs to be displayed on the client according to a pre-stored correspondence between a service component and the interface, and obtain component data through the interface corresponding to the target service component;
a sending module 920, configured to send the component data to a client, so that the client displays the target service component according to the component data when a unified entry for the service component is triggered.
In some examples, the request to obtain component data is triggered when a client page is loaded or a user clicks on a unified portal for a business component.
In some examples, an update condition of a service component is obtained, and a correspondence between the service component and an interface is updated according to the update condition.
In some instances, it may be desirable to,
the request carries a category identification of the client;
the service components comprise at least two component types, and each type of service component corresponds to a corresponding client type identifier.
In some examples, the category identification includes at least any one of: user identity identification, live broadcast room identification and identification of the type of the live broadcast room.
In the embodiments of the present application, the computer readable storage medium may be in various forms, such as, in different examples: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof. In particular, the computer readable medium may be paper or another suitable medium upon which the program is printed. Using these media, the programs can be electronically captured (e.g., optically scanned), compiled, interpreted, and processed in a suitable manner, and then stored in a computer medium.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (12)
1. A method of component data processing, the method comprising:
the client sends a component data request to the management server;
after receiving the component data request, the management server determines a target service component which needs to be displayed at the client, updates the corresponding relation between the pre-stored service component and the interface, acquires component data through the interface corresponding to the target service component according to the corresponding relation between the service component and the interface, and sends the component data to the client; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, the corresponding relation between the service component and the interface;
and the client receives the component data, and displays the target business component according to the component data if the uniform entrance aiming at the business component is triggered.
2. The method of claim 1, wherein the interface points to a corresponding component server;
the acquiring component data through the interface corresponding to the target service component includes:
and acquiring component data from a component server corresponding to the interface through the interface corresponding to the target service component.
3. A method of component data processing, the method comprising:
after receiving a component data request sent by a client, updating a corresponding relation between a prestored service component and an interface, determining an interface corresponding to a target service component to be displayed on the client according to the corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, the corresponding relation between the service component and the interface;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
4. The method of claim 3, wherein the request to obtain component data is triggered when a client page is loaded or a user clicks on the unified portal.
5. The method according to claim 3, wherein an update condition of a service component is obtained, and the correspondence between the service component and an interface is updated according to the update condition.
6. The method of claim 3, comprising:
the request carries a category identification of the client;
the service components comprise at least two component types, and each type of service component corresponds to a corresponding client type identifier.
7. The method of claim 6, wherein the category identification comprises at least any one of: user identity identification, live broadcast room identification and identification of the type of the live broadcast room.
8. An apparatus for processing component data, the apparatus comprising:
the processing module is used for updating a corresponding relation between a prestored service component and an interface after receiving a component data request sent by a client, determining an interface corresponding to a target service component to be displayed on the client according to the corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, the corresponding relation between the service component and the interface;
and the sending module is used for sending the component data to the client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
9. An element data processing system, the system comprising:
the client is used for sending a component data request to the management server and displaying a target business component according to the received component data when a uniform entrance aiming at the business component is triggered;
the management server is used for determining a target service component which needs to be displayed at the client after receiving the component data request, updating the corresponding relation between the prestored service component and the interface, acquiring component data through the interface corresponding to the target service component according to the corresponding relation between the service component and the interface, and sending the component data to the client; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, and the corresponding relation between the service component and the interface.
10. The system of claim 9, further comprising a component server;
and the component server is used for providing component data to the management server through the interface.
11. An electronic device, comprising:
a processor; a memory for storing the processor-executable instructions;
wherein the processor is configured to perform the following operations:
after receiving a component data request sent by a client, updating a corresponding relation between a prestored service component and an interface, determining an interface corresponding to a target service component to be displayed on the client according to the corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, the corresponding relation between the service component and the interface;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
12. A machine-readable storage medium having stored thereon computer instructions that, when executed, perform the following:
after receiving a component data request sent by a client, updating a corresponding relation between a prestored service component and an interface, determining an interface corresponding to a target service component to be displayed on the client according to the corresponding relation between the service component and the interface, and acquiring component data through the interface corresponding to the target service component; the interface is used for pointing to a corresponding component server; the component data includes at least one of: the icon data of the service component, the corresponding relation between the service component and the interface;
and sending the component data to a client so that the client can display the target business component according to the component data when a uniform entrance aiming at the business component is triggered.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110447330.5A CN113055702B (en) | 2018-02-08 | 2018-02-08 | Method, system and client for displaying business components |
| CN201810129017.5A CN108419089B (en) | 2018-02-08 | 2018-02-08 | Component data processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810129017.5A CN108419089B (en) | 2018-02-08 | 2018-02-08 | Component data processing method, device, equipment and storage medium |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110447330.5A Division CN113055702B (en) | 2018-02-08 | 2018-02-08 | Method, system and client for displaying business components |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108419089A CN108419089A (en) | 2018-08-17 |
| CN108419089B true CN108419089B (en) | 2021-04-27 |
Family
ID=63127027
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810129017.5A Active CN108419089B (en) | 2018-02-08 | 2018-02-08 | Component data processing method, device, equipment and storage medium |
| CN202110447330.5A Active CN113055702B (en) | 2018-02-08 | 2018-02-08 | Method, system and client for displaying business components |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110447330.5A Active CN113055702B (en) | 2018-02-08 | 2018-02-08 | Method, system and client for displaying business components |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN108419089B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111580892B (en) * | 2019-02-19 | 2023-09-19 | 杭州海康威视系统技术有限公司 | Method, device, terminal and storage medium for calling service components |
| CN110233840B (en) * | 2019-06-06 | 2022-02-25 | 广州虎牙信息科技有限公司 | Service processing method, device, equipment and storage medium |
| CN110381332A (en) * | 2019-08-01 | 2019-10-25 | 广州虎牙科技有限公司 | Direct broadcasting room component processing method, device, electronic equipment and readable storage medium storing program for executing |
| CN110543327B (en) * | 2019-09-06 | 2023-08-01 | 深圳前海环融联易信息科技服务有限公司 | Service component multiplexing method, device, computer equipment and storage medium |
| CN110865861B (en) * | 2019-11-12 | 2021-06-15 | 北京城市网邻信息技术有限公司 | Service data processing method and device |
| CN111159108A (en) * | 2019-12-18 | 2020-05-15 | 北京达佳互联信息技术有限公司 | Component management method and device, electronic equipment and storage medium |
| CN111190661B (en) * | 2019-12-31 | 2021-09-28 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
| CN111405300A (en) * | 2020-02-28 | 2020-07-10 | 北京达佳互联信息技术有限公司 | Pendant display method and device, electronic equipment and computer readable storage medium |
| CN114090083B (en) * | 2020-07-31 | 2023-08-15 | 中移(苏州)软件技术有限公司 | Visual component configuration method, device, equipment and storage medium |
| CN112948408B (en) * | 2021-03-04 | 2022-07-08 | 上海哔哩哔哩科技有限公司 | Data processing method and device |
| CN113438497B (en) * | 2021-07-08 | 2022-08-30 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and computer readable storage medium |
| CN113672309A (en) * | 2021-08-20 | 2021-11-19 | 北京乐学帮网络技术有限公司 | Business service method, device, electronic equipment and readable storage medium |
| CN114625458A (en) * | 2022-02-16 | 2022-06-14 | 中国建设银行股份有限公司 | Page data processing method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1834918A (en) * | 2005-11-04 | 2006-09-20 | 北京金山软件有限公司 | Call method between chip |
| WO2010080608A1 (en) * | 2008-12-18 | 2010-07-15 | Qsc Audio Products, Llc | Audio system control interface |
| CN102646054A (en) * | 2012-02-27 | 2012-08-22 | 华为终端有限公司 | Terminal assembly management method and terminal |
| CN102681825A (en) * | 2011-03-09 | 2012-09-19 | 北京航空航天大学 | System and method for managing service run container |
| CN106446049A (en) * | 2016-08-31 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Page data interaction apparatus and method |
| CN107479861A (en) * | 2016-06-07 | 2017-12-15 | 阿里巴巴集团控股有限公司 | Page processing method and its system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080320502A1 (en) * | 2007-06-20 | 2008-12-25 | Microsoft Corporation | Providing Information about Software Components |
| CN105760149B (en) * | 2014-12-18 | 2020-05-05 | 阿里巴巴集团控股有限公司 | Client interface dynamic display method and system |
| CN106936937B (en) * | 2015-12-29 | 2020-09-08 | 阿里巴巴集团控股有限公司 | Method and device for realizing universal interface for internet service interaction |
| CN106021617B (en) * | 2016-07-12 | 2018-09-28 | 腾讯科技（深圳）有限公司 | The method and apparatus that the page generates |
| CN106656622B (en) * | 2016-12-29 | 2020-04-24 | 深圳Tcl新技术有限公司 | Method and device for configuring interface calling task |
-
2018
- 2018-02-08 CN CN201810129017.5A patent/CN108419089B/en active Active
- 2018-02-08 CN CN202110447330.5A patent/CN113055702B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1834918A (en) * | 2005-11-04 | 2006-09-20 | 北京金山软件有限公司 | Call method between chip |
| WO2010080608A1 (en) * | 2008-12-18 | 2010-07-15 | Qsc Audio Products, Llc | Audio system control interface |
| CN102681825A (en) * | 2011-03-09 | 2012-09-19 | 北京航空航天大学 | System and method for managing service run container |
| CN102646054A (en) * | 2012-02-27 | 2012-08-22 | 华为终端有限公司 | Terminal assembly management method and terminal |
| CN107479861A (en) * | 2016-06-07 | 2017-12-15 | 阿里巴巴集团控股有限公司 | Page processing method and its system |
| CN106446049A (en) * | 2016-08-31 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Page data interaction apparatus and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113055702A (en) | 2021-06-29 |
| CN113055702B (en) | 2023-06-27 |
| CN108419089A (en) | 2018-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108419089B (en) | Component data processing method, device, equipment and storage medium | |
| CN107920112B (en) | Configuration file pushing method supporting gray mode, central server and storage medium | |
| CN112784184B (en) | ADX-based advertisement landing page dynamic generation method, computer equipment and storage medium | |
| CN110096660B (en) | Method and device for loading page pictures and electronic equipment | |
| CN102197409A (en) | Dynamic in-page advertising | |
| CN104219246A (en) | Method and device for controlling display interface of client | |
| US20170192941A1 (en) | Computer-Automated Generation of Application Deep Links | |
| US20170316455A1 (en) | System and Method for Counting Advertisement Impressions | |
| EP3528474B1 (en) | Webpage advertisement anti-shielding methods and content distribution network | |
| CN111368235A (en) | Page rendering and displaying method, device, server and storage medium | |
| CN110958462A (en) | Live broadcast activity page display method and device, storage medium and live broadcast system | |
| CN109168012B (en) | Information processing method and device for terminal equipment | |
| CN108196902B (en) | Method and apparatus for displaying open screen advertisements | |
| CN111367518A (en) | Page layout method and device, computing equipment and computer storage medium | |
| CN105224611A (en) | Based on the operation processing method of browser, device and browser | |
| CN111079048A (en) | Page loading method and device | |
| CN113781115A (en) | Advertisement display method, system, equipment and storage medium | |
| CN113747190A (en) | Live broadcast data processing method, device, equipment and storage medium | |
| CN110456999B (en) | Program creation method, program creation device, electronic equipment and computer readable storage medium | |
| CN105426532A (en) | File operation method and device | |
| CN115756461A (en) | Annotation template generation method, image identification method and device and electronic equipment | |
| CN110300321B (en) | Banner display method and device | |
| AU2016354677B2 (en) | A method and system for distributing electronic publishing content | |
| CN117998147A (en) | Method, apparatus, device and medium for content presentation | |
| CN113190306A (en) | Display level switching method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |