CN101242568B - A method and system for service quality negotiation in wireless communication network - Google Patents

Abstract

The invention discloses a method and system for negotiating service quality of a wireless communication network, comprising: a user equipment applies for a service to an application function entity; In the request message, identify whether the quality of service required for the service connection of the user equipment is allowed to be negotiated; according to whether the service quality is allowed to be negotiated, establish or reject the service connection between the user equipment and the packet data network. Using the present invention avoids setting up invalid service connections and unfair billing in the process of QoS negotiation; provides a mechanism for QoS negotiation, avoiding that users cannot use services because AF selects a higher QoS for services; The technical method is simple and easy to realize.

Description

A method and system for quality of service negotiation in a wireless communication network

technical field

The invention relates to the field of communication technology, in particular to a method and system for negotiating service quality in a wireless communication network. the

Background technique

At present, data communication has broad development prospects in the field of wireless communication. A typical wireless communication network generally consists of at least one wireless access network and at least one wireless core network. Figure 1 is a schematic structural diagram of a wireless communication network system. As shown in the figure, the wireless access network includes a certain number of base stations (BS, Base Station) and their control devices. The network is used to connect users such as mobile phones and wireless data cards. Equipment (UE, User Equipment). The mobile core network generally includes a mobility management entity (MME, Mobility Management Equipment) and a user plane entity (UPE, User Plane Equipment). The mobility management entity is used to connect to the radio access network, manage user mobility, interact with the base station and user plane entities, and establish user data transmission channels. The user plane entity is used to connect the wireless access network and the packet data network, and forward the user uplink data from the wireless access network to at least one packet data network (for example, the packet data network can be the Internet, the intranet of an enterprise, or other network, etc.) and forward the downlink user data from the packet data network to the wireless access network. In a wireless communication network, the user plane entity and the mobility management entity may be a unified physical node. The user plane entity can place the function of connecting to the wireless access network (user plane access function entity) and the function of connecting to the packet data network (user plane switching function entity) on two physical nodes respectively, and there is a data connection between the two entities . The user plane access function entity can also be located in the same physical node as the mobility management entity. the

The application function entity is used to accept the user's application for service use, and deliver the service information used by the user and the service quality (QoS, Quality of Service) information required by the service to the policy network element (PF, PolicyFunction). The QoS information generally includes service Parameters such as the maximum bandwidth, guaranteed bandwidth, delay, jitter, and bit error rate of the connection. The policy network element decides the QoS required by the service according to the subscription information of the user, and sends the QoS information of the decided service that the user is using to the user plane entity or the mobility management entity. If the policy network element sends the QoS information of the service to the user plane entity, the user plane entity sends the information to the mobility management entity, and the mobility management entity transmits the QoS information to the base station during the process of establishing the user data bearer; if The policy network element sends the QoS information of the service to the mobility management entity, and the mobility management entity transmits the QoS information to the base station and the user plane entity respectively during the process of establishing the user data bearer. the

When a user attaches to the network, it is necessary to establish a communication connection from the user equipment to an application function entity (AF, Application Function) in advance for transmitting signaling messages between the user equipment and the AF. When a user wants to carry out business, it is necessary to establish a network from user equipment to packet data (including various devices that provide the services required by the user, such as Internet servers, streaming media servers, etc., and there are communication connections between these devices and AF) communication connection, the connection passes through the radio access network, the radio core network and the packet data network. Figure 2 is a schematic diagram of the QoS negotiation process, as shown in the figure, the establishment process of the connection is as follows:

Step 201, before establishing a service connection, the user equipment UE needs to apply for a service from the application function entity AF. the

Step 202, after the application function entity accepts the user's service application, it will request the policy network element to establish a service connection between the UE and the packet data network and send the resources and QoS information required by the service to the policy network element PF. the

Step 203, the policy network element can decide the above services according to the user subscription information obtained from the external user subscription database, the user equipment access information registered on the PF by the user equipment when the user equipment accesses the network, and the requirements of the application function entity The resources and QoS required for the connection. the

Step 204, the policy network element requests the user plane entity MME or the mobility management entity UPE to establish the above-mentioned service connection and delivers the resource and QoS information required by the service connection to the user plane entity or the mobility management entity. the

Step 205, the user plane entity or the mobility management entity initiates the establishment of a service connection from the UE to the packet data network, and allocates resources required for the service connection including QoS. the

Step 206, the user plane entity or the mobility management entity requests the base station BS to allocate corresponding radio resources, and provides the base station with required radio resource information and air interface QoS information. the

Step 207, the base station allocates radio resources required by the service connection. the

Step 208, the base station and the user equipment negotiate radio resources required for the service connection. the

Step 209, after the base station and the user equipment successfully negotiate and allocate radio resources, report the success of radio resource allocation to the user plane entity or mobility management entity, and report the negotiated QoS information. the

Step 210, after the establishment of the service connection is completed, the user plane entity or mobility management entity reports the establishment of the connection to the policy entity, and reports the negotiated QoS information. the

Step 211, the policy entity reports to the AF that the service connection is established successfully and reports the negotiated QoS information. the

If the PF, MME/UPE, base station and UE find that the QoS of the service cannot be satisfied, they can choose to refuse to establish the service connection and report to the AF. the

It can be seen from the above implementation that the existing technology has shortcomings in the establishment and removal of services due to the imperfect QoS negotiation mechanism, which cannot meet the actual needs, such as:

1. When QoS degradation occurs during QoS negotiation, abnormal charging will occur. the

2. When there are services that can be used under multiple QoS, existing resources cannot be used for service connection. the

Contents of the invention

The embodiment of the present invention provides a method and system for negotiating service quality of a wireless communication network, which is used to provide a complete QoS negotiation mechanism and solve the actual requirements of establishing and dismantling services related to QoS. the

An embodiment of the present invention provides a quality of service negotiation method for a wireless communication network, in which a user equipment applies for a service to an application function entity;

After the application function entity receives the user service application, it sends a request message to the policy network element to establish a service connection between the user equipment and the packet data network;

