KR101546750B1 - A method for data transmission guaranteed Quality of Service in a terminal equipment and an apparatus thereof - Google Patents

Abstract

The present invention relates to an apparatus and method for transmitting data of a terminal for providing QoS (Quality of Service), and the present invention relates to a terminal equipment (TE) for executing a plurality of applications for providing a wireless communication service, And an SS (Subscriber Station) for transmitting data according to a wireless standard, wherein the TE comprises: an application unit for outputting data generated by execution of each application; And a network driver for scheduling and outputting the data to the SS. The data transmission apparatus and the transmission method of the terminal for providing QoS are provided.

TE, SS, QoS

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a data transmission apparatus and method for transmitting and receiving data,

The present invention relates to an apparatus and method for transmitting data of a terminal for providing QoS, and more particularly, to an apparatus and method for transmitting data of a terminal that can efficiently guarantee QoS even when data transmission is not smooth.

A terminal for providing a wireless communication service in a mobile WiMAX (mWiMAX) includes a terminal equipment (TE) and a subscriber station (SS) connected to the TE and performing a wireless section connection. Generally, the TE may be a notebook, and the SS may be a network adapter.

In order to provide QoS service in mobile WiMAX (mWiMAX), a scheduler is provided using a classifier in a MAC layer. However, in many cases, it may be difficult to guarantee the QoS. That is, when the amount of data transmitted from the TCP / IP Stack of the TE is greater than the HW Interface Throughput of the device, when the throughput of the wireless section (Air) decreases, A bottleneck occurs when an application tries to transmit a packet with a high data rate. In such a case, QoS of each application is difficult to guarantee and performance is also difficult to guarantee.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and it is an object of the present invention to provide a method and apparatus for providing a service without QoS bottleneck.

According to another aspect of the present invention, there is provided a data transmission apparatus for providing a QoS according to a preferred embodiment of the present invention includes a terminal equipment (TE) for executing a plurality of applications for providing a wireless communication service, And an SS (Subscriber Station) for transmitting data according to a wireless standard, wherein the TE comprises: an application unit for outputting data generated by execution of each application; And a network driver for performing scheduling and outputting to the SS.

The network driver receives a QoS profile according to each application from the application unit, allocates a queue according to the received QoS profile, and schedules packets input to the allocated queue.

The QoS profile includes maximum and minimum rate, jitter time, and priority.

According to another aspect of the present invention, there is provided a method of transmitting data to a terminal for providing QoS according to a preferred embodiment of the present invention includes the steps of allocating a queue corresponding to an application providing a service through a wireless communication connection, Scheduling a time for outputting the packets according to a preset QoS of each application; and outputting the packets according to the calculated time, .

The allocating process is characterized by receiving a QoS profile according to each application and allocating a queue according to the received QoS profile.

The QoS profile includes maximum and minimum rate, jitter time, and priority.

According to the present invention, a network driver performs QoS-based scheduling, thereby ensuring QoS without bottleneck and providing a service. This has the advantage of increasing the use of the wireless communication network.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, only parts necessary for understanding the operation according to the present invention will be described, and the description of other parts will be omitted so as not to obscure the gist of the present invention.

First, a wireless network system according to an embodiment of the present invention will be described. 1 is a diagram illustrating a configuration of a wireless network system according to an embodiment of the present invention.

A wireless network system according to an embodiment of the present invention includes a terminal 100, a base station device 200, and an IMS (IP Multimedia Subsystem) 300.

The terminal 100 communicates with the base station apparatus 200 according to the radio access standard as an end point of a radio channel. A terminal 100 according to an embodiment of the present invention includes a terminal equipment (TE) 110 and a subscriber station (SS)

The base station apparatus 200 plays a role of connecting between the terminal 100 and the IMS 300. In particular, the base station apparatus 200 includes a Radio Access Station (RAS) 210 and an Access Control Router (ACR) 220.

