KR20120128758A - A Method and Apparatus of processing urgent trigger in Machine Type Communication - Google Patents

Abstract

PURPOSE: A method and apparatus for executing an emergency trigger method in MTC(Machine Type Communication) are provided to execute data communication when a network is busy. CONSTITUTION: A control unit(922) determines the urgent trigger of an MTC apparatus. The control unit creates the urgent trigger request message of the MTC apparatus. A transmission and reception unit(924) transmits the created message to a wireless network system. The transmission and reception unit transmits data to the MTC apparatus and receives the data from the MTC apparatus after the MTC apparatus is triggered. The MTC apparatus temporally converts the construction information of the MTC apparatus for executing an emergency trigger mode. [Reference numerals] (910) MTC device; (912,922,932) Control unit; (914,924,934) Transmission and reception unit; (920) MTC server; (930) Wireless network system

Description

Method and Apparatus of processing urgent trigger in Machine Type Communication

In the present specification, in providing a machine type communication (MTC) service through a wireless network of a mobile carrier, an MTC server triggers an MTC device to initiate data communication with an MTC server. The present invention relates to a technology for transmitting data including emergency information so that data communication can be initiated without prior connection rejection even in the event of congestion or overload of a wireless network.

Machine type communication (hereinafter referred to as "MTC" communication) is a form of data communication, in which one or more entities represent machine or machine communications that do not necessarily require human interaction. . MTC communication that does not require human interaction refers to all communication methods in which communication is performed without human intervention in the communication process. Meanwhile, the MTC communication can be applied to various business areas, and the communication quality required by these business areas varies. In particular, devices do not always require to be connected to a communication network, and information transmitted and received may also be transmitted and received with a predetermined pattern, and data may be transmitted and received without a pattern.

MTC communication can intermittently communicate or transmit and receive data at lower priority within the network, depending on the business area to which it is applied. However, when urgently need to transmit and receive data in the MTC communication has not been presented for the method and apparatus for processing it.

In order to solve the above-mentioned problem, in the present specification, in providing MTC service through a wireless network, when performing an MTC device triggering that is urgently requested, when the MTC server requests an urgent trigger including a predetermined condition or information, the MTC device Temporarily allows access to the network with similar or equivalent priorities to common devices.

In addition, since an urgently requested trigger is performed, urgent processing of the MTC service is possible, and data transmission of the MTC device is possible even when network congestion or overload occurs.

According to an embodiment of the present disclosure, a method in which an MTC server performs an emergency trigger in MTC communication may include: generating an urgent trigger request message of the MTC device by determining an urgent trigger of an MTC device; And transmitting and receiving data to and from the MTC device after a trigger of the MTC device, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger. It is characterized by.

According to another embodiment of the present disclosure, a method of performing an emergency trigger in an MTC device by an MTC device includes receiving an emergency trigger request message from a wireless network system, and changing configuration information of the MTC device to a first value. And transmitting and receiving data with the MTC server after triggering through the wireless network system, and changing configuration information of the MTC device to a second value which is a value prior to receiving the urgent trigger request message. Include.

According to another embodiment of the present disclosure, a method for performing an emergency trigger in an MTC communication by a wireless network system may include receiving an urgent trigger request message of an MTC device from an MTC server, checking the validity of the MTC server or the message; Storing the message, and forwarding the urgent trigger request message to the MTC device or a network node to which the MTC device is coupled, wherein the MTC device is configured to perform an urgent trigger of the MTC device. It is characterized by temporarily changing the configuration information.

The MTC server according to another embodiment of the present specification determines a urgent trigger of the MTC device to generate an urgent trigger request message of the MTC device, and transmits the generated message to a wireless network system, the MTC device And a transmitting / receiving unit which transmits and receives data with the MTC device after the trigger, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger.

The MTC device according to another embodiment of the present specification is a transceiver for receiving an urgent trigger request message from a wireless network system and triggering through the wireless network system, and then transmitting and receiving data with the MTC server, and the configuration of the MTC device. And a control unit for changing the information to a first value and changing the configuration information of the MTC device to a second value which is a value before receiving the urgent trigger request message after performing a trigger through the wireless network system. do.