Also includes the following steps:

Identify in the request message whether the quality of service required for the service connection of the user equipment is allowed to be negotiated;

The policy network element establishes or rejects the service connection between the user equipment and the packet data network according to the flag of whether the service quality is allowed to be negotiated, and judges whether its service quality capability meets the service quality requirement required by the service requesting the connection.

The embodiment of the present invention also provides a quality of service negotiation system for a wireless communication network, including: user equipment for applying for services from application functional entities; The application function entity of the service connection request message between data networks;

Also includes:

An identification module, configured to identify in the request message whether the quality of service required for the service connection of the user equipment is allowed to be negotiated;

The service connection module is used to identify whether the negotiation is allowed according to the service quality, and after the policy network element judges whether the service quality capability can meet the service quality requirements required by the service requesting connection, establish or reject the user equipment and the packet data network business connection between. the

The beneficial effects of the embodiments of the present invention are as follows:

Abnormal billing will not occur when QoS is degraded during QoS negotiation. When there are services that can be used under multiple QoS, existing resources can be used for service connection. the

Description of drawings

Fig. 1 is a schematic structural diagram of the wireless communication network system described in the background technology;

Fig. 2 is a schematic diagram of the QoS negotiation process described in the background technology;

Figure 3 is a schematic diagram of the implementation process of the service quality negotiation method described in the embodiment of the present invention;

Figure 4 is a schematic diagram of the implementation process in the case where the PF cannot meet the QoS requirements of the service connection when it is marked as not allowing negotiation as described in the embodiment of the present invention;

Figure 5 is a schematic diagram of the implementation process when the MME or UPE cannot meet the QoS requirements of the service connection when the identification is not allowed to negotiate as described in the embodiment of the present invention;

Figure 6 is a schematic diagram of the implementation process in the case where the BS or UE cannot meet the QoS requirements of the service connection when the negotiation is not allowed as described in the embodiment of the present invention;

Figure 7 is a schematic diagram of the implementation process of PF, MME/UPE, BS and UE when the identification is allowed to negotiate as described in the embodiment of the present invention;

Fig. 8 is a schematic structural diagram of the QoS negotiation system in the embodiment of the present invention. the

Detailed ways

Specific embodiments of the present invention will be described below in conjunction with the accompanying drawings. the

Figure 3 is a schematic diagram of the implementation process of the service quality negotiation method. As shown in the figure, the implementation may include the following steps:

Step 301, the user equipment UE applies for a service to the application function entity AF;

Step 302, after receiving the user service application, the application function entity sends a request message to the policy network element PF to establish a service connection between the user equipment and the packet data network;

Step 303, identifying in the request message whether the QoS required for the user equipment service connection allows negotiation;

Step 304, PF judges whether the QoS mark allows negotiation, if the sign is to allow negotiation, then proceed to step 317, if the mark is not to allow negotiation, then proceed to step 305;

Step 305, PF judges whether the QoS capability satisfies the QoS requirements required by the service requesting the connection, if it can be satisfied, then go to step 306, if not satisfied, then go to step 315;

Step 306, the policy network element PF initiates a connection request to the mobile core network;

Step 307, judging whether the QoS capability of the mobile core network meets the QoS requirements, if it can be satisfied, it will go to step 308, if it cannot be satisfied, it will go to step 311;

Step 308, the mobile core network initiates a service connection request to the base station BS;

Step 309, judging whether the wireless resource capability of the base station meets the QoS requirement, if it is satisfied, then proceed to step 310, if not satisfied, then proceed to step 312;

Step 310, the base station negotiates with the user equipment whether the wireless resource meets the QoS requirement, if it is satisfied, it will go to step 330, if it is not satisfied, it will go to step 313;

Step 311, the mobile core network rejects the service connection, and proceeds to step 314;

Step 312, the base station rejects the service connection, and proceeds to step 313;

Step 313, feed back the connection rejection reason message to the mobile core network, and proceed to step 314;

Step 314, feed back the connection rejection reason message to the policy network element, and proceed to step 315;

Step 315, feed back the connection rejection reason message to the application function entity, and proceed to step 316;

Step 316, the application function entity judges whether it is necessary to re-initiate the connection request according to the connection rejection reason message;

Step 317, judging whether the QoS requirement required by the requested connection service meets the QoS requirement, if it can be satisfied, then go to step 319, if not satisfied, then go to step 318;

Step 318, modify the QoS of the service connection requested by the AF to be the QoS allowed by the PF, and turn to step 319;

Step 319, the policy network element PF initiates a connection request to the mobile core network;

Step 320, judging whether the QoS capability of the mobile core network meets the QoS requirements, if it can be satisfied, it will go to step 322, if it cannot be satisfied, it will go to step 321;

Step 321, modify the QoS of the service connection requested by the PF to be the QoS allowed by the mobile core network, and turn to step 322;

Step 322, the mobile core network initiates a service connection request to the base station BS;

Step 323, judging whether the wireless resource capability of the base station meets the QoS requirement, if it can be satisfied, then go to step 325, if not, then go to step 324;

Step 324, modify the QoS of the service connection requested by the mobile core network to be the QoS allowed by the BS, and turn to step 325;

Step 325, the base station negotiates with the user equipment whether the wireless resource meets the QoS requirement, if it is satisfied, then go to step 330, if not, then go to step 326;

Step 326, the base station feeds back the wireless resource QoS capability negotiated between the base station and the user equipment to the mobile core network;

Step 327, the mobile core network feeds back the radio resource QoS capability negotiated between the base station and the user equipment to the policy unit;

Step 328, the policy unit feeds back the wireless resource QoS capability negotiated between the base station and the user equipment to the application functional entity, and then proceeds to step 329;

Step 329, AF accepts the service connection and conducts the service according to the negotiated QoS;

Step 330, establish a service connection. the

During implementation, the QoS capability of the mobile core network can be judged by the MME or UPE. the

