Abstract: ABSTRACT The embodiments herein relate to digital home entertainment and, more particularly, to enable network connectivity of non-DLNA devices having USB port which are present in DLNA environment. This system consists of a DLNA/UPnP-USB bridge which is connected to the non-DLNA device 5 by using an USB interface between them. The DLNA/UPnP-USB bridge configures the non-DLNA device by accessing its execution commands. Further, DLNA/UPnP-USB bridge discovers all DLNA media servers and stores their content in virtual file format. Now the control of non-DLNA device can be done by sending execution commands such as PLAY, 10 PAUSE, STOP and so on through any DLNA/UPnP controllers. The DLNA/UPnP-USB bridge receives these commands through suitable network interface like wifi and delivers them to non-DLNA device in IR form. Further, non-DLNA device receives these commands through its IR receiver and performs corresponding actions treating DLNA/UPnP-USB 15 bridge as mass storage disk connected to its USB port. FIG. 1
CLIAMS:CLAIMS
We claim:
1. A method for playing DLNA contents in a non DLNA device, said method comprises:
initiating a DLNA content read for said non-DLNA device; and
reading said DLNA content using said non-DLNA device.
2. The method as in claim 1, wherein said initiating DLNA content read for said non DLNA device further comprises:
connecting a DLNA/UPnP USB bridge to said non-DLNA device;
sending a control command corresponding to said content read operation to said DLNA/UPnP USB bridge from a DLNA /UPnP controller;
receiving said control command by said DLNA/UPnP USB bridge;
generating IR commands corresponding to said received control command by said DLNA/UPnP USB bridge; and
providing said generated IR commands to said non-DLNA device; and
receiving SCSI command in response to said IR command by said DLNA/UPnP USB bridge.
3. The method as in claim 2, wherein said control commands and corresponding IR commands are preconfigured with said DLNA/UPnP USB bridge.
4. The method as in claim 2, wherein said IR commands are specific to said non DLNA device.
5. The method as in claim 4, wherein said control commands and corresponding IR commands may relate to at least one of a PLAY, PAUSE, STOP or Volume control operation of said non-DLNA device.
6. The method as in claim 1, wherein said reading the DLNA content using said non DLNA device further comprises:
receiving at least one SCSI command corresponding to said read operation from said non DLNA device by said DLNA/UPnP USB bridge;
analyzing said received SCSI command;
discovering all media servers in own network by said DLNA/UPnP USB bridge;
fetching content to be read from at least one of said discovered media servers;
creating a virtual file stack corresponding to said fetched content to be read in said DLNA/UPnP USB bridge; and
reading said content from said DLNA/UPnP USB bridge using said non DLNA device.
7. The method as in claim 6, wherein said content to be read is selected based on inputs from a DLNA /UPnP controller.
8. The method as in claim 6, wherein said analyzing SCSI command further comprises:
unwrapping said SCSI commands using a USB mass storage command interpreter; and
interpreting said unwrapped commands using a SCSI command interpreter.
9. A system for playing DLNA contents in a non DLNA device, said system configured for:
initiating a DLNA content read for said non DLNA device using a DLNA enabler network; and
reading said DLNA content using said non DLNA device using said DLNA enabler network.
10. The system as in claim 9, wherein said DLNA enabler network is further configured to initiate said DLNA content read for said non DLNA device by:
connecting a DLNA/UPnP USB bridge to said non DLNA device;
sending a control command corresponding to said content read operation to said DLNA/UPnP USB bridge from a DLNA /UPnP controller;
receiving said control command by said DLNA/UPnP USB bridge;
generating IR commands corresponding to said received control command by said DLNA/UPnP USB bridge; and
providing said generated IR commands to said non-DLNA device using said DLNA/UPnP USB bridge; and
receiving SCSI command in response to said IR command from said non-DLNA device by said DLNA/UPnP USB bridge.
11. The system as in claim 10, wherein said DLNA enabler network is further configured to provide means for pre-configuring said control commands and corresponding IR commands with said DLNA/UPnP USB bridge.
12. The system as in claim 9, wherein said DLNA enabler network is further configured to read said the DLNA content using said non DLNA device by:
receiving at least one SCSI command corresponding to said read operation from said non DLNA device using said DLNA/UPnP USB bridge;
analyzing said received SCSI command using said DLNA/UPnP USB bridge;
discovering all media servers in own network using said DLNA/UPnP USB bridge;
fetching content to be read from at least one of said discovered media servers using said DLNA/UPnP USB bridge;
creating a virtual file stack corresponding to said fetched content to be read in said DLNA/UPnP USB bridge; and
reading said content from said DLNA/UPnP USB bridge using said non DLNA device.
13. The system as in claim 12, wherein said DLNA/UPnP USB bridge is configured to select said content to be read from at least one of said discovered media servers based on inputs from a DLNA /UPnP controller.
14. The system as in claim 12, wherein said DLNA enabler network is configured to analyze said SCSI command by:
unwrapping said SCSI commands using a USB mass storage command interpreter in said DLNA/UPnP USB bridge; and
interpreting said unwrapped commands using a SCSI command interpreter in said DLNA/UPnP USB bridge.
Dated: 13-06-2013 Signature: Vikram Pratap SinghThakur
(Patent Agent)
,TagSPECI:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005
COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)
TITLE OF THE INVENTION
DLNA/UPnP-USB Mass Storage and IR Bridge With DLNA/UPnP Control
APPLICANTS:
Name : HCL Technologies Limited
Nationality : Indian
Address : HCL Technologies Ltd., 50-53 Greams
Road,Chennai – 600006, Tamil Nadu, India
The following Specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:
FIELD OF INVENTION
[001] The embodiments herein relate to digital home entertainment and, more particularly, to enable network connectivity of non-DLNA devices having USB port which are present in DLNA environment.
BACKGROUND
[002] In recent years, consumer electronic devices (like ipods, tablet PC’s, smart phones) that can access, store and play media content have become increasingly popular. At same time, digital home entertainment using wireless networks has also become common in many households. Digital Living Network Alliance (DLNA) is a technology/ a set of protocols defined to share digital contents between multimedia devices. DLNA uses universal plug and play for media management. DLNA and other similar technologies act as a bridge between various electronic devices and enable them to share data/contents such as photos, videos, music- and so on with each other.
[003] However, disadvantages of the existing sharing systems are that they do not provide means to facilitate content sharing/access for devices that do not have network access and content sharing capabilities. For example, old CD/DVD players do not have options to access network and to share or access multimedia data.
[004] What is needed therefore is a system and method that can enable devices that do not have network access and content sharing capabilities to access content from DLNA enabled media servers and also control these devices from DLNA enabled controllers present in the network.
SUMMARY
[005] In view of the foregoing, an embodiment herein provides a method for playing DLNA contents in a non DLNA device, said method comprises initiating a DLNA content read for said non DLNA device; and reading said DLNA content using said non DLNA device.
[006] Embodiments further disclose a system for playing DLNA contents in a non DLNA device, said system configured for initiating a DLNA content read for said non DLNA device using a DLNA enabler network; and reading said DLNA content using said non DLNA device using said DLNA enabler network.
[007] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.
BRIEF DESCRIPTION OF THE FIGURES
[008] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[009] FIG. 1 illustrates a block diagram of DLNA enabler network, as disclosed in the embodiments herein;
[0010] FIG. 2 illustrates a block diagram that shows various components of DLNA/UPnP-USB bridge, as disclosed in the embodiments herein;
[0011] FIG. 3 illustrates a block diagram that shows various components of configuration module, as disclosed in the embodiments herein;
[0012] FIG. 4 illustrates a block diagram that shows various components of DLNA/UPnP module, as disclosed in the embodiments herein;
[0013] FIG. 5 illustrates a block diagram that shows various components of device connectivity module, as disclosed in the embodiments herein;
[0014] FIG. 6 illustrates a block diagram that shows various components of USB interface module, as disclosed in the embodiments herein;
[0015] FIG. 7 illustrates a block diagram that shows various components of IR interface module, as disclosed in the embodiments herein;
[0016] FIG. 8 illustrates a block diagram that shows various components of memory module, as disclosed in the embodiments herein; and
[0017] FIG. 9 is a flow diagram which shows various steps involved in the process of enabling non-DLNA devices to use DLNA based data sharing options using the DLNA/UPnP-USB bridge, as disclosed in the embodiments herein.
DETAILED DESCRIPTION OF INVENTION
[0018] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0019] The embodiments herein disclose a system and method for enabling non-DLNA devices to access DLNA based data sharing services using a DLNA/UPnP-USB bridge. Referring now to the drawings, and more particularly to FIGS. 1 through 9, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0020] FIG. 1 illustrates a general block diagram of DLNA enabler network, as disclosed in the embodiments herein. The system comprises of a non-DLNA device 101, a DLNA/UPnP-USB bridge 102, a DLNA/UPnP controller103, a DLNA/UPnP media server 104 and a home router 105.The non-DLNA device 101 can be any type of network disabled digital media device (CD/DVD/audio player) that is capable of accessing digital media content from a USB port. Further, non-DLNA device 101 accesses and plays media content from a USB mass storage device connected to the USB port based on IR commands such as PLAY, STOP, PAUSE and so on, received by the IR receiver present in the non-DLNA device 101.
[0021] The DLNA/UPnP-USB bridge 102 acts as an interface between non-DLNA device 101 and DLNA network elements such as DLNA/UPnP controller 103, DLNA/UPnP media server 104. The DLNA/UPnP-USB bridge 102 is connected to the non-DLNA device 101 through the USB ports of the non-DLNA device 101. The DLNA/UPnP-USB bridge 102 discovers all DLNA enabled media servers 104 present in the network and stores the file names and directories present in DLNA/UPnP media servers 104 in the form of virtual files i.e. as virtual file system. Further, DLNA/UPnP-USB bridge 102 fetches the actual file contents when it is required from DLNA/UPnP media servers 104. Further more, the DLNA/UPnP-USB bridge 102 transmits IR commands to non-DLNA device 101 on receiving corresponding commands from DLNA/UPnP controller 103 present in the network and the commands are executed on the non-DLNA device 101.
[0022] The DLNA/UPnP controller 103 may be any type of DLNA certified/enabled product (e.g. smart phone) that is capable of controlling other DLNA enabled devices present in the network through the home router 105. Similarly, the DLNA/UPnP media server 104 may be any memory storage system that is capable of sharing stored media content with other DLNA enabled devices present in the network through the home router 105.
[0023] FIG. 2 illustrates a block diagram that shows various components of DLNA/UPnP-USB bridge, as disclosed in the embodiments herein. The DLNA/UPnP-USB bridge 102 comprises of a configuration module 201, a DLNA/UPnP module 202, a device connectivity module 203, a network connectivity module 204 and a memory module 205.
[0024] The configuration module 201, stores the configuration data such as IR command details i.e. commands of each non-DLNA device 101 in memory module 205. Later, when a particular non-DLNA device 101 is connected to DLNA/UPnP USB bridge 102, the configuration module 201 automatically detects and manages the connected non-DLNA device 101 by fetching appropriate configuration data from memory module 205.
[0025] The DLNA/UPnP module 202, discovers all the DLNA/UPnP media servers 104 present in the network through network connectivity module 204. Further, it reads the content present in the DLNA media servers 104 by using suitable DLNA/UPnP commands and transfer protocols, and stores the read data such as directories and file names of media content in the memory module 205 by creating a virtual file system. The device connectivity module 203 provides all the functionalities required to mount the DLNA/UPnP-USB bridge 102 as mass storage device by the non-DLNA device 101 i.e., when the DLNA/UPnP-USB bridge 102 is connected to USB port of a non-DLNA device 101, the non-DLNA device 101 treats the DLNA/UPnP-USB bridge as general mass storage device such as pen drive. Further, network connectivity module 204 contains required network interface such as Wi-Fi in order to communicate DLNA/UPnP-USB bridge with other network devices such as DLNA media server 104, DLNA/UPnP controller 103 through home router 105.
[0026] FIG. 3 illustrates a block diagram that shows various components of configuration module, as disclosed in the embodiments herein. The configuration module 201 comprises of a configuration manager 301 and a switch interface 302. The DLNA/UPnP-USB bridge 102 can be used with multiple non-DLNA devices 101. Further, DLNA/UPnP-USB bridge 102 can be connected with only one non-DLNA device 101 at a time. The commands to configure different non-DLNA devices 101 are different from each other. The configuration manager 301 learns the commands corresponding to each host when the DLNA/UPnP device 101 is connected for the first time. This can be done by running the DLNA/UPnP-USB bridge 102 in programming mode. The programming mode can be selected either by using switches or through the web interface. After placing the DLNA/UPnP-USB bridge 102 in programming mode, the non-DLNA device owned IR remote is placed in front of IR module present in the device connectivity module 203 of DLNA/UPnP-USB bridge 102. Later, non-DLNA device 101 specific configuration IR commands are received and sent to memory module 205 of DLNA/UPnP-USB bridge 102 while a user is pressing buttons of the remote control. For example, when the button PLAY is pressed in the device owned IR remote control, the IR command configuration related to PLAY option is received by configuration manager 301 and stores it in memory module 205. Similarly, command configurations of all other options such as PLAY, STOP, and PAUSE and so on are received and stored them in memory module 205. In another embodiment, the non-DLNA device 101 specific configurations can be downloaded to the DLNA/UPnP-USB bridge 102 via web interface.
[0027] If a non-DLNA device 101 is configured once, then the configuration manager 301 automatically detects the connected non-DLNA device 101 and selects the configuration corresponding to particular detected non-DLNA device 101 from the list of configurations stored. This can be done by sending IR commands regarding specific action such as PLAY, STOP, and PAUSE and so on from each set of configuration to the non-DLNA device 101 via IR control stack system 702 present in IR interface module 502. Further, configuration manager 301 monitors the SCSI commands that are sent to the DLNA/UPnP-USB bridge 102 from the non-DLNA device 101. If the SCSI command changes corresponding to a particular configuration, it can be determined that the DLNA/UPnP-USB bridge 102 is connected to that particular host. For example, when IR command corresponding to PAUSE/STOP is sent, SCSI READ commands for reading the file will stop. When IR commands corresponding to PLAY is sent, SCSI READ commands for reading the file will start. Thus the configuration manager 301 can detect the corresponding configuration IR commands of a particular non-DLNA device 101. In an embodiment, selection between multiple configurations can be made by manually selecting through switch interface 302 or via web interface.
[0028] FIG. 4 illustrates a block diagram that shows various components of DLNA/UPnP module, as disclosed in the embodiments herein. The DLNA/UPnP module 202 comprises of a DLNA/UPnP stack 401, a Transfer protocol stack 402 and a SCSI-DLNA adapter 403.
[0029] The DLNA/UPnP stack system of DLNA/UPnP module 202 is responsible for discovering and communicating DLNA/UPnP-USB bridge 102 with various DLNA enabled devices such as DLNA/UPnP media servers 104 present in the network by using DLNA/UPnP stack 401 and Transfer protocol stack 402. The Transfer protocol stack 402 starts and maintains the sessions with identified DLNA/UPnP media servers 104 using protocols such as HTTP/RTP/RTSP/RTCP in order to access the media content present in the DLNA/UPnP media servers 104. Further, DLNA/UPnP stack 401 handles the DLNA/UPnP specific events such as identifying new media servers, removal of current media servers and so on.
[0030] The SCSI-DLNA adapter 403 of DLNA/UPnP module 202 creates a virtual file system. The SCSI-DLNA adapter 403 of DLNA/UPnP module 202 enumerates the DLNA media servers 104 and their content using the DLNA/UPnP stack 401. This is done using commands like ContentDirectory::Browse( ) and ContentDirectory::Search( ).Each server is presented as a separate root folders in virtual file system. The files/folders of the servers are presented as files/folders, in the folders of respective servers in virtual file system. Further, the SCSI-DLNA adapter 403 is capable of fetching these virtual files back from memory module 205 whenever required. In an embodiment, the SCSI-DLNA adapter 403 can create virtual file system in form of File Allocation Table (FAT) architecture. Later by using SCSI commands, the content of the file system can be accessed. The actual contents of a particular folder and files may not be stored in advance in virtual file system. The contents will be fetched from media server 104 and stored into virtual file system whenever required. For example, when a request to READ the file folder is made by USB mass storage stack of non-DLNA device 101, the particular file folder is fetched. .Further more, the DLNA/UPnP stack 401 receives the execution commands/requests such as PAUSE, PLAY, STOP and so on from DLNA/UPnP controller 103.Later, these commands are forwarded to IR DLNA/UPnP adapter 701 which in turn delivers to IR control stack system 702 present in the IR interface module 502 for converting them to corresponding IR commands.
[0031] FIG. 5 illustrates a block diagram that shows various components of device connectivity module, as disclosed in the embodiments herein. The device connectivity module 203 further comprises of a USB interface module 501 and an IR interface module 502. The device connectivity module 203 provides all the functionalities required to mount the DLNA/UPnP-USB bridge 102 as mass storage device by the non-DLNA device 101. Further, device connectivity module 203 receives commands/requests from non-DLNA device 101 through USB interface present between non-DLNA device 101 and DLNA/UPnP-USB bridge 102. Depending upon the command/request coming from non-DLNA device 101, content will be accessed from virtual file system 801.
[0032] FIG. 6 illustrates a block diagram that shows various components of USB interface module, as disclosed in the embodiments herein. USB interface module 501 further comprises of a USB mass storage command interpreter 601 and SCSI command interpreter 602.
[0033] When non-DLNA device 101 receives IR commands/requests from DLNA/UPnP-USB bridge 102, it sends corresponding SCSI commands to USB mass storage command interpreter 601 of USB interface module 501 through USB interface. Further, USB mass storage command interpreter 601 unwraps the received commands before transmitting them to SCSI command interpreter 602. Further more, SCSI command interpreter 602 interprets the received commands and finally transmits the interpreted SCSI commands to SCSI-DLNA adapter 403 through command set such as READ, WRITE and so on. Similarly, all the responses from SCSI-DLNA adapter 403 are converted into SCSI status before being converted to USB command status wrapper. Finally these USB command status wrappers are sent to non-DLNA device 101.
[0034] FIG. 7 illustrates a block diagram that shows various components of IR interface module, as disclosed in the embodiments herein. IR interface module 502 further comprises of an IR-DLNA/UPnP adapter 701 and an IR control stack system 702. The DLNA/UPnP-USB bridge 102 transmits the commands/requests which are received from DLNA/UPnP controller 103 to the non-DLNA device 101 through IR communication only as the non-DLNA devices are mostly controlled by IR signals. This can be done by IR-DLNA/UPnP adapter 701 which receives commands/requests as PLAY, PAUSE, and STOP and so on from DLNA/UPnP stack system. Further, these commands/requests are given to IR control stack system 702 which transmits corresponding IR commands by providing a suitable interface.
[0035] FIG. 9 is a flow diagram which shows various steps involved in the process of enabling non-DLNA devices to use DLNA based data sharing options using the DLNA/UPnP-USB bridge, as disclosed in the embodiments herein. Initially, the desired non-DLNA device 101 is connected to the DLNA/UPnP-USB bridge 102 by using an USB connecter between USB ports of non-DLNA device 101 and DLNA/UPnP-USB bridge 102. Then, the configuration module 201 of DLNA/UPnP-USB bridge 102 automatically chooses the correct configuration (902) corresponding to non-DLNA device 101 to which it is connected from the list of configurations stored. In an embodiment, configuration manager 301 of configuration module 201 learns the configurations corresponding to each non-DLNA devices 101 when they are connected for the first time and stores them in memory module 205. For example, the non-DLNA device 101 specific configuration IR commands are received and sent to memory module 205 of DLNA/UPnP-USB bridge 102 while a user is pressing buttons of the remote control. For example, when the button PLAY is pressed in the device owned IR remote control, the IR command configuration related to PLAY option is received by configuration manager 301 and stores it in memory module 205. Similarly, command configurations of all other options such as PLAY, STOP, PAUSE, and so on are received and stored them in memory module 205. Further, these commands can be read from the memory module whenever required. In another embodiment, the non-DLNA device 101 specific configurations can be downloaded to the DLNA/UPnP-USB bridge 102 via web interface.
[0036] The DLNA/UPnP stack system of DLNA/UPnP module 202 discovers all the DLNA/UPnP media servers 104 present in the network. Further, DLNA/UPnP stack 401 reads (904) the media content information like file names and directories present in these DLNA/UPnP media servers 104 using DLNA/UPnP stack 401 and transfer protocol stack 402. Later, SCSI-DLNA adapter 403 presents these media content information as virtual FAT files (906) in the folders of respective servers and stores them in memory buffers of memory module 205.
[0037] The control of non-DLNA device 101 can be achieved by sending corresponding control commands such as PLAY, PAUSE, and STOP and so on from DNLA/UPnP controller 103. The DLNA/UPnP-USB bridge 102 receives (908) these control commands through network connectivity module 204 by using suitable network interface such as Wi-Fi, Ethernet etc. Further, the DLNA/UPnP stack 401 receives these control commands from DLNA/UPnP controller 103 which in turn transmits them to IR-DLNA/UPnP adapter 701. Later, IR commands corresponding to the received control commands will be generated (910) and transmitted through the IR control stack system 702 present in the IR interface module 502. Further, the IR receiver of non-DLNA device 101 receives these signals. Now, the non-DLNA device 101 sends SCSI commands corresponding to the received IR commands to USB mass storage command interpreter 601 of USB interface 501. The USB mass storage command interpreter 601 unwraps these commands and transmits them to SCSI command interpreter 602 which interprets these commands before SCSI-DLNA adapter 403 receives them. Based on the received control commands, SCSI-DLNA adapter 403 accesses (912) the stored media content information like file names and directories from memory module 205 and then fetches the required media content from DLNA media servers 104 by using suitable transfer protocols. Finally, SCSI-DLNA adapter 403 provides the fetched media content to the USB port of non-DLNA device through the USB interface 203 of DLNA/UPnP-USB bridge 102.
[0038] For example, if PLAY is given as command through DLNA/UPnP controller 103, the DLNA-UPnP stack system which is present in DLNA/UPnP-USB bridge 102 receives this command through its network connectivity module 204. Further, IR interface module 502 of device connectivity module 203 generates and transmits corresponding IR PLAY command by using suitable interface such as IR transmitter. The IR receiver of non-DLNA device 101 receives PLAY command and further sends corresponding SCSI commands to USB interface module 501 of DLNA/UPnP-USB bridge 102 through USB interface. Now SCSI-DLNA adapter 403 fetches the required media content from DLNA media servers 104. Then the non-DLNA device 101 starts reading the media content from its USB port which is provided by the USB interface 203 of DLNA/UPnP-USB bridge 102. The various actions in method 900 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 9 may be omitted.
[0039] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1 to Fig. 8 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0040] The embodiment disclosed herein specifies a system for enabling non-DLNA devices having USB port to use DLNA based network connectivity and data sharing. The mechanism allows using a DLNA/UPnP-USB bridge between non-DLNA device and DLNA network providing a system thereof. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means and/or at least one software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. The device may also include only software means. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.
[0041] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.
| # | Name | Date |
|---|---|---|
| 1 | 2580-CHE-2013-Correspondence to notify the Controller [29-12-2022(online)].pdf | 2022-12-29 |
| 1 | Form 5.pdf | 2013-06-15 |
| 2 | 2580-CHE-2013-US(14)-HearingNotice-(HearingDate-03-01-2023).pdf | 2022-12-12 |
| 2 | FORM 3.pdf | 2013-06-15 |
| 3 | Form 2.pdf | 2013-06-15 |
| 3 | 2580-CHE-2013-FORM-26 [29-07-2021(online)].pdf | 2021-07-29 |
| 4 | drawings.pdf | 2013-06-15 |
| 4 | 2580-CHE-2013-FORM 13 [09-07-2021(online)].pdf | 2021-07-09 |
| 5 | 2580-CHE-2013-POA [09-07-2021(online)].pdf | 2021-07-09 |
| 5 | 2580-CHE-2013 FORM-9 18-06-2013.pdf | 2013-06-18 |
| 6 | 2580-CHE-2013-Proof of Right [29-01-2020(online)].pdf | 2020-01-29 |
| 6 | 2580-CHE-2013 FORM-18 18-06-2013.pdf | 2013-06-18 |
| 7 | 2580-CHE-2013-ABSTRACT [01-10-2019(online)].pdf | 2019-10-01 |
| 7 | 2580-CHE-2013 CORRESPONDENCE OTHERS 25-06-2013.pdf | 2013-06-25 |
| 8 | 2580-CHE-2013-CLAIMS [01-10-2019(online)].pdf | 2019-10-01 |
| 8 | 2580-CHE-2013 POWER OF ATTORNEY 25-06-2013.pdf | 2013-06-25 |
| 9 | 2580-CHE-2013 FORM-1 25-06-2013.pdf | 2013-06-25 |
| 9 | 2580-CHE-2013-CORRESPONDENCE [01-10-2019(online)].pdf | 2019-10-01 |
| 10 | 2580-CHE-2013-FER_SER_REPLY [01-10-2019(online)].pdf | 2019-10-01 |
| 10 | abstract2580-CHE-2013.jpg | 2013-07-01 |
| 11 | 2580-CHE-2013-FER.pdf | 2019-04-05 |
| 11 | 2580-CHE-2013-FORM 13 [01-10-2019(online)].pdf | 2019-10-01 |
| 12 | 2580-CHE-2013-OTHERS [01-10-2019(online)].pdf | 2019-10-01 |
| 12 | 2580-CHE-2013-RELEVANT DOCUMENTS [01-10-2019(online)].pdf | 2019-10-01 |
| 13 | 2580-CHE-2013-OTHERS [01-10-2019(online)].pdf | 2019-10-01 |
| 13 | 2580-CHE-2013-RELEVANT DOCUMENTS [01-10-2019(online)].pdf | 2019-10-01 |
| 14 | 2580-CHE-2013-FER.pdf | 2019-04-05 |
| 14 | 2580-CHE-2013-FORM 13 [01-10-2019(online)].pdf | 2019-10-01 |
| 15 | 2580-CHE-2013-FER_SER_REPLY [01-10-2019(online)].pdf | 2019-10-01 |
| 15 | abstract2580-CHE-2013.jpg | 2013-07-01 |
| 16 | 2580-CHE-2013 FORM-1 25-06-2013.pdf | 2013-06-25 |
| 16 | 2580-CHE-2013-CORRESPONDENCE [01-10-2019(online)].pdf | 2019-10-01 |
| 17 | 2580-CHE-2013-CLAIMS [01-10-2019(online)].pdf | 2019-10-01 |
| 17 | 2580-CHE-2013 POWER OF ATTORNEY 25-06-2013.pdf | 2013-06-25 |
| 18 | 2580-CHE-2013-ABSTRACT [01-10-2019(online)].pdf | 2019-10-01 |
| 18 | 2580-CHE-2013 CORRESPONDENCE OTHERS 25-06-2013.pdf | 2013-06-25 |
| 19 | 2580-CHE-2013-Proof of Right [29-01-2020(online)].pdf | 2020-01-29 |
| 19 | 2580-CHE-2013 FORM-18 18-06-2013.pdf | 2013-06-18 |
| 20 | 2580-CHE-2013-POA [09-07-2021(online)].pdf | 2021-07-09 |
| 20 | 2580-CHE-2013 FORM-9 18-06-2013.pdf | 2013-06-18 |
| 21 | drawings.pdf | 2013-06-15 |
| 21 | 2580-CHE-2013-FORM 13 [09-07-2021(online)].pdf | 2021-07-09 |
| 22 | Form 2.pdf | 2013-06-15 |
| 22 | 2580-CHE-2013-FORM-26 [29-07-2021(online)].pdf | 2021-07-29 |
| 23 | FORM 3.pdf | 2013-06-15 |
| 23 | 2580-CHE-2013-US(14)-HearingNotice-(HearingDate-03-01-2023).pdf | 2022-12-12 |
| 24 | Form 5.pdf | 2013-06-15 |
| 24 | 2580-CHE-2013-Correspondence to notify the Controller [29-12-2022(online)].pdf | 2022-12-29 |
| 1 | tpo_05-04-2019.pdf |