A wireless network system according to another embodiment of the present disclosure receives an urgent trigger request message of an MTC device from an MTC server, and transmits and receives an urgent trigger request message to the MTC device or a network node to which the MTC device is coupled. And a controller for checking the validity of the MTC server or the message and storing the message, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger. do.

In providing the MTC service through the wireless network of the mobile service provider, when the MTC device triggers the MTC device to start a data communication session with the MTC server, the MTC server may provide information including urgency. It is possible to transmit together, and to temporarily change the attributes of the MTC device in the wireless network in response to the triggering request including the emergency information, to start data communication without prior rejection of access even during network congestion or overload It has the effect of enabling urgent data transmission of the MTC device.

1 is a diagram illustrating a configuration of a network according to an embodiment of the present specification.
2 is a diagram illustrating a procedure for performing urgently requested MTC device triggering according to an embodiment of the present specification.
FIG. 3 is a diagram illustrating the configuration of device properties according to an embodiment of the present specification.
4 is a diagram illustrating a configuration of a network according to an embodiment of the present specification.
FIG. 5 is a diagram illustrating a procedure for performing urgently requested MTC device triggering according to another embodiment of the present specification.
6 is a diagram illustrating a process of transmitting and receiving data with an MTC device by requesting an urgent trigger in an MTC server according to an embodiment of the present specification.
FIG. 7 is a diagram illustrating a process of transmitting and receiving data with an MTC server by receiving an urgent trigger request from an MTC device according to one embodiment of the present specification.
8 is a diagram illustrating a process of processing an urgent trigger in a wireless network system according to an embodiment of the present specification.
9 is a view showing the configuration of each device or system according to an embodiment of the present specification.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

In the present specification, the description will be focused on the MTC communication. MTC communication is variously referred to as machine to machine communication (M2M), Internet of Thing (IoT), smart device communication, or machine oriented communication, and the invention described herein. Is applicable for the communications listed above.

1 is a diagram illustrating a configuration of a network according to an embodiment of the present specification.

FIG. 1 shows an example in which a plurality of MTC devices (MTC devices, 101, 102, ..., 109) and a plurality of MTC servers (MTC servers, 121, 129) are connected to a wireless network 110 of a mobile service provider. . The MTC servers 121 and 129 may maintain a packet data protocol (PDP) context or a packet data network (PDN) connection. Meanwhile, in providing the MTC service, many MTC services rarely transmit data at long time intervals. One embodiment to which the MTC service device may be applied may be a gas or an electric meter. In order for a mobile communication provider to efficiently accommodate the MTC devices in the wireless network 110 of the mobile communication service provider and provide a communication service, the MTC devices 101, 102, ..., 109 of FIG. Rather than having to register a location on the wireless network 110 or maintain a data session, triggering to initiate data communication between the MTC device and the MTC server over the network upon a request from the MTC server 121, 129. It is desirable to use network resources efficiently. For example, when using the MTC devices of FIG. 1 as a meter for gas or electric metering, they are de-ached offline and broadcast or paging (offline) for most of the operating time. paging) is configured to listen to the trigger request (or triggering request) of the MTC device.

Accordingly, in FIG. 1, the MTC devices 101, 102,..., 109 are attached to the network in an online state, but a data session such as a PDP context or PDN connection is not established, or the MTC device Is registered on the network online and triggers data communication between the MTC device and the MTC server through the network when a request from the MTC server 121, 129 is established even when a data session such as a PDP context or PDN connection is established. triggering).