When the PF judges whether the QoS capability can meet the QoS required by the requested connection service, the PF can decide and judge the resources required for the above-mentioned service connection according to one or a combination of the user's subscription information, user access information, and service connection requirements and QoS. the

This embodiment is only an example, and there are many ways to implement it. For example, the PF can determine the negotiation identifier, and step 303 can also be implemented before "the PF judges and decides the resources and QoS required for the above-mentioned service connection", that is, If the AF does not decide to negotiate the identity, it can be decided by the PF. Further description will be given below with various embodiments. the

In the embodiment, the services are divided into two types that allow QoS negotiation and those that cannot negotiate QoS. During implementation, the AF or PF identifies the QoS negotiation when requesting to establish a service connection. During implementation, if AF cannot decide whether to negotiate QoS, PF can also decide whether to allow QoS negotiation. If the AF can decide whether to allow QoS negotiation, the PF can also process the QoS negotiation flag. In this embodiment mainly include but not limited to the following:

1. When the QoS negotiation flag is "negotiation not allowed", if the BS, MME/UPE or PF finds that the required QoS cannot be met, the service connection should be directly rejected. the

2. When the QoS negotiation flag is "Negotiation Allowed", if the BS, MME/UPE or PF cannot meet the requested QoS, the service connection will still be established, and the negotiated QoS information in the service connection establishment corresponding message, that is, the BS , QoS acceptable to MME/UPE or PF. the

3. When BS, MME/UPE or PF report the refusal to establish a service connection, they can simultaneously report the QoS information allowed by the current network element BS, MME/UPE and PF and the reasons for refusing to establish a service connection. The AF or PF can decide whether to initiate the service connection again according to the new QoS according to the reported QoS information and the reason for rejecting the service connection, or notify the UE of the reason for rejecting the service connection. the

How to implement the present invention will be further described below. the

Embodiment one

This embodiment describes that the AF requests the PF to establish a service connection, and the QoS identified in the request message is "Negotiation Not Allowed", and the PF makes a decision based on the subscription information of the user and the access information of the user. When the PF finds that the QoS requirements of the service connection cannot be met, it returns to the AF to refuse to establish the service connection, and reports the currently negotiated QoS information to the AF. the

Figure 4 is a schematic diagram of the implementation process when the PF cannot meet the QoS requirements of the service connection when the negotiation is not allowed. As shown in the figure, it includes the following steps:

Step 401, before establishing a service connection, the user equipment UE needs to apply for a service from the application function entity AF. the

Step 402, after the application function entity AF accepts the user's service application, it will request the policy network element to establish a service connection between the UE and the packet data network, and send the resources and QoS information required by the service to the policy network element PF. The QoS negotiation identifier carried in the request message is "Negotiation Not Allowed". the

Step 403 , the policy network element PF decides the resources and QoS required by the service connection according to one or a combination of the user's subscription information, user access information, and service connection requirements. the

Step 404, the policy network element finds that the QoS required for establishing a service connection cannot be met, for example: the data bandwidth required by the service connection is 64kbps, but the bandwidth of the service connection is limited to 16kbps in the user's subscription data. And check that the QoS negotiation flag is "Negotiation Not Allowed", you need to report to AF that you refuse to establish a service connection, and send the QoS information that is currently allowed to use the service, such as: the bandwidth is 16kbps, and the reason why PF refuses to establish a service connection to AF. For example: the signed QoS cannot meet the service requirements. the

The AF decides whether to request to establish a service connection again according to the QoS information reported by the PF, the reason for refusing to establish a service connection, and the QoS required by the service. If the service allows to reduce the QoS, for example: the minimum bandwidth allowed by the service is 16kbps, and the voice quality is degraded at this time, and the reduced QoS is lower than or equal to the QoS reported by the PF, the AF can request to establish a service connection again, and the service connection uses Reduced QoS. In addition, the AF can also record the QoS information of the user terminal reported this time, which can be used as a reference for the QoS of the service connection in the future. the

Example two

What this embodiment describes is that the AF requests the PF to establish a service connection when it is identified that the negotiation is not allowed. The PF decides to allow the establishment of the service connection, and requests the MME or UPE to establish the service connection. If the MME or UPE cannot meet the QoS required for establishing the service connection, it refuses to establish the service connection, and reports the negotiated QoS information to the AF through the PF. the

Figure 5 is a schematic diagram of the implementation process when the MME or UPE cannot meet the QoS requirements of the service connection when the negotiation is not allowed. As shown in the figure, it includes the following steps:

Step 501. Before establishing a service connection, the user equipment UE first applies for a service from the application function entity AF. the

Step 502, after the application function entity AF accepts the user's service application, it requests the policy network element to establish a service connection between the UE and the packet data network, and sends the resource and QoS information required by the service to the policy network element PF. the

Step 503 , the policy network element PF decides the resource and QoS required for the service connection according to one or a combination of the user's subscription information, user access information, and service connection requirements. The policy network element determines that the current resource can establish a service connection and meet the QoS required by the service connection, and the QoS is not allowed to be negotiated. the

Step 504, the policy network element requests the MME or UPE to establish a service connection, and delivers the QoS information required by the service to the MME or UPE. The QoS negotiation identifier carried in the request message is "Negotiation Not Allowed". the

In step 505, the MME or UPE checks whether the QoS required by the service connection can be met according to the service connection establishment request. the

Step 506, MME or UPE finds that local resources or preconfigured local policies cannot meet the QoS required for establishing a service connection, for example: the data bandwidth required by the service connection is 64kbps, but the service connection bandwidth allowed by local resources or the preconfigured local policies If it is 16kbps, etc., and the QoS negotiation flag is checked as "Negotiation Not Allowed", then it is necessary to report to the PF that the business connection is refused to be established, and the QoS information currently allowed for business use, such as: the bandwidth is 16kbps, and the reason for rejecting the business connection, such as : The bandwidth cannot meet the requirements of the service, and it is sent to the PF. the

In step 507, the PF sends the service connection rejection report, the QoS information currently allowed to use the service, and the reason for rejecting the service connection to the AF. the

