+

WO1999065188A2 - Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede - Google Patents

Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede Download PDF

Info

Publication number
WO1999065188A2
WO1999065188A2 PCT/EP1999/003952 EP9903952W WO9965188A2 WO 1999065188 A2 WO1999065188 A2 WO 1999065188A2 EP 9903952 W EP9903952 W EP 9903952W WO 9965188 A2 WO9965188 A2 WO 9965188A2
Authority
WO
WIPO (PCT)
Prior art keywords
internet
connection
network
web
request
Prior art date
Application number
PCT/EP1999/003952
Other languages
English (en)
Other versions
WO1999065188A3 (fr
Inventor
Guillaume Bichot
Gilles Straub
Original Assignee
Thomson Multimedia
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thomson Multimedia filed Critical Thomson Multimedia
Priority to US09/719,147 priority Critical patent/US9736003B1/en
Priority to DE69928009T priority patent/DE69928009T2/de
Priority to HU0103875A priority patent/HU227780B1/hu
Priority to AU45100/99A priority patent/AU4510099A/en
Priority to EP99927920A priority patent/EP1142206B1/fr
Priority to JP2000554093A priority patent/JP4404483B2/ja
Publication of WO1999065188A2 publication Critical patent/WO1999065188A2/fr
Publication of WO1999065188A3 publication Critical patent/WO1999065188A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2805—Home Audio Video Interoperability [HAVI] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/281—Exchanging configuration information on appliance services in a home automation network indicating a format for calling an appliance service function in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40058—Isochronous transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40117—Interconnection of audio or video/imaging devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities

Definitions

  • the invention concerns a communication method in a home network, in particular a HAVi-compliant network. It also concerns the network itself, and a device used in the implementation of the method.
  • the invention applies among others to the communication between an internet application running on a network device which may not necessarily have a direct access to the internet, and a device of the network which does have such an access.
  • Figure 1 is a diagram of the different devices and software layers required to access internet services from a personal computer 1 .
  • This computer 1 comprises an application including a user interface for interacting with a user, for example a 'WEB browser', qualified in figure 1 by the more general term 'WEB application'.
  • the WEB application lies above an application protocol layer (such as HTTP (Hypertext Transfer Protocol) or FTP (File Transfer Protocol) or another type of protocol).
  • the next layers are, according to the example of figure 1 , the TCP/UDP (Transmission Control Protocol, respectively User Data Protocol) layer, the IP (Internet Protocol) layer and the PPP layer.
  • the TCP/UDP and IP layers combined are referred to as the 'IP stack'.
  • the connection with an internet access provider 2 is made through modems and the public switched telephone network.
  • the internet access provider is connected to the internet, which comprises the server 3, the latter including layers globally similar in function to those of computer 1 .
  • a user may own a number of devices such as television receivers and personal computers which have the internet access functionality provided by the device 1 of figure 1 .
  • the hardware and software required for providing the internet access capability is duplicated in each device.
  • the object of the invention is a communication method in a home network comprising at least two devices connected to a communication bus, characterized in that, a first device including an internet application and a second device including means for connecting to the internet, said second device being able to manage at least one internet application protocol, said method comprises the steps of:
  • an internet application establishing an internet connection through the second device specifies itself the internet application protocol it wishes to use. This provides a very flexible way to use different internet application protocols within a same network.
  • the inventive method includes the step of sending, by said first device to said second device, a request for a list of internet application protocols supported by said second device.
  • the invention also concerns a home communication network comprising devices connected by a communication bus, said network comprising at least one device including a WEB interface, said device comprising an IP stack and a connection to the internet, said at least one device comprising an application programmable interface for making said WEB interface accessible to software element clients of other devices in said network.
  • the invention also concerns a device in a home communication network characterized in that it comprises a WEB interface, said device also comprising an IP stack and a connection to the internet, said at least one device comprising an application programmable interface for making said WEB interface accessible to software element clients of other devices in said network.
  • FIG. 1 is a schematic diagram of devices and connections for accessing an internet server from a home equipment
  • FIG. 2 is a diagram of a home network according to the present invention.
  • FIG. 3 is a diagram of the messages exchanged between the WEB client and the WEB proxy agent
  • FIG. 4 is a diagram of the communication between software elements for establishing a communication between a WEB client software element and a WEB server via a WEB proxy agent.
  • HAVi Home Audio/Video interoperability
  • Hypertext Transfer Protocol / 1 .1 RFC 2068' can be used as a reference.
  • Other protocols than HTTP may be used: FTP, SMTP, POP, IMAP and NNTP are some examples.
  • FTP, SMTP, POP, IMAP and NNTP are some examples.
  • An introduction to a HAVi-compliant network architecture will first be given, in order to define a number of concepts necessary for the description of the embodiment of the invention.
  • a HAVi network comprises devices which can be of four types, these devices being linked by a communication bus. The different device types are, ordered according to their network-related capabilities: Full Audio/Video devices (FAV devices), Intermediate Audio ⁇ /ideo Devices (IAV devices), Basic Audio/Video devices (BAV devices), and Legacy Audio/Video devices (LAV devices).
  • FAV devices Full Audio/Video devices
  • IAV devices Intermediate Audio ⁇ /ideo Devices
  • BAV devices Basic Audio/Video devices
  • LAV devices Legacy Audio/Video devices
  • the other devices all have at least the capability of communicating with each other.
  • FAV devices contain a runtime environment for HAVi bytecode.
  • HAVi bytecode is a programming language in which device control modules (DCMs) or applications may be written.
  • DCMs device control modules
  • a FAV device may thus download DCMs from or for other devices which do not include this runtime environment, for example for cost reasons.
  • IAV devices do not have the capability to run HAVi bytecode, but may include resident DCMs for the control of other devices.
  • BAV devices are devices which either contain DCM code downloadable by a FAV device, or which are controlled by a native DCM run by an IAV device.
  • LAV devices are devices which do not have any HAVi capability. These devices have their own command protocol and require that a FAV or an IAV device act as a gateway to the HAVi network and perform the necessary control command translation.
  • Each device contains a number of objects, called 'software elements' in the HAVi terminology.
  • a control manager of a given function (called FCM) of a device i.e. a software element providing an interface for controlling a specific functional component (e.g. tuner, display, mass storage...) of a device is one of such objects.
  • FCM a control manager of a given function
  • a DCM as mentioned above is another one.
  • a FAV device would contain a number of applications and device control applications which interact with the following software elements through corresponding application programmable interfaces: - a 1394 Communication Media Manager, which allows other software elements to perform asynchronous and isochronous communication over the IEEE 1394 bus;
  • Stream Manager for managing Audio ⁇ /ideo data streams between functional components, such as a tuner and a recording device;
  • the Message Passing System allocates unique identifiers to software elements, which use these identifiers to register themselves with the Registry. These identifiers are called 'SEID', standing for Software Element Identifiers, and comprise a device identifier and a software element handle within that device.
  • 'SEID' standing for Software Element Identifiers
  • a first software element wishing to send a message to a second software element will pass the SEID of this second software element as a parameter in its command to the Message Passing System. It obtains this SEID by making an appropriate request with the local Registry service.
  • the calling software element will use the whole SEID or only its software element handle part.
  • the mapping of function calls into messages of the Message Passing System is described in detail in Chapter 3.2.3 of the HAVi 0.8 document.
  • the Message Passing System described in this version of the HAVi document can handle messages up to 64 Kb long.
  • FIG. 2 represents a HAVi-compliant home network comprising devices 20, 21 and 22 connected to a communication bus 23.
  • the bus 23 is for example an IEEE 1394 serial bus.
  • Device 20 is a digital television receiver, compatible with the Digital Video Broadcast (DVB) standard in use in Europe or the Direct Satellite System (DSS) in use in the United States. It comprises a WEB application, i.e. a software application capable of sending and/or requesting data through the internet using the HTTP protocol.
  • the WEB application of device 20 is an electronic program guide (EPG) exchanging information with a given internet server.
  • EPG electronic program guide
  • Device 22 is a personal computer, whose WEB application is an internet browser. Neither one of devices 20 and 22 possesses an IP stack, the PPP protocol layer or a modem connected to the public switched telephone network.
  • Device 21 comprises a WEB access application programming interface (WEB access API), as well as the IP stack, PPP protocol and a modem.
  • WEB access API WEB access application programming interface
  • Device 21 can be a FAV, a IAV or a BAV device.
  • the functional component module (FCM) giving access to IP stack operation by the different WEB applications is called 'Internet Proxy Agent', or 'WEB Proxy Agent'. It provides the WEB access application programmable interface which is the layer above the IP stack.
  • the device 21 is a digital television decoder comprising a modem.
  • the WEB Proxy FCM offers a sharable access to the internet. It registers upon reset or hot-plugging at the local Registry of device 21 , if that device is a FAV or IAV, or at the local registry of the FAV or IAV device which runs the Device Control Module corresponding to the WEB
  • Proxy FCM if device 21 is of the BAV type.
  • the WEB application which can also be referred to as 'WEB client', is able to detect the WEB Proxy FCM in the network by sending a request to its local Registry service.
  • the local Registry dispatches the request to distant Registries and collects the responses.
  • only the identifier ('SEID') of the WEB Proxy FCM of device 21 will be detected.
  • the WEB Proxy FCM preferably supports at least several commonly used internet protocols, such as HTTP, FTP, NNTP, SMTP, POP or IMAP.
  • the WEB client uses the WEB Proxy FCM application programmable protocol through the Message Passing System.
  • the application programmable interface comprises the following functions: Open, Close, Send, Receive and GetCapability.
  • This data structure indicates the list of WEB application protocols the WEB proxy FCM may support.
  • - protocol this parameter, set by the WEB client, defines the protocol (HTTP%) dedicated to the session the WEB client wants to open.
  • this parameter set by the WEB client, gives the maximum size of a message accepted by the WEB client, in other words the size of its message buffer.
  • the WEB proxy FCM will use this parameter to define the size of messages sent to the client. Data to be sent by the WEB Proxy FCM will be split in a number of data blocks, depending on this parameter.
  • this parameter is a code the WEB proxy FCM will use to forward an incoming response from the internet to the WEB client.
  • This operation code identifies a function of the WEB client which the WEB Proxy FCM has to call to forward a response to the client.
  • This parameter is set by the WEB client.
  • the value of the opCode identifies the function 'Receive'.
  • the operation code uniquely identifies a function within a software element. The unique address of a function in the network thus comprises the 'SEID' identifier and the operation code.
  • this parameter is an identifier of the connection between the WEB client and the WEB proxy FCM. It is defined by the WEB Proxy FCM. It allows several connections from the same software component client to be opened in parallel (with the same WEB Proxy FCM or with other WEB Proxy FCMs) and also permits to match a response from the internet with a request.
  • this parameter returned by the WEB Proxy FCM, indicates the maximum size (in bytes) of a message accepted by the WEB proxy FCM.
  • the WEB client will use this parameter to determine the size of messages, for example requests, sent by the WEB client to the WEB Proxy FCM.
  • the WEB Proxy FCM After reception of the 'Open' function from a WEB client, the WEB Proxy FCM will return, along with the parameters above, one of the following status values: '0' in case of successful session opening, '1' in case of resource allocation error, '2' if the protocol type is not supported by the WEB client. (b) 'Close' function
  • This function enables a WEB client to close a previously opened connection with a WEB Proxy FCM, identified by the 'cid' parameter.
  • the function prototype is defined as follows: Status WEBProxy::Open( in long cid
  • the only parameter is the 'cid' parameter, i.e. the identifier of this connection with the WEB proxy FCM.
  • the WEB Proxy FCM acknowledges with one of the following status values: 0: The connection has been closed successfully, 1 : The transmitted value of the 'cid' parameter is unknown.
  • this parameter determined by the calling software element, indicates if the message is the first message, an intermediate message or the last message in a sequence of messages. More than one message may be required to call this function, since the amount of data transmitted in the function call may be too great for the buffer of the WEB Proxy FCM to handle in one single message.
  • this parameter contains a part or the entire request according to the WEB "application" protocol used through the connection identified by the
  • the WEB Proxy FCM acknowledges with one of the following status values: O' if the message was processed successfully, '1 ' if the size of the 'web_data' exceeds the fixed maximum size, '2' if it is impossible to process this message,
  • the WEB client decides whether or not to close the connection or to send again the previous message.
  • - web_data contains a part or the entire response according to the WEB "application” protocol used through the connection identified by the 'cid' parameter.
  • the WEB client acknowledges with one of the following status values:
  • This function callable by the WEB client, returns the list of protocols which the WEB Proxy FCM supports.
  • the function prototype is the following: Void WEBProxy::GetCapability( out sequence ⁇ ProtocolType> ProtocolList
  • 'ProtocolList' is the list of WEB application protocols which are available through the FCM. More than one protocol may be supported by the WEB Proxy FCM.
  • Figure 3 gives an example of a typical message exchange between a WEB client and a WEB Proxy FCM.
  • a function call can trigger messages in two directions: a first message from the calling software element to the called software element with 'in-bound' parameters sent to this called software element, and a second message in the inverse direction, for shuttling back 'out-bound' parameters, if required.
  • the 'Open' function gives rise to a first message from the WEB client to the WEB Proxy FCM. This message informs the WEB Proxy FCM of the protocol which will be used over the connection which is being opened, and of the size of the buffer which the WEB client allocates for return messages for that particular connection.
  • Buffer sizes may be different from connection to connection.
  • the WEB client also transmits the operation code of the Receive function, which the WEB Proxy FCM has to use to call the Receive function at the WEB client.
  • the WEB client also transmits its own identifier 'SEID'. Assuming correct reception and processing, the WEB Proxy FCM responds by the return code '0' to indicate successful processing, sends a 'cid' value to identify the connection, and also transmits its own buffer size for further communication.
  • the Web client proceeds to send a request to a WEB server, using the HTTP protocol.
  • this request holds in a single message, which contains the connection identifier cid, the request under HTTP format, and the 'End' parameter.
  • the WEB Proxy FCM acknowledges proper receipt, and forwards the request over the internet via its IP stack and modem.
  • the WEB server will respond with the requested data and transmit it to the WEB Proxy FCM. Since in the present example, the quantity of data is far beyond the buffer capacity of the WEB client, the WEB Proxy FCM splits the data into messages of appropriate size.
  • the WEB Proxy FCM sends a first data block as a parameter within the Receive function call, using the operation code previously obtained from the WEB client, appended to the 'SEID' identifier of the WEB client. It uses 'START' as a parameter. Further messages are only sent after acknowledgment of receipt by the WEB client, to give it the time to process the received data and to empty its buffer. After having received the last data block, the WEB client closes the connection using the Close function. The WEB Proxy FCM answers by a last acknowledgment of receipt.
  • the configuration of the WEB Proxy FCM is carried out directly by the user through a graphical interface provided by the Device Control Module which manages the WEB Proxy FCM.
  • the Device Control Module which manages the WEB Proxy FCM.
  • DAI data driven interaction
  • a device which controls other devices An IAV or FAV device.
  • a HAVi mechanism allowing control of software elements, eg DCMs, via user interface elements such as buttons and icons.
  • DDI controller a HAVi mechanism allowing control of software elements, eg DCMs, via user interface elements such as buttons and icons.
  • a software entity which renders DDI elements and handles user interaction.
  • the HAVi messages supporting data driven interaction supporting data driven interaction.
  • a physical entity attached to the home network examples are video players, recorders, cameras, CD and DVD players, set-top boxes, DTV receivers, and PCs.
  • a HAVi software element allowing user control of a specific device (and its functional components). Installed on request and possibly on a different controller than the one on which the DCM is installed.
  • DCM device control module
  • a HAVi software element providing an interface for controlling general functions of a device.
  • Installation of a DCM code unit results in one DCM and one or more FCMs and possibly one device control application.
  • Embedded DCMs typically run on IAV devices.
  • a HAVi-compliant device which runs the software elements of the HAVi Architecture including a HAVi bytecode runtime.
  • a DTV receiver may consist of several functional components: tuner, decoder, audio amplifier, etc.
  • FCM functional component module
  • a HAVi software element providing an interface for controlling a specific functional component of a device.
  • GUID global unique ID
  • the GUID is stored in a device's configuration ROM and is persistent over 1394 network resets.
  • the HAVi Architecture comprises the messaging model, control model, device model, and execution environment defined in this document.
  • FAV devices contain a runtime environment for loading and executing HAVi bytecode.
  • HAVi bytecode is not yet specified but will be selected from existing candidates.
  • SDD Self Describing Device
  • HAVi specifies SDD data items that may be used for DDI elements or uploaded DCMs.
  • HAVi unique ID A unique identification of devices and their functional components. Persistent over changes in network configuration (i.e., device plug-in or plug-out).
  • the home network is the generic name used to define the communications infrastructure within the home. This name is used as an abstraction from the physical media and associated protocols.
  • a home network supports both the exchange of control information and the exchange of AV content.
  • a HAVi-compliant device which runs the software elements of the HAVi Architecture but does not include a HAVi bytecode runtime environment.
  • LAV legacy AV device
  • a software element A HAVi object.
  • a software element responds to a set of messages specified by the API for that element.
  • SEID software element ID

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Selective Calling Equipment (AREA)

Abstract

L'invention concerne un procédé de communication dans un réseau familial comprenant aux moins deux dispositifs connectés à un bus de communication. Ce réseau se caractérise en ce qu'un premier dispositif comporte une application Internet et un deuxième dispositif comprend des moyens pour se connecter à Internet . Ledit deuxième dispositif peut gérer au moins un protocole d'application Internet. Ce procédé consiste à envoyer une demande depuis ledit premier dispositif audit deuxième dispositif pour établir une connexion entre eux. Cette demande contient un identificateur du protocole d'application Internet permettant d'identifier ledit protocole devant être utilisé pour assurer la connexion. Ce procédé consiste ensuite à envoyer une demande de protocole Internet dans le format du protocole d'application Internet, du premier dispositif au deuxième dispositif, puis à envoyer ladite demande de protocole Internet du deuxième dispositif au serveur Internet. Enfin, à réception, ce procédé consiste à transférer la réponse dudit serveur Internet au premier dispositif, via le deuxième dispositif, par l'intermédiaire du bus de communication. L'invention traite d'un réseau et d'un dispositif pour mettre en oeuvre le procédé décrit ci-dessus.
PCT/EP1999/003952 1998-06-06 1999-06-07 Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede WO1999065188A2 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US09/719,147 US9736003B1 (en) 1998-06-06 1999-06-07 Communication method in a home network, network and device for implementing such a method
DE69928009T DE69928009T2 (de) 1998-06-08 1999-06-07 Kommunikationsverfahren für ein hausnetzwerk, netzwerk und vorrichtung zum durchführen des verfahrens
HU0103875A HU227780B1 (en) 1998-06-08 1999-06-07 Communication method and device in a home network
AU45100/99A AU4510099A (en) 1998-06-08 1999-06-07 Communication method in a home network, network and device for implementing sucha method
EP99927920A EP1142206B1 (fr) 1998-06-08 1999-06-07 Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede
JP2000554093A JP4404483B2 (ja) 1998-06-08 1999-06-07 家庭内ネットワークにおける通信方法、かかる方法を実施するためのネットワーク及び機器

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP98401372 1998-06-08
EP98401372.2 1998-06-08
EP98402384A EP0964558A1 (fr) 1998-06-08 1998-09-28 Méthode pour accéder aux applications Internet par les équipements d'un réseau domotique
EP98402384.6 1998-09-28

Publications (2)

Publication Number Publication Date
WO1999065188A2 true WO1999065188A2 (fr) 1999-12-16
WO1999065188A3 WO1999065188A3 (fr) 2001-07-12

Family

ID=26151645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP1999/003952 WO1999065188A2 (fr) 1998-06-06 1999-06-07 Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede

Country Status (11)

Country Link
US (1) US9736003B1 (fr)
EP (2) EP0964558A1 (fr)
JP (1) JP4404483B2 (fr)
KR (1) KR100640091B1 (fr)
CN (1) CN1367968A (fr)
AU (1) AU4510099A (fr)
DE (1) DE69928009T2 (fr)
ES (1) ES2251197T3 (fr)
HU (1) HU227780B1 (fr)
MY (1) MY130201A (fr)
WO (1) WO1999065188A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10260143A1 (de) * 2002-12-20 2004-07-01 BSH Bosch und Siemens Hausgeräte GmbH Übertragung von Dateien in einem lokalen Hausgeräte-Netzwerk
US7295550B2 (en) 2002-03-13 2007-11-13 Matsushita Electric Industrial Co., Ltd. Data communication method
US9348548B2 (en) 2013-11-01 2016-05-24 Seiko Epson Corporation Print control system
US9542133B2 (en) 2013-11-01 2017-01-10 Seiko Epson Corporation Print control system and print control method

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001030026A2 (fr) * 1999-10-18 2001-04-26 Gateway, Inc. Acces de reseau a multiples paliers
US20020099799A1 (en) * 2000-06-19 2002-07-25 Kolsky Amir D. Method and system for universal and transparent access to heterogeneous resources
US20020078161A1 (en) * 2000-12-19 2002-06-20 Philips Electronics North America Corporation UPnP enabling device for heterogeneous networks of slave devices
KR100416342B1 (ko) * 2001-02-06 2004-01-31 주식회사 케이티프리텔 Ｓｍｓ와 무선 인터넷을 이용한 데이터 수신 방법 및시스템
FR2828043B1 (fr) * 2001-07-26 2003-10-10 Canon Kk Procede et dispositif de configuration et d'utilisation d'une unite fonctionnelle dont l'utilisation est soumise a une condition de paiement dans un reseau de communication
DE60124092T8 (de) * 2001-08-22 2007-09-13 Sony Deutschland Gmbh Verfahren und System zum Betrieb eines Heimnetzes
US7634795B2 (en) * 2002-01-11 2009-12-15 Opentv, Inc. Next generation television receiver
DE10333608A1 (de) * 2003-07-24 2005-02-17 Deutsche Telekom Ag Dienste-integrierendes Kommunikationssystem sowie eine Anpassungs- und Anschalteeinrichtung für eine mehrere räumliche Bereiche aufweisende Umgebung
US7451198B2 (en) * 2003-08-29 2008-11-11 Microsoft Corporation WAP XML extension for WiFi and desktop passthrough connections
CN1972276B (zh) * 2006-11-26 2010-08-11 华为技术有限公司 一种协议访问管理方法和系统
GB2453315A (en) * 2007-08-15 2009-04-08 Nec Corp Connection Identifier in a telecommunications network
JP5056373B2 (ja) * 2007-11-22 2012-10-24 ソニー株式会社 情報処理装置及び情報処理方法
CN101505251B (zh) * 2008-02-04 2011-07-20 广达电脑股份有限公司 家用网络系统及其允入控制方法
CN110995712A (zh) * 2019-12-05 2020-04-10 浩云科技股份有限公司 安防物联网设备的数据交换方法及装置
JP6813110B1 (ja) * 2020-03-02 2021-01-13 ダイキン工業株式会社 通信装置、プログラム、通信方法、及び通信システム

Family Cites Families (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4777595A (en) 1982-05-07 1988-10-11 Digital Equipment Corporation Apparatus for transferring blocks of information from one node to a second node in a computer network
JPH04839A (ja) * 1990-04-17 1992-01-06 Nippon Telegr & Teleph Corp <Ntt> パケット通信方法
US5303347A (en) 1991-12-27 1994-04-12 Digital Equipment Corporation Attribute based multiple data structures in host for network received traffic
JP3611588B2 (ja) 1992-12-21 2005-01-19 ソニー株式会社 送信方法、受信方法、通信方法及び双方向バスシステム
US5537417A (en) * 1993-01-29 1996-07-16 International Business Machines Corporation Kernel socket structure for concurrent multiple protocol access
JPH08180001A (ja) * 1994-04-12 1996-07-12 Mitsubishi Electric Corp 通信方式及び通信方法及びネットワークインタフェース
US5757801A (en) 1994-04-19 1998-05-26 Multi-Tech Systems, Inc. Advanced priority statistical multiplexer
US5892910A (en) * 1995-02-28 1999-04-06 General Instrument Corporation CATV communication system for changing first protocol syntax processor which processes data of first format to second protocol syntax processor processes data of second format
JPH08256325A (ja) * 1995-03-16 1996-10-01 Olympus Optical Co Ltd 画像取扱システム
US5867660A (en) * 1995-05-11 1999-02-02 Bay Networks, Inc. Method and apparatus for communicating between a network workstation and an internet
US5802320A (en) * 1995-05-18 1998-09-01 Sun Microsystems, Inc. System for packet filtering of data packets at a computer network interface
JP3262689B2 (ja) * 1995-05-19 2002-03-04 富士通株式会社 遠隔操作システム
US6418324B1 (en) * 1995-06-01 2002-07-09 Padcom, Incorporated Apparatus and method for transparent wireless communication between a remote device and host system
US5710908A (en) * 1995-06-27 1998-01-20 Canon Kabushiki Kaisha Adaptive network protocol independent interface
US6108704A (en) * 1995-09-25 2000-08-22 Netspeak Corporation Point-to-point internet protocol
US5751951A (en) 1995-10-30 1998-05-12 Mitsubishi Electric Information Technology Center America, Inc. Network interface
IL124606A (en) * 1995-11-22 2003-05-29 Samsung Electronics Co Ltd Home multimedia network architecture
JPH09247209A (ja) 1996-03-12 1997-09-19 Chokosoku Network Computer Gijutsu Kenkyusho:Kk 資源予約チャネル用トランスポートレイヤプロトコルのフロー制御方式
US6393497B1 (en) * 1998-03-20 2002-05-21 Sun Microsystems, Inc. Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
US5940074A (en) * 1996-06-03 1999-08-17 Webtv Networks, Inc. Remote upgrade of software over a network
US6115744A (en) * 1996-07-30 2000-09-05 Bea Systems, Inc. Client object API and gateway to enable OLTP via the internet
US5751970A (en) 1996-08-08 1998-05-12 International Business Machines Corp. Method for determining an optimal segmentation size for file transmission in a communications system
US6208952B1 (en) * 1996-10-24 2001-03-27 Microsoft Corporation Method and system for delayed registration of protocols
US6490631B1 (en) * 1997-03-07 2002-12-03 Advanced Micro Devices Inc. Multiple processors in a row for protocol acceleration
US5938752C1 (en) * 1997-05-20 2002-02-05 Microsoft Corp System and method for encapsulating legacy data transport protocols for ieee 1394 serial bus
US6014704A (en) * 1997-06-04 2000-01-11 Nortel Networks Corporation Method and apparatus for communicating data and management information
US6021132A (en) 1997-06-30 2000-02-01 Sun Microsystems, Inc. Shared memory management in a switched network element
US6073172A (en) * 1997-07-14 2000-06-06 Freegate Corporation Initializing and reconfiguring a secure network interface
US6047338A (en) 1997-07-30 2000-04-04 Ncr Corporation System for transferring a data directly from/to an address space of a calling program upon the calling program invoking a high performance interface for computer networks
US6285659B1 (en) * 1997-09-10 2001-09-04 Level One Communications, Inc. Automatic protocol selection mechanism
US5982363A (en) * 1997-10-24 1999-11-09 General Instrument Corporation Personal computer-based set-top converter for television services
US6058434A (en) * 1997-11-26 2000-05-02 Acuity Imaging, Llc Apparent network interface for and between embedded and host processors
US6243743B1 (en) * 1998-01-29 2001-06-05 Automated Business Companies Split personal computer system
US6259443B1 (en) * 1998-02-06 2001-07-10 Henry R. Williams, Jr. Method and apparatus for enabling multiple users to concurrently access a remote server using set-top boxes
US6233577B1 (en) * 1998-02-17 2001-05-15 Phone.Com, Inc. Centralized certificate management system for two-way interactive communication devices in data networks
US6222855B1 (en) * 1998-02-19 2001-04-24 Lucent Technologies, Inc. Method and apparatus for converting between differing data and command exchange protocols
US6353614B1 (en) * 1998-03-05 2002-03-05 3Com Corporation Method and protocol for distributed network address translation
US6055236A (en) * 1998-03-05 2000-04-25 3Com Corporation Method and system for locating network services with distributed network address translation
US6085251A (en) * 1998-04-02 2000-07-04 The United States Of America As Represented By The Secretary Of The Air Force Implementing a parallel file transfer protocol
US6912588B1 (en) 1998-04-02 2005-06-28 Intel Corporation System and method for managing client requests in client-server networks
FR2778046B1 (fr) 1998-04-23 2000-05-19 Thomson Multimedia Sa Procede de gestion d'objets dans un reseau de communication et dispositif de mise en oeuvre
FI106763B (fi) * 1999-02-10 2001-03-30 Nokia Mobile Phones Ltd Menetelmä käytössä olevan protokollan tiedottamiseksi protokollapinon muille kerroksille
US6496867B1 (en) * 1999-08-27 2002-12-17 3Com Corporation System and method to negotiate private network addresses for initiating tunneling associations through private and/or public networks
JP4000839B2 (ja) 2001-11-30 2007-10-31 日立化成工業株式会社 感光性樹脂組成物、これを用いた感光性エレメント、レジストパターンの形成方法及びプリント配線板の製造方法
JP4291664B2 (ja) * 2003-10-14 2009-07-08 株式会社日立製作所 通信バッファ予約機能を備えるストレージ装置およびシステム

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
DESBONNET J ET AL: "SYSTEM ARCHITECTURE AND IMPLEMENTATION OF A CEBUS/INTERNET GATEWAY" IEEE TRANSACTIONS ON CONSUMER ELECTRONICS, vol. 43, no. 4, 1 November 1997 (1997-11-01), pages 1057-1062, XP000768558 ISSN: 0098-3063 *
PEISEL B: "DESIGNING THE NEXT STEP IN INTERNET APPLIANCES" ELECTRONIC DESIGN, vol. 46, no. 7, 23 March 1998 (1998-03-23), page 50, 52, 56 XP000780455 ISSN: 0013-4872 *
PRESTON D J: "INTERNET PROTOCOLS MIGRATE TO SILICON FOR NETWORKING DEVICES" ELECTRONIC DESIGN, vol. 45, no. 8, 14 April 1997 (1997-04-14), pages 87-90, 92 - 94, XP000730016 ISSN: 0013-4872 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7295550B2 (en) 2002-03-13 2007-11-13 Matsushita Electric Industrial Co., Ltd. Data communication method
DE10260143A1 (de) * 2002-12-20 2004-07-01 BSH Bosch und Siemens Hausgeräte GmbH Übertragung von Dateien in einem lokalen Hausgeräte-Netzwerk
US9348548B2 (en) 2013-11-01 2016-05-24 Seiko Epson Corporation Print control system
US9542133B2 (en) 2013-11-01 2017-01-10 Seiko Epson Corporation Print control system and print control method
US9804809B2 (en) 2013-11-01 2017-10-31 Seiko Epson Corporation Print control system
US10091388B2 (en) 2013-11-01 2018-10-02 Seiko Epson Corporation Print control system and print control method

Also Published As

Publication number Publication date
EP0964558A1 (fr) 1999-12-15
HUP0103875A2 (hu) 2002-03-28
CN1367968A (zh) 2002-09-04
EP1142206A2 (fr) 2001-10-10
HUP0103875A3 (en) 2004-03-29
JP4404483B2 (ja) 2010-01-27
KR20010052655A (ko) 2001-06-25
ES2251197T3 (es) 2006-04-16
EP1142206B1 (fr) 2005-10-26
US9736003B1 (en) 2017-08-15
JP2002518885A (ja) 2002-06-25
MY130201A (en) 2007-06-29
HU227780B1 (en) 2012-02-28
WO1999065188A3 (fr) 2001-07-12
KR100640091B1 (ko) 2006-10-31
DE69928009T2 (de) 2006-07-27
AU4510099A (en) 1999-12-30
DE69928009D1 (de) 2005-12-01

Similar Documents

Publication Publication Date Title
EP1142206B1 (fr) Procede de communication dans un reseau familial, reseau et dispositif permettant de mettre en oeuvre ledit procede
US7171475B2 (en) Peer networking host framework and hosting API
US6275865B1 (en) Method and system for message dispatching in a home audio/video network
US6925518B2 (en) Bridging system for interoperation of remote groups of devices
US20030200340A1 (en) Method for generating a user interface on a HAVi device for the control of a Non-HAVi device
WO2001076146A1 (fr) Acces a un reseau familial par internet
EP1046259A2 (fr) Procede et systeme relatifs a un reseau audio-video
KR100740196B1 (ko) 가정용 네트워크에서 비동기성 데이터를 송신하기 위한 방법
EP1166498A2 (fr) Procede et systeme d&#39;acheminement
WO2001063413A2 (fr) Systeme et procede de communication
MXPA00012219A (en) Communication method in a home network, network and device for implementing such a method
EP1355136B1 (fr) Procédé de géneration d&#39;une interface utilisateur graphique sur un dispositif HAVi pour commander un dispositif non-HAVi
MXPA00012214A (en) Method for transmitting asynchronous data in a home network

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 99807115.3

Country of ref document: CN

AK Designated states

Kind code of ref document: A2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 1999927920

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020007013890

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: PA/a/2000/012219

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 09719147

Country of ref document: US

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWP Wipo information: published in national office

Ref document number: 1020007013890

Country of ref document: KR

AK Designated states

Kind code of ref document: A3

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

WWP Wipo information: published in national office

Ref document number: 1999927920

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: CA

WWG Wipo information: grant in national office

Ref document number: 1999927920

Country of ref document: EP

WWG Wipo information: grant in national office

Ref document number: 1020007013890

Country of ref document: KR

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载