Meanwhile, the MTC device may have a low priority access in performing network access according to the configuration of the network. In this case, since the triggering of the MTC device also proceeds according to a low connection priority, the triggering may be processed at a lower priority compared to other devices connected to the network. That is, since many MTC services are not sensitive to delay and have a characteristic that can tolerate a certain time delay, when reflecting these characteristics, the MTC device includes low access priority attribute information when performing a network access procedure. Request a connection, and in case of network congestion or overload, the MTC device is first denied the connection request of MTC device including low connection priority attribute information in the system such as Serving GPRS Support Node (SGSN) of wireless network. By transmitting a reject message to the MTC device, the MTC device does not request a reconnection for a certain time, it is possible to prevent the deterioration of the quality of the general mobile communication by the MTC service.

Therefore, triggering may also be performed at a lower rank than general cellular communication. However, there is a case where it is necessary to urgently trigger the MTC device in the process of providing the MTC service. For example, in situations where an emergency occurs in the MTC service, urgent processing is required, or information needs to be collected immediately, triggering of the MTC device is more likely than other devices (for example, a device for mobile phone communication). If the ranking is low, this can reduce the quality of MTC service. In order to maintain the quality of MTC service while providing the inherent functions of MTC communication, a method and apparatus for performing urgently requested MTC triggering are needed.

2 is a diagram illustrating a procedure for performing urgently requested MTC device triggering according to an embodiment of the present specification.

MTC device triggering of Figure 2 is largely trigger request step (S210, S220) of the MTC server, validity check step (S230) for the trigger request, MTC device triggering method selection step (S240), trigger request step to the MTC device (S250) The data communication step between the MTC device and the MTC server (S260) is divided.

The wireless network system 209 of FIG. 2 is a system that enables communication between the MTC server 202 and the MTC device 201, and may be a gateway configuring a wireless network in one embodiment of the wireless network system. The gateway may be a home location register (HLR) serving a general gateway function, a serving GPRS support node (SGSN), a gateway GPRS support node (GGSN), or the like, and a gateway for device triggering (device triggering gateway, device triggering gateway, DT-GW).

The MTC server 202 determines emergency triggering of the MTC device (S210). Emergency triggering may be determined by the MTC server 202 according to network conditions and characteristics of a service required by the MTC server 202. The MTC server 202 requests emergency triggering from the wireless network system 209 (S220). The MTC server 202 may request the MTC device triggering by sending an emergency trigger request message to the wireless network system 209. The trigger request message of S220 may use a general Internet protocol request message, such as a hyper text transfer protocol (HTTP) request message, or may be a separate triggering message provided by a wireless network system. According to an embodiment of the information that may be included in the emergency trigger request message, identification information of the MTC device 201 to perform emergency triggering, a request counter for identifying the trigger request message, an emergency classification information, an emergency A processing valid time timer, a maximum number of urgent processing signaling requests, and the like.

The wireless network system 209 receiving the emergency triggering request checks the validity of the trigger request of the MTC server 202 (S230). This is an embodiment of checking the validity of the emergency triggering that is made exceptionally in the MTC communication. In operation S230, the emergency trigger request of the MTC server 202 received by the device triggering gateway may be checked whether the trigger request is received from an authorized MTC server, and the MTC device that is about to be triggered is also transmitted from the wireless network system 209. Check if the device can be processed. In an embodiment, the device triggering gateway constituting the wireless network system 209 may determine whether the MTC device to be triggered is a processable device. To this end, the device triggering gateway is connected to the MTC server 202 through a general secure connection method, and receives MTC device identification information from a subscriber profile of the MTC device from the HLR to confirm that the MTC device can be processed. Can be stored.

In step S240 of selecting an MTC device triggering method, a method of forwarding a trigger request from the wireless network system 209, for example, the device triggering gateway, to the MTC device 201 is selected. The MTC device triggering method may use various methods, for example, a method of using a short message service (SMS) in a network registration state, a method of delivering a trigger request through an HLR in an offline state, and the like. In the selection of the network triggering method, the state of the MTC device to be triggered, the state of the entities coupled to the network processing the triggering request, the operator settings and the like can be varied. In one embodiment of the present specification, an operator of the wireless network system 209 may designate one or more of a specific triggering method.

