KR100931730B1 - Method and device for controlling terminal application process using common daemon - Google Patents

Abstract

The present invention relates to a data service control method and apparatus using a common daemon in a mobile terminal. A method of providing a data service using a common daemon in a mobile terminal according to the present invention includes: updating port information for each application by registering or deleting port information allocated to the common daemon; An application program activation step of activating an application program to which the received packet data is processed using a port number included in the received packet data and the registered port information when receiving packet data; And a packet data transmission step of transmitting the received packet data to the activated application program. Accordingly, the present invention has a merit of providing a method for controlling a terminal application process using a common daemon capable of minimizing resource waste due to data reception in an application processor by providing a common daemon managing a port registered application process.

Port, application process, common daemon, idle, active, idle

Description

Method and device for controlling terminal application process using common daemon {Method and Apparatus for Controlling the Data Service Using Common Demon}

The present invention relates to a method and apparatus for controlling a terminal application process using a common daemon, and more particularly, to manage terminal resources more efficiently by using a common daemon that maintains port registration information for each application process. The present invention relates to a terminal application process control method using a daemon and an apparatus thereof.

With the recent development of mobile communication technology, mobile terminals currently provide various application services including web browsing as well as simple voice communication.

In addition, as a multi-tasking function used on a conventional computer is introduced to a mobile terminal, a plurality of application services can be simultaneously provided through a single CPU.

For example, a mobile terminal user may simultaneously receive a multimedia message while receiving a streaming service for a specific movie from a VOD server. That is, the mobile terminal may simultaneously run an application process for receiving a VOD service and an application process for receiving a multimedia message.

At this time, the mobile terminal is allocated a separate port for each application process corresponding to the activated application service, the packet transmitted and received through the assigned port was processed by the application process.

Accordingly, every activated application process periodically checks whether a packet is received through a port allocated to the application process, and when a plurality of application processors are activated, there is a problem in that terminal resources are wasted for packet reception confirmation.

In addition, when a plurality of application processes are activated, frequent context switching occurs to confirm whether a packet is received, which causes a problem in that CPU efficiency is lowered.

An object of the present invention for solving the problems of the prior art as described above is a terminal application process control method using a common daemon capable of more efficiently managing the terminal resources by using a common daemon for maintaining port registration information for each application process And a device thereof.

Another object of the present invention is to provide a more effective multi-application processor environment in a mobile terminal through a common daemon.

Other objects of the present invention will be readily understood through the following description of the embodiments.

According to an embodiment of the present invention, a method for providing a packet data service through a common daemon in a mobile terminal is disclosed.

A method of providing a data service using a common daemon in a mobile terminal according to the present invention includes: updating port information for each application by registering or deleting port information allocated to the common daemon; An application program activation step of activating an application program to which the received packet data is processed using a port number included in the received packet data and the registered port information when receiving packet data; And a packet data transmission step of transmitting the received packet data to the activated application program.

According to another embodiment of the present invention, a mobile terminal for providing a data service through a common daemon is disclosed.

A mobile terminal providing a data service through a common daemon according to an embodiment of the present invention includes port information updating means for registering or deleting port information allocated when an application program is running to the common daemon; Application program activating means for activating an application program to be processed by the packet data when a port number included in the received packet data exists in the registered port information; And packet data transmission means for transmitting the received packet data to the activated application program.

The present invention has an advantage of providing a method and apparatus for controlling a data service using a common daemon capable of managing terminal resources more efficiently by using a common daemon that maintains port registration information for each application process.

In addition, the present invention has the advantage of providing a more effective multi-application processor environment in the mobile terminal through a common daemon.

In addition, the present invention has the advantage of deleting unnecessary packet data by monitoring the packet data received by the invalid port number through the common daemon.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.

The term and / or includes a combination of a plurality of related items or any item of a plurality of related items. The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise.

In this application, the terms "comprising" or "mounted" and "mounted" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, one Or other features or numbers, steps, operations, components, parts or combinations thereof in any way should not be excluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Other aspects, features, and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

Hereinafter, a preferred embodiment of a method and apparatus for controlling a terminal application process using a common daemon according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a packet processing method for a plurality of application programs in a mobile terminal according to the prior art.

Referring to FIG. 1, a mobile terminal according to the related art may be divided into a terminal hardware 110, a terminal operating system 120, and an application program 130.

In particular, recently released mobile terminals are capable of simultaneously driving a plurality of applications through an operating system and a middleware platform mounted on a high performance CPU. That is, the current mobile terminal provides a multitasking function.

In general, an IP-based packet service can be identified through a port number allocated for each application service. That is, the mobile terminal receives an IP address from a packet switching network (eg, the packet switching network may be SGSN and GGSN of the UMTS system), and a port number corresponding to the service is assigned to each service request.

