WO2013107240A1

WO2013107240A1 - Wireless access capability reporting method, base station and policy control method and system

Info

Publication number: WO2013107240A1
Application number: PCT/CN2012/086973
Authority: WO
Inventors: 梁爽; 朱春晖; 谢峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2012-01-20
Filing date: 2012-12-20
Publication date: 2013-07-25
Also published as: CN103220721A; CN103220721B

Abstract

A wireless access capability reporting method comprises: a base station reporting wireless access capability information thereof to a mobility management unit. The present invention can achieve policy control based on the wireless access capability of the base station and achieve offload control under various access capabilities.

Description

Radio access capability reporting method and base station, policy control method and system

Technical field

The present invention relates to the field of mobile communications, and in particular, to a radio access capability reporting method, a base station, and a policy control method and system.

Background technique

In order to maintain the competitiveness of the third generation mobile communication system in the field of communication, to provide users with faster, less delayed, more personalized mobile communication services, while reducing operators' operating costs, 3GPP (3rd Generation Partnership) Project, 3rd Generation Partnership Project) The Standards Working Group is working on the Evolved Packet System (EPS).

In recent years, the influx of large amounts of large data services has caused the operators who originally deployed 3GPP networks to feel a lot of expansion pressure. The increasing free air interface transmission rate of WLAN (Wireless Local Area Network) technology has attracted 3GPP networks. At the attention of operators, operators hope to expand the air interface capacity with the spectrum of the WLAN and ensure the user experience on this basis. Currently, WLAN accesses the 3GPP core network as an independent radio access technology, which causes 3GPP network operators to deploy additional network elements to support WLAN access, thus requiring additional operating costs for operation and maintenance. Therefore, considering the integration of LTE and WLAN, it can not only increase the wireless processing capacity, but also guarantee the requirements of QoS (Quality of Service), mobility, security and energy saving for user services. One of the LTE and WLAN convergence modes is accepted by the operator, namely: LTE as the primary access, the access control and authentication authentication of the terminal are all completed through LTE access; WLAN as the slave access, can expand the air interface bandwidth , to reduce the LTE load. Figure 1 shows the architecture of this deployment.

As shown in Figure 1, the entire EPS system is divided into two parts: a wireless access network and a core network. In the core network, a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), and a policy are included. Policy and Charging Rule Function (PCRF), Serving Gateway (S-GW), Packet Data Gateway (PDN Gateway, P-GW for short), and Packet Data Network (Packet Data Network) , packet data network), common base station, joint base station. Detailed below Each part of the function:

The home subscriber server is a permanent storage location for the subscriber's subscription data, and is located in the home network to which the subscriber subscribes;

The mobility management entity is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging. Management functions and bearer management;

The service GPRS support node is a service support point for GERAN and UTRAN users to access the core network. It is similar in function to the mobility management entity and is responsible for user location update, paging management, and bearer management functions.

The service gateway is a gateway of the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function; Responsible for counting the situation in which the user terminal uses the wireless network, and generating the CDR of the terminal using the wireless network, and transmitting the CDR to the charging gateway;

The packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, and packet filtering of the terminal. , policy control and other functions;

The packet data network is an operator's IP service network, which provides IP services to users through the operator's core network;

The policy charging rule function entity is a server responsible for providing rules for charging control, online credit control, threshold control, and quality of service (QoS) policies in an evolved system;

A common base station (NodeB/RNC, Radio Network Control or eNodeB) is mainly responsible for receiving and receiving wireless signals, and communicating with the terminal through the air interface to manage radio resources, resource scheduling, and access control of the air interface;

A joint base station refers to a common base station that integrates the above WLAN access functions. In addition to the functions of a common base station, it can also offload air traffic data to WLAN access, and perform radio resource management and resources for the two access technologies. Scheduling, access control and other functions.

The above service GPRS support node is an upgraded SGSN capable of supporting and serving the gateway. The S4 interface communicates with the mobility management unit using the GTPv2 protocol. For the SGSN supporting the 3G core network, the PS domain network architecture is different from that of Figure 1. At this time, the SGSN and the MME are connected by the Gn interface, and the GTPvl protocol is used for interworking. The SGSN cannot be connected to the serving gateway, and is connected to the Gateway GPRS Support Node (GGSN) through the Gn interface to directly access the packet data network.

