Service list installation method and communication device

Abstract

According to the service list installation method and the communication device, in the method, a terminal can obtain a service list, the service list comprises first information, the first information is used for obtaining a first interaction result from a user when the service list is installed, and then the terminal installs or does not install the service list according to the first interaction result. According to the method, interaction with the user can be realized when the service list is installed, so that the number of times of interaction with the user is reduced, and user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more particularly, to a method for installing a service list and a communication device. Background Art

[0002] Digital Video Broadcasting (DVB) is a series of internationally recognized open standards for digital television maintained by the DVB project. DVB standards provide a complete set of digital television system specifications applicable to different media. Digital Video Broadcasting-Internet (DVB-I) is a DVB-developed mechanism for discovering services over the Internet and then accessing them through various transmission methods.

[0003] When a DVB-I client discovers a service, it obtains and installs the corresponding service list (ServiceList). It then accesses the service based on the service information in the ServiceList. Because some services are subject to regulatory compliance, users must be informed and authorized before accessing the service. Alternatively, because some services involve personal privacy, user authorization is required before accessing the service. Currently, accessing a service in the ServiceList requires multiple interactions between the DVB-I client and the user, impacting the user experience. Summary of the Invention

[0004] The present application provides a method and a communication device for installing a service list, which can reduce the number of interactions between a user and a terminal and improve the user experience.

[0005] In a first aspect, a method for installing a service list is provided. The method can be executed by a terminal, or by a component of the terminal (such as a chip or circuit), without limitation. For example, in a DVB system, the terminal can be considered a DVB-I client.

[0006] The method includes: obtaining a service list, the service list including first information, the first information being used to obtain a first interaction result from a user when installing the service list; obtaining the first interaction result according to the first information; and installing or not installing the service list according to the first interaction result.

[0007] In the above technical solution, the terminal can interact with the user for the services in the service list to obtain the first interaction result when installing the service list. The terminal determines whether to install the first service list based on the first interaction result. This method can avoid the user from interacting with the terminal multiple times when accessing the services in the service list, thereby improving the user experience.

[0008] In certain implementations of the first aspect, the service list further includes service information of at least one service.

[0009] In certain implementations of the first aspect, the first information includes information or a first address that requires user confirmation when installing the service list, the first address is the access entry address of the information that requires user confirmation when installing the service list, and the first interaction result includes the user's confirmation result of the information that requires user confirmation, or the first information is used to request the user to provide authentication information required when installing the service list, and the first interaction result includes the authentication information provided by the user.

[0010] In certain implementations of the first aspect, the first service list further includes second information, and the second information is used to send an interaction result with the user. The method further includes: sending the first interaction result according to the second information.

[0011] In certain implementations of the first aspect, the second information includes a second address, which is a destination address for sending the first interaction result.

[0012] In certain implementations of the first aspect, after installing the service list according to the first interaction result, the method further includes: obtaining a second interaction result from the user, the second interaction result instructing the user to update or revoke the first interaction result; sending the second interaction result according to the second information; and maintaining or deleting the service list according to the second interaction result.

[0013] In one possible scenario, because the information related to the installation of the first service list has changed (for example, the information that requires user confirmation when installing the service list has changed, or the authentication information previously provided by the user has expired, etc.), the terminal displays new information that requires user confirmation to the user, or re-requests the user to provide authentication information, and then obtains a new interaction result from the user (i.e., updates the first interaction result).

[0014] In another possible scenario, after the service list is installed, after a period of time, the user decides to cancel the previous confirmation of information requiring user confirmation or cancel the previous authentication, and the terminal obtains a new interaction result from the user (i.e., cancels the first interaction result).

[0015] In certain implementations of the first aspect, the service list includes service information for multiple services, and the service list also includes an applicable scope of the first information, where the applicable scope indicates a range of services in the service list to which the first information applies. For example, the applicable scope may be all services in the service list, or the applicable scope may be a subset of services in the service list.

[0016] In some implementations of the first aspect, the first information indicates a first associated application.

[0017] In the above technical solution, the terminal can interact with the user through the first associated application when installing the service list.

[0018] In certain implementations of the first aspect, the first information includes information of the first associated application, and the information of the first associated application includes at least one of the following: an identifier of the first associated application, a type of the first associated application, a startup condition of the first associated application, and a lifecycle of the first associated application.

[0019] In certain implementations of the first aspect, the method further includes: sending an interaction result with the user through the first associated application.

[0020] In certain implementations of the first aspect, the method further includes: obtaining, through the first associated application, information that requires user confirmation when installing the service list, and the first interaction result includes the user's confirmation result of the information that requires user confirmation; or, obtaining, through the first associated application, request information, the request information is used to request the user to provide authentication information required when installing the service list, and the first interaction result includes the authentication information provided by the user.

[0021] In the above technical solution, the terminal can obtain confirmation information or authentication request related to the installed service list through the first associated application.

[0022] In certain implementations of the first aspect, after the service list is installed according to the first interaction result, the method further includes: obtaining a second interaction result from the first associated application or the second associated application, the second interaction result instructing the user to update or revoke the first interaction result; sending the second interaction result through the first associated application or the second associated application, wherein the second associated application is used to implement interaction with the user after the service list is installed; and maintaining or deleting the service list according to the second interaction result.

[0023] In the above technical solution, after the service list is installed, the terminal can continue to update or cancel the interaction with the user based on the first associated application, or update or cancel the interaction with the user based on a new associated application.

[0024] In certain implementations of the first aspect, the first information further includes information about the second associated application, and the information about the second associated application includes at least one of the following: an identifier of the second associated application, a type of the second associated application, a startup condition of the second associated application, and a lifecycle of the second associated application.

[0025] In certain implementations of the first aspect, the service list is installed or not installed according to the first interaction result, including: if the first interaction result indicates that the user agrees to the information that requires user confirmation, then the service list is installed; or, if authentication confirmation information is received, and the authentication confirmation information indicates that the authentication information provided by the user has passed the authentication, then the service list is installed.

[0026] In certain implementations of the first aspect, the information that requires user confirmation when installing the service list includes at least one of an agreement, terms, and conditions that the user needs to agree to when accessing a service in the service list.

[0027] In a second aspect, a method for installing a service list is provided. The method may be executed by a service list server, or may be executed by a component (such as a chip or circuit) of the service list server, without limitation.

[0028] The method includes: configuring a service list, the service list including first information, the first information being used to obtain a first interaction result from a user when installing the service list, the first interaction result being used to determine whether a terminal can install the service list; and sending the service list to the terminal.

[0029] For the beneficial effects of the second aspect, please refer to the description of the first aspect and will not be repeated here.

[0030] In certain implementations of the second aspect, the first information includes information or a first address that requires user confirmation when installing the service list, the first address is the access entry address of the information that requires user confirmation when installing the service list, and the first interaction result includes the user's confirmation result of the information that requires user confirmation, or the first information is used to request the user to provide authentication information required when installing the service list, and the first interaction result includes the authentication information provided by the user.

[0031] In certain implementations of the second aspect, the first service list further includes second information, and the second information is used to send an interaction result with the user. The method further includes: sending the first interaction result according to the second information.

[0032] In certain implementations of the second aspect, the second information includes a second address, which is a destination address for sending the first interaction result.

[0033] In some implementations of the second aspect, the first information indicates a first associated application.

[0034] In certain implementations of the second aspect, the first information includes information of the first associated application, and the information of the first associated application includes at least one of the following: an identifier of the first associated application, a type of the first associated application, a startup condition of the first associated application, and a lifecycle of the first associated application.

[0035] In certain implementations of the second aspect, the service list includes service information of at least one service.

[0036] In certain implementations of the second aspect, if the first interaction result indicates that the user agrees to install the service list, the authorization server may assign a first confirmation identifier to a service in the service list. The first confirmation identifier is used by the terminal to subsequently access the service in the service list from the service provider. The authorization server then notifies the terminal and the service provider of the first confirmation identifier. It is understood that the services in the service list are provided by the service provider.

[0037] For example, the first confirmation identifier may be a token.

[0038] In certain implementations of the second aspect, the method further includes: receiving first service list configuration information from a service provider, the first service list configuration information including service information and the first information; or, receiving second service list configuration information from the service provider, the second service list configuration information including service information, and determining the first information based on the service information.

[0039] In certain implementations of the second aspect, the first information is further used to indicate a second associated application, and the second associated application is used to implement interaction with the user after the service list is installed.

[0040] In certain implementations of the second aspect, the first information further includes information about the second associated application, and the information about the second associated application includes at least one of the following: an identifier of the second associated application, a type of the second associated application, a startup condition of the second associated application, and a lifecycle of the second associated application.

[0041] In a third aspect, a method for installing a service list is provided. The method may be executed by an authorization server, or may be executed by a component of the authorization server (eg, a chip or circuit), without limitation.

[0042] The method includes: receiving a first interaction result from a terminal, the first interaction result being an interaction result between the terminal and a user, and the first interaction result being used to determine whether the terminal can install a service list; and sending a first message to the terminal, the first message being used to confirm receipt of the first interaction result.

[0043] For the beneficial effects of the third aspect, please refer to the description of the first aspect and will not be repeated here.

[0044] In certain implementations of the third aspect, receiving the first confirmation message from the terminal includes: receiving a first interaction result of a first associated application from the terminal.

[0045] In certain implementations of the third aspect, the first interaction result includes a confirmation result of the user for information requiring user confirmation.

[0046] In certain implementations of the third aspect, the information that requires user confirmation when installing the service list includes at least one of an agreement, terms, and conditions that the user needs to agree to when accessing a service in the service list.

[0047] In certain implementations of the third aspect, the first interaction result includes authentication information provided by the user, and the first message includes authentication confirmation information, which indicates whether the authentication information provided by the user has passed or failed authentication.

[0048] In certain implementations of the third aspect, the first interaction result is used to determine whether the terminal can install the service list, and the method further includes: receiving a second interaction result from the terminal, the second interaction result instructing the user to update or revoke the first interaction result.

[0049] In certain implementations of the third aspect, a second interaction result of a second associated application from the terminal is received, and the second associated application is used to implement interaction with the user after the service list is installed.

[0050] In a fourth aspect, a communication device is provided, which is used to execute the method provided in any one of the first to third aspects. Specifically, the communication device may include a unit and / or module for executing the method provided in the first aspect or any one of the above-mentioned implementations of the first aspect, or include a unit and / or module for executing the method provided in the second aspect or any one of the above-mentioned implementations of the second aspect, or include a unit and / or module for executing the method provided in the third aspect or any one of the above-mentioned implementations of the third aspect.

[0051] In one implementation, the communication device is a device (e.g., a terminal device, a service list server, or an authorization server). When the communication device is a device, the transceiver unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0052] In another implementation, the communication device is a chip, chip system, or circuit used in a device (e.g., a terminal device, a service list server, or an authorization server). When the communication device is a chip, chip system, or circuit used in a device, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0053] In a fifth aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0054] In one implementation, the communication device is a device (eg, a terminal device, a service list server, or an authorization server).

[0055] In another implementation, the apparatus is a chip, a chip system, or a circuit used in a device (such as a terminal device, a service list server, or an authorization server).

