WO2014058113A1

WO2014058113A1 - Method and device for allocating resources of m2m network

Info

Publication number: WO2014058113A1
Application number: PCT/KR2013/001239
Authority: WO
Inventors: 양정엽
Original assignee: 주식회사 케이티
Priority date: 2012-10-12
Filing date: 2013-02-18
Publication date: 2014-04-17
Also published as: KR101479950B1; KR20140047314A

Abstract

A method and device for allocating the resources of a machine to machine (M2M) network includes: determining available network resources to be allocated from a gateway to a device; calculating a priority for quality of service (QoS) management for each device; and allocating the available network resources according to the calculated priority, wherein the priority may be calculated based on a parameter related to at least one of: a QoS required for each device; an availability based on the number and call history of available applications for each device; a connection success or failure possibility based on a connection success or failure history for each device; a reachable state and reachability for each device; and an error probability based on a data transmission and processing error history for each device.

Description

Method and apparatus for allocating M2M network resources

The present invention relates to a method and apparatus for allocating network resources for M2M devices in an M2M network, and in particular, defines available network resources that can be allocated to each device in a gateway of an M2M network including one gateway and a plurality of M2M devices, A method and apparatus for allocating network resources according to device-specific priorities.

Machine-to-Machine (M2M) network refers to a network for communication between devices that does not require human interaction. However, this means that no human interaction with the device is necessary for the M2M service, but does not mean that no human interaction is required for the operation of the device.

In the past and late 1990s, M2M meant one-to-one or one-to-many communication for simple point-to-point connection. Now, M2M communication means collecting information read from sensors or wireless communication modules. It defines the communication between machines at the level of control or control and between the device and machine on which the human is operating. Ultimately, however, the goal of M2M communication is to improve location-based, context-aware, and augmented reality, and to improve M2M communication services by automatically operating without human control or minimizing human intervention. Aims at quality and stability. M2M network communication can be utilized as an essential infrastructure that can contribute to solving social issues, preventing disasters and disasters, and saving energy through conventional u-City, u-Health, u-Transportation, and u-Environmental projects. M2M services include remote meter reading, building and facility management, vending machine management, indoor lighting control service, traffic information and vehicle control, emergency dispatch, telematics, and wireless payment service.

Conventional data networks, on the other hand, typically provide all network traffic with what is known as a "best efforts" service. For example, in a TCP / IP network, a "best effort" service is the default operation in which network nodes drop packets indiscriminately when faced with excessive network congestion. However, for such "best effort" services, no mechanism exists to ensure reliable delivery of data (i.e. there is no Quality-of-Service ("QoS")).

Also, as the number of devices connected to the network increases, the demand for available bandwidth increases. Likewise, as new applications are developed for use in distributed networking environments, problems associated with the management of network resources become serious. For example, a network may experience unsatisfactory performance due to users placing too much load on the network, and these demands may come from uses that are inconsistent with the network operator's work or other goals. Thus, solutions for managing data networks using packetized protocols such as TCP / IP have been needed to meet growing demands, otherwise congestion, application unpredictability, user dissatisfaction, and loss of productivity are required. May occur.

To address these network management problems, various solutions have been used. For example, network managers often selectively add or reallocate bandwidth to mitigate congestion. Network operators may also use QoS and policy based management techniques.

In general, QoS refers to resource retention and control mechanisms that guarantee a certain level of performance for data flow in accordance with requests from application programs or Internet service provider policies. QoS disallows certain types of packets, e.g. to reduce transmission speed, to establish distinct classes of packets and / or services for users, to indicate priorities of packets and / or to establish a queue system. Can be used to

By combining one or more of these methods, QoS systems may preferentially handle certain network traffic. See, for example, US Pat. No. 7,274,700 entitled " Router providing differentiated quality of service (QoS) and fast internet protocol packet classifying method for the router " issued on September 25, 2007 by Jin et al. A router for supporting and a method of classifying a high-speed Internet protocol (IP) packet performed in the router are disclosed. The router hierarchically divides memory with flow tables into fast internal cache memory and external typical memory. The internal cache memory stores recently retrieved table items. The router first searches for flow tables in the internal cache memory. Only when the internal cache memory search fails, the flow tables of the external memory are searched. As a result, the frequency of interaction between the packet classifier and the external memory is reduced, thereby improving the speed of packet classification. The patent merely illustrates a broader class of prior art that deals with mechanisms for providing or enforcing QoS policies.

