A development method and system of application facing TVOS system and supporting multi-service interface

Abstract

The application discloses a kind of application development method and system facing TVOS system and supporting the development of multiple service interfaces, by obtaining application demand and carrying out demand analysis, according to reference GB / T 9385-2008 "computer software requirement specification description specification" and GB / T32279-2019 "intelligent mobile terminal application software (APP) technical requirements" to application demand classification obtains service interaction demand and user interaction demand;The service interaction demand and user interaction demand obtained in step S1 are decoupled to obtain functional component module and general function module;General function module obtained in step S2 is implemented using application front-end application source code and application interaction interface file with application back-end, functional component module obtained in step S2 is implemented using application front-end HTML5 page, application library file, and the functional component module and general function module realize data interaction through HTML5 page calling interface, the advantages of native application and H5 application are considered, and a variety of applications can be provided on the TVOS terminal with limited memory performance.

Description

Technical Field

[0001] This invention belongs to the field of application development technology, specifically referring to a development method and system for applications targeting the TVOS system and supporting multiple service interfaces. Background Technology

[0002] For smart terminals with the Android operating system, applications are generally divided into web applications and APK applications. APK applications are also known as native applications. Web applications are more flexible but have limited functionality compared to APK applications, while APK applications have more open functionality but are less flexible compared to web applications.

[0003] Most smart digital TV terminals on the market currently use APK applications. However, these smart digital TV terminals generally have low hardware performance parameters such as CPU, GPU, and memory. As the demand for applications increases, the low memory performance of smart digital TV terminals greatly limits the number of applications that can be installed and the individuality and diversity of application services. On the other hand, directly using web applications results in poor user experience and poor ability to access the underlying operating system and terminal hardware. Summary of the Invention

[0004] To overcome the shortcomings and problems of existing technologies, this invention provides a development method and system for applications oriented towards TVOS systems and supporting multiple service interfaces.

[0005] A development method for an APK supporting multiple service interfaces for a TVOS system includes the following steps:

[0006] Step S1: Obtain application requirements and conduct requirements analysis. According to GB / T 9385-2008 "Computer Software Requirements Specification" and GB / T32279-2019 "Technical Requirements for Smart Mobile Terminal Application Software (APP)," the application requirements are classified to obtain business interaction requirements and user interaction requirements.

[0007] Step S2: Decouple the business interaction requirements and user interaction requirements obtained in Step S1 to obtain functional component modules and regular functional modules.

[0008] Step S3: Implement the conventional functional modules obtained in Step S2 using the application source code and application interaction interface files of the application front-end in conjunction with the application back-end. Implement the functional component modules obtained in Step S2 using the HTML5 pages and application library files of the application front-end. The functional component modules and conventional functional modules achieve data interaction through calling interfaces on the HTML5 pages.

[0009] Furthermore, in steps S2 and S3, the application frontend encapsulates an HTML5 page containing an interactive interface and user interaction operations. When the application frontend does not need to call the TVOS terminal hardware for user interaction, it sends a request to the business page system of the application backend to realize the information interaction business between the application frontend and the application backend. When the application frontend needs to call the TVOS terminal hardware for business interaction, it uses the HTML5 page containing the interactive interface and user interaction operations encapsulated in the application frontend to make an operation request to the TVOS terminal through the hardware call interface provided by the application library file. The TVOS terminal calls system hardware resources according to the operation request and implements the corresponding business service according to the interactive operations defined in the HTML5 page and the business page system of the application backend.

[0010] Furthermore, in step S1, the user interaction requirements include user interaction interface requirements and user interaction operation requirements; the business interaction requirements include business interaction process requirements, business interaction data linkage requirements, and business interaction hardware call requirements.

[0011] Furthermore, in step S2, the business interaction requirements and user interaction requirements are coupled and analyzed to obtain indirect coupling, data coupling, tag coupling, control coupling, external coupling, functional coupling, and content coupling; the indirect coupling and data coupling are decoupled to obtain functional component modules, and the tag coupling, control coupling, external coupling, functional coupling, and content coupling are decoupled to obtain conventional functional modules.

[0012] Furthermore, the application front-end source code includes a front controller and an application interaction view; the front controller includes the application front-end HTML5 initial page and the application back-end request interface method; the application interaction view includes the application business page layout template and the application business page template interface image;

[0013] The application library files for the application front-end include library files and HTML5 application call interfaces;

