KR20080098302A - Apparatus and method for setup quality of service in wireless communication system - Google Patents

Abstract

A QoS setting apparatus in a wireless communication system and a method thereof are provided to efficiently use wireless resources by selectively activating desired service flows. A QoS setting method in a wireless communication system comprises the following steps. A terminal sets up at least one fixed service flow when it receives a QoS profile from a base station in the initial connection. If a QoS change of the service flow is requested(229), the terminal a service change requesting message including QoS change information to a base station(231). The base station determines whether the service change request can be accepted, and transmits a service change response message to the terminal.

Description

Apparatus and method for setting quality of service in wireless communication system {APPARATUS AND METHOD FOR SETUP QUALITY OF SERVICE IN WIRELESS COMMUNICATION SYSTEM}

The present invention relates to an apparatus and method for establishing a quality of service (QoS) in a wireless communication system, and more particularly, to an end-to-end quality of service (QoS) in a communication system using a broadband wireless access (BWA). An apparatus and a method for guaranteeing a service are provided.

Recently, there is an increasing demand for various multimedia applications such as Voice of IP (VoIP), real-time game, and Video on Demand (VoD) with different traffic characteristics. As such, as the type of service increases, the traffic congestion, and the level of service demands of the user are diversified, current communication systems are operated in consideration of QoS indicating user satisfaction as well as their own capabilities. Moreover, since the available resources change due to the time-varying channel environment and the movement of the terminal, a policy for guaranteeing the QoS is necessarily required.

On the other hand, many wireless communication technologies have been proposed as candidates for high speed mobile communication. Among them, orthogonal frequency division multiplexing (OFDM) is recognized as the most powerful next generation wireless communication technology. The OFDM technology is expected to be used in most of the wireless communication technologies in the future, and the IEEE 802.16 series WMAN (Wireless Metropolitan Area Network) of the 3.5 generation technology is also adopted as the standard.

However, at present, the standard for the broadband wireless access is standardized only in the MAC layer QoS interworking procedure, and there is no interworking procedure with the network for guaranteeing end-to-end QoS. In other words, the IEEE 802.16 series in charge of PHY / MAC is standardized only for the DSx interworking procedure between the base station and the terminal. Here, DSA (Dynamic Service Addition) indicates service generation, DSD (Dynamic Service Deletion) indicates service deletion, and DSC (Dynamic Service Change) indicates service change.

For quality service, end-to-end QoS of application layer should be guaranteed. Therefore, in the case of a broadband wireless access system in which only MAC layer QoS is currently defined, an interworking procedure for QoS setting between a terminal, an access network, and a core network should be defined.

Accordingly, an object of the present invention is to provide an apparatus and method for correcting end-to-end QoS in a broadband wireless access system.

Another object of the present invention is to provide an apparatus and method for configuring QoS between a terminal-access network and a core network in a broadband wireless access system.

Another object of the present invention is to provide an apparatus and method for fixedly allocating a service flow to a terminal in a broadband wireless access system.

Another object of the present invention is to provide an apparatus and method for changing QoS parameters of a service flow fixedly allocated to a terminal in a broadband wireless access system.

According to an aspect of the present invention for achieving the above object, in a method of establishing a Quality of Service (QoS) in a wireless communication system, at the initial connection, the terminal receives the QoS profile from the base station to perform at least one fixed service flow Setting up, when the QoS change of the service flow is required, the terminal transmitting a service change request message including QoS change information to a base station, and when the service change request is received by the base station, The method may include determining whether to be granted, and if so, transmitting a service change response message to the terminal to change the QoS.

According to another aspect of the present invention, in a method of operating a terminal in a wireless communication system, during an initial access, a process of setting at least one fixed service flow by performing a service addition procedure with a base station, and changing the QoS of the service flow Determining whether it is required, and if the QoS change is required, transmitting a service change request message including QoS change information to the base station.

According to still another aspect of the present invention, in a method of operating a base station in a wireless communication system, a process of setting at least one fixed service flow by performing a service addition procedure with an initially accessed terminal and changing a QoS of the service flow Determining whether a request is made; and if the QoS change is required, transmitting a service change request message including QoS change information to the terminal.

According to still another aspect of the present invention, in a wireless communication system, at the initial connection, receiving a QoS profile from the base station to set up at least one fixed service flow, and includes QoS change information when the QoS change of the service flow is required And a base station for transmitting a service change request message to a base station, and determining whether the service change request is granted by itself or in association with another network entity, and if so, the base station transmitting a service change response message to the terminal. It is characterized by.

According to still another aspect of the present invention, in a terminal device in a wireless communication system, at least one fixed service flow is set by performing a service addition procedure with a base station during initial access, and QoS is required when a QoS change of a service flow is required. And a control unit for generating a service change request message including change information, and a transmitter for physically encoding and transmitting the service change request message.

According to still another aspect of the present invention, in a base station apparatus in a wireless communication system, at least one fixed service flow is set by performing a service addition procedure with an initially accessed terminal and changing the QoS when a QoS change of the service flow is required. And a control unit for generating a service change request message including information and a transmitter for physically encoding and transmitting the service change request message.

As described above, according to the interworking procedure according to the present invention, it is possible to allocate the QoS service flow to the terminal. In addition, since the QoS service flow is fixedly assigned and the desired service flow is selectively activated, radio resources can be efficiently used. In addition, since QoS parameter change is allowed for a fixedly allocated QoS service flow, there is an advantage in that the QoS service can be more flexibly operated. In addition, the present invention has the advantage of minimizing the delay (processing delay and processing delay) for QoS call processing by utilizing the currently proposed call processing interface as it is, and simplifying information transfer between the interfaces.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

Hereinafter, the present invention will be described a method for statically or provisioning a service flow to a terminal in a broadband wireless access system and for changing the QoS of a service flow fixedly assigned to the terminal. As such, the technique of changing the QoS of a fixedly allocated service flow will be referred to as "semi-dynamic QoS setup."

In the following description, the base station may be, for example, a radio access station (RAS) or a base station (BS). In addition, the control station may be an access control router (ACR) or an access service network gateway (ASN-GW). Here, the ASN-GW may perform a router function as well as a control station function.

In addition, in the following description, the name of a network entity (NE: Network entity) is defined according to a corresponding function, and may vary depending on the intention of a user or an operator.

1 illustrates a network configuration according to an embodiment of the present invention.

As shown, a terminal (MS) 110, a base station (BS) 120, a control station (ASN_GW: Access Service Network-Gateway) 130, a policy server (Policy Server) 140 ), AAA (Authentication, Authorization, Accounting) 150 and a system manager (WSM: WiBro System Manager) 160. Here, the network composed of the base station 120 and the control station 130 may be defined as an access service network (ASN). In addition, the system manager 160 may be referred to as WSM or Element Management System (EMS). The policy server 140 may be configured as a separate server as shown, or may be mounted as a function in another network entity as another example.

Referring to FIG. 1, first, the AAA server 150 performs authentication and charging for a terminal in cooperation with the control station 130. According to the present invention, the AAA server 150 requests a DSA (Dynamic Service Addition) trigger to the control station 130 when authentication of the terminal is successful. When the DSA trigger request, the AAA server 150, the user class ID (user class ID) for the terminal, QoS profile identifiers (Service profile identifiers: Multiple service profile IDs) of the service flows assigned to the terminal, Any one of a QoS parameter set of service flows allocated to the terminal may be provided to the control station 130. In this case, the service profile identifier and the QoS parameter set are output parameters of the PDF. When the output parameter is provided, the AAA server 150 may include a policy decision function (PDF). In addition, the AAA server 150 may provide the control station 130 with an allowable range of QoS parameters. Here, even in the same service type, the allowable range may vary according to the user class. The AAA server 150 and the ASN may use a common open policy service (COPS), a radius, or a diameter interface. Meanwhile, the user information may be managed in a subscription profile repository (SPR) server. In this case, the user class ID may be provided by the SPR server. The SPR function may be included in the AAA server or another server or exist as a separate server.

