KR20050092606A - Traffic memory management method in wireless communication terminal - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a traffic memory management method in a wireless communication terminal.

2. The technical problem to be solved by the invention

According to an embodiment of the present invention, after a topmost (uplink data transmission) or lowest (downlink data transmission) task is first allocated a memory for data transmission and buffers data in a wireless communication terminal or the like, the data of the next layer of the task is stored. An object of the present invention is to provide a traffic memory management method in a wireless communication terminal for effectively using a limited memory by passing a pointer of a stored memory.

3. Summary of the Solution of the Invention

In the traffic memory management method of a wireless communication terminal, the memory management task receives a data transmission request signal from another task and checks that the length field included in the packet header is less than or equal to the maximum data size. Confirmation step; A memory allocation possibility confirming step of confirming that data memory allocation is possible in a size in which an offset region is further included in the value of the length field included in the packet header as the value of the length field included in the packet header is less than or equal to the maximum data size; A data memory allocation step of allocating a data memory area as the data memory can be allocated; And a memory pointer transfer step of allowing the memory management task to return a start pointer of the allocated data memory area to the other task so that the memory management task can be transferred to a task of a next layer.

4. Important uses of the invention

The present invention is used in a wireless communication terminal.

Description

Traffic memory management method in wireless communication terminal

The present invention relates to a method of managing traffic memory in a wireless communication terminal, and more particularly, a memory for transmitting data by a highest (uplink data transmission) or lowest (downlink data transmission) task in a wireless communication terminal. After the first allocation of the buffer to the data, the next layer of the task to the traffic memory management method in a wireless communication terminal for effectively using the limited memory by passing a pointer to the memory where the data is stored.

In the present invention, a wireless communication terminal is a mobile communication terminal, a personal mobile communication terminal (PCS), a personal digital terminal (PDA), a smart phone, a next generation mobile communication terminal (IMT-2000), wireless communication while carrying an individual such as a wireless LAN terminal Say this is possible terminal. Hereinafter, a GPRS (General Packet Radio Service; GPRS), which is a European 2.5G mobile communication terminal, will be described as an example.

As research to support the transmission of packet data in a circuit data transmission network has already been conducted, a generation switched from a second generation network to a packet switched scheme (PSPDN: Public Switched Public Data Network) Packet data can now be transferred.

However, this method has a disadvantage in that it has an unfair charging system and low efficiency because it continues to occupy one line regardless of the flow of packet data. That is, in the PSPDN method, since a radio channel for transmission is allocated at the air interface stage from the start of the call to the end of the call, in case of traffic that generates data such as the Internet, the resource utilization is limited. Inefficiency exists.

In order to solve this problem, GPRS has been defined using the European mobile communication network (GSM). GPRS provides packet switched bearer service in wired as well as air interfaces.

In addition, since the channel is allocated only when the traffic occurs in the GPRS scheme and returned immediately after transmission, the inefficiency of resource utilization is greatly reduced. This principle allows multiple users to share one physical channel. This is often called statistical multiplexing.

In other words, the GPRS scheme improves the efficiency of radio resource usage by statistical multiplexing, enables charging based on the amount of data, and provides advantages such as high data rate and short connection setup time. And simplify the connection to the packet data network.

1 is a configuration diagram of an embodiment of a GPRS system to which the present invention is applied.

As shown in FIG. 1, the GPRS system to which the present invention is applied includes a Serving GPRS Support Node (SGSN) 11, a Gateway GPRS Support Node (GGSN) 13, a mobile communication terminal 12, and a home location register ( HLR 14, terminal identification register (EIR), base station (BTS), base station controller (BSC), switching center (MSC), SMS gateway switching center (SMS-GMSC) and the like.

The GPRS system adds a GPRS support node (GSN) for transferring and routing data between the mobile communication terminal 12 and the packet data network (PDN) to the structure of a conventional European mobile communication network (GSM). Has

First, the Serving GPRS Support Node (SGSN) 11 is responsible for transmitting a packet transmitted by the mobile communication terminal 12 in the management area or directed to the mobile communication terminal 12. That is, SGSN 11 performs functions such as packet routing and delivery, mobility management (attach, detach, location management), logical link management, and authentication and charging.

At this time, the location information (current cell, current visitor location register (VLR)), user profile (IMSI), packet data network (PDN) of subscribers in the management area Address to be used) is stored in a database held by the SGSN 11.