In the step S250 of requesting a trigger to the MTC device 201 in the wireless network system 209, the trigger request is transmitted to a network entity to process the MTC device triggering using the triggering method selected in S240.

Thereafter, between the MTC device 201 and the MTC server 202, the MTC device 201 establishes communication with the MTC server 202 according to the information included in the MTC trigger request message transmitted to the MTC device 201, and the data. Transmit and receive (S260).

The MTC device to which an embodiment of the present disclosure is applied may be configured to request connection to a network with low priority access attribute information for MTC communication when performing a network connection. However, as shown in FIG. 2, when the MTC trigger request message includes urgent information for requesting urgent triggering, a time required for performing urgent processing (urgent processing valid time timer period) or an urgent processing signaling request The device properties indicating the low access priority may be temporarily changed to the general access priority within the maximum number of times. A method of changing the attribute will be described later with reference to FIG. 3. In brief, the attribute can be changed by changing the low priority bit of FIG. 3 from 1 to 0. FIG.

Signaling, such as an attach request message or an PDP context request message, for an MTC device to access a network within the urgency processing validity time period or the maximum number of urgency processing signaling requests. When the message is transmitted, the low access priority may be temporarily released, so that communication between the MTC device and the MTC server may be possible by preventing communication of the MTC device preferentially even in a network congestion or overload environment.

FIG. 3 is a diagram illustrating the configuration of device properties according to an embodiment of the present specification.

3 shows a configuration of attribute information which is an embodiment of device configuration information. Bits 5 to 8 are device attribute information element identifiers (EIEs) representing device attribute information. The region of bit 1311 shows a low priority or a low priority access. If Bit 1 311 is 0, the device is set to a low priority (MS is not configured for NAS signaling low priority) .If Bit 1 311 is 1, the device is set to a low priority (MS is configured for NAS signaling low priority). When applying an embodiment of the present specification, the MTC device that does not receive the urgent triggering request, that is, when it is not necessary to urgently perform the triggering, has 311 part of the device attribute information set to 1 to connect to the wireless network system. Send and receive information. However, when the urgent triggering request described in the process of FIG. 2 is required, the MTC device sets 311 part of the device attribute information to 0 and accesses the wireless network system, ranking the same as or similar to other entities joined to the wireless network. You can connect to the network to send and receive information. When the work on the urgent triggering is completed, the MTC device sets the 311 part back to 1 to enable normal MTC communication.

The device attribute information described with reference to FIG. 3 may be information for distinguishing between an MTC device and a device other than MTC communication. In order to set the low access priority attribute information on the MTC device, the pre-configured parameters as shown in FIG. 3 in the universal subscriber identity module (USIM) of the device during the MTC device manufacturing process, and the low access during the network connection process It can be configured to use priority attribute information. Also, a parameter for setting low access priority attribute information in a network access process may be set using a device management function (e.g. OMA device management, etc.) used in a general mobile communication terminal. On the other hand, in order to set the parameter information of the MTC device using the device management function, the MTC device must be in a state registered in the network in an online state.

In one embodiment of the present specification, by using the change of the low access priority attribute information, the MTC device enables the trigger to perform an urgently requested trigger having a similar or the same priority as a general device.

According to one embodiment of the present specification, an MTC device in a non-emergency communication state may be configured to access a network using low priority access attribute information during a network access process. When congestion or overload occurs in a wireless network, in a wireless network system such as SGSN, the MTC device cannot access a network by rejecting a request message of an MTC device that requests network access using low access priority attribute information. For example, when congestion or overload occurs in a network, the MTC device may request that the MTC device establish data communication with the MTC server through a broadcast channel or a paging channel while offline.

However, when applying an embodiment of the present specification, if the urgent trigger is required even before the congestion and overload of the network is released by changing the use of the low access priority attribute information of the MTC device, the MTC device has a low access priority. The attribute information is changed to connect to the wireless network to enable urgent device triggering.

The MTC device remains off-line for most of the operating time, but even when network congestion and overload occur, urgent triggering is required, for example, when an MTC service user wants to inquire urgently. The data of the MTC device can be transmitted to the MTC server using the procedure of FIG. 2 and the method of changing the device attribute information of FIG. 3.