In the prior art, the policy charging rule function entity may formulate different charging and QoS policies according to different situations, for example, according to different access technologies, according to location information accessed by the UE, etc., and formulating different policies, and The policies are sent to the corresponding network elements, for example, PGW/GGSN, base station, etc., and these policies are performed by the corresponding network elements. When formulating these policies, the policy charging rule function entity does not consider the capabilities of the wireless network element. This is mainly because the capabilities of the wireless network element are mainly related to the access technology in the prior art, and the ordinary base station can only support An access technology. However, due to the introduction of the joint base station, the access technology and the base station capability are no longer in a one-to-one correspondence. This will result in a policy that is not sufficiently accurate for the policy billing rules functional entity to be fully adapted to this newly introduced architecture. In addition, when the relevant policies are currently formulated for the UE, only the capabilities of the UE itself are considered, and the capabilities of the radio access network element are not considered.

In addition, there is currently no clear definition of how the joint base station decides to offload data to WLAN access.

Summary of the invention

The technical problem to be solved by the present invention is to propose a radio access capability reporting method, a policy control method, a base station, and a system, to implement accurate strategy formulation and execution.

In order to solve the above problem, the present invention provides a radio access capability reporting method, including: The base station reports the radio access capability information of the base station to the mobility management unit.

The foregoing method may also have the following feature: the base station reports the radio access capability information in one or more of the following messages:

A connection request, an initial user equipment message, a configuration information update message, a handover request response, a handover complete message, and a path switch request are established.

The foregoing method may further have the following feature: the radio access capability information includes: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities. The invention also provides a policy control method, comprising:

The mobile management unit receives the radio access capability information reported by the base station accessed by the user equipment, and reports the parameter to the policy charging rule function entity by using the core network gateway, where the parameter includes the wireless access capability information;

The policy charging rule function entity formulates policy information for the user equipment according to the parameter.

The above method may also have the following features, and the parameter further includes information about whether to allow data of the user equipment to be offloaded from a specific radio access network.

The above method may further have the following features, further comprising: the mobility management unit acquiring information about whether to allow data of the user equipment to be offloaded from a specific radio access network from a local configuration or subscription information of the user equipment.

The above method may also have the following features, and further includes:

The policy charging rule function entity sends the policy information to the mobility management unit by using the core network gateway;

The mobility management unit transmits the policy information to the base station.

The above method can also have the following features.

The policy information further includes offload indication information;

The method further includes: determining, by the base station, whether to offload according to the offloading indication information in the policy information, and a offloading manner when offloading.

The above method may also have the following features: the offload indication information is one of the following:

Whether the user equipment allows the information to be diverted;

Whether the bearer of the user equipment allows the offloading information;

Whether the data flow of the user equipment allows the information to be shunted.

The foregoing method may also have the following feature: the mobility management unit reports the parameter to the policy charging rule function entity through the core network gateway in the following situation:

When the radio access capability information of the base station accessed by the user equipment is received for the first time, or when the radio access capability information of the base station accessed by the user equipment changes, or The management unit is the target mobile management unit after the handover of the user equipment, and the radio access capability information of the base station accessed by the user equipment changes before and after the handover.

The above method may also have the following features: the radio access capability information includes: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities.

The present invention further provides a base station, where the base station includes: a capability reporting unit, configured to report radio access capability information of the base station to a mobile management unit.

The foregoing base station may further have the following feature: the capability reporting unit is configured to report the radio access capability information in one or more of the following messages:

The foregoing base station may also have the following features: the radio access capability information includes: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities.

The present invention further provides a policy control system, including a mobility management unit and a policy charging rule function entity, where: the mobility management unit is configured to: receive wireless access capability information reported by a base station accessed by a user equipment, and pass through a core network. The gateway reports the parameter to the policy charging rule function entity, where the parameter includes the wireless access capability information;

The policy charging rule function entity is configured to: formulate policy information for the user equipment according to the parameter.

The above system may also have the following features, and the parameter further includes information on whether to allow data of the user equipment to be offloaded from a specific radio access network.

The above system may also have the following features, the mobility management unit is further configured to: obtain information about whether to allow data of the user equipment to be offloaded from a specific radio access network from a local configuration or subscription information of the user equipment. .

The above system may also have the following features, the policy charging rule function entity is further configured to: send the policy information to the mobility management unit by using the core network gateway;

The mobility management unit is further configured to: send the policy information to the base station. The above system may also have the following features, and further includes a base station;

The policy information includes the offloading indication information;

The base station is configured to: determine whether to offload according to the offloading indication information in the policy information, and the offloading manner when diverting.

The above system may also have the following features: the offloading indication information is one of the following:

Whether the user equipment allows the information to be diverted;

Whether the bearer of the user equipment allows the traffic to be offloaded;

The above system may also have the following features: The mobility management unit is configured to report the parameter to the policy charging rule function entity through the core network gateway in the following cases:

When the radio access capability information of the base station accessed by the user equipment is received for the first time, or when the radio access capability information of the base station accessed by the user equipment changes, or the mobility management unit is The target mobility management unit after the handover of the user equipment, and the radio access capability information of the base station accessed by the user equipment before and after the handover changes.

