TW200849990A - Method and apparatus for multiscreen management for multiple screen configuration - Google Patents

Abstract

An object of the present invention is to perform multiscreen configuration and multiscreen management by using a plurality of screens and a plurality of methods in order to represent a plurality of service contents. In accordance with a multiscreen configuration method according to an embodiment of the present invention, by mutually assigning one or more broadcasting services, one or more logical screens, one or more display screens, and one or more output ports, untimately outputting service contents which are executed on screens assigned by output ports, and setting, changing, and reporting configuration of a multiscreen, the configuration of the multiscreen may be set or reset so as to effectively output various service contents on the multiscreen by using a desired method.

Description

200849990 27131pif IX. Description of the Invention: [Technical Field] The present invention relates to a method and apparatus for displaying a plurality of services on a screen, and more particularly to a plurality of screens capable of representing or displaying a plurality of services The configuration method and device of the final output screen. [Prior Art]

Conventional broadcast receiving systems, such as digital television (τν) or digital set-top boxes, provide a single content on a single physical display device, or can display both the primary and secondary screens on a single physical display device. However, the conventional broadcast receiving system can simultaneously display the main screen and the sub-screen on the same display screen, and the method of arranging the main screen and the sub-screen can be very different. Only a few kinds of display devices can be combined and displayed. Wide =, digital multi-energy disk (DVD) and the services provided by the external device source connected to the input. Although there is a video service, the voice service sub-service can be read on the field screen, but the service can not be displayed on the firefly I ^ son-mother face (pip, coffee (four) gamma method display: display screen in a single entity At the same time 盥 150 and the main two screen tea test 旒 100,, 120, 130, 140 142, 144, 1S9 / 綦 and 105, 115, (2), 135, 105, U5, W 54 for the sub-screen. Especially Because the secondary screen 125 ' 135, 142, 144, 152 blood 1 from a to n small _, the implementation of the value of the name and the position of the 154 or the large square is also limited by the flexibility of the traditional PlP method. Interactive TV should, Use environment, such as home multimedia platform 5 200849990 Z / 1Jipu

(Multimedia Home Platform, MHP for short), ACAP (Application Configuration Access Protoco) and OpenCable Applications Platform (OCAP), which assumes that only one screen is output. In the interactive τν application environment, the user interface (UI) of HAVi (Home Audio - Video Interoperability) is used. According to the HAVi UI, even if it is not limited to display on the physical display device

The number of screens in the screen is generally only displayed on one screen. In addition, what the application shares is also the single screen that is displayed. In addition, the traditional application environment of broadcast services is limited in displaying various service content types on dynamic architecture screens. SUMMARY OF THE INVENTION The present invention provides a method for multi-screen architecture and management, which can simultaneously display a plurality of service contents at a desired location and display the present invention in a desired size. The invention also provides an interface that allows a multi-screen source device to be supported. Can be effectively utilized, and money screen function tube _ interoperability application. The invention also provides a backup interface for managing multiple screen functions and multiple screen states, such as post- or POP (Picture-out of-Picture). The multi-screen management method and device of the present invention can be moved away from the application life cycle. 'With multiple independent axes (four): for: or New: content with one or more screens, non-pair-methods, architecture of the invention and management of multiple screens 6 200849990 2713 lpif method and device dynamic architecture With the final screen output. In addition, due to various source management interfaces, the multi-screen management feature allows efficient use of resources for host devices that support multiple screens. The OCAP multiscreen management (MSM) enhanced version according to an embodiment of the present invention belongs to an enhanced version of the CAP, which includes all required application interfaces (ΑΠ), content and data formats, and communication protocols until the application phase. Applications developed for the CAP MSM Plus can be implemented on open wired compatible hosts. 〇CAp MSM Plus allows wired operators to schedule (DEPLOY) interoperability (INTER〇PERABLE) to manage multiple screen functions on open wired compatible hosts connected to their network. This protocol (PROFILE) allows wired operators There can be a standard interface to manage multiple screen functions and their screen states, such as PiP or POP screens, between multi-host device providers. According to one aspect of the present invention, a method of managing and managing multiple screens is provided, the method comprising: receiving one Or a plurality of broadcast services; specifying a fine clock), or a plurality of broadcast services to the screen; designating the screen to one or more display screens; and designating the one or more display screens to one or more port. The method further includes: associating a service context of one of the logical screens to a context of the one or more display screens; and changing an association between the contexts. The method further includes deciding to include the logic screen, the one or more display screens, the service context and a multi-screen architecture associated with one or more of the output information; and changing the multi-screen configuration. The method further includes: observing the pre-conditions for changing the multi-screen configuration. 7 200849990 Z/IJiplf and post-conditions include: reporting the multi-screen configuration and context changes. The above characteristics and advantages of Xingxingyu and Wuming can be more obvious. The following two examples of special cattle, sub-matching the drawings, are described in detail below. [Embodiment] The description of M r will be accompanied by the illustration of the embodiment, and the proposed embodiment is carried out on the 1st of 0. The same or similar is used in the average 4: ϊ:

> Deficient Titanium, 疋 is used to describe the same or similar parts. The multi-screen management of the present invention will be explained with reference to Figs. 2 to 34C. The concept of the multi-screen system and multi-screen management of the present invention will be explained with reference to Figs. The definitions and functions of various Java types of the embodiments of the present invention will be explained with reference to Figs. 11A to 29 . A change or improvement of the 〇cAp standard for implementing an embodiment of the present invention in an OCAP environment will be explained with reference to Figs. 30A to 34C. To better understand this specification, abbreviations and nouns will now be defined. “HAVi” is an abbreviation of (Home Audio - Video Interoperability). “msm” is an abbreviation for Multi-Screen Management. "PiP" is an abbreviation for the face of the child. "p〇p" is an abbreviation for separating facets. "AIT" is an abbreviation of the application information table. "XAIT" is an abbreviation for the extended application information table. ''Audio Focus Screen' is a screen that selects its sound source for display on any of the 8 200849990 27131pif sound display devices associated with any enabled image output. The screen may be directly related (when it is displayed) Screen) or indirectly related (when it is a pair of logic screens) to enable image output 埠. π Display Mapper, is a logic process that blends the normalized coordinate space of the logic screen to display The normalized coordinate space of the screen (or part of it). Display Multiscreen Configuration is a multi-screen configuration that only contains the display screen. The per-platform multi-screen configuration is a display multi-screen configuration. The type of the display that shows the multi-screen configuration is 'SCREEN-CONFIGURATIONJDISPLAYf, which will be explained below. "Display Screen" ^ A type of screen that models the final output mix of a physical display device. The display screen is related to one or more image output ports, and one or more image outputs are (1) attached to An internal integrated display; or (2) attached to a physical output line connected to an external display device through some known interface, such as High-Defmition Multimedia Interface (HDMI) or IEEE 1394. The "General Screen" is a logic screen that is assigned to the general screen type and will be explained below. The general screen can be reconfigured to serve different applications. For example, it can be grouped at certain times. The state is a PiP screen, and at other times it can be configured as a P〇P configuration. ~ "Logical Screen" is a type of screen that is not directly related to the physical display device' but can be displayed through the display And the screen is displayed to the display screen. The logic screen can be mapped or unmapped. If it is reflected, its phase 9 200849990 z/uipif about the display screen; if it is not reflected, it does not show the screen. In exceptional cases, the logic screen can be directly related to the image output port, in which case it can be used as a logical screen and a half display screen. The π Main Screen, which is the display screen or logic screen, is assigned to the main screen type and will be explained below. The main screen is always expanded to the full screen of the display unit (except for the display unit) without knowing the MSM.

Multiscreen Configurable Context is an enhancement of the multi-screen situation, which can configure status information about the multi-screen management function. The multi-screen configuration scenario is configurable by the multi-screen used in the embodiment of the present invention. The context (MultiScreenConfigurableContext) is defined by the interface, and in the present invention, the MultiScreenConfigurableContext interface is a Java type representing a multi-screen configurable context. ''Multiscreen Configuration'' is A discernable collection of screens, which may or may represent content, may (but are not necessarily) a suitable subset of all accessible screens that are implemented on a given platform or on a given display screen. At any time, a single multi-screen group The state can be applied to (1) the whole ^, in this case, the screen in the configuration is the display screen; (the magic display screen) In this case, the screen in the configuration is to display the screen itself or ^ At this point, a set of logic screens for the screen is displayed. The established bottom curtain is always present in the multi-screen configuration. Any multi-screen group And with the embodiment of the present invention

Defined by the MultiScreenConfiguration’ interface 200849990 ‘MultiScreenConflguration, the interface is the type that represents the multi-screen configuration. ''Multiscreen Configuration Type', is a feature of multi-screen configuration, mainly based on the type of screen it is composed of. The collection of configuration types can be further divided into: (1) single-display called display multi-screen configuration; and (2) other multi-screen configuration types, called non-significant no-fam configuration. The Mutiscreen Context ' is a status message that enhances the HAVi screen to allow interworking on platforms that implement multiple screens. This basic multi-screen scenario provides the ability to discover (but not change) status information.夕^: The screen of the screen is defined by the 'MultiScreenContext' interface of the present invention. In this specification, the MultiScreenC〇ntext interface represents a multi-screen scene. The Multiscreen Manager' is a separate management component that is provided by a platform implementation that effectively uses multiple screens through the features defined in this specification. Multi-screen administrators are also known as multi-screen administrators. Multi-screen administrator used by embodiments of the present invention

The MultiScreenManager’ level is defined, and the 'MultiScreenManager’ level is a java type that represents multiple screen administrators. "Overlay Screen" ^ A kind of logic screen assigned to the outer screen category, which will be explained below. The z-order of the outer screen allows the associated outer screen to be located at the top 11 other than the other non-outer screens. ^ / ij ιμιι front. Per-Display Multiscreen C〇nflgUratiGn'' is a non-display multi-screen configuration that can be used to define the silk or potential associated with a more TFf screen. The silk screen § screen group. In the current active f platform multi-screen configuration, the bottom layer display screen includes state variables to define its active display multi-screen configuration. "Multi-window configuration of each platform (Per_piatf〇rm Μιιΐ_·

Shouted, its (4) or can be used to set ίί? Display: screen group. At present, there are many screens in the active platform of each platform, and the state variables of the individual cases of the ceremonial officials. "PiP Screen" is a kind of logical cemetery ^

Pip pip ° a fragrant and (in z_order) more front than the main screen 0 "PoP screen, 'is a kind of logic screen, its pattern to pQp glory type. PoP screen - like along - 其他 other PqP Rong Curtain placement, full display screen. "SCreen" is a set of (logical or possibly physical) resources that can represent certain background colors 'background image, image and image combination. Background color' The background image 'image and image is displayed by 'HscreenDevicei' provided by HAVi. The background color and background image are displayed by 'Hbackgrounddevice1, the image is displayed by HVide〇Devke, and the image is displayed by 'HGraphicDevice'. It can include a 'Hbackgmimddevice, one, HVide〇Device, and a 'HGmphicDevice'. The screen can be categorized as a display screen or a logic screen. 200849990 27131pif "Default Screen" is in multiple screens The highest access screen. ''Preset screen device(Default Screen DeviceV^ is the highest access screen device among multiple screen devices. The default screen device can be one of 'Hbackgrounddevice', 'HVideoDevice' and fHGraphicDevice'. ▼'Screen Category (Screen Category ) '' is a set of screens, depending on their purpose or configuration characteristics. ''Screen Identifier'' is a unique platform designation of the underlying screen and its resources, which allows for different types of screens or between single screens. "Screen Type" is the top-level segmentation of the screen, divided into display screens and logic screens. π Service (Service) * - a multimedia content that includes multiple service components. "Service Component" A service component that includes an image component, a sound component, and a data component. The data component includes various information items of services and applications executed on the platform. The π Service Context is an object that includes to be Implement service resources, device and status information, etc. OCAP MEM Plus defines a set of features and To allow efficient use of multi-display and multi-logic screens on platforms that support these attributes. π Multiscreen Configuration Listener is used to provide notifications that the system and application change the overall status of the 'MultiScreenManager', or The status of a certain display of each platform, HScreen, 13 200849990 Z/ 13 ipif change, or the change of state of each display multi-screen configuration, or the change of special fMultiScreenConfiguration'. Multi-screen configuration listener by the embodiment of the present invention The fMultiScreenConfigurationListener interface used is defined, and the fMultiScreenConfigurationListener" interface in this specification is a Java type that represents a multi-screen configuration listener. The πMultiscreen Context Listener is used to provide a system and application change MultiScreenContext. The multi-screen situation listener is defined by the fMultiScreenContextListenerf interface used in the embodiment of the present invention, and the fMultiScreenContextListener' interface in this specification is a Java type representing a multi-screen situation listener. "Multiscreen Configuration Event" is used to report changes to the overall state of fMultiScreenManagerf, or to change the status of some displays 'HScreen' for each platform, or to change the status of some display multiple screen configurations. Or a special %1111^(^611(^011]^11 with 1; 丨0111 change. The multi-screen configuration event is defined by the 'MultiScreenConfigurationEvent' interface used in the embodiment of the present invention, and the fMultiScreenConfigurationEventf interface in this specification is A Java type representing a multi-screen configuration event. "Multiscreen Context Event" is used to report changes to 'MultiScreenContexf' to interested listeners. Multi-screen context events are used by embodiments of the present invention The fMultiScreenContextEvenf interface is defined, and in this specification, 14 200849990 2713 lpif 'MultiScreenContextEvent, the interface is a Java type representing a multi-screen situation event. 'Multiscreen Event' is the approximate basic level used to organize the event identification code. Event identification code Regarding the different types of events used for the multi-screen management function, the multi-screen event is defined by the Multiscreen Event, interface used in the embodiment of the present invention, and in this specification, the Multiscreen Event 'interface is a java type representing a multi-screen event. Event (Multiscreen Resource Event)' is used to report the change of the resource status of the multi-screen of the resource. The multi-screen resource event is used by the embodiment of the present invention, the Multiscreen Resource Event, and the interface is in this specification, Multiscreen Resource Event , the interface is a Java type that represents multiple screen resource events. The extent to which a particular platform supports this enhanced version is determined by the platform and device manufacturer, or by other external features of the enhanced version, which are generally ordered by type and _ , including the available adjuster (9) (four) or independent \, the number of available image decoding pipelines, integrated display; two 3 ^ with the sound = the number of output ' can be used for temporary storage of images, α small 5 fe body 1, with other unspecified resources. Interpretation. Maoyue's eve system and multi-screen management will FIG 2~10 significant test logic to an embodiment of the two curtain labor invention, which was secret group and Groups - 7 ",, membered group 23〇 not military screen associated with the display screen on the display enantiomer 15 200849990 ^ I U l pif = 220. The display mapper 220 is a process of mixing the normalized coordinate space of the logic screen to the normalized coordinate space of the display screen. That is, through the display mapper 220, one or more logic screens can be displayed at desired locations on the display screen. For example, the multi-screen management system of the embodiment of the present invention includes a display screen 220, a plurality of logic screens 212, 214 and 210, and a plurality of display screens 240' 250 and 260. Using the display mapper 220, the logic screen 212,

At least one of 214 and 216 is displayed on each of the display screens 24, 25 260. That is, the screen areas 242 are arranged in parallel within the display screen 24G because of the relationship of the display screens 22A. The logic screen 212 will slant within the _ 242 and the logic screen 214 will also be scaled within the BD area 244. Similarly, the logic screen 214 is located at the last screen area 252 where the display 2 is displayed. The logical honor screen 254 is located in the screen area 254 of 显26Π^. The logic screen 212 is located in the display: placed in the display field: 262. The logic screen 214 will be reduced; the screen will be displayed in the screen; 310 5 34〇, and I(5) unit 35/service processing unit, output unit yellow L The number is received early ttl 310 to receive the cable television broadcast signal. Another 16 200849990 2713 lpif outer 'broadcast # 5 tiger receiving Zhuoyuan 310 also receives terrestrial broadcast signals or satellite broadcast signals. The digital signal processing unit 320 utilizes the broadcast signal receiving unit 3 The service component is received to reconfigure the service. The multimedia service processing unit 330 generates a logic screen for representing the service reconfigured by the digital signal processing unit 320, and outputs the screen to the output unit 340. > The element 340 generates a display screen and displays the display screen to the logic screen. That is, the logic screen is related to the display screen, so that the service of the logic screen is related to the display screen. Although in Figure 3, the service is first related to the screen. The logic screen is then related to the display screen, and the invention is not limited thereto, the service may be directly related to the display screen. ' When the output unit 340 includes one or more When outputting, the output ports may be related to the display screen. For the side digital TV system 300 to be able to implement the multi-screen management function, it is necessary to determine the logic screen by the multimedia signal processing unit 330 and the output unit 340 to display the screen and The output is connected. When the platform is implemented, multiple screens can be generated, and the implementation of multi-screen management functions (ie, multi-screen configuration, management and change) can provide MSM application interface (API), which will be solved underneath. The display unit 350 includes a physical display screen device for displaying the above display screen. Fig. 4 shows a plurality of contents presented by the digital τν system 4〇〇 according to an embodiment of the present invention. The digital TV system 400 can simultaneously present terrestrial broadcast content. 41〇, there are 17 200849990 / W Λ pif line broadcast valley 420 and personal video camera (pers〇nai vide〇rec〇rder, PVR) poor content 430. That is, if the multi-screen management of the present invention can be implemented in digital In the TV/set-up box (DTV/STB) module, the terrestrial broadcast content is 41〇, and the cable broadcast content 420 and the personal video camera data content 43 can be respectively related to the logic screen, and each logic The screen will be displayed on the display screen 450. Because the multi-screen management of the present invention defines at least one logical screen and at least one display screen, at least one logic screen can be mapped to a display screen. The logical screen of the content 41〇 will be located in the screen area 452 of the display screen 450, and the logical screen of the wired broadcast content 42〇 will be located in the screen area 456 of the display screen 450. In addition, because of the DTV/STB module, the PVT 0 capacity 430 The logical screen will be located within the screen area 454 of the display screen 450. That is, the logic screen will be scaled and placed at the display screen 45〇 in the established manner. 5A and 5B respectively show a non-abstract service and an abstract service according to an embodiment of the present invention. In Figure 5A, service group 510 is a non-summary service group. In Figure 5B, service group 520 is a summary service group. The non-summary service group 51 includes an image service 520, a sound service 530, and an application service 54. In contrast, the summary service group 550 includes an image application 560 and a sound application 57. That is, the summary service group 550 is a service group including only application services, which does not include any image service or sound service; the non-digest service group is a service group including other service and application services. 18 200849990 2713 lpif Figure 6 shows the relationship between the screen situation _ and various methods. = Figure 6, the screen situation _ includes: z order (Z·., visibility 63 () 'related display screen 640 and related service situation 650. ^ sequence 6 job test mosquito money on the silk The logical glory displays the sequence of information. In the display area 620, the normalized screen coordinate space of the logical screen is mapped to the normalized screen coordinate space of the display screen. Visibility 630 determines the logical or invisible display on the display screen. The related display screen 640 is a kind of display screen, which is related to the logic camp. The related service context 650 is related to the logic screen or the display fire service situation. The screen scene 6GG can be set, the setting/adding person, the way to set Or add eight attributes and read or remove attributes through the “read/remove” method. Also screen scenario 600 can be used to “set/join, and,, read/remove, determine and change attributes. X ^ Although not shown in FIG. 6, the screen scenario 600 includes not only the order, the display area, the visibility, the related display screen and the related service context, but also includes at least one of the following: the sound focus related to the current screen. About the sound source of the front screen, the order of the screen device related to the current screen, related to the display area of the current screen, and related to the current technology 'image output 埠. $ ' Figure 7Α and 7Β display according to the 避 screen The sequence is showing the result on the tread screen 19 200849990. As the z-order of the relevant elements increases, the relevant elements are located at the more front. For reference to Figure 7A, when the logic screen la 710 and the logic 2 are 2a 720 on the display screen 700 The Z order on the top is 1 and 2 respectively: The position of the sneaker screen 2a 720 is higher (more front) than the logic screen 2a 720. ^ Similarly, referring to Figure 7B, when the logic screen lb 760 and logic 2b 770 The Z order on the display screen 750 is 2 and } yesterday = screen, the position of the bee shoe screen lb 760 is higher (front) than the logic screen 2b 770. Figures 8A and 8B show the service context, logic screen and display 鸯Curtain association. The day will now explain the method of directly/indirectly associating the service with the service 810 including the video content 812, the sound within the $ and the application content 816. #贝的图图8A, when the service 810 is related The empty logic screen 82 and the logic screen 830 associated with the service 810 are related to the display screen 84. The time service 810 displays 850 on the display screen 84. That is, the display screen 840 and the service 810 are transmitted through the logic screen 820. 830 is indirectly associated with each other. Referring to Figure 8B, when service 810 is associated with an empty logical screen 84, service 810 displays 860 on display screen 840. That is, display screen 840 and service 810 are directly associated with each other. The service 810 is directly/indirectly associated with the display screen 84, the service 810 can be displayed on the display screen 84, and when it is finally associated with the output, it can be rotated. Figures 9A and 9B show the display of the display area mapped to the logic screen. 200804490 2713 lpif screen results. Referring to FIG. 9A, the scroll screen is not displayed, and the display screen 〇 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 显示 940 940 显示 显示 逻辑 逻辑 逻辑 逻辑 逻辑220 and the opposite of the "Di stem" although the logical screen _ through the display will show 96G in the 92G area 95G, the logical screen 910, that is, the area 950. On-screen content Firefly 'giving shrink: T method' can be displayed on the - part of the fire map, shoulders without multiple services, multiple logic screens and display screens between the screen management device can be related to - Service two logic screens 1〇4〇 with U〇30 and related to the second service surface of the first screen and the first screen. When the first logic is related to the output 埠 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , The final output 1070 can be presented on the display screen, and the 2 display can include multiple services 'multiple logic fires can be passed through ^2 /, one output. Therefore, the multi-screen management device D D takes turns to present multiple services and multiple screens. The configuration of the fascia is 'multiple fireflies of the embodiment of the present invention; a clothing can also be configured with multiple screen states, changes and management powers ^ /, ie 'because the multi-screen management method and device can provide various energy Change, setting and discovery: 21 between the logic screen and the display screen 2008 20089090. ==, screen device, service situation, display screen and image wheel out 埠fBJ off, sound focus assignment, display multi-screen configuration and each Multi-screen configuration; retaining resources and releasing reserved resources; and monitoring ^ notification of various changes' and pre-conditions and post-conditions of various changes, enabling smooth multi-screen configuration and multi-f screen management Various capabilities for multi-screen configuration and multi-screen management. The application to the CAP screen management method and apparatus according to an embodiment of the present invention will now be explained. ......Xi

The present invention defines a modular enhanced version of the 0CAP protocol for an OCAP host device that can support the multi-screen management functions defined in this specification. The multi-screen management function is defined as a standard software interface to allow interworking CAp applications to effectively utilize the resources of host devices that support multiple screens. ^ b OCAP MEM Plus is an enhanced version of the CAP Agreement, which includes all required APIs, content and data formats and protocols at the application level. Applications developed for the enhanced version of OCAP MEM will be implemented on open wired compatible host devices. CAP CAP ME M Plus allows the cable operator to schedule interworking applications to manage multiple screen functions on open cable consoles connected to the network. This agreement allows wired operators to have standardized interfaces to manage multi-screen functions and their status, such as Pip and ρ〇ρ screens between multi-master devices. The OCAP ΜΈΜ Plus can be applied to a variety of hardware and operating systems to allow for the flexibility of CE (consumer electronics) manufacturers. The main purpose of the OCAP MEM enhanced version is to provide manufacturers of customized electronic products (CE, consumer electronics) with 22 200849990 27131pif competitive real estate _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Web screen function. Wang Wu's face, 'I hope to understand the multi-model function __he, "and the interface, the implementation of the product, the method and the computer program block combination, can be provided by the ^ ^ map of the various blocks and flow chart order can be provided to the general Used to implement. These computer programs refer to the processing of data processing devices; two =; electricity] = programmable and programmable data processing I can be used by computers or other bio-uses: the instructions defined in the implementation of the flow chart block can produce Handling 3 A to a computer or other stylized data ¥ i, - Strings of wood can be executed in a computer or programmable form 4 can be processed to make it executable on a computer or programmable step 2. The blocks of =11 that can be used to implement the functions defined in the process block can represent module 1, code segment or part, :" Logic function - or multiple executable instructions. In the case of Beiyuan, the functions in the box can be executed in different order. Even, the two blocks can be executed at the same time, or the two blocks can be reversed!!: Depending on the function used. Standard Enhanced Edition. 0(10)MSM Power Port is in the form of a signal mechanism (descriptor, 200849990f f L· J. pil deSC_〇rS) API 'platform behavior (semantics, __岣 and application usage restrictions. Implemented here) In the example, the form of Αρι defined in this specification is an enhancement of the current function, and the HAVi defined by the suite, org.havi.ui' uses the eight-sided definition API. In particular, most of the functions defined here. The second type is the interface implemented by the actual level. This actual level is used by platforms that support the 'org.havi.ui.HScreen' level. 茭HScreen is a screen. The Jaa type or parameter is written in quotation marks (',). English. Java level is A collection of various parameters and methods of the same type of object, and the Java interface defines the ability of objects to interoperate within the hierarchy. The present invention = the embodiment can be used to change the configuration by a method defined by each level. The example is the object generated by the hierarchy. The method in the multi-screen management embodiment, the interception and Java type are defined in Figures 11A to 23D. ' OCAP MSM Enhanced Edition defines the selectivity of the Xlet should be used in (4) Descriptor. In the absence of such a description, it will be

The semantics of the presupposition. S OCAP MSM Plus enhances 0CAP through the multi-screen usage description defined below. The 〇CAp application notified in AIT or XAIT can include up to one multi-screen usage descriptor in the application description sub-loop used in the application. If there is no multi-screen usage descriptor in the application description sub-circle of some applications, the 0CAP host device will regard this as the existence of multi-screen usage descriptor, and its 'terminate-on-condition' flag is heavy. Set, 〇,, 24 200849990 2713 lpif its 'disallow j) artial-display a graphics-mapping, the flag is reset to O', and its 'allow one default one device one reconfig' flag is reset, oh, . The effect of the above is that 'under the preset, (1) the application of the preset graphics plane can be scaled (along with its preset background and image plane) to the display of the glory part, through the intermediary logic screen; (2) Applying a preset screen device cannot arbitrarily reorganize sorrow or its lack of a poor source, and (3) if this last condition must be maintained, suspend the application' or suspend if it cannot be paused. In this book, "Abort" is used when the application temporarily stops processing but continues to use resources. In addition, "Abort" is used when the application cannot find the resource and completely stops the process. The multi-title usage descriptors include: f descriptor tag1, 'descriptor_length!, terminate_on_condition, , disallowjpartial—display—graphics—mapping, , 'allow—default—device—reconfig’, and 'reserved,. ▼descriptor A tag' is an 8-bit unsigned integer whose value is 0x6E, which identifies this multi-screen usage descriptor. I descriptor-length is an 8-bit unsigned integer specifying the number of bytes after this block. In this specification, only one byte is after 'descriptor_lengthf. ▼terminate—on—condition' is a 1-bit flag specified in the application lifecycle when 'disallow_partial-display-graphics-mapping' is set to, ι, or 'allow-default-device-reconfig1 is set Effect, whereby the condition specified by one of the two flags requires a pause or abort of the application. 25 200849990 丄 / 丄J 1 pif* If this flag is set to "1,, then the OCAP platform will abort (destroy) the application at the beginning of the dominant condition; if this flag is set to, 〇,,, then 〇CAp The platform will try to pause the app, if it can't be paused, the app will be aborted at the beginning of the dominant condition. If the app is paused because this flag is false, the app must be replied when the dominant condition is not obtained, but If you can't reply, = If you can't get enough resources, you must abort (destroy) the application. In this scenario,, pause, is interpreted as the 'pauseXlet() method that caused the affected application's initial Xlet instance. 』artial_display A graphics-mapping, which is a 1-bit flag, which means that the application cannot continue to execute. When the multi-screen configuration changes, or when the service context is exchanged or moved between screens, the application presets the image plane ( The screen device must be scaled to operate in the logic screen where the screen area cannot be mapped to the full display screen. If not, disall〇w_partial-display-graphics-ma Pping, set to T, at the beginning of this condition, to suspend or terminate the application, according to the value of the 'terminate-on-condition' flag above; or, if 'disallowjmrtial-display-graphics-mapping' is reset to 0", at the beginning of this condition, the application cannot be suspended or terminated. 411〇~"16€&1111_^¥ to -Curry 11 is a 1-bit flag, the specified application can continue to execute, when more Changes to the screen configuration, or when switching between screens or moving service scenarios, may cause (1) one or more of the following screen configurations of certain preset screen devices (('HscreenConfiguration') parameters may change: screen area , pixel resolution or pixel size ratio; or (7) in 26 200849990 2713 lpif configuration change or service context exchange / mobile pre-existing _ or multi-preset screen device underlying resources in configuration changes or services After the situation exchange/moving can no longer be obtained. If 'allow-default-device-reconfig' is set to, 〇,,, then at the beginning of this condition, 'the application will be suspended or terminated, according to the above 'ter The value of the minate_on_condition' flag; or, if 'allow one default one device one reconfig' is set to '' 1 '', the application cannot be paused or terminated at the beginning of this condition. Tell 'allow-default- Applications with device-reconfig' set to "1" are expected to temporarily store listeners and handle 'org.havi.ui.HscreenConflgurationEvent, with the 'org.ocap.ui.MultiScreenEvent' Java type. The 'reserved' block is reserved for future standards, and its value is all "j,". The application interface of the OCAPMSM enhanced version will now be explained. The embodiment of the present invention will be explained using the Java type. However, this embodiment is not Limited to the Java type, it is known that other techniques can be used to achieve the goals and effects of the present invention. 〇 CAP MSM Plus defines a collection of functions and behaviors to allow for effective use on the platform of embodiments supporting these features. Display and Multi-Logic A.] VISM Plus enhances OCAP by adding the multi-screen management functions described below. The OCAP host device supporting OCAP MSM Plus must implement the semantics defined below. OCAP Application Preset 'HScreen* Is fHScreen', which stands for Preset 27 200849990, the current active set of the underlying screen device and its current active HAVi screen configuration. The application preset 'HScreeW' information is described in more detail in the fDefault Hscreen Assignment' and fMultiScreenManager.getDefaultHScreen()' methods. The level of OCAP MSM Plus provides the secondary and primary viewing screens for the OCAP implementation, ie PiP and The PiP views the screen, the segmentation logic 'HScreen'. (The screen will now be explained. The HAVi user interface subsystem (called the baseline HAVi model) defines the description of the 'HScreen device's final output composition' and stands for two independent The platform of the device can support two examples of this level.” Importing MSM Plus can enhance this definition to import the interval between the display screen and the logic screen. First, the explanation will be explained by, the display screen, and the enhanced , HScreen, level. The screen showing the final output 1 composition of a physical display device is called "display screen," relatively, through the logical coordinate system conversion process, Converted by hardware or software, and the screen that is displayed on the display screen is called “logical screen, display screen related (reflecting) to 0 or more image output 埠, which can be turned into or disabled) As defined by ''VideoOutputPort'), if the display is not related to any image output, then any active display of the screen's situation is displayed here. 28 200849990 2713 lpif The display screen in the MSM situation is regarded as the image output contained in the J sound output and the display screen for displaying the sound content. The sound focus screen ,, for, and two curtains (audi〇f_sc wide. Therefore, the relevant sound source of the image wheel of the sound should be presented in the pair to display the sound output of the screen, which can be the embedded sound & 3) sound output. In this embodiment, the sound

The time is reflected in the display. This only appears when multiple logical screens are the same as , , , , ', screen, such as ΡιΡ or PoP multi-screen configuration. If there is a logic screen, the screen is displayed, or the sound focus is not related = 匕 · screen, the sound focus will be assigned to the display screen itself. Any (10) heart that is related to the display screen under it month's will become a sound source. : The sauce curtain is the natural enhancement of the baseline HAVi model of HS(10)en, which is in the ''the final output combination of the device' (the fmal 〇utput c〇mp〇siti〇n 〇fa device) + readout device (device) As a "device" related to physical devices. This enhanced version is different from the conventional concept of logical disks. In a logical disk, a part of a physical disk is treated as if it had an independent disk. From the perspective of CAP application, the purpose of the logic screen is the same as that of the display screen. It has the current (non-multiscreen), HScreen, all standard properties and behaviors of the example, a set of preset screen backgrounds, image and image screen devices, A set of non-preset screen devices of the same type, one or more sets of coherent screen device configurations, the ability to automatically change a set of screen devices to establish a coherent screen configuration of these devices, and to determine a configuration template for a given screen device The best configuration of the special type of screen device. 29 200849990 pif M screen with its own, independent and regularized screen coordinates:: defined by the tomb wide line HAVi model. Logic screen is generally related to the display screen The normalized coordinate space of the display ^ logic f screen on the display screen can be reflected to the rectangular screen in the 5th (4) of the age screen red. Although the explanation is convenient for explanation, the display area is a rectangular screen here, the present invention It is not limited to this. - When the pair of two normalized coordinate spaces has been identified, this rectangular screen (referred to below as the display area) may collide with the entire display screen. Alternatively, this rectangular screen may be phased. A part of the display screen. In this case, the display area may be entirely contained in the visible area of the display screen, or the entire display area outside the display area of the display screen. Alternatively, the rectangular screen may be interchangeable with the display screen. And non-visual (external) parts. If some parts of the display area are strengthened to the outside of the visual display area of the display screen (ie, the external rectangular screen [0,0][u] of the screen is displayed), the area can be selected. The display area of the display screen is sandwiched from the outside. Each logical screen has a set of preset screen devices, each of which is represented by a special subtype 'Hbackgrounddevice, , , HVide〇Device, or 'HSGragphicsDev Example of fHScreenDevice' for ice1. In addition, similar to the baseline HAVi model, each logical screen can have a set of additional non-preset screen devices of each subtype. 'As for the baseline HAVi model, the underlying screen device resources used by the logic screen are passed through 'HScreenDevicd The standard subtype of the level is taken into account, and each screen device has its own set of configuration parameters, which are defined by the HAVi model and represented by the standard subtype 30 200849990 27131pif of the ^HScreenConfigurationf class. For example, 'one of these parameters is determined by the template preference setting 'HScreenConfgirationTemplate.PIXEL-RESOLUTION1' and is accessed using the helper function fHScreenDevice.getPixelResoluti〇n(y.) The non-multiple screen implementation of the 'HSCreenDevice in the baseline HA Vi model. 'Example, this parameter is also rendered and accessed through the same method when referring to the screen device of the logic screen. ^ Π77

隹 Γ疋 / Γ疋 邂 邂 萤 . . . . . . . 直 直 直 直 直 直 直 直 直 直 直 直 直 直 直 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑 逻辑. Finally, the pixel resolution of the Logic 2 screen device is indeed reflected by the second-order coordinate space mapping to the normalized screen coordinate space of the display screen. However, applications that are using this 2 screen do not need to recognize the second-order conversion 'because from the logical processing = see 'this logic screen is different from the real output display device's final output signal screen's normalized screen coordinate space 盥 manifestation screen coordinates In the space, the object _ is paired, the bottom = the map pair, is defined as the logical map pair (10) ★ under the series called the display without special hardware to achieve this pair. 'i', ie 'MSM implementation does not need to - display a single _== of the screen, and a set (internal) is designed for this single-dimensional coherence and 2 order. , /, in this group of screen devices will limit the limit, if some groups of 连 连 连 规则 应用 应用 应用 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 2008 Μr m _ larger group camp curtain); set = set to see these pheromone coherence rules. The clothing-and-eight-shoulder, Z-order can also be applied. That is, the order; (7) the logical screens will be interlaced with each other. In the screen, the (screened) screen device is not (hardware)::: indicates whether the screen is displayed by logic or physical screen. This entity showing the % of the screen is called the given <logical image output 埠 association . Through the mapping to direct === connected to the image wheel out of the stick, flexible, MSM ^ i like the wheel out of the display screen. However, in both cases /, it can be indirectly related to the image rotation I 璋: (1) when the logic screen can be directly related to the image wheel out of the screen but can be regarded as: egg: that is not reflected to any display Related to the image feed f. = vertical operation (in this case, when it can be directly sourced and thus indirectly, it can be regarded as the image output of the screen, and the same - image wheel is out. Knowing and additionally directly related to the other. Also, the above two cases will be inserted separately under the opportunity to be attached to the content is being digital image photography service situation, and it needs to simultaneously output this content to 200849990 27131pif force one shirt Γ output 埠For example, 1394 or Curry. The 3 series of the screen is for the multi-screen configuration to display the display to the μ. It is better that the pip logic screen can be straight, ... the shirt is like a wheel, such as 1394 or NTSC埠. The screen will be indirectly related to the sound output, through

The image output of the screen 埠, or (7) is directly related to the other image output =1 of the =1 shirt image output 埠. When multiple logic screens are mapped to the display screen, generally only the same - (4) series can provide the source. This logic can be specified as a non-screening sound focus screen, as determined by the 'MutiSc job C〇nfigUrabieContext assignAudi〇F〇cus() method. Since a single logic screen can have multiple sources, which are derived from the preset 'HScreenDevice' example and non-preset examples, it is better to control which two: The example provides a combined sound output of the logic screen. These sources can be determined using the 'MultiScreenConfigurableContext.add, removeAudioSources(··)' method. The "screen" category will now be explained. Each screen in the multi-screen configuration is assigned to one of the following scheduled screen types or one of the platform-related categories beginning with "χ-": fNone(SCREEN-CATEGORY-NONE),, Oisplay(SCREEN-CATEGORYJDISPLAY ),, ,Main(SCREEN—CATEGORY-MAIN),, 33 200849990, fPiP(SCREENJ:ATEGORY—PIP),,

ToP (SCREEN-CATEGORY a POP),,

Overlay (SCREEN a CATEGORY-OVERLAY)', and • GeneraKSCREEN-CATEGORY-GENERAL). These screen types can be officially defined as the enhanced ''string'' given by the above-mentioned fMultiScreenConfiguration 'blocks'. When no special types are applied, the screen can be classified as σ 'SCREEN-CATEGORY-NON, The 'Screen Identifier' will now be explained. Each discernible group of screen resources that collectively display or logic screens will specify a unique (string) identification code, uniquely, at a certain _, ,, Access all f-screens through all active multi-screen configurations. ^Shi: Expands all non-active multi-screen groups including a certain time_有==关敎吨减平台操作 (during cold boot) The dynamic dynamic of the screen is added to the _ real minimum unique model _^% of the identification code 'this identification can maintain the above screen configuration. Included in each platform display 7^ multi-screen configuration and each display will take the initiative to]V [S]J screen 4 inch special (usually but not necessarily suitable) sub-group curtain, if marked; = environment = meaning, these show multiple logic _ of the inner two 200849990 2713 lpif show multi-screen configuration 'and It can be implemented by using %1111: 丨8〇^611€〇11; The 1^1^〇11' interface is set by the MSM of the interface, and the 'getConfigurationType()' method of this interface will return 'MultiScreenConfiguration.SCREEN—CONFIGURATION—D ISPLAYf. Currently active multi-screen configuration for each platform can utilize fMultiScreenManager .getMultiScreenConfiguration〇, to get 'and use? MultiScreenManager.setMultiScreenConfiguration〇 to build. In addition, for each display screen that is added to the platform multi-screen configuration, there is a special (existing) logic screen that is currently active on the display screen. A (usually appropriate) subgroup such that if the logical screen is marked as visible, it simultaneously presents its content or can present content from one or more service contexts or media players. Subgroups of such logical screens It is called "display multi-screen configuration" and is obtained by MSM using an object that can implement ']\4111 dip (^611 (^011 he 11 me 11 〇] 1' interface. This 'MultiformConfiguration' interface 'getConfigurationTypeQ' The value returned by the method is not! MultiScreenConfiguration.SCREEN^CONFIGURATION^ D ISPLAY’. The current active display multi-screen configuration for the special display screen can be obtained using the MultiScreenContext.getMultiScreenConfiguration()' method and created with ?MultiScreenConfigurableContext.setMultiScreenConfigurati 35 200849990 on. All accessible display multi-screen configurations (which can be used by special display screens) can be obtained using 'MultiScreenContext.getMultiScreenConfigurations()'. All accessible and usable multi-screen configurations (which may be currently in use or not in use, and configured for the platform or each display multi-screen) can be obtained using 'MultiScreenManager.getMultiScreenConfigurationsO'. For each un-terminated OCAP application, the underlying resources of a 'HScreen' of some active multi-screen configurations of the currently active multi-screen configuration screen must be the same as (equal to) the default screen of the 〇cAP application. resource of. Each screen group designed for multi-screen configuration will specify one of the preset configuration types or platform-related configuration types starting with "X-". Multi-screen configuration types include: Display (SCREEN-CONFIGURATION_DISPLAY), Non-PiP (SCREEN-CONFIGURATION NON PIP), PiP (SCREEN-CONFIGURATION J>IP), PoP (SCREEN-CONFIGURATION JPOP), and General (SCREEN-CONFIGURATION— GENERAL). These configuration types are defined by the enhancements, strings, and enumerations of the above special fields in the 'MultiScreenConflguration' interface. The multi-screen configuration specifies one of its accessible screens as the default service context related screen. In the absence of multiple special related information, this screen is used to determine the default association between the service situation and the screen. Each preset multi-screen configuration type defines a special screen for its initial preset service context-related screen. After the platform is powered on, the preset service context related to the multi-screen configuration can be changed using fMultiScreenConfiguration.setDefaultServiceContextScreen(. •)f. The preset service context related screen for multi-screen configuration can be obtained with fMultiScreenConfiguration.getDefaultServiceContextScreen() '. For more information, the 'MultiScreenManager.setMultiScreenConfiguration(··), ?MultiScreenConfigurableContext.setMultiScreenConflgurati οη(··)' and especially the 'serviceContextAssociations' parameters of these methods will now be explained. The preset multi-screen configuration includes preset multi-screen configuration and preset display multi-screen configuration for each platform. After a cold boot (or reboot) of an MSM enhanced version of the OCAP host device, the preset (initially active) multi-screen configuration of each platform must be the same as the multi-screen configuration that was active prior to cold boot. If you do not know the previous screen multi-screen configuration, then preset multiple screen configuration for each platform must be

TMultiScreenManager.getMultiScreenConfigurations(SCREE !^^0 仰圯1^八11(^-〇]^1^^〇, the first multi-screen configuration returned, which is related to the display screen, then, related to 'SCREEN A multi-screen configuration for each CONFIGURATION-NONJPIP' configuration type. Similarly, presets for each display screen for multiple screen configurations on each platform. 37 20084993⁄4 (Initially active) Each display multi-screen configuration is required Same as the multi-screen configuration active before cold boot. If you do not know the previous screen multi-screen configuration for the display screen, it must be 'SCREEN-CONFIGURATION_NON_PIP, the first multi-screen configuration of the configuration type, It is returned by fMultiScreenContext.getMultiScreenConfigurations(SCREE N-CONFIGURATION-NQNJPIP) on the display screen.

When performing other types such as (non-cold) reboot, restart or reset of the OCAP host device or OCAP environment that can implement MSM Plus, the preset (initial boot) multi-screen configuration must be the same as in non-cold restart , multi-screen configuration that is initiated before reboot or environment reset. The definition of "screen device," will now be explained. HScreeW represents a single independent image output signal from the device. Devices with multiple independent image output signals must be supported, HScreenDevice, multiple instances of the level. The image output signal is established, The total contribution of the HScreenDevice, the number of built-in objects of the level, can be 'HGraphicsDevice, object, HVide〇Device, object 盥^Hbackgrcmnddevicei object. Given, HScreen, quantity Any object, as long as AH is connected. However, the number of certain _ objects of the agreement. At present, there is a case that can be reasonably expected. 'Hbackgrounddevicef level represents the final background of the screen, also the background color and background image. The background is The final scene of the image _ 彡 combination stack may cover the entire area of the screen. When the device supports the banquet application (or even the window administrator), the background will not be restricted by any of the 2008 200849990 2713 lpif specific applications or windows. The power to control the background of the screen is a scarce resource, and its management is as above. liGraphicsDevi The cef level describes the specific, HScreen, available graphics device. Each HGraphicsDevice has one or more fHGraphicsConfiguration objects associated with 'HGraphicsDeviceT. These objects define different configurations (settings) that can be used with 'HGraphicsDevice'. 'HVideoDevice' level description A logical image device that facilitates the appearance of a particular screen. Each TIVideoDevic〆 has one or more 'HVideoConfiguration' objects associated with 'HVideoDevice.' These objects can be defined using different configurations (settings) of 'HVideoDevice'. 'HVideoDevice, Level The representative only presents the image 'and does not provide a choice of images to be rendered. 'HscreenDevice' level, 'Hbackgrounddevice' level, fHGraphicsDevicef level, and 'HvideoDevice, level condensed in the forg.havi.uif suite of the HA Vi user interface. The level fHbackgrounddevice' enhances 'HScreenDevice'. The 'Hbackgrounddevicef level describes the background device represented by the object inherited by the 'HScreenDevice' level. The common level 'HGraphicsDevice' enhances 'HScr eenDevice’. The fHGraphicsDevice’ level describes the graphics device represented by the object inherited by the fHScreenDeviceT level. The public level 'HVideoDevice' enhances 'HScreenDevice'. ▼HVideoDevice1 level describes the image device represented by the object inherited by the 'HScreenDevice' level. 39 200849990 2713 ipif will now explain "changing multi-screen configuration". The current multi-screen configuration can be restricted by the application (fMonitorAppPermission(''multiscreen.configurationf')f), using some of the display's fMultiScreenManager, or the fMultiScreenConfigurableContext? interface's fsetMultiScreenConfiguration(..)f

¢:

YequestMultiScreenConfigurationChangeG·)’: ^^:. It must be noted that the current multi-screen configuration can be changed by the host device itself, which is caused by other events not defined by the present invention. For example, the manufacturer can provide a remote control button that activates a specific multi-screen configuration. No matter what causes the current multi-screen configuration changes, the following conditions are established: 1. Before using the change, use the underlying preconditions; 2. During the change, use the change process steps in the end, during which time In the end, the dynamic state is invariant; 3. After the change, the underlying condition is used. In order to enhance interoperability, several pre-conditions and post-conditions are in the form of 24A~24C and Figure 25A~25E's 'Starting (ASSERT), state virtual code. Figure 24Α~24C and Figure 25Α~25Ε are restricted to appear underneath. In order to avoid confusion, in the case of contradictory situations or coding forms, the following will take precedence over the codes of Figures 24Α~24C and Figures 25Α~25Ε. Under this priority condition, Figs. 24A to 24C and Figs. 25A to 25E are applied to determine the interoperability of the MSM enhanced version. The preconditions for changing the multi-screen configuration will now be explained. 40 200849990 27131pif Before the fMultiScreenConfigurationEvent.MULTI—SCREEN—CONFI GUHATION-CHANGING’ event caused by a multi-screen change, the underlying precondition is used. It must comply with the definition of 'Quiescent State Invariants'. The change processing steps will now be explained. The MSM implementation must perform the following steps to effectively change the current multi-screen configuration. L produces 'MultiScreenConfigurationEvent.MULTI a SCREEN a CONFI GURATION-CHANGING, event to spread the application. 2· At this point, until the generation of ▼MultiScreenConfigurationEvent.MULTI—SCREEN-CONFI GURATION_CHANGED', the OCAP application is not allowed to (1) change the current multi-screen configuration, (2) retain 'HScreen^fHScreenDevice' and its underlying resources, or (3) execute The screen device configuration changes or the multi-screen screen status changes. 3. For each OCAP application that has allowed 'MonitorAppPermission(nmultiscreen.configuration'')', use any of the pre-stored 'MultiScreenConflgurationListener%fnotify()' methods to provide ▼MultiScreenConfigurationEvent.MULTI as a SCREEN-CONFI GURATION —CHANGING's argument. 41 200849990

Li lJipif All such temporary listeners must be called before proceeding to the next step. However, before proceeding, the MSM implementation does not need to wait for the listener to return the 4 certificate (^ method. 4. For its 'MultiScreenContext, the access status will be changed because of changing the multi-screen configuration of the 'HScreen' In other words, if the fHScreen's shovel is not called by fsetMultiScreenConflguration ("the y method is reserved by some OCAP applications, or if the change is due to the initial change of the host device (the CAP application does not explicitly call this method), the 〇cAP If the application {" is reserved, then for the reserved 'HScreen, the represented ▼HScreenDevice1, and the delayed notification generated 'HScreenDeviceReleasedEvent', call the 'releaseDevice()' method, and if necessary, the call keeps the reservation. 'ResourceClient''s 'releaseO' method. 5. For 'HScreenDevice' whose access status will be changed due to changing the current multi-screen configuration, if fHScreenDevicef is currently not called I 'setMultiScreenConfiguration(·· ), some OCAP applications of the method are retained or changed here Because the host device is initially changed (the OCAP application does not explicitly call this method), it is reserved by the OCAP application. For 'HScreenDevice', delay the notification of the generated HScreenDeviceReleasedEvent', call the freleaseDevice()' method, and if necessary , the beer is called to keep this reserved 1^30111^^(31丨6111: ''release()' method. 6. For any of its 'HScreenConfiguration' access status will be because 42 200849990 2713 lpif changed k current multi-screen group The status of the 'HScreenDevice, which is changed, and the delay and related fHScreenConfigurationEvent' is notified. For any 'HScreen' whose 'MultiScreenContext' access status will be changed because of the current multi-screen configuration , Generated day: Change ^1·- related 'MultiScreenContextEvent' notification. 8. If the 'n〇tify()f method has been called ▼MultiScreenConfigurationListener in step (3), it has not been returned yet, it has been waiting

Until (1) all 'notify〇f methods have been returned or (2) from the first call of this method, at least 5 seconds but no more than 30 seconds. 9. Execute all necessary changes to meet the conditions of the bottom post. 10. For each fHScreenDeviceReleasedEvent' generated in the above manner and sequence, each 0CAP application calls the ?statusChanged()' method of the fResourceStatusListenerf that has been temporarily stored, which is too controversial as 'HscreenDeviceReleasedEvent'. 11. For each ▼HScreenConfigurationEvent' generated in the above manner and sequence, each OCAP application calls the 'report()' method of any stored fHScreenConfigurationListener' as the argument for ▼HscreenConfigurationEvent▼. 12. For each 'MultiScreenContextEvent' generated in the above manner and in sequence, each OCAP application beer calls any 'temporary 丨MultiScreenContextListener' ''notify〇' method as a 'MultiScreenContextEvent' argument. 13. Generated for spreading applications

▼MultiScreenConfigurationEvent.MULTI—SCREEN—CONFI 43 200849990 27131pif GURATION—CHANGED’ event. 14. For each OCAP application, call the fnotify()' method of any pre-stored MultiScreenConfigurationListener' as a MultiScreen-ConfigurationEvent.MULTI_SCREEN_CONFI GURAUON-CHANGED% argument. The "post-conditions for multi-screen configuration changes" will now be explained. After the fMultiScreenConfigurationEvent.MULTI^SCREEN^CONFI GURATION_CHANGED' event due to a multi-screen configuration change, the following postconditions are required: 1 1Quiescent State Invariants' as defined below. 2. The current multi-screen configuration is a new configuration 3. The new preset screen must be identical to the old preset screen. 4. If the preset background screen is present in the old Multi-screen configuration and preset screen in new multi-screen configuration, unless the application issues "1" for 'allowjlefault-device-reconfigf: a·The new preset background device must be the same as the old preset background screen The device and the new preset background device must have the same screen area as the old preset background device, and the pixel resolution is proportional to the pixel size. If the application issues "1" for 'allow-default_device_reconfig, and If the background screen device exists in the old multi-screen configuration but does not exist in the new multi-screen configuration, then the reference to the old preset background device It is necessary to reset the background screen to be equal to empty. 44 200849990 27131pif 5·If the preset image screen device exists in the preset screen in the old multi-screen configuration and the new multi-screen configuration, unless the application is issued as “1, ' alio w_default—device a reconfig 丨: a · The new preset image screen device must be the same as the old preset image screen device; and b · the new preset image screen device must have the same screen as the old preset image device Area, pixel resolution and pixel size ratio.

If the application issues 'allowjiefaulLdevicejeconfig' as '1', and the default image screen device exists in the old multi-screen configuration but does not exist in the new multi-screen configuration, the reference to the old preset image device must be reset to equal Empty video screen device. 6. If the preset graphic screen device exists in the preset screen of the old multi-screen configuration and the new multi-screen configuration, unless the application issues the 'allow-default one device one reconfig,: a The new preset graphic screen device must be identical to the old preset graphic screen device; and b. The new pre-right-shaped graphic device must have the same screen area as the old preset graphic device, the pixel resolution and the pixel size. ratio. If the application issues "1", allQW_default_deviee__ and the default_screen device exists on the 0-screen, but there is no multi-screen configuration towel, the reference of the old preset_device must be reset to the empty graphic device. . $ 7. Yes? In the reconfiguration face _ any face (4) reference, if it is no longer 疋 non-preset fluorescing, then it must be "empty m 45 200849990 iVIJlplt can not be equal to the empty screen. Any non-preset screen device reference obtained before configuration, if it is no longer a non-preset screen device, it must be equal to the empty screen device, otherwise it cannot be equal to the empty screen device. Now explain 'Quiescent State Invariants'.

fMultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION—CHANGING’ before the event and related

After the fMultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION-CHANGED' event, it must be kept unchanged: 1. There must be a current and constant multi-screen administrator; 2. There must be a current and constant multi-screen multi-platform group dimension; · For each display screen, it is necessary to have a multi-screen configuration; monthly 'J and constant display 4, must have a non-empty and constant accessable multi-fire

5. The current multi-screen configuration of each platform must be able to save for appropriate authorized applications); , ', heart (for 6 · each of the current display multi-screen configuration must be (for appropriate authorized applications);疋Accessible configuration 7·In the multi-screen configuration of each platform, the screen group must be unchanged; - There is - not empty and 8 · In each of the current display multiple screen group green, empty And the same set of screens; there must be a non-nine current multi-screen configuration of the various screens in the multi-screen configuration instead of empty; 46 200849990 27131pif 10. In each of the current display multi-screen configuration The screen must not be empty; 11. Any two different screen items in any current multi-screen configuration cannot represent the same negative source, 12 must have a current preset screen; 13. The current preset screen cannot be empty Screen; 14. In some current multi-screen configurations, a screen project must represent the same resources as the default screen; 15. There must be a set of non-empty accessible screens; 16. The current default screen must be Access to an explicit member of the screen group; 1 7. At present, any background screen device of the preset screen cannot be equal to an empty background screen device; 18. Any image screen device of the current preset screen cannot be equal to an empty image screen device; 19. Any graphic screen device of the current preset screen cannot be Equal to an empty graphics device. Now I will explain 1 Dynamic State Invariants1. After the MultiScreenConfigurationEvent.MULTI-SCREEN-CONFI GURATION-CHANGING' event and related

, MultiScreenConfigurationEvent.MULTI A SCREEN-CONFI GURATION-CHANGED, before the piece must be kept unchanged. · 1 · There must be a current and unchanged multi-screen administrator; 47 200849990 ^ IU l pif 2. There must be a current but Multiple screen configurations may be changed; 3. There must be a non-empty but possibly variable accessible multi-screen configuration group; 4. The current multi-screen configuration must be accessible; 5. The multi-screen configuration must have a non-empty but possibly changing set of screens; 6. The screen in the current multi-screen configuration must not be empty; 7. Any two screens in any current multi-screen configuration The project cannot represent the same resources; 8. There must be a preset screen that is currently possible but may change; 9. The screen is currently not available for the screen; 10. In some current multi-screen configurations, there is a screen project required. Represents the same resources as the default screen; 11. There must be a set of accessible screens that are not empty but may change; 12. The current default screen must be an explicit one in the accessible screen group. Assume Any background screen device of the screen shall not be equal to an empty background screen device; 14. Any image screen device of the preset screen may not be equal to an empty image screen device; 15. Any graphic screen device of the current preset screen may not be equal to an empty graphic screen. Device. An enhanced version of the baseline HAVi model to which the present invention is applied will now be explained. Multi-screen administrators need to use some of the baseline HAVi model enhancements. 2008 200890 90 2713 lpif behavior and use, especially HAVi definition types:, HScreen,, HScreenDevice', , HScreenConfiguration,, fHScreenConfigTemplate' and 'HVideoDevice,. As described above, each of HSCreen' features a display screen or a logic screen defined by a multi-screen administrator. Multi-screen manager for 'HScreen' and the underlying resources it represents

Can be distinguished. In particular, the underlying state associated with 'HScreen' may change temporarily. That is, the following may be temporarily changed: the number of underlying background screen devices, the screen device configuration (parameter setting) of these underlying background screen devices, the underlying background screen device associated with the preset fHbackgrounddevice', and the number of underlying image screen devices. The screen device configuration (parameter setting) of these low-level image screen devices, the number of underlying image screen devices related to the preset 'HVideoDevice, the number of underlying graphic screen devices, related to the preset, the underlying graphic screen device of HGraphicsDevicef, these bottom layers Screen device configuration (parameter setting) of the graphic screen device. Each 'HScreen' must implement the fMultiScreenContext' interface, or if 'HScreenf represents the underlying screen resource configurable according to the function defined by fMultiScreenConfigurableContext', then fHScreen' must implement the 'MultiScreenConfigurableContext' interface instead of implementing the 'MultiScreenContexf interface' (note) , the 'MultiScreenConfigurableContext' interface is the child interface of the 'MultiScreenContext' interface). fHScreen.getHScreens()f static method with 49 200849990 Z/iJipif

MultiScreenManager.getInstance().getScreens() will return the same value. The HScreen.getDefaultHScreen() static method and 'MultiScreenManager.getInstance().getDefaultScreen〇' will return the same value. The Oefault HScreen Assignment’ will now be explained. When the application is initially launched, the application must first be related to a set of accessible screens that may be returned by fHScreen.getHScreens (y, then specify the default fHScreen' according to the underlying rules, if the first rule is used, The rest will be omitted. 1. If 'ServiceContext', 'SC' (application will select it, Service') is only related to one (bottom) screen, then this screen will be used as the default screen. 2) Otherwise, if " SC" is related to the multi-layer (bottom) screen, if one of these screens is classified as the main screen 'that is, fgetScreenCategory()' returns 'MultiScreenConfiguration.SCREEN-CATEGORY MAIN1', the screen will be returned by fHScreen.getHScreens()' The main screen appearing in the array acts as a preset screen. 3. Otherwise (no one in the multi-screen is the main screen), the first screen appearing in the screen array returned by fHScreen.getHScreens〇' is pre- Set the screen. MSM imports a specific 'HScreen' that is known to be empty fHScreenf, which is a unique invariant of ^HScreer^, which is used to establish (usually non-empty) ^HSc The defined and known state of reeW. The empty 'HScreen', referred to below as "ES", must meet the following conditions: 50 200849990 27131pif 1. In the scope of application reference, "ES" is unique (object); ''ES' implements the following interfaces: 'MultiScreenContext', 'MultiScreenConfigurableContext', fResourceProxyf and fResourceServer?; 3. fES.getDefaultHbackgrounddevice()! It is necessary to return 'Hbackgrounddevice' with a status equal to the empty 'Hbackgrounddevice' defined below. fES.getDefaultHVideoDeyice()f must return 'HVideoDevice', its status is equal to the empty fHVideoDevice defined below. Defined below; 5. fES.getDefaultHGraphicsDevice()f must return fHGraphicsDevicef, its status is equal to the empty fHScreenDevicef defined below ; 6. fES.getBestConfiguration(HBackgroundConfigTemplate hbc)f Required to return? ES.getDefaultBackgrounddevice〇.getBestConfiguration(hbc ),; 7. ES.getBestConfiguration(HVideoConfigTemplate hvc)f Required to return? ES.getDefaultVideoDevice().getBe stConfiguration(hvc)f ; 8. fES.getBestConfiguration(HGraphicsConfigTemplate hgc)f must return 'ES.getDefaultGraphicsDevice().getBestConfiguration(hgc)'; 51 200849990 2/13ipif 9. fES.getBackgrounddevices()?Required return, ne ~ Hbackgrounddevicef 1 ] {ES .getDefaultHbackgrounddeviceO}f ; 10. fES.getVideoDevices()? Required backhaul, ne^ HVideoDevice[l] {ES.getDefaultHVideoDevice()}f ; 11· fES .getGraphicsDevices()f Required to return HGraphicsDevice [l] {ES.getDefaultHGraphicDevice()}!; 12. rES.getCoherentScreenConfigurations(..), i^ need to return, null (null)'; 13. 'ES.setCoherentScreenConfigurations(··)' must return fHConfigurationExceptionf ; f((MultiScreenContext)ES).getScreenType()fii6 ^ ^ pass, MultiScreenContext.SCREEN_TYPEJLOGICAL,; 15. '((MultiScreenContext)ES).getDisplayScreen()' must be returned fnuir; 16· f(( MultiScreenContext)ES).getDisplayArea()' must be returned, null,; 17. f((MultiScreenContext)ES).getOutputPorts()' must be returned fnull'; 18. f((MultiScreenContext)ES).getServiceContexts()' must return fnew ServiceContext[0]'; 19· '((MultiScreenContext)ES).getVisible()' must be returned, false '; 20· '(( MultiScreenContext)ES).getZOrder()' must be returned 52 21. 200849990 27131pif '((MultiScreenContext)ES).addScreenContextListener()' can not produce any marginal effect; 22. !((MultiScreenConfigurableContext)ES).setDisplayScreen(..) • It is necessary to pass back 'IllegalStateException' unless 'SecurityExceptionf' is applied;

C 23· f((MultiScreenConfigurableContext)ES).setDisplayArea(··)' must return 'IllegalStateExceptionf unless '*Security Exception' is applied; 24. '((MultiScreenConfigurableContext)ES).setVisible(··)' must be passed back' IllegalStateException ', unless 'SecurityException' is applied; 25. I, '((MultiScreenConfigurableContext)ES).setZOrder(··)' must return 'IllegalStateException' unless 'SecurityException' is applied; 26. '((MultiScreenConfigurableContext)ES). addOutputPort(")f must pass back 'IllegalStateException' unless 'Security Exception' is applied; 27. !((MultiScreenConfigurableContext)ES).addSeryiceContext(.. 53 200849990 27131pif )' must be passed back 'IllegalStateException' unless 'SecurityException' is applied 28; '((ResourceProxy)ES).getClientC» needs to pass back |111111'. If from the underlying resources, two fHScreenDevicef ("SDr' and "SD2") are equal, ie if ^]1^ ^^0111^5(8〇1,8〇2)|Return 'true', then SDl.getIDstring (), and, SD2.getIDstring (), will return the same value, otherwise 'SDl.getIDstring () f the' SD2.getIDstring () f will return the same value. The OCAP application attempts to reserve fHScreenDevicef (its underlying screen device resources are not fully contained in the underlying screen device resource group referenced by the current active multi-screen configuration) and will issue an fHPermissionDeniedExceptionf. The above conditions are to avoid applications to preserve scarce device resources, and their resources are not included in the underlying resource group represented by a current active multi-screen configuration. This situation can be applied to screen device resource partitioning between active multi-screen configuration and inactive multi-screen configuration. The 'Default HScreenDevice Assignment' will now be explained. The preset group of accessible screen devices is assigned to the application, and the preset screen is designated as described above. Once the 'HScreen' preset is set, the "S" (specified to the default screen for this application) will be determined as follows: fS.getDefaultHbackgrounddevice()f9 'S.getDefaultHVideoDeviceQ1 and 丨 S.getDefaultHGraphicsDeviceQ 丨. If the preset screen has multiple screen devices of a particular type, then it is determined which screen devices of the screen devices are the specific types of presets of the screen 54 200849990 2713 lpif screen device must remain platform-dependent, and such designation is not possible Related to interworking applications. The MSM imports a subsequent subtype: 'Hbackgrounddevice', a specific group of 'HVideoDevice' and an empty fHScreenDevice' defined by 'HGraphicsDevice'. These examples, referred to below as "ED", must satisfy the following conditions, except for the subtype-specific conditions defined below: 1. 'ED.getlDStringO' must return an empty string ""; 2. ?ED.getScreenAspectRatio( )! Must be returned 丨new

C

Dimension()f ; 3· 'ED.addMultiScreenConfigurationListener(··), can not produce any marginal effect; 4· 'ED.reserveDevice(ResourceClient)丨 must be returned, ^,; 5. fED.releaseDevice()f can not be generated Any marginal effect; 6· 'ED.getClient〇' must return 'null,. These empty 'Hbackgrounddevice, hereinafter, EBD,,, must meet the following conditions: I 1 · Within the scope of the application reference, "EBD" is a unique (object) example; 2. EBD must satisfy the above empty fHScreenDevice, the specified condition; 3· 'EBD.getDefaultConfigurationQ' must be returned to the empty 'HbackgroundConfiguration', as defined by the bottom; 4· fEBD.getCurrentConfiguration〇's return value must be the same as fEBD.getDefaultConfiguration()'; 5· fEBD.getBestConflgumtionC·), the return value must be the same as 55 200849990 2/ijipif !EBD.getDefaultConfiguration〇,; 6· fEBD.getConfigurations()f must be returned fnew HBackgroundConfiguration[l] {getDefaultConfiguration()}f ; 7. fEBD.setBackgroundConfiguration()f must pass back 'HConfigurationException' unless 'SecurityException' or 'HPermissionDeniedException' is applied. The empty fHVideoDevice', referred to below as 'EVD', must meet the following conditions: 1. Within the scope of the application reference, ''EVD' is a unique (object) example; 2. "EVD" must be satisfied by the above-mentioned empty fHScreenDevicef The specified condition; 3· fEVD.getDefaultConfiguration()' must be returned to the empty 'HVideoConfigurationf, as defined below; 4. The return value of 'EVD.getCurrentConfigurationO' must be the same as 'EVD.getDefaultConfiguration()'; 5· fEVD The return value of .getBestConfiguration(·,)' must be the same as Cy fEVD.getDefaultConfiguration()f; 6. fEVD.getConfigurations()f must return 'new HVideoConfiguration[l] {getDefaultConfiguration()}f ; 7. Έ VD Set V ideoConfiguration()f must issue 'HConfigurationException' unless applied, fHPermissionDeniedException'. An empty fHGraphicsDevic&, called fEGD' below must meet the following conditions: 56 200849990 27131pif 1· Within the scope of the application reference, ''EGD' Is a unique (object) example; 2. ''EGD' must be met by the above empty 'HScreenD Evice, the specified condition; 3. fEGD.getDefaultConfiguration〇f must pass back empty fHGraphicsConflguration', as defined below; 4/EGD.getCurrentConfiguration()' must have the same return value as ▼EGD.getDefaultConfigurationO,; 5/ The return value of EGD.getBestConfiguration(··)' must be the same as ?EGD.getDefaultConflguration()T ; 6/EGD.getConfigurations〇, must be returned, new HGraphicsConfiguration[l] {getDefaultConfiguration〇}-; 7/EGD.setGraphicsConfiguration ()f must issue ▼HConfigurationException' unless it should or ▼HPermissionDeniedException'. MSM imports the specific, group of sub-types fHBackgroundConflgurationf, fHVideoConfiguration', and 'HGraphicsConfiguration', null ▼HScreenConfiguration'. The empty 'HScreenConfiguration', referred to below as "EC", must meet the following conditions, except for the sub-type specific conditions defined below. · 1· 'EC.convertTo(")▼ must return 丨nuu,; fEC.getFlickerFilter()' must be returned, false,; 3, fEC.getInterlaced()' must be returned, false,; 4' 'EC.getOffset(··), must return hewDimensionO,; 5; EC.getPixelAspectRatio ()f must be returned fnew 57 200849990 2713 Ipif

Dimension()f ; 6.?EC.getPixelResolution()f must be returned, new Dimension()f ; 7;EC.getScreenArea()f must be echoed, new HScreenRectangle(0,0,0,0)’. The empty 'HBackgroundConfigurationf, hereinafter, must meet the following conditions: 1. Within the scope of the application reference, fEBC is unique (object); 2. TEBC must satisfy the conditions defined by the empty 'HScreenConfiguration'; 3. fEBC. getDevice()! It is necessary to pass back the empty 'Hbackgrounddevicef, as above; 4. 'EBC.getConfigTemplate〇' must return the empty fBackgroundConfigTemplate' as described below; 5. 'EBC.getColor()' must be passed back' New Col〇r(0,0,0),; 6. EBC.setColor() must issue HConfigurationException'. The empty 'HVideoConfiguration', hereinafter referred to as EVC, must meet the following conditions: 1. Within the scope of the application reference 'fEVC is a unique (object) example; 2. fEVC' must satisfy the empty 'HScreenConfiguration', specified conditions; 3. 'EVC.getDevice()' must be returned to the empty 'HVideoDevice, as defined above; 4. fEVC.getConfigTemplate()f must be returned to the null 58 200849990 2713 lpif 'HVideoConfigTemplate', as defined below. The empty 'HGmphicsConflguration,, hereinafter referred to as £(3:::, must meet the following conditions: 1. Within the scope of the application reference, EGC' is a unique (object) example; 2. EGC must satisfy the empty HScreenConflguration , the specified condition; 3/EGC.getDeviceO, must be returned to the empty, HGraphicsDevice, as defined above;

C 4. fEGC.getConfigTemplate()? It is necessary to pass back the empty fHGraphicsConfigTemplate' as defined below; 5. 'EGC.getA Logic Fonts()' must be returned, new:p〇nt[0],; 6/EGC .getCompatibleImage(Image input, HImageHints hints)' must be returned 4叩111:' ; 7. 'EGC.getComponentHScreenRectangle(··)' must be returned 'null'; 8. fEGC.getPixelCoordinatesHScreenRectangle(··)' Required l back Pass fnew Rectangle〇'; 9. 'EGCgetPunchThroughToBackgroundColor(··)' must return 1null'; 10. 'EGC.dispose(Color)' does not produce any marginal effects. MSM imports the settings specified by the empty 'HScreenConfigTemplate' of the subtypes 'HBackgroundConfigTemplate', fHVideoConfigTemplatef and ▼HGraphicsConfigTemplate▼. 59 200849990 27131pif The empty fHScreenConfigTemplate', hereinafter referred to as ET, must satisfy the following conditions, except for the special conditions of the subtype defined below: 1. .fET.getPreferenceObject(int)f must issue 'IllegalArgumentException'; 2.!ET .getPreferencePriority(int)f must be returned, HScreenConfigTemplate.DONT_CAREf ; 3/ET.setPreference(int9int)f

'IllegalArgumentExceptionf; 4·ΈT·setPreference(int,Object,int), must issue 'IllegalArgumentException'·empty fHBackgroimdConfigTemplate', hereinafter referred to as εβΓ , must meet the following conditions: 1. Within the scope of the application reference, 'ΈΒΤ' It is a special (object) example; 2. ΈΒΤ 'must meet the empty 'HScreenConfigTemplate', the specified condition; 3.fEBT.isConfigSupported(HBackgroundConfiguration)f must return 'false'. Empty 'HVideoConfigTemplate', below is called 'EVT ', must meet the following conditions: 1. In the application reference range, ''EVT' is a special (object) example; 2. 'EVT' must meet the conditions specified by the empty 'HScreenConfigTemplate'; 3. fEVT.isConfigSupported(HVideoConfiguration ) ' Must always return 'false'. 60 200849990 27l31pif Empty 'HGraphicsConfigTemplate', hereinafter referred to as EGT', must meet the following conditions: 1. Within the scope of the application reference, ''EGT' is a special (object) example; 2/EGT' must satisfy the empty 'HScreenConfigTemplate 'The specified condition; 3/EGT.isConfigSupported(HGraphicsConfiguration), must return 'false'. 『LivideoDevice will now be explained. If at least one image pipeline (including at least one image) is allowed using some of the mechanisms defined by the present invention. The decoder and a decoder format conversion unit are related to the underlying image screen device resources represented by HVide〇Device', and one of these pipelines is designated as a contributing image pipeline, while the rest are It is designated as an uncontributed image pipeline. The image pipeline or related sound information cannot be provided to the underlying image screen device resources represented by HVideoDevice'. The following rules determine that a group of possible contribution image pipelines are available. Contributed image pipeline: 1. If this group of possible contribution image pipelines In the middle, only one image official line is related to the active image basic stream of a non-summary service, then the image pipeline is the contribution pipeline; 2, otherwise, if this group of possible contribution image pipelines, there are multiple image officers The line is related to the active image elementary stream of a non-summary service, and the image pipeline that is selected by the non-summary service is the contribution pipeline. 3. Otherwise, if this group of possible contribution image pipelines, only one 61 2U0849990 This: i::,: media player controlled by a non-summary service, = ship_image t line is the contribution pipeline; image tube this group may contribute to the image pipeline, there are multiple moves (or pause) ^ The non-digest service media player, the last line is the green 3 (four)) of this media job 11 video tube