[0056] In a sixth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0057] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0058] In the seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes instructions for executing the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or includes instructions for executing the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or includes instructions for executing the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0059] In an eighth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or the computer is caused to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or the computer is caused to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0060] In the ninth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface, executes the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or executes the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or executes the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0061] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by the above-mentioned first aspect or any one of the above-mentioned implementation methods of the first aspect, or execute the method provided by the above-mentioned second aspect or any one of the above-mentioned implementation methods of the second aspect, or execute the method provided by the above-mentioned third aspect or any one of the above-mentioned implementation methods of the third aspect.

[0062] In a tenth aspect, a communication system is provided, comprising at least one of the terminal device, the service list server and the authorization server mentioned above. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 Schematic diagram of the DVB-I logical architecture.

[0064] Figure 2 and Figure 3 A schematic diagram of a system architecture applicable to an embodiment of the present application.

[0065] Figure 4 It is a schematic flowchart of a method 400 for installing a service list provided in an embodiment of the present application.

[0066] Figures 5 to 7 This embodiment of the application is based on Figure 2 The illustrated architecture provides a schematic flow chart of a specific method for installing a service list.

[0067] Figures 8 to 10 This embodiment of the application is based on Figure 3 The illustrated architecture provides a schematic flow chart of a specific method for installing a service list.

[0068] Figures 11 to 13 This embodiment of the application is based on Figure 2 The illustrated architecture provides a schematic flow chart of another specific method for installing a service list.

[0069] Figures 14 to 16 This embodiment of the application is based on Figure 3 The illustrated architecture provides a schematic flow chart of another specific method for installing a service list.

[0070] Figure 17 It is a schematic block diagram of a communication device 200 provided in an embodiment of the present application.

[0071] Figure 18 A schematic block diagram of a communication device 300 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0073] Before introducing the embodiments of the present application, the following points are first explained.

[0074] 1. In the description of the embodiments of the present application, unless otherwise specified, “multiple” means two or more.

[0075] 2. In the various embodiments of the present application, unless otherwise specified or provided for by logic, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0076] 3. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of this application. The size of the serial numbers involved in this application does not mean the order of execution. The execution order of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third" and other various terminology labels (such as #1, #2, #3) in the specification and claims and drawings of this application are used to distinguish similar objects and are not used to limit the size, content, sequence, timing, priority or importance of multiple objects. For example, the first information and the second information do not represent the difference in the amount of information, content, priority or importance.

[0077] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0078] 5. In each embodiment of the present application, "network element A sends information A to network element B" can be understood as the destination end of the information A or the intermediate network element in the transmission path between the destination end and the network element B, which may include directly or indirectly sending information to network element B. "Network element B receives information A from network element A" can be understood as the source end of the information A or the intermediate network element in the transmission path between the source end and the network element A, which may include directly or indirectly receiving information from network element A. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be elaborated here.

[0079] In other words, sending and receiving can be performed between devices, for example, between terminal device #1 and terminal device #2, or can be performed within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, traces or interface.

[0080] 6. In the embodiments of the present application, indications include direct indications (also called explicit indications) and implicit indications. Direct indication of information A refers to including information A; implicit indication of information A refers to indicating information A through the correspondence between information A and information B and the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0081] 7. In the embodiments of the present application, information C is used to determine information D, which includes information D being determined solely based on information C, as well as information D being determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, where information D is determined based on information E, and information E is determined based on information C.

[0082] 8. "Storage" or "saving" in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, a processor, or a communication device. The type of memory may be any form of storage medium and is not limited in this application.

[0083] 9. The dotted arrows or boxes in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0084] The technical solutions of the embodiments of the present application can be applied to various communication systems, including but not limited to: the 5th generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. In addition, it can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication system or other communication systems, etc., and the present application does not limit this.

[0085] Figure 1 This is a diagram of the DVB-I logical architecture. The architecture includes a DVB-I client, a service list server, a content / service provider (hereinafter referred to as a service provider), a media presentation description (MPD) server, a stream server, a content guide server, a service list registry server, and a playlist server.

[0086] Among them, the DVB-I client is a client functional network element that supports DVB-I service discovery. The DVB-I client can be integrated into various terminal devices such as mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, smart TVs, set-top boxes, etc. The service list server is a server that provides service lists to the DVB-I client. The service provider is an organization that provides DVB-I services. The MPD server is a server that provides dynamic adaptive streaming over HTTP (DASH) MPD files based on the Hypertext Transfer Protocol. The traffic server is a server that provides DASH media segments to the DVB-I client, and the content guide server is a server that provides content guide data to the DVB-I client. The service list registration server is a server that provides the service list server address to the DVB-I client. The playlist server is a server that provides the playlist of content items to the DVB-I client.

[0087] Generally, the service provider sends the service list that can be provided to the service list server. The service list server registers the service list access entry address (such as the Uniform Resource Identifier (URI)) to the service list registration server. When the DVB-I client discovers a service, the DVB-I client obtains the service list access entry address from the service list registration server through the address of the service list registration server. The DVB-I client then queries and obtains the service list through the service list access entry address. A service list includes service information of one or more services. For example, the service information of service #1 may include the service identifier (ID), service name, service provider name, service type, and service instance (Service Instance) of service #1. If service #1 also provides additional service capabilities through linked applications, the service list also includes information about linked applications.

[0088] Currently, after the DVB-I client completes the installation of the service list, when the user uses a specific service, the user is required to perform service permission (consent or authorization) for different services or be requested to provide authentication information, which affects the user experience.

[0089] In view of this, the present application provides a method for installing a service list, which can effectively solve the above technical problems. Two possible system architectures applicable to the embodiments of the present application are given below as examples.

[0090] Figure 2 A schematic diagram of a system architecture applicable to an embodiment of the present application. Figure 2 The dotted box in the figure can be regarded as the service list provider (Service List Provider). Figure 1 The architecture shown, Figure 2 The illustrated system architecture adds an authorization server to the service list provider. This authorization server is responsible for interacting with the DVB-I client and obtaining the results of the user's interaction with the DVB-I client. The service list provider also includes the service list server. In a specific implementation, the service list server and authorization server can be co-located or separate. For example, if the authorization server is integrated into the service list server, the interaction between the terminal and the authorization server is equivalent to the interaction between the terminal and the service list server.

[0091] Figure 3 This is a schematic diagram of another system architecture applicable to the embodiment of the present application. Figure 1 The architecture shown, Figure 3 The system architecture shown adds an authorization server on the service provider side. For example, the service provider may also include a management server, which can be used to configure a service list for the service list server.

[0092] It is understood that if the method proposed in this application is applied to Figure 2 In the architecture shown in FIG, the service list provider performs the steps that the authorization server needs to perform in the corresponding method. Similarly, if the method proposed in this application is applied to Figure 3 In the architecture shown, the service provider performs the steps required by the authorization server in the corresponding method. It can also be understood that Figure 2 and Figure 3 This is just an example. In another possible system architecture, the authorization server can be established independently of the service list provider and the service provider, and this application does not impose any limitation on this.

[0093] The following combination Figure 4 The method provided in this application is introduced in detail. Figure 4 The method shown is performed through interaction between a terminal (e.g., a DVB-I client), a service list server, and an authorization server. Of course, other devices may be involved in some steps, which are not specifically limited here. To facilitate the description of the steps that the authorization server needs to perform, Figure 4The authorization server is described as a separate server.

[0094] Figure 4 This is a schematic flow chart of a method 400 for installing a service list provided in an embodiment of the present application. In this solution, a terminal needs to obtain a service list. The terminal can obtain the service list from a service list server or from other terminals. For example, if terminal A has already obtained and stored the service list, terminal B can request the service list from terminal A. Of course, in actual applications, the terminal may also obtain the service list through other methods, which are not specifically limited in this application. Figure 4 The method is described by taking the example of a terminal obtaining a service list from a service list server.

[0095] S401: A service list server sends a first service list to a terminal, the service list including first information used to obtain a first interaction result from a user when installing the service list. Correspondingly, the terminal receives the first service list from the service list server.

[0096] It is understood that the first service list also includes service information of at least one service. The above-mentioned installed service list refers to the services in the installed service list. For example, the service information of a service may include a service ID, service name, service provider name, service type, service instance, etc., which are not specifically limited here.

[0097] It can also be understood that the first interaction result is used to determine whether the terminal can install the service list.

[0098] In one possible implementation, the first information includes information requiring user confirmation when installing the service list, or the first information indicates a first address, where the first address is an access entry address for the information requiring user confirmation when installing the service list. Correspondingly, the first interaction result includes a user confirmation result of the information requiring user confirmation.

[0099] For example, when installing a service list, the information requiring user confirmation includes at least one of the following: agreements, terms, and conditions requiring user consent. For example, an agreement requiring user consent may include "whether to subscribe to a certain form of service." Another example is when the user needs to confirm clause #1, which states "whether personal data will be processed in accordance with the EU's General Data Protection Regulation."

[0100] In another possible implementation, the first information is used to request the user to provide authentication information required for installing the service list. Correspondingly, the first interaction result includes the authentication information provided by the user.

[0101] The first information includes the type of authentication information that the user needs to provide. For example, the authentication information required by the user is a password, a username, or facial information. For example, if the first information is used to request the user to provide the username and password required to install a service list, after the terminal obtains the first information, it displays the message "Please enter the username and password required to install the first service list" on the screen to the user.

[0102] Optionally, the first service list further includes second information, and the second information is used to send an interaction result with the user. For example, the second information can be used to send a first interaction result obtained based on the first information in the above two implementations.

[0103] Optionally, the second information includes a second address, and the second address is a destination address for sending the first interaction result. Based on the above two implementation methods.

[0104] In another possible implementation, the first information indicates the first associated application, that is, instructs the terminal to interact with the user through the first associated application to obtain the first interaction result when installing the service list.

[0105] Optionally, the first information includes information of the first associated application, and the information of the first associated application includes at least one of the following: an identifier of the first associated application, a type of the first associated application, a start condition of the first associated application, and a lifespan (ie, validity period) of the first associated application.

[0106] For example, the type of the first associated application indicates that the first associated application is a consent / authorization application required for installing the first service list containing the first information. The activation condition for the first associated application can be when the first service list is installed or when the first service list is loaded. For example, the lifetime of the first associated application is one week.

[0107] For example, the type of the first associated application can also be indirectly indicated by the identifier of the first associated application. For example, if the associated application types of the associated applications with identifiers 50 to 100 are defined as consent / authorization applications required for installing a service list, then an application can be selected from the applications with identifiers 50 to 100 as the first associated application.

[0108] Optionally, based on this implementation, the method also includes: the terminal activates the first associated application installed on the terminal, and obtains information that requires user confirmation when installing the first service list through the first associated application, and correspondingly, the first interaction result includes the user's confirmation result of the information that requires user confirmation; or, the terminal activates the first associated application installed on the terminal, and requests the user to provide authentication information required when installing the first service list through the first associated application, and correspondingly, the first interaction result includes the authentication information provided by the user.

[0109] Optionally, based on this implementation, the first associated application is further used to send an interaction result with the user (eg, a first interaction result).

[0110] It can be understood that the above examples are merely exemplary descriptions of the first information, and this application does not specifically limit the first information.

[0111] Optionally, before S401, the terminal may send a request message to the service list server according to the configuration, the request message being used to request the service list. For example, the configuration may be to obtain the service list periodically, or to obtain the service list upon first power-on, or when the terminal's location or language setting has changed.

[0112] S402: The terminal obtains a first interaction result according to the first information.

[0113] For the description of the first information and the first interaction result, please refer to the description in S401 and will not be repeated here.

