WO2007082493A1 - Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session - Google Patents

Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session Download PDF

Info

Publication number
WO2007082493A1
WO2007082493A1 PCT/CN2007/000249 CN2007000249W WO2007082493A1 WO 2007082493 A1 WO2007082493 A1 WO 2007082493A1 CN 2007000249 W CN2007000249 W CN 2007000249W WO 2007082493 A1 WO2007082493 A1 WO 2007082493A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
network entity
network
processing
sip message
Prior art date
Application number
PCT/CN2007/000249
Other languages
English (en)
Chinese (zh)
Inventor
Lei Zhu
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007082493A1 publication Critical patent/WO2007082493A1/fr

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/10—Architectures or entities
    • H04L65/1046—Call controllers; Call servers
    • 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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]

Definitions

  • the present invention relates to a technique for processing a Session Initiation Protocol (SIP) message in a mobile communication system, and more particularly to a method and a network entity for processing content in a SIP message.
  • SIP Session Initiation Protocol
  • mobile communication systems are not limited to traditional voice communication, but can also combine various media services such as audio, video, pictures and text.
  • Multiple media services The combination of data services such as presence, short message, web browsing, location information, push service (PUSH) and file sharing can meet the diverse needs of user terminals.
  • data services such as presence, short message, web browsing, location information, push service (PUSH) and file sharing can meet the diverse needs of user terminals.
  • PUSH push service
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • IMS In the 3GPP Release 5 (R5 Release) phase, IMS is introduced, which is superimposed on the packet domain network, by Call Control Function (CSCF), Media Gateway Control Function (MGCF), Media Resource Function (MRF), and Home Subscriber Server. (HSS) and other functional entities.
  • the CSCF can be divided into three logical entities: the service CSCF (S-CSCF), the proxy CSCF (P-CSCF), and the query CSCF (I-CSCF).
  • S-CSCF is a service switching center of the IMS, performs session control, maintains session state, is responsible for managing user terminal information, and generates charging information.
  • the P-CSCF is an access point for the UE to access the IMS, completes user terminal registration, and is responsible for services.
  • I-CSCF Quality (QoS) control and security management
  • I-CSCF is responsible for interworking between IMS domains, Manage the allocation and selection of the S-CSCF, hide the network topology and configuration, and generate billing data.
  • the MGCF controls the gateway to implement interworking between the IMS and other networks.
  • MRF provides media resources.
  • the HSS stores subscription data and configuration information of the user terminal.
  • the IMS network defined by 3GPP can also be applied to the packet network defined in 3GPP2 to provide interworking with multi-scale type networks, and realize the independence of using and using user terminal types. Therefore, the IMS network is not limited to be applied to 3GPP related networks and applications, and other types of access networks and network-enabled services and applications can also be implemented by using the IMS architecture.
  • SIP is an IP telephony signaling protocol proposed by the Internet Engineering Task Force (IETF). SIP is used to initiate a session, which can control the establishment and termination of multimedia sessions attended by multiple participants, and can dynamically adjust and modify session attributes such as session bandwidth requirements, media types (voice, video, text, etc.), media Codec format, support for multicast and unicast, etc.
  • session attributes such as session bandwidth requirements, media types (voice, video, text, etc.), media Codec format, support for multicast and unicast, etc.
  • the SIP protocol is used as the signaling control protocol for IP multimedia sessions.
  • the addition of content in a SIP message by a network entity in an IMS network is considered to be an achievable technology, but there is no technology for processing the content added in the SIP message, which may result in a network entity in the IMS network.
  • the contents of the SIP message cannot be processed.
  • the network entity in the IMS network cannot record the result of the content in the processed SIP message and send it to the network entity in other IMS networks that need to record the result of the processing.
  • Embodiments of the present invention provide a method for processing content in a SIP message, which enables a network entity in an IMS network to process content in a SIP message.
  • the embodiment of the present invention further provides a network entity that processes content in a SIP message, and the network entity enables a network entity in the IMS network to process content in the SIP message.
  • a method for processing content in a Session Initiation Protocol SIP message comprising: a network entity of an Internet Protocol IMS network based on an Internet Protocol to process content in a SIP message according to a set operation policy.
  • a network entity for processing content in a SIP message comprising: a receiving module and a content parsing module, where
  • the receiving module is configured to send the SIP message carrying the content to the content parsing module;
  • the content parsing module is configured to process the content carried by the SIP message by using an operation policy.
  • the network entity in the IMS network receives, deletes, unrecognizable, unsupported, or/and does not respond to the content in the SIP message according to the operation policy, and the operation policy may be advanced. It is stored on its own or from network entities of other IMS networks, so that the network entities in the IMS network process the content in the SIP message. Therefore, the method and the network entity provided by the embodiments of the present invention can enable the network entity in the IMS network to process the content in the SIP message. BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a flowchart of a method 1 for processing content in a SIP message according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method 2 for processing content in a SIP message according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method according to an embodiment of the present invention
  • the network entity in the IMS network processes the content in the SIP message according to the operation policy, such as receiving, deleting, unrecognized, unsupported, or/and non-responsive.
  • the operational policy is pre-stored in the network entity of the IMS network or the network entity of the IMS network is obtained from other network entities storing the operational policy.
  • the content in the SIP message can be an index of media content or media content. The media content is used to provide some information about the session to the consumer of the SIP message or to provide the media in the SIP message.
  • the index of the media content is used to find a network entity storing the media content for the user of the SIP message, and obtain the media content stored by the entity.
  • the content of the SIP message is the media content
  • the media content is carried in the message header or the message body of the SIP message; when the content in the SIP message is the index of the media content, the index of the media content is carried in the SIP message. In the header or message body.
  • the processing result of the content in the SIP message by the network entity in the IMS network does not affect the SIP message itself.
  • the deletion of the media content in the SIP message does not trigger the rejection of the SIP message.
  • the network entity in the IMS network may also record the result of processing the content in the SIP message, and send the result record to other network entities in the IMS network for reference.
  • the network entity in the IMS network records the result of processing the content in the SIP message, and can record one result of the final processing, and can also record all the multiple results processed.
  • a result history of the contents of the SIP message is formed, which may also be referred to as a processing log.
  • the result record may be carried in the message body of the SIP message or in the message header of the SIP message. , sent to other network entities in the IMS network.
  • the processing log may be sequentially numbered in the message body of the SIP message or in the message header, and sent to other networks in the IMS network. Body.
  • the network entity in the IMS network sends the record of the result of processing the content in the SIP message to other network entities in the IMS network, it may be sent by the network entity in the IMS network, or may be in the IMS network. Other network entities are required to send.
  • the network entity in the IMS network may also be determined according to a policy, which is pre-stored in its own or acquired from other network entities in the IMS network. .
  • the network entity in the IMS network may be a user terminal, or a device that is deployed in the network and serves as a user terminal in a session; the network entity in the IMS network may also be a CSCF, an application server (AS). ), Media Resource Function (MRF), SIP-based Application Layer Gateway (SIP-ALG), Media Gateway Control Function (MGCF), Outbound Border Gateway Control Function (BGCF), or Media Gateway (MGW).
  • MRF Media Resource Function
  • SIP-ALG SIP-based Application Layer Gateway
  • MGCF Media Gateway Control Function
  • BGCF Outbound Border Gateway Control Function
  • MGW Media Gateway
  • client A (Client A) establishes a session with client B (Client B) through AS#A and AS#B, and Client A is in a SIP message.
  • the added content is the media component.
  • AS#A and AS #B want to process the media components in the SIP message. The specific steps are as follows:
  • Step 100 Client A sets a SIP message, that is, an access (INVITE) request, and the request carries the media content 1#, such as a piece of text and an image.
  • a SIP message that is, an access (INVITE) request
  • the request carries the media content 1#, such as a piece of text and an image.
  • the SIP message set by Client A may also be other requests, such as a SIP MESSAGE request.
  • Step 101 Client A sends the set INVITE request to AS#A.
  • Step 102 The AS#A processes the media content 1# in the INVITE request according to the operation policy, for example, according to the operation policy or the configuration information of the user terminal on the server, receives the media type supported by the media type and deletes the media type that is not supported. In this embodiment, if the operation policy does not support the image, the image can be deleted from the media content 1 #.
  • AS#A After processing the media content 1 #, the media content 2 # is obtained, and the result of the processing is stored as a record in the AS.
  • the operation policy can be stored in AS#A in advance, or can be obtained from AS#A to other network entities.
  • the operation policy can be the policy of the operator, the setting policy of the user terminal, or the subscription policy of the user.
  • Step 103 AS#A forwards the INVITE request to AS#B, and the request carries the processed media content 1#, that is, carries the media content 2#.
  • Step 104 After receiving the 11 ⁇ 1 request for the media content 2#, the AS#B processes the media content 2# in the INVITE request according to the operation policy, for example, according to the operation policy or the user terminal on the server. Configuration information, receiving the media type it supports and deleting the media type it does not support. In this embodiment, it is assumed that the media content 2# processed by AS#A3 ⁇ 4 line still contains a piece of text and an image, if the As operation policy is not Support for images, you can delete images from media content 2 #. AS#B obtains the media content 3# after processing the media content 2#, and stores the result of the processing as a record in AS#B.
  • the operation policy for example, according to the operation policy or the user terminal on the server.
  • Configuration information receiving the media type it supports and deleting the media type it does not support.
  • AS#B obtains the media content 3# after processing the media content 2#, and stores the result of the processing as a record in AS#B.
  • the operational strategy of this step may be the same as or different from the operational strategy of step 102.
  • the operation policy of this step may be pre-stored in AS#B, or may be obtained from other network entities, and the operation policy may be an operator's policy, a user terminal setting policy, or a user's subscription policy. .
  • Step 105 AS#B forwards the INVITE request to Client B, and the request carries the processed media content 2 # , that is, carries the media content 3 #.
  • Step 106 After receiving the INVITE request carrying the media content 3 #, the client B uses the media content 3 # carried by the request, and uses the result of the client B using the media content 3 # as a processing record to be carried in the response message.
  • the response message may be a success response message, and may also be Unanswered message.
  • the response message may be an intermediate response message or a final response message.
  • Step 107 Client B sends a response message to AS#B. After receiving the response message, AS #B carries the stored processing result record of media content 2# in the response message.
  • Step 108 AS #B sends a response message to AS#A, where the response message carries the processing result record of the media content 3# by the client B and the processing result record of the media content 2# by the AS#B, and the AS#A receives the response. After the message, the stored processing result record of the media content 1 # is carried in the response message.
  • Step 109 The AS #A sends a response message to the client A, where the response message carries the processing result record of the media content 3# by the client B, the processing result record of the AS #B to the media content 2#, and the AS #A pair of the media content 1 # ⁇ .
  • Client A can obtain the result record of the processing of the media content by each network entity. .
  • AS # A or / and AS #B may not store the processing result record of the media content, but carry the processing result record of the media content in the INVITE request, send it to Client B, and then receive it.
  • the client B to the INVITE request carries the processing result of the media content and the processing result record of the eight 8 #8 or/and the eight 8 pairs of media content carried in the INVITE request are carried in the response message through As and AS #A.
  • 8 # ⁇ / ⁇ 8#8 can also carry the processing result record of the media content in the SIP message and send it to Client B, which is referenced by Client B.
  • the content of the SIP message may also be processed by using the method described in the embodiment of the present invention.
  • the PoC server provides the PoC service for the user terminal as an AS in the IMS platform.
  • a PoC server which can be a PoC Server (Controlling) and a PoC Server (Parting).
  • a SIP message is received, it can be The content in the SIP message is processed and the processing result record is generated according to the processing result, and the processing result record is sent to other network entities in the IMS network.
  • FIG. 2 is a flowchart of a method 2 for processing content in a SIP message according to an embodiment of the present invention, where Client A establishes a session with Client B through a PoC Server (Controlling) and a PoC Server (Parting), and the content added by Client A in the SIP message is The media component, PoC Server (Controlling) and PoC Server (Parting), are to process the media components in the SIP message.
  • the specific steps are as follows:
  • Step 200 Client A sets a SIP message, that is, an INVITE request, and the request carries media content 1 # , such as a piece of text and an image.
  • media content 1 # such as a piece of text and an image.
  • the SIP message set by Client A may also be other requests, such as a SIP MESSAGE request.
  • Step 201 Client A sends the set INVITE request to the PoC Server (Controlling).
  • Step 202 The PoC Server (Controlling) processes the media content 1# in the INVITE request according to the operation policy.
  • the media type supported by the INVITE request may be received according to the operation policy, and the media type that it does not support is deleted. In this embodiment, the hypothesis is assumed. If the operation strategy does not support images, the image can be deleted from the media content 1 #.
  • the AS#A obtains the media content 2# after processing the media content 1#, and carries the processed result as a processing result record in the INVITE request.
  • the operation policy can be pre-stored in the PoC Server (Controlling) or from the PoC Server (Controlling) to other network entities.
  • the operation policy can be the operator's policy, the user terminal's setting policy, or the user's subscription policy.
  • Step 203 The PoC Server (Controlling) forwards the INVITE request to the PoC Server (Parting), where the request carries the processed media content 1 # , that is, carries the media content 2 # and records the processing result of the media content 1 #.
  • Step 204 The PoC Server (Parting) receives the media content 2# and the pair After the INVITE request of the processing result of the media content 1 #, the media content 2 # in the INVITE request is processed according to the operation policy, for example, the media type supported by the INVITE request can be received according to the operation policy, and the media type that is not supported is deleted.
  • the processed media content 2# of AS#A still contains a piece of text and an image. If the AS#B operation policy does not support the image, the image can be deleted from the media content 2#.
  • the media content 3 # is obtained, and the result of the processing is carried as a processing result record in the INVITE request.
  • the operational strategy of this step may be the same as or different from the operational strategy of step 202.
  • the operation policy of this step may be pre-stored in the PoC Server (the Participating), or may be obtained by the PoC Server (the Participating) to other network entities.
  • the operation policy may be the policy of the operator, the setting policy of the user terminal, or User's signing strategy, etc.
  • Step 205 The PoC Server (the Participating) forwards the INVITE request to the Client B, where the request carries the processed media content 2#, that is, the carrying media content 3#, the processing result record of the media content 1#, and the processing of the media content 2# Record of results.
  • Step 206 After receiving the media content 3 #, the processing result record of the media content 1 #, and the INVITE request for the processing result of the media content 2 #, the client B uses the media content 3 # carried by the request to connect the client B.
  • the result of using the media content 3 # as a processing result record is carried in the response message, and the processing result record of the media content 1 # and the processing result record of the media content 2 # are also carried in the response message.
  • Steps 207 - 209 Client B sends the response message to Client A through PoC Server (Parting) and PoC Server (Controlling).
  • Client A can obtain the processing result record of the media content by each network entity.
  • PoC Server Parting or / and PoC Server (Controlling) can also store the result of processing the media content in itself, until the network that received the last hop is received.
  • the processing result of the media content is added to the response message and then sent to the network entity of the next hop, so that the client A obtains the processing result record of the media content by each network entity.
  • the PoC Server Parting or / and PoC Server (Controlling) can also carry the record of the processing result of the media content in the SIP message and send it to Client B for reference by Client B.
  • the content in the SIP message provides information about the participating user terminals participating in the session, or provides relevant information about the session, and the information does not conflict with the result of the session process to be reached by the SIP message, therefore,
  • the method provided by the embodiment of the present invention does not affect the SIP message itself by processing the content in the SIP message.
  • the embodiment of the present invention may also send a processing result record of the content of the SIP entity in the SIP message to other network entities in the IMS network.
  • the embodiment of the present invention further provides a network entity for processing content in a SIP message, as shown in FIG. 3: the entity includes a receiving module and a content parsing module, where
  • the receiving module is configured to send the SIP message carrying the content to the content parsing module;
  • the content parsing module is configured to process content carried by the SIP message.
  • the content processing may be performed according to the set operation policy.
  • the network entity further includes an operation policy setting module, configured to provide an operation policy to the content parsing module, and the content parsing module performs processing for receiving Processing, deletion, unrecognized, ability not supported, or/and no response.
  • the network entity may further include a sending module and a result recording module, where
  • a content parsing module configured to send a processing result of the content carried by the SIP message to the result recording module
  • a result recording module configured to receive a processing result sent by the content parsing module, perform recording, and send the result record to the sending module
  • a sending module configured to send a result record received from the result recording module.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un procédé et une entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session. Le procédé comprend: le traitement par l'entité de réseau basée sur un sous-système multimédia IP (IMS) du contenu de message de protocole d'ouverture de session selon la stratégie du fournisseur. L'entité de réseau comporte: un module de réception pour la réception du message de protocole d'ouverture de session portant le contenu, sa transmission à un module d'analyse de contenu; un module d'analyse de contenu, pour le traitement du contenu du message de protocole d'ouverture de session selon la stratégie de fournisseur. Ledit procédé et ladite entité selon l'invention peuvent rendre disponible le contenu du message de protocole d'ouverture de session.