When the AAA server 150 transmits the service profile identifier for the terminal to the control station 130, the AAA server 150 may transmit a plurality of service profile identifiers in one message, and the control station 130 may transmit the DSA to the base station 120. When requesting triggering, a plurality of service profile identifiers (or a plurality of service flow identifiers) may be transmitted in one message, and even when the base station 120 performs a DAS procedure with the terminal 110 over the air, one DSA message may be transmitted. Through the call processing can be performed for a plurality of service flows. For example, when the terminal 110 generates 10 service flows upon initial access, a specific service flow as a reference is selected to describe both QoS parameters and CS rules for the flow, and for the remaining service flows. It is possible to optimize the size of the DSA-REQ message by describing only the parameters that differ from the reference flow. In this case, a plurality of service flow information may exist in an array in one message.

In addition, the AAA server 150 performs the charging for the terminal. Here, the charging statistics section is determined to be a section in which the actual service flow is active. When the terminal moves, the control station responsible for the start, middle and end points of the traffic flow may be different, and each control station reports the actual serving time to the AAA server 150. As another example, whenever the call processing station is changed, the charging statistics information accumulated up to that time is transferred to the target control station, and the charging station at the end of the service reports the collected charging statistics information to the AAA server 150. Can be. If the terminal is equipped with a SIM card (SIM card), the AAA server 150 may transmit the charging statistics information collected from the control station 130 to the terminal through the application layer. In this case, charging is performed in the SIM card of the terminal. As another example, the SIM card may charge itself. In this case, the charging statistical information may be collected by the terminal itself or provided from the control station.

Meanwhile, the charging rule and the CS rule may be set identically or differently. The billing rule is set by the operator through the WSM like the CS rule, the set billing rule is transferred from the WSM to the control station, the AAA server 150 to the ASN or the policy server 140 to the ASN or Can be created and managed in the SIM card in the terminal. In the case of the CS rule, only the ASN may be managed only for the downlink and only the terminal may be managed for the uplink. In the case of the charging rule, the CS rule may be managed in the ANS or the terminal according to the subject (ASN or terminal) of statistics collection. If the ASN is a collecting agent, the billing rule is managed in both the downlink / uplink in the ASN, if the terminal is a collecting agent, both the downlink / uplink is managed in the terminal.

The policy server 140 provides the QoS mapping information input by the operator (or operator) to the control station 130 and the base station 120. For example, the QoS mapping information may consist of a service profile set (set) for each user class and a QoS parameter set (set) for each service profile. In this case, the user class may be divided into, for example, premium, gold, silver, and bronze, and the number of service flows for each user class may be different. For example, four QoS flows (eg, UGS, nrtPS, rtPS, ertPS) may be allocated to premium users, and three QoS flows may be allocated to gold users. In addition, even in the same type of QoS flow SF, QoS parameters (transmission rate, data size, latency, jitter, etc.) may have different values according to user classes. Here, a common open policy service (COPS) or a Radius or Diameter interface may be used between the policy server 140 and the ASN.

Meanwhile, the policy server 150 may provide the control station 130 with service profile identifiers or QoS parameter sets and CS rules for the terminal. Specifically, when the registration procedure for the terminal is completed, the control station 130 transmits the user identifier to the policy server 150, the policy server 150 delivers the user identifier to the SPR server to the corresponding user Obtain information about the class (eg user class). In addition, the policy server 150 determines one of service profile identifiers, QoS parameter sets, and CS rules for the terminal using the obtained user information, and transmits the same to the control station 130. . An advantage of this embodiment is that both the static QoS setting method and the dynamic QoS setting method can be managed by the policy server 150. The point of time when the user identifier is transmitted to the policy server 150 may be before the IP allocation procedure or after the IP allocation. After the IP allocation, the IP can session is established between the anchor control station and the policy server 150 (CAN). session setup).

The system manager 160 transmits information related to a network configuration to the ASN, and manages the control station 130 and the base station 120 configuring the ASN. According to the present invention, a PDF may be mounted on the system manager 160. In this case, the system manager 160 transmits QoS mapping information input by an operator (or operator) to the control station 130 and the base station 120. To provide.

The control station 130 transmits the traffic from the core network to the base station 120, and transmits the traffic from the base station 120 to the core network. In this case, the control station 130 manages a service flow (SF), a connection, and mobility for each terminal. Here, a unique service flow (SF) is generated for each uplink and downlink connection. According to the present invention, the control station 130 manages the QoS mapping information received from the policy server 140 or another network entity (with a PDF) in the form of a mapping table. When the DSA triggering for a specific terminal is requested from the AAA server 150, the control station 130 generates a fixed service flow for the terminal using the mapping table, and generates the service flow identifier (SFID). Transfer to the base station 120 to request the DSA trigger.

The base station 120 transmits the traffic from the control station 130 to the terminal 110, and transmits the traffic from the terminal 110 to the control station 130. Here, the base station 120 is connected to the control station 130 by wire and wirelessly connected to the terminal 110. The base station 120 performs scheduling based on MAC (Media Access Control) layer QoS and allocates resources to the terminal 110. According to the present invention, the base station 120 manages the QoS mapping information received from the policy server 140 or another network entity (PDF mounted) in the form of a mapping table. When DSA triggering is requested from the control station 130, the base station 120 obtains QoS parameters from the mapping table using a service flow identifier (SFID) from the control station 130, and obtains the QoS parameters. Performs a DSA procedure with the terminal. As such, the service flow is generated through the DSA procedure, and the activation of the actual service flow is performed through the DSC procedure. That is, when there is a DSC-REQ from the terminal, the base station performs a CAC, allocates a traffic connection identifier (TCID), and communicates traffic using the TCID. In addition, the present invention can change the QoS parameter of the service flow fixedly assigned to the terminal, the change of the QoS parameter is also performed by a DSC procedure (base station request or terminal request). Since the QoS parameter change procedure is described in detail later, a detailed description thereof will be omitted.

On the other hand, ASN manages the state (eg, null, active, sleep, idle) of each terminal, if the terminal that is fixedly assigned the service flow transitions to the idle mode, only the SFID (Service Flow ID) for the terminal I can keep it. When the terminal transitions to the awake mode through the QCS (Quick Connection Setup) in the idle mode, the base station transmits the "SFID vs TCID" to the terminal through a ranging response (RNG-RSP) message, the terminal has already been SFID and Since it has QoS information, it manages by mapping TCID to each SFID. Here, the CID is uniquely allocated for each flow in the base station, but the SFID may be unique for each flow in the terminal. In addition, the network between the control station 110 and the base station 112 may be configured as L2 (layer 2) network or L3 (layer 3: IP) network as shown.

The terminal 110 generates a fixed service flow by performing a DSA procedure with the base station 120 during initial access. In addition, when activation of a specific service flow is required, the terminal 110 performs a DSC procedure with the base station 120, receives a TCID, and communicates traffic using the TCID. In addition, when the QoS change of the service flow is required, the terminal 110 performs a DSC procedure with the base station 120 to change the QoS parameter.