[0114] S403: The terminal installs or does not install the first service list according to the first interaction result. That is, the terminal determines whether the first service list can be installed according to the first interaction result.

[0115] In one embodiment, the first interaction result includes a confirmation result of the user on the information requiring user confirmation. If the first interaction result indicates that the user agrees with the information requiring user confirmation, the terminal installs the first service list; otherwise, the terminal does not install the first service list.

[0116] In another embodiment, the first interaction result includes authentication information provided by the user. If the authentication information provided by the user passes authentication by the authorization server, the first service list is installed; otherwise, the first service list is not installed. Based on this embodiment, the method further includes receiving authentication confirmation information, the authentication confirmation information indicating whether the authentication information provided by the user passes authentication.

[0117] Optionally, if the first service list includes service information for multiple services, the first service list also includes an applicable scope of the first information, where the applicable scope indicates the scope of services in the first service list to which the first information applies. For example, the applicable scope may be all services in the first service list, or the applicable scope may be some services in the first service list.

[0118] Optionally, if the scope of application is all services in the first service list, it can be indicated by default without any information, or by carrying an indication information; if the scope of application is part of the services in the first service list, the scope of application can be indicated by carrying relevant parameters of the service, such as through the service identifier, service name, logical channel number (LCN) of the service, and one or more parameters in the service type.

[0119] The following description will take the example of the first information being information requiring user confirmation when installing the service list, and will explain whether to install the service list in combination with different applicable scopes.

[0120] For example, the scope of application of the first information is all services in the first service list. If the first interaction result indicates that the user agrees that the information that requires user confirmation when installing the service list applies to all services within the applicable scope, the terminal installs the first service list (that is, all services in the first service list are installed); if the first interaction result indicates that the user agrees that the information that requires user confirmation when installing the service list applies to some services within the applicable scope, the terminal only installs these services.

[0121] For example, the scope of application of the first information is some of the services in the first service list. If the first interaction result indicates that the user agrees that the information that requires user confirmation when installing the service list applies to all services within the scope of application, the terminal will install all services within the scope of application, and services outside the scope of application in the first service list can be installed directly; if the first interaction result indicates that the user agrees that the information that requires user confirmation when installing the service list applies to some of the services within the scope of application, the terminal will only install these services, and services outside the scope of application in the first service list can be installed directly.

[0122] For ease of description, the following description will take the application scope of the first information as all services in the first service list as an example, and installing / not installing the first service list means installing / not installing all services in the first service list.

[0123] Optionally, the method further includes:

[0124] S404: The terminal sends a first interaction result.

[0125] Optionally, the first service list includes second information, and the terminal device sends the first interaction result according to the second information.

[0126] Optionally, the first information indicates a first associated application, and the terminal sends the first interaction result through the first associated application.

[0127] As described above, the authorization server is responsible for interacting with the DVB-I client (i.e., the terminal) to obtain interaction results from the user. Therefore, when the terminal device sends the first interaction result based on the second information, it can be understood that the terminal device authorizes the server to send the first interaction result based on the second information. When the second information includes the second address, the second address is the address of the authorization server. Similarly, when the terminal sends the first interaction result via the first associated application, it can be understood that the terminal sends the first interaction result to the authorization server via the first associated application. Correspondingly, the authorization server receives the first interaction result from the terminal.

[0128] It can be understood that the first associated application and the authorization server are already associated, and therefore the address of the authorization server does not need to be included in the first service list, that is, the address of the authorization server is known to the associated application.

[0129] It can also be understood that the messages sent or received through the associated application in this application are all application layer messages. For example, the terminal sends the first interaction result through the first associated application, and the first interaction result can be carried in the first application layer message.

[0130] S405: The authorization server sends a first message to the terminal, where the first message is used to confirm receipt of the first interaction result. Correspondingly, the terminal receives the first interaction result from the authorization server.

[0131] It can be understood that if the terminal sends the first interaction result through the first associated application, the authorization server sends the first message to the first associated application of the terminal.

[0132] Optionally, the authentication confirmation information in S403 may be sent separately or carried in the first message, which is not limited in this application.

[0133] Optionally, if the first interaction result determines that the terminal can install the first service list, the authorization server may assign a first confirmation identifier to the services in the first service list. The first confirmation identifier is used by the terminal to subsequently access the services in the first service list from the service provider. The authorization server then notifies the terminal and the service provider of the first confirmation identifier. It is understood that the services in the first service list are provided by the service provider.

[0134] For example, the first confirmation identifier may be a token.

[0135] It should be noted that if the first interaction result in S402 includes the user's confirmation result of the information requiring user confirmation, S403 and S404 are executed in no particular order; if the first interaction result includes authentication information provided by the user, S403 is executed after S404.

[0136] Optionally, before S401, the method further includes:

[0137] S406: The service list server configures a first service list.

[0138] Two possible implementations are given below.

[0139] In method 1, the service provider's management server sends first service list configuration information to the service list server. The first service list configuration information includes the service information and the first information of at least one service in S401. In response, the service list server receives the first service list configuration information from the service provider's management server. The service list server then determines the first service list based on the received first service list configuration information.

[0140] For example, in this approach, the first service list configuration information may be manually configured offline by the service provider, or may be interactively configured between the management server of the service provider and the service list server.

[0141] In a second approach, the service provider's management server sends second service list configuration information to the service list server. The second service list configuration information includes service information of at least one service in S401. In response, the service list server receives the second service list configuration information from the service provider's management server. Subsequently, the service list server determines the first information based on the service information of the at least one service, thereby determining the first service list.

[0142] In one possible scenario, after the first service list is installed, some time later, due to changes in information related to the installation of the first service list (for example, changes in information that required user confirmation when installing the first service list, or expiration of authentication information previously provided by the user), the terminal needs to re-interact with the user to obtain a new interaction result (i.e., update the first interaction result) to confirm whether to maintain the installation of the first service list. For ease of description, this update process is described using the example of a change in information that required user confirmation when installing the first service list.

[0143] S407: The terminal obtains third information, which includes update information that requires user confirmation to maintain the first service list. Correspondingly, the terminal receives the third information from the service list server.

[0144] For example, the information requiring user confirmation in S401 includes Clause 1, such as "Do you agree to process personal data as defined in the GDPR?" If the user agrees to Clause 1, the terminal will install the first service list. Some time later, the information required for user confirmation for installing the first service list changes. For example, in addition to Clause 1, Clause 2 is added, which is "Do you agree to access services only within the EU?" In this case, the third information includes the updated information for Clauses 1 and 2.

[0145] Optionally, the third information is carried in a second service list, and the second service list also includes service information of at least one service in the first service list.

[0146] In one approach, if the terminal has not activated the first associated application (i.e., the first information does not indicate the first associated application), the terminal may send a request message to the service list server according to a configuration, requesting a service list. In response, the terminal obtains the second service list from the service list server. For example, the configuration may be a service list update period.

[0147] In another manner, if the terminal activates the first associated application (ie, the first information does not indicate the first associated application), the authorization server may directly send the third information to the first associated application installed in the terminal.

[0148] In another implementation, if the first information indicates not only the first associated application but also a second associated application, and the second associated application is used to interact with the user after the first service list is installed, then after the terminal completes the installation of the first service list, it activates the second associated application installed in the terminal, and the authorization server can directly send the third information to the second associated application.

[0149] S408: The terminal obtains a second interaction result from the user, where the second interaction result is a result of the user confirming the third information.

[0150] For example, based on the description in S407 , the terminal may directly interact with the user to obtain the second interaction result, or the terminal may interact with the user through the first associated application or the second associated application to obtain the second interaction result.

[0151] S409: The terminal maintains or deletes the first service list based on the second interaction result.

[0152] If the second interaction result indicates that the user agrees to the third information, the terminal maintains the installation of the first service list; otherwise, the terminal deletes the first service list (i.e., uninstalls the services in the installed first service list). Based on the example in S407, if the user agrees to clauses 1 and 2, the installed first service list is maintained; if the user disagrees with clauses 1 and 2, the installed first service list is deleted.

[0153] S410: The terminal sends a second interaction result.

[0154] For example, based on the description in S407 , the terminal may directly send the second interaction result, or the terminal may send the second interaction result through the first associated application or the second associated application.

[0155] As described above, the authorization server is responsible for interacting with the DVB-I client (i.e., the terminal) to obtain the interaction result from the user. Therefore, when the terminal device sends the second interaction result, it can be understood that the terminal sends the second interaction result to the authorization server. Correspondingly, the authorization server receives the second interaction result from the terminal.

[0156] It can be understood that if the terminal deletes the first service list, the authorization server instructs the terminal and the service provider to revoke the first confirmation identifier previously allocated to the first service list.

[0157] In another possible scenario, after the first service list is installed, the user may cancel the first interaction result after a period of time. The cancellation process is described below.

[0158] S411: The terminal obtains a third interaction result, where the third interaction result indicates that the user has revoked the first interaction result.

[0159] For example, the first information includes Clause 1, which is "Do you agree to process personal data in accordance with the GDPR?" The first interaction result indicates that the user agrees to Clause 1. Subsequently, the user decides to revoke the confirmation of Clause 1 (i.e., revoke the first interaction result) and performs a revocation interaction with the terminal. For example, the user can click the relevant "Revoke" button on the terminal interface to interact with the terminal.

[0160] S412: The terminal deletes the first service list based on the third interaction result.

[0161] S413: The terminal sends a third interaction result. The description of this step is similar to that of S410 and will not be repeated here.

[0162] Optionally, if the user only cancels the confirmation of some services, the third interaction result also includes a cancellation range, which is used to inform the authorization service of which services the confirmation is canceled. In this scenario, in S411, the terminal only deletes the services within the cancellation range.

[0163] In order to better illustrate the solution of the present application, four possible specific implementation solutions based on method 400 are given below.

[0164] Solution 1: This solution is based on Figure 2 In the illustrated architecture, a service list server obtains service list configuration information from one or more service providers. This service list configuration information includes service information and the aforementioned first information (see S401). Based on the obtained service list configuration information, the service list server configures a service list containing the corresponding first information and sends the service list to the terminal device. In this solution, the DVB-I client does not rely on associated applications and natively supports interaction with the user and the authorization server. For ease of description, this solution is described in detail below.

[0165] Figure 5 This is a schematic flow chart of a method 500 for installing a service list provided in an embodiment of the present application. This solution is illustrated by taking as an example a method in which a service list server obtains service list configuration information from management servers of two service providers, and the first information included in the service list configuration information is user confirmation information required for installing the service list. The method includes the following steps.

[0166] S501 , a service list server receives service list configuration information # 1 from a management server # 1 of a service provider # 1 .

[0167] The service list configuration information #1 includes a service list #1 provided by a service provider #1, information #1 requiring user confirmation, and an address #1 of the service provider #1. The service list #1 includes service information of at least one service.

[0168] For example, the service list configuration information #1 may be manually configured offline by the service provider, or may be determined through interaction between the management server #1 and the service list server.

[0169] Optionally, the service list configuration information #1 may not include the information #1 requiring user confirmation. The information #1 requiring user confirmation may be determined by the service list server based on the service list #1 in S503.

[0170] For example, the service list configuration information #1 also includes the applicable scope of information #1 that requires user confirmation. For the applicable scope, please refer to the description in S401 and will not be repeated here. The following description will take the applicable scope of information #1 that requires user confirmation as all services in service list #1 as an example.

