+

WO2010054695A1 - Procédé et appareil à utiliser dans un réseau de communications - Google Patents

Procédé et appareil à utiliser dans un réseau de communications Download PDF

Info

Publication number
WO2010054695A1
WO2010054695A1 PCT/EP2008/065617 EP2008065617W WO2010054695A1 WO 2010054695 A1 WO2010054695 A1 WO 2010054695A1 EP 2008065617 W EP2008065617 W EP 2008065617W WO 2010054695 A1 WO2010054695 A1 WO 2010054695A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
message
ims
relating
store
Prior art date
Application number
PCT/EP2008/065617
Other languages
English (en)
Inventor
Mats Stille
Staffan Blau
Jonas FALKENÅ
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2008/065617 priority Critical patent/WO2010054695A1/fr
Publication of WO2010054695A1 publication Critical patent/WO2010054695A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • 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/50—Network services
    • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • 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]
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to a method and apparatus for use in a communications network, for example a Universal Mobile Telecommunications System having an IP Multimedia Subsystem.
  • IP Multimedia services provide a dynamic combination of voice, video, messaging, data, etc. within the same session.
  • the number of services offered to the end users will grow, and the inter-personal communication experience will be enriched. This will lead to a new generation of personalised, rich multimedia communication services, including so-called "combinational IP Multimedia" services.
  • the UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • the UMTS architecture includes a subsystem known as the IP Multimedia Subsystem (IMS) for supporting traditional telephony as well as new IP multimedia services (3GPP).
  • IMS IP Multimedia Subsystem
  • IMS provides key features to enrich the end-user person-to-person communication experience through the use of standardised IMS Service Enablers, which facilitate new rich person-to-person (client-to-client) communication services as well as person-to-content (client-to-server) services over IP-based networks.
  • the IMS is able to connect to both PSTN/ISDN (Public Switched Telephone Network/Integrated
  • the IMS makes use of the Session Initiation Protocol (SIP) to set up and control calls or sessions between user terminals (or user terminals and application servers).
  • SIP Session Initiation Protocol
  • SDP Session Description Protocol
  • SIP was created as a user-to- user protocol
  • IMS allows operators and service providers to control user access to services and to charge users accordingly.
  • the 3GPP has chosen SIP for signalling between a User Equipment (UE) and the IMS as well as between the components within the IMS.
  • UE User Equipment
  • Incoming IMS border gateway control functions validate the originating operator address domain against a white-list of IMS inter-connected operators to determine whether the communication can be allowed.
  • a method of controlling the provision of IP Multimedia Subsystem, IMS, services between first and second IMSs operated by first and second different respective operators comprising at a border control function between the first and second IMSs: (a) maintaining a store of information relating to a plurality of service agreements reached between the first and second operators, the service agreements relating to respective services provided between the first and second IMSs; (b) receiving a message relating to a service; (c) determining with reference to the store of information the extent to which the service is an allowed service; and (d) processing the message in dependence upon the determination.
  • the message received in step (b) may comprise a service request message.
  • Step (d) may comprise allowing or disallowing the requested service in dependence upon the determination made in step (c).
  • the service request message may comprise a SIP service request message, and step (c) may comprise using the Accept-Contact header of the SIP service request message to identify the service.
  • the message received in step (b) may comprise a Presence notification message, and step (c) may comprise determining from the store which parts of the Presence information being notified are allowed.
  • Step (d) may comprise filtering out those parts of the Presence information not allowed and forwarding those parts that are.
  • the Presence notification message may comprise a SIP NOTIFY message.
  • the method may comprise using a feature tag according to RFC 3840/41 to identify the service.
  • the border control function may be a 3GPP Interconnection Border Control Function, IBCF.
  • an apparatus for use as or in a border control function between first and second IP Multimedia Subsystems operated by first and second different respective operators comprising: (a) means for maintaining a store of information relating to a plurality of service agreements reached between the first and second operators, the service agreements relating to respective services provided between the first and second IP Multimedia Subsystems; (b) means for receiving a message relating to a service; (c) means for determining with reference to the store of information the extent to which the service is an allowed service; and (d) means for processing the message in dependence upon the determination.
  • the border control function above need not be physically located between the two IMSs but need only act in some function as a pass-through for certain communications between the two IMSs.
  • the border control function above may in fact be any suitable node, and not necessarily one having a border control function, and may in fact be located clearly within one or other of the IMSs rather than being considered as situated at or near a border between the IMSs.
  • the "border control function" above should read as including such nodes as a Presence server, at least in the case where the service relates to the provision of Presence information.
  • a program for controlling an apparatus to perform a method according to the first aspect of the present invention or which, when loaded into an apparatus, causes the apparatus to become an apparatus according to the second aspect of the present invention may be carried on a carrier medium.
  • the carrier medium may be a storage medium.
  • the carrier medium may be a transmission medium.
  • an apparatus programmed by a program according to the third aspect of the present invention.
  • Figure 1 is a flowchart illustrating a method according to an embodiment of the present invention.
  • Figure 2 is a schematic block diagram illustrating an apparatus according to an embodiment of the present invention.
  • a solution according to an embodiment of the present invention is to have a white-list function at the incoming border control function of an IMS network, known as an Interconnection Border Control Function (IBCF) in 3GPP terminology, that is based on IMS services rather than (or in addition to) being based on IMS operators.
  • IBCF Interconnection Border Control Function
  • a solution according to an embodiment of the present invention allows an IMS inter-connect agreement to be maintained between two operators for some IMS services but not for other IMS services.
  • the IBCF would have the standard white- list, with the respective addresses of the operators with whom there is an IMS interconnect agreement. Beyond this, however, the IBCF (or other node at the discretion of the local implementation) would have a white-list on a per-IMS-service basis.
  • An IMS service is identified by a feature tag (RFC 3840/41 ). This is included in the Accept-Contact header of the initial SIP message that is sent when the IMS-service is invoked. The identifier is unique as per IMS service, and is normally described in the specification of the IMS service in particular.
  • the IMS service 'Messaging' (by OMA IM) is identified by a feature tag +g.oma.sip-im, while the IMS service 'push-to-talk' is identified by a feature tag +g.poc.talkburst.
  • a receiving portion P1 of an operator's IBCF receives an initial SIP message (such as a SIP INVITE message) from another operator with whom there is an IMS subscription.
  • an initial SIP message such as a SIP INVITE message
  • a tag identification portion P2 of the IBCF identifies the requested service with reference to the tag included in the SIP message.
  • a look-up portion checks the service identity tag carried in the Accept-contact header against a white-list of agreed services in the tag store P6, and a decision portion P5 determines whether or not the requested service is an allowed service based on the look-up.
  • the IBCF treats it as allowed for further processing in the IMS core network (step S4), due to it finding a matching result in the IMS services whitelist for "+g.oma.sip-im".
  • the IBCF will find a match for the operator address but will find a non- match on the IMS service, because "+g.3gpp.icsi_ref:"urn.3gpp. service. ims.icsi.mmtel”" is a feature tag that is not in the IMS service white-list data store of the IBCF.
  • the decision portion P5 of the IBCF rejects the INVITE e.g. with SIP 403 Forbidden message sent by the sending portion P4, and possibly a Reason header with "service not allowed” to make it clear to the originating operator what the reason for failure was.
  • the reason why the IBCF does not have the service identity +g.3gpp.icsi_ref:"urn.3gpp. service. ims.icsi.mmtel” in its data store could be either that the operator has not launched the service among his own subscribers, or that the operator do have launched the same service, but is yet in termination fee agreements negotiations with the inter-connected IMS operator with will take months to settle.
  • IMS based information service like OMA Presence.
  • Presence agreement it would not necessarily mean that all presence data attributes are agreed on.
  • operator B could have a service data filter set up with operator A. This filter may be configured to discard for example the 'note' tuplet (free text) or capability information ('service-id' tuplet in Presence terminology).
  • the filter would be activated every time there is an incoming Presence notification (SIP NOTIFY) received from another IMS network with which there is a Presence agreement, and/or when there are outgoing Presence notifications destined other networks with which there is a Presence service agreement.
  • SIP NOTIFY incoming Presence notification
  • the service data filtering need not be handled by the IBCF, but may in another embodiment be handled for example by a server inside the receiver network (such as the Presence server).
  • a black-list could be maintained instead of or as well as the white-list.
  • the black-list would indicate those services that are specifically not allowed.
  • operation of one or more of the above-described components can be controlled by a program operating on the device or apparatus.
  • Such an operating program can be stored on a computer-readable medium, or could, for example, be embodied in a signal such as a downloadable data signal provided from an Internet website.
  • the appended claims are to be interpreted as covering an operating program by itself, or as a record on a carrier, or as a signal, or in any other form.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention porte sur un procédé de commande de la fourniture de services de sous-système IP multimédia (IMS) entre des premier et second IMS exploités par des premier et second opérateurs respectifs différents, le procédé comportant, au niveau d'une fonction de contrôle en bordure ("border control function") entre les premier et second IMS : (a) le maintien d'une mémoire d'informations concernant une pluralité d'accords de service obtenus entre les premier et second opérateurs, les accords de service portant sur des services respectifs fournis entre les premier et second IMS; (b) la réception (S1) d'un message concernant un service; (c) la détermination (S2, S3) de la mesure dans laquelle le service est un service autorisé, en référence à la mémoire d'informations, et (d) le traitement (S4, S5) du message selon la détermination.
PCT/EP2008/065617 2008-11-14 2008-11-14 Procédé et appareil à utiliser dans un réseau de communications WO2010054695A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/065617 WO2010054695A1 (fr) 2008-11-14 2008-11-14 Procédé et appareil à utiliser dans un réseau de communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/065617 WO2010054695A1 (fr) 2008-11-14 2008-11-14 Procédé et appareil à utiliser dans un réseau de communications

Publications (1)

Publication Number Publication Date
WO2010054695A1 true WO2010054695A1 (fr) 2010-05-20

Family

ID=41113061

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/065617 WO2010054695A1 (fr) 2008-11-14 2008-11-14 Procédé et appareil à utiliser dans un réseau de communications

Country Status (1)

Country Link
WO (1) WO2010054695A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1619917A1 (fr) * 2003-04-11 2006-01-25 Matsushita Electric Industrial Co., Ltd. Systeme de communication et procede de communication
EP1718006A1 (fr) * 2004-09-08 2006-11-02 Huawei Technologies Co., Ltd. Sous-systeme de commande d'admission de ressources dans ngn et son procede
US20080034080A1 (en) * 2006-08-02 2008-02-07 Nokia Siemens Networks Gmbh & Co Policy translator - policy control in convergent networks
EP1956793A2 (fr) * 2006-12-29 2008-08-13 Ubiquity Software Corporation Systèmes et procédé pour connecter des réseaux hétérogènes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1619917A1 (fr) * 2003-04-11 2006-01-25 Matsushita Electric Industrial Co., Ltd. Systeme de communication et procede de communication
EP1718006A1 (fr) * 2004-09-08 2006-11-02 Huawei Technologies Co., Ltd. Sous-systeme de commande d'admission de ressources dans ngn et son procede
US20080034080A1 (en) * 2006-08-02 2008-02-07 Nokia Siemens Networks Gmbh & Co Policy translator - policy control in convergent networks
EP1956793A2 (fr) * 2006-12-29 2008-08-13 Ubiquity Software Corporation Systèmes et procédé pour connecter des réseaux hétérogènes

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
3GPP: "3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Inter-IMS Network to Network Interface;(Release 8)", 3GPP DRAFT; 29865-130_CL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Budapest; 20080828, 28 August 2008 (2008-08-28), XP050312151 *
ARLELLE PEARCE, TERJE JEILSELL AND JUDITH E. Y.: "Combining IMS and Web 2.0 - Assessing the Service Availability", August 2008 (2008-08-01), XP002548469, Retrieved from the Internet <URL:http://simula.no/research/networks/projects/RELAY/master-thesis-files/pearce-icin.pdf/view> *
JUDITH E. Y. ROSSEBØ, ARLELLE PEARCE, AND TERJE JEILSEN: "On Understanding Availability of Services Based on IP Multimedia Subsystem", XP002548470, Retrieved from the Internet <URL:http://simula.no/research/networks/projects/RELAY/master-thesis-files/pearce-itc.pdf/view> *
ROSENBERG DYNAMICSOFT H SCHULZRINNE COLUMBIA UNIVERSITY P KYZIVAT CISCO SYSTEMS J: "Caller Preferences for the Session Initiation Protocol (SIP); rfc3841.txt", IETF STANDARD, INTERNET ENGINEERING TASK FORCE, IETF, CH, 1 August 2004 (2004-08-01), XP015009619, ISSN: 0000-0003 *
SIMPLE WG J ROSENBERG DYNAMICSOFT: "A Presence Event Package for the Session Initiation Protocol (SIP); draft-ietf-simple-presence-09.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. simple, no. 9, 6 December 2002 (2002-12-06), XP015027630, ISSN: 0000-0004 *

Similar Documents

Publication Publication Date Title
KR101332891B1 (ko) 멀티미디어 서브시스템 서비스로의 그룹 액세스
US9900347B2 (en) Handling trust in an IP multimedia subsystem communication network
EP2456171B1 (fr) Appareil et procédé pour diriger une session de communication vers un dispositif de communication d&#39;un groupe de dispositifs ayant une identité d&#39;enregistrement commune
US9648048B2 (en) Message handling in an IP multimedia subsystem
US20120076136A1 (en) Methods and apparatus to provide a call-associated content service
US8463264B2 (en) Early IMS security
CA2605475C (fr) Ouverture de session a partir de serveurs d&#39;applications dans un sous-systeme multimedia ip
US9167008B2 (en) Traffic routing across and between networks
US9420018B2 (en) End-to-end address transfer
KR100928247B1 (ko) 통신 네트워크들 간의 보안 통신을 제공하기 위한 방법 및시스템
EP2293512B1 (fr) Rejet de communications malveillantes
CN101601252A (zh) 用于在ims网络中通过一组服务器提供网络服务的方法和设备
JP5069353B2 (ja) Ｉｐマルチメディア・サブシステム通信ネットワークにおいて信用性を処理するための方法および装置
WO2008095536A1 (fr) Procédé et appareil à utiliser dans un réseau de communication
WO2010054695A1 (fr) Procédé et appareil à utiliser dans un réseau de communications
EP3583757A1 (fr) Procédé de changement de réseau mobile
WO2013185795A1 (fr) Interdiction d&#39;appels
WO2013044988A1 (fr) Suppression d&#39;un appel de services camel pour le réacheminement d&#39;usagers

Legal Events

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

Ref document number: 08875321

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: 08875321

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载