The function of the SGSN 11 to manage the mobility of the mobile communication terminal 12 will be described in more detail. First, the SGSN 11 confirms that the user has the correct authority, and then copies the user profile information from the home location register (HLR) 14. Then, a packet temporary mobile subscriber identity (PTMSI) is assigned to temporarily distinguish users. The mobile communication terminal 12 for using the GPRS service must perform this attachment at initialization. On the contrary, the procedure of disconnecting from the GPRS network at the request of the mobile communication terminal 12 or SGSN 11 is called detach.

The Gateway GPRS Support Node (GGSN) 13 is located between the GPRS backbone network and an external packet data network (PDN). That is, the GGSN 13 converts the packet received from the SGSN 11 into an appropriate packet data protocol (PDP) and transmits the packet to the other packet data network (PDN).

Conversely, the GGSN 13 delivers the packet received from the external packet data network (PDN) to the SGSN 11 through the reverse process. The main task here is to convert between a packet data protocol (PDP) address valid in an external packet data network (PDN) and an address of a mobile communication terminal 12 valid in a European mobile communication network (GSM) network.

The GGSN 13 needs to know the SGSN 11 currently managing the mobile communication terminal 12 in order to deliver the packet received from the external packet data network (PDN) to the mobile communication terminal 12. Thus, the GGSN 13 manages the user's current SGSN information in a database along with the user profile. In addition, the GGSN 13 performs authentication and charging functions similarly to the SGSN 11.

That is, the mobile communication terminal 12 that has successfully completed the GPRS attach procedure should be given at least one address for use in a packet data network (PDN). For example, if an external packet data network (PDN) is an Internet Protocol (IP) network, an Internet Protocol (IP) address should be assigned. This address is called a packet data protocol (PDP) address.

In addition, the GGSN 13 transfers packet data between the mobile communication terminal 12 and the packet data network (PDN) by using mapping information between the PDP address and the International Mobile Subscriber Identity (IMSI) address. For example, when a PDP address is dynamically allocated, the PDP address is allocated and activated / deactivated.

On the other hand, the mobile communication terminal 12 can use the existing circuit switched services (voice, data, SMS) and GPRS services in parallel. In consideration of this, the GPRS mobile communication terminal 12 may be classified into three types. First, class A is a terminal that can use GPRS and GSM services at the same time, and class B is a terminal that can be attached to both GPRS and GSM services at the same time, but can receive service at any one time. C is a terminal which can register both GPRS service and GSM service, but does not support simultaneous registration.

The mobile communication terminal 12 also creates a session, which is an entity for connecting to a packet data network (PDN). At this time, a packet data protocol (PDP) context is generated for each communication session, and various pieces of information representing the attributes of the session are stored.

Information included in the packet data protocol (PDP) context includes a PDP type (for example, IPv4), a PDP address (for example, an IP address) assigned to the mobile communication terminal 12, and a quality of service (QoS). ) Profile, a GGSN address that serves as an access point for a packet data network (PDN), and the like. This PDP context is stored in the mobile communication terminal 12, SGSN 11, GGSN (13). Once the PDP context is activated, the mobile communication terminal 12 can access an external packet data network (PDN) from this point on, and can transmit and receive packet data.

At this time, PDP context activation between the mobile communication terminal 12, SGSN 11, and GGSN 13 is performed by the following process.

First, the mobile communication terminal 12 transmits an active PDP context request message including its packet data protocol (PDP) context to the SGSN 11. At this time, if a PDP address is dynamically allocated, the PDP address field is empty.

