[go: up one dir, main page]

WO2009062392A1 - Procédé de transfert de système, système de communication et entité pcrf - Google Patents

Procédé de transfert de système, système de communication et entité pcrf Download PDF

Info

Publication number
WO2009062392A1
WO2009062392A1 PCT/CN2008/001815 CN2008001815W WO2009062392A1 WO 2009062392 A1 WO2009062392 A1 WO 2009062392A1 CN 2008001815 W CN2008001815 W CN 2008001815W WO 2009062392 A1 WO2009062392 A1 WO 2009062392A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
user terminal
gateway
policy
policy information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2008/001815
Other languages
English (en)
Chinese (zh)
Inventor
Jiande Xi
Xin Zhao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Publication of WO2009062392A1 publication Critical patent/WO2009062392A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • 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/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]

Definitions

  • the present invention relates to the field of communications, and in particular, to a technique for switching between systems. Background technique
  • 3GPP LTE EPS Evolved Packet system, Evolved Packet System
  • the 3GPP LTE EPS includes the following network elements:
  • the PDN GW Packet Data Network Gateway
  • the PDN GW is configured to perform an operation policy implementation of the operator, a deep detection of the data packet, and a function of assigning a user IP address, where the user IP address corresponds to the non-3GPP home network.
  • Mobile IPv4 HoA Mobile IPv4 Home of Address, Mobile IPv4 Home Address;).
  • Serving GW Serving Gateway
  • eNodeBs evolved NodeBs
  • 3GPP E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • GERAN GSM EDGE Radio Access Network, GSM Evolution Radio Access Network
  • UTRAN Universal Terrestrial Radio Access Network
  • HSS Home Subscriber Server
  • AAA server including AAA server and database
  • database is used to store subscription information of packet data.
  • 3GPP AAA Server (3GPP Authentication Authorization and Accounting Server, 3GPP authentication and authorization accounting server), used for authentication and authorization accounting, mainly for non-3GPP systems.
  • the PCRF (Policy Charging Rule Function) entity is used to implement the service QoS policy of the operator and the corresponding charging rule.
  • PMIPv6 exists on the connection interface S5 between the Serving GW and the PDN GW.
  • the S5 interface supports IP protocol.
  • the mobility of the UE, the user registration process of the layer 2, and the resource status of the air interface link level, the registration process of the IP layer of the management user, and the external agent (FA, Foreign Agent) function of the Mobile IP ( Entities for MIPv4) or Mobile Access Gateway (MAG) functions (for PMIP), and user mobility management functions may be located on the same entity, such as the Access Service Network Gateway (ASN GW, located in the Wimax system,
  • the Access Server Network Gateway may or may not be located on the same entity, such as a Packet Control Function (PCF) entity and a Packet Data Serving Node (PDSN) entity of the CDMA2000 system.
  • PCF Packet Control Function
  • PDSN Packet Data Serving Node
  • the connection between the UE and the non-3GPP access gateway responsible for the MIP FA/PMIPv6 MAG function uses a PPP (Point to Point Protocol) connection.
  • the Mobile IPv4 Home Agent (HA, Home Agent) / ⁇ Local Mobile Agent (LMA, Local Mobile Agent) function is located on the PDN GW.
  • Step 1 The user terminal sends the uplink data by using the PDN GW to the IP address of the PDN GW, and the uplink data is forwarded to the PDN GW by using the Serving GW route, and the PDN GW refers to the stored service policy information.
  • Uplink data is used for policy control, and the policy-controlled uplink data is sent to an external packet data network PDN (Packet Data Network); the PDN GW receives downlink data from the PDN, and performs policy control on the data according to the stored service policy information. And through The PMIPv6 or GTP tunnel between the Serving GW and the PDN GW sends the policy-controlled downlink data to the Serving GW, and forwards the data to the user terminal via the Serving GW route.
  • PDN Packet Data Network
  • Step 2 The user terminal searches for the trusted non-3GPP system and decides to transfer the service carried out with the current 3GPP system to the non-3GPP system.
  • Step 3a to step 3b The user terminal sends an access authentication request (Access Auth) message to the trusted non-3GPP system, where the user identifier MN-NAI and the IP address of the PDN GW requesting to establish an IP connection are carried; the non-3GPP system After receiving the access authentication request message, the IP access gateway interacts with the HSS/AAA server to perform an access authentication and authorization process for the user terminal.
  • Access Auth access authentication request
  • the 3GPP HSS/AAA server After the user terminal is authenticated and authorized, the 3GPP HSS/AAA server sends the IP address of the PDN GW serving the user terminal to the entity responsible for mobility management in the non-3GPP system, and may also send the user's key information and used for PDN GW information configured by the protocol (including protocol configuration options).
  • Step 4 The user terminal obtains proxy address routing information by sending an AS (Agent Solicitation) IKK (Agent Advertisement) to the non-3GPP IP access gateway on the PPP connection, where the proxy address routing information is FA-CoA (Foreign Agent Care of Address).
  • AS Agent Solicitation
  • IKK Agent Advertisement
  • FA-CoA Form Agent Care of Address
  • Step 5a The user terminal sends an RRQ (Mobile IP Registration Request) message to the non-3GPP IP access gateway according to the FA-CoA, where the RRQ message includes: a user identifier MN-NAI.
  • RRQ Mobile IP Registration Request
  • Step 5b After receiving the RRQ message, the non-3GPP IP access gateway sends an authentication request message to the HSS/AAA server, and carries the user identifier MN-NAI and the non-3GPP IP access gateway in the sent authentication request message.
  • the address information to determine if you have the external proxy function for the user terminal.
  • Step 6 After the authentication is passed, the non-3GPP IP access gateway sends the RRQ message to the PDN.
  • Step 7 After receiving the RRQ message, the PDN GW interacts with the HSS/AAA server to access the RRQ.
  • the message is authenticated 4 authorized.
  • Step 8a to Step 8b After the authentication is passed, the PDN GW allocates an IP address to the user terminal, and responds by an RRP (Registration Response) message, and returns the IP address to the non-3GPP IP access gateway.
  • An MIPv4 tunnel is established between the non-3GPP IP access gateway and the PDN GW.
  • the non-3GPP IP access gateway returns the IP address to the user terminal through the RRP message.
  • the non-3GPP IP access gateway establishes a PPP connection with the user terminal.
  • Step 9 The user terminal sends uplink data based on the PPP connection and the MIPv4 tunnel, and receives data sent by the non-3GPP system.
  • the invention provides a system switching method, a communication system and a policy charging rule function entity, which can ensure the consistency of the QoS of the user terminal service data before and after the system switching, thereby improving the user experience and improving the user satisfaction.
  • An embodiment of the present invention provides a method for system switching, where the method includes:
  • the gateway for policy control in the second system sends a request for obtaining the service policy information required by the second system to control the current service of the user terminal to the policy charging rule function entity; the request carries the identifier of the user terminal, Service bearer identity, first system network type, and second system network type;
  • the policy charging rule function entity finds service policy information used by the first system to control the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type;
  • the business policy information used is converted to the second system network class
  • the second system corresponding to the type controls the service policy information required for the current service of the user terminal; and returns the service policy information required by the second system to the gateway for policy control in the second system ;
  • the gateway for policy control in the second system controls the current service that the user terminal interacts with the second system according to the service policy information required by the second system.
  • the embodiment of the invention further provides a communication system, the communication system comprising a first system and a second system:
  • the second system includes: a gateway for policy control;
  • the communication system further includes: a policy charging rule function entity;
  • the gateway for policy control in the second system is configured to send, to the policy charging rule function entity, a request for acquiring the service policy information required by the second system to control the current service of the user terminal;
  • the policy charging rule function entity is configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal;
  • the service policy information used by the first system is converted into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal; and the service policy information required by the second system is Returning to the gateway for policy control in the second system;
  • the gateway for policy control in the second system is further configured to control, according to the service policy information required by the second system, the current service that the user terminal interacts with the second system.
  • the embodiment of the present invention further provides a policy charging rule function entity, where the policy charging rule function entity includes:
  • An information processing unit configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal; Translating the service policy information into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal;
  • the information transmission unit is configured to return the service policy information required by the second system to the gateway for policy control in the second system.
  • the policy charging rule function entity finds that the first system controls the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type.
  • the service policy information is: converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal;
  • the service policy information required by the second system is returned to the gateway for policy control in the second system; the gateway for policy control in the second system, according to the service policy information required by the second system, to the user
  • the current service of the terminal interacting with the second system is controlled. Therefore, with the embodiment of the present invention, the consistency of the QoS of the service data of the user terminal before and after the system switching can be ensured, thereby improving the user experience and improving the user satisfaction.
  • FIG. 1 is a system architecture diagram of a Non-3GPP-compatible system in an EPS system provided by the prior art
  • FIG. 2 is a flowchart of switching from a 3GPP system to a non-3GPP system provided by the prior art
  • FIG. 3 is a system according to an embodiment of the present invention; Principle flow chart of the switching method
  • FIG. 4 is a flowchart of a handover of a 3GPP system to a non-3GPP system according to an embodiment of the present invention. detailed description
  • the QoS policy information of the services before and after the system handover does not match, it will affect the quality of service standards of the services being transmitted. For the same service, the corresponding service QoS policy information is inconsistent in different systems. If the QoS policy information of the service before and after the system handover is not matched, the service quality of the service being transmitted will be affected, and the user will be reduced. Experience.
  • an embodiment of the present invention provides a system switching method, in which a gateway for policy control in a second system can learn that a user terminal switches from a first system to a second system, and the method
  • the principle flow is shown in Figure 3, including: Step 101: The gateway for policy control in the second system sends a request for acquiring the service policy information required by the second system to control the current service of the user terminal to the policy charging rule function entity; the request carries the user The identity of the terminal, the service bearer identifier, the first system network type, and the second system network type.
  • the gateway for policy control in the second system may, after receiving the request for establishing an IP connection, send, to the policy charging rule function entity, the current service of the second system to the user terminal. And performing a request for controlling the required service policy information; the gateway for policy control in the second system may also send the second system pair to the policy charging rule function entity after successfully establishing an IP connection with the user terminal.
  • the current service of the user terminal performs a request for the service policy information required for control.
  • Step 102 The policy charging rule function entity finds a service policy used by the first system corresponding to the first system network type to control the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type. And converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type to control the current service of the user terminal.
  • Step 103 The policy charging rule function entity returns the service policy information required by the second system to the gateway used for policy control in the second system.
  • Step 104 The gateway for policy control in the second system controls the current service that the user terminal interacts with the second system according to the service policy information required by the second system.
  • the gateway for policy control in the second system notifies the entity responsible for the mobility management function of the second system to update the second service system according to the obtained service policy information required by the second system to control the current service of the user terminal.
  • Air interface link level service policy information managed in the system The air interface link of the current service that the user terminal interacts with the second system is controlled by using the service policy information of the air interface link level.
  • the foregoing service policy information includes: business service quality policy information.
  • the foregoing embodiment of the present invention may further include: a gateway entity for mobility management and bearer management in the first system, such as MME (Mobility Manage) Entity, mobility management entity/SGSN (Serving GPRS Support Node;), receiving an indication that the carrying user terminal decides to switch from the first system to the second system (the indication is that the user terminal is Before the system switching process is started, according to the non-real-time service type that the ongoing service belongs to, the indication includes the serial number information of the downlink data that the user terminal has successfully received, and then the corresponding gateway is notified to stop the current according to the indication.
  • the ongoing service data is delivered, and the received downlink service data is cached. After the user terminal switches to the second system, the cached service data is transferred to the second system.
  • the foregoing embodiment of the present invention may further include: after the handover process is completed, notifying the first system to release the resources allocated for the current service of the user terminal, which may be implemented in the following three manners: The first mode:
  • the access gateway of the second system learns that the user terminal requests the route update, and the reason for the route update is the different system handover, and sends the location update information to the HSS/AAA server according to the route update request, where the location update information includes the reason for the different system handover. .
  • the HSS/AAA server sends a message to cancel the location to the gateway entity for mobility management and bearer management in the first system, such as the MME/SGSN, according to the different system handover reason.
  • the gateway entity for mobility management and bearer management in the first system such as the MME/SGSN, after receiving the cancel location message sent by the HSS/AAA server, determines that the first system needs to be released according to the cancel location message.
  • the service resource allocated by the user terminal notifies the corresponding gateway in the first system, and releases the service resource allocated for the current service of the user terminal.
  • the gateway entity for mobility management and bearer management in the first system learns that the user terminal requests to detach, and the reason for detaching is a different system handover; determining, according to the detach request, that the first system needs to be released For the service resource allocated by the user terminal, the corresponding gateway in the first system is notified to release the service resource allocated for the current service of the user terminal.
  • the packet data network gateway (such as the PDN GW) in the first system learns that the user terminal completes the establishment process of the bearer channel and performs data forwarding normally through the second system access gateway and itself. After that, the gateway entity (such as MME/SGSN) for mobility management and bearer management in the first system is notified to delete the bearer resource.
  • the gateway entity such as MME/SGSN
  • the gateway entity for example, the MME/SGSN
  • the gateway entity for example, the MME/SGSN
  • the bearer management in the first system notifies the corresponding gateway in the first system to release the service allocated for the current service of the user terminal according to the notification of deleting the bearer resource. Resources.
  • the first system may be a 3GPP system
  • the second system may be a non-3GPP system
  • the gateway for policy control in the second system may be a PDN GW or a non-3GPP Access Gateway (such as a PDSN of CDMA2000, Wimax's ASN GW), or both, perform policy control.
  • Step 1 The user terminal passes the 3GPP system ( As the E-UTRAN/GERAN/UTRAN is connected to the network, the UE uses its specific GTP or PMIPv6 tunnel transmission mode (between the Serving GW and the PDN GW) in the 3GPP system during the IP connection with the 3GPP system.
  • GTP or PMIPv6 tunnel transmission mode between the Serving GW and the PDN GW
  • a PMIPv6 or GTP tunnel exists on the connection interface S5, and the S5 interface can support the IP protocol to transmit data.
  • step 2a the user terminal performs signal measurement and finds the trusted non-3GPP system, and decides to perform inter-system handover.
  • Step 2b Before starting the handover to the non-3GPP system, the UE determines whether the current service data belongs to the non-real time service type or the real-time service type, and determines whether the 3GPP system needs to cache the current service data.
  • the user terminal determines that the 3GPP system needs to buffer the current service data, and then the MME to the 3GPP system.
  • the /SGSN sends an indication to switch to the non-3GPP system, where the indication includes the sequence number information of the downlink data that the user terminal has successfully received, and then performs step 2c.
  • the user terminal determines that the 3GPP system does not need to cache the current service data. It is possible to skip step 2c and directly perform the inter-system handover process.
  • Step 2c After receiving the indication, the MME/SGSN of the 3GPP system instructs the PDN GW to suspend transmission of data and perform corresponding buffer processing.
  • the non-real-time service data is cached, so that after the user terminal establishes a bearer connection with the non-3GPP system, the service data buffered in the PDN GW is routed to the non-3GPP system to reduce data loss.
  • Step 3a to step 3b the UE initiates an access procedure to the non-3GPP system; the entity responsible for mobility management in the non-3GPP system, such as PCF in CDMA2000, ASN-GW entity in Wimax, sends a layer to the HSS/AAA server.
  • the access authentication request of 2 which carries the MN-NAI of the user terminal, and the IP address of the PDN GW serving the UE.
  • the HSS/AAA server performs layer 2 access authentication and authorization procedures for the user terminal.
  • the identity of the UE is authenticated in the non-3GPP procedure, and the subscription information of the UE is obtained.
  • the HSS/AAA server authorizes the user terminal to allow access to the non-3GPP system, and indicates to the entity responsible for mobility management in the non-3GPP system the PDN GW having the IP HA function, the address of the PDN GW, The user's key information and PDN GW information for protocol configuration (including protocol configuration options) are sent to the entity responsible for mobility management in the non-3GPP system.
  • the entity responsible for mobility management in the non-3GPP system can return the address of the PDN GW and the PDN GW information to the user terminal through the access gateway.
  • Step 4 The entity responsible for mobility management in the non-3GPP system (such as the PCF in CDMA2000) receives the above information, and notifies the access gateway (such as the AGW/PDSN in CDMA2000) and the UE corresponding to the MN-NAI. The establishment process of the PPP connection.
  • the access gateway such as the AGW/PDSN in CDMA2000
  • the ASN-GW Access Servive Network Gateway
  • the Wimax system is not only responsible for mobility management but also responsible for access functions. Then, the entity directly establishes a PPP connection with the user terminal after receiving the above information.
  • Step 5 After the PPP connection is successfully established, the access gateway of the non-3GPP system (CDMA2000) The AGW/PDSN or the ASM-GW of the Wimax performs the Mobile IPv4 FA function, and sends an AA (Agent Advertisement) message on the PPP connection, which carries the FA CoA address information, or the UE sends the Agent Solicitation on the PPP connection.
  • the message is sent to the access gateway of the non-3GPP system that performs the foreign agent (FA) function, requesting to obtain the FA CoA address information.
  • FA foreign agent
  • the user terminal sends an AS message on the PPP connection to the access gateway of the non-3GPP system (such as PCF in CDMA2000, ASN-GW entity in Wimax), according to the information returned by the access gateway of the non-3GPP system.
  • the access gateway of the non-3GPP system such as PCF in CDMA2000, ASN-GW entity in Wimax
  • the access gateway with the Mobile IP FA function in the non-3GPP system sends an AA message on the PPP connection, where the proxy address routing information is the FA CoA address information; the user terminal obtains the FA from the AA message. CoA address information.
  • Step 6 After acquiring the FA CoA address information, the user terminal initiates a Mobile IP registration process according to the FA CoA address information, that is, sends an MIPv4 RRQ message to the access gateway of the non-3GPP system with the Mobile IP FA function, where the MIPv4 The RRQ message contains the user identifier MN-NAI and the IP address (FA CoA address, HoA address) request information.
  • Step 7 After receiving the MIPv4 RRQ message sent by the UE, the access gateway of the non-3GPP system initiates an L3 (Layer 3, Layer 3) IP level authentication process to the HSS/AAA server, and sends the authentication process to the HSS/AAA server. Obtain IP-level subscription service QoS policy information. The details are as follows: The access gateway of the non-3GPP system sends an Access Request to the 3GPP HSS/AAA server.
  • L3 Layer 3, Layer 3
  • access request message which carries the user identifier MN-NAI, and the address information of the access gateway; determines whether the access gateway of the non-3GPP system is based on the Access Response returned by the 3GPP HSS/AAA server Has the function of an external proxy.
  • Step 8 after the access gateway of the non-3GPP system determines that it has the function of the external proxy, sends the MIPv4 RRQ message to the PDN GW with the IP HA function indicated in step 3b, which includes the UE identifier MN-NAI and the IP address. Request information.
  • Step 9 After receiving the MIPv4 RRQ message, the PDN GW and the 3GPP HSS/AAA service The device interacts to authenticate the MIPv4 RRQ message.
  • Step 10 After the authentication is passed, the PDN GW allocates an IP address to the UE corresponding to the MN-NAI according to the UE identifier MN-NAI and the IP address request information carried in the MIPv4 RRQ message, and responds by using the MIPv4 RRP message, and the IP address is obtained. Returned to the access gateway of the non-3GPP system.
  • the IP address is an IP address assigned to the UE by the original 3GPP system, and corresponding to the home Mobile IP HoA address, the IP address of the UE remains unchanged, and the service continuity can be maintained.
  • the IP address originally allocated to the UE can be determined according to the user identifier MN-NAI.
  • the MIPv4 tunnel between the access gateway of the non-3GPP system and the PDN GW is established.
  • the access gateway of the non-3GPP needs to obtain the service QoS policy information from the PCRF entity and update the QoS policy information of the air interface link level service managed by the PCF/ASN-GW entity.
  • the QoS policy information of the IP-level service is consistent with the QoS policy information of the air interface link-level service. Since the PCRF entity manages the service QoS policy information suitable for different access type systems, the corresponding service QoS policy information can be selected according to the access type.
  • the access gateway of the non-3 GPP sends a Register Accepted message to the UE, which carries a MIP RRP message indicating that the UE attach is complete. At this time, the user plane IP connection between the UE and the PDN GW is established successfully. Specifically as described in steps 11 and 12:
  • Step 11 After receiving the MIPv4 RRP message fed back by the PDN GW, the access gateway of the non-3GPP system requests the PCRF entity to obtain the IP-level service QoS policy information of the UE by using the Fetch QoS information signalling message.
  • the message carries information such as the MN-NAI of the user terminal, the service bearer identifier, the network type of the non-3GPP system requesting access, and the network type of the original 3GPP system;
  • the PCRF entity determines, according to the network type of the non-3GPP system carried in the Fetch QoS information signalling message, that the system currently serving the user terminal is a non-3GPP system. Then, according to the MN-NAI of the user terminal, the service bearer identifier, and the network type of the original 3GPP system, the service QoS policy information used by the original 3GPP system to control the current service of the user terminal is found, and Converting the service QoS policy information used by the original 3GPP system to control the current service of the user terminal to the service QoS policy information required by the non-3GPP system to control the current service of the user terminal, and then the service QoS policy The information is returned to the access gateway of the non-3GPP system for policy control;
  • the non-3GPP system uses the access control gateway for policy control to save the obtained service QoS policy information, and updates the air interface link level service QoS policy managed by the entity responsible for mobility management (such as the PCF entity in CDMA2000) in the non-3GPP system.
  • the information is such that the IP-level service QoS policy information and the air interface link-level service QoS policy information are consistent.
  • the Fetch QoS information signalling message is used to request the PCRF entity to obtain the IP-level service QoS policy information of the current service of the UE, where the message carries the MN-NAI of the user terminal, and the service Information such as the bearer identifier, the network type of the non-3GPP system requesting access, and the network type of the original 3GPP system;
  • the PCRF entity determines, according to the network type of the non-3GPP system carried in the Fetch QoS information signalling message, that the system currently serving the user terminal is a non-3GPP system. Then, according to the MN-NAI of the user terminal, the service bearer identifier, and the network type of the original 3GPP system, the service QoS policy information used by the original 3GPP system to control the current service of the user terminal is found, and the original 3GPP system is used for the user.
  • the service QoS policy information used by the current service control of the terminal is converted into the service QoS policy information required by the non-3GPP system to control the current service of the user terminal, and then the service QoS policy information is returned to the PDN GW.
  • the PDN GW saves the obtained service QoS policy information.
  • the 3GPP system defines Conversational, Streaming, Interactive, and Background QoS classes for voice communications, streaming downloads, Internet access, and background downloads or emails. Download and more.
  • 14 QoS parameters are used in 3GPP UTRAN/GERAN, including Traffic class, MBR (Maximum Bit Rate), GBR (Proof Guaranteed Bit Rate), Transfer Delay (Transmission Delay), ARP (Allocation) And Retention Priority,
  • Traffic class MBR (Maximum Bit Rate), GBR (Proof Guaranteed Bit Rate), Transfer Delay (Transmission Delay), ARP (Allocation) And Retention Priority
  • MBR Maximum Bit Rate
  • GBR Guaranteed Bit Rate
  • Transfer Delay Transmission Delay
  • ARP Allocation
  • Retention Priority Each priority QoS class, THP (Traffic Handling Priority), SDU Error Ratio and Residual bit error ratio, signaling indication, etc.
  • THP Traffic Handling Priority
  • Each of the above four QoS classes of service in the 3GPP EPS can be represented by four QoS parameters.
  • the four QoS parameters include QCI (QoS Class Identifier), ARP, MBR, and GBR.
  • Non-3GPP's WiMAX access system defines UGS (Unsolicited Grant Service), ErtPS (eRT-VR Data Delivery Service, enhanced real-time polling service), rtPS (RT-VR Data Delivery Service, real-time polling) 5) QoS class of service, NRTPS (nRT-VR Data Delivery Service) and BE (Best Effort), for E1 transmission, VoIP (voice over IP, IP-based Voice transmission), live video, Internet access, etc.
  • the five QoS service levels are represented by eight QoS parameters, including Max sustained traffic rate, Traffic Priority, Request/transmission policy, Maximum Latency. ), Maximum Traffic Burst, Media Flow Type, Minimum Reserved Traffic Rate, Service Class Name.
  • Non-3GPP's CDMA2000 system defines Conversational, Streaming, Interactive, and Background QoS classes, represented by seven QoS parameters.
  • the seven QoS parameters include bandwidth, delay, jitter, Packet Loss, Priority, Traffic class, and IP QoS Class.
  • the division of the QoS service level in CDMA2000 is basically the same as the division of the QoS service level in 3GPP, and is divided into a session level, a flow level, an interaction level, and a background level.
  • the service types supported by the session level are: telephone, multimedia conference, and signaling; the service types supported by the interaction level are: real-time interactive services; the service types supported by the flow level are: multimedia stream and broadcast video; For: high-throughput data services, low-latency data services, low-priority data services, and standard data services.
  • the ftp download service is carried by the Wimax system.
  • the PCRF entity needs to generate the QoS service level in the Wimax system according to the above four QoS parameters according to the network type accessed by the user terminal.
  • Step 12 The non-3GPP access gateway with the FA function encapsulates the MIPv4 RRP message in the Register Accepted message and forwards it to the user terminal.
  • the PPP connection between the user terminal and the access gateway of the non-3GPP system is established.
  • the default bearer channel of the user terminal is established, the bearer channel is connected by the PPP between the user terminal and the access gateway of the non-3 GPP system, and the MIPv4 between the access gateway of the non-3 GPP system and the PDN GW.
  • the tunnel is composed.
  • Step 13 The user terminal sends the uplink service data by using the allocated IP address of the original 3GPP system through the PPP connection; the uplink service data reaches the access gateway of the non-3GPP system, and the access gateway of the non-3GPP system uses the The saved service QoS policy information is used to control the uplink service data, and the controlled uplink service data is sent to the PDN GW through the newly established MIPv4 tunnel; the PDN GW uses the service QoS policy information it holds, The uplink service data is controlled by the policy, and the controlled uplink service data is sent to non-3GPP system.
  • the PDN GW switches the delivery path to the newly established MIPv4 tunnel, and sends downlink service data from the non-3 GPP system, which may also include the service data cached in the PDN GW, and utilizes the saved service QoS policy information,
  • the downlink service data is controlled by the policy, and the controlled downlink service data is sent to the access gateway of the non-3GPP system through the newly established MIPv4 tunnel; the access gateway of the non-3GPP system utilizes the saved service QoS policy.
  • the information is used to control the downlink service data, and the controlled downlink service data is sent to the user terminal through the newly established PPP connection.
  • Method 1 The UE actively sends a Route Update message to the entity responsible for mobility management in the non-3GPP system to initiate a route update process. , triggering the PCF/ASN-GW entity to initiate a Location Update process to the HSS/AAA server.
  • the HSS/AAA server sends the original 3GPP MME/SGSN entity according to the information it saves from the original information.
  • a Cancel Location indication is sent indicating that it triggers the deletion of bearer resources allocated for the UE in the 3GPP system.
  • the HSS/AAA server then informs the UE that the routing update is complete through the non-3GPP system. Specifically, the following steps are included:
  • Step 14 After receiving the attach complete message, the user terminal sends a Route Update message to the non-3GPP system responsible for mobility management (such as PCF of CDMA2000 and ASN GW of Wimax), where: the user terminal is in the non-3GPP system.
  • the non-3GPP system responsible for mobility management such as PCF of CDMA2000 and ASN GW of Wimax
  • the user terminal is in the non-3GPP system.
  • the reason for the current location information, routing updates is different system switching.
  • Step 15 The entity responsible for mobility management in the non-3GPP system sends a Location Update message to the 3GPP HSS/AAA server according to the received routing update message, and the reason for the message including the location update is a different system handover, and the currently served network. Type and network element entity identification information.
  • Step 16 The 3GPP HSS/AAA server sends a Cancel Location indication to the MME/SGSN entity of the 3GPP system according to the information carried in the location update message, instructing the MME/SGSN to delete the corresponding context information and bearer resources.
  • Step 17 the entity MME/SGSN responsible for mobility management and bearer management in the 3GPP system
  • the eNodeB/RNC, the Serving GW, and the PDN GW of the 3GPP system initiate a process of deleting a bearer resource by using a Delete Bearer Request message, and the eNodeB/RNC, the Serving GW, and the PDN GW delete the respective bearer resources, and feedback Delete.
  • the Bearer Response message is sent to the MME/SGSN.
  • Step 18 After receiving the Delete Bearer Response message, the MME/SGSN sends the message to the 3GPP.
  • the HSS/AAA server feeds back an ACK confirmation message.
  • Step 19 The HSS/AAA server sends a Location Update ACK message to the non-3GPP system responsible for mobility management, indicating that the location update is successful, and the HSS/AAA server saves the user terminal in the non- Location information in the 3GPP system.
  • Step 20 The non-3GPP system responsible for mobility management sends a route to the user terminal.
  • Update Ack information indicating that its routing update was successful.
  • Method 2 After the handover is completed, if the UE supports the dual radio capability, the UE actively sends a Detach Request message to the MME/SGSN entity of the original 3GPP system, and the reason for the de-attachment is a different system handover, indicating the MME/SGSN entity. Initiate the process of deleting a bearer resource. Specifically include:
  • the user terminal After receiving the attach complete message, the user terminal sends a Detach Request message to the MME/SGSN entity of the 3GPP system, which includes the reason for the user terminal to detach, and the reason is different system handover.
  • the MME/SGSN entity decides to delete the bearer resource allocated for the UE in the 3GPP system according to the reason of the detachment in the Detach Request message, and initiates deletion to the eNodeB/RNC, Serving GW, and PDN GW of the 3GPP system by using the Delete Bearer Request message.
  • the process of carrying the resources; the eNodeB/RNC, the Serving GW and the PDN GW delete the respective bearer resources, and feed back the Delete Bearer Response message to the MME/SGSN entity.
  • the MME/SGSN entity After receiving the Delete Bearer Response message of the eNodeB/RNC, the Serving GW, and the PDN GW, the MME/SGSN entity determines that the bearer resource allocated for the UE in the 3GPP system has been deleted, and sends a Detach Accept message to the user terminal. The UE is notified that the bearer resources in the 3GPP system have been successfully deleted and successfully detached from the 3GPP system.
  • Method 3 The PDN GW notifies the 3GPP system to delete the corresponding context information and bearer resources. Specifically include:
  • the PDN GW After the UE establishes a bearer between the non-3GPP access gateway and the PDN GW and performs a normal uplink and downlink data forwarding process, the PDN GW notifies the MME/SGSN entity to delete the bearer resource.
  • the MME/SGSN entity initiates a process of deleting the bearer resource to the eNodeB/RNC, the Serving GW, and the PDN GW of the 3GPP system by using the Delete Bearer Request message; the eNodeB/RNC, the Serving GW, and the PDN GW delete the respective bearer resources, and feed back the Delete Bearer.
  • the Response message is sent to the MME/SGSN entity.
  • the MME/SGSN entity After receiving the Delete Bearer Response message, the MME/SGSN entity determines that the bearer resource allocated by the 3GPP system for the UE has been successfully deleted, and feeds back to the PDN GW that the bearer resource in the 3GPP system has been successfully deleted.
  • the access gateway or the PDN GW of the non-3GPP system may obtain the service QoS policy information from the policy charging rule function entity after the system switching is completed, and the obtaining method is the same as the method described in step 11, where It is no longer detailed. It is also within the scope of the present invention to use the method provided by the embodiments of the present invention in the transmission protocol.
  • the embodiment of the present invention further provides a communication system, including a first system and a second system, where the second system includes: a gateway for policy control, which can learn that the user terminal switches from the first system to the first
  • the communication system further includes: a policy charging rule function entity;
  • the gateway for policy control in the second system is configured to send, to the policy charging rule function entity, a request for acquiring the service policy information required by the second system to control the current service of the user terminal; Carrying the identifier of the user terminal, the service bearer identifier, the first system network type, and the second system network type;
  • the policy charging rule function entity is configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal;
  • the business policy information used by the first system is converted into the second system
  • the second system corresponding to the network type controls the service policy information required for the current service of the user terminal; and returns the service policy information required by the second system to the second system for policy control.
  • the gateway for policy control in the second system is further configured to control, according to the service policy information required by the second system, the current service that the user terminal interacts with the second system.
  • an embodiment of the present invention further provides a policy charging rule function entity, including: an information processing unit and an information transmission unit.
  • An information processing unit configured to find, according to the identifier of the user terminal, the service bearer identifier, and the first system network type, service policy information used by the first system to control the current service of the user terminal;
  • the service policy information is converted into service policy information required by the second system corresponding to the second system network type to control the current service of the user terminal.
  • an information transmission unit configured to return the service policy information required by the second system to the gateway for policy control in the second system.
  • the policy charging rule function entity finds that the first system controls the current service of the user terminal according to the identifier of the user terminal, the service bearer identifier, and the first system network type.
  • the service policy information is: converting the service policy information used by the first system into the service policy information required by the second system corresponding to the second system network type for controlling the current service of the user terminal;
  • the service policy information required by the second system is returned to the gateway for policy control in the second system; the gateway for policy control in the second system, according to the service policy information required by the second system, to the user
  • the current service of the terminal interacting with the second system is controlled.
  • the embodiment of the present invention the consistency of the QoS of the service data of the user terminal before and after the system switching can be ensured, thereby improving the user experience and improving the user satisfaction.
  • the present invention will be described in detail with reference to the preferred embodiments, and those skilled in the art should understand that the technical solutions in the embodiments of the present invention may be modified or substituted without departing from the technical solutions of the embodiments of the present invention. Spirit and scope.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un transfert de système, un système de communication et une entité PCRF (Policy Charging Rule Function). L'entité PCRF trouve les informations de la politique de service qui sont utilisées par le premier système pour contrôler le service actuel de l'UE à partir de l'identifiant de l'UE, l'identifiant du support de service et le type de réseau du premier système ; l'entité PCRF convertit les informations de la politique de service en informations de la politique de service qui sont requises par le second système qui correspond au type de réseau du second système pour contrôler le service actuel de l'UE ; l'entité PCRF renvoie les informations de la politique de service requises par le second système à la passerelle de contrôle de la politique dans le second système ; la passerelle de contrôle de la politique dans le second système contrôle le service actuel en interaction entre l'UE et le second système à partir des informations de la politique de service requises par le second système. La présente invention permet de garantir que la qualité de service des données de service de l'UE avant le transfert est conforme à la qualité de service des données de service de l'UE après le transfert, par conséquent, la présente invention permet d'améliorer l'expérience des utilisateurs et d'augmenter la satisfaction des utilisateurs.
PCT/CN2008/001815 2007-10-30 2008-10-29 Procédé de transfert de système, système de communication et entité pcrf Ceased WO2009062392A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710176560.2 2007-10-30
CN2007101765602A CN101426243B (zh) 2007-10-30 2007-10-30 系统切换的方法、通信系统

Publications (1)

Publication Number Publication Date
WO2009062392A1 true WO2009062392A1 (fr) 2009-05-22

Family

ID=40616527

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/001815 Ceased WO2009062392A1 (fr) 2007-10-30 2008-10-29 Procédé de transfert de système, système de communication et entité pcrf

Country Status (2)

Country Link
CN (1) CN101426243B (fr)
WO (1) WO2009062392A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017156706A1 (fr) * 2016-03-15 2017-09-21 华为技术有限公司 Procédé et dispositif pour traiter un paquet de données

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931929B (zh) * 2009-06-19 2015-07-22 中兴通讯股份有限公司 计费方法及计费系统
CN102215469B (zh) * 2010-04-09 2015-01-28 中兴通讯股份有限公司 一种基于网络负荷的策略计费控制方法和系统
CN102986271B (zh) * 2010-06-28 2015-08-19 华为技术有限公司 目标侧承载的承载标识的获取方法、承载管理网元和分组数据网关
EP3585009B1 (fr) * 2017-03-30 2021-03-03 Huawei Technologies Co., Ltd. Procédé de transmission de données et dispositif de communication
CN109673003B (zh) 2017-10-17 2021-10-26 华为技术有限公司 一种切换的方法、移动性管理网元和通信系统
CN109996303B (zh) * 2017-12-29 2021-06-01 华为技术有限公司 一种系统切换的方法及通信实体
CN110505662B (zh) 2018-05-16 2021-05-18 华为技术有限公司 一种策略控制方法、装置及系统
CN113709822A (zh) * 2020-05-22 2021-11-26 凌华科技股份有限公司 以移动通信网络实现工业自动化的装置及其运作方法
CN113556693B (zh) * 2021-03-12 2022-09-16 中国电信股份有限公司 物联网策略控制方法、数据网网关、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889499A (zh) * 2006-07-31 2007-01-03 华为技术有限公司 实现在不同网络之间协商策略信息的方法和系统
US20070211694A1 (en) * 2006-03-13 2007-09-13 Nokia Corporation Method for the transfer of information during handovers in a communication system
CN101060692A (zh) * 2006-04-18 2007-10-24 华为技术有限公司 一种无线演进网络中的切换方法及系统
CN101060703A (zh) * 2006-04-21 2007-10-24 华为技术有限公司 用户设备切换时的策略和计费控制方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070211694A1 (en) * 2006-03-13 2007-09-13 Nokia Corporation Method for the transfer of information during handovers in a communication system
CN101060692A (zh) * 2006-04-18 2007-10-24 华为技术有限公司 一种无线演进网络中的切换方法及系统
CN101060703A (zh) * 2006-04-21 2007-10-24 华为技术有限公司 用户设备切换时的策略和计费控制方法
CN1889499A (zh) * 2006-07-31 2007-01-03 华为技术有限公司 实现在不同网络之间协商策略信息的方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Services and System Aspects; Architecture Enhancements for non-3GPP accesses", 3GPP TS23.402 V1.3.0 3RD GENERATION PARTNERSHIP PROJECT, 30 September 2007 (2007-09-30), pages 68 - 69 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017156706A1 (fr) * 2016-03-15 2017-09-21 华为技术有限公司 Procédé et dispositif pour traiter un paquet de données
US10674421B2 (en) 2016-03-15 2020-06-02 Huawei Technologies Co., Ltd. Data packet processing method and device

Also Published As

Publication number Publication date
CN101426243B (zh) 2010-11-03
CN101426243A (zh) 2009-05-06

Similar Documents

Publication Publication Date Title
US10841858B2 (en) Data processing method and system
CN101431780B (zh) 一种实现网络优化切换的方法、设备及系统
CN101473679B (zh) 在系统间切换的情况下用于为终端传送pdp上下文信息的设备和方法
CN101330753B (zh) 一种资源创建方法、资源删除方法及网络设备
CN101426243B (zh) 系统切换的方法、通信系统
US8537781B2 (en) Low latency handover between wireless communication networks using different radio access technologies
CN102047722B (zh) 使用资源准备的从非3gpp接入到3gpp接入的rat间切换
US20110235605A1 (en) Radio resource allocation method and device of henb in evolved packet system
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
US20140086210A1 (en) Data processing method and device
WO2011000318A1 (fr) Procédé et dispositif permettant de commander un transfert
WO2014121760A1 (fr) Procédé et dispositif pour sélectionner un appareil de réseau durant une commutation
WO2009002841A1 (fr) Procédé et appareil pour une gestion de ressource dans une opération de transfert
CN105813146B (zh) 业务流传输路径优化方法、装置及mme
CN101594285A (zh) 一种使用聚合最大比特率的方法、装置及系统
CN101483920B (zh) 资源接纳控制方法、网络装置及网络系统
WO2011143997A1 (fr) Procédé et dispositif de routage
CN101938728B (zh) 一种实现紧急会话切换的方法及系统
CN104041122B (zh) 一种数据域业务处理方法、装置及系统
WO2010022611A1 (fr) Procédé, système et centre de commutation mobile destinés à un commutateur à continuité d’appel vocal
CN101483899B (zh) 一种切换过程中发起源网络承载释放的方法、系统及网络锚点
WO2009092260A1 (fr) Procédé, entité fonctionnelle d'interconnexion et équipement terminal pour réaliser la continuité d'un appel vocal
WO2011023125A1 (fr) Procédé, dispositif et système pour libération de connexion
WO2009149656A1 (fr) Procédé, dispositif et système permettant la mise en œuvre d'un transfert de service
WO2011144000A1 (fr) Procédé et appareil de sélection de route

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08848710

Country of ref document: EP

Kind code of ref document: A1