CN101291525A - Wireless network default bearer establishment method and system thereof - Google Patents

Abstract

The invention relates to the field of wireless communication, and discloses a wireless network default bearer establishment method and system thereof, which can speed up the processing process when establishing the default bearer, and can provide users with individualized services without losing flexibility. In the present invention, during the UE attachment process, one of the pre-configured default PCC rules is selected, and the PCEF establishes a default bearer for the UE according to the selected default PCC rule. The network side classifies default bearers in advance, and each type of default bearer corresponds to a default PCC rule. The network side can pre-classify the default bearers according to tariff standards, business models, service models, and subscribed user levels. If the selected default PCC rule is pre-configured in the PCEF or has been transmitted to the PCEF, the network entity that selects the default PCC rule does not need to send the rule content to the PCEF, but only needs to send the identification number of the rule.

Description

Wireless network default bearer establishment method and system thereof

technical field

The invention relates to the field of wireless communication, in particular to a default bearer establishment technology.

Background technique

The Universal Mobile Telecommunications System ("UMTS" for short) is proposed by the 3rd Generation Partnership Project ("3GPP") and uses Wideband Code Division Multiple Access (WCDMA for short). ”) air interface technology of the third generation mobile communication system. In a UMTS network, a corresponding bearer is established for a user equipment (User Equipment, referred to as "UE") when it has services, and the bearer establishment 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 proposed a concept of an evolution network that serves future communication needs, System Architecture Evolution ("SAE") ) belongs to the next generation wireless core network evolution project proposed by 3GPP.

The SAE specified in TR23.882-V1 80 mainly includes: Mobility Management Entity (MME for short), User Plane Entity (UPE for short), 3GPP Anchor (3GPP anchor) and SAE Anchor (SAE anchor point) four logical function modules, as shown in Figure 16. The MME is the mobility management module, which is responsible for the mobility management of the control plane. It 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 MME to initiate paging when downlink data arrives in the idle state, and managing and saving IP bearer parameters and routing information in the network. It corresponds to the data plane part of the SGSN in the current UMTS system; the 3GPP anchor point is a different The user plane anchor point between access systems; the SAE anchor point is the user plane anchor point between the 3GPP access system and the non-3GPP system in SAE. The SAE anchor and the 3GPP anchor are collectively referred to as the Inter AS Anchor ("IASA" for short). The non-roaming architecture of the evolved network in TR23.882 is shown in Figure 16, and the roaming architecture of the evolved network in TR23.882 is shown in Figures 17 and 18 respectively, and Figure 17 is the roaming architecture of the SGi interface (Home Routed) from the home network Schematic diagram, Figure 18 is a schematic diagram of the roaming architecture of the SGi interface (Local Breakout) directly from the 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 starts up and registers with the network to obtain services provided by the network), it will establish a bearer connection with the network. In order to realize the user's "always online" function, so that the user can initiate services quickly, this bearer connection is called the default bearer. The process when the UE attaches to the network is shown in Figure 1, which includes the process of establishing a default bearer.

In step 101, the UE sends an attach request to the MME, and the message will carry the identity of the UE (temporary identity is preferred: Packet Temporary Mobile Subscriber Identity (P-TMSI) for short). Under normal circumstances, a permanent identifier is used: International Mobile Subscriber Identity (International Mobile Subscriber Identity, referred to as "IMSI")), the core network uses this identifier to identify the UE and complete the authentication and UE attachment process. At the same time, the message will also carry the access point name (Access Point Name, referred to as "APN"), etc.

Next, in step 102, the MME judges 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, in steps 103 to 106, the MME initiates a location update to the Home Subscriber Server ("HSS"), registers with the HSS that the current MME entity is the serving MME of the UE, and requests user subscription data. HSS inserts user subscription data into MME. The MME returns to the HSS that the user subscription data is inserted successfully. The HSS returns a location update confirmation message to the MME.

Next, from step 107 to step 110, the MME sends a create bearer request message to the UPE, carrying the APN and user plane key (UP key) and so on. The UPE selects an IASA according to the APN, and sends a route update/bearer establishment request message to the selected IASA. IASA interacts with the Policy and Charging Rules Function (Policy and Charging Rules Function, referred to as "PCRF") to determine the policy and charging control (Policy and Charging Control, referred to as "PCC") rules used by the default bearer, In this process, the policy and charging enforcement function (Policy and Charging Enforcement Function, referred to as "PCEF") is located on IASA. The IASA sends a route update response/bearer response message to the UPE, and the UPE sends a bearer response message to the MME.

Next, in step 111 to step 113, the MME sends a radio bearer establishment request message to the eNB (evolved base station node). A radio resource control (Radio Resource Control, "RRC") signaling connection is established between the eNB and the UE. The eNB sends a radio bearer response message to the MME. Since it is not yet determined whether the radio bearer is established when attaching or when there is data transmission, it is indicated by a dotted line.

Next, in step 114, the MME sends a bearer confirmation message to the UPE. In step 115 and step 116, the MME sends an attach accept message to the UE. The UE sends an attach complete message to the MME.