Then, the SGSN 11 performs user authentication with respect to the mobile communication terminal 12 and, upon successful authentication, transmits a PDP context request message to the GGSN 13.

Then, the GGSN 13 adds a new entry to the PDP context table and returns a PDP context response message to the SGSN 11. At this time, entry information added to the PDP context table is referred to when the GGSN 13 routes packet data between the SGSN 11 and an external packet data network (PDN). In addition, the create PDP context response message includes a dynamically allocated PDP address.

Then, the SGSN 11 updates its PDP context table information according to the PDP context response message received from the GGSN 13 and moves the PDP context activation message. It communicates to the communication terminal 12 to inform that the new PDP context is activated.

In general, a many-to-many relationship is established between SGSN 11 and GGSN 13. That is, one GGSN 13 may be used as an interface point between multiple SGSNs 11 and one packet data network (PDN). In contrast, one SGSN 11 may use multiple GGSNs 13 to transmit packets to different packet data networks (PDNs).

Meanwhile, a protocol layer designed to convert a packet data protocol in a GPRS network to a packet data protocol in a GSM network is a sub-network dependent convergence protocol (SNDCP) layer. That is, in the GPRS network, data must be divided so that packet data generated in a Transmission Control Protocol / Internet Protocol (TCP / IP) layer or an application layer can be stored in a time slot of a GSM network. In addition, the SNDCP layer provides a plurality of connections made at the network layer in a lower layer logical link control (LLC) layer to deliver packet data between the SGSN 11 and the mobile communication terminal 12. Multiplex into virtual logical link units. Then, the user data and duplicate header information are compressed and restored.

In more detail, the functions provided by the SNDCP layer are as follows.

First, the SNDCP layer performs multiplexing of Network Layer Protocol Data Units (N-PDUs).

Second, the SNDCP layer performs end-to-end configuration of logical link control (LLC) in response.

Third, the SNDCP layer performs buffering of a network layer protocol data unit (N-PDU). That is, network layer protocol data units (SN-PDUs) compressed and split at the SNDCP layer must be buffered before being transmitted to the LLC layer.

Fourth, the SNDCP layer compresses data headers and data received from higher layers according to compression parameters. At this time, data compression is optional and supports both response and non-response methods. In addition, the compression parameter is determined by end-to-end negotiation before data transmission.

Fifth, the SNDCP layer divides a network layer protocol data unit (N-PDU) received from an upper layer into SN-PDUs of a size that can be transmitted in a GSM network, and recombines SN-PDUs received from a GSM network to network layer protocol data. Perform the function of converting into a unit (N-PDU).

Sixth, the SNDCP layer transmits the compressed and split network layer protocol data unit (SN-PDU) to the LLC layer according to a preset Quality of Service (QoS) parameter.

Seventh, the SNDCP layer performs a function of renegotiating end-to-end compression parameters when the SGSN 11 is changed or the quality of service (QoS) profile is changed.

Meanwhile, the conventional GSM mobile communication terminals implement each function as a task and interface with each other under the control of a real time operating system (RTOS). At this time, the real-time operating system (RTOS) controls each task using a function called a kernel interface, and performs a role of allocating / returning memory requested by each task.

When configuring a task in the mobile communication terminal 12, the following conditions should be kept in mind.

A task cannot exit an infinite loop after it has been initialized.

Each task can be in three states: Waiting, Ready, and Running.

Since there is only one central processing unit (CPU) in a mobile communication terminal, there is only one task running at a time. Of course, it may be composed of two or more CPUs, but in this case, the configuration of the real-time operating system (RTOS) is changed.

-Each task should be defined in the form of entry point, stack size, and priority provided by the real-time operating system (RTOS) kernel.

In order to add a GPRS function to the GSM mobile communication terminal, the existing tasks should be modified and additionally required functions should be implemented as tasks. In particular, the SNDCP task includes a user interface (UI) task for transmitting data using GPRS, an LLC task for end-to-end communication with a GPRS network, and a session management (SM) task for establishing a GPRS session. Will be signaled.

