WO2009056046A1 - Procédé de fin de session - Google Patents

Procédé de fin de session Download PDF

Info

Publication number
WO2009056046A1
WO2009056046A1 PCT/CN2008/072792 CN2008072792W WO2009056046A1 WO 2009056046 A1 WO2009056046 A1 WO 2009056046A1 CN 2008072792 W CN2008072792 W CN 2008072792W WO 2009056046 A1 WO2009056046 A1 WO 2009056046A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pcrf
server
value parameter
client
Prior art date
Application number
PCT/CN2008/072792
Other languages
English (en)
Chinese (zh)
Inventor
Shiyong Tan
Weihua Wei
Xiaoyan Shi
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 WO2009056046A1 publication Critical patent/WO2009056046A1/fr

Links

Classifications

    • 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/14—Session management

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, system, server, and client for terminating a session.
  • a session refers to a connection relationship between a user terminal (UE, User Equipment) and an external network, such as the Internet.
  • the connection relationship can be identified by the IP address of the UE or the identifier of the UE. For example, In an IP-Connected Access Network (IP-CAN), if an IP address is assigned to a terminal and can be recognized by an external network, an IP-CAN session is said to exist.
  • IP-CAN IP-Connected Access Network
  • FIG. 1 is a schematic diagram of a UE-initiated IP-CAN session and an AF session release process in the prior art.
  • FIG. 1 adopts a PCC architecture defined by the 3GPP, and mainly includes: an application function entity (AF, Application Function), and a gateway (GW, Gateway). Policy and Charging Enforcement Function (PCEF) and Policy Control and Charging Rules Function (PCRF).
  • PCEF Policy and Charging Enforcement Function
  • PCF Policy Control and Charging Rules Function
  • the PCRF is mainly used to determine the policy corresponding to the user's access to the network, the operator's policy, and the current policy of the user from the AF, and provide the determined policy to the PCEF.
  • the PCEF performs the PCRF delivery or The specified policy is provided.
  • the AF dynamically provides session information of the application layer to the PCRF, and the PCRF dynamically generates or modifies the corresponding rule according to the information.
  • the current method of terminating the session mainly includes the following steps:
  • Step 101 The PCEF receives the IP-CAN [tonal release request message] initiated by the UE.
  • the IP-CAN (Telecom Data Release) request message in the present step may be specifically a deletion request message for the last Packet Data Protocol (PDP) context for the Packet Radio System (GPRS).
  • Step 102 The PCEF sends a CCR (Credit-Control-Request) message to the PCRF to the PCRF.
  • CCR Clear-Control-Request
  • the PCEF sends a CCR message of the Diameter protocol, informing the PCRF to release the IP-CAN.
  • the interface between PCRF and PCEF is the Gx interface, which allows the PCRF to dynamically control the PCC rules enforced on the PCEF.
  • the Gx interface uses the Diameter protocol defined by the IETF.
  • Step 103 The PCRF searches for the binding correspondence between the IP-CAN ⁇ tongue and the AF ⁇ tongue.
  • Step 104 The PCRF sends a CCA (Credit-Control- Answer) message to the PCEF.
  • CCA Clear-Control- Answer
  • Step 105 The PCEF sends an IP-CAN [tonal release response message" to the UE.
  • the IP-CAN session release response message in this step may be specifically for the GPRS to delete the PDP context response message of step 101.
  • Step 106 The PCRF sends an Abort-Session-Request (ASR) message to the AF.
  • ASR Abort-Session-Request
  • the PCRF acts as a server and sends an ASR message of the Diameter protocol to the AF as the client to request termination.
  • the interface between the AF and the PCRF is an Rx interface, which is used by the AF to deliver application layer related information.
  • the Rx interface also uses the Diameter protocol defined by the IETF.
  • the Diameter protocol belongs to the protocol of the client server mode.
  • the Diameter client and the Diameter server can exchange a series of information, and a series of information interactions from initiation to termination is called a Diameter session.
  • the termination of the Diameter session is completely determined by the Diameter client.
  • the Diameter server can issue the termination session request first. When the Diameter client agrees to terminate the request, it will respond to the termination response, and then the Diameter client will issue a session termination request.
  • the Diameter server ends the user session, otherwise the session is still maintained.
  • Step 107 The AF sends a terminate session response (ASA, Abort-Session-Answer) message to the PCRF.
  • ASA terminate session response
  • the AF sends an ASA message of the Diameter protocol to the PCRF as a response to the ASR message of the Diameter protocol.
  • Step 108 The AF sends a session termination request (STR, Session-Termination-Request) message to the PCRF.
  • STR Session-Termination-Request
  • the AF sends an STR message of the Diameter protocol to the PCRF, informing the PCRF to terminate the AF session.
  • Step 109 The PCRF sends a STA (Session, Session-Termination- Answer) message to the AF.
  • STA Session, Session-Termination- Answer
  • the PCRF sends the STA message of the Diameter protocol to the AF to the AF, and the AF ⁇ tongue terminates.
  • an IP-CAN session is terminated by deleting all PDP contexts.
  • the ASR/ASA message of the Diameter protocol and the STR/STA can also be used on the Gx interface between the PCRF and the PCEF. Message to release the IP-CAN session.
  • the PCEF acting as the Diameter client may not initiate the session release process after receiving the ASR message. Therefore, when the PCRF fails or the device management needs to release the session, the PCEF cannot release the IP-CAN tongue in time.
  • the current method of terminating the session cannot indicate the reasons for terminating the session, and the user experience is poor.
  • Embodiments of the present invention provide a method for terminating a session, which can improve a terminating session mechanism, thereby enhancing a user experience.
  • Embodiments of the present invention also provide a system for terminating a session, which system can improve the termination session mechanism, thereby enhancing the user experience.
  • Embodiments of the present invention additionally provide a server that can improve the termination session mechanism, thereby enhancing the user experience.
  • An embodiment of the present invention further provides a client, which can improve the termination session mechanism, And enhance the user experience.
  • the technical solution of the embodiment of the present invention is specifically implemented as follows: the client receives a request message from the server that carries the extended cause value parameter, and the client obtains the cause value parameter from the request message. Instructing the server to terminate the session based on the extended cause value parameter.
  • a system for terminating a tongue comprising:
  • a server configured to send a request message carrying an extended cause value parameter
  • the client configured to obtain the cause value parameter from the request message sent by the server, and instruct the server to terminate the tongue according to the cause value parameter.
  • a server comprising:
  • a receiving module configured to receive a session termination indication from the client
  • a sending module configured to send a request message carrying an extended cause value parameter, where the extended cause value parameter indicates that the user service quality requirement cannot be met due to a PCRF failure, a device management change, a user subscription change, a PCEF failure, or a session release
  • the AF session is released due to the release of the IP-CAN session.
  • a client said client includes:
  • Obtaining an ear parameter for obtaining a reason value parameter indicating that the user service quality requirement cannot be satisfied due to a PCRF failure, a device management reason, a user subscription change, a PCEF failure, or a request due to IP-CAN The cause value parameter of the release of the tongue resulting in AF release of the tongue;
  • a processing module configured to instruct the server to terminate the session according to the reason value parameter obtained by the obtaining module.
  • the method, the system, the server, and the client of the session termination provided by the embodiment of the present invention can indicate the PCRF failure, the device management, or the user subscription, and the QoS is not satisfied by extending the cause value parameter carried in the protocol message.
  • the reason for the termination so that the corresponding processing can be performed in time according to the reason, the termination session mechanism can be improved, and the user experience is enhanced.
  • FIG. 1 is a schematic flowchart of a method for terminating a session adopted in the prior art
  • FIG. 2 is a schematic flow chart of a method for terminating a tongue used in an embodiment of the present invention
  • 3 is a schematic flowchart of a method for terminating a session in a first embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a method for terminating a session in a second embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for terminating a session in a third embodiment of the present invention.
  • FIG. 6 is a schematic structural view of a device for terminating the tongue used in the embodiment of the present invention.
  • the method for terminating the session is: the client receives the ASR message from the server, and the ASR message carries the extended cause value parameter; the client obtains the cause value parameter from the ASR message, according to the The reason value parameter indicates that the server terminates the tongue.
  • FIG. 2 is a schematic flow chart of a method for indicating a reason for termination of a tongue according to an embodiment of the present invention. As shown in Figure 2, the following steps are specifically included:
  • Step 201 The client receives an ASR message from the server, where the ASR message carries an extended reason value parameter.
  • the client receives an ASR message from the server, and the ASR message may be
  • the ASR message of the Diameter protocol may also be an ASR message of other protocols, for example, an ASR message of the Radius protocol.
  • the ASR message in this step carries the extended cause value parameters including:
  • Device Management Reason Indicates the reason value parameter for IP-CAN session release due to device management requirements.
  • IP-CAN [SESSION- RELEASED]: Indicates the reason value parameter for the PCRF to release the AF session due to the release of the IP-CAN session.
  • Device management reason Indicates the need for device management The cause value parameter of the AF ⁇ tongue release to be caused.
  • QOS-CANNOT-BE-AUTHORISE It is mainly used to release the reason value parameter of the AF session when the user signing changes cannot meet the requirements of the user Qos.
  • SERVER_ MALFUNCTION Indicates the cause value parameter of the AF session release due to a failure of the PCRF.
  • PCEF_MALFUNCTION Indicates the cause value parameter for the AF session release due to a PCEF failure.
  • Step 202 The client obtains a cause value parameter from the ASR message, and according to the cause value parameter, instructs the server to terminate the session.
  • the reason for the termination of the tongue is indicated by carrying one of the above-mentioned cause value parameters.
  • the reason for the termination of the session is indicated.
  • the cause value parameter carried in the ASR message by extending the cause value parameter carried in the ASR message, it is possible to indicate a PCRF fault, a PCEF fault, a device management, or a user subscription change, and no longer satisfy the reasons for termination of multiple sessions such as QoS, thereby being able to
  • the corresponding processing is performed in time, for example, promptly instructing the PCRF to terminate the IP-CAN session or the AF session, thereby improving the termination mechanism and enhancing the user experience.
  • the following is a detailed description of several processes for terminating the session using the extended cause value parameter.
  • FIG. 3 is a schematic flowchart of a method for terminating a session in a first embodiment of the present invention.
  • the device management initiates an IP-CAN session and an AF session release application instance, that is, after the IP-CAN session between the PCEF and the PCRF and the AF session between the PCRF and the AF have been established, the device management on the PCRF needs to be released.
  • a user IP-CAN session and an AF session at which time the ASF message is sent by the PCRF to the PCEF and AF respectively to initiate the release of the IP-CAN session and the AF session.
  • the cause value parameters ADMINISTRATION- REASON ( 1 ) and ADMINISTRATION - REASON ( 3 ) that characterize the device management cause the tongue release are extended in the Diameter protocol message used by the Gx interface and the Rx interface. ).
  • Step 301 The PCRF sends a message carrying the characterization device management reason to the PCEF. ASR message due to value parameter.
  • the device management on the PCRF needs to release the user session connection, the PCRF sends the ASR message of the Diameter protocol to the PCEF, and the ASR message carries the Abort-Cause AVP, and takes the value as ADMINISTRATION-REASON ( 1), mainly indicating the release of IP-CAN sessions due to the need for device management.
  • Step 302 The PCEF sends an ASA message to the PCRF.
  • Step 303 The PCEF sends an STR message to the PCRF.
  • the PCEF uses the STR message to indicate that the PCRF releases the IP-CAN session according to the cause value parameter carried in the ASR message.
  • Step 304 The PCRF sends a STA message to the PCEF.
  • the PCRF sends a STA message to the PCEF.
  • Step 305 The PCRF determines the affected AF session according to the binding relationship.
  • Step 306 The PCRF sends an ASR message carrying the cause value parameter indicating that the device management causes the session release to the AF.
  • the PCRF sends an ASR message to the AF.
  • the message carries the Abort-Cause AVP, where the value is ADMINISTRATION- REASON ( 3 ), indicating that the PCRF releases the AF session due to device management.
  • Step 307 The AF sends an ASA message to the PCRF.
  • Step 308 The AF sends the STR message to the PCRF.
  • the AF uses the STR message to instruct the PCRF to release the AF ⁇ tongue according to the reason value parameter carried in the ASR message carrying.
  • Step 309 The PCRF sends a STA message to the AF.
  • the STA message is sent.
  • the PCEF can release the IP-CAN session in time after receiving the message.
  • FIG. 4 is a schematic flowchart of a method for terminating a session in a second embodiment of the present invention.
  • the PCRF failure causes an IP-CAN session and an AF session release application instance.
  • the PCRF needs to release a certain user IP-CAN ⁇ tongue and AF session.
  • the PCEF releases the IP-CAN session by sending the Diameter CCR to the PCRF to release the last IP-CAN bearer.
  • the cause value parameter characterizing the PCRF failure causing the tongue release is extended in advance in the Diameter protocol message used by the Gx interface and the Rx interface.
  • Step 401 The PCRF sends an ASR message carrying the cause value parameter indicating that the PCRF failure causes the session release to the PCEF.
  • the PCRF sends the Diameter protocol ASR message to the PCEF with the Abort-Cause AVP, where the value is
  • Step 402 The PCEF sends an ASA message to the PCRF.
  • Step 403 Release the IP-CAN bearer between the PCEF and the UE.
  • Step 404 The PCEF sends a CCR message to the PCRF.
  • the CCR message is used to instruct the PCRF to release the IP-CAN session.
  • Step 405 The PCRF sends a CCA message to the PCEF.
  • the PCRF after the IP-CAN session is released, the PCRF sends a CCA message to the PCEF.
  • Step 406 The PCRF determines the affected AF session according to the binding relationship.
  • Step 407 The PCRF sends an ASR message carrying the cause value parameter indicating that the PCRF fault causes the tongue release.
  • the PCRF sends an ASR message to the AF, and the message carries an Abort-Cause AVP, where the value is ADMINISTRATION-REASON (5), indicating that the PCRF releases the AF session because of a PCRF failure.
  • Steps 408 to 410 are the same as steps 307 to 309, and are not mentioned here.
  • the PCEF may also prompt the user for the reason for the termination of the session, such as "terminating the service due to failure", etc., and the PCEF may also count the reason for the termination of the tongue.
  • the PCEF by carrying the reason value parameter of the session release caused by the PCRF failure in the ASR message, the PCEF can release the IP-CAN session in time after receiving the message.
  • FIG. 5 is a schematic flow chart of a method for terminating a tongue according to a third embodiment of the present invention.
  • This embodiment is an example in which the change of the subscriber subscription information causes the IP-CAN session and the AF session to be released, assuming that the IP-CAN session and the AF session have been established.
  • the current IP-CAN bearer QoS and the subscription QoS are inconsistent.
  • the PCRF needs to release the user AF session and the affected IP-CAN bearer.
  • Step 501 User subscription information changes.
  • the user subscription information is changed, and the subscription information base (SPR) sends the updated subscription information to the PCRF.
  • the QoS in the new subscription information of the user is inconsistent with the subscription QoS in the current IP-CAN bearer. Different from the quality of service level (QCI), it may also not meet other QoS requirements.
  • the PCRF needs to release the AF session and the corresponding IP-CAN bearer, that is, release the corresponding bearer by deleting the PCC rule.
  • Step 502 The PCRF sends a re-authentication request (RAR, Re-Auth-Request) message to the PCEF, where the RAR message carries a cause value indicating that the PCRF failure causes the tongue to be released.
  • RAR re-authentication request
  • the RAR message carries a PCC rule that needs to be deleted.
  • Step 503 The PCEF sends a re-authentication response (RAA, Re-Auth- Answer) message to the PCRF.
  • RAA re-authentication response
  • the PCEF sends an RAA message to the PCRF.
  • Step 504 The PCEF initiates release of the IP-CAN bearer to the terminal.
  • Step 505 The PCEF sends a CCR message to the PCRF.
  • the CCR message is used to indicate the release of the IP-CAN bearer.
  • Step 506 The PCRF sends a CCA message to the PCEF.
  • Step 507 The PCRF determines the affected AF session according to the binding relationship.
  • Step 508 The PCRF sends an ASR message to the AF.
  • the ASR message sent by the PCRF carries the reason value parameter indicating that the user's service quality requirement cannot be satisfied due to the user subscription change: QOS—CANNOT—BE – AUTHORISE ( 2 ), indicating that the user's IP-CAN session is released when the user's subscription change fails to meet the user's QoS requirements.
  • Steps 509 to 511 are the same as steps 307 to 309, and are not mentioned here.
  • the reason value parameter indicating that the session is released due to the failure to satisfy the user service quality requirement due to the user subscription change is carried in the ASR message, so that the user is sent to the user as the prompt information through the PCEF, so that the user can promptly release the session.
  • FIG. 6 is a system for indicating the reason for termination of a tongue according to an embodiment of the present invention.
  • the system includes: a server 610, which sends an ASR message, where the ASR message carries an extended cause value parameter; and the client 620 sends an ASR message from the server. Obtaining a cause value parameter, according to the cause value parameter, instructing the server 610 to terminate the session.
  • Server 610 includes:
  • Receiving module 611 receiving a session termination indication from the client
  • the sending module 612 sends an ASR message, where the ASR message carries a function that indicates that the user is unable to meet the user service quality requirement due to the policy charging rule function entity PCRF failure, device management reason, user subscription change, and the policy and charging execution entity PCEF failure causes the session to be released.
  • Client 620 includes:
  • the obtaining module 621 obtains, from the ASR message sent by the server, that the session is released due to the failure of the policy charging rule function entity PCRF, the device management reason, the user subscription change, the user service quality requirement, and the policy and charging execution entity PCEF failure.
  • the processing module 622 performs corresponding processing.
  • the processing module 622 instructs the PCRF to terminate the IP-CAN.
  • the client 620 can also include: a prompting module 623, the prompting module 623 prompting the user for the reason for the termination of the session.
  • the client 620 may further include: a statistics module (not shown), and the statistics module may count the reason for the termination of the session.
  • the processing module 622 instructs the PCRF to terminate the AF ⁇ tongue.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

