Classifications

• • 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/104—Signalling gateways in the network
• • 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]
• • 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/103—Media gateways in the network
• • 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
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• • 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

Definitions

• the present invention relates to methods and apparatus for media transmission in telecommunications networks. More particularly, the invention relates to methods and apparatus for supporting the transmission of media to and from a web browser provided at a User Equipment through an IP Multimedia Subsystem core network.
• the IP Multimedia Subsystem is the technology defined by the Third Generation Partnership Project (3GPP) to provide IP Multimedia services over telecommunication networks (see 3GPP TS 22.228, TS 23.228, TS 24.229, TS 29.228, TS 29.229, TS 29.328 and TS 29.329).
• 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 is able to connect to both PSTN/ISDN (Public Switched Telephone Network/Integrated Services Digital Network) as well as the Internet.
• PSTN/ISDN Public Switched Telephone Network/Integrated Services Digital Network
• FIG. 1 illustrates schematically the architecture for the IMS core network and its relationship to an IP-Connectivity Access Network (IP-CAN).
• IP-CAN IP-Connectivity Access Network
• CSCFs Call/Session Control Functions
• BGCFs Border Gateway Control Functions
• MRFCs Media Resource Function Controllers
• the 3GPP architecture defines three types of CSCFs: a Proxy CSCF (P-CSCF) is the first point of contact within the IMS for a SIP terminal; a Serving CSCF (S-CSCF) provides services to the subscriber; and an Interrogating CSCF (l-CSCF) identifies the correct S-CSCF and forwards to that S-CSCF a request received from a SIP terminal via a P-CSCF.
• P-CSCF Proxy CSCF
• S-CSCF Serving CSCF
• l-CSCF Interrogating CSCF
• the P-CSCF serves as a Back-to-Back User Agent (SIP B2BUA).
• SIP B2BUA Back-to-Back User Agent
• the P-CSCF is responsible for forwarding SIP registration messages from the SIP terminal (e.g. the User Equipment (UE)), to the l-CSCF and subsequent call set-up requests and responses to the S-CSCF.
• the P-CSCF maintains the mapping between logical subscriber SIP URI address and physical UE IP address and a security association, for both authentication and confidentiality.
• the P-CSCF interacts with an IMS Access Gateway (IMS-AGW), over the Iq interface, for control of the boundary at the signalling and media layers (e.g. including pinhole firewall, Network Address and Port Translations (NAPT) lawful intercept and numerous other features).
• IMS-AGW IMS Access Gateway
• the IMS-AGW controls the transport boundary at layers 3 and 4 between subscribers and the service provider's network. This function acts as a pinhole firewall and NAT device protecting the service provider's IMS network. It controls access by packet filtering on IP address/port and opening/closing gates (pinholes) into the network. It uses NAPT to hide the IP addresses/ports of the service elements in the IMS network. Other features include QoS packet marking, bandwidth and signalling rate policing, usage metering and QoS measurements for the media flows.
• telecommunications network operators want to be able to easily and quickly integrate and deploy services combining web and Internet applications with telecommunications network capabilities. It is therefore desired that telecommunication networks are able to support voice and video communications to and from web applications provided on User Equipment (UE).
• UE User Equipment
• web browsers and web applications use protocols such as Hypertext Transfer Protocol (HTTP), Real-time Transport Protocol (RTP) in conjunction with the RTP Control Protocol (RTCP), and Real Time Messaging Protocol (RTMP) for delivering and controlling media.
• HTTP Hypertext Transfer Protocol
• RTP Real-time Transport Protocol
• RTCP Real-time Transport Protocol
• RTMP Real Time Messaging Protocol
• the IMS core network makes use of the Session Initiation Protocol (SIP) to set up and control calls or sessions between user terminals (or user terminals and application servers), and media transmissions are carried using the Real-time Transport Protocol (RTP).
• SIP Session Initiation Protocol
• RTP Real-time Transport Protocol
• SDP Session Description Protocol
• SIP signalling is used to describe and negotiate the media components of the session (e.g. port numbers, protocols, codecs).
• an apparatus configured to operate as a gateway node for supporting the transmission of media to and from a web browser provided at a UE through an IMS core network.
• the apparatus comprises:
• a receiver configured to receive HTTP messages from the UE, and to receive SIP messages from the IMS;
• a translation unit configured to translate the received HTTP messages to SIP messages, and to translate the received SIP messages to HTTP messages;
• a transmitter configured to send HTTP messages to the UE, and to send SIP messages to the IMS;
• a media connection unit configured to include a connection identifier in a HTTP message sent to the UE, the connection identifier being associated with a media connection within the IMS for the UE.
• the media control unit can be configured to obtain the connection identifier from a SIP message received from the IMS.
• the media control unit can be configured to obtain the connection identifier from a specified/corresponding attribute within a SDP body of a SIP message received from the IMS.
• the media control unit can be configured to obtain the connection identifier from a specified/corresponding proprietary SIP header of a SIP message received from the IMS.
• the media control unit can be configured to obtain the connection identifier from a header field of the SIP messages.
• the connection identifier may be obtained from the Call-ID or Session-ID header field of the SIP messages.
• the media control unit can be configured to obtain an IP address and port number from the SIP messages received from the IMS, and to include the received IP address and port number in a HTTP message sent to the UE.
• the IP address and port number may relate to a IMS Access Gateway (IMS-AGW) within the IMS core network that can provide media server functionality to the UE.
• IMS-AGW IMS Access Gateway
• the SIP messages can be sent to and received from a P-CSCF in the IMS core network.
• the direct media connection with the IMS can be a RTMP connection or a RTP connection.
• the media connection within the IMS can be a RTP connection.
• an apparatus configured to operate as a Proxy-Call Session Control Functions, and to support the transmission of media to and from a web browser provided at a UE through an IMS, core network.
• the apparatus comprises:
• a receiver configured to receive messages from an IMS-AGW and to receive messages sent on behalf of the UE
• a transmitter configured to send messages to the IMS-AGW, and to send messages towards the UE;
• a media connection unit configured to instruct the IMS-AGW to initiate a first media connection within the IMS for the UE and a second media connection between the IMS-AGW and the UE, and to ensure that a connection identifier is available to the UE and to the IMS-AGW, the connection identifier being used by the IMS-AGW to associate the first media connection and the second media connection.
• the receiver can be configured to receive a SIP message that requires establishment of a media session involving the web browser provided at the UE.
• the media connection unit can be configured to ensure that a H.248 Context ID used by the BGF to associate the first media connection and the second media connection is available to the UE.
• the media connection unit can be configured to obtain a H.248 Context ID from a message received from the IMS-AGW and to include the H.248 Context ID in a SIP message sent towards the UE.
• the media connection unit can be configured to include the H.248 Context ID from a specified/corresponding attribute within a SDP body of a SIP message sent towards the UE.
• the media connection unit can be configured to include the H.248 Context ID in a specified/corresponding proprietary SIP header of a SIP message sent towards the UE.
• the media connection unit can be configured to obtain a header field value from a received SIP message, and to instruct the IMS-AGW to use the header field value as a H.248 Context ID.
• the media connection unit can be configured to obtain an IP address and port number from the messages received from the IMS-AGW, and to include the received IP address and port number in a SIP message sent towards the UE.
• the transmitter can be configured to send SIP messages intended for the UE to a gateway node in the access network, the gateway node translating the SIP messages to HTTP messages for sending to the web browser provided at the UE
• a gateway node in the access network
• the apparatus comprises:
• a media connection unit configured to collaborate with a P-CSCF in order to initiate a first media connection within the IMS for the UE and a second media connection to the UE, and to establish a connection identifier to be used to associate the first media connection and the second media connection;
• a media transmission unit configured to use the first media connection and the second media connection to transmit media to and/or from the UE
• the media connection unit is further configured to allow the media transmission unit to transmit media to and/or from the UE, if a connection identifier included in media protocol messages received from the UE matches the connection identifier established during the collaboration with the P-CSCF
• the media connection unit can be configured to establish a H.248 Context ID as the connection identifier to be used by the IMS-AGW to associate the first media connection and the second media connection.
• the media connection unit can be configured to assign a H.248 Context ID to associate the first media connection and the second media connection, and to include the H.248 Context ID in a message sent to the P-CSCF.
• the media connection unit can be configured to assign a value received from the P-CSCF as the H.248 Context ID.
• the media connection unit can also be configured to dynamically allocate an IP address and port number that must be used by the UE for establishing the second media connection, and to include the IP address and port number in a message sent to the P-CSCF.
• the media connection unit can then be configured to determine if a received request to establish a media connection is received at the IP address and port number sent to the P-CSCF.
• the apparatus can further comprise a media translation unit configured to translate between a first media protocol used on the first media connection and a second media protocol used on the second media connection.
• the media translation unit can be configured to translate between RTP and RTMP.
• an apparatus configured to operate as a UE and to implement the transmission of media to and from a web browser provided at the UE through an IMS core network.
• the apparatus comprises
• a HTTP client unit configured to use HTTP messages to initiate a first media connection within the IMS for the UE and a second media connection to the IMS; and a media connection unit configured to obtain a connection identifier from received HTTP messages, the connection identifier being associated with the first media connection and the second media connection, and to include the connection identifier in media protocol messages sent towards the IMS.
• the apparatus can be configured to communicate with a node of an access network in order to initiate the first media connection and the second media connection.
• the apparatus can also be configured to send the media protocol messages to an IMS- AGW at the boundary of the IMS.
• the apparatus can therefore further comprise a receiver and a transmitter.
• the HTTP client unit can be configured to initiate a RTMP connection to the IMS, and the media connection unit can be configured to include the connection identifier in RTMP messages sent towards the IMS.
• the HTTP client unit can be configured to initiate a RTP connection to the IMS, and the media connection unit can be configured to include the connection identifier in RTP messages and RTCP messages sent towards the IMS.
• a fifth aspect of the present invention there is provided a method of operating a node of an access network in order to support the transmission of media to and from a web browser provided at a UE through an IMS core network.
• the method comprises
• connection identifier in a HTTP message sent to the UE, the connection identifier being associated with a media connection within the IMS for the UE.
• connection identifier can be obtained from a SIP message received from the IMS.
• the connection identifier can be obtained from a specified/corresponding attribute within a SDP body of a SIP message received from the IMS.
• the connection identifier is obtained from a specified/corresponding proprietary SIP header of a SIP message received from the IMS.
• a header field value from the SIP messages can be included as the connection identifier.
• the method can further comprise receiving a SIP message including an IP address and port number that must be used by the UE for establishing a direct media connection with the IMS, and including the received IP address and port number in a HTTP message sent to the UE.
• the IP address and port number can relate to an I MS-AG W within the IMS core network that can provide media server functionality to the UE.
• the SIP messages can be sent to and received from a P-CSCF in the IMS core network.
• a method of operating a P-CSCF in order to support the transmission of media to and from a web browser provided at a UE through an IMS, core network.
• the method comprises communicating with an IMS-AGW to initiate a first media connection within the IMS for the UE and a second media connection between the IMS-AGW and the UE; and
• the step of ensuring that a connection identifier is available to the UE and to the IMS- AGW can comprise ensuring that a H.248 Context ID used by the IMS-AGW to associate the first media connection and the second media connection is available to the UE.
• the method may then further comprise receiving the H.248 Context ID from the IMS-AGW and including the H.248 Context ID in a SIP message sent towards the UE.
• the H.248 Context ID may be included in a specified/corresponding attribute within a SDP body of a SIP message sent towards the UE.
• the H.248 Context ID can be included in a specified/corresponding proprietary SIP header of a SIP message sent towards the UE.
• the method may alternatively comprise obtaining a header field value from the received SIP message, and sending a message to the IMS-AGW instructing the IMS-AGW to use the header field value as the H.248 Context ID.
• the method can further comprise receiving, from the IMS-AGW, an IP address and port number that must be used by the UE for establishing the direct media connection with the IMS-AGW, and including the received IP address and port number in a SIP message sent towards the UE.
• the SIP messages intended for the UE can be sent to a node in the access network, the node translating the SIP messages to HTTP messages for sending to the web browser provided at the UE.
• a seventh aspect of the present invention there is provided a method of operating an IMS-AGW in order to support the transmission of media to and from a web browser provided at a UE through an IMS core network.
• the method comprises:
• a P-CSCF communicating with a P-CSCF to initiate a first media connection within the IMS for the UE and a second media connection to the UE, and to establish a connection identifier to be used by the IMS-AGW to associate the first media connection and the second media connection;
• the media protocol messages including a connection identifier
• the connection identifier to be used by the IMS-AGW to associate the first media connection and the second media connection can be a H.248 Context ID.
• the method can then further comprise assigning a H.248 Context ID to associate the first media connection and the second media connection, and sending the H.248 Context ID to the P-CSCF.
• the method may further comprise receiving a message from the P-CSCF, the message instructing the IMS-AGW to use a specified value as the H.248 Context ID, and assigning the specified value as the H.248 Context ID.
• the method can comprise dynamically allocating an IP address and port number that must be used by the UE for establishing the second media connection, and sending the IP address and port number to the P-CSCF.
• the method may then further comprise receiving a request from to establish a media connection, and determining if the request is received at the IP address and port number sent to the P-CSCF.
• a method of operating a UE in order to implement the transmission of media to and from a web browser provided at the UE, through an IMS core network.
• the method comprises using HTTP messages in order to initiate a first media connection within the IMS for the UE and a second media connection to the IMS;
• connection identifier in the HTTP messages, the connection identifier being associated with the first media connection and the second media connection;
• connection identifier in media protocol messages sent towards the IMS.
• the UE can communicate with a node of an access network in order to initiate the first media connection and the second media connection.
• the second media connection can be between the UE and an IMS-AGW at the boundary of the IMS.
• the media protocol messages are then sent to the IMS-AGW.
• the second media connection can be a RTMP connection, and the connection identifier is then included in RTMP messages.
• the second media connection can be a RTP connection, and the connection identifier is then included in RTP messages and RTCP messages.
• a computer program comprising computer program code means adapted to perform all the steps of any of the fifth to eighth aspects when said program is run on a computer.
• a computer program according to the additional aspect embodied on a computer readable medium.
• Figure 1 illustrates schematically the architecture for the IMS core network and its relationship to an IP-CAN
• Figure 2 illustrates schematically a network configuration suitable for implementing the methods described herein;
• Figure 3 is a flow diagram illustrating an example of the process of a web browser initiating a media session via the IMS according to a method described herein;
• Figure 4 is a flow diagram illustrating an example of the process of a web browser initiating a media session via the IMS according to a method described herein;
• Figure 5 is a flow diagram illustrating an example of the process of a web browser initiating a media session via the IMS according to a method described herein;
• Figure 6 is a flow diagram illustrating an example of the process of a web browser initiating a media session via the IMS according to a method described herein;
• Figure 7 illustrates schematically an example of a UE suitable for implementing the methods described herein;
• FIG. 8 illustrates schematically an example of a gateway node suitable for implementing the methods described herein;
• Figure 9 illustrates schematically an example of a P-CSCF suitable for implementing the methods described herein.
• Figure 10 illustrates schematically an example of an IMS-AGW suitable for implementing the methods described herein.
• H2S GW HTTP-to-SIP Gateway
• the H2S GW communicate with the UE using HTTP-REST and communicate with a Proxy-Call Session Control Function (P-CSCF) at the border of the IMS core network and the access network using SIP.
• P-CSCF Proxy-Call Session Control Function
• REST Representational State Transfer
• XML Extensible Markup Language
• the H2S GW will therefore be required to translate between HTTP-REST and SIP, and will act as an IMS terminal emulator for control signalling.
• the UE can then directly establish a session with a media handling node of the IMS core network, such as an IMS Access Gateway (IMS-AGW), in order to send and/or receive media.
• IMS-AGW IMS Access Gateway
• An IMS-AGW at the boundary between the access network and the IMS core network therefore acts as a media server with respect to the UE, and may therefore be required handle the conversion between RTP used for media transmission by the IMS and RTMP or RTP/RTCP that may be used by the web browser provided at the UE.
• Figure 2 illustrates schematically a network configuration suitable for implementing the methods described herein.
• the IMS-AGW must be able to correlate any media protocol messages received from the UE with a RTP connection (or at least the resources reserved for the RTP connection) that has been initiated/established for the UE in the IMS (i.e. as a result of the SIP signalling from the H2S GW).
• the HTTP signalling does not provide a mechanism to convey the IP address of the UE to the P-CSCF, as the HTTP signalling is routed between the P- CSCF and the UE via the H2S GW and possibly via other HTTP proxies.
• the P-CSCF when the P-CSCF communicates with the IMS-AGW, in order to create a context and reserve resources for a RTP connection in the IMS and for a direct media connection to the UE, the P-CSCF will not be able to provide the IMS- AGW with the IP address of the UE. Therefore, even if the IMS-AGW can correlate received media protocol messages with a corresponding RTP connection, the IMS- AGW may not be able to confirm that these media protocol messages are actually from the UE for which the RTP connection has been initiated/established.
• the IMS-AGW is configured to dynamically allocate an IP address (from several fixed IP addresses available to the IMS_AGW) and port number for the direct media connection with the UE.
• the media protocol messages received from the UE for this direct media connection will be received on a specifically allocated port.
• the IMS-AGW can therefore correlate any media protocol messages received on this specified port with the RTP connection in the IMS that has been negotiated/initiated/established for the UE.
• the P-CSCF is configured to include the IP address and port number allocated by the IMS-AGW in the SDP of a SIP message sent to the H2S GW (e.g. a SIP 200 OK message if on the originating side or a SIP INVITE message if on the terminating side).
• the H2S GW is then also configured to include the IP address and port number received from the P-CSCF in a HTTP message sent to the UE.
• the UE is configured to use the IP address and port number received from H2S GW to establish the direct media connection with the IMS-AGW. Whilst this first embodiment enables the IMS-AGW to correlate any media protocol messages received on the specifically allocated port with the RTP connection, the IMS-AGW will still be unable to confirm that these media protocol messages are actually from the UE for which the RTP connection has been initiated/established, and not from another UE that may have malicious intent.
• the P-CSCF is configured to use the control signalling that initiates the media connections to ensure that a connection identifier is available to both the UE and the IMS-AGW.
• the UE can therefore be configured to include this connection identifier in any media protocol messages sent to the IMS-AGW, thereby enabling the IMS-AGW to confirm that these messages are from the UE for which the media connections are intended.
• a P-CSCF uses the H.248 protocol to communicate with a IMS-AGW in order to initiate media connections. To do so, the P-CSCF sends a H.248 Add command to the IMS-AGW in order to create a H.248 context and reserve resources for a RTP connection in the IMS and for a direct media connection to the UE.
• the resulting H.248 context will be assigned a Context ID which can therefore be used as a connection identifier.
• the IMS-AGW is configured to assign a Context ID to the H.248 context created for the media connections and to send the assigned Context ID to the P-CSCF in the reply to the H.248 Add command.
• the P-CSCF is then configured to include the received Context ID in a SIP message sent to the H2S GW.
• the P-CSCF can either include the Context ID as an attribute within the SDP body of the SIP message, or can include the Context ID as a proprietary SIP header.
• the H2S GW is therefore configured to obtain the Context ID from the received SIP message and to include this Context ID in a HTTP message sent to the UE.
• the UE is configured to include the Context ID received from H2S GW in media protocol messages that are sent to the IMS-AGW, thereby enabling the IMS-AGW to confirm that these messages are from the UE for which the media connections are intended by comparing the Context-ID received from the UE with the Context-ID assigned to the H.248 context.
• FIG. 3 is a flow diagram illustrating an example of the process of a web browser initiating a RTMP audio session via the IMS according to the first alternative of the first embodiment described above.
• the Context ID is used as a connection identifier and is communicated to the UE as an attribute within the SDP body of a SIP message. The steps performed are as follows:
• the user of an originating UE starts a voice call from their web browser. For example, the use may press on a button within a web page presented on the Graphical User Interface (GUI) of the UE.
• GUI Graphical User Interface
• the web browser/HTTP client of the originating UE generates a corresponding HTTP-REST message indicating that it wants to establish a voice call.
• This HTTP-REST message will include some of the parameters/attributes for the call, such as the media protocol to be used and the codecs that are supported.
• the HTTP-REST message is received by a H2S GW in the originating access network.
• the H2S GW translates the HTTP-REST message to an equivalent SIP INVITE message and transmits the SIP INVITE message towards the IMS.
• the media description line of the SDP body of the SIP INVITE message specifies that the media type is audio and that RTMP is to be used to transport the media.
• the SIP INVITE message is received by an P-CSCF on the originating side of the IMS core network that serves the UE.
• the originating P-CSCF therefore sends a H.248 Add command to an IMS-AGW on the originating side of the IMS core network.
• the originating IMS-AGW Upon receipt of the H.248 Add command, the originating IMS-AGW creates a H.248 context and reserves resources for a RTP connection in the IMS and for a RTMP connection to the UE. In this example, this includes the originating IMS-AGW dynamically allocating an IP address and port number for the RTMP connection with the UE. The originating IMS-AGW also assigns a Context ID (e.g. ctxtlD-o) to the H.248 context created for the media connections. A6. The originating IMS-AGW sends a reply to the H.248 Add command and includes the assigned Context ID and the IP address and port number allocated for the RTMP connection with the UE.
• a Context ID e.g. ctxtlD-o
• the originating P-CSCF sends the SIP INVITE through the IMS core network to an P-CSCF on the terminating side that serves the called UE.
• the SIP INVITE message is received by the terminating P-CSCF, which therefore sends a H.248 Add command to a IMS-AGW on the terminating side of the IMS core network.
• the terminating IMS-AGW Upon receipt of the H.248 Add command, the terminating IMS-AGW creates a H.248 context and reserves resources for a RTP connection in the IMS and for a RTMP connection to the UE. In this example, this includes the terminating IMS-AGW dynamically allocating an IP address and port number for the RTMP connection with the UE. The terminating IMS-AGW also assigns a Context ID (e.g. ctxtlD-t) to the H.248 context created for the media connections on the terminating side.
• a Context ID e.g. ctxtlD-t
• the terminating IMS-AGW sends a reply to the H.248 Add command and includes the assigned Context ID and the IP address and port number allocated for the RTMP connection with the UE.
• the terminating P-CSCF includes the received Context ID as an attribute within the SDP body of the SIP INVITE message, together with the allocated
• IP address and port number (e.g. in the connection information), sends the SIP INVITE towards the UE.
• the SIP INVITE message is received by a H2S GW in the terminating access network.
• the terminating H2S GW translates the SIP INVITE message to an equivalent HTTP-REST message inviting the user to establish a voice call and including both the received Context ID and the allocated IP address and port number.
• the terminating H2S GW transmits the HTTP-REST message to the terminating/called UE.
• the terminating UE receives the HTTP-REST message inviting the user to establish a voice call from the web browser of the terminating UE, and thereby obtains the IP address and port number that is to be used for the RTMP connection to the terminating IMS-AGW and the Context ID.
• the web browser/HTTP client of the terminating UE generates a HTTP-REST message indicating that the user has accepted the call, and sends the HTTP- REST message to the terminating H2S GW.
• the web browser of the terminating UE also generates an RTMP connect command message and includes the Context ID received from the terminating H2S GW as a parameter of the command message. The web browser then sends the RTMP connect command message to the IP address and port number received from the terminating H2S GW.
• the terminating IMS-AGW receives RTMP connect command message on the port allocated to the RTMP connection initiated for the UE and is therefore able to correlate the RTMP command message with the RTP connection initiated in the IMS.
• the terminating IMS-AGW is also able to confirm that the RTMP command is from the terminating UE by comparing the Context-ID received in the message with the Context-ID assigned to the H.248 context.
• An RTMP connection is therefore established between the terminating IMS- AGW and the terminating UE, and an RTP connection is established between the terminating IMS-AGW and the originating IMS-AGW through the IMS.
• the HTTP-REST message sent by the terminating UE is received by the terminating H2S GW.
• the terminating H2S GW translates the HTTP-REST message to an equivalent SIP 200 OK message and transmits the SIP 200 OK message towards the IMS.
• the SIP 200 OK message is received by the terminating P-CSCF.
• the terminating P-CSCF then sends a H.248 Modify command to the terminating
• this H.248 Modify command may be used to modify the attributes of the reserved resources, such as the codec, bitrate etc, in accordance with attributes specified by the terminating UE.
• the terminating IMS-AGW sends a reply to the H.248 Modify command.
• the terminating P-CSCF sends the SIP 200 OK message through the IMS core network to the originating P-CSCF.
• the SIP 200 OK message is received by the originating P-CSCF.
• the originating P-CSCF then sends a H.248 Modify command to the originating P-CSCF.
• this H.248 Modify command may be used to modify the attributes of the reserved resources, such as the codec, bitrate etc, in accordance with attributes specified by the terminating UE.
• the originating IMS-AGW sends a reply to the H.248 Modify command.
• the originating P-CSCF includes the Context ID received from the originating IMS-AGW as an attribute within the SDP body of the SIP INVITE message, together with the allocated IP address and port number, sends the SIP 200 OK message towards the originating UE.
• the SIP 200 OK message is received by the originating H2S GW.
• the originating H2S GW translates the SIP 200 OK message to an equivalent HTTP-REST message indicating that the called user has accepted the call and including both the Context ID and the allocated IP address and port number received from the originating P-CSCF.
• the originating H2S GW transmits the HTTP-REST message to the originating UE.
• the originating UE receives the HTTP-REST message indicating that the called user has accepted the call, and thereby obtains the IP address and port number that is to be used for the RTMP connection to the originating IMS-AGW and the corresponding Context ID.
• the web browser of the originating UE generates an RTMP connect command message and include the Context ID received from the originating H2S GW as a parameter of the command message.
• the web browser then sends the RTMP connect command message to the IP address and port number received from the originating H2S GW.
• the originating IMS-AGW receives RTMP connect command message on the port allocated to the RTMP connection initiated for the originating UE and is therefore able to correlate the RTMP command message with the RTP connection initiated in the IMS.
• the originating IMS-AGW is also able to confirm that the RTMP command is from the originating UE by comparing the Context-ID received in the message with the Context-ID assigned to the H.248 context.
• An RTMP connection is therefore established between the originating IMS-AGW and the originating UE, and an RTP connection is established between the originating IMS-AGW and the terminating IMS-AGW through the IMS.
• the P-CSCF is configured to set the Context ID assigned to the H.248 context to the value of a SIP identifier that is associated with the SIP message that initiate the session.
• this dialog/session identifier could be the SIP Call-ID used to identify the SIP dialog, or could by the SIP Session-ID used to identify the media session.
• the P- CSCF is configured to include the SIP identifier in the Context ID attribute of the H.248 Add command sent to the IMS-AGW in order to create the H.248 context.
• the H2S GW will have selected the SIP identifier and included this in the SIP message sent to the P-CSCF, and is therefore also configured to include the SIP identifier in a HTTP message sent to the UE.
• the UE is configured to include the SIP identifier received from H2S GW in media protocol messages that are sent to the IMS-AGW.
• the SIP identifier is therefore used as the connection identifier that enables the IMS- AGW to confirm that the media protocol messages are from the UE for which the media connections are intended, as the IMS-AGW can compare the SIP identifier received from the UE with the Context-ID assigned to the H.248 context.
• FIG. 4 is a flow diagram illustrating an example of the process of a web browser initiating a RTMP audio session via the IMS according to the second alternative of the first embodiment described above.
• Steps B1 to B25 are substantially the same as those of Figure 3.
• the P-CSCF instructs the IMS-AGW to set the SIP Call-ID as the Context-ID.
• the H2S GW is configured to communicate SIP Call-ID to the UE, the SIP Call-ID having been obtained from the SIP signalling.
• the UE then includes the SIP Call-ID in the RTMP messages sent to the IMS-AGW, and in steps B15 and B25 the IMS-AGW compares compare the Call-ID received from the UE with the Context-ID assigned to the H.248 context.
• the IMS-AGW is configured to dynamically allocate an IP address and port number for the direct media connection with the UE.
• the IMS-AGW must use pre- configured default port numbers for direct media connections with the UE, and therefore cannot rely on the IP address and port number to correlate any received media protocol messages with a RTP connection in the IMS that has been initiated/established for the UE.
• a typical RTMP server listens for RTMP requests on port 1935 by default and on port 80 for RTMP Tunnelling requests (wherein RTMPT is RTMP encapsulated within HTTP). Consequently, a typical RTMP client will first try to connect to a RTMP server using port 1935 and, if unsuccessful, will then encapsulate the RTMP request in HTTP and try to connect using port 80.
• the IMS-AGW is configured to use a connection identifier to correlate media protocol messages received from the UE with the RTP connection initiated for the UE, and to confirm that these messages are from the UE for which these media connections are intended.
• the P-CSCF is configured to use the control signalling that initiates the media connections to ensure that a connection identifier is available to both the UE and the IMS-AGW. The UE can therefore be configured to include this connection identifier in any media protocol messages sent to the IMS-AGW.
• the Context ID assigned to the H.248 context by the IMS-AGW is used as the connection identifier, and is communicated to the UE via the P-CSCF and H2S GW.
• the UE is then configured to include the Context ID received from H2S GW in media protocol messages that are sent to the IMS-AGW.
• Figure 5 is a flow diagram illustrating an example of the process of a web browser initiating a RTMP audio session via the IMS according to the first alternative of the second embodiment described above. Steps C1 to C25 are substantially the same as those of Figure 3.
• the IMS-AGW creates a H.248 context and reserves resources for the media connections but uses the default port 1935 for the RTMP connection with the UE, and it is this default port number that is communicated to the UE.
• the IMS-AGW therefore receives a RTMP connect command message on the default port and is required to compare the Context-ID received in the message with the Context-ID assigned to the H.248 context in order to correlate the RTMP command message with the RTP connection initiated in the IMS. This comparison also enables the IMS-AGW to confirm that the RTMP command is from the intended UE.
• the SIP identifier included in the SIP message that initiates the session is used as the connection identifier, and is provided to the IMS-AGW by the P-CSCF when the P-CSCF sets the SIP identifier as the Context ID of the H.248 context.
• the UE is then configured to include the SIP identifier received from H2S GW in media protocol messages that are sent to the IMS-AGW.
• Figure 6 is a flow diagram illustrating an example of the process of a web browser initiating a RTMP audio session via the IMS according to the first alternative of the second embodiment described above. Steps D1 to D25 are substantially the same as those of Figure 4.
• the IMS-AGW creates a H.248 context and reserves resources for the media connections but uses the default port 1935 for the RTMP connection with the UE, and it is this default port number that is communicated to the UE.
• the IMS-AGW therefore receives a RTMP connect command message on the default port and is required to compare the Call-ID received in the message with the Context-ID assigned to the H.248 context in order to correlate the RTMP command message with the RTP connection initiated in the IMS. This comparison also enables the IMS-AGW to confirm that the RTMP command is from the intended UE.
• connection identifier must therefore be available to both the UE and the IMS-AGW, such that the UE can include this connection identifier in any media protocol messages sent to the IMS- AGW, and the IMS-AGW can compare the connection identifier received from the UE with a connection identifier allocated to the corresponding H.248 context.
• the web browser/UE can be configured to include this connection identifier as the Synchronization Source (SSRC) within any RTP and RTCP messages sent to the IMS-AGW. Including the connection identifier in both RTP and RTCP messages prevents malicious users from using either.
• SSRC Synchronization Source
• the examples described above and illustrated in Figures 3 to 6 relate to a web browser initiating a session in which RTMP media is transmitted through the IMS to a terminating web browser, such that the RTMP media is translated to RTP for transmission through the IMS and this RTP media is then translated back to RTMP for transmission to the terminating UE.
• the methods and apparatus described are equally applicable to sessions in which a web browser wants to transmit RTMP media to a SIP client at a terminating UE.
• the originating side of the call would proceed in accordance with the methods and apparatus described above, whilst the terminating side of the call would not require the involvement of a H2S GW, as the P-CSCF could communicate directly with the terminating UE using SIP.
• the terminating IMS-AGW would also not be required to translate the RTP media back to RTMP, as it would be able to allow the RTP media from the IMS to pass through to the terminating UE.
• FIG. 7 illustrates schematically an example of a UE 10 for implementing the transmission of media to and from a web browser provided at the UE through an IMS in accordance with the methods described above.
• the UE 10 can be implemented as a combination of computer hardware and software.
• the UE 10 comprises a processor 1 1 , a memory 12, a receiver 13 and a transmitter 14.
• the memory 12 stores the various programs/executable files that are implemented by the processor 1 1 , and also provides a storage unit for any required data.
• the programs/executable files stored in the memory 12, and implemented by the processor 11 include but are not limited to a rule a web browser/HTTP client unit 15, a media unit 16, and a media connection unit 17.
• FIG. 8 illustrates schematically an example of a H2S GW 20 for implementing the transmission of media to and from a web browser provided at a UE through an IMS in accordance with the methods described above.
• the H2S GW 20 can be implemented as a combination of computer hardware and software.
• the H2S GW 20 comprises a processor 21 , a memory 22, a receiver 23 and a transmitter 24.
• the memory 22 stores the various programs/executable files that are implemented by the processor 21 , and also provides a storage unit for any required data.
• the programs/executable files stored in the memory 22, and implemented by the processor 21 include but are not limited to a protocol unit 25 (e.g. for implementing the SIP and HTTP protocols), a HTTP-SIP translation unit 26, and media connection unit 27.
• a protocol unit 25 e.g. for implementing the SIP and HTTP protocols
• HTTP-SIP translation unit 26 e.g. for implementing the SIP and HTTP protocols
• FIG. 9 illustrates schematically an example of a P-CSCF 30 for implementing the transmission of media to and from a web browser provided at a UE through an IMS in accordance with the methods described above.
• the P-CSCF 30 can be implemented as a combination of computer hardware and software.
• the P-CSCF 30 comprises a processor 31 , a memory 32, a receiver 33 and a transmitter 34.
• the memory 32 stores the various programs/executable files that are implemented by the processor 31 , and also provides a storage unit for any required data.
• the programs/executable files stored in the memory 32, and implemented by the processor 31 include but are not limited to a protocol unit 35 (e.g. for implementing the SIP and H.248 protocols), , and a media connection unit 36.
• a protocol unit 35 e.g. for implementing the SIP and H.248 protocols
• FIG 10 illustrates schematically an example of an IMS-AGW 40 for implementing the transmission of media to and from a web browser provided at a UE through an IMS in accordance with the methods described above.
• the IMS-AGW 40 can be implemented as a combination of computer hardware and software.
• the IMS-AGW 40 comprises a processor 41 , a memory 42, a receiver 43 and a transmitter 44.
• the memory 42 stores the various programs/executable files that are implemented by the processor 41 , and also provides a storage unit for any required data.
• the programs/executable files stored in the memory 42, and implemented by the processor 41 include but are not limited to a protocol unit 45 (e.g. for implementing the H.248, RTP-RTCP and RTMP protocols), a media translation/transmission unit 46, and a media connection unit 47.
• a protocol unit 45 e.g. for implementing the H.248, RTP-RTCP and RTMP protocols
• media translation/transmission unit 46 e.g

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Multimedia (AREA)
• Computer Security & Cryptography (AREA)
• Business, Economics & Management (AREA)
• General Business, Economics & Management (AREA)
• Telephonic Communication Services (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (1)

Applications Claiming Priority (1)

Publications (1)

Family

ID=45808908

Family Applications (1)

Country Status (1)

Cited By (3)

Citations (1)

• 2012
  • 2012-03-02 WO PCT/EP2012/053679 patent/WO2013127469A1/fr not_active Ceased

Patent Citations (1)

Non-Patent Citations (2)

Similar Documents

Legal Events