The SNDCP task assigns several PDP context data to multiple SAPIs and sends them to the LLC task, transmission of acknowledgment / unacknowledged data mode, and downlink / uplink for downlink / uplink. It allocates memory, splits / merges data, compresses / decompresses data and protocol headers, negotiates compression algorithms and compression parameters, and returns memory when uplink data transmission is terminated. The following is a closer look at the functions that the SNDCP task should perform.

Ability to map SN-DATA messages to LL-DATA messages.

Ability to map SN-UNIDATA messages to LL-UNIDATA messages.

Multiplexing function to properly LLC-link N-PDUs from one or several network layers.

The ability to establish, re-establish, and terminate LLC end-to-end operations in acknowledged form.

Ability to buffer N-PDUs for LLC end-to-end operation and data for retransmission.

-Ability to manage the transfer of each independent NSAPI.

-LLC end-to-end data transfer in acknowledgment using N-PDU buffering and retransmission.

Independent operation of each NSAPI.

-Compression of the TCP / IP header and data, and the function of restoring the received data by SAPI-specific PDP context (in this case, the compression method parameter is determined by negotiation).

-Ability to split and merge to the maximum size of LL-PDUs.

Ability to negotiate and determine XID parameters.

On the other hand, the flow of data through the GPRS stack is called traffic data. In the case of acknowledged mode data, it can be released only when there is an end-to-end confirm signal. That is, when data is lost due to transmission failure or data corruption, end-to-end tasks should perform retransmission of the data. To do this, each end-to-end task must store data in a buffer.

For example, the N-PDU must be buffered to compress and split at the SNDCP layer and send to the LLC layer. In this case, the SN-PDU, which is the partitioned form of the N-PDU, should be buffered until the transmission of the acknowledgment type data is completed, and the N-PDU is divided when the unacknowledged type data transmission is completed. It must be buffered until all SN-PDUs in form are sent to the LLC layer. To this end, the mobile communication terminal 12 must manage a process of allocating and returning a traffic memory for each data transmission.

A traffic memory management method in a conventional GPRS mobile communication terminal will be described with reference to FIG.

2 is a flowchart illustrating a method of managing traffic memory in a conventional GPRS mobile communication terminal, and illustrates a process of transmitting a response mode packet between an application task and an SNDCP protocol (IP) task.

First, when the real-time operating system (RTOS) receives a data transmission request signal from an application task (201), it is checked whether the value of the length field included in the packet header is less than or equal to the maximum NPDU size (202), and the length field included in the packet header If the value of P exceeds the maximum NPDU size, an error message is returned (205).

Meanwhile, if the value of the length field included in the packet header is equal to or less than the maximum NPDU size (203), the entire data is copied to the corresponding memory area (203), and the data is transmitted to the SNDCP task (204).

Similarly, in the case of signaling between tasks in the signaling base, when the highest (uplink data transmission) or the lowest (downlink data transmission) task first signals memory for data transmission and then signals to the next task, each data According to the flow, copy the data and buffer the original in the transmitted task, and copy the data in the received task and send it to the next task.

In other words, since each independent task in a real-time operating system (RTOS) cannot invade the memory of another task, the data transfer requires that memory be allocated as many as the number of tasks or active applications included in the GPRS stack. There was a problem that inefficiency occurs.

Also, considering that up to seven PDP contexts can be activated depending on the size of data that one PDU (Protocol Data Unit) can have (this depends on the type of service), the inefficiency of memory usage. Has a problem that becomes larger.

The present invention has been proposed in order to solve the above problems, and the first time (uplink data transmission) or the lowest (downlink data transmission) task in the wireless communication terminal, such that the first memory allocated for the data transmission data received After buffering, the next layer of the task to provide a traffic memory management method in a wireless communication terminal to effectively use the limited memory by passing a pointer to the memory where the data is stored.

