KR101506448B1 - Method And Apparatus for Managing Machine to Machine Traffic - Google Patents

Abstract

Disclosed are a method and an apparatus for managing M2M traffic. According to the present invention, the apparatus for managing M2M traffic performs the following procedures: monitoring whether M2M traffic is in an overload state; applying a load-balancing parameter, an overload queue, or priority information step by step, if the M2M traffic is determined to be in an overload state; and processing the M2M traffic.

Description

METHOD AND APPARATUS FOR MANAGING M2M TRAFFIC [

The present embodiment relates to a method and apparatus for managing M2M traffic.

It should be noted that the following description merely provides background information related to the present embodiment and does not constitute the prior art.

Although the object intelligence communication is defined somewhat differently internationally, the terms are generally defined as M2M (Machine to Machine, ETSI), Internet of Things (ITU-T), MTC (Machine Type Communications, 3GPP) About such intelligent communications The Korea Communications Standards Commission (KCC) is a service that intelligently collects, processes, processes and transmits information through telecommunication, broadcasting, and internet infrastructures, '. The meaning of the agreement means communication between machines and between devices and machines in which people operate. In a broad sense, it means that all the infrastructure, systems, terminals, etc. that can confirm the information of objects at remote places by combining communication and ICT technology Means solution.

Mobile office, home service, health service, vehicle service, settlement, logistics management, security, etc. are attracting attention as the main application fields of the intelligent communication, and it is possible to create new business model through convergence with other industries Do. This kind of intelligent communication is a major policy for fostering new growth engines of each country together with Smart Grid, Cloud Computing and Smart Work around the world. In other words, major governments and global corporations are rushing to build aggressive investment and service development infrastructure. In particular, they are applying the intelligent communication technology and services to green IT, telematics, location-based services, remote meter reading and logistics management.

Meanwhile, some of the intelligent communication services provided in Korea include card settleters, traffic systems, remote meter reading, smart grids, and weather control systems. In addition, various services for intelligent automobiles are being developed through convergence with the automobile industry. As the convergence service based on the object intelligence communication is diversified, it is necessary to develop a platform for providing the optimal service for the M2M communication between the object (device) and the object (device). In addition, although standardization is currently being promoted through domestic and overseas standards organizations, standardization is proceeding centering on the structure and function of the object intelligence communication platform for new services rather than interworking between existing object intelligence communication platforms.

Recent trends require efficient M2M traffic management.

The present embodiment provides an M2M traffic management method and apparatus for monitoring an overload state of M2M traffic and processing M2M traffic by stepwise applying load balancing parameters, overload queues, or priority information when it is determined to be in an overload state There is a main purpose.

According to an embodiment of the present invention, an overload monitoring unit monitors an overload state for M2M traffic (Machine to Machine Traffic). A load balancer for controlling a predetermined load balancing parameter to be applied to the M2M terminal when the state of the M2M traffic is an overload state; And a processor for storing the M2M traffic in a separate overload queue and processing the M2M traffic according to predetermined priority information.

According to another aspect of the present invention, there is provided a method for a traffic management device managing M2M traffic, the method comprising: an overload monitoring process for monitoring an overload state of M2M traffic; A load balancing process of controlling a predetermined load balancing parameter to be applied to the M2M terminal when the status of the M2M traffic is overloaded as a result of the overload monitoring process; Storing the M2M traffic in a separate overload queue; And processing the M2M traffic according to the preset priority information.

As described above, according to the present embodiment, if the overload state of the M2M traffic is monitored and it is discriminated as an overload state, it is possible to effectively process the M2M traffic by applying the load balancing parameter, the overload queue or the priority information step by step .

In addition, according to the present embodiment, the performance of the internal processing of the M2M platform is not only improved but also can be applied to the main M2M service (or terminal, session) by applying differentiated priorities. Also, due to the application of priority, various premium services can be developed and applied.

1 is a block diagram schematically showing an M2M traffic management system according to the present embodiment.
FIG. 2 is a flowchart illustrating a method of setting threshold values, parameters, and priorities for managing M2M traffic according to the present embodiment.
3 is a flowchart illustrating a method for managing M2M traffic according to an embodiment of the present invention.

Hereinafter, the present embodiment will be described in detail with reference to the accompanying drawings.

1 is a block diagram schematically showing an M2M traffic management system according to the present embodiment.

M2M service is a service for exchanging information between machines or between machines and users. M2M communication is performed using specially developed terminals and servers such as communication terminals with low data transmission rates. In the field where M2M communication is applied, periodic (periodic) communication is required, but the amount of data to be transmitted is small. For example, when a safety diagnostic device is installed in each part of a bridge to check the safety of bridges and the like, each safety diagnostic device can transmit a safety diagnosis result to the application server using M2M terminals. The M2M communication can be performed in the terminal period, the terminal and the server in a promised time zone. The M2M terminal may transmit data to the application server at certain time zones.

If a plurality of M2M terminals simultaneously transmit data in a specific time zone, the load on the network through which the data is transmitted and the application server processing the data may instantaneously increase and bottlenecks may occur or proper processing may be difficult. Accordingly, the process of distributing the load due to the M2M traffic management according to the present embodiment will be described below.

The M2M traffic management system according to the present embodiment includes an M2M terminal 110, an M2M gateway 120, and an M2M traffic management device 130. [ The components of the M2M traffic management system are not limited thereto.

The M2M terminal 110 refers to all terminals or function modules for transmitting and receiving various data for M2M communication. The M2M terminal 110 includes a memory for storing a program or a protocol for communicating with the M2M gateway 120 for M2M communication, and a module for executing and controlling the corresponding program.

The M2M terminal 110 is a terminal equipped with an M2M application for M2M communication and drives an M2M application installed for M2M communication. The M2M terminal 110 includes (i) a communication device such as a communication modem for communicating with another M2M terminal, the M2M gateway 120 or various devices or networks, (ii) a memory for storing various programs and data, (Iii) a microprocessor for executing and controlling the program, and the like. According to at least one embodiment, the memory may be a computer such as a random access memory (RAM), a read only memory (ROM), a flash memory, an optical disk, a magnetic disk, or a solid state disk Readable recording / storage medium. According to at least one embodiment, a microprocessor can be programmed to selectively perform one or more of the operations and functions described in the specification. In accordance with at least one embodiment, the microprocessor may be implemented in hardware, such as an Application Specific Integrated Circuit (ASIC), in wholly or partially of a particular configuration.

The M2M terminal 110 refers to a terminal equipped with an M2M application for M2M communication, and can perform communication with another M2M terminal using a specific interface by driving an M2M application installed for M2M communication.

The M2M gateway 120 is a network point serving as an entrance for entering another network for M2M communication. The M2M gateway 120 is a group including a plurality of gateways, but in the present embodiment, the M2M gateway is referred to as an M2M gateway for convenience of explanation. A plurality of M2M terminals 110 may be connected to one M2M gateway 120, and M2M gateways 120 may be connected using a network.

The M2M traffic management device 130 has the same hardware configuration as a normal server. However, in software, it may include a program module implemented in any language such as C, C ++, Java, Visual Basic, and Visual C. The M2M traffic management device 130 may be implemented in the form of a conventional server. For example, the M2M traffic management device 130 is generally connected to an unspecified number of clients or other servers through an open computer network such as the Internet, receives requests for work performed by clients or other servers, Means computer systems and computer software installed for them.

The M2M traffic management apparatus 130 is connected to the network, and the L4 switch can be connected between the network and the M2M traffic management apparatus 130. [ In addition, the M2M traffic management device 130 can be operated as an application server in the form of an active-active cluster.

The M2M traffic management apparatus 130 according to this embodiment performs functions such as priority management, traffic distribution processing, overload monitoring, load balancing policy, and traffic parameter setting in order to avoid traffic concentration phenomenon of periodic M2M data.

Hereinafter, each function performed by the M2M traffic management device 130 will be described.

①. The M2M traffic management device 130 manages period reporting and priority.

The M2M traffic management device 130 applies the priority of the terminal unit preset to the M2M traffic. The M2M traffic management device 130 applies a predetermined service unit priority to the M2M traffic. The M2M traffic management device 130 applies the priority of the communication session set in the M2M traffic.

②. The M2M traffic management device 130 performs the load distribution processing function of the M2M traffic.

The M2M traffic management device 130 distributes the centralized M2M traffic due to the concurrent data transmission of the M2M terminal 110. [ The M2M traffic management device 130 applies an offset time, which is a load balancing parameter, to the M2M terminal 110 using the periodic report. The M2M traffic management device 130 applies a back-off time, which is a load balancing parameter, to the M2M terminal 110 when an overload occurs in the M2M traffic so that the M2M terminal 110 can detect a non- Quot;). ≪ / RTI > The M2M traffic management device 130 uses an overload queue to prepare for a message queue overflow.

③. The M2M traffic management device 130 monitors the overload state and manages the overload policy.

The M2M traffic management device 130 monitors and measures the system overload rating status. The M2M traffic management device 130 classifies and manages overload level classes. The M2M traffic management device 130 performs an action for applying load balancing parameters when a specific overload condition is reached.

④. The M2M traffic management device 130 sets the M2M traffic parameters.

The M2M traffic management device 130 sets a priority for each terminal or service. The M2M traffic management device 130 sets load balancing parameters (offset time or backoff time). The M2M traffic management device 130 sets the access priority of the communication session.

The M2M traffic management apparatus 130 monitors an overload state of the M2M traffic and controls the M2M terminal 110 to apply a predetermined load distribution parameter when the state of the M2M traffic is an overload state, M2M traffic is stored in a separate overload queue and M2M traffic is processed according to the preset priority information.

The M2M traffic management apparatus 130 includes an overload monitoring unit 132, a load distributing unit 134, and a processing unit 136. [ Hereinafter, the components of the M2M traffic management device 130 will be described.

The overload monitoring unit 132 monitors the overload state of the M2M traffic. In other words, the overload monitoring unit 132 internally grasps the number of requests to be processed per second, and applies a logic to determine an overload state when a predetermined threshold value or more is reached. In the overload state, the overload monitoring unit 132 processes all requests that have not been processed so far (reason for overloading the server) and returns them. Then, the overload monitoring unit 132 performs an operation for the predetermined load balancing with the M2M terminal 110 when the M2M traffic is overloaded.

The overload monitoring unit 132 monitors the overload state of the M2M traffic according to the present embodiment. In other words, the overload monitoring unit 132 determines that the number of processes per second of the M2M traffic reaches the predetermined threshold value or more and is in an overload state. If the overload monitoring unit 132 determines that the overloaded state is present, the overload monitoring unit 132 fails to process all unprocessed requests.

The load distributing unit 134 introduces and applies a load distribution parameter. At this time, the load distribution parameter includes an offset time and a backoff time. The 'offset time' is a parameter that causes the M2M terminal 110 to transmit data at an arbitrary time (offset time) at a time when data transmission should be performed, assuming that the data is transmitted to the server at a predetermined cycle. For example, when the offset time is set to '5 minutes', the transmission is performed such as '1: 5 minutes', '2: 5 minutes', and '3: 5 minutes' Parameter. The 'back-off time' is a parameter for allowing the M2M terminal 110 to wait for a predetermined back-off time in the overloaded state of the M2M traffic and to retransmit the data again. Due to the two parameters mentioned above, the load to be processed is distributed in the M2M platform.

The load distributing unit 134 according to the present embodiment controls the M2M terminal 110 to apply a predetermined load distribution parameter when the M2M traffic is in an overloaded state. More specifically, when the M2M traffic is in an overloaded state, the load distributing unit 134 allows the offset time, which is a load balancing parameter, to be applied to the M2M terminal 110. In other words, the load balancer 134 transmits the offset time to the M2M terminal 110 so as to allow the M2M terminal 110 to transmit the offset data to the M2M terminal 110 after the elapse of the offset time that is arbitrarily set at the time when the transmission period of the M2M terminal 110 arrives. Lt; / RTI > Also, when the M2M traffic to which the offset time is applied is in an overload state, the load balancing unit 134 applies the backoff time, which is a load balancing parameter, to the M2M terminal. In other words, the load balancer 134 transmits the backoff time to the M2M terminal 110, and when the M2M traffic to which the offset time is applied is overloaded, the M2M terminal 110 waits for a predetermined backoff time Retransmit the data again.

The processing unit 136 introduces an additional (overloaded) queue. The processing unit 136 stores the request packets in a separate overload queue in order to wait for the situation improvement for a while when the requests to be processed gradually accumulate even though the load balancing parameter is applied in the load balancing unit 134. [

Then, the processing unit 136 applies a preset priority. The priority to be applied by the processing unit 136 is information used by the M2M platform to determine what to process first when the requests to be processed arrive at the same time. At this time, the higher the priority, the higher the priority. For example, 'priority among sessions (ports)' can be set to '1 to 3', 'priority among services' can be set to '1 to 9' Can be set to '1 to 5'.

The M2M traffic management apparatus 130 may allocate a session (meaning a physical TCP port) for each service in advance. For example, only a major (Mission Critical) service is available. As a result, the priority value of the traffic generated by any one of the M2M terminals 110 can be calculated as a quantitative value such as Equation (1).

(P: priority value)

The priority value calculated as in Equation (1) may have the same value in the case of the M2M terminal belonging to different services. In this case, the length of the corresponding traffic message is referred to. In other words, the smaller the length of the traffic message, the higher the priority. This is because the total waiting time can be reduced until all competing traffic messages are processed. If the M2M terminal 110 sends a large message first, a small message has to wait for a long time, whereas if a small message is sent first, the waiting time is not large even for a large message. This is a possible solution considering the overall efficiency.

The processing unit 136 according to the present embodiment stores M2M traffic in a separate overload queue and processes M2M traffic according to predetermined priority information. More specifically, when the back-off time is applied to the M2M traffic in the overload state, the processor 136 stores the back-off time applied M2M traffic in the overload queue. In addition, the processor 136 preferentially processes traffic having a high priority among a predetermined session (port) priority, a predetermined inter-service priority, and a predetermined inter-terminal priority.

FIG. 2 is a flowchart illustrating a method of setting threshold values, parameters, and priorities for managing M2M traffic according to the present embodiment.

The user terminal accesses the M2M traffic management device 130 via the network (S210). In step S210, the terminal connected to the M2M traffic management device 130 does not necessarily have to be the M2M terminal 110, and a user terminal connectable to the network may be used.

The M2M traffic management device 130 sets a threshold for determining an overload state based on the information input from the user terminal (S220). The M2M traffic management device 130 sets an offset time and a backoff time for each M2M service based on the information input from the user terminal (S230). Herein, the 'offset time' is a parameter that allows the M2M terminal 110 to transmit data at a predetermined time (offset time) at a time when data transmission should be performed, assuming that the data is transmitted to the server at a predetermined cycle. In addition, the 'backoff time' is a parameter for allowing the M2M terminal 110 to wait for a predetermined backoff time and then retransmit the data again when the M2M traffic is overloaded.

The M2M traffic management apparatus 130 designates a priority value for each session based on the information input from the user terminal (S240). In step S240, the M2M traffic management device 130 designates a use port for each M2M service. For example, 'session (port) priority' may be set to '1 to 3'. The M2M traffic management apparatus 130 designates a priority value for each service based on the information input from the user terminal (S250). For example, the 'inter-service priority' may be set to '1 to 9'. The M2M traffic management apparatus 130 designates a priority value for each M2M terminal based on the information input from the user terminal (S260). For example, the 'inter-terminal priority' may be set to '1 to 5'. The M2M traffic management device 130 drives the M2M service platform (S270).

Although it is described in Fig. 2 that steps S210 to S270 are sequentially executed, the present invention is not limited thereto. 2 is not limited to the time-series order, as it would be applicable to changing or executing the steps described in FIG. 2 or executing one or more steps in parallel.

As described above, the M2M traffic management method according to the present embodiment described in FIG. 2 can be implemented by a program and recorded on a computer-readable recording medium. A program for implementing the M2M traffic management method according to the present embodiment is recorded, and a computer-readable recording medium includes all kinds of recording devices for storing data that can be read by a computer system.

3 is a flowchart illustrating a method for managing M2M traffic according to an embodiment of the present invention.

When M2M communication is performed between the M2M terminal 110 or when the M2M terminal 110 accesses the application server to perform the M2M communication, M2M traffic for the M2M data occurs (S310).

The M2M traffic management device 130 determines whether an overload occurs in the M2M traffic (S320). In step S320, the M2M traffic management device 130 determines the number of requests to be processed per second and determines that the M2M traffic is overloaded when the traffic reaches a predetermined threshold value or more.

If an overload occurs in the M2M traffic in step S320, the M2M traffic management device 130 applies the offset time logic, which is a load balancing parameter, to the M2M terminal 110 (S330). In step S330, the M2M terminal 110 receives the offset time from the M2M traffic management device 130 and then transmits the data after elapse of the offset time that is arbitrarily set at each time when the data transmission period arrives.

The M2M traffic management device 130 determines whether an overload occurs in the M2M traffic to which the offset time is applied (S340). In step S340, the M2M traffic management device 130 determines the number of requests to be processed per second, and can determine that the M2M traffic to which the offset time is applied reaches an overload state when reaching a preset threshold value or more.

When an overload occurs in the M2M traffic to which the offset time is applied in step S340, the M2M traffic management device 130 applies the back-off time logic of the load balancing parameter to the M2M terminal 110 (S350). In step S350, the M2M terminal 110 waits for a predetermined backoff time after receiving the backoff time from the M2M traffic management device 130, and then retransmits the data again.

The M2M traffic management device 130 determines whether an overload occurs in the M2M traffic to which the backoff time is applied (S360). In step S360, the M2M traffic management device 130 may determine the number of requests to be processed per second and may determine that the M2M traffic to which the backoff time is applied is overloaded when the M2M traffic reaches a preset threshold value or more.

If an overload occurs in the M2M traffic to which the backoff time is applied in step S360, the M2M traffic management device 130 stores the M2M traffic to which the backoff time is applied in a separate overload queue in step S370. The M2M traffic management device 130 processes the M2M2 traffic stored in the overload queue based on the preset priority value (S380). In step S380, the M2M traffic management device 130 preferentially processes traffic having a higher priority among the pre-established session (port) priority, predetermined service priority, and predetermined inter-terminal priority.

In FIG. 3, steps S310 to S380 are sequentially executed. However, the present invention is not limited thereto. 3 is not limited to the time-series order, since it would be applicable to changing or executing the steps described in FIG. 3 or performing one or more steps in parallel.

As described above, the M2M traffic management method according to the present embodiment described in FIG. 3 can be implemented by a program and recorded in a computer-readable recording medium. A program for implementing the M2M traffic management method according to the present embodiment is recorded, and a computer-readable recording medium includes all kinds of recording devices for storing data that can be read by a computer system.

The foregoing description is merely illustrative of the technical idea of the present embodiment, and various modifications and changes may be made to those skilled in the art without departing from the essential characteristics of the embodiments. Therefore, the present embodiments are to be construed as illustrative rather than restrictive, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be construed according to the following claims, and all technical ideas within the scope of equivalents thereof should be construed as being included in the scope of the present invention.

As described above, the present embodiment is applied to the field of M2M traffic management, and is a useful invention for generating an effect of distributing the load of M2M traffic when the M2M traffic is determined as an overloaded state.

110: M2M terminal 120: M2M gateway
130: M2M traffic management device 134:
134: overload monitoring unit 136:

Claims (8)

delete delete An overload monitoring unit for monitoring an overload state for M2M traffic (Machine to Machine Traffic);
A load balancer for controlling an offset time, which is a predetermined load balancing parameter, to be applied to the M2M terminal when the state of the M2M traffic is an overload state; And
A processor for storing the M2M traffic in a separate overload queue and processing the M2M traffic according to predetermined priority information,
Wherein the load balancer transmits the offset time to the M2M terminal and causes the M2M terminal to transmit data after elapse of the offset time arbitrarily set at each time when the transmission period of the M2M terminal arrives Gt; M2M < / RTI > traffic management device. An overload monitoring unit for monitoring an overload state of the M2M traffic;
A load balancer for controlling the offset time, which is a predetermined load balancing parameter, to be applied to the M2M terminal when the state of the M2M traffic is an overload state; And
A processor for storing the M2M traffic in a separate overload queue and processing the M2M traffic according to preset priority information
Wherein the overload monitoring unit monitors an overload state of the M2M traffic to which the offset time is applied, and the load distributing unit monitors the back-off time, which is the load distribution parameter, when the M2M traffic to which the offset time is applied is in an overload state, Off Time) is applied to the M2M terminal. 5. The method of claim 4,
Wherein the load-
The M2M terminal transmits the backoff time to the M2M terminal and causes the M2M terminal to retransmit the data after waiting for the predetermined backoff time when the M2M traffic to which the offset time is applied is overloaded. Traffic management device. 5. The method of claim 4,
The overload monitoring unit monitors an overload state of the M2M traffic to which the backoff time is applied,
Wherein the processor stores the M2M traffic to which the backoff time is applied in the overload queue if the M2M traffic to which the backoff time is applied is in an overload state. The method of claim 3,
Wherein,
Wherein the priority management unit preferentially processes traffic having a higher priority among a predetermined session (port) priority, a predetermined service priority, and a predetermined inter-terminal priority. A method for a traffic management device to manage M2M traffic,
Overload monitoring process to monitor overload status for M2M traffic;
A load balancing process for controlling the offset time, which is a predetermined load balancing parameter, to be applied to the M2M terminal when the status of the M2M traffic is overloaded as a result of the overload monitoring process;
Storing the M2M traffic in a separate overload queue; And
A process of processing the M2M traffic according to the preset priority information
Wherein the load balancing process includes transmitting the offset time to the M2M terminal and causing the M2M terminal to transmit data after elapse of the offset time that is arbitrarily set at a time point when the transmission period of the M2M terminal arrives A method for managing M2M traffic.

Images