WO2008128459A1 - Method for establishing wireless network default bearers and system thereof - Google Patents

Abstract

A method for establishing wireless network default bearers and a system thereof in wireless communication field are disclosed, which enable the processing procedure when establishing default bearers to be quickened, and provide users with personalized services flexibility. In the present invention, during the attachment process of the UE, one rule is selected from the pre-configured default PCC rules, PCEF establishes default bearers for the UE according to the selected default PCC rule. The network side classifies the default bearers in advance, and each class of default bearers correspond to one default PCC rule. The network side may classify the default bearers in advance according to the following manners such as charging criteria, commercial model, service model, subscribed user level and the like. If the selected default PCC rule pre-configuration is in the PCEF or has been sent to the PCEF, the network entity that selects the default PCC rule needn't send the rule content to the PCEF, and it only need send the rule identifier.

Description

 Wireless network default bearer establishment method and system thereof

 The present invention relates to the field of wireless communications, and in particular, to a default bearer setup technique. Background technique

 The Universal Mobile Telecommunications System (UMTS) is a Wideband Code Division Multiple Access (3D Generation Partnership Project, referred to as "3GPP"). "WCDMA") third-generation mobile communication system for air interface technology. In the UMTS network, the user equipment (User Equipment, referred to as "UE") has a corresponding bearer for the UE. The bearer setup process is initiated by the UE.

 However, with the gradual development of communication, people's requirements for mobile communication are getting higher and higher. Therefore, 3GPP proposes a concept of an evolved network serving future communication needs, System Architecture Evolution (SAE). It belongs to the next generation wireless core network evolution project proposed by 3GPP.

The SAEs specified in TR23.882-V180 mainly include: Mobility Management Entity ("MME"), User Plane Entity ("UPE"), 3GPP Anchor (3GPP Anchor) and SAE Anchor. (SAE anchor) Four logical function modules, as shown in Figure 16. The MME is a mobility management module, and is responsible for the mobility management of the control plane, which corresponds to the control plane part of the Serving GPRS Support Node (SGSN) in the current UMTS system; the UPE is the user plane. The entity is responsible for triggering the MME to initiate paging when the downlink data arrives in the idle state, managing the saved IP bearer parameters and the intra-network routing information, etc., which corresponds to the data plane part of the current UMSN system SGSN; the 3GPP anchor point is different in the 3GPP system User plane anchor point between access systems; SAE anchor point is a user plane anchor point between the 3GPP access system and the non-3GPP system in the SAE. The SAE anchor and the 3GPP anchor are collectively referred to as an Inter AS Anchor (IASA). The non-roaming architecture of the evolved network in TR23.882 is shown in Figure 16. The roaming architecture of the evolved network in TR23.882 is shown in Figures 17 and 18, respectively. Figure 17 is the roaming framework of the Home Routed from the home network. Schematic diagram, FIG. 18 is a schematic diagram of a roaming architecture of a SGi interface (Local Breakout) directly from a roaming network. In the SAE network, in order to increase the support for the voice service and improve the connection speed of the mobile terminal, when the UE attaches to the network (that is, the UE registers to the network to obtain the service provided by the network), a bearer connection is established with the network. In order to realize the "always on" function of the user, so that the user can initiate the service quickly, the bearer connection is called the default bearer. The process when the UE attaches to the network is as shown in FIG. 1, which includes the process of establishing a default bearer.

 In step 101, the UE sends an attach request to the MME, where the message carries the identifier of the UE (the temporary use temporary identifier: Packet Temporary Mobile Subscriber Identity (P-TMSI)), without P-TMSI In the case of using the permanent identity: International Mobile Subscriber Identity ("IMSI"), the core network identifies the UE by using the identifier and completes the authentication and UE attach process, and the message also carries the access. Point Name (Access Point Name, referred to as "ΑΡΝ").

 Next, in step 102, ΜΜΕ determine whether there is an available authentication vector of the UE, and if not, trigger a two-way authentication process between the UE and the network (shown as a dotted line, indicating that the process is optional).

 Next, in step 103 to step 106, a location update is initiated to the Home Subscriber Server (HSS), the current MME entity is registered with the HSS as the serving MME of the UE, and the user is requested to subscribe to the data. The HSS inserts user subscription data into the MME. The MME successfully returns the user subscription data to the HSS. The HSS returns a location update confirmation message to the MME.

 Next, in step 107 to step 110, the MME sends a create bearer request message to the UPE, carrying the APN and the user plane key (UP key), and the like. The UPE selects the IASA based on the APN and sends a Route Update/Bearer Setup Request message to the selected IASA. The IASA performs signaling interaction with the Policy and Charging Rules Function (PCRF) to determine the policy and charging control (PCC) rules used by the default bearer. The Policy and Charging Enforcement Function ("PCEF") in this process is located on the IASA. The IASA sends a route update response to the UPE, and the UPE sends a bearer response message to the MME.

Next, in steps 111 to 113, the MME transmits a radio bearer setup request message to the eNB (evolved base station node). A radio resource control (Radio Resource Control, referred to as "RRC") signaling connection is established between the eNB and the UE. The eNB sends a radio bearer response message to the MME. Since the radio bearer is created when it is attached or when there is data transmission, it has not yet been determined, so it is indicated by a broken line. Next, in step 114, the MME sends a bearer acknowledgement message to the UPE. In steps 115 and 116, the MME sends an attach accept message to the UE. The UE sends an attach complete message to the MME.

 The following describes the PCC involved in the above process. PCC is a unified control and billing policy architecture, as shown in Figure 2. The architecture is applicable to a variety of different IP-CAN (IP-connected access networks). In this architecture, the Application Function ("AF") provides the required parameters to the PCRF. The function of the PCRF is to generate PCC rules based on these parameters and send them to the PCEF. The PCEF is used to execute the PCC rules. . The PCC rules can be classified into dynamic generation and pre-configuration. The dynamically generated PCC rules are dynamically generated by the PCRF and sent to the PCEF through the Gx interface and activated by the PCRF. The pre-configured PCC rules are directly pre-configured in the PCEF, which can be PCRF or Activated by PCEF according to operator policy. For different IP-CANs, the PCEF is located in its corresponding gateway (GW).

 For 3GPP access, the evolved network written in TS23.401-V030 is shown in Figures 19-21. 19 and 20 are non-roaming network architectures. In FIG. 20, there may be an S5 shown in FIG. 19 between a serving SAE gateway and a Packet Data Network ("PDN") SAE gateway. Figure 21 is a schematic diagram of an evolved network roaming architecture of the SGi interface from the home network. The public land mobile network (Public Land Mobile Network, referred to as "PLMN") and the PLMN of the roaming network are respectively bounded by the thick solid line. . In addition, the roaming architecture including PCC has not been determined, so the existence of the S9 interface between H-PCRF (Home PCRF) and V-PCRF (PCRF of the roaming network) has not yet been determined.

 For non-3GPP (non-3GPP) access, the evolved network written in TS23.402-V030 is shown in Figures 22 and 23. 22 is a non-roaming network architecture; FIG. 23 is a schematic diagram of an evolved network roaming architecture of the SGi interface from the home network.

 In Figures 19 ~ 23, the serving SAE gateway is equivalent to the UPE and 3GPP anchor in TR23.882, and the PDN SAE gateway is equivalent to the SAE anchor.

 If a UE is required to generate a PCC rule for establishing a default bearer for the UE, the network side needs to increase the processing time when the default bearer is established for the UE, thereby affecting the UE. The speed of launching a business. Moreover, because the type of service that the network runs is limited, if a default bearer with different PCC rules is established for each UE, unnecessary complexity will be added to the system. Summary of the invention

The main technical problem to be solved by the embodiments of the present invention is to provide a default bearer establishment of a wireless network. The method and its system make the process of establishing the default bearer faster.

 To solve the above technical problem, an embodiment of the present invention provides a wireless network default bearer establishment method, which includes the following steps:

 During the user equipment attachment process, one of the default PCC rules pre-configured by the network side is selected, and the policy and charging execution function establishes a corresponding default load for the user equipment according to the selected default PCC rule.

 The embodiment of the present invention further provides a wireless network default bearer establishment system, including: a storage module, configured to save each default PCC rule preconfigured on the network side;

 a selection module, configured to select a default PCC rule from each default PCC rule saved by the storage module during the user equipment attaching process;

 The establishing module is configured to establish a corresponding default bearer for the user equipment according to the default PCC rule selected by the selecting module.

 And a establishing module, configured to establish a corresponding default bearer for the UE according to a default PCC rule selected by the selecting module.

 In the embodiment of the present invention, one of the pre-configured default PCC rules is selected in the UE attach procedure, and the PCEF establishes a corresponding default bearer for the UE according to the selected default PCC rule. Since the default PCC rule is pre-configured, it is not necessary to generate a rule for each UE. When a default bearer is established for the UE, only one of the limited configured rules can be selected, thereby making processing. The workload is relatively small, the processing is relatively fast, and the setup delay of the default bearer is reduced. DRAWINGS

 1 is a flow chart of a UE attached to a SAE network in the prior art;

 2 is a schematic diagram of a PCC architecture in the prior art;