The method of the present invention for achieving the above object is a traffic memory management method in a wireless communication terminal, the memory management task receives a data transmission request signal from another task, the value of the length field included in the packet header A data size checking step of confirming that the maximum data size is less than or equal to A memory allocation possibility confirming step of confirming that data memory allocation is possible in a size in which an offset region is further included in the value of the length field included in the packet header as the value of the length field included in the packet header is less than or equal to the maximum data size; A data memory allocation step of allocating a data memory area as the data memory can be allocated; And a memory pointer transfer step of allowing the memory management task to return a start pointer of the allocated data memory area to the other task so that the memory management task can be transferred to a task of a next layer.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

One embodiment of the present invention proposes a method for efficiently retransmitting data when a GPRS mobile communication terminal uses limited memory. That is, in one embodiment of the present invention, each GPRS stack is allocated a memory of a predetermined area for traffic data and hands over a data pointer using signaling data parameters.

The data memory for this is different from the memory allocation of the kernel interface (Kernel interface) for signaling managed by the real-time operating system (RTOS). That is, in the present invention, the data memory is not used for signaling for exchanging information between tasks, but for data flow of uplink data transfer and downlink data transfer. Memory that is allocated.

The allocation of data memory is possible for any task that desires data flow. At this time, the function for allocating data memory is as follows.

DtmuMem_Alloc (Int32 Data length, Int8 ** DtmuMem, DtmuDirection);

The first argument, "Data length", indicates the memory size required by the task invoking function in bytes. Since the memory size that can be requested by the task can be up to 32 Kbytes, use an unsigned integer (Int32: Unsigned long).

However, in the GPRS stack, the header of each layer is padded whenever data descends to the lower layer. Also, the top or bottom task cannot know how many layers the data will be sent. Therefore, this "Data length" should be determined larger than the actual size in consideration of the header size of the layers to be passed during transmission.

That is, the highest or lowest task loads data after a certain offset when sending data to the SNDCP frame. In the signaling process, a start pointer, which is the front end of an offset, is passed. This is because modifying and passing a pointer value that points to actual data every time a signal is transmitted between layers may affect processing. In addition, the offset value should be set to an appropriate value to reduce the waste of memory and to prevent overflow.

The second argument, "DtmuMem", uses a double pointer form to get the starting address of the memory to be allocated. If NULL is returned as the return address, there is no free memory in the data memory, so it cannot be allocated. Therefore, all packets to be transmitted should be discarded.

The third parameter "DtmuDirection" indicates the direction of uplink / downlink. For example, a user interface task (UI task) or a logical link control task (LLC Task) is set to Uplink, and a medium access control task (RLC-MAC Task) is set to Downlink. SNDCP tasks can be configured in both directions. The structure of the data memory will be described in more detail with reference to FIG. 3.

3 is a structural diagram of an embodiment of a data memory used in the present invention.

As shown in FIG. 3, the data memory used in the present invention includes an uplink reserved memory area, a downlink reserved memory area, and a bidirectional reserved memory area. do.

The uplink reserved memory area occupies about twice (for example, 20 Kbytes) of the downlink reserved memory area, which is divided / compressed during uplink data transmission. This is because the throughput of the task is increased compared to downlink due to compression, etc., and thus uses a lot of memory.

In contrast, the downlink reserved memory area occupies about half (eg, 10 Kbytes) of the uplink reserved area.

Each task may be allocated a memory area corresponding to each direction. If memory in either direction is allocated, a bidirectional center memory pool may be used.

At this time, "UP_RSVD_SIZE_BYTE" indicates a memory allocation space when data is transmitted in the uplink direction, and "DN_RSVD_SIZE_BYTE" indicates a memory allocation space when data is transmitted in the downlink direction. In addition, "UP_BUFF_SIZE_BYTES" and "DN_BUFF_SIZE_BYTES" indicate a limit size that can be actually allocated, and "UP_HYST_SIZE_BYTES" and "DN_HYST_SIZE_BITES" indicate thresholds that can be reassigned when a memory is returned.

