KR20090015826A - Apparatus and method for managing qos of service flow in wireless communication system - Google Patents

Abstract

A service quality management apparatus of a service flow and a method thereof in a wireless telecommunications system for reducing a whole transmission delay for a QOS call process and increasing the processing capacity are provided to perform a CAC(Connection Admission Control) according to a QoS(Quality of Service) policy when performing QCS(Quick Connection Setup), HHO(Hard handover) and FBSS(Fast Base Station Switching). When entering initial network, a terminal performs an authentication process with a base station(201). An AAA server transmits QoS policy information about the terminal to ASN(203). The base station stores QoS policy information from the AAA server(205). A QoS service flow is produced by interworking with ASN(Access Service Network) and CSN(Core Service Network). Traffic communications is performed through the QoS service flow(207). The terminal inspects whether an idle timer is expired(209).

Description

Apparatus and method for managing service quality of service flow in wireless communication system {APPARATUS AND METHOD FOR MANAGING QoS OF SERVICE FLOW IN WIRELESS COMMUNICATION SYSTEM}

The present invention relates to an apparatus and method for managing quality of service (QoS) of service flows in a wireless communication system, and more particularly, to an apparatus and method for managing QoS when re-establishing a connection for a pre-allocated service pulley. It is about.

Here, the situation of establishing a connection again for the pre-allocated service flow is, for example, when the terminal performs Quick Connection Setup (QCS) or hard handover (HHO). Or when performing Fast Base Station Switching (FBSS). The fast base station switching is called soft handover in other terms, and the fast connection setup is called network reentry in other terms.

Recently, the demand for services with different traffic characteristics, for example, various multimedia application services such as Voice of IP (VoIP), real-time game, and Video on Demand (VoD) Is increasing. 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. In addition, 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 only standardized in MAC (Media Access Control) layer QoS interworking procedure, interworking procedure with the network to guarantee end-to-end QoS that the user experiences Is not provided. In other words, the IEEE 802.16 series in charge of PHY (PHYsical) / 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.

To improve the quality of service experienced by users, end-to-end QoS of the 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.

In particular, the current standard is a per-flow mode (per-flow) of service flows (SFID-allocated flows) managed by the terminal when performing Quick Connection Setup (QCS) or Hard Handover (HHO) or Fast Base Station Switching (FBSS). There is no operation plan for the mode. This may cause a phenomenon in which a call (connection) is disconnected according to the result of Connection Admission Control (CAC) when the radio network resources are congested, and the resource may be wasted due to inefficient radio resource management.

Accordingly, an object of the present invention is to provide an apparatus and method for managing QoS of a service flow in a wireless communication system.

Another object of the present invention is to provide an apparatus and method for managing QoS when re-establishing a connection for a pre-assigned service flow in a wireless communication system.

Another object of the present invention is to provide an apparatus and method for processing a QCS according to a QoS policy of a terminal in a wireless communication system.

Another object of the present invention is to provide an apparatus and method for processing handover according to a QoS policy of a terminal in a wireless communication system.

Another object of the present invention is to provide an apparatus and method for processing base station switching according to a QoS policy of a terminal in a wireless communication system.

According to an aspect of the present invention for achieving the above object, in the method of operating a base station in a wireless communication system, by receiving the QoS policy information of the terminal or user authentication successful from a network entity (NE: Network entity) including a PDF Storing, and if a network reentry of an idle mode terminal is detected, checking a QoS policy of the terminal or the user, and controlling a state of a service flow set for the terminal or the user according to the QoS policy. Characterized in that.

According to another aspect of the present invention, in a method of operating a base station in a wireless communication system, a process of receiving and storing QoS policy information of a terminal performing a hard handover from an adjacent base station, and when a hard handover of the terminal is detected, And checking the QoS policy information of the terminal and controlling a state of a service flow set in the terminal according to the QoS policy.

According to still another aspect of the present invention, in a method of operating a base station in a wireless communication system, receiving a request message including QoS policy information of a soft handover terminal from an adjacent base station, analyzing the request message and Checking the QoS policy information of the terminal, assigning a TCID to the service flow of the terminal according to the QoS policy, and transmitting a response message including the assigned TCID to the neighbor base station. It features.

According to still another aspect of the present invention, in a base station apparatus in a wireless communication system, a storage unit for storing QoS policy information of a terminal, a state manager for managing an operation mode and a service flow state for each terminal, A timer manager that manages a timer required for an operation mode transition and a state transition of the service flow; and transitions an operation mode or a service flow state of a corresponding terminal when the timer expires, and when a reconnected terminal is detected, according to a QoS policy of the terminal. And a control unit for controlling a state of a service flow set to the terminal.

As described above, the present invention proposes a QCS, HHO, and FBSS processing scheme for QoS service flows that are not standardized in the current standard. According to the present invention, by performing CAC at the base station according to the QoS policy when performing QCS, HHO and FBSS, it is possible to prevent call disconnection and waste of radio resources and to prevent malfunction due to flow mismatch between the base station and the terminal. have. In addition, since the present invention utilizes the existing call processing interface as it is and minimizes the information transfer of each interface, it is possible to reduce the overall transmission delay for QoS call processing and increase the processing capacity.

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 with respect to QoS operations when performing QCS (or network reentry) or HHO (Hard handover) or FBSS (or soft handover) in a broadband wireless access system.

In the following description, the name of a network entity (NE: Network Entity or Network Element) is defined according to a corresponding function, and may vary according to the intention of the standardization group or the operator. For example, the base station may be 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.

Prior to the description, the assumptions according to the present invention will be described.

First, it is assumed that the flow-specific QoS profile information (or QoS parameter set) is transmitted to the corresponding NE when the UE moves the serving BS or the anchor (or FA responsible) control station ASN_GW in the awake mode. do. In addition, per-user QoS information is continuously managed by the anchor control station, and the QoS profile information is released when the corresponding UE transitions to the null mode.