If this is the group's possible contribution to the image pipeline, only - ρ" 二二目' is a media player controlled by a non-summary service, 'the video pipeline of this media player is the contribution pipeline; This group of possible contribution image pipelines, there are multiple ~ image, s-line phase ^ media player for a non-summary service, then the media player is finally activated (or in the temporary (four) stop money is replied) The image camp line of i is the contribution pipeline; 7. Otherwise, the present invention does not define how to determine which image pipeline is a contributing pipeline, and this decision is related to the embodiment. When the embodiment of the present invention is based on an OCAP host device implementing OCAPMSM enhanced version, it will now be explained to ensure certain allowable conditions for the Xlet application. σ To call the method defined by the present invention, the application requires ▼MonitorAppPermissionC'multiscreen.configuration’'1 and / gas 'MonitorAppPermission (nmultiscreen.context''). In the implementation of OCAPMSM enhanced version of the OCAP host device, the following conditions must be considered to apply to the ']\4〇1111; 0 mouth? 61^11^5丨0111. 'multiscreen.configuration' can access and change the platform multi-screen and 62 200849990 2713 lpif state. Applications with this allow you to change the multi-screen configuration of the platform and discover and detect its dynamic state. ▼multiscreen·contextf changes the multi-screen status of the screen. With this allowed application, you can change the multi-screen status of the accessible screen. In addition, it is necessary to consider the enumerated symbol value types of the attributes of the focap:monitorapplicationf component type defined by the document type definition (DPD) defined by the permission request file (PDF) to include the following values ▼ Multiscreen.configuration' with 'multiscreenxontext'. Since the embodiment of the present invention is based on the Java system, it will now be defined, System Property. If the MSM enhanced version is implemented by the OCAP host device in this embodiment, the system property of the 〇r〇cap.api.option.msm'7ava must be defined by the relevant value of the implementation version of the present invention, and the version of the present invention is "〗. 〇·〇,,. Conversely, 'if the host device defines 〇Cap api 〇pti〇n msm' Java system attribute, the host device must implement the version of the invention associated with this attribute value. The signed and unsigned must be signed The application of this chapter allows reading of this attribute. An implementation of a Java system-based multi-screen administrator in accordance with an embodiment of the present invention will now be explained. 1A to 11G are used to explain the login of the java interface constant of the embodiment of the present invention. Figure 11ADD is a list of Java constants in the org.ocap.Ul.MultiScreenConfigurableContext according to an embodiment of the present invention. The constant is defined in 〇rg 〇cap Ui, kit 63 200849990 2/13ΐρΐΤ In 'MultiScreenConfigurableContexf, please refer to FIG. 13A to 13Fo. FIG. 11B shows Java constants in 'org.ocap.ui.MultiScreenConfiguration1 according to an embodiment of the present invention. Record the 歹1J table. The constant is defined in the fMultiScreenConfigurablej of the brg.ocap.ur suite, please refer to Figures 14A to 14C. Figure 11C shows the list of login buildings of the Java constant in 'org.ocap.ui.MultiScreenContext1 according to an embodiment of the present invention. The constant is defined in the fMultiScreenContextf of the f〇rg.ocap.uif suite, please refer to Figures 15A-15D. Figure 11D shows the login of the Java constant in 'org.ocap.ui.event.MultiScreenConfigurationEvent' according to an embodiment of the present invention. List. Constants are defined in '▼MultiScreenConfigurationEvent' of the '〇rg.ocap.uif suite, please refer to FIGS. 18A-18D. FIG. 11E shows Java in 'org.ocap.ui.event.MultiScreenContextEvent' according to an embodiment of the present invention. Uncle's login file list. Constants are defined in the 'MultiScreenContextEvenf' of the 'org.ocap.uif suite, please refer to Figures 20A-20D. Figure 11F shows a list of logins for Java constants in forg.ocap.uLevent.MultiScreenEvent' in accordance with an embodiment of the present invention. The constant is defined in %1111^(^611£¥6111^ of the f〇rg.ocap.uif suite, please refer to Figures 22A-22D. Figure 11G shows 'org.ocap.ui.event.MultiScreenResourceEvent according to an embodiment of the present invention. List of login files for Java constants within . The constants are defined in 64 200849990 2713 lpif rMultiScreenResourceEventf of the 'org.ocap.ui1 suite, please refer to Figures 23A to 23D. The multi-screen management platform behavior of the embodiment of the present invention will now be explained ( Semantics. An enhanced version of the forg.ocap.uif suite of the HA Vi user interface is explained with reference to Figures 12 to 16F. Figure 12 shows an interface list of packages forg.ocap.ui' according to the embodiment of the present invention. With a list of ratings.

The interface list 1200 of the Java suite 'org.ocap.ui' includes: fMultiScreenConfigurableContextf interface 1210, 'MultiScreenConfiguration, interface 1220 and 'MultiScreenContext, interface 1230. The "MultiScreenConfigurableContext" interface 1210 will be explained with reference to Figs. 13A to 13F; the 'MultiScreenConfiguration' interface 1220 will be explained with reference to Figs. 14A to 14C; the fMultiScreenContextf interface 1230 will be explained with reference to Figs. 15A to 15D.

The level list 1250 of the Java Suite forg.ocap.ui' includes the 'MultiScreenManager' level 1260. The 'MultiScreenManager' level 1260 will be explained with reference to Figs. 16A to 16F. Figure 13A shows the definition of the interface 'MultiScreenConfigurableContext' of the Java suite 'org.ocap.ui' in accordance with an embodiment of the present invention. The 'MultiScreenConfigurableContexf interface 1210 has fMultiScreenContextf M forg.davic.resources.ResourceProxyf as the super interface. This public interface ©fMultiScreenConfigurableContext' can be used to increase the 'MultiScreenContexf', 'org.davic.resources.ResourceProxyf'. The fMultiScreenConfigurableContext' interface 1210 provides a set of tools to accomplish the following: 1. Change the mapping of the logical fHScreenf to display 'HScreenf, which includes displaying the area on fHScreenf, where the logical fHScreenf will appear with its visibility and its Z order (in other 'HScreen'); 2. Change the Z order of 'HScreenDevice' with fHScreen'; 3. Change the association related to 'HScreenWYServiceContext'; 4. Change the association between display fHScreenf and related fVideoOutputPort; 5. Change the fHScreenDevice' group, The sound produced by it will constitute the sound source of 'HScreen'; 6. Change the current sound focus specification of display fHScreen'; 7. Retain and release the remaining underlying screen and screen device resources; 8. Get a reference to current resource customers, Its customers have reserved screens and their underlying resources; and 9· establishes the current active display multi-screen configuration for displaying fHscreenf. If 'HScreen1 is available for OCAP applications, and if HScreen can be configured with the functionality defined by the MultiScreenConfigurableContext' interface 1210, then the MSM implementation must support the 'MultiScreenConflgurableContext' interface on each such HScreen. The MSM implementation supports the fMultiScreenConfigurableContext interface 1210 on 'HScreen, which is not configured with the functionality defined by 66 200849990 27131pif fMultiScreenConfigurableContextf interface 1210. The established implementation of the 'MultiScreenConfigurableContext' interface 1210 does not need to support any or all of the defined configuration changes, but may only support specific configuration changes due to hardware or other restrictions. If the implementation of the 'MultiScreenConfigurableContext' interface 1210 does not support a particular configuration change, then attempting to make the change will result in the occurrence of an 'IllegalStateException', as described in the methods below. The 'MultiScreenConfigurableContext' interface 1210 is used by MSM 101. Figure 13B shows a list of fields of the interface 'MultiScreenConfigurableContexf' of the Java suite forg.ocap.ui', in accordance with an embodiment of the present invention. The 'MultiScreenConfigurableContext' interface 1210's block list 1300 includes at least one of the following: 'static int CONFIGURABLE SCREEN PARAMETER AUDIO FOC USf 1302 , 1 static int CONFIGURABLE SCREEN PARAMETER AUDIO SOU RCEf 1304 , ? static int CONFIGURABLE—SCREEN—PARAMETER—DEVICE O RDERf 1306 , 'static int CONFIGURABLE—SCREENJPARAMETER—DISPLAY—AR EAf 1308 , 'static int

CONFIGURABLE SCREEN PARAMETER DISPLAY SC 67 200849990 Z / IJ) ipif REENf 1310 CONFIGURABLE^ SCREEN RT’ 1312 CONFIGURABLE_SCREEN ΝΤΕΧΓ 1314

CONFIGURABLE SCREEN , f static int PARAMETER an OUTPUT a PO f static int PARAMETER a SERVICE_C〇 static int PARAMETER VISIBILITY1 1316 , and ’static int CONFIGURABLE SCREEN PARAMETER Z ORDER,

1318. Block 1320 from the 'org.ocap.ui.MultiScreenContext' interface 1230 includes at least one of the following: 'SCREEN_TYPE_DISPLAY^ and SCREEN_TYPE_LOGICAL. CONFIGURABLE—SCREEN—PARAMETER—AUDIO_ SOURCE 1 Field 1304 is a "static final int CONFIGURABLE-SCREEN-PARAMETER- AUDIO-SOU RCE,, and is a configuration parameter that identifies the sound focus configuration. The configuration of the screen sound focus is done using the 'addAudioSources(··)' and YemoveAudioSourcesC·)’ methods, which are defined by the 'org.ocap.ui.MultiscreenconfigurableContexf interface 1210. If the 'HScreen' referenced by the forg.ocap.ui.MultiscreenconfigurableContext' interface 1210 supports its sound source configuration, then risConfigurableParameter(CONFIGURABLE_SCREEN_PAR AMETER_AUDIO-SOURCE)' will be returned, true. 68 200849990 2713 lpif If 'hasDiscreteParameterSpace(CONFIGURABLE—SCREEN-P ARAMETER-AUDIO-SOURCE) 1 is returned, true, then 'getDiscreteParameterSpace(CONFIGURABLE-SCREEN-P ARAMETER-AUDIO-SOURCE)' must return the fHScreenDevice[]' type The value of each of the arrays in this value is an accessible screen device for this screen that can be used as a screen source. Since MSMI01, the 'CONFIGURABLE-SCREEN-PARAMETER-AUDIO-FOC US' field 1304 is applied. CONFIGURABLE - SCREEN - PARAMETER - AUDIO - FOCUSf Intercept 1302 is defined as ''static final int CONFIGURABLE' SCREEN_PARAMETER- AUDIOJFOC usn, and is a configuration parameter that distinguishes the sound focus configuration. The configuration of the screen sound focus can be done using the fassignAudioFocus("y method defined by the 'org.ocap.ui.MultiScreenConfigurableContext' interface 1210. If the fHScreen' referenced by this interface supports the configuration of its source, isConfigurableParameter (CONFIGURABLE—SCREEN—PAR AMETER_AUDIO_FOCUS) 'Requires a return, true. If fhasDiscreteParameterSpace(CONFIGURABLE—SCREEN—P ARAMETER—AUDIO—FOCUS)' is passed back, true, then 69 200849990 LIV5 ipif 'getDiscreteParameterSpace(CONFIGURABLE a SCREENJ> ARAMETER —AUDIO—FOCUS) 'Requires the return of the value of type 'HScreen[]', where each item in the array of values is an accessible screen that can be used as a screen source. If the screen is displayed, the returned item It is necessary to limit the logic screen to the current display screen that can be assigned to the focus of the sound. Because the display screen can always directly specify the sound focus (related to the specified sound focus to a logical screen that is displayed on this display screen), this display screen itself ' Not included in the return item If the screen is a logic screen and if this logic screen is mapped to the screen and the sound focus is on the 4th, then the returned array must include only this screen, otherwise, the returned The array must be empty. Since MSMI01, 'CONFIGURABLE-S CREEN—PARAMETER AUDIO_FOCUS has been applied, block 1302.

'CONFIGURABLE—SCREENJPARAMETER—DEVICE l —Z—ORDER’ field 1306 is "static final int

CONFIGURABLE—SCREEN—PARAMETERJDEVICE—Z—O RDERn ’ and is a configuration parameter that can identify the Z-sequence configuration of the screen device. The screen device Z sequence configuration can be done using the forg.ocap.ui.MultiScreenContext ‘Block 1230 defined by the 'setZOrderiJiScreenDeviceH)1 method. If fHScreenf referenced by this interface supports the configuration of its screen device Z sequence, then 70 200849990 2713 lpif fisConfigurableParameter(CONFIGURABLE_SCREEN_PAR AMETER_DEVICE_Z-ORDER)f must be returned, true. If 'hasDiscreteParameterSpace(CONFIGURABLE - SCREEN - P ARAMETER - DEVICE - Z - ORDER), return, true,, Belle J 'getDiscreteParameterSpace(CONFIGURABLE - SCREEN - P ARAMETER - DEVICE - Z - ORDER)' must be returned fHScreenDevice[] a value of type [], where each item in the array of values is an array of screen devices, the order of which corresponds to the supported Z order of the screen devices, and the first item of such a screen device array is the last in the Z order One (ie, its device Z sequence is 0). Figure 13C shows the use case of 'CONFIGURABLE-SCREEN-PARAMETER DEVICE Ζ Ο — — — RDER'. In Figure 13C, the following assumptions are used: The screen has a background device B1, an image device V1 and two graphic devices G1 and G2; and the sequence of the graphics device is: (1) B1 < V1 < G1 < G2 & (2) Bl < Vl < G2 < Gb Through S1330, it can be confirmed that the Z order of the background device B1 is, 〇,,, the Z order of the image device VI is "1", the Z order of the graphic device G1 is "2", and the Z order of the graphic device G2. It is "3".

Similarly, through S1340, it can be confirmed that the Z order of the background device B1 is "〇", the Z order of the image device VI is "1", and the Z 71 200849990 27131pif order of the graphic device G2 is "2", and the graphic device G1 The Z order is "3". Since MSM 101, the fCONFIGURABLE_SCREENJPARAMETER_DEVICE_Ζ-ΟRDER’ block 1306 is applied. The CONFIGURABLE_SCREEN JPARAMETER_DISPLA Y-AREA' field 1308 is defined as ''static final int CONFIGURABLE' SCREEN_PARAMETER_DISPLAY_AR EAn, and it is a configuration parameter to identify the configuration of the screen-related display area. The configuration of the (logical) display area of the screen can be done using the fsetDisplayArea(HScreenRectangle)f method defined by the forg.ocap.ui.MultiScreenContext’ interface 1230. If the 'HScreen1 referenced by 'org.ocap.ui.MultiScreenConfigurableContexf interface 1210' is a display screen, then fisConfigurableParameter(CONFIGURABLE_SCREEN_PAR AMETERJDISPLAY-AREA)' must return 'false'; otherwise, if this logic screen supports The configuration of its display area, then nisConfigurableParameter (CONFIGURABLE-SCREEN-PA RAMETER-DISPLAY-AREA), must be returned, true. If 'hasDiscreteParameterSpace(CONFIGURABLE - SCREEN JP ARAMETER - DISPLAY_AREA), return, true, then fgetDiscreteParameterSpace(CONFIGURABLE_SCREEN_P ARAMETER_DISPLAY_AREA), must return the value of type fHScreenRectangle[]f, where the value of the array Each item is a display area supported by 72 200849990 ζηόίρη. Since MSM 101, 'CONFIGURABLE-SCREEN-PARAMETER-DISPLAY-A REA, 1308 has been applied. 'CONFIGURABLE_SCREEN—PARAMETER JDISPLA Y-SCREEN' Field 1310 Set ’’static final int CONFIGURABLE a SCREEN—PARAMETER DISPLAY-SC REEN", and is a configuration parameter that identifies the configuration of this screen-related display screen. The configuration of the (logical) screen display can be done using the 'setDisplayScreen(HScreen)^ defined by the forg.ocap.ui.MultiScreenContext' interface 1230. If 'HScreei^ is referenced by the 'org.ocap.ui.MultiScreenConfigurableContext' interface 1210, the fisConfigurableParameter(CONFIGURABLE_SCREEN_PAR AMETERJDISPLAY_SCREEN)' must be returned, false. Otherwise, if the logic screen supports the display configuration, fisConfigurableParameter(CONFIGURABLE^SCREEN^PAR AMETERJDISPLAY_ SCREEN), must be returned, true. If the 'hasDiscreteParameterSpace(CONFIGURABLE_SCREEN_P ARAMETER_DISPLAY_ SCREEN)' method is returned, true, then, getDiscreteParameterSpace(CONFIGURABLE_SCREEN_P ARAMETER_DISPLAY_ SCREEN), it is necessary to return the value of type 'HScreen □', where this Each item in the value array is mapped to the logic screen. 73 200849990 ^/1^1 pii Accessible display screen. Applied since MSM 101 version

CONFIGURABLE SCREEN PARAMETER DISPLAY SC — — — REENUMi 1310.

CONFIGURABLE SCREEN PARAMETER OUTPU — —— T—PORT, field 1312 is set to "static final int

CONFIGURABLE SCREEN PARAMETER OUTPUT PO ———————— — RTn, and it is a configuration parameter that can distinguish the configuration of the screen-related output ,, ('The configuration of the screen output 可 can use the forg.ocap.ui.MultiScreenConfigurableContext' interface 1210 The defined faddOutputPorts(··)' and 'removeOutputPorts(··)' are completed. If fHScreen' referenced by the 'org.ocap.ui.MultiScreenConfigurableContext' interface 1210 supports the configuration of its image output port, then isConfigurableParameter (CONFIGURABLE_SCREEN_PAR AMETER_Ouput_Port)' It is necessary to return "true". If 'hasDiscreteParameterSpace(CONFIGURABLE_SCREENJP U ARAMETER_OUTPUT a PORT), return, 'true', fgetDiscreteParameterSpace(CONFIGURABLE_SCREEN_P ARAMETER_OUTPUT_PORT)' Returns the value of the TVideoOutputPort□' type, where each item in the array is an accessible image that the screen can directly map. Since the MSM 101, it has been applied

'CONFIGURABLE—SCREEN PARAMETER OUTPUT PO — — — RTf block 1312. 74 200849990 2/I3ipli CONFIGURABLE—SCREEN—PARAMETER—SER VIC E—CONTEXT' The block 1314 is set to ''static final int CONFIGURABLE—SCREEN—PARAMETER—SERVICE_CO NTEXT', and it is a configuration parameter that can identify the screen-related service situation. The configuration of the screen scenario is faddServieContexts(··)' and fremoveServieContexts(··)' defined by the forg.ocap.ui.MultiScreenConfigurableContextf interface 1210, and the 'swapServiceContexts' defined by the 'MultiScreenManagerf level 1260'. ·)' is completed with 1moveServiceContexts(··)'. If fHScreen' referenced by the 'org.ocap.uiLMultiScreenConfigurableContext' interface 1210 supports the configuration of its output, then isConfigurableParameter(CONFIGURABLE_SCREEN_PAR AMETER-SERVICE^CONTEXT), required Pass back 'true'. If fhasDiscreteParameterSpace(CONFIGURABLE_SCREEN_P ARAMETER_ SERVICE_CONTEXT), return '真丨, Bellow J 'getDiscreteParameterSpace(CONFIGURABLE-SCREEN-P ARAMETER- SERVICE_CONTEXT), must be returned Value ServiceContextn 'type, wherein the value of each item in the array is relative on this screen may access the service context.

Since MSM 101, CONFIGURABLE-SCREEN-PARAMETER-SERVICE_C 75 200849990f ΟΝΤΕΧΓBlock 1314 has been applied.

'CONFIGURABLE SCREEN PARAMETER VISIBIL — — — ITY! Field 1316 is set to "static final int CONFIGURABLE SCREEN PARAMETER VISIBILITY” — — — and it is a configuration parameter that identifies the configuration of the screen visibility. Screen Visibility Group The state is done by the fsetVisible(boolean)' defined by the 'org.ocap.ui.MultiScreenConfigurableContext' interface 1210. If the 'HScreeiV referenced by the 'org.ocap.ui.MultiScreenConfigurableContext' interface 1210 supports its visibility configuration, Then fisConfigurableParameter(CONFIGURABLE_SCREEN__PAR AMETER-VISIBILITY), it is necessary to return "true,,, but fhasDiscreteParameterSpace(CONFIGURABLE-SCREEN-P ARAMETER_VISIBILITY) 'back to 1 false', implying that if its visibility is configurable, then apply continuous parameter space (ie, "true" and "false"). Since MSM 101, CONFIGURABLE-SCREEN-PARAMETER-VISIBILITY has been applied, block 1316. -CONFIGURABLE-SCREEN JPARAMETER-Z_ORDE R' block 1318 is set to "static Final int CONFIGURABLE_SC REEN—PARAMETER-Z-ORDER”, and it is a configuration parameter that can distinguish the configuration of the screen Z sequence. The configuration of the screen Z sequence can be done with the \org.ocap.ui.MultiScreenConfigurableContext' interface defined by 1210, 200849990 2713 lpif fsetZOrder(int)f. If 'HScreen' referenced by the forg.ocap.ui.MultiScreenConfigurableContext' interface 1210 supports its Z-order configuration (as opposed to other screens in its multi-screen configuration), then fisConfigurableParameter(CONFIGURABLE—SCREEN—PAR AMETER_Z_ORDER) ' Must be returned, really,. If 'hasDiscreteParameterSpace(CONFIGURABLE—SCREEN—P ARAMETER— Z—ORDER) f is returned, true, then 'getDiscreteParameterSpace(CONFIGURABLE—SCREEN-P ARAMETER—Z_ORDER)f must return the value of type 'Integer[]f, where The value item V in this value array is fv.intValue〇f back to the supported Z-order index of this screen in the context of this screen multi-screen configuration. Since MSM 101, 'CONFIGURABLE-SCREENJPARAMETER-Z-ORDER has been applied to block 1318. The field 1320 from *forg.ocap.ui.MultiScreenContext' includes 'SCREEN TYPE DISPLAY, 盥 one — /, 'SCREEN TYPE LOGICAL. Figures 13D-13F show a method list 1350 of the interface 'MultiScreenConfigurableContext', 1210 of the java suite 'org.ocap.ui', in accordance with an embodiment of the present invention. The 'org.ocap.ui.MultiScreenContext' interface method list 1350 includes at least one of the following: v〇id 77 200849990 If uipir addAudioSources(org.havi.ui.HScreenDevice[] devices, boolean mixWithAudioFocus)f Method 1352; Void addOutputPorts (org.ocap.hardware.

VideoOutputPort[] ports, boolean removeExisting) '方> Go to 1354; Void addServiceContexts(javax.tv.service.selection. ServiceContex t[] contexts, a boolean associateDefaultDevices)1 Method 1356 ·, Void assignAudioFocusQ1 Method 1358 ; 'Boolean checkServiceContextCompatibility( Javax.tv.service.selection .ServiceContext context)' Method 1360 ; forg.davic.resources.ResourceClient getClient()f 1362;

Java.lang· Object [] getDiscreteParameterSpace(int parameter)' Method 1364; 'boolean hasDiscreteParameterSpace(int parameter)1 side> goes 1366; 'boolean isConfigurableParameter(int parameter)' method 1368 ; fvoid releaseScreen()' method 1370 ; Void removeAudioSources(org.havi.ui.HScreenDevice[] devices)' Method 1372; 'void removeOutputPorts(org.ocap.hardware. VideoOutputPort[] ports)' Method 1374 ; Void removeServiceContexts(javax.tv.service.selection. ServiceCo ntext[ ] contexts)' Method 1376; Void requestMultiScreenConfigurationChange(MultiScreenConfig uration configuration, java.utiLDictionary 78 200849990 2713 lpif serviceContextAssociations)f Method 1378; 'boolean reserveScreen(org.davic.resources.ResourceClient client, java.lang. Object requestData)' Method 1380 Void setDisplayArea(org.havi.ui.HScreenRectangle rect)' Method 1382; Void setDisplayScreen(org.havi.ui.HScreen screen)'Method 1384; Void setMultiScreenConflguration(MultiSc reenConfiguration configuration, java.util.Dictionary serviceContextAssociations)' Method 1386; Void setVisible(boolean visible)' Method 1388; Void setZOrder(org.havi.ui.HScreenDevice[] devices)' Method 1390; and fvoid setZOrder(int order)' Method 1392. The method list 1394 from the 'org.ocap.ui.MultiScreenContext' interface 1230 includes at least one of the following: faddMultiScreenConfigurationListenerf, 'addScreenContextListener', fgetAudioFocus', 'getAudioSources 丨, 'getDisplayArea', 'getDisplayScreen', 'getID', fgetMultiScreenConfigurationf5 fgetMultiScreenConfigurations', fgetMultiScreenConfigurationsf? fgetOutputPortsf5 'getScreenCategory,, 'getScreenType', fgetServiceContextsf5 fgetVisiblef, 'getZOrder', 'getZOrder', fremoveMultiScreenConfigurationListenerf and 'removeScreenContextListener'. 79 200849990 2713 I pif fisConfigurableParameterf Method 1368 is set to "boolean isConfigurableParameter(int parameter),, and if the configuration parameters can be configured by a platform implementation of the screen (as opposed to fixed), then it is determined. Parameter' is a configurable screen parameter whose content value is as defined above. If the platform implementation supports continuous or discrete changes to a particular 'parameter' on this screen, this 'isConfigurableParameter* method 1368 then returns 'true'; Otherwise, it returns 'false.' Since the MSM 101 version, the fisConfigurableParameter' method 1368 has been applied. The fhasDiscreteParameterSpacef method 1366 is set to 丨'boolean hasDiscreteParameterSpace(int parameter)", and if the supported configurable parameters are discrete or Continuously changing the value space, and it is determined. In the present context, the 'continuously' configuration parameter represents that the platform supports or predicts all values of this parameter type value, and "discrete" represents Only certain and listed parameter types The value can be used by the report of fgetDiscreteParameterSpace(· ·)'. The parameter "parameter1 is a configurable list of screen parameter values, as defined above. If the platform implementation supports the value of the value type space of the specific, parameter on the screen, The discrete (()) group, then the 'hasDiscreteParameterSpace' method 1366 returns, true, otherwise, 'hasDiscreteParameterSpace1 method 1366 backhaul, false, where all values of this value type space can be supported (or predictable) 200849990 27131pif If 'isConflgurableParametei^parameteryiSeS returns 'false', this 'hasDiscreteParameterSpace' method 1366 issues rjava.lang.IllegalArgumentException, ° Since the MSM 101 version, the 'hasDiscreteParameterSpacef method 1366 has been applied. 'getDiscreteParameterSpace' method 1364 sets fjava.lang .Object[] getDiscreteParameterSpace(int parameter)'1, and the discrete and (sub)groups of the values of the value type space of the configuration parameter are available. *fgetDiscreteParameterSpace'Method 1364 The true execution time type of the returned array and array elements must be set for the specific configuration parameters set by the above configuration parameters. The order of items returned by the 'getDiscreteParameterSpace' method 1364 is not defined in the present invention and must be considered as an implementation related to the interworking application, unless defined by the 4 inch group of teas. A set of supported discrete parameters may change for a given screen based on a given configuration parameter on the screen lifecycle of the state of the underlying resources of the screen. However, such a change does not occur in the completion of the distribution.

fMultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION-CHANGING’ events are related to completion distribution

• This change occurs outside the period between the MultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION—CHANGED’ pieces. The parameter 'parameter' is a configurable screen parameter whose value is as described in 81 200849990 2/ IJ ipif. fgetDiscreteParameterSpacef Method 1364 Back to Object 歹丨j, each object represents a discrete value of a particular parameter supported (or predictable) by the platform. If 'hasDiscreteParameterSpace(parameter), method 1366 returns, false f, 'isConfigurableParametei^parameter)' method i368 or 'getDiscreteParameterSpace' method 1364 must issue 'java.lang.IllegalArgumentException1'. Since the MSM 1〇1 version, the 'getDiscreteParameterSpacel;^ 1364 ’ ‘setVisible’ method 1388 has been set to %〇id setVisible(bo〇lean visible)" and screen visibility has been set. If this screen is a logical screen, then the screen will be marked as visible (if previously hidden) or marked as hidden (if previously visible). If this tribute is not glory, all logical screens that are unrecognizable will be marked as visible (if previously hidden) or marked as hidden (if visible previously).

