Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method of ordering the delivery of a media stream to a second client terminal coupled to an IP network, the method comprising: identifying, at a first client terminal, destination address information for the second client terminal, wherein the destination address information includes an IP address and port number of the second client terminal and an IP address and port number of a Residential Gateway through which the second client terminal is coupled to the IP network; authenticating the first client terminal to an application server of an IP Multimedia Subsystem network, wherein the authentication of the first client terminal to the application server includes authorizing the second client terminal to the application server; sending the destination address information from the first client terminal to the application server; delivering the media stream to the second client terminal; wherein a RTSP Uniform Resource Locator of the application server is sent to the first client terminal; and wherein the RTSP Uniform Resource Locator of the application server is passed from the first client terminal to the second client terminal.
A method for delivering a media stream to a second client device (e.g., a TV or set-top box) connected to an IP network involves a first client device (e.g., a mobile phone) discovering the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
2. The method of claim 1 , wherein the authentication of the first client terminal to the application server includes an authentication of a user identity module associated with the first client terminal.
The media streaming method involves the first client device authenticating with the application server by verifying the user identity module (e.g., a SIM card) associated with the first device. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
3. The method of claim 1 , wherein the authentication of the first client terminal to the application server includes a token identity handshake.
The media streaming method involves the first client device authenticating with the application server using a token identity handshake. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
4. The method of claim 1 , wherein a session identity is generated in the application server, sent to the first client terminal and passed from there to the second client terminal, and used by the second client terminal to control delivery of the media stream.
The media streaming method involves the application server generating a session identity, sending it to the first client device, which then passes it to the second client device. This session identity is then used by the second client device to control the delivery of the media stream (e.g., pause, play, stop). The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
5. The method of claim 1 , wherein the media stream is delivered to the second client terminal in response to an IMS INVITE message and RTSP PLAY message sent from the first client terminal to the application server.
The media stream is delivered to the second client device after the first client device sends an IMS INVITE message and an RTSP PLAY message to the application server. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
6. The method of claim 1 , wherein the media stream is delivered to the second client terminal in response to an IMS INVITE message sent from the first client terminal and an RTSP PLAY message sent from the second client terminal to the application server.
The media stream is delivered to the second client device after the first client device sends an IMS INVITE message to the application server, and then the second client device sends an RTSP PLAY message to the application server. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
7. The method of claim 1 , wherein the media stream is delivered to the second client terminal in response to a RTSP DESCRIBE, SET-UP and PLAY from the second client terminal to the application server.
The media stream is delivered to the second client device in response to the second client device sending RTSP DESCRIBE, SET-UP, and PLAY commands to the application server. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
8. The method of claim 1 , wherein a SIP INVITE message is sent from the application server to the second client terminal in response to a service request sent from the first client terminal to the application server.
A SIP INVITE message is sent from the application server to the second client device after the first client device sends a service request to the application server. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device sends this information to the application server and authorizes the second device, enabling the media stream delivery to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
9. The method of claim 1 , wherein the first client terminal is coupled to the IP network via a cellular access network.
The first client device (e.g., the device sending the service request) is connected to the IP network via a cellular access network (e.g., 4G, 5G). The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
10. The method of claim 1 , wherein the second client terminal is coupled to the IP network via a fixed access network.
The second client device (e.g., the device receiving the media stream) is connected to the IP network via a fixed access network (e.g., Ethernet, Wi-Fi). The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
11. The method of claim 10 , wherein a reservation of resources for delivery of the media stream to the second client terminal over the fixed access network is initiated by an IMS message sent from the first client terminal towards the application server.
A reservation of resources for the media stream delivery to the second client device over the fixed access network (where the second client is connected via fixed access) is initiated by an IMS message sent from the first client device towards the application server. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
12. The method of claim 11 , wherein the IMS message sent towards the application server is a SIP INVITE message including the destination address information.
The IMS message sent towards the application server (to reserve resources for delivery of the media stream to the second client via fixed access) is a SIP INVITE message including the destination address information (IP address and port of the second client and its residential gateway). The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
13. The method of claim 1 , wherein the first client terminal establishes communication with the second client terminal in order to identify the destination address information.
The first client device establishes communication with the second client device to identify the destination address information (IP address and port of the second client and its residential gateway). The first client device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
14. The method of claim 13 , wherein the communication established between the first client terminal and the second client terminal is established using a local wireless network.
The communication established between the first and second client devices (to identify the destination address) uses a local wireless network (e.g., Bluetooth, Wi-Fi Direct). The first client device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
15. The method of claim 1 , wherein the media is IPTV media.
The media being delivered is IPTV media. The first client device discovers the second device's IP address and port, along with the IP address and port of the residential gateway it uses to connect to the internet. The first device authenticates with an application server within an IP Multimedia Subsystem (IMS) network, authorizing the second device in the process. The first device then sends the second device's address information to the application server. The IPTV media stream is subsequently delivered to the second device. The application server's RTSP URL is sent to the first client, which then passes it on to the second client for connection.
16. An application server for use in an IP Multimedia Subsystem to control the delivery of media to client terminals coupled to an IP network, the application server comprising: a receiver for receiving, from a first client terminal in the IP Multimedia Subsystem, destination address information for a second client terminal coupled to the IP network, wherein the destination address information includes an IP address and port number of the second client terminal and an IP address and port number of a Residential Gateway through which the second client terminal is coupled to the IP network; an authentication circuit for authenticating the first client terminal, and to authorize the second client terminal as a result of the authentication of the first client terminal; and a processor and transmitter for arranging delivery of the media from a media source to the second client terminal, wherein a RTSP Uniform Resource Locator of the application server is sent to the second client terminal via the first client terminal.
An application server within an IP Multimedia Subsystem (IMS) controls the delivery of media to client devices connected to an IP network. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
17. The application server of claim 16 , wherein the authentication circuit is arranged to authenticate a user identity module associated with the first client terminal.
The application server's authentication circuit authenticates the first client device by authenticating a user identity module (e.g., SIM card) associated with the first client. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
18. The application server of claim 16 , wherein the authentication circuit is arranged to carry out a token identity handshake.
The application server's authentication circuit performs a token identity handshake to authenticate the first client device. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
19. The application server of claim 16 , wherein the receiver is arranged to receive a RTSP service request from the first client terminal, and wherein the processor is configured to arrange delivery of the media to the second client terminal in response to the RTSP service request.
The application server's receiver receives an RTSP service request from the first client device, and the processor arranges the delivery of media to the second client device in response to this RTSP request. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
20. The application server of claim 16 , wherein the processor is configured to send a SIP INVITE message towards the second client terminal in response to a service request received from the first client terminal.
The application server's processor sends a SIP INVITE message to the second client device in response to a service request received from the first client device. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
21. The application server of claim 16 , wherein the receiver is arranged to receive an RTSP PLAY command from the second client terminal, and wherein the processor is configured to arrange delivery of the media to the second client terminal in response to the RTSP PLAY command.
The application server's receiver receives an RTSP PLAY command from the second client device, and the processor arranges the delivery of media to the second client device in response to this RTSP PLAY command. The server includes a receiver that receives destination address information (IP address and port of the second client and its residential gateway) for a second client device from a first client device. An authentication circuit authenticates the first client device and authorizes the second client as a result. A processor and transmitter arrange the delivery of media from a media source to the second client device. The server's RTSP URL is sent to the second client device via the first client device.
22. A first client terminal arranged in use to communicate with an application server of an IP Multimedia Subsystem, the first client terminal comprising: a receiver configured to: receive destination address information from a second client terminal, wherein the destination address information includes an IP address and port number of the second client terminal and an IP address and port number of a Residential Gateway through which the second client terminal is coupled to the IP network; and receive a RTSP Uniform Resource Locator of the application server; and a transmitter/processor/receiver for sending the destination address information to said application server, authenticating the first client terminal to the application server, authenticating the second client terminal to the application server, instructing the application server to arrange delivery of media to the second client terminal, and passing the RTSP Uniform Resource Locator of the application server to the second client terminal.
A first client device (e.g. mobile phone) communicates with an application server of an IP Multimedia Subsystem (IMS). It has a receiver to get destination address info (IP address/port of second client and its residential gateway) from a second client. It also receives the application server's RTSP URL. A transmitter/processor/receiver sends the destination info to the application server, authenticates itself and authorizes the second client to the application server, instructs the server to deliver media to the second client, and passes the application server's RTSP URL to the second client.
23. The terminal of claim 22 , further comprising an HTTP interface for communicating with the application server.
The first client device (described in the previous claim) also includes an HTTP interface for communicating with the application server. It has a receiver to get destination address info (IP address/port of second client and its residential gateway) from a second client. It also receives the application server's RTSP URL. A transmitter/processor/receiver sends the destination info to the application server, authenticates itself and authorizes the second client to the application server, instructs the server to deliver media to the second client, and passes the application server's RTSP URL to the second client.
24. The terminal of claim 22 , further comprising a wireless interface for communicating with the second client terminal.
The first client device (described in the previous claim) includes a wireless interface (e.g., Bluetooth, Wi-Fi Direct) for communicating with the second client device. It has a receiver to get destination address info (IP address/port of second client and its residential gateway) from a second client. It also receives the application server's RTSP URL. A transmitter/processor/receiver sends the destination info to the application server, authenticates itself and authorizes the second client to the application server, instructs the server to deliver media to the second client, and passes the application server's RTSP URL to the second client.
Unknown
September 30, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.