WO2013005938A2 - Procédé et appareil destinés à servir de déclencheur pour un dispositif mtc dans des conditions de congestion / surcharge du réseau - Google Patents

Procédé et appareil destinés à servir de déclencheur pour un dispositif mtc dans des conditions de congestion / surcharge du réseau Download PDF

Info

Publication number
WO2013005938A2
WO2013005938A2 PCT/KR2012/005039 KR2012005039W WO2013005938A2 WO 2013005938 A2 WO2013005938 A2 WO 2013005938A2 KR 2012005039 W KR2012005039 W KR 2012005039W WO 2013005938 A2 WO2013005938 A2 WO 2013005938A2
Authority
WO
WIPO (PCT)
Prior art keywords
mtc device
mtc
trigger
wireless network
network
Prior art date
Application number
PCT/KR2012/005039
Other languages
English (en)
Korean (ko)
Other versions
WO2013005938A3 (fr
Inventor
홍성표
조수현
김세훈
이현송
이성훈
Original Assignee
주식회사 케이티
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020110066261A external-priority patent/KR20130007380A/ko
Application filed by 주식회사 케이티 filed Critical 주식회사 케이티
Publication of WO2013005938A2 publication Critical patent/WO2013005938A2/fr
Publication of WO2013005938A3 publication Critical patent/WO2013005938A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • a method of triggering an MTC device to initiate data communication with an MTC server by an MTC server in providing a machine type communication (MTC) service through a wireless network of a mobile service provider, a method of triggering an MTC device to initiate data communication with an MTC server by an MTC server.
  • an invention relating to an apparatus. More particularly, the present invention relates to a technique for triggering an MTC device to initiate data communication with an MTC server even in a congested or overloaded state 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 to 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.
  • MTC communication can proceed even if the network is congested or overloaded, so a study on a method and apparatus for enabling MTC communication during network congestion is required.
  • an MTC device configured with a low access priority may perform an MTC device triggering even in a network congestion or overload condition. Allows you to access the network with similar or equivalent priorities to non-devices.
  • the MTC device since the MTC device performs the requested trigger even in a congestion / overload state of the network, the MTC device enables urgent processing of the MTC service and enables data transmission of the MTC device even when the network is congested or overloaded.
  • Method of performing a trigger of the MTC device comprises the steps of receiving a trigger request message for requesting a trigger of the MTC device from the MTC server, to determine whether the trigger request message immediately includes the trigger request identification information And transmitting a trigger request message to the MTC device according to whether the immediate trigger request classification information is included.
  • a method of performing a trigger of an MTC device may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, and checking whether the trigger request message includes immediate trigger request identification information. If the immediate trigger request classification information is included, requesting a device that executes connection control of the MTC device to process the network connection of the MTC device with a priority equal to or higher than that of a general device, and Sending a trigger request message to the MTC device to trigger the MTC device, and attempting a network connection (NAS signaling) without including a low connection priority at the MTC device.
  • NAS signaling network connection
  • a method of performing a trigger of an MTC device may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, and confirming whether the trigger request message includes immediate trigger request identification information. Inquiring, if the immediate trigger request classification information is not included, inquiring a network load state of a device executing the access control of the MTC device; and as a result of the inquiring, the network load state is If not, transmitting the trigger request message to the MTC device via paging, and attempting a network connection (NAS signaling) at the MTC device, including a low connection priority, in response to paging. .
  • NAS signaling network connection
  • a wireless network system in another aspect of the present disclosure, includes a receiver configured to receive a trigger request message for requesting a trigger of an MTC device from an MTC server, and a controller configured to determine a congestion or overload condition of a wireless network to trigger the MTC device. And a transmitter configured to transmit a trigger request message to the MTC device according to a condition of congestion or overload of the network and whether the trigger request message immediately includes the trigger request identification information.
  • the MTC device performs the trigger. In order to access the wireless network at the same or higher connection priority as the device other than the MTC device.
  • a method in which an MTC server performs a trigger in a network congestion / overload state may include generating, by an MTC server, a trigger request message requesting a trigger of an MTC device, and transmitting the generated message to a wireless network system. Transmitting, receiving information about network congestion or overload from the wireless network system, generating and transmitting a trigger request message to the wireless network system so that triggering of the MTC device is performed immediately, and configuration information Performing a trigger with the temporarily changed MTC device.
  • the MTC device may override configuration information of the MTC device to perform the trigger, and connect the MTC device with a normal priority or a high priority.
  • a method of performing a trigger in a congestion / overload state of a wireless network may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, and a wireless network to perform triggering of the MTC device. Confirming a congestion or overload condition of the network, transmitting information on the congestion or overload of the network to the MTC server, and transmitting a trigger request message to the MTC device to trigger the MTC device; And allowing a wireless network connection of the MTC device whose configuration information has been temporarily changed, wherein the MTC device overrides the configuration information of the MTC device to perform the trigger, and is usually of priority or high priority. It is characterized by the connection in the ranking.
  • a method in which an MTC device performs a trigger in a congestion / overload state of a wireless network may include receiving, by the MTC device, a message instructing to change configuration information of a device from a device management apparatus. Changing the configuration information to a first value, performing a trigger through a wireless network system, transmitting and receiving data with an MTC server, and receiving a message indicating configuration information change of the configuration information of the MTC device. Changing to a second value that is a value prior to receiving.
  • a method of changing a setting of the MTC device to trigger the MTC device in a congestion / overload state of a wireless network may include configuring configuration information of the MTC device from an MTC server or a wireless network system. Receiving a message requesting a change to a value, transmitting a message instructing the MTC device to change the configuration information to a first value, and receiving the configuration information of the MTC device from the MTC server or the wireless network system. Receiving a message requesting a return to a second value, and transmitting a message instructing the MTC device to return configuration information to a second value, wherein the MTC device is configured to transmit the configuration information to the second value. After changing to have a value of 1, perform data communication with the MTC server And that is characterized.
  • MTC server is a transmitter for transmitting a trigger request message requesting a trigger of the MTC device to a wireless network system, a receiver for receiving information about network congestion or overload from the wireless network system, and And a control unit generating a trigger request message to immediately trigger the MTC device and transmitting the transmitter to the wireless network system, wherein the MTC device rejects configuration information of the MTC device to perform the trigger. override), and access with normal priority or high priority.
  • a wireless network system in another aspect of the present disclosure, includes a receiver configured to receive a trigger request message for requesting a trigger of an MTC device from an MTC server, and a controller configured to determine a congestion or overload condition of a wireless network to trigger the MTC device. And a transmitting unit which transmits information about the congestion or overload of the network to the MTC server, and transmits a trigger request message to the MTC device to trigger the MTC device, wherein the MTC device performs the trigger.
  • the configuration information of the MTC device it is characterized in that the access to normal priority or high priority.
  • MTC server is a transmitter for transmitting a trigger request message requesting a trigger of the MTC device to a wireless network system, a receiver for receiving information about network congestion or overload from the wireless network system, and A control unit for generating a trigger request message to immediately trigger the MTC device and controlling the transmitter to transmit to the wireless network system, wherein the MTC device temporarily stores configuration information of the MTC device to perform the trigger; It is characterized by changing.
  • an MTC device may include a transmitter configured to transmit data with an MTC server, a receiver configured to receive data from an MTC server, and to receive a message instructing to change configuration information of a device from a device management apparatus, and the MTC device.
  • the controller receives the message, and the controller changes the configuration information of the MTC device to a second value which is a value before receiving the message instructing to change the configuration information.
  • Device management apparatus is a receiving unit for receiving a message requesting to change the configuration information of the MTC device to the first value or the second value from the MTC server or the wireless network system, the MTC device A control unit for generating a message instructing to change the configuration information to a first value or a second value, and a transmitting unit for transmitting the generated message to an MTC device, wherein the MTC device is a congestion / After performing a trigger with the configuration information as the first value in the overload state, the configuration information is reduced to the second value again.
  • a method of performing a trigger of an MTC device may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, and confirming whether the trigger request message includes immediate trigger request identification information. And if the immediate trigger request classification information is not included, inquiring a network load state of a device executing the access control of the MTC device, and as a result of the inquiring, the network load state is a congestion or an overload state. In the case of transmitting a cause value indicating that the trigger failed due to network congestion / overload, through the confirmation message or the report message for the trigger request message.
  • a method of performing a trigger of an MTC device may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, and confirming whether the trigger request message includes immediate trigger request identification information. Inquiring, if the immediate trigger request classification information is not included, inquiring a network load state of a device executing the access control of the MTC device; and as a result of the inquiring, the network load state is Otherwise, forwarding the trigger request message to the MTC device through paging, and including a low access priority indication in the NAS signaling message when attempting a network connection at the MTC device in response to paging.
  • a method of performing a trigger of an MTC device in a congestion / overload state of a network may include generating a trigger request message for requesting a trigger of an MTC device by an MTC server, and transmitting the generated message to a wireless network system.
  • the wireless network system checks the congestion or overload of the wireless network to be triggered by the MTC device, and transmits information on the congestion or overload of the network to the MTC server.
  • the wireless network system Generating and transmitting a trigger request message to the wireless network system so that the MTC device is triggered immediately, the wireless network system transmitting a trigger request message to the MTC device so that the MTC device is triggered; MTC D
  • the vice changes the configuration information of the MTC device to a first value to perform the trigger, performs a trigger through the wireless network system, and then transmits and receives data with the MTC server. And changing the configuration information of the MTC device to a second value which is a value prior to the step of receiving a message indicating the configuration information change.
  • the method may include receiving a trigger request message requesting a trigger of an MTC device from an MTC server, confirming a congestion or overload condition of a wireless network that will trigger the MTC device, or immediately including trigger request identification information in the trigger request message. Checking whether the wireless network is congested or Sending an trigger request message to the MTC device when it is overloaded or when the MTC device needs triggering immediately, and allowing a wireless network connection of the MTC device whose configuration information has been temporarily changed.
  • a wireless network system includes a receiver configured to receive a trigger request message for requesting a trigger of an MTC device from an MTC server, confirming a congestion or overload condition of a wireless network to perform triggering of the MTC device, or A control unit for checking whether the trigger request message immediately includes trigger request classification information, and a transmitter for transmitting a trigger request message to the MTC device when the wireless network is congested or overloaded, or when the MTC device needs to trigger immediately. And the MTC device temporarily changes configuration information of the MTC device to perform the trigger.
  • an MTC device configured to request access to a network with low priority access attribute information may have low access priority attribute information even under network overload / congestion. Allows you to perform a connection without including it. If the MTC device detects a congestion or overload in the network, for example to trigger a data communication session with the MTC server, for example to trigger an MTC device, the MTC device uses an OMA DM procedure or an OTA procedure. After releasing the low access priority attribute information of the MTC device to start the data communication with the MTC server.
  • the low priority priority attribute information of the MTC device is reduced by using the OMA DM procedure or the OTA procedure, so that the MTC device is requested by the MTC server even during network congestion or overload.
  • the MTC device maintains the low access priority attribute information, and then the MTC device can transmit data with the MTC server even under network congestion or overload conditions, while maintaining the low access priority attribute. It is effective to make.
  • FIG. 1 is a diagram illustrating a configuration of a network according to an embodiment of the present specification.
  • FIG. 2 is a diagram illustrating a configuration of a plurality of devices according to an embodiment of the present specification.
  • FIG. 3 is a diagram illustrating a process of performing triggering using SMS when the network is not in a congestion state according to an embodiment of the present specification.
  • FIG. 4 is a diagram illustrating a process of performing triggering using an HLR when the network is not in a congestion state according to an embodiment of the present specification.
  • FIG. 5 is a diagram illustrating a process of performing triggering using a device triggering gateway when the network is not in a congestion state according to an embodiment of the present specification.
  • FIG. 6 is a diagram illustrating a configuration of device properties according to an embodiment of the present specification.
  • FIG. 7 is a diagram illustrating a process of requesting a change of a device configuration by an MTC server according to one embodiment of the present specification.
  • FIG. 8 is a diagram illustrating a process of requesting a change of a device configuration by a wireless network system according to one embodiment of the present specification.
  • FIG. 9 illustrates triggering by confirming a congestion state of a network where data communication between an MTC device and an MTC server is to be established through MTC device triggering before processing a trigger request of an MTC server in a wireless network system according to an embodiment of the present specification.
  • FIG. 10 is a diagram illustrating a process of requesting a change of a device configuration by a wireless network system according to one embodiment of the present specification.
  • FIG. 11 is a diagram illustrating an operation of an MTC server according to one embodiment of the present specification.
  • FIG. 12 is a view illustrating an operation process in a wireless network system according to an embodiment of the present specification.
  • FIG. 13 is a diagram illustrating a process of performing a trigger in an MTC device according to one embodiment of the present specification.
  • FIG. 14 is a diagram illustrating a process of changing or reducing configuration information of an MTC device to enable a trigger in a device management apparatus according to an embodiment of the present specification.
  • FIG. 15 is a diagram illustrating a configuration of an MTC server, a device management apparatus, a wireless network system, and an MTC device according to one embodiment of the present specification.
  • FIG. 16 illustrates an example of performing an operation related to MTC communication in MTC-IWF according to an embodiment of the present specification.
  • FIG. 17 is a diagram illustrating a process of working with a separate server for changing a setting of an MTC device in order to perform a task related to MTC communication in an MTC-IWF according to another embodiment of the present specification.
  • FIG. 18 is a diagram illustrating an example in which a wireless network system performs an operation related to MTC communication based on trigger request classification information and a load state of a wireless network system according to an embodiment of the present disclosure.
  • FIG. 19 illustrates an example of performing a task related to MTC communication in MTC-IWF according to an embodiment of the present specification.
  • 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.
  • M2M machine to machine communication
  • IoT Internet of Thing
  • smart device communication smart device communication
  • machine oriented communication machine oriented communication
  • MTC machine type communication
  • a wireless network of a mobile service provider requesting access to a network with low access priority attribute information.
  • MTC device For a set MTC device, if congestion is detected / recognized in the network, the MTC device can be opened using the Open Mobile Alliance (OMA) Device Management (OMA) procedure or the Universal Subscriber Identity Module (USIM) Over The Air (OTA) procedure.
  • OMA Open Mobile Alliance
  • USIM Universal Subscriber Identity Module
  • OTA Universal Subscriber Identity Module
  • FIG. 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.
  • MTC Machine type communication
  • MTC is a form of data communication in which one or more entities do not necessarily require human interaction.
  • MTC service in providing the MTC service through the wireless network of the mobile communication service, a number of MTC services have a feature of rarely transmitting data at long time intervals.
  • One embodiment in which the MTC service device may be applied / used includes a meter for gas or electric meter reading.
  • the devices may transmit data by initiating data communication with the MTC server at regular time intervals preset in the device at rare intervals.
  • 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 receive a trigger request (or triggering request) of the MTC device.
  • 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 a 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).
  • the MTC device may be configured to include low priority access in performing a network connection (NAS: Non Access Stratum procedure) according to the configuration of the network.
  • NAS Non Access Stratum procedure
  • the triggering 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, many MTC services are not sensitive to delay and have a characteristic of allowing a certain time delay.
  • the MTC device When reflecting these characteristics, the MTC device requests access (NAS signaling) including low access priority attribute information when performing the network access procedure, and in case of network congestion or overload, SGSN (In a system such as Serving GPRS Support Node / Mobility Management Element (MME), the MTC device preferentially rejects the access request of the MTC device including the low access priority attribute information, and transmits a reject message to the MTC device.
  • NAS signaling access
  • SGSN In a system such as Serving GPRS Support Node / Mobility Management Element (MME), the MTC device preferentially rejects the access request of the MTC device including the low access priority attribute information, and transmits a reject message to the MTC device.
  • MME Mobility Management Element
  • triggering may also be performed at a lower rank than general cellular communication.
  • 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.
  • a method and apparatus for performing urgently requested MTC triggering are needed. In particular, since the MTC device is connected to the network with a low connection order, a network solution including triggering may be denied when the network is overloaded or congested.
  • FIG. 2 is a diagram illustrating a configuration of a plurality of devices according to an embodiment of the present specification. The configuration of FIG. 1 was described in more detail. In the present specification, it can be applied when the network is congested.
  • the MTC device 201 and the MTC server 202 are entities that perform the MTC communication described above.
  • the MTC server 202 may configure a network such as a packet data network (PDN).
  • the mobile communication network 220 includes a home location register (HLR) 221, a serving GPRS support node (SGSN) 222, and a short message service (SMS-SC). Service Center (226), DT-GW 227, and Gateway GPRS Support Node (GGSN) 228.
  • HLR home location register
  • SGSN serving GPRS support node
  • SMS-SC short message service
  • the DT-GW (Device Triggering Gateway) 227 receives the MTC device triggering request from the MTC server 202, the MTC device 201 through the network according to the device triggering method set by the operator MTC server 202 It is acting as an agent requesting to initiate communication with it.
  • SMS can be used to forward the trigger request herein to the MTC device.
  • the SMS-SC 226 may send an SMS message.
  • the trigger request may be transmitted through the HLR 221 in the offline state of the device.
  • the OTA server 200 performs a function of configuring device property information using SMS, and the OMA DM server 201 uses an HTTP transmission method through a DM client installed in the device. Or, as a device that performs various device management functions by using SMS, SMS can be utilized for simple device attribute information configuration or notification.
  • the over-the-air server 200 or the OMA DM server 201 is a low access priority MTC device in order to succeed in triggering a low access priority MTC device in a network congestion or overload condition.
  • An embodiment of a device management apparatus that performs a task of temporarily changing a property of a device.
  • the MTC device triggering scheme for allowing the MTC device to initiate data communication with the MTC server at the request of the MTC server can be variously developed according to the network registration status of the MTC device to perform the MTC device triggering and the entity handling the MTC device triggering. have.
  • FIG. 3 is a diagram illustrating a process of performing triggering using SMS when the network is not in a congestion state according to an embodiment of the present specification.
  • the MTC server 302 transmits an SMS text including an MSISDN (Mobile Subscriber Integrated Services Digital Network Number) number of an MTC device 301 to be triggered on an SMS message, an IP address of the MTC server 302, etc. S310).
  • the SMS-SC 309 transfers the text received in step S310 to the MTC device 301.
  • the MTC device 301 having received the text of S320 establishes data communication with the MTC server 302 to initiate communication (S330). 3 can be applied while the MTC device is attached to the network.
  • FIG. 4 is a diagram illustrating a process of performing triggering using an HLR when the network is not in a congestion state according to an embodiment of the present specification.
  • the MTC server 402 requests triggering from the HLR 408 including information necessary for triggering the MTC device 401 (for example, a device identifier such as MSISDN and an IP address of the MTC server) (S410).
  • the HLR 408 transmits a triggering request message to the SGSN 409 accommodating the MTC device 401 for which triggering is requested (S420).
  • the SGSN 409 transmits triggering request information by using non access stratum (NAS) signaling procedures for network access.
  • NAS non access stratum
  • 4 shows a Routing Area Update procedure during NAS signaling procedures.
  • the MTC device 401 transmits a Routing Area Update Request message to the SGSN 409 for a Routing Area Update (S430).
  • the SGSN 409 transmits a Routing Area Update Accept (RAU) message to the received RAU request, and at this time, includes triggering request information in the RAU response message (S440).
  • the MTC device 401 confirms that there is a trigger request from the MTC server 402 while receiving the RAU response message, completes the RAU process (RAU Complete) (S450), and starts data communication with the MTC server 402. Communication can be set to (S460).
  • FIG. 5 is a diagram illustrating a process of performing triggering using a device triggering gateway when the network is not in a congestion state according to an embodiment of the present specification.
  • the MTC server 502 requests a trigger from the triggering gateway (DT-GW) 508 (S510).
  • the DT-GW 508 requests the triggering process with respect to the received triggering request by using one of various MTC device triggering methods in consideration of the network connection state of the MTC device 501. That is, the DT-GW 508 may request a trigger by transmitting an SMS to the SMS-SC of FIG. 3, and may request a trigger from the HLR as shown in FIG. 4 (S520).
  • the SMS-SC / HLR 509 requests a trigger from the MTC device 501 according to the scheme of FIG. 3 or 4 (S530), and as a result, the MTC device 501 ) May set communication to initiate data communication with the MTC server 502 (S540).
  • MTC device when looking at the state of the MTC device that the MTC device can be triggered, i) MTC device is attached to the network in the online (online) state, but the packet data protocol (PDP) context or PDN connection (Packet Data No data session is established, such as a network connection, ii) the MTC device is online and attached to the network, and a data session, such as a PDP context (Packet Data Protocol context) or PDN connection (Packet Data Network connection).
  • FIG. 2 may also be divided into a state in which the MTC device is detached from the network in an offline state. However, the MTC device in the offline state is set to listen to a trigger request of the MTC device through a broadcast or paging channel.
  • the MTC device may be configured to request network access by including low priority access attribute information when performing a network access procedure.
  • the wireless network system such as the Serving GPRS Support Node (SGSN) preferentially rejects the MTC device's access request including the low access priority attribute information and sends the MTC device an access request.
  • SGSN Serving GPRS Support Node
  • a parameter for using the low access priority attribute information in the network connection process such as the universal subscriber identity module (USIM) of the MTC device
  • USB universal subscriber identity module
  • Pre-configured or device management functions such as OMA DM or OTA procedures can be used to configure parameters that use low access priority attribute information during network access.
  • MTC device should be in online state and registered in network.
  • FIG. 6 is a diagram illustrating a configuration of device properties information element according to an embodiment of the present specification.
  • Bits 5 to 8 are device attribute information element identifiers (EIEs) representing device attribute information.
  • the area of Bit 1 611 represents low priority or low priority access. If Bit 1 611 is 0, the device is set to a low priority (MS is not configured for NAS signaling low priority) . If Bit 1 611 is 1, the device is set to a low priority (MS is configured for NAS signaling low priority).
  • the MTC device may not be able to access a network by preferentially rejecting a request message of an MTC device that has requested network access including low access priority attribute information. Therefore, even if a network congestion or overload occurs, even if the MTC device triggering using the MTC device triggering method described above, the MTC device may attempt to access the network using the low access priority attribute information, MTC device, Communication with the server is not possible.
  • device triggering for an MTC device configured to access a network using low access priority attribute information may be impossible except for waiting for congestion and overload of the network.
  • FIG. 2 which is an embodiment of the present specification, in providing an MTC service through a wireless network of a mobile carrier, requesting access to a network with low priority access attribute information.
  • the MTC device detects congestion or overload in the network, use the OMA DM procedure or the OTA procedure to release the low access priority attribute information of the MTC device, and then the MTC device performs data communication with the MTC server. After the communication between the MTC device and the MTC server is terminated, the OMA DM procedure or the OTA procedure is used to reduce the low priority priority attribute information of the MTC device. Enable MTC device data transfer, then MTC device That explores the process of maintaining a low access priority attribute information.
  • the device management apparatus may control the attributes of the MTC device in order to change or reduce the attribute information of the MTC device, and an embodiment of the device management apparatus will be described with reference to an OMA-DM server or an OTA server.
  • the device management apparatus herein is not limited thereto, and a device having a function of changing an attribute of the MTC device may be separated from the MTC server independently, and the MTC server may also include such a function.
  • the network congestion or overload is illustrated as a situation in which the connection of the MTC device is denied, which is derived from the feature that the connection of the MTC device has a low connection rank, and in addition to the situation of network congestion / overload, the MTC device Means any situation where network access is denied.
  • FIG. 7 is a diagram illustrating a process of requesting a configuration change of a device by an MTC server according to one embodiment of the present specification.
  • the MTC server receives a network access request rejection result to recognize a network congestion situation, and the MTC server requests a device configuration change.
  • the MTC server 703 transmits a trigger request message to the wireless network system 709 for triggering the MTC device 701 (S710).
  • the wireless network system 709 requests triggering from the MTC device 701 (S712).
  • the wireless network system 709 includes equipment such as SMS-SC, DT-GW, HLR, SGSN, GGSN, etc., which are the mobile communication network entities of FIG. 1, and the wireless network system (
  • the network entity in step S710 of FIG. 7 transmitting the trigger request to 709 may vary according to the triggering method of the MTC device 701. That is, the SMS-SC in the MTC device triggering method through the SMS of FIG. 3, the HLR in the MTC device triggering method through the HLR of FIG.
  • the trigger request message through the SMS may use an SMS message, and the trigger request message through an HLR or DT-GW may use a general Internet protocol request message such as an HTTP text (hyper text transfer protocol request) message.
  • the trigger request message may include identification information of the MTC device 701 such as MSISDN and the MTC server 703 IP address.
  • the wireless network system 709 that has received the trigger request message transmits a trigger request message to the MTC device 701 according to a general MTC device 701 triggering method (S712).
  • the MTC device 701 receiving the trigger request message attempts to access the network with the SGSN including the low access priority attribute information (S714). However, if the wireless network system 709, for example, SGSN detects a congestion condition exceeding a certain number of times, the wireless network system 709 may determine that the MTC device 701 includes low access priority attribute information. Reject the network connection request (S720). In operation S722, the MTC device 703 requesting the MTC device triggering may be transmitted to the MTC device 701 due to network congestion.
  • the wireless network system 709 may transmit such information to the MTC server 703 through wireless network equipment such as SMS-SC, HLR, DT-GW, etc., which has requested the triggering of the MTC device 701. have.
  • wireless network equipment such as SMS-SC, HLR, DT-GW, etc.
  • the MTC server 703 recognizes the network congestion state and requests the OMA DM server or the OTA server 702 to change the low access priority attribute information of the MTC device 701 in order to change the setting of the MTC device 701 (S730). ).
  • the OMA DM server or the OTA server 702 requests the MTC device 701 to change the device settings using an SMS message (S732).
  • the MTC device 701 changes the device configuration so that the network connection can be requested without including the low connection priority attribute information (S740).
  • the configuration change can be implemented by changing the low priority bit 611 shown in FIG. 6 from 1 to 0.
  • the MTC device 701 may also change the configuration to a state in which communication is possible immediately by receiving a network access rejection message and stopping the set backoff timer.
  • the MTC server 703 requests the trigger to the wireless network system 701 again (S750).
  • the wireless network system 709 transmits a trigger request message to the MTC device 701 (S752).
  • the MTC device 701 requests a network connection without including low connection priority attribute information, and as a result, the MTC device 701 preferentially refuses access by allowing it to be processed in the same manner as a general communication service even in a network congestion or overload condition. By not doing so, data communication with the MTC server 703 can be established (S750).
  • the MTC server 703 may return the OMA DM server or the OTA server 702 to return the MTC device 701 to request a network connection with low connection priority attribute information.
  • connection priority attribute information of the MTC device 701 (S760), and the OMA DM server or the OTA server 702 reduces the connection priority attribute information of the MTC device 701 by using an SMS message.
  • Request (S762).
  • the MTC device 701 is reduced to original attribute information (S770). It can be implemented through reducing the low priority bit 611 of Figure 6 from 0 to 1.
  • 8 is a diagram illustrating a process of requesting a change of a device configuration by a wireless network system according to one embodiment of the present specification. 8 illustrates an embodiment in which a wireless network system that first receives a trigger request from an MTC server requests a change of MTC device configuration when a network congestion is detected as a result of the network access request rejection.
  • the MTC server 803 transmits a trigger request message to the wireless network system 809 for triggering the MTC device 801 (S810).
  • the wireless network system 809 requests triggering from the MTC device 801 (S812).
  • the wireless network system 809 includes equipment such as SMS-SC, DT-GW, HLR, SGSN, GGSN, etc., which are the mobile communication network entities of FIG.
  • the network entity in step S810 of FIG. 8 that transmits a trigger request may be changed according to the MTC device 801 triggering method.
  • the wireless network system 809 which has received the trigger request message transmits a trigger request message to the MTC device 801 according to a general MTC device 801 triggering method (S812).
  • the MTC device 801 receiving the trigger request message attempts to access the network with the SGSN including the low access priority attribute information (S814). However, if the wireless network system 809, for example, SGSN detects a congestion condition over a certain number of times, the wireless network system 809 may determine that the MTC device 801 includes low access priority attribute information. Reject the network connection request (S820). In operation S822, the MTC device 803 may request that the MTC device triggering be failed due to network congestion.
  • the wireless network system 809 may transmit such information to the MTC server 803 through wireless network equipment such as SMS-SC, HLR, DT-GW, etc., which has requested the triggering of the MTC device 801. have.
  • wireless network equipment such as SMS-SC, HLR, DT-GW, etc.
  • the MTC server 803 which has received the message that the MTC device triggering has failed, transmits a message requesting that the MTC device 801 be immediately triggered to the wireless network system 809 to receive urgent data (S830).
  • the MTC server 803 may immediately add trigger request classification information to the trigger request message in order to urgently request a trigger even in a network congestion.
  • the wireless network system 809 which has immediately identified the trigger request identification information through the trigger request message, transmits a low connection priority attribute of the MTC device 801 to the OMA DM server or the OTA server 802 to change the setting of the MTC device 801. Request a change of information (S832).
  • the OMA DM server or OTA server 802 requests the MTC device 801 to change settings of the device using an SMS message (S834).
  • the MTC device 801 changes the device configuration as described above with reference to FIGS. 6 and 7 so as to request a network connection without including low connection priority attribute information (S840).
  • the configuration may be changed to a state in which communication can be performed immediately by stopping the set backoff timer by receiving a network access rejection message.
  • the wireless network system 809 transmits a trigger request message to the MTC device 801 as in S812 (S842), and the MTC device 801 does not include low connection priority attribute information and requests network connection.
  • the network service of the MTC device is processed in the same manner as the general communication service and is not preferentially denied connection, thereby enabling data communication between the MTC server 803 and the MTC device (S850).
  • the wireless network system 809 that receives the MTC device triggering request from the MTC server 803 and changes the low connection priority attribute information of the MTC device is MTC.
  • the OMA DM server or the OTA server 802 requests the reduction of the connection priority attribute information of the MTC device.
  • the MTC device 801 is reduced to original attribute information (S870).
  • the wireless network system 809 may report a cause of failure (network congestion) (S822) and the MTC server 803 may immediately request a trigger (S830). That is, when the MTC server 803 recognizes the network congestion by a separate contract with the network operator, it may be the case that the network provider to solve the self by itself to process the triggering immediately.
  • a cause of failure network congestion
  • S830 a trigger
  • the MTC server 803 may optionally provide such information, and the MTC server 803 requests that the trigger be completed immediately. If it is confirmed that the information is shared, or the information about this, without the need to report a separate network congestion to the MTC server 803, it is possible to immediately proceed to the next process for triggering immediately.
  • FIG. 9 illustrates triggering by confirming a congestion state of a network where data communication between an MTC device and an MTC server is to be established through MTC device triggering before processing a trigger request of an MTC server in a wireless network system according to an embodiment of the present specification.
  • a diagram showing a process of processing. 9 illustrates an embodiment in which triggering is successful because there is no network congestion.
  • the process of transmitting the trigger request message to the wireless network system 909 by the MTC server 903 (S910) is the same as in FIGS. 7 and 8.
  • the wireless network system 909 inquires through the HLR / HSS the SGSN / MME information for performing the connection control of the MTC device 901 received the trigger request.
  • the request message and response message for querying the SGSN / MME information may use a general Internet protocol request message such as an HTTP request message and an HTTP response message.
  • the wireless network system 909 which processes the trigger request message of the MTC server 903, inquires about the current network load status of the SGSN / MME to the SGSN / MME executing the access control of the MTC device 901 (S920).
  • One embodiment of the request message and the response message for querying the network load information may use a DSD request message and a response message.
  • an embodiment of the request message and response message for querying the network load information may use a trigger request message and a trigger confirm or trigger report message for the SGSN.
  • the SGSN can respond with network congestion if the current network connection request detects a certain number of congestion conditions. If the SGSN is currently receiving the network connection request is less than the above-mentioned predetermined number of times, the wireless network system 909 transmits a trigger request to the MTC device 901 (S912) and establishes data communication between the MTC device and the MTC server. (S920).
  • FIG. 10 is a diagram illustrating a process of requesting a change of a device configuration by a wireless network system according to one embodiment of the present specification.
  • the network congestion is recognized in advance and the network congestion is reported to the MTC server as a procedure for processing the triggering process. For example.
  • the wireless network system recognizes the congestion state of the network where data communication between the MTC device and the MTC server is established through MTC device triggering without a trigger request process.
  • the MTC server 1003 requests a trigger from the wireless network system 1009 (S1010).
  • the trigger request has been described with reference to FIGS. 7, 8, and 9 above.
  • the wireless network system 1009 informs the MTC server 1003 that the network is congested. Deliver a notification message including a (S1022).
  • the network congestion state is checked without a separate MTC trigger process.
  • the message may use a general Internet protocol message such as an HTTP response message.
  • the MTC server 1003 received the congestion status notification message transmits a trigger request message to the wireless network system 1009 in order to receive urgent data to the MTC device (S1030).
  • the MTC server 1003 may immediately add trigger request classification information to the trigger request message in order to urgently request a trigger even in a network congestion.
  • the wireless network system 1009 which has immediately identified the trigger request identification information through the trigger request message, has a low connection priority attribute of the MTC device 1001 to the OMA DM server or the OTA server 1002 to change the setting of the MTC device 1001.
  • Request a change of information (S1032).
  • the OMA DM server or the OTA server 1002 requests the MTC device 1001 to change the device settings using an SMS message (S1034).
  • the MTC device 1001 changes the device configuration as described above with reference to FIGS. 6 and 7 so that the MTC device 1001 may request network access without including low connection priority attribute information (S1040).
  • the backoff timer set by receiving the network connection rejection message may also be stopped, and the configuration may be changed to enable communication immediately.
  • the wireless network system 1009 transmits a trigger request message to the MTC device 1001 in the same manner as in S812 (S1042), and the MTC device 1001 requests network connection without including low connection priority attribute information. Accordingly, even in a network congestion state, the MTC device 1001 is processed in the same manner as the general communication service and is not preferentially denied connection, thereby enabling data communication with the MTC server 1003 (S1050).
  • the wireless network system 1009 which receives the MTC device triggering request from the MTC server 1003 and changes the low connection priority attribute information of the MTC device is MTC.
  • the OMA DM server or the OTA server 1002 requests the reduction of the priority access attribute information of the MTC device.
  • the MTC device 1001 is reduced to original attribute information (S1070).
  • a process in which the wireless network system 1009 reports a cause of failure (network congestion) (S8102) and a request for an immediate trigger in the MTC server 1003 (S1030) may be omitted. That is, when the MTC server 1003 recognizes the congestion of the network by a separate contract with the network operator, it may be a case that the network provider to solve this by itself to immediately process the triggering.
  • the MTC server 1003 may optionally provide such information, and the MTC server 1003 requests that the trigger be completed immediately. If it is confirmed that the information is shared, or the information about this, without the need to report a separate network congestion fact to the MTC server 1003, it is possible to immediately proceed to the next steps for triggering immediately.
  • the wireless network by changing the device attribute information of the MTC device Allow access to the system. That is, it is possible to change the property information of the MTC device, to implement the connection to send and receive information by accessing the network in the same or similar rank to other entities coupled to the wireless network, and when such a triggering work is completed, The attribute information portion of the MTC device is reduced again to indicate that it is an MTC device, so that normal MTC communication can be performed.
  • the device management function for example, OMA Device management, etc.
  • the device management function for example, OMA Device management, etc.
  • the portion 611 of FIG. 6 may be changed or reduced to correspond to a lower rank.
  • FIG. 11 is a diagram illustrating an operation of an MTC server according to one embodiment of the present specification.
  • the MTC server generates a trigger request message for requesting a trigger of the MTC device (S1110).
  • the generated message is transmitted to a wireless network system.
  • SMS-SC in the MTC device triggering method through SMS of FIG. 3 HLR in the MTC device triggering method through HLR of FIG. 4, and DT- in the MTC device triggering method through DT-GW of FIG. 5.
  • the trigger request message through the SMS may use an SMS message, and the trigger request message through an HLR or DT-GW may use a general Internet protocol request message such as an HTTP text (hyper text transfer protocol request) message.
  • the trigger request message may include identification information of the MTC device such as MSISDN and the MTC server IP address.
  • the information on the network congestion or overload received from the wireless network system includes a result of confirming the network congestion as a result of transmitting the trigger request message as shown in Figs. That is, after the wireless network system requests a trigger from the MTC device, the connection of the MTC device fails, resulting in a network congestion afterwards.
  • the information on the network congestion or overload received from the wireless network system is a result of checking the state of the wireless network system to which the corresponding MTC device will trigger before the wireless network system transmits trigger information.
  • the wireless network system determines whether the MTC device triggers the congestion or overload of the wireless network, and may provide the MTC server with information indicating congestion / overload without transmitting a trigger request message separately.
  • configuration information of the MTC device is changed (S1140).
  • the MTC server may request a device management apparatus that controls the configuration of the MTC device to change the configuration information of the MTC device in order to temporarily change the configuration information of the MTC device.
  • the wireless network system may request a device management apparatus that controls the configuration of the MTC device to change the configuration information of the MTC device in order to temporarily change the configuration information of the MTC device. have.
  • configuration information of the MTC device may be temporarily changed, and a trigger request message may be generated and transmitted to the wireless network system so that triggering of the MTC device is immediately performed (S1150). That is, the MTC device requests a network connection without including low connection priority attribute information, and thus establishes data communication with the MTC server by processing the same as a general communication service in a network congestion state and not being denied preferentially. It becomes possible.
  • the configuration information of the MTC device may be reduced again.
  • the MTC server or the wireless network system requests the device setting reduction from the device management apparatus that has temporarily changed the configuration information of the MTC device, Again, data can be transmitted and received under the configuration information suitable for MTC communication and connected to the network.
  • FIG. 12 is a view illustrating an operation process in a wireless network system according to an embodiment of the present specification.
  • the wireless network system of FIG. 12 in the MTC device triggering method through SMS of FIG. 3, SMS-SC, the HLR in the MTC device triggering method through HLR of FIG. 4, and the MTC device triggering method through DT-GW of FIG. 5. It can be DT-GW.
  • a trigger request message for requesting a trigger is received from the MTC server (S1210).
  • the trigger request message through the SMS may use an SMS message, and the trigger request message through the HLR or DT-GW may be a general Internet protocol request message such as a hyper text transfer protocol request message. Can be used.
  • the trigger request message may include identification information of the MTC device such as MSISDN and the MTC server IP address.
  • the controller detects the congestion or overload of the wireless network that will trigger the MTC device, and transmits information on the congestion or overload of the network to the MTC server. In this case, as shown in FIGS.
  • the wireless network system includes a result of confirming network congestion as a result of transmitting a trigger request message by the wireless network system. That is, after the wireless network system requests a trigger from the MTC device, the connection of the MTC device fails, resulting in a network congestion afterwards.
  • the corresponding MTC device may be a result of checking a state of the wireless network system to trigger the trigger. That is, the wireless network system determines whether the MTC device triggers the congestion or overload of the wireless network, and may provide the MTC server with information indicating congestion / overload without transmitting a trigger request message separately.
  • configuration information of the MTC device is changed (S1230).
  • the MTC server may request the device management apparatus that controls the configuration of the MTC device to change the configuration information of the MTC device in order to temporarily change the configuration information of the MTC device.
  • the wireless network system may request a device management apparatus that controls the configuration of the MTC device to change the configuration information of the MTC device in order to temporarily change the configuration information of the MTC device. have.
  • configuration information of the MTC device is temporarily changed, and a trigger request message is transmitted to the MTC device to trigger the MTC device (S1240). That is, due to the changed configuration information, the MTC device can be triggered even in a congestion or overload of the network.
  • a trigger request message may be received from the MTC server to immediately trigger the MTC device as shown in FIG. 7.
  • the MTC device requests a network connection without including the low connection priority attribute information, so that even in a network congestion state, the MTC device is processed in the same manner as a general communication service and is not denied preferentially so that data communication with the MTC server can be established. do.
  • the configuration information of the MTC device may be reduced again.
  • the MTC server or the wireless network system requests the device setting reduction from the device management apparatus that has temporarily changed the configuration information of the MTC device, Again, data can be transmitted and received under the configuration information suitable for MTC communication and connected to the network.
  • FIG. 13 is a diagram illustrating a process of performing a trigger in an MTC device according to one embodiment of the present specification.
  • the MTC device receives a message instructing to change configuration information of the device from the device management apparatus in operation S1310.
  • the configuration information of the MTC device is changed to a first value (S1320). This is to prevent the MTC device from being rejected or processed at a lower rank in the wireless network system when the trigger is performed.
  • the configuration information of the MTC device is changed to a second value which is a value before receiving a message indicating the configuration information change (S1340).
  • the second value is to set 611 of FIG. 6 to a value of 1, which means to change the configuration information of the MTC device suitable for MTC communication.
  • the first value or the second value may be set according to an implementation process and an applied service, and is not limited to a specific value.
  • S1340 is to reduce configuration information of the MTC device, and as described above with reference to FIGS. 7, 8, and 10, the device management apparatus may request the reduction of configuration information.
  • FIG. 14 is a diagram illustrating a process of changing or reducing configuration information of an MTC device to enable a trigger in a device management apparatus according to an embodiment of the present specification.
  • the device management apparatus implementing FIG. 14 may be an OMA DM server or an OTA server as described above.
  • a message for requesting to change configuration information of the MTC device to the first value is received from the MTC server or the wireless network system.
  • a message instructing the MTC device to change the configuration information to a first value is transmitted.
  • the MTC device requests a network connection without including the low access priority attribute information. Accordingly, the MTC device can set data communication with the MTC server by processing the same as a general communication service and not being denied preferentially even in a network congestion state. Will be. That is, the MTC device performs a trigger with the MTC server, and data communication is possible.
  • the MTC server or the wireless network system receives a message requesting to reduce the configuration information of the MTC device to the second value (S1430), and instructs the MTC device to reduce the configuration information to the second value.
  • the message is transmitted (S1440).
  • the first value or the second value may be set according to an implementation process and an applied service, and is not limited to a specific value.
  • FIG. 15 is a diagram illustrating a configuration of an MTC server, a device management apparatus, a wireless network system, and an MTC device according to one embodiment of the present specification.
  • the configuration of FIG. 15 may implement various embodiments described herein.
  • each of the entities is shown in one drawing, but these entities are each connected to a network and may be remotely located.
  • the MTC server 1510 includes a receiver 1512, a controller 1514, and a transmitter 1516.
  • the transmitter 1516 transmits a trigger request message for requesting the trigger of the MTC device 1540 to the wireless network system 1530, and the receiver 1512 receives information about network congestion or overload from the wireless network system.
  • the controller 1514 is a component that controls the receiver 1512 and the transmitter 1516.
  • the controller 1514 generates a trigger request message to immediately trigger the MTC device 1540 and transmits the triggered message to the wireless network system 1530. Can be controlled to transmit.
  • the controller 1514 controls the configuration of the MTC device 1540 in order to temporarily change the configuration information of the MTC device 1540.
  • the transmitter 1516 may be controlled to request to change the configuration information of the configuration information 1540.
  • the device management apparatus 1520 is composed of a receiver 1522, a controller 1524, and a transmitter 1526.
  • the receiver 1522 receives a message requesting to change configuration information of the MTC device 1540 from the MTC server 1510 or the wireless network system 1530 to a first value or a second value, and the controller 1524. ) Generates a message instructing the MTC device 1540 to change the configuration information to a first value or a second value. Meanwhile, the transmitter 1526 transmits the generated message to the MTC device 1540. In this case, the MTC device 1540 performs a trigger using the configuration information as the first value in the congestion / overload state of the wireless network, and then reduces the configuration information to the second value again. By making the region a first value (0), the MTC device 1540 may not be rejected to a lower rank or processed late in the wireless network system 1530. Subsequently, when the MTC device 1540 completes the triggering with the first value, the MTC device 1540 may set the region 611 described with reference to FIG. 6 as the second value 1 for the original MTC communication.
  • the device management apparatus 1520 may be requested to change or reduce configuration information of the MTC device from any one of the MTC server 1510 or the wireless network system 1530, such as S1550 / S1560.
  • the wireless network system 1530 includes a receiver 1532, a controller 1534, and a transmitter 1536.
  • the receiver 1532 receives a trigger request message for requesting a trigger from the MTC server, and the controller 1534 checks the congestion or overload of the wireless network that will trigger the MTC device.
  • the transmitter 1536 transmits information about the congestion or overload of the network, which is a result of the check, to the MTC server and transmits a trigger request message to the MTC device so that the MTC device is triggered.
  • the MTC device When the network is congested or overloaded, the MTC device temporarily changes configuration information of the MTC device to perform the trigger, and the temporary change of the configuration information is transmitted to the device management apparatus 1520 by the controller 1534. Requests can be made as in S1560.
  • the MTC device 1540 includes a receiver 1542, a controller 1544, and a transmitter 1546.
  • the transmitter 1546 transmits data with the MTC server 1510, the receiver 1542 receives data from the MTC server 1510, and the MTC device 1540 cannot make a network connection in a network congestion / overload state.
  • the device management apparatus 1520 receives a message instructing to change configuration information of the device.
  • the controller 1544 After the control unit 1544 changes the configuration information of the MTC device to a first value, the controller 1544 performs a trigger through a wireless network system, and the receiving unit 1542 is provided from the device management apparatus 1520 after performing the trigger.
  • a message instructing reduction of configuration information of the device is received.
  • the first value or the second value may be set according to an implementation process and an applied service, and is not limited to a specific value.
  • FIG. 16 illustrates an example of performing an operation related to MTC communication in MTC-IWF according to an embodiment of the present specification.
  • the MTC-IWF (InterWorking Function) 1609 receives an immediate trigger request message from the MTC server 1602 (S1610).
  • the MTC-IWF 1609 selects a method for delivering the received trigger request to the MTC device 1601 (S1615). As described above with reference to FIGS. 7, 8, 10, etc., how does the MTC device check the current situation of the combined network, or which network entity will request the setting of the MTC device through the device management apparatus? Or, it may select whether or not to notify the MTC server 1602 of such a network condition.
  • a message for requesting a trigger is immediately transmitted to the MTC device 1601 based on the selected scheme.
  • various triggering methods and network nodes may be combined to deliver a trigger request message.
  • the configuration change is performed so that the MTC device 1601 may perform network access without including a low connection priority in the network congestion / overload state (S1625). Thereafter, data communication is established between the MTC device and the MTC server (S1630), and data exchange is possible.
  • FIG. 17 is a diagram illustrating a process of working with a separate server for changing a setting of an MTC device in order to perform a task related to MTC communication in an MTC-IWF according to another embodiment of the present specification.
  • the MTC-IWF (InterWorking Function) 1709 receives an immediate trigger request message from the MTC server 1702 (S1710).
  • the MTC-IWF 1709 transfers the received trigger request as a normal trigger request to the MTC device 1701 (S1720), but confirms that the trigger failed from the network (Receive the trigger failure) S1725).
  • the DM server or the OTA server 1702 is requested to change the setting of the MTC device to be triggered immediately (S1730).
  • the DM server or the OTA server 1702 requests a configuration change from the corresponding MTC device (S1735).
  • a setting change may be requested using SMS.
  • the configuration change request includes changing the low access rank portion as described above.
  • the MTC device changes the setting (S1740), and the MTC-IWF (InterWorking Function) 1709 requests a trigger again (S1750).
  • the trigger succeeds, and data communication is established between the MTC device and the MTC server (S1630), and data exchange is possible.
  • FIG. 18 is a diagram illustrating an example in which a wireless network system performs an operation related to MTC communication based on trigger request classification information and a load state of a wireless network system according to an embodiment of the present disclosure.
  • the network operator forwards a trigger request to the MTC device through paging for a network connection request initiated by all trigger requests (trigger requests sent by the MTC server) transmitted through the network to the MTC device, and the MTC device is paging. Attempts to connect to the network in response to the MTC device, but does not include low access priority attribute information.
  • a network connection request of an MTC device initiated by all trigger requests transmitted through the network is not included by triggering of the MTC server, and a connection is periodically included in the MTC device, including a low connection priority. It can also be configured to take precedence over network connection requests. That is, the network connection request of the disclosed MTC device may be processed at a higher priority than the general device, or may be processed at the same priority as the general device, or immediately include the trigger request identification information from the MTC server.
  • FIG. 18 An example of FIG. 18 is as follows.
  • the MTC server 1802 transmits a trigger request message to the wireless network system 1809 (S1810).
  • the MTC server 1802 may immediately add trigger request classification information to the trigger request message and transmit the trigger request message to the wireless network system 1809.
  • the wireless network system 1809 that processes the trigger request message of the MTC server 1802 immediately determines whether to process a trigger request (S1815). To this end, the wireless network system 1809 checks whether the trigger request message is immediately included in the trigger request message and transmitted. If the trigger request classification information is included immediately, the trigger request message is directly transmitted to the MTC device 1801.
  • the wireless network system 1809 receives a network connection request from the MTC device 1801 that is immediately triggered for SGSN or the like that executes the connection control of the MTC device 1801, it is equivalent to the general device or a general device. You can request to be processed at a higher priority.
  • the wireless network system 1809 inquires about the load state of the network. To this end, the wireless network system 1809 inquires the network load status of the current SGSN or the like that executes the connection control of the MTC device 1801, and only when the current network connection request is less than or equal to a certain number, that is, the load is not large or congested. If not, the trigger request message is transmitted to the MTC device 1801 (S1820). If the SGSN detects a congestion condition exceeding a certain number of current network connection requests (eg, NAS level congestion control starts), the MTC maintains a trigger request in the wireless network system 1809 until the network load goes out of congestion. The device 1801 may request triggering or may report to the MTC server 1802 that the current triggering is not possible.
  • a congestion condition exceeding a certain number of current network connection requests eg, NAS level congestion control starts
  • the MTC device 1801 which has received the trigger request message through the wireless network system 1809 is currently configured to perform NAS signaling including low access priority attribute information in the network connection of the MTC device 1801, but is currently MTC. Regardless of the operation state of the back off timer of the device, the MTC device attempts to connect to the network without including the low connection priority attribute information (S1830), and the network connection of the MTC device is performed even in the wireless network system 1809 such as SGSN. For an attempt, the network connection request is prioritized over the network connection request that attempts to connect, including a low connection priority.
  • the network connection request of the disclosed MTC device 1801 including the immediate trigger request identification information from the MTC server 1802 is processed at the same priority as the general device or higher than the general device, and immediately from the MTC server 1802.
  • the network connection request of the MTC device 1801 that does not include the trigger request classification information is processed at the same priority as that of the general device by NAS signaling without including the low access priority information.
  • the MTC device 1801 When the network connection request is processed, the MTC device 1801 establishes data communication with the MTC server 1802 (S1840).
  • FIG. 19 illustrates an example of performing a task related to MTC communication in MTC-IWF according to an embodiment of the present specification.
  • the MTC-IWF (InterWorking Function) 1909 receives an immediate trigger request message from the MTC server 1902 (S1910).
  • an emergency indication may be included in a trigger request.
  • the MTC-IWF 1909 Upon receiving the trigger request, the MTC-IWF 1909 verifies the trigger request and immediately determines whether to trigger it. In addition, the MTC-IWF 1909 may transmit an emergency indication to the MME / SGSN such that the MME / SGSN coupled to the MTC device does not stop the trigger request of the MTC device regardless of network congestion.
  • the MTC-IWF 1909 transmits a trigger request to the MTC device in such a manner as to paging through the SGSN / MME.
  • the MTC-IWF 1909 may or may not include an emergency indication in a trigger request message sent to the MTC device.
  • the MTC device 1901 receives a trigger request by paging or emergency indication, the MTC device 1901 attempts to communicate with the MTC server 1902. To initiate communication, the MTC device 1901 may attempt to connect to the network without including low connection priority attribute information during NAS signaling.
  • the trigger request from the MTC server is a normal trigger request rather than an immediate / emergency trigger request (eg it contains normal priority information rather than immediate / urgent priority information)
  • network congestion is detected by the MME / SGSN. Is not initiated (eg NAS level congestion control is not started), and if the MME / SGSN forwards a trigger request to the MTC device through paging, the MTC device will have a low connection priority in attempting NAS signaling in response to paging. May include ranking information.
  • the MTC device may override configuration information of the MTC device in order to perform an urgently requested trigger when the network is in a congested or overloaded state, and may connect with a normal priority or a high priority.
  • the MTC device can perform a trigger having a similar or the same priority as a general device. That is, when various embodiments of the present disclosure are applied, the MTC device connects to the network using low priority access attribute information in a network access procedure for normal MTC communication, but may be congested in a wireless network. In the event of an overload, the device management apparatus instructs to change the low priority access attribute information so that the MTC device can access a wireless network system such as SGSN without having a low access priority. When the network connection is requested using the low access priority attribute information, the request message of the MTC device may be rejected during overload / congestion of the network.
  • the MTC device remains off-line for most of the operating time, but even when network congestion and overload occur, if it is necessary to perform triggering, for example, the MTC service user is urgently looking for data.
  • the data of the MTC device may be transmitted to the MTC server based on a method of changing the device property information by applying the above-described embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un appareil destinés à servir de déclencheur pour un dispositif de communication de type machine (MTC) dans des conditions de congestion / surcharge du réseau. Le procédé destiné à servir de déclencheur pour un dispositif MTC dans un mode de réalisation de la présente invention comprend les étapes qui consistent à : recevoir d'un serveur MTC un message de demande de déclencheur demandant un déclencheur pour un dispositif MTC; vérifier que les informations pour distinguer une demande immédiate de déclencheur soient incluses dans le message de demande de déclencheur; et transmettre le message de demande de déclencheur au dispositif MTC en fonction de l'éventuelle inclusion des informations pour distinguer une demande immédiate de déclencheur.