PCT/CN2007/000249 2006-01-23 2007-01-23 Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session WO2007082493A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610001983.6A CN101009664B (zh) 2006-01-23 2006-01-23 一种处理会话初始化协议消息中内容的方法及网络实体
CN200610001983.6 2006-01-23

Publications (1)

Publication Number Publication Date
WO2007082493A1 true WO2007082493A1 (fr) 2007-07-26

Family

ID=38287278

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000249 WO2007082493A1 (fr) 2006-01-23 2007-01-23 Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session

Country Status (2)

Country Link
CN (1) CN101009664B (fr)
WO (1) WO2007082493A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1421083A (zh) * 1999-11-08 2003-05-28 Mci全球通讯公司 互联网协议电话话音/视频消息存放和检索
US20050015499A1 (en) * 2003-05-15 2005-01-20 Georg Mayer Method and apparatus for SIP user agent discovery of configuration server
WO2005039132A1 (fr) * 2003-10-17 2005-04-28 Nokia Corporation Systeme, appareil et procede pour etablir des transmissions a commutation de circuits par transmission dans des reseaux a commutation de paquets
CN1620046A (zh) * 2003-11-17 2005-05-25 国际商业机器公司 用于VoIP呼叫控制的SIP消息的区别处理
EP1583312A1 (fr) * 2004-04-02 2005-10-05 France Telecom Appareils et méthode pour contrôler l'accès à un système multimédia IP à partir d'un serveur d'applications
EP1619854A1 (fr) * 2004-07-21 2006-01-25 Siemens Mobile Communications S.p.A. Message SIP étendue pour un service utilisant des poussoirs de régarder

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1243432C (zh) * 2003-06-26 2006-02-22 中国科学院计算技术研究所 一种ip视频电话系统会话和媒体授权方法
US20050124365A1 (en) * 2003-12-05 2005-06-09 Senaka Balasuriya Floor control in multimedia push-to-talk

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1421083A (zh) * 1999-11-08 2003-05-28 Mci全球通讯公司 互联网协议电话话音/视频消息存放和检索
US20050015499A1 (en) * 2003-05-15 2005-01-20 Georg Mayer Method and apparatus for SIP user agent discovery of configuration server
WO2005039132A1 (fr) * 2003-10-17 2005-04-28 Nokia Corporation Systeme, appareil et procede pour etablir des transmissions a commutation de circuits par transmission dans des reseaux a commutation de paquets
CN1620046A (zh) * 2003-11-17 2005-05-25 国际商业机器公司 用于VoIP呼叫控制的SIP消息的区别处理
EP1583312A1 (fr) * 2004-04-02 2005-10-05 France Telecom Appareils et méthode pour contrôler l'accès à un système multimédia IP à partir d'un serveur d'applications
EP1619854A1 (fr) * 2004-07-21 2006-01-25 Siemens Mobile Communications S.p.A. Message SIP étendue pour un service utilisant des poussoirs de régarder