A radio access station (RAS) 210 is a device for connecting a radio network and a wired network, and controls a radio channel according to characteristics of each network. The RAS 210 is connected to a wired network and directly provides a wireless packet data service do. Its main functions are to transmit and receive wireless signals, to perform modulation and demodulation signal processing on packet traffic signals, and to perform protocol processing and routing functions.

An ACR (Access Control Router) 220 is connected to and manages a plurality of RASs 210, and performs a handover control function for ensuring high mobility in the ACR 220. The ACR 220 controls the terminal 100 and the RAS 210 and routes IP packets. From the perspective of data traffic, the ACR 220 can be viewed as a router.

The IP Multimedia Subsystem (IMS) 300 includes a home subscriber server (HSS), a subscriber location function (SLF), a session charging function (SCF), a call session control function (CSCF) (Policy Decision Function), AS (Application Server), MRF (Media Resource Function), BGCF (Breakout Gateway Control Function), MGCF (Media Gateway Controller Function) , A Charging Collector Function (CCF), and an Event Charging Function (ECF). IMS (IP Multimedia Subsystem) is a core network infrastructure (infra) that enables various multimedia services based on IP. As described above, the IMS 300 may have various entities, and a set of these entities will be referred to as an IMS 300. [

Among these entities, entities for a Session Initiation Protocol (SIP) network may be P-CSCF, I-CSCF, S-CSCF, BGCF, MRFC, MGCF, AS,

The HSS supports the IMS entities that perform session control as an evolved form of HLR as a user information database. The HSS contains user related subscription information related to multimedia session control, i.e., location information of the user, security information for authentication and permission of the user, and user profile information including the service to which the user subscribes.

The CSCF processes SIP signals in the IMS 300 as a kind of SIP server. The P-CSCF is a SIP proxy server that is the first connection point for the IMS terminal. The P-CSCF may reside in a home network or a visited network. The P-CSCF is assigned to the IMS terminal at the time of registration in the IMS network and is not changed during the registration period. The P-CSCF can include PDF or be separately configured and performs QoS control functions such as policy control and band management.

The I-CSCF is located at the boundary of the management domain when the border function is not present. Therefore, the server of the other domain finds it and exposes the IP address to the DNS of the domain so that it can be used as the input node of the network. The I-CSCF queries the HSS for the user's location and forwards the SIP message to the user's assigned S-CSCF. The S-CSCF is a central node of the signaling layer and performs session control as one SIP server. Always exists in the home network, downloading and uploading user profiles from HSS. Binds the user's location and SIP address at SIP registration.

Application servers (ASs) host and perform services, and interfaces with the S-CSCF using SIP. Examples of these services include Caller ID related services (CLIP, CLIR, etc.), call hold, call hold, push-to-talk, transfer, call forwarding, call blocking, legitimate interception, SMS, MMS, presence information, instant messaging, and so on. The term "service" as used in an embodiment of the present invention includes those described above.

Next, the configuration of the terminal 100 according to the embodiment of the present invention will be described in more detail. 2 is a diagram for explaining a schematic configuration of a terminal according to an embodiment of the present invention.

A terminal 100 according to an embodiment of the present invention includes a terminal equipment (TE) 110 and a subscriber station (SS) In particular, the TE 110 includes an application unit 111 and a network driver 113.

The TE 110 provides an application for providing services using various wireless communications to the user and the SS 120 provides a wireless connection for providing the service . Accordingly, the TE 110 provides the SS 120 with the packet-based data generated according to the use of each application, and the SS 120 transmits the data to the base station 200. In addition, the SS 120 receives data from the base station apparatus 200 and transmits the data to the TE 110.

The application unit 111 has a plurality of applications that can provide various services, and provides them to a user through a predetermined interface. In addition, the application unit 111 provides the QoS information including the QoS profile of each application to the network driver 113. The application unit 111 provides the network driver 113 with packets generated according to the usage of each application.

The network driver 113 schedules a packet generated in each application of the application unit 111 and transmits the packet to the SS 120. To this end, the network driver 113 allocates a queue according to each application according to a request of the application unit. Then, when the packet is inputted, the network driver 113 classifies the input packet according to each application and inputs the packet to the corresponding queue. In addition, the network driver 113 schedules according to the QoS of each application and outputs the packet to the SS 120. In order to perform the above-described functions, the network driver 113 includes a classification module (QoS Classification) for inputting packets received in the application queue to the assigned queue, a queue management A module (Queue Manager), a scheduler (Packet Scheduler) for scheduling and outputting packets input to each queue, and the like.

The SS 120 transmits a packet input from the TE 110 to the base station apparatus 200 according to the radio standard. For this purpose, the SS 120 may include a device for connection with the TE 110 and a wireless communication module for performing wireless communication with the base station 200. The SS 120 also transmits a packet according to the application according to the QoS set by each application.

According to an embodiment of the present invention, scheduling is performed for each QoS according to each application in order to perform data transmission according to the QoS of the terminal 100. For example, it performs scheduling according to the data rate. To this end, the application unit 111 provides the QoS profile of each application to the network driver 113, and the network driver 113 allocates a queue for each application. After the queues are allocated, if application-specific data is generated for each application, the application unit 111 provides the generated data to the network driver on a packet-by-packet basis. Then, the network driver 113 schedules the packets input to the assigned queue according to the QoS and outputs the packets to the SS 120.

The TE 110 and the SS 120 may be included in one device. In case of a different device, the TE 110 and the SS 120 are connected to each other through a specific interface. Specific interfaces include wired and wireless. For example, the TE 110 may be a portable device such as a notebook, and the SS 120 may be a so-called "network adapter "," network device "

According to the embodiment of the present invention, the network driver 113 allocates a queue for each application and outputs a packet input to each queue to the SS 120 according to the QoS, The transmission performance is not deteriorated even when a specific application generates excessive traffic.

A data transmission method for assuring the QoS of the MS will be described in more detail. Each application has QoS to provide its services. For example, the QoS may be a minimum transmission rate or a maximum transmission rate required for a corresponding application to be executed and to provide a service to a user. In the embodiment of the present invention, the QoS setting is performed to guarantee the QoS of the application when the application is executed, and the QoS setting is canceled at the end of the application.

First, a description will be made of a QoS setting method in case of a service request according to each application according to an embodiment of the present invention. 3 is a diagram for explaining a QoS setting method according to an embodiment of the present invention.

In order to receive a service according to a specific application, the TE 110 transmits a service request message (SIP INVITE) to the IMS 300 in step S301. In response to this, the IMS 300 transmits to the TE 110 an information message (SIP 183) including an authentication token for the service in step S303. The message exchange between the TE 110 and the IMS 300 is performed through the base station 200 and the SS 120.

The TE 110 having received the authorization token transmits the QoS reservation request message to the SS 120 in step S305. The QoS reservation request message includes an authorization token for the service and an application handle (App_Handle) for handling the application performing the service. Upon receiving the QoS reservation request message, the SS 120 reserves QoS for the base station 200 and the corresponding application in step S307.

The SS 120 then transmits a QoS RESERVATION RESPONSE to the TE 110 to notify that the reservation is completed in step S309. Here, the QoS reservation response message includes a QoS handle (QoS_Handle).

Accordingly, the TE 110 itself performs a process of setting a QoS "reserved for QoS" between the application unit 111 and the network driver 113. "Setting QoS" means allocating a queue corresponding to the application from the viewpoint of the terminal.

In order to "set QoS ", the application unit 111 requests the network driver 113 to set the QoS of the application in step S311. At this time, the application unit 111 transmits an identifier corresponding to the QoS of the application and a profile corresponding to the QoS. In step S313, the network driver 113 allocates a queue corresponding to the application. In step S315, the network driver 113 informs the application unit 111 of a result indicating that a queue corresponding to the application has been allocated.

After the setting is completed, the TE 110 and the IMS 300 exchange a response message in steps S317 and S319 to complete the session setup, and a media channel according to the QoS set in advance is formed in step S321.

The TE 110 may set the QoS through steps S311 to S315 and provide a service for guaranteeing QoS through the media channel. It is preferable that the processes of steps S311 to S315 are performed before completion of session setting.

Then, the TE 110 and the IMS 300 exchange a response message in steps S317 and S319 to complete the session setup, and a media channel according to the QoS set in advance is formed in step S321.

As described above, "QoS setting" means allocating a queue corresponding to the application from the viewpoint of the terminal. This queue allocation method will be described below.

4 is a flowchart illustrating a queue allocation method according to an embodiment of the present invention.

The process of FIG. 4 may correspond to steps S311 to S315 of FIG. Referring to FIG. 4, in step S401, the application unit 111 transmits a QoS profile for an application for which QoS is to be set, to the network driver 113. FIG. The QoS profile includes identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value), maximum and minimum transfer rates (Max_DataRate, Min_DataRate), tolerable jitter (abbreviated below as "jitter time"), do.

The identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value) is information for extracting an identifier (QoS_ID), and the identifier (QoS_ID) is for identifying an application corresponding to the packet when the packet is input to the network driver. At this time, "QoS_ID_Offset" indicates a position where data in which an identifier (QoS_ID) is stored in an incoming packet is started, and "QoS_ID_Size" Also, "QoS_ID_Value" means a port number (Source Port Nuber) of the packet. Therefore, the network driver 113 can extract the identifier (QoS_ID) through "QoS_ID_Offset", "QoS_ID_Size" and "QoS_ID_Value".

The maximum and minimum transmission rates (Max_DataRate, Min_DataRate) mean the maximum and minimum transmission rates per packet to guarantee the QoS of the application, and the unit may be "bps". Tolerated jitter means that the packet is delayed due to jitter. The unit of the jitter time (Tolerated Jitter) can be "ms". In addition, the priority refers to a predetermined one according to each application.

Upon receiving the QoS profile, the network driver 113 determines whether the QoS of the application can be supported in step S403. For example, assuming that the maximum transferable capacity of the network driver is 100 bps and the transfer capacity of the pre-allocated queues is 80 bps, the network driver can only support applications with a maximum transfer rate (Max_DataRate) of 20 bps or less.

If it is determined in step S403 that QoS support for the application is available, the network driver 113 proceeds to step S405 and searches for a queue according to the application. This search is done using an identifier.