3 is a flowchart of a method for establishing a default bearer of a wireless network according to a first embodiment of the present invention. FIG. 4 is a flowchart of a method for establishing a default bearer for a wireless network according to a third embodiment of the present invention. FIG. 5 is a fifth embodiment of the present invention. FIG. 6 is a flowchart of a method for establishing a default bearer of a wireless network according to a sixth embodiment of the present invention. FIG. 7 is a flowchart of a method for establishing a default bearer for a wireless network according to a seventh embodiment of the present invention. 8 is a flowchart of a method for establishing a default bearer of a wireless network according to a ninth embodiment of the present invention. FIG. 9 is a flowchart of a method for establishing a default bearer for a wireless network according to a tenth embodiment of the present invention. 10 is a flowchart of a method for establishing a default bearer of a wireless network according to an eleventh embodiment of the present invention; FIG. 11 is a flowchart of a method for establishing a default bearer for a wireless network according to a fourteenth embodiment of the present invention;

Flowchart of V-PCEF interacting with H-PCRF through V-PCRF;

 12 is a flowchart of interaction between a V-serving SAE gateway and an H-PDN SAE gateway in a method for establishing a default bearer of a wireless network according to a fourteenth embodiment of the present invention;

 13 is a flowchart of a method for establishing a default bearer of a wireless network according to a twelfth embodiment of the present invention; FIG. 14 is a flowchart of a method for establishing a default bearer for a wireless network according to a thirteenth embodiment of the present invention; A schematic diagram of a structure of a wireless network default bearer setup system according to a sixteenth embodiment;

 16 is a schematic diagram of a non-roaming architecture of an evolved network in the prior art TR23.882;

 17 is a schematic diagram of a roaming architecture of an evolved network from the home network to the SGi interface in the prior art TR23.882;

 18 is a schematic diagram of a roaming architecture of an SGi interface from a roaming network of an evolved network in the prior art TR23.882;

 19 is a schematic diagram 1 of a non-roaming architecture of an evolved network in the prior TS23.401-V030; FIG. 20 is a second schematic diagram of a non-roaming architecture of an evolved network in the prior TS23.401-V030; Schematic diagram of the roaming architecture of the SGi interface from the home network of the evolved network in TS23.401-V030;

 22 is a schematic diagram of a non-roaming architecture of an evolved network in the TS23.402-V030 of the prior art; FIG. 23 is a schematic diagram of a roaming architecture of an evolved network from the home network to the SGi interface in the TS23.402-V030 of the prior art;

 24 is a flowchart of establishing a dedicated bearer by using a PCC rule mapping mechanism from a roaming network to an SGi interface in a roaming scenario according to the fourteenth embodiment of the present invention;

 25 is a flow chart of a method for establishing a default bearer of a wireless network according to a fifteenth embodiment of the present invention. detailed description

 In order to make the objects, technical solutions and advantages of the present invention more comprehensible, the embodiments of the present invention will be further described in detail with reference to the accompanying drawings.

In the embodiments of the present invention, the network side classifies the default bearers in advance and divides them into N types of default bearers (N > 1 ). Each type of default bearer corresponds to a pre-configured use in the default bearer setup process. The PCC rule is simply referred to as "default PCC rule" by the present invention. Except for the IP multimedia core network subsystem signaling, most of the services running in the network are not Guaranteed Bit Rate (GBR) services and operator-controlled services, and PCRF does not have much for these services. Controlling capabilities, therefore, pre-configured default PCC rules can be used without the need for PCC rules dynamically generated in the PCRF. That is to say, the default bearer of the UE is divided into N categories, and it can be considered that the different UEs are divided into N categories, and the UEs of different classes correspond to a pre-configured default PCC rule, and enjoy different types of services.

 If a default bearer with different PCC rules is established for each UE, that is, N is equal to the number of UEs, the system becomes more complicated. If all UEs use the same default bearer of the PCC rules, that is, N is equal to 1. It is not user friendly and lacks flexibility, because each user may customize different services as needed to pay different fees and enjoy different levels of service. Therefore, the preferred value of N is between 1 and the number of UEs, so as to provide corresponding personalized services for different levels of UEs while reducing flexibility, and effectively reduce the default PCC rules stored on the network side. Quantity. Moreover, the number of pre-configured default PCC rules is limited, which further speeds up the process of establishing a default bearer for the UE.

 There are several types of classification criteria for the default bearer of the UE. For example, it can be performed according to the carrier policy. The specific classification methods are as follows:

 (1) Pre-classify default bearers according to tariff standards, and high-rate users enjoy high-level services;

(2) Pre-classify the default bearers according to the business model or business model, for example, which packages the user has customized;

 (3) The default bearers are classified in advance according to the contracted user level. For example, the users are classified into ordinary users, gold users, and platinum users according to the accumulated amount of user consumption or the length of use.

 For the roaming UE, the pre-configured default PCC rule of the UE at the roaming location may be obtained according to the pre-configured default PCC rule corresponding to the default bearer class of the UE in the home location, thereby determining The UE is in the default bearer category of the roaming network; or the default PCC rule of the UE in the roaming area may be obtained according to the roaming agreement between the roaming network and the home network, thereby determining the default bearer category of the UE in the roaming network; Alternatively, the default PCC rule of the UE at the roaming location may also be obtained by the roaming network operator policy, thereby determining the default bearer category of the UE in the roaming network.

However, in the future development of standards, for 3GPP access, the PCEF function may also be moved down to the serving SAE gateway or even the access network side. For non-3GPP access, the PCEF function may also be located in the evolution. The packet data gateway (evolved Packet Data Gateway, e.g., "ePDG") is described as an example in which the PCEF function is located in the PDN SAE gateway.

 The first embodiment of the present invention relates to a method for establishing a default bearer of a wireless network. In this embodiment, a default PCC rule corresponding to a UE of a different type or its identification number is stored in the general database as the subscription data of the UE, for example, The HSS, the Subscription Profile Repository (SPR), or the Authentication Authorization and Accounting Server (AAA), etc., the network side selects a default PCC rule according to the subscription data of the UE. In this embodiment, the general database is used as the HSS, and the default PCC rules are pre-configured in the PCEF as an example. The specific process is shown in FIG. 3 .

 In step 301, the UE sends an attach request to the MME, where the message carries the identifier of the UE (the temporary identifier P-TMSI is used preferentially, and the permanent identifier IMSI is used without the P-TMSI), and the core network identifies the UE by using the identifier. The authentication and UE attachment process is completed.

 Next, proceeding to step 302, the MME determines whether it has an available authentication vector of the UE, and if not, triggers a two-way authentication process between the UE and the network (shown as a dotted line, indicating that the process is optional).

 Next, proceeding to step 303, the MME initiates a location update to the HSS, registers the current MME entity with the HSS as the serving MME of the UE, and requests the user to subscribe to the data.

 Next, proceeding to step 304, the HSS provides user subscription data to the MME. The identifier of the default PCC rule corresponding to the UE of the different types of UEs is stored in the HSS as the subscription data of the UE. Therefore, the HSS provides the MME with the identification number (ID) of the default PCC rule including the UE in the user subscription data. . That is, the MME can query the identification number of the default PCC rule of the UE. Since the piggyback is used in the present embodiment, steps 303 and 304 implement the location update and request user subscription data functions, which are equivalent to steps 103 to 106 in FIG.

 Then, proceeding to step 305, the MME sends a create bearer request message to the serving SAE gateway, where the message carries the queried identification number of the default PCC rule of the UE.

Then, proceeding to step 306, the serving SAE gateway sends a routing update/bearing request message to the PDN SAE gateway, where the message carries the queried identification number of the default PCC rule of the UE. The default PCC rules are pre-configured in the PCEF in the PDN SAE gateway. Therefore, the PCEF in the PDN SAE gateway can activate the corresponding PCC rule for the UE according to the identification number, and establish a serving SAE gateway and a PDN in this step. Wired bearer between SAE gateways. Since it is not necessary to send the rule content to the PCEF, it is only necessary to issue the identifier of the rule, thereby reducing the amount of communication between different network entities, thereby The system resources were approximated and the establishment process of the bearer was accelerated.

 Next, proceeding to step 307, the PDN SAE gateway sends a route update response to the serving SAE gateway and

