MXPA01010790A - Communication system and method - Google Patents

Abstract

A communication system (100) including a controller station (114) and a controlled station (102), interconnected via a communication network (120), a set of functions of the controlled station (102) being accessible through a base software element, characterized by an extension to said set of functions being accessible through an extended software element, the extended software element comprising a link to the base software element for enabling access to the base software element.

Description

System and Method of Communication The invention relates to a communication system that includes a controller station and a controlled station, connected through a communication network, a set of functions of the controlled station being accessible through a base element of the software. The invention also relates to a method that provides a standardized extended functionality in a communication system that includes a controlled station and a controlled station, connected through a communication network, a set of functions of the controlled station being accessible to through a base element of the software.

The electronic consumer multimedia system may contain home digital networks, using DVB and similar technologies to provide multimedia content to consumers. To allow the different devices that can be used in this system to interact, several standards have been defined. One of those standards is the Specification of the internal operability of the Residential Audio / Video Architecture (HAVi), version 1.0, January 2000 Digital Video Transmission (DVB); guidelines on the implementation and use of the Information Service (SI), ETR 211, August 1997, second edition. The invention will be discussed in parts, in terms of the following HAVi architecture, although it should be understood that the invention can also be applied to systems and similar architectures without deviating from the scope of the application. A multimedia system according to the invention can comprise a plurality of stations. A station can act as a controlling station, controlling one or more of the other stations, acting as controlled stations. A station makes its local functioning available in the form of a set of functions, which can be accessed by transferable messages. The operation set can be seen as an abstract representation of the current fundamental operation, which is provided by the hardware, and / or the software of the station. The representation is abstract in the sense that a strict one-to-one relationship is not required between the external functions offered and the internal implementation. Typically, the representation is standardized considering that the current implementation is selling, or even a specific model. Consequently, the station projects abstract representation (AR) into internal control mechanisms and controls the fundamental hardware / software (eg using an internal port, such as I2C, to control the hardware components). Said projection and control is usually performed in the software. This also covers the functionality required to project the abstract representation to the concrete representation of the fundamental hardware / software of the station. RA can be controlled using a messenger mechanism. Command messages are defined for each function by instructing a station to perform a defined task. Request messages allow information to be retrieved from the station with respect to the execution of the function, such as the station status. The event messages enable the station to inform another station of events such as: the status changes that have occurred in the station. In a controller station, the task of controlling the functionality of another station is assigned to the so-called Audio / Video Controller (AV / C). The AV / C acts independently of any of the other controller stations. Typically, the AV / C begins a control sequence, usually referred to as an application or device, as a reaction of a user trigger (eg a user has pressed a button on a remote control) or as an event that has occurred in the system. A typical example of an application executed by the AV / C is that of the automatic ignition device. For this device, in response to the activation of the VCR's visual rewind function by the user (eg pressing a power button or inserting a cassette), the AV / C instructs the VCR platform to run the video, instructs the The VCR that makes the A / V signal originated from the cassette is available for TV, and instructs the TV to provide the VCR signal to the monitor. It will be appreciated that for this example the AV / C controller is preferably, although not strictly required, located either on the TV or in the VCR to reduce the number of command messages. Many AV / C's may be present at the stations. A station can program or even act simultaneously as a controlling station or as a controlled station. An FCM is an abstraction (of the software) that provides access to the operation of a controlled station through the FCM. It contains a code to execute the functions related to the controlled station, such as those mentioned above. An FCM has a vendor ID, which identifies the vendor or manufacturer of the FCM. This allows the vendor to add their own specific extensions to the defined standard FCMs. However, as the vendor ID indicates to a vendor, this method can not be used by another entity to extend the standard, such as a standardization, physical.

