WO2008086722A1 - Procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos, et système et dispositif correspondants - Google Patents

Procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos, et système et dispositif correspondants Download PDF

Info

Publication number
WO2008086722A1
WO2008086722A1 PCT/CN2007/071252 CN2007071252W WO2008086722A1 WO 2008086722 A1 WO2008086722 A1 WO 2008086722A1 CN 2007071252 W CN2007071252 W CN 2007071252W WO 2008086722 A1 WO2008086722 A1 WO 2008086722A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
message
idle mode
termination
terminal
Prior art date
Application number
PCT/CN2007/071252
Other languages
English (en)
Chinese (zh)
Inventor
Jiaxing Xiao
Junxian Mo
Anning Xie
Weimin Chen
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 WO2008086722A1 publication Critical patent/WO2008086722A1/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
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a service termination method in which a terminal is in an idle (IDLE) mode, a system in which a terminal is in an idle mode to implement service termination, a state detection device, and a policy execution device.
  • the Policy and Charging Control (PCC) architecture is a general policy control and charging control framework suitable for various Internet Protocol (IP) connection access networks.
  • the functions of the PCC include: MS-based customized information Implementing policy control and charging control based on service data flow.
  • the PCC is located between the service control layer and the access/bearer layer in the network, and blocks specific access/bearer layer technologies and topology information to the service control layer.
  • the PCC receives service-related requests from the service control layer, and then combines with the admission control policy and the topology information of the network to implement policy control and charging control.
  • FIG. 1 is a basic functional architecture diagram of a PCC in the prior art.
  • the basic functional architecture of the PCC includes: Application Function (AF), which provides service information for related decisions; and Subscription Profile Repository (SPR), which is mainly used to save real-time.
  • Policy and Charging Enforcement Function (PCRF) used to formulate rules
  • PCEF Policy and Charging Enforce Function
  • PCEF Policy and Charging Enforce Function
  • GW Gateway
  • OCS Online Charging System
  • OFDMS Offline Charging System
  • the SPR interface is connected between the SPR and the PCRF, and the PCRF can be connected through the Sp interface.
  • the user's valid ID such as the International Mobile Subscriber Identification Number (IMSI)
  • IMSI International Mobile Subscriber Identification Number
  • requests the SPR to be associated with the bearer policy if the PCRF has requested the relevant subscription information, the SPR detects the relevant subscription.
  • the changes are notified to the corresponding PCRF through the Sp interface; the PCRF and the PCEF are connected by a Gx interface, and the two perform a PCC rule request message, a PCC rule response message, and a user plane event message through the Gx interface.
  • the AF and PCRF are connected by Rx interface, and the two transmit the session control layer information about the IP Multimedia Subsystem (IMS) session and media parameters through the Rx interface; the Gz interface is connected between the PCEF and the OFCS, and the transmission is performed.
  • IMS IP Multimedia Subsystem
  • the Gz interface is connected between the PCEF and the OFCS, and the transmission is performed.
  • User non-real-time charging message; PCEF and OCS are connected by Gy interface to transmit real-time charging messages of users.
  • the PCC architecture can be integrated into the mobile communication system, and the PCC architecture is used to work together with related functional units to implement corresponding strategies.
  • the WiMAX system mainly includes a mobile terminal (MS), an Access Service Network (ASN), and a Connectivity Service Network (CSN).
  • the ASN mainly includes a base station (BS) and an access service network gateway (ASN-GW);
  • the CSN mainly includes a logical function entity such as a prepaid server (PPS) and an AAA server.
  • FIG. 3 is a schematic structural diagram of a WiMAX system providing QoS in the prior art.
  • QoS Quality of Service
  • NSG WiMAX Network Work Group
  • the MS is the user's mobile terminal, and the user interacts with the network through the MS;
  • the Service Flow Manager (SFM) in the ASN is used for admission control of service flows.
  • the Service Flow Authorization (SFA) in the ASN is used to authorize service flows, including the service SFA (Serving). SFA and Anchor SFA;
  • the Policy Function (PF) provided by the Network Service Provider (NSP) is used to provide policies for the user's service flow. In the user roaming scenario, the PF score is used.
  • AF For visiting PF (Visit PF, V-PF) and local PF (Home PF, H-PF); AF provided by NSP is a functional entity that provides application services. The user's MS directly accesses AF through an application layer protocol connection. AF will The PF is notified to actively create a service flow for the user.
  • FIG. 4 is a schematic structural diagram of a WiMAX system for providing charging in the prior art.
  • the MS is equivalent to the user in the accounting, and the accounting client is used to collect all accounting information and provide authentication, authorization, and accounting.
  • (Authorization Authorization Accounting, AAA) server (AAA Server); AAA Proxy (AAA Proxy) is an optional intermediate device, which is used to process a received accounting packet to generate a new accounting packet.
  • the local AAA server is the home AAA server or the AAA server.
  • the local AAA server is the primary AAA server or the AAA server of the user's home.
  • the local AAA server stores the AAA server.
  • the user's subscription information, including the accounting policy is performed by the user in the local AAA server.
  • the AAA server is used to record the accounting information when the user roams. Pass and forward.
  • FIG. 5 is a schematic structural diagram of a conventional WiMAX system and a PCC architecture.
  • the convergence with the IMS is implemented by a WiMAX system that integrates PCC, and the system includes: SFM, SFA, Agent, PCRF, and AF.
  • SFM is used for user service flow and access permission control and allocates radio resources for this service flow;
  • SFA is used to authorize corresponding service flows according to PCC rules and local policies sent by PCRF;
  • Agent is a generation of PCEF responsible for the conversion of R3-PCC to Gx interface;
  • PCRF is used to provide policy charging rules for a certain user service flow.
  • the PCRF is divided into Visited PCRF and Home PCRF; AF is the application service functional entity, MS directly By accessing the AF through the application layer protocol connection, the AF will notify the PCRF to actively create a service flow for the user, which can trigger the user to create a service flow.
  • SFA Agent, and Accounting Client
  • the MS is in the idle (IDLE) mode, the user actively shuts down or the system network side triggers the MS to exit the network, releasing the context of the MS.
  • the anchor paging control/location entity (Anchor PC/LR) in the NAP initiates a paging procedure for the MS, looking for The call flow is abnormal, that is, when the number of pagings specified by the protocol is completed, the corresponding MS response is not found, the MS may be in a lost state, and the paging fails; or the PC/LR is not receiving the location update request message of the MS, causing the MS to be lost. .
  • IP-Connectivity Access Network IP-CAN
  • the Bay' J Anchor PC/LR cannot terminate the IP-CAN session. , ie delete the IP-CAN session.
  • the MS in the existing mobile communication system with the PCC framework, the MS is in the IDLE mode, and the MS is lost due to the failure of the periodic location update or the paging failure, or the MS is normally shut down when the MS is in the IDLE mode. In the case of a state, it is impossible to terminate related services such as an IP-CAN session, so that the reliability of the existing mobile communication system of the converged PCC framework is not high. Summary of the invention
  • the present invention provides a service termination method in which the terminal is in an idle mode, and can terminate the service when the terminal in the idle mode is in a lost state.
  • the present invention provides a system for terminating a service in an idle mode, which can terminate a service when a terminal in an idle mode is in a lost state.
  • the present invention provides a state detecting device capable of issuing a request for service termination when a terminal in an idle mode is in a lost state.
  • the present invention provides a policy enforcement device capable of implementing termination of a service when a terminal in an idle mode is in a lost state.
  • a method for terminating a service in an idle mode includes the following steps: The first function entity determines that the terminal in the idle mode is in a lost state, and sends a request message to the second function entity;
  • the second functional entity receives the request message from the first functional entity, triggering the termination of the service.
  • a system in which a terminal is in an idle mode to implement service termination including: a first device and a second device, where
  • the first device is configured to send a request message to the second device when determining that the terminal in the idle mode is in a lost state
  • the second device is configured to trigger service termination according to the request sent by the first device.
  • a state detecting device comprising: a message generating unit and a transceiver unit;
  • the message generating unit is configured to: when the terminal in the idle mode is in a lost state, generate a request message including the terminal loss information in the idle mode, and provide the request message to the transceiver unit; and the transceiver unit is configured to receive the message generating unit Providing a request message, and transmitting the request message; receiving a response message indicating that the service has been terminated.
  • a policy execution device includes: a transceiver unit and a message parsing unit;
  • the transceiver unit is configured to receive and send a request message and a response message from the outside indicating that the service has been terminated; and provide a request message from the outside to the message parsing unit;
  • the message parsing unit is configured to determine the sending and receiving Whether the request message provided by the unit is sent because the terminal in the idle mode is in a lost state, and if so, the service termination is triggered.
  • the technical solution in the embodiment of the present invention has the following beneficial effects: when the second functional entity is triggered by the first functional entity to initiate a service termination process to terminate the service, thereby ensuring that the MS in the idle mode is in a lost state. , can terminate the existing services, thereby improving the reliability of the mobile communication system that integrates the PCC architecture.
  • the state detecting device and the policy executing device in the embodiment of the present invention may respectively serve as a first device/functional entity and a second device/functional entity in the service termination system.
  • the embodiment of the present invention implements the state detecting device and the policy executing device, that is, the first device/functional entity and the second device/functional entity, by using different functional entities, so that the technical solution of the embodiment of the present invention is applicable to multiple scenarios. Therefore, it has high versatility.
  • FIG. 1 is a schematic diagram of a PCC architecture in the prior art.
  • FIG. 2 is a schematic structural view of a WiMAX system in the prior art.
  • FIG. 3 is a schematic structural diagram of a WiMAX system providing QoS in the prior art.
  • FIG. 4 is a schematic structural diagram of a WiMAX system for providing charging in the prior art.
  • FIG. 5 is a schematic structural diagram of a conventional WiMAX system and a PCC architecture.
  • FIG. 6 is a schematic structural diagram of a system for implementing termination of a service in an idle mode according to an embodiment of the present invention.
  • FIG. 7 is an exemplary flowchart of a method for terminating a service in an idle mode in a terminal according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 1 of the present invention.
  • FIG. 9 is a flowchart of a method for terminating a service in an idle mode in a first embodiment of the present invention.
  • FIG. 10 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 2 of the present invention.
  • FIG. 11 is a flowchart of a method for terminating a service in an idle mode in a second embodiment of the present invention.
  • FIG. 12 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 3 of the present invention.
  • FIG. 13 is a flowchart of a method for terminating a service in an idle mode in a third embodiment of the present invention.
  • FIG. 14 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 4 of the present invention.
  • FIG. 15 is a flowchart of a method for terminating a service in an idle mode in a fourth embodiment of the present invention.
  • FIG. 16 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 5 of the present invention.
  • 17 is a flowchart of a method for terminating a service in an idle mode in a fifth embodiment of the present invention.
  • FIG. 18 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 6 of the present invention.
  • FIG. 19 is a flowchart of a method for terminating a service in an idle mode according to Embodiment 6 of the present invention. Mode for carrying out the invention
  • the basic idea of the embodiment of the present invention is: when the MS is in the IDLE mode, the PC/LR triggers due to the failure of the periodic location update or the paging failure, or the MS is in a lost state due to the normal shutdown of the MS in the IDLE mode. PCEF initiates the business termination process.
  • the manner in which the PCEF initiates the service termination process may be:
  • the PC/LR sends an IP-CAN session release request to the PCEF, and the PCEF triggers an IP according to the received request.
  • the PCEF feeds back an IP-CAN session response message to the PC/LR, and then the PC/LR completes the corresponding processing;
  • the PC/LR sends an IP-CAN session release request to the PCEF, also Forwarding can be achieved through an intermediate entity, such as Data Path Function (DPF), FA, and so on.
  • DPF Data Path Function
  • FIG. 6 is a schematic structural diagram of a system for implementing termination of a service in an idle mode according to an embodiment of the present invention.
  • the system in which the terminal is in the idle mode to implement service termination in the embodiment includes: a first device and a second device.
  • the first device may be a paging control/location registration entity
  • the second device may be a policy charging execution function entity.
  • the paging control/location registration entity sends a service termination request message to the policy charging execution function entity, and carries the service termination information in the request and sends the message to the policy charging execution function entity; receiving the function from the policy charging execution function entity The response message that the service has been terminated.
  • the service termination information is an indication for terminating the service, and includes: MS information (such as MS ID, SF Info, etc.), terminal loss information in idle mode, paging control, and location registration entity (PC/LR) identifier.
  • MS information such as MS ID, SF Info, etc.
  • terminal loss information in idle mode includes: status information indicating that the user is lost in the idle mode and/or loss cause value indicating the cause of the loss (shutdown, paging) Failure, location update timeout, etc.).
  • the policy charging execution function entity receives the request message from the paging control/location registration entity, triggers the service termination process according to the received request message and the service termination information carried in the message, and controls the paging after the service is terminated.
  • the location hosting entity sends a response message confirming that the paging control/location host entity has requested termination of the service.
  • the first device of the foregoing system may further include an intermediate entity, such as a DPF, a mobile IP access proxy (MIP FA), a context function entity (Context Function), an authentication entity (Authenticator), and an accounting client (Accounting Client). Or a radio resource control (RRC) entity or the like, implementing information forwarding between the paging control/location registration entity and the policy charging execution function entity, that is, the first device is a combination of a paging control/location registration entity and an intermediate entity .
  • an intermediate entity such as a DPF, a mobile IP access proxy (MIP FA), a context function entity (Context Function), an authentication entity (Authenticator), and an accounting client (Accounting Client).
  • RRC radio resource control
  • the paging control/location registration entity sends a request to the intermediate entity to trigger the service termination process, and carries the service termination information in the request and sends it to the intermediate entity; receives the response from the intermediate entity, and receives the response.
  • the response corresponds to the processing.
  • the intermediate entity sends a request from the paging control/location depositing entity to the policy charging enforcement function entity; the response from the policy charging enforcement function entity is sent to the paging control/location hosting entity.
  • the policy charging execution function entity receives the request from the intermediate entity, triggers the service termination process according to the received request and the service termination information, and sends a response to the intermediate entity after the service is terminated, confirming that the paging control/location registration entity requests termination The business has been terminated.
  • the paging control/location registration entity ie, the PC/LR
  • the PC/LR is responsible for entering the idle state MS information maintenance entity, and the request is issued when the MS in the idle mode is in a lost state
  • the intermediate entity is an optional entity, which may be The DPF, the FA, and the like
  • the policy charging execution function entity that is, the PCEF or the SFA, sends a request message triggering the service termination to the PCRF/PF (the PCRF/PF in the present embodiment indicates the PCRF and/or the PF), and notifies the PCRF/PF to initiate the request message.
  • the request message for triggering the service termination may be any one.
  • Some request messages such as an MS information request (MS Info REQ) may also be other messages used to notify the user to shut down normally or the MS is lost, but the messages carry the lost information in the idle mode, that is, the idle mode is indicated.
  • the status information lost by the user and/or the loss cause value indicating the cause of the loss; the response confirming the successful termination of the service may be any existing response message, such as MS Info RSP, etc., or may represent the service Other messages that have been terminated.
  • the first device functions as a state detecting device, and includes: a message generating unit, a state determining unit, and a transceiver unit.
  • the status determining unit determines whether the terminal in the idle mode is in a lost state, and if yes, acquires the terminal lost information in the idle mode, and provides the information to the message generating unit, indicating that the terminal is lost in the idle state;
  • the message generating unit according to the terminal loss information in the idle mode from the state judging unit, knows that the terminal in the idle mode is in a lost state, and at this time, generates a request message including the terminal end loss information in the idle mode, and provides the request message to the transceiver unit;
  • the transceiver unit receives the request message provided by the message generating unit, and directly or indirectly sends a request to the policy execution device that implements the service termination in the idle mode of the terminal.
  • the request may carry the lost information, which is used to notify the policy execution device to trigger the termination of the service; and the transceiver unit is further configured to receive a response message indicating that the service has been terminated.
  • the device may further include a message parsing unit;
  • the transceiver unit receives a request message from other external functional units capable of determining that the terminal is lost in the idle mode, and provides the request message to the message parsing unit;
  • the message parsing unit parses the request message provided by the transceiver unit, and determines the request Whether the message carries the terminal loss information in the idle mode, if yes, it is determined that the service termination needs to be triggered, and the parsed out terminal loss information in the idle mode is provided to the message generating unit;
  • the message generating unit generates a request message including the terminal lost information in the idle mode from the message parsing unit according to the terminal loss information in the idle mode from the message parsing unit, and provides the request message to the transceiver unit.
  • the second function entity serves as a policy execution device, and includes: a transceiver unit, a message parsing unit, and a message generating unit.
  • Transceiver unit receiving a request message from the outside, and providing a request message from the outside to the message parsing unit; usually, the request message is directly or indirectly from the state detecting device; sending a service termination to the external PCRF/PF Requesting a message; notifying the PCRF/PF to initiate the termination of the service, and instructing the PCRF/PF to terminate the service, notifying the reason for the termination of the service, indicating that the MS is lost due to the idle mode, so the service established before the MS needs to be terminated;
  • the service has terminated the response message, and is provided to the message parsing unit; the device that sends the request, that is, the state detecting device, may forward the response message from the message parsing unit; the message parsing unit determines whether the request message provided by the transceiver unit is If the terminal in the idle mode is sent in a lost state, if the request message is sent because the terminal in the idle mode is in a lost state, for example, if the request carries the terminal lost information in the
  • the message generating unit generates a request message including a service for terminating the service according to the request message from the message parsing unit and the terminal loss information in the idle mode, and the message parsing unit
  • the terminal loss information in the idle mode is carried in the request message and is provided to the transceiver unit.
  • FIG. 7 is a schematic flowchart of a method for terminating a service in an idle mode in a terminal according to an embodiment of the present invention.
  • the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 701 The first functional entity sends a request message for terminating the service to the second functional entity, and carries the service termination information in the request message.
  • the first functional entity may be a paging control/location registration entity; the second functional entity may be a policy charging execution function entity; the service termination information is an indication for terminating the service, including: MS information (eg, MS ID, SF) Info, etc.), terminal lost information, PC/LR identification, etc. in idle mode.
  • MS information eg, MS ID, SF
  • terminal lost information e.g., PC/LR identification, etc. in idle mode.
  • the terminal lost information in the idle mode includes: status information indicating that the user is lost in the idle mode and/or a loss cause value indicating the cause of the loss (shutdown, paging failure, location update timeout, etc.).
  • the paging control/location registration entity issues a request when the MS in the idle mode is in a lost state;
  • the request sent by the paging control/location registration entity may be any existing request message, such as MS Info. REQ, etc., may also be other messages used to notify the user that the system is normally shut down or the MS is lost.
  • the first functional entity may also be a combination of a paging control/location entity and an intermediate entity.
  • the paging control/location entity may pass such as DPF, MIP FA, Context Function, Authenticator, Accounting Client or RRC, etc.
  • the intermediate entity sends a request to the policy charging enforcement function entity that is the second functional entity.
  • Step 702 When the second functional entity receives the request message from the first functional entity, triggering a service termination process.
  • the policy charging execution function entity as the second functional entity may
  • the PCRF/PF triggers the service processing process, and sends a request message for triggering the service termination to the PCRF/PF, notifying the PCRF/PF to initiate the termination of the service, and instructing the PCRF/PF to terminate the service, notifying the cause of the service termination, indicating that the service is idle.
  • the MS is lost, so the service established before the MS needs to be terminated.
  • the PCRF/PF terminates the service according to the indication of the policy charging execution function entity, and sends a response message to the policy charging execution function entity as the second functional entity.
  • the policy charging execution function entity as the second functional entity and the PCRF/PF can be based on the Remote Authentication Dial In User Service (RADIUS) protocol or the Dell Mitt (The Diameter Control Protocol Credit Control Request (CCR) message interacts with a Credit Control Response (CCA) message.
  • RADIUS Remote Authentication Dial In User Service
  • Dell Mitt The Diameter Control Protocol Credit Control Request (CCR) message interacts with a Credit Control Response (CCA) message.
  • Step 703 After confirming that the service termination process is completed, the second function entity sends a response message to the first function entity, that is, responds to the request of the first function entity, and confirms that the service requested by the first function entity is terminated.
  • the response message sent by the policy charging execution function entity as the second functional entity may be any existing response message, such as MS Info RSP, or other messages indicating that the service has been terminated;
  • a functional entity which is a combination of a paging control/location entity and an intermediate entity
  • the policy charging execution function entity may forward to the paging through an intermediate entity such as DPF, MIP FA, Context Function, Authenticator, Accounting Client or RRC.
  • the control/location register entity sends a response message.
  • the address of the second functional entity may be statically configured in advance, thereby implementing addressing in the interaction process.
  • Embodiment 1 is an example of the implementation of the IP-CAN session in the WiMAX system based on the fused PCC in the present embodiment.
  • the system and the device in the idle mode are implemented in the idle mode, and the terminal is in the idle mode.
  • the business termination method is described in detail.
  • Embodiment 1
  • the paging control/location registration entity is a PC/LR
  • the policy charging execution function entity is a PCEF, and there is no intermediate entity between them to directly interact; the PCEF triggers the IP-CAN session processing process to terminate the PCRF. IP-CAN session.
  • FIG. 8 is a structural diagram of a system for implementing termination of a service in an idle mode in a first embodiment of the present invention.
  • the system in which the terminal is in the idle mode to implement the service termination in the embodiment includes: PC/LR, PCEF and PCRF.
  • PC/LR when the MS in the idle mode is in the lost state, sends a request message PC_PCEF_Request to the PCEF, requests the PCEF to terminate the currently existing IP-CAN session, and carries the service termination information in the PC_PCEF_Request and sends it to the PCEF; receiving the PCEF from the PCEF PC_PCEF_Response, and the corresponding processing after the IP-CAN session is terminated.
  • the PCEF sends a Diameter CCR message carrying the termination cause value termination cause to the PCRF according to the request of the PC/LR, triggers the IP-CAN session processing process, and instructs the IP-CAN session to terminate; after receiving the Diameter CCA message from the PCRF, A response message PC_PCEF_Response is sent to the PC/LR, indicating that the PCRF has completed the IP-CAN session termination.
  • the PCRF performs the corresponding processing of the IP-CAN session termination according to the termination cause value termination cause carried in the PCEF request, and sends a Diameter CCA message to the PCEF after the IP-CAN session is terminated, responding to the PCEF request, indicating IP-CAN The session has been terminated.
  • FIG. 9 is a flowchart of a method for terminating a service in an idle mode in a first embodiment of the present invention. As shown in FIG. 9, based on the system shown in FIG. 8, the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 901 When the MS in the IDLE mode is in a lost state, the PC/LR sends a request message PC_PCEF_Request to the PCEF, requesting the PCEF to terminate the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, and the like), terminal loss information in an idle mode including a loss cause value, a PC/LR identifier, and the like.
  • Step 902 The PCEF sends a request, that is, a Diameter CCR message, to the PCRF according to the request of the PC/LR, triggering an IP-CAN session processing process, and instructing the IP-CAN session to terminate.
  • a request that is, a Diameter CCR message
  • the PCEF sets the value of the CC-Request-Type in the Diameter CCR message to "TERMINATION_REQUEST", and carries the termination cause value termination cause in the message; this embodiment uses the WiMAX system as an example, and therefore, termination The cause is a WiMAX IDLE termination cause.
  • the meaning of the specific value can be set according to the specific situation. For example, 0 indicates paging failure, 1 indicates location update timeout, and 2 indicates shutdown.
  • Step 903 The PCRF performs corresponding processing of the IP-CAN session termination according to the request of the PCEF.
  • Step 904 the PCRF confirms that the IP-CAN session is terminated, and sends a response, that is, a Diameter CCA message, to the PCEF to notify the PCEF that the IP-CAN session has terminated.
  • Step 905 After receiving the Diameter CCA message, the PCEF sends a response message PC_PCEF_Response to the PC/LR to notify the PC/LR that the IP-CAN session has been terminated.
  • the PC/LR and the PCEF are exchanged between the PC_PCEF_Request and the PC_PCEF_Response; when the PCEF triggers the service termination process to the PCRF, the PCEF sends the termination cause to the PCRF; the PCRF is mainly for the different "termination cause" included in the request for the PCEF. " To deal with it accordingly.
  • the paging control/location registration entity is a PC/LR
  • the policy charging execution function entity is an SFA
  • the SFA includes: a service SFA and an anchor SFA, a PC/LR and an SFA.
  • anchor SFA triggers IP-CAN session processing to the PCRF to terminate the IP-CAN session.
  • FIG. 10 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 2 of the present invention.
  • the system in which the terminal is in the idle mode to implement the service termination in the embodiment includes: a PC/LR, a service SFA, an anchor SFA, and a PCRF/PF.
  • PC/LR when the MS in the idle mode is in a lost state, sends a request message PC_SFA_Request to the service SFA, requests the SFA to terminate the currently existing IP-CAN session, and carries the service termination information in the message and sends it to the service SFA;
  • the PC_SFA_Response from the service SFA performs related processing after the IP-CAN session is terminated.
  • the service SFA receives the request from the PC/LR, and sends a request message PD-Request to the anchor SFA according to the request, and carries an indication of the IP-CAN session termination in the request message, where the message also carries the termination cause value.
  • the termination cause after receiving the PD-Response message, sends a response message PC_SFA_Response to the PC/LR, indicating that the PCRF/PF completes the IP-CAN session termination.
  • Anchoring the SFA receiving the PD-Request from the serving SFA, and transmitting a Diameter CCR/PD-Request message carrying the termination cause value termination cause to the PCRF/PF according to the received request message PD-Request, triggering IP-CAN session processing Procedure, and instructing the IP-CAN session to terminate; after receiving the Diameter CCA/PD-Response message, confirming that the IP-CAN session is terminated, and transmitting a PD-Response message to the serving SFA, indicating that the PCRF/PF has completed the IP-CAN session termination.
  • PCRF/PF according to the termination cause value termination cause carried in the request of the anchor SFA, performs corresponding processing of IP-CAN session termination; after confirming the termination of the IP-CAN session, sends a Diameter CCA/PD-Response message to the anchor SFA , responding to the request to anchor the SFA, indicating that the IP-CAN session has terminated.
  • the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 1101 When the MS in the IDLE mode is in a lost state, the PC/LR sends a request message PC_SFA_Request to the serving SFA, requesting the SFA to terminate the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, and the like), terminal loss information in an idle mode including a loss cause value, and a PC/LR identifier.
  • Step 1102 The service SFA sends a request, that is, a PD-Request, to the anchor SFA according to the request of the PC/LR, and carries an indication of the IP-CAN session termination in the request message.
  • the PD-Request also carries a termination cause value; the present embodiment is a WiMAX system as an example. Therefore, the termination cause is a WiMAX IDLE termination cause, and the meaning of the specific value can be arbitrarily set, for example, 0 means paging failure, 1 means location update timeout, 2 means shutdown, etc.
  • Step 1103 The anchor SFA sends a request to the PCRF/PF according to the request of the serving SFA, that is, a Diameter CCR/PD-Request message, triggers an IP-CAN session processing process, and indicates that the IP-CAN session is terminated.
  • the anchor SFA sets the value of the CC-Request-Type in the Diameter CCR/PD-Request message to "TERMINATION_REQUEST", and carries the received WiMAX IDLE termination cause in the message.
  • Step 1104 the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the request of the anchor SFA.
  • Step 1105 the PCRF/PF confirms that the IP-CAN session is terminated, and sends a response to the anchor SFA, that is, a Diameter CCA/PD-Response message indicating that the IP-CAN session has terminated.
  • Step 1106 after the anchor SFA receives the Diameter CCA/PD-Response message, Confirm that the IP-CAN session is terminated and send a PD-Response message to the serving SFA, indicating that the PCRF/PF has completed the IP-CAN session termination.
  • Step 1107 After receiving the PD-Response message, the serving SFA sends a response message PC_SFA_Response to the PC/LR, indicating that the PCRF/PF completes the IP-CAN session termination.
  • the PC/LR and the SFA exchange with each other through the PC_SFA_Request and the PC_SFA_Response; when the service SFA sends the PD-Request to the anchor SFA, the message carries the termination cause in the message, and sends the termination cause by the cat SFA.
  • PCRF/PF PCRF/PF is mainly processed for different "termination cause”.
  • the paging control/location registration entity is a PC/LR
  • the policy charging execution function entity is an anchor SFA
  • anchoring the SFA to the PCRF /PF triggers the IP-CAN session process to terminate the IP-CAN session.
  • FIG. 12 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 3 of the present invention.
  • the system in which the terminal is in the idle mode to implement the service termination includes: PC/LR, anchor SFA, and PCRF/PF.
  • the PC/LR when the MS in the idle mode is in a lost state, sends a request message PC_SFA_Request to the service SFA, requests the SFA to terminate the currently existing IP-CAN session, and carries the service termination information in the message and sends it to the anchor SFA;
  • the PC_SFA_Response from the anchor SFA is received, and the related processing after the IP-CAN session is terminated.
  • PCRF/PF according to the termination cause value termination cause carried in the request of the anchor SFA, performs corresponding processing of IP-CAN session termination; after confirming the termination of the IP-CAN session, sends a Diameter CCA/PD-Response message to the anchor SFA , responding to the request to anchor the SFA, indicating that the IP-CAN session has terminated.
  • FIG. 13 is a flowchart of a method for terminating a service in an idle mode in a third embodiment of the present invention. As shown in FIG. 13, based on the system shown in FIG. 12, the service termination method in which the terminal is in the idle mode in this embodiment includes the following steps:
  • Step 1301 When the MS in the idle mode is in a lost state, the PC/LR sends a request message PC_SFA_Request to the serving SFA, requesting the anchor SFA to terminate the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, etc.), terminal loss information in idle mode including loss reason value, PC/LR identifier, and the like.
  • Step 1302 The anchor SFA sends a request to the PCRF/PF according to the request of the PC/LR, that is, a Diameter CCR/PD-Request message, triggers an IP-CAN session processing process, and indicates that the IP-CAN session is terminated.
  • the anchor SFA sets the value of the CC-Request-Type in the Diameter CCR/PD-Request message to "TERMINATION-REQUEST"; the Diameter CCR/PD-Request message also carries the termination cause value;
  • the WiMAX system is used as an example. Therefore, the termination cause is a WiMAX IDLE termination cause.
  • the meaning of the specific value can be arbitrarily set. For example, 0 indicates paging failure, 1 indicates location update timeout, and 2 indicates shutdown.
  • step 1303 the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the request of the anchor SFA.
  • step 1304 the PCRF/PF confirms that the IP-CAN session is terminated, and sends a response to the anchor SFA, that is, a Diameter CCA/PD-Response message indicating that the IP-CAN session has terminated.
  • Step 1305 After receiving the Diameter CCA/PD-Response message, the anchor SFA confirms that the IP-CAN session is terminated, and sends a response message PC_SFA_Response to the PC/LR, and the PCRF/PF completes the IP-CAN session termination.
  • the PC/LR and the anchor SFA are exchanged between the PC_SFA_Request and the PC_SFA_Response; the anchor SFA carries the termination cause in the request message when triggering the service termination process to the PCRF/PF; the PCRF/PF is mainly directed to Different "termination cause" for corresponding processing.
  • the paging control/location registration entity is a PC/LR
  • the policy charging execution function entity is a combined entity of the SFA and the Agent, and the PC/LR and the combined entity have no intermediate entity and directly interact;
  • the PCRF/PF triggers the IP-CAN session process to terminate the IP-CAN session.
  • FIG. 14 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 4 of the present invention.
  • the system in which the terminal is in the idle mode to implement the service termination in the embodiment includes: PC/LR, SFA, Agent, and PCRF/PF.
  • PC/LR when the MS in the idle mode is in a lost state, sends a request message PC_SFA_Request to the SFA, requests to terminate the currently existing IP-CAN session, and carries the service termination information in the message and sends it to the SFA; receives the SFA from the SFA.
  • PC_SFA_Response performs related processing after the IP-CAN session is terminated.
  • the SFA receives the request from the PC/LR, and sends a Diameter CCR message to the Agent according to the request, and carries an indication of the IP-CAN session termination in the request message, and the Diameter CCR message also carries a termination cause value termination cause; Received Diameter After the CCA message, a response message PC_SFA_Response is sent to the PC/LR, indicating that the PCRF/PF has completed the IP-CAN session termination.
  • the agent receives the Diameter CCR message from the SFA, and sends a Diameter CCR message carrying the termination cause value termination cause to the PCRF/PF according to the received request message Diameter CCR message, triggers the IP-CAN session processing process, and indicates the IP-CAN.
  • the session is terminated; after receiving the Diameter CCA message, it is confirmed that the IP-CAN session is terminated, and a Diameter CCA message is sent to the SFA, indicating that the PCRF/PF has completed the IP-CAN session termination.
  • the PCRF/PF performs the corresponding processing of the IP-CAN session termination according to the termination cause value carried in the request of the Agent. After confirming the termination of the IP-CAN session, the Diameter CCA message is sent to the Agent to respond to the request of the Agent. Indicates that the IP-CAN session has been terminated.
  • FIG. 15 is a flowchart of a method for terminating a service in an idle mode in a fourth embodiment of the present invention. As shown in FIG. 15, based on the system shown in FIG. 14, the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 1501 When the MS in the idle mode is in a lost state, the PC/LR sends a request message PC_SFA_Request to the SFA, requesting to terminate the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, and the like), terminal loss information in an idle mode including a loss cause value, and a PC/LR identifier.
  • Step 1502 The SFA sends a Diameter CCR message to the Agent according to the request of the PC/LR, and carries an indication of the IP-CAN session termination in the message.
  • the Diameter CCR message also carries a termination cause value;
  • the present embodiment is a WiMAX system, for example, the termination cause is WiMAX IDLE termination cause, the meaning of the specific value can be arbitrarily set, for example, 0 means paging failure, 1 means location update timeout, 2 means shutdown, and so on.
  • Step 1503 After receiving the Diameter CCR message sent by the SFA, the Agent sends a Diameter CCR message to the PCRF/PF, triggers an IP-CAN session processing process, and indicates that the IP-CAN session is terminated.
  • the agent sets the value of the CC-Request-Type in the Diameter CCR message to "TERMINATION_REQUEST", and carries the received WiMAX IDLE termination cause in the message.
  • Step 1504 The PCRF/PF performs corresponding processing of the IP-CAN session termination according to the request of the Agent.
  • Step 1505 the PCRF/PF confirms that the IP-CAN session is terminated, and sends a response to the Agent, that is, a Diameter CCA message, indicating that the IP-CAN session has terminated.
  • Step 1506 after receiving the Diameter CCA message, the Agent confirms that the IP-CAN session is terminated, and sends a Diameter CCA message to the SFA, indicating that the PCRF/PF completes the IP-CAN step 1507, and after receiving the Diameter CCA message, the SFA sends the PC to the PC. /LR sends a response message PC_SFA_Response, indicating that the PCRF/PF has completed the IP-CAN session termination.
  • the PC/LR and the SFA are exchanged between the PC_SFA_Request and the PC_SFA_Response; when the SFA sends the Diameter CCR message to the Agent, the SFA also carries the termination cause, and the Agent sends the termination cause to the PCRF/PF; PCRF/PF is mainly processed for different "termination cause”.
  • the paging control/location registration entity is a PC/LR, and policy charging is performed.
  • the functional entity is a combined entity of the SFA and the Agent, that is, the combined PCEF, and the PC/LR interacts with the combined PCEF through the intermediate entity FA; the combined PCEF triggers the IP-CAN session processing procedure to the PCRF/PF to terminate the IP-CAN session.
  • the technical solution of the embodiment is implemented by adding one FA.
  • FIG. 16 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 5 of the present invention.
  • the system in which the terminal is in the idle mode to implement the service termination in the embodiment includes: PC/LR, FA, combined PCEF and PCRF/PF composed of SFA and Agent.
  • PC/LR when the MS in the IDLE mode is in a lost state, sends a request message PC_FA_Request to the FA, requests to terminate the currently existing IP-CAN session, and carries the service termination information in the message and sends it to the FA; receives the FA from the FA PC_FA_Response, performs related processing after the IP-CAN session is terminated.
  • the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the termination cause value carried in the request of the combined PCEF; after confirming the termination of the IP-CAN session, A Diameter CCA message is sent to the combined PCEF to respond to the request to combine the PCEFs, indicating that the IP-CAN session has terminated.
  • FIG. 17 is a flowchart of a method for terminating a service in an idle mode in a fifth embodiment of the present invention. As shown in FIG. 17, based on the system shown in FIG. 16, the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 1701 When the MS in the IDLE mode is in a lost state, the PC/LR sends a request message PC_FA_Request to the FA, requesting to terminate the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, and the like), terminal loss information in an idle mode including a loss cause value, and a PC/LR identifier.
  • Step 1702 The FA sends a Diameter CCR message to the combined PCEF according to the request of the PC/LR, and carries an indication of the IP-CAN session termination in the message.
  • the Diameter CCR message also carries a termination cause value; the present embodiment is a WiMAX system, and therefore, the termination cause is a WiMAX IDLE termination cause, and the meaning of the specific value can be arbitrarily set, for example, 0 means paging failure, 1 means location update timeout, 2 means shutdown, etc.
  • Step 1703 After receiving the Diameter CCR message sent by the FA, the combined PCEF sends a request to the PCRF/PF, that is, a Diameter CCR message, triggers an IP-CAN session processing process, and indicates that the IP-CAN session is terminated.
  • the combined PCEF sets the value of the CC-Request-Type in the Diameter CCR message to "TERMINATION_REQUEST", and carries the received WiMAX IDLE termination cause in the message.
  • Step 1704 the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the request of the combined PCEF.
  • Step 1705 the PCRF/PF confirms that the IP-CAN session is terminated, and sends a response to the combined PCEF, that is, a Diameter CCA message, indicating that the IP-CAN session has terminated.
  • Step 1706 after receiving the Diameter CCA message, the combined PCEF confirms that the IP-CAN session is terminated, and sends a Diameter CCA message to the FA, indicating that the PCRF/PF completes the IP-CAN session termination.
  • Step 1707 After receiving the Diameter CCA message, the FA sends a response message PC_FA_Response to the PC/LR, indicating that the PCRF/PF completes the IP-CAN session termination.
  • the PC/LR and the intermediate entity FA interact with each other through the PC_FA_Request and the PC_FA_Response; when the FA sends the Diameter CCR message to the combined PCEF, the FA also carries the termination cause in the message, and sends the termination cause to the combined PCEF.
  • PCRF/PF PCRF/PF is mainly processed for different "termination cause”.
  • the interaction mode between the SFA and the agent in the combined PCEF may be the same as the interaction between the SFA and the agent in the fourth embodiment.
  • the paging control/location registration entity is a PC/LR
  • the policy charging execution function entity is a combined entity of the SFA and the agent, that is, the combined PCEF, and the PC/LR and the combined PCEF interact through the intermediate entity DPF.
  • the combined PCEF triggers an IP-CAN session process to the PCRF/PF to terminate the IP-CAN session.
  • the technical solution of the embodiment is implemented by adding a DPF.
  • FIG. 18 is a structural diagram of a system for implementing termination of a service in an idle mode according to Embodiment 6 of the present invention.
  • the system in which the terminal is in the idle mode to implement service termination in the embodiment includes: PC/LR, DPF, combined PCEF composed of SFA and Agent. And PCRF/PF.
  • PC/LR when the MS in the idle mode is in a lost state, sends a request message PC_DPF_Request to the DPF, requests to terminate the currently existing IP-CAN session, and carries the service termination information in the message and sends it to the DPF; receives the DPF from the DPF.
  • PC_DPF_Response performs related processing after the IP-CAN session is terminated.
  • the DPF receives the request from the PC/LR, and according to the request, sends a Diameter CCR message to the combined PCEF, and carries an indication of the IP-CAN session termination in the message, and the Diameter CCR message also carries a termination cause value termination cause;
  • the response message PC_DPF_Response is sent to the PC/LR, indicating that the PCRF/PF completes the IP-CAN session termination.
  • the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the termination cause value termination cause carried in the request of the combined PCEF. After confirming the termination of the IP-CAN session, the Diameter CCA message is sent to the combined PCEF, and the request for the combined PCEF is performed. A response is made indicating that the IP-CAN session has terminated.
  • the DPF may be an anchor DPF or a combined entity that serves DPF and anchor DPF.
  • FIG. 19 is a flowchart of a method for terminating a service in an idle mode in a sixth embodiment of the present invention. As shown in FIG. 19, based on the system shown in FIG. 18, the service termination method in the idle mode of the terminal in this embodiment includes the following steps:
  • Step 1901 when the MS in the idle mode is in a lost state, the PC/LR is directed to the DPF.
  • the request message PC_DPF_Request is sent to request termination of the currently existing IP-CAN session, and the message carries the service termination information.
  • the service termination information includes: MS information (including service flow information related to the MS, MS ID, SF Info, etc.), terminal loss information in idle mode including loss reason value, PC/LR identifier, and the like.
  • Step 1902 The DPF sends a Diameter CCR message to the combined PCEF according to the request of the PC/LR, and carries an indication of the IP-CAN session termination in the message.
  • the Diameter CCR message also carries a termination cause value; the present embodiment is a WiMAX system, and therefore, the termination cause is a WiMAX IDLE termination cause, and the meaning of the specific value can be arbitrarily set, for example, 0 means paging failure, 1 means location update timeout, 2 means shutdown, etc.
  • Step 1903 After receiving the Diameter CCR message sent by the DPF, the combined PCEF sends a request to the PCRF/PF, that is, a Diameter CCR message, triggers an IP-CAN session processing process, and indicates that the IP-CAN session is terminated.
  • the combined PCEF sets the value of the CC-Request-Type in the Diameter CCR message to "TERMINATION_REQUEST", and carries the received WiMAX IDLE termination cause in the message.
  • Step 1904 the PCRF/PF performs corresponding processing of the IP-CAN session termination according to the request of the combined PCEF.
  • Step 1905 the PCRF/PF confirms that the IP-CAN session is terminated, and sends a response to the combined PCEF, that is, a Diameter CCA message, indicating that the IP-CAN session has terminated.
  • Step 1906 after receiving the Diameter CCA message, the combined PCEF confirms that the IP-CAN session is terminated, and sends a Diameter CCA message to the DPF, indicating that the PCRF/PF completes the IP-CAN session termination.
  • Step 1907 after receiving the Diameter CCA message, the DPF sends a response to the PC/LR.
  • the message PC_DPF_Response indicates that the PCRF/PF has completed the IP-CAN session termination. At this point, the process ends.
  • the PC/LR and the intermediate entity DPF exchange with each other through the PC_DPF_Request and the PC_DPF_Response; when the DPF sends the Diameter CCR message to the combined PCEF, the DPF also carries the termination cause in the message, and sends the termination cause to the combined PCEF.
  • PCRF/PF PCRF/PF is mainly processed for different "termination cause”.
  • the interaction mode between the SFA and the agent in the combined PCEF may be the same as the interaction between the SFA and the agent in the fourth embodiment.
  • PD-Request and PD-Response may also be replaced by RR_Request and RR-Response 0.
  • the foregoing embodiment implements the processing of the service termination when the MS in the idle mode is in the lost state; the service termination processing in different scenarios is implemented by using different logical functional entities and related messages.
  • the system in which the terminal is in the idle mode to implement service termination and the service termination method in which the terminal is in the idle mode are also applicable to other schemes of the converged PCC architecture except WiMAX, and may also be used in addition to service termination. Business process.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Selon l'invention, un procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos comporte : la réception par une seconde fonction d'un message de demande, émis par une première fonction, lorsque la première fonction considère qu'un terminal, qui se trouve en mode repos, se trouve dans un état de perte ; le déclenchement par la seconde fonction d'une procédure de clôture de service. La description de la présente invention divulgue un système permettant de réaliser la clôture d'un service lorsqu'un terminal se trouve au repos, un dispositif de vérification d'état et un dispositif d'application de politique. Selon l'invention, la première fonction déclenche la seconde fonction pour lancer la procédure de clôture de service et effectue la clôture du service ; la clôture du service existant pourrait donc être assurée lorsque le terminal, qui se trouve en mode repos, se trouve dans un état de repos. En outre, selon l'invention, si l'on utilise les différentes fonctions pour réaliser le dispositif de vérification d'état et le dispositif d'application de politique, le schéma est applicable dans différentes circonstances et permet une utilisation plus générale.
