KR20100027473A - A method for data transmission guaranteed quality of service in a terminal equipment and an apparatus thereof - Google Patents

Abstract

PURPOSE: A method for transmitting data of a terminal to provide quality of service and an apparatus thereof are provided to supply a service by guaranteeing the quality of service without a bottleneck phenomenon. CONSTITUTION: TE(Terminal Equipment)(110) executes a plurality of applications for providing a wireless communication service. An SS(Subscriber Station)(120) transmits data following application execution of the TE according to radio standards. An application unit(111) of the TE outputs data due to execution of each application. A network driver(113) outputs the data to the SS by scheduling the outputted data according to QoS of a corresponding application.

Description

A method for data transmission guaranteed quality of service in a terminal equipment and an apparatus

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 capable of efficiently guaranteeing QoS even when data transmission is not smooth.

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

In order to provide a QoS service in mobile WiMAX (mWiMAX), a scheduling service is provided using a classifier in the MAC layer. However, in many cases, it is difficult to guarantee the QoS. In other words, if the amount of data transferred from the TCP / IP stack of the TE is to transmit the data of more than the HW Interface Throughput of the device, and if the throughput of the wireless section is reduced, A bottleneck occurs when an application attempts to transmit a high data rate packet. In this case, it becomes difficult to guarantee the QoS of each application and also to guarantee the performance.

Accordingly, an object of the present invention is to provide a method and apparatus capable of providing a service by guaranteeing QoS without a bottleneck.

In order to achieve the above object, a data transmission apparatus of a terminal for providing QoS according to an exemplary embodiment of the present invention includes a terminal (TE) and a terminal application 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 according to a wireless standard, wherein the TE includes an application unit for outputting data generated by execution of each application, and the output data according to a QoS of a corresponding application. It is characterized in that it comprises a; network driver for scheduling and outputting to the SS.

The network driver may receive a QoS profile for each application from the application unit, allocate a queue according to the received QoS profile, and schedule packets input to the allocated queue.

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

According to a preferred embodiment of the present invention, there is provided a data transmission method of a terminal for providing a QoS, comprising the steps of: allocating a queue corresponding to an application providing a service through a wireless communication connection; Inputting packets of an application allocated to each of the queues, scheduling a time for outputting the packets according to a predetermined QoS of each application, and outputting the packets according to the calculated time. Include.

The assigning process may include 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, since the network driver performs scheduling according to QoS, it is possible to provide a service by guaranteeing QoS without a bottleneck. Accordingly, there is an advantage of increasing the use of a wireless communication network.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to distract from 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 exemplary 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 a wireless access standard as an end point of a wireless channel. The terminal 100 according to the embodiment of the present invention includes a terminal equipment (TE) 110 and a subscriber station (SS) 120.

The base station apparatus 200 serves to connect 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.

RAS (Radio Access Station) 210 is a device that connects a wireless network and a wired network, controls a wireless channel according to the characteristics of each network, and is connected with a wired network to provide a wireless packet data service directly to the terminal 100. do. The main functions are to transmit and receive radio signals, to perform modulation and demodulation signal processing for packet traffic signals, and to perform protocol processing and routing functions.

An access control router (ACR) 220 is connected to and manages a plurality of RASs 210 and performs a handover control function to ensure high-speed mobility in the ACR 220. The ACR 220 controls the terminal 100 and the RAS 210 and routes the IP packet. From the standpoint of data traffic, the ACR 220 can be viewed as a router.

IP Multimedia Subsystem (IMS) 300 is a home subscriber server (HSS), a subscriber location function (SLF), a session charging function (SCF), a call session control function (CSCF) (P-CSCF, I). (CSCF, S-CSCF, etc.), PDF (Policy Decision Function), Application Servers (AS), Media Resource Function (MRF), Breakout Gateway Control Function (BGCF), Media Gateway Controller Function (MGCF). It may include a charging collector function (CCF), an event charging function (ECF). IMS (IP Multimedia Subsystem) is a core network infrastructure that provides various multimedia services based on IP. As described above, the IMS 300 may have various entities, and the set of such entities will be referred to as the IMS 300.

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

HSS supports IMS entities that perform session control as an evolutionary form of HLR into a user information database. The HSS includes user related subscription information related to multimedia session control, that is, user location information, security information for authentication and permission of the user, and user profile information including a service subscribed to by the user.