One purpose of the invention is to provide a communication system of the exposed type, which is flexible to expand functionality. This purpose is carried out according to the invention in a communication system characterized by an extension of said set of functions being accessible through an added software element, the added software element comprises a link to the base of the element of software to enable access to the base of the software element. In such a system, aggregate functionality can also be accessed through the added software element, and the set of functions offered through the base of the software element continue to exist and can be used normally. If a station uses aggregate functionality, it can also access the feature set by following the access link to the base of the software element. A station that has no knowledge of the mechanism for aggregate functionality can continue to operate without any problem, making the communication system reversibly compatible. Preferably, the communication system is »about the internal operability of the Residential Audio / Video Architecture (HAVi). In such a case, the base of the software element works better as a HAVi tuner of an FCM. In one embodiment, the link comprises a software identifier element (SEID) for the base of the software element. The SEID is guaranteed to be unique in the communication system, so it is a more suitable candidate to locate the base of the software element, for example, when searching for a record using the SEID as a key for the station that contains the base of the software element. In another additional embodiment, the added software element consists of a computer code to execute a call function, which returns said identifier of the software element. By implementing a standard calling function or, when an object orientation software is used, a method to read the SAID is very easy for other stations to find which base of the software element is being linked. In another additional modality, the added software element has been stored in a registry to enable the questioning of the registry to locate the aggregate software element. The registry can be used to locate the software elements that have specific functionality, so registering the added software element is then necessary to make the added functionality available. In another additional embodiment, the base of the software element comprises a first identifier of the vendor and the added software element comprises a second identifier of the vendor, the second being different from the first. The second identifier of the seller preferably identifies one of the physical standardizations and a consortium, such as the consortium of digital video transmission (DVB). The vendor identification, in combination with an error in the message number, identifier method or type of software item, can be used to create vendor-specific unique error messages, method identifiers or software elements. This allows manufacturers to extend the standardization of FCMs with their own specific extensions. However, since the said vendor identifier indicates to a vendor, this method can not be used by another entity to extend the standard, as it is. a physical standardization or a consortium. Now they can provide an element of the added software with their own vendor identifier, and link it to a base element of the software that has the identification of their vendor or manufacturer. A further purpose of the invention is to provide a method according to the preamble that is flexible with respect to providing such operation. This purpose is achieved according to the invention in a method characterized by storing in a register an element of the added software, which provides access to standardized aggregate operation, said aggregate software element consists of a link to the base of the software element to enable access to the base of the software element. By storing the added software item in the registry, other applications can locate it, or locate the functionality provided by it. The functionality offered by the base of the software element can also be registered. In one embodiment, the method also questions the record to locate the aggregate software element, which contains a computer code to execute a call function, which returns an identifier of the software element to the base of the software element? when executing said calling function to obtain said identifier of the software element; questioning the registry to locate the base of the software element and accessing the set of functions being accessible through said base of the software element.

These and other aspects of the invention will be apparent and explained with reference to the embodiments shown in the drawings in which: Fig. 1 is a block diagram of a system with consumer artifacts according to the invention. Fig. 2 is a block diagram of the software architecture of a controller station in the system of Fig. 1.

Through the figures, the same reference numerals indicate similar or corresponding devices. Some of the devices indicated in the drawings are typically implemented in the software, and to those software entities, such as software objects or modules. Fig. 1 is a block diagram of a control system 100 according to the invention. The system 100 contains at least one of the controlled stations; the controlled stations 102, 104, 106, 108, 110,, and 112 are shown. The system 100 further includes a plurality of controller stations. The figure illustrates the controller stations 114 and 116. The controller stations are connected through the main communication network 120 of the system, for these instances based on IEEE 1394, using the same maximum level communication protocols. The controlled stations 102-106 are directly connected to the controller station 114. The connection can be through any suitable means of communication, such as a proprietary network. The controlled station 108 is connected to the main network 120, but does not use all the protocols required to make its available ARs to control in a mode required by the main network 129. However, the station 108 may use other protocols (eg. or according to a different standard) and likewise be able to communicate with a controlling station.