The AF decides whether to request to establish a service connection again according to the QoS information reported by the PF, the QoS required by the service, and the reason for rejecting the service connection. If the service allows to reduce the QoS, and the reduced QoS is lower than or equal to the QoS reported by the PF, the AF can request to establish the service connection again, and the service connection uses the reduced QoS. In addition, the AF can also record the QoS information of the user terminal reported this time, which can be used as a reference for the QoS of the service connection in the future. the

Embodiment three

The description in this embodiment is similar to that of the first and second embodiments, except that the negotiation is not allowed. The difference is that the network element that refuses the service connection is the BS or the UE. These two network elements also need to carry the QoS information of the allowed access in the report of rejecting the service connection, that is, the negotiated QoS information. the

Figure 6 is a schematic diagram of the implementation process when the BS or UE cannot meet the QoS requirements of the service connection when the negotiation is not allowed. As shown in the figure, it includes the following steps:

In step 601, the user equipment UE applies for a service from the application function entity AF before establishing a service connection. the

Step 602: After the application function entity AF accepts the user's service application, it will request the policy network element to establish a service connection between the UE and the packet data network and send the resources and QoS information required by the service to the policy network element PF. The message carries a QoS negotiation identifier, and the identifier content is "QoS negotiation not allowed". the

Step 603 , the policy network element PF decides the resources and QoS required for the service connection according to one or a combination of the user's subscription information, user access information, and service connection requirements. The policy network element decides that the current resource can establish a service connection and satisfy the QoS required by the service connection. the

Step 604, the policy network element requests the MME or UPE to establish a service connection, and sends the QoS information required by the service to the MME or UPE, and the request message carries the QoS negotiation identifier. the

Step 605, MME or UPE establishes a service connection according to the request, and checks whether the QoS required by the service connection can be satisfied

In step 606, the MME or UPE thinks that the QoS required by the service connection can be satisfied, so it requests the BS to establish and allocate wireless resources, and sends QoS information, and the request message carries the QoS negotiation identifier. the

Step 607, the BS checks whether the current radio resources can meet the requested radio resources. the

Step 608, the BS negotiates with the UE to allocate air interface radio resources. the

If the BS checks in step 607 and finds that the current radio resource cannot satisfy the requested radio resource, the BS can directly reject it, and this step can be omitted. the

Step 609, the BS finds that the current wireless resources cannot meet the QoS required for establishing a service connection during the inspection or negotiation process, for example: the data bandwidth required by the service connection is 64kbps, but insufficient wireless resources can only limit the bandwidth of the service connection to 16kbps , and check that the QoS negotiation flag is "Negotiation Not Allowed", the BS needs to report to the MME or UPE that the wireless resources are insufficient, and the QoS information allowed by the existing wireless resources, for example: the bandwidth is 16kbps, and the wireless network that refuses to be allocated Resource reasons, such as insufficient air interface wireless resources or insufficient bandwidth, etc., are sent to the MME or UPE. the

In step 610, the MME or UPE reports to the PF that the establishment of the service connection is rejected, and reports the information of the allowed QoS and the reasons for rejecting the establishment of the connection to the PF. the

In step 611, the PF sends the service connection rejection report, the allowed QoS information and the reasons for refusing to establish the service connection to the AF. the

The AF decides whether to request the establishment of the service connection again according to the QoS information reported by the PF, the QoS required by the service, and the reasons for refusing to establish the service connection. If the service allows to reduce the QoS, and the reduced QoS is lower than or equal to the QoS reported by the PF, the AF can request to establish the service connection again, and the service connection uses the reduced QoS. In addition, the AF can also record the QoS information of the user terminal reported this time, which can be used as a reference for the QoS of the service connection in the future. the

Embodiment four

This embodiment describes that when the AF requests to establish a service connection, the QoS negotiation flag carried in the request message is "allow negotiation", and the PF, MME/UPE, BS, and UE can first establish a service connection and use the negotiated QoS The information is reported to the AF, and the AF adjusts the service accordingly according to the reported QoS. the

Figure 7 is a schematic diagram of the implementation process of PF, MME/UPE, BS and UE when it is marked as allowing negotiation, as shown in the figure, including the following steps:

Step 701. Before establishing a service connection, the user equipment UE applies for a service from the application function entity AF. the

Step 702: After the application function entity AF accepts the user's service application, it requests the policy network element to establish a service connection between the UE and the packet data network and sends the resources and QoS information required by the service to the policy network element PF. carries the QoS negotiation identifier, and the identifier content is "allow QoS negotiation". the

Step 703 , the policy network element PF decides the resources and QoS required for the service connection according to one or a combination of the user's subscription information, user access information, and service connection requirements. The policy network element decides whether the current resource can meet the QoS required by the service connection. If not, and the QoS negotiation flag is checked as "Negotiation Allowed", it decides the QoS that the current resource can satisfy, that is, the negotiated QoS. the

Step 704, the policy network element requests the MME or UPE to establish a service connection, and sends the QoS required by the service or the negotiated QoS information to the MME or UPE, and the request message carries the QoS negotiation permission identifier. the

In step 705, the MME or UPE establishes a service connection according to the request, and checks whether the QoS required by the service connection can be met. If it cannot be satisfied and QoS is allowed to be negotiated, an appropriate QoS is negotiated based on existing resources. the

In step 706, the MME or UPE requests the BS to set up and allocate radio resources, and sends QoS or negotiated QoS information, and the request message carries a QoS negotiation flag. the

Step 707, the BS checks whether the current radio resource can satisfy the requested radio resource. the

Step 708, the BS negotiates with the UE to allocate air interface radio resources. the

Step 709, the BS finds that the current wireless resources cannot meet the QoS required for establishing a service connection during the inspection or negotiation process, for example: the data bandwidth required by the service connection is 64kbps, but insufficient wireless resources can only limit the bandwidth of the service connection to 16kbps , and check that the QoS negotiation flag is "Negotiation Allowed", the BS needs to report the radio resource allocation response to the MME or UPE, and send the negotiated QoS information, for example, the bandwidth is 16kbps, to the MME or UPE. the

