WO2013170437A1 - 缺省承载上策略计费控制规则移除方法和装置 - Google Patents

缺省承载上策略计费控制规则移除方法和装置 Download PDF

Info

Publication number
WO2013170437A1
WO2013170437A1 PCT/CN2012/075503 CN2012075503W WO2013170437A1 WO 2013170437 A1 WO2013170437 A1 WO 2013170437A1 CN 2012075503 W CN2012075503 W CN 2012075503W WO 2013170437 A1 WO2013170437 A1 WO 2013170437A1
Authority
WO
WIPO (PCT)
Prior art keywords
port number
service flow
flow
service
description information
Prior art date
Application number
PCT/CN2012/075503
Other languages
English (en)
French (fr)
Inventor
时晓岩
乔伟华
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP12876611.0A priority Critical patent/EP2846581B1/en
Priority to PCT/CN2012/075503 priority patent/WO2013170437A1/zh
Priority to CN201280000657.7A priority patent/CN103535076B/zh
Publication of WO2013170437A1 publication Critical patent/WO2013170437A1/zh
Priority to US14/542,284 priority patent/US9838913B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for removing policy charging control rules on a default bearer.
  • the Evolved Packet Core (EPC) architecture is a mobile network architecture defined by the 3rd Generation Partnership Project (3GPP) in TS 23.401, which mainly includes packet data network gateways (Packet Data Network). a network element such as a gateway, a PGW, a Mobility Management Entity (MME), and a Policy Control and Charging Rules Function (PCRF), where the PGW is an EPC network and a packet providing a service
  • the interface gateway of the Data Network (PDN) is responsible for forwarding, filtering, assigning user IP addresses, performing Quality of Service (QoS) policies, and accounting for user data flows.
  • the MME is mainly responsible for user mobility.
  • PCRF Sex management and user's attached signaling processing, etc.
  • PCRF is based on user access network information (obtained from Gx interface), operator policy (local configuration), user subscription data (obtained from user subscription database), and user ongoing IP Multimedia Subsystem (IP Multimedia Subsyste
  • the m, IMS) service information (the IMS service information is obtained from the Rx interface) and the like, the Policy and Charging Control (PCC) rule is determined, and the rule is provided to the PGW for execution, thereby implementing policy charging control.
  • the PCC rule contains IP flow description information (for example, the source destination address of the IP packet, the source destination port number, etc.), the execution policy corresponding to the IP flow description information, QoS information (for example, priority, bandwidth, etc.), and the gate information. (forward/discard) and billing information, etc.
  • 3GPP also defines Single Radio Voice Call Continuity (SRVCC) in TS 23.216.
  • SRVCC is used to solve the continuity of voice calls when user equipment (UE) switches between different access technologies.
  • the problem which describes the process of the UE switching from the Circuit Switching (CS) domain of the 2G/3G network to the Packet Switching (PS) domain of the 3G/LTE network, that is, the UE is connected to the 2G/3G in 3GPP.
  • the IMS voice service is used in the incoming CS domain.
  • the UE moves out of the coverage of the CS domain or the CS domain signal is poor, the UE switches to The PS domain accessed by 3G/LTE continues to use the IMS voice service through the PS domain.
  • the basic principle of the IMS voice service switching from the CS domain to the PS domain is as follows: The UE completes the IMS registration in the PS domain in advance, and negotiates with the IMS network for information such as the IP port number of the UE side in the PS domain for voice service; When the IMS voice is switched from the CS domain to the PS domain, the core network element of the CS domain, the Mobile Switching Center (MSC), notifies the MME of the PS domain that the MME is about to switch to allow the MME to perform resource allocation in advance; at the same time, the MME and the IMS network. The interaction is performed to obtain an IP port number of the IMS network side allocated by the IMS network for the voice to be switched and sent to the terminal. In this way, the UE can be connected to the PS network to send and receive IMS voice data packets, ensuring continuity of the IMS voice service.
  • MSC Mobile Switching Center
  • the specific switching process of the IMS voice service in the SRVCC scenario includes steps S101 to S116, which are described as follows:
  • the base station controller or the radio network controller sends a handover request to the MSC.
  • the MSC interacts with the IMS network side device to obtain the IP ports allocated by the IMS network side device.
  • the MSC sends, to the target MME or the target SGSN, a handover request that the UE will be handed over to the PS domain by the CS domain, and the target MME or the target SGSN obtains an indication from the CS domain.
  • the target MME or the target SGSN sends a context (Context) request to the source MME or the source SGSN.
  • a context Context
  • the source MME or the source SGSN returns a response of the context request to the target MME or the target SGSN.
  • the target MME or the target SGSN completes resource reservation on the PS network side.
  • the target MME or the target SGSN returns a response of the handover request that the UE will switch from the CS domain to the PS domain to the MSC;
  • the MSC returns a response obtained by step S107 to the UE.
  • the MSC sends a session transfer preparation request to the IMS network side device, and the IMS network side device stops sending the voice service packet to the CS domain, and starts to send the voice service packet to the PS domain, where the source port of the packet is allocated by the IMS network side device.
  • IP port the destination port of the packet is the IP port of the UE side that the terminal negotiates with the IMS network side device in advance;
  • the UE switches to the PS domain.
  • the source MME or the source SGSN notifies the MSC that the terminal has completed the attachment of the PS domain.
  • the target MME or the target SGSN notifies the PS domain PGW that the terminal has completed the CS to PS switchover, ;
  • the PGW activates the PCC rule on the default bearer by interacting with the PCRF.
  • the PCC rules activated on the default bearer are used to temporarily transport IMS voice traffic from the circuit switched domain to the packet switched domain switch.
  • the source MME or the source SGSN releases resources by interacting with a base station controller or a radio network controller.
  • the UE interacts with the IMS network side device to notify the IMS network side device that the handover has been completed, and the IMS network side device triggers the PS domain to create a dedicated bearer for the IMS voice service of the UE, ensuring
  • the PCRF installs PCC rules for the default bearer on the PGW for temporary transmission of IMS voice traffic. After the establishment of the dedicated bearer of the IMS voice service, that is, after the step S117 of the foregoing process, the data message of the IMS voice starts to be sent on the dedicated bearer, and the PCC rule on the default bearer has lost its utility; For consideration, the PCC rules on the default bearer should be removed.
  • the method for deleting the PCC rule on the default bearer is implemented by a timer-based mechanism, that is, when the PCRF or the PGW installs the PCC rule on the default bearer for the IMS voice service that the CS switches to the PS, A timer, after exceeding the preset timer duration, deletes the PCC rule on the default bearer.
  • the above-mentioned prior art cannot actually accurately preset the timer duration because it is impossible to predict when the IMS network side device triggers the PS domain to create a dedicated bearer for the IMS voice service of the UE.
  • the timer duration is too short, the PCC rule on the default bearer is deleted before the dedicated bearer is created for the IMS voice service of the UE, and the UE cannot receive the data packet; Long, it will lead to long-term invalid PCC rules on the PGW, wasting resources.
  • the embodiment of the invention provides a method and a device for removing a policy charging control rule on a default bearer. Accurately remove temporary policy charging control rules and maintain continuity of user equipment voice services.
  • An embodiment of the present invention provides a method for removing a policy charging control rule on a default bearer, where the method includes: determining, when receiving the flow description information of the service flow, whether the received service flow is a single channel voice call continuity The service flow of the SRVCC handover; if the received service flow is a service flow of a single channel voice call continuity SRVCC handover, removing the policy charging control rule activated for the SRVCC handover on the default bearer and simultaneously Issue the policy charging control rules for the newly created bearer.
  • An embodiment of the present invention provides a device for removing a policy charging control rule on a default bearer, where the device includes: a determining module, configured to determine, when receiving the flow description information of the service flow, whether the received service flow is a single Channel voice call continuity SRVCC handover service flow; policy charging control rule processing module, configured to remove, if the judgment module determines that the received service flow is a single channel voice call continuity SRVCC handover service flow, The policy charging control rule activated for the SRVCC handover is performed on the default bearer, and the policy charging control rule defined for the newly created bearer is simultaneously delivered.
  • the method of removing the activated policy charging control rule on the default bearer is sent and newly issued. Bear the policy charging control rules.
  • the method provided by the embodiment of the present invention does not depend on the setting of the timer, as compared with the determination of whether the timer is set to expire on the default bearer. Therefore, there is no problem that the timer duration setting is inaccurate.
  • the activated policy charging control rule on the default bearer can be removed in time and accurately to maintain the continuity of the voice service of the user equipment. At the same time, the default is removed in time.
  • the activated policy charging control rules on the bearer also save resources.
  • FIG. 1 is a schematic flowchart of a method for removing a policy charging control rule on a default bearer according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of each function in a method for removing a policy charging control rule on a default bearer according to an embodiment of the present invention. Schematic diagram of the process of module interaction;
  • FIG. 3 is a schematic flowchart of interaction of each functional module in a method for removing a policy charging control rule on a default bearer according to another embodiment of the present invention
  • FIG. 4 is a schematic flowchart of interaction of various functional modules in a method for removing a policy charging control rule on a default bearer according to another embodiment of the present invention
  • FIG. 5 is a schematic flowchart of interaction of various functional modules in a method for removing a policy charging control rule on a default bearer according to another embodiment of the present invention
  • FIG. 6 is a schematic flowchart of interaction of each functional module in a method for removing a policy charging control rule on a default bearer according to another embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • 9b is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 10b is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • Figure lib is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to another embodiment of the present invention.
  • FIG. 13 is a diagram of a method for removing a policy charging control rule on a default bearer according to another embodiment of the present invention. Schematic.
  • the embodiment of the invention provides a method and a device for removing a policy charging control rule on a default bearer, and timely removes the temporary policy charging control rule and maintains the continuity of the voice service of the user equipment.
  • FIG. 1 is a schematic flowchart of a method for removing a policy charging control rule on a default bearer according to an embodiment of the present invention, where an executive body may be a policy control charging rule function entity PCRF or a packet data gateway PGW, etc.
  • the flow description information of the received service flow may be regarded as a trigger condition for determining whether the received service flow is a service flow of a single channel voice call continuity SRVCC handover, and the service flow may be The IMS voice service flow or the IMS video service flow
  • the flow description information may be an IMS service flow description information generated after the IMS service is switched from the circuit switched domain to the packet switched domain
  • the flow description information may be an IMS network device, such as an application function entity ( Application Function, AF) or the content of the service establishment or modification signaling sent by the Proxy Call Session Control Function (P-CSCF), or the Packet Data Network GateWay (PGW)
  • the content of the sent IP-CAN session modification signaling may also be a bearer resource command (Bearer Resource Command) received by the PGW from a Service Gate (SGW) or a Mobile Management Entity (MME). Contained content, source of flow description information of the present invention To which is not limited.
  • the received service flow is a service flow of a single-channel voice call continuity SRVCC handover, remove the policy charging control rule activated for the SRVCC handover on the default bearer and simultaneously deliver the new policy.
  • the bearer formulates the policy charging control rules.
  • the single channel voice call continuity SRVCC handover may be an IMS service from The switching of the circuit switched domain to the packet switched domain, and the service flow of the SRVCC handover may be an IMS service flow.
  • the system After the IMS service is switched from the circuit switched domain to the packet switched domain, the system creates a new bearer for the IMS service switched to the PS domain and formulates a policy charging control rule corresponding to the new bearer. .
  • the activated policy charging control rule that exists on the default bearer in the process of the IMS service switching from the circuit switched domain to the packet switched domain is no longer needed, and can be removed while being sent as the policy charging control rule for the newly created bearer.
  • the policy charging control rule activated for the SRVCC handover on the default bearer is temporarily used in the handover process of the IMS service from the circuit switched domain to the packet switched domain, after a new bearer corresponding policy charging control rule is formulated.
  • the activated policy charging control rule that exists on the default bearer in the process of the IMS service switching from the circuit switched domain to the packet switched domain is no longer needed, and can be removed while being sent as the policy charging control rule for the newly created bearer.
  • the policy charging control rule activated for the SRVCC handover on the default bearer is no longer needed, and can be removed while being sent as the policy charging control rule for the newly created bearer.
  • the device traffic is removed when it is determined that the received service flow is a single channel voice call continuity SRVCC handover service flow.
  • the policy-based charging control rule that is activated for the SRVCC switch and the policy-based charging control rule that is set for the newly-created bearer is delivered at the same time.
  • the problem of inaccurate setting of the timer of the activated policy charging control rule on the default bearer is deleted, and the activated policy charging control rule can be removed in time and accurately to maintain the continuous voice service of the user equipment.
  • timely removal of activated policy charging control rules on the default bearer also saves resources.
  • the flow description information includes a service flow packet, that is, an IP packet sent from the IMS network side device to the user equipment, or a port number of the IP packet sent by the user equipment to the IMS network side device, and the service flow report.
  • the port number of the text includes the destination port number and/or the source port number of the downlink packet of the service flow.
  • the "destination” in the destination port number” obviously refers to the user equipment, and the “source port number” The “source” obviously refers to the IMS network side device, and the destination port number of the service flow downlink>3 ⁇ 4 text corresponds to the source port number of the service flow uplink packet, and the source port number of the service flow downlink packet corresponds to the service flow uplink packet. Destination port number.
  • the traffic description information includes the port number of the service flow packet. Therefore, determining whether the received service flow is a single channel voice call continuity SRVCC handover service flow may be: a port number reserved for the SRVCC handover and the The port number of the service flow packet included in the flow description information is matched. The port number reserved by the SRVCC switch is consistent with the port number of the service flow packet included in the flow description information, and the received service flow is determined to be a service flow of the single channel voice call continuity SRVCC handover.
  • the port number reserved for the SRVCC handover may be an IMS network device, such as an application function entity (Application Function, AF) or a proxy voice session, during the handover of the IMS service from the circuit switched domain to the packet switched domain.
  • the content of the service establishment or modification signaling sent by the Proxy Call Session Control Function (P-CSCF) may also be the IP-CAN session modification signaling sent by the Packet Data Network GateWay (PGW).
  • PGW Packet Data Network GateWay
  • the content included may also be content included in a bearer resource command (Bearer Resource Command) from a Service Gate (SGW) or a Mobile Management Entity (MME) received by the PGW, and the present invention is directed to the service flow.
  • the source of the description information may not be limited.
  • the port number that is reserved for the SRVCC handover matches the port number of the service flow packet included in the flow description information.
  • the policy control charging rule function entity PCRF matches the destination port number of the service flow downlink message included in the flow description information with the port number reserved by the user equipment for SRVCC handover when registering with the IMS network.
  • the policy control charging rule function entity PCRF matches the destination port number of the service flow downlink message included in the flow description information with the port number reserved by the user equipment for SRVCC handover when registering with the IMS network,
  • the PCRF interacts with the application function entity AF or the proxy voice session control function entity P-CSCF to obtain the port number reserved for the SRVCC handover when the user equipment registers with the IMS network; and the handover of the IMS service from the circuit switched domain to the packet switched domain
  • the PCRF acquires the flow description information by interacting with the AF or P-CSCF.
  • the port number reserved for the SRVCC handover when the user equipment registers with the IMS network is also the destination port number of the downlink packet of the IMS service flow, and is of course the source port number of the uplink packet of the IMS service flow.
  • the flow of interaction of each functional module in the method for removing the policy charging control rule on the default bearer provided by the embodiment of the present invention includes steps S201 to S210. as follows:
  • the user equipment provides the IMS network with a port number reserved for SRVCC handover.
  • the port number reserved by the user equipment for the SRVCC handover to the IMS network may be the process of the IMS service being switched from the circuit switched domain to the packet switched domain, and the user equipment is reserved when registering with the IMS network, and the IMS service is switched from the circuit switched domain to the packet.
  • the information of the port number reserved by the user equipment for SRVCC handover can be sent to the IMS network through registration signaling.
  • the IMS network may specifically refer to an IMS network side device or an entity unit, for example, an application function entity (AF) or a proxy voice session control function (P-CSCF).
  • AF application function entity
  • P-CSCF proxy voice session control function
  • the AF or P-CSCF establishes an Rx session for registration signaling of the user equipment by interacting with the PCRF.
  • the AF or P-CSCF When the AF or P-CSCF establishes an Rx session for the registration signaling of the user equipment, it indicates to the PCRF the port number reserved by the user equipment for the SRVCC handover.
  • the port number reserved by the user equipment for the SRVCC handover is also the destination port number of the IMS service flow downlink packet, and is of course the source port number of the IMS service flow uplink packet.
  • the PCRF stores information that the user equipment reserves the port number reserved for the SRVCC handover.
  • the PCRF receives the "CS to PS SRVCC" indication from the packet data gateway PGW.
  • the "CS to PS SRVCC" indication indicates that the IMS service will switch from the circuit switched domain to the packet switched domain.
  • the PCRF formulates a Policy and Charging Control (PCC) rule for the default bearer.
  • PCC Policy and Charging Control
  • the default bearer is allowed to transmit data packets to or from the IMS network.
  • the specific method for formulating the PCC rule may be to directly activate the pre-configured PCC rule, or may be based on the information that the user equipment saved by the PCRF saved in the step S203 is reserved for the SRVCC handover.
  • the present invention applies the PCC on the default bearer. There are no restrictions on how the rules are formulated.
  • the PCRF returns a response to the PGW.
  • This response is used by the PGW to install the established PCC rules on the default bearer.
  • the user equipment instructs the IMS network to complete the SRVCC handover.
  • the Single Radio Voice Call Continuity (SRVCC) handover refers to the handover of the IMS voice service from the circuit switched domain to the packet switched domain.
  • an application function entity Application Function, AF
  • agent voice session control function entity p r0X y Call Session Control Function , P-CSCF
  • the signaling includes flow description information, for example, the destination port number, source port number, destination IP address, and source IP address of the IMS service flow downlink.
  • PCRF matches the port number.
  • the PCRF matches the destination port number of the service flow downlink message included in the flow description information with the port number reserved by the user equipment for SRVCC handover when registering with the IMS network.
  • the PCRF may further formulate, according to the flow description information sent by the AF or the P-CSCF, the PCC rule corresponding to the new bearer created by the system for switching to the IMS service of the PS domain.
  • the PCRF instructs the PGW to remove the PCC rule on the default bearer.
  • the PCRF instructs the PGW to remove the PCC rule that the PCRF is the default bearer in step S205.
  • the PCF rule may be sent to the PGW, so that the PGW is installed, and the PCC rule corresponding to the new bearer defined in the step S209 is sent to the PGW.
  • New PCC rules these new PCC rules are used for new bearer transmissions to switch to IMS services in the PS domain.
  • the port number reserved for the SRVCC handover is matched with the port number of the service flow packet included in the flow description information.
  • the policy control charging rule function entity PCRF matches the source port number of the service flow downlink message included in the flow description information with the port number reserved by the IMS network for SRVCC handover, and the policy control charging rule function Before the physical PCRF matches the source port number of the service flow downlink packet included in the flow description information with the port number reserved by the IMS network for the SRVCC handover, the PCRF interacts with the packet data gateway PGW to obtain the IMS network reserved for the SRVCC handover.
  • the port number after the handover process of the IMS service switching from the circuit switched domain to the packet switched domain is completed, the PCRF acquires the flow description information by interacting with the application function entity AF or the proxy voice session control function entity P-CSCF.
  • the IMS network reserves the port number reserved for the SRVCC handover, which is also the IMS service.
  • the source port number of the downstream packet is of course the destination port number of the IMS service flow uplink packet.
  • a flow of interaction of each functional module in a method for removing a policy charging control rule on a default bearer includes the following steps.
  • the base station controller initiates a handover request of the SRVCC.
  • the base station controller may be a base station controller of the circuit switched domain 2G (Base
  • BSC Station Controller
  • 3G Radio Network Controller Radio Network Controller
  • the mobile switching center MSC obtains the port number information reserved by the IMS network for the SRVCC handover from the IMS network.
  • the MSC interacts with the AF or the P-CSCF to obtain information of the port number reserved by the AF or the P-CSCF for the SRVCC handover from the AF or the P-CSCF.
  • the port number reserved by the AF or P-CSCF for the SRVCC handover is also the source port number of the IMS service flow downlink text, and is of course the destination port number of the IMS service flow uplink packet.
  • the mobile switching center MSC notifies the target mobility management entity MME of the handover event of the SRVCC.
  • the mobile switching center When the mobile switching center sends a notification, it indicates to the target mobility management entity MME the port number reserved by the AF or P-CSCF for SRVCC handover.
  • the target mobility management entity MME initiates a bearer modification process.
  • the signaling carries "CS to
  • the PS SRVCC indicates information such as the port number reserved for the SRVCC handover by the AF or P-CSCF, and the information is transmitted to the packet data gateway PGW through the Serving Gateway SGW.
  • the packet data gateway PGW initiates an IP-CAN session modification process.
  • the signaling carries the "CS to PS SRVCC" indication and the port number reserved by the AF or P-CSCF for SRVCC handover, and the information is sent to the policy control and
  • the charging rule function entity PCRF is saved by the PCRF.
  • the PCRF formulates a PCC rule for the default bearer.
  • the default bearer is allowed to be transmitted to or from the IMS network. Data message.
  • the specific method for formulating the PCC rule may be to directly activate the pre-configured PCC rule, and also to formulate the information.
  • the present invention may not limit the specific manner of formulating the PCC rule on the default bearer.
  • the PCRF returns a response to the PGW.
  • This response is used by the PGW to install the established PCC rules on the default bearer.
  • the user equipment instructs the IMS network to complete the SRVCC handover.
  • the Single Radio Voice Call Continuity (SRVCC) switchover in the embodiment of the present invention, refers to the IMS service switching from the circuit switched domain to the packet switched domain.
  • the application function (AF) or the proxy voice session control function (P-CSCF) initiates a service establishment or modification process.
  • the signaling sent to the PCRF includes flow description information, for example, a destination port number, a source port number, a destination IP address, and a source IP address of the IMS service flow downlink message, and the like. .
  • the PCRF matches the source port number of the service flow downlink packet included in the flow description information with the port number reserved by the AF or P-CSCF for SRVCC handover.
  • the PCRF may further formulate, according to the flow description information sent by the AF or the P-CSCF, the PCC rule corresponding to the new bearer created by the system for switching to the IMS service of the PS domain.
  • the PCRF instructs the PGW to remove the PCC rule on the default bearer.
  • the PCRF instructs the PGW to remove the PCC rule that the PCRF is the default bearer in step S306. It should be noted that, in step S311, while instructing the PGW to remove the PCC rule on the default bearer, the PCRF may also send the PCC rule corresponding to the new bearer defined in step S310 to the PGW, so that the PGW is installed. New PCC rules, these new PCC rules are used for new bearer transmissions to switch to IMS services in the PS domain.
  • the port number of the service flow packet includes the source port number of the downlink packet of the service flow.
  • the port number reserved by the SRVCC switch matches the port number of the service flow packet included in the flow description information.
  • the packet data gateway PGW may match the source port number of the traffic flow included in the flow description information with the port number reserved by the IMS network for SRVCC handover, and the packet data gateway PGW will Before the source port number of the service flow downlink packet included in the flow description information matches the port number reserved by the IMS network for the SRVCC handover, the PGW interacts with the target mobility management entity MME to obtain the IMS network reserved for SRVCC handover. a port number; after the handover process of the IMS service switching from the circuit switched domain to the packet switched domain is completed, the PGW obtains the flow description information by interacting with the target MME.
  • the IMS network is an SRVCC handover pre-
  • the port number that is reserved is also the source port number of the IMS service flow downlink packet, and is of course the destination port number of the IMS voice service flow uplink packet.
  • each functional module in the method for removing the policy charging control rule on the default bearer includes steps S401 to S410. as follows:
  • the base station controller initiates a handover request of the SRVCC.
  • the base station controller may be a base station controller (BSC) of the circuit switched domain 2G or a radio network controller (RNC) of the 3G.
  • BSC base station controller
  • RNC radio network controller
  • the mobile switching center MSC obtains the port number information reserved by the IMS network for the SRVCC handover from the IMS network.
  • the MSC interacts with the AF or the P-CSCF to obtain information of the port number reserved by the AF or the P-CSCF for the SRVCC handover from the AF or the P-CSCF.
  • the port number reserved by the AF or P-CSCF for the SRVCC handover is also the source port number of the IMS service flow downlink packet, and is of course the destination port number of the IMS voice service flow uplink packet.
  • the mobile switching center notifies the target mobility management entity MME of the handover event of the SRVCC.
  • the mobile switching center sends a notification, it indicates to the target mobility management entity MME the port number reserved by the AF or P-CSCF for SRVCC handover.
  • the target mobility management entity MME initiates a modify bearer process.
  • the signaling carries the "CS to PS SRVCC" indication and the port number reserved by the AF or P-CSCF for the SRVCC handover, and the information is sent to the packet data gateway PGW through the serving gateway SGW. 5405.
  • the packet data gateway PGW activates the PCC rule on the default bearer.
  • the default bearer is allowed to transmit data packets to or from the IMS network.
  • the specific activation method of the PCC rule may be to directly activate the information of the port number reserved by the pre-configured PCC switch.
  • the specific activation mode of the PCC rule on the default bearer may be not limited.
  • the user equipment instructs the IMS network to complete the SRVCC handover.
  • the Single Radio Voice Call Continuity (SRVCC) switch in this embodiment, refers to the IMS service switching from the circuit switched domain to the packet switched domain.
  • the user equipment initiates a bearer modification process.
  • the signaling sent to the target mobility management entity MME includes the IMS service flow description information, for example, the destination port number, the source port number, the destination IP address, and the source IP address of the IMS service flow downlink packet. Wait.
  • the target mobility management entity MME forwards the flow description information to the packet data gateway PGW.
  • the IMS flow description information may be transmitted through the bearer resource signaling (Bearer Resource) to the PGW.
  • the bearer resource signaling carries the flow description information, for example, the destination port number, source port number, destination IP address, and source IP address of the service flow downlink message.
  • Packet Data Gateway PGW matches the port number.
  • the packet data gateway PGW matches the source port number of the service flow downlink packet included in the flow description information with the port number reserved by the AF or P-CSCF for SRVCC handover.
  • the packet data gateway PGW may further formulate, according to the flow description information sent by the target mobility management entity MME, a PCC rule corresponding to a new bearer created by the system to switch to the IMS voice service in the PS domain.
  • Packet Data Gateway The PGW removes the PCC rules on the default bearer.
  • the packet data gateway PGW removes the PCC rule that the packet data gateway PGW has activated on the default bearer in step S405.
  • step S410 while the PCC rule that has been activated on the default bearer is removed, the packet data gateway PGW may also use the PCC rule corresponding to the new bearer defined in step S409. Activated, these new PCC rules are used for new bearer transmissions to switch to the IMS service of the PS domain.
  • determining whether the received service flow is a single-channel voice call continuity SRVCC handover service flow may be, if the received signaling includes indicating an application function entity AF or a proxy voice session control function entity P
  • the service initiated by the CSCF is an indication that the circuit switched domain switches to the IMS service of the packet switched domain, and then determines that the received service flow is a service flow of the single channel voice call continuity SRVCC handover.
  • the flow of interaction of each functional module in the method for removing the policy charging control rule on the default bearer provided by the embodiment of the present invention includes steps S501 to S510. as follows:
  • the user equipment provides the IMS network with a port number reserved for SRVCC handover.
  • the port number reserved by the user equipment for the SRVCC handover to the IMS network may be the process of the IMS service being switched from the circuit switched domain to the packet switched domain, and the user equipment is reserved when registering with the IMS network, and the IMS service is switched from the circuit switched domain to the packet.
  • the information of the port number reserved by the user equipment for SRVCC handover can be sent to the IMS network through registration signaling.
  • the IMS network may specifically refer to an IMS network side device or an entity unit, for example, an application function entity (AF) or a proxy voice session control function (P-CSCF).
  • AF application function entity
  • P-CSCF proxy voice session control function
  • the 5502, AF or P-CSCF establishes an Rx session for registration signaling of the user equipment by interacting with the PCRF.
  • the AF or P-CSCF When the AF or P-CSCF establishes an Rx session for the registration signaling of the user equipment, it indicates to the PCRF the port number reserved by the user equipment for the SRVCC handover.
  • the port number reserved by the user equipment for the SRVCC handover is also the destination port number of the IMS service flow downlink packet, and is of course the source port number of the IMS service flow uplink packet.
  • the PCRF stores information that the user equipment reserves the port number reserved for the SRVCC handover.
  • the PCRF receives a "CS to PS SRVCC" indication from the packet data gateway PGW.
  • the "CS to PS SRVCC" indication indicates that the IMS service will switch from the circuit switched domain to the packet switched domain.
  • the PCRF formulates a Policy and Charging Control (PCC) rule for the default bearer.
  • PCC Policy and Charging Control
  • the default bearer is allowed to transmit data packets to or from the IMS network.
  • the specific method for formulating the PCC rule may be to directly activate the pre-configured PCC rule, or may be based on the information that the user equipment saved by the PCRF saved in the step S503 is reserved for the SRVCC handover.
  • the present invention applies the PCC on the default bearer. There are no restrictions on how the rules are formulated.
  • the PCRF returns a response to the PGW.
  • This response is used by the PGW to install the established PCC rules on the default bearer.
  • the user equipment instructs the IMS network to complete the SRVCC handover.
  • the Single Radio Voice Call Continuity (SRVCC) switch in this embodiment, refers to the IMS voice service switching from the circuit switched domain to the packet switched domain.
  • the application function entity Application Function, AF
  • agent voice session control function entity p r0X y Call Session Control Function , P-CSCF
  • the signaling includes the flow description information, and may also include the application function entity AF or the proxy voice session control function entity P-CSCF; An indication to switch to the IMS service of the packet switched domain.
  • the flow description information also includes the destination port number, source port number, destination IP address, and source IP address of the IMS service flow downlink.
  • the PCRF determines whether the received service flow is a service flow of a single channel voice call continuity SRVCC handover.
  • the signaling sent by the AF or P-CSCF may include the service initiated by the application function entity AF or the proxy voice session control function entity P-CSCF.
  • the indication that the circuit switched domain switches to the IMS service of the packet switched domain therefore, the PCRF can determine whether the received service flow is a single channel voice call continuity SRVCC switched service flow according to whether the indication is included in the signaling.
  • the PCRF may further formulate, according to the flow description information sent by the AF or the P-CSCF, a PCC rule corresponding to a new bearer created by the system to switch to the IMS voice service in the PS domain.
  • the PCRF instructs the PGW to remove the PCC rule on the default bearer. That is, if the PCRF determines that the received service flow is a service flow of the single-channel voice call continuity SRVCC handover, the PGW is instructed to remove the PCC rule that the PCRF is the default bearer in step S505.
  • the PCRF may also send the PCC rule corresponding to the new bearer defined in step S509 to the PGW, so that the PGW is installed.
  • New PCC rules these new PCC rules are used for new bearer transmissions to switch to IMS services in the PS domain.
  • the service flow that determines whether the received service flow is a single-channel voice call continuity SRVCC handover may be: if the received signaling includes a resource indicating that the user equipment applies for the circuit-switched domain.
  • the indication of switching to the IMS service of the packet switched domain determines that the received service flow is a service flow of a single channel voice call continuity SRVCC handover.
  • the base station controller initiates a handover request of the SRVCC.
  • the base station controller may be a base station controller (BSC) of the circuit switched domain 2G or a radio network controller (RNC) of the 3G.
  • BSC base station controller
  • RNC radio network controller
  • the mobile switching center MSC obtains the port number information reserved by the IMS network for the SRVCC handover from the IMS network.
  • the MSC interacts with the AF or the P-CSCF to obtain information of the port number reserved by the AF or the P-CSCF for the SRVCC handover from the AF or the P-CSCF.
  • the port number reserved by the AF or P-CSCF for SRVCC handover is also the destination port number of the IMS service flow downlink "3 ⁇ 4 text source port number, and of course, the IMS voice service flow uplink".
  • the mobile switching center notifies the target mobility management entity MME of the handover event of the SRVCC.
  • the mobile switching center sends a notification, it indicates to the target mobility management entity MME the port number reserved by the AF or P-CSCF for SRVCC handover.
  • the target mobility management entity MME initiates a modify bearer process.
  • the signaling carries the "CS to PS SRVCC" indication and the information such as the IMS port number reserved by the AF or P-CSCF for the SRVCC handover, and the information is sent to the packet data gateway through the serving gateway SGW. PGW.
  • Packet Data Gateway The PGW activates the PCC rule on the default bearer.
  • the default bearer is allowed to transmit data packets to or from the IMS network.
  • the specific activation method of the PCC rule may be to directly activate the information of the port number reserved by the pre-configured PCC switch.
  • the specific activation mode of the PCC rule on the default bearer may be not limited.
  • the user equipment instructs the IMS network to complete the SRVCC handover.
  • the Single Radio Voice Call Continuity (SRVCC) switch in this embodiment, refers to the IMS service switching from the circuit switched domain to the packet switched domain.
  • the user equipment initiates a bearer modification process.
  • the bearer resource modification signaling sent to the target mobility management entity MME includes the IMS service flow description information, for example, the destination port number, the source port number, the destination IP address, and the source of the IMS service flow downlink packet.
  • the IP address and the like; the bearer resource modification signaling may further include an indication indicating that the resource requested by the user equipment is used by the circuit switched domain to switch to the IMS service of the packet switched domain.
  • the target mobility management entity MME forwards the flow description information to the packet data gateway PGW.
  • the flow description information may be forwarded by the bearer resource command (Bearer Resource Command) sent to the PGW, that is, the bearer resource signaling carries the flow description information, for example, the destination port number, the source port number, and the destination IP address of the service flow downlink message. And source IP address and so on.
  • the bearer resource signaling may further include an indication that the user equipment sends the resource requested by the user equipment to the target mobility management entity MME by using the bearer resource modification signaling for the IMS service of the circuit switched domain to switch to the packet switched domain. .
  • the packet data gateway PGW determines whether the received service flow is a service flow of a single channel voice call continuity SRVCC handover.
  • the bearer resource signaling may further include an indication indicating that the resource requested by the user equipment is used for the IMS service of the circuit switched domain handover to the packet switched domain. Therefore, the packet data gateway PGW can determine whether the received service flow is a single-channel voice call continuity SRVCC handover service flow according to whether the bearer resource signaling contains the indication. S610. The packet data gateway PGW removes the PCC rule on the default bearer.
  • the packet data gateway PGW determines that the received traffic flow is a single channel voice call continuity
  • the service flow of the SRVCC handover removes the PCC rule activated by the packet data gateway PGW on the default bearer in step S605.
  • FIG. 7 is a schematic structural diagram of a device for removing a policy charging control rule on a default bearer according to an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown.
  • the default bearer policy charging control rule removal device illustrated in FIG. 7 includes a determining module 701 and a policy charging control rule processing module 702, where:
  • the determining module 701 is configured to determine, when the flow description information of the service flow is received, whether the received service flow is a single-channel voice call continuity SRVCC handover service flow.
  • the policy charging control rule processing module 702 is configured to: if the determining module 701 determines that the received service flow is a service flow of a single channel voice call continuity SRVCC handover, remove the SRVCC on the default bearer. The policy charging control rule is activated and the policy charging control rule is set for the newly created bearer.
  • each functional module is only an example, and the actual application may be implemented according to requirements, such as corresponding hardware configuration requirements or software implementation.
  • the above function allocation is performed by different functional modules, that is, the internal structure of the policy charging control rule removal device on the default bearer is divided into different functional modules to complete all or part of the functions described above.
  • the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be performed by corresponding hardware to execute corresponding software.
  • the foregoing determining module may be configured to perform the foregoing upon receipt.
  • the hardware that determines whether the received service flow is a single-channel voice call continuity SRVCC switched service flow may also be a general processor capable of executing a corresponding computer program to perform the foregoing functions. Or another hardware device; and the foregoing policy charging control rule processing module may be configured to execute the foregoing determining module (or the determining unit) to determine the received business.
  • the service flow is a service flow of the single-channel voice call continuity SRVCC handover, and the policy charging control rule activated for the SRVCC handover on the default bearer is removed and the policy charging control established for the newly created bearer is simultaneously delivered.
  • the hardware of the rule function such as the policy charging control rule processor, may also be a general processor or other hardware device capable of executing the corresponding computer program to perform the aforementioned functions (the various embodiments provided in the present specification may apply the above described principles).
  • the flow description information includes a port number of the service flow message
  • the determining module 701 may include a matching submodule 801 and a determining submodule 802.
  • FIG. 8 shows a default bearer policy charging rule removal device according to another embodiment of the present invention, where:
  • the matching submodule 801 is configured to match the port number reserved for the SRVCC handover with the port number of the service flow packet included in the flow description information;
  • the determining sub-module 802 is configured to determine that the received service flow is a single-channel voice call continuity, if the port number reserved for the SRVCC handover matches the port number of the packet included in the IMS voice service flow description information. SRVCC switched service flow.
  • the port number of the service flow message may include the destination port number of the service flow downlink.
  • the matching sub-module 801 illustrated in FIG. 8 may include a first matching unit 903, and the default bearer policy charging control rule removing device provided by another embodiment of the present invention, as shown in FIG. 9a, may be an example of FIG.
  • the policy-based charging rule function entity PCRF in the policy-based charging control rule removal method of the default bearer, the first matching unit 903 is configured to use the destination port number of the service flow downlink packet included in the flow description information
  • the user equipment matches the port number reserved for SRVCC handover when registering with the IMS network.
  • the matching sub-module 801 illustrated in FIG. 9a may further include a first acquiring unit 901 and a second obtaining unit 902, as shown in FIG. 9b, a default bearer policy charging control rule removing device provided by another embodiment of the present invention. , among them:
  • a first obtaining unit 901 configured to be used with an application function entity AF or a proxy voice session control function entity
  • the P-CSCF interacts to obtain a port number reserved for the SRVCC handover when the user equipment registers with the IMS network.
  • the second obtaining unit 902 is configured to: after the handover process of the IMS service switching from the circuit switched domain to the packet switched domain is completed, The stream description information is acquired by interacting with the AF or P-CSCF.
  • the port number of the service flow packet may include the source port number of the voice service flow downlink packet.
  • the matching sub-module 801 illustrated in FIG. 8 may include a second matching unit 1003. As shown in FIG. 10a, the default bearer policy charging control rule removing device provided by another embodiment of the present invention may be an example of FIG.
  • the default bearer is a policy control charging rule function entity PCRF in the policy charging control rule removal method
  • the second matching unit 1003 is configured to use the source port number of the service flow downlink packet included in the flow description information.
  • the IMS network matches the port numbers reserved for SRVCC handover.
  • the matching sub-module 801 illustrated in FIG. 10a may further include a third acquiring unit 1001 and a fourth obtaining unit 1002, as shown in FIG. 10b, a default bearer policy charging control rule removing device provided by another embodiment of the present invention. , among them:
  • the third obtaining unit 1001 is configured to interact with the packet data gateway PGW to obtain a source port number reserved by the IMS network for the SRVCC handover;
  • the fourth obtaining unit 1002 is configured to acquire the flow description information by interacting with the application function entity AF or the proxy voice session control function entity P-CSCF after the switching process of the IMS service switching from the circuit switched domain to the packet switched domain is completed.
  • the port number of the service flow message may include the source port number of the service flow downlink >3 ⁇ 4 text.
  • the matching sub-module 801 illustrated in FIG. 8 may include a third matching unit 1103, which is a default bearer policy charging control rule removing device provided by another embodiment of the present invention as shown in FIG. 11a, which may be an example of FIG.
  • the default bearer is the packet data gateway PGW in the policy charging control rule removal method, and the third matching unit 1103 is configured to use the source port number of the service flow downlink packet included in the flow description information and the IMS network as the SRVCC. Switch the reserved port number to match.
  • the matching sub-module 801 illustrated in FIG. 11a may further include a fifth acquiring unit 1101 and a sixth obtaining unit 1102, and the default bearer policy charging control rule removing device provided by another embodiment of the present invention is shown in FIG. , among them:
  • a fifth obtaining unit 1101 configured to interact with the target mobility management entity MME, to obtain a port number reserved by the IMS network for SRVCC handover when the IMS voice service is switched from the circuit switched domain to the packet switched domain; and a sixth obtaining unit 1102, configured to Switching of IMS services from circuit switched domain to packet switched domain After the change process is completed, the flow description information is obtained by interacting with the target ⁇ .
  • the default bearer policy charging control rule removal device illustrated in FIG. 7 may be the policy control charging rule function entity PCRF in the default bearer policy charging control rule removal method illustrated in FIG. 5, and the determining module thereof
  • the 701 may include a first judging unit 1201.
  • the first determining unit 1201 is configured to: if the received signaling includes an indication that the service initiated by the application function entity AF or the proxy voice session control function entity P-CSCF is an IMS service in which the circuit switched domain switches to the packet switched domain,
  • the incoming traffic is a traffic flow for a single channel voice call continuity SRVCC handover.
  • the default bearer policy charging control rule removing device illustrated in FIG. 7 may be the packet data gateway PGW in the policy charging control rule removal method on the default bearer illustrated in FIG. 6 , and the determining module 701 may include the first Second judging unit 1301.
  • the second determining unit 1301 is configured to determine, if the received signaling includes an indication that the resource requested by the user equipment is used for switching the IMS service of the circuit switched domain to the packet switched domain, to determine that the received service flow is a single channel voice call continuity. SRVCC switched service flow.
  • the policy charging control rule activated for the SRVCC handover on the default bearer is removed and simultaneously delivered as the newly created bearer. Policy charging control rules are developed.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.
  • ROM Read Only Memory
  • RAM Random Access Memory

Abstract

本发明提供缺省承载上策略计费控制规则移除方法和装置，以及时准确地移除临时的策略计费控制规则并保持用户设备语音业务的连续性。所述方法包括：在收到业务流的流描述信息时，判断收到的业务流是否为SRVCC切换的业务流；若所述收到的业务流是SRVCC切换的业务流，则移除在缺省承载上为所述SRVCC切换激活的策略计费控制规则并同时下发为新创建的承载制定的策略计费控制规则。本发明提供的方法并不依赖于定时器的设置，因此不存在定时器时长设置不准确的问题，可以将缺省承载上已激活策略计费控制规则及时准确地移除而能够保持用户设备语音业务的连续性，与此同时，及时移除缺省承载上已激活策略计费控制规则也节省了资源。

Description

缺省承载上策略计费控制规则移除方法和装置 技术领域
本发明涉及通信领域，尤其涉及缺省承载上策略计费控制规则移除方法和 装置。
背景技术
演进分组核心网 （Evolved Packet Core, EPC ) 架构是第三代合作伙伴项 目 （ 3rd Generation Partnership Project, 3GPP )在 TS 23.401里定义的一种移动 网络架构，其主要包括分组数据网网关（ Packet Data Network Gateway, PGW )、 移动性管理实体 ( Mobility Management Entity, MME )和策略控制和计费规则 功能实体 ( Policy Control and charging Rules Function , PCRF )等网元， 其中， PGW为 EPC网络与提供服务的分组数据网 （ Packet Data Network, PDN ) 的接 口网关， 负责对用户数据流进行转发、 过滤、 分配用户 IP地址、 执行服务质量 ( Quality of Service, QoS )策略和计费等； MME主要负责用户的移动性管理 和用户的附着信令处理等； PCRF根据用户接入网络信息 （从 Gx接口获取） 、 运营商策略（在本地配置）、 用户签约数据（从用户签约数据库获取）和用户 当前正在进行的 IP多媒体子系统（IP Multimedia Subsystem, IMS )业务信息 ( IMS业务信息从 Rx接口获得）等决策出策略计费控制 （Policy and Charging Control, PCC )规则， 并将该规则提供给 PGW执行， 从而实现策略计费控制。 PCC规则含有 IP流描述信息（例如， IP报文的源目的地址、 源目的端口号等）、 与 IP流描述信息对应的执行策略、 QoS信息 （例如， 优先级、 带宽等） 、 门控 信息 （转发 /丟弃）和计费信息等等。
3GPP在 TS 23.216里还定义了单信道语音呼叫连续性（Single Radio Voice Call Continuity, SRVCC ) , SRVCC用于解决用户设备 ( User Equipment, UE ) 在不同接入技术间切换时， 语音呼叫的连续性问题， 其中描述了 UE从 2G/3G 网络的电路交换（ Circuit Switching, CS )域向 3G/LTE网络的分组交换（ Packet Switching, PS )域切换的流程， 即， UE在 3GPP的 2G/3G接入的 CS域下使用 IMS 语音业务， 当用 UE移动出 CS域的覆盖范围或者 CS域信号较差时， UE切换至 3G/LTE接入的 PS域， 通过 PS域继续使用 IMS语音业务。 IMS语音业务从 CS域 向 PS域切换的基本原理是： UE预先在 PS域完成 IMS注册，并与 IMS网络协商好 在 PS域进行语音业务的 UE侧的 IP端口号等信息； 当 UE准备将 IMS语音从 CS域 切换至 PS域时， CS域的核心网元移动交换中心（ Mobile Switching Center, MSC ) 通知 PS域的 MME即将发生切换以便 MME预先进行资源分配；与此同时， MME 与 IMS网络交互以获取 IMS网络为待切换语音分配的 IMS网络侧的 IP端口号并 发送给终端。 如此， 可以使得 UE—附着至 PS网络就可以发送和接受 IMS语音 数据报文， 确保了 IMS语音业务的连续性。
SRVCC场景下 IMS语音业务的具体切换流程包括步骤 S101至步骤 S116, 说明如下：
5101 , 基站控制器或无线网络控制器向 MSC发送切换请求；
5102, MSC与 IMS网络侧设备交互， 获取 IMS网络侧设备分配的 IP端口号 ( media ports ) ；
5103, MSC向目标 MME或目标 SGSN发送 UE将由 CS域切换至 PS域的切换 请求， 目标 MME或目标 SGSN获取来自 CS域的指示；
5104, 目标 MME或目标 SGSN向源 MME或源 SGSN发送上下文（ Context ) 请求；
5105 , 源 MME或源 SGSN向目标 MME或目标 SGSN返回上下文请求的响 应；
S106, 目标 MME或目标 SGSN完成 PS网络侧的资源预留；
5107, 目标 MME或目标 SGSN向 MSC返回 UE将由 CS域切换至 PS域的切换 请求的响应；
5108, MSC向 UE返回步骤 S107获得的响应；
5109, MSC向 IMS网络侧设备发送会话转移准备请求， IMS网络侧设备停 止向 CS域发送语音业务报文而开始向 PS域发送语音业务报文， 报文的源端口 为 IMS网络侧设备分配的 IP端口， 报文的目的端口为终端预先与 IMS网络侧设 备协商的 UE侧的 IP端口；
5110, UE切换至 PS域； 5111 , 源 MME或源 SGSN通知 MSC "终端已经完成 PS域的附着" ；
5112, 目标 MME或目标 SGSN通知 PS域 PGW "终端已经完成 CS至 PS的切 换，， ；
5113, PGW通过与 PCRF交互， 在缺省承载上激活 PCC规则；
在缺省承载上激活的 PCC规则用于从电路交换域向分组交换域切换中临 时传输 IMS语音业务。
S115, 源 MME或源 SGSN通过与基站控制器或无线网络控制器交互，释放 资源；
S116至 S117, UE与 IMS网络侧设备进行交互，通知 IMS网络侧设备已经完 成切换， IMS网络侧设备触发 PS域为 UE的 IMS语音业务创建专有承载， 保证
IMS语音业务的服务质量。
从上述切换流程可知， UE的 IMS语音业务从 CS域向 PS域切换过程中，
PCRF会在 PGW上为缺省承载安装 PCC规则以用于临时传输 IMS语音业务。 当 为 IMS语音业务的专有承载建立以后， 即上述流程的步骤 S117之后， IMS语音 的数据报文都开始在专有承载上发送， 缺省承载上的 PCC规则已经失去效用； 出于节省资源的考虑， 缺省承载上的 PCC规则应当予以删除。
现有技术提供的一种删除缺省承载上的 PCC规则是基于定时器的机制实 现， 即， 在 PCRF或者 PGW为 CS切换至 PS的 IMS语音业务安装缺省承载上的 PCC规则时， 同时启动一个定时器， 当超过预设的定时器时长后， 则删除缺省 承载上的 PCC规则。
由于很多场景下无法预测出 IMS网络侧设备何时触发 PS域为 UE的 IMS语 音业务创建专有承载， 因此， 上述现有技术实际上无法准确预设定时器时长。 如此， 若定时器时长预设过短， 则导致缺省承载上的 PCC规则在为 UE的 IMS 语音业务创建专有承载之前被删除， UE无法收到数据报文； 若定时器时长预 设过长， 则会导致 PGW上长期存在无效的 PCC规则， 浪费资源。
发明内容
本发明实施例提供缺省承载上策略计费控制规则移除方法和装置，以及时 准确地移除临时的策略计费控制规则并保持用户设备语音业务的连续性。
本发明实施例提供一种缺省承载上策略计费控制规则移除方法，所述方法 包括： 在收到业务流的流描述信息时， 判断收到的业务流是否为单信道语音呼 叫连续性 SRVCC切换的业务流； 若所述收到的业务流是单信道语音呼叫连续 性 SRVCC切换的业务流，，则移除在缺省承载上为所述 SRVCC切换激活的策略 计费控制规则并同时下发为新创建的承载制定的策略计费控制规则。
本发明实施例提供一种缺省承载上策略计费控制规则移除装置，所述装置 包括： 判断模块， 用于在收到业务流的流描述信息时， 判断收到的业务流是否 为单信道语音呼叫连续性 SRVCC切换的业务流； 策略计费控制规则处理模块， 用于若所述判断模块判断所述收到的业务流是单信道语音呼叫连续性 SRVCC 切换的业务流， 则移除在缺省承载上为所述 SRVCC切换激活的策略计费控制 规则并同时下发为新创建的承载制定的策略计费控制规则。
从上述本发明实施例可知，由于是在判断缺省承载上存在已激活策略计费 控制规则时，指示移除所述缺省承载上已激活策略计费控制规则并同时下发为 新创建的承载制定的策略计费控制规则。与现有技术提供的以设定的定时器是 否超时作为是否删除缺省承载上已激活策略计费控制规则的判断依据相比，本 发明实施例提供的方法并不依赖于定时器的设置，因此不存在定时器时长设置 不准确的问题，可以将缺省承载上已激活策略计费控制规则及时准确地移除而 能够保持用户设备语音业务的连续性， 与此同时，及时移除缺省承载上已激活 策略计费控制规则也节省了资源。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对现有技术或实施例 描述中所需要使用的附图作筒单地介绍，显而易见地， 下面描述中的附图仅仅 是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动 性的前提下， 还可以如这些附图获得其他的附图。
图 1是本发明实施例提供的缺省承载上策略计费控制规则移除方法流程示 意图；
图 2本发明实施例提供的缺省承载上策略计费控制规则移除方法中各功能 模块交互的流程示意图；
图 3是本发明另一实施例提供的缺省承载上策略计费控制规则移除方法中 各功能模块交互的流程示意图；
图 4是本发明另一实施例提供的缺省承载上策略计费控制规则移除方法中 各功能模块交互的流程示意图；
图 5是本发明另一实施例提供的缺省承载上策略计费控制规则移除方法中 各功能模块交互的流程示意图；
图 6是本发明另一实施例提供的缺省承载上策略计费控制规则移除方法中 各功能模块交互的流程示意图；
图 7是本发明实施例提供的缺省承载上策略计费控制规则移除装置结构示 意图；
图 8是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置结 构示意图；
图 9a是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 9b是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 10a是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 10b是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 11a是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 lib是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 12是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图；
图 13是本发明另一实施例提供的缺省承载上策略计费控制规则移除装置 结构示意图。
具体实施方式
本发明实施例提供缺省承载上策略计费控制规则移除方法和装置，以及时 准确地移除临时的策略计费控制规则并保持用户设备语音业务的连续性。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例， 本领域普通技术人员在没有做出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
请参阅附图 1 , 是本发明实施例提供的缺省承载上策略计费控制规则移除 方法流程示意图， 其执行主体可以是策略控制计费规则功能实体 PCRF或分组 数据网关 PGW等， 主要包括步骤 S101和步骤 S102:
S101 ,在收到业务流的流描述信息时，判断收到的业务流是否为单信道语 音呼叫连续性 SRVCC切换的业务流。
在本发明实施例中， 收到业务流的流描述（ Flow Description )信息可以视 作收到的业务流是否为单信道语音呼叫连续性 SRVCC切换的业务流的判断的 触发条件， 业务流可以是 IMS语音业务流或者 IMS视频业务流， 流描述信息可 以为 IMS业务从电路交换域向分组交换域切换完成后生成的 IMS业务流描述信 息，流描述信息可以是 IMS网络设备，例如应用功能实体（ Application Function, AF ) 或代理语音会话控制功能实体 ( Proxy Call Session Control Function, P-CSCF )发送的业务建立或者修改信令所包含的内容， 也可以是分组数据网 关（ Packet data network GateWay, PGW )发送的 IP-CAN会话修改信令包含的 内容， 还可以是 PGW接收的来自服务网关（Service GateWay, SGW )或移动 管理实体（ Mobile Management Entity, MME )的承载资源信令（ Bearer Resource Command )所包含的内容， 本发明对流描述信息的来源可以不做限定。
S102, 若所述收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务 流， 则移除在缺省承载上为所述 SRVCC切换激活的策略计费控制规则并同时 下发为新创建的承载制定的策略计费控制规则。
在本发明实施例中，单信道语音呼叫连续性 SRVCC切换可以是 IMS业务从 电路交换域向分组交换域的切换， SRVCC切换的业务流可以是 IMS业务流。 当 IMS业务从电路交换域向分组交换域切换完成后， 系统为切换至 PS域的 IMS业 务创建了新的承载（Bearer ) 以及制定了与该新的承载相应的策略计费控制规 贝 'J。由于在缺省承载上为 SRVCC切换激活的策略计费控制规则是 IMS业务从电 路交换域向分组交换域切换过程中临时使用， 因此，在制定了新的承载相应的 策略计费控制规则后， 不再需要 IMS业务从电路交换域向分组交换域切换过程 中缺省承载上存在的已激活策略计费控制规则，在下发为新创建的承载制定的 策略计费控制规则的同时， 可以移除缺省承载上为所述 SRVCC切换激活的策 略计费控制规则。
从上述本发明实施例提供的缺省承载上策略计费控制规则移除方法可知， 由于是在判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流 时， 才移除在缺省承载上为所述 SRVCC切换激活的策略计费控制规则并同时 下发为新创建的承载制定的策略计费控制规则， 因此， 与现有技术提供的以设 定的定时器是否超时作为是否删除缺省承载上已激活策略计费控制规则的判 定时器时长设置不准确的问题，可以将缺省承载上已激活策略计费控制规则及 时准确地移除而能够保持用户设备语音业务的连续性， 与此同时，及时移除缺 省承载上已激活策略计费控制规则也节省了资源。
在本发明实施例中， 流描述信息包含业务流报文即从 IMS网络侧设备向用 户设备下发的 IP报文或用户设备发送给 IMS网络侧设备的 IP报文的端口号， 业 务流报文的端口号包括业务流下行报文的目的端口号和 /或源端口号， 对于下 行"¾文， "目的端口号" 中的 "目的" 显然指用户设备， 而 "源端口号" 中的 "源"显然指 IMS网络侧设备， 而业务流下行 >¾文的目的端口号对应于业务流 上行报文的源端口号，业务流下行报文的源端口号对应于业务流上行报文的目 的端口号。
由于流描述信息包含了业务流报文的端口号， 因此， 判断收到的业务流是 否为单信道语音呼叫连续性 SRVCC切换的业务流可以是： 将为 SRVCC切换预 留的端口号与所述流描述信息包含的业务流报文的端口号进行匹配，若所述为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文的端口号匹配 一致， 则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流。 在本发明实施例中，为 SRVCC切换预留的端口号可以是在 IMS业务从电路交换 域向分组交换域切换过程中， IMS网络设备， 例如应用功能实体（Application Function, AF ) 或代理语音会话控制功能实体 ( Proxy Call Session Control Function, P-CSCF )发送的业务建立或者修改信令所包含的内容， 也可以是分 组数据网关（ Packet data network GateWay, PGW )发送的 IP-CAN会话修改信 令包含的内容， 还可以是 PGW接收的来自服务网关（Service GateWay, SGW ) 或移动管理实体 ( Mobile Management Entity, MME )的承载资源信令 ( Bearer Resource Command )所包含的内容， 本发明对业务流描述信息的来源可以不 做限定。
若业务流报文的端口号包括所述业务流下行报文的目的端口号，则作为将 为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文的端口号匹 配的一个实施例， 可以是策略控制计费规则功能实体 PCRF将所述流描述信息 包含的业务流下行报文的目的端口号与用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号匹配。 而在策略控制计费规则功能实体 PCRF将所述 流描述信息包含的业务流下行报文的目的端口号与用户设备在向 IMS网络注 册时为 SRVCC切换预留的端口号进行匹配之前，所述 PCRF与应用功能实体 AF 或代理语音会话控制功能实体 P-CSCF交互，获取用户设备在向 IMS网络注册时 为 SRVCC切换预留的端口号；在 IMS业务从电路交换域向分组交换域切换的切 换流程完成后， 所述 PCRF通过与所述 AF或 P-CSCF交互获取所述流描述信息。 在本实施例中， 用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号， 也 是 IMS业务流下行报文的目的端口号， 当然也是 IMS业务流上行报文的源端口 号。
为了更加清楚地说明上述实施例， 请参阅附图 2, 本发明实施例提供的缺 省承载上策略计费控制规则移除方法中各功能模块交互的流程，包括步骤 S201 至步骤 S210, 详细说明如下：
S201 , 用户设备向 IMS网络提供为 SRVCC切换预留的端口号。 用户设备向 IMS网络提供为 SRVCC切换预留的端口号可以是 IMS业务从 电路交换域向分组交换域切换过程中， 用户设备向 IMS网络注册时预留， 是将 IMS业务从电路交换域向分组交换域切换所作的准备工作之一。 用户设备为 SRVCC切换预留的端口号这一信息可以通过注册信令发送到 IMS网络。 IMS网 络具体可指 IMS网络侧设备或实体单元， 例如， 应用功能实体（Application Function, AF ) 或代理语音会话控制功能实体 ( Proxy Call Session Control Function, P-CSCF )等。
5202, AF或 P-CSCF通过与 PCRF交互， 为用户设备的注册信令建立 Rx会 话。
AF或 P-CSCF在为用户设备的注册信令建立 Rx会话时， 向 PCRF指明用户 设备为 SRVCC切换预留的端口号。 如前所述， 用户设备为 SRVCC切换预留的 端口号也是 IMS业务流下行报文的目的端口号， 当然也是 IMS业务流上行报文 的源端口号。
5203 , PCRF存储用户设备为 SRVCC切换预留的端口号这一信息。
S204, PCRF接收来自分组数据网关 PGW的 "CS to PS SRVCC" 指示。
"CS to PS SRVCC" 指示指明 IMS业务将从电路交换域向分组交换域切 换。
5205 , PCRF为缺省承载制定策略计费控制 （ Policy and Charging Control, PCC )规则。
为缺省承载制定 PCC规则后， 允许该缺省承载上传输发往或来自 IMS网络 的数据报文。 PCC规则的具体制定方法可以是直接激活预配置的 PCC规则， 也 可以是根据步骤 S203中 PCRF保存的用户设备为 SRVCC切换预留的端口号这 一信息制定， 本发明对缺省承载上的 PCC规则具体制定方式可不做限制。
5206, PCRF向 PGW返回响应。
该响应用于 PGW在缺省承载上安装制定的 PCC规则。
5207, 用户设备指示 IMS网络完成 SRVCC切换。
单信道语音呼叫连续性（ Single Radio Voice Call Continuity, SRVCC )切 换，在本发明实施例中，指的是 IMS语音业务从电路交换域向分组交换域切换。 5208, 应用功能实体 ( Application Function, AF )或代理语音会话控制功 能实体（ pr0Xy Call Session Control Function, P-CSCF )发起业务建立或者修改 流程。
AF或 P-CSCF发起的业务建立或者修改流程时， 其中的信令包含流描述信 息， 例如， IMS业务流下行 文的目的端口号、 源端口号、 目的 IP地址和源 IP 地址等等。
5209, PCRF匹配端口号。
在本实施例中， 具体是指 PCRF将流描述信息包含的业务流下行报文的目 的端口号与用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号匹配。
需要说明的是， 在步骤 S209中， PCRF还可以根据 AF或 P-CSCF发送的流 描述信息， 制定系统为切换至 PS域的 IMS业务创建的新的承载所对应的 PCC规 则。
5210, PCRF指示 PGW移除缺省承载上的 PCC规则。
即， PCRF指示 PGW移除步骤 S205中 PCRF为缺省承载制定的 PCC规则。 需要说明的是， 在步骤 S210中， 在指示 PGW移除缺省承载上的 PCC规则 的同时， PCRF还可以将步骤 S209中制定的新的承载所对应的 PCC规则下发至 PGW, 使得 PGW安装新的 PCC规则， 这些新的 PCC规则用于新的承载传输切 换至 PS域的 IMS业务。
若业务流报文的端口号包括业务流下行报文的源端口号， 则作为将为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文的端口号进行 匹配的另一实施例， 可以是策略控制计费规则功能实体 PCRF将流描述信息包 含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行 匹配， 而在策略控制计费规则功能实体 PCRF将流描述信息包含的业务流下行 报文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行匹配之前， 所述 PCRF与分组数据网关 PGW交互， 获取 IMS网络为 SRVCC切换预留的端口号； 在 IMS业务从电路交换域向分组交换域切换的切换流程完成后， 所述 PCRF通 过与应用功能实体 AF或代理语音会话控制功能实体 P-CSCF交互获取所述流描 述信息。 在本实施例中， IMS网络为 SRVCC切换预留的端口号， 也是 IMS业务 流下行报文的源端口号， 当然也是 IMS业务流上行报文的目的端口号。
为了更加清楚地说明上述实施例， 请参阅附图 3, 本发明另一实施例提供 的缺省承载上策略计费控制规则移除方法中各功能模块交互的流程，包括步骤
S301至步骤 S311 , 详细说明如下：
S301 , 基站控制器发起 SRVCC的切换请求。
在本实施例中， 基站控制器可以是电路交换域 2G的基站控制器 （Base
Station Controller, BSC )或 3G的无线网络控制器（ Radio Network Controller,
RNC )。
S302 ,移动交换中心 MSC从 IMS网络获取 IMS网络为 SRVCC切换预留的端 口号信息。
具体地， 是 MSC与 AF或 P-CSCF交互， 从 AF或 P-CSCF处获取 AF或 P-CSCF 为 SRVCC切换预留的端口号这一信息。如前所述， AF或 P-CSCF为 SRVCC切换 预留的端口号也是 IMS业务流下行 文的源端口号， 当然也是 IMS业务流上行 报文的目的端口号。
S303, 移动交换中心 MSC向目标移动管理实体 MME通知 SRVCC的切换事 件。
移动交换中心发送通知时， 向目标移动管理实体 MME指明 AF或 P-CSCF 为 SRVCC切换预留的端口号。
5304, 目标移动管理实体 MME发起承载修改流程。
目标移动管理实体 MME发起承载修改流程时， 其中的信令中携带 "CS to
PS SRVCC" 指示和 AF或 P-CSCF为 SRVCC切换预留的端口号等信息， 这些信 息通过服务网关 SGW发送至分组数据网关 PGW。
5305 , 分组数据网关 PGW发起 IP-CAN会话修改流程。
分组数据网关 PGW发起 IP-CAN会话修改流程时， 其中的信令中携带 "CS to PS SRVCC" 指示和 AF或 P-CSCF为 SRVCC切换预留的端口号等信息， 这些 信息发送至策略控制和计费规则功能实体 PCRF, 由 PCRF保存。
5306, PCRF为缺省承载制定 PCC规则。
为缺省承载制定 PCC规则后， 允许该缺省承载上传输发往或来自 IMS网络 的数据报文。 PCC规则的具体制定方法可以是直接激活预配置的 PCC规则， 也 这一信息制定， 本发明对缺省承载上的 PCC规则具体制定方式可不做限制。
5307, PCRF向 PGW返回响应。
该响应用于 PGW在缺省承载上安装制定的 PCC规则。
5308, 用户设备指示 IMS网络完成 SRVCC切换。
单信道语音呼叫连续性（ Single Radio Voice Call Continuity, SRVCC )切 换， 在本发明实施例中， 指的是 IMS业务从电路交换域向分组交换域切换。
5309, 应用功能实体（Application Function, AF )或代理语音会话控制功 能实体（ Proxy Call Session Control Function, P-CSCF )发起业务建立或者修改 流程。
AF或 P-CSCF发起业务建立或者修改流程时，发送给 PCRF的信令包含流描 述信息， 例如， IMS业务流下行报文的目的端口号、 源端口号、 目的 IP地址和 源 IP地址等等。
S310, PCRF匹配端口号。
在本实施例中， 具体是指 PCRF将流描述信息包含的业务流下行报文的源 端口号与 AF或 P-CSCF为 SRVCC切换预留的端口号匹配。
需要说明的是， 在步骤 S310中， PCRF还可以根据 AF或 P-CSCF发送的流 描述信息， 制定系统为切换至 PS域的 IMS业务创建的新的承载所对应的 PCC规 则。
S311 , PCRF指示 PGW移除缺省承载上的 PCC规则。
即， PCRF指示 PGW移除步骤 S306中 PCRF为缺省承载制定的 PCC规则。 需要说明的是， 在步骤 S311中， 在指示 PGW移除缺省承载上的 PCC规则 的同时， PCRF还可以将步骤 S310中制定的新的承载所对应的 PCC规则下发至 PGW, 使得 PGW安装新的 PCC规则， 这些新的 PCC规则用于新的承载传输切 换至 PS域的 IMS业务。
若业务流报文的端口号包括所述业务流下行报文的源端口号，则作为将为
SRVCC切换预留的端口号与所述流描述信息包含的业务流报文的端口号匹配 的又一实施例， 可以是分组数据网关 PGW将所述流描述信息包含的业务流下 行 "¾文的源端口号与 IMS网络为 SRVCC切换预留的端口号匹配，而在分组数据 网关 PGW将所述流描述信息包含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预留的端口号匹配之前， 所述 PGW与目标移动管理实体 MME交 互， 获取 IMS网络为 SRVCC切换预留的端口号； 在 IMS业务从电路交换域向分 组交换域切换的切换流程完成后， 所述 PGW通过与所述目标 MME交互获取所 述流描述信息。 在本实施例中， IMS网络为 SRVCC切换预留的端口号也是 IMS 业务流下行报文的源端口号， 当然也是 IMS语音业务流上行报文的目的端口 号。
为了更加清楚地说明上述实施例， 请参阅附图 4, 本发明实施例提供的缺 省承载上策略计费控制规则移除方法中各功能模块交互的流程，包括步骤 S401 至步骤 S410, 详细说明如下：
5401 , 基站控制器发起 SRVCC的切换请求。
在本实施例中， 基站控制器可以是电路交换域 2G的基站控制器 （Base Station Controller, BSC )或 3G的无线网络控制器（ Radio Network Controller, RNC )。
5402 ,移动交换中心 MSC从 IMS网络获取 IMS网络为 SRVCC切换预留的端 口号信息。
具体地， 是 MSC与 AF或 P-CSCF交互， 从 AF或 P-CSCF处获取 AF或 P-CSCF 为 SRVCC切换预留的端口号这一信息。如前所述， AF或 P-CSCF为 SRVCC切换 预留的端口号也是 IMS业务流下行报文的源端口号， 当然也是 IMS语音业务流 上行报文的目的端口号。
5403, 移动交换中心向目标移动管理实体 MME通知 SRVCC的切换事件。 移动交换中心发送通知时， 向目标移动管理实体 MME指明 AF或 P-CSCF 为 SRVCC切换预留的端口号。
5404, 目标移动管理实体 MME发起修改承载流程。
其中的信令中携带 "CS to PS SRVCC"指示和 AF或 P-CSCF为 SRVCC切换 预留的端口号等信息，这些信息通过服务网关 SGW发送至分组数据网关 PGW。 5405 , 分组数据网关 PGW激活缺省承载上的 PCC规则。
将缺省承载上的 PCC规则激活后， 允许该缺省承载上传输发往或来自 IMS 网络的数据报文。 PCC规则的具体激活方法可以是直接激活预配置的 PCC规 切换预留的端口号这一信息制定，本发明对缺省承载上的 PCC规则具体激活方 式可不做限制。
5406, 用户设备指示 IMS网络完成 SRVCC切换。
单信道语音呼叫连续性（ Single Radio Voice Call Continuity, SRVCC )切 换， 在本实施例中， 指的是 IMS业务从电路交换域向分组交换域切换。
S407, 用户设备发起承载修改流程。
用户设备发起承载修改流程时， 发送给目标移动管理实体 MME的信令包 含 IMS业务流描述信息， 例如， IMS业务流下行报文的目的端口号、 源端口号、 目的 IP地址和源 IP地址等等。
5408, 目标移动管理实体 MME向分组数据网关 PGW转发流描述信息。 IMS流描述信息可以通过向 PGW发送的承载资源信令（Bearer Resource
Command )转发， 即， 承载资源信令携带流描述信息， 例如， 业务流下行报 文的目的端口号、 源端口号、 目的 IP地址和源 IP地址等等。
5409, 分组数据网关 PGW匹配端口号。
在本实施例中， 具体是指分组数据网关 PGW将流描述信息包含的业务流 下行报文的源端口号与 AF或 P-CSCF为 SRVCC切换预留的端口号匹配。
需要说明的是， 在步骤 S409中， 分组数据网关 PGW还可以根据目标移动 管理实体 MME发送的流描述信息， 制定系统为切换至 PS域的 IMS语音业务创 建的新的承载所对应的 PCC规则。
5410, 分组数据网关 PGW移除缺省承载上的 PCC规则。
即， 分组数据网关 PGW移除步骤 S405中该分组数据网关 PGW在缺省承载 上已激活的 PCC规则。
需要说明的是， 在步骤 S410中， 在移除缺省承载上已激活的 PCC规则的同 时， 分组数据网关 PGW还可以将步骤 S409中制定的新的承载所对应的 PCC规 激活， 这些新的 PCC规则用于新的承载传输切换至 PS域的 IMS业务。 在本发明实施例中， 判断收到的业务流是否为单信道语音呼叫连续性 SRVCC切换的业务流还可以是， 若收到的信令包含指明应用功能实体 AF或代 理语音会话控制功能实体 P-CSCF发起的业务为电路交换域切换至分组交换域 的 IMS业务的指示，则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换 的业务流。 为了更加清楚地说明本实施例， 请参阅附图 5 , 本发明实施例提供 的缺省承载上策略计费控制规则移除方法中各功能模块交互的流程，包括步骤 S501至步骤 S510, 详细说明如下：
5501 , 用户设备向 IMS网络提供为 SRVCC切换预留的端口号。
用户设备向 IMS网络提供为 SRVCC切换预留的端口号可以是 IMS业务从 电路交换域向分组交换域切换过程中， 用户设备向 IMS网络注册时预留， 是将 IMS业务从电路交换域向分组交换域切换所作的准备工作之一。 用户设备为 SRVCC切换预留的端口号这一信息可以通过注册信令发送到 IMS网络。 IMS网 络具体可指 IMS网络侧设备或实体单元， 例如， 应用功能实体（Application Function, AF ) 或代理语音会话控制功能实体 ( Proxy Call Session Control Function, P-CSCF )等。
5502, AF或 P-CSCF通过与 PCRF交互， 为用户设备的注册信令建立 Rx会 话。
AF或 P-CSCF在为用户设备的注册信令建立 Rx会话时， 向 PCRF指明用户 设备为 SRVCC切换预留的端口号。 在本实施例， 用户设备为 SRVCC切换预留 的端口号也是 IMS业务流下行报文的目的端口号， 当然也是 IMS业务流上行报 文的源端口号。
5503 , PCRF存储用户设备为 SRVCC切换预留的端口号这一信息。
5504, PCRF接收来自分组数据网关 PGW的 "CS to PS SRVCC" 指示。
"CS to PS SRVCC" 指示指明 IMS业务将从电路交换域向分组交换域切 换。
5505 , PCRF为缺省承载制定策略计费控制 （ Policy and Charging Control, PCC )规则。 为缺省承载制定 PCC规则后， 允许该缺省承载上传输发往或来自 IMS网络 的数据报文。 PCC规则的具体制定方法可以是直接激活预配置的 PCC规则， 也 可以是根据步骤 S503中 PCRF保存的用户设备为 SRVCC切换预留的端口号这 一信息制定， 本发明对缺省承载上的 PCC规则具体制定方式可不做限制。
S506, PCRF向 PGW返回响应。
该响应用于 PGW在缺省承载上安装制定的 PCC规则。
S507, 用户设备指示 IMS网络完成 SRVCC切换。
单信道语音呼叫连续性（ Single Radio Voice Call Continuity, SRVCC )切 换， 在本实施例中， 指的是 IMS语音业务从电路交换域向分组交换域切换。
S508, 应用功能实体（Application Function, AF )或代理语音会话控制功 能实体（ pr0Xy Call Session Control Function, P-CSCF )发起业务建立或者修改 流程。
AF或 P-CSCF发起的业务建立或者修改流程时， 其中的信令包含流描述信 息， 也可以包含指明应用功能实体 AF或代理语音会话控制功能实体 P-CSCF;^ 起的业务为电路交换域切换至分组交换域的 IMS业务的指示。 如前述实施例相 同， 流描述信息也包含 IMS业务流下行 文的目的端口号、 源端口号、 目的 IP 地址和源 IP地址等等。
5509, PCRF判断收到的业务流是否是单信道语音呼叫连续性 SRVCC切换 的业务流。
如前所述， 若在步骤 S508中， AF或 P-CSCF发起的业务建立或者修改流程 时， 其发送的信令可以包含指明应用功能实体 AF或代理语音会话控制功能实 体 P-CSCF发起的业务为电路交换域切换至分组交换域的 IMS业务的指示， 因 此， PCRF可以根据信令中是否包含这一指示判断收到的业务流是否是单信道 语音呼叫连续性 SRVCC切换的业务流。
需要说明的是， 在步骤 S509中， PCRF还可以根据 AF或 P-CSCF发送的流 描述信息， 制定系统为切换至 PS域的 IMS语音业务创建的新的承载所对应的 PCC规则。
5510, PCRF指示 PGW移除缺省承载上的 PCC规则。 即， 若 PCRF判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业 务流， 则指示 PGW移除步骤 S505中 PCRF为缺省承载制定的 PCC规则。
需要说明的是， 在步骤 S510中， 在指示 PGW移除缺省承载上的 PCC规则 的同时， PCRF还可以将步骤 S509中制定的新的承载所对应的 PCC规则下发至 PGW, 使得 PGW安装新的 PCC规则， 这些新的 PCC规则用于新的承载传输切 换至 PS域的 IMS业务。
在本发明另一实施例中，判断收到的业务流是否为单信道语音呼叫连续性 SRVCC切换的业务流还可以是： 若收到的信令包含指明用户设备申请的资源 用于电路交换域切换至分组交换域的 IMS业务的指示， 则判断收到的业务流是 单信道语音呼叫连续性 SRVCC切换的业务流。 为了更加清楚地说明本实施例， 请参阅附图 6, 本发明实施例提供的缺省承载上策略计费控制规则移除方法中 各功能模块交互的流程， 包括步骤 S601至步骤 S610, 详细说明如下：
5601 , 基站控制器发起 SRVCC的切换请求。
在本实施例中， 基站控制器可以是电路交换域 2G的基站控制器 （Base Station Controller, BSC )或 3G的无线网络控制器（ Radio Network Controller, RNC )。
5602 ,移动交换中心 MSC从 IMS网络获取 IMS网络为 SRVCC切换预留的端 口号信息。
具体地， 是 MSC与 AF或 P-CSCF交互， 从 AF或 P-CSCF处获取 AF或 P-CSCF 为 SRVCC切换预留的端口号这一信息。在本实施例中， AF或 P-CSCF为 SRVCC 切换预留的端口号也是 IMS业务流下行 "¾文的源端口号， 当然也是 IMS语音业 务流上行"¾文的目的端口号。
5603 , 移动交换中心向目标移动管理实体 MME通知 SRVCC的切换事件。 移动交换中心发送通知时， 向目标移动管理实体 MME指明 AF或 P-CSCF 为 SRVCC切换预留的端口号。
5604, 目标移动管理实体 MME发起修改承载流程。
其中的信令中携带 "CS to PS SRVCC"指示和 AF或 P-CSCF为 SRVCC切换 预留的 IMS端口号等信息， 这些信息通过服务网关 SGW发送至分组数据网关 PGW。
5605 , 分组数据网关 PGW激活缺省承载上的 PCC规则。
将缺省承载上的 PCC规则激活后， 允许该缺省承载上传输发往或来自 IMS 网络的数据报文。 PCC规则的具体激活方法可以是直接激活预配置的 PCC规 切换预留的端口号这一信息制定，本发明对缺省承载上的 PCC规则具体激活方 式可不做限制。
5606, 用户设备指示 IMS网络完成 SRVCC切换。
单信道语音呼叫连续性（ Single Radio Voice Call Continuity, SRVCC )切 换， 在本实施例中， 指的是 IMS业务从电路交换域向分组交换域切换。
5607, 用户设备发起承载修改流程。
用户设备发起承载修改流程时， 发送给目标移动管理实体 MME的承载资 源修改信令包含 IMS业务流描述信息， 例如， IMS业务流下行报文的目的端口 号、 源端口号、 目的 IP地址和源 IP地址等等； 承载资源修改信令还可以包含指 明用户设备申请的资源用于电路交换域切换至分组交换域的 IMS业务的指示。
5608, 目标移动管理实体 MME向分组数据网关 PGW转发流描述信息。 流描述信息可以通过向 PGW发送的承载资源信令 （Bearer Resource Command )转发， 即， 承载资源信令携带流描述信息， 例如， 业务流下行报 文的目的端口号、 源端口号、 目的 IP地址和源 IP地址等等。 在本实施例中， 承 载资源信令还可以包含用户设备通过承载资源修改信令发送给目标移动管理 实体 MME的指明用户设备申请的资源用于电路交换域切换至分组交换域的 IMS业务的指示。
5609, 分组数据网关 PGW判断收到的业务流是否是单信道语音呼叫连续 性 SRVCC切换的业务流。
如前所述，若在步骤 S608中，承载资源信令还可以包含指明用户设备申请 的资源用于电路交换域切换至分组交换域的 IMS业务的指示。 因此， 分组数据 网关 PGW可以根据承载资源信令是否含有这一指示判断收到的业务流是否是 单信道语音呼叫连续性 SRVCC切换的业务流。 S610, 分组数据网关 PGW移除缺省承载上的 PCC规则。
即， 若分组数据网关 PGW判断收到的业务流是单信道语音呼叫连续性
SRVCC切换的业务流， 则移除步骤 S605中该分组数据网关 PGW在缺省承载上 已激活的 PCC规则。
需要说明的是， 在步骤 S610中， 在移除缺省承载上已激活的 PCC规则的同 时， 分组数据网关 PGW还可以将步骤 S609中制定的新的承载所对应的 PCC规 激活， 这些新的 PCC规则用于新的承载传输切换至 PS域的 IMS业务。 请参阅附 图 7 , 是本发明实施例提供的缺省承载上策略计费控制规则移除装置结构示意 图。 为了便于说明， 仅仅示出了与本发明实施例相关的部分。 附图 7示例的缺 省承载上策略计费控制规则移除装置包括判断模块 701和策略计费控制规则处 理模块 702, 其中：
判断模块 701 , 用于在收到业务流的流描述信息时， 判断收到的业务流是 否为单信道语音呼叫连续性 SRVCC切换的业务流。
策略计费控制规则处理模块 702,用于若所述判断模块 701判断所述收到的 业务流是单信道语音呼叫连续性 SRVCC切换的业务流， 则移除在缺省承载上 为所述 SRVCC切换激活的策略计费控制规则并同时下发为新创建的承载制定 的策略计费控制规则。
需要说明的是， 以上缺省承载上策略计费控制规则移除装置的实施方式 中， 各功能模块的划分仅是举例说明， 实际应用中可以根据需要， 例如相应硬 件的配置要求或者软件的实现的便利考虑，而将上述功能分配由不同的功能模 块完成，即将所述缺省承载上策略计费控制规则移除装置的内部结构划分成不 同的功能模块， 以完成以上描述的全部或者部分功能。 而且， 实际应用中， 本 实施例中的相应的功能模块可以是由相应的硬件实现，也可以由相应的硬件执 行相应的软件完成， 例如， 前述的判断模块， 可以是具有执行前述在收到业务 流的流描述信息时， 判断收到的业务流是否为单信道语音呼叫连续性 SRVCC 切换的业务流的硬件， 例如判断器，也可以是能够执行相应计算机程序从而完 成前述功能的一般处理器或者其他硬件设备；再如前述的策略计费控制规则处 理模块， 可以是具有执行前述若所述判断模块（或判断器）判断所述收到的业 务流是单信道语音呼叫连续性 SRVCC切换的业务流， 则移除在缺省承载上为 所述 SRVCC切换激活的策略计费控制规则并同时下发为新创建的承载制定的 策略计费控制规则功能的硬件， 例如策略计费控制规则处理器，也可以是能够 执行相应计算机程序从而完成前述功能的一般处理器或者其他硬件设备（本说 明书提供的各个实施例都可应用上述描述原则）。
在附图 7示例的缺省承载上策略计费控制规则移除装置中， 所述流描述信 息包含业务流报文的端口号，判断模块 701可以包括匹配子模块 801和判断子模 块 802,如附图 8所示本发明另一实施例提供的缺省承载上策略计费控制规则移 除装置， 其中：
匹配子模块 801用于将为 SRVCC切换预留的端口号与所述流描述信息包 含的业务流报文的端口号进行匹配；
判断子模块 802用于若所述为 SRVCC切换预留的端口号与所述 IMS语音业 务流描述信息包含的报文的端口号匹配一致，则判断收到的业务流是单信道语 音呼叫连续性 SRVCC切换的业务流。
附图 8示例的缺省承载上策略计费控制规则移除装置中， 业务流报文的端 口号可以包括业务流下行 文的目的端口号。附图 8示例的匹配子模块 801可以 包括第一匹配单元 903 , 如附图 9a所示本发明另一实施例提供的缺省承载上策 略计费控制规则移除装置， 可以为附图 2示例的缺省承载上策略计费控制规则 移除方法中的策略控制计费规则功能实体 PCRF,其第一匹配单元 903用于将所 述流描述信息包含的业务流下行报文的目的端口号与用户设备在向 IMS网络 注册时为 SRVCC切换预留的端口号进行匹配。
附图 9a示例的匹配子模块 801可以进一步包括第一获取单元 901和第二获 取单元 902, 如附图 9b所示本发明另一实施例提供的缺省承载上策略计费控制 规则移除装置， 其中：
第一获取单元 901 , 用于与应用功能实体 AF或代理语音会话控制功能实体
P-CSCF交互， 获取用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号； 第二获取单元 902, 用于在 IMS业务从电路交换域向分组交换域切换的切 换流程完成后， 通过与所述 AF或 P-CSCF交互获取所述流描述信息。 附图 8示例的缺省承载上策略计费控制规则移除装置中， 业务流报文的端 口号可以包括语音业务流下行报文的源端口号。 附图 8示例的匹配子模块 801 可以包括第二匹配单元 1003, 如附图 10a所示本发明另一实施例提供的缺省承 载上策略计费控制规则移除装置， 可以为附图 3示例的缺省承载上策略计费控 制规则移除方法中的策略控制计费规则功能实体 PCRF , 其第二匹配单元 1003 用于将所述流描述信息包含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行匹配。
附图 10a示例的匹配子模块 801可以进一步包括第三获取单元 1001和第四 获取单元 1002, 如附图 10b所示本发明另一实施例提供的缺省承载上策略计费 控制规则移除装置， 其中：
第三获取单元 1001 , 用于与分组数据网关 PGW交互， 获取 IMS网络为 SRVCC切换预留的源端口号；
第四获取单元 1002, 用于在 IMS业务从电路交换域向分组交换域切换的切 换流程完成后， 通过与应用功能实体 AF或代理语音会话控制功能实体 P-CSCF 交互获取所述流描述信息。
附图 8示例的缺省承载上策略计费控制规则移除装置中， 业务流报文的端 口号可以包括所业务流下行 >¾文的源端口号。附图 8示例的匹配子模块 801可以 包括第三匹配单元 1103, 如附图 11a所示本发明另一实施例提供的缺省承载上 策略计费控制规则移除装置， 可以为附图 4示例的缺省承载上策略计费控制规 则移除方法中的分组数据网关 PGW, 其第三匹配单元 1103用于将所述流描述 信息包含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预留的端口 号进行匹配。
附图 11a示例的匹配子模块 801可以进一步包括第五获取单元 1101和第六 获取单元 1102, 如附图 lib所示本发明另一实施例提供的缺省承载上策略计费 控制规则移除装置， 其中：
第五获取单元 1101 , 用于与目标移动管理实体 MME交互， 获取 IMS语音 业务从电路交换域向分组交换域切换时 IMS网络为 SRVCC切换预留的端口号； 第六获取单元 1102, 用于在 IMS业务从电路交换域向分组交换域切换的切 换流程完成后， 通过与所述目标 ΜΜΕ交互获取流描述信息。
附图 7示例的缺省承载上策略计费控制规则移除装置可以为附图 5示例的 缺省承载上策略计费控制规则移除方法中的策略控制计费规则功能实体 PCRF, 其判断模块 701可以包括第一判断单元 1201。 第一判断单元 1201用于若 收到的信令包含指明应用功能实体 AF或代理语音会话控制功能实体 P-CSCF发 起的业务为电路交换域切换至分组交换域的 IMS业务的指示， 则判断收到的业 务流是单信道语音呼叫连续性 SRVCC切换的业务流。
附图 7示例的缺省承载上策略计费控制规则移除装置可以为附图 6示例的 缺省承载上策略计费控制规则移除方法中的分组数据网关 PGW , 其判断模块 701可以包括第二判断单元 1301。 第二判断单元 1301用于若收到的信令包含指 明用户设备申请的资源用于电路交换域切换至分组交换域的 IMS业务的指示， 则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流。
需要说明的是， 上述装置各模块 /单元之间的信息交互、 执行过程等内容， 由于与本发明方法实施例基于同一构思，其带来的技术效果与本发明方法实施 例相同， 具体内容可参见本发明方法实施例中的叙述， 此处不再赘述。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成，比如以下各种方法的一种或多种 或全部：
在收到业务流的流描述信息时，判断收到的业务流是否为单信道语音呼叫 连续性 SRVCC切换的业务流；
若所述收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流， 则 移除在缺省承载上为所述 SRVCC切换激活的策略计费控制规则并同时下发为 新创建的承载制定的策略计费控制规则。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读 存储介质中， 存储介质可以包括： 只读存储器（ ROM, Read Only Memory ) 、 随机存取存储器（RAM, Random Access Memory ) 、 磁盘或光盘等。
以上对本发明实施例提供的缺省承载上策略计费控制规则移除方法和装 阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时, 对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围 上均会有改变之处， 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种缺省承载上策略计费控制规则移除方法， 其特征在于， 所述方法 包括：
在收到业务流的流描述信息时，判断收到的业务流是否为单信道语音呼叫 连续性 SRVCC切换的业务流；
若所述收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流，， 则 移除在缺省承载上为所述 SRVCC切换激活的策略计费控制规则并同时下发为 新创建的承载制定的策略计费控制规则。
2、 如权利要求 1所述的方法， 其特征在于， 所述流描述信息包含业务流报 文的端口号；
所述判断收到的业务流是否为单信道语音呼叫连续性 SRVCC切换的业务 流包括：
将为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文的端 口号进行匹配；
若所述为 SRVCC切换预留的端口号与所述流描述信息包含的报文的端口 号匹配一致， 则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业 务流。
3、 如权利要求 2所述的方法， 其特征在于， 所述业务流报文的端口号包括 业务流下行 文的目的端口号；
所述将为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文 的端口号进行匹配包括： 策略控制计费规则功能实体 PCRF将所述流描述信息 包含的业务流下行报文的目的端口号与用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号进行匹配。
4、 如权利要求 3所述的方法， 其特征在于， 所述策略控制计费规则功能实 体 PCRF将所述流描述信息包含的业务流下行报文的目的端口号与用户设备在 向 IMS网络注册时为 SRVCC切换预留的端口号进行匹配之前进一步包括：
所述 PCRF与应用功能实体 AF或代理语音会话控制功能实体 P-CSCF交互， 获取所述用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号； 在 IMS业务从电路交换域向分组交换域切换的切换流程完成后， 所述 PCRF通过与所述 AF或 P-CSCF交互获取所述流描述信息。
5、 如权利要求 2所述的方法， 其特征在于， 所述业务流报文的端口号包括 业务流下行 "¾文的源端口号；
所述将为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文 的端口号进行匹配包括： 策略控制计费规则功能实体 PCRF将所述流描述信息 包含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预留的端口号进 行匹配。
6、 如权利要求 5所述的方法， 其特征在于， 所述策略控制计费规则功能实 体 PCRF将所述流描述信息包含的业务流下行报文的源端口号与 IMS网络为
SRVCC切换预留的端口号进行匹配之前进一步包括：
所述 PCRF与分组数据网关 PGW交互， 获取 IMS网络为 SRVCC切换预留的 端口号；
在 IMS业务从电路交换域向分组交换域切换的切换流程完成后， 所述 PCRF通过与应用功能实体 AF或代理语音会话控制功能实体 P-CSCF交互获取 所述流描述信息。
7、 如权利要求 2所述的方法， 其特征在于， 所述业务流报文的端口号包括 所述业务流下行 >¾文的源端口号；
所述将为 SRVCC切换预留的端口号与所述流描述信息包含的业务流报文 的端口号进行匹配包括： 分组数据网关 PGW将所述流描述信息包含的业务流 下行 4艮文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行匹配。
8、 如权利要求 7所述的方法， 其特征在于， 所述分组数据网关 PGW将所 述流描述信息包含的业务流下行报文的源端口号与 IMS网络为 SRVCC切换预 留的端口号进行匹配之前进一步包括：
所述 PGW与目标移动管理实体 MME交互， 获取 IMS网络为 SRVCC切换预 留的端口号；
在 IMS业务从电路交换域向分组交换域切换的切换流程完成后，所述 PGW 通过与所述目标 MME交互获取所述流描述信息。
9、 如权利要求 1所述的方法， 其特征在于， 所述判断收到的业务流是否为 单信道语音呼叫连续性 SRVCC切换的业务流包括： 若收到的信令包含指明应 用功能实体 AF或代理语音会话控制功能实体 P-CSCF发起的业务为电路交换域 切换至分组交换域的 IMS业务的指示， 则判断收到的业务流是单信道语音呼叫 连续性 SRVCC切换的业务流。
10、 如权利要求 1所述的方法， 其特征在于， 所述判断收到的业务流是否 为单信道语音呼叫连续性 SRVCC切换的业务流包括： 若收到的信令包含指明 用户设备申请的资源用于电路交换域切换至分组交换域的 IMS业务的指示， 则 判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流。
11、 一种缺省承载上策略计费控制规则移除装置， 其特征在于， 所述装置 包括：
判断模块， 用于在收到业务流的流描述信息时， 判断收到的业务流是否为 单信道语音呼叫连续性 SRVCC切换的业务流；
策略计费控制规则处理模块，用于若所述判断模块判断所述收到的业务流 是单信道语音呼叫连续性 SRVCC切换的业务流， 则移除在缺省承载上为所述 SRVCC切换激活的策略计费控制规则并同时下发为新创建的承载制定的策略 计费控制规则。
12、 如权利要求 11所述的装置， 其特征在于， 所述流描述信息包含业务流 报文的端口号；
所述判断模块包括：
匹配子模块， 用于将为 SRVCC切换预留的端口号与所述流描述信息包含 的业务流 "¾文的端口号进行匹配；
判断子模块， 用于若所述为 SRVCC切换预留的端口号与所述流描述信息 包含的报文的端口号匹配一致，则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业务流。
13、 如权利要求 12所述的装置， 其特征在于， 所述业务流报文的端口号包 括业务流下行报文的目的端口号， 所述装置为策略控制计费规则功能实体 PCRF; 所述匹配子模块包括： 第一匹配单元， 用于将所述流描述信息包含的业务 流下行报文的目的端口号与用户设备在向 IMS网络注册时为 SRVCC切换预留 的端口号进行匹配。
14、 如权利要求 13所述的装置， 其特征在于， 所述匹配子模块还包括： 第一获取单元， 用于与应用功能实体 AF或代理语音会话控制功能实体
P-CSCF交互， 获取用户设备在向 IMS网络注册时为 SRVCC切换预留的端口号； 第二获取单元， 用于在 IMS业务从电路交换域向分组交换域切换的切换流 程完成后， 通过与所述 AF或 P-CSCF交互获取所述流描述信息。
15、 如权利要求 12所述的装置， 其特征在于， 所述业务流报文的端口号包 括业务流下行报文的源端口号，所述装置为策略控制计费规则功能实体 PCRF; 所述匹配子模块包括： 第二匹配单元， 用于将所述流描述信息包含的业务 流下行 >¾文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行匹配。
16、 如权利要求 15所述的装置， 其特征在于， 所述匹配子模块还包括： 第三获取单元， 用于与分组数据网关 PGW交互， 获取 IMS网络为 SRVCC 切换预留的端口号；
第四获取单元， 用于在 IMS业务从电路交换域向分组交换域切换的切换流 程完成后， 通过与应用功能实体 AF或代理语音会话控制功能实体 P-CSCF交互 获取所述流描述信息。
17、 如权利要求 12所述的装置， 其特征在于， 所述业务流报文的端口号包 括所述业务流下行报文的源端口号， 所述装置为分组数据网关 PGW;
所述匹配子模块包括： 第三匹配单元， 用于将所述流描述信息包含的业务 流下行 >¾文的源端口号与 IMS网络为 SRVCC切换预留的端口号进行匹配。
18、 如权利要求 17所述的装置， 其特征在于， 所述匹配子模块还包括： 第五获取单元， 用于与目标移动管理实体 MME交互， 获取 IMS网络为 SRVCC切换预留的端口号；
第六获取单元， 用于在 IMS业务从电路交换域向分组交换域切换的切换流 程完成后， 通过与所述目标 MME交互获取所述流描述信息。
19、 如权利要求 11所述的装置， 其特征在于， 所述装置为策略控制计费规 则功能实体 PCRF, 所述判断模块包括：
第一判断单元， 用于若收到的信令包含指明应用功能实体 AF或代理语音 会话控制功能实体 P-CSCF发起的业务为电路交换域切换至分组交换域的 IMS 业务的指示， 则判断收到的业务流是单信道语音呼叫连续性 SRVCC切换的业 务流。
20、 如权利要求 11所述的装置， 其特征在于， 所述装置为分组数据网关 PGW, 所述判断模块包括：
第二判断单元，用于若收到的信令包含指明用户设备申请的资源用于电路 交换域切换至分组交换域的 IMS业务的指示， 则判断收到的业务流是单信道语 音呼叫连续性 SRVCC切换的业务流。
PCT/CN2012/075503 2012-05-15 2012-05-15 缺省承载上策略计费控制规则移除方法和装置 WO2013170437A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP12876611.0A EP2846581B1 (en) 2012-05-15 2012-05-15 Method and device for removing policy and charging control rule on default bearer
PCT/CN2012/075503 WO2013170437A1 (zh) 2012-05-15 2012-05-15 缺省承载上策略计费控制规则移除方法和装置
CN201280000657.7A CN103535076B (zh) 2012-05-15 2012-05-15 缺省承载上策略计费控制规则移除方法和装置
US14/542,284 US9838913B2 (en) 2012-05-15 2014-11-14 Method and apparatus for removing policy and charging control rule from default bearer

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/075503 WO2013170437A1 (zh) 2012-05-15 2012-05-15 缺省承载上策略计费控制规则移除方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/542,284 Continuation US9838913B2 (en) 2012-05-15 2014-11-14 Method and apparatus for removing policy and charging control rule from default bearer