[0014] The application backend includes an application function scheduling module, a business page system, and an application database.

[0015] The TVOS terminal includes the TVOS operating system, the TVOS hardware abstraction layer, JNI, and TVOS hardware; the JNI is the TVOS hardware native Java interface.

[0016] The application front-end operates on the TVOS terminal.

[0017] Furthermore, the application frontend initiates a request to the business page system of the application backend through the initial HTML5 page and access parameters. The application backend provides any page address in the business page system that matches the access parameters of the application frontend based on the access request. This transforms the personalized customization of the application frontend into the customized development of the business page system in the application backend, enabling the same frontend application to be used in multiple scenarios.

[0018] Furthermore, when the application front-end does not need to call the TVOS terminal hardware for user interaction, the user initiates a business request to the function scheduling module of the application back-end through the front-end controller. The function scheduling module of the application back-end calls the business entry URL address specified by the business page system according to the business request to respond and perform relevant application database operations. The application front-end receives the business entry URL response from the application back-end and performs its business operations.

[0019] When the application frontend needs to perform business operations by calling the TVOS terminal hardware, the HTML5 page encapsulated by the application frontend, which includes an interactive interface and interactive operations, first sends an operation request to JNI through the hardware call interface provided by the application library file. The TVOS system then calls the TVOS hardware through the TVOS hardware abstraction layer according to the JNI operation request to realize the user's hardware call operation. At the same time, the data returned by the hardware call is displayed through the application frontend HTML5 page to realize the user's business interaction.

[0020] Furthermore, when a user first enters the application front-end, the access request initiated by the front-end controller to the application back-end must include the unique terminal identifier of the TVOS terminal where the application front-end is located and the geographical area number defined by the TVOS system of the terminal.

[0021] When a user enters the application front end for the first time, the application back end sends an access request to the application back end for the unique identification number of the TVOS terminal and the geographical area code of the TVOS system. The application back end uses the function scheduling module to query the application database for the business entry URL address corresponding to the unique identification number of the TVOS terminal and the geographical area code of the TVOS system, and directly points the page access request to the business page system, which then provides business services to the application front end.

[0022] Furthermore, it includes an application front-end and an application back-end, wherein the application front-end operates on a TVOS terminal. To achieve the above objectives, the present invention adopts the following technical solution:

[0023] The outstanding and beneficial technical effects of this invention compared to the prior art are:

[0024] (1) In the prior art, different applications need to be packaged and their memory resources are independent of each other, which undoubtedly limits the number of applications that can be installed on the TVOS terminal. In this invention, it was found that although different applications have different user interfaces, they may have the same functions. Therefore, the system classifies, decouples and develops application requirements to obtain a hybrid application framework with application source code, application interaction interface files, application library files and business page system. When the hybrid application framework is oriented towards different applications but has the same user interface with the same functional requirements, the application with the same functional requirements but different user interfaces can be displayed by using a set of application source code, application interaction interface files and application library files and changing different business page systems. Therefore, the development method and system of this TVOS system application that supports multiple business interfaces saves the memory resources occupied by applications on the TVOS terminal and increases the number of applications that can be installed on the TVOS terminal.

[0025] (2) In this invention, the method takes into account the advantages of native applications and H5 applications. It can provide a wide variety of application services on TVOS terminals with limited or even small memory performance. It also has the advantages of fast running speed, rich user interface, good interactive experience and no need to update the application. Moreover, the developed application can satisfy different types of terminals to enjoy the same user interface, without the need to develop different applications for different types of terminals, thus reducing development costs.

[0026] (3) In this invention, by decoupling the application requirements and developing them on a hybrid application development framework, the application front end is made into a general container. Only the business page system of the application back end needs to be customized to realize the application development of multiple business interfaces in one application front end. Attached Figure Description

[0027] Figure 1 A schematic diagram illustrating the APK application development framework and management for TVOS;

[0028] Figure 2 This is a schematic diagram of the overall process of developing an APK for TVOS system that supports multiple service interfaces according to the present invention.

[0029] Figure 3 The software requirement types defined in GB / T 9385-2008 "Computer Software Requirements Specification".

[0030] Figure 4 A schematic diagram illustrating the functional requirements classification of this invention;

[0031] Figure 5 This is a schematic diagram illustrating the coupling type of the present invention based on functional requirements;