U.S. Pat.No. 6,771,661, also entitled "Apparatus and methods for providing event-based data communications device configuration," filed August 3, 2004, discloses the activity of data communication in the occurrence of specific events or times. A system and method are provided that allow a data communication device to be programmed to automatically and dynamically modify the allocation of resources without having to interrupt sessions. Resource allocation may be by means of bandwidth retention provided to the data communication device via network policy or via separate bandwidth retention messages. The bandwidth allocation information may specify the session of the data communication and future bandwidth modification information, such as time or event, which causes the data communication device to modify the amount of bandwidth held for the specified session of the data communication, Receive bandwidth allocation information indicating future bandwidth allocation modification information associated with a session of data communication. The data communication device can then determine a future event, i.e., a future event in which the data communication device will modify the amount of bandwidth allocated to the session of data communication upon the occurrence of that event. Future events may be determined based on future bandwidth allocation modification information and event information (eg, time signals from clocks or other event signals). The data communication device may detect the occurrence of a future event in the data communication device and may modify the amount of bandwidth allocated to the session of data communication in the data communication device in response to the detection of the occurrence.

However, despite the network's QoS guarantee and resource management method as described above, the network (including Wi-Fi “hotspots” in wireless LANs), in particular, by allocating available resources such as bandwidth according to user-determined specifications or inputs. There is a remarkable need for a mechanism for effectively managing and controlling the operation of the < RTI ID = 0.0 >

Easily access to their network for a variety of different operating environments and according to a number of different network parameters such as type of application, geographic proximity or location (e.g. range), type of wireless air interface, etc. And provide flexible control to the network administrator, and do not significantly disrupt router or gateway performance, for example due to latency associated with management processing. It would also be highly desirable to be able to reserve resources for certain classes of users.

However, the network resource management method according to the prior art as described above can be mainly applied to the WAN, LAN, and WCDMA, LTE, etc., which are conventional local and remote networks. There is a need for a QoS management scheme to ensure stable operation of the CDMA. This is because M2M gateway requests various kinds of quality of service from network according to application type of connected device by accommodating various kinds of devices, and there is a possibility of causing network load according to data amount or data transmission speed of the quality of service. This is because there is a problem. Therefore, there is no comprehensive QoS management method considering various situations occurring in the current M2M network.

Embodiments of the present invention have been made to solve the problems of the prior art as described above, and an object thereof is to provide a method for providing a QoS management scheme in consideration of the characteristics of the M2M network. This effectively manages the traffic of the M2M network to provide stable M2M service, ensuring the normal operation of the device, allowing users to receive the service in a timely manner.

A method of allocating resources of a machine-to-machine network according to an embodiment of the present invention for achieving the above object includes: determining available network resources to be allocated to a device from a gateway; Calculating priorities for device-by-device quality of service (QoS) management; And allocating the available network resources according to the calculated priority.

Here, the priority is: QoS required per device; Availability based on call history and number of applications available per device; Connection failure or success possibility based on device-specific connection success or failure history; Per device reachable state and reachability; And a parameter related to at least one of the possibility of error occurrence based on the device-specific data transmission and processing error history.

In addition, the M2M network resource allocation apparatus according to an embodiment of the present invention for achieving the above object, a priority calculating unit for calculating or recalculating the priority for quality of service (QoS) management for each device; And a resource allocating unit for allocating available network resources according to the calculated or recalculated priority.

According to embodiments of the present invention, when network resource allocation according to device priority is implemented in a gateway of an M2M network, QoS for each device of the M2M is guaranteed, so that most devices on the M2M network are not required for user needs regardless of network load. It solves the problem of delay caused by low priority devices, guarantees fairness of service of each device and improves the performance of overall M2M network.

For example, a security alert service can be provided immediately by allocating network resources in an emergency situation to a device that is urgently connected to an M2M network and provides a service, such as a security device such as intrusion detection. On the other hand, devices that are rarely used, such as fire alarms, that do not know exactly whether they have a failure can be detected immediately by checking the usage history and the possibility of data transmission and finding out before the accident. Finally, if a defibrillator or a cardiac pacemaker, which is a life-saving device that is directly connected to human life, needs to be operated, network resources can be immediately allocated for medical data transmission to receive information and enable first aid.