Even if the terminal in the awake or sleep mode moves to another subnet, the anchor control station (or FA control station) is not changed. In this case, the QoS profile for the terminal is delivered to a new serving base station through tunneling or L2 extension. When the terminal in the idle state moves to another subnet, the anchor control station is changed, but the terminal maintains the SFID. The QoS profile for the terminal is transferred from a conventional anchor control station to a target anchor control station. In this case, when the existing anchor control station and the target anchor control station interwork with the same AAA server, instead of the QoS profile, user class ID or identifiers of service flows, which are information overlooked by the AAA server, may be used. However, even if the control stations or base stations operating under the same PDF can be provided with a QoS setup scheme (semi-dynamic QoS setup, fixed QoS setup, etc.), considering the situation, the QoS provided to the target anchor control station is CS. It is desirable to be a parameter and a QoS profile.

On the other hand, when the terminal moves to another network in the AAA server, the anchor control station is basically changed. In this case, the PDF may be applied as it is, or only the QoS information may be changed while the number of flows allowed is the same. If the QoS information is changed, all CS parameters and QoS information are delivered to the target anchor control station in order to guarantee seamless QoS, and if the PDF is different enough to not be resolved by DSC, the terminal must proceed with the initial access procedure again. do.

In addition, an intermediate AAA may be configured for translation between AAA servers having different user class classification methods. The charging policy is based on charging only for the portion used in each transfer network or target network. For example, looking at the charging method of the target network, the AAA server of the target network performs the charging according to the usage time and the amount of usage for each service flow based on the charging statistics information from the target control station to notify the AAA server of the previous network. can do. As another example, the AAA server of the previous network may be notified only after the usage time and the amount of use are used, and the corresponding amount may be paid to the provider of the target network.

Although not shown in FIG. 1, network entities for allocating an IP address to a terminal (DH for simple IP, HA and FA for mobile IP), and a network entity name (NAI: Network Access Identifier) and an IP address It is obvious that a DNS (Domain Name Server) server, etc., which manages the mapping relationship of the server is configured.

Prior to describing the operation, the input parameters and output parameters of the PDF are defined as follows.

First, the PDF input parameters are 5tuple (source & destination IP address, source & destination port number, protocol ID) or 6tuple (5tuple + ToS (Type of service) and user class (e.g. Premium, Gold, Silver, Bronze, etc.) In this case, since 5 tuples and 6 tuples are used to distinguish flows, they must be delivered to the NE (eg, ASN_GW) that is responsible for the CS (ClasSification) rule.

Next, the PDF output parameters may be defined as QoS parameter sets (sets) for IP QoS (DSCP: DiffServ Code Point) and MAC QoS (eg, IEEE 802.16 QoS parameters). Here, the IEEE 802.16 QoS parameters include traffic priority, maximum sustained rate, minimum reserved rate, maximum latency, grant interval, and the like. have.

Meanwhile, the present invention further proposes QoS parameters as shown in Table 1 in addition to the PDF output parameters defined above.

parameter Explanation  Compression of IP Header and Compression Method 1) uncompressed 2) Payload Header Suppression (PHS) 3) Robust Header Compression (ROHC) Whether to use a Traffic Encryption Key (TEK) Security entry Pre-provisioned Per terminal If not Pre-provisioned, choose Provisioned, Admitted, Active by flow Provisioned: Create SFID only Admitted / Active: Assign TCID by performing CAC at initial connection Whether to allow QoS changes using DSC 1) The increase or decrease of the parameter value can be set selectively. 2) The allowable range of QoS change includes the change of service type (eg nrtPS-> UGS). QoS Changes in Activation Flow Status When DSC is allowed, the handling of QoS parameters not exchanged through DSC 1) Reuse the previous value 2) Use the default value of the system 3) Ignore the QoS parameter Reliability Example: target error rate Call Release Condition Duration threshold when the minimum reserved rate is not met Whether to perform retransmission scheme (ARQ, HARQ) What happens if the number of awake mode users on the serving base station exceeds a certain threshold 1) Transition the low priority among users who do not flow traffic for a certain time to sleep or idle mode, and allow the initial access user to awake mode. 2) After completing the initial connection, transfer the user to sleep mode. 3) After the initial connection is completed, the user transitions to the idle mode. 4) The number of sleep mode users of the serving base station is compared with a threshold value. If the threshold value is not exceeded, the user transitions to the sleep mode. Transition to mode. Whether to provide symmetric QoS flow Indicates whether the sender can adjust the service level of the other terminal to the same level as itself when performing a two-way service such as VoIP with a terminal having a relatively low class of service. When the call ends, the control station managing the receiver deletes the temporarily assigned QoS information. The terminal automatically recovers the original QoS profile after completing the call internally, or receives and updates the original QoS profile by the base station request DSC procedure.  Maximum allowable number of DSC usages for each flow Allow flow timer for active-> provisioned and timer value Terminal-specific timers (sleep timer, idle timer) take precedence over flow timer. If there is no timer for each terminal, when the timers of all flows exceed the sleep transition (idle transition) timer value, the terminal may transition to the sleep (idle) mode. Whether horizontal handover to other carrier networks using the same wireless technology is possible Vertical handover to other wireless networks using different radio technologies DSD Accepted

In Table 1, the "pre-provisioned" mode indicates a mode in which all service flows belonging to the terminal are activated during initial access. At this time, if all the service flows are allowed through the CAC, not only the SFID but also the TCID is allocated. If any one of the service flows fails, the initial connection itself is failed.

2 illustrates a QoS setting procedure in a wireless network according to an embodiment of the present invention. FIG. 2 illustrates a case in which a PDF is mounted in a system manager (WSM) and determines whether to allow QoS change through a connection admission control (CAC) at a base station.

Referring to FIG. 2, the system manager first provides QoS mapping information input by an operator (or operator) to a control station in step 201. In operation 203, the system manager provides the QoS mapping information to a base station. In this case, the system manager provides the QoS mapping information to the control station and the base station separately, but the system manager delivers the QoS mapping information to the control station, and the control station may deliver the QoS mapping information to the base station. have. In addition, the QoS mapping information may be provided only to the control station. The QoS mapping information may include a service profile set (set) for each user class and a QoS parameter set (set) for each service profile (or QoS profile).

In step 205, the control station generates a PDF mapping table according to the QoS mapping information from the system manager. In step 207, the base station generates a PDF mapping table according to the QoS mapping information from the system manager. As such, FIG. 2 illustrates a case in which the PDF exists in the form of a mapping table in the ASN.

In step 209, the terminal attempting initial access performs a ranging procedure (RNG-REQ / RNG-RSP) with the base station, and performs a capability negotiation procedure (SBC-REQ / SBC-RSP) in step 211. In step 213, the terminal performs an authentication procedure (PKM) with the base station. At this time, the base station authenticates the terminal in association with the AAA server. When the authentication is completed, the terminal performs a registration procedure (REG-REQ / REG-RSP) in step 215, open the best effort (BE) flow for each of the DL and UL and is assigned an IP address through this flow Complete the initial network entry.

On the other hand, the AAA server determines whether the terminal is a subscriber that is fixedly assigned a service flow. If it is determined that the terminal is fixedly assigned a service flow, the AAA server transmits a message requesting the DSA trigger to the control station to the control station in step 217. In this case, the AAA server sets a user class ID for the terminal, multiple service profile IDs of QoS flows to be allocated to the terminal, and a QoS parameter set of QoS flows assigned to the terminal. ) May be provided to the control station.

Then, in step 219, the control station generates an identifier (SFID) of a service flow allocated to the terminal in response to the DSA trigger request. After generating the SFID, the control station transmits the SFID and the user class ID (or service profile ID) to the base station in step 221 to request a DSA trigger. Thereafter, a communication name tag between the control station and the base station may be determined as an SFID.