[0171] For example, business list #1 includes business information of business #1 and business #2. Information #1 that requires user confirmation is "Clause (1): Do you agree to process personal data in accordance with the definition of GDPR?" The address of business provider #1 is URI1, and the applicable scope is all businesses in business list #1 (the businesses within the applicable scope are indicated by business ID in Table 1). Then, the structure of business list A corresponding to the business list configuration information #1 is shown in Table 1.

[0172] Table 1

[0173]

[0174] It can be understood that the service list server can synchronize the received service list configuration information #1 to the authorization server.

[0175] S502: The service list server receives service list configuration information #2 from management server #2 of service provider #2.

[0176] Optionally, the service list configuration information #2 includes a service list #2 provided by the service provider #2, information #2 requiring user confirmation, and an address #2 of the service provider #2, wherein the service list #2 includes service information of at least one service. The description of S502 is similar to that of S501 and is not repeated here.

[0177] For example, the service list configuration information #2 also includes the applicable scope of information #2 requiring user confirmation. For the applicable scope, please refer to the description in S401 and will not be repeated here. The following description will take the applicable scope of information #2 requiring user confirmation as all services in service list #2 as an example.

[0178] For example, service list #2 includes the service information of services #3 and #4. The information #2 that needs to be confirmed by the user is "Clause (1): Do you agree to process personal data in accordance with the definition of GDPR?" The address of service provider #2 is URI2, and the applicable scope is all services in service list #2. The structure of service list B corresponding to the service list configuration information #2 is shown in Table 2.

[0179] Table 2

[0180]

[0181]

[0182] It can be understood that the service list server synchronizes the received service list configuration information #2 to the authorization server.

[0183] S503: The service list server configures service list #3 based on the service list configuration information #1 and the service list configuration information #2.

[0184] Among them, business list #3 (i.e., an example of the first business list in method 400) includes business list #1 and business list #2, information #1 that requires user confirmation and information #2 that requires user confirmation, and destination address #3 for receiving the confirmation results (i.e., interaction results) of information #1 that requires user confirmation and information #2 that requires user confirmation.

[0185] It is understandable that service list #3 will be sent to the DVB-I client later, and the DVB-I client needs to feedback the user's confirmation result to the authorization server. Therefore, the destination address #3 in service list 3 is the address of the authorization server.