In the system, a distinction is made between the controlling stations (or, abbreviated controllers) and the controlled stations. A controller is a station that acts as a host for a controlled station. A controlled station and its controller can reside in the same physical device or in separate devices. A controller is assigned as the host of an abstract representation (AR) for the controlled device. The control interface is exposed through the API (interface application program) of this AR. This API is the access point for applications (devices) to control the station. For example, a smart television in the television room can be the controller for a number of controlled stations connected to each other. A controlled station can contain a code that builds a user interface for the station and allows external control of the station. When this station is connected for the first time, the controller obtains the user interface and the control code. An icon representing the station can then appear on the television screen and manipulating the icon can cause the elements of the control program to act on the station (s) represented in prescribed ways. To appreciate the operation and the versatile character of the system 100, a categorization of the communications skills of the consumer electronic stations 102-112 will be discussed first. While there is in fact a uniform continuity of the capabilities of the devices that can be explained here, this categorization is useful to understand the model of the system 100. The communication capabilities of the stations 102-112 in this generic example have different levels of sophistication. Depending on their communication capabilities, stations 102-112 belong to one of the following classes: • Controller stations. A distinction can be made between the following two types of controller stations: Complete AV device (AVF) A complete AV device generally has a large set of resources and is capable of supporting a complex software environment. The primary distinguishing device of an AVF is the presence of a time-governed environment to execute an abstract representation (AR) for a controlled station. This allows the FAV to load an AR of other *, 3taciones or through other communication networks of local or peripheral areas and thus provide improved capabilities for their control. The FAV may also be able to download applications / devices. Preferably, the download code is a form of executable code of a virtual machine (eg JAVA or similar bit codes). The most feasible candidates for FAV equipment can be Installation Boxes (STB), Digital Television Receivers (DTV), Home Control Devices for multiple uses, and even home PCs. AV Intermediate Device (IAV) Intermediate AV devices are generally cheaper than FAV devices and more limited in resources. They do not provide a time-governed environment for downloadable AR's and therefore can not act as arbitrary device drivers within the system, however, an IAV can provide natural support for the control of particular controlled stations in the system. Controlled stations. A distinction can be made between the following two types of controlled stations: * >; AV base device (BAV). These are devices that, for business or resource reasons, they prefer to implement because of their behavior of future duration providing a chargeable AR, but the devices themselves do not execute an AR. These devices can be controlled by a station with a rolling device (by a FAV device through controller codes (by a FAV device through loadable byte codes or by an IAV device through a natural code). BAV and its controlling station is typically proprietary Communication between a controlling station and a BAV device requires that the commands for the AR be interpreted by and for the command protocol used by the BAV device This interpretation is performed by the controlling station When executing the AR 4 AV Legacy Device (LAV), LAV devices are devices that do not comply with the described architecture system and communication protocols Typically, such devices were previously built in. These devices use proprietary protocols for their control, and usually have unique simple control protocols. can work in the residential network, but require FAV or IAV devices to act as an input. Communication between a complete or intermediate AV device and an AV legacy device requires commands to be interpreted by and for the legacy command protocol.

During the course of the interaction, stations can exchange control and data in a parity mode. This ensures that, at the communication level, no device is required to act as controller or dominator of the system. However, it also allows a logical dominator or controller to impose a control structure on the type of parity mode communication.