Publications (1)

Publication Number Publication Date
WO2013170437A1 true WO2013170437A1 (zh) 2013-11-21

Family

ID=49582985

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075503 WO2013170437A1 (zh) 2012-05-15 2012-05-15 缺省承载上策略计费控制规则移除方法和装置

Country Status (4)

Country Link
US (1) US9838913B2 (zh)
EP (1) EP2846581B1 (zh)
CN (1) CN103535076B (zh)
WO (1) WO2013170437A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108260097B (zh) * 2016-12-29 2020-07-31 中国移动通信集团公司 解决eSRVCC切换时误产生漫游计费的方法及eMSC
CN111770545B (zh) * 2019-04-02 2022-08-26 华为技术有限公司 一种业务流路由控制方法、装置及系统
US20230007128A1 (en) * 2021-07-01 2023-01-05 T-Mobile Usa, Inc. Voice packets over the control plane

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011047726A1 (en) * 2009-10-22 2011-04-28 Telefonaktiebolaget L M Ericsson (Publ) P-cscf address discovery
CN102238676A (zh) * 2010-04-30 2011-11-09 华为技术有限公司 电路交换域到分组交换域的切换方法和设备及通信系统
CN102387558A (zh) * 2007-08-21 2012-03-21 华为技术有限公司 一种演进网络切换过程中释放源网络资源的方法及系统
CN102415150A (zh) * 2009-04-23 2012-04-11 瑞典爱立信有限公司 Ps到cs切换指示符

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7333773B2 (en) * 2004-09-16 2008-02-19 International Business Machines Corporation Coordination of cellular telephones in a residential area to obviate need for wired residential service
US9294902B2 (en) * 2008-10-31 2016-03-22 Telefonaktiebolaget L M Ericsson (Publ) Policy and charging control method, servers and computer programs therefor
US9344924B2 (en) * 2008-11-27 2016-05-17 Htc Corporation Method of handling handover security configuration and related communication device
CN101924751B (zh) * 2009-05-22 2013-11-06 中兴通讯股份有限公司 一种单模业务连续性实现方法及单模业务连续性系统
US8929284B2 (en) * 2010-02-03 2015-01-06 Qualcomm Incorporated Method and apparatus to enable inter-system transfer of a packet switched session
US8903354B2 (en) * 2010-02-15 2014-12-02 Ford Global Technologies, Llc Method and system for emergency call arbitration
US20120003969A1 (en) * 2010-06-30 2012-01-05 Motorola, Inc. Method and apparatus for establishing a group call
EP3678428B1 (en) * 2010-08-18 2022-04-13 BlackBerry Limited Method to maintain call continuity
WO2012046930A1 (en) * 2010-10-04 2012-04-12 Lg Electronics Inc. Device and method for performing an rsrvcc procedure
WO2013110346A1 (en) * 2012-01-27 2013-08-01 Telefonaktiebolaget L M Ericsson (Publ) Single radio voice call continuity handover of calls with video media from a circuit switched access network
US8908681B1 (en) * 2012-05-31 2014-12-09 Sprint Communications Company L.P. Facilitating call continuity when transferring calls between a mobile access network to a VoIP network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387558A (zh) * 2007-08-21 2012-03-21 华为技术有限公司 一种演进网络切换过程中释放源网络资源的方法及系统
CN102415150A (zh) * 2009-04-23 2012-04-11 瑞典爱立信有限公司 Ps到cs切换指示符
WO2011047726A1 (en) * 2009-10-22 2011-04-28 Telefonaktiebolaget L M Ericsson (Publ) P-cscf address discovery
CN102238676A (zh) * 2010-04-30 2011-11-09 华为技术有限公司 电路交换域到分组交换域的切换方法和设备及通信系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2846581A4 *