Then, in step 223, the base station acquires the required QoS parameters (QoS profile) from the mapping table (step 207) using the user class ID (or service profile ID), and generates a DSA-REQ message with the QoS parameters. Create and send to the terminal. If the base station does not have the mapping table 207, the control station should provide the base station with QoS parameters necessary for generating the DSA-REQ message when requesting a DSA trigger.

In step 225, the terminal generates a service flow according to the DSA-REQ message, and transmits a DSA-RSP message to the base station in response. Then, in step 227, the base station transmits a DSA-ACK message to the terminal as confirmation of the DSA-RSP message to complete the DSA procedure. Here, the DSA procedure (DSA-REQ / DSA-RSP / DSA-ACK) may be performed by the number of fixed service flows allocated to the terminal.

In addition, in the DSA procedure, a service (BE) that is not a QoS guarantee target may be directly assigned to a TCID by setting an admitted or active flow. That is, in the case of a service flow set to admitted or active, a CAC is executed immediately during the initial access DSA procedure, and if it is accepted by the CAC, a TCID is assigned and activated, otherwise a provisioned flow is provided. ). Herein, when traffic flows to the assigned TCID, an active state service flow becomes, and when traffic does not flow, an admitted state service flow. Here, although not shown, when the DSA procedure is completed, the control station notifies the AAA server of the DSA trigger response (DAS trigger Res.) To proceed with accounting. If the QoS setting is made through the policy server (PDF) rather than the AAA server or the system manager (WSM), the DSA trigger response is also notified to the policy server. When setting QoS through AAA server or WSM, proceed with DSA interworking procedure for creating QoS service flow before IP allocation procedure, and after IP allocation because IP address can be used as terminal identifier when proceeding through policy server. You can proceed with the DSA interworking process.

The present invention can change the QoS of the fixedly assigned service flow. In detail, the terminal determines whether a QoS change is required by the user in step 229. Since the QoS setting is based on per-flow, it is assumed that the QoS change is made per flow. If the QoS change is required, the terminal transmits a DSC-REQ message including the changed QoS information to the base station in step 231.

In step 233, the base station performs a connection acceptance control (CAC) with the changed QoS information. In this case, when the connection is accepted, the base station reports QoS change information of the corresponding service flow of the terminal to the control station in step 239. In addition, the base station transmits a DSC-RSP message to the terminal in response to the DSC-REQ message in step 235, and the terminal confirms the DSC-RSP message in step 237 by the DSC-ACK message. To complete the QoS parameter change.

On the other hand, although not described in Figure 2 above, the QoS change can be requested from the ASN (base station and control station), in this case the initiation of the DSC procedure (initiate) is performed in the base station. For example, the base station may determine and start the DSC procedure regardless of the request of the terminal. For example, when radio resources or network resources are congested, the base station may arbitrarily change the QoS parameters. As another example, when the policy of the operator is changed so that the QoS parameter (or CS rule) for the service flow is changed, the base station may initiate the DSC procedure to change the QoS parameter. In this case, it is assumed that the final permission of the QoS change information follows the scheme of FIGS. 2 to 6 as in the terminal initiation.

Basically, the state-by-flow state (active, admitted, provisioned) change is performed through a DSC procedure (terminal request (outgoing) or base station request (incoming)). In a special case, the system and the terminal may mutually promise to perform the same state change for each flow between the two ends without the DSC procedure. For example, when the terminal transitions from the idle mode to the awake mode, both the base station and the terminal may change the flow-specific state without the DSC procedure.

DSC triggering for service flow state transition may be performed by traffic generation or a higher layer command as follows.

First, BS_init DSC or MS_init DSC can be performed depending on traffic. When DL traffic occurs, the BS_init transitions the flow from the provisioned state to the active state by the MS_init when UL traffic occurs. On the contrary, if there is a timer for each flow in both the system and the terminal, it is possible to transition the state of the flow to the ready state by the timer expiration. In this case, the DSC procedure may be initiated at the node where the timer expires first to transition the flow to the ready state.

Secondly, in case of BS_init DSC, when the UE transmits Session Initiation Protocol (SIP) signaling, the IMS server triggers a policy server (PDF server), and the policy server transmits a DSC trigger command to the control station. Send the DSC trigger command to the base station. When transitioning from the ready state to the active state, the base station performs CAC, and if accepted, transmits a DSC-REQ message including activation information (including TCID) to the terminal, and the terminal responds to the DSC-RSP message to the base station. send.

Third, in case of MS_init DSC, when the UE transmits SIP signaling, the IMS server transmits. Then, the application layer of the terminal triggers the MAC layer to proceed with the MS_init DSC procedure to change the state of the flow. Even when the service flow is terminated, the application layer of the terminal may trigger the MS_init DSC procedure by triggering the MAC layer.

In addition, the service flow may be deleted by a DSD procedure (base station request or terminal request). For example, the base station may determine the deletion of the service flow by whale or the like. In this case, it is assumed that the number of service flows that can be deleted for each user class is predetermined through a QoS profile. If the service flow is deleted, the SFID is deleted at both ASN and MS.

When the policy (QoS mapping information) is modified in the scheme of FIG. 2, that is, when the operator modifies the QoS mapping information through the system manager, the modified QoS mapping information is transmitted from the system manager to the ASN. And the base station update the mapping table according to the modified QoS mapping information.

In addition, when the policy (PDF) is changed, the method of processing the access users is as follows. First, it maintains the QoS profile and CS rule of the access user. Second, trigger all users to re-establish their initial connection. That is, apply a new policy. Third, the QoS parameter and CS rule changed according to the changed policy are updated through the DSC procedure.

3 illustrates a QoS setting procedure in a wireless network according to another embodiment of the present invention. 3 shows a case where a PDF is embedded in a system manager (WSM) and the base station and the control station determine whether to allow QoS change. Hereinafter, descriptions overlapping with those of FIG. 2 will be omitted and descriptions will be given based on differences.

Referring to FIG. 3, the system manager (WSM) provides the QoS mapping information to the control station in step 301. At this time, the system manager also transmits the allowable range of each QoS parameter to the control station. Accordingly, the control station generates a mapping table with QoS mapping information including the allowable range of each parameter in step 305.

On the other hand, the terminal performing the initial access is assigned a fixed service flow in step 309 to step 327. In step 329, the terminal determines whether a QoS change is required by the user. When the QoS change is required, the terminal transmits a DSC-REQ message including QoS change information to the base station in step 331.

In step 332, the base station performs a connection acceptance control (CAC) with the changed QoS information. In this case, when the connection is accepted, the base station transmits the QoS change information to the control station in step 333. In step 335, the control station checks whether the QoS change information is within an allowable range stored in the mapping table 305. If it is within the allowable range, the control station transmits a response to the base station to allow a QoS change in step 337. If not within the allowable range, the control station sends a response to the base station to reject the QoS change in step 337. Herein, if the connection is accepted, the control station determines whether to allow the QoS change, but as another example, the control station first determines whether to change the QoS, and if granted, the base station may perform CAC.

In step 339, the base station generates a DSC-RSP message according to the response from the control station, and transmits the DSC-RSP message to the terminal. Then, in step 341, the terminal completes the QoS parameter change by transmitting a DSC-ACK message to the base station in acknowledgment of the DSC-RSP message.

4 illustrates a QoS setting procedure in a wireless network according to another embodiment of the present invention. 4 illustrates a case in which a PDF server (policy server) is separately configured in a core service network (CSN) and the base station and the policy server determine whether to allow QoS change. Hereinafter, descriptions overlapping with those of FIG. 2 will be omitted and the focus will be on differences.