PCT/KR2012/005039 2011-07-01 2012-06-26 Procédé et appareil destinés à servir de déclencheur pour un dispositif mtc dans des conditions de congestion / surcharge du réseau WO2013005938A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20110065287 2011-07-01
KR10-2011-0065287 2011-07-01
KR10-2011-0066261 2011-07-05
KR1020110066261A KR20130007380A (ko) 2011-07-01 2011-07-05 네트워크 폭주/과부하 상태에서 ｍｔｃ 디바이스의 트리거를 수행하는 방법 및 장치

Publications (2)

Publication Number Publication Date
WO2013005938A2 true WO2013005938A2 (fr) 2013-01-10
WO2013005938A3 WO2013005938A3 (fr) 2013-03-14

Family

ID=47437527

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/005039 WO2013005938A2 (fr) 2011-07-01 2012-06-26 Procédé et appareil destinés à servir de déclencheur pour un dispositif mtc dans des conditions de congestion / surcharge du réseau

Country Status (1)

Country Link
WO (1) WO2013005938A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015111963A1 (fr) * 2014-01-23 2015-07-30 (주)휴맥스 홀딩스 Dispositif de planification dans une communication du type machine d'évolution à long terme (lte)
US10129689B2 (en) 2015-11-02 2018-11-13 Definition Networks, Inc. Systems and methods for machine-type communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011041979A1 (fr) * 2009-10-09 2011-04-14 华为技术有限公司 Procédé, dispositif et système permettant à un équipement terminal de communications du type machine d'accéder à un réseau
WO2011042370A1 (fr) * 2009-10-08 2011-04-14 Alcatel Lucent Prevention d'encombrement a l'acces radio dans un systeme de communication mobile ou sans fil

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011042370A1 (fr) * 2009-10-08 2011-04-14 Alcatel Lucent Prevention d'encombrement a l'acces radio dans un systeme de communication mobile ou sans fil
WO2011041979A1 (fr) * 2009-10-09 2011-04-14 华为技术有限公司 Procédé, dispositif et système permettant à un équipement terminal de communications du type machine d'accéder à un réseau

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
'3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security aspects of Machine-Type Communications; (Release 11)' 3GPP TR 33.868 VO.3.1 April 2011, *
'3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Improvements for Machine-Type Communications; (Release 10)' 3GPP TR 23.888 V0.5.1 July 2010, *
ZTE: 'Group Identification in Overload Control' 3GPP TSG SA WG2 MEETING #79E (ELECTRONIC), TD S2-103127 06 July 2010, *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015111963A1 (fr) * 2014-01-23 2015-07-30 (주)휴맥스 홀딩스 Dispositif de planification dans une communication du type machine d'évolution à long terme (lte)
US10129689B2 (en) 2015-11-02 2018-11-13 Definition Networks, Inc. Systems and methods for machine-type communication