The above system may also have the following features: the radio access capability information includes: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities.

The invention can implement policy control based on the radio access capability of the base station and shunt control under multiple access capabilities.

BRIEF abstract

1 is a schematic structural diagram of an evolved packet domain system;

2 is a method 1 for implementing base station capability reporting by using the present invention;

FIG. 3 is a second manner of implementing base station capability reporting by using the present invention;

FIG. 4 is a third manner of implementing base station capability reporting by using the present invention;

FIG. 5 is a fourth method for implementing base station capability reporting by using the present invention;

6 is a fifth method for implementing base station capability reporting by using the present invention;

FIG. 7 is a sixth manner of implementing base station capability reporting by using the present invention; FIG. FIG. 8 is a seventh method for realizing base station capability reporting by using the present invention.

Preferred embodiment of the invention

In order to make the objects, the technical solutions and the advantages of the present invention more clearly, the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other. An embodiment of the present invention provides a method for reporting a radio access capability, including:

The base station reports the radio access capability information of the base station to the mobility management unit.

The base station reports the radio access capability information in one or more of the following messages: establishing a connection request, an initial user equipment message, a configuration information update message, a handover request response, a handover complete message, and a path conversion request.

The wireless access capability information includes: whether the base station supports multiple wireless access capabilities, and/or supported wireless access capabilities.

The embodiment of the invention further provides a policy control method, including:

The parameter further includes information about whether to allow data of the user equipment to be offloaded from a specific radio access network.

The mobility management unit obtains, from the local configuration or the subscription information of the user equipment, whether the data of the user equipment is allowed to be offloaded from a specific radio access network.

The method further includes:

The mobility management unit transmits the policy information to the base station. The policy information further includes offload indication information;

The method further includes: determining, by the base station, whether to offload according to the offloading indication information in the policy information, and determining a shunting manner when offloading.

The offloading indication information is one of the following:

Whether the user equipment allows the information to be diverted;

Whether the bearer of the user equipment allows the offloading information;

The mobility management unit passes the parameter to the policy charging rule function entity by using the parameter on the core network gateway in the following situation:

The above base station includes a normal base station and a joint base station.

Hereinafter, the joint base station is not only a general base station integrated with the above WLAN access function, but also a base station integrated with a plurality of radio access functions.

FIG. 2 is a first schematic diagram of implementing base station capability reporting by using the present invention. The present embodiment can be applied to the case where the joint base station of the UTRAN/GERAN accesses the GPRS or the EPC network, or the joint base station of the EUTRAN accesses the EPC network. The mobile management unit accessed for the joint base station of UTRAN/GERAN is the SGSN, and the mobile management unit accessed for the joint base station of EUTRAN is the MME.

Step 201: After the joint base station is started, establish a connection with the mobility management unit. The joint base station sends a connection establishment request message to the mobility management unit, where the radio access capability (also referred to as RAN capability) of the joint base station is carried, which specifically includes: whether to support multiple radio access capabilities, and/or which wireless connections are supported. Ability to enter. For example, LTE and WLAN, LTE, WLAN, and HSPA (High Speed Packet Access). Step 202: After receiving the mobile management unit, locally save the radio access capability information of the joint base station.

Step 203: The mobility management unit sends a connection establishment response message to the joint base station.

For a joint base station supporting multiple access technologies, one or several of the wireless access capabilities can be dynamically turned on or off, and thus the above capabilities may change. If the subsequent capability changes, the mobility management unit is notified through steps 204-206.

Step 204: The joint base station sends a configuration information update notification message to the mobility management unit, where the updated radio access capability information is carried.

Step 205: After receiving the mobile management unit, the updated wireless access capability information is locally saved. Step 206: The mobility management unit sends a configuration information update response message to the joint base station.

FIG. 3 is a second method for realizing base station capability reporting by using the present invention. This embodiment is applicable to the joint base station of the EUTRAN to access the EPC network. At this point the mobility management unit is the MME.

Step 301: The terminal sends an attach request, where the non-access stratum message (ie, the attach request) is included in a radio connection establishment request sent by the terminal to the joint base station.

Step 302: The joint base station includes the received attach request in the initial UE message and sends the request to the mobile management unit. The initial UE message carries the radio access capability information of the joint base station, that is, whether to support multiple radio access capabilities, and/or which radio access capabilities are supported, such as LTE and WLAN, LTE, WLAN, and HSPA.

Step 303: After receiving the mobile management unit, locally save the radio access capability information of the joint base station.

Thereafter, the mobility management unit performs an authentication and authorization process on the UE. After the authentication authorization succeeds, an update location request is sent to the HSS, and the subscription data of the UE is obtained.