The Visible' parameter is the Boolean value, which represents the logic of the display screen. The fHScreenf or logic screen needs to be visible or hidden (invisible) for its related display fHScreeiy. If the calling thread does not allow MonitorAppPermission(f!multiscreen.contextff)f ^ fsetVisiblef method 1388 to issue 'java.lang.SecurityException1' if llScreen' visibility cannot be changed, for example, if the platform uses permanent visibility ,, setVisible, method 1388 issues 82 200849990 2713 lpif ▼ java.lang.IllegalStateException '. Since the MSM 101 version, the setVisible’ method 1388 has been applied. If the 'setZOrder(int)' method 1392 is set to , void setZOrder(intorder)n, it sets the Z order of the screen. The 'setZOrder(int)' method 1392 causes the logical 'HScreen' to change its Z order between the other ^HScreenfs that are mapped to the same display 'HScreeW'. The forderf argument is a positive integer representing the new Z order of HScreen’ to be assigned to this logic. If the call line does not allow fMonitorAppPermission(Mmultiscreen.context??)f , the 'setZOrder(int)' method issues a 'java.lang.SecurityException'. If the type of this 'HScreen' is not 'SCREEN_TYPE_LOGICAL', or if the 'HScreen% Z order cannot be changed, for example, the platform uses the permanent z order setting, the 'setZOrder(int)f method 1392 issues 'java.lang.IllegalStateException'. Since the MSM 101 version, the 'setZOrder(int)f method 1392 has been applied. The 'setZOrder(HScreenDevice[])' method 1390 is set to ’’void setZOrder(org.havi.ui.HScreenDevice[] devices),' and sets the Z order of the screen devices in the screen of a group of screen devices. , setZOrder(HScreenDevice[])丨1390 automatically sets the z-order of the specific group of 'HScreenDevicef', which applies the following conditions: - If fHbackgrounddevicef exists in a specific device group, 83 200849990 2/13ipif (i) 'Hbackgrounddevice, in this device The group contains any 'HVideoDevice' before; and (9) it precedes any 'HGraphicsDevice1' included in this device group. - If 'HVideoDevice is present in a specific device group, fHVideoDevice' is before any of the HGraphicsDevices included in this device group. If the fsetZOrder(HScreenDevice[])' method does not cause any accidents, the order of this group-specific fHScreenDevice' is such that any sequence (rMultiScreenContext.getZOrder(HScreenDevice)f called on this screen will return the Z order. Index, which retains this particular relative order. If less than the entire set of 'HScreenDevice' associated with this screen is provided in the devices' argument, the relative order of unspecified devices relative to a particular device is not defined unless by 'MultiScreenContext' The conditions defined by .getZOrder(HScreenDevice)' are applied to all device sequences in this screen after execution, 'setZOrder(HScreenDevice[])' method 1390. The 'devices1 parameter is the order of the 'HScreenDevice' associated with this screen. Array. If the call line does not allow fMonitorAppPermission(f?multiscreen.context ff)f , ?setZOrder(HScreenDevice[])f method 1390 issues fj ava.lang· Security Exception'. If the 'device' parameter is not the fHScreenDevicef of this screen, 84 200849990 2713 lpif fsetZOrder(HScreenDevice [])f method 1390 issues fjava.lang.IllegalArgumentException'. 'setZOrder(HScreenDevice[])f method 1390 must produce 'java.lang.megalStateException', when (i) the specific 'HScreenDevice', the Z order cannot be changed, such as When the platform uses the permanent Z-order setting of the screen device in this screen, or (9) when the order of the specific device cannot allow the Z-order index specification that satisfies the above limitation. Since the MSM 101, the 'setZOrder(HScreenDevice[])' method has been applied. 1390. The 'addAudioSources' method 1352 is set to, 'v〇id addAudioSources(org.havi.ui.HScreenDevice[] devices, boolean mixWithAudioFocus)", and joins one or more sources of this screen. The faddAudioSources' method 1352 adds one or more 'HScreenDevice's to the sound source group, which represents the sound that has been selected (and mixed) to present a sound from this screen. If a specific source has been assigned as the source for this screen, but fmixWithAudioFocusf is different from the value when it was added as a source, use the new fmixWithAudioFocus’. The ▼devices1 parameter is a non-empty array of 'HScreenDevice', and each fHScreenDevicef contributes to the mix presentation of this screen. If the fmixWithAudioFocusf parameter is 'true', then the particular shader contributes sound or mixes any sound output associated with any image output (directly or indirectly) associated with this screen, whether or not the screen specifies the sound focus. If |11^^¥11:11八11(1丨〇?〇<:1^ parameter is 'false', then only this 85

200849990 A specific screen device contributes sound when the Z/UlplT screen specifies the sound focus. If the call line does not allow fMonitorAppPermission("multiscreen.context’')' , the 'addAudioSources' method 1352 issues 'j ava.lang· Security Exception'. If the 'devices' parameter is not a non-empty array or some items of 'devices' are not the 'HScreenDevice' of this screen, the Bellow J faddAudioSources' method 1352 produces 1java"ang.IllegalArgumentExceptionf. f add Audi o S our ce s1 Method 1352 must generate fjava.lang.IllegalStateException', when (i) the source of this 'HScreenDevice' cannot be changed, such as when the platform uses a permanent source set on the screen of this screen or (ii) ) When a multiple source is specified but the mix is not supported. Since the MSMI01 version, the fflfaddAudioSources' method 1352 has been applied. The 'removeAudioSources' method 1372 is set to nv〇id removeAudioSources(org.havi.ui.HScreenDevice[] devices)'' and removes one or more sources. The fremoveAudioSourcesf method 1372 removes all or part of the non-empty group of a particular 'HScreenDevice' from the source group of 'HScreen'. If the value of 'devices' is, null, then all sources are removed. The 'devicesf number represents a null value or a non-empty group of 'HScreenDevice'. If the call line is not allowed!MonitorAppPermission(ffmultiscreen.contextff)f , fremoveAudioSourcesf method 1372 issues 86 200849990 27131pif fjava.lang.SecurityException, ° if , devices, is not empty, and some 'HScreenDevice' items are not related to this 'HScreenf , 'removeAudioSources' method 1372 emits ▼j ava. lang.IllegalArgumentException'.

If the specific 'HScreenDevice' that cannot be changed as the source of this 'HScreen' cannot be changed, for example, if this platform uses a permanent source for this particular fHScreenDevicef, the 'removeAudioSources' method 1372 must issue ]ava iangjQiegalStateException'. Since the MSM 101 script, ‘removeAudioSources, method 1372 has been applied. The 'assignAudioFocusf method 1358 is set to ''void asSignAudi〇Focus()' and specifies the sound focus on this screen. Any 4 moments, the display must specify the sound focus to itself or to a logical screen of itself (this display screen) When the new sound dance displays the screen's logic screen and this logic screen is currently not specified, all the remaining logic ", 曰..., points from the screen to the display screen are assigned to this newly assigned logic screen. The specified screen is assigned to the established display screen, or the logical screen that does not reflect the screen is specified. It is necessary to specify the sound position of the screen (cat machine, s..., ",, occupant, 嘁 萤 萤 _ _ And Mo Zhen..., ",, pre-sigh." The sound focus can be explicitly assigned to the nitrous-free power, using the display screen on the display screen 疋芏 gnAudl 〇 F〇cus' method 1358. Specifies that you want to present this display to the honor screen;:: The selected source (implicitly) the sound presentation device looks like the output of all the clothes? The screen of the sundial sound focus has no sound 87 200849990 / IJI pif source, that is, it has an empty sound source group, then the sound (generated by or possibly generated by the CAp platform) should not be reflected by this display screen. All (implicit) sound rendering devices of all image output ports are presented. Each display screen can have a separate logic screen that specifies the focus of the sound to present the sound of the display screen (and the set of mapped logical screens). If the call line is not allowed

MonitorAppPermission(nmultiscreen. context")!, then the ‘assignAudioFocus, method 1358 issues 'java.lang.SecurityException’. The fassignAudioFocusT method 1358 will generate an fjava.lang.megalStateException if the sound focus cannot be assigned to this 'HScreen' or the current sound focus cannot be changed'. The ‘assignAudioFocus’ method 1358 has been applied since the MSM 101 version. The faddOutputPorts? method 1354 is set to "v〇id addOutputPorts(org.ocap.hardware.VideoOutputPort[] ports, boolean removeExisting)", and one or more image outputs are added to the screen being screened. If this fHScreenf is For the logic screen instead of the display screen, fHScreenf must be considered equivalent to the display screen to reflect the specific image output. That is, the logic screen is treated as if it is the main display screen. Parameter 'ports$fVideo〇utputPort' Non-empty array. If the value of the parameter 'removeExistingf is true, then the association with the existing screen is removed before adding to the new screen. 88 200849990 2713 lpif If the call line does not allow fMonitorAppPermission(?fmultiscreen. C〇ntextf?)f , then the 'addOutputPorts' method 1354 is issued. faddOutputPortsf method 1354 issues 'java.lang.IllegalStateException', when (i) specific 'VideoOutputPort,

i has been associated with a different 'HScreen' and 'removeExisting' is not true, ; (ϋ) This ^HScreen1 cannot be mapped to a specific fVideoOutputPort' because of platform-specific hardware-restricted relationships; and (iii) when mapped to ' HScreen's ▼VideoOutputPorf group cannot be changed, ie when the platform uses the permanence associated with a particular group of f VideoOutputPorf. Since the MSM 101 version, 4 (1 (1〇1^1仙〇11^ method 1354 has been applied. The 'removeOutputPorts' method 1374 is set to, void removeOutputPorts(org.ocap.hardware.VideoOutputPort[] ports)'', And remove one or more image output bees that are mapped to the screen. The 'removeOutputPorts' method 1374 removes all or some of the non-empty groups of the special 'VideoOutputPort' from the image output group that is mapped to fHScreenf. If the parameter &gt ;〇115' is "empty", then all image output 埠 associations are removed. The parameter ^ports' is "empty" or a non-empty array of fVideoOutputPortf. If the call line does not allow fMonitorAppPermission(?!multiscreen.contextff) f , 贝 ij fremoveOutputPorts! Method 1374 issues 'java.lang.SecurityException'. 89 200849990 2713 Ipif If fportsf is not empty, and some 'VideoOutputPorf items are not related to 'HScreenf', then 'removeOutputPorts', method 1374 issues TjavaJang.IllegalArgumentExceptionf If it cannot be changed, HScreenf's specific fVideoOutputPortf, for example, if the platform is used Regarding the permanent association of a particular 'VideoOutputPorf', the 1J 'removeOutputPortsf method 1374 must issue 'java.lang.IllegalStateExceptionf. Since the MSM 101 version, the 'generation 111〇¥6〇1^1^〇11:5' method 1374 has been applied. The 'setDisplay Screen' method 1384 is set to ''void setDisplayScreen(org.havi.ui.HScreen screen)'' and the logic screen is related to the display screen. That is, the fsetDisplayScreenf method 1384 associates the logical fHScreenf with the display fHScreenf. Creenf is to display fHScreenf or is empty. If the parameter 'screen1 is empty', the 'setDisplayScreen' method 1384 is executed in principle, and the parameter fscreenf is returned, then the logic, HScreen' is no longer related to the display fHScreenf ° if the call line is not allowed fMonitorAppPermission(f!multiscreen.contextM)f , then fsetDisplayScreen! method 1384 issues 'java.lang.SecurityException'. 'setDisplay Screen' method 1384 issues 'java.lang.IllegalStateException', when (1), HScreen, the type is not 'SCREEN_TYPE-LOGICAL,; (9) specific 'screenf is not empty, nuu' 90 200849990 27131pif and its screen type is not, SCREEN-TYPEJDISPLAY,,4(iii)&& changes related to the avoidance fHScreen4々 display 'HScreen', for example, when the platform is permanently associated with the special display 'HScreen'. Since MSM 101, "setDisplayScreen" has been applied, method 1384. setDisplayArea method 1382 is set to "void setDisplayArea(org.havi.ui.HScreenRectanglerect)n, and the area that is displayed to the screen of the avoidance screen is set. , fsetDisplayArea' method 1382 relates this logic 'HScreen' to the region (range) of its associated display fHScreen, parameter seven (^ is ugly 8 (^611 feet 6 (^ ton 16', which specifies the logic associated with 'HScreeW' The area on fHScreeW is displayed, which needs to be related to the scope of this logical fHScreen'. If this call line does not allow fMonitorAppPermission(f?multiscreen.contextf,)f then the 'setDisplayArea' method 1382 issues 'java.lang.SecurityException' ° ' setDisplayArea' method 1382 emits ▼java.lang.IllegalStateException' if (1) 'HScreen' type is not *fSCREEN_TYPE_LOGICAL'; or (2) if the area associated with this logic 'HScreenf' showing fHScreenf cannot be changed, for example, If this platform uses the permanent association of the relevant special area. Since the MSM 101 version The 1setDisplayArea' method 1382 has been applied. 91 200849990 2/13ipif fcheckServiceContextCompatibilityf side> Go to 1360 and set to "boolean checkServiceContextCompatibility(javax.tv.service.selection •ServiceContext context)" and test the compatibility of the service context with the screen. That is, the 'checkServiceContextCompatibility method 1360 determines whether the application can specify 'ServiceContexf to this fHScreenf and whether the particular ServiceContextf is compatible with the rendered content on this fHScreenf.

The parameter fcontextf is a valid fServiceContext'. The 'checkServiceContextCompatibility' method 1360 returns a Boolean value indicating whether a particular fServiceContexf can be assigned to this 'HScreen1'. If the specific 'ServiceContextf can be specified, then return, true, otherwise return 'false. Call line not allowed

fMonitorAppPermission(ftmultiscreen.context,f)f , shell, J ‘checkServiceContextCompatibility’ method 1360 Issue 'java.lang.SecurityException’. If the specific 1ServiceContexf is not valid, the 'checkServiceContextCompatibility' method 1360 issues fjava.lang.IllegalArgumentExceptionr 〇 Since the MSM 101 version, the 'checkServiceContextCompatibility' method 1360 has been applied. The 'addServiceContextsf method 1356 is set to nvoid addServiceContexts(javax.tv.service.selection. ServiceContex t[] Contexts,boolean associateDefaultDevices)n, and the service is added to this screen. That is, the 'addServiceContexts' method 1356 adds one or more 'ServiceContexf' to the service context group associated with this 'HScreen, to allow the background, image and graphical content from the 'ServiceContext' to be rendered on the respective screens of fHScreenf. On the device. If a particular service situation is already related to the underlying screen represented by the 'org.ocap.ui.MultiScreenContext' interface, then this service context is not multiple related to this screen, but the existing association remains. That is, the 'established service situation must be related to the established (bottom) screen, either once or not. If two or more non-summary contexts are related to a given screen and the multi-image source transmitted by the background playback of the multi-digest service context will be the default video device of the given screen, then the video content needs to be played twice. The background play of the service situation will be determined according to the following rules. 1. If the application of one of the related non-summary service scenarios retains the established 'HVideoDevice' on the firefly, the background of the service context will be Specified to be rendered on this image device; and the month is not working, 2 otherwise ''the background play content specified as the highest priority paste context will be specified to render the force on this image device if the above rules are applied After that, the multi-background $, 'specified application' of the application is presented on this image device, and the image is presented: the second-passive passive player has priority. Qi Kai

It is currently listed in Huihui. If the parameter is then the screen's default screen device .r'' is currently only for the specific 93 200849990 z / u ipif fServiceContext'; otherwise. If the parameter fassociateDefaultDevices' is 'false', no association between the preset screen devices is made. If the call line does not allow fMonitorAppPermission(??multiscreen.contextff)f , the 'addServiceContexts' method 1356 issues 'java.lang.SecurityException'. If some of the specific 'ServiceContext' of this fHScreen' cannot be changed, for example, if the platform uses a permanent association of a particular 'ServiceContexf', the f, bel |J ‘addServiceContexts' method 1356 issues fjava.lang.IllegalStateException'. Since the MSM 101 version, the SddServiceContexts▼ method 1356 〇 'removeServiceContexts' method 1376 has been set to "void removeServiceContexts(javax.tv.service.selection.ServiceCo ntext[] contexts)" and the service context has been removed from the screen. That is, the ▼removeServiceContextsf method 1376 removes all or part of the non-empty group of the special 'ServiceContext, ί from the service context group associated with fHScreenf. If 'contexts' is empty, all service contexts are removed. Contexts' is a non-empty array of empty or 'ServiceContext'. If the call line does not allow fMonitorAppPermission(f,multiscreen.contextf,)f, the shell 'removeServiceContexts' method 1376 issues 'java.lang.SecurityException'. If 'contexts' is not Empty and some 'ServiceContext, project not 94 200849990 2713 lpif related to fHScreenf, Bellow J'removeServiceContexts' method 1376 Issue Tjava.lang.IllegalArgumentException'. If the fServiceContext' cannot be changed, eg the platform uses a specific 'ServiceCon For the permanent correlation of text', the 'removeServiceContexts' method 1376 must be issued as ¥&.1&1^.11168&181&{6£乂〇601^〇11'. Since the MSM 101 version, 'removeServiceContexts' has been applied Method 1376. The 'setMultiScreenConfiguration' method 1386 is set to "void setMultiScreenConfiguration(MultiScreenConfiguration configuration, java.util.Dictionary serviceContextAssociations),', and sets the current active multi-screen configuration of this display screen. That is, one of the logical screen subgroups associated with this display screen will be selected at a given time. If the specific 'configuration' is the current configuration of this display screen, then unless the application is defined (:111^啦〇^七〇11',4{]\4111 dip.11€〇11如1«^〇11, method The value returned by 1386 does not produce any marginal effect. If the specific 'configuration' is not the current configuration of this display screen, and if 'SecurityException', 'IllegalStateExceptionf 舆 'IllegalStateException' is not applied, then the synchronous display defined by the present invention is performed. Multi-screen configuration changes. If the 'serviceContextAssociations' argument is specific (ie, if it is not empty), then any 'ServiceContexf, which can be accessed by the application, must be related to no screen or specific (new) Application screen in multi-screen configuration. If some are accessible, ServiceC〇ntext, no association, if 95 200849990

Z/ijipiT Some accessible 'ServiceContext' does not exist in a specific application, or if it exists but no such applicable screen exists in the new multi-screen configuration, then 'ServiceContext must be related to this particular multi-screen configuration The default service context 'that is, the screen returned by ▼configuration.getDefaultServiceContextScreen〇. To match the accessible "ServiceContext", refer to the keywords that are treated as specific fserviceContextAssociations' for these keywords (using the virtual method 'equalsCObject), which assumes that the fsetMultiScreenConfigurationf side is going to 1386.

The default implementation of Object.equals(Object)f. In the context of a given application, the MSM host implementation must maintain a one-to-one relationship between the fServiceContextf that the application can affect and the set of underlying service context resources. If the MSM host implementation cannot maintain this relationship, then when the architecture 'serviceContextAssociations' dictionary is schemad, the MSM implementation may treat two different sets of underlying service context resources as the same service context 'eg if 'at a different time, single, The 'ServiceContext' refers to a different set of underlying resources. Alternatively, the MSM implementation can treat a single collection of underlying service context resources as two different service contexts, for example, at a given moment, two different 'ServiceContext' refer to the same underlying resource collection. The DFC state of the image management, which is used to process images related to the service context exchanged or moved by the 'setMultiScreenConflguration1 method 1386, is not affected by the execution of the fsetMultiScreenConfigurationf method 1386. 96 200849990 2713 lpif 麦 'configuration' is, MultiScreenConfiguration , in order to become the current active display of this display screen, the multi-screen configuration. If the parameter 'serviceContextAssociations' is not empty, it is 'Dicti〇nary, its key sub-疋ServiceContext' and its value is, S Tring', where the string value is defined as follows: (1) If the string value is ""', the screen is not applied (in this case, the matching service context is not related to any screen, after the configuration is changed); (2 For example, if the substring value is 疋 then all screens of the new screen configuration should be applied; (3) otherwise 'if the substring value 萤 is returned by the 'MultiScreenContext.getID()T screen identification code, then apply this screen; (4) Otherwise, if the string value is

MultiScreenContext.getScreenCategory()' The screen type returned, any screen of this type of new configuration can be applied; (5) Otherwise, if the substring value is a semicolon-separated list of screen identification codes, then match Each screen of the new configuration of the identification code will be applied; (6) Otherwise, if the string value is a semicolon-separated list of screen types, the newly configured screens with the matching type will be applied; (7) otherwise If the string value is a semicolon-separated list of screen identification codes or screen types, each screen with a new configuration matching the identification code or matching type will be applied; and (8) otherwise, the newly configured default service The situation will be applied. If the call line does not allow fMonitorAppPermission(f,multiscreen.configurationff)?, then the 'setMultiScreenConfiguration' method 1386 issues rjava.lang.SecurityException? ° If the parameter '''configuration' is not returned by ▼MultiScreenContext.getMultiScreenConfigurations()▼ 97 200849990 ^ This (display) screen's multi-screen configuration _, then fsetMultiScreenConfigurationf side> go to 13S6 to generate fjava·lang.IllegalArgumentExceptionf. fsetMultiScreenConfigurationf method ^ 丨 'java.lang.IllegalStateException', if this screen is not a display screen, or (1) if the MSM implementation does not allow the startup of a particular multi-screen configuration; (2) if the 'setMultiScreenConfiguration' method 1386 was previously called and The change process is not completed; or (3) if the start is not allowed during the method call. The ‘setMultiScreenConfiguration’ method 1386 has been applied since the MSM 101 release. ‘requestMultiScreenConfigurationChange, method 1378 is set to "void requestMultiScreenConfigurationChange(MultiScreenConfig uration configuration, java.utiLDictionary serviceContextAssociations)'’, and the current active multi-screen configuration of the display screen is required to be changed. If the specific 'configuration1' is the current configuration of this display, then unless the 'SecurityException' is applied, the frequestMultiScreenConfigurationChange' method 1378 will return the value ' without any marginal effects. If the specific 'configuration' is not currently displayed, and if ''SecurityException", 'IllegalArgumentException'' and 'IllegalStateException' are not applied, the non-synchronous 98 200849990 2713 lpif change for the current multi-screen configuration will be initialized, where fsetMultiScreenConfiguration is applied ( The semantics of f, except that this method needs to return the value immediately after the generation of ▼MultiScreenConfiguration.MULTI_SCREEN-CONFIGURA Ή ON_CH ANGINGf (but before its spread). The parameter 'configuration' is 'MultiScreenConfigurationf' to become the current active screen configuration. The parameter fserviceContextAssociationsf is empty or 'Dictionary' whose key is 'ServiceContext' and whose value is 'String', according to the semantics defined by 'setMultiScreenConfiguration'. If the call line does not allow fMonitorAppPermission(Mmultiscreen.configurationn)f , the ▼requestMultiScreenConfigurationChange’ method 1378 issues 'java.lang.SecurityException'. If the parameter 'configuration' is not returned by fMultiScreenContext.getMultiScreenConfigurations, one of the (display) screen multi-screen configurations returned by the 'requestMultiScreenConfigurationChange' method 1378 issues an fjava.lang.IllegalArgumentException, if this screen is not a display screen or (1) If the msm implementation does not allow the startup of a particular multi-screen configuration; (2) if the fsetMultiScreenConfiguration 'method 1378 was previously called and the change process has not completed; or (3) if the start is not allowed during the call method, the 'setMultiScreenConfiguration' method 1378 Issue fjava.lang.IllegalStateException'. 99 200849990 ζ/υιριτ Since the MSM 101 version, the frequestMultiScreenConfigurationChange' method 1378 has been applied. The getClientf method 1362 sets norg.davic.resources.ResourceClient getClientQ" and gets the current underlying screen resource client and screen resources associated with this fHScreenf. The fgetClient' method 1362 is also defined by the fgetClient of the 'org.davic.resources.ResourceProxyf interface. 'getClient' method 1362 returns 'ResourceClient, or postback, null value' 'If the underlying screen and screen resources associated with this fHScreen' are not retained. Since the MSMI01 version, 'getciient, method 1362. 'reserveScreen' has been applied. Method 1380 sets " boolean reserveScreen(org.davic.resources.ResourceClient client, java.lang.Object requestData)n and automatically retains the underlying source of this screen. If the reserved screen is considered equivalent to retaining all HScreenDevice1' associated with this screen, then except when this screen is reserved with 'reservescreenf method 1380', it will not release all the 'HScreenDevice' with all the underlying screen resources that are not released with this screen. . If, while the screen is reserved, some of this screen, HScreenDevice, has been reserved by another application, this reservation must be successfully released (by the MSM implementation) before allowing this screen to be retained. If it is not released or cannot be released 100 200849990 2713 lpif stay, the attempt to keep this screen will be lost. That is, the reserveScreenf method 1380 must be returned, ‘fake,’. If some screens of fHScreenDevice on this screen have been reserved by the reserved application, this reservation implies a successful reservation of the entire screen. If the 'reserveScreen' method 1380 is used to reserve the screen successfully, ie if the 'reserveScreen' method 1380 is returned, 'true', then the return value of all 'HScreenDevice's of this screen must be the same as by org.ocap.ui. The MultiScreenConfigurableContexf interface defines the getClient() method 1362 (as in the discrete implementation of 'HScreen'). If this screen was not previously reserved and calls 'reserveScreen', method 1380 causes this screen to be preserved, then in 'reservescreen, method 1380 Before the return, it must be produced

‘MultiScreenResourceEvent.MULTI a SCREEN—RESOURCE — SCREEN—RESERVED’ event. If the call application has reserved this screen and if specific, the client, and 'requestData' argument is the same as that specified when the call application previously allowed this reservation, the freserveScreen' method 1380 has no marginal effect and returns 'true'. If the calling application has reserved this screen but the specific "client,, or 'requestData" is not the same as specified when the call application previously allowed this reservation, then (1) the specific ''client'' and 'requestData' arguments will be Replaced by a previous specific; (2) the call application must maintain this reservation; and (3) 'reserveScreen, method 1380 must be returned, true. The parameter 'client^fResourceClient'. The parameter frequestData' is "empty" or an Object' that implements the 'java.rmi.Remote' interface. 101 200849990 z / u ipu If the underlying resources of the screen are successfully preserved, then 'reserveScreen, method 1380 returns 'true', otherwise it returns 'false'. Since the MSM 101 version, the freserveScreenf method 1380 has been applied and is referred to as 'Remote'. The 'releaseScreenf method 1370 sets the null releaseScreen()' and automatically releases the underlying resources of the screen. If the call application does not retain this screen, the freleaseScreen’ method 1370 must have no marginal effect. If this screen was previously reserved and the call to freleaseScreen' method 1370 causes this screen to no longer be retained (not to be retained), then 'MultiScreenResourceEvent.MULTI-SCREEN-RESOURCE-SCREEN-RELEASED must be generated before the YeleaseScreen* method 1370 returns the value, event . Method 1370 has been applied since the MSM 101 release. Figure 14A shows the definition of the interface 'MultiScreenConflgurationf' of the java suite 'org.ocap.uif' according to an embodiment of the present invention. The fMultiScreenConfiguration' interface is set to "public interface MultiScreenConfiguration’. The fMultiScreenConfiguration' interface 1220, implemented by the OCAP host platform, provides information on discrete screen configurations and mechanisms for monitoring changes to this screen configuration. The MSM implementation must support at least one multi-screen configuration with a configuration type of SCREEN-CONFIGURATION-DISPLAY'. 102 200849990 27131pif The MSM implementation must support at least one multi-screen configuration with a configuration type of 'SCREEN—CONFIGURATION—NON—PIP. If the MSM implements the PIP function and allows the PIP screen to be presented while the 〇CAP is operating, the MSM implementation must support multiple screen configurations, SCREEN-CONFIGURATION-PIP'. If the MSM implements the POP function and allows the POP screen to be rendered while the OCAP is operating, the MSM implementation must support the multi-screen configuration 'SCREEN-CONFIGURATION-POP'. If the MSM implements a PIP, POP or OVERLAY function for a discrete configuration explicitly specified for a non-general multi-screen configuration, the MSM implementation must support one or more multi-screen groups of the configuration type 'SCREEN-CONFIGURATION-GENERAL' State, which represents this multi-screen configuration. Since the MSM 101 release, the fMultiScreenConfiguration▼ interface 1220 of the f〇rg.ocap.uif suite has been applied. 14B shows a block list 1400 of the interface 'MultiScreenConfiguration' of the Java suite 'org.ocap.ui' according to an embodiment of the present invention.

The field list 1400 of the Java suite 'org.ocap.uif' interface fMultiScreenConfigurationf includes at least one of the following: 'static java.lang.String SCREEN-CATEGORY-DISPLAY, block 1402, 'static java.lang.String SCREEN_CATEGORY_GENERAL' 1404, 'static java.lang.String SCREEN—CATEGORY—MAIN' 103 200849990, 2 / JLpif Field 1406, f static java.lang. String SCREEN_CATEG〇RY—NONE' Field 1408, f static java.lang.String SCREEN —CATEGORY_OVERLAY' field 1410, 'static java.lang.String SCREEN—CATEGORY—PIP' pole 1 bit 1412 , 'static java.lang.String SCREEN_CATEGORY—POPf block 1414 , 'static java.lang.String SCREEN—CONFIGURATION— DISPLAY, field 1416, 'static java.lang.String SCREEN—CONFIGURATION-GENERAL' field 1418, 'static java.lang.String SCREEN—CONFIGURATION—NON_PIP, block 1420, 'static java.lang.String SCREEN—CONFIGURATION - PIP, field 1422, and, static java.lang.String SCREEN_CONFIGURATION - POP, field 1 424. , SCREEN_CONFIGURAUON—DISPLAY’ field 1416 Set "static final java.lang.String SCREEN-CONFIGURATIONJDISPLAY,’ . If fMultiScreenConfigurationf is related to one or more display screens and may be configured as multiple screens for each platform, its configuration type is SCREEN_CONFIGURATIONJDISPLAY, field 1416. The initial preset screen for the configuration type of 'SCREEN—CONFIGURATION—DISPLAY’ field 1416 must be the first screen returned by getScreens(SCREEN—CATEGORY—MAIN). If there is no such screen in this configuration, then 104 200849990 2713 lpif ’SCREEN_CONFIGURATIONJDISPLAY, the initial preset screen for the configuration type of Block 1416 must be the first screen returned by fgetScreens〇’. Since the MSM 101 version, the 'SCREEN-CONTIGURATION—DISPLAY’ field 1416 has been applied. ▼SCREEN—CONFIGURATION—NON—PIP, block 1420 set "static final java.lang.String SCREEN_CONFIGURATION—NON—PIP. If fMultiScreenConfiguration' is only related to one screen, its type is 'SCREEN_CATEGORY_MAINf, and its configuration type The initial preset screen of the configuration type of 'SCREEN-CONFIGURATION-NON-PIP, 'SCREEN-CONFIGURATION-NON-PIP' 1420 must be 'getScreens(SCREEN-CATEGORY-MAIN), the first screen to be returned. The class fMultiScreenConfiguration with the 'SCREEN_CONFIGURATION_NON_ΡΙΡ' 1420 configuration type cannot include more than one display screen. Since the MSM 101 version, 'SCREEN-CONFIGURATION-NONJPIPW^Il 1420 has been applied. 'SCREEN_CONFIGURATIONJ>IP, block 1422 setting' 'static final java.lang. String SCREEN—CONFIGURATION—PIP”. If ▼MultiScreenConfiguration' is (1) a logical screen related to the 0 preset z-order of the entire area of the single display 105 200849990 Z/lJipif screen, and (2) related to the same display screen to the same display 1 One or more non-intersecting logic screens of Z sequence are preset, and the configuration type is fSCREEN-CONFIGURATION-PIP' 1422. 'SCREEN_CONFIGURATI〇N_PIP, the initial preset screen for the configuration type of field 1422 must be 'getScreens(SCREEN-CATEGORY-MAIN), the first screen returned, if there is no class under this configuration can be classified as 'SCREEN - CATEGORY - MAIN, 1406 screen, the initial preset screen of the configuration type of 'SCREEN_CONFIGURATIONJPIP' block 1422 must be the first screen returned by 'getScreens()'. 'MultiScreenConfiguration1, which is classified as having the 'SCREEN_CONFIGURATION_PIPf 1422 configuration type, cannot include more than one display screen. Since the MSM 101 version, SCREENJ: ONFIGURATION—PIP, field 1422 has been applied. , SCREEN—CONFIGURATION—POP, field 1424 setting n static final java.lang. String SCREEN-CONFIGURATION—POP’1 . If ▼MultiScreenConfiguration1 is related to more than two non-intersecting logic screens with Z order of preset 0, and its preset display screen (overall) covers the entire area of a single display screen, its configuration type is ▼SCREEN-CONFIGURATIONJPOP, Field 1424. , SCREEN—CONFIGURATION—POP%hiL 1424 Configuration 106 200849990 2713 The initial preset screen of type lpif must be the first screen returned by fgetScreens(SCREEN—CATEGORY—POP)'; or, if configured under this configuration, There is no screen that can be classified as 'SCREEN-CATEGORY-POP' 1414, then the initial screen of the configuration type of 'SCREEN-CONFIGURATIONJPOPf field 1424 must be the first screen returned by *fgetScreens〇f. 'MultiScreenConfigurationf', which is classified as having the 'SCREEN_CONFIGURATIONJPOPf 1424 configuration type, cannot include more than one display screen. Since the MSM 101 version, 'SCREEN—CONFIGURATlON—POPHWi 1424 has been applied. 'SCREEN—CONFIGURATION—GENERAL, field 1418 Set M static final java.lang.String SCREEN—CONFIGURATION—GENERAL,, . If 'MultiScreenConfiguration' cannot be categorized as one of the other defined screen configuration types, its configuration type is 'SCREEN-CONFIGURATION-GENERAL' 1418. The initial preset screen for the configuration type of 'SCREEN—CONnGURATION_GENERAL’ 1418 must be getScreens(SCREEN—CATEGORY_MAIN), the first screen to be returned. If there is no screen classified as 'SCREEN-CATEGORY-GENERAL' 1404 in this configuration, the initial preset screen for the configuration type of SCREEN_CONFIGURATION_GENERAL' 1418 must be the first screen returned by getScreensQ'. 107 200849990 27I3ipif categorization MultiScreenConfiguration1 with ▼SCREEN—CONFIGURATION_GENERAL’ 1418 configuration type may not include more than one display screen. Since the MSM 101 release, fSCREEN—CONFIGURATION—GENERALUHi 1418 has been applied. 'SCREEN—CATEGORY—NONE, field 1408 Set "static final java.lang.String SCREEN—CATEGORY—NONE. If ^ 'HScreen' is not related to any other special category, its category is 'SCREEN-CATEGORY-NONE , 1408. MultiScreenConfiguratior categorized as having the 'SCREEN_CATEGORY_NONE' 1408 configuration type cannot include more than one display screen. Since MSM 101 version, SCREEN-CATEGORY-NONE, field 1408. 'SCREEN-CATEGORY- DISPLAY, field 1402 setting static final java.lang. String SCREEN_CATEGORYJDISPLAY". If 'HScreen, classified as non-main screen, its category is 'SCREEN_CATEGORY_DISPLAY' 1402. Specify the display screen for this category is not available, Hbackgrounddevicef or fHVideoDevicef Positioning, but can be positioned as one or more overlapping 'HGraphicsDevice'. Classified as, SCREEN_CATEGORY—DISPLAY, 1402 shows that fHScreenf has an exception attribute, and its fHGraphicsDevice> exists in 108 200849990 2713 lpif, it must overlap to this Show firefly All logical screens. Even if 0 is returned to any display, this attribute should not be confirmed. The above exception attribute is to support (1) inheritance device, closed caption overlap appears in other content And (the illusion configuration, not the heavy screen as a separate logic screen, the overlapping screen is regarded as the display screen integration 'HGraphicsDevice'. Since the MSM 101 version, 'SCREEN-CATEGORY DISPLAY has been applied, blocking 1402. 1 'SCREEN—CATEGORY—MAINf field 1406 Set "static final java.lang.String SCREEN-CATEGORY—MAIN,. If the display or logic 'HScreeW' feature is the main screen, its type is ▼SCREEN_CATEGORY_MAIN' 1406. Specify this category The logical screen must be mapped to the entire area of some display screens, and the default Z order of ,, 0, , must be specified. Since the MSM 101 version, the 'SCREEN-CATEGORY-]\^1 field has been applied 1406. i ’SCREEN—CATEGORY—PIP, field 1412 settings, 'static final java.lang.String SCREEN-CATEGORY—PIP,’. If the feature of the logical fHScreen' is a PIP screen, its type is , SCREEN_CATEGORYJPIP' 1412. Specifies that this type of logic screen cannot be mapped to all areas of a display screen. You cannot specify a screen sequence of "0" and must coexist in some configurations of the screen type 'SCREEN_CATEGORY_MAINf 1406'. Since the MSM 101 version, 109 200849990 has been applied, i"JL pif ''SCREEN-CATEGORY-PIP' field 1412. , SCREEN-CATEGORY-POP, field 1414 set "static final java.lang.String SCREEN-CATEGORY-POP". If the feature of the logical 'HScreen' is a POP screen, the Bechi type is 'SCREEN_CATEGORY_POP' 1414. Specifies that this type of logic screen cannot be mapped to all areas of some display screens and cannot coexist in certain screens that specify this type of configuration and must coexist in some other screen-specified type 'SCREEN-CATEGORYJPOP' 1414 State. Since the MSM 101 version, the SCREEN-CATEGORY-POP’ field 1414 has been applied. 'SCREEN—CATEGORY—OVERLAY1 Block 1410 Settings n static final java.lang. String SCREEN^CATEGORY—OVERLAY’,. If the feature of the logical 'HScreen' is an overlay screen, its type is SCREEN-CATEGORY-OVERLAY1 1410. Specifies that this type of logic screen must be mapped to all areas of the display screen, and the preset Z sequence must be specified to be larger than the screen associated with one of the following: SCREEN-CATEGORY-MAIN' 1406, 'SCREEN_CATEGORY-PIP' 1412 ^ 'SCREEN-CATEGORY-POP' 1414, and cannot contain background or explicit image plane (fHVideoDevicef). However, the overlay screen can utilize the resources of the internal image plane ('HVideoDevicef) to render the composition image in one of its image planes. 110 200849990 2713 lpif Since the MSM 101 version, ‘SCREEN—CATEGORYJ3VERLAY has been applied, blocking 1410. 'SCREEN—CATEGORY—GENERAL'Block 1404 sets ''static final java.lang.String SCREEN-CATEGORY-GENERAL'. If the logic 'HScreen' can be configured (eg its size, position or Z order), The operational mode is that it is recommended to specify two or more other screen types, the type can be 'SCREEN-CATEGORY-GENERAL' 1404. Specifying this type of logic screen can not limit its size, position, Z order or other configuration properties. In addition to the terminal device's internal restrictions on one (or more) configuration attributes. Since SCM 101 version, 'SCREEN-CATEGORY-GENERAL has been applied, block 1404. Figure 14C shows the Java suite 'org. Method list for the interface 'oScreenConfiguration' of ocap.ur 1450 〇

The method list 1450 of the interface 'MultiScreenConflguration' 1200 of the Java suite 'org.ocap.ui' includes at least one of the following: 'java.lang·String getConfigurationType()f method 1452, forg.havi.ui.HScreen getDefaultServiceContextScreen()f method 1454 , forg.havi.ui.HScreen[] getScreens()f Method 1456, forg.havi.ui.HScreen[] getScreensGava.lang.String category)1 Method 1458, 'boolean hasOverlayScreen()' method 1460, 'boolean isscreenInConfiguration (org.havi.ui.HScreen screen), Method 111 200849990 4L. IL ρίΓ 1462 and 丨void setDefaultServiceContextScreen, method 1464. 'getConfigurationType' method 1452 Set "javajang.string getConfigurationType(yi get the screen configuration type of this configuration. If more than one non-generic configuration type can be applied or if this configuration type cannot be known or cannot be changed, then 'SCREEN —CONFIGURATION—GENERAL· The value of method 1418 is to be returned. The string returned by 'getConfigurationType' method 1452 is the following ('one (1) one of the following: SCREEN-C0NFIGURA110N—DISPLAY, 1416, 'SCREEN—CONFIGURATION— NON JPIP, 1420, 'SCREEN a CONFIGURATION—PIPf 1422, , SCREEN_CONnGURAHON a POP, 1424, and 'SCREEN—CONFIGURATION—GENERAL' 1418; or (ii) a word representing the platform-related configuration type and prefixed with “x-” String. Since the MSM 101 version, applied, getConflguratkmType, method 1452. ( 'getScreens〇f method 1456 set' org, havi.ui.HScreen[] getScreens()n, and get the accessible screen associated with this configuration Group. By the 'getScreens〇' method 1456 backhaul, the underlying resources of HScreen' can be shared with another Within the screen configuration, HScreen, however, at any time, shared resources cannot be active within more than one multi-screen configuration. The order of items within the fHScreeW's backhaul array is related to the implementation. Any two of the given backhaul arrays The values of the items (S1 and S2) and the given 'MultiScreenManager', MSM, a unique example, in 丨getScreens〇, 112 200849990 2713 lpif method 1456 back and

The following conditions must be used between the generation/spreading of fMultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION-CHANGING': • fMSM.isEmptyScreen(Sl)f must be 'false'; • fMSM.isEmptyScreen(S2)' must be 'false ▼; MSM.sameResourcesCSl.SS) 'Must be 'false'; if called by an application that does not have 'MonitorAppPermission(''multiscreen.configuration'')', this group is not related to the 'ServiceContext' accessible by this application. The status screen cannot be returned; otherwise, all accessible screens of this configuration are returned. In the application life cycle, in addition to the underlying restrictions, the MSM implementation can add/subtract screens to multiple screen configurations, where it must produce fMultiScreenConfigurationEvent.MULTI_SCREEN_CONFI GURATION-SCREEN-ADDED, ^ 'MultiScreenConfigurationEvent.MULTI—SCREEN—CONFI GURATION— SCREEN—REMOVED, event. The screen cannot be added/reduced to the multi-screen configuration of the active platform of each platform or some multi-screen configurations that are currently active in displaying multiple screen configurations. The MSM implementation must wait until the multi-screen configuration is no longer the current active multi-screen configuration to add/subtract screens from this configuration. Not produced

'MultiScreenConflgurationEvent.MULTI—SCREEN—CONFI 113 200849990 Z / i J ipif GURATION—SCREEN an ADDED' or fMultiScreenConfigurationEvent.MULTI_SCREEN_CONFI GURATION—SCREEN-REMOVED' event, the return of the "Hscreen" setting and the order of these backhaul are not available Changed, from a given application. The MSM implementation may not remove or generate the fMultiScreenConfigurationEvent.MULTI_SCREEN CONFI GURATION_SCREEN__REMOVEDf event, which may have the 'HScreen' of the underlying resource of the default 'HScreeW' that has the same underlying resource as some uncorrupted applications removed from this multiscreen configuration (or Report the effect of this removal).

The TgetScreens〇' method 1456 returns the 'HScreen' array. The returned fHScreen7 train may be an empty array. Since the MSM 101 version, the fgetScreens()' method 1456 has been applied. The 'getScreens(String)' method 1458 sets Morg.havi.ui.HScreen[] getScreens〇ava.lang.String category)’' with all of the types of accessible screens. The function of I fgetScreens(String)f method 1458 must be the same as fgetScreens()' method 1456, except for the following: • If iategoryf is not empty, only those screens that specify this particular type are returned, or if there is no such screen , then pass back the empty 'HScreen' array; for example, if 'category' is empty, the return value is the same as fgetScreens〇' method 1456. The value of the parameter Category is one of the following: (1) empty, (2) one of the following: { 'SCREEN-CATEGORY one NONE' 1408, 114 200849990 2713 lpif 'SCREEN-CATEGORY JDISPL A Yf 1402, 'SCREEN-CATEGORY one MAIN' 1406, ,SCREEN-CATEGORY-PIP' 1412, ,SCREEN_C ATEGORY a POP 1414, 'SCREEN a CATEGORY-OVERLAY, 1410, with 'SCREEN_CATEGORY-GENERAL; 1404}, or (3) platform-dependent string value, not scheduled Return the fHScreen' array for the screen type but can be returned by 'getScreenCategory(HScreen)' 0 fgetScreens(String)' method 1458. The 'HScreen' array returned by the 'getScreens(String)f method 1458 can be empty. The 'getScreens(String)' method 1458 has been applied since the MSM 101 release. fhasOverlayScreen()' method 1460 sets 丨'boolean hasOverlayScreen()'' and decides if the settings related to this configuration include overlapping screens, ie the screen type is 'SCREEN-CATEGORY-OVERLAY, 1410 〇'hasOverlayScreen()' method 1460 returns f true f, if, getScreens(SCREEN_CATEGORY_OVERLAY), returns a non-empty array; otherwise, it returns "false". The fhasOverlayScreen()' method 1460 has been applied since the MSM 101 version. fgetDefaultServiceContextScreen()' Method 1454 Set "org.havi.ui.HScreen getDefaultServiceContextScreen〇n, and 115 200849990 Get the default service context related screen for this configuration. The default service context-related screen for multi-screen configuration is that it can't get the 4 inch special price to decide how to associate 'servicec〇ntexf to the curtain. When this configuration becomes active, its ServiceContext is related. The following restrictions apply: 1. If the multi-screen configuration is to display multiple screen configurations for each platform, the preset service context-related screens must be displayed for each display screen associated with certain display screens associated with this multi-screen configuration. State; Μ 2· Otherwise, if this multi-screen configuration is a multi-screen configuration for each display, the preset service context-related screen needs to be a display screen or evasion screen associated with this multi-screen configuration. The 'getDefaultServiceContextScreen()f method 1454 returns fHScreenf as the default service context screen for this configuration. If the call line does not allow fMonitorAppPermission("multiscreen.configuration"), the fgetDefaultServiceContextScreen()f method 1454 issues 'java.lang.SecurityException'. The fgetDefaultServiceContextScreen()f method 1454 has been applied since the MSM 101 release. The fsetDefaultServiceContextScreen' method 1464 sets the nv〇id setDefaultServiceContextScreen(org.havi.ui.HScreen screen)'' and sets the default service context related screen for this configuration. The default service context-related screen for multi-screen configuration is that when more special information is not available to determine how to relate 1ServiceContext1 to the screen, when this configuration becomes active, its 'ServiceContexf' is relevant. 116 200849990 2713 The lpif parameter 'screen' is fHScreenf to specify the preset service context-related screen for this multi-screen configuration. If the call line does not allow fMonitorAppPermission(f,multiscreen.configuration??)? , , setDefaultServiceContextScreenf method 1464 issues fjava.lang.SecurityExceptionf . If the above condition of the ▼getDefaultServiceContextScreen()' method 1454 is not met, the shell J'setDefaultServiceContextScreen' method 1464 issues the 丨java.lang.IllegalArgumentException' 〇 ‘setDefaultServiceContextScreen' method 1464 since the MSM 101 version has been applied. fisscreenInConfiguration(HScreen)' method 1462 sets nbooleanisscreenInConfiguration(org.havi.ui.HScreen screen)". The 'isscreenlnConflguration(HScreen)' method 1462 determines whether the underlying resources of a particular screen are thus configured to fHScreeiy included in the settings of the relevant screen. The parameter fscreen' is the parameter 'HScreen'. The 'isscreenlnConfiguration(HScreen)' method 1462 returns 'true' if the underlying resource of a particular screen is represented by 'HScreenf within this configuration; otherwise, the return is false, The ▼isscreenlnConflguration(HScreen)' method 1462 has been applied since the MSM 101 version. Figure 15A shows the definition of the interface 'MultiScreenContext' 1230 of the Java suite 'org.ocap.ui' according to an embodiment of the invention. 117 200849990 27131pif

The Java Suite @org.ocap.ui' interface TMultiScreenContexf 1230's ''All Known Sub interfaces" includes 'MultiScreenConfigurableContext' 1210 and is set to ''public interface MultiScreenContextn ° fMultiScreenContextf interface 1230 provides a set of tools to accomplish the following: 1 · through The logical mapping pair is directly related to 'HScreenf of fVideoOutputPorf and 'HScreen' which is indirectly related to fVideoOutputPort', that is, whether fHScreen' is a display screen or a logic screen; 2. Discover the unique platform identification code of the underlying resources of THScreeiy; 3. Discover the ^HScreen% category assigned to its internal "MultiScreenConfiguration"; 4. Discover the logic ^HScreen' to display the mapping of fHScreenf, including the area (range) on the display fHScreen', where the logic, HScreen, is present , its visibility and its Z order; 5) found the Z order of fHScreenDevice' in 'HScreen'; 6 found the 'ServiceContext' group related to fHScreenf; 7. found the association with the related VideoOutputPorf; 8 found fHScreenDevicef Group, the sound produced by it constitutes the sound source group of 'HScreen'; 9. The discovery shows the current sound focus of 'HScreen, the specified; I 〇·gets the state change of fMultiScreenContext' or implements the notification of the change of 'HScreen' of this interface; II. Get notifications of changes to the display screen display for each screen; 118 200849990 Z/ 丄Jipif 12·Discover the display multi-screen configuration group for each display screen; and 13·Get the current active display of the display screen Multi-screen configuration. If the OCAP implementation does not support OCAP MSM Plus and does not support the 'MultiScreenContext' interface 1230, the OCAP application can assume that the behavior of ▼HScreenf is equivalent to implementing this 'MultiScreenContexf interface 1230's fHScreen' as follows: • TYPEJDISPLAY' ; 'getID()' returns the platform-dependent (possibly empty) string; • fgetScreenCategory() 'returned string nmain'; • 'getVisible〇f returns 'true'; • 'getZOrder(), backhaulΌ ' ; • getZOrder(HScreenDevice device)' returns the 'device' array index in the 'HScreenDevice1 array', which is called by fHScreen.getHbackgrounddevices〇', fHScreen.getHVideoDevices()f and fHScreen.getHGraphicsDevices()' under fHScreenf. Caused by consecutive results, or I, if the device does not exist in this array, issue 'IllegalArgumentException'; • 'getAudioSources〇f return 'HScreenDevice' array, which is called 'HScreen' in sequence under 'HScreen'. getHbackgrounddevices(),,,fHScreen.getHVideoDevices()f with ' Caused by the continuous result of HScreen.getHGraphicsDevices()'; • fgetAudioFocus〇 'returning fHScreen'; • The array returned by fgetOutputPorts〇f includes all fVideoOutputPortf obtained on the platform 119 200849990 ^/υιριτ; • fgetDisplayScreen()' Return fHScreen'; • TgetDisplayArea() f return, new HScreenRectangle(090,l9l)f ; • The array returned by fgetContexts〇f includes all 'ServiceContext's that can be accessed by the current application; MSM implementation must support ' MultiScreenContext' interface, for each fHScreenf. Since the MSM 101 release, the "MultiScreenContext' interface 1230 of the 'org.ocap.ui' suite has been applied. Figure 15B shows a block list 1500 of the interface fMultiScreenContext' 1230 of the Java Suite 'org.ocap.ui', in accordance with an embodiment of the present invention.

The booth list 1500 of the interface 'MultiScreenContext' 1230 of the Java Suite forg.ocap.ui' includes at least one of the following: 'static int SCREEN - TYPE_DISPLAY, field 1502 and, static int SCREEN - TYPE - LOGICAL, block 1504. 'SCREEN_TYPE—DISPLAY’ block 1502 settings, 'static final int SCREEN-TYPEJDISPLAYn. If THScreenf is directly related to ▼VideoOutputPort' and the range of fHScreenf is mapped to the image range produced by 'VideoOutputPortf, then the type of 'HScreen' is , SCREEN_TYPE_DISPLAY, and is called display, HScreen. Since the MSM 101 version, ‘SCREEN—TYPE—DISPLAY has been applied, blocking 15〇2. 120 200849990 27131pif , SCREEN TYPE-LOGICAL, block 1504 set "static final int SCREENJTYPE - LOGICAL". If fHScreenf is not directly related to the range of 'VideoOutputPort' or fHScreen', it is mapped to the image of the image generated by a fVideoOutputPorf The area, then, HScreen, is of type 'SCREEN_TYPE-LOGICAL1 and is called logic, HScreenf. The logic 'HScreeW may be related to the display 'HScreen'. If the logic 'HScreen, not related to display fHScreen', then this logic 'HScreenf's 'ServiceContext' does not produce visual or audible objects. It is not relevant to the display 'HScreeiV's logic ^HScreen' to decode and use the content for purposes other than rendering. For example, the logic 'HScreenf can be recorded by the ServiceContext 'Called content for future presentation. SCREEN_TYPE_LOGICAL' field 1504 has been applied since the MSM 101 version. Figures 15C and 15D show the Java suite 'org.ocap.uif' according to an embodiment of the invention List of methods for interface fMultiScreenContextf1230 1550 〇

The method list 1550 of the interface 'MultiScreenContext' 1230 of the Java suite 'org.ocap.ui' includes at least one of the following: Void addMultiScreenConfigurationListener(MultiScreenConfigura tionListener listener) 'method 1552, Void addScreenContextListener(MultiScreenContextListener listener)' method 1554, 'org.havi .ui.HScreen getAudioFocus()f Method 1556, forg.havi.uLHScreenDevice[] getAudioSources()' Method 1558, 'org.havi.ui.HScreenRectanglegetDisplayAreaO' 121 200849990 Z / 1J 1 pif Method 1560, 'org.havi.ui .HScreen getDisplayScreen()f Method 1562, a 'java.lang· String getID()' Method 1564, 'MultiScreenConfiguration getMultiScreenConfiguration()f ^ Method 1566 , fMultiScreenConfiguration[] getMultiScreenConfigurations()f Method 1568 , fMultiScreenConfiguration[] getMultiScreenConfigurations(java. lang.String screenConfigurationType)f method 1570,

'org.ocap.hardware·VideoOutputPort[] getOutputPorts()f Method: 1572,fjava.lang·String getScreenCategory()'method 1574,'int getScreenType()f method 1576 , fjavax.tv.service.selection. ServiceContext[] getServiceContexts 〇 'Method 1578, 'boolean getVisible()' method 1580, 'int getZOrder()f method 1582, fint getZOrder(org.havi.uLHScreenDevice device) '方> go 1584, Void removeMultiScreenConfigurationListener(MultiScreenConfi gurationListener listener)' method 1586 with Void removeScreenContextListener(MultiScreenContextListener listener)' method 1588. The 'getScreenTypeQ' method 1576 sets "int getScreenType()" and gets the type of fHScreenf. The 'getScreenType()f method 1576 returns an integer value representing 'SCREEN_TYPE_DISPLAY' or , SCREEN TYPE LOGICAL,. 122 200849990 27131pif Since the MSM 101 release, the 'getScreenType()' method 1576 has been applied. fgetID() 'method 1564 sets ''java.lang.String getID()n and gets the platform-specific unique identification code of the underlying collection of screen resources represented by this screen'. The unique range is not less than the current active platform. The screen is configured with all active display screens for multiple screen configurations. It relates to the implementation 'regardless of the scope of the uniqueness of the screen identification code, including other non-active multi-screen configurations. The screen identification code cannot be equal to any screen type returned by fgetScreenCategory()f. If S1 and S2 are within the scope of the unique implementation, HScreenfa 'MultiScreenManager.sameResources(Sl,S2)' returns 6 false ', then '((MultiScreenContext)S 1 ).getID(), and X(MultiScreenContext)S2 ).getID()7 returns the same (equivalent) string. Conversely, if 'MultiScreenManager.sameResources(Sl,S2)' returns 'true', then f((MultiScreenContext)S 1 ).getID()f is the same as '(MultiScreenContext)S2).getID()' must be returned (equivalent) string. The string value representing the underlying resource set of 'HScreen1' may represent the scope of implementation of the uniqueness. The 'getID〇' method 1564 has been applied since the MSMI01 version. fgetScreenCategory()' method 1574 Sets '’java.lang.String getScreenCategoryQ" and gets the screen type of fHScreenf. 123 200849990^ 厶 / 1 j jl μϋ fgetScreenCategory() f method 1574 can be a string, which is (1) one of the constants defined by the following: 'MultiScreenConfigurationT 1220: { -SCREEN a CATEGORY-DISPLAY, 14〇2 , ,SCREEN—CATEGORY-MAIN' 14〇6, ,SCREEN-CATEGORY-PIPf 1412, 'SCREEN-CATEGORY-POP, 1414, 'SCREEN-CATEGORY_OVERLAY, 1410, and 'SCREEN-CATEGORY-GENERAL1 1404}, or (2) A string value representing the platform-related screen type and prefixed with "x-". Since the MSM 101 release, 'getScreenCategory〇, Method 1574 has been applied. , getVisible()' method 1580 sets, fboolean getVisible〇n and gets screen visibility. The fgetVisible 〇f method 1580 determines whether fHScreeni is marked as visible to be rendered in some display 'HScreen^, where' visibility, defined as generating a signal to VideoOutputPort', whether or not i fVideoOutputPort' is enabled. 'HScreen' must remain marked as visible. The logic 'HScreen' can be visible or hidden (not visible). The fgetVisible〇f method 1580 returns a Boolean value representing 'HScreen, which is indicated on some display fHScreen' as Visible or not. Since the MSMI01 version, 'getVisible〇, method 1580 has been applied. 'getZOrder()f method 1582 sets nint getZOrder(), and gets the Z order of the screen, ie, it determines the Z of this 'HScreen' Sequence. Shows 'HScreen' always returns the ZZ order. Logic 'HScreen' can return 'Γ or 124 200849990 z/uipif larger z order, unless it is not related to the display screen, in this case, its The Z order is. The larger Z order represents between a group of 'HScreen1' and is the front (topmost). fgetZOrder (the value of y method 1582 represents the Z order of this 'HScreeW' Or Lr. If fHScreenf is not related to the logical fHScreen' that displays fHScreenf, then return '-Γ. Since the MSMI01 version, the 'getZOrder()f method 1582 has been applied. 'getZOrder(HScreenDevice)' Method 1584 sets nint ( getZOrder(org.havi.ui.HScreenDevice device)'' and get the screen sequence of the screen in this screen. That is, 'getZOrder(HScreenDevice)' 1584 determines the specific fHScreenDevice% Z order with 'HScreen, which applies the following Restrictions: • If fHbackgrounddevice' is present on this screen, then the last (bottom) 'book&〇1^〇1111 (1 (16¥&丨 2 order is 0; • If there is no 'Hbackgrounddevice' on this screen) 'And if fHVideoDevicef is present on the screen, the Z-order of the last party (the bottommost 'HVideoDevice' is 0; • If there is no 'Hbackgrounddevice' and fHVideoDevice' in the screen and if it exists in this screen, then The last (most bottom) 'HGraphicsDevice''s order is 〇; • The 'ZVideo' of the 'HVideoDevice' is greater than any ▼Hbackgroundde on the screen. The Z order of vice'; • In the screen, the Z order of fHGraphicsDevice' is greater than the Z order of any 'HVideoDevice'. 125 200849990 /. / 1 j 1 μιι The larger Z order represents the order of the front (top) in fHScreenDevice' under fHScreen'. Each of the bottom screen device groups represented by fHScreenf constitutes each z-order. That is, given multiple THScreenfs representing different underlying screens, the Z-order values of the underlying screen device resources assigned to these screens can again be indexed using the same z-order. The parameter fdeviceifHScreenDevicef, which is related to the screen. fgetZOrder(HScreenDevice)' 1584 returns a non-negative value, representing if 'device' is not the 'HScreenDevice' of the screen, then fgetZOrder(HScreenDevice)f 1584 returns ▼javaJang.IllegalArgumentException'. Since the MSM 101 version, 'getZOrder(HScreenDevice)' 1584 has been applied. fgetAudioSources()f Method 1558 Set ’’org.havi.ui.HScreenDevice[] getAudioSources()n and get the sound source for this i screen. That is, the fgetAudioSources(R) method 1558 obtains 'HScreenDevicei, where the sound is selected (and mixed) to present the sound from this screen. The preset set of sound sources for the screen constitutes an item sequence associated with all of the 'HScreenDevicef''s returned by the fgetAudioSources(R) method 1558 of this screen, which is not defined in the present invention and which is considered to be implementation dependent. fgetAudioSources()' Method 1558 Back to Reference 126 200849990 2713 lpif 'Happable' array of 'HScreenDevice', each case contributes to the sound of the mix presented on this screen, or if the screen does not support mixing, A project will exist in the return array. Since the MSM 101 version, the 'getAudioSources()' method 1558 〇▼getAudioFocusO has been applied, and the method 1556 sets "org.havi.ui.HScreen getAudioFocus〇'f and gets the sound focus screen. The decision of the 'HScreen' sound focus screen is According to the following rules, when the first rule is applied, other rules are ignored: 1. If this liScreen' is a logical screen, the following sub-rules are applied: a. If this logic ^HScreeW is mapped to the display screen, the following sub-applications are applied. Rule: i. If this logic 'HScreei^ is the currently specified sound focus in the context of its display screen, then return this logic. ii. Otherwise, (not the currently specified sound focus in this display), return "empty" ''. ( b • Otherwise, (not reflected to the display screen), if this logic is directly mapped to the image output 埠 ' then return this fHScreenf. c. Otherwise (not reflected to the display screen and not directly reflected to the image round埠), return, 'empty'. 』 2. Otherwise '(This fHScreenf is the display screen), apply the following sub-rules · a · If the screen is displayed, some of the logic screens of the display screen specify the sound focus, then return This logic 'HScreei^ ; 曰b·other (no logic screen to this display screen or screen to this display 127 200849990 2 / Uipif screen display screen has no specified sound focus), then return to display 'HScreen'. Display screen The sound focus screen is that all of the currently selected sources are assigned to present all (implicit) sound rendering devices for all of the image output screens displayed on this screen. , getAudioFocus〇f Method 1556 Back, HScreen, or, , empty,,, as above. Since the MSM 101 version, fgetAudioFocus()l& (1556 has been applied. 'getOutputPorts()f method 1572 sets norg.ocap, hardware.VideoOutputPort[ ] getOutputPortsQ'' and get the image that is mapped to the screen. That is, the SetOutputPorts()f method 1572 gets related to this fHScreen%fVideoOutputPortf group. If the HScreenf type is 'SCREENJTYPEJDISPLAY, then the screen is related to this display. VideoOutputPorf. If the 'HScreen' type is fSCREEN_TYPE_LOGICAL' and this 'HScreen' is related to the display I 'HScreen', then return the VideoOutputPortf associated with this display 'HScreenf. If 'HScreen, the type is SCREEN_TYPE_LOGICALf and this 'HScreen, not related to display fHScreenf, returns an empty array. 'getOutputPorts〇' method 1572 returns the reference to the array of fVideoOutputPort'. If the returned array is empty, then this 'HScreen1 is not relevant For any fVideoOutputPort'. Since the MSM 101 version, it has been applied >1:0 qing1^〇11;3()1 method 128 200849990 2713 lpif 1572. fgetDisplayScreen()? Method 1562 Set ''org.havi.ui. HScreen getDisplayScreenQ" and get the display screen associated with this screen. That is, SetDisplayScreen (y method 1562 gets the display fHScreenf related to this fHScreen'. If the type of 'HScreen1 is 'SCREEN_TYPEJ) ISPLAY, then the reference of fHScreenT is returned. If fHScreen' is of the type 'SCREEN_TYPE_LOGICAI; and this 'HScreen' is related to the display, then this fHScreen' is returned. If the type of 'HScreen' is SCREEN_TYPEJLOGICALf and this 'HScreen' is not related to displaying 'HScreen', then return the ''empty' value. fgetDisplayScreen()' method 1562 returns the reference to display or return 'empty'. Return 'empty, then this 'HScreen, not related to display fHScreenf. Since the MSM 101 version, the fgetDisplayScreen〇f method 1562 has been applied. The 'getDisplayAreaO' method 1560 sets norg.havi.ui.HScreenRectangle getDisplayArea〇n and gets the image For the area of the display screen to this screen, the getDisplayArea()f method 1560 gets the area (range) of this 'HScreeW. If the type of fHScreenf is 'SCREEN TYPE-DISPLAY, then it is necessary to return the condition 8 (^6111^( ^1]^^', whose value is equal to '118(^6111^(^邱16(0,0,1,1), if 'HScreen' type is 'SCREEN_TYPEJLOGICAL', and this fHScreenf is related to display fHScreenf, Then the area (range) occupied by the logical fHScreenf on its associated display fHScreen, is to be returned. If 129 200849990 jL. I i pif 'HScreenf type is 'SCREEN-TYPEJL OGICAL, and this 'HScreen, is not related to the display 'HScreeiV, then return the empty value'. 'getDisplayArea()' method 1560 returns the reference to the HscreenRectangle or returns the ''empty' value. If the return The "empty" value, then this 'HScreen' is not related to displaying fHScreen'. Since the MSM 101 version, the fgetDisplayAreaO' method 1560 has been applied. 'getServiceContexts〇f method 1578 sets njavax.tv.service.selection. ServiceContext[] getServiceContexts〇 " and get the service context related to this screen. That is, fgetServiceContexts 〇f method 1578 gets the relevant fServiceContexf group related to fHScreenf that the call application is allowed to access. fgetServiceContexts 〇f method 1578 returns the reference to 'ServiceContext, array. If the empty array is returned, then this fHScreeiV is not associated with any accessible 'ServiceContext'. Since the MSM 101 release, fgetServiceContexts(), Method 1578 has been applied. faddScreenContextListener(MultiScreenContextListener y method 1554 sets ''void addScreenContextListener(MultiScreenContextListener listener)n& to join the screen situation listener. That is, once the screen situation event occurs, the faddScreenContextListener(MultiScreenContextListener)f method 1554 joins the listener to be notified. Has joined the listener and 130 200849990 2713 lpif has not been removed, then try to join the listener again can not produce any marginal effect. The parameter 'listener' is 'MultiScreenContextListener'. Since the MSM 101 version, has applied faddScreenContextListener(MultiScreenContextListener)f Method 1554 〇fremoveScreenContextListener(MultiScreenContextList ener) method 1588 sets "void removeScreenContextListener(MultiScreenContextListener listener)" and removes the screen situation listener. That is, the removes creenContextListener(MultiScreenContextListener)f method 1588 removes the previous one when a screen context event occurs. Join the listener to be notified. If this particular listener is not currently set as a listener, then trying to remove it does not produce any marginal effects. Parameter flistener'*fMultiScreenContextListener, Since the MSM 101 version, the ?removeScreenContextListener(MultiScreenContextListener)f method 1588 has been applied. addMultiScreenConfigurationListener(MultiScreenCon figurationListener)' Method 1552 sets ''void addMultiScreenConfigurationListener(MultiScreenConfigura tionListener listener)', and when the screen is displayed, the multi-screen configuration event applied to this screen, once it appears, joins the listener to be notified. If 131 200849990 Z/iJipn has previously been added to the listener and has not been removed, attempting to re-enter the listener does not produce any marginal effects. Configuration events applied to the display screen are limited to affect the completion of the logic screen associated with the display screen. If an event defined by 1MultiScreenConfigurationEvenf is generated, the MSM [Implementation must notify each of the scratch screen configuration listeners. The 'listener' parameter 'MultiScreenConfigurationListener'. If this screen type is not 'SCREEN_TYPE_DISPLAY', the faddMultiScreenConfigurationListener(MultiScreenConflgura tionListener)1 method 1552 issues ▼java.lang.niegalStateException'. Since the MSM 101 version, the faddMultiScreenConfigurationListener(MultiScreenConfigura tionListener)' method 1552 has been applied. fremoveMultiScreenConfigurationListener(MultiScreen ConfigurationListener)f Method 1586 Set "void removeMultiScreenConfigurationListener(MultiScreenConfi gurationListener listener)'1, and remove the listener previously added to the notification when a multi-screen configuration event occurs. If this particular listener is not currently set as a listener, trying to remove it will not create any marginal effects. The parameter listener' is 'MultiScreenConflgurationListener'. Since the MSM 101 version, the fremoveMultiScreenConfigurationListener (MultiScreenConfi 132 200849990 2713 lpif gurationListener)' method 1586 has been applied. fgetMultiScreenConfigurations()f Method 1568 sets ffMultiScreenConfiguration[] getMultiScreenConfigurations〇ff and gets all the display multi-screen configuration groups currently associated with this display screen. The configuration type of any such multi-screen configuration cannot be 'SCREEN-CONFIGURATION —DISPLAYlKiL 1416. fgetMultiScreenConfigurations()' Method 1568 Returns a non-empty array of ▼MultiScreenConfiguration’. If the call line is not allowed?MonitorAppPermission(f?multiscreen.configurationff)f , Bay 1J fgetMultiScreenConfigurations() f method 1568 is issued!java,lang.SecurityExceptionf ° Since the MSM 101 version, the application has been applied 61]\41111^〇^611( ^〇11;%11瓜1^〇115()? Method 1568 〇'getMultiScreenConfigurations(String)'Method 1570 Sets ?fMultiScreenConfiguration[] getMultiScreenConfigurations(java.lang.String screenConfigurationType)'', and gets related to this display screen The special type displays multiple screen configurations. The parameter fscreenConfigurationType' is (1) the following defined constant: 'MultiScreenConfiguration, interface 1220: {'SCREEN CONFIGURATION NON PIP, 1420, 'SCREEN CONFIGURATION PIP' 1422 ————- 5 133 200849990 27131pif ' SCREEN_CONFIGURATION_POPf 1424 with 'SCREEN—CONFIGURATION—GENERAL' 1418}, or (2) some other platform-related values not scheduled for multi-screen configuration type. 'getMultiScreenConfigurations(String)f method 1570 returns fMultiScreenConfiguration The array of f or the backhaul "empty" depends on whether a particular configuration type is supported. If the call line does not allow fMonitorAppPermission(nmultiscreen.configurationff)f, the shell 1J 'getMultiScreenConfigurations(String)' method 1570 issues fjava.lang.SecurityException'. If fscreenConfigurationTypef is fSCREEN_CONFIGURATIONJDISPLAY, or it is undefined, or the platform implementation is unknown, then fgetMultiScreenConfigurations(String)' method 1570 issues 'java.lang.IllegalArgumentException'. The 'getMultiScreenConfigurations(String)' method 1570 has been applied since the MSM 101 release. The fgetMultiScreenConfiguration()' method 1566 sets the MMultiScreenConfiguration getMultiScreenConfiguration()n and gets the current active multi-screen configuration for this display. ▼getMultiScreenConfiguration()f*& 1566 Applies to this display the current active display fMultiScreenConfiguration’ of the screen. If 'HScreen' is not a display screen, 134 200849990 2713 lpif fgetMultiScreenConfiguration()? Method 1566 Issues ▼java.lang.IllegalStateException'. The fgetMultiScreenConfiguration()' method 1566 has been applied since the MSM 101 release. Figure 16A shows the level of the Java Suite ▼org.ocap.ui' according to an embodiment of the present invention as defined by 1111^〇^11]\4&11&861*'1260.

The level of the Java suite f〇rg.ocap.ui丨fMultiScreenManagerf1260 is a low level of "ava.lang·Object", and '▼ All Implemented Interfaces'' includes forg.davic.resources.ResourceServer' 〇

Java Suite 'org.ocap.ui' level 'MultiScreenManager' 1260 set ''public abstract class MultiScreenManager', enhanced 'extends java.lang.Object' and implemented as ▼implements org.davic.resources.ResourceServer 丨0 ' The MultiScreenManagef level is a summary, separate management level, implemented by the 0CAP host platform that provides multi-screen management services. Other semantic restrictions and behaviors to be applied will be detailed in the present invention. Since the MSM 101 version, the Java Suite 'org has been applied .ocap.ur level 'MultiScreenManager' 1260 Figure 16B shows the architecture of the java suite 'org.ocap.ui' level 'MultiScreenManager' 1260 according to an embodiment of the invention 1600 〇 level 'MultiScreenManager' 1260 architect 1602 setting ''protected MultiScreenManager〇n and protected preset architects. Since the MSM 101 version, fMultiScreenManager() has been applied. 135 200849990^ I VD pil pil 1602 16 Figures 16C to 16F show Java Suite according to an embodiment of the present invention' Org.ocap.uif level ']\41111^(^^11]\^11&§61^ List of methods for 1260 1630.

The method list 1630 of the Java Suite forg.ocap.ui' level 1\41111^8 (^6611?^&11&861''1260 includes at least one of the following: fvoid addMultiScreenConfigurationListener(MultiScreenConfigura tionListener listener)' Method 1632, Void addPlayerScreenDevices(javax.media.Player player, org.havi.ui.HScreenDevicef] devices)' Method 1634, Void addResourceStatusListener(org.davic.resources.ResourceStat usListener listener) 'Method 1636,?org.havi.ui.HScreen[] fmdScreens(javax.tv.service.selection.ServiceContext context) 'method 1638 , forg.havi.ui.HScreen[] getCompatibleScreens(org.ocap.hardware.VideoOutputPort port)f Method 1640, forg.havi.ui.HScreen getDefaultScreen( )f method 1642, forg.havi.ui.HScreen getEmptyScreen() 'method 1644,^static MultiScreenManager getlnstance() 'method 1646, 'MultiScreenConfiguration getMultiScreenConfiguration()' method 1648 , ?MultiScreenConfiguration getMultiScreenConfiguration(org.havi.ui.HScreen screen )' Method 1650, fMultiScr eenConfiguration[] getMultiScreenConfigurations()' Method 1652, fMultiScreenConfiguration[] 136 200849990 27131pif getMultiScreenConfigurations(java.lang.String screenConflgurationType) 'Method 1654, forg.havi.ui.HScreen getOutputPortScreen(org.ocap.hardware.VideoOutputPort port)' Method 1656 , forg.havi.ui.HScreenDevice[] getPlayerScreenDevices〇avax.media.Player player)1 Method 1658, 'org.havLui.HScreen[] getScreens()f Method 1660, 丨boolean isEmptyScreen(org.havi.ui.HScreen screen ) Method 1662 , 'boolean isEmptyScreenDevice(org.havi.ui.HScreenDevice device)▼ Method 1664, Void moveSeryiceContexts(org.havi.ui.HScreen src, org.havi.ui.HScreen dst , javax.tv.service.selection .ServiceContextf] contexts)1 Method 1666, Void removeMultiScreenConfigurationListener(MultiScreenConfi gurationListener listener)' Method 1668, Void removePlayerScreenDevices(javax.media.Player player, org.havi.ui.HScreenDevice[] devices)'Method 1670, Void removeResourceS tatusListener(org.davic.resources.Resource StatusListener listener)1 Method 1672, Void requestMultiScreenConfigurationChange(MultiScreenConfig uration configuration, java.util.Dictionary serviceContextAssociations)f Method 1674, 'boolean sameResources(org.havi.ui.HScreenDevice device 15 org.havi .ui.HScreenDevice device2'method 1676, 'boolean 137 200849990 2713 lpif sameResources(org.havi.ui.HScreen screen 19 org.havi.ui-HScreen screen2' Method 1678, 'boolean sameResources(javax.ty.seryice*selection. ServiceContext scl9 javax.tv.service.selection.ServiceContext sc2f Method 1680, Void setMultiScreenConfiguration(MultiScreenConfiguration configuration, java.util.Dictionary serviceContextAssociations)' Method 1682 with 'void swapServiceContexts(org.havi.ui.HScreen screen 1, org.havi. ui.HScreen screen2, javax.tv.service.selection.ServiceContext[] exclusions)' Method 1684. Method 1690 from level 'java.lang.Objecf includes at least one of the following: fdonef, 'equals', 'finalize', 'getClass', 'hashCode', 'notify', 'notifyAll', 'toString', ' Wait', 'wait', and ?wait' o The method 1695 from the 'org.davic.resources.ResourceServer' interface includes at least one of the following: 'addResourceStatusEventListener1 and 'removeResourceStatusEventListener'. The 'getScreens()' method 1660 sets "public org.havi.ui.HScreen] getScreens()n and gets the accessible 'HScreen' group. The setting of the returned 'HScreen' must be determined as follows. When the 138 200849990 2713 lpif 〇CAP of fMonitorAppPermission(t?multiscreen.configurationff)f is allowed to be applied to the call, it is necessary to return the display screen and the fHScreen' of each logical screen. When calling this method, it can be accessed through any access. MultiScreenConfiguration' is in contact. Otherwise, the respective display screens associated with the accessible 'ServiceContext' and the TIScreenf of each logical screen are returned (directly or indirectly) for presentation or possible presentation. The first of the returned 'HScreen[]' arrays, HScreen, has to be equal to the value returned by the fgetDefaultScreen()f method 1642 of the MultiScreenManager' level 1260. Subsequent elements of this backhaul array do not follow the same order' and the application may not rely on the order of these subsequent elements. The 'HScreen' group returned by the 'getScreens〇' method 1660 can be changed during the application lifecycle, for example, when adding or removing screens from an accessible multi-screen configuration. However, on behalf of the application preset 'HScreen, HScreen, the reference may not remain fixed during the application life cycle. That is, from the point of view of the intended application, the MSM application must always return the same, HScreen' reference, the same as the first component of the fHScreen' backhaul array. When the fgetScreens()f method 1660 returns a value with the ▼MultiScreenConfigurationEvent.MULTI—SCREEN—CONFI GURATION—CHANGING’ event or

'MultiScreenContextEvent.MULTI—SCREEN—CONTEXT—S ERVICE-CONTEXT-CHANGED' event generation/distribution between fgetScreens (all returned by y method 1660, HScreen, may not equal empty fHScreen'. *fgetScreens〇' method 1660 Each of the returned, HScreen, can be returned to the fHScreenDevice 'group' which differs from its 'getHbackgrounddevices(), 139 200849990 2713 lpif , getHVideoDevices〇' and getHGraphicsDevices()' methods during the application lifecycle. However, as follows Said, under the definition of fgetDefauitScreen〇f* method 1642, through 'getHbackgrounddevices〇f, fgetHVideoDevices〇, and, getHGraphicsDevices〇, group, libackgrounddevice', fVideoDevicef and fHGraphicsDevice' groups are returned by default 'HScreen' The life cycle needs to be fixed, and the underlying device resources and configuration of these preset fHScreenDevice's can be changed. When the empty fgetScreensO' method 1660 returns the value and when the 'MultiScreenConfigurationEvent.MULTI-SCREEN-CONFI GURATION_CHANGING' event is generated or MultiScreenContextEvent.MULTI—SCREEN—CONTEXT_S ERVICE—CONTEXT—CHANGED, any background, image, or graphics device of any fHScreenf returned by the getScreens()f method 1660 between events, ie 'Hbackgrounddevic^, ▼HVideoDevicef4fHGraphicsDevice ', may not be equal to the special subtype of empty THScreenDevicef. *fgetScreens〇 'Method 1660 returned 'HScreen' returned by the 'getHbackgrounddevices〇f, fgetHVideoDevices()f and 'getHGraphicsDevices〇f method's fHScreenDevice' number here' HScreenf may change during its life cycle. If there is a change, it is produced

fMultiScreenContextEvent.MULTI SCREEN CONTEXT D EVICES_CHANGEDf event and spread to all staging fMultiScreenContextListener' 〇140 200849990 2713 lpif If the number of specific types of fHScreenDevice' increases or remains the same (for a specific fHScreenf), then it is passed back to this application. The reference to 'HScreenDevice' must be kept practicable and, under the choice of MSM implementation, must (1) be reused to represent the new underlying device resources of such a screen device; or (2) be reset to the appropriate Subtype of empty "HScreenDevic^. In the former case, the re-used fHScreenDevice▼ must exist in the settings of the screen device returned by the method, getHbackgrounddevicesO,, 'getHVideoDevices()' or 'getliGraphicsDevicesO, depending on its screen type. In the latter case, the status is reset to the empty fHScreenDevice, and the status, HScreenDevice, cannot be stored in the settings of the screen device returned by 'getHbackgrounddevices〇,, 'getHVideoDevices〇' or 'getHGraphicsDevices〇. If the number of a particular type of fHScreenDevice is reduced (for a particular fHScreenf), then the reference to the non-preset 'HScreenDevice' that was previously passed back to this application must be reset to the empty screen device state and may not be returned by fHScreenf In the screen device group. The net effect of the above specific behavior is that only the application itself, HScreen, and the application of the preset 'HScreenDevice' can be accessed and used continuously without knowing the existence of the MSM function. In contrast, applications that access non-preset 'HScreenf' or non-preset 'HScreenDevice' need to monitor changes to the current platform and display multi-screen configurations and changes to the set of screen devices associated with the non-preset screen. If the previously referenced non-preset, HS creen, is reset to the empty screen 141 200849990 Z/ ipif state, this application can detect this fact because of the multi-screen configuration change, by comparing the appropriate fMultiScreenConfigurationEvent' Get the 'HScreenf reference group and the 'HScreen' reference group that was obtained after the event. After this event, the reset to empty state will no longer exist in HScreen, which is returned by the 'getScreens〇' method 1660. Even the previously obtained fHScreeW can be questioned whether it was reset by using fisEmptyScreen(HScreen)' as defined by the 'Multi ScreenManager' level 1260. Finally, if the app continues to use fHScreeW after this reset, its behavior is defined and unchanged. Similarly, if the non-preset fHScreenDevicef that was previously referenced is reset to the empty screen state, because of the multi-screen configuration change, 'this application can detect this fact by comparing it before the appropriate 'Multi ScreenContextEvent' The obtained hs creen, the reference group and the fHScreenf reference group obtained after the event. After this event, the fHScreen' that is reset to the empty state will no longer be accessed by the accessible, HScreenf returned by 'getScreens(), method 1660. Even, previously obtained, HScreen, can be asked whether it is re-assigned by the fisEmptyScreenDevice (HScreeIlDevice) method defined by the 'MultiScreenManager' level 1260. Finally, if the application continues to use this reset, HScreen, its behavior is defined and unchanged. If, HScreen', ie S, does not implement the 'MultiScreenConfigurableContext' interface 1210 (for example, because it was not configurable when it was originally created and the VIS1VI implementation will selectively implement this interface to the special 'HScreen') and if new The underlying screen resources are group 142 200849990 2713 lpif state (and therefore, this interface can be implemented on HScreen representing the underlying screen resources of this group) 'When multiple screens and configuration changes, msm implementation can no longer use S to The new layer listens to the resource group, but can reset s to the empty state. ‘getscreens〇|Method 1660 returns a non-empty array, HScreen, as described above. Since the MSM 101 version, 々etScreens() has been applied, method i 66〇. (4) DefaultScreen(), method 1642 Set "public org.havi.ui.HScreen getDefaultScreenO" and get the default 'HScreen'. By the return of getDefaultScreenO▼ method 1642, Jake Qiu, must represent the current set of the default low-level screen device group and its current startup HAVi curtain group. In addition, HScreen’ can represent the currently configured non-preset low-level screen set and its configuration. The returned default 'HScreenf' is intended to be pre-set, from the point of view of the application currently calling or the application being called by this method. If the context in which the 'getDefaultScreen()' method 1642 is called by the platform does not imply a special application, then the return value is undefined and must depend on the implementation, including, for example, a backhaul "empty". The reference returned by SetDefaultScreen〇' method 1642 must remain fixed during the application life cycle. Even 'by default Hscreen's fgetDefaultHbackgrounddevice()?9 fgetDefaultHVideoDevice()f and 'getDefaultHGraphicsDevice(), the method's default fHScreenDevice' group must remain fixed 143 200849990 Z / 1J ipif for this application life cycle . Despite the fixed nature of the reference, the underlying device resources and underlying configuration of these device resources may change over the life of the application. 0 Any non-preset background image or graphics device returned by the 'getDefaultScreen〇f method 1642, also That is, fHbackgrounddevicef, fHVideoDevicef4fHGraphicsDevice', cannot be equal to its special subtype of empty ^HScreenDevic, when this method is returned and when generated

fMultiScreenConfigurationEvent.MULTI_SCREEN_CONFI GURATION_CHANGINGf ^

• MultiScreenContextEvent.MULTI SCREEN CONTEXT S — — — ERVICE—CONTEXT—CHANGED’ when. If 'getDefaultHbackgrounddevice(), 'getDefaultHVideoDevice()' and any of the 'hScreenConfiguration' parameters of any of the preset fHScreenDevice's returned by the 'getDefaultHGraphicsDevice()f method (or the resulting screen device type specific parameters) are in the application life cycle Within the change, the appropriate fHScreenConfigurationEventf is generated and distributed to all the staging fHScreenConfigurationListener'. Similarly, if any of the values returned by any of the challenge Cget*T methods of interface 1230 are changed by the 1MultiScreenContext implemented by the default 'HScreen', then the appropriate 'MultiScreenContextEvent' is generated and distributed to all temporary stores. MultiScreenContextListenerf 〇 If any of the fHScreenfs returned by the getDefaultScreen()f method 1642 implements the 144 200849990 27131pif of the 'MultiScreenConfigurableContext' interface 1210, then each 'HScreen' returned by this method must implement the 'MultiScreenConfigurableContext' interface 1210, regardless of Whether the underlying screen resource represented by any of the returned fHScreen' is configurable. The 'getDefaultScreenQ' method 1642 returns 'HScreen' as described above. Since the MSM 101 version, has been applied, getDefaultScreen〇f method 1642 〇

TmdScreens(ServiceContext)f Method 1638 sets "public org.havi.ui.HScreen[] findScreens(javax.tv.service.selection.ServiceContext context)" and finds at least one accessible screen associated with the particular service context. The service context can be related to one, one or more, HScreen, ie TmdScreens(ServiceContext), method 1638 finds the accessible 'HScreen, group associated with a particular 'ServiceContext'. If fgetScreens〇' method 1660 Return (or possibly post back), HScreen' (when called while calling the same application), HScreen, is accessible (for some applications). The parameter 'context' is ' ServiceContext, 'fmdScreens(ServiceContext)' method 1638 postback, HScreen, array or passback "null" value. If specific, ServiceC〇ntext, related to some accessible 'HScreen', then 'HScreen' must exist in Cannot be, empty, value, and non-empty in the backhaul array. Otherwise, return, null," means that s er er er er er er er er er erSince the MSM version 1〇1, the 145 200849990 2/1.5iplf ‘fmdScreens(ServiceContext)' method 1638 has been applied. The 'getOutputPortScreen(VideoOutputPort)' method 1656 sets "public org.havi.ui.HScreen getOutputPortScreen(org.ocap.hardware.VideoOutputPort port)'' and gets a screen related to an output port. Given a special 'VideoOutputPorf,' getOutputPortScreen(VideoOutputPort)' method 1656, fHScreenf associated with this is obtained for presentation. The parameter 'port' is 'VideoOutputPort'. The 'getOutputPortScreen(VideoOutputPort)' method 1656 returns 'HScreen' associated with this particular ,, or returns ''empty'' if the correlation does not exist. Since the MSM 101 version, fgetOutputPortScreen(VideoOutputPort)f;^^ 1656 has been applied. The 'getCompatibleScreens(VideoOutputPort)' method 1640 sets the "public org.havi.ui.HScreen port getCompatibleScreens(org.ocap.hardware.VideoOutputPort port)" and gets an accessible set of screens compatible with the output port. VideoOutputPorf , 'getCompatibleScreens(VideoOutputPort)' Method 1640 gets a subgroup of 'HScreen' (larger set back by fgetScreens() f method 1660, which may be related to this for presentation. Parameters > 011 'Yes'\^(160〇1^1油011:'. 'getCompatibleScreens(VideoOutputPort)' method 1640 returns a (possibly empty) 'HScreen' array, which is related to a specific 埠. 146 200849990 2713 Ipif since MSM 101 version After that, the getCompatibleScreens(VideoOutputPort)' method 1640 has been applied.

The 'getMultiScreenConfigurationsO' method 1652 sets '’public MultiScreenConfiguration[] getMultiScreenConfigurations()M and pays to all current multi-screen configuration groups supported by this platform, regardless of their configuration type. The multi-screen configuration group returned by the 'getMultiScreenConfigurationsO' method 1652 must include all screen multi-screen configurations (only display screens) and all display multi-screen configurations (including no more than one display screen and any number) Logic screen). The order of the multi-screen configuration returned by the 'getMultiScreenConfigurations〇' method 1652 is not defined in the present invention. , getMultiScreenConfigurations()' method 1652 returns the fMultiScreenConflguration’ P car column. The 'getMultiScreenConflgurations()' method 1652 must issue a Tjava.lang.SecurityException if the call line does not allow 'MonitorAppPermission(''multiscreen.configuration')'. Since the MSM 101 version, the fgetMultiScreenConfigurations()' method 1652 〇'getMultiScreenConfigurations has been applied (String) 'Method 1654 Set ''public Multi S creenConflguration [] getMultiScreenConfigurations(java.lang. String screenConfigurationType)" and get a multi-screen configuration of a special configuration type. 147 200849990 2713 The lpif parameter "screenConfigurationType" is one of the following values: (1) one of the 歹丨] constants defined by 'MultiScreenConfiguration': {'SCREEN a CONFIGURATION-DISPLAY' 1416, 'SCREEN-CONFIGURATION-NON-PIP '1420, 'SCREEN-CONFIGURATIONJPIP' 1422, SCREEN CONFIGURATION POP1 1424, , SCREEN-CONFIGURATION_GENERAI; 1418}, or (2) Other platform-related values not scheduled for the multi-screen configuration type. The 'getMultiScreenConfigurations(String)' method 1654 The multi-screen configuration group passed by the ISJ must include all of the multi-screen configurations of this particular type, which appear in the array returned by the 'getMultiScreenConfigurationsO' method 1652. The order of the multi-screen configuration returned by the fgetMultiScreenConfigurations(String)' method 1654 is not defined in the present invention. The 'getMultiScreenConfigurations(String)' method 1654 returns the fMultiScreenConfigurationf array or returns an "empty" value, depending on whether this particular configuration type is supported. The 'getMultiScreenConfigurations(String)f method 1654 issues 'java.lang.SecurityException' if the beer call line is not allowed ‘MonitorAppPermission(nmultiscreen.configurationn)f. The 'getMultiScreenConfigurations(String)' method 1654 has been applied since the MSM 101 release. fgetMultiScreenConfiguration(HScreen)' method 1650 Settings ’’public MultiScreenConfiguration 148 200849990 2713 lpif getMultiScreenConfiguration(org.havi.ui.HScreen screen)n& A multi-screen configuration for a particular glory. The established THScreenf must be related to one or only one multi-screen configuration; however, because a single underlying screen may be shared by multiple, HScreenf (multiple references), the underlying screen (with its constituent resources) may be associated with more than one multi-screen configuration . The parameter 'screen' is fHScreenf. ▼getMultiScreenConfiguration(HScreen)'Method 1650 Returns ▼MultiScreenConfiguration1, where the specific fHScreen' is a constitutive screen or ''null value'' if the specific fHScreeiV is alone (ie, not owned by multiple screen configurations, such as This may be the case if it is an empty screen.) The 'getMultiScreenConfiguration(HScreen)' method 1650 has been applied since the MSM 101 version. ▼getMultiScreenConfiguration()' method 1648 Set '’public MultiScreenConfiguration getMultiScreenConfiguration()n and get the multi-screen configuration for each platform currently launched. The 'getMultiScreenConfiguration()' method 1648 returns the currently launched platform 'MultiScreenConfiguration'. The fgetMultiScreenConfiguration()' method 1648 has been applied since the MSM 101 release. The 'setMultiScreenConfiguration()' method 1682 sets the ''public void setMultiScreenConflguration(MultiScreenConfiguration configuration, java.util.Dictionary 149 200849990 L! lJipif serviceContextAssociations)n& setting to display the multi-screen configuration for each platform currently launched. If a particular Configuration' is currently displaying multiple screen configurations on each platform, the fsetMultiScreenConfiguration()f method 1682 returns the value and does not produce any marginal effects unless 'SecurityException' is applied. If the specific YonfiguratioiV is not currently displaying multiple screen configurations on each platform and if 'SecurityException', 'IllegalArgumentExceptionf and 'IllegalStateException' are not applied, then 'setMultiScreenConfiguration()f* method 1682 synchronizes multiple screen configuration changes for each platform, which is handled by OCAP MSM Enhanced Edition is defined. If the 'serviceContextAssociations' argument is specific (eg, not empty), then any ServiceContext that the current call application can access must be related to no screen or specific (new) platform multi-screen configuration (or in each Display the application screen in the multi-screen configuration). If no association matches certain accessible ServiceContext's, if some accessible 'ServiceContext' does not exist in a particular association, or if it exists, no such application screen exists in the new platform multi-screen configuration (or in its multiple display screens) "Required to be associated with a specific multi-screen configuration of the default service context-related screen, that is, the honor screen returned by configuration.getDefaultServiceContextScreenO. To match the accessibility of 'ServiceContextf', the reference is treated as a specific 150 200849990 2713 lpif fserviceContextAssociations' dictionary keyword, the virtual method fequals(Object)f must be used for this keyword, assuming that fsetMultiScreenConfiguration〇' method 1682 behaves the same In Object.equals (the default implementation of the Objecty method. In the context of a given application, the MSM host implementation must maintain a one-to-one relationship between the 'ServiceContext' that is exposed to the application and the set of underlying service context resources. If the MSM host If the implementation cannot maintain this relationship, the MSM implementation can treat the two different sets of underlying service context resources as the same service context when composing the 'serviceContextAssociations' dictionary: eg 'if at a different time, a single fServiceContextf is separated from the resource The underlying collection, or a single collection of underlying service context resources can be treated as two different service contexts, for example, if at a particular time, two different 'ServiceContexfs refer to the same underlying collection of resources. For processing related service contexts (which Be The state of the DFC component of the image pipeline of the setMultiScreenConfiguration() 'method 1682 darkly swapped or moved between screens' is not affected by the execution of the 'setMultiScreenConfiguration()' method 1682. The parameter 'configuration' is, MultiScreenConfiguration, which becomes the current The launched platforms display multiple screen configurations. If the parameter 'serviceContextAssociations' is not empty, the keyword of ▼Dictionary' is 'ServiceContext' and its value is string, where its string value is defined as follows: (1) If The string value is ,, _,,, then the screen is not applied (in this case, the matching service context is not related to any screen, after the configuration change), (2) otherwise, if the string value is "*&quot ;, then apply this screen to 151 200849990 z / 〇ipn all screens, (3) Otherwise, if the string value is the 'MultiScreenContext.getID()' method back to the screen identification code, then apply this screen, ( 4) Otherwise, if the string value is the screen type returned by the fMultiScreenContext.getScreenCategory() method, then the application has this Any other screen of the new configuration, (5) Otherwise, if the string value is a semicolon-separated list of screen identification codes, apply the newly configured screens with matching identification codes, (6) otherwise, if the words The string value is a semicolon-separated list of screen types, and the new screens with the matching type are applied. '(7) Otherwise, if the string value is a screen-separated list of screen identification codes or screen types, the application has a match. Identify the code or type of newly configured screen, (8) Otherwise, apply this newly configured preset service context to the screen. The 'setMultiScreenConfiguration()' method 1682 issues fjava.lang.SecurityExceptionT if the call line does not allow 'MonitorAppPermission(’’multiscreen.configuration"). The 'setMultiScreenConfiguration()' method 1682 issues fjava.lang.IllegalArgumentExceptionf, if the parameter 'configuration' is not fMultiScreenManager.getMultiScreenConfigurations(SCREE N^ONFIGURATriON+DISPLAYy is returned for each platform multi-screen configuration. 'setMultiScreenConfiguration()' method 1682 Issue fjava .lang.IllegalStateException', if the MSM implementation (1) does not allow the startup of a particular multi-screen configuration, (2) if the 'setMultiScreenConfiguration()' method 1682 has been previously called and the change processing step 152 200849990 27131pif is not completed, or (3) if The start of the call method is not allowed. Since the MSM 101 version, the 'setMultiScreenConfiguration()' method 1682 has been applied. The frequestMultiScreenConfigurationChange 'method 1674 is set by "public void requestMultiScreenConfigurationChange(MultiScreenConfig uration configuration, java.utiLDictionary serviceContextAssociations)ff It is also necessary to display changes to the multi-screen configuration for each platform currently launched. If specific 'configurati' On' is currently configured, unless the application of f S ecurity Exception1 , 'requestMultiScreenConfigurationChangef method 1674 returns the value without any marginal effect. If the specific 'configuration' is not currently showing multiple screen configurations for each platform, and if 'SecurityException is not applied ', 'IllegalArgumentException' and 'IllegalStateExceptionf, then ▼requestMultiScreenConfigurationChange' method 1674 initially performs asynchronous changes to the current multi-screen configuration for each platform, where the semantics of the 'setMultiScreenConfiguration()' method 1682 is applied, except in the generation

After the TMultiScreenConfiguration.MULTI—SCREEN—CONFIGURA TION—CHANGING’ event (but before its spread), the 'requestMultiScreenConfigurationChange’ method 1674 must be returned immediately. 153 200849990 2/lJipif Parameter '(:〇11丘81^&1^〇11' is ']\/[1111;18(^6611(^〇11丘81^&1^〇11', The currently launched screen configuration. The parameter null value f4fDictionary', whose keyword is 'ServiceContext' and whose value is 'String', whose semantics are defined by 'setMultiScreenConfiguration(··)'. The 'requestMultiScreenConfigurationChangef method 1674 issues fjava.lang. SecurityExceptionf, if the call line does not allow fMonitorAppPermission(''multiscreen.configuration")'. The frequestMultiScreenConfigurationChange' method 1674 issues 'java.lang.IllegalStateException': (1) if the MSM implementation does not allow the startup of a particular multi-screen configuration, (2) If the 'requestMultiScreenConfigurationChange' method 1674 has been previously called and the change processing step is not completed, or (3) the start is not allowed when the method is called. Since the MSM 101 version, the 'requestMultiScreenConfigurationChange' method 1674 〇 'addMultiScreenConfigurationListener' method 1632 has been applied. "public Void addMultiScreenConflgurationListener(MultiScreenConflgura tionListener listener)'', and join the listener to be notified, once the multi-screen configuration event occurs. If you have previously joined the listener and have not been removed later, try to add it again. Marginal effect. The configuration event applied to this individual fMultiScreenManager must be limited to affect the completion of the available display screen. If an event defined by fMultiScreenConfigurationEvent is generated, the MSM implementation must notify each of the temporary screen configurations. 154 200849990 27131pif Listener. The reference listener' is fMultiScreenConfigurationListener'. The 'addMultiScreenConfigurationListener' method 1632 has been applied since the MSM 101 release. fremoveMultiScreenConfigurationListener1*;^: 1668 History "public void removeMultiScreenConfigurationListener(MultiScreenConfi gurationListener listener)" and removes the listener who was previously added to be notified, once a multi-screen configuration event occurs. If a particular listener is not currently staged as a listener, then trying to remove it does not produce a marginal effect. The parameter is also {61 grab' is ']\41111^(^611(^011 and 1^11〇111^{61^1·,. Since the MSM 101 version, the 'removeMultiScreenConfigurationListenerf method 1668 〇faddResourceStatusListener' method 1636 has been applied. "public void addResourceStatusListener(org.davic.resources.ResourceStat usListener listener)'' and join the resource state listener. The parameter listener' is 'ResourceStatusUstener!. Since the MSM 101 version, the 'addResourceStatusListener' method 1636 has been applied. The fremoveResourceStatusListener' method 1672 set,, public void removeResourceStatusListener(org.davic.resources.Resource StatusListener listener)'' and remove the resource state listener. 155 200849990

2 / i J ipiT parameter 'listener'SfResourceStatusListener'. Since the MSM 101 version, the fremoveResourceStatusListener' method 1672 〇 fswapServiceContexts' method 1684 has been applied to set "public void swapServiceContexts(org.havi.ui.HScreen screen 1? org.havi.ui.HScreen screen2,

javax.tv.service.selection.ServiceContext[] exclusions)’’ and automatically exchanges service contexts between the two 'HScreer^'. The 'swapServiceContexts' method 1684 is a convenient way to support the common functionality of exchanging content presentations between screens. Similar results obtained by the 'swapServiceContexts' method 1684 can also be accomplished using fMultiScreenConfigurableContext.addServiceContext(··), with the fMOScreenConfigurableContext.removeServiceContext( )f method being removed and joining the service context to a more general-purpose screen with special accessibility screens. In addition, the use of more general methods can lead to more rendering of the state of the art of artificial technology than the use of the swapServiceContexts method; [684, the death is because the fswapServiceContexts' method 1684 automatic exchange error is being used to deal with the service context (I am The state of the image pipeline being exchanged by the 'swapServiceContexts' method 1684) is not available to the 'swapServiceContexts' method 1684's Boo--parameter 'screen1', which is the 'HScreen', its service context 'screen2' service context. The parent, the parameter 'SCreen2' is 'HScreen', and its service context can be exchanged for the service context of 156 200849990 27131pif 'screenl'. The parameter Exclusions', if not ''null'', is a non-empty array of 'ServiceContext' to be excluded from the exchange operation, i.e., its screen correlation is not affected by the exchange. The fswapServiceContextsf method 1684 issues fjava.lang.SecurityException? if the call line does not allow 'MonitorAppPermission(f,multiscreeiLconfigurationn)'. The ?swapServiceContextsf method 1684 issues fjava.lang.IllegalStateException' if one of the following is true: (1) the image is being rendered as a component image instead of the background image on the screen; or (2) the 'ServiceContextT' of the particular screen cannot be changed, That is, for example, the platform uses a specific 'ServiceContexf' to permanently associate with the screen. The wapServiceContexts' method 1684 has been applied since the MSM 101 release. The 'moveServiceContexts' method 1666 sets "public void moveServiceContexts(org.havi.ui.HScreen src, org.havi.ui.HScreen dst, javax.tv.service.selection.ServiceContext[] contexts)'' and automatically sets the specific service The situation group moves from one fHScreenf to another 'HScreen'. The fmoveServiceContexts' method 1666 is a convenient method to support the common functionality of moving content presentations between screens for a given set of situational contexts. Similar results obtained by *fmoveServiceContexts' method 1666 can also be exploited with ▼MultiScreenConfigurableContext.addServiceContexts(..), with 157 200849990 2VL3lpif fMultiScreenConfigurableContext.removeServiceContexts(..)i method removal and joining service contexts for special accessible screens A universal mechanism to complete. Furthermore, using a more general approach can result in more transitional rendering techniques than using fmoveServiceContexts, method 1666, because of the automatic exchange semantics of the 'moveServiceContexts' method 1666. Is being used to deal with the service context (it is being

The DFC state of the image pipeline of the fmoveServiceContexts' method 1666 is not affected by the execution of the 'moveServiceContexts1 method 1666'. A parameter from which a particular service situation can be moved. A parameter from which a particular service situation can be moved. The context parameter is a non-empty array of fServiceContextf, moving from , src, screen to the 'dst’ screen. The 'moveServiceContexts' method 1666 issues fjava.lang.SecurityException, if the call line does not allow 'MonitorAppPermission(nmultiscreen.configurationif),. The 'moveServiceContexts' method 1666 issues 'java.lang.IllegalArgumentException1 if a particular 'ServiceContext' is not currently associated with the source 'HScreen', 'src'. fmoveServiceContexts! Method 1666 issues java.lang.IllegalStateException' if one of the following is true: (1) On the screen, the image is being rendered as a component image instead of the background image; (2) A particular fServiceContextf for a particular screen cannot be removed That is, if the platform uses a specific 'ServiceContext' with a permanent association to the screen; or, (3) the non-summary fServiceContextf is already associated with the destination screen and the platform only 158 200849990 • 2713 lpif supports a non-summary ServiceContexf on each screen. Method 1666 has been applied since the MSM 101 release. fgetPlayerScreenDevices' Method 1658 sets ''public org.havi.ui.HScreenDevice[] getPlayerScreenDevices(javax.media.Player player)" and gets the currently specified set of screen devices for use by the Java Media Framework (JMF) media player The parameter fplayerf is a JMF player to challenge its screen device set. The fgetPlayerScreenDevicesf method 1658 is an 'HScreenDevice' array that is empty if and only if there is no associated screen device. Since the MSM 101 version, the fgetPlayerScreenDevicesf method has been applied. 1658. 'addPlayerScreenDevicesf Method 1634 sets ''public void addPlayerScreenDevices(javax.media.Player player, org.havi.ui.HScreenDevice[] devices)" and adds the screen device to the media player. The parameter ^player' is JMF 'Player' to challenge a particular screen device. The parameter 'devices' is a non-empty array of fHScreenDevicef to render certain types of content from a particular media player. taddPlayerScreenDevices, method 1634 issues java.lang.SecurityException' If the calling line is not allowed 'MonitorAppPermission (" multiscreenxontext ")'. 159 200849990 z / υ ιμιι , addPlayerScreenDeviCes' Method 1634 Issue "ava.lang.megalStateException" if any of the following is true: (1) specific, player' is not in a stopped state; (2) specific screen ^ such as "乂不Some of the underlying screen devices that are compatible with a particular 'player'; (3) 'devices' cannot be used by the application, for example, because they are reserved exclusively by another application; or some of the underlying screen devices of 'devices' are already associated with the media. Player, and this device does not support the multimedia player. Since the MSM 101 version, the details of the method 1634 of the 'addPlayerScreenDevices丨 method 1634 〇faddPlayerScreenDevices' have been applied. Refer to rPlayerf, 'HScreenDevicef. 'removePlayerScreenDevices' Method 1670 Set "public void removePlayerScreenDevices〇avax.media.Player player, org.havi.ui.HScreenDevice[] devices)'' and remove the screen device from the media player. That is, fHScreenDevice's all or non-empty groups are rendered (or related) Presenting the screen of a specific media player Group removal. If 'devices1 is 'null', all screen device associations are removed. 0 fremovePlayerScreenDevicesf method 1670 issues fjava.lang.SecurityExceptionf if the call line does not allow 'MonitorAppPermission("multiscreen.contextn)' 'removePlayerScreenDevices1 method 1670 issues 'java.lang.IllegalArgumentException' if 'devices' is not 'null' and fdevices4々 is not related to a specific Tlayer'. 160 200849990 2713 lpif

The VemovePlayerScreenDevices' method 1670 issues ▼java.lang.IllegalStateException' if the particular fplayer' is not in a stopped state. The fremovePlayerScreenDevices' method 1670 has been applied since the MSM 101 release. The getEmptyScreen()f method 1644 sets ’’public org.havi.ui.HScreen getEmptyScreen()" and gets a separate empty fHScreen’. Using the empty IHScreen, 'getEmptyScreen()f method 1644, you can get the reference to the empty fHScreenDevice', empty 'HScreenConfiguration' and empty 'HScreenConfigTemplate' for each of the available subtypes (such as ^Hbackgrounddevice, fHVideoDevicef, ?HGraphicsDevicef, etc.). The presence of the 'getEmptyScreen' method 1644 is primarily to support functional MSM functions such as the semantics of fisEmptyScreen()f, fisEmptyScreenDevice()', 'sameResources()', and the like. The 'getEmptyScreen()' method 1644 returns an empty 'HScreen'. Since the MSM 101 version, the method 1644 〇▼isEmptyScreen' method 1662 has been applied as the 1£11^}^〇^11() method 1662 to set npublic boolean isEmptyScreen(org.havi.ui.HScreen screen)'' and decides if From the point of view of conditional satisfaction, whether fHScreen' is equal to the empty ▼HScreen'. If 'screen' does not implement 'MultiScreenConfigurableContext', 161 200849990 Z / ijipn The restrictions on fMultiScreenConfigurableContextf must be considered equal. The parameter 'screen' is 'HScreen'. The fisEmptyScreen’ method 1662 returns true ', if the specific 'screen' is equal to the empty 'HScreen'. Since the MSM 101 version, the 'isEmptyScreenf method 1662 〇risEmptyScreenDevicef method 1664 has been set to "public boolean isEmptyScreenDevice(org.havi.ui.HScreenDevice device)", and it has been decided whether the special subtype is from the point of view of conditional satisfaction. Empty fHScreenDevicef. The device parameter is 'HScreenDevic〆: 'Hbackgrounddevice', fHVideoDevice' or GraphicsDevice' which is one of the following subtypes. The fisEmptyScreenDevice' method 1664 is passed back; true, if the specific 'device' is equal to the empty fHScreenDevicef of the matching subtype. Method 1664 has been applied since the MSM 101 release. The 'sameResources(HScreen,HScreen)' method 1678 sets npublic boolean sameResources(org.havi.ui.HScreen screenl, org.havi.ui.HScreenscreen2)n and determines whether two fHScreen's represent the same underlying platform resources and underlying resources. State, that is, whether they are equal for these underlying resources. To determine equality, the following conditions are used: • If one of fscreenl' and 'screen2' is equal to the empty 'HScreen', then this 162 200849990 2713 lpif two screens are not equal to the underlying resources; screenl.getHbackgrounddevicesO1 The screen device returned, fBDl· and the screen device fBD2' returned from fscreen2.getHbackgrounddevices()' do not have 'sameResources(BDl, BD2)' return 'true', then the two screen pairs The underlying resources are not equal; • If there is no one for the screen device TVDlf returned by 丨screenl.getHVideoDevices()' and the screen device VD2' returned by fscreen2.getHVideoDevices()fm, 'sameResources(VD 1 , VD2)f returns 'true', then the two screens are not equal to the underlying resources; • if the screen is returned by fscreenl.getHGraphicsDevices〇' and returned by fscreen2.getHGraphicsDevices()f The screen device 'GD21 does not have one, 'sameResources(GDl, GD2) f returns 'true', then the two screens are not equal to the underlying resources. • If, for the established equivalent setting of the template argument, ?screenl.getBestConflguration(..)f and 'screen2egetBestConfiguration(··)' are not returned (nominally out of order) equal to the setting of fHScreenConfigurationf, then the two screens are on the bottom Resources and Lv are not equal, • If, for the established equivalent set of screen configuration arguments, fscreenl.getCoherentScreenConfigurations(..)f and 'screen2.getCoherentScreenConflgurations(··)' do not return the same fHScreenConfigurationf settings, then the two The screen is not equal to the underlying resources, 163 200849990 Z/IJipir • If, for the established equivalent set of screen configuration arguments, fscreenl .setCoherentScreenConfigurations(..)f and ^screer^.setCoherentScreenConfigurationsC·)' are not returned the same Values or changes to the screen set associated with a particular screen configuration argument make these screen devices equal, then the two screens are not equal to the underlying resources; • If none of the above conditions are true, fscreenl and 'screen2' The underlying resources are equal; the parameter ' Screen Γ and ‘ screen2 ’ are fHS creen1. If the specific screen is equal to the above conditions, return the fax value. The fsameResources(HScreen, HScreen) method 1678 has been applied since the MSM 101 release. ,sameResources(HScreenDevice,HScreenDevice)'method 1676 sets ''public boolean sameResources(org.havi.ui.HScreenDevice device 1, org.havi.ui.HScreenDevice device2)'' and decides whether the two fHScreenDevice% tables are the same underlying platform The status of resources and underlying resources, that is, whether they are equal for these underlying resources. To determine equality, the following conditions apply: • If 'devicel' is different from 'device2', HB ackgroundde vicef 9 'HVideoDevice', or 'HGraphicsDevice', then the two screen devices are not equal to the underlying resources. • If one of 'devicel· and fdevice2' is equal to the empty sub-fHScreenDevice' of the appropriate subtype, then the two screen devices are not 164 for the underlying resources. 200849990 2713 lpif

• If 'devicel.getFlickerFilter()' is not the same as fdevice2.getFlickerFilter (the return value of y, the two screen devices are not equal to the underlying resource; • if 'devicel.getlnterlaced()' and fdevice2.getInterlaced〇 The return value of f is not the same, then the two screen devices are not equal to the underlying resources; • If the return value of f device l.getPixelAspectRatio()' and fdevice2.getPixelAspectRatio〇' are not the same, then the two screen devices Not equal to the underlying resources; • If the return value of fdevicel.getPixelResolution()' and fdevice2.getPixelResolution〇' are not the same, then the two screen devices are not equal to the underlying resources; • If fdevicel.getScreenArea( ) f and 'device2.getScreenArea (y's return value is not the same, then the two screen devices are not equal to the underlying resources; • If given equal 'HScreenConfiguration' ('SCl' and 'SC21) as controversial, 'devicel.getOffsel^SCl)' is not the same as the return value of 4evice2.getOffset(SC2)', then the two screen devices are on the underlying resources. Words are not equal; • If given equal fHScreenConfiguration, (, SCl$, SC2f) and equal Toint' ΓΡΓ and fP2f) are controversial, 'devicel.convertTo(SCl, Pl), and fdevice2.convertTo(SC2, P2 ), the return value is not the same, then the two screen devices are not related to the underlying resources 165 200849990, etc.; • If f device l.getConfigurations()f and 'device2.getConfigurations〇f are not returned (nominally If the fHScreenConfigurationf group is not in order, the two screens are not equal to the underlying resources. • If fdevice1.getCurrentConfiguration()f and device2.getCurrentConfiguration()f do not return the same fHScreenConfigurationf, then the two screens For the underlying resources, it is not the same as f, etc.; • If f device l.getDefaultConfiguration()f and device2.getDefaultConfiguration()f do not return the same 'HScreenConfiguration' ' then the two screens are not for the underlying resources. Equivalent; • If given an equal template argument or a model argument group, device 1 .getBestConfiguration(· ·)' with fdevice2 .getBestConfiguration(··)' does not return equal (^IlScreenConfiguration' settings, then the two screens are not specific to the underlying resources, • if 'devicel' and 'device2' are 'Hbackgrounddevice' and if fdevicel. setBackgroundConfiguration(..)f does not return the same value as 'device2.setBackgroundConfiguration(..)f. When the equal fHBackgroundConfigurationf is specified as an argument, then the two screens are not equal to the underlying resource; • If 'devicel' is Fdevice2' is 'HVideoDevice' and if 166 200849990 2713 Ipif (1) fdevicel .setVideoConfiguration(..)f and 'deviceS.setVideoConfigurationC·)1 do not return the same value when equal 'HVideoConfiguration' is specified as argument, (2) 'devicel.getVideoSource()' and fdevice2.getVideoSource()f do not return nominally equal image sources, or (3) f device l.getVideoController()f and fdevice2.getVideoController〇f do not return nominally equal images Controller, then the two screens are not equal to the underlying resources; • If fdevicel 'And 'device2' is 'HGraphicsDevice▼ and if fdevicel.setGraphicsConfiguration(..)f and 'device2.setGraphicsConfiguration(··)' do not return the same value when equal fHGraphicsConfigurationf is specified as argument, then the two screens are against the underlying resources It is not equal; • If none of the above conditions are true, then Wevicel· and 4evice2f are considered equal, for the underlying resources; the parameters 'devicel' and , device2' are 'HScreenDevice,'. fsameResources(HScreenDevice, HScreenDevice)' Method 1676 returns the true value, if the specified screens are equal, according to the above conditions. Since the MSM 101 version, the 'sameResources(HScreenDevice, HScreenDevice)' method 1676 has been applied. fsameResources(ServiceContext? ServiceContext)' Method 1680 sets ''public boolean sameResources(javax.tv.service.selection.ServiceContext scl. 167 200849990 i/iMpn javax.tv.service.selection.ServiceContextsc2)n, and decides, two' Whether ServiceContexf represents the same underlying platform resource and underlying resource state, that is, whether these underlying resources are equal. The parameters 'scl· and 'sc2' are 'ServiceContext'. fsameResources(ServiceContext5 ServiceContext), method 1680 returns 'true' if the specific service contexts are equal (ie, representing the same underlying resource and resource state). Since the MSM 101 release, the fsameResources(ServiceContext, ServiceContext)f method 1680 has been applied. 'geUnstance〇' Method 1646 Set "public static MultiScreenManager getlnstance()" and get a separate 'MultiScreenManager'. Pass back 'MultiScreenManager'. Since MSM 101 version, !getlnstance()' method 1646 has been applied Figure 17 shows The interface list 1700 and rank list 1710 of the java suite 'org.ocap.ui.evenf according to an embodiment of the invention. The suite 'org.ocap.ui.event1 has an enhanced version of the HAVi user interface event level, including OCAP specific remote events Interface with multiple screen management events. The interface list 1700 of the suite brg.ocap.ui.evenf includes at least one of the following: 'MultiScreenConfigurationListener▼ interface 1702 and a fMultiScreenContextListenerf interface 1704 〇 'MultiScreenConfigurationListener' interface 1702 to notify the system and the application Change the 'flag status change for fIvlultiScreenManager', or for a display of multiple screens or for each display multi-screen 168 200849990 2713 lpif shows the status change of fHScreenf, or a change to a specific 'MultiScreenConfiguration'. fMultiScreenCont extListenerf interface 1704 The change caused by the system and application of the switch to the 'MultiScreenContext.' The list of classes for the package 'org.ocap.ui.event1' includes at least one of the following: ?MultiScreenConflgurationEventf Level\η\2 'MultiScreenContextEvent 'Level 1714, 'MultiScreenEvenf level 1716 and 'MultiScreenResourceEventf level 1718. 'MultiScreenConfigurationEvent▼ level 1712 will report a change in status for fMultiScreenManager% overall status change, or for a display fHScreen' for each level or each display multi-screen configuration, Or a change to a specific 'MultiScreenConfiguration1'. fMultiScreenContextEvent' Level 1714 is used to report changes to the ▼MultiScreenContext' to interested listeners. The 'MultiScreenEvent' level 1716 is a summary, base level, used to organize event identification codes that are used by different event types associated with multi-screen management functions. ▼MultiScreenResourceEvent’ level 1718 reports resource state changes for multiple screen related resources. Figure 18A shows the definition of level 1712 for the fMultiScreenConfigurationEvent of the java suite 丨org.ocap.ui.event', in accordance with an embodiment of the present invention. Kit 'org.ocap.ui.event' - 169 200849990 L· i U ipii The 'Java Type of 'MultiScreenConfigurationEvent' level 1712 is defined as the sub-level of brg.ocap.ui.event.MultiScreenEvent', rorg.ocap .ui.event.MultiScreenEvent, a sub-level of ▼java.util.EventObject', and 'java.util.EventObject' is a sub-level of java.lang. The suite?org.ocap.ui.event1?MultiScreenConfigurationEvent' level 1712 includes as ''All Implemented Interfacesf4々fjava.io.Serializable', set "public class MultiScreenConfigurationEvent'' and force strong fMultiScreenEventf ° 'MultiScreenConfigurationEvent' level 1712 Reporting system and application changes to the overall state of 'MultiScreenManager1', or the status of a display fHScreenf for each level or each display multi-screen configuration, or for the special SfMultiScreenConfiguratioiy. The following change types will cause 'MultiScreenConfigurationEvent' Level 1712 generation ·· • The multi-screen configuration of each platform currently started by 'MultiScreenManager' is changed from one screen configuration to another multi-screen configuration; • The current display is determined by a display fHScreenf The screen configuration is changed from one multi-screen configuration to another multi-screen configuration; • When the relevant KfMultiScreenConfigurationf screen group changes (ie, the screen is added or removed from the multi-screen configuration). Since MSM After version 101, the 'MultiScreen ConflgurationEvent' level 1712 of the suite 'org.ocap.ui.evenf has been applied. 170 200849990 27131pif Figure 18B shows the fMultiScreenConfigurationEvent' level 1712 of the Java suite 'org.ocap.ui.event' in accordance with an embodiment of the present invention. The list of fields is 1800.

The list of fields of the Java Suite 'org.ocap.ui.eventf!MultiScreenConflgurationEvent' level 1712 includes at least one of the following: 'static int MULTI-SCREEN_CONFIGURATION—CHANGED' block 1802/static int MULTI-SCREEN—CONFIGURATION_CHANGINGf block 1804 /static int MULTI—SCREEN—CONFIGURATION—LAST' Field 1806, 丨static int MULTI SCREEN CONFIGURATION SCREEN ADDED, —— — _ STOP 1808 and 'static int MULTI SCREEN CONFIGURATION SCREEN REMOVE D' STOP 1810. Field 1820 derived from the 'MultiScreenEvent1 level 1716 of the Java suite 'org.ocap.ui.eventf' includes at least one of the following: 'MULTI-SCREEN-CONFIGURATIONJFIRST, and 'MULTI-SCREEN_CONTEXT-FIRST'. Field 1825 from level fjava.utiLEventObjecf includes a 4ourc€ position. ▼MULTI-SCREEN—CONFIGURATION A CHANGING, field 1804 sets "public static final int 171 200849990 2713 Ipif MULTI—SCREEN—CONFIGURATION—CHANGING”. The changes to the currently launched platforms or displays are made by fMultiScreenManagerf or some Determined by 'HScreen', has been initialized, where the return value by fgetSource〇' must be affected by 'MultiScreenManager丨' or 'HScreen', and the return value of 'getRelatedQ' must be followed by MultiScreenConflguration '.MULTI-SCREEN-CONFIGURATION-CHANGING] 804 events cannot be spread to applications that do not allow fMonitorAppPermission(f!multiscreen.configurationff)f. Since MSM 101 version, 'MULTI-SCREEN_CONFIGURATION_CHANGING, field 1804 has been applied. 'MULTI —SCREEN_CONnGURAlTK)N—CHANGED, field 1802 sets "public static final int MULTI SCREEN CONFIGURATION CHANGED”. At present - - - - ― each platform or each display fMultiScreenConfiguratior^, which is determined by fMultiScreenManagerf or a display fHScreen¥;f, has been changed, where the return value of fgetSource〇f must be affected by fMultiScreenManagerf or display fHScreen ', and the return value from 'getRelated()' must be the previously started fMultiScreenConflguratior^. Since the MSM 101 version, 'MULTI-SCREEN-CONFIGURATION—CHANGED has been applied, field 1802 〇172 200849990 2713 lpif MULTI a SCREEN CONFIGURATION A SCREEN-AD DED' block 1808 sets "public static final int MULTI SCREEN CONFIGURATION SCREEN ADDED" — —— — . The screen group associated with fMultiScreenConflgurationf has changed and has been added to the new screen, where the value returned by 'getSource〇' must be the affected 'MultiScreenConfiguration▼', and the value returned by 'getRelated(y must be new Join the 'HScreen'.

Except for the last time between the MULTI-SCREEN-CONFIGURATION-CHANGING' 1804 event and the ▼MULTI-SCREEN-CONFIGURATION-CHANGED, 1802 event generation, the screen cannot be added and the 'MULTI SCREEN CONFIGURATION SCREEN ADDED, — _ — 1808 event is not available. Produced as a multi-screen configuration, which is currently configured for each platform or for each display multiple screens. Applied since MSM 101 version

fMULTI SCREEN CONFIGURATION SCREEN ADDED —- — _ Field 1808. 'MULTI-SCREEN-CONFIGURATION-SCREEN-RE MOVED’ STOP 1810 SET ’’public static final int MULTI A SCREEN—CONFIGURATION—SCREEN A REMOVE Dn. Related to the fMultiScreenConfiguration% screen group has been changed, the existing screen is removed, where by getSource (y return value must be affected ''MultiScreenConfiguration', and return value by 'getRelated()' 173 200849990 27131 pit· Must be the newly removed fHScreenf. Except for the period of time after the last occurrence of fMULTI SCREEN CONFIGURATION CHANGING1 1804 — —— event, the event cannot be removed, and MULTI-SCREEN_CONFIGURATION—SCREEN —REMOV ED'1810 cannot be configured as a multi-screen configuration, which currently displays multiple screen configurations for each platform or case. Since the MSM 101 version, it has been applied.

fMULTI SCREEN CONFIGURATION SCREEN REMOV ———————— ED* Shelf 1810. ▼MULTI—SCREEN—CONFIGURATION—LAST, field 1806 sets "public static final int MULTI—SCREEN—CONFIGURATION—LAST", and is the last event identification code assigned to the 'MultiScreenConflgurationEvent’ event identification code. Since the MSM 101 version, it has been applied, MULTI-SCREEN-CONFIGURATION-LAST, block 1806. Figure 18C shows a schema listing 1830 of the level 'MultiScreenConfigurationEvent' 1712 of the Java suite forg.ocap.ui.event', in accordance with an embodiment of the present invention. The architecture list 1830 includes fMultiScreenConfigurationEvent(java.lang.Object source, int 174 200849990 2713 lpif id, java.lang.Object related)' 1832. The architect 1832 sets "public MultiScreenConfigurationEventQava.lang.Object source, int id, java.lang.Object related)" and constructs the 'MultiScreenConfigurationEvent' level 1712. The parameter '5〇111^' is for ']\41111;丨8 (^66111431^§61'', showing a reference to 'HScreen' or fMultiScreenConfigurationf, according to the specific event above.

The parameter fid' is the event identification code for this event, and its value must be one of the following: MULTI-SCREEN-CONFIGURATION-CHANGING,, fMULH-SCREEN-CONFIGURATION-CHANGED', ▼MULTI-SCREEN-CONFIGURATION-SCREEN-ADDED, or ▼MULTI—SCREEN—CONnGURATlON—SCREEN A REMOV ED,. The relevant parameter is a reference to 'MultiScreenConfiguration, or fHScreen, according to the specific event above. The architect 1832 of the 'MultiScreenConfigurationEvenf level 1712 has been applied since the MSM 101 release. Figure 18D shows a side of the level 'MultiScreenConfigurationEvent' 1712 of the java suite forg.ocap.ui.event? according to the embodiment of the present invention;

Level 1840 of the Java Suite forg.ocap.ui.event? includes a list of methods for fMultiScreenConfigurationEvent' 1712

Java.lang.Object getRelated〇' method 1842. The method 185 from level 175 200849990 27131pif 'org.ocap.ui.event.MultiScreenEvent' includes fgetldf; the method 1852 derived from the level fjava.util.EventObjectf includes at least one of the following: fgetSource', 'toString, . The method 1854 derived from the level Java.lang.Objecf includes at least one of the following: 'clone', 'equals1, 'finalize', 'getClass', fhashCode', fnotifyf, 'notifyAll', 'wait', fwait', and 'wait'. , getRelated(), method 1842 sets '’public java.lang.Object getRelated() ff and gets the relevant object for this event. That is, fgetRelated (y method 1842 returns the related object of this event, the value must be one of the following depending on the special event type: reference to 'MultiScreenConfigurationf' or reference to 'HScreen'. Since the MSMI01 version, The getRelated()' method 1842 is applied. Figure 19A shows the definition of the fMultiScreenConfigurationListener' interface 1702 of the Java suite 'org.ocap.ui.event', in accordance with an embodiment of the present invention.

The 'MultiScreenConflgurationListener' interface 1702 of the Java suite 'org.ocap.ui.event' includes 'java.util.EventListener' as a super interface, set ''public interface MultiScreenConfigurationListener'' and enhance 'java.util.EventListener'. fMultiScreenConfigurationListener' interface 1702 is used to notify the system and application of the overall state change of MMultiScreenManagef, or the change of state of a display fHScreen' for each flat or some display multi-screen configuration, or the change of a specific fMultiScreenConfigurationf. 176 200849990 2713 lpif since MSM 101 After the version, the 'MultiScreenConfigurationListener' interface 1702 has been applied. Figure 19B shows a method list 1900 of the fMultiScreenConfigurationListener' interface 1702 of the Java suite 'org.ocap.ui.event', in accordance with an embodiment of the present invention.

The method list 1900 of the 'MultiScreenConfigurationListener' interface 1702 of the Java suite 'org.ocap.ui. event' includes a 'void notify(MultiScreenConfigurationEvent evt)' method 1910. The 'notify' method 1910 sets ',v〇id notify(MultiScreenConfigurationEvent evt)n . When a ▼MultiScreenConfigurationEvent' is generated, this embodiment must call all of the temporary listener's 'notify' methods 1910 to report event information to the listeners as needed for special event semantics. When the event is

When fMultiScreenConfigurationEvent.MULTI_SCREEN_CONFI GURATION—CHANGING’, the notify’ method 1910 cannot be called unless the listener's application has been allowed to _fMonitorAppPermission(ffmultiscreen.configurationf,)f . Even, the implementation of the 'notify1 method 1910 must strictly limit the amount of processing that may occur because there is an absolute time limit for calls to the fnotifyf method 191 that can be applied by the listener. The parameter 'evt' is 'MultiScreenConfigurationEvent'. The 'notify method 1910 has been applied since the MSMI01 version. 177 200849990 2713 Ipif Figure 20A shows the definition of the Java Suite 'org.ocap.ui.event%TMultiScreenContextEvent' level 1714 in accordance with an embodiment of the present invention.

The 'MultiScreenContextEvent' level 1714 of the Java Suite forg.ocap.ui.event' is defined as a sub-level of ▼org.ocap.ui.event.MultiScreenEvent', where 'org.ocap.ui.event.MultiScreenEvent' is 'java.util The subclass of .EventObject' and 'java.util.EventObject' are sub-levels of fjava.lang.Object'.

The 'MultipleContextContextEvent' level 1714 of the Java Suite 'org.ocap.ui.event' ''All Implemented hiterfaces'' includes 'java.io.Serializable', which sets "public class MultiScreenContextEvent" and enhances ']\41111^8(^ 6611£\^111:' 〇'MultiScreenContextEvenf Level 1714 is used to report changes to 'Multi ScreenContexf' to interested listeners. The following types of changes will result in a MultiScreenContextEvenf level 1714: • a change in the associated 'ServiceContext'; fHScreen' changes; • related display changes in THScreen' area (range); • changes in fVideoOutputPortsf related settings; • display changes in THScreenf's sound focus; • screen visibility changes; • screen z-order changes; 178 200849990 2713 lpif • Contribute the sound source to the underlying 'HScreenDevice of 'HScreen', group changes; • Changes to the underlying fHScreenDevicef group, for example because of the addition/removal of ▼HScreenDevice', HScreen'; • the underlying 'HScreenDevice' of fHScreen' Z-order change The 'MultiScreenContex1; Event' level 1714 of the java suite 'org.ocap.ui.event' has been applied since the MSM 101 version. Figure 20B shows the java suite 'org.ocap.ui.event' in accordance with an embodiment of the present invention. 'MultiScreenContextEvent, field list 2000 for level 1714.

The ▼MultiscreenContextEvent' level 1714 of the Java Suite 'org.ocap.ui· event' has a list of at least one of the following: ' static int MULTI—SCREEN—CONTEXT—AUDIOJFOCUS—CHANGE Df Field 2002, 'static int MULTI— SCREEN CONTEXT AUDIO SOURCES—CHAN GED' STOP 2004, f static int MULTI—SCREEN—CONTEXT—DEVICES—CHANGED, field 2006, 'static int MULTI—SCREEN—CONTEXT—DEVICES—Z_ORDER—CHA NGEDf field 2008 , 'static int MULTI—SCREEN—CONTEXTJ3ISPLAY—AREA—CHANGE D' field 2010 , 'static int

MULTI-SCREEN—CONTEXTJDISPLAY—SCREEN—CHAN 179 200849990 2/Uipif GEDf Field 2012, 'static int MULTI One SCREEN_CONTEXT_OUTPUTJPORT_CHANGE Df Field 2014, 'static int MULTI One SCREEN_CONTEXT One SERVICE_CONTEXT_CHA NGED' Field 2016, 'static int MULTI-SCREEN —CONTEXT—VISIBILITY—CHANGED, field 2018, ? static int MULTI_SCREEN_CONTEXT—Z_ORDER—CHANGED' field 2020, and 'static int MULTI-SCREEN—CONTEXTS—LAST, field 2022. The block 2030 from the forg.ocap.ui.event.MultiScreenEvent' level includes at least one of the following: 'MULTI-SCREEN_CONFIGURATION_FIRST, and , MULTI-SCREEN-CONTEXT-FIRST, . Field 2035 from the 'java.util.EventObject' level includes 'source'. 'MULTI-SCREEN-CONTEXT-DEVICES-CHANGED' Block 2006 set "public static final int MULTI-SCREEN-CONTEXT-DEVICES_CHANGED,, and when fHScreenDevice\-related to the underlying fHScreenf of the source fMultiScreenContextf changes, it is related to This situation. Since the MSM 101 release, 'MULTTI-SCREEN—CONTEXTJDE VICES—CHANGED has been applied, field 2006.

fMULTI SCREEN CONTEXT DEVICES Z ORDER 180 200849990 27131pif CHANGED, field 2008 set,, public static final int MULTI a SCREEN—CONTEXT—DEVICES—Z_ORDER a CHA NGED”, and when related to the source 'MultiScreenContext', the bottom layer "HScreen^lIScreenDevice The group's Z-order changes when it is related to this situation. Since the MSM 101 version, fMULTI-SCREEN-CONTEXT-DEVICES-Z_ORDER-CHA NGED' has been applied to 2008. TMULTI-SCREEN-CONTEXT-SERVICE_CONTEXT ^CHANGED' 2016 Set ''public static final int MULTI_SCREEN_CONTEXT_SERVICE_CONTEXT_CHA NGED') and this is relevant when the underlying ▼HScreen%fServiceContext' associated with the source fMultiScreenContextf changes. Since the MSM 101 version, 'MULTI-SCREEN-CONTEXT-SERVICE-CONTEXT_CHA NGED, 2016 has been applied. 'MULTI a SCREEN-CONTEXT a DISPLAY-SCREEN-C HANGEDf stop 2012 set "public static final int

MULTI SCREEN CONTEXT DISPLAY SCREEN CHAN —* —— — . __ GED”, and when the display fHScreen’ related to the underlying fHScreenf of the source fMultiScreenContexf changes, it is related to this case. Since the MSM 101 version, it has been applied.

fMULTI SCREEN CONTEXT DISPLAY SCREEN CHAN ~ — —— _ GED’ field 2012. 181 200849990 Z / i 1 pif fMULTI a SCREEN_CONTEXT_DISPLAY an AREA_CH ANGEDf 2010 set ''public static final int MULTI a SCREEN_CONTEXT a DISPLAY an AREA_CHANGE Dtf, and when the area (range) of the display TIScreen' of the underlying fHScreen' assigned to the source fMultiScreenContextf is changed It is related to this situation. Since the MSM 101 version, MULH-SCREEN^CONTEXTJDISPLAY-AREA_CHANG E;D’ 2010 has been applied. 'MULTI_SCREEN a CONTEXT_OUTPUT_PORT_CHA NGEDf field 2014 sets ‘’public static final int MULTI—SCREEN_CONTEXT_OUTPUTJPORT_CHANGE D" and is related to this when the associated display image output group of the underlying fHScreenf of the source fMultiScreenContextf changes. Since the MSM 101 release, fMULTI-SCREEN-CONTEXT_OUTPUT-PORT_CHANGE D’ has been applied to 2014. The 'MULTI-SCREEN-CONTEXT-VISIBILITY-CHANGE ED’ block 2018 sets "public static final int MULTI-SCREEN_CONTEXT-VISIBILITY_CHANGED", and is related to this when the visibility of the underlying fHScreen' of the source 'MultiScreenContext' changes. Since the MSM 101 version, ‘MULTI—SCREEN_CONTEXT—VISIBILITY—CHANGED has been applied to block 2018. 182 200849990 2713 lpif 'MULTI-SCREEN-CONTEXT a Z-ORDER-CHANGE D' field 2020 set ''public static final int MULTI SCREEN CONTEXT Z ORDER CHANGED", and — _ — — — when the source 'MultiScreenContext1' of the underlying fHScreenf This is related to the Z sequence change. Since the MSM 101 version, 'MULTI-SCREEN-CONTEXT-Z_ORDER-CHANGED has been applied, field 2020.

'MULTI-SCREEN—CONTEXT_AUDIO_SOURCES—C HANGED’ field 2004 set "public static final int

MULTI—SCREEN—CONTEXT—AUDIO—SOURCES—CHAN GED”, and this is related when the source of the underlying 'HScreen' of the source 'MultiScreenContext' changes. Since the MSM 101 version, MULTIVEL SCREEN CONTEXT AUDIO SOURCES has been applied. CHAN — — — — — GED' field 2004. 'MULTI—SCREEN—CONTEXT—AUDIOJFOCUS—CHA NGED' field 2002 setting "public static final int MULTI—SCREEN—CONTEXT—AUDIO—FOCUS—CHANGE D”, and when The sound focus of the underlying 'HScreen' of the source 'MultiScreenContext' is changed when the screen source is changed. This event must be generated twice when the fHScreenf6 sound focus screen source is changed (after the change is completed: the first time is the 'MultiScreenContexf' of the logic screen that has lost the sound focus (if such a logic screen exists), The second time is 183 200849990, which is the fMultiScreenContextf of the display screen. In both cases, the source must be the 'MultiScreenContexf display screen. Applied since MSM 101 version

MULTI SCREEN CONTEXT AUDIO FOCUS CHANGE — — — — — D’ field 2002. fMULTI - SCREEN - CONTEXTS - LAST, field 2022 sets "public static final int MULTI - SCREEN - CONTEXTS - LAST', and is the last event identification code assigned to the 'MultiScreenConflgurationEvent' event identification code. Since the MSM 101 release, fMULTI-SCREEN-CONTEXTSJLAST has been applied, field 2022. Figure 20C shows a list of architectures 2040 for the 'MultiScreenContextEventf level 1714' of the java suite 'org.ocap.ui.evenf', in accordance with an embodiment of the present invention. The architecture list 2040 includes fMultiScreenContextEvent(java.lang.Object source, int id)' 2042. The architect 2042 sets "public MultiScreenContextEvent(java.lang.Object source, int id)ff 5 and ranks 1714. The parameter f source' is a reference to the 'Multi ScreenContext' interface. The parameter Id' is the event identification code of this event, and its value needs to be one of the following: ▼MULTI_SCREEN_CONTEXT_DEVICES_CHANGED, field 184 200849990 2713 Ipif 2006 , 'MULTI-SCREEN-CONTEXT a DEVICES a Z-ORDER A CHA NGED' block 2008, 'MULTI a SCREEN a CONTEXT a SERVICE a CONTEXTJ^HA NGEDf block 2016, 'MULTI-SCREEN-CONTEXT-DISPLAY-SCREEN-CHAN GED' block 2012,

"fMULTI-SCREEN-CONTEXT-DISPLAY-AREA-CHANG ED' field 2010, MULTI-SCREEN-CONTEXT_OUTPUTJPORT_CHANGE Df field 2014, ▼MULTI-SCREEN-CONTEXT-VISIBILITY-CHANGED' field 2018, 'MULTI-SCREEN-CONTEXT- Z-ORDER-CHANGED' field 2020,

'MULTI-SCREEN—CONTEXTAUDIO—SOURCES—CHAN (~, GED' field 2004 and 'MULTI-SCREEN—CONTEXT—AUDIOJFOCUS—CHANGE D' field 2002. Since the MSM 101 version, the structure list of ▼MultiScreenContextEventf level 1714 has been applied 2040. Figure 20D shows a method list 2050 of the Java suite 'org.ocap.ui.event4々'MultiScreenContextEvent' level 1714 in accordance with an embodiment of the present invention. 185 200849990 2/iJlpif by the Java suite 'org.ocap.ui.event, The method 2052 derived from the level 1716 includes fgetld'; and the method 2054 derived from the 'java.utiLEventObjecf level includes at least one of the following: the method 2056 derived from the fgetSourcef and 'toStringf.*fjava.lang.Object' levels includes the following At least one: fcl〇nef, 'eqUaisf, 'fmaiize,, 'getClass丨, 'hashCode', 'notify', fnotifyAll', 'wait', fwaitf, and 'wait' 0 FIG. 21A shows an embodiment in accordance with the present invention. The java suite 'org.ocap.ui.evenf' defines the 'MultiScreenContextListener' interface 1702.

The 'MultiScreenContextListener' interface 1702 of the Java suite 'org.ocap.ui.event' includes fjava.utiLEventListenerf as a super interface, which is set to 'public interface Multi ScreenContextListener' and force σ strong ▼java.util.EventListener'. 'MultiScreenConfigurationListenerf interface 1702 can notify the change to fMultiScreenContext' caused by the system and application. Since the MSM 101 version, the fMultiScreenConfigurationListener interface 1702 has been applied. Figure 21B shows the Java suite ▼org.ocap.ui.event' in accordance with an embodiment of the present invention. fMultiScreenContextListener' Method list 2100 of interface 1702. Method list 2100 of 'MultiScreenContextListener' interface 1702 includes 'notify(MultiScreenContextEvent evt)f method 2102 〇186 200849990 2713 lpif fnotify(MultiScreenContex1;Event)' Method 2102 Set ''void notify(MultiScreenContextEvent evt )". When the OCAP implementation changes fMultiScreenContext' to produce fMultiScreenContextEvent', this implementation must call all of the temporary listener's 'notify(MultiScreenContextEvent)' methods 2102 to report the change information to the listener. If the application that temporarily stores this listener does not allow 'MonitorAppPermission(nmultiscreen.context'')' and the source 'MultiScreenContext' associated with a particular fMultiScreenContextEventf is not related to fServiceContext' or 'ServiceContext' that is not accessible to this application, The method 1102 cannot be called on this listener; otherwise, it needs to be called on this listener. 'ServiceContext' can be accessed by the application if it is a postback passed back by the 'ServiceContextFactory.getServiceContexts()' method. Parameter 4丫1: 'is %1111^(^611(^〇1]^\1£red]11:'. Since the MSM 101 version, the 'notify(MultiScreenContextEvent)' method 2102 has been applied. Figure 22A shows The definition of the Java Suite 'org.ocap.ui.event^'MultiScreenEvent' level 1716 of the inventive embodiment.

The 'MultiScreenEvent1 level 1716 of the Java Suite 'org.ocap.ui.event' is defined as a sub-level of fjava.util.EventObjectf, and fjava.util.EventObject' is a sub-level of fjava.lang.Object'. 187 200849990 z / u ipif

The Java Suite 'org.ocap.ui.evenf', MultiScreenEventf level 1716 includes fjava.io.Serializablef as ''All Implemented Interfaces'' and includes at least one of the following: when MultinConsertEvent' of "Known Subclasses" and "MultiScreenContex1; Event' .

The 'MultiScreenEvent' level 1716 of the Java suite 'org.ocap.ui.event' sets "public abstract class MultiScreenEvent" and enhances 'java.util.EventObjecf. 'MultiScreenEvent' is the summary base level for organizing event identification codes. It is used by different types of events related to the multi-screen management function. Since the MSM 101 version, the 1MultiScreenEvent' level 1716 of the Java Suite forg.ocap.ui.event' has been applied. Figure 22B shows the java suite 'in accordance with an embodiment of the present invention' Org.ocap.ui.evenf's 'MultiScreenEventf level 1716's list of fields 2200.

The fMultiScreenEvent' level 1716 of the Java Suite 'org.ocap.ui.event' has a shelf list 2200 that includes at least one of the following: fstatic int MULIl-SCREEN-CONFIGURATION—FIRST' field 2202 and 'static int MULTI_SCREEN—CONTEXTJFIRST, block 2204. Field 2210 from the fjava.utiLEventObjectf level includes 'source, 'MULTI_SCREEN—CONFIGURATION—FIRSTf field 2202 is set "public static final int MULTl—SCREEN—CONFIGURATION—FIRST, and refers to 200849990 27131pif to ' MultiScreenConfigurationEvent' The first event identification code for the event identification code. Since the MSM 101 version, 'MULTI-SCREEN-CONFIGURATTIONJFIRST has been applied, block 2202. fMULTI-SCREEN-CONTEXTJFIRST, field 2204 set "public static final int MULTI- SCREEN—CONTEXT—FIRST”, and is the first event identification code assigned to the fMultiScreenContextEventf event identification code. Since the MSM 101 version, the MULTI-SCREEN-CONTEXT-FIRST'Block 2204 has been applied. Figure 22C shows a schema list 2220 for the 'MultiScreenEvent1 level 1716' of the java suite ▼org.ocap.ui.event', in accordance with an embodiment of the present invention.

MultiScreenEvent for Java Suite 'org.ocap.ui.event', Level 1716 Architecture List 2220 includes at least 'One Protected? MultiScreenEvent(java.lang.Object source, int id)? 2222 °

The "Architecture" level 2222 of the 'MultiScreenEvent' level 1716 of the Java Suite 'org.ocap.ui.event' sets "protected MultiScreenEvent(java.lang.Object source, int id)" and is the protected architect of MultiScreenEvent1. The parameter 'source' is a reference to the source of the event, which is defined by the discrete sub-level of fMultiScreenEvent' level 1716. The event identification code for the parameter fidlfMultiScreenEvent' level 1716. 189 200849990 l / 1 J ipif Since the MSM 101 version, the "Architect" 2222 of the 'MultiScreenEvent' level 1716 has been applied. Figure 22D shows a method listing 2230 of the Java Suite 'org.ocap.ui.eventW'MultiScreenEvent, level 1716, in accordance with an embodiment of the present invention.

The method list 2230 of the 'MultiScreenEvent' level 1716 of the Java Suite 'org.ocap.ui.event' includes the find getld()f method 2232. The method 2240 derived from the fjava.utiLEventObject' level includes at least the following ί, . . . . . fgetSource' and 1toString'. The method 2245 derived from the java.lang.Object' level includes at least one of the following: fclonef, 'equals', 'finalize', 'getClassf, 'hashCode', 'notify', 'notifyAll', 'wait', ' Wait' and !wait' o 'getld()' method 2232 sets "public int getId〇', and gets the event identification code associated with the fMultiScreenEventf level. The MultiScreenEvenf level event identification code is returned, which finds the sub-level of fMultiScreenEventf (fMultiScreenConfigurationEventf and ('MultiScreenContextEventf). Since the MSMI01 version, the 'getld()f method 2232 has been applied. Figure 23A shows the Java Suite forg according to an embodiment of the present invention Definition of 'MultiScreenResourceEvent1 level I7ig' for .ocap.ui.event'.

The MultiScreenResourceEventf level 1718 of the Java suite 'org.ocap.ui.event' is defined as a sub-level of forg.davic.resources.ResourceStatusEvent', and 190 200849990 2713 lpif 'org.davic.resources.ResourceStatusEvenf shell^ is fjava.utiLEventObjectf The sub-level, and fjava.util.EventObject' is again a sub-level of 'java.lang.Objecf.

The 'MultiScreenResourceEvent' level 1718 of the Java Suite forg.ocap.ui.event' includes: fjava.io.Serializable' as ''All Implemented Interfaces''. fMultiScreenResourceEvent' level 1718 setting for the Java suite 'org.ocap.ui.event' ''public class MultiScreenResourceEvent' and enhance 'org.davic.resources.ResourceStatusEvent'. The 'MultiScreenResourceEvent' level is used to report changes in the resource status of multiple screen related resources. Since the MSM 101 release, the Java Suite forg.ocap.ui.event4々'MultiScreenResourceEvent' level 1718 has been applied. Figure 23B shows a list of fields 2300 for the fMultiScreenResourceEvent' level 1718 of the java suite 'org.ocap.ui.event', in accordance with an embodiment of the present invention.

The fMultiScreenResourceEvenf level 1718 of the Java suite 'org.ocap.ui.event' includes at least one of the following: 'static int MULTI_SCREEN—RESOURCE_SCREEN—RELEASED, block 2302 with 'static int MULTI one SCREEN one RESOURCE one SCREEN one RESERVED, field 2304 . The *fjava.utiLEventObject' level of the block 2310 includes the fsource' field. 191 200849990 2/Uipif 'MULTI a SCREEN a RESOURCE_SCREEN a RELEASE D' field 2302 set ''public static final int MULTI-SCREENJIESOURCE-SCREEN-RELEASED'. Just released the reserved screen, representing this screen (or its configuration screen device) ) can now be retained (ie, they are currently unreserved). Since the MSM 101 version, fMULTI-SCREEN-RESOURCE-SCREEN-RELEASED has been applied, field 2302. fMULTI-SCREEN-RESOURCE_SCREEN-RESERVE Df field 2304 Set "public static final int MULTI SCREEN RESOURCE SCREEN RESERVED,,. The playback of the screen is just allowed to the application, representing this screen (including its constituent screen devices) is no longer unreserved. Since the MSM 101 version Thereafter, MULTI-SCREEN-RESOURCE-SCREEN-RESERVED, field 2304 has been applied. Figure 23C shows a schema list 2320 of the fMultiScreenResourceEventf level 1718 of the Java suite 'org.ocap.ui.event' in accordance with an embodiment of the present invention. 'MultiScreenResourceEvent 'List of Structures for Level 1718 2320 Including 'MultiScreenResourceEvent(java.lang.Object source, int id)f 2322. 'MultiScreenResourceEvent' level 1718's architect 2322 sets ''public MultiScreenResourceEvent(java.lang.Object 192 200849990 27131pif source,int id)", and is 'MultiScreenResourceEvent, the architect. The parameter fsourcd is a reference to the 'HScreen1' whose resource status has changed. The parameter fid' is the event identifier of the 'MultiScreenResourceEvent' level 1718. Since the MSM 101 version, the architect of the 'MultiScreenResourceEventf level 1718 has been applied 2232. Figure 23D shows a list 2330 of methods for the 'MultiScreenResourceEvent' level of the java suite 'org.ocap.ui.event', in accordance with an embodiment of the present invention.

The method list 2330 of the ▼MultiScreenResourceEvent' level of the Java Suite 'org.ocap.ui.event' includes at least one of the following: 'int getld()' method 2332 and fjava.lang.Object getSource()f method 2334. The method 2340 derived from the 'java.util.EventObject' level includes 1toString'; the method 2345 derived from the 'java.lang.Object' level includes at least one of the following: fjava.lang.Object, include at least one of ' Clone', 'equals', 'finalize', 'getClassVhashCode,, 'notify', 'notifyAll', 'wait', 'wait' and 'wait'. The 'getSource〇' method 2334 sets "public java.lang.Object getSource〇n" and gets the source object that generated this event. 'getSource()' method 2334 overload (〇verride)fgetSource' in 'org.davic.resources.ResourceStatusEvent 'Level.' getSourceQ, method 2334 returns the reference to the pair, or its sub-level. Since the MSM 101 version, the 'getSource()f method 2334 has been applied. 'getld()f method 2332 sets "public int getld() , ', and get phase 193 200849990 2713 lpif About 'MultiScreenResourceEvent' level 1718 resource event identification code. ▼MultiScreenResourceEvent' Level 1718 event identification code will be returned, where the identification code is one of the following: fMULTl-SCREEN-RESOURCE- SCREEN-RELEASED' field 2302, 'MULTI-SCREEN-RESOURCE-SCREEN-RESERVED, block 2304} 〇f ' Since the MSMI01 version, the 'getldCT method 2332 has been applied. Here, refer to Figures 24A-24D, 25A~25E 26A to 26D, 27, 28A and 28B, 29 to describe application use restrictions according to an embodiment of the present invention. For example, it is necessary to satisfy the preconditions (Figs. 24A to 24C) and postconditions (Figs. 25A to 25E) of the multi-screen configuration change processing, that is, the multi-screen reconfiguration. In this example, the pre-conditions and the post-conditions The condition must satisfy the following pseudoririL · Han · 1 · platform implementation MSM, as defined; C, 2 · more than one explicit multi-screen configuration and is accessible; 3 · caller has fMonitorAppPermission(nmultiscreenxonfigurationff)f 4. Do not generate TMultiScreenConfigurationEvent.MULTI—SCREEN—CONFI GURATION__CHANGINGf ^ fMultiScreenConfigurationEvent.MULTI—SCREEN a CONFI GURATION—CHANGED' event, execute RfverifyC〇nstraints()' 194 200849990 2713 lpif method instead of VerifyConstraints()' method call fsetMultiScreenConflguration( ) the period of direct result of f; 5. does not produce

▼MultiScreenConfigurationEvent.MULTI—SCREEN—CONFI GURATION—SCREEN an ADDING' or, MultiScreenConfigurationEvent.MULTI_SCREEN—CONFI GURATION—SCREEN—REMOVED, event, during the execution of the f verify Constraints() method; 6. The application issues “1” 1allow_default_device_reconflgfK Multi-screen use in the description; 7. In the configuration change, the platform reserves the key preset screen device configuration parameters, especially the screen area, the pixel resolution and the pixel size ratio, that is, it does not use the application The advantage of 'allowjefault^device^reconflg' has been issued for "1" to reconfigure the default screen device parameters (note that this verification procedure can be expanded to cover situations where the platform does not reserve these parameters, ie, listenable A suitable 'HScreenConflgurationEvent' or 'MultiScreenContextEvent' is used to inform the platform that these parameters are not reserved. Figures 24A-24C show preconditions for changing the multi-screen architecture in accordance with an embodiment of the present invention. At S2410 of Fig. 24A, the constant number is verified. According to an embodiment of the invention, the static invariant is verified as a precondition. In this example, the 'verifyInvariantConstraints()' method for verifying the constant number can be described with reference to Figs. 26A to 26D. 0 195 200849990 z/ijipif At S2420 of Fig. 24A, the preset screen is recorded. At S2430 of Fig. 24A, the preset background screen device and key configuration parameters are recorded. At S2440 of Fig. 24B, the preset image screen device and key configuration parameters are recorded. At S2450 of Fig. 24B, the preset graphic screen device and key configuration parameters are recorded. At S2460 of Fig. 24C, a non-preset screen is recorded. At S2470 of Fig. 24C, a non-preset screen device is recorded. In S2480 of Figure 24C, the different configurations of the current configuration are found. Figure 24D shows a process of changing a multi-screen architecture in accordance with an embodiment of the present invention. Change the multi-screen configuration at S2490 ’. That is, the multi-screen configuration is changed by fMSM.setMultiScreenConfiguration (MSC2, null), and fMULTl SCREEN CONFIGURATION CHANGING, and 3, MUL1TI_SCREEN-CONFIGURATION are waited by the 'waitForMultiScreenConfigurationChangingEvent〇 method and the 'waitForMultiScreenConfigurationChangedEvent()' method. The generation of the CHANGED' event. 25A to 25E show preconditions for changing a multi-screen frame according to an embodiment of the present invention. At S2500 of Fig. 25A, the constant number is verified. According to an embodiment of the invention, the static invariant is verified as a postcondition. In this case, verify the constant number of 196 200849990 27131pif

The VerifyInvariantConstraints()' method will be described with reference to Figs. 26A to 26D. In S2505 of Figure 25, the current multi-screen configuration is a new configuration. In S2510 of Figure 25, the new preset screen must be the same as the preset firefly in S2515 of Figure 25, and the new preset background screen (if any) must be the same as the old preset background screen (if it exists) unless ( The application is issued as ''1'' 411〇\¥一36£&pool_^¥ to ~1^011 him, where: after the configuration is configured, there is no longer a preset background device available, the previous preset background The device must be reset to the empty background state of the screen device. In S2520 of Figure 25, the new preset background screen device must have the same screen area as the old preset background device, if any, the degree of depreciation and Prime size ratio. ι Solve in S2525 of Figure 25C, the new preset image screen device (if present) must be the same as the old preset image screen device (if any), unless (applies as "Γ", all〇 W—default-device~re_ fetch, where the re-configured no longer has a preset image device available, and the pre-preset image splice must be reset to the empty image screen device state. In Figure 25C S2530, if any, new preset image display It needs to have the same screen area as the old preset image screen device, and compare the resolution with the size of the element. i turn ^ In S2535 of Figure 25D, the new preset graphics device (if any) must be the same as the old preset. Graphical screen device (if any), unless the application issues a "Γ" fall〇w-defauit-device-reconfig, which, 199, 499, 499, 2, 2, 1 1 1 pif has a preset graphics device available, the front preset graphics The state of the graphic screen device that is heavy 5 is empty. In S2540 of Fig. 25D, if there is a 砵k setting, it must be compared with the old preset graphic screen device. In the Chung Chin area, the picture is in S2545 of Figure 25E, and if it is no longer a screen, the non-preset screens that come to it cannot be the same as the empty screen. ~ The same as the empty screen, otherwise ' In S2500 of FIG. 25A, the re-assembly device and the device are, for example, non-preset screens=non-preset screen devices, otherwise, they are not the same as the space, and the same as the empty pictures 26Α~26D are displayed according to the present invention. ▲ restrictions on invariants. &歹, the verification constant number in the figure 5, must be multi-filament in Figure 26A, S2610, must be a, a, only in the map back, must:: f f screen configuration. Configuration. 4 — _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ~T meaning and there is a lot of stems in the S2630' of Figure 26B. The screen in the eve of the curtain configuration is not available in S2635 in Tuhu, and currently there are two different screen configurations. 198 200849990 2713 The lpif screen project cannot represent the same resources. At S2640 of Fig. 26C, it is necessary to have a current preset fee screen. In S2645 of Fig. 26B, the current preset screen cannot be equal to the empty screen. In S2650 of Figure 26C, the current multi-screen configuration must represent the same resources as the default screen. In S2655 of Figure 26C, there must be a group of non-empty accessible Dimensions in Figure 26C#S266G. Currently, the preset screen must be an explicit member of the group of accessible viewers. The screen is installed in S2665 of Fig. 26C, and any current setting of the preset screen cannot be equal to the empty background screen device. Month 豕 In the S2670 survey, any preset screen can not be equal to the empty image screen device.豕 幕 screen In S2675 of Figure 26D, any preset screen can not be equal to the empty graphics device. 7 poor screens Figure 27 shows the definition of each ^!getNonDefaultScreens()' method in accordance with the present invention. The getNonDefaultScreens()' method of j gets non-pre-" ('SXINDi), by returning a non-preset screen on the MSM (sset the sound screens 28A and 28B showing real = ND according to the present invention). The definition of the 'getNonDefaultScreenDevices()f method. For example, in S2810 of FIG. 28A, the background image of the background screen and the non-preset screen device of the graphic screen device are respectively checked in S2820 of FIG. 28B, and the background=1 strong image screen is separately checked and returned. Non-preset screen skirting of the device and the graphic screen device '199 200849990 2/13 Jpif Figure 29 shows various methods in accordance with an embodiment of the present invention. At S2910, the wait state is maintained until the ▼MultiScreenConfigurationEvent.MULTI_SCREEN_CONFI GURATION-CHANGING' event is generated. At S2920, the wait state is maintained until the event "MultiScreenConflgurationEvent.MULTI_SCREEN-CONFI GURATION-CHANGED" is generated. At S2930, the fault is checked and reported. Here, reference is made to Figs. 30A, 30B, 31, 32A, 32B, 33A, 33B and 34A to 34C to describe how to change and join the 〇CAP standard to implement the embodiment of the present invention in an OCAP environment. The OCAP application does not support or hardly support screen management for multi-display or multi-logic screens, as defined by the HAVi Hscreen level, especially for PIP and POP functions. Therefore, in order to implement the OCAP MSM' OCAP application of the present invention, it is necessary to verify the presence of ''ocap.api.option.msm', Java system attributes. If you verify "ocap.apLoption.msm, Java system properties' then the OCAP application can discover, configure, use and copy the following device capabilities: PIP, POP, multi-display, and from the main, ριρ and POP screens To output 埠. Here, the implementation of the OCAP MSM if the AppID for verifying the application is changed is described with reference to Figs. 30A and 30B. Fig. 30A shows virtual codes of the 'AppID' Java type according to the OCAP standard. Figure 30B shows the virtual code of the Java type OcapAppID' of the κ OCAP MSM in accordance with an embodiment of the present invention. 200 200849990 2713 lpif If the OCAP platform implementation supports simultaneous presentation of multiple service scenarios ('javax.tv.selection.ServiceContexf), Bay ij cannot distinguish between two different applications that use the same organization and application identification code, such as] [V] As represented by 'org.dvb.application.AppID', these examples are executed in different service scenarios. Therefore, the application database with the 'AppID' level and the related level functions are not defined, that is, in this use. For example, it is ambiguous. According to an embodiment of the present invention, the application identification code is defined as the newly imported level OcapAppIDf, instead of the level, AppID', by changing S3050 of FIG. 30A to S3050 of FIG. 30B. Otherwise, the application identification code It is defined as the level '〇capAppID' in S3055, S3060, S3065 and S3070 of Fig. 30B, instead of the level, AppID' in 3015, S3020, S3025 and S3030 of Fig. 30A. The definition of the level OcapAppID' is described with reference to FIG. 31 shows a virtual code supporting a java type OcapAppID' according to an embodiment of the present invention. In S3110, level, 〇capAppID, allowed in the same application Between multiple embodiments separately 'wherein these examples related to different' the ServiceContext '. Here, ",, represents the same application, this application should use the same tissue discrimination code. Supporting OCAP implementations that simultaneously present multiple 'ServiceContexf' can allow multiple common examples of the same application. The application visibility of 'AppID' must be 〇capAppiD, except that 'org.dvb.application.AppId' is the explicit call structure of the OCAP application's 'AppID(int,int)'. 201 200849990 2 / 1J iplf If the OCAP implementation or 〇CAP application encounters, AppiD, calls this Tid'' instead of '0capAppID, then this example needs to be semantically treated as equivalent to the OcapAppID as follows. : In S3120, define the public architect to use when this, OcapAppID, and ServiceContext fields are used as defaults. In particular, calling this architecture must be equivalent to calling OcapAppID( oid, aid, null), method. The parameter foid' is an organization identification code that is compatible with the same name parameter of the super-level architect fAppID(irit oid, int aid)'. The parameter 'aidf' is an organization identification code that is compatible with the same name parameter of the super-level architect fAppID(int oid, int aid)f. The public architect to be used when specifying the fServiceContexf field of this '〇capAppID' is defined in S3130'. The parameter 'oid' is an organization identification code that is compatible with the same name parameter of the super-level architect fAppID(int oid, int aid). The parameter 1aidf is an organization identification code that is compatible with the same name parameter of the super-level architect AppID(int oid, int aid)f. The parameter 'context' is either 'ServiceContexf' or 'null value'. If 'context,' is 'null', then the current default 'ServiceContexf' of the current application needs to be replaced by a null value when Initializing ServiceContexf. At S3140, the 'ServiceContext' associated with OcapAppUT is available. Because of the fgetServiceContext〇f method, a non-empty 1ServiceContext’ is returned. Thereafter, referring to FIGS. 32A, 32B, 33A, 33B and 34A to 34C, if the "Hscene Manager" according to the OCAP standard is changed to support 202 200849990 2713 lpif OCAPMSM enhanced version. By forg.ocap.uLHSceneManager' and related types The defined ▼'Scene Management' feature does not support the following uses: • Single application uses multiple 'HScenef', where these different examples are related to different 'HGraphicsDevice'; • Independent of the dominant application 'Monitoring application or other authorized application between different rHScenef Ability to shift focus; • Ability to monitor applications or other authorized applications to monitor and/or allow/deny 'HScenef focus applications' or platform initial changes; • Broadcast with leading applications 'monitoring applications or other authorized deer To determine whether the different 'HSceneBinding' can refer to the same or different underlying conditions; ^ • Monitor the ability of the application or other authorized application to maintain all visual conditions, its Z-index and its appropriate state model for the screen position;

• The ability to monitor applications or other authorized applications in response to another Z-index that specifies the inactive condition for reordering requirements; • Change the type of return value of 'HSceneManager.getHSceneOrderQ,'; The following functions will be better represented: • Combine fHSceneChangeRequestHandler.testShow(.·) into 'testOrder(··)' by specifying 'oldOrder' as '_Γ; this engineering change will solve the following issues: Mouth into 'HSceneBinding.getGraphicsDevice()'; • Join 203 200849990 2/Ulplf fHSceneChangeRequestHandler.testMoveFocus(HSceneBindi ng'HSceneBinding),; • Add fHSceneChangeRequestHandler.focusChanged(HSceneBindi ng,HSceneBinding)' ; • Remove 'HSceneChangeRequestHandler.testShow(&quot ;)f ; • Change the 'HSceneChangeRequestHandler.testOrder(")▼ signature, return the value type and the exceptions set; • Change the 'HSceneChangeRequestHandler.testMove(··)' signature with the exceptions set; Into fHSceneManager.getAppDefaultHSce Ne(AppID)' ; • force into fHSceneManager.getAppHScenes(AppID)'; • join? HSceneManager.getAppHSceneLocation(HScene)!; • force into 'HSceneManager.getHSceneFocusO1; • force into fHSceneManager.getHSceneOrder(HGraphicsDevice)f; • Join? HSceneManager.transferHSceneFocus(HSceneBinding)f ; • Join fHSceneManager.sameScene (HSceneBinding, HSceneBinding

• Change the return value type of fHSceneManager.getHSceneOrder()f. 204 200849990 2713 lpif In addition the text description of 'fHSceneManager,5, HSceneBinding, and fHSceneChangeRequestHandler', with its pre-existing members has been enhanced to edit and improve the expression; in 'javax.tv.graphics.TVContainerf, if fgetRootContainer(XletContext Ctx) 'called by the OCAP application (or on behalf of it), itx' is the initial 'xietc〇ntext' for this call application, and its return instance needs to be the same as being passed back by 'org.havLuLHSceneFactory.getDefaultHScene()' Example. OCAP strengthens DVB-GEM 1 ·0·2 by adding the OCAP special 'Scene Management' function described below. In particular, the 〇CAP implementation is subject to rg.〇cap.ui.HSceneBindingf, forg.ocap. ui.HSceneChangeRequestHandler\ 'org.ocap.ui.HSceneManagerf and its associated semantics, as shown in Figure 32B, 33B, 34B and 340. Also, in 'org.havi.ui.HsceneFactory, in getting another "Hscene'CS]' Before, the 0CAP application does not need to perform the 'dispose(HScene)f method on the previously obtained 'Hscene' ('Sr), assuming that the previous and subsequent 'HsceneW columns, 3Γ and 'S2f, are related to different fHgraphicsDevice, in focus. In the processing rules, the implementation must maintain the overall ordered list of focusable fHSceneT. The focus of ^Scene is visible and started by 'HScend, where fHScenef is treated as visible if fHScene.isVisible()' method is returned Pass 6 true, and it is considered to be started if (l) 'HScene.setActive(boolean)' method has not been called by the application; or (2) 205 200849990 2713 lpif if, HScene.setActive(boolean focus)' method Being squeaked at least once and the value of 'focus' is 'true', after the last call with the value 'f0CUS' being 'false'. The focus fHScenef is focusable (f〇cusableyHScenef, which is assigned to the input focus. Any time There is only one focus ^HScene, no matter how many 'HGraphicsDevice' or fHScreen' are enabled. When fHScenef becomes focusable, it is added to the end of the list that can be focused, HScene. / a 1 when fHScene can be specified At the focus, it moves to the focusable, HScene, at the beginning of the list. When fHScene^ is again focusable, it is removed from the focusable, HScene' list. When the focus "HScene'f is again focusable, implement The way must remove the focus from the focused fHScenef and specify the input focus to focusable, HScene, the first one of the list can focus on THScene'. When the first focusable 'HScene' is inserted into the focusable 'HScene, list (when it Implementations do not automatically specify input focus. Figure 32A shows a virtual code of the java type "HSceneBinding' according to an embodiment of the present invention. Figure 32B shows a virtual code implementing a Java type 'HSceneBinding' of an OCAP MSM, in accordance with an embodiment of the present invention. In S3250 of Fig. 32B, the 'HGraphicsDevice' interface that does not exist in the OCAP standard of the map μα is additionally set. In S3260 of Figure 32B, 'HSceneBinding' is implemented by platform definitions, etc. 206 200849990 27131 pif level to provide certain characteristics representative of 'HScene', where HScene is generally owned by another application and thus is not allowed to be directly stored. Take this, HScene' reference. In S3270 of Fig. 32B, a square screen of 'HScene' represented by 'HSceneBinding' can be obtained (returned) in the normalized coordinate space of 'HScreen' mapped to the 'getGraphicsDevice〇' method. At S3280 of Fig. 32B, application attributes related to 'HScene' represented by 'HSceneBinding' are available (returned). In S3290 of Fig. 32B, a graphics device related to 'HScene' represented by 'HScene Bindingf' is available (returned). Figure 33A shows the virtual code of the java type 'HSceneChangeRequestHandler' according to the OCAP standard. Figure 33B shows a virtual code of a Java type 'HSceneChangeRequestHandler' implementing an OCAP MSM in accordance with an embodiment of the present invention. S3310 of Figure 33A will be removed in the OCAPMSM of Figure 33B. In S3330 of Figure 33B, 'HSceneChangeRequestHandler' is implemented by the authorized application to handle the following requirements: (1) join THScenef not currently shown, (2) remove the currently displayed, HScene, (3) change fHScenef On the screen, (4) moves in the 'HScene'Z order of the HGraphicsDevice, ^HScene', (5) moves, HScenef contains the AWT focus between the levels, and (6) the notification that the AWT focus is specified to change Give, HScene, contains the hierarchy. In S3340 of Fig. 33B, the requirements of whether or not to allow, Hscene, movement (or size change) are tested. When 'HScene, move here' to HScene, or 207 200849990 Z. / 1J> 1 pif to resize, ie if fHScreenRectanglef representing 'HScene', to change position or size, will call, testMove(HSceneBinding move , HSceneBinding currentScenes[]) '方〉Go. , which specifies the screen square of the affected fHScene' and which needs to be a project of fcurrentScenes'. The parameter 'currentScenes' is fHSceneBinding', which is related to the existing visible fHScene' (with its current screen square), which also includes the affected ▼HScene'. In this scenario, if this 'HScene.isVisible(), the method returns to Fax 'HScene is considered visible. If the move is complete, the "testMove1 method returns ‘true, otherwise it returns 6 false’. In S3350 of Fig. 33B, it is tested whether the fHScenefZ order change requirement can be completed or not. When moving in the Z order or to be added or removed in the Z order, HSceneBinding reorder, HSceneBinding currentScenes[]5 int currentOrder, int newOrdery will be called. In the case where fHScenef is to be removed from the Z order, the value of the ftestOrderf method can be ignored by the implementation (eg, the 'HScend of the application is being removed because the application is terminated). When calling the 'testOrder' method, the following restrictions apply: • at least one of fcurrentOrder' or (and) fnewOrderf2 is not negative; • if fcurrentOrder' is not negative, it is an array referenced by sixceScenes' Valid index; • If 'currentOrder' is a valid index of 'currentScenes' and if 208 200849990 2713 Ipif is not negative, it is a valid index of the array referenced by sixceScenesf. The parameter 'reorder' is 'HSceneBinding', which specifies the affected 'HScene'. If this fHScene' already exists in the 'HScene' Z sequence, it must appear in the form of a 'currentScenesf array; otherwise, it cannot exist in 'currentScenes'. The 'testOrder' method of S3320 of Fig. 33A does not consider the parameter Reorder', and the Z order can be verified by the parameter 'reorder', which is affected by the 1testOrderj method of Fig. 33B, HScene. The parameter 'currentScenes' is 'HSceneBinding', which is related to the Z-order of the existing visible HScene' whose first item (〇) is the first 'HScene'. In this case, fHScenef is considered visible if the fHScene.isVisible()’ method returns ‘true. Because of the call to the 'HScene·show()' method or the fHScene.setVisible(true)f method, the value of the parameter 'currentOrder,' is '-Γ if 'HScene' is to be displayed; or, if 'HScene' is already displayed, A non-negative integer representing the existing location in the 'currentScene' array of 'HScene' is to be moved. The parameter hewOrder' is a non-negative integer specifying the affected, HScene, the new location to be moved, or it is Μ", if the affected 'HScene' is about to be (completely) removed from the Z order of 'HScene'. If the affected 'HScene' is to be added to the Z-order of 'HScene1', then 'newOrder' represents the position it wants to appear, and all other currently moves down one position. If iurrentOrder' is '-Γ and the value of fnewOrder' is greater than The index of the last valid index of 'cuirentScenes', and the 209 200849990 / 1J ipif fHScenef to be added will be required to be located at the end of the 'HScen&Z order. The 'testOrder' method returns the null value ', if The reorcjer (join/remove) requirement has been allowed, as specified by the parameter. If this requirement cannot be executed as specified, then the value of the parameter is passed back. The new array of fHSceneBindingf will be returned, which is the following The arrangement of the component's set of components: (a) fcurrentScenesf minus 'reorder', if 'currentOrder' is not negative and! This \¥(^(^1" is negative; (b), cmrentScenes, ^ Add 'reorder' if fcurrentOrder, negative and 'newOrder, not negative; or ^ (c) 'currentScenes' if none is negative. In S3360 of Figure 33b, it will test whether AWT focus can be reassigned to (or Removed from yHScene'. If the fHSceneChangeRequestHandlerf is staged, the 0CAP platform must call 'testFocusChange', the method, when the AWT focus can be initially assigned to fHScene, contains the hierarchy, moves between the fHScene's containing classes, or moves from all fHScenef containing levels In addition, if a focus state changes such that the i ltestFocusChangef method returns a "false," value, then the CAP platform cannot complete the change, and the AWT focus must not be changed. The OCAP platform cannot call 'testFocuschange, method, when in 'HScenef When moving the sub-container (sub_container) or the focus between the components. 〇 CAP platform can but not need, the beer is called the 'testFocusChange' method (or use its return value), when the platform original AWT, HScene' focus is re-specified; however In this case, the platform must call 'focusChanged(..), method to Know the original platform, HScenef focus change. 210 200849990 27131pif When calling the 'testFocusChange' method, 'newScene' or (and) 'oldScen& one (or both) cannot be a "null value" condition. The parameter fnewScenef is fHSceneBinding', which represents liScene' to specify the focus, or when the focus is not assigned to any IHScene', that is, when not specified, it is "null value"'. The parameter 'oldScene' is 'HSceneBinding', which Represents 'HScene' to remove focus, or null when no focus is specified to any fHScene' (before calling the lestFocusChange' method. 彳estFocusChangi method returns 'true' if focus is shifted (or removed) Can be completed, otherwise, return 'false'. In S3370 of Figure 33B, the processing change is notified in the current designation of the AWT focus. The 'focusChangedf method notifies the currently specified change to the AWT focus, giving an 'HScene'. Specify this 'HScene, use fHSceneBinding', which uniquely distinguishes the situation, through the combination ('HSceneBinding.getAppAttributesQ' method), the identified application and the graphical screen ('HSceneBinding.getGraphicsDevice()T method)) The OCAP platform cannot call 'f0CUSChanged, the method, when in, HScene, moves the focus to the subcontainer Between the components. The above unique identification is based on the following conditions: For a given application, each 'HGraphicsDevice' must not have more than one 'HScene'. The parameter 'newScene' is (1) indirectly representing the 'HSceneBinding' of the new HScene1 with the specified focus. Or (2) 'null value', representing the current 'HScene' focus (in this application environment). 211 200849990 2/i3ipif parameter foldScenel(1) indirectly represents the old (previous) 'HScene' fHSceneBinding with the removed focus ', or (2) null, on behalf of the previous, HScene, unspecified focus (in this application environment). Figure 34A shows the virtual code of the Java type 'HSceneManager' according to the 〇cAP standard. Figures 34B and 34C show according to this The Java type 'HSceneManagerj^j virtual code of the OCAP MSM is implemented in the embodiment of the invention. In the S3420 of Fig. 34B, ''HsceneManager' represents the platform administrator's injury', which allows the authorized application to temporarily store the processor (]^ηί^ Γ) to handle the changes in Hscene1 required (including 'HgraphicsDevice,'), Hscene, HgraphicsDevice. In addition, the Z sequence of 'Hscene' is pre-set to allow the uranium focus designation to be queried using the 'HsceneManager'. In S3430 of Fig. 34B, a protected preset architect is generated. At S3435 of Fig. 34B, a separate example of 'HsceneManager' is obtained, where the behavior of this example (from the point of view of the accessible state) appears to be within the scope of the platform (rather than the call application). Return 'HsceneManager'. In S3440 of Figure 34B, the fsetHSceneChangeRequestHandler(HSceneChangeRequestHa ndler handler)' method allows the creation of an application, when fHscene, changes the demand handler. When the fsetHSceneChangeRequestHandler' method is called, if the handler has been temporarily stored, the fHscene7t variable demand handler is replaced by a specific handler. The parameter 'handler, is (1) the fHsceneChangeRequestHandler to be queried, about, the change in HscenefZ order 212 200849990 2713 lpif with the specified change to the preset focus, or (2) 'null value', in this case 'remove the current The processor. If the caller does not have ▼MonitorAppPermission(’’handler.resource’’)’ then a 'SecurityException' is issued. In S3445 of Fig. 34B, a set of visual fHScenes of the preset 'HGraphicsDevice' of the call application is obtained, as in the case of bindings. Compared to the ''public static OcapAppAttributes[] getHSceneOrder()n of S3410 of Figure 34A, the backhaul is joined by setting the fHSceneBinding[]' type instead of the Static OcapAppAttributes []' type. If the call application specifies a preset graphics screen, the return value of the fgetHSceneOrder〇 method is the same as

?getHSceneOrder(HScreen.getDefaultHScreen().getDefaultH

The GraphicsDevice〇y method, otherwise, it will return the empty array. Regarding the visible fHScene%'HSceneBinding of the preset fHGraphicsDevicef of the call application, the array will be returned in the Z order, where the visual representation of 'scene.isVisible()f is 4 true. If the caller does not have 'MonitorAppPermission(nhandler.resource'f)', then 'SecurityException' is issued. In S3450 of Fig. 34B, a set of case joins relating to the visible fHScene' of the particular fHGraphicsDevice' is obtained. The order of the back-synchronized arrays is such that the first item is related to 213 200849990 2713 lpif to the front of the fHScene 'Z order of the particular fHGraphicsDevice' visible fHScene', and the last item is related to the last visible 'HScen〆 . If the screen associated with a particular graphics device is not related to the display or output port, or if the display on the output port is not enabled, then the empty array must be returned. The parameter 'device' is fHGraphicsDevice'. The HSceneBindingf array of visual 'HScend' associated with a particular 'HGraphicsDevice' will be returned in the Z order, where the visual representation 'scene' sVisible()f® passes 'true'. If the caller does not have ‘MonitorAppPermission(’’handler.resource’’)’, then Baye 1J issues 'SecurityException1'. In S3455 of Figure 34C, the 'HScene'Z order position of the preset fHScenef of the call application is obtained. The application can call the 'getAppHSceneLocation()f method to determine where its preset 'HScene' is to be in the Z order of 'HGraphicsDevicd'. The fgetAppHSceneLocation() method returns '-Γ if the application never gets a reference to its default 'HSceni' (meaning that the application has no user interface); otherwise, its return value is the same as fgetAppHSceneLocation(HSceneFactory.getDefaultHScene() In S3460 of Figure 34c, the fHScene'Z order position of the specific Hscene is obtained. The application can call the fgetAppHSceneLocation(HScene scene)f method to determine the position in the specific fHScene4fHGraphicsDevice'Z 214 214 200849990 2713 lpif order. The parameter 'scene' is fHScenef , which is used to get the Z-order position in fHgraphicsDevice' related to HScene.

The ?getAppHSceneLocation(HScene scene)' method returns an integer specifying the '118〇61162 order position of the particular case 8〇611&. The order of this value in the 2: order is increasing, where 0 is the first and the other values are increasing at the most two sides of HScene. The return value is f-lf ’ If 1HScene’ is unscheduled or it is not visible, the visual definition is 'scene.isVisible()f. In S3465 of Figure 34C, the 'getAppDefaultHScene(AppID id)f method gets fHSceneBinding', which allows to determine the pre-set 'HScene' for the identified application if the application has the preset 'HScene'. The call 'getAppDefaultHScene(AppID id)' method cannot cause the generation of ▼HScene' or its association to the application. The parameter fid' is AppID', which represents the OCAP application. The 'getAppDefaultHScene(AppID id)' method will return: (1) (indirect) represents the ▼HSceneBinding' of the preset 'HScene' assigned to the identified application, or (2) "null value"', indicating that the application is no longer Reappears in the application repository, terminated, or (currently) not specified as default fHScene'. If the caller does not have 'MonitorAppPermission(nhandler.resource'f)', then 'Security Exception' is issued 图 Figure 34C In the S3470, the 'HSceneBinding' array representing the current fHScen^ of the identified application is obtained by the fgetAppHScenes(AppID id)' method. 215 200849990 27131pif Calling getAppHScenes(AppID id)f;^ The law cannot cause the generation of fHScene, or its association To application. Parameter 4d' is the 'AppID' representing the OCAP application. If (ι) (indirect) represents the specified application to the identified application, HSCene▼'s ▼HSceneBinding' is not an empty array, or (2) represents that the application is no longer Exists in the application database, terminated, or (currently) not specified as pre-s, HScenef's 'null value', to be 'getAppHScenes(AppIDid), method If the caller does not have 'MonitorAppPermissionChandler.resource')', then 'SecurityExceptionf' is issued. In S3475 of Figure 34C, the 'getHSceneFocus()' method will be allowed to determine the ATW focus assignment to (this application environment), HScene , fHSceneBinding'. If the call application does not allow fMonitorAppPermission(nhandler.resourceff)t, the shell j:匕fgetHSceneFocus〇' method is to return, null,,, if the ATW focus has been specified to the '1«061^' that the call application does not own. . The 'getHSceneFocus〇' method needs to be returned: (1) (indirect) represents the fHSceneBinding' that the ATW focus has been assigned to fHScenef, or (2) "null value," which represents the ATW focus not assigned to (in this application environment) Any 'HScene', or call application does not have the above fMonitorAppPermission(f,handler.resourceff)f ° In S3480 of Figure 34C, the ftransferHSceneFocus(HSceneBinding binding)' method would require 216 200849990 27131pif (this should be the case) special 'HScene , the transfer (or removal) of the AWT focus. If this transfer (or removal) requirement is met, then this meets a call that may be asynchronous to the 'transferHSceneFocus' method; even worse, if the platform state or other conditions are avoided This satisfaction may not occur if the AWT focus changes. The requirements for assigning the AWT focus to an application that is not in execution or to the unfocusable 'HScene' are not met. Once 'transferHSceneFocus, method or platform (nothing about 'tmnsferHSceneFocus, Method) Complete the focus transfer (or removal) of a certain, HScene, in the pre-stored HSceneChangeRequestHandler, under, can not call ffocusChanged (y method. Parameter Wnding' is one of the following · uniquely distinguishes the requirements of the eight \\^ focus of the condition 8〇61^'s '118〇61163丨11出1^'; or 2) ''null value'', representing all fHScene' requests from the (this application environment) to remove the AWT focus specification. If the caller does not have 'MonitorAppPermission(''handler.resource')', then 'SecurityException1' is issued In S3485 of Figure 34C, the 'sameScene( HSceneBinding sbl, HSceneBinding sb2)f method determines whether two fHSceneBindingfs refer to the same underlying condition. The parameters 'sbl· and 'sb2' are 'HSceneBinding'. fsameScene( HSceneBinding sbl5 HSceneBinding sb2)f method Will return 6 true 'if the pyr [with 'sb2' represents the same underlying situation; otherwise, 217 200849990 z / u ipif its return 'false. The embodiment of the present invention can be written as a computer program, and can be implemented on an I-reading recording medium to execute the program. ^ Recording media include magnetic storage media (such as R〇二商" hard disk drives, etc.), optical recording media (such as CD_R〇M or CD player) and carrier storage media (that is, through the network) The present invention has been disclosed as an embodiment of the present invention. However, it is not intended to be used in the present invention. Any of the technical fields of the present invention can be modified and retouched in the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims. [FIG. 1 shows a screen configuration diagram of a conventional PiP method. FIG. 2 shows a logic screen according to an embodiment of the present invention. The relationship between the devices. /, A person

Figure 3 shows a digital television block diagram that implements multi-screen management in accordance with an embodiment of the present invention. Fig. 4 shows a non-abstract service and digest service according to an embodiment of the present invention in a digital television system according to an embodiment of the present invention. Figure 6 shows the relationship between the screen situation (£11〇) and various methods. Figures 7A and 7B show the results displayed on the Firefly according to the z-order (z_〇rder) of the logic screen. 218 200849990 2713 lpif Association Figures 8A and 8B show the service context, logical screen and display screen. Figures 9A and 9B show the results on the screen when the logic screen is mapped to the display area. τ is associated. Figure 1A shows multiple services, between multiple logical screens and display screens. Figure 11A shows an embodiment in accordance with the present invention.

A registry list of Java constants in 'org.ocap.ui.MultiScreenConfigurableContext'. Figure 11B shows a list of login files for Java constants in forg.ocap.ui.MultiScreenConfigurationf in accordance with an embodiment of the present invention. Figure 11C shows a list of login buildings for Java constants in 'org.ocap.ui.MultiScreenContext', in accordance with an embodiment of the present invention. Figure 11D shows a login playlist of Java constants within forg.ocap.ui.event.MultiScreenConflgurationEvent', in accordance with an embodiment of the present invention. Figure 11E shows a list of login buildings for Java constants in 'org.ocap.ui.event.MultiScreenContextEvent', in accordance with an embodiment of the present invention. Figure 11F shows a list of logins for Java constants within 'org.ocap.ui.event.MultiScreenEvent', in accordance with an embodiment of the present invention. 219 200849990 2/Uiplf Figure 11G shows a list of login files for Java constants in 'org.ocap.ui.event.MultiScreenResourceEvent1, in accordance with an embodiment of the present invention. Figure 12 shows a list of interfaces and levels of a Java package forg.ocap.ui' in accordance with an embodiment of the present invention. Figure 13A shows the definition of the interface 'MultiScreenConfigurableContext' of the Java suite forg.ocap.ui' in accordance with an embodiment of the present invention. Figure 13B shows a list of fields of the interface 'MultiScreenConfigurableContext1' of the java suite 'org.ocap.ui', in accordance with an embodiment of the present invention. Figure 13C shows the use case of the block 'CONFIGURABLE—SCREEN—PARAMETER—DEVICE Z 〇 —- — RDER’. 13D to 13F show a list of methods of the interface 'MultiScreenConfigurableContext' of the java suite forg.ocap.ui' according to an embodiment of the present invention. Figure 14A shows the definition of the interface fMultiScreenConfiguration' of the suite 'org.ocap.ui' not according to the embodiment of the present invention. Figure 14B shows a list of slots for the interface 'MultiScreenConfiguration' of the Java suite 'org.ocap.ui' in accordance with an embodiment of the present invention. Figure 14C shows a list of methods for the interface 'MultiScreenConfiguration' of the Java Suite org org.ocap.uif, in accordance with an embodiment of the present invention. Figure 15A shows the definition of the interface fMultiScreenContext of the Java Suite 220 200849990 2713 lpif 'org.ocap.ui', in accordance with an embodiment of the present invention. Figure 15B shows a list of interceptions for the interface 'MultiScreenContextf' of the Java suite 'org.ocap.uif' according to an embodiment of the present invention. 15C and 15D show a list of methods of the interface fMultiScreenContext' of the java suite 'org.ocap.uif' according to an embodiment of the present invention. Figure 16A shows the definition of the level 'MultiScreenManager' of the Java suite ▼org.ocap.ui' in accordance with an embodiment of the present invention. Figure 16B shows a list of architectures for the level 'MultiScreenManager' of the java suite 'org.ocap.ui', in accordance with an embodiment of the present invention. 16C to 16F show a list of methods of the level fMultiScreenManager' of the java suite 'org.ocap.ui' according to an embodiment of the present invention. Figure 17 shows a list of interfaces and levels of the java suite forg.ocap.uLevenf in accordance with an embodiment of the present invention. Figure 18A shows the level of the java suite 'org.ocap.ui.evenf', 1^11 out of 8 (^611€: 〇1^痛1«^丨〇1]£^^1^, according to an embodiment of the present invention. Figure 18B shows a list of blocks for the level of the java suite 'org.ocap.ui.evem', MultiScreenConfigurationEvent, according to an embodiment of the present invention. Figure 18C shows the java suite 'org.ocap.ui' according to an embodiment of the present invention. The hierarchy of event's level ']\41111^8〇^611(^〇111^11 is 1;1〇11£¥6111:'. Figure 18D shows the Java suite 'org.ocap.' according to an embodiment of the present invention. The level of ui.event' is ']\41111^8 (: 221 200849990 27131pif method list of €11 (^〇111^1〇^1^〇1^¥6111:') Fig. 19A shows a method according to an embodiment of the present invention. Definition of the interface 'MultiScreenConfigurationListener' of the java suite 'org.ocap.ui.event'. Figure 19B shows a list of methods for the interface 'MultiScreenConfigurationListener' of the java suite 'org.ocap.ui.event' according to an embodiment of the present invention. Shows the level of the java suite forg.ocap.ui.event' 'MultiScreenContex1' according to an embodiment of the present invention Definition of Event' Figure 20B shows a list of fields of the java suite 'org.ocap.ui.event', etc. according to an embodiment of the present invention. Figure 20C shows a java suite rorg.ocap.ui according to an embodiment of the present invention. A list of the schemas of the level 'MultiScreenContex1; Event' of event'. Figure 20D shows a list of methods for the level 'MultiScreenContextEvent' of the java suite 'org.ocap.ui.event' in accordance with an embodiment of the present invention. Figure 21A shows an embodiment in accordance with the present invention. The definition of the interface of the java suite 'org.ocap.ui.event', MultiScreenContextListener, Fig. 21B shows a list of methods of the interface 'MultiScreenContextListener' of the java suite 'org.ocap.ui.event' according to an embodiment of the present invention. 200849990 27131pif FIG. 22A shows a definition of the Java suite 'org.ocap.ui.evenf' and the like according to an embodiment of the present invention. Figure 22B shows a list of column values for the level fMultiScreenEventf of the Java suite ▼org.ocap.ui.event', in accordance with an embodiment of the present invention. Figure 22C shows a list of architectures for the Java suite ▼org.ocap.ui.event', etc., in accordance with an embodiment of the present invention. Figure 22D shows a list of methods for the level %1111^〇^611£¥6111;' of the Java suite forg.ocap.ui.event', in accordance with an embodiment of the present invention. Figure 23A shows the definition of the level 'MultiScreenResourceEvent' of the java suite 'org.ocap.ui.evem', in accordance with an embodiment of the present invention. 23B shows a list of placements of the java suite 'org.ocap.ui.event' at a level of ]]\41111^(^611^5〇111^£¥6111;' according to an embodiment of the present invention. FIG. 23C shows Schematic list of the level 'MultiScreenResourceEvent' of the Java suite 'org.ocap.ui.event▼' of the embodiment of the invention. Figure 23D shows the level 'MultiScreenResourceEvent' of the Java suite 'org.ocap.ui.event' according to an embodiment of the present invention. Method Lists Figures 24A-24C show preconditions for changing a multi-screen architecture in accordance with an embodiment of the present invention. Figure 24D shows a process for changing a multi-screen architecture in accordance with an embodiment of the present invention. 223 200849990 27131pif Figures 25A through 25E are shown in accordance with the present invention. The preconditions for changing the multi-screen architecture of the embodiment. Figures 26A-26D show the constraints of verifying invariants in accordance with an embodiment of the present invention.Figure 27 shows the definition of the fgetNonDefaultScreens()' method in accordance with an embodiment of the present invention. 28A and 28B show an embodiment in accordance with the present invention.

The definition of the 'getNonDefaultScreenDevices()' method. Figure 29 shows various methods in accordance with embodiments of the present invention. Figure 30A shows the Java-type virtual code (pseudo_codes) according to the fAppID of the 〇peil Cable Application Platform (OCAP) standard. Figure 30B shows a Java type OcapAppID^ virtual code implementing a 〇cAP MSM in accordance with an embodiment of the present invention. FIG. 31 shows a virtual code supporting a java type OcapAppID1 according to an embodiment of the present invention. Figure 32A shows a java type 'HSceneBinding4' virtual code in accordance with an embodiment of the present invention. Figure 32B shows a virtual code of a Java type 'HSceneBinding1' implementing 〇cAp msm, in accordance with an embodiment of the present invention. Figure 33A shows the virtual code of the java type fHSceneChangeRequestHandler' according to the OCAP standard. FIG. 33B shows an implementation of 〇CAp MSM according to an embodiment of the present invention.

Virtual code for the Java type 'HSceneChangeRequestHandler' 224 200849990 27131pif Figure 34A shows the Java type fHSceneManager4 virtual code according to the OCAP standard. Figures 34B and 34C show virtual code of a Java type 'HSceneManager' implementing an OCAP MSM in accordance with an embodiment of the present invention. [Main component symbol description] 100, 110, 120, 130, 140, 150: physical display screen 105, 115, 125, 135, 142, 144, 152, 154: secondary screen 210: logical screen group 220: display mapper 230: display screen group 212, 214, 216: logic screen 240, 250, 260: display screen 242, 244, 252, 254, 262, 264, 266: screen area 300: digital television system 310: broadcast signal receiving unit 320: Digital signal processing unit 330: multimedia service processing unit 340: output unit 350: display unit 400: digital TV system 410: terrestrial broadcast content 420: cable broadcast content 430: personal video camera data content 440: DTV/STB module 225 200849990 z / υ ipif 450 : Display screen 452, 454, 456 · Screen area 510, 550: Service group 520: Image service 530: Sound service 540: Application service 560 · Image application 570: Sound application 600: Screen scenario 610: Z Sequence 620 · Display Zone 630: Visibility 640: Related Display Screen 650: Related Service Context 700: Display Screen 710: Logic Screen 720: Logic Screen 2a 750 · Display Screen 760: Logic Screen lb 770: Logic Screen 2b 810: Service 812: Video Content 814: Sound Content 816: Application Content 226 200849990 2713 lpif 820: Empty Logic Screen 830: Logic Screen 840: Display Screen 850, 860: Display 910: Logic Screen 920: Display Screen 930: Overall Area 940: Display 950: Area 960: Display 1010, 1020: Service 1030, 1040: Logic Screen 1050: Display Screen 1060: Output 埠 1070: Output 1200: Interface List 1210: fMultiScreenConfigurableContext▼ Interface 1220 ·· ' MultiScreenConfiguration 'Interface 1230: fMultiScreenContext' interface 1250: Level List 1260: 'MultiScreenManager' Level 1300: Block Lists 1302~1320: Field 1330: Method 227 200849990 2713 lpif 1340: Method 1350 · Method List 1352~1392: Method 1394 : Method List 1400: Field List 1402~1424: Field 1450: Method List 1452~1464: Method 1500: Field List 1502, 1504: Field 1550: Method List 1552~1588: Method 1600: Architecture List 1602: Architecture 1630: Method List 1632~1695: Method 1700: Interface List 1710: Rank Column Table 1702, 1704: Interface 1712~1718: Level 1800: Field List 1802~1825 · Field 18 3 0 · Architecture List 1832: Architect 200849990 27131pif Method 1840 · Method List 1842, 1850, 1852, 1854: 1900 : Method List 1910: Method 2000: Field List 2002~2035: Field 2040: Architecture List f 2042: Architect % 2050 · Method List 2052~2056: Method 2100: Method List 2102: Method 2200: Field List 2202 , 2204, 2210: Field 2220: Architecture List 2222: Architect (2230: Method List 2322, 2240, 2245 • Method 2300: Field List 2302, 2304, 2310 • Field 2320: Architecture List Architect 2322 2330 : Method list method 2332, 2334, 2340, 2345: 229 200849990 2713 lpif 2410~2490: Method 2500~2550: Method 2605~2675: Method 2810, 2820: Method 2910~2930: Method 3010~3070: Virtual code 3110~ 3140: virtual code 3250~3290: virtual code ^ 3310~3370: virtual code 3410~3485: virtual code 230

Claims (1)

200849990 2713 lpif X. Patent application scope: L A method for configuring and managing multiple screens, including: receiving one or more broadcast services; specifying one or more of the above broadcast services to a screen; specifying this screen to one or more Display screens; and designate one or more of the above display screens to one or more output ports. 231