7 loaded response.

 Next, proceeding to step 308, the serving SAE gateway sends a bearer response message to the MME.

 Next, proceeding to step 309, the MME sends a radio bearer setup request message to the eNB.

 Next, proceeding to step 310, a radio bearer is established between the eNB and the UE.

 Next, proceeding to step 311, the eNB sends a radio 7-load response message to the MME.

 Next, proceeding to step 312, the MME sends a bearer acknowledgement message to the serving SAE gateway.

 Next, proceeding to step 313, the MME sends an attach accept message to the UE.

 Then, proceeding to step 314, if the core network allocates a new P-TMSI to the UE, the UE

The MME sends an attach complete message.

 It is not difficult to find that, in this embodiment, since the default PCC rule is pre-configured, it is not necessary to generate a rule for each UE. When a default bearer is established for the UE, only a limited number of configurations are configured. One of the rules can be selected, so that the processing workload is relatively small, the processing process is relatively fast, and the establishment delay of the default bearer is reduced.

 The second embodiment of the present invention relates to a method for establishing a default bearer of a wireless network. The present embodiment is substantially the same as the first embodiment, except that in the first embodiment, each default PCC rule is pre-configured in the PCEF. In this embodiment, each default PCC rule is pre-configured in the HSS.

 Specifically, the PCEF in the PDN SAE gateway needs to save the default PCC rule that has been received. The HSS records the default PCC rule sent to the PCEF to determine whether the default PCC rule of the currently attached UE has been Sending to the PCEF, if yes, sending the identification number of the default PCC rule of the UE to the PCEF, the PCEF activating the corresponding PCC rule according to the identification number, and establishing a default bearer for the UE (with the first embodiment) The process is the same). If the default PCC rule of the UE has not been sent to the PCEF, the default PCC rule of the UE is sent to the PCEF, and the PCEF establishes a default bearer for the UE according to the received default PCC rule. Next, in step 304, the HSS provides the user subscription data with the default PCC rule of the UE instead of the default PCC rule identifier. In step 305 and step 306, the MME sends the service SAE gateway to the serving SAE gateway. The create bearer request message, and the route update/bearer request message sent by the serving SAE gateway to the PDN SAE gateway, need to include the default PCC rule of the UE, instead of the identification number of the default PCC rule.

Although in this embodiment, the default PCC rule is not pre-configured in the PCEF, due to PCEF The default PCC rule that has been received is saved. Therefore, if the default PCC rule of the currently attached UE has been sent to the PCEF, the rule content does not need to be sent to the PCEF repeatedly, which reduces the relationship between different network entities. The amount of traffic, which saves system resources.

 It is to be noted that, in the first and second embodiments, the general database is used as an example of the HSS. If the general database is an AAA server, the AAA server will use the default PCC rule corresponding to the UE or the default PCC rule. The information is sent to the PCEF. The two configurations of the default PCC rules in the PCEF and the AAA server are the same as those in the first and second embodiments, and are not described here. If the general-purpose database is an SPR, the SPR sends the default PCC rule corresponding to the UE or the identification number of the default PCC rule to the PCEF through the PCRF of the network side, and the default PCC rules are pre-configured in the PCEF and the AAA server. The two cases are the same as the first and second embodiments, and are not described here.

 The third embodiment of the present invention relates to a radio network default bearer establishment method. In this embodiment, each default PCC rule is pre-configured in the PCEF, and the PCRF of the network side determines the identification number of the default PCC rule, and the PCEF according to the The default PCC rule selected by the PCRF establishes a default bearer for the UE. The specific process is shown in Figure 4.

 In step 401, the UE sends an attach request to the MME, where the message carries the identifier of the UE (the temporary identifier P-TMSI is used preferentially, and the permanent identifier IMSI is used without the P-TMSI), and the core network identifies the UE by using the identifier. The authentication and UE attachment process is completed.

 Next, proceeding to step 402, the MME determines whether it has an available authentication vector of the UE, and if not, triggers a two-way authentication process between the UE and the network (shown as a dotted line, indicating that the process is optional).

 Next, proceeding to step 403 and step 404, the MME initiates a location update to the HSS, registers the current MME entity with the HSS as the serving MME of the UE, and requests the user to subscribe to the data. The HSS provides user subscription data to the MME.

 Next, proceeding to step 405, the MME sends a create bearer request message to the serving S AE gateway.

 Next, proceeding to step 406, the serving SAE gateway sends a route update/bearer request message to the PDN SAE gateway.

Then, proceeding to step 407, the PDN SAE gateway performs signaling interaction with the PCRF, and the PCRF selects the default PCC rule of the UE according to a certain policy, and returns the identifier of the selected default PCC rule to the PDN SAE gateway. Alternatively, the PDN SAE gateway queries the SPR for the identification number of the default PCC rule of the UE, and returns the identified identification number of the default PCC rule to the PDN SAE gateway. The default PCC rules are pre-configured in the PCEF in the PDN SAE gateway. Therefore, the PCEF in the PDN SAE gateway can activate the corresponding PCC rule for the UE according to the identification number, and establish a service SAE gateway and PDN in this step. Wired bearer between SAE gateways. It can be seen that the PCRF does not need to send the rule content to the PCEF, as long as the identity of the rule is sent, the traffic between different network entities is reduced, thereby saving system resources.

 It should be noted that the information of the interaction between the PCEF and the PCRF may include the following parameters: MME ID (MME identification number), service SAE gateway identification number, PDN SAE gateway identification number, UE identification number, location information, location information Charging information, subscription information, etc. These parameters may be used together with the subscriber's subscription information and the operator's policy to determine the UE's default PCC rules. If the PCRF can obtain the subscription information of the UE by using the UE, the PCRF does not need to obtain the subscription information of the UE by interacting with the SPR.

 Steps 408 to 415 are completely the same as steps 307 to 314, and are not described herein again. The fourth embodiment of the present invention relates to a method for establishing a default bearer of a wireless network. The present embodiment is substantially the same as the third embodiment. The difference is that, in the third embodiment, each default PCC rule is pre-configured in the PCEF. In this embodiment, each default PCC rule is pre-configured in the PCRF.

 Specifically, the PCRF records the default PCC rule sent to the PCEF, and determines whether the currently selected default PCC rule has been sent to the PCEF. If yes, the identifier of the selected default PCC rule is sent to The PCEF, the PCEF activates a corresponding PCC rule according to the identification number, and establishes a default bearer for the UE (same process as the third embodiment). If the selected default PCC rule has not been sent to the PCEF, the selected default PCC rule is sent to the PCEF, and the PCEF establishes a default bearer for the UE according to the received default PCC rule, in this case, In step 407, the PCRF returns the selected default PCC rule to the PDN SAE gateway instead of the selected PCC rule identification number. The PCEF in the PDN SAE Gateway needs to save the default PCC rules that have been received.

 It can be seen that if the currently selected default PCC rule has been sent to the PCEF before, the rule content is not repeatedly sent to the PCEF, which reduces the traffic between different network entities, thereby saving system resources.

It is to be noted that, in the third and fourth embodiments, if the parameter of the default PCC rule is the default parameter, the PCRF may also change the selected default PCC rule according to the operator policy and the subscription information of the UE. Part of the parameters, therefore, in step 407, the PCRF also needs to return to the PDN SAE gateway. Go back to the PCC parameters that need to be changed.

 A fifth embodiment of the present invention relates to a radio network default bearer establishment method. In this embodiment, the network side is based on a quality of service (QoS) parameter of the UE, such as a label Label, MBR, or AMBR. The default PCC rule is selected. The PCEF establishes a default bearer for the UE according to the selected default PCC rule. The network entity that selects the default PCC rule may be an HSS, SPR, MME, PCEF, or PCRF. In this embodiment, the default PCC rule is selected according to the label (the label is saved in the HSS as the subscription data), and the network entity that selects the default PCC rule is the PCEF as an example. Each default PCC rule is pre-configured in the PCEF. The process is shown in Figure 5.

 Steps 501 to 503 are completely the same as steps 301 to 303, and details are not described herein again. In step 504, the HSS provides the user subscription data to the MME, and the provided user subscription data includes the label signed by the UE.

 Next, in step 505, the MME sends a create bearer request message to the serving SAE gateway, where the message carries a Label.

 Next, in step 506, the serving SAE gateway sends a route update/bearer request message to the PDN SAE gateway, where the message carries a Label. The PCEF in the PDN SAE gateway selects the default PCC rule of the UE according to the Label, activates the corresponding PCC rule, and establishes a wired bearer between the serving SAE gateway and the PDN SAE gateway in this step. Since Label is a QoS parameter, selecting the default PCC rule according to Label can enable different types of UEs to enjoy different quality of service.

 Steps 507 to 514 are completely the same as steps 307 to 314, and details are not described herein again. The sixth embodiment of the present invention relates to a radio network default bearer establishment method. In this embodiment, the network side selects a default PCC rule according to a QoS parameter of the UE, such as a label Label, MBR, or AMBR, and the PCEF selects according to the selected The default PCC rule establishes a default bearer for the UE. The network entity that selects the default PCC rule may be an HSS, SPR, MME, PCEF or PCRF. In this embodiment, the default PCC rule is selected according to the Label (the Label is provided by the PCRF), and the network entity that selects the default PCC rule is the PCEF. The default PCC rules are pre-configured in the PCEF. Shown.

