[go: up one dir, main page]

WO2009036605A1 - Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims - Google Patents

Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims Download PDF

Info

Publication number
WO2009036605A1
WO2009036605A1 PCT/CN2007/002783 CN2007002783W WO2009036605A1 WO 2009036605 A1 WO2009036605 A1 WO 2009036605A1 CN 2007002783 W CN2007002783 W CN 2007002783W WO 2009036605 A1 WO2009036605 A1 WO 2009036605A1
Authority
WO
WIPO (PCT)
Prior art keywords
rtsp
message
sip
ims
network element
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.)
Ceased
Application number
PCT/CN2007/002783
Other languages
English (en)
Inventor
Aihao Yin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia of America Corp
Original Assignee
Lucent Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lucent Technologies Inc filed Critical Lucent Technologies Inc
Priority to CN200780100643.1A priority Critical patent/CN101803324A/zh
Priority to PCT/CN2007/002783 priority patent/WO2009036605A1/fr
Publication of WO2009036605A1 publication Critical patent/WO2009036605A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the invention generally relates to the field of data communication, and in particular, to a method and system for processing Session Initiation Protocol (SIP) message with Real Time Streaming Protocol (RTSP) encapsulation in IP Multimedia Subsystem (IMS).
  • SIP Session Initiation Protocol
  • RTSP Real Time Streaming Protocol
  • IMS IP Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • IP Multimedia Subsystem IP Multimedia Subsystem
  • SIP Next Generation Network
  • IP IP Multimedia Subsystem
  • 3G handsets already support the SIP protocol for originating or terminating voice and video sessions. Unlike the traditional ones, these UEs are no longer used for single purpose. They can be enhanced to support other functionalities, such as accessing the IPTV (IP Television) and VoD (Video-On-Demand) services.
  • the RTSP protocol can be easily implemented on the terminal equipments for supporting the IPTV/ VoD services.
  • the Real Time Streaming Protocol (RTSP), developed by the IETF and published in 1998 as RFC 2326, is a protocol for use in streaming media systems. It provides an extensible frame which allows a client to remotely control a streaming media server, issues VCR-like commands such as "play” and "pause”, and allows time -based access to files on a server.
  • the RTSP commands include: DESCRIBE, SETUP, PLAY, PAUSE, RECORD, TEARDOWN, etc.
  • the RTSP messages comprise two types: Request and Response, in which their formats are different from each other, as explained below in detail. • Request message:
  • URI is the address of the recipient, such as, rtsp://192.168.20.136
  • RTSP-Version is typically RTSP/1.0
  • CR LF at the end of each line represents the carriage return & line feed.
  • RTSP-Version is typically RTSP/ 1.0
  • Status-Code is a numeral value, such as 200, which indicates a status of success
  • Explanation is a text explanation corresponding to the "Status-Code”.
  • RTSP is normally transferred over the TCP protocol.
  • it can also be carried over the Hyper Text Transfer Protocol (HTTP).
  • HTTP Hyper Text Transfer Protocol
  • the Session Initiation Protocol is an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. SIP is a text-based message protocol. It operates independently of the underlying network transport protocols, establishing sessions between multiple users irrespective if the transferred data is text data, audio data, or video data.
  • the basic SIP methods include: INVITE, CANCEL, BYE, OPTIONS, MESSAGE, SUBSCRIBE, NOTIFY, etc.
  • the SIP protocol enables end users to communicate with each other via messages.
  • the basic form of a message could either be a request sent from a client to a server or a reply from the server to the client.
  • a message consists of a start-line, one or more header fields, a null line indicating the end of the header fields, and an optional message-body.
  • start-line Request-Line /Status-Line
  • the SIP messages comprise two types: Request and Response.
  • a SIP Request message may be recognized by the presence of a Request-Line as the start-line.
  • a SIP Response message may be recognized by the presence of a Status-Line as the start-line.
  • the format of a status-line is shown as below:
  • RTSP only involves the interactions between the media server and the media client
  • SIP involves a lot of network elements for message routing and service control in the IMS network.
  • both are related to the establishment and control of real-time media streams, they are used for different services with different network architectures.
  • RTSP For the IMS subscribers to access the IPTV and VoD service, some existing implementations prefer not to use RTSP in the IMS network.
  • SIP is used to establish the sessions with the remote IPTV/VoD servers. Users need to use key pressing mapping to simulate the media control operations such as play, pause, fast forward, etc. This is good for some legacy SIP video endpoints that do not support the RTSP client functionalities, but the control of these services is not natural and it is preferred that these clients need to support RTSP as well.
  • Some new endpoints support the SIP and RTSP protocols separately.
  • RTSP flows in a different path from SIP
  • IPTV/VoD services to be controlled in the IMS or VoIP (Voice over Internet Protocol) network.
  • VoIP Voice over Internet Protocol
  • QoS Quality of Service
  • security and charging framework in the IMS or VoIP network.
  • a method for processing SIP message with RTSP encapsulation in IMS comprising the following steps: defining a new SIP content type; and encapsulating a RTSP message into a SIP message with the new SIP content type.
  • a system for processing SIP message with RTSP encapsulation in IMS comprising: a user equipment, for encapsulating a RTSP message into a SIP message with a newly- defined SIP content type and extracting a RTSP message from a SIP message with the newly- defined SIP content type; and at least one network element in IMS; wherein both the user equipment and the at least one network element in IMS support the newly-defined SIP content type.
  • the method and system for processing SIP message with RTSP encapsulation in IMS proposed by the present invention encapsulates a RTSP messages into a SIP message, thereby realizing the use of the IMS security features, the reuse of the IMS QoS framework, the use of the existing IMS charging system, and the convergence of the RTSP-based services, such as IPTV and VoD, with the existing SIP-based IMS services.
  • FIG. 1 illustrates an exemplary IMS architecture with separated SIP and RTSP message flows
  • FIG. 2 illustrates an integrated architecture supporting SIP with RTSP encapsulation according to an embodiment of the invention
  • FIG. 3 illustrates an exemplary scenario supporting SIP with RTSP encapsulation according to an embodiment of the invention.
  • a User Equipment (UE) 110 makes access to service 190, such as IPTV and VoD, through IMS 100.
  • An IMS User Equipment (UE) is a device allowing user access to network services, such as a 3G handset, a SIP phone or a soft-client running on a PC.
  • a UE supports a number of audio/video media codecs and is capable of originating or terminating sessions to the IMS via the SIP interface.
  • IMS 100 comprises P-CSCF 120, S-CSCF 130, I-CSCF 140, AS 150, HSS 160, CRF 170, and Bearer Network 180.
  • CSCF Call Session Control Function
  • AS application server
  • P-CSCF 120 is the first contact point within the IMS. It behaves like a SIP proxy server, i.e. it accepts requests from the UE 110 and forwards them on. Also P-CSCF 120 can initiate QoS control based on the session description information received in SIP messages.
  • S-CSCF 130 performs the session control services for the UE. It maintains a session state as needed by the network operator for the support of the services. It processes SIP requests based on the initial Filter Criteria (iFC) downloaded from the Home Subscriber Server (HSS). Wherein, initial Filter Criteria (iFC) contains the rules for processing the subscriber's service requests, for example, routing the requests to specific AS, I-CSCF/RSTP Gateway, etc. It is downloaded by S-CSCF upon the UE's successful registration. It can be expanded to include filtering rules for processing the RTSP body encapsulated in the SIP requests. S-CSCF also relays SIP messages between the SIP network elements, such as P-CSCF, AS and I-CSCF, etc. It also generates Call Detail Records (CDR) for billing purpose.
  • CDR Call Detail Records
  • I-CSCF 140 Interrogating CSCF 140 is the contact point for all connections destined to a user of an operator's network or a roaming user currently located within that network operator's service area. I-CSCF hides the network topology information when forwarding SIP messages between different operators' domains. Also I-CSCF can initiate QoS control based on the session description information received in SIP messages.
  • AS (Application Server) 150 is the IMS application server, which runs the IMS application logic for IMS subscribers. S-CSCF will invoke AS when it checks through the service profile of the subscriber and find that it has IMS application enabled. A valid AS name/address is provisioned for each of IMS service in the service profile.
  • HSS (Home Subscriber Server) 160 is the IMS subscriber database, which contains all the IMS subscriber service profiles, e.g. iFC, registration data, service filter criteria, service data, and location data.
  • IMS subscriber service profiles e.g. iFC, registration data, service filter criteria, service data, and location data.
  • CRF (Charging Rule Function) 170 is a main entity for flow based charging.
  • CRF can be applied to both offline charging and online charging. Charging rules defined by the system operator are transferred to CRF through a uniform interface so as to make charging for the provided services and contents.
  • the Bearer Network 180 is a network used for transmitting data between UEs. In the lifecycle of one session, a number of bearer networks can be used.
  • the Bearer Network 180 and P-CSCF 120 perform the QoS control respectively.
  • the dashed arrows in FIG. 1 indicate the SIP flows. SIP flows pass from the UE 110 through P-CSCF 120, S-CSCF 130, I-CSCF 140, in turn, or on the contrary direction. Also, S-CSCF 130 may exchange SIP messages with AS 150, HSS 160, CPvF 170, respectively.
  • the solid arrows in FIG. 1 indicate the RTSP flows between the UE 110 and the IPTV/VoD services 190 via the bearer network 180.
  • the dashed lines in FIG. 1 indicate the bearer streams between the UE 110 and the IPTV/VoD services 190 via the bearer network 180.
  • the IMS UE employs SIP messages to carry RTSP messages in the IMS/VoIP network. Instead of contacting with the remote IPTV/VoD servers directly, the IMS UE encapsulates the RTSP message into a SIP message and passes it through the IMS network elements, to facilitate the convergence of RTSP related services into existing IMS framework.
  • the IMS UE sends the SIP message to P-CSCF.
  • P-CSCF then forwards the SIP message to S-CSCF, which processes and forwards it to I-CSCF.
  • I-CSCF extracts the RTSP message from the received SIP message and sends to the remote RTSP server, and relays the RTSP response backward to the UE through the original SIP message routing path.
  • FIG. 2 there is illustrated an integrated architecture supporting SIP with RTSP encapsulation according to an embodiment of the invention.
  • a User Equipment (UE) 210 makes access to service 290, such as IPTV and VoD, through IMS 200.
  • IMS 200 comprises P-CSCF 220, S-CSCF 230, I-CSCF 240, AS 250, HSS 260, CRF 270, Bearer Gateway 285, and Bearer Network 280. Except the Bearer Gateway 285, all of the other elements in FIG.2 are similar to those as shown in FIG. 1, but with some enhancements according to the invention.
  • an IMS SIP interface with new content type is defined, i.e. a new SIP content type is defined, so that the RTSP message can be encapsulated into the SIP message.
  • a new SIP content type is defined, so that the RTSP message can be encapsulated into the SIP message.
  • the IMS UE 210 has the following enhancements:
  • the UE upon initiating a RTSP -based service request (IPTV/VoD, etc), the UE encapsulates the RTSP message into a SIP MESSAGE method and sends it to P-CSCF, instead of sending the RTSP message directly.
  • P-CSCF 220 in which QoS Application Function (QoS AF) 225 is comprised, is the first contact point of the IMS network for UEs, in which the enhancements include:
  • P-CSCF parse the requirements, such as bandwidth, rate, from the RTSP message and initiate QoS control using the existing QoS functionality.
  • the QoS AF 225 is able to communicate with the Bearer Gateway 285 for QoS control.
  • S-CSCF 230 is a network element that serves the UE's service request, in which the enhancements include:
  • IMS subscriber service profiles comprise but not limit to initial filter criteria (iFC), registration data, service filter data, service data, and location data.
  • iFC initial filter criteria
  • registration data e.g., registration data
  • service filter data e.g., registration data
  • service data e.g., registration data
  • location data e.g., location data
  • iFC is used for processing SIP message with encapsulated RTSP message, for example, routing the message to specific AS, I-CSCF/RSTP Gateway, etc.
  • I-CSCF 240 comprises a new RTSP gateway 245.
  • the new RTSP gateway 245 is to be deployed at the edge of the IMS network, preferably as part of the I-CSCF, but not essential.
  • I- CSCF 240 performs the following functionalities:
  • the dashed arrows in FIG. 2 indicate the SIP flows. SIP flows pass from the UE 210 through P-CSCF 220, S-CSCF 230, I-CSCF 240, in turn, or on the contrary direction. Also, S- CSCF 230 may exchange SIP messages with AS 250, HSS 260, CRF 270, respectively.
  • the solid arrows in FIG. 2 indicate the RTSP flows between I-CSCF 240 and the IPTV/VoD services 290.
  • the dashed lines in FIG. 2 indicate the bearer streams between the UE 210 and the IPTV/ VoD services 290 via the bearer network 280.
  • the solid line in FIG.2 indicates the QoS control.
  • the RTSP messages can be securely protected via secure SIP transport, such as SIP over IPSec (IP Security) or TLS (Transport Layer Protocol).
  • SIP over IPSec IP Security
  • TLS Transmission Layer Protocol
  • the QoS resource request in the RTSP message can be parsed by the SIP servers, so as to perform QoS control via the existing network interfaces between the SIP server and the policy decision function.
  • the RTSP-based services such as IPTV and VoD, can be converged with the existing SIP-based IMS services.
  • FIG.3 there is illustrated an exemplary scenario supporting SIP with RTSP encapsulation according to an embodiment of the invention.
  • the exemplary scenario is illustrated in conjunction with the IMS architecture supporting SIP with RTSP encapsulation, as shown in FIG. 2.
  • Step 1 a subscriber (user) browses the IPTV and VoD program list on his/her IMS UE.
  • the selection of a program is made by clicking or selecting an RTSP link, such as, rtsp://vod.example.com/musicl l23.en.
  • the IMS UE is configured to enable the RTSP encapsulation by using a SIP protocol configuration option. Instead of sending the RTSP server the RTSP link, rtsp://vod.example.com, directly, the UE encapsulates the initial RTSP DESCRIBE request in the SIP MESSAGE method and sends it to P-CSCF. As an example, there is a SIP message with the encapsulated RTSP message shown below.
  • P-CSCF recognizes the new SIP content type: "application/RTSP", and forwards the message to S-CSCF that serves this UE.
  • Step 4 upon receiving the SIP message with RTSP encapsulation, S-CSCF determines whether or not to apply the application scenario based on the content type "application/RTSP" and the content. If yes, the process proceeds to Step 4a, in which S-CSCF forwards the message to AS to trigger the application logic. This allows the opportunities of service blending and the possibilities of some more complex services.
  • S- CSCF collects and reports the RTSP related charging information to an IMS charging function, such as CRF 270.
  • Step 4c S-CSCF requests IMS subscriber service profiles from an IMS database, such as HSS 260.
  • S- CSCF chooses I-CSCF based on the RTSP destination received in the encapsulated RTSP message (either from P-CSCF or from AS) and sends the SIP message to I-CSCF.
  • I-CSCF acknowledges the SIP message with the SIP "200 OK" response, extracts the RSTP message from the SIP message, and sends it to a remote RTSP server based on the information in the RTSP message.
  • S-CSCF S-CSCF
  • AS optional
  • P-CSCF P-CSCF
  • the SIP method shall be acknowledged with a SIP response.
  • the SIP MESSAGE method is always acknowledged immediately by the remote SIP end (UE or I-CSCF) using the SIP "200 OK" response, which shall traverse through the IMS core network (S-CSCF/AS/P- CSCF) as normal;
  • I-CSCF may contact a Domain Name Service (DNS) server to get the resolved IP address of the RTSP server.
  • DNS Domain Name Service
  • the remote RTSP server acknowledges the RTSP DESCRIBE command with the RTSP "200 OK" response and sends to I-CSCF.
  • the exemplary RTSP response sent to I- CSCF is shown as below:
  • I-CSCF encapsulates the RTSP "200 OK" response using SIP MESSAGE method and sends to S-CSCF.
  • the exemplary SIP message with the encapsulated RTSP response sent to S-CSCF is shown as below:
  • S-CSCF forwards the SIP message back to P-CSCF.
  • S-CSCF determines to apply the application scenario, i.e. there is any application triggered as described in step 4a, then at Step 8a, S-CSCF forwards the SIP message to the AS prior to forwarding it to P-CSCF.
  • P-CSCF forwards the SIP message with the encapsulated RTSP response back to the IMS UE.
  • the UE extracts the RTSP response from the received SIP message and continues with the next command, such as initiating the media stream by sending the RTSP PLAY command, down the same message flow.
  • the dashed arrows, the solid arrows, the dashed lines, and the solid line shown in FIG.3 refer to the same denotations as FIG. 2, and the detailed descriptions are skipped.
  • the present invention may be embodied as a method, a system, and/or a computer program product. Therefore, the present invention can be embodied in the form of hardware, software, or the combination thereof. Additionally, the present invention may be embodied as a computer program product contained on machine-readable media where the computer executable program instructions for programming a computer system to execute the process according to the invention are stored.
  • machine-readable media used herein includes any media that provide the computer system with instructions for execution.
  • Non-volatile media commonly comprises, for example, floppy disk, floppy magnetic disk, hard disk, magnetic tape, or any other magnetic media, CD-ROM or any other optical media, slotting card or any other physical media with hole pattern, PROM, EPROM, EEPROM, flash memory, any other memory chip or cartridge, or any other media that can be read by the computer system and are appropriate for storing instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé et un système pour traiter un message SIP (protocole d'ouverture de session) avec une encapsulation RTSP (protocole de transfert de flux continu en temps réel) dans un sous-système IMS (sous-système de session multimédia IP). Le procédé comprend les étapes consistant à : définir un nouveau type de contenu SIP ; et encapsuler un message RTSP dans un message SIP avec le nouveau type de contenu SIP. L'invention développe l'utilisation des fonctions de sécurité IMS, la réutilisation du cadre général de la qualité de service IMS, l'utilisation du système de taxation IMS existant et la convergence des services basés sur RTSP, tels que l'IPTV et la VoD, avec les services IMS existants basés sur SIP.
PCT/CN2007/002783 2007-09-20 2007-09-20 Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims Ceased WO2009036605A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN200780100643.1A CN101803324A (zh) 2007-09-20 2007-09-20 在ims中处理具有rtsp封装的sip消息的方法和系统
PCT/CN2007/002783 WO2009036605A1 (fr) 2007-09-20 2007-09-20 Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2007/002783 WO2009036605A1 (fr) 2007-09-20 2007-09-20 Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims

Publications (1)

Publication Number Publication Date
WO2009036605A1 true WO2009036605A1 (fr) 2009-03-26

Family

ID=40467482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002783 Ceased WO2009036605A1 (fr) 2007-09-20 2007-09-20 Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims

Country Status (2)

Country Link
CN (1) CN101803324A (fr)
WO (1) WO2009036605A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011069450A1 (fr) * 2009-12-08 2011-06-16 中国移动通信集团公司 Procédé, système et appareil permettant une gestion de contenus multimédias dans un sous-système multimédia ip

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004040777A2 (fr) * 2002-10-30 2004-05-13 Nokia Corporation Equipement utilisateur adapte au protocole de signalisation sip permettant de fournir des services multimedia avec qualite de service
CN1741633A (zh) * 2004-08-27 2006-03-01 华为技术有限公司 实现电路域移动流媒体点播的系统及其方法
US20070043872A1 (en) * 2005-08-12 2007-02-22 Samsung Electronics Co., Ltd System and method for transmitting system messages insession initiation protocol
CN101026616A (zh) * 2006-02-18 2007-08-29 华为技术有限公司 基于ip多媒体子系统的交互式媒体会话建立系统和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004040777A2 (fr) * 2002-10-30 2004-05-13 Nokia Corporation Equipement utilisateur adapte au protocole de signalisation sip permettant de fournir des services multimedia avec qualite de service
CN1741633A (zh) * 2004-08-27 2006-03-01 华为技术有限公司 实现电路域移动流媒体点播的系统及其方法
US20070043872A1 (en) * 2005-08-12 2007-02-22 Samsung Electronics Co., Ltd System and method for transmitting system messages insession initiation protocol
CN101026616A (zh) * 2006-02-18 2007-08-29 华为技术有限公司 基于ip多媒体子系统的交互式媒体会话建立系统和方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011069450A1 (fr) * 2009-12-08 2011-06-16 中国移动通信集团公司 Procédé, système et appareil permettant une gestion de contenus multimédias dans un sous-système multimédia ip

Also Published As

Publication number Publication date
CN101803324A (zh) 2010-08-11

Similar Documents

Publication Publication Date Title
CN101401427B (zh) 用于iptv系统的时间偏移和追踪播放
CN101385303B (zh) 用于iptv服务的启用ims的控制信道
CN101547189B (zh) 一种CoD业务的建立方法,系统和装置
US10412136B2 (en) Methods and apparatus for media transmission in telecommunications networks
US8307049B2 (en) Method and device for obtaining media description information of IPTV services
US20090017796A1 (en) Methods and systems for communicating between ims and non-ims networks
CN101123718B (zh) 多媒体点播的方法及系统
CN101060532B (zh) 因特网网络电视业务信息传输方法
US20100122281A1 (en) Method and system for controlling authorization of service resources
US20050243746A1 (en) Session inspection scheme
CN100571370C (zh) 将传统iptv终端接入ims域的装置、系统和方法
US7953123B2 (en) Method and system for controlling the establishment of communications channels for allowing transmission of multimedia information
EP3228057B1 (fr) Protocole de commande d'application ims
CN101415250B (zh) Ip互联网络电视系统中会话建立的方法、系统及实体
CN101453402A (zh) 一种对媒体流控制的方法、系统及设备
CN101114985A (zh) 编解码转换系统及方法
WO2009036605A1 (fr) Procédé et système pour traiter un message sip avec une encapsulation rtsp dans un sous-système ims
CN101110790A (zh) 建立会话的方法
CN101414999B (zh) 会话描述协议中获取频道与媒体关系的方法、频道信息的发送方法以及相关设备
CN101114993A (zh) 一种会话初始协议网络系统及控制业务路由的方法
EP2059001A1 (fr) Élément de traitement SIP multi-type
Ruiz et al. Multimedia Control Protocols for Wireless Networks
Ajagbe Video over Internet

Legal Events

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

Ref document number: 200780100643.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07816399

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07816399

Country of ref document: EP

Kind code of ref document: A1