4 is a diagram illustrating a configuration of a network according to an embodiment of the present specification. 1 and 2 have been described in more detail. One embodiment of the present specification can be applied to the configuration of FIGS. 1 and 2, and one embodiment of the present specification can be applied to the configuration of FIG. 4.

In FIG. 4, the MTC device 401 and the MTC server 402 are entities that perform the MTC communication described above. The MTC server 402 constitutes a packet data network (PDN). 1 and 2, the mobile communication network 420 includes an HLR 421, an SGSN 422, an SMS-SC 426, a DT-GW 427, and a GGSN ( 428). Among them, as described above, the DT-GW receives the MTC device triggering request from the MTC server 402 and communicates with the MTC server 402 by the MTC device 401 through the network according to the device triggering method set by the operator. It is acting as an agent requesting to initiate, and according to one embodiment of the present specification, an MTC server may process a triggering request transmitted including urgent information.

An SMS message may be sent in the SMS-SC 426 to use the SMS to communicate the urgent trigger request herein to the MTC device. In addition, the trigger request may be transmitted through the HLR 421 in the offline state of the device.

FIG. 5 is a diagram illustrating a procedure for performing urgently requested MTC device triggering according to another embodiment of the present specification. FIG. 5 illustrates a method of performing MTC device triggering as described in FIG. 2 in more detail, and is an embodiment of a method of performing an urgent MTC device trigger through an HLR.

First, if the MTC device needs to trigger urgently, the MTC server 502 sends the device triggering gateway 509 the above-mentioned emergency information, an urgent processing valid time timer, and an urgent processing signaling request maximum number in the trigger request message. It transmits (S510). The trigger request message including the urgency may use a general Internet protocol request message such as an HTTP request message.

Trigger requests that include urgency can be expensive compared to normal billing, so you can send a generic trigger request message and make a trigger request that includes urgency only if the trigger fails within a certain time after the normal trigger request. have.

The device triggering gateway 509 receiving the trigger request including the urgency checks the validity of the trigger request and stores the emergency trigger request (S521). Thereafter, for example, a triggering method selected by an operator operating in advance, for example, a mobile communication network, is selected (S522). FIG. 5 shows a case where a method of transmitting a trigger request through the HLR 508 in the offline state is selected. The device triggering gateway 509 transmits a trigger request message including the aforementioned urgency to the HLR 508 (S525). The trigger request message including the urgency may also use a general Internet protocol request message such as an HTTP request message.

The HLR 508 receiving the trigger request message including the urgency converts the MTC device identification information included in the trigger request message into IMSI information using self-managed subscriber profile information. Also, using the self-managed location information, it determines the SGSN 507 that accommodates the MTC device 501 that needs to be urgently triggered, and stores the emergency trigger request (S531). ) May be set by temporarily changing the information set as the low access priority attribute on the subscriber profile to the general access priority for the duration of the urgent processing validity time period. The rank attribute information is reduced again.

Thereafter, the HLR 508 transmits a trigger request message including urgency using the IMSI information as an identifier for identifying the MTC device to the determined SGSN 507 (S532). As an embodiment of the trigger request message including the urgency, which is transmitted to the SGSN 507, a general Diameter Subscriber Data request message may be used, and the message may include location information of the MTC device 501. Can be.

SGSN 507 also stores an emergency trigger request (S541). Thereafter, the MTC device 501 is paged using the location information of the MTC device 501 provided through the emergency trigger request message in step S532 (S542). The paging may use a broadcast channel or a paging channel, and the paging information provides IMSI information, urgent information, urgent processing valid time timer, and maximum number of urgent processing signaling requests of the MTC device 501 to be triggered. Can be.