In step 710, the MME or UPE reports the PF service connection establishment response, and reports the negotiated QoS information to the PF. the

In step 711, the PF sends the service connection establishment response and the negotiated QoS information to the AF. the

The AF adjusts the QoS of the service according to the reported service connection establishment response and the negotiated QoS information. the

In specific implementation, it can also be implemented in the following ways:

1. In Embodiment 2 and Embodiment 3, the QoS negotiation identifier can be issued by the AF according to the needs of the business, or can be issued by the PF according to the needs of the business QoS policy decision. At the same time, the PF can modify the QoS negotiation identifier issued by the AF according to the needs of business policy decisions. the

2. In Embodiments 1 to 3, if there is no sign of QoS negotiation and the network resources cannot meet the QoS requirements of the service connection, each network element can decide whether to refuse to establish a service connection in a default manner. Each network element includes PF, MME/UPE, BS and UE. Each network element can carry the allowed QoS information and/or the reason for refusing to establish a service connection in the report of refusal to establish a service connection. The reason can be that the network resources cannot meet the requirements of service QoS, and can be specific to the fact that it cannot meet the requirements of QoS. Which parameter or parameters. These parameters can include maximum bandwidth, guaranteed bandwidth, average bandwidth, peak bandwidth, transmitted data type, delay, jitter, data packet size, priority, bit error rate, etc.; the reason for rejection can also be the establishment of user service subscription restrictions The business connection or the region where the user resides restricts the establishment of the service connection; in addition, the reason for the refusal may also include which network element refuses to establish the service connection. the

Three, in embodiment one to embodiment four, if there is QoS negotiation mark, and when network resource can't satisfy the QoS requirement of service connection, each network element can decide to simply accept or refuse to set up service connection according to the instruction of this sign. The report of refusing to establish a service connection may also carry only the allowed QoS information or the reason for refusing to establish a service connection, or even neither. the

4. In Embodiment 1 to Embodiment 3, AF can decide whether to modify the QoS of the service and initiate the service connection again according to the allowed QoS information carried in the report of refusal to establish the service connection and/or the reason for refusing to establish the service connection . For example:

(1) If the reason for the refusal is that the user's subscription is restricted or the region is restricted, there is no need to re-establish the service connection. the

(2) If the PF or MME/UPE refuses to establish a service connection due to insufficient network resources, and the QoS that the network resources can satisfy is greater than or equal to the minimum or lower QoS required by the service, the AF can use the minimum required by the service Or lower QoS to request to establish a service connection again. the

(3) If the BS or UE refuses to establish a service connection due to insufficient air interface radio resources, and the QoS that the air interface radio resources can satisfy is much greater than the minimum or lower QoS required by the service. Then the AF can use the lowest or lower QoS required by the service to request to establish the service connection again. the

5. In Embodiment 3, if the base station or the UE does not support identifying the QoS negotiation identifier, the base station can allocate wireless air interface resources by itself, or the base station and the UE negotiate to allocate wireless resources, and the wireless air interface The resource information is reported to the MME/UPE, and the MME/UPE can compare the reported allocated wireless air interface resources with the QoS. If the allocated wireless air interface resources cannot meet the QoS requirements, and the QoS negotiation flag is "QoS negotiation not allowed", then The MME/UPE may refuse to establish a service connection, and notify the base station to release the allocated air interface radio resource information. the

6. In Embodiments 2 to 4, both the MME/UPE and the PF can modify or directly transparently transmit the negotiated QoS information in the service connection establishment response or the QoS information carried in the service connection rejection report and the rejection of the connection establishment report. reason. the

The embodiment of the present invention also provides a QoS negotiation system for a wireless communication network. The specific implementation of the negotiation system will be described below with reference to the accompanying drawings. the

Figure 8 is a schematic diagram of the structure of the quality of service negotiation system. As shown in the figure, the negotiation system includes: user equipment, base station, mobile core network, application function entity, policy network element, identification module, service connection module, and each module unit in the system The working relationship is as follows:

The user equipment applies for a service from the application functional entity; the application functional entity sends a request message for establishing a service connection between the user equipment and the packet data network to the policy network element after receiving the user service application; the identification module identifies the user equipment in the request message Whether the quality of service required by the service connection is allowed to be negotiated; the service connection module establishes or rejects the service connection between the user equipment and the packet data network according to the sign of whether the service quality is allowed to be negotiated. the

The identification module can be located in the application function entity or the policy network element. the

The service connection module can establish or reject the service connection between the user equipment and the packet data network after the policy network element judges whether the quality of service is allowed to be negotiated. The policy network element can base on the subscription information, user access One or a combination of information and service connection requirements is used to judge the quality of service required by the service requesting the connection. the

The business connection module includes a first judging unit, a first sending unit, a first feedback unit, a second judging unit, a second sending unit, a second feedback unit, a third judging unit, a negotiating unit, a third feedback unit, a fourth Judgment unit, fourth feedback unit, business connection unit, business rejection unit, wherein:

A service connection unit, configured to establish a service connection between the user equipment and the packet data network after being triggered by the first judgment unit;

Rejecting the service unit, used to reject the service connection between the user equipment and the packet data network after being triggered by the first judging unit, the second judging unit, the third judging unit, and the fourth judging unit;

The first sending unit is used to send a service connection request message and/or a first negotiation message containing the quality of service requirements that the policy network element can satisfy to the mobile core network;

The first judging unit is used to trigger related units after judging according to the quality of service identifier and the quality of service requirements that the policy network element can meet;

The first feedback unit is used to feed back the reason message for rejecting the connection and the negotiated QoS information when the rejecting service unit is triggered;

The second judging unit is used to trigger related units after judging according to the quality of service identifier, the first negotiation message and the quality of service capability of the mobile core network;