For example, the port number corresponding to the FTP service may be 100 and the port number for the web browsing service may be 200. At this time, the plurality of application programs driven by the user checks whether or not packets are received at their ports at predetermined intervals.

However, conventionally, there is a problem of wasting limited terminal resources because the application program always waits whether there is a packet received through its own port regardless of whether packet data is received.

That is, in the related art, all of the terminal applications that are driven maintain an active state to periodically check whether the packet is received. Accordingly, frequent context switching between applications may occur.

2 is a block diagram illustrating a mobile terminal for explaining a data service providing method using a common daemon according to an embodiment of the present invention.

As shown in FIG. 2, the mobile terminal according to an embodiment of the present invention is characterized in that a common daemon processor 230 is provided to control data flow between the terminal operating system 220 and the application program 250. .

Here, it should be noted that the mobile terminal can simultaneously drive the first to Nth application programs at the request of the user.

For example, a mobile terminal user according to the present invention can simultaneously execute services such as surfing the web, chatting, and downloading files.

In the following description, a method of processing received data using a common daemon in a mobile terminal according to the present invention will be described in detail with reference to FIG. 2.

The mobile terminal according to the present invention initializes the common daemon process 230 when power is applied. Here, the mobile terminal may generate a predetermined port registration table 240 for managing port information allocated for each application.

The terminal operating system 220 is a predetermined control signal for requesting registration or deletion of port information corresponding to the corresponding application when the specific application is started or terminated according to a user's selection, hereinafter referred to as a "port update request message". Send the box to the common daemon process 230. Here, the port update request message may include a command type for identifying whether the corresponding message is a message for registering port information or a message for deleting port information.

When the common daemon process 230 receives a port update request message for registering port information, the common daemon process 230 registers corresponding port information in the port registration table 240.

On the other hand, when the common daemon process 230 receives a port update request message for deleting port information, the common daemon process 230 deletes the corresponding port information from the port registration table 240.

The common daemon process 230 according to the present invention receives all packets received from the mobile terminal from the terminal operating system 220, and the port number included in the header of the received packet is registered in the port registration table 240. You can check whether it is a port number. As a result of the check, in the case of the registered port number, the common daemon process 230 may transmit a predetermined packet reception event message indicating that the packet for the application program corresponding to the corresponding port number has been received to the terminal operating system 220. have.

In this case, the common daemon process 230 may store the received packet in a buffer allocated in advance corresponding to the corresponding port number.

Here, the packet reception event message may include at least one of an application identifier and a port number uniquely allocated to each application program.

When the terminal operating system 220 receives the packet reception event message, the terminal operating system 220 activates an application program corresponding to the corresponding application identifier.

The activated application program reads and processes the packet stored in the receive buffer allocated to the application.

At this time, note that the remaining applications remain inactive. That is, the application programs other than the application program activated by the terminal operating system 220 does not check whether there is a packet received in its reception buffer.

The terminal operating system 220 deactivates the activated application again when the activated application completes processing of the received packet.

Accordingly, the mobile terminal according to the present invention can activate only an application program in which a packet is received at a specific time, and the common daemon process 230 periodically checks whether a packet received from the terminal operating system 220 exists. .

According to another embodiment of the present invention, when the common daemon process 230 receives a packet from the terminal operating system 220, using the port number included in the received packet to directly activate the application, Note that once the processing of the received packets is complete, the active application may be deactivated.

In addition, although FIG. 2 illustrates that a reception buffer is allocated for each application program, the mobile terminal according to another embodiment of the present invention may include a shared memory shared by a plurality of application programs, and a common daemon. The process 230 may deliver the packet received from the terminal operating system 220 to the corresponding application program through the shared memory.

Here, the size of the shared memory is preferably allocated in consideration of the received packet processing capability of the mobile terminal, including, for example, CPU performance and maximum wireless data processing speed, and the number of applications that can be run at the same time.

3 is a flowchart illustrating a received packet processing method of a common daemon process according to an embodiment of the present invention.

Referring to FIG. 3, when terminal power is applied and initialization of the terminal hardware 210 and the terminal operating system 220 is completed, the terminal operating system 220 initializes the common daemon process 230 (S302). In this case, the terminal operating system 220 may also initialize the port registration table 240.

The common daemon process 230 waits for receiving a message from the terminal operating system 220 (S304).

If the port update message is received from the terminal operating system 220, the common daemon process 230 checks whether the command type included in the port update message is port registration (S308).

Here, the port update message may further include at least one of an application identifier and a port number.

As a result of the check, if the command type is port registration, the common daemon process 230 adds port information included in the port update message to the port registration table 240 (S310).