[0186] Taking Table 1 and Table 2 as examples, in one possible implementation method, the service list server can directly splice Table 1 and Table 2, and modify the confirmation address in Table 1 and Table 2 to the address URI3 of the authorization server (that is, the confirmation address #3 is URI3) to obtain service list #3. The structure of the service list #3 obtained after splicing is shown in Table 3.

[0187] Table 3

[0188]

[0189]

[0190] Taking Table 1 and Table 2 as examples, in another possible implementation method, the service list server can merge and splice the same information that requires user confirmation in Table 1 and Table 2, and modify the merged confirmation address to the address URI3 of the authorization server to obtain service list #3. The structure of the spliced service list #3 is shown in Table 4.

[0191] Table 4

[0192]

[0193]

[0194] S504: The DVB-I client sends a request message #1 to the service list server, where the request message #1 is used to request a service list. Correspondingly, the service list server receives the request message #1 from the DVB-I client.

[0195] Optionally, the DVB-I client requests a service list from the service list server based on a configuration. For example, the configuration may be to obtain the service list periodically, or to obtain the service list upon first power-on, or when the terminal location or language changes.

[0196] S505: The service list server sends a request response message #1 to the DVB-I client, where the request response message #1 includes the service list #3. Correspondingly, the DVB-I client receives the request response message #1 from the service list server.

[0197] S506: The DVB-I client displays the information required for user confirmation contained in service list #3 to the user.

[0198] For example, if the service list #3 obtained by the DVB-I client is shown in Table 3 or Table 4, the DVB-I client displays on the screen to the user "Do you agree that the following services process personal data in accordance with the definition of GDPR: Service #1, Service #2, Service #3, Service #4?"

[0199] S507, the DVB-I client obtains confirmation result #1 (also called interaction result #1) from the user, where confirmation result #1 is the user's confirmation result for the information requiring user confirmation (ie, information #1 requiring user confirmation and information #2 requiring user confirmation).

[0200] S508: The DVB-I client sends a confirmation message #1 to the authorization server, where the confirmation message #1 includes a confirmation result #1. Correspondingly, the authorization server receives the confirmation message #1 from the DVB-I client.

[0201] S509: The authorization server sends a confirmation response message #1 to the DVB-I client. Correspondingly, the DVB-I client receives the confirmation response message #1 from the authorization server.

[0202] Optionally, if the user agrees to information #1 requiring user confirmation, confirmation response message #1 includes confirmation identifier #1, which is used by the DVB-I client to subsequently access services from service provider #1. If the user agrees to information #2 requiring user confirmation, confirmation response message #1 includes confirmation identifier #2, which is used by the DVB-I client to subsequently access services from service provider #2.

[0203] S510 , the DVB-I client installs or does not install the service list # 3 based on the confirmation result # 1 .

[0204] For example, the service list #3 obtained by the DVB-I client is shown in Table 4. If the confirmation result #1 indicates that the user agrees to the terms (1), the DVB-I client installs the list #3. If the confirmation result #1 indicates that the user does not agree to the terms (1), the DVB-I client does not install the service list #3.

[0205] Optionally, if the user agrees to information #1 requiring user confirmation, the DVB-I client displays the service information of the services in service list #1 to the user; if the user agrees to information #2 requiring user confirmation, the DVB-I client displays the service information of the services in service list #2 to the user.

[0206] Optionally, when the DVB-I client displays the service information of the services in service list #1 to the user, it may also display information #1 requiring user confirmation; when the DVB-I client displays the service information of the services in service list #2 to the user, it may also display information #2 requiring user confirmation.

[0207] Optionally, if the user agrees to information #1 requiring user confirmation, the method further includes:

[0208] S511: The authorization server sends a notification message #1 to the management server #1 of the service provider #1, where the notification message #1 includes a confirmation identifier #1. Correspondingly, the management server #1 of the service provider #1 receives the notification message #1 from the authorization server.

[0209] Optionally, if the user agrees to information #2 requiring user confirmation, the method further includes:

[0210] S512: The authorization server sends a notification message #2 to the management server #2 of the service provider #2, where the notification message #2 includes a confirmation identifier #2. Correspondingly, the management server #2 of the service provider #2 receives the notification message #2 from the authorization server.

[0211] Based on method 500, in a possible scenario, after all services in service list #3 are installed, after a period of time, due to changes in information related to the installation of service list #3, the service list server can also provide an updated service list to the DVB-I client. Here, the scenario where the services provided by service provider #1 (i.e., the services in service list #1) are installed and the corresponding information requiring user confirmation changes is explained as an example. Figure 6 This section describes the update process.

[0212] S601: The service list server receives service list configuration information #3 from the management server #1 of the service provider #1.

[0213] Service list configuration information #3 includes service list #1 provided by service provider #1, information #3 requiring user confirmation, and address #1 of service provider #1. Information #3 requiring user confirmation is the information required for installing the service in service list #1 (i.e., information #3 requiring user confirmation is the updated information of information #1 requiring user confirmation). The rest of the description of service list configuration information #3 is similar to that of service list configuration information #1 and is not repeated here.

[0214] For example, business list #1 includes business information of business #1 and business #2, and information #3 that requires user confirmation is "Clause (1): Do you agree to process personal data in accordance with the definition of GDPR; Clause (2): Do you agree to access the business only within the EU?", and confirm that address #1 is the address URI1 of business provider #1, and the applicable scope is all businesses in business list #1 (the business within the applicable scope is indicated by the business ID in Table 3). Then, the structure of the business list C corresponding to the updated business list configuration information #3 is shown in Table 5.

[0215] Table 5

[0216]

[0217] S602: The service list server configures service list #4 based on service list configuration information #3 and service list configuration information #2.

[0218] Among them, business list #4 (i.e., an example of the second business list in method 400) includes business list #1 and business list #2, information #3 requiring user confirmation and information #2 requiring user confirmation, and confirmation address #3 for receiving the confirmation results of information #1 requiring user confirmation and information #2 requiring user confirmation, wherein business list #1 includes business information of at least one business.

[0219] Optionally, in addition to the above-mentioned method of obtaining the information #3 requiring user confirmation, the service list server may also determine the information #3 requiring user confirmation by itself.

[0220] It is understandable that service list #4 will be sent to the DVB-I client later, and the DVB-I client needs to feedback the user's confirmation result to the authorization server. Therefore, address #3 in service list 4 is the address of the authorization server.

[0221] Taking Table 5 and Table 2 as an example, the service list server can directly splice Table 2 and Table 5, and modify the confirmation address in Table 2 and Table 5 to the address URI3 of the authorization server (that is, the confirmation address #3 is URI3) to obtain service list #4. The structure of the service list #4 obtained after splicing is shown in Table 6.

[0222] Table 6

[0223]

[0224]

[0225] S603: The DVB-I client sends a request message #2 to the service list server, where the request message #2 is used to request a service list. Correspondingly, the service list server receives the request message #2 from the DVB-I client.

[0226] Optionally, the DVB-I client requests a service list from the service list server based on a configuration. For example, the configuration may be obtaining the service list based on an update period.

[0227] S604: The service list server sends a request response message #2 to the DVB-I client, where the request response message #2 includes the service list #4. Correspondingly, the DVB-I client receives the request response message #2 from the service list server.

[0228] S605: The DVB-I client displays the information required for user confirmation contained in service list #4 to the user.

[0229] For example, if the service list #4 obtained by the DVB-I client is shown in Table 6, the DVB-I client displays to the user "Do you agree that the following services process personal data in accordance with the definition of GDPR and access the services only within the EU: Service #1, Service #2; Do you agree that the following services process personal data in accordance with the definition of GDPR: Service #3, Service #4?"

[0230] S606, the DVB-I client obtains confirmation result #2 (also called interaction result #2) from the user, where confirmation result #2 is the user's confirmation result for the information requiring user confirmation (ie, information #3 requiring user confirmation and information #2 requiring user confirmation).

[0231] S607: The DVB-I client sends a confirmation message #2 to the authorization server, where the confirmation message #2 includes a confirmation result #2. Correspondingly, the authorization server receives the confirmation message #2 from the DVB-I client.

[0232] S608: The authorization server sends a confirmation response message #2 to the DVB-I client. Correspondingly, the DVB-I client receives the confirmation response message #2 from the authorization server.

[0233] Optionally, confirmation result #2 indicates that the user agrees that information #3 requiring user confirmation is applied to the services provided by service provider #1 in service list #4 (i.e., the services in service list #1), then confirmation response message #2 includes confirmation identifier #3, which is used by the DVB-I client to subsequently access the services provided by service provider #1 in service list #4 from the service provider.

[0234] S609: The DVB-I client maintains or deletes the previously installed service based on confirmation result #2.

[0235] Optionally, if confirmation result #2 indicates that the user disagrees with information #3 requiring user confirmation, the DVB-I client deletes the services in the previously installed service list #1.

[0236] Optionally, if confirmation result #2 indicates that the user agrees to information #3 requiring user confirmation, the DVB-I client displays service information for the services in service list #1 to the user. Furthermore, the updated information requiring user confirmation (i.e., information #3 requiring user confirmation) that the user has agreed to may also be displayed to the user.

[0237] Optionally, if the user agrees to information #3 requiring user confirmation, the method further includes:

[0238] S610: The authorization server sends a notification message #3 to the management server #1 of the service provider #1. The notification message #3 includes a confirmation identifier #3.

[0239] Based on method 500, in a possible scenario, after all the services in service list #3 are installed, after a period of time, the user decides to cancel the previous confirmation result #1. Figure 7 This section describes the update process.

[0240] S701 , the DVB-I client obtains interaction result #3 from the user, where interaction result #3 indicates that the user has revoked confirmation result #1.

[0241] For example, when the user decides to cancel confirmation result #1, the user clicks the relevant "Cancel" button on the screen.

[0242] S702: The DVB-I client sends a request message #3 to the authorization server, where the request message #3 includes an interaction result #3. Correspondingly, the authorization server receives the request message #3 from the DVB-I client.

[0243] Optionally, the request message #3 includes a revocation scope. For details about the revocation scope, refer to the description of S413 and will not be repeated here.

[0244] S703: The authorization server sends a request response message #3 to the DVB-I client. Correspondingly, the DVB-I client receives the request response message #3 from the authorization server.

[0245] S704: The DVB-I client deletes the service whose confirmation has been revoked based on the interaction result #3.

[0246] S705: The authorization server sends a notification message #4 to the management server #1 of the service provider #1, indicating that the user has revoked the confirmation of the service in the service list #1. In response, the management server #1 of the service provider #1 receives the notification message #4 from the authorization server.

[0247] It can be understood that when the authorization server instructs the user to revoke the confirmation of the services in the service list #1, it instructs the user to revoke the confirmation identifier previously allocated to the services in the service list #1.

[0248] S706: The authorization server sends a notification message #5 to the management server #2 of the service provider #2, indicating that the user has revoked the confirmation of the service in the service list #2. In response, the management server #2 of the service provider #2 receives the notification message #5 from the authorization server.

[0249] It can be understood that the authorization server instructing the user to revoke the confirmation of the services in the service list #2 is to instruct the user to revoke the confirmation identifier previously allocated to the services in the service list #1.

[0250] Solution 2: This solution is based on Figure 3 In the illustrated architecture, a service list server obtains service list configuration information from one or more service providers. This service list configuration information includes service information and the aforementioned first information (see S401). Based on the obtained service list configuration information, the service list server configures a service list containing the corresponding first information and sends the service list to the terminal device. In this solution, the DVB-I client does not rely on associated applications and natively supports interaction between users and service providers. This solution is described in detail below.

[0251] Figure 8This is a schematic flow chart of method 800 for installing a service list, provided in an embodiment of the present application. For ease of description, this solution uses as an example a method in which a service list server obtains service list configuration information from the management servers of two service providers, and the first information included in the service list configuration information is user confirmation information required for installing the service list. It will be appreciated that the primary difference between method 800 and method 500 is that, in method 500, the DVB-I client exchanges user confirmation results with the authorization server on the service list provider side, while in method 800, the DVB-I client exchanges user confirmation results with the service provider. The method includes the following steps.

[0252] about Figure 8 S801 to S806 shown in FIG. Figure 5 The description of S501 to S506 is not repeated here. However, it should be noted that, compared with S504, the request message #1 in S804 includes the address of service provider #1 (e.g., URI1 in S501) and the address of service provider #2 (e.g., URI2 in S502).

[0253] S807 , the DVB-I client obtains confirmation result #1 (also called interaction result #1) and confirmation result #2 (also called interaction result #2) from the user.

[0254] Confirmation result #1 is the user's confirmation result for information #1 requiring user confirmation, and confirmation result #2 is the user's confirmation result for information #2 requiring user confirmation.

[0255] S808: The DVB-I client sends a confirmation message #1 to the service provider #1, where the confirmation message #1 includes a confirmation result #1. Correspondingly, the service provider #1 receives the confirmation message #1 from the DVB-I client.

[0256] S809: Service provider #1 sends a confirmation response message #1 to the DVB-I client. Correspondingly, the DVB-I client receives the confirmation response message #1 from service provider #1.

[0257] Optionally, if the user agrees to the information #1 requiring user confirmation, the confirmation response message #1 includes a confirmation identifier #1, which is used by the DVB-I client to subsequently access services from the service provider #1.

[0258] S810: The DVB-I client sends a confirmation message #2 to the service provider #2, where the confirmation message #2 includes a confirmation result #2. In response, the service provider #2 receives the confirmation message #2 from the DVB-I client.

[0259] S811: Service provider #2 sends a confirmation response message #2 to the DVB-I client. Correspondingly, the DVB-I client receives the confirmation response message #2 from service provider #2.

[0260] Optionally, if the user agrees to the information #2 requiring user confirmation, the confirmation response message #1 includes a confirmation identifier #2, which is used by the DVB-I client to subsequently access services from the service provider #1.

[0261] S812: The DVB-I client installs or does not install service list #3 based on confirmation result #1 and confirmation result #2. Figure 5 The description of S510 in

[15] will not be repeated here.

[0262] Based on method 800, in a possible scenario, after all services in service list #3 are installed, after a period of time, due to changes in information related to the installation of service list #3, the service list server can also provide an updated service list to the DVB-I client. Here, the scenario where the services provided by service provider #1 (i.e., the services in service list #1) are installed and the corresponding information requiring user confirmation changes is explained as an example. Figure 9 This section describes the update process.

[0263] about Figure 9 S901 to S906 shown in FIG. Figure 6 The description of S601 to S605 will not be repeated here.

[0264] S906, the DVB-I client obtains confirmation result #3 (also called interaction result #3), which is the user's confirmation result for the information requiring user confirmation (ie, information #3 requiring user confirmation and information #2 requiring user confirmation).

[0265] S907: The DVB-I client sends a confirmation message #3 to the service provider #1, where the confirmation message #3 includes a confirmation result #3. Correspondingly, the service provider #1 receives the confirmation message #3 from the DVB-I client.

[0266] S908: Service provider #1 sends a confirmation response message #3 to the DVB-I client. Correspondingly, the DVB-I client receives the confirmation response message #3 from service provider #1.

[0267] Optionally, confirmation result #3 indicates that the user agrees that information #3 requiring user confirmation is applied to the services provided by service provider #1 in service list #4 (i.e., the services in service list #1), then confirmation response message #3 includes confirmation identifier #3, which is used by the DVB-I client to subsequently access the services provided by service provider #1 in service list #4 from the service provider.

[0268] S909 , the DVB-I client maintains or deletes the previously installed service based on confirmation result #3.

[0269] Optionally, if confirmation result #3 indicates that the user disagrees with information #3 requiring user confirmation, the DVB-I client deletes the services in the previously installed service list #1.

[0270] Optionally, if confirmation result #3 indicates that the user agrees to information #3 requiring user confirmation, the DVB-I client displays service information of the services in service list #1 to the user. Furthermore, the updated information requiring user confirmation (i.e., information #3 requiring user confirmation) that the user has agreed to may also be displayed to the user.

[0271] Based on method 800, in a possible scenario, after all the services in service list #3 are installed, after a period of time, the user decides to cancel the previous confirmation result #1 and / or confirmation result #2. Figure 10 The revocation process is introduced using user revocation confirmation result #1 as an example.

[0272] S1001 , the DVB-I client receives an interaction result #4 from a user, where the interaction result #4 indicates that the user has revoked the confirmation result #1.

[0273] For example, when the user decides to cancel confirmation result #1, the user clicks the relevant "Cancel" button on the screen.

[0274] S1002: The DVB-I client sends a request message #3 to the service provider #1, where the request message #3 includes the interaction result #4. Correspondingly, the authorization server receives the request message #3 from the DVB-I client.

[0275] Optionally, the request message #3 includes a revocation scope. For details about the revocation scope, refer to the description of S413 and will not be repeated here.

[0276] S1003: The authorization server sends a request response message #3 to the service provider #1. Correspondingly, the DVB-I client receives the request response message #3 from the authorization server.

[0277] S1004: The DVB-I client deletes the service whose confirmation has been revoked based on the interaction result #3.

[0278] Solution 3: This solution is based on Figure 2 In the illustrated architecture, a service list server obtains service list configuration information from one or more service providers. This service list configuration information includes service information and the aforementioned first information (see S401). Based on the obtained service list configuration information, the service list server configures a service list containing the corresponding first information and sends this service list to the terminal device. In this solution, the DVB-I client relies on an associated application to interact with the user and the authorization server. This solution is described in detail below.

[0279] Figure 11 This is a schematic flow chart of a method 1100 for installing a service list, provided in an embodiment of the present application. For ease of description, this solution uses an example in which a service list server obtains service list configuration information from management servers of two service providers, and the first information included in the service list configuration information is user confirmation information required for installing the service list. The method includes the following steps.

[0280] S1101 , the service list server receives service list configuration information #1 from management server #1 of service provider #1.

[0281] The service list configuration information #1 includes a service list #1 provided by a service provider #1, information #1 requiring user confirmation, and an address #1 of the service provider #1. The service list #1 includes service information of at least one service.

[0282] For example, the service list configuration information #1 may be manually configured offline by the service provider, or may be determined through interaction between the management server #1 and the service list server.

[0283] For example, the service list configuration information #1 also includes the applicable scope of information #1 that requires user confirmation. For the applicable scope, please refer to the description in S401 and will not be repeated here. The following description will take the applicable scope of information #1 that requires user confirmation as all services in service list #1 as an example.

[0284] For example, business list #1 includes business information of business #1 and business #2. Information #1 that requires user confirmation is "Terms: Do you agree to process personal data in accordance with the definition of GDPR?" Address #1 of business provider #1 is URI1, and the applicable scope is all businesses in business list #1 (the businesses within the applicable scope are indicated by business ID in Table 7). The structure of the business list D corresponding to the business list configuration information #1 is shown in Table 7.

[0285] Table 7

[0286]

[0287]

[0288] It can be understood that the service list server can synchronize the received service list configuration information #1 to the authorization server.

[0289] S1102: The service list server receives service list configuration information #2 from management server #2 of service provider #2.

[0290] Optionally, the service list configuration information #2 includes a service list #2 provided by the service provider #2, information #2 requiring user confirmation, and an address #2 of the service provider #2, wherein the service list #2 includes service information of at least one service. The description of S1102 is similar to that of S1101 and is not repeated here.

[0291] For example, the service list configuration information #2 also includes the applicable scope of the information #2 that requires user confirmation. In the following description, the applicable scope of the information #2 that requires user confirmation is all services in the service list #2.

[0292] For example, service list #2 includes service information of service #3 and service #4. Information #2 that requires user confirmation is "Terms: Do you agree to access the service only within the EU?", address #2 of service provider #2 is URI2, and the applicable scope is all services in service list #2 (services within the applicable scope are indicated by service ID in Table 8). The structure of service list E corresponding to service list configuration information #2 is shown in Table 8.

[0293] Table 8

[0294]

[0295] It can be understood that the service list server can synchronize the received service list configuration information #1 to the authorization server.

[0296] S1103: The service list server configures service list #3 based on service list configuration information #1 and service list configuration information #2.

[0297] The service list #3 includes the service list #1, the service list #2 and information of associated applications, and the associated applications are used for the DVB-I client to interact with the user to obtain the interaction result #1 when installing the service list.

[0298] It can be understood that interaction result #1 is used to determine whether the user agrees to install the service list.

[0299] Optionally, the associated application information includes at least one of the following: an associated application identifier, an associated application type, associated application startup conditions, and an associated application lifecycle. For example, associated applications with identifiers 50 to 100 are designated as consent / authorization applications required for installing a service list. For further details, refer to S401 and are not repeated here.

[0300] For example, service list configuration information #1 and service list configuration information #2 correspond to Table 7 and Table 8 respectively, and the information of the associated application includes the identifier of the associated application (for example, the identifier of the associated application is 60), the startup condition of the associated application (for example, when service list #3 is installed), and the life cycle of the associated application (for example, 1 week). The structure of service list #3 configured by the service list server is shown in Table 9.

[0301] Table 9

[0302]

[0303] S1104: The DVB-I client sends a request message #1 to the service list server, where the request message #1 is used to request a service list. Correspondingly, the service list server receives the request message #1 from the DVB-I client.

[0304] Optionally, the DVB-I client requests a service list from the service list server based on a configuration. For example, the configuration may be to obtain the service list periodically, obtain the service list upon first power-on, or when the terminal location or language setting of the DVB-I client changes.

[0305] S1105: The service list server sends a request response message #1 to the DVB-I client, where the request response message #1 includes the service list #3. Correspondingly, the DVB-I client receives the request response message #1 from the service list server.

[0306] S1106: The DVB-I client activates the associated application and sends an application layer message #1 to the authorization server through the associated application. The application layer message is used to request information requiring user confirmation when installing service list #3. In response, the authorization server receives application layer message #1 from the DVB-I client.

[0307] S1107: The authorization server sends an application layer response message #1 to the associated application of the DVB-I client. Application layer response message #1 includes information #1 and information #2 requiring user confirmation when installing service list #3. In response, the DVB-I client receives application layer response message #1 from the authorization server.

[0308] S1108: The DVB-I client displays information requiring user confirmation to the user.

[0309] For example, if message #1 requiring user confirmation is "Do you agree to process personal data in accordance with the GDPR definition?", and the scope of application is all services in service list #1; if message #2 requiring user confirmation is "Do you agree to process personal data in accordance with the GDPR definition?", and the scope of application is all services in service list #1, then the DVB-I client will display to the user "Do you agree to process personal data in accordance with the GDPR definition for the following services: Service #1, Service #2, Service #3, Service #4?"

[0310] S1109, the DVB-I client receives confirmation result #1 (also called interaction result #1) from the user, where confirmation result #1 is the user's confirmation result for the information requiring user confirmation (ie, information #1 requiring user confirmation and information #2 requiring user confirmation).

[0311] S1110: The DVB-I client sends an application layer message #2 to the authorization server via the associated application. The application layer message #2 includes the confirmation result #1. Correspondingly, the authorization server receives the application layer message #2 from the DVB-I client.

[0312] S1111: The authorization server sends an application layer response message #2 to the associated application of the DVB-I client. Correspondingly, the DVB-I client receives the application layer response message #2 from the authorization server.

[0313] Optionally, if the user agrees to information #1 requiring user confirmation, confirmation response message #2 includes confirmation identifier #1, which is used by the DVB-I client to subsequently access services from service provider #1. If the user agrees to information #2 requiring user confirmation, confirmation response message #1 includes confirmation identifier #2, which is used by the DVB-I client to subsequently access services from service provider #2.

[0314] S1112 , the DVB-I client installs or does not install service list # 3 based on confirmation result # 1 .

[0315] If confirmation result #1 indicates that the user agrees that information #1 requiring user confirmation is applied to services #1 and #2, and agrees that information # requiring user confirmation is applied to services #3 and #4, the DVB-I client installs service list #3; if confirmation result #1 indicates that the user agrees that information #1 requiring user confirmation is applied to services #1 and #2 in service list #1, and the user does not agree that information #2 requiring user confirmation is applied to services #3 and #4, the DVB-I client only installs services #1 and #2 in list #3; if confirmation result #1 indicates that the user does not agree that information #1 requiring user confirmation is applied to services #1 and #2 in service list #1, and the user agrees that information #2 requiring user confirmation is applied to services #3 and #4, the DVB-I client only installs services #3 and #4 in list #3.

[0316] Optionally, if the user agrees to information #1 requiring user confirmation, the DVB-I client displays the service information of the services in service list #1 to the user; if the user agrees to information #2 requiring user confirmation, the DVB-I client displays the service information of the services in service list #2 to the user.

[0317] Optionally, when the DVB-I client displays the service information of the services in service list #1 to the user, it may also display information #1 requiring user confirmation; when the DVB-I client displays the service information of the services in service list #2 to the user, it may also display information #2 requiring user confirmation.

[0318] Optionally, if the user agrees to information #1 requiring user confirmation, the method further includes:

[0319] S1113: The authorization server sends a notification message #1 to the management server #1 of the service provider #1, where the notification message #1 includes a confirmation identifier #1. Correspondingly, the management server #1 of the service provider #1 receives the notification message #1 from the authorization server.

[0320] Optionally, if the user agrees to information #2 requiring user confirmation, the method further includes:

[0321] S1114: The authorization server sends a notification message #2 to the management server #2 of the service provider #2, where the notification message #2 includes a confirmation identifier #2. Correspondingly, the management server #2 of the service provider #2 receives the notification message #2 from the authorization server.

[0322] Based on method 1100, in a possible scenario, after all services in service list #3 are installed, after a period of time, due to changes in information related to the installation of service list #3, the authorization server can directly provide the DVB-I client with updated information related to the installation of service list #3. This is explained by taking the scenario where the services provided by service provider #1 (i.e., the services in service list #1) are installed and the corresponding information requiring user confirmation changes as an example. Figure 12 This section describes the update process.

[0323] S1201: The authorization server sends application layer message #3 to the associated application of the DVB-I client. Application layer message #3 includes information #3 requiring user confirmation. Information #3 requiring user confirmation is information requiring user confirmation to update the installed services provided by service provider #1 in service list #3. In response, application #1 associated with the DVB-I client receives application layer message #3 from the authorization server.

[0324] For example, before the update, the information #1 that requires user confirmation is "Clause (1): Do you agree to process personal data in accordance with the definition of GDPR?", and the scope of application is all businesses in business list #1; after the update, the information #3 that requires user confirmation is "Clause (1): Do you agree to process personal data in accordance with the definition of GDPR?; Clause (2) Do you agree to access the business only within the EU?", and the scope of application is all businesses in business list #1.

[0325] Optionally, the information #3 requiring user confirmation can be sent by the service provider #1 to the service list server, which then synchronizes the information #3 requiring user confirmation to the authorization server. For a description of the information provided by the service provider #1, please refer to the description in S601 and will not be repeated here.

[0326] Optionally, the service list server may determine the information #3 that requires user confirmation by itself, and then synchronize it to the authorization server.

[0327] S1202: The associated application of the DVB-I client sends an application layer response message #3 to the authorization server. Correspondingly, the authorization server receives the application layer response message #3 from the associated application of the DVB-I client.

[0328] S1203: The DVB-I client displays information #3 requiring user confirmation to the user.

[0329] Based on the example in S1201 , the DVB-I client displays to the user “Do you agree that the following services process personal data in accordance with the definition of GDPR and agree to access the services only within the EU: Service #1, Service #2?”.

[0330] S1204: The DVB-I client obtains confirmation result #2 (also referred to as interaction result #2) from the user. Confirmation result #2 is the user's confirmation result for information #3 requiring user confirmation.

[0331] S1205: The associated application of the DVB-I client sends an application layer message #4 to the authorization server, where the application layer message #4 includes confirmation result #2. Correspondingly, the authorization server receives the application layer message #4 of the associated application #1 from the DVB-I client.

[0332] S1206: The authorization server sends an application layer response message #4 to the associated application of the DVB-I client. Correspondingly, the associated application #1 of the DVB-I client receives the application layer response message #4 from the authorization server.

[0333] Optionally, if confirmation result #2 indicates that the user agrees to information #3 requiring user confirmation, the confirmation response message #2 includes confirmation identifier #3, which is used by the DVB-I client to subsequently access the services provided by service provider #1 in service list #3 from the service provider.

[0334] S1207: The DVB-I client maintains or deletes the previously installed service based on confirmation result #2.

[0335] Optionally, if the user agrees to information #3 requiring user confirmation, the method further includes:

[0336] S1208: The authorization server sends a notification message #3 to the management server #1 of the service provider #1. The notification message #3 includes a confirmation identifier #3.

[0337] Based on method 1100, in a possible scenario, after all the services in service list #3 are installed, after a period of time, the user decides to cancel the previous confirmation result #1. Figure 13 This section describes the update process.

[0338] S1301: The DVB-I client obtains interaction result #3 from the user, where interaction result #3 indicates that the user has revoked confirmation result #1.

[0339] S1302: The associated application of the DVB-I client sends an application layer message #5 to the authorization server, where the application layer message #5 includes the interaction result #3. Correspondingly, the authorization server receives the application layer message #5 from the associated application of the DVB-I client.

[0340] Optionally, the application layer message #5 includes the applicable scope of the revocation instruction. The applicable scope of the revocation instruction is similar to the indication of the applicable scope of the information requiring user confirmation in S401, and will not be described in detail here.

[0341] S1303: The authorization server sends an application layer response message #5 to the associated application of the DVB-I client. Correspondingly, the associated application #1 of the DVB-I client receives the application layer response message #5 from the authorization server.

[0342] S1304: The DVB-I client deletes the service whose confirmation has been revoked based on the interaction result #3.

[0343] S1305: The authorization server sends a notification message #4 to the management server #1 of the service provider #1, indicating that the user has revoked the confirmation of the service in the service list #1. In response, the management server #1 of the service provider #1 receives the notification message #4 from the authorization server.

[0344] It can be understood that when the authorization server instructs the user to revoke the confirmation of the services in the service list #1, it instructs the user to revoke the confirmation identifier previously allocated to the services in the service list #1.

[0345] S1306: The authorization server sends a notification message #5 to the management server #2 of the service provider #2, indicating that the user has revoked the confirmation of the service in the service list #2. In response, the management server #2 of the service provider #2 receives the notification message #5 from the authorization server.

[0346] It can be understood that the authorization server instructing the user to revoke the confirmation of the services in the service list #2 is to instruct the user to revoke the confirmation identifier previously allocated to the services in the service list #1.

[0347] Option 4: This option is based on Figure 3 In the illustrated architecture, a service list server obtains service list configuration information from one or more service providers. This service list configuration information includes service information and the aforementioned first information (see S401). Based on the obtained service list configuration information, the service list server configures a service list containing the corresponding first information and sends this service list to the terminal device. In this solution, the DVB-I client relies on associated applications to interact with users and service providers. This solution is described in detail below.

[0348] Figure 14This is a schematic flow chart of a method 1400 for installing a service list, provided in an embodiment of the present application. For ease of description, this solution uses an example in which a service list server obtains service list configuration information from management servers of two service providers, and the first information included in the service list configuration information is user confirmation information required for installing the service list. The method includes the following steps.

[0349] S1401: The service list server receives service list configuration information #1 from management server #1 of service provider #1.

[0350] The service list configuration information #1 includes a service list #1 provided by a service provider #1 and information about an associated application #1, wherein the service list #1 includes service information of at least one service.

[0351] Optionally, the information about associated application #1 includes at least one of the following: an identifier of associated application #1, a type of associated application #1, a startup condition for associated application #1, and a lifespan of associated application #1. For example, if the associated application #1 type of associated application #1 with identifiers 50 to 100 is a consent / authorization application required for installing a service list, then an application from the applications with identifiers 50 to 100 can be selected as associated application #1. For further details, refer to the description in S401 and are not repeated here.

[0352] For example, the service list configuration information #1 may be manually configured offline by the service provider, or may be determined through interaction between the management server #1 and the service list server.

[0353] For example, business list #1 includes business information of business #1 and business #2, and the information of associated application #1 includes the identifier of associated application #1 (for example, the identifier of associated application #1 is 60), the startup condition of associated application #1 (for example, when business list #1 is installed), and the life cycle of associated application #1 (for example, 1 week). The structure of the business list F corresponding to the business list configuration information #1 is shown in Table 10.

[0354] Table 10

[0355]

[0356] S1402: The service list server receives service list configuration information #2 from management server #2 of service provider #2.

[0357] Optionally, the service list configuration information #2 includes a service list #2 provided by a service provider #2 and information about an associated application #2, wherein the service list #2 includes service information of at least one service.

[0358] Optionally, the information of associated application #2 includes at least one of the following: an identifier of associated application #2, a type of associated application #2, a start condition of associated application #2, and a life cycle of associated application #2. The rest of the description in S1402 is similar to that in S1401 and will not be repeated here.

[0359] For example, service list #2 includes service information of service #3 and service #4, and the information of associated application #2 includes the identifier of associated application #2 (for example, the identifier of associated application #2 is 80), the startup condition of associated application #2 (for example, when service list #2 is installed), and the life cycle of associated application #2 (for example, 1 week). The structure of the service list G corresponding to the service list configuration information #2 is shown in Table 11.

[0360] Table 11

[0361]

[0362]

[0363] S1403: The service list server configures service list #3 based on the service list configuration information #1 and the service list configuration information #2.

[0364] The service list #3 includes the service list #1, the service list #2, the information of the associated application #1, and the information of the associated application #2.

[0365] Taking Table 10 and Table 11 as examples, in a possible implementation, the service list server may directly concatenate Table 10 and Table 11 to obtain service list #3. The structure of the concatenated service list #3 is shown in Table 12.

[0366] Table 12

[0367]

[0368]

[0369] S1404: The DVB-I client sends a request message #1 to the service list server, where the request message #1 is used to request a service list. Correspondingly, the service list server receives the request message #1 from the DVB-I client.

[0370] Optionally, the DVB-I client requests a service list from the service list server based on a configuration. For example, the configuration may be to obtain the service list periodically, or to obtain the service list upon first power-up.

[0371] S1405: The service list server sends a request response message #1 to the DVB-I client, where the request response message #1 includes the service list #3. Correspondingly, the DVB-I client receives the request response message #1 from the service list server.

[0372] S1406: The DVB-I client activates associated application #1 and sends application layer message #1 to service provider #1 via associated application #1. Application layer message #1 requests information requiring user confirmation for installing service list #1. In response, service provider #1 receives application layer message #1 from the DVB-I client regarding associated application #1.

[0373] S1407: Service provider #1 sends application layer response message #1 to associated application #1 of the DVB-I client. Application layer response message #1 includes information #1 requiring user confirmation when installing service list #1. In response, associated application #1 of the DVB-I client receives application layer response message #1 from the authorization server.

[0374] Optionally, the application layer response message #1 also includes the applicable scope of the information #1 that requires user confirmation.

[0375] S1408: The DVB-I client activates associated application #2 and sends application layer message #2 to service provider #2 via associated application #2. Application layer message #2 requests information requiring user confirmation for installing service list #2. In response, service provider #2 receives application layer message #2 from the DVB-I client regarding associated application #2.

[0376] At step S1409, service provider #2 sends application layer response message #2 to associated application #2 of the DVB-I client. Application layer response message #2 includes information #2 requiring user confirmation when installing service list #2. In response, associated application #2 of the DVB-I client receives application layer response message #2 from the authorization server.

[0377] Optionally, the application layer response message #2 also includes the applicable scope of the corresponding information #2 requiring user confirmation.

[0378] S1410: The DVB-I client displays information requiring user confirmation to the user.

[0379] S1411, the DVB-I client obtains confirmation result #1 (also called interaction result #1) and confirmation result #2 (also called interaction result #2), where confirmation result #1 is the user's confirmation result for information #1 requiring user confirmation, and confirmation result #2 is the user's confirmation result for information #2 requiring user confirmation.

[0380] S1412: The associated application #1 of the DVB-I client sends an application layer message #3 to the service provider #1. The application layer message #3 includes the confirmation result #1. In response, the service provider #1 receives the application layer message #3 from the DVB-I client.

[0381] S1413: The authorization server sends an application layer response message #3 to the associated application #1 of the DVB-I client. Correspondingly, the DVB-I client receives the application layer response message #3 from the authorization server.

[0382] S1414: The associated application #2 of the DVB-I client sends an application layer message #4 to the service provider #2. The application layer message #4 includes the confirmation result #2. In response, the service provider #2 receives the application layer message #4 from the DVB-I client.

[0383] S1415: The authorization server sends an application layer response message #4 to the associated application #2 of the DVB-I client. Correspondingly, the DVB-I client receives the application layer response message #4 from the authorization server.

[0384] S1416: The DVB-I client installs service list #3 based on confirmation result #1 and confirmation result #2.

[0385] Based on method 1400, in a possible scenario, after all services in service list #3 are installed, after a period of time, due to changes in information related to the installation of service list #3, the service provider can directly provide the DVB-I client with updated information related to the installation of service list #3. This is explained by taking the scenario where the services provided by service provider #1 (i.e., the services in service list #1) are installed and the corresponding information requiring user confirmation changes as an example. Figure 15 This section describes the update process.

[0386] At step S1501, service provider #1 sends application layer message #5 to application #1 associated with a DVB-I client. Application layer message #5 includes information #3 requiring user confirmation. Information #3 requiring user confirmation is information regarding updates to installed services provided by service provider #1 in service list #3, requiring user confirmation. In response, application #1 associated with the DVB-I client receives application layer message #5 from service provider #1.

[0387] S1502: The associated application #1 of the DVB-I client sends an application layer response message #5 to the service provider #1. In response, the service provider #1 receives the application layer response message #5 from the associated application #1 of the DVB-I client.

[0388] S1503: The DVB-I client displays information #3 requiring user confirmation to the user.

[0389] S1504: The DVB-I client obtains confirmation result #3 (also referred to as interaction result #3), where confirmation result #3 is the user's confirmation result for information #3 requiring user confirmation.

[0390] S1505: Associated application #1 of the DVB-I client sends application layer message #6 to service provider #1. Application layer message #6 includes confirmation result #3. In response, service provider #1 receives application layer message #6 from associated application #1 of the DVB-I client.

[0391] S1506: Service provider #1 sends an application layer response message #6 to application #1 associated with the DVB-I client. Correspondingly, application #1 associated with the DVB-I client receives application layer response message #6 from service provider #1.

[0392] S1507: The DVB-I client maintains or deletes the previously installed service based on confirmation result #3.

[0393] Based on method 1400, in a possible scenario, after all the services in service list #3 are installed, after a period of time, the user decides to cancel the previous confirmation result #1. Figure 16 This section describes the update process.

[0394] S1601: The DVB-I client obtains interaction result #3 from the user, where interaction result #3 indicates that the user has revoked confirmation result #1.

[0395] S1602: The DVB-I client sends application layer message #7 to service provider #1 via associated application #1. Application layer message #7 includes interaction result #3. In response, service provider #1 receives application layer message #7 of associated application #1 from the DVB-I client.

[0396] Optionally, application layer message #7 includes a revocation scope.

[0397] S1603: Service provider #1 sends an application layer response message #7 to application #1 associated with the DVB-I client. Correspondingly, application #1 associated with the DVB-I client receives application layer response message #7 from service provider #1.

[0398] Optional,

[0399] S1604: The DVB-I client deletes the service whose confirmation has been revoked based on the interaction result #3.

[0400] It can be understood that the solutions in the various embodiments of the present application can be reasonably combined and used, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained with each other in the various embodiments, without limitation to this.

[0401] It can also be understood that the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of this application.

[0402] It can also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0403] It is also understood that in some of the above embodiments, devices in existing network architectures are mainly used as examples for illustrative purposes, and it should be understood that the embodiments of the present application do not limit the specific form of the devices. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0404] It can also be understood that in the above-mentioned various method embodiments, the methods and operations implemented by the device may also be implemented by components of the device (such as chips or circuits).