PCT/CN2007/071252 2007-01-15 2007-12-17 Procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos, et système et dispositif correspondants WO2008086722A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710000967.X 2007-01-15
CN200710000967XA CN101227702B (zh) 2007-01-15 2007-01-15 终端处于空闲模式下的业务终止方法、系统和设备

Publications (1)

Publication Number Publication Date
WO2008086722A1 true WO2008086722A1 (fr) 2008-07-24

Family

ID=39635656

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/071252 WO2008086722A1 (fr) 2007-01-15 2007-12-17 Procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos, et système et dispositif correspondants

Country Status (2)

Country Link
CN (1) CN101227702B (fr)
WO (1) WO2008086722A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324428A (zh) * 2019-07-10 2019-10-11 中国工商银行股份有限公司 应用层会话清理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2303360A1 (fr) * 1997-09-29 1999-03-29 Telefonaktiebolaget Lm Ericsson Procede et systeme pour lier automatiquement un appel a un temps choisi dans un reseau de telecommunication radio
CN1419392A (zh) * 1996-06-07 2003-05-21 夸尔柯姆股份有限公司 在多址通信系统中实现空闲切换的方法和装置
CN1852384A (zh) * 2005-06-18 2006-10-25 华为技术有限公司 一种策略和计费规则决策的实现方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100441044C (zh) * 2005-07-12 2008-12-03 华为技术有限公司 一种无线接入网中会话中止方法
CN100499545C (zh) * 2005-08-19 2009-06-10 华为技术有限公司 一种移动因特网协议注册/去注册方法
CN100361472C (zh) * 2005-11-03 2008-01-09 华为技术有限公司 一种在WiMAX系统中释放空闲资源的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1419392A (zh) * 1996-06-07 2003-05-21 夸尔柯姆股份有限公司 在多址通信系统中实现空闲切换的方法和装置
CA2303360A1 (fr) * 1997-09-29 1999-03-29 Telefonaktiebolaget Lm Ericsson Procede et systeme pour lier automatiquement un appel a un temps choisi dans un reseau de telecommunication radio
CN1852384A (zh) * 2005-06-18 2006-10-25 华为技术有限公司 一种策略和计费规则决策的实现方法

