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)
French (fr)
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/zh

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)

Description

终端处于空闲模式下的业务终止方法、 ***和设备
技术领域
本发明涉及移动通信技术， 特别涉及终端处于空闲 （IDLE )模式下 的业务终止方法、 终端处于空闲模式下实现业务终止的***、 状态检测 设备和策略执行设备。 发明背景
策略计费控制功能实体（ Policy and Charging Control, PCC )架构是 一个通用的适合于各种互联网协议（Internet Protocol, IP )连接接入网 络的策略控制和计费控制框架。 PCC的功能包括： 基于 MS的定制信息 实现基于业务数据流的策略控制和计费控制等。 PCC位于网络中的业务 控制层和接入 /承载层之间 , 向业务控制层屏蔽具体的接入 /承载层技术 和拓朴信息。 PCC从业务控制层接收业务相关请求， 然后与接纳控制策 略以及网络的拓朴信息等相结合， 实现策略控制和计费控制。
图 1为现有技术中 PCC的基本功能架构图。 如图 1所示， PCC的 基本功能架构包括： 应用功能实体（Application Function, AF ), 提供用 于相关决策的业务信息； 签约信息存储功能实体（Subscription Profile Repository, SPR ), 主要用于保存实时的拥护签约策略； 策略计费规则 功能实体（ Policy and Charging Enforcement Function, PCRF ), 用于制定 规则； 策略控制和计费执行功能实体 （Policy and Charging Enforce Function, PCEF ), 即网关（Gateway, GW ), 用于执行规则； 在线计费 ***（ Online Charging System, OCS )和离线计费***（ Offline Charging System, OFCS )分别用于在线的实时计费和离线的后付费。
SPR和 PCRF之间采用 Sp接口连接， PCRF通过 Sp接口可以根据 用户的有效 ID, 例如国际移动用户标识 ( International Mobile Subscriber Identification Number, IMSI )等， 向 SPR请求和承载策略相关的签约信 息； 如果 PCRF已经请求了相关的签约信息， 则 SPR在检测到相关的签 约信息已经改变时， 就会通过 Sp接口将这些改变通知给相应的 PCRF; PCRF和 PCEF之间采用 Gx接口连接，二者通过 Gx接口进行 PCC规则 请求消息、 PCC规则响应消息和用户面的事件消息； AF和 PCRF之间 采用 Rx接口连接， 二者通过 Rx接口传输会话控制层有关 IP多媒体子 ***（IP Multimedia Subsystem, IMS )会话和媒体参数的信息； PCEF 和 OFCS之间采用 Gz接口连接，传输用户非实时的计费消息； PCEF和 OCS之间采用 Gy接口连接， 传输用户实时的计费消息。
为了使得能够实现移动通信***与其它***的融合， 例如微波接入 全球互通 ( WiMAX, Worldwide Interoperability for Microwave Access ) ***和 IMS的融合，从而使得更加有效地对用户业务流进行策略控制和 计费控制， 可以将 PCC架构融合于移动通信***中， 并采用 PCC架构 与相关功能单元一起协同工作， 执行相应的策略。
图 2为现有技术中 WiMAX***的结构示意图。如图 2所示， WiMAX ***主要包括移动终端 （Mobile Station, MS )、 业务接入网络（Access Service Network, ASN )和连接业务网络 ( Connectivity Service Network, CSN )三部分。 其中， ASN主要包括基站（Base Station, BS )和接入业 务网络网关（ Access Service Network Gateway, ASN-GW )等； CSN主 要包括预付费服务器（ Prepaid Server, PPS )和 AAA Server等逻辑功能 实体。
图 3为现有技术中提供 QoS的 WiMAX***结构示意图。如图 3所 示， WiMAX网络工作组（Network Work Group, NWG )标准的服务质 量 QoS框架中， MS是用户的移动终端，用户通过 MS与网络进行交互； ASN中的业务流管理实体（ Service Flow Manager, SFM )用于业务流的 准入控制等； ASN中的业务流授权实体（ Service Flow Authorization, SFA ) 用于为业务流授权， 包括服务 SFA ( Serving SFA )和锚定 SFA ( Anchor SFA ); 网络服务提供商 ( Network Service Provider, NSP )提供的策略 功能实体（Policy Function, PF )用于为用户的业务流提供策略， 用户 漫游场景中， PF分为拜访 PF ( Visited PF, V-PF )和本地 PF ( Home PF, H-PF ); NSP提供的 AF是提供应用服务的功能实体， 用户的 MS直接 通过应用层协议连接访问 AF, AF将会通知 PF主动为用户创建业务流。
图 4为现有技术中提供计费的 WiMAX***结构示意图。 如图 4所 示， 现有 WiMAX NWG标准计费架构中， MS在计费中相当于用户， 计 费客户端 （ Accounting Client )用于收集所有的计费信息并提供给认证、 授权和计费( Authentication Authorization Accounting , AAA )服务器( AAA Server ); AAA代理（ AAA Proxy )是可选的中间设备， 用于对收到的计 费报文进行处理后， 生成一个新的计费报文， 并转发给本地 AAA Server ( Home AAA Server )或拜访 AAA Server ( Visited AAA Server )等； 本 地 AAA Server是归属 AAA Server , 即用户初始注册的 AAA Server或用 户归属地的 AAA Server, 本地 AAA Server中存储有用户的签约信息， 包括计费策略等， 用户的计费处理主要是在本地 AAA Server中完成的； 拜访 AAA Server是用户拜访地的 AAA Server, 用于实现用户漫游时的 计费信息记录、 透传和转发。
图 5为现有的一种 WiMAX***与 PCC架构融合的结构示意图。如 图 5所示， 通过融合 PCC的 WiMAX***实现与 IMS的融合， 该*** 包括： SFM、 SFA、 代理（Agent )、 PCRF和 AF。 SFM用于用户业务流 及接入允许控制并为此业务流分配无线资源等； SFA用于根据 PCRF发 送的 PCC规则和本地策略， 对相应的业务流授权； Agent是 PCEF的代 理， 负责 R3-PCC到 Gx接口的转换； PCRF用于为某个用户业务流提供 策略计费规则， 用户漫游场景中， PCRF分为 Visited PCRF和 Home PCRF; AF是应用服务功能实体， MS直接通过应用层协议连接访问 AF, AF将会通知 PCRF主动为用户创建业务流， 可以触发用户来创建业务 流。 上述***中， SFA、 Agent以及 Accounting Client的组合可以等效于 PCEF。
融合了 PCC 的移动通信***虽然提高了策略控制和计费控制的能 力， 但是却存在以下问题：
MS 处于空闲 （IDLE )模式， 用户主动关机或者***网络侧触发 MS退网， 释放 MS的上下文。 此时， 如果访问地代理（Foreign Agent, FA )接收到针对该 MS的数据包， NAP中的锚定寻呼控制 /位置寄存实 体（Anchor PC/LR )发起对该 MS的寻呼流程， 寻呼流程异常， 即当协 议规定的寻呼次数完成还没找到相应的 MS响应， MS可能处于丢失状 态， 寻呼失败； 或者 PC/LR—直没有收到 MS的位置更新请求消息， 导 致 MS丢失。
在例如上述的两种情况下，如果此时存在移动多媒体业务中的 IP连 通接入网络（IP-Connectivity Access Network, IP-CAN )会话， 贝' J Anchor PC/LR无法终止该 IP-CAN会话， 即删除该 IP-CAN会话。
可见， 在现有的融合 PCC框架的移动通信***中， MS处于 IDLE 模式下由于周期性位置更新失败或寻呼失败、 或者在 MS处于 IDLE模 式下 MS正常退网即关机等原因导致 MS处于丢失状态的情况下， 无法 终止例如 IP-CAN会话等相关业务，从而使得现有的融合 PCC框架的移 动通信***的可靠性不高。 发明内容
有鉴于此， 本发明提供一种终端处于空闲模式下的业务终止方法， 能够在空闲模式下的终端处于丢失状态时， 实现业务的终止。
本发明提供一种终端处于空闲模式下实现业务终止的***， 能够在 空闲模式下的终端处于丢失状态时， 实现业务的终止。
本发明提供一种状态检测设备， 能够在空闲模式下的终端处于丢失 状态时， 发出实现业务终止的请求。
本发明提供一种策略执行设备， 能够在空闲模式下的终端处于丢失 状态时， 实现业务的终止。
本发明的技术方案是这样实现的：
一种终端处于空闲模式下的业务终止方法， 包括以下步骤： 第一功能实体判断空闲模式下的终端处于丢失状态， 向第二功能实 体发送请求消息；
第二功能实体接收到来自第一功能实体的请求消息，触发业务终止。 一种终端处于空闲模式下实现业务终止的***， 包括： 第一设备和 第二设备， 其中，
第一设备用于在判断出空闲模式下的终端处于丢失状态时， 向所述 第二设备发送请求消息；
第二设备用于根据第一设备发送的请求， 触发业务终止。
一种状态检测设备， 包括： 消息生成单元和收发单元；
所述消息生成单元， 用于在空闲模式下的终端处于丢失状态时， 生 成包括空闲模式下终端丢失信息的请求消息， 并提供给所述收发单元； 所述收发单元， 用于接收消息生成单元提供的请求消息， 并发送该 请求消息； 接收表示业务已终止的响应消息。
一种策略执行设备， 包括： 收发单元和消息解析单元； 所述收发单元， 用于接收和发送来自外部的表示业务已终止的请求 消息和响应消息； 将来自外部的请求消息提供给所述消息解析单元； 所述消息解析单元， 用于判断所述收发单元提供的请求消息是否是 由于空闲模式下的终端处于丢失状态而发送的， 如果是， 则触发业务终 止。
由此可见， 本发明实施方式中的技术方案具有如下有益效果： 在由 第一功能实体触发第二功能实体发起业务终止过程， 实现业务的终止， 从而保证了空闲模式下的 MS处于丢失状态时， 能够终止存在的业务， 进而提高了融合 PCC架构的移动通信***的可靠性。其中，本发明实施 方式中的状态检测设备和策略执行设备可以分别作为业务终止***中 的第一设备 /功能实体和第二设备 /功能实体。
而且， 本发明实施方式通过不同的功能实体来实现状态检测设备和 策略执行设备， 即第一设备 /功能实体和第二设备 /功能实体， 使得本发 明实施方式的技术方案适用于多种场景， 从而具有较高的通用性。 附图简要说明
图 1为现有技术中 PCC架构示意图。
图 2为现有技术中 WiMAX***的结构示意图。
图 3为现有技术中提供 QoS的 WiMAX***结构示意图。
图 4为现有技术中提供计费的 WiMAX***结构示意图。
图 5为现有的一种 WiMAX***与 PCC架构融合的结构示意图。 图 6为本发明实施方式中终端处于空闲模式下实现业务终止的*** 的示例性结构图。
图 7为本发明实施方式中终端处于空闲模式下的业务终止方法的示 例性流程图。 图 8为本发明实施方式一中终端处于空闲模式下实现业务终止的系 统结构图。
图 9为本发明实施方式一中终端处于空闲模式下的业务终止方法的 流程图。
图 10 为本发明实施方式二中终端处于空闲模式下实现业务终止的 ***结构图。
图 11 为本发明实施方式二中终端处于空闲模式下的业务终止方法 的流程图。
图 12 为本发明实施方式三中终端处于空闲模式下实现业务终止的 ***结构图。
图 13 为本发明实施方式三中终端处于空闲模式下的业务终止方法 的流程图。
图 14 为本发明实施方式四中终端处于空闲模式下实现业务终止的 ***结构图。
图 15 为本发明实施方式四中终端处于空闲模式下的业务终止方法 的流程图。
图 16 为本发明实施方式五中终端处于空闲模式下实现业务终止的 ***结构图。
图 17 为本发明实施方式五中终端处于空闲模式下的业务终止方法 的流程图。
图 18 为本发明实施方式六中终端处于空闲模式下实现业务终止的 ***结构图。
图 19 为本发明实施方式六中终端处于空闲模式下的业务终止方法 的流程图。 实施本发明的方式
为使本发明的目的、 技术方案及优点更加清楚明白， 以下对本发明 实施方式进一步详细说明。
本发明实施方式的基本思想是： MS处于 IDLE模式下由于周期性位 置更新失败或寻呼失败、 或者在 MS处于 IDLE模式下正常退网即关机 等原因导致 MS处于丢失状态时， PC/LR触发 PCEF发起业务终止过程。
其中， 以需要终止的业务为 IP-CAN会话为例， 触发 PCEF发起业 务终止过程的方式可以为： PC/LR发送一个 IP-CAN会话释放请求到 PCEF, PCEF根据接收到的请求触发一个 IP-CAN会话终止过程， 当会 话终止过程完成以后， PCEF反馈一个 IP-CAN会话响应消息给 PC/LR, 再由 PC/LR完成相应的处理； PC/LR向 PCEF发送 IP-CAN会话释放请 求，也可以通过一个中间实体来实现转发，例如数据路径功能实体（Data Path Function, DPF )、 FA等。
图 6为本发明实施方式中终端处于空闲模式下实现业务终止的*** 的示例性结构图。 如图 6所示， 本实施方式中终端处于空闲模式下实现 业务终止的***包括： 第一设备和第二设备。
其中， 第一设备中可以为寻呼控制 /位置寄存实体， 第二设备可以为 策略计费执行功能实体。
寻呼控制 /位置寄存实体，向策略计费执行功能实体发送业务终止的 请求消息， 并将业务终止信息携带于该请求中发送给策略计费执行功能 实体； 接收来自策略计费执行功能实体的业务已终止的响应消息。
其中， 业务终止信息为用于终止业务的指示， 包括： MS 信息（例 如 MS ID、 SF Info等）、 空闲模式下终端丢失信息、 寻呼控制和位置寄 存实体（PC/LR )标识等。 空闲模式下终端丢失信息包括： 表示空闲模 式下用户丢失的状态信息和 /或表示丢失原因的丢失原因值（关机、寻呼 失败、 位置更新超时等）。
策略计费执行功能实体，接收来自寻呼控制 /位置寄存实体的请求消 息， 根据接收到的请求消息和消息中携带的业务终止信息， 触发业务终 止过程， 并在业务终止后， 向寻呼控制 /位置寄存实体发送响应消息， 确 认寻呼控制 /位置寄存实体请求终止的业务已终止。
实际应用中，上述***的第一设备还可以包括中间实体，例如 DPF、 移动 IP访问地代理（MIP FA )、 上下文功能实体（Context Function ), 认证实体 ( Authenticator )、 计费客户端（ Accounting Client )或无线资源 控制（RRC )实体等， 实现寻呼控制 /位置寄存实体与策略计费执行功能 实体之间的信息转发，即第一设备为寻呼控制 /位置寄存实体和中间实体 的组合体。
这种情况下， 寻呼控制 /位置寄存实体， 向中间实体发送触发业务终 止过程的请求， 并将业务终止信息携带于该请求中发送给中间实体； 接 收来自中间实体的响应， 并进行接收到的响应所对应的处理。
中间实体，将来自寻呼控制 /位置寄存实体的请求发送给策略计费执 行功能实体；将来自策略计费执行功能实体的响应发送给寻呼控制 /位置 寄存实体。
策略计费执行功能实体， 接收来自中间实体的请求， 根据接收到的 请求和业务终止信息， 触发业务终止过程， 在业务终止后向中间实体发 送响应， 确认寻呼控制 /位置寄存实体请求终止的业务已终止。
上述***中， 寻呼控制 /位置寄存实体即 PC/LR, 负责进入空闲状态 的 MS信息维护实体，在空闲模式下的 MS处于丢失状态时才发出请求； 中间实体是一个可选实体， 可以是 DPF、 FA等； 策略计费执行功能实 体即 PCEF或 SFA,向 PCRF/PF(本实施方式中的 PCRF/PF均表示 PCRF 和 /或 PF )发送触发业务终止的请求消息， 通知 PCRF/PF发起业务的终 止， 并向 PCRF/PF指示终止该业务， 通知其业务终止的原因， 表示由于 空闲模式下 MS丢失， 故需要将该 MS之前建立的业务终止； 触发业务 终止的请求消息可以为任意一种现有的请求消息，如 MS信息请求（ MS Info REQ )等， 也可以为用于通知用户正常关机退网或 MS丢失的其他 消息， 但消息中均携带空闲模式下终端丢失信息， 即表示空闲模式下用 户丢失的状态信息和 /或表示丢失原因的丢失原因值；确认业务成功终止 的响应可以为任意一种现有的响应消息，如 MS信息响应（ MS Info RSP ) 等， 也可以为表示业务已终止的其他消息。
具体来说， 如图 6所示的***中， 第一设备作为状态检测设备， 包 括： 消息生成单元、 状态判断单元和收发单元。
其中， 状态判断单元， 判断空闲模式下的终端是否处于丢失状态， 如果是， 则获取空闲模式下终端丢失信息， 并提供给消息生成单元， 指 示空闲状态下终端丢失；
消息生成单元，根据来自状态判断单元的空闲模式下终端丢失信息， 获知在空闲模式下的终端处于丢失状态， 此时， 生成包括空闲模式下终 端丢失信息的请求消息， 并提供给收发单元；
收发单元， 接收消息生成单元提供的请求消息， 并直接或间接地向 终端空闲模式下实现业务终止的策略执行设备发送请求。 该请求中可以 携带丢失信息， 用于通知该策略执行设备触发业务的终止； 收发单元还 用于接收表示业务已终止的响应消息。
如果作为状态检测设备的第一设备为寻呼控制 /位置寄存实体和中 间实体的组合体， 则该设备中还可以包括消息解析单元；
这种情况下， 收发单元接收来自外部其他能够判断空闲模式下终端 丢失的功能单元的请求消息， 并提供给所述消息解析单元；
消息解析单元对收发单元提供的请求消息进行解析， 并判断该请求 消息中是否携带空闲模式下终端丢失信息， 如果是， 则判断出需要触发 业务终止， 并将解析出的空闲模式下终端丢失信息提供给所述消息生成 单元；
消息生成单元再根据来自消息解析单元的空闲模式下终端丢失信 息， 生成包括所述来自消息解析单元的空闲模式下终端丢失信息的请求 消息， 并提供给收发单元。
如图 6所示的***中， 第二功能实体作为策略执行设备， 包括： 收 发单元、 消息解析单元和消息生成单元。
收发单元， 接收来自外部的请求消息， 并将来自外部的请求消息提 供给所述消息解析单元； 通常情况下， 该请求消息直接或间接来自状态 检测设备； 向外部的 PCRF/PF发送业务终止的请求消息；通知 PCRF/PF 发起业务的终止， 并向 PCRF/PF指示终止该业务，通知其业务终止的原 因， 表示由于空闲模式下 MS丢失， 故需要将该 MS之前建立的业务终 止； 接收表示业务已终止的响应消息， 并提供给消息解析单元； 可以向 发送请求的设备， 即状态检测设备，转发来自消息解析单元的响应消息； 消息解析单元， 判断所述收发单元提供的请求消息是否是由于空闲 模式下的终端处于丢失状态而发送的， 如果该请求消息是由于空闲模式 下的终端处于丢失状态而发送的， 例如判断出该请求中携带空闲模式下 终端丢失信息， 则触发业务终止； 例如， 根据从请求消息中解析出的空 闲模式下终端丢失信息判断出需要触发业务终止； 将解析出的空闲模式 下终端丢失信息提供给所述消息生成单元； 接收收发单元提供的响应消 息并进行解析， 将解析后的响应消息提供给收发单元， 告知收发单元该 响应消息表示业务已终止；
消息生成单元， 根据来自消息解析单元的请求消息和空闲模式下终 端丢失信息， 生成包括用于终止业务的请求消息， 并将消息解析单元提 供的空闲模式下终端丢失信息携带于该请求消息中， 提供给收发单元。 上述***和设备可以有不同的工作原理和实现方式， 以上仅为较佳 方案。
图 7为本发明实施方式中终端处于空闲模式下的业务终止方法的示 例性流程图。 如图 7所示， 基于上述***， 本实施方式中终端处于空闲 模式下的业务终止方法包括以下步骤：
步骤 701 ,第一功能实体向第二功能实体发送终止业务的请求消息， 并在请求消息中携带业务终止信息。
其中， 第一功能实体可以为寻呼控制 /位置寄存实体； 第二功能实体 可以为策略计费执行功能实体； 业务终止信息为用于终止业务的指示， 包括： MS信息 （例如 MS ID、 SF Info等）、 空闲模式下终端丢失信息、 PC/LR标识等。 空闲模式下终端丢失信息包括： 表示空闲模式下用户丢 失的状态信息和 /或表示丢失原因的丢失原因值（关机、 寻呼失败、 位置 更新超时等）。
本步骤中， 在空闲模式下的 MS处于丢失状态时， 寻呼控制 /位置寄 存实体才发出请求；寻呼控制 /位置寄存实体发送的请求可以为任意一种 现有的请求消息， 如 MS Info REQ等， 也可以为用于通知用户正常关机 退网或 MS丢失的其他消息。
第一功能实体中也可以为寻呼控制 /位置寄存实体与中间实体的组 合体，此时，寻呼控制 /位置寄存实体可以通过如 DPF、 MIP FA、 Context Function, Authenticator, Accounting Client或 RRC等中间实体， 向作为 第二功能实体的策略计费执行功能实体发送请求。
步骤 702, 当第二功能实体接收到来自第一功能实体的请求消息时， 触发业务终止过程。
本步骤中， 作为第二功能实体的策略计费执行功能实体可以向 PCRF/PF触发业务处理过程，并向 PCRF/PF发送触发业务终止的请求消 息， 通知 PCRF/PF发起业务的终止， 并向 PCRF/PF指示终止该业务， 通知其业务终止的原因， 表示由于空闲模式下 MS 丢失， 故需要将该 MS之前建立的业务终止； PCRF/PF会根据策略计费执行功能实体的指 示终止该业务， 并向作为第二功能实体的策略计费执行功能实体发送响 应消息， 表示业务已终止； 作为第二功能实体的策略计费执行功能实体 与 PCRF/PF之间可以通过基于远端用户拨入鉴权（ Remote Authentication Dial In User Service, RADIUS )协议或者戴尔米特 ( Diameter )协议的 信用控制请求（CCR ) 消息和信用控制响应 （CCA ) 消息进行交互。
步骤 703, 第二功能实体在确认所述业务终止过程完成之后， 向第 一功能实体发送响应消息， 即对第一功能实体的请求进行响应， 确认第 一功能实体请求终止的业务已终止。
本步骤中， 作为第二功能实体的策略计费执行功能实体发送的响应 消息可以为任意一种现有的响应消息， 如 MS Info RSP等， 也可以为表 示业务已终止的其他消息；如果第一功能实体中为寻呼控制 /位置寄存实 体与中间实体的组合体， 则策略计费执行功能实体可以通过如 DPF、 MIP FA、 Context Function、 Authenticator、 Accounting Client或 RRC等 中间实体， 向寻呼控制 /位置寄存实体发送响应消息。
本实施方式中， 作为第一功能实体的寻呼控制 /位置寄存实体中， 可 以预先静态配置第二功能实体的地址， 例如策略计费执行功能实体的地 址， 从而实现交互过程中的寻址。
下面， 以本实施方式基于融合 PCC的 WiMAX***实现、需要终止 的业务为 IP-CAN会话为例， 对本实施方式中终端处于空闲模式下实现 业务终止的***和设备、 以及终端处于空闲模式下的业务终止方法进行 详细说明。 实施方式一
在实施方式一中， 寻呼控制 /位置寄存实体为 PC/LR、 策略计费执行 功能实体为 PCEF, 二者之间没有中间实体， 直接交互； PCEF向 PCRF 触发 IP-CAN会话处理过程来终止 IP-CAN会话。
图 8为本发明实施方式一中终端处于空闲模式下实现业务终止的系 统结构图。 如图 8所示， 本实施方式中终端处于空闲模式下实现业务终 止的***包括： PC/LR, PCEF和 PCRF。
PC/LR, 在空闲模式下的 MS处于丢失状态时， 向 PCEF发送请求 消息 PC_PCEF_Request, 请求 PCEF终止当前存在的 IP-CAN会话， 并 将业务终止信息携带于 PC_PCEF_Request 中发送给 PCEF; 接收来自 PCEF的 PC_PCEF_Response, 并进行 IP-CAN会话终止后的相应处理。
PCEF ,根据 PC/LR的请求，向 PCRF发送携带终止原因值 termination cause的 Diameter CCR消息，触发 IP-CAN会话处理过程，并指示 IP-CAN 会话终止； 在接收到来自 PCRF的 Diameter CCA消息后， 向 PC/LR发 送响应消息 PC_PCEF_Response, 表示 PCRF完成了 IP-CAN会话终止。
PCRF , 根据 PCEF的请求中携带的终止原因值 termination cause进 行 IP-CAN会话终止的相应处理， 并在 IP-CAN会话终止后向 PCEF发 送 Diameter CCA消息， 对 PCEF的请求进行响应， 表示 IP-CAN会话已 终止。
图 9为本发明实施方式一中终端处于空闲模式下的业务终止方法的 流程图。 如图 9所示， 基于如图 8所示的***， 本实施方式中终端处于 空闲模式下的业务终止方法包括以下步骤：
步骤 901 , 在 IDLE模式下的 MS处于丢失状态时， PC/LR向 PCEF 发送请求消息 PC_PCEF_Request, 请求 PCEF终止当前存在的 IP-CAN 会话， 且该消息中携带业务终止信息。 本步骤中， 业务终止信息中包括： MS信息（包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 902, PCEF根据 PC/LR的请求，向 PCRF发送请求，即 Diameter CCR消息， 触发 IP-CAN会话处理过程， 并指示 IP-CAN会话终止。
本步骤中， PCEF将 Diameter CCR消息中的 CC-Request-Type的值 设置为" TERMINATION—REQUEST " , 并在消息中携带终止原因值 termination cause;本实施方式是以 WiMAX***为例, 因此, termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以 根据具体情况来设定， 例如， 0表示寻呼失败， 1表示位置更新超时， 2 表示关机等。
步骤 903 , PCRF根据 PCEF的请求， 进行 IP-CAN会话终止的相应 处理。
步骤 904, PCRF确认 IP-CAN会话终止， 并向 PCEF发送响应， 即 Diameter CCA消息， 以通知 PCEF , IP-CAN会话已终止。
步骤 905 , PCEF在接收到 Diameter CCA消息后， 向 PC/LR发送响 应消息 PC_PCEF_Response , 通知 PC/LR , IP-CAN会话已终止。
至此， 本流程结束。
本实施方式中， PC/LR 和 PCEF之间通过 PC_PCEF_Request 和 PC_PCEF_Response进行交互； PCEF在向 PCRF触发业务终止过程时， 将 termination cause发送给 PCRF; PCRF主要是针对 PCEF的请求中包 括的不同 "termination cause" 来进行相应处理的。
实施方式二
在实施方式二中， 寻呼控制 /位置寄存实体为 PC/LR, 策略计费执行 功能实体为 SFA, SFA包括： 服务 SFA与锚定 SFA, PC/LR与 SFA之 间没有中间实体， 直接交互； 锚定 SFA向 PCRF触发 IP-CAN会话处理 过程来终止 IP-CAN会话。
图 10 为本发明实施方式二中终端处于空闲模式下实现业务终止的 ***结构图。 如图 10所示， 本实施方式中终端处于空闲模式下实现业 务终止的***包括： PC/LR、 服务 SFA、 锚定 SFA和 PCRF/PF。
PC/LR, 在空闲模式下的 MS处于丢失状态时， 向服务 SFA发送请 求消息 PC_SFA_Request, 请求 SFA终止当前存在的 IP-CAN会话， 并 将业务终止信息携带于该消息中发送给服务 SFA;接收来自服务 SFA的 PC_SFA_Response, 进行 IP-CAN会话终止后的相关处理。
服务 SFA, 接收来自 PC/LR的请求， 并根据该请求， 向锚定 SFA 发送请求消息 PD-Request, 并在该请求消息中携带 IP-CAN会话终止的 指示， 该消息中还携带终止原因值 termination cause； 在接收到 PD-Response消息后， 向 PC/LR发送响应消息 PC_SFA_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。
锚定 SFA,接收来自服务 SFA的 PD-Request, 并根据接收到的请求 消息 PD-Request, 向 PCRF/PF发送携带终止原因值 termination cause的 Diameter CCR/PD-Request消息， 触发 IP-CAN会话处理过程， 并指示 IP-CAN会话终止； 在接收到 Diameter CCA/PD-Response消息后， 确认 IP-CAN会话终止，并向服务 SFA发送 PD-Response消息，表示 PCRF/PF 完成了 IP-CAN会话终止。
PCRF/PF, 根据锚定 SFA 的请求中携带的终止原因值 termination cause,进行 IP-CAN会话终止的相应处理； 在确认 IP-CAN会话终止后， 向锚定 SFA发送 Diameter CCA/PD-Response消息， 对锚定 SFA的请求 进行响应， 表示 IP-CAN会话已终止。
图 11 为本发明实施方式二中终端处于空闲模式下的业务终止方法 的流程图。 如图 11所示， 基于如图 10所示的***， 本实施方式中终端 处于空闲模式下的业务终止方法包括以下步骤：
步骤 1101 , 在 IDLE模式下的 MS处于丢失状态时， PC/LR向服务 SFA发送请求消息 PC_SFA_Request,请求 SFA终止当前存在的 IP-CAN 会话， 且该消息中携带业务终止信息。
本步骤中， 业务终止信息中包括： MS信息（包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 1102, 服务 SFA根据 PC/LR的请求， 向锚定 SFA发送请求， 即 PD-Request , 并在该请求消息中携带 IP-CAN会话终止的指示。
本步骤中， PD-Request中还携带终止原因值 termination cause; 本实 施方式是以 WiMAX***为例，因此， termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以任意设定， 例如， 0表 示寻呼失败， 1表示位置更新超时， 2表示关机等。
步骤 1103,锚定 SFA根据服务 SFA的请求，向 PCRF/PF发送请求， 即 Diameter CCR/PD-Request消息，触发 IP-CAN会话处理过程，并指示 IP-CAN会话终止。
本步骤中， 锚定 SFA 将 Diameter CCR/PD-Request 消息中的 CC-Request-Type的值设置为 "TERMINATION—REQUEST " , 并将接收 到的 WiMAX IDLE termination cause携带于该消息中。
步骤 1104, PCRF/PF根据锚定 SFA的请求， 进行 IP-CAN会话终止 的相应处理。
步骤 1105, PCRF/PF确认 IP-CAN会话终止， 并向锚定 SFA发送响 应， 即 Diameter CCA/PD-Response消息， 表示 IP-CAN会话已终止。
步骤 1106,锚定 SFA在接收到 Diameter CCA/PD-Response消息后， 确认 IP-CAN会话终止， 并向服务 SFA发送 PD-Response消息， 表示 PCRF/PF完成了 IP-CAN会话终止。
步骤 1107, 服务 SFA在接收到 PD-Response消息后， 向 PC/LR发 送响应消息 PC_SFA_Response,表示 PCRF/PF完成了 IP-CAN会话终止。
至此， 本流程结束。
本实施方式中， PC/LR 和 SFA 之间通过 PC_SFA_Request 和 PC_SFA_Response进行交互； 服务 SFA在向锚定 SFA发送 PD-Request 时， 还在该消息中携带 termination cause, 并由猫定 SFA将 termination cause发送给 PCRF/PF; PCRF/PF主要是针对不同的 "termination cause" 来进行相应处理的。
实施方式三
在实施方式三中， 寻呼控制 /位置寄存实体为 PC/LR, 策略计费执行 功能实体为锚定 SFA, PC/LR与锚定 SFA之间没有中间实体，直接交互； 锚定 SFA向 PCRF/PF触发 IP-CAN会话处理过程来终止 IP-CAN会话。
图 12 为本发明实施方式三中终端处于空闲模式下实现业务终止的 ***结构图。 如图 12所示， 本实施方式中终端处于空闲模式下实现业 务终止的***包括： PC/LR、 锚定 SFA和 PCRF/PF。
PC/LR, 在空闲模式下的 MS处于丢失状态时， 向服务 SFA发送请 求消息 PC_SFA_Request, 请求 SFA终止当前存在的 IP-CAN会话， 并 将业务终止信息携带于该消息中发送给锚定 SFA;接收来自锚定 SFA的 PC_SFA_Response, 进行 IP-CAN会话终止后的相关处理。
锚定 SFA, 接收来自 PC/LR 的请求， 并根据接收到的请求消息 PC_SFA_Request, 向 PCRF/PF发送 Diameter CCR/PD-Request消息， 触 发 IP-CAN会话处理过程，并指示 IP-CAN会话终止；在接收到 Diameter CCA/PD-Response消息后， 确认 IP-CAN会话终止， 并向 PC/LR发送响 应消息 PC_SFA_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。
PCRF/PF, 根据锚定 SFA 的请求中携带的终止原因值 termination cause,进行 IP-CAN会话终止的相应处理； 在确认 IP-CAN会话终止后， 向锚定 SFA发送 Diameter CCA/PD-Response消息， 对锚定 SFA的请求 进行响应， 表示 IP-CAN会话已终止。
图 13 为本发明实施方式三中终端处于空闲模式下的业务终止方法 的流程图。 如图 13所示， 基于如图 12所示的***， 本实施方式中终端 处于空闲模式下的业务终止方法包括以下步骤：
步骤 1301 ,在空闲模式下的 MS处于丢失状态时， PC/LR向服务 SFA 发送请求消息 PC_SFA_Request,请求锚定 SFA终止当前存在的 IP-CAN 会话， 且该消息中携带业务终止信息。
本步骤中， 业务终止信息中包括： MS信息 （包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 1302, 锚定 SFA根据 PC/LR的请求， 向 PCRF/PF发送请求， 即 Diameter CCR/PD-Request消息，触发 IP-CAN会话处理过程，并指示 IP-CAN会话终止。
本步骤中， 锚定 SFA 将 Diameter CCR/PD-Request 消息中的 CC-Request-Type的值设置为 "TERMINATION—REQUEST "； Diameter CCR/PD-Request消息中还携带终止原因值 termination cause； 本实施方 式是以 WiMAX ***为例， 因此， termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以任意设定， 例如， 0表 示寻呼失败， 1表示位置更新超时， 2表示关机等。
步骤 1303, PCRF/PF根据锚定 SFA的请求， 进行 IP-CAN会话终止 的相应处理。 步骤 1304, PCRF/PF确认 IP-CAN会话终止， 并向锚定 SFA发送响 应， 即 Diameter CCA/PD-Response消息， 表示 IP-CAN会话已终止。
步骤 1305 ,锚定 SFA在接收到 Diameter CCA/PD-Response消息后， 确认 IP-CAN会话终止， 并向 PC/LR发送响应消息 PC_SFA_Response, PCRF/PF完成了 IP-CAN会话终止。
至此， 本流程结束。
本实施方式中， PC/LR和锚定 SFA之间通过 PC_SFA_Request和 PC_SFA_Response进行交互； 锚定 SFA在向 PCRF/PF触发业务终止过 程时，还在请求消息中携带 termination cause; PCRF/PF主要是针对不同 的 "termination cause" 来进行相应处理的。
实施方式四
在实施方式四中， 寻呼控制 /位置寄存实体为 PC/LR, 策略计费执行 功能实体为 SFA和 Agent的组合实体， PC/LR与组合实体之间没有中间 实体， 直接交互； 组合实体向 PCRF/PF触发 IP-CAN会话处理过程来终 止 IP-CAN会话。
图 14 为本发明实施方式四中终端处于空闲模式下实现业务终止的 ***结构图。 如图 14所示， 本实施方式中终端处于空闲模式下实现业 务终止的***包括： PC/LR、 SFA、 Agent和 PCRF/PF。
PC/LR, 在空闲模式下的 MS处于丢失状态时， 向 SFA发送请求消 息 PC_SFA_Request, 请求终止当前存在的 IP-CAN会话， 并将业务终止 信息携带于该消息中发送给 SFA; 接收来自 SFA的 PC_SFA_Response, 进行 IP-CAN会话终止后的相关处理。
SFA ,接收来自 PC/LR的请求，并根据该请求，向 Agent发送 Diameter CCR消息， 并在该请求消息中携带 IP-CAN会话终止的指示， Diameter CCR 消息中还携带终止原因值 termination cause; 在接收到 Diameter CCA消息后，向 PC/LR发送响应消息 PC_SFA_Response,表示 PCRF/PF 完成了 IP-CAN会话终止。
Agent, 接收来自 SFA的 Diameter CCR消息， 并根据接收到的请求 消息 Diameter CCR消息， 向 PCRF/PF发送携带终止原因值 termination cause的 Diameter CCR消息，触发 IP-CAN会话处理过程，并指示 IP-CAN 会话终止； 在接收到 Diameter CCA消息后， 确认 IP-CAN会话终止， 并 向 SFA发送 Diameter CCA消息， 表示 PCRF/PF完成了 IP-CAN会话终 止。
PCRF/PF,根据 Agent的请求中携带的终止原因值 termination cause, 进行 IP-CAN会话终止的相应处理；在确认 IP-CAN会话终止后，向 Agent 发送 Diameter CCA消息，对 Agent的请求进行响应，表示 IP-CAN会话 已终止。
图 15 为本发明实施方式四中终端处于空闲模式下的业务终止方法 的流程图。 如图 15所示， 基于如图 14所示的***， 本实施方式中终端 处于空闲模式下的业务终止方法包括以下步骤：
步骤 1501 ,在空闲模式下的 MS处于丢失状态时， PC/LR向 SFA发 送请求消息 PC_SFA_Request, 请求终止当前存在的 IP-CAN会话， 且该 消息中携带业务终止信息。
本步骤中， 业务终止信息中包括： MS信息（包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 1502, SFA根据 PC/LR的请求， 向 Agent发送 Diameter CCR 消息， 并在该消息中携带 IP-CAN会话终止的指示。
本步骤中， Diameter CCR 消息中还携带终止原因值 termination cause; 本实施方式是以 WiMAX***为例， 因此， termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以任意设 定， 例如， 0表示寻呼失败， 1表示位置更新超时， 2表示关机等。
步骤 1503 , Agent接收到 SFA发送的 Diameter CCR消息后， 向 PCRF/PF发送 Diameter CCR消息，触发 IP-CAN会话处理过程， 并指示 IP-CAN会话终止。
本步骤中， Agent将 Diameter CCR消息中的 CC-Request-Type的值 设置为 "TERMINATION—REQUEST " , 并将接收到的 WiMAX IDLE termination cause携带于该消息中。
步骤 1504, PCRF/PF根据 Agent的请求， 进行 IP-CAN会话终止的 相应处理。
步骤 1505, PCRF/PF确认 IP-CAN会话终止，并向 Agent发送响应， 即 Diameter CCA消息， 表示 IP-CAN会话已终止。
步骤 1506, Agent在接收到 Diameter CCA消息后， 确认 IP-CAN会 话终止，并向 SFA发送 Diameter CCA消息，表示 PCRF/PF完成了 IP-CAN 步骤 1507, SFA在接收到 Diameter CCA消息后， 向 PC/LR发送响 应消息 PC_SFA_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。
至此， 本流程结束。
本实施方式中， PC/LR 和 SFA 之间通过 PC_SFA_Request 和 PC_SFA_Response进行交互； SFA在向 Agent发送 Diameter CCR消息 时,还在该消息中携带 termination cause,并由 Agent将 termination cause 发送给 PCRF/PF; PCRF/PF主要是针对不同的 "termination cause" 来进 行相应处理的。
实施方式五
在实施方式五中， 寻呼控制 /位置寄存实体为 PC/LR, 策略计费执行 功能实体为 SFA和 Agent的组合实体，即组合 PCEF, PC/LR与组合 PCEF 之间通过中间实体 FA进行交互； 组合 PCEF向 PCRF/PF触发 IP-CAN 会话处理过程来终止 IP-CAN会话。
在实施方式四的终端处于空闲模式下实现业务终止的***中， 增加 一个 FA, 即可实现本实施方式的技术方案。
图 16 为本发明实施方式五中终端处于空闲模式下实现业务终止的 ***结构图。 如图 16 所示， 本实施方式中终端处于空闲模式下实现业 务终止的***包括： PC/LR、 FA、 由 SFA和 Agent构成的组合 PCEF和 PCRF/PF。
PC/LR, 在 IDLE模式下的 MS处于丢失状态时， 向 FA发送请求消 息 PC_FA_Request, 请求终止当前存在的 IP-CAN会话， 并将业务终止 信息携带于该消息中发送给 FA; 接收来自 FA的 PC_FA_Response, 进 行 IP-CAN会话终止后的相关处理。
FA, 接收来自 PC/LR的请求， 并根据该请求， 向组合 PCEF发送 Diameter CCR 消息， 并在该消息中携带 IP-CAN会话终止的指示， Diameter CCR 消息中还携带终止原因值 termination cause; 在接收到 Diameter CCA消息后， 向 PC/LR发送响应消息 PC_FA_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。
组合 PCEF, 接收来自 FA的 Diameter CCR消息， 并向 PCRF/PF发 送携带终止原因值 termination cause的 Diameter CCR消息，触发 IP-CAN 会话处理过程， 并指示 IP-CAN会话终止； 在接收到 Diameter CCA消息 后， 确认 IP-CAN会话终止， 并向 FA发送 Diameter CCA消息， 表示 PCRF/PF完成了 IP-CAN会话终止。
PCRF/PF, 根据组合 PCEF的请求中携带的终止原因值 termination cause,进行 IP-CAN会话终止的相应处理； 在确认 IP-CAN会话终止后， 向组合 PCEF发送 Diameter CCA消息， 对组合 PCEF的请求进行响应， 表示 IP-CAN会话已终止。
图 17 为本发明实施方式五中终端处于空闲模式下的业务终止方法 的流程图。 如图 17所示， 基于如图 16所示的***， 本实施方式中终端 处于空闲模式下的业务终止方法包括以下步骤：
步骤 1701 , 在 IDLE模式下的 MS处于丢失状态时， PC/LR向 FA 发送请求消息 PC_FA_Request, 请求终止当前存在的 IP-CAN会话， 且 该消息中携带业务终止信息。
本步骤中， 业务终止信息中包括： MS信息（包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 1702, FA根据 PC/LR的请求，向组合 PCEF发送 Diameter CCR 消息， 并在该消息中携带 IP-CAN会话终止的指示。
本步骤中， Diameter CCR 消息中还携带终止原因值 termination cause; 本实施方式是以 WiMAX***为例， 因此， termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以任意设 定， 例如， 0表示寻呼失败， 1表示位置更新超时， 2表示关机等。
步骤 1703 , 组合 PCEF在接收到 FA发送的 Diameter CCR消息后， 向 PCRF/PF发送请求， 即 Diameter CCR消息， 触发 IP-CAN会话处理 过程， 并指示 IP-CAN会话终止。
本步骤中， 组合 PCEF将 Diameter CCR消息中的 CC-Request-Type 的值设置为 "TERMINATION—REQUEST " , 并将接收到的 WiMAX IDLE termination cause携带于该消息中。
步骤 1704, PCRF/PF根据组合 PCEF的请求， 进行 IP-CAN会话终 止的相应处理。 步骤 1705 , PCRF/PF确认 IP-CAN会话终止， 并向组合 PCEF发送 响应， 即 Diameter CCA消息， 表示 IP- CAN会话已终止。
步骤 1706,组合 PCEF在接收到 Diameter CCA消息后，确认 IP-CAN 会话终止， 并向 FA发送 Diameter CCA消息， 表示 PCRF/PF完成了 IP-CAN会话终止。
步骤 1707, FA在接收到 Diameter CCA消息后，向 PC/LR发送响应 消息 PC_FA_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。
至此， 本流程结束。
本实施方式中， PC/LR和中间实体 FA之间通过 PC_FA_Request和 PC_FA_Response进行交互； FA在向组合 PCEF发送 Diameter CCR消息 时， 还在该消息中携带 termination cause , 并由组合 PCEF将 termination cause发送给 PCRF/PF; PCRF/PF主要是针对不同的 "termination cause" 来进行相应处理的。
本实施方式中， 组合 PCEF中 SFA和 Agent之间的交互方式可以与 实施方式四中 SFA和 Agent之间的交互方式相同。
实施方式六
在实施方式六中， 寻呼控制 /位置寄存实体为 PC/LR, 策略计费执行 功能实体为 SFA和 Agent的组合实体，即组合 PCEF, PC/LR与组合 PCEF 之间通过中间实体 DPF进行交互； 组合 PCEF向 PCRF/PF触发 IP-CAN 会话处理过程来终止 IP-CAN会话。
在实施方式四的终端处于空闲模式下实现业务终止的***中， 增加 一个 DPF, 即可实现本实施方式的技术方案。
图 18 为本发明实施方式六中终端处于空闲模式下实现业务终止的 ***结构图。 如图 18 所示， 本实施方式中终端处于空闲模式下实现业 务终止的***包括： PC/LR、 DPF, 由 SFA和 Agent构成的组合 PCEF 和 PCRF/PF。
PC/LR, 在空闲模式下的 MS处于丢失状态时， 向 DPF发送请求消 息 PC_DPF_Request,请求终止当前存在的 IP-CAN会话， 并将业务终止 信息携带于该消息中发送给 DPF; 接收来自 DPF的 PC_DPF_Response , 进行 IP-CAN会话终止后的相关处理。
DPF, 接收来自 PC/LR的请求， 并根据该请求， 向组合 PCEF发送 Diameter CCR 消息， 并在该消息中携带 IP-CAN 会话终止的指示， Diameter CCR 消息中还携带终止原因值 termination cause; 在接收到 Diameter CCA消息后， 向 PC/LR发送响应消息 PC_DPF_Response, 表 示 PCRF/PF完成了 IP-CAN会话终止。
组合 PCEF, 接收来自 DPF的 Diameter CCR消息， 并向 PCRF/PF 发送携带终止原因值 termination cause 的 Diameter CCR 消息， 触发 IP-CAN会话处理过程， 并指示 IP-CAN会话终止； 在接收到 Diameter CCA消息后， 确认 IP-CAN会话终止， 并向 DPF发送 Diameter CCA消 息， 表示 PCRF/PF完成了 IP-CAN会话终止。
PCRF/PF, 根据组合 PCEF的请求中携带的终止原因值 termination cause,进行 IP-CAN会话终止的相应处理； 在确认 IP-CAN会话终止后， 向组合 PCEF发送 Diameter CCA消息， 对组合 PCEF的请求进行响应， 表示 IP-CAN会话已终止。
上述***中， DPF可以为锚定 DPF,也可以为服务 DPF与锚定 DPF 的组合实体。
图 19 为本发明实施方式六中终端处于空闲模式下的业务终止方法 的流程图。 如图 19所示， 基于如图 18所示的***， 本实施方式中终端 处于空闲模式下的业务终止方法包括以下步骤：
步骤 1901 , 在空闲模式下的 MS处于丢失状态时， PC/LR向 DPF 发送请求消息 PC_DPF_Request,请求终止当前存在的 IP-CAN会话，且 该消息中携带业务终止信息。
本步骤中， 业务终止信息中包括： MS信息 （包括与 MS相关的业 务流信息、 MS ID、 SF Info等）、 包括丢失原因值的空闲模式下终端丢 失信息、 PC/LR标识等。
步骤 1902 , DPF根据 PC/LR的请求，向组合 PCEF发送 Diameter CCR 消息， 并在该消息中携带 IP-CAN会话终止的指示。
本步骤中， Diameter CCR 消息中还携带终止原因值 termination cause; 本实施方式是以 WiMAX***为例， 因此， termination cause为 WiMAX IDLE termination cause, 其具体取值所表示的含义可以任意设 定， 例如， 0表示寻呼失败， 1表示位置更新超时， 2表示关机等。
步骤 1903,组合 PCEF在接收到 DPF发送的 Diameter CCR消息后， 向 PCRF/PF发送请求， 即 Diameter CCR消息， 触发 IP-CAN会话处理 过程， 并指示 IP-CAN会话终止。
本步骤中， 组合 PCEF将 Diameter CCR消息中的 CC-Request-Type 的值设置为 "TERMINATION—REQUEST " , 并将接收到的 WiMAX IDLE termination cause携带于该消息中。
步骤 1904, PCRF/PF根据组合 PCEF的请求， 进行 IP-CAN会话终 止的相应处理。
步骤 1905 , PCRF/PF确认 IP-CAN会话终止， 并向组合 PCEF发送 响应， 即 Diameter CCA消息， 表示 IP- CAN会话已终止。
步骤 1906,组合 PCEF在接收到 Diameter CCA消息后，确认 IP-CAN 会话终止， 并向 DPF发送 Diameter CCA消息， 表示 PCRF/PF完成了 IP-CAN会话终止。
步骤 1907, DPF在接收到 Diameter CCA消息后， 向 PC/LR发送响 应消息 PC_DPF_Response, 表示 PCRF/PF完成了 IP-CAN会话终止。 至此， 本流程结束。
本实施方式中， PC/LR和中间实体 DPF之间通过 PC_DPF_Request 和 PC_DPF_Response进行交互； DPF在向组合 PCEF发送 Diameter CCR 消息时， 还在该消息中携带 termination cause , 并由组合 PCEF 将 termination cause 发送给 PCRF/PF ; PCRF/PF 主要是针对不同的 "termination cause" 来进行相应处理的。
本实施方式中， 组合 PCEF中 SFA和 Agent之间的交互方式可以与 实施方式四中 SFA和 Agent之间的交互方式相同。
上述实施方式中， PD-Request 和 PD-Response 也可以替换为 RR— Request和 RR-Response0
上述实施方式实现了， 空闲模式下的 MS处于丢失状态时对业务终 止的处理； 通过不同逻辑功能实体和相关消息， 实现了在不同场景下的 业务终止处理。
本实施方式中终端处于空闲模式下实现业务终止的***和终端处于 空闲模式下的业务终止方法也适用于除 WiMAX之外的其它融合 PCC架 构的方案， 也可以用于除业务终止之外的其它业务处理过程。
以上所述仅为本发明较佳实施方式而已， 并非用于限定本发明的保 护范围。 凡在本发明实施方式的精神和原则之内， 所作的任何修改、 等 同替换以及改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种终端处于空闲模式下实现业务终止方法， 其特征在于， 包括 以下步骤：
第二功能实体接收第一功能实体在判断空闲模式下的终端处于丢失 状态时， 发送的请求消息；
第二功能实体触发业务终止。
2、 如权利要求 1所述的方法， 其特征在于， 所述请求消息为： 通知 第二功能实体触发业务终止的请求消息。
3、如权利要求 2所述的方法， 其特征在于， 所述通知第二功能实体 触发业务终止的请求消息中包括： 空闲模式下终端丢失信息。
4、 如权利要求 3所述的方法， 其特征在于， 所述触发业务终止为： 第二功能实体向策略计费规则功能 PCRF和 /或策略功能实体 PF发送终 止业务的请求消息， 并在请求消息中携带空闲模式下终端丢失信息； 所述触发业务终止之后， 该方法进一步包括： PCRF和 /或 PF在执 行所述终止业务后， 向第二功能实体发送表示业务已终止的响应消息。
5、 如权利要求 4所述的方法， 其特征在于， 所述 PCRF/PF向第二 功能实体发送表示业务已终止的响应消息之后， 进一步包括： 第二功能 实体在确认所述业务终止完成之后， 向第一功能实体进行响应， 表示业 务已终止。
6、如权利要求 1至 5中任意一项所述的方法， 其特征在于， 所述第 一功能实体为寻呼控制 /位置寄存实体 PC/LR, 或者为 PC/LR与访问地 代理 FA、 或数据路径功能实体 DPF、 或移动 IP访问地代理 MIP FA、 或 上下文功能实体 Context Function, 或认证功能实体 Authenticator, 或计 费客户端 Accounting Client, 或无线资源控制 RRC实体的组合体； 所述第二功能实体为： 策略控制和计费执行功能实体 PCEF, 或者 锚定业务流授权实体 SFA, 或者锚定 SFA与服务 SFA和\或代理 Agent 的组合体。
7、 如权利要求 6所述的方法， 其特征在于， 所述业务为： IP连通 接入网络 IP-CAN会话。
8、 一种终端处于空闲模式下实现业务终止的***， 其特征在于， 包 括： 第一设备和第二设备， 其中，
第一设备用于在判断出空闲模式下的终端处于丢失状态时， 向所述 第二设备发送请求消息；
第二设备用于根据第一设备发送的请求， 触发业务终止。
9、如权利要求 8所述的方法， 其特征在于， 所述请求消息中携带空 闲模式下终端丢失信息。
10、 如权利要求 9所述的***， 其特征在于， 该***进一步包括： 策略计费规则功能 /策略功能设备；
所述第二设备用于向所述策略计费规则功能 /策略功能设备发送携 带空闲模式下终端丢失信息的请求消息，通知策略计费规则功能 /策略功 能设备终止该终端的业务；
所述策略计费规则功能 /策略功能设备用于根据来自所述第二设备 的请求消息， 执行所述终止业务， 向所述第二设备进行响应， 表示业务 已终止。
11、 如权利要求 10所述的***， 其特征在于， 所述第二设备进一步 用于在业务终止后， 向所述第一设备进行响应， 表示业务已终止。
12、如权利要求 8至 11中任意一项所述的***， 其特征在于， 所述 第一设备为： 寻呼控制 /位置寄存实体 PC/LR, 或者 PC/LR与访问地代 理 FA、 或数据路径功能实体 DPF、 或移动 IP访问地代理 MIP FA、 或上 下文功能实体 Context Function, 或认证功能实体 Authenticator、 或计费 客户端 Accounting Client, 或无线资源控制 RRC实体的组合体；
所述第二设备为： 策略控制和计费执行功能实体 PCEF, 或者锚定 业务流授权实体 SFA, 或者锚定 SFA与服务 SFA和\或代理 Agent的组 合体。
13、 如权利要求 12所述的***， 其特征在于， 所述业务为 IP连通 接入网络 IP-CAN会话。
14、 一种状态检测设备， 其特征在于， 包括： 消息生成单元和收发 单元；
所述消息生成单元， 用于在空闲模式下的终端处于丢失状态时， 生 成包括空闲模式下终端丢失信息的请求消息， 并提供给所述收发单元； 所述收发单元， 用于接收消息生成单元提供的请求消息， 并发送该 请求消息； 接收表示业务已终止的响应消息。
15、如权利要求 14所述的状态检测设备， 其特征在于， 该设备进一 步包括状态判断单元， 用于判断空闲模式下的终端是否处于丢失状态， 如果是， 则获取丢失信息， 并提供给所述消息生成单元。
16、如权利要求 14所述的状态检测设备， 其特征在于， 该设备进一 步包括消息解析单元；
所述收发单元进一步用于接收来自外部的请求消息并提供给所述消 息解析单元；
所述消息解析单元用于对收发单元提供的请求消息进行解析， 并判 断该请求消息中是否携带空闲模式下终端丢失信息， 如果是， 则判断出 需要触发业务终止， 并将解析出的空闲模式下终端丢失信息提供给所述 消息生成单元；
所述消息生成单元进一步用于根据来自消息解析单元的空闲模式下 终端丢失信息， 生成包括所述来自消息解析单元的空闲模式下终端丢失 信息的请求消息， 并提供给收发单元。
17、 一种策略执行设备， 其特征在于， 包括： 收发单元和消息解析 单元；
所述收发单元， 用于接收和发送来自外部的表示业务已终止的请求 消息和响应消息； 将来自外部的请求消息提供给所述消息解析单元； 所述消息解析单元， 用于判断所述收发单元提供的请求消息是否是 由于空闲模式下的终端处于丢失状态而发送的， 如果是， 则触发业务终 止。
18、如权利要求 17所述的策略执行设备， 其特征在于， 该设备进一 步包括消息生成单元；
所述消息解析单元用于根据从请求消息中解析出的空闲模式下终端 丢失信息判断出需要触发业务终止， 并将解析出的空闲模式下的终端丢 失信息提供给所述消息生成单元；
所述消息生成单元用于根据来自消息解析单元的请求消息和空闲模 式下终端丢失信息， 生成包括所述来自消息解析单元的空闲模式下终端 丢失信息的请求消息， 并提供给收发单元；
所述收发单元进一步用于将来自所述消息生成单元的请求消息向外 部的策略计费规则功能和 /或策略功能实体 PCRF和 /或 PF发送， 请求终 止业务。
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
CN200710000967XA CN101227702B (zh) 2007-01-15 2007-01-15 终端处于空闲模式下的业务终止方法、***和设备
CN200710000967.X 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 (zh)
WO (1) WO2008086722A1 (zh)

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 (en) * 1997-09-29 1999-03-29 Telefonaktiebolaget Lm Ericsson Method and system for automatically connecting a call at a selected time in a radio telecommunications network
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 (en) * 1997-09-29 1999-03-29 Telefonaktiebolaget Lm Ericsson Method and system for automatically connecting a call at a selected time in a radio telecommunications network
CN1852384A (zh) * 2005-06-18 2006-10-25 华为技术有限公司 一种策略和计费规则决策的实现方法