Un procédé de fin de session implique les étapes suivantes : un client reçoit un message de demande qui comprend un paramètre de valeur de cause étendue en provenance d'un serveur ; le client obtient le paramètre de valeur de cause à partir du message de demande, demande au serveur de mettre fin à une session selon le paramètre de valeur de cause. Un système de fin de session qui implique un client et un serveur est décrit dans un mode de réalisation. Un client et un serveur sont également décrits dans le mode de réalisation.
PCT/CN2008/072792 2007-10-25 2008-10-23 Procédé de fin de session WO2009056046A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710165403.1 2007-10-25
CN200710165403.1A CN101420361A (zh) 2007-10-25 2007-10-25 一种会话终止的方法、***及服务器、客户端

Publications (1)

Publication Number Publication Date
WO2009056046A1 true WO2009056046A1 (fr) 2009-05-07

Family

ID=40590554

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072792 WO2009056046A1 (fr) 2007-10-25 2008-10-23 Procédé de fin de session

Country Status (2)

Country Link
CN (1) CN101420361A (fr)
WO (1) WO2009056046A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022022889A1 (fr) * 2020-07-31 2022-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de commande de politique

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4927213B1 (ja) * 2010-12-03 2012-05-09 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、ゲートウェイ装置、移動管理ノード及び呼セッション制御サーバ装置
CN102984783B (zh) * 2011-09-02 2015-03-25 阿尔卡特朗讯公司 一种用于控制终端访问无线网络的方法和装置
EP2896156B1 (fr) * 2012-09-17 2016-11-09 Telefonaktiebolaget LM Ericsson (publ) Systèmes extensibles et à haute disponibilité, de commande des politiques et de la taxation, et procédés correspondants
CN106470412B (zh) * 2015-08-20 2021-08-24 中兴通讯股份有限公司 终端下线方法、备用pcrf装置、用户签约数据装置及***
CN110880981B (zh) * 2018-09-06 2020-11-03 中兴通讯股份有限公司 Gx会话异常的处理方法及装置
CN115118762A (zh) * 2022-05-19 2022-09-27 北京京东乾石科技有限公司 一种会话处理的方法、客户端和***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1735278A (zh) * 2004-06-17 2006-02-15 Lg电子株式会社 用于会话终止的移动通信***和方法
CN1794872A (zh) * 2005-07-12 2006-06-28 华为技术有限公司 一种无线接入网中会话中止方法
US7269182B1 (en) * 2001-10-22 2007-09-11 Redback Networks Inc. Method and apparatus for PPPoE multicast
CN101052054A (zh) * 2006-04-04 2007-10-10 中兴通讯股份有限公司 保持ps域和ims域ip地址注销一致性的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7269182B1 (en) * 2001-10-22 2007-09-11 Redback Networks Inc. Method and apparatus for PPPoE multicast
CN1735278A (zh) * 2004-06-17 2006-02-15 Lg电子株式会社 用于会话终止的移动通信***和方法
CN1794872A (zh) * 2005-07-12 2006-06-28 华为技术有限公司 一种无线接入网中会话中止方法
CN101052054A (zh) * 2006-04-04 2007-10-10 中兴通讯股份有限公司 保持ps域和ims域ip地址注销一致性的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022022889A1 (fr) * 2020-07-31 2022-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et appareils de commande de politique
EP4312413A3 (fr) * 2020-07-31 2024-02-07 Telefonaktiebolaget LM Ericsson (publ) Procédés et appareils de commande de politique