In addition, since the present invention implements or utilizes the functions of the gateway and the device proposed in the standard document (ETSI TS 102 690 M2M Functional Architecture), anyone who is a product regardless of a specific company or country as long as the standard is followed. It has the advantage that it can be applied and standardized.

1 illustrates an architect for an M2M service that includes a device and gateway domain and a network domain.

2 is a diagram illustrating a configuration of a device and a gateway domain composed of one gateway and a plurality of devices according to an exemplary embodiment of the present invention.

3A to 3C are flowcharts illustrating a method of allocating M2M network resources according to preferred embodiments of the present invention.

4 is a diagram schematically illustrating a configuration of an M2M network resource allocation apparatus according to a preferred embodiment of the present invention.

In order to explain the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, the following describes exemplary embodiments of the present invention and looks at it with reference.

First, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention, and singular forms may include plural forms unless the context clearly indicates otherwise. . Also, as used herein, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

In describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

Machine-to-Machine (M2M) communication is an object-to-machine communication that differs from the existing human-centered human-to-human communication. From these differences, technically necessary technologies may vary, and the required characteristics may vary slightly depending on the field of application using M2M communication. M2M communication is a paradigm of the new communication network in the coming future, which goes beyond the existing people-oriented communication, and presents various complex convergence services not only in the ubiquitous business but also in various industries.

Currently, standardization groups around the world, including the European Telecommunication Standard Institute (ETSI), are continuing research and development for the standardization of successful M2M communication. FIG. 1 shows the ETSI Technical Specification (TSSI) 102 690 [Machine-] in the ESTI standard document. to-Machine Communications (M2M); Fig. 4 shows the architecture for M2M services including device and gateway domains and network domains.

Referring to FIG. 1, the

M2M devices

10 and 10 ′ are terminal devices that communicate with minimal or no human input and intervention, and transmit or transmit their own data on request or automatically. It is a kind of device.

When the M2M device 10 'directly connects to the access network 40, the M2M application M12M of the M2M device 12 using the M2M service capability 11 of the M2M device 10'. In the case where the M2M device 10 connects to the access network 40 through the M2M gateway 30, the M2M gateway (M2M gateway 30) may be used using the M2M service capability 31 of the M2M gateway 30. It is prescribed to use the M2M application 32 of 30).

The M2M Area Network 20 provides a connection between the M2M device 10 and the M2M gateway 30. Examples of the M2M local area network 20 include a personal area network (hereinafter referred to as a 'PAN') or a wireless local area network such as IEEE 802.15.x, Zigbee, Bluetooth, IETF ROLL, ISA100.11a, and the like. Area Network (hereinafter referred to as 'LAN'), PLC, M-BUS, Wireless M-BSU, KNX may include a LAN.

The M2M gateway 30 is a gateway that executes the M2M application 32 using the M2M service capability 31 and serves as a proxy between the M2M device 10 and the access network 40.

The access network 40 is a network that allows the M2M device 10 'to M2M gateway 30 to communicate with the core network 50. Examples of the access network 40 include xDSL, HFC, FTTH, PLC, Satellite network, GERAN, UTRAN, eUTRAN, Wireless LAN, WiMAX (WiBro), and the like.

The core network 50 is a network that provides IP connectivity, access network control and network service control functions, interconnection with other networks, roaming functions, and the like. Examples of the core network 50 are 3GPP CN, ETSI TISPAN CN, 3GPP2 CN, IMS, and the like.

The M2M service capability 60 of the network domain provides a function that can be shared by different applications, and provides an environment for accessing other service capabilities through an open interface. By using M2M service capabilities, it is possible to develop and deploy optimal applications without considering the characteristics of lower network layers.

M2M applications 70 in the network domain use M2M service capabilities through an open interface to execute and provide M2M service logic in the M2M system.

Meanwhile, according to FIG. 1, the network domain is defined to include M2M Management Functions and Network Management Functions. Here, M2M Management Functions (80) is composed of all the functions required to manage M2M service capabilities in the network domain, the management of the M2M device to M2M gateway uses a specific M2M service capability. . In addition, the network management functions 90 are composed of all functions required to manage the access network 40 and the core network 50, and provide provisioning, supervision, and fault management. And other features.