Steps 601 to 606 are completely the same as steps 401 to 406, and details are not described herein again. In step 607, the PDN SAE gateway performs signaling interaction with the PCRF. The PCRF determines the Label of the UE and returns it to the PDN SAE gateway. The PCEF in the PDN SAE gateway selects the identification number of the default PCC rule of the UE according to this, and activates the corresponding PCC rules, and in this step, establish PDN SAE Wired bearer between the gateway and the serving SAE gateway. Since Label is a QoS parameter, different UEs can enjoy different quality of service according to the default PCC rules selected by Label.

 Steps 608 to 615 are completely the same as steps 408 to 415, and are not described herein again. A seventh embodiment of the present invention relates to a method for establishing a default bearer of a radio network. In this embodiment, the UE sends the identifier of the desired default PCC rule to the network side in the process of attaching, and the network side according to the received identifier. The number selects the corresponding default PCC rule, and each default PCC rule is pre-configured in the PCEF. The specific process is shown in Figure 7.

 In step 701, the UE sends an attach request to the MME, where the message carries the identifier of the UE (the temporary identifier P-TMSI is used preferentially, and the permanent identifier IMSI is used without the P-TMSI), and the core network identifies the UE by using the identifier. And complete the authentication and UE attachment process. At the same time, the message will also carry the identification number of the default PCC rule expected by the UE.

 The steps 702 and 703 are the same as the steps 302 and 303, respectively, and are not described here. In step 704, the HSS provides user subscription data to the MME.

 Steps 705 to 714 are completely the same as steps 305 to 314, and are not described herein again. In this embodiment, the rule content is not required to be sent to the PCEF, and the identifier of the rule can be sent, thereby reducing the traffic between different network entities, thereby saving system resources.

 The eighth embodiment of the present invention relates to a method for establishing a default bearer of a wireless network. The present embodiment is substantially the same as the seventh embodiment. The difference is that, in the seventh embodiment, each default PCC rule is pre-configured in the PCEF. In this embodiment, each default PCC rule is pre-configured in the PCRF.

 Specifically, the MME sends the identifier of the default PCC rule that is expected by the UE to the PCEF by using the serving SAE gateway, and the PCEF determines whether there is a default PCC rule corresponding to the identifier in the PCEF, and if yes, according to The default PCC rule corresponding to the identifier is used to establish a default bearer for the UE. If not, the identifier is sent to the PCRF that holds the default PCC rule, and the default PCC rule corresponding to the identifier is requested. After receiving the request, the corresponding default PCC rule is sent to the PCEF. The PCEF in the PDN SAE Gateway needs to save the default PCC rules that have been received.

It can be seen that if the default PCC rule that the UE expects has been sent to the PCEF, the PCEF can directly establish a default bearer for the UE according to the received identification number of the default PCC rule, and does not need to repeat the PCRF. The PCEF sends the rule content, which reduces the amount of communication between different network entities, thereby saving system resources. The ninth embodiment of the present invention relates to a radio network default bearer establishment method. In this embodiment, the network side selects a default PCC rule according to the service type, APN, or charging information of the UE, and the PCEF is selected according to the selected The default PCC rule establishes a default bearer for the UE. The network entity that selects the default PCC rule may be an HSS, SPR, MME, PCEF, or PCRF. In this embodiment, the network entity that selects the default PCC rule is a PCEF as an example. The service category, APN, or charging information is stored in the network side HSS as the subscription data of the UE, and each default PCC rule is pre-configured in the PCEF. Inside, the specific process is shown in Figure 8.

 Steps 801 to 803 are the same as steps 301 to 303, and are not described here. In step 804, the HSS provides user subscription data to the MME, and the provided user subscription data includes a service category, APN, or charging information.

 Next, in step 805, the MME sends a create bearer request message to the serving SAE gateway, where the message carries the service class, APN or charging information.

Next, in step 806, the serving SAE gateway to the PDN SAE Gateway transmits a routing update / bearer request message, and the message carries traffic class ¹ APN or other billing information. The PCEF in the PDN SAE gateway selects the default PCC rule of the UE according to the service class, APN or charging information, activates the corresponding PCC rule, and establishes a wired bearer between the PDN SAE gateway and the serving SAE gateway in this step.

 Steps 807 to 814 are completely the same as steps 307 to 314, and are not described herein again. The tenth embodiment of the present invention relates to a method for establishing a default bearer of a wireless network. In this embodiment, the network side selects a default PCC rule according to the service type, APN, or charging information of the UE, and the PCEF is based on the selected default PCC rule. A default bearer is established for the UE. The network entity that selects the default PCC rule can be HSS, SPR, MME, PCEF or PCRF. In this embodiment, the network entity that selects the default PCC rule is a PCEF as an example. The service class, the APN, or the charging information is generated by the PCRF on the network side, and the default PCC rules are pre-configured in the PCEF. As shown in Figure 9.

 Steps 901 to 906 are completely the same as steps 401 to 406, and details are not described herein again. In step 907, the PDN SAE gateway performs signaling interaction with the PCRF, and the PCRF generates a service class, APN, or charging information of the UE according to a certain policy, or queries the SPR for the service class, APN, or charging information of the UE, and Returning to the PDN SAE gateway, the PCEF in the PDN SAE gateway selects the identification number of the default PCC rule of the UE, activates the corresponding PCC rule, and in this step, establishes a wired bearer between the PDN SAE gateway and the serving SAE gateway. .

Steps 908 to 915 are completely the same as steps 408 to 415, and are not described herein again. The eleventh embodiment of the present invention relates to a radio network default bearer establishment method. In this embodiment, the network side selects a default PCC rule according to the service type, APN, or charging information of the UE, and the PCEF is based on the selected default PCC. The rule establishes a default bearer for the UE. The network entity that selects the default PCC rule may be an HSS, SPR, MME, PCEF, or PCRF. In this embodiment, the network entity that selects the default PCC rule is a PCEF as an example. The service class, APN, or charging information is provided by the UE, that is, the UE classifies the service class and APN of the UE during the attaching process. Or the accounting information is sent to the MME on the network side. The default PCC rules are pre-configured in the PCEF. The specific process is shown in Figure 10.

 In step 1001, the UE sends an attach request to the MME, where the message carries the identifier of the UE (the temporary identifier P-TMSI is used preferentially, and the permanent identifier IMSI is used without the P-TMSI), and the core network identifies the UE by using the identifier. And complete the authentication and UE attachment process. At the same time, the message will also carry the service class, APN or charging information of the UE.

 Steps 1002 and 1003 are identical to steps 302 and 303, respectively, and are not described herein.

 In step 1004, the HSS provides user subscription data to the MME.

 Next, in step 1005, the MME sends a create bearer request message to the serving SAE gateway, where the message carries the service class, APN or charging information of the UE.

 Next, in step 1006, the serving SAE gateway sends a routing update/bearing request message to the PDN SAE gateway, where the message carries the service class, APN or charging information of the UE. The PCEF in the PDN SAE gateway selects the default PCC rule of the UE according to the service class, APN or charging information, activates the corresponding PCC rule, and establishes a wired bearer between the PDN SAE gateway and the serving SAE gateway in this step.

 Steps 1007 to 1014 are completely the same as steps 307 to 314, respectively, and are not described herein again.

 The twelfth embodiment of the present invention relates to a method for establishing a default bearer of a radio network, and the present embodiment is different from the foregoing embodiments in that the foregoing embodiments are applied to a scenario in which a UE accesses a 3GPP network, and the present embodiment It is applied to the scenario where the UE accesses the non-3GPP network. In the present embodiment, the mobility management protocol of Proxy Mobile IP (PMIP) is used in the non-3GPP network. The specific process is shown in FIG.