[0032] Figure 6 This is a schematic diagram of the steps of decoupling according to the coupling type of functional requirements in this invention;

[0033] Figure 7 This is a schematic diagram of the application APK development method based on the decoupling of terminal-dependent functional requirements and user interaction requirements according to the present invention;

[0034] Figure 8 This invention relates to a development method and system model for application APKs supporting multiple service interfaces based on the TVOS system. Detailed Implementation

[0035] To facilitate understanding by those skilled in the art, the present invention will be further described below with reference to the accompanying drawings and specific embodiments.

[0036] TVOS is a smart television operating system officially released by the State Administration of Radio and Television in 2016. It is a dedicated smart operating system for television terminals developed based on the general-purpose Linux open-source kernel. TVOS runs on digital television receivers and manages the hardware, software, and data resources of the receivers, controls program execution, provides a human-computer interaction interface, and provides system software for the operation and security of other application software. In this embodiment, applications are generally referred to simply as "applications." Since TVOS is an Android-like operating system, like Android, applications running on TVOS can exist in the form of APKs. TVOS uses a hierarchical modular approach to build application management components, which include functional units such as download management, package management, application status management, application window management, application permission management, digital signature, and application management interfaces. An APK is an Android application package used by the Android operating system and is one type of application.

[0037] like Figure 1 As shown, the core element for application development and management on TVOS is considering TVOS application management. Conceptually, this means embodying the essence of human-computer interaction and designing and implementing corresponding management methods accordingly. Applications are the main body of interaction, and the manager of this interaction needs to handle interface presentation, content interaction, and message transmission and processing. For Android-like TVOS, application management also includes functional modules such as application package parsing, installation, updating, uninstallation, information construction, and permission management.

[0038] A TVOS terminal with the TVOS operating system installed generally includes the TVOS hardware abstraction layer, JNI, and TVOS hardware (including built-in or connected hardware); the JNI is the TVOS hardware Java native interface.

[0039] Based on the TVOS application and management framework, current application development methods for TVOS generally include two types: HTML5 (H5) application development and native application development. Each method has its advantages and disadvantages. If direct access to all terminal hardware functions is required, native application development is typically chosen. However, native applications suffer from drawbacks such as long development time, high development costs, need for updates, and large memory consumption. If cross-platform compatibility, installation-free operation, rapid deployment, and no occupation of terminal hardware storage are considered, H5 application development is usually chosen. However, H5 applications have the advantages of not being able to directly access device hardware and a poor user experience. This invention aims to combine the advantages of both native and H5 application development methods by choosing a hybrid application development approach.

[0040] like Figure 2 As shown, for any application APK requirement, after requirement sorting and analysis, the functional requirements are first decoupled using a method that decouples the functional requirements of the application-dependent terminal from the user interaction requirements. Then, the application APK development is divided into two parts: the application (APK) front-end (user end) and the application (APK) back-end (server end) through an application APK development method based on the decoupling of functional requirements of the dependent terminal and user interaction requirements. This separates the functional requirements of the dependent terminal and user interaction requirements into functional component modules. Finally, a complete application APK development method and its system model for the TVOS system are given. The business page system that the application APK needs to access is transferred from the application (APK) front-end (user end) to the application (APK) back-end (server end), enabling the same application to quickly support and provide different business application services (interface and information services) without the need for updates, upgrades, or installations.

[0041] This embodiment provides a development method for APKs supporting multiple service interfaces for TVOS systems, including the following steps:

[0042] Step S1: Obtain application requirements and conduct requirements analysis, referring to GB / T 9385-2008 "Computer Software Requirements Specification" and GB / T32279-2019 "Technical Requirements for Smart Mobile Terminal Application Software (APP)". Figure 3As shown, the requirements for any application are categorized into functional requirements and non-functional requirements. Functional requirements can be further classified into user interaction requirements and business interaction requirements, while non-functional requirements can be categorized into performance requirements, security requirements, quality requirements, and business specification requirements. This invention focuses on functional requirements to achieve subsequent decoupling and does not involve the non-functional requirements.

[0043] like Figure 4 As shown, current mainstream software requirements specifications, GB / T 9385-2008, and GB / T32279-2019 further categorize the functional requirements of any application to facilitate decoupling in the next step. Specifically, user interaction requirements are categorized into user interface requirements and user operation requirements; business interaction requirements are categorized into business interaction process (logic) requirements, business interaction hardware call requirements, and business interaction data linkage requirements.