The MTC device 501 that receives the emergency trigger request through the paging of step S542 sends device property information indicating a low access priority during the emergency processing validity time timer period or within the maximum number of emergency processing signaling requests. Temporarily changes to general access priority and performs a device trigger (S550). This may be configured by changing the low priority bit 311 of FIG. 3 from 1 to 0. FIG. Thereafter, the MTC device 501 connects to the network, and establishes communication between the MTC device 501 and the MTC server 502 (S555).

SGSN 507 receiving the network connection request message of the MTC device 501 during the network connection process of the MTC device 501 releases the emergency trigger request of the MTC device 501 stored at step S541. (S560). At this time, the emergency trigger request stored in the SGSN 507 may be found using the IMSI information included in the network access request message. Thereafter, the SGSN 507 transmits a message confirming that the emergency trigger request has been processed to the HLR 508 (S561). The confirmation message may use a general Diameter Notification message. The HLR 508 receiving the confirmation message releases the emergency trigger request stored in step S531 (S570). At this time, the IMSI information of the MTC device 501 included in the confirmation message may be converted into the identification information of the MTC device 501 to find an emergency trigger request stored in the HLR 508. Thereafter, the HLR 508 transmits a message confirming that the emergency trigger request has been processed to the device triggering gateway 509 (S571). The confirmation message may use a general Internet protocol response message such as an HTTP response message. The device triggering gateway 509 receiving the confirmation message releases the emergency trigger request stored in step S521 (S580). Thereafter, the device triggering gateway 509 transmits a message confirming that the emergency trigger request has been processed to the MTC server 502 (S581). The confirmation message may also use a general Internet protocol response message such as an HTTP response message.

In one embodiment of the present specification, in providing an MTC communication service through a wireless network of a mobile carrier, urgently triggering an MTC device configured to request access to a network with low priority access attribute information. Do it. In other words, in triggering the MTC device to initiate data communication with the MTC server (initiating a communication session) by the MTC server, the urgency information is transmitted and transmitted, even when the wireless network is congested or overloaded. Enables data communication to be initiated without preferential access reject.

6 is a diagram illustrating a process of transmitting and receiving data with an MTC device by requesting an urgent trigger in an MTC server according to an embodiment of the present specification. First, the MTC server determines the urgent trigger of the MTC device to generate an urgent trigger request message of the MTC device (S620). The message may include one or more of identification information of the MTC device, emergency information, time information required for emergency processing, or the maximum number of requests for an emergency trigger. Here, the identification information of the MTC device may be a mobile subscriber ISDN (Mobile Subscriber ISDN or Mobile Station ISDN), IMSI, IMEI (International Mobile Equipment Identity), or Integrated Circuit Card ID (ICCID).

Urgent information may be information indicating the degree of urgency. This sets the degree of urgency in order to reduce the load on the wireless network, so that the urgency information can affect how the emergency trigger request is handled in the wireless network. For example, the trigger request message having the highest urgency is delivered unconditionally. If not, the emergency trigger request message is compared with the mobile communication in consideration of the load of the network. , It can be processed as next order.

The time information required for emergency processing includes a time reference value required for processing an urgent trigger after a predetermined time has elapsed in a wireless network or for processing with a general MTC trigger. Similarly, the maximum request count information of the emergency trigger is also counted in the wireless network, and when the maximum request count is exceeded, the trigger request may be configured to be processed as a general MTC trigger.

The message generated in S620 is transmitted to the wireless network system (S630). In an embodiment, the generated urgent trigger request message may be transmitted to a device triggering gateway. After the trigger of the MTC device, data is transmitted and received with the MTC device (S630). According to an embodiment of the present invention, the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger.

FIG. 7 is a diagram illustrating a process of transmitting and receiving data with an MTC server by receiving an urgent trigger request from an MTC device according to one embodiment of the present specification.

The MTC device receives an urgent trigger request message from the wireless network system (S710). As described above with reference to FIG. 6, the message may include at least one of identification information of the MTC device, emergency information, time information required for emergency processing, or maximum number of requests for an emergency trigger. Each will be replaced with the description of FIG. 6.