The PCC involved in the above process is introduced below. PCC is a unified control and charging policy architecture, as shown in Figure 2. This architecture is applicable to various IP-CANs (IP Connected Access Networks). In this architecture, the application function (Application Function, referred to as "AF") provides the required relevant parameters to the PCRF. The role of the PCRF is to generate PCC rules based on these parameters and send them to the PCEF. The role of the PCEF is to execute the PCC rules. . PCC rules can be divided into two types: dynamic generation and pre-configuration: dynamically generated PCC rules are dynamically generated by PCRF and sent to PCEF through the Gx interface, and activated by PCRF; pre-configured PCC rules are directly pre-configured in PCEF and can be generated by PCRF or Activated by PCEF according to operator policy. For different IP-CANs, 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. Among them, Figures 19 and 20 are non-roaming network architectures. In Figure 20, there may be a service SAE gateway and a packet data network (Packet Data Network, referred to as "PDN") SAE gateway that are put together as shown in Figure 19. S5 interface; Figure 21 is a schematic diagram of the evolution network roaming architecture from the home network to the SGi interface, and the thick solid line is the public land mobile network (PublicLand Mobile Network, referred to as "PLMN") of the home network and the PLMN of the roaming network. . In addition, the roaming architecture including the PCC has not yet been determined, so whether the S9 interface exists between the H-PCRF (home PCRF) and the V-PCRF (the 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. Among them, FIG. 22 is a non-roaming network architecture; FIG. 23 is a schematic diagram of an evolved network roaming architecture where an SGi interface is sent from a home network.

In Figure 19-23, the service SAE gateway is equivalent to the UPE and 3GPP anchor point in TR23.882, and the PDN SAE gateway is equivalent to the SAE anchor point.

The inventors of the present invention have found that if the network side needs to generate a PCC rule for establishing a default bearer for the UE every time it attaches to the network, it will increase the burden of establishing the default bearer for the UE to a certain extent. The processing time affects the speed with which the UE initiates services. Moreover, since the types of services operated by the network are limited, if a default bearer with different PCC rules is established for each UE, unnecessary complexity will be added to the system.

Contents of the invention

The main technical problem to be solved by the embodiment of the present invention is to provide a wireless network default bearer establishment method and its system, so that the processing process when establishing the default bearer can be accelerated.

In order to solve the above technical problems, the embodiment of the present invention provides a method for establishing a wireless network default bearer, which includes the following steps:

During the UE attach process, one of the default PCC rules pre-configured on the network side is selected, and the policy and charging enforcement function PCEF establishes a corresponding default bearer for the UE according to the selected default PCC rule.

The embodiment of the present invention also provides a wireless network default bearer establishment system, including:

A storage module, configured to store default PCC rules preconfigured on the network side;

A selection module, configured to select a default PCC rule from the default PCC rules stored in the storage module during the UE attach process;

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

Compared with the prior art, the embodiment of the present invention has the main difference and its effects in that:

During the attach process of the UE, 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 rules are pre-configured, there is no need to generate a rule for each UE. When establishing a default bearer for a UE, it is only necessary to select one of the limited configured rules, so that the processing The workload is relatively small, and the processing process is relatively fast, which reduces the delay in setting up the default bearer.

Description of drawings

FIG. 1 is a flowchart of a UE attaching to an SAE network in the prior art;

Fig. 2 is a schematic diagram of a PCC framework in the prior art;

FIG. 3 is a flowchart of a method for establishing a wireless network default bearer according to a first embodiment of the present invention;

4 is a flowchart of a method for establishing a default bearer in a wireless network according to a third embodiment of the present invention;

5 is a flowchart of a method for establishing a wireless network default bearer according to a fifth embodiment of the present invention;

6 is a flow chart of a method for establishing a wireless network default bearer according to a sixth embodiment of the present invention;

7 is a flow chart of a method for establishing a wireless network default bearer according to a seventh embodiment of the present invention;

FIG. 8 is a flowchart of a method for establishing a wireless network default bearer according to the ninth embodiment of the present invention;

FIG. 9 is a flow chart of a method for establishing a wireless network default bearer according to the tenth embodiment of the present invention;

FIG. 10 is a flowchart of a method for establishing a wireless network default bearer according to an eleventh embodiment of the present invention;

11 is a flow chart of V-PCEF interacting with H-PCRF through V-PCRF in the method for establishing a wireless network default bearer according to the fourteenth embodiment of the present invention;

12 is a flow chart of interaction between the V-service SAE gateway and the H-PDN SAE gateway in the wireless network default bearer establishment method according to the fourteenth embodiment of the present invention;

FIG. 13 is a flow chart of a method for establishing a wireless network default bearer according to the twelfth embodiment of the present invention;

14 is a flow chart of a method for establishing a wireless network default bearer according to the thirteenth embodiment of the present invention;

FIG. 15 is a schematic structural diagram of a system for establishing a wireless network default bearer according to a sixteenth embodiment of the present invention;

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

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

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

FIG. 19 is a first schematic diagram of a non-roaming architecture of an evolved network in TS23.401-V030 in the prior art;

FIG. 20 is a second schematic diagram of the non-roaming architecture of the evolved network in TS23.401-V030 in the prior art;

FIG. 21 is a schematic diagram of the roaming architecture of the SGi interface from the home network in the evolved network in the prior art TS23.401-V030;

FIG. 22 is a schematic diagram of a non-roaming architecture of an evolved network in TS23.402-V030 in the prior art;

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

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

Fig. 25 is a flowchart of a method for establishing a wireless network default bearer according to the fifteenth embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention clearer, the following will further describe the implementation of the present invention in detail in conjunction with the accompanying drawings.

In each embodiment of the present invention, the network side classifies default bearers in advance, and divides them into N types of default bearers (N≥1), and each type of default bearer corresponds to a preconfigured default bearer used in the default bearer establishment process The PCC rule is referred to as "default PCC rule" for short in the present invention. Except for IP multimedia core network subsystem signaling, most of the services running in the network are not Guaranteed BitRate ("GBR") services and services controlled by operators, and PCRF does not have much control over these services Capability, therefore, instead of dynamically generated PCC rules in the PCRF, pre-configured default PCC rules can be used. That is to say, dividing UE default bearers into N categories can also be regarded as dividing different UEs into N categories, and UEs of different categories correspond to a pre-configured default PCC rule and enjoy services of different categories.

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 will become more complicated; if all UEs use the same default bearer with PCC rules, that is, N is equal to 1, It is not user-friendly and lacks flexibility, because each user may customize different services according to needs, thereby paying different fees and enjoying different levels of services. Therefore, the preferred value of N is between 1 and the number of UEs, so as to provide corresponding personalized services for UEs of different levels without losing flexibility, and effectively reduce the cost of default PCC rules stored on the network side. quantity. Moreover, it ensures that the number of pre-configured default PCC rules is limited, further speeding up the process of establishing a default bearer for the UE.

There are many bases for classifying UE default bearers. For example, it can be carried out according to the operator's policy. The specific classification methods are as follows:

(1) Classify default bearers in advance according to tariff standards, and those with high tariffs can enjoy high-level services;

(2) Classify the default bearers in advance according to the business model or service model, for example, which packages the user has customized;

(3) Classify the default bearer in advance according to the user level of the contract, for example, divide the user into common user, gold user, platinum user, etc. according to the accumulated consumption amount of the user or the length of usage time.

For a roaming UE, according to the preconfigured default PCC rule corresponding to the default bearer category of the UE in the home location, a predetermined mapping mechanism can be used to obtain the preconfigured default PCC rule of the UE in the roaming location, so as to determine the The default bearer category of the UE in the roaming network; or, the default PCC rule of the UE in the roaming region can be obtained according to the roaming agreement between the roaming network and the home network, so as to determine the default bearer category of the UE in the roaming network; or , the default PCC rule of the UE in the roaming area can also be obtained from the policy of the roaming network operator, so as to determine the default bearer category of the UE in the roaming network.

However, in future standard progress, for 3GPP access, the PCEF function may 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 evolved packet data gateway (evolved Packet Data Gateway, referred to as "ePDG"), but each embodiment of the present invention is described by taking the PCEF function located in the PDN SAE gateway as an example.

The first embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, the default PCC rules or their identification numbers corresponding to different types of UEs are stored in the general database as the subscription data of the UEs, such as HSS, Subscription Profile Repository (Subscription Profile Repository, referred to as "SPR") or authentication, authorization and accounting server (Authentication Authorization and Accounting Server, referred to as "AAA"), etc., the network side selects the default PCC rule according to the subscription data of the UE. In this implementation mode, the general database is the HSS, and the default PCC rules are pre-configured in the PCEF as an example for illustration. The specific process is shown in FIG. 3 .

In step 301, the UE sends an attach request to the MME, and the message will carry the identity of the UE (the temporary identity P-TMSI is preferred, and the permanent identity IMSI is used if there is no P-TMSI), and the core network identifies the UE through the identity and Complete the authentication and UE attach process.

Next, enter step 302, where the MME judges whether it has an available authentication vector for the UE, and if not, triggers a two-way authentication process between the UE and the network (shown as a dotted line in the figure, indicating that the process is optional).

Next, in step 303, the MME initiates a location update to the HSS, registers with the HSS that the current MME entity is the serving MME of the UE, and requests user subscription data.

Next, enter step 304, the HSS provides the user subscription data to the MME. Since the identification numbers of the default PCC rules corresponding to different types of UEs are stored in the HSS as the subscription data of the UE, the HSS provides the MME with the identification number (ID) of the default PCC rules of the UE included in the user subscription data . That is to say, the MME can query the identification number of the UE's default PCC rule. Since this embodiment adopts the piggyback method, steps 303 and 304 implement the functions of updating location and requesting user subscription data, which are equivalent to steps 103 to 106 in FIG. 1 .

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

Then, enter step 306, the serving SAE gateway sends a routing update/bearer request message to the PDN SAE gateway, and the message carries the queried identification number of the default PCC rule of the UE. Since each default PCC rule is pre-configured in the PCEF in the PDN SAE gateway, the PCEF in the PDN SAE gateway can activate the corresponding PCC rule for the UE according to the identification number, and establish the serving SAE gateway and PDN in this step Wired bearer between SAE gateways. Since there is no need to send the rule content to the PCEF, it is only necessary to send the rule identifier, which reduces the traffic between different network entities, thereby saving system resources and speeding up the bearer establishment process.

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

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

Next, enter step 309, the MME sends a radio bearer establishment request message to the eNB.

Next, enter step 310, establish a radio bearer between the eNB and the UE.

Next, enter step 311, where the eNB sends a radio bearer response message to the MME.

Next, enter step 312, the MME sends a bearer confirmation message to the serving SAE gateway.

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

Next, enter step 314, if the core network allocates a new P-TMSI for the UE, the UE sends an attach completion message to the MME.

It is not difficult to find that in this embodiment, since the default PCC rules are pre-configured, there is no need to generate a rule for each UE. When establishing a default bearer for a UE, only a few configured Only one of the rules can be selected, so that the processing workload is relatively small, the processing process is relatively fast, and the delay in establishing the default bearer is reduced.

The second embodiment of the present invention relates to a method for establishing a default bearer in a wireless network. This embodiment is substantially the same as the first embodiment, the difference being that in the first embodiment, each default PCC rule is pre-configured in the PCEF, and 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 received default PCC rules, and the HSS records the default PCC rules sent to the PCEF to determine whether the default PCC rules of the currently attached UE have been If so, send the identification number of the default PCC rule of the UE to the PCEF, and the PCEF activates the corresponding PCC rule according to the identification number, and establishes a default bearer for the UE (similar to the first embodiment same process). If the UE's default PCC rule has not been sent to the PCEF, the UE's 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 Next, in step 304, the user subscription data provided by the HSS to the MME must include the default PCC rule of the UE, not the identification number of the default PCC rule. In steps 305 and 306, the MME sends the service SAE gateway The create bearer request message of the UE and the routing update/bearer request message sent by the serving SAE gateway to the PDSAE gateway must include the default PCC rule of the UE, not the identification number of the default PCC rule.

Although in this embodiment, the default PCC rules are not pre-configured in the PCEF, since the PCEF saves the received default PCC rules, if the default PCC rules of the currently attached UE have been sent to The PCEF does not need to repeatedly send the rule content to the PCEF, which reduces the traffic between different network entities, thereby saving system resources.

It is worth mentioning that in the first and second embodiments, the general database is HSS as an example for illustration. 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 identification number of each default PCC rule is sent to the PCEF, and the two cases where each default PCC rule is pre-configured in the PCEF and the AAA server are the same as the first and second implementation modes, and will not be repeated here. If the general database is SPR, then the SPR sends the default PCC rule corresponding to the UE or the identification number of the default PCC rule to PCEF through the PCRF on the network side. The two situations are the same as those of the first and second implementation manners respectively, and will not be repeated here.

The third embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, each default PCC rule is pre-configured in the PCEF, and the PCRF on the network side determines the identification number of the default PCC rule. 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, and the message will carry the identity of the UE (the temporary identity P-TMSI is preferred, and the permanent identity IMSI is used if there is no P-TMSI), and the core network identifies the UE through the identity and Complete the authentication and UE attach process.

Next, enter step 402, where the MME judges whether it has an available authentication vector for the UE, and if not, triggers a two-way authentication process between the UE and the network (shown as a dotted line in the figure, indicating that the process is optional).

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

Next, enter step 405, the MME sends a create bearer request message to the serving SAE gateway.

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

Then, enter step 407, carry out signaling interaction between PDN SAE gateway and PCRF, PCRF selects the default PCC rule of this UE according to certain strategy, and returns the identification number of the default PCC rule of selection to PDN SAE gateway; Alternatively, the PDN SAE gateway queries the SPR for the identification number of the UE's default PCC rule, and returns the queried identification number of the default PCC rule to the PDN SAE gateway.

Since each default PCC rule is pre-configured in the PCEF in the PDN SAE gateway, the PCEF in the PDN SAE gateway can activate the corresponding PCC rule for the UE according to the identification number, and establish the serving SAE gateway and PDN SAE in this step Wired bearer between gateways. It can be seen that the PCRF does not need to send the rule content to the PCEF, but only needs to send the rule identifier, which reduces the traffic between different network entities, thus saving system resources.

It should be noted that the information exchanged between PCEF and PCRF may include the following parameters: MME ID (MME identification number), serving 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 user's subscription information and the operator's policy to determine the UE's default PCC rule. If the PCRF can obtain the UE's subscription information through the UE's report, the PCRF does not need to interact with the SPR to obtain the UE's subscription information.

Steps 408 to 415 are completely the same as steps 307 to 314 respectively, and will not be repeated here.

The fourth embodiment of the present invention relates to a method for establishing a wireless network default bearer. This embodiment is roughly the same as the third embodiment, the difference being that in the third embodiment, each default PCC rule is pre-configured in the PCEF, and In this embodiment, each default PCC rule is pre-configured in the PCRF.

Specifically, the PCRF judges whether the currently selected default PCC rule has been sent to the PCEF by recording the default PCC rule sent to the PCEF, and if so, sends the identification number of the selected default PCC rule to The PCEF activates a corresponding PCC rule according to the identification number, and establishes a default bearer for the UE (the process is the same as that of 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, what the PCRF returns to the PDN SAE gateway is the selected default PCC rule, not the identification number of the selected default PCC rule. The PCEF in the PDN SAE gateway needs to save the received default PCC rules.

It can be seen that if the currently selected default PCC rule has been sent to the PCEF before, there is no need to repeatedly send the rule content to the PCEF, which reduces the traffic between different network entities and saves system resources.

It is worth mentioning that in the third and fourth embodiments, if the parameters of the default PCC rule are used as the default parameters, the PCRF can also change the parameters of the selected default PCC rule according to the operator's policy and the subscription information of the UE. Therefore, in step 407, the PCRF also needs to return those PCC parameters that need to be changed to the PDN SAE gateway.

The fifth embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, the network side, according to the UE's Quality of Service (Quality of Service, "QoS") parameters, such as Label, MBR or AMBR, etc., A default PCC rule is selected, and 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 HSS, SPR, MME, PCEF or PCRF. In this embodiment, the default PCC rule is selected according to the Label (the Label is stored in the HSS as the subscription data), and the network entity that selects the default PCC rule is 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 respectively, and will not be repeated here.

In step 504, the HSS provides the user subscription data to the MME, and the provided user subscription data includes the Label subscribed by the UE.

Next, in step 505, the MME sends a bearer creation request message to the serving SAE gateway, and 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, and 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 respectively, and will not be repeated here.

The sixth embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, the network side selects a default PCC rule according to the QoS parameters of the UE, such as Label, MBR or AMBR, and the PCEF selects the default PCC rule according to the selected The default PCC rule establishes a default bearer for the UE, and the network entity that selects the default PCC rule may be HSS, SPR, MME, PCEF or PCRF. In this embodiment, the default PCC rule is selected according to the Label (Label is provided by the PCRF), and the network entity that selects the default PCC rule is PCEF as an example. The default PCC rules are pre-configured in the PCEF. The specific process is shown in Figure 6 shown.

Steps 601 to 606 are completely the same as steps 401 to 406 respectively, and will not be repeated here.

In step 607, the PDN SAE gateway and the PCRF perform signaling interaction, the PCRF determines the Label of the UE and returns it to the PDN SAE gateway, and the PCEF in the PDN SAE gateway selects the identification number of the default PCC rule of the UE accordingly, and activates the corresponding PCC rules, and in this step, establish a wired bearer between the PDN SAE gateway and the serving SAE gateway. Since the Label is a QoS parameter, selecting a default PCC rule according to the Label can enable different types of UEs to enjoy different service qualities.

Steps 608 to 615 are completely the same as steps 408 to 415 respectively, and will not be repeated here.

The seventh embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, during the attach process, the UE sends the identification number of the expected default PCC rule to the network side, and the network side number to select 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, and the message will carry the identity of the UE (the temporary identity P-TMSI is preferred, and the permanent identity IMSI is used if there is no P-TMSI), and the core network identifies the UE through this identity And complete the authentication and UE attach process. At the same time, the message will also carry the identification number of the default PCC rule expected by the UE.

Step 702 and step 703 are completely the same as step 302 and step 303 respectively, and will not be repeated 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 respectively, and will not be repeated here. In this embodiment, there is also no need to send the rule content to the PCEF, only the rule identifier is needed, which reduces 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 in a wireless network. This 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, and In this embodiment, each default PCC rule is pre-configured in the PCRF.

Specifically, the MME sends the identification number of the default PCC rule expected by the UE to the PCEF through the serving SAE gateway, and the PCEF judges whether there is a default PCC rule corresponding to the identification number in the PCEF. The default PCC rule corresponding to the identification number establishes a default bearer for the UE. If it does not exist, the identification number is sent to the PCRF that stores the default PCC rules, and the default PCC rule corresponding to the identification number is requested, and the PCRF After receiving the request, send the corresponding default PCC rule to the PCEF. The PCEF in the PDN SAE gateway needs to save the received default PCC rules.

It can be seen that if the default PCC rule expected by the UE has been sent to the PCEF before, 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 the PCRF to repeatedly send The PCEF sends rule content, which reduces the traffic between different network entities, thereby saving system resources.

The ninth embodiment of the present invention relates to a method for establishing a default bearer in a wireless network. In this embodiment, the network side selects a default PCC rule according to the service category, APN or charging key of the UE, and the PCEF selects the default PCC rule 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 HSS, SPR, MME, PCEF or PCRF. In this embodiment, the network entity that selects the default PCC rule is PCEF as an example for illustration. The service category, APN or charging information is stored in the HSS on the network side as UE subscription data, and each default PCC rule is pre-configured in the PCEF. The specific process is shown in Figure 8.

Steps 801 to 803 are completely the same as steps 301 to 303 respectively, and will not be repeated here.

In step 804, the HSS provides the user subscription data to the MME, and the provided user subscription data includes service category, APN or charging information.

Next, in step 805, the MME sends a bearer creation request message to the serving SAE gateway, and the message carries service category, APN or charging information.

Next, in step 806, the serving SAE gateway sends a routing update/bearer request message to the PDN SAE gateway, and the message carries service category, APN or charging information. The PCEF in the PDN SAE gateway selects the default PCC rule of the UE according to the service category, 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.

Step 807 to step 814 are completely the same as step 307 to step 314 respectively, and will not be repeated here.

The tenth embodiment of the present invention relates to a method for establishing a default bearer in a wireless network. In this embodiment, the network side selects a default PCC rule according to the service category, APN or charging information of the UE, and the PCEF selects the default PCC rule according to the selected default PCC rule. A default bearer is established for the UE. The network entity that selects the default PCC rule may be HSS, SPR, MME, PCEF or PCRF. In this embodiment, the network entity that selects the default PCC rule is PCEF as an example for illustration. The service category, APN or charging information is generated by the PCRF on the network side, and each default PCC rule is pre-configured in the PCEF. The specific process As shown in Figure 9.

Step 901 to step 906 are completely the same as step 401 to step 406 respectively, and will not be repeated here.

In step 907, signaling interaction is performed between the PDN SAE gateway and the PCRF, and the PCRF generates the service category, APN or charging information of the UE according to a certain strategy, or queries the service category, APN or charging information of the UE to the SPR, and Return to the PDN SAE gateway, based on which the PCEF in the PDN SAE gateway selects the identification number of the UE's default PCC rule, 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 respectively, and will not be repeated here.

The eleventh embodiment of the present invention relates to a method for establishing a wireless network default bearer. In this embodiment, the network side selects a default PCC rule according to the service category, APN or charging information of the UE, and the PCEF selects the default PCC rule according to the selected default PCC rule. The rule establishes a default bearer for the UE. The network entity that selects the default PCC rule may be HSS, SPR, MME, PCEF or PCRF. In this embodiment, the network entity that selects the default PCC rule is PCEF as an example. The service category, APN or charging information is provided by the UE, that is, the UE attaches the UE's service category, APN Or the charging information is sent to the MME on the network side, and each default PCC rule is 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, and the message will carry the identity of the UE (the temporary identity P-TMSI is preferred, and the permanent identity IMSI is used if there is no P-TMSI), and the core network identifies the UE through the identity And complete the authentication and UE attach process. At the same time, the message will also carry the service category, APN or charging information of the UE.

Step 1002 and step 1003 are completely the same as step 302 and step 303 respectively, and will not be repeated here.

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

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

Next, in step 1006, the serving SAE gateway sends a routing update/bearer request message to the PDN SAE gateway, and the message carries the service category, 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 category, 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 will not be repeated here.

The twelfth embodiment of the present invention relates to a method for establishing a wireless network default bearer. Applicable to the scenario where the UE accesses a non-3GPP network. In this embodiment, a mobility management protocol of Proxy Mobile IP (PMIP for short) is adopted in the non-3GPP network, and the specific process is shown in FIG. 13 .

In step 1301, when the UE is attached to a non-3GPP network, the UE will initiate an Internet Key Exchange Protocol Version 2 (Internet Key Exchange Protocol Version 2, referred to as "IKEv2") tunnel establishment process. The address of the evolved Packet Data Gateway ("ePDG" for short) can be pre-configured or queried through the domain name service system (DOMAINNAME SYSTEM, "DNS" for short), and then the UE is authenticated.

During the establishment of the 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 can be notified by the HSS/AAA to the ePDG during access authentication or service authentication, or the UE can report the address itself when attaching, but these methods are not limited. The address of the PDN SAE gateway can also be stored in the network entity on the source network side (such as MME, HSS), and the address of the PDN SAE gateway is notified to the ePDG or UE during the handover preparation process. For example, the ePDG is notified through the interface between the MME and the ePDG; for example, the UE is notified during the handover preparation, or the UE is directly notified during the SAE network attachment process of the UE. In this step, the UE can obtain the address of the ePDG in the following ways:

(1) During the access authentication process, the UE determines the address of the ePDG and PDN SAE gateway by the HSS/AAA through the reported parameters (such as APN, 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 (Home Agents, referred to as "HA"), similar to the case of multiple PDN SAE gateways, different HAs handle different services. At this time, after the UE accesses a non-3GPP network, the UE A service request will be initiated to the new PDN SAE gateway (ie: HA), and the HSS/AAA can determine the addresses of the new ePDG and PDN-GW through 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 ePDG and PDN SAE gateways through the DNS query process;

(3) During the handover preparation process, the source network entity (such as MME, HSS) notifies the UE of the addresses of the ePDG and PDN SAE gateways that access the network.

Next, in step 1302, the ePDG sends a proxy binding message to the PDN SAE gateway, and the PDN SAE gateway 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 perform security authentication on this 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 proxy binding message, that is, according to the proxy binding message For the parameters carried in the message, one is selected from the default PCC rules pre-configured on the network side. The parameters in the proxy binding message can be reported by the UE, or obtained from the network side entity during the authentication process. The index PCC rule that can be displayed by explicitly carrying the identification number of the default PCC rule in the proxy binding message (as notified to the UE during authentication in step 1301), or other parameters (such as APN, network address identification Multiple parameters such as NAI, or a combination of multiple parameters) to index related PCC rules, and the indexed PCC rule is the default PCC rule selected for the UE. The PCEF activates the indexed default PCC rule, 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 establishment request to the PCRF, and the PCRF sends the relevant default PCC rules to the PCEF. Specifically, after receiving the proxy binding message, the PCEF reports a user plane establishment request to the PCRF. The request message includes parameters such as NAI for identifying the user and Access RAT (access radio technology), and requests the UE's Default PCC rule. 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 they may also be implemented in the same physical entity), and request relevant information from the SPR, such as the Subscription data of the UE, the identification number of the PCC rule or the PCC rule, etc. 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, default PCC rules are pre-configured in the PCEF, but the PCRF needs to send the identification number of the default PCC rule selected for the UE to the PCEF to activate the default PCC rule. Specifically, there are two situations:

A. The identification number of each default PCC rule is preconfigured in the SPR, and the PCRF obtains the identification number of the default PCC rule of the UE through interaction 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 through the user subscription information exchanged with the SPR, and the selected 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, PCRF may also pass the QoS Profile required for this service to PCEF. Also in this step, ePDG carries the QoS profile parameter required by this service in the agent binding message sent (for example, by extending the PMIP registration message, the required QoS profile parameter is passed to PCEF). The ePDG can obtain the QoSprofile parameter from the HSS/AAA during access authentication, or the UE can report the parameter during the attach.

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

Then, in step 1304, after the agent is bound successfully, the IPSec tunnel is established.

Next, in step 1305, the ePDG sends the final IKEv2 information to the UE, and the information includes the IP address allocated for the UE and so on.

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

The thirteenth embodiment of the present invention relates to a method for establishing a default bearer in a wireless network. This embodiment is roughly the same as the twelfth embodiment. The difference is that in the twelfth embodiment, PMIP mobility In this embodiment, the mobility management protocol of Client Mobile IP (Client Mobile IP, referred to as "CMIP") version 6 is adopted in the non-3GPP network, and the specific process is shown in FIG. 14 .

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

During the establishment of the 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 can be notified by the HSS/AAA to the ePDG during access authentication or service authentication, or the UE can report the address itself when attaching, but these methods are not limited. The address of the PDN SAE gateway can also be stored in the network entity on the source network side (such as MME, HSS), and the address of the PDN SAE gateway is notified to the ePDG or UE during the handover preparation process. For example, the ePDG is notified through the interface between the MME and the ePDG; for example, the UE is notified during the handover preparation, or the UE is directly notified during the SAE network attachment process of the UE. In this step, the UE can obtain the address of the ePDG in the following ways:

(1) During the access authentication process, the UE determines the address of the ePDG and PDN SAE gateway by the HSS/AAA through the reported parameters (such as APN, 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, similar to the case of multiple PDN SAE gateways, different HAs handle different services. At this time, after the UE accesses a non-3GPP network, the UE will send the new PDN SAE gateway (ie: HA) Initiating a service request, the HSS/AAA can determine the address of the new ePDG and PDN-GW through some parameters (such as: APN, network address identifier NAI). These parameters can be carried in the MIP registration request message, but are not limited to this form.

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

(3) During the handover preparation process, the source network entity (such as MME, HSS) notifies the UE of the addresses of the ePDG and PDN SAE gateways that access the network.

Next, in step 1402, the ePDG sends the final IKEv2 information to the UE, and the information includes the IP address allocated for the UE and so on.

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 the subsequent binding information is safe. In the process of establishing the security association, the QoS profile parameter 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 perform security authentication on this 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 binding update message received, that is, according to the binding update message For the parameters carried in , select one from the default PCC rules preconfigured on the network side. The index PCC rule that can be displayed by explicitly carrying the identification number of the default PCC rule in the binding update message (as notified to the UE during authentication in step 1401), or other parameters (such as APN, network address identification) can also be used Multiple parameters such as NAI, or a combination of multiple parameters) to index related PCC rules, and the indexed PCC rule is the default PCC rule selected for the UE. The PCEF activates the indexed default PCC rule, 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 establishment request to the PCRF, and the PCRF sends the relevant default PCC rules to the PCEF.

Specifically, after receiving the binding update message, the PCEF reports a user plane establishment request to the PCRF. The request message includes parameters such as NAI for identifying the user and Access RAT (access radio technology), and requests the UE's Default PCC rule. 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 they may also be implemented in the same physical entity), and request relevant information from the SPR, such as the Subscription data of the UE, the identification number of the PCC rule or the PCC rule, etc. 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, default PCC rules are pre-configured on the PCEF, but the PCRF needs to send the identification number of the default PCC rule selected for the UE to the PCEF to activate the default PCC rule. Specifically, there are two situations:

A. The identification number of each default PCC rule is preconfigured in the SPR, and the PCRF obtains the identification number of the default PCC rule of the UE through interaction 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 through the user subscription information exchanged with the SPR, and the selected 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, PCRF may also pass the QoS Profile required for this service to PCEF. Also in this step, the ePDG intercepts the UE registration message, and adds the QoS profile parameter required for this service in the sent binding update message (for example, by extending the MIP registration message, the required QoS profile parameter is passed to PCEF). ePDG can obtain QoS profile parameters from HSS/AAA during access authentication. The UE can also carry the QoS parameters of this service in the binding message, for example, report the parameters to the PDN SAE GW through the extension of registration messages such as MIPv4, MIPv6, and DS-MIP;

Next, in step 1406, the PDN SAE gateway assigns an IP address to the UE, and sends a binding confirmation message to the UE to establish connectivity between the UE and the IP of the PDN SAE gateway

The fourteenth embodiment of the present invention relates to a method for establishing a default bearer in a wireless network. On the basis of the foregoing embodiments, this embodiment adds the situation that the UE is in a roaming network.

Since 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 home network and/or the roaming network will select a default PCC rule for the UE, and the PCEF will establish a default bearer for the UE according to the selected default PCC rule. Depending on the specific circumstances, the default PCC rule selected for the UE may be the default PCC rule of the UE in the home network, or the default PCC rule selected for the UE in the roaming network.

Specifically, in the roaming scenario, whether to select the default PCC rule for the UE in the roaming network is related to whether the roaming network has the PCEF function. If the roaming network has the PCEF function, it must be selected for the UE in the roaming network. PCC rules, otherwise, it is determined whether to select a default PCC rule for the UE in the roaming network according to the specific situation, generally not required. For the case where the default PCC rule in the roaming network does not need to be selected for the UE, the default PCC rule selected by the home network can be directly used to establish a default bearer, and the default PCC rule can be selected in the above implementation manner. The following will focus on the situation where a default PCC rule needs to be selected for the UE in a roaming network.

When it is necessary to select the default PCC rule for the UE in the roaming network, the roaming network and/or the home network can determine the default PCC rule for the UE in the roaming network according to the operator policy and/or the roaming agreement. Refer to the default PCC rule of the UE in the home network or its identification number; or, map the default PCC rule of the UE in the home network 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's policy and/or roaming agreement, the default PCC rule in the roaming network can be selected for the roaming UE in one of the following ways:

(1) During the attach process, the UE sends the expected default PCC rule identification number to the roaming network by carrying the identification number of the default PCC rule in the attach message, and identifies whether the carried default PCC rule identification number is assigned by the home network or roaming If it is assigned by the home network, the roaming network needs to convert it into the corresponding default PCC rule identification number of the roaming network according to the operator's policy and/or roaming agreement. The PCEF of the roaming network activates a 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 in the HSS as subscription data, the identification number of the default PCC rule of the home network can be obtained through the user subscription data request/provide message, and according to the operator's policy And/or the roaming agreement converts it into the identification number of the corresponding default PCC rule of the roaming network (the entity that completes the conversion of the identification number can be HSS, V-PCEF, H/V-PCRF, etc.).

(3) If the UE's default PCC rule is selected according to QoS (such as Label, subscribed QoS parameters, etc.), service category, APN or charging information, and the above parameters exist in the HSS in the form of subscription data, the user can The subscription data request/provide message obtains the above parameters, and the roaming network uses these parameters to select the corresponding default PCC rule in the roaming network according to the operator's policy and/or roaming agreement.

(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 can be obtained through the PCC rule request/provide message, and the The roaming network converts it into the identification number of the corresponding default PCC rule of the roaming network according to the operator's policy and/or the roaming agreement.

(5) If the default PCC rule is selected according to QoS, service category, APN or charging information, and the above parameters are provided by H-PCRF, the above parameters can be obtained through the PCC rule request/provide message, and these parameters can be used by the roaming network Select the corresponding default PCC rule in the roaming network according to the operator's policy and/or roaming agreement.

It should be noted that if the above method of 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, a predetermined mapping can be used The 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 can be located in the home network or the roaming network, or it can be determined by the home network and the roaming network through PCC negotiation. Finally, the V-ID of the roaming network is obtained. In a specific implementation, it may also be considered to divide the default PCC rules in the roaming network into two categories, namely: local default PCC rules for home users and roaming default PCC rules for roaming users.

In the roaming scenario, if the roaming network framework is adopted with the SGi interface from the roaming network, 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) (at this time, the - there is an S9 interface between the PCRF and the H-PCRF), the corresponding flow chart is shown in FIG. 11 . In this scenario, since the PCEF must be located in the roaming network, a default PCC rule in the roaming network needs to be selected for the UE. It should be noted that V-PCRF is drawn as a dotted line in this figure, indicating that there is a possibility that V-PCRF does not participate in this process, that is, there is an interface directly connected to the V-PDN SAE gateway (the PDN SAE gateway of the roaming network) H-PCRF.

In the roaming scenario, if the roaming network framework is adopted with the SGi interface from the home network, the service SAE gateway of the roaming network needs to interact with the H-PDN SAE gateway (the PDNSAE gateway of the home network) through the S8 interface. The corresponding process is shown in the figure 12 shown. In this scenario, it is necessary to decide whether to select the default PCC rule for the UE in the roaming network according to the specific situation. If the PCEF function does not exist in the roaming network, for example, the PCEF function only exists on the H-PDN SAE gateway, it is generally not required. Select the default PCC rule for the UE in the roaming network; if there is a PCEF function in the roaming network, for example, the serving SAE gateway of the roaming network has the PCEF function, it is definitely necessary to select the default PCC rule for the UE in the roaming network.

It can be seen that, in this embodiment, the roaming network can also select a default PCC rule for the roaming UE.

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

For example, if a roaming network framework is adopted in which the SGi interface is provided from the roaming network, the specific process of establishing a dedicated bearer in the roaming network is shown in Figure 24. In step 2401a, the H-PCRF applies the PCC rules related to this service (i.e. 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 deliver the relevant PCC rules to the PDN SAE gateway. Steps 2402 to 2409 are to initiate a normal network-side triggered bearer establishment process, which is the same as the prior art, and will not be repeated here. In step 2410a, the PDN SAE gateway confirms the response message of the relevant PCC rules to the V-PCRF, and in step 2410b, the V-PCRF responds to the H-PCRF with the response message of the PCC rules. Wherein, the entity that completes the mapping may be located in the home network or in the roaming network, or it may be determined by the home network and the roaming network through PCC negotiation.

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

In step 2501, the attach request message initiated by the UE is first sent to the eNB through RRC signaling.

Next, in step 2502, the eNB selects an appropriate MME according to the parameters (such as P-TMSI) carried in the attach request message of the UE, 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 with the serving SAE gateway, routing metrics, load link status and other information.

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

Steps 2504 to 2517 are completely the same as steps 902 to 915 respectively, and will not be repeated here.

It is worth mentioning that the selection of the serving SAE gateway by the eNB may also occur when the eNB selects the serving SAE gateway during Tracking Area Update ("TAU"). This mainly occurs in the scenario where the MME/UPE pool is crossed, or when a network exception occurs and the network needs to be operated and maintained.

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

The sixteenth embodiment of the present invention relates to a system for establishing a wireless network default bearer, as shown in FIG. During the process, a default PCC rule is selected from the default PCC rules stored in the storage module; the establishment module is used to establish a corresponding default bearer for the UE according to the default PCC rule selected by the selection module. Each pre-configured default PCC rule corresponds to one type of default bearer. It can be seen that when establishing a default bearer for a UE, it is only necessary to select one of the limited configured rules, so that the processing workload is relatively small, the processing process is relatively fast, and the default bearer is reduced. the setup delay.

Wherein, the selection module selects the default PCC rule in one of the following ways: selects the default PCC rule according to the information in the subscription data of the UE, selects the default PCC rule according to the default PCC rule generated by PCRF or the identification number of the default PCC rule . Select the default PCC rule according to the QoS parameter, service category, APN or charging information of the UE, or select the default PCC rule according to the identification number of the desired default PCC rule reported by the UE during the attach process. Therefore, this embodiment can be implemented flexibly.

If the UE is in a roaming network, depending on the specific circumstances, the default PCC rule selected by the selection module for the UE may be the default PCC rule of the UE in the home network; it may also be the default PCC rule selected for the UE in the roaming network. The default PCC rules in . Specifically, the UE's default PCC rule in the home network can be mapped to the default PCC rule in the roaming network according to one of the following methods:

(1) The roaming network and/or the home network determine the default PCC rule of the UE in the roaming network according to the operator policy and/or the roaming agreement, and may need to refer to the default PCC rule of the UE in the home network;

(2) Map the default PCC rule of the UE in the home network to the default PCC rule in the roaming network according to a predetermined mapping mechanism.

It can be seen that, in this embodiment, the roaming network can also select a default PCC rule for the roaming UE.

The system of this embodiment may further include a judging module for judging whether the default PCC rule selected by the selection module already exists in the establishment module. If the judging module judges that the default PCC rule selected by the selection module already exists in the building module, then by sending the identification number of the default PCC rule to the building module, the default PCC rule selected by the building module is notified; if judged The module determines that the default PCC rule selected by the selection module does not exist in the establishment module, and then sends the selected default PCC rule to the establishment module, and the establishment module saves the default PCC rule. It avoids repeatedly sending rule content to the PCEF, reduces communication traffic between different network entities, and thus saves system resources.

It should be noted that each module in this embodiment is a logic module, and in practical applications, there may be various physical implementation manners.

To sum up, in the embodiment of the present invention, the network side pre-configures at least one default PCC rule, and classifies the default bearers in advance, and each type of default bearer corresponds to a pre-configured default PCC rule. 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 rules are pre-configured, there is no need to generate a rule for each UE. When establishing a default bearer for a UE, it is only necessary to select one of the limited configured rules, so that the processing The workload is relatively small, and the processing process is relatively fast, which reduces the delay in setting up the default bearer. Moreover, by classifying default bearers in advance, the number of preconfigured default PCC rules is controlled within a limited range, further speeding up the process of establishing default bearers for UEs.

The network side can pre-classify the default bearers according to tariff standards, business models, service models, and subscribed user levels. While ensuring that the number of pre-configured default PCC rules is limited, it can flexibly provide services for different levels of users. Provide different personalized services.

If the default PCC rule is pre-configured in PCEF, the network entity that selects the default PCC rule does not need to send the rule content to PCEF, but only needs to send the rule identifier, which reduces the communication traffic between different network entities and saves system time. resource.

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

The network side can select the default PCC rule in various ways, such as selection according to subscription data or selection according to QoS parameters, so that the embodiment of the present invention can be implemented flexibly.

If the UE is in a roaming network, the network side can select a default PCC rule for the UE according to different circumstances. The selected default PCC rule may be the default PCC rule of the UE in the home network; Default PCC rules for UE in roaming network. This enables the roaming network to also select a default PCC rule for the roaming UE.

Although the present invention has been illustrated and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the present invention. The spirit and scope of the invention.

Claims (24)

1. A method for establishing a default bearer of a wireless network is characterized by comprising the following steps:

in the attachment process of User Equipment (UE), one of default Policy and Charging Control (PCC) rules preconfigured by a network side is selected, and a Policy and Charging Enforcement Function (PCEF) establishes a corresponding default bearer for the UE according to the selected 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 default load in advance, and each type of default load corresponds to a default PCC rule pre-configured by the network side.

3. The method of claim 2, wherein the network side classifies the default bearer in advance according to one of the following manners or any combination thereof:

classifying the default bearer in advance according to a charge standard;

classifying the default bearer in advance according to a business model or a service model;

and classifying the default load in advance according to the signed user level.

4. The method according to claim 1, wherein one of the default PCC rules preconfigured on the network side is selected as follows:

the UE corresponds to one default PCC rule, and the default PCC rule of the UE or the identification number of the default PCC rule is used as subscription data of the UE and is stored in a general database of a network side;

and selecting one from default PCC rules preconfigured by the network side according to the subscription data of the UE.

5. The method of claim 4, wherein the generic database is a Home Subscriber Server (HSS);

if the default PCC rules are preconfigured in the PCEF, a Mobility Management Entity (MME) at a network side inquires an identification number of the default PCC rule corresponding to the UE from the HSS and sends the inquired identification number to the PCEF;

if the default PCC rules are pre-configured in the HSS, the HSS sends the default PCC rules or the identification numbers thereof corresponding to the UE to the PCEF through an MME;

or, the general database is an authentication, authorization and accounting AAA server, and the AAA server sends the default PCC rule corresponding to the UE or the identification number of the default PCC rule to the PCEF;

or, the general database is a subscription specification database SPR, and the SPR sends the default PCC rule corresponding to the UE or the identification number of the default PCC rule to the PCEF through a PCRF of a network side.

6. The method of claim 1, wherein during the UE attach procedure, a Policy and Charging Rules Function (PCRF) on the network side selects a preconfigured default PCC rule and sends the selection result to the PCEF.

7. The wireless network default bearer establishment method of claim 6,

and the PCRF selects the default PCC rules according to a preset strategy or an SPR of a query network side.

8. The wireless network default bearer establishment method of claim 6,

if the default PCC rules are pre-configured in the PCEF, the PCRF sends the identification number of the selected default PCC rule to the PCEF, and the PCEF establishes a default bearer for the UE according to the default PCC rule corresponding to the identification number;

if the default PCC rules are pre-configured in the PCRF, the PCRF sends the selected default PCC rules or the identification numbers of the default PCC rules to the PCEF, and the PCEF establishes default load bearing for the UE according to the received default PCC rules or the default PCC rules corresponding to the received identification numbers.

9. The method according to claim 1, wherein one of the default PCC rules preconfigured on the network side is selected as follows:

selecting one of default PCC rules preconfigured by the network side according to the QoS requirement, the service type, the APN (access point name) or the charging information of the UE;

10. the wireless network default bearer setup method according to claim 9,

selecting a network side entity of the default PCC rule as one of: HSS, SPR, MME, PCEF and PCRF.

11. The method of claim 9, wherein the service class, APN or charging information is obtained by one of the following methods:

the service type, the APN or the charging information is stored on a network side as subscription data of the UE;

generating the service category, the APN or the charging information by the PCRF of the network side;

and the UE sends the service type, the APN or the charging information of the UE to the network side in the attachment process.

12. The method according to claim 1, wherein the UE sends an identification number of an expected default PCC rule to the network side during an attach procedure, and the network side selects the corresponding default PCC rule according to the received identification number.

13. The method according to claim 12, wherein if the default PCC rules are preconfigured in the PCEF, the network entity that receives the identification number of the default PCC rule desired by the UE sends the identification number to the PCEF, and the PCEF establishes the default bearer for the UE according to the default PCC rule corresponding to the identification number;

if the default PCC rules are pre-configured in the PCRF, the network entity receiving the identification number of the default PCC rules expected by the UE sends the identification number to the PCEF, and if the default PCC rules corresponding to the identification number do not exist in the PCEF, the network entity requests the PCRF for the default PCC rules corresponding to the identification number.

14. The wireless network default bearer establishment method of claim 1,

in the attaching process of the UE, if the network to which the UE is attached is a non-third generation partnership project (non-3 GPP) network, the network side selects the default PCC rule when processing the binding message in the attaching process of the UE.

15. The wireless network default bearer setup method according to claim 14,

when receiving the binding message, the PCEF selects one of default PCC rules preconfigured by the network side according to parameters carried in the binding message; or,

when receiving the binding message, the PCEF requests a PCRF for default PCC rules of the UE, the PCRF selects one of the default PCC rules preconfigured by the network side through interaction with the SPR, and notifies the PCEF of the selected default PCC rule; or,

the default PCC rules are pre-configured in the PCEF, the PCEF informs the PCRF when receiving the binding message, the PCRF selects one of the default PCC rules pre-configured on the network side, and sends the identification number of the selected default PCC rule to the PCEF.

16. The wireless network default bearer setup method according to any of claims 1 to 15, wherein if the UE is in a roaming network, a default PCC rule is selected for the UE by a home network and/or a roaming network; the PCEF establishes a default bearer for the UE according to the selected default PCC rule;

the default PCC rule selected for the UE is the default PCC rule of the UE in the home network; or, a default PCC rule in the roaming network selected for the UE.

17. The method of claim 16, wherein the default PCC rule in the roaming network selected for the UE is determined according to one of the following:

determining a default PCC rule of the UE in a roaming network according to an operator policy and/or a roaming agreement;

and mapping the default PCC rule of the UE in the home network into the default PCC rule in the roaming network according to a preset mapping mechanism.

18. The method for establishing a default bearer of a wireless network according to any one of claims 1 to 15, further comprising the steps of:

and when the network side is in an abnormal condition or cannot select the default PCC rule, the network side selects a default PCC rule for the UE according to an operator strategy and establishes a corresponding default bearer for the UE according to the selected default PCC rule.

19. A wireless network default bearer establishment system, comprising:

the storage module is used for storing each default PCC rule pre-configured by the network side;

a selecting module, configured to select a default PCC rule from the default PCC rules stored in the storage module in an UE attach process;

and the establishing module is used for establishing corresponding default load bearing for the UE according to the default PCC rule selected by the selecting module.

20. The system for establishing a default bearer in a wireless network according to claim 19, wherein the preconfigured default PCC rules respectively correspond to a class of default bearers.

It is the bearer correspondence rule, but not the rule correspondence bearer, which can be described as follows: the network side classifies default load in advance, and each type of default load corresponds to a default PCC rule pre-configured by the network side.

21. The wireless network default bearer setup system of claim 19, wherein the selection module selects the default PCC rule by one of:

selecting the default PCC rule according to information in subscription data of the UE;

selecting the default PCC rule according to the default PCC rule generated by the PCRF or the identification number of the default PCC rule;

selecting the default PCC rule according to the service quality parameter, the service type, the APN or the charging information of the UE;

and selecting the default PCC rule according to the identification number of the expected default PCC rule reported by the UE in the attachment process.

22. The system of claim 19, wherein if the UE is in a roaming network, the selection module selects the default PCC rule for the UE, i.e., the default PCC rule for the UE in the home network; or, a default PCC rule in the roaming network selected for the UE.

23. The wireless network default bearer setup system of claim 22, wherein the default PCC rule in the roaming network selected for the UE is determined according to one of the following:

determining a default PCC rule of the UE in a roaming network according to an operator policy and/or a roaming agreement;

and mapping the default PCC rule of the UE in the home network into the default PCC rule in the roaming network according to a preset mapping mechanism.

24. The system according to any of claims 19 to 23, further comprising a determining module configured to determine whether the default PCC rule selected by the selecting module already exists in the establishing module;

if the judging module judges that the default PCC rule selected by the selecting module exists in the establishing module, the establishing module is informed of the selected default PCC rule by sending the identification number of the default PCC rule to the establishing module;

and if the judging module judges that the default PCC rule selected by the selecting module does not exist in the establishing module, the selected default PCC rule is sent to the establishing module, and the establishing module stores the default PCC rule.

Images