The second sending unit sends a service connection request message to the base station, and/or a second negotiation message containing the service quality requirements that the policy network element and the mobile core network can satisfy;

The second feedback unit is used to feed back a second negotiation message when the second sending unit is triggered; when the reject service unit is triggered, feed back a connection rejection reason message;

The third judging unit is configured to trigger related units after judging according to the second negotiation message and the wireless resource capability;

A negotiating unit, configured to negotiate according to the second negotiation message, the radio resource capability of the base station, and/or the radio resources of the base station and the user equipment;

The third feedback unit is used to feed back the quality of service capability message that the base station can provide according to the second negotiation message and the radio resource capability after the negotiation unit is triggered; when the service rejection unit is triggered, feed back a connection rejection reason message ;

The fourth judging unit is used to trigger related units after judging the negotiation of radio resources with the user equipment according to the second negotiation message, the radio resource capability of the base station;

The fourth feedback unit is configured to feed back the quality of service capability message that the base station can provide after negotiation with the user equipment according to the second negotiation message, the radio resource capability of the base station, or Connection refused reason message. the

In the business connection module, each unit can be implemented as follows:

1), when the first judging unit judges that the service quality identifier is to allow negotiation, after the policy network element can meet the service quality requirements required for the requested connection service, trigger the service connection unit to establish a service connection;

After the policy network element cannot meet the service quality requirements required for the requested connection service, trigger the first sending unit to send the service connection request message and the first negotiation message to the mobile core network to the core network;

When the first judging unit judges that the service quality identifier is not allowed to be negotiated, and the policy network element cannot meet the service quality requirements required for the requested connection service, it triggers the reject service unit to reject the service connection;

When the quality of service identifier does not allow negotiation, after the policy network element judges that the required quality of service requirement for the connection service can meet the quality of service requirement, the first sending unit is triggered to send a service connection request message to the mobile core network. the

The first feedback unit feeds back a connection rejection reason message and negotiated QoS information after the service rejection unit is triggered. the

2), when the second judging unit judges that the quality of service identifier is to allow negotiation, and when the mobile core network can meet the quality of service requirements, trigger the business connection of the service connection unit; when judging that the quality of service requirements cannot be met, trigger the second sending unit to send the message Send a service connection request message and a second negotiation message to the base station;

When the second judging unit judges that the quality of service identifier does not allow negotiation, and the mobile core network cannot meet the quality of service requirements, it triggers the rejection service unit to reject the service connection; when the mobile core network can meet the quality of service requirements, it triggers the second sending unit to send The base station sends a service connection request message. the

The second feedback unit feeds back a second negotiation message when the second sending unit is triggered; and feeds back a connection rejection reason message when the service rejection unit is triggered. the

3), when the third judging unit judges that the quality of service identifier is to allow negotiation, and the base station can meet the quality of service requirements, trigger the service connection unit to establish a service connection; when the base station cannot meet the quality of service requirements, trigger the negotiation unit according to the second negotiation message , The radio resource capability of the base station negotiates with the user equipment on radio resources;

When the third judging unit judges that the quality of service identifier does not allow negotiation, and the base station cannot meet the quality of service requirements, it triggers the rejection service unit to reject the service connection; when the base station can meet the quality of service requirements, it triggers the negotiation unit according to the radio Resources are negotiated. the

When the negotiation unit is triggered, the third feedback unit feeds back the QoS capability message that the base station can provide according to the second negotiation message and the radio resource capability; when the service rejection unit is triggered, it feeds back a connection rejection reason message. the

4), when the fourth judging unit judges that the quality of service identifier is allowed to negotiate, and the QoS capability of the base station and the user can meet the quality of service requirements, trigger the service connection unit to establish a service connection;

When the fourth judging unit judges that the quality of service identification does not allow negotiation, and the QoS capability of the base station and the user cannot meet the quality of service requirements, it triggers the rejection service unit to reject the service connection; when it can meet the quality of service requirements, it triggers the service connection unit to establish a service connect. the

The fourth feedback unit, when the quality of service capability of the base station and the user cannot meet the quality of service requirement, feeds back the quality of service capability message that the base station can provide after negotiation with the user equipment according to the second negotiation message, the radio resource capability of the base station, or the reason for rejecting the connection information. the

In a preferred implementation, a retransmission request module may also be included, which is used to determine whether to trigger the retransmission request according to one or a combination of the QoS-related connection rejection reason message, the second negotiation message, the radio resource capability of the base station, and the negotiation result between the base station and the user equipment. The application function entity initiates a service connection request again. the

It can be seen from the above embodiments that in the prior art, when QoS degradation occurs during the QoS negotiation process, the QoS of the established service connection cannot meet the service transmission requirements. If this happens, it is necessary to initiate a process of disconnecting the service connection from the AF and terminate the service. However, once the service connection is established, the user service will be charged. For the user, this kind of expense should obviously be inappropriate; and in this embodiment, because in the negotiation process, only when each network element that establishes the service connection can meet the QoS requirement of service establishment, the service may be established , so there will be no unfair billing due to QoS degradation during the negotiation process;

Meanwhile, in the prior art, when the higher QoS required by the service connection cannot be satisfied, the service connection will be rejected, which will cause the user to be unable to use the service. And some services can be used under a variety of QoS. For example, voice services can run at different bandwidths: 8kbps, 16kbps, 64kbps, etc. Different bandwidths will bring different voice quality, so the rejection of this type of service will Reduce user satisfaction; and in this embodiment, because there is a negotiation flag in the service establishment process, when the service negotiation mark is negotiable, each network element in the service establishment process will negotiate with itself and other network elements Only the QoS requirements that can be met will establish a business connection, so it not only guarantees the problem of unfair billing caused by QoS degradation in the negotiation process, but also solves the problem when the higher QoS required by the business connection cannot be met. , the service connection will be rejected and the user satisfaction will decrease. the