[0044] User interface requirements: The user interface refers to the requirements for the form of service windows (status bar, navigation bar, main menu bar, content area, etc.) and their visual effects (lines, shapes, colors, textures and patterns) that the application should provide.

[0045] User interaction requirements refer to the interactive operations that users perform when using the various services provided by the application (APP), such as page navigation, progress bars, page scrolling, image carousels, drop-down menus, and search boxes, through clicking or selecting.

[0046] Business interaction process (logic) requirements: The logical relationship requirements of the sequential process, branch process, and loop process of the business itself when users use the application APP.

[0047] Hardware call requirements for business interaction: Some business functions provided by the application (APP) require the TV to call specific hardware such as camera, Bluetooth, sensors, and speakers. When users use these business functions, the application (APP) needs to call the specific hardware.

[0048] Business interaction data linkage requirements: There is a need for data for certain business functions provided by the application APP to be shared with other applications APP, either from outside the application APP or from the application APP itself.

[0049] By further subdividing functional requirements, and considering the characteristics of native application development technologies and H5 application development technologies, Table 1 presents a matrix for selecting the best application development technologies based on different types of functional requirements:

[0050] Table 1

[0051]

[0052]

[0053] The table above shows that hardware call requirements for business interactions must be implemented using native application development technologies, while other functional requirements can be implemented using H5 application development technologies, which allow for flexible and rapid updates and iterations of the business.

[0054] Step S2: Decouple the business interaction requirements and user interaction requirements obtained in Step S1 to obtain functional component modules and regular functional modules.

[0055] like Figure 5 As shown, application requirements are broken down and categorized, and then atomicated (minimized in functionality) and classified according to actual needs. Through the analysis of application requirements, coupling type analysis and matching are performed on all functional requirements of the overall application based on user expectations and the application prototype design.

[0056] like Figure 6 As shown, the coupling types, from weakest to strongest, are:

[0057] The decoupling method of this invention ranks non-directly coupled (lower than data coupled, lower than tag coupled, lower than control coupled, lower than external coupled, lower than functional coupled, lower than content coupled) functional requirements as follows: Non-directly coupled and data coupled functional requirements are encapsulated into functional component modules, which are then provided to other functional requirements for invocation or interfacing via interfaces. Through coupling type analysis and matching, non-directly coupled and data coupled functional requirements are encapsulated into functional component modules, while other coupled functional requirements are treated as regular functional modules, thus achieving decoupling.

[0058] Step S3: Implement the conventional functional modules obtained in Step S2 using the application source code and application interaction interface files of the application front-end in conjunction with the application back-end. Implement the functional component modules obtained in Step S2 using the HTML5 pages and application library files of the application front-end. The functional component modules and conventional functional modules achieve data interaction through calling interfaces on the HTML5 pages.

[0059] like Figure 7 As shown, based on the decoupling method of application-dependent terminal business function requirements and user interaction requirements, and combining native application development and H5 application development technology frameworks with the mainstream development environment of Android terminals, the application development method of this invention is presented:

[0060] By decoupling the application's terminal-dependent business function requirements from user interaction requirements, this approach categorizes and decouples the regular functional modules and encapsulated functional component modules of an application APK. Regular functional modules are divided into application (APK) source code and application (APK) interactive interface files according to the Android terminal application APK development environment. The functional component modules to be encapsulated are defined as application (APK) library files and implemented using HTML5 pages on the application frontend. Regular functional modules and encapsulated functional component modules interact with each other through HTML5 pages calling interfaces (including hardware calls and data calls). The application frontend encapsulation includes the interactive interface and the HTML5 pages for user interaction.

[0061] Overall, the application (APK) frontend requests services from the application (APK) backend (business page system). In this method, when the application frontend does not need to call the user interaction requirements of the TVOS terminal hardware, it initiates a request to the application function model of the application backend through the front-end controller to realize the information interaction business between the application frontend and the application backend; for example, it responds to the specified business entry URL address and performs relevant application database operations, and the application frontend receives the business entry URL of the application backend response and performs its business operations.