If the queue is not allocated to the network driver 113 in step S407, the network driver 113 proceeds to step S409 and newly allocates a queue according to the application. Then, the network driver 113 returns a result indicating that the queue is successfully (SUCCESS) allocated to the application unit 111 in step S411. On the other hand, if there is a pre-allocated queue according to the identifier, the network driver 113 returns a result indicating that the application unit 111 fails to allocate the queue in step S413.

The queue allocated as described above is maintained until the service according to the application is terminated. The termination of the service is performed at the request of the TE 110 or the IMS 300. A description will now be made of a method of releasing a QoS setting upon termination of service according to a request of each of the TE 110 and the IMS 300. FIG.

First, a description will be given of a QoS setting release method upon termination of service according to a request of the TE 110. [ 5 is a diagram for explaining a QoS setting release method according to an embodiment of the present invention.

Referring to FIG. 5, in step S501, a channel is formed through a session connection established between the TE 110 and the IMS 300 according to the method described with reference to FIG. 3, indicating that a service is provided through the channel.

During the service provision in step S501, the TE 110 transmits a service end message (SIP BYE) to the IMS 300 in step S503. The transmission of the service termination message (SIP BYE) is performed through the base station apparatus 200 and the SS 120.

Then, the TE 110 transmits a QoS DELETE REQUEST message in step S505. The QoS deletion request message includes an application handle (App_Handle) and a QoS handle (QoS_Handle).

Then, in step S507, the SS 120 and the base station 200 delete the QoS setting for the application (QoS DELETE procedure), and transmit a QoS delete response message (QoS DELETE RESPONSE) to the TE in step S509 do. The QoS deletion response message includes an application handle (App_Handle) and a QoS handle (QoS_Handle).

On the other hand, the TE 110 itself performs a process for releasing the QoS setting between the application unit 111 and the network driver 113. The "QoS deactivation" means that the TE 110 releases the queue corresponding to the application. For this, the application unit 111 requests the network driver 113 to release the QoS setting of the application in step S511. Then, the network driver 113 cancels the queue allocation of the application in step S513, and returns to the application unit 111 a result indicating that the QoS setting according to the application is canceled in step S515.

The above-described processes are performed until the IMS 300 transmits a response message (SIP 200 OK) to the TE 110 in step S517. As this response message is transmitted, the session connection between the TE 110 and the IMS 300 is also ended. Here, the response message (SIP 200 OK) is a response to the end message of the preceding step S501.

5, a method of releasing the QoS setting upon termination of service according to the request of the TE 110 has been described. Next, a description will be given of a QoS setting release method upon termination of service in response to a request from the IMS 300. FIG. 6 is a diagram for explaining a QoS setting release method according to an embodiment of the present invention.

Referring to FIG. 6, in step S601, a channel is formed through a session connection established between the TE 110 and the IMS 300 according to the method described above with reference to FIG. 3, and a service is provided through the formed channel.

It is assumed that a session-connected channel is not required in step S603 due to the service termination during service provision as in step S601.

Then, in step S605, the base station apparatus 200 and the SS 120 delete the QoS setting for the application (QoS DELETE procedure), and transmit a QoS delete notification message (QoS DELETE INDICATE) to the TE in step S607 do. The QoS deletion notification message includes an application handle (App_Handle) and a QoS handle (QoS_Handle).

Then, the TE 110 itself performs a process for releasing the QoS established between the application unit 111 and the network driver 113. The "QoS deactivation" means that the TE 110 releases the queue corresponding to the application. For this, the application unit 111 requests the network driver 113 to release the QoS setting of the application in step S609. Then, the network driver 113 cancels the queue allocation of the application in step S611, and returns to the application unit 111 a result indicating that the QoS setting according to the application is canceled in step S613. Accordingly, the session connection between the TE 110 and the IMS 300 is also ended.

As described above, "deactivation of QoS" means releasing a queue corresponding to the application from the viewpoint of the TE 110. A method of releasing such a queue will be described below. 7 is a flowchart illustrating a queue deassigning method according to an embodiment of the present invention.

Referring to FIG. 7, in step S701, the application unit 111 transmits an identifier (QoS_ID) of an application for which QoS setting is to be canceled to the network driver 113. FIG. Then, the network driver 113 searches for a queue corresponding to the identifier (QoS_ID) in step S703. If the corresponding queue exists in step S705, the network driver 113 releases the corresponding queue in step S707. Then, in step S709, the network driver 113 returns a result informing the application unit 111 that the queue has been released SUCCESS. On the other hand, if the corresponding queue does not exist in step S705, the network driver 113 returns to step S709 that the queue is released (SUCCESS) to the application unit 111 .

As described above, according to the embodiment of the present invention, the network driver 113 allocates a queue for each application. Packets according to usage of each application are input to such a queue. The input packets are scheduled and transmitted according to the QoS of each application. A QoS scheduling method and a data transmission method according to scheduling will be described.

First, a structure of a queue allocated to each application according to an embodiment of the present invention will be described. 8 is a diagram for explaining a structure of a queue according to an embodiment of the present invention.

Referring to FIG. 8, a queue according to an embodiment of the present invention is allocated to each application. In FIG. 8, it is assumed that the first to third queues 10, 20, and 30 according to three applications are allocated.

Referring to FIG. 8, the data structure of the queue includes a QoS profile (QoS_Profile), schedule information (Schedule_Info), and packet link information (HeadList of PacketQueue).

As described above, the QoS profile (QoS_Profile) includes identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value), maximum and minimum data rate (Max_DataRate, Min_DataRate), jitter time (Tolerated Jitter), and priority.

The identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value) is information for extracting an identifier (QoS_ID), and the identifier (QoS_ID) is for identifying an application corresponding to the packet when the packet is input to the network driver. At this time, "QoS_ID_Offset" indicates a position where data in which an identifier (QoS_ID) is stored in an incoming packet is started, and "QoS_ID_Size" Also, "QoS_ID_Value" means a port number (Source Port Nuber) of the packet. Therefore, the network driver 113 can extract the identifier (QoS_ID) through "QoS_ID_Offset", "QoS_ID_Size" and "QoS_ID_Value".

The maximum and minimum transmission rates (Max_DataRate, Min_DataRate) mean the maximum and minimum transmission rates per packet to guarantee the QoS of the application, and the unit may be "bps". Tolerated jitter means that the packet is delayed due to jitter. The unit of the jitter time (Tolerated Jitter) can be "ms". In addition, the priority refers to a predetermined one according to each application.

The schedule information (Schedule_Info) includes an output time (Next_Schedule_Time) and queue link information (Prev_Scheduled_Queue, Next_Scheduled_Queue). The output time (Next_Schedule_Time) means the output time of each packet of the corresponding queue according to the scheduling. The queue link information (Prev_Scheduled_Queue, Next_Scheduled_Queue) is link information with another queue, and each queue is linked according to the output time.