In this process, the subscription information of the UE may include an identifier of whether to allow the UE data to be offloaded from a specific RAT (Radio Access Technology). In addition, the process is completely consistent with the prior art and is not mentioned here.

The mobility management unit determines whether the UE is allowed according to the subscription information and/or the local configuration of the UE. Data specific RAT offloading.

Step 304: The mobility management unit selects an appropriate core network gateway according to the APN (Access Point Name) or the location information. In this embodiment, the appropriate service gateway and the data gateway are selected.

The mobility management unit sends a create session request to the data gateway through the serving gateway, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the indication of the UE's data is allowed to be offloaded from the specific RAT, the identifier of the UE, and the like.

The specific RAT is typically a WLAN, but is not limited to WLAN, and may be UTRAN/LTE or the like based on subscription.

Step 305: The data gateway sends an IPCAN session establishment request message to the policy charging rule function entity, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, the identifier of the UE, and the like .

Step 306: The policy charging rule function entity formulates policy information for the UE according to the foregoing parameters, where the policy information includes a QoS and a charging policy.

The policy information further includes the offloading indication information, where the offloading indication information includes: a shunt indication and/or a shunting manner, for example, indicating a splitting granularity. The offload indication information may be, but is not limited to, the following:

1. Whether each UE allows the offloaded information, how to perform the offload is completely determined by the joint base station.

2. Whether the bearer of the UE allows the information of the offload, and the indication based on the bearer may be needed at this time. At this time, there is no special instruction information, and similar indication functions can be accomplished by setting special QoS parameters such as QCI and/or ARP.

For example, the QCI/ARP of a certain bearer is set as follows, QCI == 23, or ARP is set to {can be preempted, non-preemptable, low priority} to determine whether the bearer can be offloaded.

3. Whether the data stream of the UE allows the information to be offloaded, and the data stream of the UE can be identified by a packet filter. Then you may need to set an indication of whether to split the flow for each data stream.

Step 307: The policy charging rule function entity sends an IPCAN session establishment response message to the data gateway, where the policy information is carried. Step 308: The data gateway returns a create session response message to the mobility management unit by using the service gateway, where the policy information is carried.

Step 309: The mobility management unit sends an initial UE context setup request to the joint base station, where the policy information is carried.

Step 310: The joint base station determines, according to the policy information, whether to perform the offloading, and the offloading manner (for example, the splitting granularity).

Step 311: The joint base station reserves radio resources for the UE according to the foregoing policy information, and establishes a radio bearer. When shunting is allowed, the radio resource includes all involved radio resource reservations, such as WLAN access.

Step 312 315, performing the remaining steps of the attaching process, consistent with the prior art, without making a comment.

FIG. 4 is a third method for realizing base station capability reporting by using the present invention. This embodiment can be applied to the case where the joint base station of UTRAN/GERAN accesses the GPRS or EPC network. The mobile management unit accessed for the joint base station of TRAN/GERAN is the SGSN. The process description is based on the access EPC. If the access is GPRS, the message between the SGSN and the data gateway (GGSN) is not a session but a PDP (Packet Data Protocol) context activation message, which is carried in the message. The way of wireless access capability information and policy information is similar.

Step 401: The terminal sends an attach request, where the non-access stratum message (ie, attach request) is included in a radio connection establishment request sent by the terminal to the joint base station.

Step 402: The joint base station includes the received attach request in the initial UE message and sends the request to the mobile management unit. The initial UE message carries its own radio access capability, that is, whether it supports multiple radio access capabilities, and/or which radio access capabilities are supported. For example, LTE and WLAN, LTE, WLAN and HSPA.

Step 403: After receiving the mobile management unit, locally save the radio access capability information of the joint base station.

In this process, the subscription information of the UE may include whether to allow the UE data to be classified from a specific RAT. The identifier of the indication of the stream. In addition, the process is completely consistent with the prior art and is not mentioned here. The mobility management unit determines whether to allow the data of the UE to be offloaded from the specific RAT according to the subscription information and/or the local configuration of the UE.

Steps 404 to 405, the remaining steps of the attaching process are performed, which are consistent with the prior art, and are not described herein.

Step 406: The terminal initiates a PDP context activation request, and the non-access stratum message is brought to the mobility management unit by using the joint base station. In this embodiment, the mobility management unit is an SGSN.

Step 407: The mobility management unit selects an appropriate service gateway and data gateway according to the APN, or location information.

Step 408: The data gateway sends an IPCAN session establishment request message to the policy charging rule function entity, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, the identifier of the UE, and the like .

Step 409: The policy charging rule function entity formulates policy information for the UE according to the foregoing parameters, where the policy information includes: a QoS and a charging policy.