The CSCF is a SIP server that processes SIP signals in the IMS 300. P-CSCF is a SIP proxy server that is the first connection point for an IMS terminal. P-CSCF may exist in a home network or a visited network. The P-CSCF is assigned to the IMS terminal upon registration in the IMS network and does not change during the registration period. The P-CSCF may include or be configured separately from the PDF, and performs QoS control functions such as policy control and band management.

I-CSCF is located at the boundary of the management domain if no border function exists. Thus, the IP address is published in the DNS of the domain so that it can be found by servers in other domains and used as input nodes of the network. The I-CSCF queries the HSS for the user's location and forwards the SIP message to the S-CSCF to which the user is assigned. S-CSCF is a central node of the signaling layer and performs session control as a SIP server. Always on your home network, download and upload user profiles from HSS. Binds user's location and SIP address when registering SIP.

Application servers (ASs) host and run services and interface with the S-CSCF using SIP. Examples of such services include caller ID (CLIP, CLIR, etc.), call waiting, call hold, push-to-talk, call transfer, call forwarding, call closure service, legitimate interception, service announcement, conference call service, voice mail, Services include text and voice conversion, location-based services, SMS, MMS, presence information and instant messaging. The term "service" as used in the embodiments of the present invention includes those as described above.

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

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

Looking at each component of the terminal 100 in more detail, TE (110) provides a user with an application for providing a service using a variety of wireless communication, SS 120 is a wireless connection for providing such a service It is for. Accordingly, the TE 110 provides the SS 120 with packet data generated according to the use of each application, and the SS 120 transmits the data to the base station apparatus 200. In addition, the SS 120 receives data from the base station apparatus 200 and transmits the data to the TE 110.

Application unit 111 has a plurality of applications (application) that can provide a variety of services, and provides them to the user through a predetermined interface. In addition, the application unit 111 provides the network driver 113 with QoS information including the QoS profile of each application. The application unit 111 provides the network driver 113 with packets generated according to the use 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 for each application according to the request of the application unit. Then, when a packet is input, 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 corresponding packet to the SS 120. In order to perform the above-described function, the network driver 113 is a classification module (QoS Classification) for inputting the packet received by the application program to the assigned queue, queue management for managing the input and output of the packet input to each queue Module (Queue Manager), a scheduler (Packet Scheduler) for scheduling and outputting the packets input to each queue.

The SS 120 transmits a packet input from the TE 110 to the base station apparatus 200 according to a wireless standard. To this end, the SS 120 may be provided with a wireless communication module for performing wireless communication with the device for the connection with the TE (110) and the base station device (200). The SS 120 also transmits a packet according to the corresponding application according to the set QoS of each application.

According to an embodiment of the present invention, in order to perform data transmission according to QoS of the terminal 100, scheduling is performed for each QoS according to each application. For example, scheduling is performed according to the data rate. To this end, the application unit 111 provides the network driver 113 with a QoS profile of each application, and the network driver 113 allocates a queue for each application. After allocating a queue and generating data for each application, the application unit 111 provides the generated data to the network driver for each packet. 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 different devices, the TE 110 and the SS 120 are connected to each other through a specific interface. Specific interfaces include wired and wireless. For example, TE 110 may be a portable device such as a notebook (note book), SS 120 may be a so-called "network adapter", "network device" or "cave".

According to an 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 QoS, thereby enabling the air transmission capability of the SS 120. Even if this is degraded or if a specific application generates excessive traffic, it is possible to prevent the transmission performance from dropping.

Next, the data transmission method for guaranteeing QoS of the terminal described above will be described in more detail. Each application has a QoS to provide that service. For example, QoS may be a minimum or maximum transmission rate required for the corresponding application to be executed to provide a service to a user. According to an 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 released when the application is terminated.

First, a description will be given of a QoS setting method when requesting a service according to each application according to an embodiment of the present invention. 3 is a diagram illustrating 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, the IMS 300 transmits an information message (SIP 183) including an authentication token (Authorization Token) for the corresponding service to the TE 110 in step S303. The message exchange between the TE 110 and the IMS 300 is performed through the base station apparatus 200 and the SS 120.

Upon receiving the authentication token (Authorization Token), the TE 110 transmits a QoS reservation request message (QoS RESERVATION REQUEST) to the SS 120 in step S305. The QoS reservation request message includes an authentication token for the corresponding service and an application handle (App_Handle) for handling an application that performs the corresponding service. Receiving the QoS reservation request message, the SS 120 reserves a QoS for the base station apparatus 200 and the corresponding application in step S307.

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