Referring to FIG. 2, a device and a gateway domain to which a preferred embodiment of the present invention is applied include a gateway 30 connected to a network domain 100 and N (where N is an integer of 1 or more) M2M devices 10-1 and 10-. 2, 10-3, ...., 10-N). At this time, the M2M devices 10-1, 10-2, 10-3,..., 10 -N register, authenticate and authorize the device through the service capability in the gateway 30. , Management, provisioning, and the like, and the gateway 30 executes an M2M application using a service capability, for example, a function of collecting and processing various information data from a sensor included in a device. You can run an application that does this.

As shown in FIG. 1, available network resources that can be allocated to each device from a gateway of an M2M network may be defined as follows.

The amount of available network resources that can be allocated to all N M2M devices 10-1, 10-2, 10-3, ..., 10-N from the gateway 30 at a specific time t is GW (t). If the required traffic for each device is called D_T (t), the average network resource that can be allocated per device is GW (t) / N, and the minimum traffic required for one device is min (D_T (t)). .

In this case, the minimum traffic required by one device must be smaller than the average network resource allocable per device, and the sum of the minimum traffic required by all devices must be smaller than the network resource allocable to all N devices. In other words,

min (D_T (t)) <GW (t) / n, Σmin (D_T (t)) = n * min (D_T (t)) <GW (t)

Should be

In this case, the difference [Reserved_GW (t)] between the network resources allocable to the N M2M devices and the minimum traffic required by all devices may be defined as follows.

Reserved_GW (t) = GW (t)-Σmin (D_T (t))

Here, Reserved_GW (t) will be variable according to the traffic allocation situation per device per hour.

Therefore, the total amount of traffic to be allocated to a device for a specific time t is t * D_T (t), and the gateway can control the allocation of available network resources by calculating the priority of each device at the gateway.

3A is a flowchart illustrating a network resource allocation method for managing QoS of an M2M device according to an embodiment of the present invention.

First step S31 determines available network resources to be allocated for each device at the gateway. As described above with reference to FIG. 2 and the related art, this determination may be performed in consideration of available network resources allocable by the gateway and minimum traffic required for each device in a domain composed of one gateway and N M2M devices.

Subsequently, in step S32, the gateway on the M2M network calculates the priority for QoS management for each device in the network. In this case, for convenience, a function SORT (D (n)), which calculates the priority of N devices, is implemented in the gateway, the SORT function may calculate the result value by considering the following factors comprehensively:

QoS required by device

Availability based on the number of available (loaded) applications per device and actual call history

Connection failure or likelihood of success based on device-specific connection success or failure history;

-Reachable state and reachability by device

-Possibility of error based on device data transfer and processing error history.

In this case, the SORT function may determine a policy problem such as assigning a weight to each element by the gateway manager or a program.

The factor for calculating the constituent factor of the SORT function for the above-mentioned priority is the service capability of the gateway and the device (hereinafter referred to as 'SC'), for example, the above-described ETSI Technical Specification (TS) 102 690 [Machine]. -to-Machine Communications (M2M); Functional architectures as defined in [functional architecture]. According to the standard, M2M Service Capabilities provide capabilities that are exposed to reference points (i.e. interfaces), for example a combination of externally accessible interfaces such as 3GPP, 3GPP2, ETSI TISPAN, etc. Through this, you can use the capabilities of the core network and access it through one or several core networks and interfaces. The standard also includes a layer representing M2M service capabilities in a network domain, a network service capability layer (hereinafter referred to as NSCL), and a layer representing M2M service capabilities of a gateway. Layer (hereinafter referred to as GSCL) and a layer representing M2M service capabilities of an M2M device are defined as a Device Service Capability Layer (hereinafter referred to as a DSCL), collectively referred to as NSCL, GSCL and DSCL. It is defined as a service capability layer (hereinafter, referred to as 'SCL').

In addition, the M2M application refers to a device application (hereinafter referred to as "DA"), a gateway application (hereinafter referred to as "GA"), and a network application (hereinafter referred to as "NA"). For example, the DA may be located in a device in which the M2M service function is implemented or in a device in which the service capability is not implemented.

The SC of the GSCL for calculating the constituents of the SORT function for the above-described priorities may include the following SC:

Gateway Application Enablement (hereinafter referred to as 'GAE') capability providing functions such as allowing GA and DA to register with the Gateway's GSCL; Gateway Generic Communication (GGC) capability that provides a function such as reporting an error that may occur in a message transmission process; Provides functions such as managing the reachability status of the device and scheduling information regarding reachability, creating, deleting and viewing device groups, storing data of NA / DA / GA and GSCL or NSCL, and setting access rights. Gateway Reachability, Addressing and Repository (hereinafter referred to as GRAR) capability; Gateway Remote Entity Management (hereinafter referred to as GREM) capability to provide functions such as scheduling remote management tasks for sleeping M2M devices; Gateway History and Data Retention (hereinafter referred to as 'GHDR') capability that provides the ability to record messages and related information exchanged within a reference point or GSCL; Gateway Transaction Management (GTM) capability that provides the ability to collect the results of individual operations, and so on.

In addition, the SC of the DSCL for calculating the constituents of the SORT function for the above-described priority may include the following SC:

Device Application Enablement (DAE) capability providing functions such as allowing DA to register with DSCL; Device Generic Communication (DGC) capability to perform a function such as reporting an error that may occur in a message transmission process; Device Reachability, Addressing and Storage for creating, deleting, and querying device groups, storing DA properties and NSCL information, and passing device-related reachability or scheduling information to NSCL. Repository (hereinafter referred to as 'DRAR') capability; Device Remote Entity Management (hereinafter referred to as 'DREM') ability to provide a function such as triggering a connection establishment of the device itself; Device History and Data Retention (hereinafter referred to as 'DHDR') capability that provides the ability to record messages and related information exchanged within a reference point or DSCL; Device Transaction Management (DTM) ability to collect the results of individual jobs.

M2M Service Capabilities considered as constituents of the SORT function according to the preferred embodiment of the present invention utilize service capabilities that must be implemented as long as they conform to the above-described standards. Anyone can apply and standardize on any product that follows the above standard.

A detailed calculation method for each element of the priority calculation formula according to an embodiment of the present invention is as follows.

First of all, the required QoS for each device may be determined according to a predefined type of device. For example, the level of network traffic required to provide an M2M service for a corresponding device may be divided into classes such as high / medium / low compared to all devices. In addition, since the service provided through the M2M network may be a service directly related to human life such as an e-health service or a fire alarm service, in this case, the importance of a specific device may be considered separately.

For the availability based on the number of applications (mounted) available for each device and the actual call history, for example, the number of DAs available (number_of_registered_DA) compared to the number of DAs (number_of_registered_DA) stored in the device as shown in the following equation ( The probability of using the corresponding DA can be calculated by the ratio of number_of_performed_DA).

In addition, the connection failure or the likelihood of success based on the connection success or failure history for each device is, for example, the number of successful device registrations (number_of_registered_Device) as the history of the device having succeeded in configuring the gateway and the network or the number of failures, as shown in the following equation. And the number of successful connection (number_of_registered_Device).

On the other hand, for each device reachable state and reachability, for example, the current reachable state of the device is calculated by comparing the state of the Gateway Service Capability Layer (GSCL) and the state (status_of_Device) of the DSCL (Device Service Capability Layer). can do.

Next, the error occurrence probability based on the data transmission and processing error history for each device may be calculated based on the transaction processing history (number_of_successful_transaction) and the message transmission failure history (number_of_transmission_errors) of the device as shown in the following equation.

Referring back to FIG. 3A, in step S33, if device priorities are determined according to the SORT function calculated in step S32, QoS is allocated by assigning network resources by device through device bandwidth adjustment and access blocking / allowing according to device. Manage it.

The SORT (D (n)) function described above with reference to FIG. 3A may be calculated and applied in the case of an initial M2M network configuration, but when the total number of devices connected to the gateway changes or the Connection_Timer for checking the connection status of all devices expires. Whenever it may, it may also be used to reclaim the QoS priority of the device.

3B illustrates a flowchart of a method of reallocating available network resources by reassigning a priority function in order to efficiently allocate network resources when the total number of M2M devices connected to the gateway increases or decreases.

Steps S31 to S33 are the same as described above with reference to FIG. 3A, and thus detailed descriptions thereof will be omitted. In step S34, it is determined that the number of M2M devices connected to the M2M gateway is changed or evidenced, and when it is determined that the number of M2M devices is changed, in step S35, the priority function for allocating network resources is recalculated. Reallocate available network resources using the calculated priority function.