Software architecture. The software architecture of a controller station is shown in FIGURE 2. The architecture software elements support the basic notions of network management, abstraction devices, communication between devices, and the management of user interface devices (Ul). Collectively these elements of the software expose the API interoperability, a set of services to build portable applications distributed in the system. The software elements themselves reside on top of a specific platform of the vendor 210, as is a real-time operating system. FIGURE 2, describes the distribution of the software elements in a controlling station. The diagram illustrates how the software elements form a middle layer between the API-specific platform and the platforms of the independent applications, although not intentionally, as an implementation plane. An important element of software is abstract representation (AR). Three AR's (220, 222 and 224) are indicated. AR is an element of the software used to control a station. An AR contains a code for the RA itself, plus a code for the functional component modules (FCM's) for each functional component within the controlled station. An FCM is an abstraction (of the software) of a functional component that provides its functionality for the environment and software applications. The applications do not communicate with a functional component directly, but only through the FCM, the FCM in turn does not communicate with the functional component directly, but always through the AR (this is at least the model used to present the relationship). An FCM is an object in the sense that it can be stored as a receiver in a registry (the details are provided below) and can communicate with other objects by means of a messenger system. A functional component represents functions associated with an identifiable primary function of a station. Pe A VCR AR can contain separate FCM's for the cassette deck and for the tuner; an AR television can contain separate FCM's for the monitor, for the PIP (to show two simultaneous images) and for the tuner. Likewise an AR can include a control application device - an element of the software that. allows the user to control the device and its functional components. In the Figure, the AR 220 represents the functionality of the same controller station, where the AR 222 and 224, respectively, represent the functionality of two controlled stations. The controller station contains the control means 240, which provide a time-governed environment for the RA's (eg, the loaded RAs) or for the applications. The controller station also contains the AR 250 distribution means and the AR 260 positioning means. The AR 260 positioning means places an AR which has been assigned to execute in this controlling station the control means 240 for its execution. The distribution means 250 performs the task of the AR administrator, which controls the installation and removal of the AR's in the controlling stations. ARs are a central concept for architecture and the source of flexibility in accommodating new devices and distinctive features. ARs come in two main types: • Recessed AR's - an AR pre-installed in a controller station. • AR loaded - an AR implemented using a downloadable code eg. A byte code. Loadable AR's only run on FAV devices. Preferably, a recessed RA is capable of being used to control a range of controllable stations, such as a range of VCRs from a manufacturer. Preferably the controlling station obtains additional information from the current controlled controlled station (eg, by reading a model number through a network) and adjusts a generic AR to operate optimally for a specific controlled station. As such, ARs can provide API's for the control of device families or, optionally, for specific models only. Generally, family-oriented ARs will have a wider range of use, but specific ARs allow for the control of the vendor's specific distinctive capabilities and characteristics. For a controlled station, an associated RA must be present in the system so that the controlled station can participate. For a BAV device, the AR can be obtained (downloaded) directly from the store of the BAV device or from some other store associated with the BAV device (such as a hard disk located at another station in the network or even through a network of a peripheral area). In the latter case, an indication of the location of the warehouse is kept by the controlled station. This indication can be stored in the same controlled station or in another station, such as a controlling station or a central station. For an LAV device, the AR is pre-installed in the controller station or obtained from any storage site. Similarly, an AR that runs to a controller station is also required, to be used by the applications / distinguishing features in other stations. Normally, said AR will run inside the controlling station by itself, although this is not strictly required. A controller station may also consist of one or more applications (distinguishing features); Applications 270, 272 and 274 are displayed. The application sends messages to one or more AR's. The AR's can be located in the same station, or in another station, in which case the message is transferred through the network. Other elements of the software may be included in the controlling station, such as: • A media manager 230 - allows other elements to perform the communication, such as isochronous and asynchronous communications through the network. Preferably the IEEE 1394 is used as the network.

• Messenger system 232 - Is responsible for passing messages between the elements. • Admi.ni.strador of events 234 - si.rve as a servi.ci.o of delivery of events. An event is the change in the state of an object or a residential network. • Course Manager 236 - is responsible for managing the real-time transfer of AV and other media between functional components. between functional components. • Registry 238 - serves as a service directory, allows any object to locate another object in the residential network. The stations in the system can contain descriptive information (Self-describing Device Information or SDD) about the station and its capabilities. If the IEEE 1394 is used as the network, preferably this information follows the directional scheme of the IEEE 1212 used for the ROM Configuration. The SDD information may include an AR code and information for constructing a user interface element.