Referring to FIG. 4, the policy server first provides QoS mapping information input by an operator (or operator) to a control station in step 401. In step 403, the policy server provides the QoS mapping information to a base station. The QoS mapping information may include a service profile set (set) for each user class and a parameter set (set) for each service profile.

On the other hand, the terminal performing the initial access is assigned a fixed service flow in step 409 to step 427. Thereafter, the terminal determines whether a QoS change is required by the user in step 429. When the QoS change is required, the terminal transmits a DSC-REQ message including QoS change information to the base station in step 431.

In step 432, the base station performs a connection acceptance control (CAC) with the changed QoS information. In this case, if the connection is accepted, the base station transmits the QoS change information to the control station in step 433, and the control station transmits the QoS change information to the policy server in step 435. In step 437, the policy server checks whether the QoS change information exists within an allowable range. If it is within the allowable range, the policy server sends a response to the control station to allow a QoS change in step 439. If not within the allowable range, the policy server sends a response to the base station to reject the QoS change in step 439.

In step 441, the control station transmits a response from the policy server to the base station. Then, the base station generates a DSC-RSP message according to the response from the control station in step 443, and transmits the DSC-RSP message to the terminal. Then, in step 443, the terminal completes the QoS parameter change by transmitting a DSC-ACK message to the base station in acknowledgment of the DSC-RSP message.

When the policy (QoS mapping information) is modified in the scheme of FIG. 4, the PDF is modified in the core service network, and the modified QoS mapping information is transmitted from the policy server to the ASN, and the control station and the base station are modified. Update the mapping table according to the QoS mapping information. As another example, the modified QoS mapping information may be transferred from the policy server to a system manager, and the modified QoS mapping information may be transferred from the system manager to the ASN.

5 illustrates a QoS setting procedure in a wireless network according to another embodiment of the present invention. FIG. 5 illustrates a case in which a PDF server (policy server) is separately configured in a core service network (CSN) and the base station and the control station determine whether to allow QoS change. Hereinafter, descriptions overlapping with those of FIG. 2 will be omitted and the focus will be on differences.

Referring to FIG. 5, the policy server first provides QoS mapping information input by an operator (or operator) to a control station in step 501. In step 503, the policy server provides the QoS mapping information to a base station. The QoS mapping information may include a service profile set (set) for each user class and a parameter set (set) for each service profile.

The terminal performing the initial access is allocated a fixed service flow in steps 509 to 527. On the other hand, the AAA server determines whether the terminal requesting authentication is a subscriber that fixedly allocates a service flow. If it is determined that the terminal is fixedly assigned a service flow, the AAA server transmits a message requesting a DSA trigger for the terminal to the control station in step 517, and transmits a QoS parameter allowance range in step 529. Send a message requesting the to the policy server.

In step 531, the policy server transmits the QoS parameter allowance of the service flows allocated to the terminal to the control station, and the control station stores the QoS parameter allowance in step 533.

In step 535, the terminal determines whether a QoS change is required by the user. When the QoS change is required, the terminal transmits a DSC-REQ message including QoS change information to the base station in step 531.

In step 538, the base station performs a connection acceptance control (CAC) with the changed QoS information. In this case, if the connection is accepted, the base station transmits QoS change information to the control station in step 539. In step 541, the control station checks whether the QoS change information exists within the stored allowable range. If it is within the allowable range, the control station transmits a response to the base station to allow QoS change in step 543. If not within the allowable range, the control station sends a response to the base station to reject the QoS change in step 543.

In step 545, the base station generates a DSC-RSP message according to the response from the control station, and transmits the DSC-RSP message to the terminal. Then, in step 547, the terminal completes the QoS parameter change by transmitting a DSC-ACK message to the base station with confirmation of the DSC-RSP message.

In the embodiment of FIG. 5, if the AAA server has a PDF loaded, when the DSA trigger is requested in step 517, a QoS parameter allowance may also be provided to the control station. In this case, steps 529 and 531 may be omitted.

6 illustrates a QoS setting procedure in a wireless network according to another embodiment of the present invention. 6 shows a case where the control station also generates the QoS parameter allowance when generating the SFID. Hereinafter, descriptions overlapping with those of FIG. 2 will be omitted and the focus will be on differences.

Referring to FIG. 6, the control station and the base station receive and store QoS mapping information from a system manager (including PDF) or a policy server existing in the core service network. The terminal performing the initial access is assigned a fixed service flow in steps 609 to 627.

On the other hand, the AAA server determines whether the terminal requesting authentication is a subscriber that fixedly allocates a service flow. If it is determined that the terminal is fixedly assigned a service flow, the AAA server transmits a message requesting a DSA trigger for the terminal to the control station in step 617. At this time, the AAA server also transmits an input variable (eg, user class ID, service profile identifier, etc.) necessary to determine the QoS parameter allowance range to the control station.

In step 619, the control station generates an identifier (SFID) of a service flow allocated to the terminal in response to the DSA trigger request. In addition, the control station generates a QoS parameter tolerance range using the input variable received from the AAA server in step 619. For example, the QoS parameter allowable range according to the input variable may be provided from a system manager, and in another example, a PDF server of a core service network may periodically transmit it to the control station.

In step 629, the terminal determines whether a QoS change is required by the user. If the QoS change is required, the terminal transmits a DSC-REQ message including QoS parameter change information to the base station in step 631.

In step 632, the base station performs a connection acceptance control (CAC) with the changed QoS information. If the connection is accepted, the base station transmits the QoS change information to the control station in step 633. In step 635, the control station checks whether the QoS change information exists within the allowable range (step 619). If it is within the allowable range, the control station transmits a response to the base station to allow a QoS change in step 637. If not within the allowable range, the control station sends a response to the base station to reject the QoS change in step 637.

In step 639, the base station generates a DSC-RSP message according to the response from the control station, and transmits the DSC-RSP message to the terminal. Then, in step 641, the terminal completes the QoS parameter change by transmitting a DSC-ACK message to the base station with confirmation of the DSC-RSP message.

As described above with reference to FIGS. 2 to 6, the PDF may be mounted in one network entity or may be mounted in multiple network entities. For example, you can do a PDF in multiple stages. That is, the intermediate output variable may be generated using the input variable in the first PDF, and the final output variable may be generated using the intermediate output variable in the second PDF. Specifically, the first PDF located in the core generates intermediate output variables related to priority and performance (throughput, latency, reliability, etc.) that do not depend on the wireless network, and the second PDF located in the ASN uses the intermediate output variables. The final output variable can be generated for the wireless network. Of course, there may also be parameters (eg bandwidth) where the intermediate and final output variables match. This multi-level PDF can be usefully applied for handover or roaming between operators using networks between different networks or using different wireless technologies.

Meanwhile, while the above-described embodiments are described as the AAA server requesting the DSA trigger to the control station, in another embodiment, the system manager (WSM) may request the DSA trigger to the control station. Since the system manager does not manage user classes on its own, the DSA & QoS profiles cannot be managed differently for each user class. However, since it is possible to know whether the terminal is a mobile terminal or a fixed terminal through the registration procedure (MS_init REG) during initial access, the number of DSAs and the QoS profile may be differently allocated.