Also Published As

Publication number Publication date
CN101009664A (zh) 2007-08-01
CN101009664B (zh) 2010-08-11

Similar Documents

Publication Publication Date Title
CN100362807C (zh) 一种实现网际协议多媒体子系统中用户注册的方法
JP4500852B2 (ja) 端末の機能変更をネットワークに通知する方法
JP4493104B2 (ja) ホーム加入者サーバのインターフェイス負荷を軽減する方法
US7792116B2 (en) Method and device for interworking between internet protocol networks
US8401005B2 (en) Session initiation protocol message content processing method and network
WO2006136106A1 (fr) Procede et systeme d'authentification de terminal d'usager
WO2006136097A1 (fr) Procédé pour traiter une anomalie lors de la procédure d'inscription d'un utilisateur
WO2008049326A1 (fr) Enregistrement de dispositif d'utilisateur, système d'activation, procédé et dispositif dans la gestion de réseau privé
WO2007068206A1 (fr) Procede et reseau de mise en marche d'informations concernant la capacite de session
EP2034688A1 (fr) Méthode et dispositif de transmission d'un message de demande dans un système multimédia
WO2007095855A1 (fr) Procédé et entité réseau de négociation d'un paramètre de type média
WO2009049518A1 (fr) Procédé, système et entité d'établissement de session de système de télévision par internet ip
WO2008080297A1 (fr) Procédé, équipement et système pour mettre en rapport une session
CN100499670C (zh) 一种在注册过程中确定服务呼叫控制功能的方法
WO2009121310A1 (fr) Procédé, système, et dispositif, permettant de sélectionner une passerelle
WO2007140699A1 (fr) Procédé et appareil de mise à jour des données signées d'abonné
WO2008086744A1 (fr) Procédé de mise en œuvre d'établissement d'appel, système et élément de réseau de contrôle d'appel
WO2008080349A1 (fr) Dispositif utilisateur, entité de fonction de commande de session d'appel de service et procédé d'enregistrement du dispositif utilisateur
WO2008119278A1 (fr) Procédé, terminal et dispositif réseau pour le changement d'état de domaine à commutation de paquets
WO2007082493A1 (fr) Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session
WO2014187252A1 (fr) Procédé et appareil de traitement adaptatif de session concomitante dans un réseau ims
WO2006032204A1 (fr) Procede pour permettre une communication dans les serveurs d’application
WO2008113272A1 (fr) Procédé, système et dispositif de déclenchement de service
WO2008125063A1 (fr) Procédé, système et appareil de route appelée

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07702178

Country of ref document: EP

Kind code of ref document: A1