Media Manager. The Media Manager (CMM, 230) is a dependent entity in the network. Performs an interface with the fundamental communication medium to provide services to other components or applications of resident programs in the same device in which the CMM resides. Each physical communication means has its own CMM to carry out the purposes described above. Here the CMM for the IEEE 1394 port is described in more detail. Two types of services are provided by the CMM. One is to provide a transport mechanism to send requests and receive indications from the remote device. The other is to extract the activities from the port and present the information to the system. The IEEE 1394 port is a dynamically configurable network. After each port is configured, a device can have a physical identification completely different from the one it had before. If a network component or application has been communicating with a device on the network, it will still want to continue communication after the port is configured, even though the device may have a different physical identification. To identify a single device despite the frequency of port configuration, a unique global identifier (GUID) is used by the CMM and other entities. The GUID is a 64-bit number that is composed of 24 non-flexible bits of vendor identification and 40 bits of chip identification. While the physical identifier of a device can change constantly, its GUID is permanent. The CMM makes the GUID device available to its customers. One of the advanced distinguishing features of the 1394 port is its support for dynamic actions of the device such as the connect and disconnect. To fully support "this at the user level, the components or applications of the system need to be aware of these changes in the environment." The CMM works with the event manager (EM) to detect and announce such dynamic port changes. change in the topology within the port 1394 can cause the port to be reconfigured, the CMM can find the changes and notify the event administrator about these changes as well as the associated information. The event manager will then distribute events related to all interested entities or applications.

Messenger System The messenger system 232 provides the elements of the software with means of communication. This is independent of the network and transport layers. A messenger system is embedded in any IAV and FAV device. The messenger system of a device is in charge of locating identifiers of the software elements of said device. said identifiers are first used by the elements of the software for their registration. Then they are used by the software elements to identify themselves within the residential network: when an element of the software (A) wants to send a message to another element of the software (B) it has to use the software element identifier of B , while calling the API messenger system.

Control Devices In the system, according to the invention, an AR must exist for each BAV and LAV known in that network. The AR provides an interface to the device and presents it as an element of the software in the architecture. Within an AR several FCM's are contained representing the functional components of the device and which are also presented as elements of the software in the architecture. Other applications may challenge the registry to find available devices and functional components and to obtain an identifier of the software element, which allows them to interact with the device through an AR and FCM's. The ARs are managed by a FAV or IAV ßl which can install them. The installation of an AR code unit results in the installation of all the associated FCM's. The code can be written in a standard byte code, in which case, they can be installed in all FAV devices, or in some native code, in which case they can be installed only in (and for) some FAV or IAV that know the code and are prepared for that code.

Functional Component Module (FCM) An FCM is an abstraction (of the software) of a functional component providing the functionality of that functional component to the environment and software applications. The applications will not communicate with a functional component directly, but only through the FCM, the FCM in turn, does not communicate with the functional component directly, but always through the AR (This is at least the model used to present the relationship; implementation of a FCM can communicate with the CMM directly). An FCM is a software object in the sense that it is registered as a receiver in the registry and that it can communicate with other objects through the messenger system. Through the messenger system, it offers the protocol command according to the conventions of the system. In the registry, each software element (such as an FCM or a DCM) is defined by a set of consonants. In the context of the HAVi architecture, the most important of these consonants are a type of software elements, the vendor identifier and the HUID. The type of the software element identifies the type of the element (eg, tuner, register, etc.). The HUID is the unique identifier of the HAVi of the device that hosts the element. The vendor identification identifies the vendor or manufacturer of the FC *. This value is standardized by the IEEE.

