US20090092109A1 - Method and Apparatus for Enabling Discovery Within a Home Network - Google Patents
Method and Apparatus for Enabling Discovery Within a Home Network Download PDFInfo
- Publication number
- US20090092109A1 US20090092109A1 US12/097,625 US9762508A US2009092109A1 US 20090092109 A1 US20090092109 A1 US 20090092109A1 US 9762508 A US9762508 A US 9762508A US 2009092109 A1 US2009092109 A1 US 2009092109A1
- Authority
- US
- United States
- Prior art keywords
- ims
- home
- gateway
- upnp
- enabled
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1023—Media gateways
- H04L65/1026—Media gateways at the edge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1033—Signalling gateways
- H04L65/1036—Signalling gateways at the edge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- 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
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
Definitions
- the present invention relates to a method and apparatus for enabling discovery within a home network, and in particular to enabling the discovery of a Home IP Multimedia Subsystem Gateway by a non-IP Multimedia Subsystem enabled device.
- IP Multimedia (IPMM) services provide a dynamic combination of voice, video, messaging, data, etc. within the same session.
- IPMM IP Multimedia
- IMS IP Multimedia Subsystem
- 3GPP Third Generation Partnership Project
- 3GPP TS 23.228 and TS 24.229 Release 5 and Release 6 IP Multimedia Subsystem
- IMS provides key features to enrich the end-user person-to-person communication experience through the integration and interaction of services.
- IMS allows new rich person-to-person (client-to-client) as well as person-to-content (client-to-server) communications over an IP-based network.
- the IMS makes use of the Session Initiation Protocol (SIP) to set up and control calls or sessions between user terminals (or user terminals and web servers).
- SDP Session Description Protocol
- SIP Session Description Protocol
- Other protocols are used for media transmission and control, such as Real-time Transport Protocol and Real-time Transport Control Protocol (RTP/RTCP), Message Session Relay Protocol (MSRP), Hyper Text Transfer Protocol (HTTP).
- IMS requires an access network which would typically be a 2G/3G General Packet Radio Service (GPRS)/Packet Switched (PS) network, but which might be some other access network such as fixed broadband or WiFi.
- GPRS General Packet Radio Service
- PS Packet Switched
- IMS IMS Residential Gateway
- Non-IMS but SIP enabled terminals are SIP telephones and PCs
- legacy telephones including DECT telephones and IP devices with UPnP (Universal Plug and Play) support
- STBs Set top boxes
- the IRG will include a SIP gateway in order to handle interoperability issues (e.g. conversion between SIP and other signalling protocols required by user equipment).
- interoperability issues e.g. conversion between SIP and other signalling protocols required by user equipment.
- alternatives to the TISPAN IRG proposal may well emerge in the future.
- a plain IP device on a home network that is not IMS enabled cannot automatically discover the IRG or the functions of the IRG.
- the IRG provides means for translating between IMS protocols and protocols used by the non-IMS enabled device, it is therefore difficult for non-IMS enabled devices to access remote networks having, for example, IMS services. For example, it is not possible to initiate an outgoing IMS call from a non-IMS enabled IP device if the non-IMS enabled device cannot discover the IRG, as the non-IMS enabled device is not aware of the availability of the remote network.
- a method of automating the process for a non-IMS enabled device to detect the availability of a Home IMS Gateway comprising:
- a service or a device on said remote network is a Session Initiation Protocol service or device.
- a service or a device on said remote network is an IMS service or device.
- UPF Universal Plug and Play
- DHCP Dynamic Host Configuration Protocol
- the method further comprises sending said advertisement message periodically over a Local Area Network.
- the method may further comprise:
- the database is disposed at the Home IMS Gateway.
- the method further comprises the step of registering the advertisement message at the or each non-IMS device.
- an IMS Service Gateway comprising:
- a method for alerting a non-IP Multimedia Subsystem device to the availability of an IMS network comprising:
- FIG. 1 illustrates schematically a Home IMS Gateway comprising an IMS Service Gateway within a home network
- FIG. 2 illustrates services and actions of an IMS Service Gateway device
- FIG. 3 illustrates signalling to establish a call session using an IMS Service Gateway device.
- a Home IMS Gateway (HIGA) 101 comprising an IMS Service Gateway (ISG) 102 both within a Local Area Network (LAN).
- the HIGA 101 functions as an IRG, in addition to providing other functions.
- the HIGA 101 is disposed on a control plane in the LAN.
- Non-IMS devices 103 , 104 are also connected to the LAN. These devices are plain IP or SIP devices, such as a PC or a STB, and so cannot by themselves establish media connections with remote SIP or IMS clients.
- These non-IMS enabled devices are UPnP devices.
- the HIGA 101 contains a range of functions to assist inter-working between IMS and non-IMS enabled devices 103 , 104 on the LAN.
- the HIGA 101 may be implemented in a separate physical box or integrated in any other box in the home, e.g. the Residential Gateway (RGW) 105 or a STB.
- the ISG 102 is also part of the HIGA 101 and is preferably implemented in the same physical box as the HIGA 101 .
- the ISG 102 uses the UPnP protocol to communicate with other devices on the LAN.
- the HIGA also contains an IMS Address Book (IAB) 106 to facilitate communication between non-IMS enabled devices on the LAN and remote IMS services.
- IAB IMS Address Book
- the UPnP ISG device 102 advertises its presence on the LAN by sending a discovery advertisement message: Device available—NOTIFY with ssdp:alive.
- the message is sent as a multicast over User Datagram Protocol (UDP) to a standard address and port. Control points within the devices on the LAN listen to this port to detect when new capabilities are available on the LAN. To advertise the full extent of its capabilities, the ISG device 102 multicasts a number of discovery messages corresponding to the services available.
- the UPnP ISG advertises the remote SIP and IMS services and this is registered by the UPnP Control Points of the LAN devices 103 , 104 .
- the UPnP description for the ISG device 102 is partitioned into two parts; the device description describes properties of the HIGA, while the service description describes the services available via the HIGA.
- the device description lists basic properties of the HIGA as well as all services it supports.
- the UPnP ISG device 102 is a logical entity that advertises a set of communication services to non-IMS enabled UPnP devices 103 , 104 on the LAN.
- the UPnP ISG device 102 introduces the IMS and SIP services. Each of these services allows non-IMS enabled UPnP devices to establish media connections with remote SIP or IMS clients by invoking the relevant UPnP actions in the ISG 102 .
- FIG. 2 herein there are illustrated services and actions advertised by an IMS Service Gateway device. These are provided by way of example, and it will be appreciated that other actions are possible.
- the call action 201 enables a non-IMS enabled device on the LAN to establish a conference call with a remote IMS client.
- the call may be voice, video or both depending on the functionalities of the RTP client of the non-IMS enabled device.
- the Call action has the following syntax:
- Parameters these represent parameters that are provided by the RTP client such as the codec, format etc. These are preference values passed by the client application. This field is optional.
- the hang up action 202 is invoked by the UPnP Control Point of a non-IMS enabled UPnP device on the LAN to end an ongoing media session.
- the hang up action has the following syntax:
- Session_ID A string variable containing a unique identifier of a connection established between the HIGA and the remote client.
- the access content action 203 enables a non-IMS enabled UPnP device on the LAN to access multimedia content stored in the remote IMS system.
- the access content action has the following syntax:
- Server the SIP URI or IMS public identity of the server where the content is located.
- Parameters these represent optional parameters that may be provided by the RTP client such as the codec, format etc.
- IAB IMS address book
- FIG. 1 An IMS address book (IAB) 106 function, shown in FIG. 1 as part of the HIGA 101 , stores all outgoing and incoming IMS Public Identities.
- the IAB can be common to all users of the LAN or separate users of the LAN may have their own IAB for increased privacy. This function facilitates simplified IMS service activation from non-IMS enabled UPnP devices 103 , 104 on the LAN.
- the UPnP Control Point of the non-IMS enabled UPnP device 103 on the LAN invokes the GetAddrBk action 204 specifying the user's name.
- the HIGA 101 returns a list of SIP URIs and their respective display names as stored in the IAB 106 .
- the user is able to select a desired contact URI and invokes the Call action of the IMS or SIP service of the UPnP ISG device 102 . This effectively provides a “speed dial” type of functionality. Alternatively the user would have to input the SIP URI into the home device when making a call.
- the HIGA 101 also stores the SDP of each device on the home network, hence the SDP is the default information used for session negotiation.
- the GetAddrBk action 204 has the following syntax:
- User_name Identity of user that sends the request (this parameter is optional).
- UPnP existing UPnP architecture assumes that media is transported via HTTP, IEEE 1394 or the RTSP protocol.
- the RTSP protocol supports RTP, which is the protocol used to transport media between IMS clients and hence is of interest.
- RTP the protocol used to transport media between IMS clients and hence is of interest.
- the handshake is exchanged within the RTSP SETUP and OK messages.
- a new UPnP action is deemed necessary.
- the new UPnP action is included in the AVTransport service. This method returns the IP address of the non-IMS enabled UPnP device on the LAN and the UDP port on which the non-IMS enabled UPnP devices on the LAN is ready to receive RTP media.
- the syntax of the action is as follows:
- IP port Set_com_transport(IP′, port′, ID)
- IP IP address of the non-IMS enabled UPnP device on the LAN
- IP′ IP address of the remote IMS device
- Port Port number on which the non-IMS enabled UPnP device on the LAN is ready to receive
- RTP Port′ Port number on which the remote IMS device is ready to receive
- RTP ID unique identifier of the session which is assigned by the HIGA
- this action can be implemented within a new UPnP service.
- This approach reflects the changes that can be made on the UPnP Media Renderer side and is depicted as a dotted box 107 in the non-IMS enabled UPnP IP device in FIG. 1 .
- RTP/UDP is used as an example of transport protocol throughout this description.
- the IMS and SIP services of the UPnP ISG device offer communication services to non-IMS enabled UPnP devices via the call action of the ISG device.
- the non-IMS enabled UPnP device is running a UPnP Media Renderer device, which relies on an underlying RTP stack to render RTP media.
- An alternative embodiment is a non-IMS enabled UPnP device running a RTP application that is exposed to UPnP network via a UPnP bridge.
- the establishment of a call between a non-IMS enabled UPnP device and a remote IMS device entails the negotiation of media codecs, UDP ports for RTP and the opening of these ports in the RGW.
- the HIGA terminates the SIP signalling originating from the remote IMS terminal and performs all negotiations with the non-IMS enabled UPnP device via UPnP.
- the media port in the non-IMS enabled UPnP device may or may not be of a predefined value. If the media port is predefined, this value is stored in a device database 109 in HIGA 101 . Alternatively, the media ports are dynamic in nature and are allocated for a given connection during the connection establishment.
- FIG. 3 there is illustrated the signalling to establish a call session using an IMS Service Gateway device.
- the signalling illustrated is by way of example only, as different signalling may be used to establish a call session.
- a precondition 301 for the access to IMS services by a non-IMS enabled UPnP device is that the non-IMS enabled UPnP device is registered to the HIGA and the HIGA is itself registered to the IMS core.
- the UPnP Control Point of the non-IMS enabled UPnP device invokes the Call action with the SIP URI as the first parameter.
- the GetAddrBk action may have been invoked to get the list of SIP URI.
- the second parameter of the Call action allows specification of connection parameters of the session such as the codec, media formats etc. If these are not specified, the HIGA uses the session definition parameters as defined by the SDP of the device stored in the device database.
- the Call action initiates 302 the selection and reservation of a port on the WAN interface of the RGW through the UPnP IGD.
- the selection of a free port number is achieved by invoking the GetGenericPortMappings action with an incrementing array index until no more entries are found on the UPnP IGD, hence a list of all current NAT bindings is returned.
- the HIGA logic is then able to select a free port based on this list.
- a preliminary port binding is made in the RGW.
- This NAT binding is redefined and is made at this stage with the aim of reserving the selected port number.
- the port number is used along with the external IP address of the RGW in the SDP body of the INVITE message as the media port for the respective RTP stream.
- the INVITE message 303 passes via several nodes of the IMS core, and is received by the remote IMS device of the callee.
- the OK message 304 contains the SDP which includes the IP address of the terminal and the UDP port for incoming RTP streams.
- the SDP of the OK message is parsed and the IP address and port are extracted.
- the HIGA CP invokes the proposed Set_com_transport( ) action in the Media Renderer device which informs the RTP stack of port number and IP address of incoming RTP media. The action returns the port number opened by the RTP stack of the Media Renderer device.
- the HIGA then creates a NAT binding using the earlier selected port in the RGW for RTP media using the Addportmapping action 305 based on the following information: the IP address of the IMS terminal, the external port of the RGW for incoming RTP, the IP address of the calling home device and its port number.
- the ACK message sent in has a different port value and hence causes a re-negotiation of connection between the HIGA and the remote IMS device.
- the call establishment procedure is successful up to the point of Addportmapping 305 , the HIGA sends an ACK message to the IMS terminal and from this point the caller and callee may start exchanging RTP traffic.
- the Access_content action differs from the call action in that the SIP URI of a server is specified and most likely the RTP flow is uni-directional, from the server to the home device.
- the non-IMS enabled UPnP device uses the Hang_up action function 306 of the IMS service to end the media session.
- the parameter of the action is the SIP URI of the callee and the session ID.
- a SIP BYE message is sent to the remote IMS device informing it of the session end.
- the NAT binding is also removed in the IGD by invoking the DeletePortMapping 307 .
- UPnP enabled SIP and IP devices on the home LAN automatically receive information on the presence and capabilities of a home IMS gateway. This information can be used to initiate IMS calls or services from non-IMS devices within the home network.
- IMS Address Book One of the supporting capabilities of HIGA is the IMS Address Book, which can be used by home devices to facilitate easier access to IMS services.
- the ISG is described as being implemented with the HIGA, although it is possible to dispose an ISG at other points in the LAN and not necessarily with the HIGA.
Abstract
A method and Home IP Multimedia Subsystem (IMS) Gateway for enabling a non-IMS enabled device within a home network to discover the availability of the Home IMS Gateway. The Home IMS Gateway is interposed at a control plane between a remote network and the non-IMS enabled device. The Home IMS Gateway sends an advertisement message to the non-IMS enabled device advertising the availability of services on the remote network via the Home IMS Gateway.
Description
- The present invention relates to a method and apparatus for enabling discovery within a home network, and in particular to enabling the discovery of a Home IP Multimedia Subsystem Gateway by a non-IP Multimedia Subsystem enabled device.
- IP Multimedia (IPMM) services provide a dynamic combination of voice, video, messaging, data, etc. within the same session. By growing the numbers of basic applications and the media that it is possible to combine, the number of services offered to the end users will grow, and the inter-personal communication experience will be enriched. This will lead to a new generation of personalised, rich multimedia communication services, including so-called “combinational IP Multimedia” services, which are considered in more detail below.
- IP Multimedia Subsystem (IMS) is the technology defined by the Third Generation Partnership Project (3GPP) to provide IP Multimedia services over 3G mobile communication networks (3GPP TS 23.228 and TS 24.229
Release 5 and Release 6). IMS provides key features to enrich the end-user person-to-person communication experience through the integration and interaction of services. IMS allows new rich person-to-person (client-to-client) as well as person-to-content (client-to-server) communications over an IP-based network. The IMS makes use of the Session Initiation Protocol (SIP) to set up and control calls or sessions between user terminals (or user terminals and web servers). The Session Description Protocol (SDP), carried by SIP signalling, is used to describe and negotiate the media components of the session. Other protocols are used for media transmission and control, such as Real-time Transport Protocol and Real-time Transport Control Protocol (RTP/RTCP), Message Session Relay Protocol (MSRP), Hyper Text Transfer Protocol (HTTP). - IMS requires an access network which would typically be a 2G/3G General Packet Radio Service (GPRS)/Packet Switched (PS) network, but which might be some other access network such as fixed broadband or WiFi.
- The TISPAN working group of the European Telecommunications Standards Institute (ETSI) is currently working on a proposal for the Next Generation Network (NGN) for fixed networks based upon IMS. As part of this project, consideration will be given to a so-called IMS Residential Gateway (IRG), which will allow non-IMS terminals to access IMS services. It is expected that the IRG will find applications in the home and small office environments where users might wish to access IMS services using a number of non-IMS enabled terminals, which may or may not be SIP terminals. Examples of non-IMS but SIP enabled terminals are SIP telephones and PCs, whilst examples of non-IMS terminals that do not have SIP functionality are legacy telephones including DECT telephones and IP devices with UPnP (Universal Plug and Play) support such as STBs (Set top boxes). The IRG will include a SIP gateway in order to handle interoperability issues (e.g. conversion between SIP and other signalling protocols required by user equipment). Of course, alternatives to the TISPAN IRG proposal may well emerge in the future.
- At present, a plain IP device on a home network that is not IMS enabled cannot automatically discover the IRG or the functions of the IRG. As the IRG provides means for translating between IMS protocols and protocols used by the non-IMS enabled device, it is therefore difficult for non-IMS enabled devices to access remote networks having, for example, IMS services. For example, it is not possible to initiate an outgoing IMS call from a non-IMS enabled IP device if the non-IMS enabled device cannot discover the IRG, as the non-IMS enabled device is not aware of the availability of the remote network.
- According to a first aspect of the present invention there is provided a method of automating the process for a non-IMS enabled device to detect the availability of a Home IMS Gateway, the method comprising:
-
- interposing a Home IMS Gateway at a control plane between a remote network and one or more non-IMS enabled devices;
- sending an advertisement message to the or each non-IMS enabled device, said advertisement message advertising the availability via the Home IMS Gateway of services on the remote network.
- Preferably, a service or a device on said remote network is a Session Initiation Protocol service or device.
- It is preferred that a service or a device on said remote network is an IMS service or device.
- A common standard for interoperability in home networks is Universal Plug and Play (UPnP). The UPnP standard is based on all devices on a home LAN being connected to the same IP sub-net, and so all devices have IP capability and receive local IP addresses from the Dynamic Host Configuration Protocol (DHCP) server in the residential gateway. For this reason, it is preferred that the advertisement message uses Universal Plug and Play protocol.
- Preferably, the method further comprises sending said advertisement message periodically over a Local Area Network.
- The method may further comprise:
-
- storing at least one address at a database on a Local Area Network, said address corresponding to a Uniform Resource Identifier identifying an IMS device or service;
- sending said address to said non-IMS enabled device.
- Preferably, the database is disposed at the Home IMS Gateway.
- In a specific embodiment, the method further comprises the step of registering the advertisement message at the or each non-IMS device.
- According to a second aspect, there is provided an IMS Service Gateway comprising:
-
- a first interface for communicating with a remote network;
- a second interface for communicating with a non-IMS enabled device;
- means for sending an advertisement message to the non-IMS enabled device, the advertisement message advertising the availability via a Home IMS Gateway of services on the remote network.
- According to a third aspect, there is provided a method for alerting a non-IP Multimedia Subsystem device to the availability of an IMS network, the method comprising:
-
- providing means to automatically advertise to the non-IMS device the availability of devices or services via a Home IMS Gateway on the IP Multimedia Subsystem network.
-
FIG. 1 illustrates schematically a Home IMS Gateway comprising an IMS Service Gateway within a home network; -
FIG. 2 illustrates services and actions of an IMS Service Gateway device; and -
FIG. 3 illustrates signalling to establish a call session using an IMS Service Gateway device. - Referring to
FIG. 1 herein, there is illustrated schematically a Home IMS Gateway (HIGA) 101 comprising an IMS Service Gateway (ISG) 102 both within a Local Area Network (LAN). The HIGA 101 functions as an IRG, in addition to providing other functions. The HIGA 101 is disposed on a control plane in the LAN.Non-IMS devices - The HIGA 101 contains a range of functions to assist inter-working between IMS and non-IMS enabled
devices - The UPnP
ISG device 102 advertises its presence on the LAN by sending a discovery advertisement message: Device available—NOTIFY with ssdp:alive. The message is sent as a multicast over User Datagram Protocol (UDP) to a standard address and port. Control points within the devices on the LAN listen to this port to detect when new capabilities are available on the LAN. To advertise the full extent of its capabilities, theISG device 102 multicasts a number of discovery messages corresponding to the services available. The UPnP ISG advertises the remote SIP and IMS services and this is registered by the UPnP Control Points of theLAN devices - The UPnP description for the
ISG device 102 is partitioned into two parts; the device description describes properties of the HIGA, while the service description describes the services available via the HIGA. The device description lists basic properties of the HIGA as well as all services it supports. - The
UPnP ISG device 102 is a logical entity that advertises a set of communication services to non-IMS enabledUPnP devices UPnP ISG device 102 introduces the IMS and SIP services. Each of these services allows non-IMS enabled UPnP devices to establish media connections with remote SIP or IMS clients by invoking the relevant UPnP actions in theISG 102. Referring toFIG. 2 herein, there are illustrated services and actions advertised by an IMS Service Gateway device. These are provided by way of example, and it will be appreciated that other actions are possible. - The
call action 201 enables a non-IMS enabled device on the LAN to establish a conference call with a remote IMS client. The call may be voice, video or both depending on the functionalities of the RTP client of the non-IMS enabled device. The Call action has the following syntax: -
Call([contact] [parameters]) - Contact: SIP address or IMS Public Identity in form of a SIP URI of the callee.
Parameters: these represent parameters that are provided by the RTP client such as the codec, format etc. These are preference values passed by the client application. This field is optional. - The hang up
action 202 is invoked by the UPnP Control Point of a non-IMS enabled UPnP device on the LAN to end an ongoing media session. The hang up action has the following syntax: -
Hang_up(contact, session_ID) - Contact: the SIP URI or IMS public identity of the callee.
Session_ID: A string variable containing a unique identifier of a connection established between the HIGA and the remote client. - The
access content action 203 enables a non-IMS enabled UPnP device on the LAN to access multimedia content stored in the remote IMS system. The access content action has the following syntax: -
Access_Content([server],[parameters]) - Server: the SIP URI or IMS public identity of the server where the content is located.
Parameters: these represent optional parameters that may be provided by the RTP client such as the codec, format etc. - An IMS address book (IAB) 106 function, shown in
FIG. 1 as part of theHIGA 101, stores all outgoing and incoming IMS Public Identities. The IAB can be common to all users of the LAN or separate users of the LAN may have their own IAB for increased privacy. This function facilitates simplified IMS service activation from non-IMS enabledUPnP devices - To establish a video or audio session with a remote client connected to the IMS system, the UPnP Control Point of the non-IMS enabled
UPnP device 103 on the LAN invokes theGetAddrBk action 204 specifying the user's name. TheHIGA 101 returns a list of SIP URIs and their respective display names as stored in theIAB 106. The user is able to select a desired contact URI and invokes the Call action of the IMS or SIP service of theUPnP ISG device 102. This effectively provides a “speed dial” type of functionality. Alternatively the user would have to input the SIP URI into the home device when making a call. TheHIGA 101 also stores the SDP of each device on the home network, hence the SDP is the default information used for session negotiation. - The
GetAddrBk action 204 has the following syntax: -
GetAddrBk([user_name]) - User_name: Identity of user that sends the request (this parameter is optional).
- Existing UPnP architecture assumes that media is transported via HTTP, IEEE 1394 or the RTSP protocol. The RTSP protocol supports RTP, which is the protocol used to transport media between IMS clients and hence is of interest. Using RTSP, the UDP port numbers of the source and sink RTP applications for a given media session are made known to the opposite parties by RTSP. The handshake is exchanged within the RTSP SETUP and OK messages. To be able to explicitly exchange the UDP port numbers allocated for a given media session between a UPnP Media Renderer in a device on the LAN and a remote IMS device, a new UPnP action is deemed necessary. The new UPnP action is included in the AVTransport service. This method returns the IP address of the non-IMS enabled UPnP device on the LAN and the UDP port on which the non-IMS enabled UPnP devices on the LAN is ready to receive RTP media. The syntax of the action is as follows:
-
IP,port Set_com_transport(IP′, port′, ID) - IP: IP address of the non-IMS enabled UPnP device on the LAN
IP′: IP address of the remote IMS device
Port: Port number on which the non-IMS enabled UPnP device on the LAN is ready to receive RTP
Port′: Port number on which the remote IMS device is ready to receive RTP
ID: unique identifier of the session which is assigned by the HIGA - Alternatively, this action can be implemented within a new UPnP service. This approach reflects the changes that can be made on the UPnP Media Renderer side and is depicted as a
dotted box 107 in the non-IMS enabled UPnP IP device inFIG. 1 . - RTP/UDP is used as an example of transport protocol throughout this description.
- Combined, the IMS and SIP services of the UPnP ISG device offer communication services to non-IMS enabled UPnP devices via the call action of the ISG device. The non-IMS enabled UPnP device is running a UPnP Media Renderer device, which relies on an underlying RTP stack to render RTP media. An alternative embodiment is a non-IMS enabled UPnP device running a RTP application that is exposed to UPnP network via a UPnP bridge.
- The establishment of a call between a non-IMS enabled UPnP device and a remote IMS device entails the negotiation of media codecs, UDP ports for RTP and the opening of these ports in the RGW. The HIGA terminates the SIP signalling originating from the remote IMS terminal and performs all negotiations with the non-IMS enabled UPnP device via UPnP. The media port in the non-IMS enabled UPnP device may or may not be of a predefined value. If the media port is predefined, this value is stored in a
device database 109 inHIGA 101. Alternatively, the media ports are dynamic in nature and are allocated for a given connection during the connection establishment. For this reason it is deemed necessary to introduce a new action into the AVTransport service of the UPnP Media Renderer device, as described above for a modified media renderer. This action informs the Media Renderer device of the IP and port number of the originating RTP media. The device responds indicating the number of the UDP port which was opened for the connection. Alternatively, a new service can be defined for the UPnP Media Renderer device, which addresses all two-way RTP communication issues for Media Renderer devices. - Referring to
FIG. 3 herein, there is illustrated the signalling to establish a call session using an IMS Service Gateway device. The signalling illustrated is by way of example only, as different signalling may be used to establish a call session. - A
precondition 301 for the access to IMS services by a non-IMS enabled UPnP device is that the non-IMS enabled UPnP device is registered to the HIGA and the HIGA is itself registered to the IMS core. To establish a video or audio session with a remote IMS device, the UPnP Control Point of the non-IMS enabled UPnP device invokes the Call action with the SIP URI as the first parameter. Prior to this the GetAddrBk action may have been invoked to get the list of SIP URI. The second parameter of the Call action allows specification of connection parameters of the session such as the codec, media formats etc. If these are not specified, the HIGA uses the session definition parameters as defined by the SDP of the device stored in the device database. - The Call action initiates 302 the selection and reservation of a port on the WAN interface of the RGW through the UPnP IGD. The selection of a free port number is achieved by invoking the GetGenericPortMappings action with an incrementing array index until no more entries are found on the UPnP IGD, hence a list of all current NAT bindings is returned. The HIGA logic is then able to select a free port based on this list. After this a preliminary port binding is made in the RGW. This NAT binding is redefined and is made at this stage with the aim of reserving the selected port number. The port number is used along with the external IP address of the RGW in the SDP body of the INVITE message as the media port for the respective RTP stream.
- The
INVITE message 303 passes via several nodes of the IMS core, and is received by the remote IMS device of the callee. TheOK message 304 contains the SDP which includes the IP address of the terminal and the UDP port for incoming RTP streams. On reaching the HIGA device, the SDP of the OK message is parsed and the IP address and port are extracted. The HIGA CP invokes the proposed Set_com_transport( ) action in the Media Renderer device which informs the RTP stack of port number and IP address of incoming RTP media. The action returns the port number opened by the RTP stack of the Media Renderer device. The HIGA then creates a NAT binding using the earlier selected port in the RGW for RTP media using theAddportmapping action 305 based on the following information: the IP address of the IMS terminal, the external port of the RGW for incoming RTP, the IP address of the calling home device and its port number. - In the event of a problem opening ports in the RGW, the ACK message sent in has a different port value and hence causes a re-negotiation of connection between the HIGA and the remote IMS device. The call establishment procedure is successful up to the point of
Addportmapping 305, the HIGA sends an ACK message to the IMS terminal and from this point the caller and callee may start exchanging RTP traffic. - The Access_content action differs from the call action in that the SIP URI of a server is specified and most likely the RTP flow is uni-directional, from the server to the home device.
- To terminate the call, the non-IMS enabled UPnP device uses the
Hang_up action function 306 of the IMS service to end the media session. The parameter of the action is the SIP URI of the callee and the session ID. When the ISG device receives a Hang_up message a SIP BYE message is sent to the remote IMS device informing it of the session end. The NAT binding is also removed in the IGD by invoking theDeletePortMapping 307. - UPnP enabled SIP and IP devices on the home LAN automatically receive information on the presence and capabilities of a home IMS gateway. This information can be used to initiate IMS calls or services from non-IMS devices within the home network. One of the supporting capabilities of HIGA is the IMS Address Book, which can be used by home devices to facilitate easier access to IMS services.
- It will be apparent to one skilled in the art that various modifications may be made to the embodiments described above without departing from the scope of the present invention. For example, the ISG is described as being implemented with the HIGA, although it is possible to dispose an ISG at other points in the LAN and not necessarily with the HIGA.
Claims (10)
1. A method of enabling a device that is not IP Multimedia Subsystem (IMS) enabled to detect the availability of a Home IMS Gateway, the method comprising the steps of:
interposing a Home IMS Gateway at a control plane between a remote network and the non-IMS enabled device; and
sending an advertisement message to the non-IMS enabled device, said advertisement message advertising the availability via the Home IMS Gateway of services on the remote network.
2. The method according to claim 1 wherein a service on said remote network is a Session Initiation Protocol service.
3. The method according to claim 1 wherein a service on said remote network is an IMS service.
4. The method according to claim 1 wherein said advertisement message uses Universal Plug and Play protocol.
5. The method according to claim 1 , wherein the step of sending the advertising message includes sending said advertisement message periodically over a Local Area Network.
6. The method according to claim 1 further comprising the steps of:
storing at least one address at a database on a Local Area Network, said address corresponding to a Uniform Resource Identifier identifying an IMS device or service; and
sending said address to said non-IMS enabled device.
7. The method according to claim 6 wherein the database is disposed at the Home IMS Gateway.
8. The method according to claim 1 further comprising the step of registering the advertisement message at the non-IMS enabled device.
9. A Home IP Multimedia Subsystem (IMS) Gateway comprising:
a first interface for communicating with a remote network;
a second interface for communicating with a non-IMS enabled device; and
means for sending an advertisement message to the non-IMS enabled device, the advertisement message advertising the availability via the Home IMS Gateway of services on the remote network.
10. A method for alerting a device that is not IP Multimedia Subsystem (IMS) enabled to the availability of an IMS network, the method comprising:
automatically advertising to the non-IMS device, the availability of devices or services via a Home IMS Gateway on the IMS network.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2005/056922 WO2007071282A1 (en) | 2005-12-19 | 2005-12-19 | Method and apparatus for enabling discovery within a home network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090092109A1 true US20090092109A1 (en) | 2009-04-09 |
Family
ID=36814569
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/097,625 Abandoned US20090092109A1 (en) | 2005-12-19 | 2005-12-19 | Method and Apparatus for Enabling Discovery Within a Home Network |
US12/097,583 Active 2028-09-06 US8289980B2 (en) | 2005-12-19 | 2006-09-05 | Method for establishing a unicast media session |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/097,583 Active 2028-09-06 US8289980B2 (en) | 2005-12-19 | 2006-09-05 | Method for establishing a unicast media session |
Country Status (4)
Country | Link |
---|---|
US (2) | US20090092109A1 (en) |
EP (1) | EP1964351A1 (en) |
CN (3) | CN101361342A (en) |
WO (2) | WO2007071282A1 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080159313A1 (en) * | 2006-12-28 | 2008-07-03 | Nokia Corporation | Interworking policy and charging control and network address translator |
US20090086740A1 (en) * | 2007-10-01 | 2009-04-02 | General Instrument Corporation | Customer Premises Gateway providing User Devices with Access to Internet Protocol Multimedia Subsystem (IMS) Services and Non-IMS Services |
US20090175296A1 (en) * | 2008-01-04 | 2009-07-09 | General Instrument Corporation | Extensible System and Method to Bridge SIP and UPnP Devices |
US20100138900A1 (en) * | 2008-12-02 | 2010-06-03 | General Instrument Corporation | Remote access of protected internet protocol (ip)-based content over an ip multimedia subsystem (ims)-based network |
US20100246444A1 (en) * | 2006-08-23 | 2010-09-30 | Andreas Witzel | Method for registering in an ims domain a non-ims user device |
US20110182205A1 (en) * | 2006-12-28 | 2011-07-28 | Martin Gerdes | Method and apparatus for service discovery |
US20120079029A1 (en) * | 2009-06-04 | 2012-03-29 | Telefonaktiebolaget L M Ericsson (Publ) | Method And Arrangement For Obtaining A Media Object For A Device In A Local Network |
USRE44412E1 (en) * | 2005-06-24 | 2013-08-06 | Aylus Networks, Inc. | Digital home networks having a control point located on a wide area network |
US20130300547A1 (en) * | 2011-01-17 | 2013-11-14 | Lg Electronics Inc. | Control apparatus, control target apparatus, and alarm-setting method using the apparatuses |
US9485801B1 (en) * | 2014-04-04 | 2016-11-01 | Sprint Communications Company L.P. | Mobile communication device connected to home digital network |
US10771525B2 (en) * | 2008-11-26 | 2020-09-08 | Free Stream Media Corp. | System and method of discovery and launch associated with a networked media device |
US11784876B1 (en) * | 2023-04-17 | 2023-10-10 | Dell Products L.P. | System and method for managing the operation and remote provisioning of data processing systems |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7965771B2 (en) | 2006-02-27 | 2011-06-21 | Cisco Technology, Inc. | Method and apparatus for immediate display of multicast IPTV over a bandwidth constrained network |
US8218654B2 (en) | 2006-03-08 | 2012-07-10 | Cisco Technology, Inc. | Method for reducing channel change startup delays for multicast digital video streams |
US8031701B2 (en) | 2006-09-11 | 2011-10-04 | Cisco Technology, Inc. | Retransmission-based stream repair and stream join |
US7937531B2 (en) * | 2007-02-01 | 2011-05-03 | Cisco Technology, Inc. | Regularly occurring write back scheme for cache soft error reduction |
US8769591B2 (en) | 2007-02-12 | 2014-07-01 | Cisco Technology, Inc. | Fast channel change on a bandwidth constrained network |
US7940644B2 (en) * | 2007-03-14 | 2011-05-10 | Cisco Technology, Inc. | Unified transmission scheme for media stream redundancy |
US20080253369A1 (en) | 2007-04-16 | 2008-10-16 | Cisco Technology, Inc. | Monitoring and correcting upstream packet loss |
TWI382717B (en) * | 2007-11-12 | 2013-01-11 | D Link Corp | A method of sharing resources by interconnecting a network terminal device of two private networks by a user agent |
EP2061216A1 (en) * | 2007-11-16 | 2009-05-20 | Nederlandse Organisatie voor toegepast-natuurwetenschappelijk Onderzoek TNO | Exchanging control codes between SIP/IMS and UPnP network elements. |
ATE546939T1 (en) | 2007-11-16 | 2012-03-15 | Alcatel Lucent | PROCEDURE FOR CREATING AN IMS SESSION |
US8787153B2 (en) | 2008-02-10 | 2014-07-22 | Cisco Technology, Inc. | Forward error correction based data recovery with path diversity |
WO2009101488A1 (en) * | 2008-02-13 | 2009-08-20 | Nds Limited | Advertisement shifting system |
US20110026510A1 (en) * | 2008-04-21 | 2011-02-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for Enabling Communication between a User Equipment and an IMS Gateway |
GB0808447D0 (en) * | 2008-05-12 | 2008-06-18 | Nortel Networks Ltd | A mechanism to divert an IP flow over a non-IP transport |
US8270417B2 (en) * | 2008-06-04 | 2012-09-18 | Telefonaktiebolaget L M Ericsson (Publ) | Access network node and method for access network node |
US8738389B2 (en) | 2008-06-05 | 2014-05-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Vehicle information communication |
WO2010044731A1 (en) * | 2008-10-13 | 2010-04-22 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and arrangements for an ip tv network |
CN101820409A (en) * | 2009-02-26 | 2010-09-01 | 中兴通讯股份有限公司 | IMS (IP Multimedia Subsystem) service implementation method and service implementation device based on personal network |
EP2356797B1 (en) | 2009-05-18 | 2015-03-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for implementing ims functionality in a set top box |
KR101859235B1 (en) * | 2009-12-15 | 2018-06-28 | 삼성전자주식회사 | System and method of multi-media conferencing between universal plug and play (upnp) enabled telephony devices and wireless area network (wan) devices |
CN101820499B (en) * | 2010-05-18 | 2014-01-01 | 中兴通讯股份有限公司 | Method and system for realizing automatic interaction between STB (set top box) and home gateway |
US8812685B2 (en) | 2010-07-16 | 2014-08-19 | At&T Intellectual Property I, L.P. | Advanced gateway device |
US8838735B2 (en) | 2011-06-28 | 2014-09-16 | At&T Intellectual Property I, L.P. | Methods, systems, and products for address translation in residential networks |
CN102291415B (en) * | 2011-09-08 | 2014-05-14 | 中国联合网络通信集团有限公司 | Media stream processing method and system and home gateway |
CN102946386A (en) * | 2012-10-29 | 2013-02-27 | 中兴通讯股份有限公司 | Whiteboard sharing method and whiteboard sharing system for home network |
WO2014134820A1 (en) * | 2013-03-08 | 2014-09-12 | 华为终端有限公司 | Video communication method, home terminal and home server |
CN111447482A (en) * | 2020-05-13 | 2020-07-24 | 威盛电子股份有限公司 | Synchronous playing method and system for streaming media |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030045290A1 (en) * | 2001-08-21 | 2003-03-06 | Sakari Tuohimetsa | Internet protocol (IP) multimedia subsystem (IMS) availability detection |
US6788676B2 (en) * | 2002-10-30 | 2004-09-07 | Nokia Corporation | User equipment device enabled for SIP signalling to provide multimedia services with QoS |
US20050114491A1 (en) * | 2003-11-25 | 2005-05-26 | Dennis Bushmitch | SIP service for home network device and service mobility |
US20060018272A1 (en) * | 2004-07-20 | 2006-01-26 | Nokia Corporation | Instance identification |
US20060206504A1 (en) * | 2005-03-10 | 2006-09-14 | Lucent Technologies Inc. | IMS network access using legacy devices |
US20060258394A1 (en) * | 2005-05-11 | 2006-11-16 | Dhillon Harry S | Short message service encapsulation of supplementary service requests for IMS |
US20060291488A1 (en) * | 2005-06-24 | 2006-12-28 | Aylus Networks, Inc. | System and method of interworking non-IMS and IMS networks to create new services utilizing both networks |
US20070121608A1 (en) * | 2004-09-30 | 2007-05-31 | Huawei Technologies Co., Ltd | Method and System for Implementing Communications |
US20070195805A1 (en) * | 2004-10-27 | 2007-08-23 | Telefonaktiebolaget Lm Ericsson (Publ) | IP multimedia subsystem access method and apparatus |
US8036211B1 (en) * | 2004-03-09 | 2011-10-11 | Genband Us Llc | Legacy user proxy call session control function |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2000262769A1 (en) | 2000-07-21 | 2002-02-05 | Bertenyi, Balazs | Sip sessions between ipv4 and ipv6 clients and sip based call setup in 3gpp ip multimedia subsystem with nat in place |
EP1597896A2 (en) * | 2003-02-19 | 2005-11-23 | Nokia Corporation | Routing messages via an ims system |
GB2408415B (en) * | 2003-11-19 | 2008-04-09 | Vodafone Plc | Networks |
US7626950B2 (en) * | 2004-08-18 | 2009-12-01 | At&T Intellectual Property, I,L.P. | SIP-based session control among a plurality of multimedia devices |
JP4348271B2 (en) * | 2004-10-05 | 2009-10-21 | パナソニック株式会社 | SIP terminal control system |
CN1604589A (en) * | 2004-10-28 | 2005-04-06 | 无锡三通科技有限公司 | SIP crossing supported firewall implementing method |
CN100391212C (en) * | 2005-01-26 | 2008-05-28 | 清华大学 | Method for realizing interactive multimedia data transmission on internet |
CN100369430C (en) * | 2005-06-21 | 2008-02-13 | 中兴通讯股份有限公司 | A protection method for access security of IP multimedia subsystem |
-
2005
- 2005-12-19 CN CNA2005800523319A patent/CN101361342A/en active Pending
- 2005-12-19 EP EP05826373A patent/EP1964351A1/en not_active Withdrawn
- 2005-12-19 WO PCT/EP2005/056922 patent/WO2007071282A1/en active Application Filing
- 2005-12-19 US US12/097,625 patent/US20090092109A1/en not_active Abandoned
-
2006
- 2006-09-05 CN CN201510137603.0A patent/CN104717315B/en not_active Expired - Fee Related
- 2006-09-05 CN CNA2006800478229A patent/CN101341716A/en active Pending
- 2006-09-05 WO PCT/EP2006/066008 patent/WO2007071461A1/en active Application Filing
- 2006-09-05 US US12/097,583 patent/US8289980B2/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030045290A1 (en) * | 2001-08-21 | 2003-03-06 | Sakari Tuohimetsa | Internet protocol (IP) multimedia subsystem (IMS) availability detection |
US6788676B2 (en) * | 2002-10-30 | 2004-09-07 | Nokia Corporation | User equipment device enabled for SIP signalling to provide multimedia services with QoS |
US20050114491A1 (en) * | 2003-11-25 | 2005-05-26 | Dennis Bushmitch | SIP service for home network device and service mobility |
US8036211B1 (en) * | 2004-03-09 | 2011-10-11 | Genband Us Llc | Legacy user proxy call session control function |
US20060018272A1 (en) * | 2004-07-20 | 2006-01-26 | Nokia Corporation | Instance identification |
US20070121608A1 (en) * | 2004-09-30 | 2007-05-31 | Huawei Technologies Co., Ltd | Method and System for Implementing Communications |
US20070195805A1 (en) * | 2004-10-27 | 2007-08-23 | Telefonaktiebolaget Lm Ericsson (Publ) | IP multimedia subsystem access method and apparatus |
US20060206504A1 (en) * | 2005-03-10 | 2006-09-14 | Lucent Technologies Inc. | IMS network access using legacy devices |
US20060258394A1 (en) * | 2005-05-11 | 2006-11-16 | Dhillon Harry S | Short message service encapsulation of supplementary service requests for IMS |
US20060291488A1 (en) * | 2005-06-24 | 2006-12-28 | Aylus Networks, Inc. | System and method of interworking non-IMS and IMS networks to create new services utilizing both networks |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USRE44412E1 (en) * | 2005-06-24 | 2013-08-06 | Aylus Networks, Inc. | Digital home networks having a control point located on a wide area network |
US20100246444A1 (en) * | 2006-08-23 | 2010-09-30 | Andreas Witzel | Method for registering in an ims domain a non-ims user device |
US20080159313A1 (en) * | 2006-12-28 | 2008-07-03 | Nokia Corporation | Interworking policy and charging control and network address translator |
US20110182205A1 (en) * | 2006-12-28 | 2011-07-28 | Martin Gerdes | Method and apparatus for service discovery |
US20090086740A1 (en) * | 2007-10-01 | 2009-04-02 | General Instrument Corporation | Customer Premises Gateway providing User Devices with Access to Internet Protocol Multimedia Subsystem (IMS) Services and Non-IMS Services |
US8873570B2 (en) * | 2008-01-04 | 2014-10-28 | Motorola Mobility Llc | Extensible system and method to bridge SIP and UPnP devices |
US20090175296A1 (en) * | 2008-01-04 | 2009-07-09 | General Instrument Corporation | Extensible System and Method to Bridge SIP and UPnP Devices |
US10771525B2 (en) * | 2008-11-26 | 2020-09-08 | Free Stream Media Corp. | System and method of discovery and launch associated with a networked media device |
US20100138900A1 (en) * | 2008-12-02 | 2010-06-03 | General Instrument Corporation | Remote access of protected internet protocol (ip)-based content over an ip multimedia subsystem (ims)-based network |
US20120079029A1 (en) * | 2009-06-04 | 2012-03-29 | Telefonaktiebolaget L M Ericsson (Publ) | Method And Arrangement For Obtaining A Media Object For A Device In A Local Network |
US20130300547A1 (en) * | 2011-01-17 | 2013-11-14 | Lg Electronics Inc. | Control apparatus, control target apparatus, and alarm-setting method using the apparatuses |
US9728083B2 (en) * | 2011-01-17 | 2017-08-08 | Lg Electronics Inc. | Control apparatus, control target apparatus, and alarm-setting method using the apparatuses |
US9485801B1 (en) * | 2014-04-04 | 2016-11-01 | Sprint Communications Company L.P. | Mobile communication device connected to home digital network |
US11784876B1 (en) * | 2023-04-17 | 2023-10-10 | Dell Products L.P. | System and method for managing the operation and remote provisioning of data processing systems |
Also Published As
Publication number | Publication date |
---|---|
US20080310435A1 (en) | 2008-12-18 |
CN104717315A (en) | 2015-06-17 |
CN101341716A (en) | 2009-01-07 |
EP1964351A1 (en) | 2008-09-03 |
CN104717315B (en) | 2018-06-19 |
WO2007071282A1 (en) | 2007-06-28 |
WO2007071461A1 (en) | 2007-06-28 |
CN101361342A (en) | 2009-02-04 |
US8289980B2 (en) | 2012-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20090092109A1 (en) | Method and Apparatus for Enabling Discovery Within a Home Network | |
JP4648458B2 (en) | Control of service quality in communication systems | |
JP5189104B2 (en) | Method and apparatus for enabling multimedia communication with a private network | |
JP4875169B2 (en) | Method and apparatus for remote access to a home network | |
EP2116006B1 (en) | Method for remotely controlling multimedia communication across local networks. | |
US8787267B2 (en) | Technique for providing access to a media resource attached to a network-registered device | |
EP2856727B1 (en) | Methods and apparatus for media transmission in telecommunications networks | |
US20070198669A1 (en) | Plug-and-play device for videophony applications on packet-switched networks | |
Haruyama et al. | Dial-to-connect VPN system for remote DLNA communication | |
EP2566113B1 (en) | Method and apparatus for transmitting media resources | |
WO2008046302A1 (en) | A method, system and network entity for obtaining the session description protocol capability information | |
EP1964353B1 (en) | Method for establishing a unicast media session | |
RU2406249C2 (en) | Quality of service management in communication system | |
Hjelm et al. | Bringing IMS Services to the DLNA Connected Home |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CAGENIUS, TORBJORN;DAMOLA, AYODELE;REEL/FRAME:022513/0632;SIGNING DATES FROM 20080609 TO 20080610 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |