KR101698074B1 - M2m system based on mobile communication network, data transmitting method of m2m device with mobile communication network and data transmitting method of m2m device with lte network - Google Patents

Abstract

A data transmission method of an M2M device over a mobile communication network comprises the steps of: collecting, by at least one of a plurality of M2M devices having the same device ID, data; authenticating, by a mobile communication network device, the plurality of M2M devices by using the same device ID that is transferred by at least one of the plurality of M2M devices and that is shared by the plurality of M2M devices, and then allowing, by the mobile communication network device, connection of the plurality of M2M devices; and transmitting, by at least one of the plurality of M2M devices, data to the mobile communication network device. The plurality of M2M devices transmit data in a predetermined time interval spanning from the time at which data transmission is possible, and each of the plurality of M2M devices transmits data at different time points in the time interval when transmitting data.

Description

TECHNICAL FIELD [0001] The present invention relates to an M2M system based on a mobile communication network, a method for transmitting data through an M2M device, and a method for an M2M device to transmit data over an LTE network. MOBILE COMMUNICATION NETWORK AND DATA TRANSMITTING METHOD OF M2M DEVICE WITH LTE NETWORK}

The following description relates to a method and system for M2M devices to transmit data via a mobile communication network.

Machine to machine communication (hereinafter referred to as M2M communication) basically means that a machine and a machine communicate with each other via a specific network. Furthermore, the M2M communication may also include a service for communicating between a person and a device. M2M communication transmits information collected by M2M device to other devices through network. M2M communication eventually transfers data or information over any network.

M2M communication can transmit data or information through various communication networks. The mobile communication network can be a network for M2M communication in terms of ensuring a constant QoS and transmitting data over a long distance.

The M2M communication may be performed by a third generation partnership project (3GPP) technology such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or the Institute of Electrical and Electronics Engineers Lt; / RTI > or other technologies, such as those developed by < RTI ID = 0.0 >

Korean Patent Publication No. 10-2014-0006977

The mobile communication network must identify a terminal or device connected to the network with a unique identifier. That is, when a mobile communication network is used for M2M communication, a unique identifier (e.g., MSIN) should be assigned to each M2M device. However, when a large number of M2M devices are introduced, there is a fear that the mobile communication network may exhaust the identifier resources for identifying the M2M devices.

The following description is intended to provide an M2M system or an M2M communication method capable of supporting a large number of M2M devices based on a mobile communication network.

An M2M system based on a mobile communication network includes a plurality of first M2M devices; A plurality of second M2M devices; The method of claim 1, further comprising: assigning the same first identifier to the plurality of first M2M devices, assigning the same second identifier to the plurality of second M2M devices, A mobile communication network device that communicates with at least one second M2M device of the second M2M devices; And a server for receiving data collected by the at least one first M2M device or the at least one second M2M device via the mobile communication network device.

Wherein the first M2M devices connect to the mobile communication network device using the first identifier and transmit data collected by the at least one first M2M device at different times from the time of connection, The devices connect to the mobile communication network device using the second identifier and transmit data collected by the at least one second M2M device at different times from the time of connection.

A method for an M2M device to transmit data over a mobile communication network includes the steps of at least one of a plurality of M2M devices having the same device identifier collecting data, Authenticating the plurality of M2M devices with the same device identifier shared by the plurality of M2M devices communicating and allowing connection to the plurality of M2M devices, and allowing at least one of the plurality of M2M devices to transmit data To the mobile communication network device. The plurality of M2M devices transmit data in a predetermined time range from a time when data transmission is possible, and each of the plurality of M2M devices transmits data at different times in the time domain when transmitting data.

A method for an M2M device to transmit data over an LTE network includes the steps of: storing the same International Mobile Subscriber Identity (IMSI) value assigned to a plurality of M2M devices connected to the LTE network by the HSS; The MME transmitting to the HSS an identifier carried by at least one of the plurality of M2M devices; The HSS comparing the IMSI value with the identifier to perform initial authentication for the at least one M2M device; When the initial authentication is successful, the MME receives data in a predetermined time zone from the reference time point from the plurality of M2M devices, and each of the plurality of M2M devices transmits data at different times in the time domain; And the PGW comprises receiving the data.

The technique described below is an M2M system or an M2M communication method in which a plurality of M2M devices can simultaneously transmit data while simultaneously identifying a plurality of M2M devices as one identifier.

Figure 1 is an example of a block diagram illustrating a schematic configuration of an M2M system based on a mobile communication network.
2 is an example of a block diagram illustrating a configuration for an M2M system based on a mobile communication network.
3 is another example of a block diagram illustrating a configuration for an M2M system based on a mobile communication network.
4 is an example of a procedure flow diagram of a process of transmitting data by the M2M device in the M2M system of FIG.
5 is an example of a time domain in which a plurality of M2M devices sharing one terminal identifier transmits data.
FIG. 6 is another example of a procedure flow chart for a process of transmitting data by the M2M device in the M2M system of FIG.
7 is an example of a sequence in which a plurality of M2M devices transmit data in a predetermined time domain.
FIG. 8 is another example of a procedure flow chart for a process of M2M device transmitting data in the M2M system of FIG. 3. FIG.
9 is another example of a time domain in which a plurality of M2M devices sharing one terminal identifier transmits data.

The following description is intended to illustrate and describe specific embodiments in the drawings, since various changes may be made and the embodiments may have various embodiments. However, it should be understood that the following description does not limit the specific embodiments, but includes all changes, equivalents, and alternatives falling within the spirit and scope of the following description.

The terms first, second, A, B, etc., may be used to describe various components, but the components are not limited by the terms, but may be used to distinguish one component from another . For example, without departing from the scope of the following description, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

As used herein, the singular " include "should be understood to include a plurality of representations unless the context clearly dictates otherwise, and the terms" comprises & , Parts or combinations thereof, and does not preclude the presence or addition of one or more other features, integers, steps, components, components, or combinations thereof.

Before describing the drawings in detail, it is to be clarified that the division of constituent parts in this specification is merely a division by main functions of each constituent part. That is, two or more constituent parts to be described below may be combined into one constituent part, or one constituent part may be divided into two or more functions according to functions that are more subdivided. In addition, each of the constituent units described below may additionally perform some or all of the functions of other constituent units in addition to the main functions of the constituent units themselves, and that some of the main functions, And may be carried out in a dedicated manner.

Also, in performing a method or an operation method, each of the processes constituting the method may take place differently from the stated order unless clearly specified in the context. That is, each process may occur in the same order as described, may be performed substantially concurrently, or may be performed in the opposite order.

First, the terms used in the following description will be described. In terms of object communication, terms such as M2M and IoT are mixed in academia and industry. Hereinafter, M2M refers to a communication or communication service that is connected to a network such as the Internet and utilizes data collected by a specific object.

Hereinafter, an M2M device refers to a device that is connected to a network and collects certain data. The M2M device is a sensor device that collects a small amount of data such as a temperature sensor, a device that collects image data such as CCTV, a device that collects location information such as a GPS device installed in a vehicle, Wearable device) device for collecting acceleration or position information, smart phone, and the like. As a result, an M2M device refers to a device that is connected to a network and transmits collected data or input data to the network.

As described above, the M2M communication described below is based on a mobile communication network. The mobile communication system includes a third generation partnership project (3GPP) technology and / or an IEEE (Institute of Electrical and Electronics Engineers) such as GSM (Global System for Mobile Communication), UMTS (Universal Mobile Telecommunications System) And the like. Accordingly, the mobile communication network can use various communication methods. However, for the sake of convenience of explanation, it will be explained based on the LTE network.

Hereinafter, an M2M system based on a mobile communication network and a method for transmitting data through a mobile communication network will be described in detail with reference to the drawings. Hereinafter, the same terms mean basically the same configuration. Further, the configuration of the mobile communication network corresponds to the configuration defined in the standard.

1 is an example of a block diagram illustrating a schematic configuration for an M2M system 100 based on a mobile communication network.

The M2M device 111 is a device for collecting certain data as described above. In addition, the M2M device 111 carries out a function of transmitting the collected information to the base station (eNodeB) 130, which is an access point (AP) of the mobile communication network, in addition to a certain data collecting function. 1 illustrates three M2M devices 111 connected to an M2M gateway 120 and three M2M devices 112 connected to a base station 130. In FIG. The M2M gateway 120 receives the data collected by the M device 111. The M2M gateway 120 transmits the received data to the mobile communication network. The M2M gateway 120 is connected to a base station (eNodeB) 130, which is an access point (AP) of the mobile communication network. As shown in FIG. 1, the M2M gateway 120 and the base station 130 may form an Evolved Universal Terrestrial Access Network (E-UTRAN). Also, as shown in FIG. 1, the M2M device 112 may be connected to the base station 130 without forming the M2M gateway 120 to form an E-TURAN. The base station 130 is connected to a mobile communication core network (EPC: Evolved Packet Core). The configuration of the EPC included in the EPC will be described later.

Figure 1 shows a server 190 connected to an EPC. The server 190 is a device that finally receives the data collected by the M2M devices 111 and 112. The server 190 corresponds to a device for providing a certain information service based on data collected by the M2M devices 111 and 112. For example, if the M2M devices 111 and 112 collect and transmit climate information such as temperature and humidity, the server 190 may provide a service that guides the current weather by region based on the acquired information. Although not shown in FIG. 1, the EPC and the server 190 are generally connected through an Internet network. Hereinafter, the mobile communication network apparatus is used to mean a base station and an EPC.

2 is an example of a block diagram illustrating a configuration for an M2M system 100 based on a mobile communication network. Fig. 2 is an example of a block diagram showing the configuration shown in Fig. 1 in more detail. FIG. 2 does not show all the configurations that can be included in the EPC, but shows only the configuration necessary for the explanation.