In this manner, when allocating data memory, the entire memory area designated for uplink / downlink cannot be allocated. Because more data is transmitted or received than the CPU, it may require more memory than expected. To this end, memory is allocated when free memory up to "UP_BUFF_SIZE_BYTES" or "DN_BUFF_SIZE_BYTES" can be preempted.

Even if the free memory drops below "UP_BUFF_SIZE_BYTES" or "DN_BUFF_SIZE_BYTES" because all signals to be transmitted or received have been processed, the free memory must be available up to "UP_HYST_SIZE_BYTES" or "DN_HYST_SIZE_BYTES", but the data memory can be allocated again. Should be available.

On the other hand, unlike traffic data flow that can frequently require memory allocation in all tasks, static data blocks as shown in FIG. 4 when large data processing or memory allocation is not necessary. Memory (SDBM: Static Data Block Memory) is used. The only task in the GPRS stack that requires such large data memory is the SNDCP task. This is because the SNDCP task has to split and compress a large size of data received from an upper layer and transmit it to a lower layer.

That is, the SNDCP task needs about 100 Kbytes of memory for data compression and 20 Kbytes for header compression. Therefore, the total size of the static data block memory (SDBM) is set to 128 Kbytes, whereas the total size of the data memory used for traffic data flow is 32 Kbytes.

Static data block memory (SDBM), like data memory, is composed of a separate memory area from the kernel (kernel) memory for signaling.

4 is a structural diagram of an embodiment of a static data block memory (SDBM) used in the present invention.

As shown in Fig. 4, " NextFreeBlock " represents a memory pointer that can be allocated next to a memory area currently allocated. At this time, since each memory is allocated in units of blocks, the memory to be allocated next is represented by the number of blocks.

In addition, the beginning of the allocated memory block includes an allocation block group header (AllocBlockGroupHeader) including the number of allocated blocks (numberOfAllocBlocks) indicating the number of allocated memory blocks and the task ID (Task Id) requesting memory allocation. have. After the allocation block group header, there is a memory area for data processing.

Meanwhile, the memory management task according to the present invention may call any task such as an RLC / media access control task for receiving data, an application task for requesting data transmission, and an SNDCP task for performing data compression / decompression. Therefore, the memory management task according to the present invention prevents memory overflow in a way that limits the memory that can actually be allocated.

That is, if memory of "UP_BUFF_SIZE_BYTES" or "DN_BUFF_SIZE_BYTES" or more is used during memory allocation, the memory allocation impossible signal MemAboveBuffSizeInd is transmitted to the task requesting data transfer. On the contrary, when the free memory becomes less than "UP_HYST_SIZE_BYTES" or "DN_HYST_SIZE_BYTES", the memory allocation signal MemBelowHystSizeInd is transmitted to the task requesting data transfer.

Then, the task requesting data transmission waits until the memory capacity is created by setting "SendOff" so that when the memory allocation signal (MemAboveBuffSizeInd) is received, the data is no longer transmitted to the uplink / downlink. When the memory allocable signal (MemBelowHystSizeInd) is received, it is set to "SendOn" to transmit the waiting data again. Referring to Figure 5 will be described in more detail the overall operation of the present invention.

5 is a flowchart illustrating a traffic memory management method in a GPRS mobile communication terminal according to the present invention.

First, when a PDP context allocated by a request of a UI task is activated, the UI task transmits data to a GPRS network using a GPRS stack. . This is called uplink data transfer. For uplink data transfer, a UI task signals “SnUnackDataReq” to an SNDCP task to transmit unacknowledged type packet data, and acknowledges the packet data of an acknowledgment type. signal “SnAckDataReq” to transmit type packet data).

Then, the memory allocation of the data to be transmitted is made by the memory management task. At this time, the memory management task, since the first sender is a UI task, allocates memory to data NPDU, and then transfers the pointer to the UI Tast.