Accordingly, the TE 110 performs a process for "setting QoS" reserved between the application unit 111 and the network driver 113 by itself. "QoS setting" means that a queue corresponding to the application is allocated from the terminal's point of view.

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

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

The TE 110 may set the QoS through the above-described steps S311 to S315 and thus provide a service for guaranteeing the QoS through the above-described media channel. The above-described processes of steps S311 to S315 are preferably performed before completion of session establishment.

Subsequently, when the TE 110 and the IMS 300 exchange response messages in steps S317 and S319 to complete session establishment, in step S321, a media channel according to the QoS set forth above is formed.

As described above, "QoS setting" means that a queue corresponding to the application is allocated from the terminal's point of view. This queue allocation method will be described.

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. 3. Referring to FIG. 4, in step S401, the application unit 111 transmits a QoS profile of an application to set QoS to the network driver 113. The QoS profile includes identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value), maximum and minimum data rates (Max_DataRate, Min_DataRate), acceptable jitter time (abbreviated as "jitter time"), priority, etc. do.

The identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value) is information for extracting the 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 the position where the data storing the identifier QoS_ID is started in the input packet, and "QoS_ID_Size" indicates the size of the data where the identifier QoS_ID is stored from the starting position. In addition, "QoS_ID_Value" means a port number (Source Port Nuber) of the corresponding packet. Accordingly, the network driver 113 may extract the identifier QoS_ID through "QoS_ID_Offset", "QoS_ID_Size", and "QoS_ID_Value".

The maximum and minimum data rates Max_DataRate and Min_DataRate mean the maximum and minimum data rates per packet to guarantee the QoS of the corresponding application, and the unit may be "bps". Tolerated Jitter means the time that the packet can be delayed due to the occurrence of jitter. The unit of jitter time can be "ms". In addition, priority refers to a preset value according to each application.

Upon receiving the QoS profile as described above, the network driver 113 determines whether the QoS of the corresponding application can be supported in step S403. For example, assuming that the maximum transmission capacity of the network driver is 100bps and the transmission capacity of pre-allocated queues is 80bps, the network driver may support only an application having a maximum transmission rate Max_DataRate of 20bps or less.

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

As a result of the search, if the queue according to the identifier is not allocated in step S407, the network driver 113 proceeds to step S409 and newly assigns a queue according to the corresponding application. Thereafter, the network driver 113 returns a result indicating that the queue has been successfully allocated to the application unit 111 at step S411. On the other hand, if there is a pre-assigned queue according to the identifier, the network driver 113 returns a result indicating that the allocation of the queue to the application unit 111 failed (FAIL) in step S413.

As described above, the assigned queue is maintained until the service according to the corresponding application is terminated. Termination of the service is made at the request of the TE 110 or the IMS 300. Next, a method of releasing QoS setting at the end of service according to each request of the TE 110 and the IMS 300 will be described.

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

Referring to FIG. 5, in operation 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, thereby providing a service.

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

Then, the TE 110 transmits a QoS delete request message (QoS DELETE REQUEST) in step S505. The QoS delete 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 apparatus 200 delete the QoS setting for the corresponding application (QoS DELETE Procedure), and in step S509, transmit a QoS delete response message (QoS DELETE RESPONSE) indicating this to the TE. do. The QoS delete response message includes an application handle (App_Handle) and a QoS handle (QoS_Handle).

Meanwhile, the TE 110 performs a process for releasing QoS setting between the application unit 111 and the network driver 113 by itself. "Unset QoS" means that the TE 110 releases a queue corresponding to the corresponding application. To this end, the application unit 111 requests the network driver 113 to release the QoS setting of the corresponding application in step S511. Then, the network driver 113 releases the queue allocation of the corresponding application in step S513 and returns to the application unit 111 a result indicating that the QoS setting according to the corresponding application is released 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 sent, the session connection between the TE 110 and the IMS 300 is terminated. Here, the response message (SIP 200 OK) is a response to the end message of the previous step (S501).

In the foregoing, FIG. 5 has described a method of canceling QoS setting at the end of a service according to a request of the TE 110. Subsequently, a method of canceling QoS setting at the end of service according to the request of the IMS 300 will be described. 6 is a diagram for describing a method of canceling QoS setting according to an embodiment of the present invention.