Thereafter, the common daemon process 230 may allocate a reception buffer corresponding to the added port information (S312).

In step 308, if the check result indicates that the command type is port deletion, the common daemon process 230 displays port information corresponding to the port number or the application identifier included in the received port update message. Delete from step (S314).

Thereafter, the common daemon process 230 releases the allocated reception buffer corresponding to the corresponding port number (S316).

In the above step S304, if the message received from the terminal operating system 220 is packet data (S318), the common daemon process 230 extracts the port number from the header of the received packet data ( S320).

Thereafter, the common daemon process 230 checks whether the extracted port number is registered in the port registration table 240 (S322).

As a result of the check, if the extracted port number exists on the port registration table 240, the common daemon process 230 stores the received packet data in the reception buffer corresponding to the extracted port number (S324).

Subsequently, the common daemon process 230 generates a predetermined packet reception event indicating that the packet has been received at the corresponding port number and transmits it to the terminal operating system 220 (S326).

In this case, the terminal operating system 220 activates an application program corresponding to the received packet reception event, and the application program can read and process the stored packet data in step 324.

In step S322, if the extracted port number is not registered in the port registration table 240, the common daemon process 230 transmits a predetermined packet reception error notification signal to the terminal operating system 220. The packet data received after the transmission may be discarded (S328).

According to another embodiment of the present invention, the common daemon process 230 may discard the packet data immediately without generating a separate packet reception error notification signal for the packet data received at the unregistered port number. Be careful.

The common daemon process 230 returns to step S304 after performing any one of steps S312, S316, S326, and S328.

4 is an internal block diagram of a common daemon process according to one embodiment of the invention.

Referring to FIG. 4, the common daemon process 230 according to an embodiment of the present invention may include a message transmitter / receiver 410, a controller 420, a packet receiver event generator 430, and a port registration table updater 440. And a port number verification unit 450. In particular, the common daemon process 230 manages the port registration table 240, and when receiving packet data, the common daemon process 230 activates the corresponding application and provides the received packet data to the activated application. Can be.

In the following description, the function of each component included in the common daemon process 230 will be described in detail.

The message transmitter / receiver 410 provides a transmission interface for control signals and packet data transmitted and received between the terminal operating system 220 and the common daemon process 230.

The control unit 420 controls the update of the port registration table 240 according to a control signal received from the terminal operating system 220, for example, a port update message.

In addition, when the packet data is received from the terminal operating system 220, the controller 420 controls the lower module to verify a port number included in the received packet data and to generate a predetermined packet reception event signal according to the verification result. It performs the function. In addition, the controller 420 may transmit the generated packet reception event signal to the message transmitter / receiver 410 and store the received packet data in a corresponding reception buffer.

The packet reception event generation unit 430 generates a predetermined packet reception event signal indicating that the packet data has been received to a specific port according to a control signal of the control unit 420 and transmits the signal to the terminal operating system 220.

The port registration table updater 440 receives a port update message from the controller 420 and adds or deletes specific port information to the port registration table 240.

The port number verification unit 450 extracts a port number included in the packet data received from the terminal operating system 220 according to the control signal of the control unit 420, and the extracted port number is displayed on the port registration table 240. Performs a function to verify whether or not it is registered. If, as a result of the verification, the extracted port number is not registered in the port registration table 240, the port number verification unit 450 may generate a predetermined packet reception error notification message and transmit it to the terminal operating system 220. have.

Here, the packet reception error notification message may include a port number of an error packet data, and the terminal operating system 220 may transmit the received packet reception error notification message to a corresponding service server through an access base station.

For example, such a packet reception error may occur when the mobile terminal terminates an application program corresponding to the corresponding port number and maintains the corresponding port number in a specific server providing a service through the corresponding port number. .

Therefore, when the server receives the packet reception error notification message, the server may interrupt the transmission of packet data to the mobile terminal, thereby preventing unnecessary transmission of packet data.

According to another embodiment of the present invention, the controller 420 may store the received packet data in a reception buffer allocated corresponding to the corresponding application program when generating the packet reception event signal, and then directly activate the corresponding application program. Be careful.

5 is a data structure illustrating a structure of a port registration table according to an embodiment of the present invention.

As shown in FIG. 5, the port registration table 240 according to an embodiment of the present invention may include first to Nth application port information.

Each application port information may include an application identifier 510, a port number 520, a buffer start address 530, a buffer size 540, and a remaining buffer size 540.

The application identifier 510 is a field in which an identifier uniquely assigned to each application program is stored, and the port number 520 is a field for storing a port number allocated corresponding to the application identifier 510.