Also Published As

Publication number Publication date
CN101227702A (zh) 2008-07-23
CN101227702B (zh) 2011-08-03

Similar Documents

Publication Publication Date Title
JP4828608B2 (ja) 課金方法、課金システム、課金クライアントおよび課金処理手段
US7885636B2 (en) Data pre-paid in simple IP data roaming
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
WO2013104234A1 (fr) Procédé et système de contrôle de règles pour un réseau convergé
WO2009021462A1 (fr) Procédé et dispositif d'établissement de session ip-can
WO2008022602A1 (fr) Procédé, dispositif et système de commande de conditions d'utilisation et de facturation
WO2015131331A1 (fr) Procédé et dispositif pour gérer une session de facturation
WO2013064004A1 (fr) Procédé et système de mise à jour de la qualité de service
WO2008083630A1 (fr) Procédé, système et dispositif pour une décision de stratégie et de règles
WO2013044730A1 (fr) Procédé et système de mise à jour de qualité de service pour règles de politique et de facturation
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2013060170A1 (fr) Procédé et dispositif de fourniture de support de facturation basé sur un support lipa
WO2008092346A1 (fr) Procédé, système et appareil pour l'établissement d'un support de signalisation
WO2008043307A1 (fr) Procédé, dispositif et système de taxation commune
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
WO2009138016A1 (fr) Procédé, appareil et système de transmission d’information
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2010043095A1 (fr) Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"
WO2010118570A1 (fr) Système et appareil de convergence de réseaux wimax et wifi
WO2008086722A1 (fr) Procédé de clôture d'un service lorsqu'un terminal se trouve en mode repos, et système et dispositif correspondants
WO2013178183A1 (fr) Procédé et dispositif de traitement de mise à jour de la qualité de service
WO2012019506A1 (fr) Procédé et système adaptés pour mettre en œuvre un contrôle de ressources dans un scénario d'intégration d'un réseau fixe et d'un réseau mobile
US9253706B2 (en) Method, apparatus, and system for local routing authorization

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

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

Country of ref document: EP

Kind code of ref document: A1