Packet link information (HeadListofPacketQueue) is link information of packets input to the queue.

As described above, the queue according to the embodiment of the present invention stores the output time of packets input to each queue, and outputs a packet accordingly. On the other hand, when the output times are the same, the QoS profile is referred to, and the jitter time is output in a short sequence. When the jitter time is the same, the packet is output according to the priority order.

A scheduling method according to an embodiment of the present invention will now be described based on the above-described structure of a queue. 9 is a diagram for explaining a QoS-based scheduling method according to an embodiment of the present invention.

9, the application unit 111 inputs data to the network driver 113 for each packet when data corresponding to the application is generated. Then, the network driver extracts the identifier (QoS_ID) from the packet in step S901 and searches for a queue corresponding to the extracted identifier in step S903.

If the queue exists in step S905, the network driver 113 proceeds to step S907 according to the search result in step S903, and otherwise proceeds to step S909. That is, if there is a queue corresponding to the identifier (QoS_ID), the network driver 113 inputs the packet to the queue in step S907. On the other hand, if there is no queue corresponding to the identifier (QoS_ID), the network driver 113 inputs the packet to the predetermined queue in step S909. That is, when a queue is not allocated according to a specific application, the network driver 113 inputs a packet to a predetermined queue.

After the packet is input to the queue as described above, the network driver 113 performs the scheduling in step S911.

According to an embodiment of the present invention, data input to each queue is output in a packet unit according to scheduling for determining an output order of a plurality of allocated queues. At this time, the output time of each packet is calculated according to the QoS of each application, and the packet is outputted in the order of the packets whose output time is fast according to the calculated output time. A method of calculating such an output time will be described. 10A to 10D are diagrams for explaining an output time calculating method according to the QoS of each application.

Referring to FIG. 10, the network driver 113 calculates the output time as shown in the following flow for each queue. At this time, scheduling is performed according to the QoS (in particular, the minimum transmission rate) according to the queue allocated to each application.

The network driver 113 determines whether the current time exceeds the output time of the packet stored in the queue in step S1001.

If the determination result in step S1001 is exceeded, the network driver 113 proceeds to step S1003 and calculates the output time of the packet according to Equation (1) below.

Next_Schedule_Time = Current_Time + (Size of Next Packet / min_DataRate)

Referring to Equation (1), "Next_Schedule_Time" means the output time of the packet, and "Current_Time" means the current time. Also, "Size of Next Packet" indicates the size of a packet to be transmitted, and "min_DataRate" Therefore, the value obtained by dividing the packet size (b) by the minimum transmission rate (bps) as in the "Size of Next Packet / min_DataRate" indicates that the maximum transmission delay time of Next Packet / min_DataRate "). Therefore, packets not yet output according to Equation (1) are scheduled to be transmitted after the maximum delay time according to the QoS at least at the current time. An example of such a scheduling is shown in FIG. According to FIG. 10B and Equation (1), the output of the packet is performed after the maximum transmission delay time of the packet at the current time.