In step 1301, when the UE attaches to the non-3GPP network, the UE will initiate an Internet Key Exchange Protocol Version 2 (referred to as 'ΊΚΕν2'). The tunnel establishment process. The address of the evolved Packet Data Gateway (ePDG) can be pre-configured or queried by the DOMAIN NAME SYSTEM ("DNS"), and then the UE is authenticated.

 During the establishment of an IKE tunnel, the address of the PDN SAE gateway can be sent to the ePDG. The method of obtaining the address of the PDN SAE gateway may be notified to the ePDG by the HSS/AAA during the access authentication or service authentication, or may be reported by the UE when attaching, but the method is not limited. The address of the PDN SAE gateway can also be stored in the source network side network entity (such as MME, HSS). During the handover preparation process, the address of the PDN SAE gateway is notified to the ePDG or UE. For example, the ePDG is notified through the interface of the MME and the ePDG; for example, the UE is notified in the handover preparation, or directly notified to the UE in the SAE network attachment process of the UE. In this step, the UE may obtain the address of the ePDG in the following manner:

(1) In the access authentication process, the UE determines the address of the ePDG and the PDN SAE gateway by the HSS/AAA through the reported parameters (such as the APN and the network address identifier NAI), and notifies the UE in the response message of the access authentication. ;

 It should be noted that when there are multiple Home Agents (HAs), similar to the case of multiple PDN SAE gateways, different HAs handle different services. At this time, after the UE accesses the non-3GPP network, the UE The service request is initiated to the new PDN SAE gateway (ie, HA), and the HSS/AAA can determine the addresses of the new ePDG and PDN-GW by using some parameters (such as: APN, network address identifier NAI). These parameters can be carried in the PMIP registration request message, but are not limited to this form.

 (2) After access authentication, obtain the addresses of the ePDG and PDN SAE gateways through the DNS query process;

 (3) In the handover preparation process, the source network side entity (such as MME, HSS) notifies the UE to access the ePDG and PDN SAE gateway addresses of the network.

 Next, in step 1302, the ePDG sends a proxy binding message to the PDN SAE gateway, which processes the received proxy binding message.

 Specifically, the PDN SAE gateway needs to establish a binding entity for the UE and assign an IP address to the UE. If the PDN SAE gateway needs to securely authenticate the binding message, the PDN SAE gateway will contact the AAA server to verify the authentication and key information in the binding message (this security authentication is an optional step). In addition, the PDN SAE gateway also needs to select a pre-configured default PCC rule for the accessed UE according to the policy and subscription data.

For example, each default PCC rule is pre-configured in the PCEF in the PDN SAE gateway, the PCEF. Indexing to the relevant PCC rule according to the parameters in the received proxy binding message, that is, selecting one of the default PCC rules pre-configured by the network side according to the parameters carried in the proxy binding message, the proxy The parameters in the binding message may be reported by the UE or acquired from the network side entity during the authentication process. The index PCC rule can be displayed by explicitly carrying the identification number of the default PCC rule in the proxy binding message (as notified to the UE when authenticating in step 1301), and other parameters (such as APN, network address identifier) can also be utilized. A plurality of parameters such as NAI, or a combination of multiple parameters, are used to index related PCC rules, and the PCC rules indexed to are the default PCC rules selected for the UE. The PCEF activates the default PCC rule indexed, and establishes a default bearer for the UE according to the default PCC rule.

 Alternatively, the PCEF in the PDN SAE gateway reports a binding request to the PCRF, and the PCRF sends the relevant default PCC rule to the PCEF. Specifically, after receiving the proxy binding message, the PCEF establishes a user plane request to the PCRF, where the request message includes parameters such as an NAI, an Access RAT (Access Wireless Technology) for identifying the user, and requests the The default PCC rule of the UE. After receiving the request from the PCEF, the PCRF will contact the SPR (in this embodiment, the SPR and the HSS are divided into two logical entities, but may also be implemented in the same physical entity), and the related information is requested from the SPR, such as the The subscription data of the UE, the identification number of the PCC rule, or the PCC rule. The PCRF obtains the default PCC rule selected for the UE according to the information obtained from the SPR, such as the subscription data of the UE, the identification number of the PCC rule, or the PCC rule, and sends the default PCC rule to the PCEF. The PCEF establishes a default bearer for the UE according to the default PCC rule selected by the PCRF.

 Alternatively, the PCEF is pre-configured with default PCC rules, but the PCRF is required to send the PCEF with the identification number of the default PCC rule selected for the UE to activate the default PCC rule. Specifically, it can be divided into two cases:

 A. The identification number of each default PCC rule is pre-configured in the SPR, and the PCRF obtains the identification number of the default PCC rule of the UE by interacting with the SPR.

 B. The identification number of each default PCC rule is pre-configured in the PCRF. The PCRF may need to select the identification number of the default PCC rule of the UE by using the user subscription information exchanged with the SPR, and select the default PCC. The identification number of the rule is sent to the PCEF, and the PCEF activates the corresponding default PCC rule according to the received identification number, and establishes a default bearer for the UE according to the rule.

In this step, the PCRF may also pass the QoS profile required for this service to the PCEF. In this step, the ePDG carries the QoS profile parameters required for the current service in the sent proxy binding message (for example, by extending the PMIP registration message, the required QoS profile parameter is transmitted. Give PCEF). The ePDG can obtain the QoS profile parameter from the HSS/AAA during the access authentication, or can report the parameter when the UE attaches.

 Next, in step 1303, the PDN SAE gateway sends a proxy binding acknowledgement to the ePDG, and the proxy binding acknowledgement may include an IP address and QoS parameter information allocated for the UE. The PDN SAE gateway may need to interact with the PCRF to obtain the relevant QoS parameters.

 Next, in step 1304, after the proxy binding is successful, the IP Sec channel establishment is completed.

 Next, in step 1305, the ePDG sends the final IKEv2 information to the UE, where the information includes an IP address assigned to the UE, and the like.

 Next, in step 1306, the connectivity of the IP of the UE to the PDN SAE gateway is established.

 A thirteenth embodiment of the present invention relates to a radio network default bearer establishment method, which is substantially the same as the twelfth embodiment, except that in the twelfth embodiment, PMIP movement is used in a non-3GPP network In the present embodiment, the mobility management protocol of the client mobile IP (Client Mobile IP, hereinafter referred to as "CMIP") version 6 is used in the non-3GPP network. The specific process is shown in FIG. 14.

 In step 1401, when the UE attaches to the non-3GPP network, the UE will initiate an IKEv2 tunnel establishment procedure. The address of the ePDG can be pre-configured or queried via DNS. The UE is then authenticated.

 During the establishment of an IKE tunnel, the address of the PDN SAE gateway can be sent to the ePDG. The method of obtaining the address of the PDN SAE gateway may be notified to the ePDG by the HSS/AAA during the access authentication or service authentication, or may be reported by the UE when attaching, but the method is not limited. The address of the PDN SAE gateway can also be stored in the source network side network entity (such as MME, HSS). During the handover preparation process, the address of the PDN SAE gateway is notified to the ePDG or UE. For example, the ePDG is notified through the interface of the MME and the ePDG; for example, the UE is notified in the handover preparation, or directly notified to the UE in the SAE network attachment process of the UE. In this step, the UE may obtain the address of the ePDG in the following manner:

(1) In the access authentication process, the UE determines the address of the ePDG and the PDN SAE gateway by the HSS/AAA through the reported parameters (such as the APN and the network address identifier NAI), and notifies the UE in the response message of the access authentication. ;