[0405] Above, combined Figures 1 to 16 The method provided by the embodiment of the present application is described in detail. The above method is mainly introduced from the perspective of interaction between devices. It is understandable that in order to implement the above functions, each device includes a hardware structure and / or software module corresponding to the execution of each function.

[0406] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0407] The following, combined Figure 17 and Figure 18The communication device provided by the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the content that is not described in detail, please refer to the method embodiment above. For the sake of brevity, some content will not be repeated. The embodiment of the present application can divide the functional modules of each device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0408] The communication method provided by this application has been described in detail above. The following describes the communication device provided by this application. In one possible implementation, the device is used to implement the steps or processes corresponding to the DVB-I client in the above method embodiment. In another possible implementation, the device is used to implement the steps or processes corresponding to the service list server in the above method embodiment. In yet another possible implementation, the device is used to implement the steps or processes corresponding to the authorization server in the above method embodiment.

[0409] Figure 17 2 is a schematic block diagram of a communication device 200 provided in an embodiment of the present application. Figure 17 As shown, the apparatus 200 may include a communication unit 210 and a processing unit 220. The communication unit 210 may communicate with the outside, and the processing unit 220 may be used for data processing. The communication unit 210 may also be referred to as a communication interface or a transceiver unit.

[0410] In one possible design, the device 200 can implement steps or processes corresponding to those executed by the service list server in the above method embodiment, wherein the processing unit 220 is used to execute processing-related operations of the service list server in the above method embodiment, and the communication unit 210 is used to execute sending-related operations of the service list server in the above method embodiment.