2. Whether the bearer of the UE allows the information of the offloading. At this time, it may be necessary to have a bearer-based indication. At this time, there is no special instruction information, and similar indication functions can be accomplished by setting special QoS parameters such as QCI and/or ARP.

3. Whether the data stream of the UE allows the information to be offloaded, and the data stream of the UE can be identified by a packet filter. Then you may need to set a split for each data stream at this time. Instructions.

Step 410: The policy charging rule function entity sends an IPCAN session establishment response message to the data gateway, where the policy information is carried.

Step 411: The data gateway returns a create session response message to the mobility management unit by using the service gateway, where the policy information is carried.

Step 412: The mobility management unit sends a radio bearer assignment request to the joint base station, where the foregoing policy information is carried.

Step 413: The joint base station performs, according to the offload information in the policy information, whether to perform offloading, and what kind of offload granularity.

Step 414: According to the foregoing policy information, the joint base station reserves radio resources for the UE, and establishes a radio bearer. When shunting is allowed, the radio resource includes all involved radio resource reservations, such as WLAN access.

Step 415 417, the remaining steps of the attach process are performed, which is consistent with the prior art, and is not mentioned.

FIG. 5 is a fourth method for realizing base station capability reporting by using the present invention. The present embodiment can be applied to the case where the joint base station of the UTRAN/GERAN accesses the GPRS or the EPC network, or the joint base station of the EUTRAN accesses the EPC network. The mobile management unit accessed for the joint base station of UTRAN/GERAN is the SGSN, and the mobile management unit accessed for the joint base station of EUTRAN is the MME. The process description takes the access EPC as an example. If the GPRS is accessed through UTRAN/GERAN, the message between the SGSN and the data gateway (GGSN) is not a modify bearer message and an update bearer message but a PDP context modification message and a PDP context update message. The RAN capability information and the policy information carried in the message are similar.

Step 501: The terminal sends a service request message, where the non-access stratum message (ie, the service request message) is included in a wireless connection establishment request sent by the terminal to the joint base station.

Step 502: The joint base station sends the received service request message to the mobile management unit in the initial UE message. The initial UE message carries the radio access capability of the joint base station, that is, whether to support multiple radio access capabilities and/or which radio access capabilities are supported. For example, LTE and WLAN, LTE, WLAN, HSPA, and the like. Step 503: After receiving the initial UE message, the mobility management unit locally saves the radio access capability information of the joint base station.

The mobility management unit determines whether the wireless access capability information changes to determine whether to notify the backend network element. Possible changes include but are not limited to the following:

1. Determine whether the wireless access capability information of the joint base station is saved, and if it is received for the first time, it needs to notify the back-end network element;

2. If the radio access capability information of the joint base station is previously saved and is different from the radio access capability information obtained in the initial UE message, the backend network element needs to be notified.

Step 504: The mobility management unit sends an initial UE context setup request/radio bearer assignment request to the joint base station, where the policy information is carried.

Step 505: At this time, if the radio access capability of the base station changes, the policy sent by the mobility management unit to the joint base station is still based on the policy established by the radio access capability of the previous base station, and the policy is updated in step 514.

Step 506: The joint base station reserves radio resources for the UE according to the foregoing policy information, and establishes a radio bearer. When shunting is allowed, the radio resource includes all involved radio resource reservations, such as WLAN access.

Step 507: The joint base station returns an initial UE context setup response/wireless assignment response to the mobility management unit.

Step 508: The mobility management unit sends a modify bearer request to the data gateway by using the serving gateway, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, and the identifier of the UE is used.

Step 509: The data gateway sends an IPCAN session modification request message to the policy charging rule function entity, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, the identifier of the UE, and the like .

Step 510: The policy charging rule function entity may formulate policy information for the UE according to the foregoing parameters, including QoS and charging policies. If no new QoS and charging policies are established, the steps after step 513 need not be performed.

If the policy changes, the content of the policy is delivered, and the specific method is the same as that of Figure 3 and Figure 4. Similar.

Step 511: The policy charging rule function entity sends an IPCAN session modification response message to the data gateway, where the policy information is carried.

Step 512: The data gateway returns a modify bearer response message to the mobility management unit through the serving gateway.

Step 513: The data gateway sends an update bearer request message to the mobility management unit by using the serving gateway, where the updated policy information is carried.

Step 514: The mobility management unit sends a radio bearer modification request to the joint base station, where the policy information is carried.

Step 515: The joint base station determines, according to the policy information, whether to perform the offloading, and the offloading manner, for example, the splitting granularity.

Step 516: The joint base station reserves radio resources for the UE according to the foregoing policy information, and establishes a radio bearer. When shunting is allowed, the radio resource includes all involved radio resource reservations, such as WLAN access.

Step 517: The joint base station returns a radio bearer modification response to the mobility management unit. interest. One' , . ^W , , - . ; '