It should be noted that when there are multiple HAs, different HAs handle different services, similar to the case of multiple PDN SAE gateways. At this time, after the UE accesses the non-3GPP network, the UE will go to the new PDN SAE gateway (ie: HA). ) to initiate a service request, HSS/AAA can pass some parameters (such as: APN, network The address identifier NAI) determines the address of the new ePDG, PDN-GW. These parameters may be carried in the MIP registration request message, but are not limited to this form.

 (2) After access authentication, obtain the addresses of the ePDG and PDN SAE gateways through the DNS query process;

 (3) In the handover preparation process, the source network side entity (such as MME, HSS) notifies the UE to access the ePDG and PDN SAE gateway addresses of the network.

 Next, in step 1402, the ePDG sends the final IKEv2 information to the UE, where the information includes an IP address assigned to the UE, and the like.

 Next, in step 1403, an IP sec channel between the UE and the ePDG is established.

 Next, in step 1404, the UE establishes a security association with the PDN SAE gateway to ensure that subsequent binding information is secure. In the process of establishing a security association, the QoS profile parameters of this service can also be passed to the PDN SAE gateway.

 Next, in step 1405, the UE sends a Binding Update message to the PDN SAE Gateway, and the PDN SAE Gateway processes the received Binding Update message.

 Specifically, the PDN SAE gateway needs to establish a binding entity for the UE and assign an IP address to the UE. If the PDN SAE gateway needs to securely authenticate the binding message, the PDN SAE gateway will contact the AAA server to verify the authentication and key information in the binding message (this security authentication is an optional step). In addition, the PDN SAE gateway also needs to select a pre-configured default PCC rule for the accessed UE according to the policy and subscription data.

 For example, each default PCC rule is pre-configured in the PCEF in the PDN SAE gateway, and the PCEF indexes to the relevant PCC rule according to the parameters in the received binding update message, that is, according to the binding update message. The parameters carried in the network are selected from the default PCC rules pre-configured on the network side. The index PCC rule that can be displayed by explicitly carrying the identification number of the default PCC rule (as notified to the UE when authenticating in step 1401) in the binding update message may also utilize other parameters (such as APN, network address identifier). A plurality of parameters such as NAI, or a combination of multiple parameters, are used to index related PCC rules, and the PCC rules indexed to are the default PCC rules selected for the UE. The PCEF activates the default PCC rule indexed to, and establishes a default bearer for the UE according to the default PCC rule.

 Alternatively, the PCEF in the PDN SAE gateway reports a binding request to the PCRF, and the PCRF sends the relevant default PCC rule to the PCEF.

Specifically, after receiving the binding update message, the PCEF reports to the PCRF to establish a user plane request. The request message includes parameters such as an NAI, an Access RAT (Access Radio Technology) for identifying a user, and requests a default PCC rule of the UE. After receiving the request from the PCEF, the PCRF will contact the SPR (in this embodiment, the SPR and the HSS are divided into two logical entities, but may also be implemented in the same physical entity), and the related information is requested from the SPR, such as the The subscription data of the UE, the identification number of the PCC rule, or the PCC rule. The PCRF obtains the default PCC rule selected for the UE according to the information obtained from the SPR, such as the subscription data of the UE, the identification number of the PCC rule, or the PCC rule, and sends the default PCC rule to the PCEF. The PCEF establishes a default 7-load for the UE according to the default PCC rule selected by the PCRF.

 Alternatively, the PCEF is pre-configured with default PCC rules, but the PCRF is required to send the PCEF with the identification number of the default PCC rule selected for the UE to activate the default PCC rule. Specifically, it can be divided into two cases:

 A. The identification number of each default PCC rule is pre-configured in the SPR, and the PCRF obtains the identification number of the default PCC rule of the UE by interacting with the SPR.

 B. The identification number of each default PCC rule is pre-configured in the PCRF. The PCRF may need to select the identification number of the default PCC rule of the UE by using the user subscription information exchanged with the SPR, and select the default PCC. The identification number of the rule is sent to the PCEF, and the PCEF activates the corresponding default PCC rule according to the received identification number, and establishes a default bearer for the UE according to the rule.

 In this step, the PCRF may also pass the QoS profile required by this service to the PCEF. In this step, the ePDG intercepts the UE registration message, and adds the QoS profile parameter required for the current service in the sent binding update message (for example, by extending the MIP registration message, the required QoS profile parameter is transmitted. Give PCEF). The ePDG can obtain the QoS profile parameters from the HSS/AAA during access authentication. The UE may also carry the QoS parameters of the current service in the binding message, for example, by reporting the extension of the registration message, such as multiple ΜΙΡν4, ΜΙΡνό, DS-MIP, to the PDN SAE GW; then, in step 1406, the PDN SAE gateway Assigning an IP address to the UE, and issuing a binding acknowledgement message to the UE, establishing IP connectivity of the UE to the PDN SAE gateway

 The fourteenth embodiment of the present invention relates to a method for establishing a default bearer of a radio network. In this embodiment, based on the foregoing embodiments, the UE is in a roaming network.

The default bearers in the roaming scenario should also be classified, and each type of default bearer corresponds to a default PCC rule. Therefore, if the UE is in a roaming network, the default PCC rule will be selected for the UE by the home network and/or the roaming network, and the PCEF establishes a default inheritance for the UE according to the selected default PCC rule. Loaded. Depending on the specific situation, the default PCC rule selected for the UE may be the default PCC rule of the UE in the home network, or may be the default PCC rule selected for the UE in the roaming network.

 Specifically, in the roaming scenario, whether the default PCC rule in the roaming network needs to be selected for the UE is related to whether the roaming network has a PCEF function. For example, if the roaming network has the PCEF function, the default setting in the roaming network must be selected for the UE. PCC rules, otherwise it is determined that it is not necessary to select the default PCC rules in the roaming network for the UE as the case may be. For the case that the default PCC rule in the roaming network is not required for the UE, the default bearer can be established directly using the default PCC rule selected by the home network, and the default PCC rule can be selected by using the above embodiment. The following highlights the need to select the default PCC rules for roaming networks for the UE.

 When it is required to select a default PCC rule in the roaming network for the UE, the roaming network and/or the home network may determine the default PCC rule of the UE in the roaming network according to the operator policy and/or the roaming protocol, which may be required Referring to the default PCC rule of the UE in the home network or its identification number; or, the default PCC rule of the UE in the home network may be mapped to the default PCC rule in the roaming network according to a predetermined mapping mechanism.

 For example, when the roaming network determines the default PCC rule of the UE in the roaming network according to the operator policy and/or the roaming protocol, the default PCC rule in the roaming network may be selected for the roaming UE by one of the following methods:

 (1) The UE sends the identifier of the default PCC rule in the attached message to the roaming network, and identifies whether the identification number of the default PCC rule carried by the UE is assigned by the home network or roaming. If the network is allocated, if it is allocated by the home network, the roaming network needs to convert it into the identification number of the corresponding default PCC rule of the roaming network according to the operator policy and/or the roaming agreement. The PCEF of the roaming network activates the corresponding PCC rule according to the identification number, and establishes a default bearer for the roaming UE.

 (2) If the identification number of the default PCC rule of the roaming UE exists as the subscription data in the HSS, the identification number of the default PCC rule of the home network may be obtained through the user subscription data request/providing message, and according to the operator policy. And/or the roaming protocol converts it into the identification number of the corresponding default PCC rule of the roaming network (the entity that completes the identification number conversion may be HSS, V-PCEF, H/V-PCRF, etc.).