If the result of the determination in step S1001 does not exceed the determination result, the network driver 113 proceeds to step S1005 and calculates the delay time according to the following equation (2).

diff_Time = (Size of Next Packet / min_DataRate) + Next_Schedule_Time - Current_Time

Referring to Equation (2), "diff_Time" means a delay time. The delay time is for determining how much time is delayed after the output time of the output packet. Here, "Next_Schedule_Time" is the output time of the previously output packet, "Current_Time" is the current time, "Size of Next Packet" is the size of the packet to be transmitted, and "min_DataRate"

If the delay time calculated in step S1007 is negative, the network driver 113 proceeds to step S1009 and sets the output time of the packet as the current time. An example in which such an output time is calculated is shown in Fig. 10C. As shown in the figure, in the case of step S1009, the next packet is not output even after the output time of the previously output packet and after the maximum transmission delay time. Therefore, it is scheduled to output the packet immediately at the current time.

On the other hand, if the calculated delay time is not negative in step S1007, the network driver 113 proceeds to step S1011 and sets the output time of the packet as the sum of the current time and the delay time. That is, the output time of the packet in step S1011 is the time after the maximum transmission delay time in the output time of the previously output packet ("Next Schedule Time"). An example in which such an output time is calculated is shown in Fig. As shown in the figure, the current time does not exceed the maximum transmission delay time in the output time of the output packet. In this case, the output time is set at the point of time when the maximum transmission delay time elapses from the output time of the previously output packet.

As described above, the output time of the packet input to each queue is determined. A data transmission method according to an embodiment of the present invention will now be described. 11 is a diagram for explaining a data transmission method according to an embodiment of the present invention.

Referring to FIG. 11, the network driver 113 retrieves the output times of the packets stored in the respective queues calculated as described with reference to FIG. 10A in step S1101. Then, the network driver 113 sorts each of the queues in output time order in step S1103.

At this time, the network driver 113 determines whether a queue having the same output time exists in step S1105. If it is determined in step S1105 that there is a queue having the same output time, the network driver 113 proceeds to step S1107 and compares the jitter time (Tolerated jitter) of the same queue of the output time. Here, the jitter time refers to the QoS profile.

Then, in step S1109, the network driver 113 arranges the same cues of the output time in the order of short jitter time.

At this time, in step S1111, the network driver 113 determines whether there is a queue having the same jitter time among queues arranged in order of short jitter time.

If it is determined in step S11111 that there is a queue having the same jitter time, the network driver 113 searches for priorities of queues having the same jitter time in step S1113. Here, the priority refers to the QoS profile. Then, the network driver 113 sorts cues having the same jitter time in descending order of priority in step S1115.

As described above, when the queues are sorted in consideration of the calculated output time, jitter time, and priority, the network driver 113 outputs the packet to the SS 120 in the sorted queue order in step S1117. On the other hand, in the case of an application to which a queue is not allocated, a packet is input to a predetermined queue (Default Queue).

As described above, the network driver 113 according to the embodiment of the present invention performs scheduling according to QoS (calculated output time, jitter time, and priority). Therefore, when the packet is output from the TE 110 to the SS 120, QoS can be guaranteed.

While the present invention has been described with reference to several preferred embodiments, these embodiments are illustrative and not restrictive. It will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit of the invention and the scope of the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram illustrating a configuration of a wireless network system according to an embodiment of the present invention; FIG.

2 is a diagram for explaining a schematic configuration of a terminal according to an embodiment of the present invention;

3 is a diagram for explaining a QoS setting method according to an embodiment of the present invention;

4 is a flowchart illustrating a queue allocation method according to an embodiment of the present invention.

5 is a diagram for explaining a QoS setting release method according to an embodiment of the present invention;

6 is a diagram for explaining a QoS setting release method according to an embodiment of the present invention;

7 is a flowchart illustrating a queue deassignment method according to an embodiment of the present invention.