FIG. 6 is a fifth method for realizing base station capability reporting by using the present invention. The present embodiment can be applied to the case where the joint base station of the UTRAN/GERAN accesses the GPRS or the EPC network, or the joint base station of the EUTRAN accesses the EPC network. The mobile management unit accessed for the joint base station of UTRAN/GERAN is the SGSN, and the mobile management unit accessed for the joint base station of EUTRAN is the MME. The process description uses the access EPC as an example.

This process takes the change of the mobility management unit and the service gateway as an example. If the service gateway does not change, the target mobility management unit and the serving gateway modify the bearer message, otherwise, create a session message.

Contents not related to the present invention are omitted in the flowchart, such as location update, authentication, etc. between the mobility management unit and the HSS, and resource release to the source serving gateway. If the GPRS is connected to the GPRS through the UTRAN/GERAN, the message between the SGSN and the data gateway (GGSN) is not a modify bearer message and an update bearer message but a PDP context modification message and a PDP context update message, and the message carries the radio access capability information. And the way the policy information is similar.

Step 601: The terminal sends a location update request, where the non-access stratum message is included in a radio connection establishment request sent by the terminal to the joint base station.

Step 602: The joint base station sends the received location update request to the target mobility management unit in the initial UE message. The initial UE message carries the radio access capability of the joint base station, that is, whether multiple radio access capabilities are supported, and/or which radio access capabilities are supported. For example, LTE and WLAN, LTE, WLAN and HSPA.

Step 603: The target mobility management unit finds the source mobility management unit according to the identifier of the UE, and sends a context request message thereto. It carries the policy information previously formulated for the UE, and the wireless access capability information.

Step 605: The target mobility management unit sends a context response message to the source mobility management unit. Step 606: The target mobility management unit compares the radio access capability in the context response message with the locally stored radio access capability of the joint base station currently accessed by the terminal (ie, the radio access capability in step 602). Whether to notify the backend network element. Possible changes include but are not limited to the following:

1. Determine whether the received context response message includes the radio access capability information of the previously accessed joint base station, if not, and if the radio access capability information of the currently connected joint base station is received in step 602, Need to notify the backend network element;

2. If the step 602 receives the radio access capability information of the currently connected joint base station, and the information obtained in the context response message changes, the backend network element needs to be notified.

Thereafter, the mobility management unit performs an authentication and authorization process on the UE, and after the authentication authorization succeeds,

The HSS sends an update location request and acquires subscription data of the UE.

In this process, the UE's subscription information may include an identifier of whether to allow UE data to be offloaded from a specific RAT. In addition, the process is completely consistent with the prior art and is not mentioned here. Step 607: The target mobility management unit determines, according to the current location information, whether to perform reselection of the serving gateway. In this embodiment, it is assumed to be reselected. The mobility management unit sends a create session request to the serving gateway, where the radio access capability information of the base station currently accessed by the UE is carried, whether the data of the UE is allowed to be offloaded from the specific RAT, and the identifier of the UE is used.

Step 608: The serving gateway sends a modify bearer request to the data gateway, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from a specific RAT, and the identifier of the UE is used.

Step 609: The data gateway sends an IPCAN session modification request message to the policy charging rule function entity, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, the identifier of the UE, and the like .

Step 610: The policy charging rule function entity may formulate policy information for the UE according to the foregoing parameters, including QoS and charging policies. If no new QoS and charging policies are in place, the steps following step 614 need not be performed.

If the policy changes, the method of issuing the policy is similar to the method in Figure 3 and Figure 4. Step 611: The policy charging rule function entity sends an IPCAN session modification response message to the data gateway, where the policy information is carried.

Step 612: The data gateway returns a modify bearer response message to the serving gateway.

Step 613: The service gateway returns a create session response message to the target mobility management unit. Request a message, which carries updated policy information.

Step 615: The target mobility management unit saves the foregoing policy information in the context of the UE. Should be the message.

FIG. 7 is a sixth manner of realizing base station capability reporting by using the present invention. This embodiment can be applied to the case where the joint base station of the UTRAN/GERAN accesses the GPRS or the EPC network, or the joint base station of the EUTRAN accesses the EPC network. For the joint base station of UTRAN/GERAN, the mobile management unit accessed is the SGSN, and the mobile tube accessed for the joint base station of EUTRAN The unit is the MME. The process description uses the access EPC as an example.

Contents not related to the present invention are omitted in the flowchart, such as location update, authentication, etc. between the mobility management unit and the HSS, and resource release to the source service gateway.

If the GPRS is connected to the GPRS through the UTRAN/GERAN, the message between the SGSN and the data gateway (GGSN) is not the modify bearer message and the update bearer message but the PDP context modification message and the PDP context update message, and the RAN capability information carried in the message and The way the strategy information is similar.