(3) If the default PCC rule of the UE is selected according to QoS (such as Label, signed QoS parameters, etc.), service class, APN or charging information, and the above parameters exist in the form of subscription data in HSS. The above parameters may be obtained by the user subscription data request/providing message, and the roaming network uses these parameters to select a corresponding default PCC rule in the roaming network according to the operator policy and/or the roaming protocol.

 (4) If the default PCC rule of the roaming UE is selected by the H-PCRF (PCRF of the home network), the identification number of the default PCC rule of the UE of the home network may be obtained by using the PCC rule request/providing message, and The roaming network converts it to the identification number of the corresponding default PCC rule of the roaming network according to the operator policy and/or the roaming agreement.

 (5) If the default PCC rule is selected according to QoS, service class, APN or charging information, and the above parameters are provided by the H-PCRF, the above parameters may be obtained through the PCC rule request/provide message, and the parameters are utilized by the roaming network. The corresponding default PCC rules in the roaming network are selected according to the operator policy and/or the roaming agreement.

 It should be noted that if the method for obtaining the identification number (V-ID) of the default PCC rule of the roaming network through the identification number (H-ID) of the default PCC rule of the home network is not feasible, the predetermined The mapping mechanism maps the default PCC rule corresponding to the H-ID to the default PCC rule of the roaming network, and the entity that completes the mapping may be located in the home network or in the roaming network, or negotiated by the home network and the roaming network through the PCC. , finally get the V-ID of the roaming network. In a specific implementation, it is also considered to classify the default PCC rules in the roaming network into two categories, namely: a local default PCC rule for the home subscriber and a roaming default PCC rule for the roaming subscriber.

 In the roaming scenario, if the roaming network architecture of the SGi interface from the roaming network is used, and the V-PCEF (PCEF of the roaming network) needs to interact with the H-PCRF through the V-PCRF (PCRF of the roaming network) (in this case There is an S9 interface between V-PCRF and H-PCRF, and the corresponding flowchart is shown in Figure 11. In this scenario, since the PCEF is definitely located in the roaming network, the default PCC rule in the roaming network needs to be selected for the UE. It should be noted that the V-PCRF is drawn as a dotted line in the figure, indicating that there is a possibility that the V-PCRF does not participate in the process, that is, the V-PDN SAE gateway (the PDN SAE gateway of the roaming network) has an interface directly connected to H-PCRF.

In the roaming scenario, if the roaming network architecture of the SGi interface is used from the home network, the serving SAE gateway of the roaming network needs to interact with the H-PDN SAE gateway (the PDN SAE gateway of the home network) through the S8 interface, and the corresponding process As shown in Figure 12. In this scenario, the default PCC rule in the roaming network needs to be selected for the UE. If there is no PCEF function in the roaming network, for example, only the PCEF function exists on the H-PDN SAE gateway, Select the default PCC rule in the roaming network for the UE; if there is a PCEF function in the roaming network, such as a roaming network If the service SAE gateway has PCEF function, it is necessary to select the default PCC rule in the roaming network for the UE.

 It can be seen that the present embodiment enables the roaming network to also select a default PCC rule for the UE in roaming.

 The method for mapping the default PCC rule of the home network to the default PCC rule of the roaming network in this embodiment may be applied not only to the default bearer but also to the dedicated bearer.

 For example, if the roaming network architecture of the SGi interface is used from the roaming network, the specific process of establishing a dedicated bearer in the roaming network is as shown in FIG. 24. In step 2401a, the H-PCRF checks the PCC rules related to the service ( That is, the default PCC rule of the roaming network mapped according to the default PCC rule of the home network is delivered to the V-PCRF. Next, in step 2401b, the V-PCRF will issue the relevant PCC rules to the PDN SAE gateway. Step 2402 to step 2409 are the same as the prior art, and are not described here. In step 2410a, the PDN SAE gateway acknowledges the response message of the relevant PCC rule to the V-PCRF. In step 2410b, the V-PCRF responds to the H-PCRF with a response message of the PCC rule. The entity that completes the mapping may be located in the home network or in the roaming network, or may be negotiated by the home network and the roaming network via the PCC.

 A fifteenth embodiment of the present invention relates to a radio network default bearer setup method. In this embodiment, when the UE attaches to the network side, the eNB selects a core network device (such as an MME, an ePDG, a PDN SAE gateway, and a service SAE gateway). In this embodiment, the eNB selects the MME and the serving SAE gateway, and the network side selects the default PCC rule according to the service type, APN, or charging information of the UE as an example. The specific process is shown in Figure 25.

 In step 2501, the UE-initiated attach request message is first sent to the eNB through RRC signaling. Next, in step 2502, the eNB selects an appropriate MME according to parameters (such as P-TMSI) carried by the UE's attach request message, and selects a serving SAE gateway for the UE. The eNB can select a suitable serving SAE gateway for the UE by referring to the configuration relationship between the SAE gateway, the routing metric, and the load link status.

 Then, in step 2503, the eNB forwards the attach request message to the selected MME, and carries the identifier of the serving SAE gateway in the attach request message (the identifier may be the IP address of the serving SAE gateway, but is not limited to the IP address. address).

Steps 2504 to 2517 are completely the same as steps 902 to 915, respectively, and details are not described herein again. It is worth mentioning that the case where the eNB chooses to serve the SAE gateway may also occur in the Tracking Area Update ("TAU"), and the eNB selects the serving SAE gateway. This occurs mainly in the scenario where the MME/UPE pool is deployed, or the network is abnormal, and the network needs to be operated and maintained.

 In addition, it should be noted that, in the foregoing embodiments, when the network side cannot select a default PCC rule for the UE or an abnormal situation occurs, the network side may select a default PCC rule for the UE according to the operator policy, and according to the The default PCC rule establishes a corresponding default bearer for the UE.

 A sixteenth embodiment of the present invention relates to a wireless network default bearer setup system, as shown in FIG. 15, comprising: a storage module, configured to save each default PCC rule preconfigured on the network side; and a selection module, configured to attach to the UE In the process, a default PCC rule is selected from the default PCC rules saved by the storage module. The establishing module is configured to establish a corresponding default bearer for the UE according to the default PCC rule selected by the selecting module. Each of the pre-configured default PCC rules corresponds to a type of default bearer. Therefore, when the default bearer is set for the UE, only one of the limited configured rules can be selected, so that the processing workload is relatively small, the processing procedure is relatively fast, and the default bearer is reduced. The establishment delay.

 The selection module selects a default PCC rule by using one of the following methods: selecting a default PCC rule according to the information in the subscription data of the UE, and selecting a default PCC rule according to the default PCC rule generated by the PCRF or the identification number of the default PCC rule. And selecting a default PCC rule according to the QoS parameter of the UE, the service class, the APN or the charging information, or selecting the default PCC rule according to the identification number of the expected default PCC rule reported by the UE in the attaching process. This embodiment can be flexibly implemented.

 If the UE is in the roaming network, the default PCC rule selected by the module for the UE may be the default PCC rule of the UE in the home network, or may be the roaming network selected for the UE. The default PCC rule in . Specifically, the default PCC rule of the UE in the home network may be mapped to the default PCC rule in the roaming network according to one of the following ways:

 (1) The roaming network and/or the home network determines the default PCC rule of the UE in the roaming network according to the operator policy and/or the roaming protocol, and may need to refer to the default PCC rule of the UE in the home network; (2) The default PCC rule of the UE in the home network is mapped to a default PCC rule in the roaming network according to a predetermined mapping mechanism.

 It can be seen that the present embodiment can enable the roaming network to also select a default PCC rule for the UE in roaming.

The system of this embodiment may further include a determining module, configured to determine whether the establishing module already exists Select the default PCC rule selected by the module. If the determining module determines that the default PCC rule selected by the selecting module already exists in the establishing module, the default PCC rule selected by the establishing module is notified by sending the identification number of the default PCC rule to the establishing module; If the default PCC rule selected by the selection module does not exist in the module determination establishing module, the selected default PCC rule is sent to the establishing module, and the default PCC rule is saved by the establishing module. In order to avoid repeating the transmission of rule content to the PCEF, the communication between different network entities is reduced, thereby saving system resources.

 It should be noted that each module in this embodiment is a logic module, and various practical implementations may be implemented in practical applications.

 In the embodiment of the present invention, the network side pre-configures at least one default PCC rule, and classifies the default bearer in advance, and each type of default bearer corresponds to a pre-configured default PCC rule, in the UE. During the attach process, one of the pre-configured default PCC rules is selected, and the PCEF establishes a corresponding default bearer for the UE according to the selected default PCC rule. Since the default PCC rule is pre-configured, it is not necessary to generate a rule for each UE. When a default bearer is established for the UE, only one of the limited configured rules can be selected, thereby making processing. The workload is relatively small, the processing is relatively fast, and the setup delay of the default bearer is reduced. Moreover, by classifying the default bearers in advance, the number of pre-configured default PCC rules is controlled within a limited range, which further speeds up the process of establishing a default bearer for the UE.

 The network side can pre-classify the default bearers according to the tariff standard, the business model, the service model, and the user level of the subscription. The number of default PCC rules that are pre-configured is limited, and the users can be flexibly configured for different levels. Provide different personalized services.

 If the default PCC rule is pre-configured in the PCEF, the network entity that selects the default PCC rule does not need to send the rule content to the PCEF. As long as the rule ID is sent, the traffic between different network entities is reduced, thereby saving the system. Resources.

 Even if the default PCC rule is not pre-configured in the PCEF, since the PCEF saves the received default PCC rule, if the selected default PCC rule has been sent to the PCEF before, there is no need to repeat The PCEF sends rule content, which reduces the amount of communication between different network entities, thereby saving system resources.

 The network side can select default PCC rules according to various manners, such as selection according to subscription data or selection according to QoS parameters, etc., so that the embodiments of the present invention can be flexibly implemented.

If the UE is in the roaming network, the network side may select the UE for the UE according to the specific situation. For the provincial PCC rule, the selected default PCC rule may be the default PCC rule of the UE in the home network; it may also be the default PCC rule of the UE in the roaming network. The roaming network is also enabled to select a default PCC rule for the roaming UE.

 While the invention has been illustrated and described with reference to the preferred embodiments embodiments The spirit and scope of the invention.

Claims

Rights request A method for establishing a default bearer of a wireless network, comprising the following steps: In a process of attaching a user equipment, selecting one of a default policy and a charging control rule pre-configured by the network side, and performing policy and charging execution The function establishes a corresponding default 7-load for the user equipment according to the selected default PCC rule.  2. The method for establishing a default bearer of a wireless network according to claim 1, further comprising the steps of:  The network side classifies the default bearers in advance, and each type of default bearer corresponds to one default PCC rule preconfigured by the network side.  The method for establishing a default bearer of a wireless network according to claim 2, wherein the network side classifies the default bearer in advance according to one of the following modes or any combination thereof:  The default bearers are classified in advance according to the tariff;  Pre-classify default bearers according to business models or business models;  The default bearers are pre-classified according to the contracted user level.  The method for establishing a default bearer of a wireless network according to claim 1, wherein one of the default PCC rules pre-configured by the network side is selected by:  The user equipment corresponds to one of the default PCC rules, and the default PCC rule of the user equipment or the identification number of the default PCC rule is saved as the subscription data of the user equipment in the universal database on the network side;  And selecting one of each default PCC rule pre-configured by the network side according to the subscription data of the user equipment.  The method for establishing a default bearer of a wireless network according to claim 4, wherein the universal database is a home user server;  If the default PCC rules are pre-configured in the policy and charging execution function, the mobility management entity on the network side queries the home user server for the identification number of the default PCC rule corresponding to the user equipment. And sending the queried identification number to the policy and charging execution function; If the default PCC rules are pre-configured in the home user server, the home user server sends the default PCC rule corresponding to the user equipment or its identification number to the policy and meter through the mobility management entity. Fee execution function; Or the general database is an authentication, authorization, and accounting server, and the authentication, authorization, and accounting server sends the default PCC rule corresponding to the user equipment or the identification number of the default PCC rule to the policy and Billing execution function;  Or the general database is a contract specification database, and the contract specification database sends the default PCC rule corresponding to the user equipment or the identification number of the default PCC rule to the policy by using a policy and a charging rule function on the network side. And billing execution function.  The wireless network default bearer establishing method according to claim 1, wherein in the user equipment attaching process, the pre-configured default PCC rule is selected by the network side policy and charging rule function. The selection result is sent to the policy and charging execution function.  The method for establishing a default bearer of a wireless network according to claim 6, wherein the policy and charging rule function selects the default PCC rule according to a predetermined policy or a database of a subscription specification database.  The method for establishing a default bearer of a wireless network according to claim 6, wherein if the default PCC rules are pre-configured in the policy and charging execution function, the policy and charging rules are The function sends the identifier of the selected default PCC rule to the policy and the charging execution function, and the policy and the charging execution function establish a default load for the user equipment according to the default PCC rule corresponding to the identifier.  If the default PCC rules are pre-configured in the policy and charging rule function, the policy and charging rule function sends the selected default PCC rule or the identification number of the default PCC rule to the policy. And a charging execution function, the policy and the charging execution function establish a default bearer for the user equipment according to the received default PCC rule or according to a default PCC rule corresponding to the received identification number.  The method for establishing a default bearer of a wireless network according to claim 1, wherein one of the default PCC rules pre-configured by the network side is selected by:  And selecting one of each default PCC rule pre-configured by the network side according to the quality of service requirement of the user equipment, the service category, the access point name, or the charging information;  The method for establishing a default bearer of a wireless network according to claim 9, wherein the network side entity that selects the default PCC rule is one of the following: a home user server, a subscription specification database, a mobility management entity, Policy and billing execution functions, policies, and billing rules. The method for establishing a default bearer of a wireless network according to claim 9, wherein the service category, access point name or charging information is obtained by one of the following methods: The service category, the access point name, or the charging information is saved as the subscription data of the user equipment on the network side;  Generating the service category, access point name or charging information by the policy and charging rule function on the network side;  The service class, the access point name, or the charging information of the user equipment is sent to the network side by the user equipment during the attaching process.  The method for establishing a default bearer of a radio network according to claim 1, wherein the user equipment sends an identifier of a desired default PCC rule to the network side during the attaching process, where The network side selects a corresponding default PCC rule according to the received identification number.  The method for establishing a default bearer of a wireless network according to claim 12, wherein if the default PCC rules are pre-configured in the policy and charging execution function, the user equipment is received. The network entity of the identifier of the desired default PCC rule is sent to the policy and the charging execution function, and the policy and the charging execution function are established for the user equipment according to the default PCC rule corresponding to the identification number. Default bearer  If the default PCC rules are pre-configured in the policy and charging rule function, the network entity that receives the identification number of the default PCC rule desired by the user equipment sends the identification number to the policy. And the charging execution function, if there is no default PCC rule corresponding to the identification number in the policy and charging execution function, requesting the default PCC rule corresponding to the identification number to the policy and charging rule function.  The method for establishing a default bearer of a wireless network according to claim 1, wherein, in the attaching process of the user equipment, if the network to which the user equipment is attached is a non-third generation partner project network, When the network side processes the binding message in the process of attaching the user equipment, the default PCC rule is selected.  The method for establishing a default bearer of a wireless network according to claim 14, wherein the policy and the charging execution function, when receiving the binding message, are based on parameters carried in the binding message. Select one of each default PCC rule pre-configured on the network side; or When the policy and the charging execution function receive the binding message, request the default PCC rule of the user equipment from the policy and charging rule function, and the policy and the charging rule function interact with the subscription specification database. And selecting one of each default PCC rule pre-configured by the network side, and notifying the selected default PCC rule of the policy and the charging execution function; or The default PCC rules are pre-configured in the policy and charging execution function, and the policy and charging execution function notifies the policy and charging rule function when receiving the binding message, The fee rule function selects one of the default PCC rules pre-configured by the network side, and sends the identification number of the selected default PCC rule to the policy and the charging execution function.  The method for establishing a default bearer of a wireless network according to any one of claims 1 to 15, wherein if the user equipment is in a roaming network, the user equipment is selected by the home network and/or the roaming network. a default PCC rule; the policy and the charging execution function establish a default bearer for the user equipment according to the selected default PCC rule;  The default PCC rule selected for the user equipment is the default PCC rule of the user equipment in the home network; or the default PCC rule selected for the user equipment in the roaming network.  The method for establishing a default bearer of a wireless network according to claim 16, wherein the default PCC rule selected in the roaming network for the user equipment is determined according to one of the following manners: according to an operator policy and / or roaming agreement determines the default PCC rules of the user equipment in the roaming network;  The default PCC rules of the user equipment in the home network are mapped to default PCC rules in the roaming network according to a predetermined mapping mechanism.  The method for establishing a default bearer for a wireless network according to any one of claims 1 to 15, further comprising the steps of:  When the network side is in an abnormal situation or the default PCC rule cannot be selected, the network side selects a default PCC rule for the user equipment according to the operator policy, and selects the default PCC rule according to the selected default PCC rule. The device establishes the corresponding default bearer.  19. A wireless network default bearer setup system, comprising:  a storage module, configured to save each default PCC rule preconfigured on the network side;  a selection module, configured to select a default PCC rule from each default PCC rule saved by the storage module during the user equipment attaching process;  And a establishing module, configured to establish a corresponding default load for the user equipment according to a default PCC rule selected by the selection module. The wireless network default bearer setup system according to claim 19, wherein the network side classifies the default bearers in advance, and each type of default bearer corresponds to one default PCC preconfigured on the network side. rule. The wireless network default bearer setup system according to claim 19, wherein the selection module selects the default PCC rule by one of the following methods:  Selecting the default PCC rule according to information in the subscription data of the user equipment;  Selecting the default PCC rule according to the default PCC rule generated by the policy and charging rule function or the identification number of the default PCC rule;  Selecting the default PCC rule according to the quality of service parameter, the service category, the access point name, or the charging information of the user equipment;  The default PCC rule is selected according to the identification number of the expected default PCC rule reported by the user equipment during the attaching process.  The wireless network default bearer establishing system according to claim 19, wherein, if the user equipment is in a roaming network, the selecting module is a default PCC rule selected by the user equipment, that is, the user The default PCC rule of the device in the home network; or the default PCC rule in the roaming network selected for the user equipment.  The wireless network default bearer setup system according to claim 22, wherein the default PCC rule selected in the roaming network for the user equipment is determined according to one of the following manners: according to the operator policy and / or roaming agreement determines the default PCC rules of the user equipment in the roaming network;  The default PCC rules of the user equipment in the home network are mapped to default PCC rules in the roaming network according to a predetermined mapping mechanism.  The wireless network default bearer setup system according to any one of claims 19 to 23, wherein the system further includes a determining module, configured to determine whether the selection is already in the establishing module The default PCC rules selected by the module;  If the determining module determines that the default selected by the selection module already exists in the establishing module The PCC rule notifies the default PCC rule selected by the establishing module by sending an identification number of the default PCC rule to the establishing module;  If the determining module determines that the selection selected by the selection module does not exist in the establishing module The PCC rule sends the selected default PCC rule to the setup module, and the setup module saves the default PCC rule.