Also Published As

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

Similar Documents

Publication Publication Date Title
JP4828608B2 (ja) 課金方法、課金システム、課金クライアントおよび課金処理手段
US7885636B2 (en) Data pre-paid in simple IP data roaming
WO2010108356A1 (zh) 一种终端通过多接入网接入的计费方法和***及上报方法
WO2013104234A1 (zh) 一种融合网络中策略控制方法及***
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 (zh) 一种计费会话管理方法、装置
WO2013064004A1 (zh) 一种更新服务质量的方法及***
WO2008083630A1 (fr) Procédé, système et dispositif pour une décision de stratégie et de règles
WO2013044730A1 (zh) 一种策略与计费规则的服务质量更新方法及***
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和***
WO2013060170A1 (zh) 一种提供基于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 (zh) 漫游本地业务的计费策略方法及装置
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、***及重定向dra
WO2009138016A1 (zh) 信息传递方法、装置和***
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
WO2010043095A1 (zh) 一种用于用户注册失败处理的方法及移动管理实体
WO2012155774A1 (zh) S9子会话建立方法、***及pcrf
WO2010118570A1 (zh) 一种WiMAX和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 (zh) 服务质量的更新处理方法及装置
WO2012019506A1 (zh) 在固网移动网络融合场景下实现资源控制的方法和***
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