Step 701: The source joint base station initiates a handover procedure, and requests the UE to report the measurement report. The source base station selects a suitable target cell for the UE, and sends a handover request to the source mobility management unit. It carries the policy information previously formulated for the UE, and the radio access capability information of the source joint base station.

Step 703: According to location information of the target cell, the target mobility management unit determines whether to perform service gateway reselection, and establishes a forwarding tunnel for forwarding data. This process is not relevant to the present invention and is performed in accordance with the prior art and is not to be construed.

Step 704: The target mobility management unit sends a handover request to the target joint base station, where the policy information is carried. At this time, if the capability of the base station changes, the policy sent by the mobility management unit to the joint base station is still based on the policy formulated by the capabilities of the previous UE base station, and the policy is updated after step 714.

Step 705: The target joint base station completes resource reservation according to the foregoing policy.

Step 706: The target joint base station returns a handover request response message to the target mobility management unit, where the radio access capability information of the target base station is carried.

Step 707: Perform other preparation processes on the source side during the handover process, which are not related to the present invention, and are not described herein.

Step 708: The terminal accesses from the target base station, and sends a handover complete message.

Step 709: The target base station returns a handover complete message to the target mobility management unit, where the radio access capability of the target base station is carried. In step 706 and step 709, an optional step may carry the radio access capability of the target base station. Step 710: The target mobility management unit compares the radio access capability in the context (ie, the radio access capability information received in step 706 or 709) and the radio access capability of the currently accessed base station (ie, received in step 702). Whether the wireless access capability information is consistent, to determine whether to notify the back-end network element. Possible changes include but are not limited to the following:

1. Determine whether the received radio access capability information of the previously connected joint base station is received in the context (ie, whether the radio access capability information of the source joint base station in step 702 is received), if not, and in step 706 or If the wireless access capability information of the current base station is received in 709, the network element of the back end needs to be notified;

2. If the wireless access capability information of the joint base station is received in the previous context, and with the steps

The difference obtained in 706 or 709 needs to be notified to the backend network element.

The target mobility management unit notifies the back-end network element that the network element may be completed in the process, or may be completed after acquiring the subscription data of the UE in the TAU process after the HO. That is, the service gateway and the data gateway are notified by the bearer modification command. After receiving the capability change notification, the data gateway also performs steps 712 to 714, and step 716 721 to complete the modification process.

Step 711: The target mobility management unit sends a modify bearer request to the data gateway by using the serving gateway, where the radio access capability information of the base station currently accessed by the UE is allowed, whether the data of the UE is allowed to be offloaded from the specific RAT, and the identifier of the UE is used.

Steps 712 to 721 are similar to the steps 509 518 in Embodiment 4, and are not mentioned here.

FIG. 8 is a seventh method for realizing base station capability reporting by using the present invention. The present embodiment can be applied to the case where the joint base station of the UTRAN/GERAN accesses the GPRS or the EPC network, or the joint base station of the EUTRAN accesses the EPC network. The mobile management unit accessed for the joint base station of UTRAN/GERAN is the SGSN, and the mobile management unit accessed for the joint base station of EUTRAN is the MME. The process description uses the access EPC as an example.

This process takes the service gateway change as an example. If the service gateway does not change, the mobility management unit and the service gateway modify the bearer message. Otherwise, the session message is created. Contents not related to the present invention are omitted in the flowchart, such as resource release by the mobility management unit to the source service gateway, and the like.

If the GPRS is connected to the GPRS through the UTRAN/GERAN, the message between the SGSN and the data gateway (GGSN) is not a modify bearer message and an update bearer message but a PDP context modification message and a PDP context update message, and the message carries the radio access capability information. And the way the policy information is similar.

Step 801: The resource reservation of the wireless network element is completed, and the UE has switched to the target base station.

Step 802: The target base station sends a path switch request message to the mobility management unit, where the radio access capability of the target base station is carried.

Step 803: The mobility management unit compares the radio access capability in the context (the radio access capability acquired during the UE handover process) and the radio access capability of the base station currently accessed by the UE (the path conversion request message carried in step 802) Whether the wireless access capability is consistent, to determine whether to notify the back-end network element. Possible changes include but are not limited to the following:

1. Determine whether the radio access capability information is received in the context (that is, whether the radio access capability information is obtained during the handover process). If not, and the radio access capability information of the currently connected joint base station is received in step 802, Then need to notify the backend network element;

2. If the wireless access capability is previously saved (that is, the wireless access capability information is obtained during the handover), and is different from the obtained (from the path conversion request message) obtained in step 802, the backend network element needs to be notified. .