The M2M device 111 is a device for collecting certain data. In FIG. 2, the M2M devices 111 of k (D # 1 to D # k) are shown as an example. In FIG. 2, the M2M gateway 120 is not shown for convenience of explanation. 2, the M2M device 113 includes an M2M device 112 directly connected to the base station 130 in FIG. 1 and an M2M device 111 connected to the base station 130 through the M2M gateway 120 .

The base station 130 transmits information related to the control among the data collected by the M2M device 113 to the MME 140 and packet data to be transmitted to the server 190 through the Serving GateWay 160 .

The MME 140 takes charge of signal control between the M2M device 113 and the core network. For example, the MME 140 is involved in authenticating the M2M device 113 using certain information when the M2M device 113 requests connection to the network. An HSS (Home Subscriber Server) 150 stores and manages information related to subscription to a mobile communication service. For example, when a user subscribes to a mobile communication service, identifiers and the like for the user (terminal) are stored and managed. The HSS 150 can process the authentication of the M2M device 113 using the managed information.

On the other hand, the MME 140 also controls the process of accessing the mobile communication by the M2M device 113 corresponding to the terminal. Although not shown in FIG. 2, a plurality of base stations 130 exist. The MME 140 controls which base station wakes up the specific M2M device 113 when the M2M device 113 is opposite to the base station. For example, the MME 140 generates a Tracking Area Identifier (TAI) list and transfers the information to the M2M device 113 to manage which base station the specific M2M device 113 should connect to.

The SGW 160 basically serves as an anchor for the movement of the terminal. The SGW 160 may also participate in packet data transmission. The Packet Data Network GateWay (PGW) 170 transmits the packet data to the Internet network through the EPC. Data collected by the M2M device 113 in the EPC is transmitted to the Internet network (network service provider) via the base station 130, the SGW 160 and the PGW 170 in general.

The technique described below is important as to how the mobile communication network identifies the M2M device 113 and allows the connection. First, the process of connecting the M2M device 113 to the mobile communication network will be described. A box indicated by a dotted line beside the configuration shown by the solid line in Fig. 2 represents information managed and maintained by the configuration.

When the M2M device 113 subscribes to the first mobile communication network service, the M2M device 113 transmits the Mobile Subscription Identification Number (MSIN) held by the M2M device 113 to the mobile communication network and requests authentication. The MSIN is an identifier used by the mobile communication carrier to identify the user's terminal (M2M device). In fact, the M2M device 113 delivers the International Mobile Subscriber Identity (IMSI) to the mobile communication network. The IMSI is a combination of PLMN ID and MSIN. PLMN (Public Land Mobile Network) is a combination of MCC and MNC. The MCC (Mobile Country Code) is a unique code for identifying a country, and the MNC (Mobile Network Code) is a unique code for identifying a network (network operator). As a result, the IMSI has a different value for each terminal receiving the mobile communication service around the world.

The M2M device 113 transfers its IMSI value to the mobile communication network at the first connection of the mobile communication network. In FIG. 2, information mainly exchanged between D # 1 and M2M device 113 is shown. The IMSI value of D # 1 is assumed to be IMSI # 1. D # 1 transmits the IMSI # 1 to the MME 140 through the base station 130 when the mobile communication network is first accessed. Meanwhile, the M2M device 113 stores its IMSI value in a storage medium such as a USIM.

 The MME 140 forwards the IMSI # 1 included in the connection request of the D # 1 to the HSS 150. The HSS 150 stores the IMSI values for all the M2M devices 113 that have previously subscribed to the mobile communication service. The HSS 150 compares the received IMSI # 1 with its own IMSI to determine whether the IMSI # 1 exists. Whereby the HSS 150 can authenticate D # 1.

Hereinafter, it is assumed that the authentication is successful. The MME 140 transmits a message indicating that the authentication is successful to the D # 1, and the D # 1 can then forward the packet data to the mobile communication network.

The IMSI value is a value that does not change to a value that identifies the M2M device 113. Mobile communication networks generally use IMSI only on the initial connection. To increase security, the MME 140 may assign another identifier to the M2M device 113 after the initial connection. The MME 140 provides a Globally Unique Temporary Identifier (GUTI) to the M2M device 113, and the M2M device 113 transmits a GUTI when reconnecting. The mobile communication network then authenticates the M2M device 113 based on the GUTI. Whether to use the IMSI or the GUTI as the ID of the M2M device 113 when reconnecting depends on the TIN (Temporary Identifier used in Next update) value of the M2M device 113.

Although FIG. 2 shows one MME 140, a plurality of MMEs are actually used for the EPC. Therefore, the MME 140 also has an ID for identifying the MME. The MME ID is composed of an MMEGI (MME Group Identifier) indicating an MME group and an MMEC (MME CodE) indicating a specific MME in the MME group. The Globally Unique MME Identifier (GUMMEI) is the information that the PLMN ID is combined with MMEGI. In other words, GUMMEI can identify one MME globally. In addition, the MME 140 allocates MME Temporary Mobile Subscriber Identity (M-TMSI), which is a unique value in the MME 140, to the subscriber (M2M device) registered with the MME 140. GUTI is a value composed of GUMMEI and M-TMSI. Therefore, the GUTI is also unique worldwide. However, unlike the fixed IMSI, the GUTI is a temporary value allocated from the MME every time the M2M device 140 registers in the network.

In FIG. 2, the MME 140 assigns a GUTI value of GUTI # 1 to D # 1. Then, when D # 1 reconnects to the mobile communication network, GUTI # 1 is transmitted to MME 140, and MME 140 authenticates D # 1 based on GUTI # 1.

Meanwhile, the MME 140 may provide the M2M device 113 with SA-Temporary Mobile Subscriber Identity (S-TMSI). In FIG. 2, the MME 140 indicates that the value of S-TMSI # 1 is assigned to D # 1. The S-TMSI is a value for identifying a specific M2M device 113 in one MME group including a plurality of MMEs. S-TMSI consists of MMEC and M-TMSI only. For example, if the mobile communication network does not use the MME group, the M2M device 113 may be identified using the S-TMSI instead of the GUTI. In FIG. 2, when D # 1 transfers S-TMSI # 1 to MME 140, MME 140 compares S-TMSI value held by itself and S-TMSI # 1 to perform authentication.

The HSS 150 manages the GUTI and S-TMSI, and the HSS may use this value to authenticate the M2M device 113.

As described above, when the M2M device 113 exponentially grows, the IMSI, GUTI, or S-TMSI has a limited number of digits, which may result in insufficient identifier resources. An alternative to this is the M2M system 100 of FIG.

3 is another example of a block diagram illustrating a configuration for an M2M system 100 based on a mobile communication network. 3 is different from the M2M system 100 of FIG. 2 in that a plurality of M2M devices form a group, and one group shares an identifier for a mobile communication network connection.

3 shows an example of two M2M groups, Group X (Group X, 110A) and Group Y (Group Y, 110B). An M2M group refers to a group that includes a plurality of M2M devices. In FIG. 3, group X 110A shows k M2M devices 113 from D # 1 to D # k. Although not shown in FIG. 3, the group Y (110B) also includes a plurality of M2M devices (113).

In FIG. 3, IMSI, GUTI, and S-TMSI are used as identifiers that the mobile communication network uses to authenticate the M2M device 113. However, unlike FIG. 2, the MME 140 in FIG. 3 assigns an IMSI having the same value to each M2M group. That is, the M2M devices 113 belonging to one M2M group all have the same IMSI value.

When at least one terminal belonging to the group X 110A requests a connection, the MME 140 to the HSS 150 give the same IMSI to the group X 110A. In FIG. 3, the M2M devices (D # 1 to D # k) belonging to the group X 110A all have the same IMSI # 1 value. The mobile communication network does not individually identify and authenticate the M2M device 113 when the first M2M device (D # 1 to D # k) makes a connection request (authentication request), and transmits the M2M device 113 Identify and authenticate the group. 2, unlike FIG. 2, the mobile communication network authenticates an M2M group including a plurality of M2M devices 113 without authenticating one M2M device 113 using IMSI.

If the M2M group authentication is successful, the M2M device 113 belonging to the corresponding M2M group can transmit the data packet to the mobile communication network. As will be described later, the M2M device 113 belonging to the same M2M group is different from the M2M devices belonging to the same M2M group in order to distinguish data transmitted from the plurality of M2M devices 113 (i.e., to distinguish the M2M devices) Transmit data in time.

The MME 140 may then grant the GUTI or S-TMSI to the M2M device 113. [ As described above, the M2M device 113 is used when reconnecting the GUTI or the S-TMSI to the mobile communication network. The MME 140 may assign a GUTI or S-TMSI having a different value to each of the M2M devices 113. [ A plurality of M2M devices 113 belonging to the same M2M group each have a unique GUTI or S-TMSI. Also in FIG. 3, M2M devices belonging to the same M2M group have different values of GUTI or S-TMSI. For example, D # 1, which is an M2M device belonging to Group X 110A in FIG. 3, has a value of GUTI # X1 and / or S-TMSI # X1. In FIG. 3, the other M2M devices D # k belonging to Group X 110A have values of UTI # Xk and / or S-TMSI # Xk.

The M2M device 113 having the unique identifier is not limited to the time for transmitting the data when reconnecting (the M2M terminal belonging to the same M2M group has a time area for data transmission at the time of initial connection) It is possible to access the mobile communication network and transmit data using the S-TMSI. For example, D # 1, which is an M2M device belonging to Group X 110A in FIG. 3, transmits GUTI # X1 or S-TMSI # X1 assigned to itself to MME 140. The MME 140 performs authentication for D # 1 based on GUTI # X1 or S-TMSI # X1. If the authentication is successful, D # 1 transmits the data packet to the MME 140. D # k belonging to the Group X 110A at the same time also transmits the GUTI # Xk or the S-TMSI # Xk given to the MME 140 to the MME 140 for authentication, and D # k transmits the data packet To the MME 140. In summary, upon reconnection, the M2M device 113 can connect and transmit data using a GUTI or S-TMSI like a general terminal (M2M device) connected to a mobile communication network. When the M2M device 113 receives the GUTI or the S-TMSI, it can freely access the mobile communication network and transmit data regardless of whether the specific M2M group belongs or not.

Meanwhile, various criteria may be used as criteria for classifying the M2M devices 113 into one group. For example, the M2M devices located in a specific area can be classified into the same group. Or an M2M device of the same kind (for example, a temperature sensor device) may be classified into the same group. Alternatively, the group may be classified based on the smoothness of communication of the M2M device. Alternatively, an arbitrary M2M device may be classified into the same group according to the setting of the manager.

FIG. 4 is an example of a procedure flow diagram for a process 200 of transmitting data by the M2M device in the M2M system of FIG. FIG. 4 shows an example of authenticating an M2M group using an IMSI and authenticating an M2M device using a GUTI.

The HSS 150 stores (201) the IMSI value for each M2M group, and the M2M group (110) stores an IMSI of the same value (202). In FIG. 3, all M2M devices belonging to the M2M group X 110A store a value of IMSI # X, and the HSS 150 stores IMSI #X for the M2M group X 110A. The HSS 150 stores IMSIs for each group for a plurality of M2M groups.

At least one M2M device 113 belonging to the M2M group 110 collects data (211). At least one M2M device 113 belonging to the M2M group 110 transmits a connection request to the MME 140 through the base station 130 (221). For example, the M2M device D # 1 belonging to the M2M group X 110A transmits a connection request with the IMSI # X. On the other hand, the M2M device that has collected data at 211 and the M2M device that requests connection at 221 may be the same device or may be different devices. For example, an M2M device serving as a control such as a connection request in one M2M group may be set in advance.

The MME 140 delivers the received IMSI to the HSS 150, and the HSS 150 compares the received IMSI with its own IMSI value to perform authentication. It is assumed that the authentication is successful. The MME 140 may generate a unique GUTI value for each M2M device belonging to the M2M group X 110A and store it (231). Meanwhile, the MME 140 may transmit the generated GUTI value to the HSS 150. The MME 140 transmits the generated GUTI value to each M2M device belonging to the M2M group X 110A (232). All M2M devices 113 belonging to the M2M group 110 store the received GUTI value (233). For example, the M2M device D # 1 stores a GUTI value of GUTI # X1.

At least one M2M device belonging to the M2M group 110 transmits the collected data to the base station 130 in step 231. The base station 130 transmits the data packet to the SGW 160 in step 232 and the SGW 160 Transmits the data packet to PGW 170 (233). Although not shown in FIG. 4, the PGW 170 delivers a data packet to the server 190. For example, each M2M device belonging to the M2M group X 110A can transmit data to the PGW 170. As described above, each of the M2M devices belonging to the M2M group X 110A must transmit data in different time zones. A time zone in which each M2M device belonging to the M2M group X 110A transmits data must be set in advance.

4 shows an example in which the M2M device belonging to the M2M group X 110A performs the initial connection to the IMSI and the M2M devices belonging to the M2M group X 110A transmit data with different time (231 to 233). However, the process of generating and transmitting the GUTI for each M2M device by the MME 140 may be performed after 231 to 233.

Then, one M2M device D # 1 belonging to the M2M group 110 newly collects data (241). D # 1 requests the MME 140 to reconnect with the GUTI value (GUTI # X1) to transmit the collected data to the mobile communication network (step 251). The MME 140 compares the received GUTI value with its own GUTI based on the received GUTI value (step 252). Or the HSS 150 may perform the authentication in comparison with the GUTI held by the HSS 150 itself.

If the authentication is successful, D # 1 transfers the collected data to the base station 130 (261), and the base station 130 transfers the data packet to the SGW 160 (262) To the PGW 170 (263). D # 1 can forward the collected data to the mobile communication network when the reconnection request is accepted. The time for transmitting data is not limited as when D # 1 is initially connected to the mobile communication network using IMSI.

Then, D # k, another M2M device belonging to the M2M group 110, newly collects the data (271). D # k requests the MME 140 to reconnect with the GUTI value (GUTI # Xk) (281) in order to transfer the collected data to the mobile communication network. The MME 140 compares the received GUTI value with its own GUTI based on the received GUTI value (step 282). Or the HSS 150 may perform the authentication in comparison with the GUTI held by the HSS 150 itself. D # k transfers the collected data to the base station 130 (291), and the base station 130 transmits the data packet to the SGW 160 (292). The SGW 160 transmits the data packet To the PGW 170 (293).

D # 1 and D # k may transmit their collected data at the same or a duplicated time when the reconnection request is accepted.

As described above, the mobile communication network assigns an identifier to the M2M group 110 including a plurality of M2M devices. For example, an M2M device belonging to an M2M group has the same IMSI value. That is, the mobile communication network can identify the M2M group 110 at the initial connection with the M2M device. However, when one of the M2M devices belonging to the M2M group 110 transmits data, I do not know.

Therefore, the M2M devices belonging to the same M2M group transmit data packets at different time zones when the first access using the IMSI value is performed. That is, similar to the time divisional communication method, the M2M device transmits data at different times. The time at which M2M devices belonging to the same M2M group communicate data must be predetermined. Hereinafter, a process in which the M2M device belonging to the same M2M group transfers data packets in the initial connection using the IMSI in FIGS. 5 to 9 will be described.

5 is an example of a time domain in which a plurality of M2M devices sharing one terminal identifier transmits data. FIG. 5A shows an example of a time zone in which an M2M device belonging to a group X (Group X) transmits a data packet. FIG. 5B shows an example of a time when a M2M device belonging to a group Y (Group Y) This is an example of a region.

Referring to FIG. 5A, the group X, which is an M2M group, includes five M2M devices (D # 1 to D # 5). The M2M devices belonging to the group X can transmit data packets in the order of D # 1, D # 2, D # 3, D # 4 and D # 5 in the order of time. The area shown in FIG. 5 shows a time area in which each M2M device can allocate a data packet. If D # 2 does not have a data packet to be transmitted at that time, the data packet may not be transmitted in the time domain.

Referring to FIG. 5B, the group Y, which is an M2M group, includes five M2M devices (D # 1 to D # 5). In FIG. 5B, the data packet transmission order is D # 3, D # 1, D # 4, D # 5 and D # 2. In FIG. 5, for convenience of description, the identifier "D # number" is displayed in each time zone. However, the identifier of the M2M device is basically not transmitted by the M2M device in the actual data packet transmission process. Therefore, it is necessary for some M2M devices to share information in advance with other devices in order to transmit data packets (in what time zone). Here, the other apparatus may be a configuration included in the mobile communication network or a server providing M2M service.

FIG. 6 is another example of a procedure flow chart for the process 300 of the M2M device transmitting data in the M2M system of FIG. 6, processes corresponding to different embodiments are shown. In FIG. 6, the processes classified into A and B correspond to different embodiments.

First, an example indicated by A will be described. The M2M devices first set up the M2M group (301). Thereafter, the MME 140 of the mobile communication network transmits a data packet delivery order to the M2M devices belonging to the same M2M group 110 (302). For this, the MME 140 must know information about the M2M group formed by the M2M devices in advance. For example, you need to know which M2M device is the same M2M group. Further, the MME 140 must know the criteria for determining the data packet delivery order for M2M devices belonging to the same M2M group. For example, the mobile communication network basically knows the location information of the M2M device. Thus, the order of data packet delivery may be determined based on the location of the M2M device. Furthermore, the order of data packet delivery may be determined according to the order set by the administrator without any specific criteria. In this process, additional identifiers may be used to identify M2M devices belonging to the same M2M group. Where the additional identifier may be local rather than global, or may be to identify the M2M device only within a single carrier. In addition, a control configuration other than the MME 140 in the configuration of the mobile communication network may determine a data packet delivery order for the M2M device.

Further, the server 190 providing the M2M service may determine the order (time domain) in which the M2M devices belonging to the same M2M group transmit data packets. In this case, as shown in FIG. 6, the server 190 may transmit the data transfer order to each M2M device in the M2M group 110 (303). In this case, an additional identifier may be used to identify a specific M2M device by the M2M service provider. That is, although the mobile communication network can not be distinguished, the M2M service provider can assign an identifiable identifier to each M2M device, and set a data packet order for the corresponding M2M device.

Thereafter, at least one M2M device belonging to the M2M group 110 collects data (304). Assuming that the authentication process is successful, the MME 140 forwards the post-authentication data start message to the MME group 110 (305).

At least one M2M device belonging to the M2M group 110 transmits the data packet at the time of receiving the data start message or at a specific time included in the data start message (306). The data packet is transmitted to the server 190 via the PGW 170.

Now, an example indicated by B will be described. B is an example in which M2M devices belonging to the M2M group 110 determine the data packet order by themselves. The M2M devices first set up the M2M group (311). For example, it is assumed that M2M devices can exchange information with each other by using D2D (Device to Device) communication or group communication technique. (312) a data packet forwarding order between terminals belonging to the M2M group (110), which is a constant reference or randomly. At least one M2M device (or each M2M device) belonging to the M2M group 110 transmits the packet data transfer order to the server 190. [ Although not shown in FIG. 6, when the M2M device transmits the packet data transmission order to the mobile communication network configuration such as the MME 140, the mobile communication network configuration will have to inform the server 190 of the packet data transmission order at a later time. At least one M2M device belonging to the M2M group 110 collects data (314). If authentication is successful between the M2M group 110 and the MME 140, the MME 140 forwards the data start message to the MME group 110 (315).

At least one M2M device belonging to the M2M group 110 transmits the data packet at the time of receiving the data start message or at a specific time included in the data start message (316). The data packet is transmitted to the server 190 via the PGW 170.

7 is an example of a sequence in which a plurality of M2M devices transmit data in a predetermined time domain. 7 is an example of a criterion for determining the order in which M2M devices belonging to the same M2M group transmit data packets to the mobile communication network. 7 assumes that the subject determining the data packet delivery order of the M2M device knows location information of the M2M device in advance.

FIG. 7A shows an example in which the order is determined according to whether or not the M2M device is located in a specific area. In Fig. 7 (a), the M2M device shows a temperature sensor as an example. In Fig. 7 (a), the dotted circle means a specific region (or position). There may be a priority in which a data packet is delivered according to a specific location in advance. In FIG. 7 (a), the number displayed in each area corresponds to a priority for transmitting a data packet. 7A shows an example in which there is no M2M device in the area corresponding to the second priority.

7B is an example of determining the data packet delivery order based on the distance between the M2M device and the AP serving as an AP. In Fig. 7 (b), the M2M device shows CCTV as an example. FIG. 7 (b) shows an example in which the order of data packet delivery is determined according to the order of closest distance between the base station and the M2M device.

Furthermore, various criteria not shown in FIG. 7 may be used. Of course, without special criteria, an administrator or service provider could manually configure a particular M2M device to determine the data packet in a particular order.

FIG. 8 is another example of a procedure flow diagram for a process 400 in which the M2M device transmits data in the M2M system of FIG. 7 shows processes corresponding to different embodiments. In FIG. 8, the processes classified into A and B correspond to different embodiments. Basically, unlike FIG. 6, FIG. 8 basically transmits data packets at random by M2M devices belonging to the same M2M group 110 without predetermined order.

An example represented by A will be described first. The M2M devices first establish the M2M group (401). At least one M2M device belonging to the M2M group 110 collects data (402). If the authentication is successful between the M2M group 110 and the MME 140, the MME 140 forwards the data start message to the MME group 110 (403). The M2M device having the data transmitted from among the M2M devices belonging to the M2M group 110 can transmit the data packet according to the order of generating the data (404). For example, an M2M device that first collected data among M2M devices first transmits data packets. To do this, we need a method that can distinguish the time of generation of collected data. For example, the M2M group 110 may store data in queues used in common and then transmit data packets in order. Furthermore, if M2M devices are able to communicate with each other, they may share data collection time and deliver data packets according to the order of collection.

B will be described. The M2M devices first set up the M2M group (411). At least one M2M device belonging to the M2M group 110 collects data (412). If authentication is successful between the M2M group 110 and the MME 140, the MME 140 forwards the data start message to the MME group 110 (413). The M2M devices in the M2M group 110 may then transmit data packets in a random order (414).

The example described in FIG. 8A has a certain order, but the order is not known to the server 190. Therefore, the example illustrated in FIG. 8A can also be included in the case where the M2M device randomly transmits data packets. When a plurality of M2M devices randomly transmit their own data packets, basically, there must be an additional identifier in the data packet that identifies each M2M device. Preferably, the additional identifier is previously known by the service provider or server 190 providing the M2M service regardless of the mobile communication network.

When an M2M device sends a packet at random, it can send a data packet at the same time. That is, data packets may collide. A way to avoid this would be needed. 9 is another example of a time domain in which a plurality of M2M devices sharing one terminal identifier transmits data. 9 shows an inactive period in a time domain in which M2M devices transmit data. The inactivity period corresponds to a time domain in which a configuration of the mobile communication network or the server 190 ignores the packet because it receives the data packet. Various methods can be used. Basically, the M2M device can repeatedly transmit the data packet at a predetermined time interval until the server 190 receives the ACK message that the server 190 has received the data packet. Also, an avoidance strategy used in a competition-based communication method such as a wireless LAN (IEEE 802.11) may be used. For example, each M2M device may transmit data packets at random intervals. In addition, various techniques may be used to prevent impulsiveness and finally to transmit data packets securely.

It should be noted that the present embodiment and the drawings attached hereto are only a part of the technical idea included in the above-described technology, and those skilled in the art will readily understand the technical ideas included in the above- It is to be understood that both variations and specific embodiments which can be deduced are included in the scope of the above-mentioned technical scope.

111: M2M device
112: M2M device
113: M2M device
110: M2M Group
110A, 110B: M2M group
120: M2M gateway
130: Base station
140: MME
150: HSS
160: SGW
170: PGW
190: Server

Claims (21)

A plurality of first M2M devices;
A plurality of second M2M devices;
The method of claim 1, further comprising: assigning the same first identifier to the plurality of first M2M devices, assigning the same second identifier to the plurality of second M2M devices, A mobile communication network device that communicates with at least one second M2M device of the second M2M devices; And
And a server for receiving data collected by the at least one first M2M device or the at least one second M2M device via the mobile communication network device,
Wherein the first M2M devices connect to the mobile communication network device using the first identifier and transmit data collected by the at least one first M2M device at different times from the time of connection, The devices connect to the mobile communication network device using the second identifier and deliver data collected by the at least one second M2M device at different times from the time of connection. The method according to claim 1,
Wherein the first identifier is at least one of an identifier belonging to a group including a Mobile Subscriber Identification Number (MSIN) and an International Mobile Subscriber Identity (IMSI), and the second identifier is at least one of identifiers belonging to a group including an MSIN and an IMSI M2M system based on mobile communication network. The method according to claim 1,
The mobile communication network device
A base station to which the first M2M devices or the second M2M devices are connected;
A subscriber information server storing the first identifier and the second identifier;
A device management apparatus managing the connection of the first M2M devices using the first identifier and managing connection of the first M2M devices using the second identifier; And
And a gateway device for communicating data transmitted by the at least one first M2M device or the at least one second M2M device to the server. The method according to claim 1,
The plurality of first M2M devices are different from each other based on at least one of a reference group including a sequence in which each device collects data, a predetermined order, a position of the device, and a distance between the device and the AP of the mobile communication network device M2M system based on mobile communication network that transmits data in time. The method according to claim 1,
The mobile communication network device stores in advance the time at which the at least one first M2M device of the first M2M devices transmits data and transmits the data to the at least one first M2M device The mobile communication network based M2M system. The method according to claim 1,
Wherein the server stores in advance a time at which the at least one first M2M device transmits data, and transmits the at least one first M2M device to a mobile communication Network based M2M system. The method according to claim 1,
The mobile communication network device authenticates the first M2M devices based on the first identifier and if the authentication is successful, assigns a unique identifier unique to each of the plurality of first M2M devices in the mobile communication network device M2M system based on mobile communication network. 8. The method of claim 7,
The mobile communication network device
Wherein the at least one M2M device authenticates the at least one M2M device using the unique identifier when at least one of the plurality of first M2M devices reconnects to the mobile communication network device. 8. The method of claim 7,
Wherein the unique identifier is at least one of a group including a Globally Unique Temporary Identifier (GUTI) and an S-Temporary Mobile Subscriber Identity (S-TMSI). Collecting data from at least one of a plurality of M2M devices having the same device identifier;
The mobile communication network device authenticates the plurality of M2M devices with the same device identifier shared by the plurality of M2M devices communicated by at least one of the plurality of M2M devices and permits connection to the plurality of M2M devices step; And
Wherein at least one of the plurality of M2M devices transmits data to the mobile communication network device,
Wherein the plurality of M2M devices transmit data in a predetermined time range from a time when data transmission is possible and each of the plurality of M2M devices transmits data at different times in the time domain when the M2M devices transmit data, Lt; / RTI > 11. The method of claim 10,
Wherein the device identifier is at least one of a group comprising a Mobile Subscriber Identification Number (MSIN) and an International Mobile Subscriber Identity (IMSI). 11. The method of claim 10,
The mobile communication network device allocating the same device identifier to the plurality of M2M devices; And
Wherein the mobile communication network device stores the same device identifier. ≪ RTI ID = 0.0 > 31. < / RTI > 11. The method of claim 10,
Further comprising: the mobile communication network device allocating the different time to each of the plurality of M2M devices, wherein the M2M device transmits data through the mobile communication network. 11. The method of claim 10,
Wherein the server receiving the data collected by the plurality of M2M devices through the mobile communication network device previously allocates the different time to each of the plurality of M2M devices in advance through the mobile communication network How to transfer data. 11. The method of claim 10,
Wherein each of the plurality of M2M devices is connected to each of the plurality of M2M devices at different times based on at least one of the order in which each device collects data, a preset order, a location of the device, and a distance between the device and the AP of the mobile communication network device Wherein the M2M device transmitting the data transmits data over the mobile communication network. 11. The method of claim 10,
After the mobile communication network device authenticates the plurality of M2M devices with the same device identifier, assigning unique identifiers unique to each of the plurality of M2M devices in the mobile communication network device; And
Wherein at least one of the plurality of M2M devices accesses the mobile communication network device using the unique identifier and transmits data to the mobile communication network device, wherein the M2M device transmits data through the mobile communication network How to. 17. The method of claim 16,
Wherein the unique identifier is at least one of a group including a Globally Unique Temporary Identifier (GUTI) and an S-Temporary Mobile Subscriber Identity (S-GUTI). Storing an identical International Mobile Subscriber Identity (IMSI) value assigned to a plurality of M2M devices connected to the LTE network by the HSS;
The MME transmitting to the HSS an identifier carried by at least one of the plurality of M2M devices;
The HSS comparing the IMSI value with the identifier to perform initial authentication for the at least one M2M device;
When the initial authentication is successful, the MME receives data in a predetermined time zone from the reference time point from the plurality of M2M devices, and each of the plurality of M2M devices transmits data at different times in the time domain; And
Wherein the PGW transmits the data over an LTE network, wherein the M2M device comprises receiving the data. 19. The method of claim 18,
Wherein the MME further comprises transmitting the different time to each of the plurality of M2M devices in advance. 19. The method of claim 18,
Further comprising the step of granting a globally unique temporary GUID (Globally Unique Temporary Identifier) or an S-TMSI (S-TMSI) to each of the plurality of M2M devices when the MME succeeds in the initial authentication How to transfer data over an LTE network. 21. The method of claim 20,
Wherein the MME performs authentication for the at least one M2M device using the GUTI or S-TMSI delivered by the at least one M2M device when the MME requests to reconnect at least one of the plurality of M2M devices step; And
The method further comprising the step of the MME receiving data communicated by the at least one M2M device to transmit data over the LTE network.

Images