Referring to FIG. 6, step S601 indicates that 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, so that a service is provided through the formed channel.

It is assumed that a case in which the session-connected channel is not necessary in step S603 occurs due to service termination during service provision, such as step S601.

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

Then, the TE 110 itself performs a process for releasing QoS set between the application unit 111 and the network driver 113. "Unset QoS" means that the TE 110 releases a queue corresponding to the corresponding application. To this end, the application unit 111 requests the network driver 113 to release the QoS setting of the corresponding application in step S609. Then, the network driver 113 releases the queue allocation of the corresponding application in step S611, and returns to the application unit 111 a result indicating that the QoS setting according to the corresponding application is released in step S613. Accordingly, the session connection between the TE 110 and the IMS 300 is also terminated.

As described above, "releasing QoS" means that the TE 110 releases a queue corresponding to the corresponding application from the standpoint of the TE 110. This method of de-queueing will be described. 7 is a flowchart illustrating a queue allocating method according to an exemplary embodiment of the present invention.

Referring to FIG. 7, the application unit 111 transmits the identifier QoS_ID of the application to release the QoS setting to the network driver 113 in step S701. Then, the network driver 113 searches for a queue corresponding to the identifier QoS_ID in step S703. As a result of the search, if there is a corresponding queue in step S705, the network driver 113 frees the corresponding queue in step S707. Thereafter, the network driver 113 returns a result indicating that the queue has been successfully released to the application unit 111 in step S709. On the other hand, if the corresponding queue does not exist in step S705, the network driver 113 returns that the queue is successfully released to the application unit 111 in step S709 (SUCCESS). .

As described above, according to an embodiment of the present invention, the network driver 113 allocates a queue for each application. In such a queue, a packet according to the use of each application is input. The packets input in this way are scheduled and transmitted according to the QoS of each application. Such a scheduling method according to QoS 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 view for explaining the 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 for each application. In FIG. 8, it is assumed that first to third queues 10, 20, and 30 according to three applications are allocated.

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

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

The identifier information (QoS_ID_Offset, QoS_ID_Size, QoS_ID_Value) is information for extracting the 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 the position where the data storing the identifier QoS_ID is started in the input packet, and "QoS_ID_Size" indicates the size of the data where the identifier QoS_ID is stored from the starting position. In addition, "QoS_ID_Value" means a port number (Source Port Nuber) of the corresponding packet. Accordingly, the network driver 113 may extract the identifier QoS_ID through "QoS_ID_Offset", "QoS_ID_Size", and "QoS_ID_Value".

The maximum and minimum data rates Max_DataRate and Min_DataRate mean the maximum and minimum data rates per packet to guarantee the QoS of the corresponding application, and the unit may be "bps". Tolerated Jitter means the time that the packet can be delayed due to the occurrence of jitter. The unit of jitter time can be "ms". In addition, priority refers to a preset value according to each application.

The schedule information Schedule_Info includes output time Next_Schedule_Time and queue link information Prev_Scheduled_Queue and 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.

The packet link information (HeadListofPacketQueue) refers to link information of packets input to the corresponding queue.

As described above, the queue according to an embodiment of the present invention stores the output time of packets input to each queue, and outputs the packet accordingly. On the other hand, when the output times are the same, the jitter time is output in the shortest order with reference to the QoS profile, and when the jitter times are the same, the packets are output in accordance with priority.

Next, a scheduling method according to an embodiment of the present invention will be described based on the structure of the above-described queue. 9 is a diagram illustrating a scheduling method according to QoS according to an embodiment of the present invention.

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

According to the search result of step S903, the network driver 113 proceeds to step S907 if the corresponding queue exists in step S905, and otherwise proceeds to step S909. That is, if there is a queue corresponding to the identifier QoS_ID, the network driver 113 inputs a packet to the corresponding queue in step S907. On the other hand, if the queue corresponding to the identifier (QoS_ID) does not exist, the network driver 113 inputs the packet to the default queue (S909). In other words, when a queue is not assigned according to a specific application, the network driver 113 inputs a packet to any predetermined queue.

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

According to an exemplary embodiment of the present invention, data input to each queue is output in packet units according to a scheduling that determines an output order of a plurality of allocated queues. At this time, the output time in packet units is calculated according to the QoS of each application, and the packets are output in the order of the packets having the fastest output time according to the calculated output time. A method of calculating such an output time will be described. 10A to 10D are diagrams for describing an output time calculation method according to QoS of each application.