Therefore, using the embodiment of the present invention can avoid establishing invalid service connections and unfair charging in the process of QoS negotiation. At the same time, it provides a QoS negotiation mechanism to avoid the user being unable to use the service because the AF selects a higher QoS for the service. The technical method implemented at the same time is simple and easy to use. the

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations. the

Claims (25)

1. A quality of service negotiation method for a wireless communication network, in which a user equipment applies for a service to an application function entity; The application function entity sends a request message for establishing a service connection between the user equipment and the packet data network to the policy network element after receiving the user service application; It is characterized in that it also includes the following steps: Identify in the request message whether the service quality required for the service connection of the user equipment is allowed to be negotiated; The policy network element establishes or rejects the service connection between the user equipment and the packet data network according to the flag of whether the service quality is allowed to be negotiated, and judges whether its service quality capability meets the service quality requirement required by the service requesting the connection. 2. The method according to claim 1, wherein the application function entity or the policy network element identifies in the request message whether the QoS required by the service connection of the user equipment is allowed to be negotiated. 3. The method according to claim 1, wherein the policy network element judges the quality of service required for the requested connection service according to one or a combination of subscription information, user access information, and service connection requirements . 4. The method according to claim 1, wherein said establishing or rejecting a service connection comprises the steps of: When the quality of service identifier is to allow negotiation, after the policy network element judges that its quality of service capability can meet the quality of service requirements required by the requested connection service, establish a service connection between the user equipment and the packet data network; When the quality of service identifier is to allow negotiation, after the policy network element judges that its quality of service capability cannot meet the quality of service requirements required for the requested connection service, it sends a service connection request message to the mobile core network, and sends a message containing the policy network element a first negotiation message of a satisfyable quality of service requirement to the mobile core network; When the quality of service identifier does not allow negotiation, rejecting the service connection between the user equipment and the packet data network after the policy network element judges that its service quality capability cannot meet the service quality requirements required by the requested connection service; When the quality of service identifier is not allowed to be negotiated, the policy network element sends a service connection request message to the mobile core network after judging that its service quality capability can meet the service quality requirements required by the request connection service. 5. The method of claim 4, further comprising the steps of: When the quality of service identifier is that negotiation is not allowed, after rejecting the service connection between the user equipment and the packet data network, feed back a connection rejection reason message and the negotiated QoS information. 6. The method of claim 4, wherein, When the quality of service identifier is to allow negotiation, after the mobile core network receives the service connection request message, the mobile core network judges that the quality of service requirement can be met according to the first negotiation message and the service quality capability of the mobile core network, and establishes the user equipment and packet data Service connection between networks; when it is judged that the service quality requirement cannot be met, send a service connection request message to the base station, and send a second negotiation message containing the service quality requirement that the policy network element and the mobile core network can satisfy to the base station; When the quality of service identifier does not allow negotiation, after the mobile core network receives the service connection request message, the mobile core network judges that the service quality capability cannot meet the service quality requirements, rejecting the service connection between the user equipment and the packet data network; When the core network determines that the quality of service capability meets the quality of service requirements, it sends a service connection request message to the base station. 7. The method of claim 6, further comprising the steps of: When the quality of service identifier is to allow negotiation, the mobile core network judges that the quality of service requirement cannot be met, and feeds back a second negotiation message; When the quality of service identifier is that negotiation is not allowed, after the service connection between the user equipment and the packet data network is rejected, a connection rejection reason message is fed back. 8. The method of claim 6, wherein, When the quality of service identifier is to allow negotiation, after the base station receives the service connection request message, the base station judges that the service quality requirement can be met according to the second negotiation message and the radio resource capability, and establishes the service connection between the user equipment and the packet data network; When the base station judges that the quality of service requirement cannot be met, the base station negotiates radio resources with the user equipment according to the second negotiation message and the radio resource capability of the base station; When the quality of service identifier does not allow negotiation, after the base station receives the service connection request message, the base station judges that the radio resource capability cannot meet the service quality requirement, rejects the service connection between the user equipment and the packet data network; the base station judges the radio resource capability When the quality of service requirements can be met, the base station negotiates with the user equipment on radio resources. 9. The method of claim 8, further comprising the steps of: When the quality of service identifier is to allow negotiation, when the base station judges that the quality of service requirement cannot be met, feed back the quality of service capability message that the base station can provide according to the second negotiation message and the radio resource capability; When the quality of service identifier is that negotiation is not allowed, after the service connection between the user equipment and the packet data network is rejected, a connection rejection reason message is fed back. 10. The method of claim 8, wherein, When the quality of service identifier is to allow negotiation, and the base station can meet the quality of service requirement according to the second negotiation message, the radio resource capability of the base station, and the user equipment for wireless resource negotiation, establish a service connection between the user equipment and the packet data network; When the quality of service identifier does not allow negotiation, and the base station and the user equipment cannot meet the quality of service requirements for wireless resource negotiation, reject the service connection between the user equipment and the packet data network; when the negotiation can meet the quality of service requirements, establish the user equipment Service connection with packet data network. 11. The method of claim 10, further comprising the steps of: When the quality of service identifier is to allow negotiation, the negotiation cannot meet the quality of service requirement, and the base station feeds back a message of the quality of service capability that can be provided after negotiation with the user equipment according to the second negotiation message and the radio resource capability of the base station; When the quality of service identifier is that negotiation is not allowed, after the service connection between the user equipment and the packet data network is rejected, a connection rejection reason message is fed back. 12. The method according to any one of claims 5, 7, 9, 11, further comprising the steps of: The application function entity decides whether to initiate a service connection request again according to one or a combination of the QoS-related connection rejection reason message, the second negotiation message, base station radio resource capability, and the negotiation result between the base station and the user equipment. 13. The method according to claim 12, wherein the connection rejection reason message includes one or a combination of the following reasons: Maximum bandwidth, guaranteed bandwidth, average bandwidth, peak bandwidth, transmitted data type, delay, jitter, data packet size, priority, bit error rate, user service contract restrictions to establish service connections, user location restrictions to establish service connections, A network element that refuses to establish a service connection. 14. A quality of service negotiation system for a wireless communication network, comprising: a user equipment for applying for a service from an application functional entity; and for issuing a policy to a network element after receiving a service application from a user to establish a service between the user equipment and a packet data network The application function entity of the connection request message; It is characterized in that it also includes: An identifying module, configured to identify in the request message whether the quality of service required for the service connection of the user equipment is allowed to be negotiated; The service connection module is used to identify whether the negotiation is allowed according to the service quality, and after the policy network element judges whether the service quality capability can meet the service quality requirements required by the service requesting connection, establish or reject the user equipment and the packet data network business connection between. 15. The system according to claim 14, wherein the identification module is located at the application function entity or the policy network element. 16. The system according to claim 14, wherein the service connection module is configured to, according to the indication of whether the service quality is allowed to be negotiated, in the policy network element according to the subscription information, the user's access information, and the service connection After judging one or a combination of the requirements of the requested connection service, the service connection between the user equipment and the packet data network is established or rejected. 17. The system according to claim 14, wherein the service connection module comprises a first judging unit, a service connection unit, a service rejection unit, and a first sending unit, wherein: A service connection unit, configured to establish a service connection between the user equipment and the packet data network after being triggered by the first judging unit; A rejecting service unit, configured to reject the service connection between the user equipment and the packet data network after being triggered by the first judging unit; The first sending unit is configured to send a service connection request message and/or a first negotiation message containing the quality of service requirements that the policy network element can satisfy to the mobile core network; The first judging unit is configured to trigger related units after judging according to the quality of service identifier and the quality of service requirements that the policy network element can meet; When the first judging unit judges that the quality of service identifier is to allow negotiation, and the quality of service capability of the policy network element can meet the quality of service requirements required by the requested connection service, trigger the service connection unit to establish a service connection; When the first judging unit judges that the quality of service identifier is to allow negotiation, and the quality of service capability of the policy network element cannot meet the quality of service requirements required for the requested connection service, the first sending unit is triggered to send the service connection request message to the mobile core network and sending the first negotiation message to the mobile core network; When the first judging unit judges that the quality of service identifier does not allow negotiation, and the quality of service capability of the policy network element cannot meet the quality of service requirements required by the service requesting the connection, trigger the rejecting service unit to reject the service connection; When the first judging unit judges that the quality of service identifier does not allow negotiation, after the quality of service capability of the policy network element can meet the quality of service requirements required for the requested connection service, trigger the first sending unit to send a service connection request to the mobile core network information. 18. The system according to claim 17, further comprising a first feedback unit, configured to feed back a connection rejection reason message when the service rejection unit is triggered. 19. The system according to claim 17, further comprising a second judging unit, configured to trigger the related unit after judging according to the quality of service identifier, the first negotiation message and the mobile core network quality of service capability; The second sending unit sends a service connection request message to the base station, and/or a second negotiation message containing the quality of service requirements that the policy network element and the mobile core network can satisfy; When the second judging unit judges that the quality of service identifier is allowed to negotiate and the mobile core network can meet the quality of service requirements, it triggers the service connection unit to establish a service connection; when it judges that the quality of service requirements cannot be met, it triggers the second sending unit to send the service to the base station a connection request message and a second negotiation message; When the second judging unit judges that the quality of service identifier does not allow negotiation, and the mobile core network cannot meet the quality of service requirements, it triggers the rejection service unit to reject the service connection; when the mobile core network can meet the quality of service requirements, it triggers the second sending unit to send The base station sends a service connection request message. 20. The system according to claim 19, further comprising a second feedback unit, configured to feed back a second negotiation message when the second sending unit is triggered; , to return a connection rejection reason message. 21. The system according to claim 19, further comprising a third judging unit, configured to trigger a related unit after judging according to the second negotiation message and the radio resource capability; a negotiating unit, configured to perform negotiation according to the second negotiation message, the radio resource capability of the base station, and/or the radio resources of the base station and the user equipment; When the third judging unit judges that the quality of service identifier is allowed to negotiate, and the base station can meet the quality of service requirements, it will trigger the service connection unit to establish a service connection; when the base station cannot meet the quality of service requirements, the trigger negotiation unit will Negotiating wireless resources with the user equipment on resource capabilities; When the third judging unit judges that the quality of service identifier does not allow negotiation, and the base station cannot meet the quality of service requirements, it triggers the rejection service unit to reject the service connection; when the base station can meet the quality of service requirements, it triggers the negotiation unit according to the radio Resources are negotiated. 22. The system according to claim 21, further comprising a third feedback unit, configured to feed back the service that the base station can provide according to the second negotiation message and radio resource capability after the second sending unit is triggered Quality capability message; when the reject service unit is triggered, a connection reject reason message is fed back. 23. The system according to claim 21, further comprising a fourth judging unit, configured to trigger a related unit after judging the negotiation of radio resources with the user equipment according to the second negotiation message, the radio resource capability of the base station; When the fourth judging unit judges that the service quality identifier is allowed to be negotiated, and the service quality capability of the base station and the user can meet the service quality requirements, trigger the service connection unit to establish a service connection; When the fourth judging unit judges that the quality of service identifier is not allowed to be negotiated, and the quality of service capabilities of the base station and the user cannot meet the quality of service requirements, trigger the rejection service unit to reject the service connection; when the quality of service requirements can be met, trigger the establishment of the service connection unit business connection. 24. The system according to claim 23, further comprising a fourth feedback unit, which is used to feed back the base station according to the second negotiation message and the base station wireless resource when the service quality capability of the base station and the user cannot meet the service quality requirement. The message of the quality of service capability that can be provided after the capability is negotiated with the user equipment, or the message of the reason for rejecting the connection. 25. The system according to any one of claims 18, 20, 22, and 24, further comprising a retransmission request module, configured to respond to the QoS-related connection rejection reason message, second negotiation message, One of the radio resource capability of the base station, the negotiation result between the base station and the user equipment, or a combination thereof determines whether to trigger the application function entity to initiate a service connection request again.

Images