Identification the seller can be used to extend the specification. The vendor identification, in combination with an error in the message number, or the identifier method or a type of software item, may be used to create a unique error message, or identification method or item of vendor-specific software. . This allows manufacturers to extend the FCM's standard, with their own and specific extensions. However, because the mentioned vendor identifier indicates a vendor, this method can not be used to extend the standard by any other entity, such as physical standardization. If another entity wants to extend the standard, the extension needs to be identified as an extension of, for example, DVB. An application that requires such additional functionality must be able to locate the functionality easily and without errors. This requires that extended functionality can be located using the registry. However, the original interface must also be present and manufacturers must be able to extend it in the manner described above. If the extension is intended to replace the vendor that provides the FCM's, this will make it impossible for a vendor to provide their own extensions. Few vendors would be willing to take this risk. To resolve this issue, the mornings views or interfaces of the base element of the software is introduced. Register 238 may now contain not only the existing software element, but also one or more views of this element of the software. These views contain the standardized methods of extension and a link to the base of the software element. The mechanism for creating such views is that the FCM's are registered as a set of software elements in register 238. The base of the software element has the vendor identifier of the software element manufacturer. The aggregate software element is a view or interface in the base of the software element. Although this is registered under a separate SEID, it is directly related to the base of the software element. In said system, the base of the software element represents the access point to the standard functionality of the software element. All standard functionality can be accessed using the base of the software element, eg. if the base of the software element represents an FCM, all the resource management of this FCM must be done using the base of the software element and not the added software element. The added functionality, in contrast, can only be accessed by calling functions available in the added software element. These can function as a kind of wrap around the functionality of the base of the software element, for example, providing a standardized format for a parameter.

The aggregate software element performed in this mode does not have to copy all the functionality of the base of the software element. The link provides access to the base of the software element, and therefore, to the functionality that it provides. Only the added functionality needs to be implemented in the aggregate software element. Because the vendor identifier of this extension is the vendor identifier of the entity creating the extension, all software elements, methods, attributes, and error identifiers can be defined as unique by the entity in question, using the range for proprietary extensions. To provide a direct link, the basis of the software element 310, the aggregate software element provides the SEID of the base of the software element 310. This allows an application to search the register 238 for the required standardized combination of the SEID and the seller identifier. When this combination is found, the base of the software element is also found. This requires, however, that the element of the added software and the base of the software element be connected. When the extension is present, the base must also be present.

The base element of the software can be recognized using the type of the software element defined by the standard. The elements of the aggregate software can be identified using a type of the private software element and the seller's identifier.

In the later embodiment of the invention, an extension related to the DVB is made to a HAVi FCM tuner. This aggregate FCM can provide a link for later extensions. Because the extension is a focal point of any DVB extension, a residential DVB door must always provide a DVB tuner extension for each FCM tuner. Moreover, basic utility methods are provided and a method that allows the selection of the course transport source of a tuner without having to select any component that is brought to the IHDN. This functionality is required by the MHP API tuner. An example use of this functionality is to select a means of transport to filter some sections of MPEG-2. To make the aggregate FCM available, it must be stored in register 238. The vendor identifier and the attributes of the SEID are required, and are defined as follows: The aggregate FCM offers the following services: Using this aggregate FCM, other extensions of FCM's can be added. In particular, the basic functionality is provided to add an extension to the information service and an extension to the filtering section. The services are explained below: DVBTunerExt:: 6etBaseFCMSBID • JQ Prototype DVBTunerExt State:: GetBaseFCMSEID (SEID out FCM base SEID) Parameters FCM base SEID / SEID tuner FCM is an extension in. Desoripoión This method returns the identifier of the software element of the HAVi FCM tuner added by the service of the invention. 0 DVBTunerExt:: GetDVBSiSEID Prototype State DVBTunerExt:: GetDVBSiSEID (SEID outside dvbsiseid) Parameters 5 DvbSiSeid - The SEID of the SI extension of this FCM tuner.

Description This method returns the identifier of the software element of the DVB tuner information service extension. Error codes • ENOIMPLEMENTED - The tuner does not implement a DVB-SI extension. DVBTunerExt:: 6etSfSEID Prototype DVBTunerExt State:: GetSfSEID (SEID outside SfSeid) Parameters SfSeid - The SEID of the extension of the filtering section of this FCM tuner. Description This method returns the i? Entifier of the software element of an extension of the filter section of a tuner DVB. Error codes • ENOIMPLEMENTED - The tuner does not implement a DVB-SI extension. DVBTunerExt:: SelectSourceTß Prototype DVBTunerExt State:: SelectSourceTs (In Ts service locator) Parameters ts - The service locator representing the transport course that the tuner, connected to the HAVi FCM tuner is tuned. Description This method changes the MPEG2-TS selection of a HAVi FCM tuner for this DVB FCM tuner extension. Selecting an MPEG2-TS will not generate any current in the output sockets. Only the MPEG2-TS source is selected as a preparation for SI filtering and / or filtering section. This method allows the filtering section and the DVB-Si extension to access different transport courses without passing information about the HLN.