8 is a diagram for explaining a structure of a queue according to an embodiment of the present invention.

9 is a diagram for explaining a QoS-based scheduling method according to an embodiment of the present invention.

10A to 10D are diagrams for explaining an output time calculating method according to the QoS of each application.

11 is a diagram for explaining a data transmission method according to an embodiment of the present invention.

Claims (12)

A data transmission apparatus of a terminal for providing QoS, A terminal equipment (TE) for executing a plurality of applications for providing a wireless communication service, and a subscriber station (SS) for transmitting data according to a wireless standard, The TE includes an application unit for outputting a data packet generated by execution of each application, a queue unit for assigning a queue to each application, inputting the data packet to the allocated queue, And outputting the data to the SS according to the scheduling information. A method of transmitting data in a terminal for providing QoS (Quality of Service) Assigning a queue to an application of the terminal; Inputting a data packet generated in the application to the allocated queue; Scheduling a time to output the data packet according to a predetermined QoS of the application; And And outputting the data packet according to the scheduled time. 3. The method of claim 2, Wherein the application is a minimum transmission rate or a maximum transmission rate required to provide a service to a user when the application is executed. 3. The method of claim 2, wherein allocating a queue to an application of the terminal comprises: Obtaining a QoS identifier of the application; Determining whether there is a pre-allocated queue in the application using the identifier; And And allocating a queue corresponding to the application when a queue pre-allocated to the application does not exist. 3. The method of claim 2, wherein scheduling the time to output the data packet according to a predetermined QoS of the application comprises: Determining whether a current time of the terminal has exceeded an output time of a data packet input to the queue; And And scheduling the terminal to output a QoS guaranteed maximum transmission delay time when a time of the terminal exceeds an output time of a data packet input to the queue. 3. The method of claim 2, wherein scheduling the time to output the data packet according to a predetermined QoS of the application comprises: Determining whether a current time of the terminal has exceeded an output time of a data packet input to the queue; Calculating a delay time that is a time until the terminal's time after the output time of the previously output data packet if the terminal's time does not pass the output time of the data packet input to the queue; And And scheduling the current time of the terminal as an output time if the delay time is negative. 3. The method of claim 2, wherein scheduling the time to output the data packet according to a predetermined QoS of the application comprises: Determining whether a current time of the terminal has exceeded an output time of a data packet input to the queue; Calculating a delay time that is a time until the terminal's time after the output time of the previously output data packet if the terminal's time does not pass the output time of the data packet input to the queue; And And scheduling to output, when the delay time is a positive number, a maximum guaranteed transmission delay time after QoS has elapsed. 2. The method of claim 1, Wherein the application is a minimum transmission rate or a maximum transmission rate required to provide a service to the user when the application is executed. The network device according to claim 1, Acquiring a QoS identifier of the application, determining whether a queue pre-allocated to the application is present using the identifier, and allocating a queue corresponding to the application when the pre-allocated queue does not exist And the data transmission apparatus. The network device according to claim 1, Determining whether or not the current time of the terminal has exceeded the output time of the data packet input to the queue and if the time of the terminal has exceeded the output time of the data packet input to the queue, And outputting the maximum transmission delay time after the maximum transmission delay time has elapsed. The network device according to claim 1, The method comprising the steps of: determining whether the current time of the terminal has exceeded the output time of the data packet input to the queue; and if the time of the terminal is less than the output time of the data packet input to the queue, Wherein the scheduling unit schedules the current time of the terminal as an output time when the delay time is a negative number, and calculates a delay time that is a time until the terminal's time after the output time of the data packet. The network device according to claim 1, The method comprising the steps of: determining whether the current time of the terminal has exceeded the output time of the data packet input to the queue; and if the time of the terminal is less than the output time of the data packet input to the queue, Wherein the scheduling is performed such that a delay time which is a time until a time of the terminal after an output time of a data packet is calculated and is outputted after a maximum transmission delay time in which QoS is assured is elapsed when the delay time is positive. Device.

Images