In all wireless networks, the number of awake users is limited due to the limited wireless capacity, and even in the case of supporting the sleep mode, the number of sleep users may be limited for reasons such as CID resource management. Similarly, the idle mode may also limit the number of idle users for reasons such as CS (ClasSification) rules and QoS profile information management. In general, when the transition from the idle mode to the awake mode through the QCS, the base station delivers a SFID vs TCID (Service Flow IDentifier vs Transport Connection IDentifier) to the terminal through a ranging response (RNG_RSP: Ranging response) message, Since the terminal already has SFID information, the connection can be established by mapping the TCID to the SFID. In the case of a hard handover (HHO), the terminal updates the TCID through a ranging response message after handing over to the target base station. In the case of soft handover (FBSS), candidate target base stations of a diversity set generate TCIDs and transmit them to a serving base station, and the serving base station transmits TCIDs of the candidate target base stations to a handover response ( HO_RSP) message is transmitted to the terminal. Accordingly, when the terminal determines the handover target base station, it may be automatically assigned the TCID of the target base station.

It is assumed that SFID, which is a name tag of the MAC layer, is independently assigned at the control station (ACR), and CID is independently assigned at the base station (BS). The CID may be uniquely allocated for each flow in the base station, but the SFID may be unique for each flow in the terminal.

In addition, it is assumed that the state of each flow is classified into a provisioned state, an admitted state, and an active state. Here, the ready state indicates a state in which only an SFID is allocated, and the permission state and the active state indicate a state in which not only the SFID but also a traffic CID (TCID) are allocated. At this time, if traffic flows to the TCID, it may be defined as an active state.