Referring to FIG. 10, the network driver 113 calculates an output time as shown in the following flow for each queue. At this time, scheduling is performed according to QoS (particularly, 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 of step S1001 does not exceed, 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, "Current_Time" means the current time. In addition, "Size of Next Packet" represents the size of the packet to be transmitted, "min_DataRate" is the minimum transmission rate. Therefore, the value of the packet size (b) divided by the minimum transmission rate (bps), such as "Size of Next Packet / min_DataRate", is the maximum transmission delay time ("Size") required for transmission of packets output from the corresponding queue when QoS is guaranteed. of Next Packet / min_DataRate "). Therefore, according to Equation 1, a packet not yet output is scheduled to transmit after the maximum delay time according to QoS at least at the current time. An example of such scheduling is shown in FIG. 10B. 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 determination result of step S1001 does not exceed, the network driver 113 proceeds to step S1005 and calculates a delay time according to Equation 2 below.

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

Looking at 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 previously 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, "min_DataRate" is the minimum transmission rate.

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 to the current time. An example in which this output time is calculated is shown in Fig. 10C. As shown, in the case of step S1009, the next packet is not output after the maximum transmission delay time after the output time of the previously output packet. Therefore, we schedule the packet output at the current time.

If the delay time calculated in step S1007 is not negative, the network driver 113 proceeds to step S1011 to set the output time of the packet to the sum of the delay time and the current time. That is, in step S1011, the output time of the corresponding packet is the time after the maximum transmission delay time from the output time (“Next Schedule Time”) of the previously output packet. An example in which this output time is calculated is shown in FIG. 10D. As shown, the current time does not exceed the maximum transmission delay time in the output time of the pre-printed packet. In this case, the output time is set when the maximum transmission delay time elapses from the output time of the previously output packet.

As described above, the output time of the packets input to each queue is determined. Based on this, a data transmission method according to an embodiment of the present invention will be described. 11 is a diagram illustrating a data transmission method according to an embodiment of the present invention.

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

In this case, the network driver 113 determines whether a queue having the same output time exists in step S1105. As a result of the determination in step S1105, if a queue having the same output time exists, the network driver 113 proceeds to step S1107 to compare the jitter time (Tolerated Jitter) of the same queue of the output time. Here, jitter time refers to the QoS profile.

The network driver 113 then sorts the same queues of output time in order of jitter time in step S1109.

In this case, the network driver 113 determines whether a queue having the same jitter time exists among queues arranged in the order of shortest jitter time in step S1111.

As a result of the determination in step S11111, if there are queues with 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, in step S1115, the network driver 113 sorts the queues having the same jitter time in ascending order of priority.

As described above, when the queues are aligned in consideration of the calculated output time, jitter time and priority, the network driver 113 outputs the packets to the SS 120 in the order of the queues arranged in step S1117. On the other hand, in the case of an application to which a queue is not allocated, the application is input to a predetermined queue, and a packet input to such a queue is transmitted when there is room for transmission processing.

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

While the present invention has been described using some preferred embodiments, these embodiments are illustrative and not restrictive. As such, those of ordinary skill in the art will appreciate that various changes and modifications can be made according to equivalents without departing from the spirit of the present invention and the scope of rights set forth in the appended claims.

1 is a diagram showing the configuration of a wireless network system according to an embodiment of the present invention.

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

3 is a diagram illustrating 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 describing a method of canceling QoS setting according to an embodiment of the present invention.

6 is a diagram for describing a method of canceling QoS setting according to an embodiment of the present invention.

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

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

9 is a diagram illustrating a scheduling method according to QoS according to an embodiment of the present invention.

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

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

Claims (2)

In the data transmission apparatus of the terminal for providing QoS, 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 the application execution of the TE according to a wireless standard, The TE includes an application unit for outputting data generated by the execution of each application, and a network driver for scheduling the output data according to the QoS of the corresponding application and outputting the data to the SS. Device for transmitting data for the terminal. In the data transmission method of the terminal for providing QoS, Allocating queues corresponding to applications providing a service through a wireless communication connection, Inputting packets of applications to each of the assigned queues; Scheduling a time for outputting the packets according to a predetermined QoS of each of the applications; And transmitting the packets according to the calculated time.

Images