[0062] When the application frontend needs to call the TVOS terminal hardware for business interaction, the HTML5 page containing the interactive interface and user interaction operations encapsulated by the application frontend sends an operation request to the TVOS terminal's JNI through the hardware call interface provided by the application library file. The TVOS terminal, based on the JNI operation request, calls the TVOS system hardware resources through the TVOS hardware abstraction layer to realize the user's hardware call operation. At the same time, the data returned by the hardware call is displayed through the application frontend HTML5 page to realize business interaction with the user.

[0063] The application backend business page system implements corresponding business services. By requesting different business page systems from the application (APK) backend through regular functional modules, the interface of the application APK can be personalized through different layouts of the application interaction interface files.

[0064] The application (APK) source code includes all the program code files required by the application (APK), including the front controller, application interaction view definition, etc.; the front controller includes the application front-end HTML5 initial page and the application back-end request interface method; the application interaction view includes the application business page layout template and the application business page template interface image, including: image resources, layout files, character, color, style and other format parameters.

[0065] The application (APK) library files include library files that the application (APK) needs to call with the TVOS terminal hardware, HTML5 application call interfaces, etc.; the library files can directly interface with the terminal hardware layer;

[0066] The business page system is a set of program code deployed on the backend of the application (APK) for the function configuration, interactive interface definition and design, and can be accessed and called by the front-end controller of the application (APK).

[0067] The application (APK) frontend initiates a request to access the business page system of the application (APK) backend through an initial HTML5 page and access parameters. The application (APK) backend provides any page address in the business page system that matches the access parameters of the application (APK) frontend based on the access request. This transforms the personalized customization of the application (APK) frontend into the customized development of the business page system in the application backend, enabling the same frontend application to be used in multiple scenarios.

[0068] like Figure 8 As shown, this paper presents the development method and system model for application APKs based on the TVOS system that support multiple service interfaces.

[0069] The system model consists of two processes:

[0070] The first process: The input / output process between the application (APK) front-end (user end) deployed on the TVOS terminal and the terminal hardware with the TVOS system installed:

[0071] Users input data into the TVOS terminal via touchscreen or remote control. The TVOS terminal hardware, through system drivers and TVOS's HAL (Hardware Abstraction Layer) related variables or functions, initiates device services to provide hardware calls to the application (APK). The device services are provided to the application (APK) library files via JNI (Java Native Interface). After the application (APK) front-end (user end) and application (APK) back-end (server end) complete the function request response, the data is displayed to the user through the TVOS system and its terminal hardware.

[0072] The second process: The application (APK) front-end (user-side) process and the application (APK) back-end (server-side) function request and response process:

[0073] JNI (Java Native Interface) provides hardware control to the application (APK) library file through Java native interfaces. The application (APK) library file is provided to the application (APK) front-end controller through the SDK (Software Development Kit). When a user first enters the application front-end, the front-end controller initiates an access request to the application back-end. The front-end controller requests access from the application function scheduler of the application (APK) back-end (server-side) function scheduling module using the TVOS terminal's unique identifier and the geographical area code defined by the TVOS system. The application function back-end scheduler queries the application database to find the business entry URL address corresponding to the TVOS terminal's unique identifier and the geographical area code defined by the TVOS system, and returns the business entry URL address to the application (APK) front-end application function front-end controller. The application function back-end scheduler directly directs the page access request to the business page system to perform read and write operations on the application (APK) data and the application database. The business page system then provides business services to the application front-end. After receiving the business entry URL address, the application (APK) front-end application function front-end controller calls the application business page layout and application business page interface images of the application interactive view, and finally displays them through the TVOS system and its terminal hardware.

[0074] The above embodiments are merely preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Therefore, all equivalent changes made in accordance with the structure, shape, and principle of the present invention should be covered within the scope of protection of the present invention.

Claims