Also Published As

Publication number Publication date
US20150063310A1 (en) 2015-03-05
EP2846581A4 (en) 2015-06-10
CN103535076B (zh) 2017-06-20
EP2846581B1 (en) 2018-06-27
CN103535076A (zh) 2014-01-22
US9838913B2 (en) 2017-12-05
EP2846581A1 (en) 2015-03-11

Similar Documents

Publication Publication Date Title
US9288816B2 (en) Providing service based on quality of service resources in a long term evolution communications system
US9078173B2 (en) Method for handover from circuit switched domain to packet switched domain, device, and communications system
US20140078898A1 (en) Handing off between networks with different radio access technologies during a communication session that is allocated quality of service
US9497684B2 (en) Radio access technology handover optimization in a push-to-talk session
KR101589586B1 (ko) 리버스 ｓｒｖｃｃ에서 음성 베어러를 선택하기 위한 장치 및 방법
JP6051214B2 (ja) 通信サービスのハンドオーバをハンドリングするための方法及び装置
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2008101392A1 (fr) Procédé de transmission de qualité de service lors de transfert entre systèmes et système de réseau et réseau de destination correspondants
US20130128816A1 (en) Method, Apparatus, and System for Setting Maximum Bandwidth
TR201815648T4 (tr) UTRAN'dan LTE'ye devir.
KR102114630B1 (ko) 데이터 서비스 제어 방법 및 관련 장치
WO2012041073A1 (zh) 一种实现流迁移的方法及系统
WO2009089790A1 (fr) Procédé pour l'acquisition du type d'un service support et pour la commutation entre réseaux supports pour des terminaux
WO2009026835A1 (fr) Système, appareil et procédé pour un transfert de service d'utilisateur
WO2016107404A1 (zh) 业务流传输路径优化方法、装置及mme
WO2014005444A1 (zh) 分流到无线局域网络的接入方法及系统、mme和ue
WO2009062392A1 (fr) Procédé de transfert de système, système de communication et entité pcrf
KR102170503B1 (ko) 이동통신시스템에서의 호출장치 및 방법
KR20150135035A (ko) 무선 랜으로 미디어 전송 시 사용자 체감 서비스 품질을 높이는 방법 및 장치
WO2011120222A1 (zh) 优先级业务激活、去激活方法、装置和系统
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
TWI427961B (zh) 封包資料支持節點及封包流內容於交遞時之啟動方法
WO2009149656A1 (zh) 一种实现业务切换的方法、装置及系统
WO2013170437A1 (zh) 缺省承载上策略计费控制规则移除方法和装置
WO2011134408A1 (zh) 选择性ip数据分流激活的通知及输出方法、系统和设备

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012876611

Country of ref document: EP