In another embodiment, a static OoS setup may be integrated in a policy server (PDF) that determines QoS policies. That is, upon initial access, the AAA server (or SPR) triggers the policy server after the authentication procedure, or after the terminal IP assignment, the control station (ASN_GW) triggers the policy server to perform at least one per-flow allowed to the corresponding terminal. QoS setting may be performed by transmitting QoS information and CS rules to the control station. In general, the policy server does not manage the terminal identifier, so it should contact another NE (eg AAA or SPR). Because terminal IP address is dynamically assigned, it is managed by HA (Home Agent), but it is difficult to manage in SPR linked with Policy Server and NAI is easy to manage in SPR. Is expected to be used as the terminal identifier.

Hereinafter, the active state in the awake mode, the sleep mode, the idle mode and the per-flow mode in the per-user mode, the admitted Let's take a look at how to operate state, provisioned state together.

The active state refers to a state in which CAC passes and is assigned a SFID (Service Flow IDentifier), a TCID (Traffic Connection IDentifier), and a radio resource. The permission state means a state in which SFID and TCID are allocated and a radio resource is reserved, but a radio resource is not allocated. In addition, the ready state means that the SFID is allocated but the TCID is not allocated, and only the QoS parameters and CS rule information are maintained. Here, resources reserved only and not allocated may be used for best effort flows.

You can manage timers for state transitions (Active-> Admitted, Active-> Provisioned, Admitted-> provisioned) for all flows.

The state of each service flow is operated as follows according to the user mode. When the terminal is in the awake mode, the state of the service flow operates as described above. When the terminal is in the sleep mode, the flow in the active state during the sleep period is only resource reservation, not allocated, it may allocate resources during the listening (listening) period. When the terminal is in the idle mode, it stores the per-flow state in the awake mode and releases all reserved or allocated resources. When transitioning from the idle mode to the awake mode or the sleep mode, the flow returns to the existing flow-specific state that stores the states of the flows, and performs the CAC when the existing flow-specific state is active or allowed. At this time, for the service flow that is not granted, both the system and the terminal transition to the ready state without the DSC procedure.

Meanwhile, the sleep mode may allow transmission of bearer traffic at a communication interval.

7 illustrates an operation procedure of a terminal in a broadband wireless access system according to an embodiment of the present invention.

Referring to FIG. 7, the terminal first checks whether initial access is necessary in step 701. If the initial access is required, the terminal proceeds to step 703 to perform an initial network entry procedure. Here, the initial network entry procedure may include a ranging procedure, a basic capability negotiation procedure, an authentication procedure, and a registration procedure.

After completing the initial network entry procedure, the terminal checks whether the DSA-REQ message is received from the base station in step 705. Here, it is assumed that the terminal is fixedly assigned a service flow. That is, the DSA-REQ message includes a QoS parameter set for each of the fixedly allocated service flows.

When the DSA-REQ message is received, the terminal obtains a QoS profile (a QoS parameter set for each service flow) from the DSA-REQ message in step 707 and generates a QoS service flow according to the QoS profile.

After generating the QoS service flow as described above, the terminal performs the remaining DSA procedure (DSA-RSP / DSA-ACK) with the base station in step 709. As such, the terminal is assigned a fixed service flow through the initial connection.

In step 711, the terminal checks whether a QoS change is required by the user. Here, the QoS change may be performed not only when the service flow is in the ready state but also when it is in the active state. If the QoS change is required, the terminal performs a DSC procedure with the base station in step 713 to change the QoS and returns to step 711. In this case, whether to allow the QoS change information requested by the terminal is determined by the network entity having the base station and the PDF, and the QoS may be changed according to the determination result.

In step 715, the terminal checks whether activation of a service flow is required. If activation of the service flow is required, the terminal proceeds to step 717 to perform a DSC procedure with the base station, transitions the service flow to an active state, and returns to step 711. In other words, a TCID is allocated from a base station through a DSC procedure and traffic is communicated through the TCID.

In operation 719, the terminal checks whether a transition to the ready state of the active service flow is required. Typically, when the terminal transitions to the idle mode, all the active flows may transition to the ready state. As another example, the timer may be driven while there is no traffic flow for the active flow, and when the timer expires, the service flow of the active state may be shifted to the ready state. As such, when the transition to the ready state is required, the terminal proceeds to step 721 to perform a DSC procedure with the base station, transitions the corresponding service flow to the ready state, and returns to step 711.

In operation 723, the terminal checks whether service flow deletion is required. If the service flow deletion is required, the terminal proceeds to step 725 and performs a DSD procedure with the base station to delete the service flow and returns to step 711.

8 is a flowchart illustrating an operation procedure of a base station in a broadband wireless access system according to an embodiment of the present invention.

Referring to FIG. 8, the base station first checks in step 801 whether a DSA trigger request for a specific terminal is received from a control station. Here, the DSA trigger request message includes an identifier (SFID) of a service flow fixedly allocated to the terminal and a PDF input variable (user class ID or service profile ID) for finding a QoS profile.

When the DSA trigger request is received, the base station proceeds to step 803 to obtain the required QoS profile from the PDF mapping table using the input variable. That is, a QoS parameter set for each SFID is obtained. In step 805, the base station generates the DSA-REQ message with the obtained QoS profile and transmits the generated DSA-REQ message to the terminal. In step 807, the base station performs a remaining DSA procedure (DSA-RSP / DSA-ACK) to allocate a fixed service flow to the terminal.

In step 809, the base station checks whether a QoS change is required by a current system state or a request of a counterpart terminal. Here, the QoS change may be performed not only when the service flow is in the ready state but also when it is in the active state. If the QoS change is required, the base station performs connection acceptance control with the QoS change information in step 711, and if the connection is accepted, returns to step 809 after changing the QoS by performing a DSC procedure with the terminal. In this case, whether to use QoS change is determined by the network entity having the base station and the PDF, and may change the QoS parameter according to the determination result.

In step 813, the base station determines whether activation of a service flow is required. For example, when a call is received to the terminal, the corresponding service flow should be activated. If activation of the service flow is required, the base station proceeds to step 815 and performs a DSC procedure with the terminal to transition the service flow to an active state and returns to step 809. In other words, a TCID is allocated to the terminal through a DSC procedure and traffic is communicated through the TCID.

In addition, the base station determines whether a transition to the ready state of the active service flow is required in step 817. Typically, when the terminal transitions to the idle mode, all the active flows may transition to the ready state. As another example, the timer may be driven while there is no traffic flow for the active flow, and when the timer expires, the service flow of the active state may be shifted to the ready state. As such, when the transition to the ready state is required, the base station proceeds to step 819 and performs a DSC procedure with the terminal to transition the service flow to the ready state and returns to step 809.

In addition, the base station checks whether a service flow deletion is required in step 821. If the service flow deletion is required, the base station proceeds to step 823 and performs a DSD procedure with the terminal to delete the service flow and returns to step 809.

So far, the overall operation procedure for semi-dynamic QoS configuration in a broadband wireless access communication system has been described. Hereinafter, an internal block configuration of a terminal and a base station for semi-dynamic QoS setting will be described. Since the terminal and the base station having the same interface module (communication module) have the same block configuration, the following describes the configuration of the terminal and the base station with the apparatus shown in FIG.

9 shows the configuration of a terminal (base station) in a broadband wireless access system according to an embodiment of the present invention.

As shown, the terminal (base station) according to the present invention, the control unit 900, the transmission modem 902, the RF transmitter 904, the duplexer 906, the RF receiver 908, the reception modem 910, flow A state manager 912, a timer manager 914, and a QoS information storage unit 916 are configured.

First, the terminal is as follows.

The transmission modem 902 includes a channel code block, a modulation block, and the like, and outputs a baseband modulated message from the controller 900. The channel code block includes a channel encoder, an interleaver, a modulator, and the like, and the modulation block is an IFFT (Inverse Fast Fourier Transform) for loading transmission data on a plurality of orthogonal subcarriers. ) May be configured as an operator. In consideration of an OFDM system, in the case of a CDMA system, the IFFT operator may be replaced with a code spreading modulator.