The target mobility management unit notifies the back-end network element that the network element may be completed in the process, or may be completed after acquiring the subscription data of the UE in the TAU process after the HO. That is, the service gateway and the data gateway are notified by the bearer modification command. After receiving the capability change notification, the data gateway also performs steps 805 to 807, and step 810 815 to complete the modification process.

Steps 804 to 808 are the same as steps 607 to 613 of Embodiment 5, and are not mentioned here.

Step 809: The mobility management unit sends a path switch response message to the target base station.

Steps 810 to 815 are the same as steps 607 613 of Embodiment 5, and are not mentioned here.

An embodiment of the present invention further provides a base station, including: a capability reporting unit, configured to move The mobile management unit reports the radio access capability information of the base station.

The capability unit is configured to set the radio access capability information on one or more of the following messages:

Embodiments of the present invention also provide a policy control system including a mobility management unit and a policy accounting rule function entity, where:

The mobility management unit is configured to: receive the radio access capability information reported by the base station that is accessed by the user equipment, and report the parameter to the policy charging rule function entity by using the core network gateway, where the parameter includes the radio access capability information;

The mobility management unit is further configured to: obtain information about whether to allow data of the user equipment to be offloaded from a specific radio access network from a local configuration or the subscription information of the user equipment.

The policy charging rule function entity is further configured to: deliver the policy information to the mobility management unit by using the core network gateway;

The mobility management unit is further configured to: send the policy information to the base station.

The policy information includes the offloading indication information;

The base station is configured to: determine whether to offload according to the offloading indication information in the policy information, and determine a shunting manner when diverting.

The offloading indication information is one of the following: Whether the user equipment allows the information to be diverted;

Whether the bearer of the user equipment allows the offloading information;

The mobility management unit is configured to report the parameter to the policy charging rule function entity through the core network gateway in the following cases:

The service gateway, the data gateway, the mobility management unit, and the joint base station in the foregoing embodiment may obtain the foregoing policy information. If the network element needs to notify other network elements of the back end, such as an operation and management system and a charging system, the foregoing policy Information may also be reported to other back-end network elements.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

Claims

Claim

A method for reporting a wireless access capability, comprising:

2. The method according to claim 1, wherein the base station reports radio access capability information in one or more of the following messages:

The method according to claim 1 or 2, wherein the radio access capability information comprises: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities.

4. A policy control method, including:

The method according to claim 4, wherein the parameter further includes information about whether to allow data of the user equipment to be offloaded from a specific radio access network.

The method of claim 5, further comprising: the mobility management unit obtaining, from the local configuration or the subscription information of the user equipment, whether to allow data of the user equipment to be offloaded from a specific radio access network. Information.

7. The method of any of claims 4 to 6, further comprising:

8. The method of claim 7, wherein

The policy information further includes offload indication information;

The method further includes: the base station determining, according to the offloading indication information in the policy information, No diversion, and, when diverting, the way of diversion.

The method according to claim 8, wherein the offload indication information is one of the following: whether the user equipment allows the offloaded information;

Whether the bearer of the user equipment allows the offloading information;

The method of claim 4, wherein the mobility management unit reports the parameter to the policy charging rule function entity through the core network gateway in the following situation:

11. The method according to any one of claims 4 to 6, 10, wherein

12. A base station, comprising:

The capability reporting unit is configured to report the radio access capability information of the base station to the mobility management unit.

The base station according to claim 12, wherein the capability reporting unit is configured to report the radio access capability information in one or more of the following messages:

The base station according to claim 12 or 13, wherein the radio access capability information comprises: whether the base station supports multiple radio access capabilities, and/or supported radio access capabilities.

15. A policy control system, comprising a mobility management unit and a policy charging rule function entity, wherein:

The mobility management unit is configured to: receive the radio access capability information reported by the base station that is accessed by the user equipment, and report the parameter to the policy charging rule function entity by using the core network gateway, where the parameter includes the radio access capability information; The policy charging rule function entity is configured to: formulate policy information for the user equipment according to the parameter.

The system according to claim 15, wherein the parameter further includes information of whether to allow data of the user equipment to be offloaded from a specific radio access network.

The system of claim 16, wherein the mobility management unit is further configured to: obtain, from the local configuration or the subscription information of the user equipment, whether to allow data of the user equipment to be from a specific wireless access Information diverted from the network.

18. The system of any one of claims 15 to 17, wherein

19. The system of claim 18, further comprising a base station;

The policy information includes the offloading indication information;

The system according to claim 19, wherein the offloading indication information is one of the following: whether the user equipment allows the offloaded information;

Whether the bearer of the user equipment allows the offloading information;

The system according to claim 15, wherein the mobility management unit is configured to report the parameter to the policy charging rule function entity through the core network gateway in the following case:

22. The system according to any one of claims 15 to 17, 21, wherein