[0411] In another possible design, the device 200 may implement steps or processes corresponding to those performed by the DVB-I client in the above method embodiment, wherein the communication unit 210 is used to perform reception-related operations of the DVB-I client in the above method embodiment, and the processing unit 220 is used to perform processing-related operations of the DVB-I client in the above method embodiment.

[0412] In another possible design, the device 200 may implement steps or processes corresponding to those performed by the authorization server in the above method embodiment, wherein the communication unit 210 is used to perform reception-related operations of the authorization server in the above method embodiment, and the processing unit 220 is used to perform processing-related operations of the authorization server in the above method embodiment.

[0413] It should be understood that the apparatus 200 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, a combined logic circuit, and / or other suitable components that support the described functions. In an optional example, those skilled in the art will appreciate that the apparatus 200 may be specifically a service list server in the above-described embodiment, and may be used to execute the various processes and / or steps corresponding to the service list server in the above-described method embodiment; or, the apparatus 200 may be specifically a DVB-I client in the above-described embodiment, and may be used to execute the various processes and / or steps corresponding to the DVB-I client in the above-described method embodiment; or, the apparatus 200 may be specifically an authorization server in the above-described embodiment, and may be used to execute the various processes and / or steps corresponding to the authorization server in the above-described method embodiment. To avoid repetition, further description will be omitted here.