The RF transmitter 904 includes a frequency converter, an amplifier, and the like, and converts the baseband signal from the transmission modem 902 into a signal in a radio frequency (RF) band. The duplexer 906 transmits a transmission signal (uplink signal) from the RF transmitter 904 through an antenna according to a duplexing scheme, and provides a received signal (downlink signal) from the antenna to the RF receiver 908. do. The RF receiver 908 includes an amplifier, a frequency converter, and the like. The RF receiver 908 converts an RF band signal passing through a radio channel into a baseband signal and outputs the baseband signal.

The reception modem 910 includes a demodulation block, a channel decoding block, and the like, and baseband demodulates and outputs a signal from the RF receiver 908. Here, the reception modem 910 is composed of an FFT operator for extracting data carried on each subcarrier, and the channel decoding block is composed of a demodulator, a deinterleaver, a channel decoder, and the like. Can be.

The controller 900 performs overall processing and control for the QoS service. According to the present invention, the control unit 900 obtains a QoS profile (the QoS parameter set for each service flow) from the DSA-REQ message received from the base station upon initial access, and sets the QoS service flow according to the QoS profile. In addition, the control unit 900 stores the QoS profile in the QoS information storage unit 916.

Meanwhile, when service activation is required, the controller 900 performs a DSC procedure with the base station to transition the corresponding service flow to an active state. In addition, when the QoS change of the service flow is required, the controller 900 performs a DSC procedure with the fraudulent base station to change the QoS of the corresponding service flow. In addition, when the transition to the ready state of the active service flow is requested, the control unit 900 performs a DSC procedure with the base station to transition the corresponding service flow to the ready state. When the deletion of the service flow is required, the controller 900 performs a DSD procedure with the base station to delete the corresponding service flow.

The flow state manager 912 manages a state for each of the fixedly assigned service flows. The state of the service flow may be divided into an active state, a provisioned state, and an admitted state. The timer manager 914 operates a timer necessary for managing the state of the service flows. That is, the timer manager 914 drives the timer under the control of the flow state manager 912, and notifies the flow state manager 912 when the timer expires. Then, the flow state manager 912 performs a state transition according to the expiration of the timer. For example, if there is no traffic flow for an active service flow, the timer may be driven. If there is no traffic flow until the timer expires, the active service flow may transition to a ready state flow. . Of course, in order to transition the active flow to the ready state, the terminal transitions to the ready state after performing a DSC procedure with the base station.

Next, look at the base station as follows.

Since the functions and operations of the transmission modem 902, the RF transmitter 904, the duplexer 906, the RF transmitter 908, and the receiver modem 910 are the same as those of the above-described terminal, a detailed description thereof will be omitted.

The QoS information storage unit 916 manages a QoS profile received from the policy server or another network entity (PDF mounted) in the form of a mapping table.

The flow state manager 912 manages a parameter set for each service flow assigned to each terminal and a state for each service flow assigned to each terminal. The state of the service flow may be divided into an active state, a provisioned state, and an admitted state. The timer manager 914 operates a timer necessary for managing the state of the service flows. That is, the timer manager 914 drives the timer under the control of the flow state manager 912, and notifies the flow state manager 912 when the timer expires. Then, the flow state manager 912 performs a state transition according to the expiration of the timer.

The controller 900 performs overall processing and control for the QoS service. When a DSA trigger request for a specific terminal is received from a control station, the controller 900 obtains a QoS parameter set for each service flow assigned to the terminal using the PDF mapping table of the storage unit 916. And a DSA-REQ message is generated with the parameter set of each service flow obtained and transmitted to the terminal. As such, the controller 900 allocates a QoS service flow to a terminal through a DSA procedure, and stores information on the service flow assigned to the terminal in the flow state manager 912.

Meanwhile, when flow activation is required, the controller 900 transitions the corresponding service flow to the active state by performing a DSC procedure with the corresponding terminal. When the QoS change of the service flow is required, the controller 900 performs a DSC procedure with the corresponding terminal to change the QoS of the corresponding service flow. In addition, when the transition to the ready state of the active service flow is requested, the control unit 900 performs a DSC procedure with the terminal to transition the service flow to the ready state. When the deletion of the service flow is required, the controller 900 performs a DSD procedure with the corresponding terminal to delete the corresponding service flow.

Meanwhile, the above-described embodiment of the present invention has been described as setting a QoS parameter set for each service flow. In another embodiment, a QoS parameter set may be set differently according to a data type even within a service flow. For example, among various types of data transmitted through one service flow, there is data that should not be lost because it is relatively important. In this case, since a relatively high level of QoS must be guaranteed for important data, it is necessary to set QoS levels differently for each data type. As another example, there may be multiple sessions (voice, video, etc.) in one service flow. In this case, it is necessary to set QoS differently for each session.

As such, when the QoS parameter set is set for each data type, the parameter set for each data type may be recorded in a corresponding message (eg, DSA-REQ) in an array form. In this case, the first array may be provided in full as a reference QoS parameter set, and the remaining arrays may record only parameters different from the reference QoS parameter set. In addition, if there are QoS parameters (eg, whether TEK is applied or HARQ retransmission) separately applied for each data type in addition to the QoS parameters that are commonly applied, these QoS parameters may be separately recorded for each data type.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

1 is a diagram illustrating a network configuration according to an embodiment of the present invention.

2 illustrates a QoS setting procedure in a wireless network according to an embodiment of the present invention.

3 is a diagram illustrating a QoS setting procedure in a wireless network according to another embodiment of the present invention.

4 is a diagram illustrating a QoS setting procedure in a wireless network according to another embodiment of the present invention.

5 is a diagram illustrating a QoS setting procedure in a wireless network according to another embodiment of the present invention.

6 is a diagram illustrating a QoS setting procedure in a wireless network according to another embodiment of the present invention.

7 is a diagram illustrating an operation procedure of a terminal in a broadband wireless access system according to an embodiment of the present invention.

8 is a diagram illustrating an operation procedure of a base station in a broadband wireless access system according to an embodiment of the present invention.

9 is a diagram illustrating a configuration of a terminal (base station) in a broadband wireless access system according to an embodiment of the present invention.

Claims (25)