Thereafter, the configuration information of the MTC device is changed to a first value (S720). This is to prevent the MTC device from being rejected or processed at a lower priority in the wireless network system when the trigger is performed. When applying the embodiment of FIG. 3, it is recommended to set 311 of FIG. 3 to a value of 0. FIG. In one embodiment.

And after triggering through the wireless network system, and transmits and receives data with the MTC server (S730); The configuration information of the MTC device is changed to a second value which is a value before receiving the urgent trigger request message (S740). In this case, the second value is to set 311 in FIG. 3 to a value of 1, which means that the configuration information of the MTC device is changed to be suitable for MTC communication.

In this case, the configuration information of the MTC device is changed to a second value before receiving the urgent trigger request message, and when the time information required for the urgent processing passes, the trigger information may be passed or not. You can change it to a value (second value). This is to prevent the MTC device from operating like a general mobile phone device for a long time. Similarly, even when the trigger is performed in excess of the maximum number of requests of the emergency trigger, the original value (second value) can be changed.

8 is a diagram illustrating a process of processing an urgent trigger in a wireless network system according to an embodiment of the present specification. 8 may operate in one of a particular wireless network configuration system and may operate in multiple systems.

An emergency trigger request message of the MTC device is received from the MTC server (S810). The MTC server or the server checks the validity of the message and stores the message (S820). Validating the server or message ensures that the MTC device can perform an urgent trigger can burden the wireless network system, so that an urgent trigger request message can only be sent from a pre-scheduled or authorized MTC server. I mean. In addition, the validity of the message means that the urgent trigger processing of the MTC device may add a load to the wireless network system, thereby adding a method of verifying validity such as a separate encryption or a predetermined key value.

The urgent trigger request message is transmitted to the MTC device or the network node to which the MTC device is coupled (S830).

The message of S810 may include any one or more of identification information of the MTC device, emergency information, time information required for emergency processing, or maximum number of requests for an emergency trigger, and these information are described with reference to FIGS. 6 and 7. This means that the urgent trigger request information is performed within a certain range. In operation S820, the validity of the message may determine whether the emergency information, the time information, or the maximum number of requests are suitable for performing an urgent trigger request. That is, the degree of urgency can be used to reduce the load on the wireless network. For example, the trigger request message having the highest urgency is delivered unconditionally, and when the urgency is low, the network The urgent trigger request message can be processed in the next order by comparing the urgent trigger request message with the cellular phone communication.

The time information required for emergency processing includes a time reference value required for processing an urgent trigger after a predetermined time has elapsed in a wireless network or for processing with a general MTC trigger. Similarly, the maximum request count information of the emergency trigger is also counted in the wireless network, and when the maximum request count is exceeded, the trigger request may be configured to be processed as a general MTC trigger.

In an embodiment of storing information in FIG. 8, an emergency trigger request is previously stored in the DT-GW 509, the HLR 508, and the SGSN 507 of FIG. 5, which may be an emergency trigger completed or more. If it is no longer needed, the emergency trigger request related to the MTC device can be deleted or the emergency trigger can be released.

9 is a view showing the configuration of each device or system according to an embodiment of the present specification.

The configuration of the MTC device 910, the MTC server 920, and the wireless network system 930 are as follows.

The MTC server 920 includes a controller 922 and a transceiver 924. The controller 922 determines an urgent trigger of the MTC device to generate an urgent trigger request message of the MTC device. The transceiver 924 transmits the generated message to the wireless network system, and transmits and receives data with the MTC device after the trigger of the MTC device. Detailed operations of the MTC server 920 are as described above with reference to FIGS. 2, 5, and 6.

The MTC device 910 includes a controller 912 and a transceiver 914.

The transceiver 914 receives an urgent trigger request message from a wireless network system and transmits and receives data with the MTC server after triggering through the wireless network system. Of course, data transmission and reception with the MTC server is possible through the wireless network system (930).