In addition, in the following description, Connection Admission Control (CAC) includes not only a negotiated CAC based on wireless capacity and bandwidth request per flow, but also a CAC by overload control by CPU load, subscriber number and flow number limitation. It means. For example, when selecting a handover candidate base station, it must pass subscriber limit and overload control to be selected as a candidate base station.

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) server 150 and a system manager (WSM: WiBro System Manager) is configured to include. 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 an internal function of a specific network entity (eg, AAA server) 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 provides information about the terminal to the policy server 140 when the terminal is successfully authenticated. In another embodiment, a subscription profile repository (SPR) server that manages user information is triggered by the AAA server 150 to deliver information about the terminal to the policy server 140, or conversely, the policy server 140 sends the SPR server to the SPR server. By request, information about the terminal can be obtained. Here, the information on the terminal is a PDF input parameter, 5 tuple (source & destination IP address, source & destination port number, protocol ID) or 6 tuple (5 tuple + ToS (Type of service), user class (eg Premium, Gold , Silver, bronze, etc.), a QoS setup type, and the like.

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. The AAA server 150 and the ASN may use a common open policy service (COPS), a radius (RADIUS), or a diameter (diameter) interface.

As mentioned above, user information may be managed in a subscription profile repository (SPR) server (not shown). That is, the SPR server may manage user classes, QoS setup types (eg, static, dynamic, semi-dynamic, etc.), user location, and the like. In this case, the user class ID and QoS setting type are provided from the SPR server to the policy server 140. The function of the SPR server may be included in the AAA server or another server, or exist as a separate server.

The policy server 140 generates a PDF output parameter using a PDF input parameter from an IMS server or an SPR server, and provides the generated PDF output parameter to a corresponding NE. The PDF output parameter according to the present invention is a parameter related to the QoS policy applied when performing QCS or HHO or FBSS, and will be described in detail later with reference to <Table 1>. The policy server 140 transmits QoS policy information for the terminal which is successfully authenticated to the ASN to which the terminal is connected.

 Here, a common open policy service (COPS), a radius (RADIUS), or a diameter (diameter) interface may be used between the policy server 140 and the ASN. Here, PDF (Policy Decision Funtion) and charging (charging) of the policy server 140 can be implemented as one function, such a function can be defined as a PCRF (Policy Charging Rule Function). The PDF may be implemented in an Internet Multimedia Subsystem (IMS) server or may exist as a separate server as shown in FIG. 1. For example, PDF and Proxy-Call Session Control Function (P-CSCF) may be mounted on one server, and Interrogating-CSCF (I-CSCF) and Serving-CSCF (S-CSCF) may be mounted on another server. . In addition, the PDF function may be separated into several steps and exist in different NEs. That is, the PDF and the SPR of the policy server 140 may exist in the AAA server 150, may exist as separate servers, and the SPR and the PDF may be implemented as one server. In the following description, it is assumed that both PDF and SPR exist in the AAA server 150.

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. Here, a common open policy service (COPS), a radius (RADIUS), or a diameter (diameter) interface may be used between the system manager 160 and the ASN.

The control station 130 transmits the traffic from the core network (CSN: Core Service 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. For example, in the case of static QoS, 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, and the service The flow identifier (SFID) is transmitted to the base station 120 to request a 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. For example, in the case of fixed QoS, when DSA triggering is requested from the control station 130, the base station 120 uses the service profile identifier from the control station 130 to obtain QoS parameters from the QoS mapping table. Acquire and perform a DSA procedure with the terminal with the QoS parameter. Here, the QoS mapping table may be provided in a specific NE in the ASN. In general, a QoS mapping table is provided in the control station 130, and may be provided in both the base station 120 and the control station 130 as another example. In this way, a service flow is generated through a DSA procedure, and is performed through an active DSA procedure or a DSC procedure of an actual service flow. When the service flow is activated in the allowed or active state, the base station performs CAC to allocate a traffic connection identifier (TCID), and communicates traffic using the TCID.

In addition, according to the present invention, the base station 120 performs QoS policy information (per-flow QoS parameter, CS rule, domain) or MVNO (mobile virtual network operator) for a terminal successfully authenticated from the AAA server 150. Per-user QoS parameters including an identifier and an idle timer for each user), and the like, and control the QCS or the HHO or FBSS of the terminal according to the stored QoS policy information. For example, when the UE performs QCS, it determines whether to perform CAC according to the QoS policy. When performing CAC, the base station returns the service flows to the previous state through the CAC. In addition, the base station may process flows not returned to the previous state according to the QoS policy. QoS operation schemes when performing the QCS or HHO or FBSS will be described in detail later with reference to the accompanying drawings.

On the other hand, the ASN manages both the per-user mode and the status of each service flow. In this case, the user-specific mode may represent, for example, an awake mode, a sleep mode, and an idle mode, and the service per-flow state may be an active state, a permission ( Indicates an admitted state and a provisioned state. For example, when a terminal fixedly allocated a service flow transitions to an idle mode, only a service flow ID (SFID) and QoS profile information may be maintained for the terminal. When the UE transitions to the awake mode through the QCS (Quick Connection Setup) in the idle mode, the base station performs the CAC according to the QoS policy (per-user QoS information), and when passing the CAC "SFID vs TCID" The terminal transmits the ranging response (RNG-RSP) message to the terminal. At this time, since the terminal already has the SFID and QoS information, it manages by mapping the TCID to each SFID. In addition, the network between the control station 130 and the base station 120 may be configured as an L2 (layer 2: Ethernet) network or L3 (layer 3: IP) network as shown.

The terminal 110 performs a DSA procedure with the base station 120 to generate a QoS service flow. If the QoS of the service flow of the semi-dynamic QoS (dynamic QoS) or dynamic QoS (dynamic QoS) type is required, the terminal 110 may change the QoS parameter by performing a DSC procedure with the base station 120. .

Even if the UE in the awake mode or the sleep mode moves to another subnet in the same ASN, the anchor control station (or FA control station) is not changed. In this case, per-flow QoS profile information for the terminal is delivered to a new serving base station through tunneling or L2 extension. In addition, it is assumed that per-user QoS information of the terminal is continuously managed by the anchor control station. Of course, when the transition to the null mode, the ASN releases all QoS policy information of the terminal. It is assumed that the ASN is shifted, that is, in case of inter-ASN, the anchor control station is relocated.

Although not shown in FIG. 1, network entities (DHCP (Dynamic Host Configuration Protocol), HA (Home Agent), FA (Forign Agent)) and the name of the network entity (NAI: Network Access) for allocating an IP address to the UE It is obvious that a DNS (Domain Name Server) server, which manages the mapping relationship between an identifier and an IP address, 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 can be 5tuple (source & destination IP address, source & destination port number, protocol ID) or 6tuple (5tuple + ToS (Type of service), user class (e.g. Premium, Gold, Silver, Bronze, etc.), QoS configuration type (eg, static, dynamic, semi-dynamic, etc.) Here, 5 tuples and 6 tuples are used to distinguish flows, so they are in charge of CS (ClasSification) rules. MUST be delivered to an NE (eg ASN_GW).

Next, PDF output parameters may be defined as QoS parameter sets (sets) for IP QoS (eg DiffServ Code Point (DSCP)) 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 per-user QoS information as shown in Table 1 in addition to the PDF output parameter defined above.

TABLE 1

parameter Explanation QCS Whether the service flow returns to its previous state Manage all provisioned if not in previous state When returning to the previous state, take measures for flows not allowed in CAC 1. Complete the QCS with the non-returned flows ready 2. Process the QCS failure 3. Proceed with CAC until all flows are returned 4. Perform load balancing Status for flows granted by CAC 1. active state 2. admitted state HHO CAC at target base station Assign TCID to Active and Allowed Flows Without CAC In case of performing CAC, measures for flows not allowed in CAC 1. Manage unlicensed flows in the ready state. 2. Continue the CAC. 3. Clear flows not allowed in the CAC by not updating the CID. 4. Load balancing FBSS Candidate base station performs CAC If no CAC is performed, assign TCID to active and allowed flows (reserved resources) Processing method for flows without a TCID assigned to the target base station 1. In the case of static QoS, the flow transitions to the ready state (can perform CAC for the set timer time) 2. In the case of dynamic, the flow is deleted (automatically deleted or deleted through DSD)

Table 1 shows QoS information for each user according to the present invention. In addition, parameters indicating whether the IP header is compressed and compressed as a PDF output parameter, parameters indicating whether the TEK (Traffic Encryption Key) is used, and pre-prevision (Pre-Provisioned) parameter, parameter for selecting provisioned / admitted / active, parameter indicating whether or not to allow QoS change using Dynamic Service Change (DSC), QoS in active state Parameters that specify the number of 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 schemes, and serving stations Parameter, symmetric QoS, that specifies how to handle when the number of active mode users in a threshold exceeds the threshold Parameters to indicate row availability, parameters to specify the maximum allowable number of DSC uses, parameters to allow and allow flow timers, parameters to indicate horizontal handover, and to enable vertical handover Parameters indicating whether or not, parameters indicating whether to allow a dynamic service delete (DSD) may be included.

When DSC occurs, the local policy can be set to PDF (e.g., AAA or PCRF or USI (Universal) so that the base station controller's A-PCEF (Policy and Charging Enforcement Function) can make its own decisions without asking the CSN for permission. Service Interface (Server) or EMS) can be overlooked by ASN. For example, the ASN informs the parameter set for each of the provisioned, admitted, and active states as defined in IEEE 802.16, and specifies specific QoS parameters in the active state parameter set. Changes are made possible within the range of values of the corresponding QoS parameters in the admitted state or provisioned state parameter set. Likewise, certain QoS parameter changes of the admitted state parameter set are possible within the corresponding QoS parameter value range of the provisioned parameter set.

In the case of semi-dynamic QoS, the ASN's A-PCEF may decide whether to change the QoS independently, or change it according to the CSN's PDF policy in conjunction with the CSN (eg AAA or PCRF or USI server). You can also decide whether or not.

In the case of initial access, the QoS profile is set according to the preset operator policy. In case of reconnection, the CSN (for example, AAA or PCRF or USI server) is involved, and according to the provider policy, the QoS profile is established. It may restore or update the changed provider QoS policy.

As mentioned above, QoS configuration types are, for example, static, semi-dynamic, dynamic, and the like. Hereinafter, for convenience of description, it will be assumed that the QoS setting type of the terminal is static.

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

Referring to FIG. 2, a terminal attempting initial access first acquires synchronization using a preamble signal received from a base station, and when synchronization is obtained, a MAP message, a downlink channel descriptor (DDC) message, and an uplink channel descriptor (UCD) message. Receive system parameters to obtain system parameters for communication. Thereafter, the terminal performs an initial network entry procedure with the base station. The initial network entry procedure includes a ranging procedure (RNG-REQ / RNG-RSP), a basic capability negotiation procedure (SBC-REQ / SBC-RSP), an authentication procedure (PKM), and a registration procedure (REG-REQ / REG-RSP). And the like. That is, upon initial network entry, the terminal performs an authentication procedure with the base station in step 201. At this time, the base station authenticates the terminal in association with the AAA server.

The AAA server generates a PDF output parameter (QoS policy information) using the information of the terminal successfully authenticated. The QoS policy information may include per-user QoS information as shown in Table 1 as well as QoS profile information for each flow. In step 203, the AAA server delivers QoS policy information for the terminal to the ASN. In step 205, the base station stores QoS policy information from the AAA server.

In step 207, the terminal interworkes with the ASN and the Core Service Network (CSN) to generate a QoS service flow, and performs traffic communication through the QoS service flow.

In this manner, during communication, the terminal checks whether the idle timer expires in step 209. The idle timer is a timer that expires when there is no traffic blur for a set time, and the idle timer is operated in the base station as well as the terminal. When the idle timer expires in either the terminal or the base station, the terminal transitions to the idle mode after exchanging a message with the base station in step 211.

When the traffic occurs during the idle mode, the terminal may transition to the awake mode through a quick connection setup (QCS) procedure. That is, the terminal checks whether a QCS is required in step 213. If the QCS is required, the terminal performs a QCS procedure with the base station in step 215. In this case, the terminal transmits a ranging code to the base station, and the base station transmits a ranging response message and a resource allocation message (CDMA_alloc_IE) to the terminal in response. Then, the terminal transmits the ranging request message through the allocated resource. At this point, the base station can identify the terminal.

When the terminal performing the QCS is identified, the base station checks QoS policy information of the terminal in step 217. That is, check the QoS policy to be applied when performing the QCS. In step 219, the base station determines whether to return the flows of the terminal to a previous state according to the QoS policy. Here, when not returning to the previous state, the base station transitions the flows of the terminal to a provisioned state. If returning to the previous state, the base station performs CAC to return the flows to the previous state. At this time, the flow in which the previous state is the ready state may be maintained in the ready state.

If there is a flow not returned to the previous state, the base station processes the flow not returned to the previous state according to the QoS policy in step 221. According to the QoS policy, flows that are not returned are prepared in a ready state, and the QCS is completed or deleted at all, the QCS itself is failed, the QCS is continued until all flows are returned, or load balancing is performed. Can be done. When completing the QCS, the base station transmits a ranging response message including "SFID vs TCID" to the terminal. At this time, the ready state flow does not perform the CID update through the ranging response message, or transmits the ranging response message in which the CID corresponding to the SFID is set to null, or the ranging response message in which only the SFID is set. Can be transmitted to the terminal. In case of failing the QCS, the base station transmits a ranging response message to which the ranging state is set to abort. If the QCS proceeds until it is returned, the base station may transmit a ranging response message to which the ranging state is set to continue.

In addition, for the flow managed in the ready state, the base station and the terminal may manage the flow in the ready state without a separate procedure, or may negotiate a transition to the ready state through a DSC procedure.

In addition, the CAC result may be set in a Service Level Prediction (SLP) field of a ranging response message. That is, it is possible to notify the terminal by setting the ranging response message whether the return of all the service flows is possible, only a part of the service flow, or whether the return of all the services is not possible because there are no resources left. In addition, flows granted in CAC may be managed in an active state or an admitted state according to QoS policy.

3 illustrates an HHO processing procedure according to a QoS policy in a wireless network according to an embodiment of the present invention.

Referring to FIG. 3, a terminal attempting initial access acquires synchronization using a preamble signal received from a base station, and when synchronization is obtained, a MAP message, a downlink channel descriptor (DDC) message, and an uplink channel descriptor (UCD) message are obtained. Receive the system parameters to obtain the communication. Thereafter, the terminal performs an initial network entry procedure with the base station.

That is, upon initial network entry, the terminal performs an authentication procedure with the base station in step 301. At this time, the base station authenticates the terminal in association with the AAA server.

The AAA server generates a PDF output parameter (QoS policy information) using the information of the terminal successfully authenticated. The QoS policy information may include per-user QoS information as shown in Table 1 as well as QoS profile information for each flow. In step 303, the AAA server delivers QoS policy information for the terminal to the ASN. Then, the serving base station stores the QoS policy information from the AAA server in step 305.

In step 307, the terminal generates a QoS service flow in association with a serving ASN and a core service network (CSN), and performs traffic communication with a serving base station through the QoS service flow.

During the communication, the terminal scans the neighbor base station in step 309 and compares the signal strength of the serving base station with the signal strength of the neighbor base station to determine whether handover is necessary. If it is determined that the handover is necessary, the terminal performs a handover procedure with the serving base station in step 311. For example, the terminal transmits a handover request message including reception strengths of candidate base stations to the base station, and the base station collects the service capability (bandwidth and service level, etc.) of the candidate base stations, and then the handover target base station. Determine. In this case, the service capability may include the CAC result for the corresponding terminal as well as the bandwidth and service level. Accordingly, the notification message including the service capability includes a parameter indicating whether all flows are granted in the CAC, only part of the flow, and all are rejected, a parameter indicating whether CAC is granted for each flow, and the number of CAC granted flows. It may include a parameter that can display. Thereafter, the base station transmits a handover response message including the target base station to the terminal, and when the handover to the target base station is finally determined, the terminal transmits a handover instruction message to the serving base station and then the target. Attempt to connect to the base station.

When the handover indication message is received, the serving base station transmits QoS policy information for the terminal to the target base station to the target base station in step 313. In this case, not only a profile identifier (or QoS profile information) for each service flow but also user-specific QoS information is transmitted to the target base station. In operation 315, the target base station stores the QoS policy information.

In step 317, the target base station performs a network reentry procedure with the terminal. In this case, the terminal transmits a ranging code to the target base station, and the target base station transmits a ranging response message and a resource allocation message (CDMA_alloc_IE) to the terminal in response. Then, the terminal transmits the ranging request message through the allocated resource. At this point, the target base station can identify the terminal.

When the terminal performing the handover is identified as described above, the target base station checks QoS policy information of the terminal in step 319. That is, check the QoS policy to be applied to the terminal when the handover. In step 321, the target base station determines whether to perform CAC for the terminal according to the QoS policy. In this case, when the CAC is not performed, the target base station allocates a TCID to all active state and admitted state flows of the terminal. If the CAC is performed, the base station performs a CAC and allocates a TCID according to the CAC result.

If there is a flow that does not pass through the CAC, the target base station processes the flow that does not pass through the CAC according to the QoS policy in step 323. According to the QoS policy, it is necessary to manage a flow that does not pass the CAC in preparation, continue the network reentry procedure (ranging procedure) until the CAC passes, or perform CID update on the flow that does not pass the CAC. Can be turned off or load balancing performed. In addition, when the QoS type of the terminal is "dynamic", the flow may proceed to the ready state for the flow not assigned the TCID, or may be automatically deleted or the flow may be deleted through the DSD procedure. Meanwhile, when a TCID is assigned to the flow, the target base station transmits a ranging response message including "SFID vs TCID" to the terminal. At this time, the ready state flow does not perform the CID update through the ranging response message, or transmits the ranging response message in which the CID corresponding to the SFID is set to null, or the ranging response message in which only the SFID is set. Can be transmitted to the terminal. If the ranging procedure continues until all the flows pass the CAC, the target base station may transmit a ranging response message with a ranging status set to continue to the terminal. .

In addition, with respect to the flow managed in the ready state, the target base station and the terminal may manage the flow in the ready state without a separate procedure, or may negotiate a transition to the ready state through a DSC procedure. The flows that transition to the ready state no longer need to buffer bearer traffic at the previous serving base station, target base station and anchor control station.

In addition, the CAC result may be set in a Service Level Prediction (SLP) field of a ranging response message. That is, it is possible to notify the terminal by setting the ranging response message whether the return of all the service flows is possible, only a part of the service flow, or whether the return of all the services is not possible because there are no resources left.

4 illustrates an FBSS processing procedure according to a QoS policy in a wireless network according to an embodiment of the present invention.

Referring to FIG. 4, a terminal attempting initial access first acquires synchronization using a preamble signal received from a base station, and when synchronization is obtained, a MAP message, a downlink channel descriptor (DDC) message, and an uplink channel descriptor (UCD). Receive a message to obtain system parameters for communication. Thereafter, the terminal performs an initial network entry procedure with the base station.

That is, upon initial network entry, the terminal performs an authentication procedure with the base station in step 401. At this time, the base station authenticates the terminal in association with the AAA server.

The AAA server generates a PDF output parameter (QoS policy information) using the information of the terminal successfully authenticated. The QoS policy information may include per-user QoS information as shown in Table 1 as well as QoS profile information for each flow. In step 403, the AAA server delivers QoS policy information for the terminal to the ASN. Then, the serving base station stores the QoS policy information from the AAA server in step 405.

In step 407, the terminal generates a QoS service flow in association with a serving ASN and a core service network (CSN), and performs traffic communication with a serving base station through the QoS service flow.

The terminal and the serving base station update a diversity set by an event or periodically for FBSS during the traffic communication. Here, the diversity set represents a set of candidate base stations to which the terminal can move. In detail, in step 411, the serving base station transmits a request message for inquiring service capability to the candidate base station through the backbone network. In this case, the request message may include a parameter indicating the QoS policy of the terminal.

In operation 413, the candidate base station determines the QoS policy of the terminal by interpreting the request message. In operation 415, the candidate base station determines whether to perform CAC for the terminal according to the QoS policy. Here, when not performing CAC, the candidate base station allocates a TCID to all active and permission state flows of the terminal. If the CAC is performed, the base station performs a CAC and allocates TCIDs to flows according to the CAC result. In the following description, it is assumed that the candidate base station performs CAC.

In operation 417, the candidate base station constructs a response message including the CAC result and transmits the response message to the serving base station. In this case, the response message may include a parameter indicating whether all flows are allowed, only a part of the flow, or all are rejected, and TCID information allocated to the flows allowed.

On the other hand, after collecting the CAC result from at least one candidate base station, the serving base station configures a diversity set update request (BSHO_REQ) message based on the collected information in step 419, and the diversity set update request message Transmit to the terminal.

In step 421, the terminal updates the diversity set managed by the terminal based on the diversity set update request message. Here, the diversity set includes TCID information of each flow allocated by the candidate base station for the terminal. In step 422, the terminal transmits a diversity set update response message to the serving base station. The diversity set update may be performed by a base station or a terminal request, and may be performed by a specific event or periodically.

In this manner, during communication, the terminal checks whether the FBSS is required in step 423. That is, it is checked to which candidate base station in the diversity set is necessary. If it is determined that the FBSS is necessary, the terminal performs an FBSS procedure with the serving base station in step 425. In this case, the terminal finally determines a target base station among candidate base stations, transmits an indication message including the target base station to the serving base station and switches to the target base station. On the other hand, upon receiving the indication message, the serving base station transmits an acknowledgment message indicating the base station switching of the terminal in step 427 to the target base station.

After transmitting the indication message, the UE acquires synchronization by acquiring a preamble signal from the target base station in step 429, and receives and analyzes a MAP message in step 431 when synchronization is obtained. In this case, the terminal may check an allocation message (CQICH_alloc_IE) including Channel Quality Indicator CHannel (CQICH) resource information allocated thereto. That is, when the confirmation message is received, the target base station allocates a CQICH resource to the terminal, and broadcasts an assignment message (CQICH_alloc_IE) including the allocated resource information.

In addition, in step 433, the target base station processes flows to which the TCID is not assigned according to the QoS policy of the terminal. According to the QoS policy, a flow in which no TCID is assigned may be managed in a ready state, or a timer may be set to continue CAC for a set time. In addition, when the QoS type of the terminal is "dynamic", the flow may be managed in a ready state or automatically deleted for a flow to which a TCID is not assigned, or the flow may be deleted through a DSD procedure. When a TCID is assigned to a flow through the above operation, the base station may transmit a message including "SFID vs TCID" to the terminal. At this time, the ready state flow does not perform the CID update through the ranging response message, or transmits the ranging response message in which the CID corresponding to the SFID is set to null, or the ranging response message in which only the SFID is set. Can be transmitted to the terminal. In operation 435, the terminal switched to the target base station performs traffic communication using the TCID assigned by the target base station.

For the flow managed in the ready state, the base station and the terminal may manage the flow in the ready state without a separate procedure, or may negotiate a transition to the ready state through a DSC procedure. The flows that transition to the ready state no longer need to buffer bearer traffic at the previous serving base station, target base station and anchor control station.

On the other hand, when the UE in progress of FBSS while accessing a serving base station creates a new service flow or deletes or changes an existing service flow, the terminal and the serving base station may perform a diversity set update procedure through BSHO_REQ / MSHO_REQ. have. When creating a new service flow, the ASN allocates SFID and TCID. In the current specification, a field indicating TCID is present in BSHO_REQ / BSHO_RSP, but there is no field indicating SFID. In this case, the request message may include a QoS parameter indicating whether candidate base stations perform CAC only for the changed flow or CAC for all flows again.

5 illustrates a procedure for processing a QCS at a base station according to an embodiment of the present invention.

Referring to FIG. 5, in step 501, the base station receives QoS policy information of an initially accessed terminal from an AAA server, and stores the QoS policy information of the terminal in step 503. The QoS policy information may include per-user QoS information as shown in Table 1 as well as QoS profile information for each service flow.

In step 505, the base station generates a QoS service flow in association with the terminal and the CSN, and performs traffic communication through the generated service flow. For example, when the QoS configuration type of the terminal is static or semi-dynamic, the base station performs a DSA procedure with the terminal upon initial access to prepare a fixed service flow. After generating, the TCID can be assigned through the DSC procedure to perform traffic communication.

During this communication, the base station checks whether the idle timer expires in step 507. The idle timer is a timer that expires when there is no traffic flow for a set time, and is operated by the terminal as well as the base station. When the idle timer expires, the base station proceeds to step 509 and exchanges a message with the terminal, and then transitions the mode of the terminal to the idle mode.

During the idle mode, the base station determines whether a quick connection setup (QCS) procedure is performed with the terminal in step 511. When the QCS procedure is performed, the terminal transmits a ranging code to the base station, and the base station transmits a ranging response message and a resource allocation message (eg, CDMA_alloc_IE) to the terminal in response. Then, the terminal transmits the ranging request message through the allocated resource. At this point, the base station can identify the terminal performing the QCS.

If the terminal performing the QCS is identified, the base station checks the QoS policy information of the terminal previously stored in step 513. That is, the QoS policy to be applied to the terminal is checked when the QCS is performed. In step 515, the base station determines whether to return the flows of the terminal to a previous state according to the QoS policy. If the base station does not return to the previous state, the base station proceeds to step 519 and manages all flows in a provisioned state. If returning to the previous state, the base station proceeds to step 517 and performs a CAC to return the flows to the previous state. At this time, only the flow passing the CAC is returned to the previous state.

Accordingly, the base station processes flows that are not returned to the previous state at step 521P according to the QoS policy of the terminal. That is, according to the QoS policy, a flow that is not returned is prepared in a ready state, and the QCS is completed, the QCS itself is failed, or the QCS is continued until all flows are returned, or load balancing is performed. can do.

On the other hand, when the QCS is completed, the base station proceeds to step 523 and transmits a ranging response message including "SFID vs TCID" to the terminal. In this case, the ranging response message may include CAC result information. In addition, with respect to the flow managed in the ready state, the base station and the terminal may manage the flow in the ready state without a separate procedure, or may negotiate a transition to the ready state through a DSC procedure.

6 illustrates a procedure for processing an HHO in a base station according to an embodiment of the present invention. In particular, FIG. 6 illustrates a processing procedure of a target base station when performing an HHO of a terminal.

Referring to FIG. 6, the base station first receives QoS policy information of a terminal handing over from a previous serving base station in step 601. That is, when the handover of the terminal is finally determined, the previous serving base station transmits QoS policy information of the terminal to the target base station. At this time, QoS information for each user as well as QoS profile information for each service flow are transmitted to the target base station. In step 603, the base station (target base station) stores QoS policy information of the terminal.

In step 605, the base station determines whether a network reentry procedure is performed with the terminal. When the network reentry procedure is performed, the terminal transmits a ranging code to the base station, and the base station transmits a ranging response message and a resource allocation message (CDMA_alloc_IE) in response. Then, the terminal transmits a ranging request message through the allocated resource. At this point, the base station can identify the terminal.

When the terminal to handover is identified as such, the base station checks the QoS policy of the terminal received from the previous serving base station in step 607. That is, the QoS policy to be applied to the terminal is checked when the HHO is performed. In step 609, the base station determines whether to perform CAC on the flows of the terminal according to the QoS policy. If the CAC is not performed, the base station proceeds to step 613 and allocates a TCID to all active and allowed state flows. If the CAC is performed, the base station proceeds to step 611 to perform the CAC and allocates TCIDs to the corresponding flows according to the CAC result. At this time, only the flow passing the CAC allocates the TCID.

Accordingly, the base station processes flows for which the TCID is not assigned at step 615 according to the QoS policy of the terminal. That is, according to the QoS policy, a flow that does not pass the CAC is prepared in a ready state, a network reentry procedure (ranging procedure) is continued until the CAC passes, or a CID update is performed for a flow that does not pass the CAC. If not, it can be turned off or load balancing can be performed. In addition, when the type of the terminal is dynamic, a flow to which a TCID is not assigned may be automatically deleted or a corresponding flow may be deleted through a DSD procedure.

 Meanwhile, when the network re-entry procedure is completed, the base station transmits a ranging response message including "SFID vs TCID" to the terminal in step 617. In this case, the ranging response message may also include CAC result information. In addition, for the flow managed in the ready state, the base station and the terminal may manage the flow in the ready state without a separate procedure, or may negotiate a transition to the ready state through a DSC procedure.

7 illustrates a procedure for processing FBSS according to QoS policy in a base station according to an embodiment of the present invention. In particular, FIG. 7 illustrates a processing procedure of a candidate base station when performing a FBSS of a terminal.

Referring to FIG. 7, the base station first checks whether a request message for inquiring service capability is received from the serving base station in step 701. In this case, the request message may include profile IDs of service flows currently maintained by the UE performing FBSS and QoS information for each user. The serving base station and the terminal update a specific event or a set (diversity set) of candidate base stations to which the terminal can move periodically. In this process, the serving base station transmits the request message to neighboring base stations.

When the request message is received, the base station determines the QoS policy of the terminal by interpreting the request message in step 703. That is, the QoS policy to be applied to the terminal is checked when the FBSS is performed. In step 705, the base station determines whether to perform CAC on the flows of the terminal according to the QoS policy. If the CAC is not performed, the base station proceeds to step 709 and allocates a TCID to all active and admitted state flows. If the CAC is performed, the base station proceeds to step 707 to perform the CAC and allocate TCIDs to the corresponding flows according to the CAC result. At this time, only the flow passing the CAC allocates the TCID. The following description assumes that the CAC has been performed.

In step 711, the base station constructs a response message including the CAC result and transmits the response message to the serving base station. Then, the serving base station constructs a diversity set update request (BSHO_REQ) message based on the CAC result collected from the candidate base stations and transmits it to the terminal. Then, after updating the diversity set managed by the terminal, the terminal transmits a response message to the serving base station. Then, when FSBB is finally determined, the terminal transmits an indication message including the target base station information and then switches to the base station. On the other hand, the serving base station receiving the indication message transmits a confirmation message indicating the base station switching of the terminal to the base station.

Accordingly, the base station checks whether the confirmation message is received from the serving base station in step 713. When the acknowledgment message is received, the base station proceeds to step 715 and processes flows for which no current TCID is assigned according to the QoS policy of the terminal. According to the QoS policy, it is possible to manage a flow without a TCID assigned to a ready state, or set a timer to continue CAC for a set time. In addition, if the QoS setting type of the terminal is dynamic, the flow may not be automatically deleted for the flow to which the TCID is not assigned or the flow may be deleted through the DSD procedure.

In step 717, the base station allocates a channel quality indicator channel (CQICH) resource to the terminal and broadcasts an allocation message (CQICH_alloc_IE) including the allocated resource information. After allocating the CQICH resource to the terminal as described above, the base station performs traffic communication with the terminal in step 719.

On the other hand, with respect to the flow managed in the ready state, the base station and the terminal can manage the flow in the ready state without a separate procedure, or can negotiate the transition to the ready state through the DSC procedure.

8 illustrates a configuration of a base station in a broadband wireless access system according to an embodiment of the present invention.

As shown, the base station according to the present invention, the control unit 800, the transmission modem 802, the RF transmitter 804, the duplexer 806, the RF receiver 808, the reception modem 810, the flow state manager ( 812, a timer manager 814, and a QoS information storage 816.

Referring to FIG. 8, the transmission modem 802 includes a channel code block, a modulation block, and the like, and outputs a baseband modulated message (or packet) from the controller 800. 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. This is considered an OFDM system. In the case of a CDMA system, the IFFT operator may be replaced by a code spreading modulator.

The RF transmitter 804 includes a frequency converter, an amplifier, and the like, and converts a baseband signal from the transmission modem 802 into a signal in a radio frequency (RF) band. The duplexer 806 transmits the transmission signal from the RF transmitter 804 through the antenna according to the duplexing scheme, and provides the received signal from the antenna to the RF receiver 808. The RF receiver 808 includes an amplifier, a frequency converter, and the like, and converts a signal of an RF band received through an antenna into a baseband signal and outputs the signal.

The reception modem 810 includes a demodulation block, a channel decoding block, and the like, and base-band demodulates and outputs a signal from the RF receiver 808. Here, the demodulation block may include an FFT operator for extracting data carried on each subcarrier, and the channel decoding block may include a demodulator, a deinterleaver, a channel decoder, and the like. .

The QoS information storage unit 816 manages QoS policy information of a terminal received from a policy server or another network entity (eg, an AAA server equipped with PDF). In addition, the QoS information storage unit 816 receives and manages QoS information of a terminal performing a hard handover (HHO) or a soft handover (FBSS) from a previous serving ASN. For example, the QoS policy information may include per-flow QoS profile information (or QoS parameter set) and per-user QoS information.

The state manager 812 manages an operation mode (eg, awake, sleep, idle) and a state (eg, active, admitted, or provisioned) for each of the service flows for each terminal. The state of the service flow is managed according to a predetermined QoS policy. The timer manager 814 operates a timer for terminal mode transition and a timer for service flow state transition. That is, the timer manager 814 drives the timer under the control of the state manager 812, and notifies the state manager 812 when the timer expires. Then, the state manager 812 performs a mode transition or a state transition according to the expiration of the timer.

The controller 800 performs overall processing and control for the QoS service. According to the present invention, the controller 800 processes QCS, HHO, FBSS according to QoS policy. When the QCS is detected, the controller 800 checks the QoS policy of the corresponding terminal and determines whether to return the service flow of the terminal to a previous state according to the QoS policy. If it does not return to the previous state, the controller 800 transitions the service flow of the terminal to a provisioned state. If returning to the previous state, the controller 800 performs a CAC and returns the flows to the previous state according to the result.

In addition, when a terminal handing over is detected from an adjacent base station, the controller 800 checks the QoS policy of the terminal and determines whether to CAC for the terminal according to the QoS policy. If the CAC is not performed, the controller 800 allocates a TCID to active and permission state flows of the terminal. If performing the CAC, the control unit 800 performs the CAC, and allocates the TCID according to the result.

In addition, when the terminal in the neighboring base station performs the FBSS, the control unit 800 may allocate the TCID to the terminal in advance. In this case, the controller 800 determines whether to CAC for the terminal according to the QoS policy of the terminal. If the CAC is not performed, the controller 800 allocates a TCID to active and allowed state flows of the terminal. If performing the CAC, the control unit 800 performs the CAC, and allocates the TCID according to the result.

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 the equivalents of the claims.

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

2 is a diagram illustrating a QCS processing procedure according to a QoS policy in a wireless network according to an embodiment of the present invention.

3 is a diagram illustrating an HHO processing procedure according to a QoS policy in a wireless network according to an embodiment of the present invention.

4 is a diagram illustrating an FBSS processing procedure according to a QoS policy in a wireless network according to an embodiment of the present invention.

5 is a diagram illustrating a procedure for processing a QCS at a base station according to an embodiment of the present invention.

6 is a diagram illustrating a procedure for processing an HHO in a base station according to an embodiment of the present invention.

7 is a diagram illustrating a procedure for processing an FBSS according to a QoS policy in a base station according to an embodiment of the present invention.

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

Claims (27)

In the method of operation of a base station in a wireless communication system, Receiving and storing QoS (Quality of Service) policy information of a terminal from a network entity or a neighboring base station including a PDF (Policy Decision Function); Detecting a terminal to reconnect, When the reconnection terminal is detected, checking a QoS policy of the terminal; And controlling a state of a service flow generated for the terminal according to the QoS policy. The method of claim 1, The network entity including the PDF is a policy server or AAA (Authentication / Authorization / Accounting) server. The method of claim 1, The reconnection terminal is one of a terminal for reentry a network, a terminal for hard handover (HO), and a terminal for soft handover. The method of claim 1, wherein the control process, If the reconnection terminal is a terminal reentering a network, checking whether the service flow of the terminal returns to a previous state; If not returning to the previous state, transitioning all service flows of the terminal to a provisioned state; When returning to the previous state, performing a CAC (Connection Admission Control) for the terminal, and transitioning the CAC passed service flow to an active or admitted state Way. The method of claim 4, wherein And processing the service flow not passed through the CAC according to the QoS policy of the terminal. The method of claim 5, wherein the treatment process, If the QoS policy is the first case, transitioning a flow not passed through the CAC to a ready state; If the QCS policy is the second case, failing the QCS; If the QCS policy is the third case, proceeding with CAC until all service flows return to their previous state; If the QCS policy is the fourth case, performing load balancing. The method of claim 4, wherein And transmitting a message including a TCID (Traffic Connection IDentifier) assigned to the CAC passed flow to the terminal. The method of claim 1, The QoS policy information of the terminal received from the neighboring base station includes at least one of a parameter indicating whether or not CAC, a parameter indicating a processing method for the service flow that does not pass the CAC. The method of claim 1, wherein the control process, When the reconnection terminal is a hard handover terminal, checking whether to perform CAC for the terminal; Assigning a TCID to an active state and a permit state flow of the terminal when the CAC rule is not performed; When performing the CAC, performing the CAC for the terminal, characterized in that it comprises the step of assigning the TCID to the service flow passed the CAC. The method of claim 9, And processing the service flow not passed through the CAC according to the QoS policy of the terminal. The method of claim 10, wherein the treatment process, If the QoS policy is the first case, transitioning a flow not passed through the CAC to a ready state; If the QoS policy is the second case, continuing the network re-entry procedure until passing through the CAC; Deleting the flow not passed through the CAC when the QoS policy is the third case; If the QoS policy is the fourth case, performing load balancing. The method of claim 9, And transmitting a message including the TCID assigned to the CAC passed flow to the terminal. The method of claim 1, Allocating a TCID to a service flow of the terminal according to the QoS policy when receiving the QoS policy information of the terminal performing soft handover from the neighbor base station; Transmitting the message including the assigned TCID to the neighbor base station. The method of claim 13, wherein the assignment process, Checking whether to perform CAC for the terminal; Assigning a TCID to an active state and a permit state flow of the terminal when the CAC rule is not performed; When performing the CAC, performing the CAC for the terminal, characterized in that it comprises the step of assigning the TCID to the service flow passed the CAC. The method of claim 13, The method may further include allocating a channel quality channel (CQICH) resource to the terminal when the acknowledgment message indicating soft handover of the terminal is received from the neighbor base station, and broadcasting the QCICH allocation message. The method of claim 13, wherein the control process, When the reconnection terminal is a soft handover terminal, checking a QoS policy for a flow that is not assigned a TCID; If the QoS policy is the first case, transitioning a flow to which the TCID is not assigned to a provisioned state; If the QoS policy is the second case, deleting the flow to which the TCID is not assigned. The method of claim 1, When generating a new service flow for the terminal that is undergoing the soft handover, further comprising transmitting a diversity set update request message including the SFID and the TCID assigned to the terminal to the terminal. . The method of claim 17, The diversity set update request message is a base station handover request (BSHO_REQ) message or a BSHO_RSP (BSHO ReSPonse) message. A base station apparatus in a wireless communication system, A storage unit for storing QoS policy information of the terminal; A state manager for managing an operation mode and a service flow state for each terminal; A timer manager for managing a timer required for transitioning an operation mode of the terminal and a state transition of the service flow; And a controller for changing an operation mode or a service flow state of a corresponding terminal when the timer expires, and controlling a state of a service flow set to the terminal according to a QoS policy of the terminal when a reconnected terminal is detected. . The method of claim 19, QoS policy information of the terminal is received from a network entity or a neighboring base station including a PDF. The method of claim 20, The network entity including the PDF is a policy server or an AAA server. The method of claim 19, The QoS policy information of the terminal comprises at least one of QoS policy information for network re-entry, QoS policy information for hard handover, and QoS policy information for soft handover. The method of claim 19, wherein the control unit, When the reconnection terminal is a terminal reentering a network, it is checked whether the service flow of the terminal returns to a previous state, and when not reverting to the previous state, all service flows of the terminal are transitioned to a provisioned state, and And returning to a previous state after performing CAC for the terminal and transitioning a service flow to an active state or an admitted state according to the result. The method of claim 23, wherein the control unit, And the CAC does not pass the flow according to the QoS policy of the terminal. The method of claim 19, wherein the control unit, When the reconnection terminal is a hard handover terminal, the terminal checks whether the terminal performs CAC. If the terminal does not perform the CAC rule, it assigns a TCID to an active state and a permit state flow of the terminal, and performs the CAC. If the terminal performs the CAC and assigns a TCID to the service flow according to the result. The method of claim 19, wherein the control unit, When the QoS policy of the terminal performing soft handover is received from the neighboring base station, assigning a TCID to the service flow of the terminal according to the QoS policy of the terminal and transmitting a message including the assigned TCID to the neighboring base station. Characterized in that the device. The method of claim 26, wherein the control unit, When the reconnection terminal is the terminal to which the soft handover is performed, the QoS policy for the flow to which the TCID is not assigned is checked. When the QoS policy is the first case, the flow retransmits the unassigned flow to the ready state. And in the second case, deletes a flow to which the TCID is not assigned.

Images