The buffer start address 530 is a field for storing the start address of the reception buffer allocated corresponding to the corresponding port number, and the buffer size 540 is a field for storing size information of the reception buffer allocated corresponding to the corresponding port number. to be. The remaining buffer size 540 is a field for recording the storage remaining memory size of the corresponding reception buffer.

When the common daemon process 230 according to the present invention receives packet data corresponding to a specific port number, the common daemon process 230 compares the size of the received packet data with the remaining buffer size 550 of the reception buffer corresponding to the corresponding port number. You can check whether there is a buffer overflow.

If a buffer overflow occurs in a specific reception buffer, the common daemon process 230 may activate the application program in which the buffer overflow occurs so that the received packet data may be processed.

Preferred embodiments of the present invention described above are disclosed for purposes of illustration, and those skilled in the art will be able to make various modifications, changes, and additions within the spirit and scope of the present invention. Additions should be considered to be within the scope of the following claims.

1 is a view for explaining a packet processing method for a plurality of application programs in a mobile terminal according to the prior art.

2 is a block diagram of a mobile terminal for explaining a data service providing method using a common daemon according to an embodiment of the present invention.

3 is a flowchart illustrating a method of processing a received packet of a common daemon process according to an embodiment of the present invention.

4 is an internal block diagram of a common daemon process according to one embodiment of the invention.

5 is a data structure showing a structure of a port registration table according to an embodiment of the present invention.

* Key Drawing

220: terminal operation system

230: common daemon process

240: port registration table

250: Application

420: control unit

430: packet receiving event generation unit

440: Port registration table update unit

450: port number verification unit

510: application identifier

520: port number

Claims (12)

In the data service providing method using a common daemon in a mobile terminal, A port information updating step of registering or deleting port information allocated for each application program in the common daemon according to a predetermined control signal; An application program activating step of activating an application program to which the received packet data is processed using a port number included in the received packet data and the registered port information; And A packet data transmission step of transmitting the received packet data to the activated application program Including but not limited to: The activated application waits for the reception of the received packet data from the common daemon, but the application programs except the activated application remain idle. And when the activated application program completes the processing of the received packet data, deactivation of the activated application program again. delete The method of claim 1, The port information is And at least one of an application identifier which is a unique identifier assigned to each application and a port number assigned to the application corresponding to the application identifier. The method of claim 3, The port information update step Receiving a predetermined port update message including the port information according to the start of a new application program or the termination of a pre-run application program in the common daemon; And Adding or deleting the port information to a predetermined port registration table according to the port update message Data service providing method using a common daemon in a mobile terminal comprising a. The method of claim 1, In the application activation step And generating a predetermined packet reception error notification message if the port number does not exist in the registered port information. In the mobile terminal providing a data service through a common daemon, Port information updating means for registering port information allocated when an application program is running to the common daemon; Application program activating means for activating an application program to which the corresponding packet data is to be processed, if a port number included in the received packet data exists in the registered port information; And Packet data delivery means for delivering the received packet data to the activated application program Including, The activated application waits for the reception of the received packet data from the common daemon, but the application programs except the activated application remain idle. And when the activated application completes the processing of the received packet data, deactivating the activated application again. The method of claim 6, The port information updating means Means for receiving a predetermined port update message including the port information according to whether a new application program is started or the application program is terminated; And Means for adding or deleting the port information to a predetermined port registration table according to the port update message. Mobile terminal providing a data service through a common daemon comprising a. The method of claim 6, And if the port number included in the received packet data does not exist in the registered port information, further comprising means for discarding the received packet data. The method of claim 6, The port information is An application identifier for identifying the application program; A port number assigned to an application corresponding to the application identifier; And Receive buffer status information allocated for each port number A mobile terminal providing a data service through a common daemon including at least one of. The method of claim 9, And the received buffer status information provides a data service through a common daemon including at least one of a buffer start address, a buffer size, and a remaining buffer size. The method of claim 6, The mobile terminal provides a data service through a common daemon that is transmitted to a corresponding application program through a reception buffer allocated for each port number. What is claimed is: 1. A recording medium readable by an electronic device on which a program comprising typed instructions for executing a data service providing method using a common daemon in a mobile terminal is recorded. A port information updating step of registering or deleting port information allocated for each application program in the common daemon according to a predetermined control signal; An application program activating step of activating an application program to which the received packet data is processed using a port number included in the received packet data and the registered port information; And A packet data transmission step of transmitting the received packet data to the activated application program Including but not limited to: The activated application waits for the reception of the received packet data from the common daemon, but the application programs except the activated application remain idle. When the activated application program completes the processing of the received packet data, the activated application program is deactivated again, which is recorded as a program for executing a data service providing method using a common daemon in a mobile terminal. Recording media.

Images