The control unit 912 changes the configuration information of the MTC device to a first value, and after performing a trigger through the wireless network system, sets the configuration information of the MTC device to a value before receiving the urgent trigger request message. Change to the second value. According to one embodiment of the above-described first and second values, 311 is set to '0' as the first value in FIG. 3 to perform an urgent trigger, and then, '1' is set as the second value. It involves doing. Detailed operations of the MTC device 930 are as described above with reference to FIGS. 2, 5 and 7.

The wireless network system 930 includes a controller 932 and a transceiver 934.

The transceiver 934 receives an urgent trigger request message of an MTC device from an MTC server, and transmits the urgent trigger request message to the MTC device or a network node to which the MTC device is coupled.

The controller 932 checks the validity of the MTC server or the message and stores the message. Detailed operations of the wireless network system 930 are as described above with reference to FIGS. 2, 5, and 8.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.

201, 401, 501, 910: MTC device
202, 402, 502, 920: MTC Server
209, 930: wireless network system
310: device configuration information
420: mobile network
427, 509: DT-GW

Claims (11)

The MTC server determining an urgent trigger of the MTC device to generate an urgent trigger request message of the MTC device;
Transmitting the generated message to a wireless network system; And
And transmitting and receiving data with the MTC device after the trigger of the MTC device, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger. How to perform an emergency trigger in communication.
The method of claim 1,
And the message includes any one or more of identification information of the MTC device, urgent information, time information required for urgent processing, or a maximum number of requests of an emergency trigger, wherein the MTC server performs an emergency trigger in MTC communication.
The method of claim 1,
The transmitting step
Sending the generated urgent trigger request message to a device triggering gateway, wherein an MTC server performs an urgent trigger in MTC communication.
The MTC device receiving an urgent trigger request message from a wireless network system;
Changing configuration information of the MTC device to a first value;
Transmitting and receiving data to and from the MTC server after a trigger through the wireless network system; And
Changing configuration information of the MTC device to a second value that is a value prior to receiving the urgent trigger request message.
The method of claim 4, wherein
And the message includes any one or more of identification information of the MTC device, urgent information, time information required for urgent processing, or a maximum number of requests for an emergency trigger.
6. The method of claim 5,
Changing the configuration information of the MTC device to a second value prior to receiving the urgent trigger request message;
After the time information necessary for the emergency processing has passed or the trigger has been performed exceeding the maximum number of requests of the emergency trigger, the MTC device changes the second trigger to the second value. How to do it.
Receiving an urgent trigger request message of an MTC device from an MTC server;
Checking the validity of the MTC server or the message and storing the message; And
And transmitting the urgent trigger request message to the MTC device or a network node to which the MTC device is coupled, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger. A method of performing, in a wireless network system, an emergency trigger in MTC communication.
8. The method of claim 7,
The message includes one or more of identification information of the MTC device, emergency information, time information required for emergency processing, or maximum number of requests for an emergency trigger.
Validating the message further includes verifying that the urgency information, the time information, or the maximum number of requests is suitable for performing an urgent trigger request, wherein the wireless network system triggers an emergency trigger in MTC communication. How to do it.
A controller configured to determine an urgent trigger of an MTC device to generate an urgent trigger request message of the MTC device; And
And transmitting and receiving the generated message to a wireless network system and transmitting and receiving data to and from the MTC device after the trigger of the MTC device, wherein the MTC device temporarily stores configuration information of the MTC device to perform the emergency trigger. MTC server, characterized in that for changing to.
A transceiver for receiving an urgent trigger request message from a wireless network system and transmitting and receiving data with the MTC server after triggering through the wireless network system; And
After changing the configuration information of the MTC device to a first value and performing a trigger through the wireless network system, the configuration information of the MTC device to a second value which is a value before receiving the urgent trigger request message. MTC device comprising a control unit for changing.
A transceiver for receiving an urgent trigger request message of an MTC device from an MTC server, and transmitting the urgent trigger request message to the MTC device or a network node to which the MTC device is coupled; And
And a controller for checking the validity of the MTC server or the message and storing the message, wherein the MTC device temporarily changes configuration information of the MTC device to perform the urgent trigger. Network system.

Images