Selecting a transport stream will stop the current of any MPEG2-Ts component of an MPEG2-Ts. This method is mandatory for all DVB FCM tuners that also implement a filter section or a DVB-SI extension. Error codes • ENOIMPLEMENTED - The method of the TS Selection source is not supported by the DVB FCM tuner. • DvbTunerExt:: Elocalizer - If the FCM tuner can not resolve the locator.

DVBTunerEx:: TetBouquetServlceLißtß Prototype State DVBTunerExt:: GetBouquetServiceLists (Out ucorto homeNumberList Out ucorto finalNumberLista) Parameters StartNu eroLista - The list number of the first branch list service. EndNumberList - The list number of the last branch list service. Description This method returns the start and end list number of the service list representing branches, known for the FCM tuner (Tuner:: GetServiceList and Tuner:: GetServiceListInfo). Error codes • ENOIMPLEMENTED - The base of the FCN tuner does not support the list of branches. • TUNER: LISTAE - None of the branches are known by the tuner.

DVBTunerExt:: GetNetvorlServioeLißts Prototype State DVBTunerExt:: GetNetwor ServiceLists Out ucorto startNumberList Out ucorto finalNumberLista)) Parameters StartNumberList - The list number of the first network list service. EndNumberList - The list number of the last network list service. Description This method returns the start list and end list number of the service list representing known networks for the FCM tuner (Tuner:: GetServiceList and Tuner:: GetServiceListInfo). Error codes • ENOIMPLEMENTED - The base of the FCN tuner does not support the list of networks. • TUNER: LISTAE - None of the networks are known by the tuner.

Claims (11)

1. PEDIMENTS: 1. A communication system (100) that includes a controller station (114) and a controlled station (102), connected to each other through a communication network (120), a set of functions of the controlled station ( 102) being accessible through a base of the software element, characterized by an extension of said functions being accessible through an added software element, the added software element containing a link to the base of the software element to enable the access to the base of the software element.
2. 2. The communication system (100) of the request 1, wherein said communication system (100) is from the audio / video residential operating architecture (HAVi).
3. 3. The communication system (100) of the request 2, wherein said base of the software element is a HAVi FCM Tuner.
4. 4. The communication system (100) of request 1, wherein the link contains an identifier of the software element (SEID) for the base of the software element.
5. 5. The communication system (100) of the request 4, wherein the added software element contains a computer code to execute a call function which returns said identifier of the software element.
6. 6. The communication system (100) of the request 1, wherein the added software element has been stored in a register (238) to enable a challenge to the register (238) to locate the added software element.
7. 7. The communication system (100) of the request 1, wherein the base of the software element contains a first vendor identifier and the aggregate software item contains a second vendor identifier, the second identifier being different from the first.
8. 8. The communication system (100) of the request 7, where the second vendor identifier identifies one of the physical standardizations and a consortium.
9. 9. The communication system (100) of request 7, wherein the second vendor identifier identifies the Digital Video Transmission (DVB) consortium.
10. 10. A method that provides aggregate standardized functionality in a communication system (100) including a controller station (114) and a controlled station (102), connected to each other through a communication network (120), a set of functions of the controlled station (102) being accessible through a base of the software element, the method being characterized by storing in a register (238) an aggregate software element which provides access to the aggregate standardized operation, said software element aggregate containing a link to the base of the software element to enable access to the base of the software element.
11. 11. The method of the petition 10, furthermore contains a question in the register (238) to locate the added software element, which contains a computer code to execute a call function which returns an identifier of the software element for the base of the software element; executing said calling function to obtain said identifier of the software element; questioning the registry (238) to locate the base of the software element; and accessing the set of functions being accessible through said base of software element.