Table 1 below shows the structure of data included in the "SnAckDataReq" signal.

 NSAPI  Mapped NPAPI information  HeaderCompressType  How headers are compressed  DataComplressType  How data is compressed  Npdu  N-PDU to be sent to SNDCP

That is, when the memory management task receives the data transmission request signal from the application task (the task that requested the first data transmission) (501), it is checked whether the value of the length field included in the packet header is equal to or less than the maximum NPDU size (502). If the value of the length field included in the packet header exceeds the maximum NPDU size, an error message is returned (506).

On the other hand, if the value of the length field included in the packet header is equal to or less than the maximum NPDU size, the check result 502 further includes an offset region (the size of the header and tail of the next layer) to the value of the length field included in the packet header. In operation 503, it is determined whether data memory allocation is possible.

As a result of the determination (503), if the allocation is possible, after allocating the data memory area (504), the start pointer of the allocated memory area is returned to be transferred to the task of the next layer (505).

As a result of the determination 503, an error message (null value) is returned if it is not possible to be allocated, and then transmitted when memory allocation becomes possible next (506).

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

As described above, according to the present invention, after the top (uplink data transmission) or the bottom (downlink data transmission) task is first allocated a memory for data transmission and buffers the data, the next layer of tasks By passing a pointer to the memory where data is stored, the memory can effectively use limited memory and prevent waste of memory.

1 is a configuration diagram of an embodiment of a GPRS system to which the present invention is applied.

2 is a flowchart illustrating a traffic memory management method in a conventional GPRS mobile communication terminal.

3 is a structural diagram of an embodiment of a data memory used in the present invention.

4 is a structural diagram of an embodiment of a static data block memory (SDBM) used in the present invention.

5 is a flowchart illustrating a traffic memory management method in a GPRS mobile communication terminal according to the present invention.

* Explanation of symbols on the main parts of the drawing

11: Serving GPRS Support Node (SGSN)

12: mobile communication terminal

13: Gateway GPRS Support Node (GGSN)

14: home position register (HLR)

Claims (5)

In the traffic memory management method in a wireless communication terminal, A data size checking step of the memory management task receiving a data transmission request signal from another task and confirming that a value of a length field included in a packet header is equal to or less than a maximum data size; A memory allocation possibility confirming step of confirming that data memory allocation is possible in a size in which an offset region is further included in the value of the length field included in the packet header as the value of the length field included in the packet header is less than or equal to the maximum data size; A data memory allocation step of allocating a data memory area as the data memory can be allocated; And A memory pointer transfer step of allowing the memory management task to return a start pointer of the allocated data memory area to the other task to be transferred to a task of a next layer Traffic memory management method in a wireless communication terminal comprising a. The method of claim 1, The offset area is, A method for managing traffic in a wireless communication terminal, comprising adding sizes of headers and tails of subsequent layers in consideration of sizes of headers and tails of layers to be transmitted. The method according to claim 1 or 2, The data memory allocation step, As a result of the memory allocation possibility checking, if a data memory having a preset allocable threshold is used, a memory allocation impossible signal (MemAboveBuffSizeInd) is transmitted to another task requesting the data transfer, and the free data memory is greater than or equal to a preset reassignment. In this case, the memory allocation signal (MemBelowHystSizeInd) is transmitted to a task (task) requesting data transmission traffic memory management method in a wireless communication terminal. The method of claim 3, wherein The data memory, Data transfer of uplink data transfer and downlink data transfer in an area distinct from memory allocation of kernel interface for signaling managed by a real-time operating system (RTOS) Traffic memory management method in a wireless communication terminal, characterized in that the memory allocated for flow). The method of claim 4, wherein The data memory, Uplink Reserved Memory Area for Uplink Data Transmission, Downlink Reserved Memory Area for Uplink Data Transmission, and Uplink Reserved Area and Downlink Reserved Area A method of managing traffic memory in a wireless communication terminal including a bidirectional center memory pool for use when all of them are allocated.