[0414] The apparatus 200 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the service list server in the above-mentioned method, or the apparatus 200 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the DVB-I client in the above-mentioned method, or the apparatus 200 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the authorization server in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software implementation can be executed by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the communication unit can be replaced by a transceiver (for example, the sending unit in the communication unit can be replaced by a transmitter, and the receiving unit in the communication unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, respectively performing the sending and receiving operations and related processing operations in each method embodiment.

[0415] In addition, the communication unit may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit. Figure 17The device in the embodiment can be a service list server, DVB-I client, or authorization server in the aforementioned embodiments, or a chip or chip system, such as a system on a chip (SoC). The communication unit can be an input / output circuit or a communication interface, and the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0416] Figure 18 This is a schematic block diagram of a communication device 300 provided in an embodiment of the present application. The device 300 includes a processor 310 and a transceiver 320. The processor 310 and the transceiver 320 communicate with each other via an internal connection path, and the processor 310 is used to execute instructions to control the transceiver 320 to send and / or receive signals.

[0417] Optionally, the apparatus 300 may further include a memory 330, which communicates with the processor 310 and the transceiver 320 via an internal connection path. The memory 330 is used to store instructions, and the processor 310 can execute the instructions stored in the memory 330. In one possible implementation, the apparatus 300 is used to implement the various processes and steps corresponding to the service list server in the above-mentioned method embodiment. In another possible implementation, the apparatus 300 is used to implement the various processes and steps corresponding to the DVB-I client in the above-mentioned method embodiment. In yet another possible implementation, the apparatus 300 is used to implement the various processes and steps corresponding to the authorization server in the above-mentioned method embodiment.

[0418] It should be understood that the apparatus 300 can be specifically the service list server, DVB-I client, or authorization server in the above-mentioned embodiments, or it can be a chip or chip system. Correspondingly, the transceiver 320 can be the transceiver circuit of the chip, which is not limited here. Specifically, the apparatus 300 can be used to execute the various steps and / or processes corresponding to the service list server, DVB-I client, or authorization server in the above-mentioned method embodiments. Optionally, the memory 330 can include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory can also include non-volatile random access memory. For example, the memory can also store device type information. The processor 310 can be used to execute instructions stored in the memory. When the processor 310 executes the instructions stored in the memory, the processor 310 is used to execute the various steps and / or processes corresponding to the above-mentioned method embodiments corresponding to the service list server, DVB-I client, or authorization server.

[0419] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0420] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, digital signal processing (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The processor in the embodiments of the present application can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0421] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0422] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0423] In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the operations and / or processes performed by the service list server or DVB-I client or authorization server in each method embodiment of the present application are executed.

[0424] The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are executed on a computer, the operations and / or processes performed by the service list server, DVB-I client, or authorization server in each method embodiment of the present application are executed.

[0425] In addition, the present application further provides a chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is configured to execute the computer program stored in the memory to execute the operations and / or processing performed by the service list server, the DVB-I client, or the authorization server in any one of the method embodiments.

[0426] Furthermore, the chip may further include a communication interface. The communication interface may be an input / output interface, or an interface circuit, etc. Furthermore, the chip may further include a memory.

[0427] In addition, the present application also provides a communication system, including the service list server, authorization server and DVB-I client in the embodiment of the present application.

[0428] It should also be noted that the memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0429] Those skilled in the art will appreciate that the various exemplary units and algorithmic steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented using hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for ease of description and brevity, the specific operating processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical functional division. In actual implementation, other divisions may be used, such as multiple units or components being combined or integrated into another system, or some features being omitted or not implemented. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interface, or indirect coupling or communication connection between devices or units, which may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0430] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0431] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0432] It should also be understood that the ordinal numbers "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to define the size, content, order, timing, priority, or importance of the multiple objects. For example, the first information and the second information do not indicate differences in information size, content, priority, or importance.

[0433] It should also be understood that in this application, "when", "if" and "if" all mean that the network element will make corresponding processing under certain objective circumstances, which is not a time limit, and does not require the network element to make judgment actions when implementing it, nor does it mean that there are other limitations.

[0434] It should also be understood that, in this application, "at least one" means one or more, and "plurality" means two or more. "At least one item" or similar expressions refers to one or more items, that is, any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a, b, and c.

[0435] It should also be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, including A and B, and B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects are in an "or" relationship. For example, "A / B" means: A or B.

[0436] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, and B can also be determined based on A and / or other information.

Claims

1. A method for installing a service list, characterized in that: include: Obtaining a service list, wherein the service list includes first information, and the first information is used to obtain a first interaction result from the user when installing the service list; Acquire the first interaction result according to the first information; The service list is installed or not installed according to the first interaction result.

2. The method according to claim 1, characterized in that The first information includes information or a first address that requires user confirmation when installing the service list, the first address being an access entry address for the information that requires user confirmation when installing the service list, and the first interaction result including the user's confirmation result of the information that requires user confirmation. or, The first information is used to request the user to provide authentication information required when installing the service list, and the first interaction result includes the authentication information provided by the user.

3. The method according to claim 2, characterized in that The first service list further includes second information, where the second information is used to send an interaction result with the user. The method further includes: The first interaction result is sent according to the second information.

4. The method according to claim 3, characterized in that The second information includes a second address, which is a destination address for sending the first interaction result.

5. The method according to claim 3 or 4, characterized in that After installing the service list according to the first interaction result, the method further includes: Acquire a second interaction result from the user, where the second interaction result indicates that the user updates or cancels the first interaction result; sending the second interaction result according to the second information; The service list is maintained or deleted according to the second interaction result.

6. The method according to claim 1, characterized in that The first information indicates a first associated application.

7. The method according to claim 6, characterized in that The first information includes information of the first associated application, and the information of the first associated application includes at least one of the following: an identifier of the first associated application, a type of the first associated application, a start condition of the first associated application, and a life span of the first associated application.

8. The method according to claim 6 or 7, characterized in that The method further comprises: The interaction result with the user is sent through the first associated application.

9. The method according to any one of claims 6 to 8, characterized in that The method further comprises: obtaining, through the first associated application, information requiring user confirmation when installing the service list, wherein the first interaction result includes a confirmation result of the user for the information requiring user confirmation; or, Request information is obtained through the first associated application, where the request information is used to request the user to provide authentication information required for installing the service list, and the first interaction result includes the authentication information provided by the user.

10. The method according to any one of claims 6 to 9, characterized in that After installing the service list according to the first interaction result, the method further includes: obtaining a second interaction result from the user through the first associated application or the second associated application, wherein the second interaction result instructs the user to update or cancel the first interaction result, wherein the second associated application is used to implement interaction with the user after the service list is installed; Sending the second interaction result through the first associated application or the second associated application; The service list is maintained or deleted according to the second interaction result.

11. The method according to claim 10, characterized in that The first information also includes information of the second associated application, and the information of the second associated application includes at least one of the following: an identifier of the second associated application, a type of the second associated application, a start condition of the second associated application, and a life span of the second associated application.

12. The method according to any one of claims 2 to 5 and 9, characterized in that The installing or not installing the service list according to the first interaction result includes: If the first interaction result indicates that the user agrees with the information requiring user confirmation, then the service list is installed; or, Authentication confirmation information is received, where the authentication confirmation information indicates that the authentication information provided by the user has passed authentication, and the service list is installed.

13. The method according to any one of claims 2 to 5, 9 and 12, characterized in that The information that needs to be confirmed by the user when installing the service list includes at least one of the agreements, terms, and conditions that the user needs to agree to when accessing the services in the service list.

14. The method according to any one of claims 1 to 13, characterized in that The service list also includes service information of at least one service.

15. A method for installing a service list, characterized in that: include: Configuring a service list, the service list including first information, the first information being used to obtain a first interaction result from a user when installing the service list, the first interaction result being used to determine whether the terminal should install the service list; Sending the service list to the terminal.

16. The method according to claim 15, characterized in that The first information includes information or a first address that requires user confirmation when installing the service list, the first address being an access entry address for the information that requires user confirmation when installing the service list, and the first interaction result including the user's confirmation result of the information that requires user confirmation. or, The first information is used to request the user to provide authentication information required when installing the service list, and the first interaction result includes the authentication information provided by the user.

17. The method according to claim 16, characterized in that The first service list further includes second information, where the second information is used to send an interaction result with the user. The method further includes: The first interaction result is sent according to the second information.

18. The method according to claim 17, characterized in that The second information includes a second address, which is a destination address for sending the first interaction result.

19. The method according to claim 15, characterized in that The first information indicates a first associated application.

20. The method according to claim 19, characterized in that The first information includes information of the first associated application, and the information of the first associated application includes at least one of the following: an identifier of the first associated application, a type of the first associated application, a start condition of the first associated application, and a life span of the first associated application.

21. The method according to any one of claims 15 to 20, characterized in that The service list includes service information of at least one service.

22. The method according to claim 21, characterized in that The method further comprises: receiving first service list configuration information from a service provider, where the first service list configuration information includes the service information and the first information; or, receiving second service list configuration information from a service provider, wherein the second service list configuration information includes the service information; The first information is determined according to the business information.

23. The method according to any one of claims 15 to 22, characterized in that The first information is further used to indicate a second associated application, and the second associated application is used to implement interaction with the user after the service list is installed.

24. The method according to claim 23, wherein The first information also includes information of the second associated application, and the information of the second associated application includes at least one of the following: an identifier of the second associated application, a type of the second associated application, a start condition of the second associated application, and a life span of the second associated application.

25. A method for installing a service list, characterized in that: include: receiving a first interaction result from a terminal, where the first interaction result is an interaction result between the terminal and a user, and the first interaction result is used to determine whether the terminal has installed the service list; A first message is sent to the terminal, where the first message is used to confirm that the first interaction result has been received.

26. The method according to claim 25, characterized in that The receiving a first confirmation message from the terminal includes: The first interaction result of the first associated application is received from the terminal.

27. The method according to claim 25 or 26, characterized in that The first interaction result includes a confirmation result of the user on the information requiring user confirmation.

28. The method according to claim 27, characterized in that The information that needs to be confirmed by the user when installing the service list includes at least one of the agreements, terms, and conditions that the user needs to agree to when accessing the services in the service list.

29. The method according to claim 25 or 26, characterized in that If the first interaction result includes authentication information provided by the user, the first message includes authentication confirmation information, and the authentication confirmation information indicates whether the authentication information provided by the user has passed or failed authentication.

30. The method according to any one of claims 25 to 29, characterized in that The first interaction result is used to determine that the terminal can install the service list, and the method further includes: A second interaction result is received from the terminal, where the second interaction result instructs the user to update or cancel the first interaction result.

31. The method according to claim 30, wherein The receiving a second interaction result from the terminal includes: The second interaction result of a second associated application from the terminal is received, where the second associated application is used to implement interaction with a user after the service list is installed.

32. A communication device, characterized in that: The apparatus comprises: a module or a unit for executing the method according to any one of claims 1 to 31.

33. A communication device, characterized in that: include: at least one processor; The at least one processor is configured to execute a computer program or instruction stored in the memory, so that the method according to any one of claims 1 to 31 is performed.

34. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 31 is performed.

35. A computer program product comprising a computer program or instructions, characterized in that When the computer is run, the method according to any one of claims 1 to 31 is executed.

Images