Also Published As

Publication number Publication date
CN101420361A (zh) 2009-04-29

Similar Documents

Publication Publication Date Title
RU2513711C2 (ru) Триггер события услуги
WO2009046678A1 (fr) Procédé et dispositif pour obtenir la capacité de fonction d'application de politique et de facturation
WO2008128470A1 (fr) Procédé, système et entité de réalisation de détection d'événement
WO2010121565A1 (fr) Procédé de notification de mises à jour des priorités de service, et procédé et appareil pour mise à jour des priorités de service
WO2008154840A1 (fr) Procédé, système et entité permettant de mettre en œuvre une commande de politique
WO2009124441A1 (fr) Procédé de déclenchement d’une fin de session, procédé de mise en place et appareil
WO2010108356A1 (fr) Procédé de chargement, système et procédé de rapport pour accès à un terminal par le biais de réseaux à accès multiple
WO2008116406A1 (fr) Procédé de commande, système et entité de fonction pour notifier un événement de flux d'internet de signalisation
WO2009135362A1 (fr) Procédé de commande de politique et de facturation pour cacher la topologie d'un réseau visité
JP2012507223A (ja) ポリシー及び課金制御方法、サーバ、及びコンピュータプログラム
WO2005109758A1 (fr) Methode de traitement pour une taxation en ligne parfaite basee sur le flux de donnees de service
WO2010031316A1 (fr) Procédé et système pour réaliser la commande de politique et de facturation sur la scène de multiples réseaux de données par paquets (pdn)
WO2006047965A1 (fr) Procede de traitement de facturation en ligne
WO2010069170A1 (fr) Procédé pour réaliser une régulation de politique et de facturation
WO2011079773A1 (fr) Procédé, dispositif et système destinés à commander une police de séance d'utilisateur
WO2012103770A1 (fr) Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic
WO2009056046A1 (fr) Procédé de fin de session
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
WO2011063688A1 (fr) Procédé et système de sélection d'entité à fonction de règles de politique et de facturation
WO2007112657A1 (fr) Procédé et système de décision concernant l'information sur les services dans un système de communication mobile
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
JP2014506420A (ja) デュアルスタックをサポートするｉｐ−ｃａｎセッションにおいてアプリケーション検出及び制御を実現する方法及びシステム
WO2013044730A1 (fr) Procédé et système de mise à jour de qualité de service pour règles de politique et de facturation
WO2012119488A1 (fr) Procédé pour fournir un service, courtier en services et fonction d'imputation et de règles

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

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

Country of ref document: EP

Kind code of ref document: A1