1. A method for developing an APK supporting a multi-service interface for a TVOS system, characterized by, Comprise the following steps: Step S1: Obtain application requirements and carry out requirement analysis, and obtain business interaction requirements and user interaction requirements according to the classification of application requirements according to the reference GB / T 9385-2008 "Computer software requirement specification specification" and GB / T32279-2019 "Intelligent mobile terminal application software (APP) technical requirements"; Step S2: The business interaction requirements and user interaction requirements obtained in step S1 are decoupled to obtain functional component modules and general function modules; the general function modules are divided into application source code and application interaction interface files according to the Android terminal application development environment, and the functional component modules are application library files and are realized by using the HTML5 page of the application front end; The business interaction requirements and user interaction requirements are coupled to obtain non-direct coupling, data coupling, label coupling, control coupling, external coupling, function coupling and content coupling; The non-direct coupling and the data coupling are decoupled to obtain the functional component modules, and the label coupling, the control coupling, the external coupling, the function coupling and the content coupling are decoupled to obtain the general function modules; Step S3: The general function modules obtained in step S2 are realized by using the application source code and the application interaction interface files of the application front end in cooperation with the application back end, and the functional component modules obtained in step S2 are realized by using the HTML5 page and the application library file of the application front end, and the functional component modules and the general function modules realize data interaction through the HTML5 page calling interface. 2.The method of claim 1, wherein the method further comprises: receiving a request for a service from the TVOS system; and providing the requested service to the TVOS system. In steps S2 and S3, the application front end HTML5 page encapsulating the interaction interface and the user interaction operation, when the application front end does not need to call the user interaction requirements of the TVOS terminal hardware, initiates a request to the application function model of the application back end, realizes the information interaction business of the application front end and the application back end; when the application front end needs to call the business interaction requirements of the TVOS terminal hardware, uses the application front end HTML5 page encapsulating the interaction interface and the user interaction operation to make an operation request to the TVOS terminal through the hardware calling interface provided by the application library file, and the TVOS terminal calls the system hardware resources according to the operation request and realizes the corresponding business service according to the interaction operation defined by the HTML5 page and the business page system of the application back end. 3.The method of claim 1, wherein the method further comprises: determining a plurality of services supported by the APK; and providing a plurality of service interfaces for the plurality of services. In step S1, the user interaction requirements include user interaction interface requirements and user interaction operation requirements; the business interaction requirements include business interaction process requirements, business interaction data linkage requirements and business interaction hardware calling requirements. 4.The method of claim 2, wherein the method further comprises: receiving a request for a service from the TVOS system; and providing the requested service to the TVOS system. The application source code of the application front end includes a pre-controller and an application interaction view; the pre-controller includes an application front end HTML5 initial page and an application back end request interface method; the application interaction view includes an application business page layout template and an application business page template interface picture; The application library file of the application front end includes a library file and an HTML5 application calling interface; The application back end includes an application function scheduling module, a business page system and an application database; The TVOS terminal comprises a TVOS operating system, a hardware abstraction layer of the TVOS, a JNI and TVOS hardware; the JNI is a hardware Java native interface of the TVOS; The application front end works in the TVOS terminal.

5. The method according to claim 4, characterized in that, The application front end initiates a request access to the service page system of the application back end through an initial HTML5 page and access parameters, and the application back end gives any page address matched by the access parameters of the application front end in the service page system according to the access request, and then converts the individual customization of the application front end into the customized development of the service page system in the application back end, so as to realize the same front end application in multiple scenarios.

6. The method according to claim 4, characterized in that, When the application front end does not need to call the user interaction requirement of the TVOS terminal hardware, the application front end initiates a service request to the function scheduling module of the application back end through the front controller, the function scheduling module of the application back end responds to the service request according to the service request and performs related application database operations, and the application front end performs business operations according to the service entry URL address of the application back end response; When the application front end needs to call the service interaction requirement of the TVOS terminal hardware for business operations, the application front end encapsulates an HTML5 page containing an interaction interface and an interaction operation, and first performs an operation request to the JNI through the hardware calling interface provided by the application library file, the TVOS system calls the TVOS hardware to realize the hardware calling operation of the user according to the JNI operation request through the hardware abstraction layer of the TVOS, and simultaneously displays the data returned by the hardware calling through the HTML5 page of the application front end and realizes the business interaction of the user.

7. The method of claim 6, wherein the method further comprises: determining a service type of the service; and displaying a service type icon corresponding to the service type on the service type area. The front controller initiates an access request to the application back end when the user enters the application front end for the first time, and the access request of the front controller must contain the terminal unique identification number of the TVOS terminal where the application front end is located and the geographical area number defined by the TVOS system; The front controller initiates an access request to the application back end when the user enters the application front end for the first time, and the access request of the front controller must contain the terminal unique identification number of the TVOS terminal where the application front end is located and the geographical area number defined by the TVOS system; 8. A system for developing a method of supporting a multi-service interface of an APK using the TVOS system of claim 1, characterized by, The application front end and the application back end are included, and the application front end works in the TVOS terminal.

Images