3C determines whether the connection timer Connection_Timer for checking the connection status of the M2M device has expired (step S36), regenerates a priority function each time the connection timer expires (step S37), and recalculates the priority. Reallocate available network resources according to rank function. Due to the nature of the M2M device, the information transmitted from the M2M device tends to be sent only for a short period of time, because there are few messages. Therefore, it is necessary to periodically check whether the gateway is disconnected from the device. The role of the connection timer Connection_Timer in this embodiment is to periodically check the case where the connection between the gateway and the device is abnormal and to check the idle state of each device. The time period of the connection timer Connection_timer may be arbitrarily determined according to the characteristics of the M2M service provided by the M2M service provider.

4 is a schematic structural diagram of an apparatus for allocating M2M network resources according to an embodiment of the present invention. The device may be included as part of the M2M gateway, but may be included as a separate entity from the gateway or included in the network domain to perform the network resource allocation method as described above.

Referring to FIG. 4, the M2M network resource allocation apparatus according to an embodiment of the present invention includes a priority calculator 41 and a resource allocator 42.

The priority calculating unit 41 according to the present embodiment calculates a priority for QoS management for each device when initially configuring an M2M network including one or more M2M devices and M2M gateways. In addition, the priority calculating unit 41 is a device when the total number of devices connected to the M2M gateway changes or every time a certain time elapses (for example, whenever a predetermined Connection_Timer expires to check the connection status of the devices). Reprioritize priorities for each QoS management. The priority calculation or recalculation process of the priority calculation unit 41 may be executed by, for example, using the SORT function as described above implemented in the M2M gateway.

In addition, the resource allocation unit 42 according to the present embodiment, bandwidth control for each device and time zone for the gateway according to the priority for QoS management for each device calculated or recalculated by the priority calculation unit 41. Allocates or reallocates network resources by device through blocking / allowing access.

While the foregoing description has indicated, described, and pointed out novel features of the invention as applied to various embodiments, various omissions, substitutions, and changes in the form and details of the illustrated apparatus or process may be contemplated from the invention. It will be appreciated that it may be made by one of ordinary skill in the art without departing. The above description relates to the best mode currently envisioned for carrying out the invention. This description is not intended to be limiting at all, and should be taken as illustrating the general principles of the invention. The scope of the invention should be determined with reference to the claims.

Claims

As a method of allocating resources in a machine-to-machine network,

Determining available network resources to be allocated from the gateway to the device;

Calculating priorities for device-by-device quality of service (QoS) management; And

And allocating the available network resources according to the calculated priority.
The method of claim 1,

The priorities include: required QoS per device; Availability based on call history and number of applications available per device; Connection failure or success possibility based on device-specific connection success or failure history; Per device reachable state and reachability; And calculating based on at least one parameter related to an error occurrence possibility based on device-specific data transmission and processing error history.
The method of claim 1,

Confirming a change in the number of devices connected to the gateway;

Recalculating a priority according to the number of changed devices; And

M2M network resource allocation method further comprising the step of reallocating the available network resources according to the re-prioritized priority.
The method of claim 1,

Recalculating the priority whenever a predetermined time elapses; And

M2M network resource allocation method further comprising the step of reallocating the available network resources according to the re-prioritized priority.
The method of claim 2,

The required QoS for each device is divided into layers according to the type of device, the resource allocation method of the M2M network.
The method of claim 1,

The allocation of the available network resources includes the resource allocation of the device according to the priority or the resource allocation method of the M2M network, characterized in that the time zone.
The method of claim 2,

Wherein the priority is calculated based on a function using M2M service capability implemented in the gateway and the device.
As a resource allocation device in a machine-to-machine network,

A priority calculator configured to calculate priority for device-by-device quality of service (QoS) management; And

M2M network resource allocation apparatus comprising a resource allocating unit for allocating available network resources of the gateway for each device according to the calculated priority.
The method of claim 8,

The priorities include: required QoS per device; Availability based on call history and number of applications available per device; Connection failure or success possibility based on device-specific connection success or failure history; Per device reachable state and reachability; And calculated based on a parameter related to at least one of an error occurrence possibility based on device-specific data transmission and processing error history.
The method of claim 8,

And the priority calculating unit recalculates the priority whenever the number of devices connected to the gateway changes or whenever a predetermined time elapses.
The method of claim 8,

The resource allocator allocates the available network resources through device bandwidth adjustment or time zone access blocking and allowing for the gateway.