Also Published As

Publication number Publication date
WO2013005938A3 (fr) 2013-03-14

Similar Documents

Publication Publication Date Title
WO2018164498A1 (fr) Procédé pour maintenir un équipement d'utilisateur en mode connexion initiée par mobile uniquement dans un mode connecté
WO2020204530A1 (fr) Appareil et procédé de prise en charge d'un service de communication biunivoque dans un système de communication sans fil
WO2021091285A1 (fr) Procédé et appareil pour commander une tranche de réseau dans un système de communication sans fil
WO2019194630A1 (fr) Procédé et appareil aptes à prendre en charge des communications dans un système 5g
WO2018038503A1 (fr) Procédé et appareil d'exploitation d'un système de communication sans fil doté d'une gestion de mobilité et d'une gestion de session séparées
WO2020251309A1 (fr) Procédé et appareil permettant de fournir un service dans un système de communication sans fil
WO2019216717A1 (fr) Procédé et appareil pour l'exécution d'une communication dans un système de communication sans fil
WO2016208960A1 (fr) Procédé et appareil permettant d'abonner un dispositif électronique dans un système de communication mobile
WO2017142362A1 (fr) Procédé d'émission/réception de message associé à l'enregistrement de position dans un système de communication sans fil et appareil approprié
WO2018021861A1 (fr) Procédé et appareil pour effectuer une procédure de spécification de cellule pour un nr basé sur une tranche de réseau dans un système de communication sans fil
WO2011021875A2 (fr) Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
WO2015105374A1 (fr) Dispositif et procédé pour le faire fonctionner
WO2019194536A1 (fr) Procédé et appareil pour fournir un service de réseau de données de zone locale sur la base d'un modèle de non abonnement dans un système de communication sans fil
WO2014069925A1 (fr) Procédé et appareil pour gérer une connexion d'un réseau à commutation de paquets sur la base d'une zone locale dans un système de communication sans fil
WO2012074337A2 (fr) Appareil et procédé d'envoi/réception de trafic de diffusion groupée dans un système d'accès sans fil prenant en charge une communication de machine à machine
WO2013109082A1 (fr) Procédé et dispositif pour la définition d'une priorité dans la transmission de données
WO2014115711A1 (fr) Dispositif d'utilisateur, dispositif de passerelle, station de base radio, système de communications entre mobiles et procédé de communications entre mobiles
WO2017007122A1 (fr) Procédé et système de fourniture de service de réseau privé
WO2017003158A1 (fr) Procédé et dispositif permettant d'exécuter une communication de service de proximité dans un système de communication sans fil
WO2019221493A1 (fr) Procédé de commande de terminal pour service ido cellulaire dans un système de communication mobile 5g
KR101641096B1 (ko) 이동통신 시스템에서 노드 간 경로 관리 방법 및 장치
WO2020009537A1 (fr) Procédé et dispositif de gestion de ressources
CN108882278B (zh) 数据链路监测方法、设备、装置以及计算机可读存储介质
US11109265B2 (en) Method and apparatus for transmitting control message in software defined network-based mobile communication system
EP2926608A1 (fr) Appareil et procédé de radiorecherche dans un système de communications sans fil

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12807685

Country of ref document: EP

Kind code of ref document: A2