A method of setting quality of service (QoS) in a wireless communication system, During the initial access, the terminal receives a QoS profile from the base station and sets up at least one fixed service flow; When the QoS change of the service flow is required, transmitting, by the terminal, a service change request message including QoS change information to the base station; And determining, by the base station, whether the service change request is granted, and if so, transmitting a service change response message to the terminal to change the QoS. The method of claim 1, wherein the QoS change process, Upon reception of the service change request message, the base station performing connection admission control; When the connection is accepted, transmitting, by the base station, the service change response message to the terminal; And reporting, by the base station, the changed QoS information to the control station. The method of claim 1, wherein the QoS change process, A process of the control station receiving and storing allowance information of QoS information from a network entity (NE) including a PDF; Upon reception of the service change request message, the base station performing connection admission control; When the connection is accepted, transmitting, by the base station, the QoS change information to the control station; Determining, by the control station, whether the QoS change information exists within the allowable range, and if the control station exists within the allowable range, transmitting a response to allow the QoS change to the base station; Receiving, by the base station, the service change response message to the terminal. The method of claim 1, wherein the QoS change process, Upon reception of the service change request message, the base station performing, by the base station, connection admission control; When the connection is accepted, transmitting, by the base station, the QoS change information to a policy server; Determining, by the policy server, whether the QoS change information exists within an allowable range, and transmitting a response allowing the OoS change to the base station if the QoS change information exists within an allowable range; Receiving, by the base station, the service change response message to the terminal. The method of claim 1, wherein the QoS change process, An authentication server performing authentication on the terminal and triggering a policy server; Transmitting, by the policy server, an allowable range for QoS information of the terminal to a control station; Upon reception of the service change request message, the base station performing, by the base station, connection admission control; When the connection is accepted, transmitting, by the base station, the QoS change information to the control station; Determining, by the control station, whether the QoS change information exists within the allowable range, and if the control station exists within the allowable range, transmitting a response to allow the QoS change to the base station; Receiving, by the base station, the service change response message to the terminal when the response is received. The method of claim 1, wherein the QoS change process, An authentication server performing authentication on the terminal and transmitting a PDF input parameter to a control station; Generating, by the control station, an allowance range for QoS information of the terminal using the PDF input parameter; Upon reception of the service change request message, the base station performing connection admission control; When the connection is accepted, transmitting, by the base station, the QoS change information to the control station; Determining, by the control station, whether the QoS change information exists within the allowable range, and if the control station exists within the allowable range, transmitting a response to allow the QoS change to the base station; Receiving, by the base station, the service change response message to the terminal. The method of claim 6, And the PDF input parameter is a user class ID or a service profile identifier. The method of claim 1, The QoS profile comprises at least one Service Flow IDentification (SFID) and a QoS parameter set for each SFID. The method of claim 1, The QoS profile may include, for each service flow, IP QoS parameters, parameters for MAC QoS, parameters indicating whether the IP header is compressed and compressed, parameters indicating whether or not to use a traffic encryption key (TEK), and a pre-free ratio. Parameters indicating whether or not to be pre-provisioned, parameters for selecting provisioned / admitted / active, parameters indicating whether to allow QoS changes using Dynamic Service Change (DSC), Parameters that specify the number of QoS changes, parameters that specify how to handle QoS parameters that are not exchanged through DSC, parameters that specify required reliability, parameters that specify call release conditions, parameters that specify retransmission delays, serving A parameter, symmetric Q, that specifies how to handle when the number of active mode users on a flag exceeds the threshold. parameters to indicate whether oS flows are provided, parameters to specify the maximum allowable number of DSC usages, parameters to allow and to allow a flow timer, parameters to indicate horizontal handover, and parameters to indicate vertical handover. And at least one of parameters indicating whether to allow dynamic service delete (DSD). The method of claim 1, wherein the service flow setting process comprises: Performing an initial access procedure between the terminal and the base station; During the initial access procedure, an authentication server performing authentication on the terminal and requesting a service addition trigger to a control station; Generating, by the control station, an identifier of a service flow fixedly allocated to the terminal, and transmitting a service flow identifier and a PDF input variable to a base station to request a service addition trigger; Obtaining, by the base station, a QoS profile from a policy decision table (PDF) mapping table using the PDF input variable, and transmitting a service addition request message including the QoS profile to the terminal; Setting, by the terminal, at least one fixed service flow using the QoS profile, and transmitting a service addition response message to the base station in response. The method of claim 10, When the authentication server requests a service addition trigger, the authentication server transmits one of a user class ID for the terminal, QoS identifiers of service flows assigned to the terminal, and a QoS parameter set of service flows assigned to the terminal to the control station. Providing a method. The method of claim 10, And the control station obtains a QoS identifier of a service flow assigned to the terminal from a PDF mapping table using a user class ID from the AAA server or a subscription profile repository (SPR) server. The method of claim 1, When the QoS change of the service flow is required, transmitting, by the base station, a service change request message including QoS change information to the terminal; And by the terminal, changing a QoS of a corresponding service flow according to the service change request message, and transmitting a service change response message to the base station in response. The method of claim 1, If there are a plurality of data types in one service flow, a method for setting a QoS parameter for each data type. The method of claim 1, Wherein each of the at least one fixed service flow is managed in one of an active state, an admitted state, and a provisioned state. In the QoS setting method in a wireless communication system, At the time of initial access, the terminal setting up at least one fixed service flow; When the state transition of the service flow is required, transmitting, by the terminal, a SIP message to an IMS server; Sending, by the IMS server, a DSC trigger request to a control station, and transmitting, by the control station, the DSC trigger request to a base station; And determining, by the base station, whether the DSC is allowed, and if so, transmitting a service change response message to the terminal. In the QoS setting method in a wireless communication system, In the initial connection, the terminal, the process of setting at least one fixed service flow, When the state transition of the service flow is required, transmitting, by the terminal, a SIP message to an IMS server; Transmitting, by the IMS server, a SIP response message for checking authorization and informing that the terminal is allowed; Transmitting, by the application layer of the terminal, a DSC request to the base station by triggering a MAC layer; And determining, by the base station, whether the DSC is allowed, and if so, transmitting a DSC response message to the terminal to transition the state of the service flow. In a wireless communication system, Receiving a QoS profile from the base station upon initial access to establish at least one fixed service flow, and when the QoS change of the service flow is required, the terminal for transmitting a service change request message including QoS change information to the base station; And the base station for determining whether the service change request is granted by itself or in association with another network entity, and if so, transmitting a service change response message to the terminal. The method of claim 16, The base station performs a connection admission control in response to the service change request message, and if the connection is accepted, the system characterized in that for transmitting the service change response message to the terminal. The method of claim 16, Receives and stores tolerance information of QoS information from a network entity including a PDF, determines whether the QoS change information exists within the tolerance range, and transmits a response allowing the QoS change to the base station if it exists within the tolerance range. Further comprising a control station. The method of claim 16, And a policy server that determines whether the QoS change information exists within an allowable range and transmits a response allowing the QoS change to the base station when present within the allowable range. The method of claim 16, An authentication server for performing authentication on the terminal and triggering a policy server upon successful authentication; A policy server that transmits an allowable range for QoS information of the terminal to a control station in response to the trigger; And a control station that determines whether the QoS change information exists within the allowable range and transmits a response allowing the QoS change to the base station if present within the allowable range. The method of claim 16, An authentication server for performing authentication on the terminal and transmitting PDF input parameters to the control station upon successful authentication; Generates an allowance range for the QoS information of the terminal by using the PDF input parameter, determines whether the QoS change information exists within the allowable range, and if it exists within the allowable range, sends a response to the base station to allow the QoS change. And a control station for transmitting. The method of claim 16, The QoS profile includes at least one Service Flow IDentification (SFID) and a QoS parameter set for each SFID. The method of claim 16, The QoS profile may include, for each service flow, IP QoS parameters, parameters for MAC QoS, a parameter indicating whether the IP header is compressed and a compression scheme, a parameter indicating whether a traffic encryption key (TEK) is used, and a pre-free ratio. Parameters indicating whether or not to be pre-provisioned, parameters for selecting provisioned / admitted / active, parameters indicating whether to allow QoS changes using Dynamic Service Change (DSC), Parameters that specify the number of QoS changes, parameters that specify how to handle QoS parameters that are not exchanged through DSC, parameters that specify required reliability, parameters that specify call release conditions, parameters that specify retransmission delays, serving A parameter that specifies how to handle a user if the number of active mode users on the flag exceeds the threshold, symmetric. Parameters indicating whether or not QoS flows are provided, parameters specifying the maximum allowable number of DSC usages, parameters allowing or not the flow timer, parameters indicating whether or not horizontal handover is possible, and parameters indicating whether vertical handover is possible And at least one of parameters indicating whether to allow a dynamic service delete (DSD).

Images