[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

KR20130038002A - Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof - Google Patents

Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof Download PDF

Info

Publication number
KR20130038002A
KR20130038002A KR1020110102614A KR20110102614A KR20130038002A KR 20130038002 A KR20130038002 A KR 20130038002A KR 1020110102614 A KR1020110102614 A KR 1020110102614A KR 20110102614 A KR20110102614 A KR 20110102614A KR 20130038002 A KR20130038002 A KR 20130038002A
Authority
KR
South Korea
Prior art keywords
trigger request
trigger
terminal
information
mtc
Prior art date
Application number
KR1020110102614A
Other languages
Korean (ko)
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
Application filed by 주식회사 케이티 filed Critical 주식회사 케이티
Priority to KR1020110102614A priority Critical patent/KR20130038002A/en
Priority to PCT/KR2012/008099 priority patent/WO2013051898A2/en
Publication of KR20130038002A publication Critical patent/KR20130038002A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

PURPOSE: A trigger request transmission server, a trigger request transmission method, a communication network, and a terminal trigger method thereof are provided to trigger terminals as a group unit in a communication network for an MTC(Machine Type Communication). CONSTITUTION: An MTC server(140) receives a trigger request from an external server. The MTC server determines a trigger request transmission method based on communication network information and information included in the trigger request. The MTC server transmits the trigger requests based on the trigger request transmission method. An SMS(Short Message Service) entity receives the trigger request from the MTC server. The SMS entity transmits an SMS message including the trigger request to UE(User Equipment)(120). [Reference numerals] (AA) Triggering an SMS group; (BB) Triggering a paging group; (CC) Triggering a broadcast group;

Description

Trigger request delivery server, trigger request delivery method of server, communication network, and terminal trigger method of communication network {Trigger Request Delivering Server, Triggering Request Delivering Method Thereof, Communication Network, and User Equipment Triggering Method Thereof}

The present invention relates to a control function associated with a trigger in a communication network for mechanical communication.

Machine Type Communication (MTC) is a form of data communication that represents a machine or machine to machine communication in which one or more entities do not or require minimal human interaction. An MTC device user terminal (or MTC device) such as an electric meter, gas meter, or vending machine equipped with a mobile communication module may communicate with an MTC server that controls the MTC device and collects data through a wireless network of a mobile communication operator. .

Many MTC application services provided through MTC communication rarely transmit data at long time intervals. In the case of such an application service, the MTC user may periodically allow the MTC device to start data communication through the wireless network of the mobile communication provider to transmit data to the MTC server. However, in another way, the MTC device initiates data communication through the mobile operator's wireless network at the request of the MTC server for control and management of the MTC device, collection of data on demand, and the like. You can also communicate with the MTC server. As in the latter case, the MTC device transmits a trigger request of the MTC server through the wireless network of the mobile communication operator, and the MTC device receiving the trigger request initiates data communication through the wireless network of the mobile communication operator to communicate with the MTC server. This is called triggering.

Need to trigger multiple MTC devices simultaneously with the same or similar properties (e.g., same service provider, same user, same application, same geographic location, etc.) in a carrier's wireless network that accommodates a large number of MTC devices There can be. In this case, a method of triggering on a group consisting of a plurality of MTC devices may be required.

An object of the present invention is to provide a system and method for triggering a terminal on a group basis in a communication network for mechanical communication.

One embodiment of the present invention, the server interface module for receiving a trigger request from an external server; A trigger determination module for determining a trigger request delivery method for determining a trigger method based on at least one of information included in the trigger request and communication network information; And a trigger forwarding interface module configured to forward a trigger request to an entity determined based on the trigger request forwarding method.

According to another embodiment of the present invention, a trigger request is received from an external server, a trigger request forwarding method is determined based on the information and communication network information included in the trigger request, and the trigger is performed on the entity determined based on the trigger request forwarding method. An access server for forwarding the request; And a short message service entity configured to receive a trigger request from the access server and transmit a short message including the trigger request to the terminal.

According to another embodiment of the present invention, a trigger request is received from an external server, a trigger request forwarding method is determined based on the information and communication network information included in the trigger request, and the trigger is performed on the entity determined based on the trigger request forwarding method. An access server for forwarding the request; And a paging entity that receives a trigger request from the access server and transmits a paging including the trigger request to a terminal.

According to another embodiment of the present invention, a trigger request is received from an external server, a trigger request forwarding method is determined based on the information and communication network information included in the trigger request, and the trigger is performed on the entity determined based on the trigger request forwarding method. An access server for forwarding the request; And a broadcast entity that receives a trigger request from the access server and transmits a broadcast message including the trigger request to a terminal through a broadcast channel.

Another embodiment of the invention, receiving a trigger request from an external server; Determining a trigger request delivery method for determining a trigger method based on at least one of information included in the trigger request and communication network information; And forwarding a trigger request to the entity determined based on the trigger request forwarding method.

Another embodiment of the invention, the access server receives the trigger request from the external server; Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information; Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And a short message service entity receiving the trigger request from the access server, transmitting the short message including the trigger request to the terminal.

Another embodiment of the invention, the access server receives the trigger request from the external server; Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information; Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And transmitting, by the paging entity receiving the trigger request from the access server, a paging including the trigger request to the terminal.

Another embodiment of the invention, the access server receives the trigger request from the external server; Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information; Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And a broadcast entity receiving a trigger request from the access server, transmitting a broadcast message including the trigger request to a terminal through a broadcast channel.

According to the present invention described above, a system and method for triggering a terminal on a group basis in a communication network for mechanical communication is provided.

1 illustrates an example of a network system for an MTC.
2 illustrates a method of device triggering using SMS.
3 illustrates a method of device triggering using a paging channel.
4 illustrates a method of device triggering using a broadcast channel.
5 illustrates a method of device triggering using SMS broadcast.
6 illustrates a group triggering control level according to an embodiment of the present invention.
FIG. 7 shows a flowchart of a triggering method in FIG. 6.
FIG. 8 shows the detailed steps of step S702 in FIG. 7.
9 illustrates a configuration of the MTC-IWF according to an embodiment.

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.

This specification will be described based on machine type communication (MTC). MTC may be variously called as M2M communication (Machine to Machine Communication), Internet of Things (IoT), Smart Device Communication, Machine Oriented Communication, and the like.

MTC is a form of data communication that represents a machine or machine-to-machine communication where one or more entities do not or require minimal human interaction. An MTC device user terminal (or MTC device) such as an electric meter, gas meter, or vending machine equipped with a mobile communication module may communicate with an MTC server that controls the MTC device and collects data through a wireless network of a mobile communication operator. .

Many MTC application services provided through MTC have a feature of rarely transmitting data at long time intervals. In the case of such an application service, the MTC user may periodically allow the MTC device to start data communication through the wireless network of the mobile communication provider to transmit data to the MTC server. However, in another way, the MTC device initiates data communication through the mobile operator's wireless network at the request of the MTC server for control and management of the MTC device, collection of data on demand, and the like. You can also communicate with the MTC server. As in the latter case, the MTC device transmits a trigger request of the MTC server through the wireless network of the mobile communication operator, and the MTC device receiving the trigger request initiates data communication through the wireless network of the mobile communication operator to communicate with the MTC server. This is called triggering.

1 illustrates an example of a network system for an MTC. The example shown in FIG. 1 is a structure under consideration in the 3rd Generation Partnership Project (3GPP), but the present invention is not limited to the system shown in FIG.

Referring to FIG. 1, an MTC user 110 who wants to use a user equipment (UE) 120 may access an M2M application 130. In FIG. 1, the terminal 120 is an MTC device. The M2M application 130 may communicate with the M2M application 122 of the terminal 120 at the level of the application program. The M2M application 130 may be operated by a service provider (SP).

The M2M application 130 may communicate with the terminal 120 through a network. In one example, the M2M application 130 may be directly connected to the network to communicate with the terminal 120 (Direct Model).

Alternatively, the M2M application 130 may be connected to the network through the MTC server 140 to communicate with the terminal 120 (Indirect Model). The MTC server 140 may be operated by a service provider or operated by a mobile network operator (MNO).

The wireless network operated by the mobile network operator includes a Radio Access Network (RAN) 150 and a Core Network (CN). In the example of FIG. 1, the core network is a home location register / home subscriber server (HLR / HSS) 162, a serving GPRS support node / mobility management entity (SGN / MME) 164, a cell broadcast center (CBC) 166. ), SMS-SC / IP-SM-GW (Short Message Service-Service Center / IP-Short Message-GateWay) 168, Machine Type Communication-InterWorking Function (MTC-IWF) 170, and GGSN / PGW / An ePDG (Gateway GPRS Support Node / Packet Data Network GateWay / enhanced Packet Data Gateway) 172 may be included.

In order for the terminal 120 to communicate with the MTC server 140 via the mobile network operator's wireless network, the MTC user 110 allows the terminal 120 to periodically communicate with the MTC server 140 via the network. Can be set.

Alternatively, in order to control and manage the terminal 120 and collect data on demand, the MTC user 110 may use the terminal 120 based on a request of the MTC server 140 at any time. It may trigger to communicate with the MTC server 140 via this wireless network. The network transmits the trigger request of the MTC server 140 to the terminal 120, and the terminal 120 receiving the trigger request initiates data communication through the network to communicate with the MTC server 140 is called MTC device triggering. Can be called

In order to facilitate device triggering of a plurality of MTC servers 140 in a wireless network of a mobile network operator accommodating a large terminal 120, an MTC server receiving a trigger request of the MTC server 140 and transmitting a trigger request ( Device triggering control functions such as MTC server authentication, trigger request authorization, charging, trigger delivery mechanism selection, and terminal identifier mapping. MTC-IWF 170 may be required to perform.

MTC-IWF 170 may be implemented as a separate entity or as part of other wireless network equipment. The MTC server 140 may transmit a trigger request to the MTC-IWF 170 by resolving an IP address of the MTC-IWF 170 that performs a device triggering control function for a specific terminal.

The MTC-IWF 170 may select a trigger delivery mechanism by a trigger request of the MTC server 140. Trigger delivery mechanisms include a method of using a short message service (SMS), a method of using a paging channel, a method of using a broadcast channel, and a method of using a cell broadcast service (CBS).

2 illustrates a method of device triggering using SMS. The method using SMS can be mainly used for a terminal attached to a network. 2, the MTC server 140 transmits a trigger request to the SMS-SC 168 (S201), and the SMS-SC 168 transmits a trigger request in the form of a short message to the terminal 120 ( S202). Upon receiving the trigger request, the terminal 120 starts data communication with the MTC server 140 (S203). The address of the MTC server 140 may be included in the short message.

3 illustrates a method of device triggering using a paging channel. The method using the paging channel can be used not only for the registered terminal but also for a terminal that is not registered and knows its location in the network. Referring to FIG. 3, the MTC server 140 transmits a trigger request to the HLR / HSS 162 (S301), and the HLR / HSS 162 currently sends the SGSN / MME 164 to service the terminal 120. Notify that there is a trigger request (S302). In this case, the notification of the trigger request may use the Insert Subscriber Data procedure used for user update of the SGSN / MME 164 between the HLR / HSS 162 and the SGSN / MME 164 (Insert Subscriber Data Request). SGSN / MME 164 notified of the trigger request responds to HLR / HSS 162 (Insert Subscriber Data Answer) (S303) and paging to terminal 120 (S304). The terminal 120 confirms that there is a trigger request from the SGSN / MME 164 in the network registration process and starts data communication with the MTC server 140 (S305). The address of the MTC server 140 may be preconfigured in the terminal 120 or included in the trigger request information.

4 illustrates a method of device triggering using a broadcast channel. The method using the broadcast channel can be used not only for registered terminals but also for terminals which are not registered and whose location is known in the network. Referring to FIG. 4, the MTC server 140 transmits a trigger request to a node of a core network (S401). The core network node may be the HLR / HSS 162, the CBC 166, and the GGSN / PGW / ePDG 172. The core network node is a node (cell or cell group) of the RAN 150 where the terminal 120 is located by using the identifier information of the terminal 120 to be triggered received from the MTC server 140. The update request is transmitted to broadcast the trigger request indication (S402). The identifier information of the terminal 120 to be triggered may be identifier information (eg, International Mobile Subscriber Identity (IMSI), etc.) of the individual terminal or identifier information of the terminal group. The location information of the terminal 120 to be triggered is preconfigured in the HLR / HSS 162 so that the core network node can know the location of the RAN.

The RAN node broadcasts a system information block (SIB) through a broadcast channel (S403). The system information block used for the trigger may be defined as a new system information block or may be used by changing an existing system information block (for example, SIB10, SIB11, and SIB12 for disaster alert broadcast). Upon receiving the trigger request through the broadcast channel, the terminal 120 initiates data communication with the MTC server 140 (S404).

In FIG. 4, the core network node may be a CBC 166 which is a server used when using the CBS, and the RAN node may be a base station, a Node-B, an evolved Node-B (eNodeB), a Radio Network Controller (RNC), and a BTS (Base). It may be a transmitting end that may be called a term such as a transceiver system, an access point, a base station controller (BSC), or the like.

5 illustrates a method of device triggering using SMS broadcast. The method using SMS broadcast can be used not only for registered terminals but also for terminals which are not registered and whose location is known in the network. Referring to FIG. 5, the MTC server 140 transmits a CBS (Cell Broadcast Service) message including a trigger request to the CBC 166 (S501). The trigger request information may include information on a specific geographic area for delivering the cell broadcast message, or identifier information of the terminal 120 to be triggered. The identifier information of the terminal to be triggered may be identifier information (eg, IMSI) of the individual terminal 120 or identifier information of the group. The CBC 166 transfers the new CBS message to the RNC / BTS through the Write / Replace message (S502). The RNC / BTS transfers the CBS message to the terminal 120 using the SMS BROADCAST COMMAND (S503). Thereafter, the RNC / BTS reports to the CBC 166 that the CBS message has been successfully broadcasted (S504). The CBC 166 reports that the CBS message has been successfully transmitted to the MTC server 140 (S505). Upon receiving the trigger request, the terminal 120 starts data communication with the MTC server 140 (S506).

One or more terminals belonging to the same subscriber may be referred to as an MTC group, and a method of performing device triggering on the MTC group may include the following methods.

As one method, there is a method in which the MTC server 140 repeatedly performs a device triggering procedure for each of the terminals 120 belonging to the MTC group. This method consumes a lot of network resources in the process of transmitting the trigger request from the MTC server 140 to the terminal 120 through the wireless network.

As another method, there is a method of using an MTC group identifier as a terminal identifier while performing device triggering using a broadcast channel.

These two methods may be effective when the terminals belonging to the MTC group are concentrated in a specific geographic area, but may be inefficient when the terminals belonging to the MTC group are scattered geographically.

On the other hand, the method using the broadcast channel or SMS broadcast is not a MTC terminal, but a general terminal and MTC terminal not belonging to a specific MTC group because the message through the broadcast channel or SMS broadcast is received by all user terminals in the cell In addition, trigger messages that are not needed may be received. The broadcast channel is shared by all terminals in the cell, which may increase the performance of the broadcast channel, causing performance degradation for other terminals.

FIG. 6 illustrates a group triggering control plane according to an embodiment of the present invention, and FIG. 7 illustrates a flowchart of the triggering method in FIG. 6. Each line in FIG. 6 represents a transmission path of a triggering message. For convenience of description, some entities shown in FIG. 1 are omitted.

6 and 7, the MTC server 140 transmits a group trigger request message to the MTC-IWF 170 (S701). The MTC-IWF 170 determines the trigger forwarding method based on the attribute included in the received group trigger request message (S702), and based on the determined method, the network entity (SMS-SC / IP-SM in the example of FIG. 5). GW 168, SGSN / MME 164, CBC 166, etc.) transmits a group trigger request message (S703). That is, in case of group triggering using SMS, MTC-IWF 170 transmits a trigger message to SMS-SC / IP-SM-GW 168, and in case of group triggering using paging, MTC- The IWF 170 sends a trigger message to the SGSN / MME 164, and when performing group triggering using broadcast, the MTC-IWF 170 sends a core network node (e.g., the CBC 166). You can pass trigger messages. The entity receiving the trigger request message from the MTC-IWF 170 transmits a trigger request message to each terminal 120 of the group (S704), and each terminal 120 receiving the trigger request message is the MTC server 140. Communication with the system is started (S705).

In step S601 in which the MTC server 140 requests a group trigger to the MTC-IWF 170, the MTC server 140 pre-configures the IP address of the MTC-IWF 170 to forward a request for a specific MTC group. The known or preconfigured domain name of the MTC-IWF 170 can be used to solve the problem. The group trigger request message transmitted by the MTC server 140 to the MTC-IWF 170 may include some or all of the information shown in Table 1 below.

[Table 1]

Parameters Parameter Description

Validity time A time information for storing a trigger request in the network when the trigger request is not delivered to the terminal.

MTC Group identifier Information used to identify a group consisting of terminals belonging to the same user. An external identifier of an individual group (eg, Mobile Subscriber Integrated Services Digital Network Number (MSISDN), Fully Qualified Domain Name (FQDN), NAI) (Network Access Identifier), SIP (Session Initiation Protocol) URI (Uniform Resource Identifier), IP address, etc.) can be used.

Group triggering indication Information that indicates that the trigger request is group triggering.

MTC Server Identifier The external identifier of the MTC device may be used as information for identifying an MTC server capable of requesting device triggering through a wireless network of a mobile service provider.

Application ID Information of an application to be operated in the MTC device user terminal by a trigger request of the MTC server.

Priority and urgency information that may be needed to determine whether to process in a priority overload (e.g. whether to handle device triggers in many cases relative to network capacity).

Trigger delivery method A method for transmitting a trigger request through a wireless network of a mobile carrier (e.g. triggering using SMS, method using CBS, etc.)

MTC group location information Fixed location information of MTC device user terminals belonging to the MTC group

List of individual terminal identifiers included in MTC group List of external identifiers (e.g. MSISDN, FQDN, NAI, etc.) of terminals included in MTC group

Application-specific information Specific information that can be used by the application of the MTC device that received the trigger request (eg application port number, URL, etc.)

FIG. 8 shows the detailed steps of step S702 of FIG. 7.

In step S702, the MTC-IWF 170 authenticates the MTC server 140 and authorizes whether the MTC server 140 has authority to the group trigger request (S801). For authentication to the MTC server 140, identifier information (e.g., MSISDN, FQDN, NAI, SIP URI, IP address, etc.) of the MTC server 140 that may request group triggering and / or individual triggering may be MTC. It may be preconfigured in the IWF 170. For authorization to the MTC server 140, information that can determine whether the MTC server 140 capable of group triggering for a specific MTC group is pre-configured in the MTC-IWF 170 or the HLR / HSS 162 Can be queried through. To this end, the HLR / HSS 162 may manage new group-specific information related to the MTC group. The group information includes group identifier information (for example, MSISDN, FQDN, NAI, SIP URI, IP address, etc.) set for each group, external identifiers of individual terminals included in the group (for example, MSISDN, FQDN, NAI, SIP). URI, IP address, etc.), an IMSI list of individual terminals included in the group, and identifier information of the MTC server capable of requesting a group trigger.

The MTC-IWF 170 determines whether the trigger request message is a duplicate message that is duplicated with a previously received trigger request message (S802). The group identifier information (or terminal identifier list) and / or MTC server identifier in the trigger request message are the same as the group identifier information (or terminal identifier list) and / or MTC server identifier included in the previously received trigger request signal, and the trigger If the request message is received within the valid time of the previously received trigger request signal, the MTC-IWF 170 determines that the trigger request message is a duplicate message. If it is determined that the trigger request message is a duplicate message, the MTC-IWF 170 may report this to the MTC server 140.

The MTC-IWF 170 may extract the IMSI list of the individual terminals 120 included in the group through the group identifier information, the terminal identifier list, the terminal IMSI list, and the like (S803). Such information may be included in a trigger request from the MTC server 140, preconfigured in the MTC-IWF 170, or viewed through the HLR / HSS 162. In addition, the group identifier information, the mapping information of the terminal identifier list and the terminal IMSI list may be pre-configured in the MTC-IWF 170 or may be inquired through the HLR / HSS 162.

The MTC-IWF 170 may inquire location information of the individual terminal 120 belonging to the group (S804). Location information of the individual terminal 120 may be pre-configured in the MTC-IWF 170, or may be inquired through the HLR / HSS 162 and SGSN / MME (164). To this end, the HLR / HSS 162 may manage attribute information indicating a fixed position of the individual terminal 120 belonging to the group, or location information of the individual terminal 120, and at the time when the terminal 120 is registered The terminal 120 may be confirmed through the SGSN / MME 164 serving.

The MTC-IWF 170 may inquire connection state (reachability) information of the individual terminal 120 belonging to the group (S805). The connection state information of the individual terminal 120 may be inquired through the HLR / HSS 162 using the IMSI information of the individual terminal 120.

The MTC-IWF 170 may inquire load information of the cell where the individual terminal 120 belonging to the group is located (S806). In one example, load information lookup of a cell may be performed via the CBC 166. The MTC-IWF 170 may transmit a message to the CBC 166 with a request for load information of a cell including a list of location information of individual terminals 120 belonging to the group. The CBC 166 may transmit load information to the MTC-IWF 170 by using a LOAD QUERY Request / Indication message, a LOAD QUERY Response / Confirm message, and the like defined in 3GPP TS25.419.

The MTC-IWF 170 may process information based on the location information and location information of the terminal 120 (for example, the number of terminals 120 belonging to a group in a specific cell), and connection state information of the terminal 120. Considering one or more of cell load information, a trigger forwarding method included in a trigger request message of the MTC server 140, a trigger forwarding method provided by a mobile operator through a wireless network, and an operation policy of another mobile carrier. The group triggering delivery method may be determined (S807).

For example, if the number of terminals 120 belonging to a group in a specific cell exceeds a predetermined number or ratio, a group triggering transmission method using a broadcast channel may be determined. Alternatively, if the terminal 120 exists in a low frequency in a large number of areas (cells), a group triggering delivery method using SMS or paging may be determined. Alternatively, when triggering the unregistered terminal 120, the group triggering delivery method using SMS may be excluded.

According to the operation policy of the mobile communication operator, the connection state inquiry of the individual terminal 120 or the load inquiry of the cell may not be performed or performed only in a specific situation such as a group trigger re-request by the MTC server 140 within a predetermined time. May be

The MTC-IWF 170 may inquire the information of the entity in the network to which the group trigger request is to be transmitted, based on the determined group trigger delivery method (S808). For example, SMS-SC 168 information for group trigger delivery through SMS, and SGSN / MME 164 information for serving an individual terminal 120 for group trigger delivery through paging, through broadcast For group trigger delivery, information of a core node such as CBC 166 is queried. The SMS-SC 168 information and the CBC 166 information may be preconfigured within the MTC-IWF 170. SGSN / MME 164 information may be queried through HLR / HSS 162.

The MTC-IWF 170 may transmit a trigger request message to the selected entity (S809). The trigger request message from the MTC-IWF 170 may include some or all of the information in Table 1. The information included in the trigger request message transmitted by the MTC server 140 to the MTC-IWF 170 may be different from the information included in the trigger request message transmitted by the MTC-IWF 170 to the selected entity. The information included in the trigger request message transmitted by the MTC-IWF 170 to the selected entity may vary depending on the selected entity.

After transmitting the trigger request message, the MTC-IWF 170 may generate charging data and transmit the charging data to the charging system of the mobile communication operator (S810). The charging data may include an identifier of the MTC server 140, an MTC group identifier, a list of identifiers of the individual terminals 120 included in the group, and the like.

The method described above with reference to FIG. 8 is merely an example and other order methods are possible. For example, the order of steps S802 to S806 may be changed.

9 illustrates a configuration of the MTC-IWF 170 according to an embodiment.

In order to execute the above-described process, referring to FIG. 9 illustrating the configuration of the MTC-IWF 170, the MTC-IWF 170 may include an MTC server interface module, an MTC server authentication module, a group trigger authority authorization module, and a group identifier. Mapping information extraction module, location inquiry module, connection status inquiry module of individual devices, cell load inquiry module, group trigger delivery method determination module, network object information inquiry module to be delivered, group trigger delivery interface, group triggering charging module, duplicate message determination module And the like.

According to each entity, the trigger request step S703 by the MTC-IWF 170 and the trigger request step S704 by each entity are described in detail below in FIG. 7.

When the MTC-IWF 170 determines the trigger delivery method using SMS, the MTC-IWF 170 transmits a trigger request message to the SMS-SC / IP-SM-GW 168. In this case, the trigger request message includes the identifier of the individual terminal 120 included in the group. When the terminal 120 can be identified through the MSISDN, the trigger request message may include an MSISDN list. If the terminal 120 cannot be identified through the MSISDN, the trigger request message may include an IMSI list.

When the SMS-SC / IP-SM-GW 168 receives the MSISDN list, the SMS-SC / IP-SM-GW 168 uses the MSISDN for each terminal 120 included in the MSISDN list. As with forwarding, request a trigger by sending a short message over the network. The called phone number included in the short message uses the MSISDN of the terminal 120.

When the SMS-SC / IP-SM-GW 168 receives the IMSI list, the SMS-SC / IP-SM-GW 168 sends a short message using the IMSI to each terminal 120 included in the IMSI list. Send a request for a trigger. The called phone number included in the short message uses an external identifier (eg, FQDN, NAI, SIP URI, IP address, etc.) of the terminal 120. To this end, the SMS-SC / IP-SM-GW 168 may query the HLR / HSS 162 for routing information (eg, SGSN / MME 164) using IMSI, and the HLR / HSS 162 may respond to the routing information inquiry request of the SMS-SC / IP-SM-GW 168.

When the MTC-IWF 170 determines a trigger delivery method using paging, the MTC-IWF 170 transmits a trigger request message to the HLR / HSS 162. The trigger request message may include a group identifier and / or an IMSI list of the terminal 120 included in the group. As described above in steps S302 to S305 of FIG. 3, the HLR / HSS 162 may request a trigger to the SGSN / MME 164, and the SGSN / MME 164 may page the terminal 120.

When the MTC-IWF 170 determines the trigger delivery method using broadcast, the MTC-IWF 170 transmits a trigger request message to a core network node (eg, CBC 166). The core network node updates the broadcast information to the RAN node, and the RAN node broadcasts a trigger request message to all terminals in the cell.

In such a case, the broadcast message may include a message identifier, a group identifier, and / or a terminal identifier (or terminal identifier) in order for another terminal (non-MTC terminal) to ignore the received broadcast message, which is not intended for triggering. List). The message identifier may indicate whether the broadcast message is a message for triggering the MTC device, and the general terminal may ignore the broadcast message if it is a message for triggering. The group identifier or the terminal identifier may indicate a terminal or a group of terminals to which a broadcast message is to be received, and the terminal may ignore this if the group identifier or the terminal identifier does not specify itself.

Alternatively, the broadcast message for the trigger may use another data coding method. The general terminal can ignore the case of the message that does not currently use the standardized data coding method. The broadcast message for the trigger of the MTC terminal may be data coded using, for example, coding group bits left in the CBS data coding scheme of 3GPP TS23.038, and data coded in this manner. The message is ignored by the generic terminal and can only be interpreted by the MTC terminal. The broadcast message interpreted by the MTC terminal may include a group identifier or a terminal identifier. Thus, if the group identifier or the terminal identifier does not specify itself, the MTC terminal may ignore it. The distinguishing information of the MTC terminal capable of receiving the broadcast message for MTC device triggering and the general terminal which cannot be received may be included in the attribute information of the device, and may be changed by the mobile operator.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art 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 protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims (16)

A server interface module for receiving a trigger request from an external server;
A trigger determination module for determining a trigger request delivery method for determining a trigger method based on at least one of information included in the trigger request and communication network information; And
And a trigger forwarding interface module to forward a trigger request to an entity determined based on the trigger request forwarding method. The method of claim 1,
The information included in the trigger request includes at least one of a valid time of the trigger request, trigger method information, identifier information of a terminal to receive the trigger request, identifier information of a group of the terminal, and identifier information of the external server. Trigger request forwarding server. The method of claim 1,
The communication network information includes at least one of the location information of the terminal, the connection state information of the terminal, load information of the cell to which the terminal belongs. The method of claim 1,
The trigger request delivery method includes at least one of a delivery method using a short message, a delivery method using paging, and a delivery method using a broadcast channel. An access server receiving a trigger request from an external server, determining a trigger request delivery method based on information included in the trigger request and communication network information, and forwarding the trigger request to an entity determined based on the trigger request delivery method; And
And a short message service entity configured to receive a trigger request from the access server and transmit a short message including the trigger request to a terminal. An access server receiving a trigger request from an external server, determining a trigger request delivery method based on information included in the trigger request and communication network information, and forwarding the trigger request to an entity determined based on the trigger request delivery method; And
And a paging entity configured to receive a trigger request from the access server and transmit a paging including the trigger request to a terminal. An access server receiving a trigger request from an external server, determining a trigger request delivery method based on information included in the trigger request and communication network information, and forwarding the trigger request to an entity determined based on the trigger request delivery method; And
And a broadcast entity that receives a trigger request from the access server and transmits a broadcast message including the trigger request to a terminal through a broadcast channel. The method of claim 7, wherein
And wherein the broadcast message comprising the trigger request is coded in a different manner than the broadcast message containing no trigger request. Receiving a trigger request from an external server;
Determining a trigger request delivery method for determining a trigger method based on at least one of information included in the trigger request and communication network information; And
And forwarding a trigger request to an entity determined based on the trigger request delivery method. The method of claim 9,
The information included in the trigger request includes at least one of a valid time of the trigger request, trigger method information, identifier information of a terminal to receive the trigger request, identifier information of a group of the terminal, and identifier information of the external server. How to forward trigger requests from the server. The method of claim 9,
The communication network information includes at least one of location information of a terminal, connection state information of the terminal, load information of a cell to which the terminal belongs. The method of claim 9,
The trigger request delivery method includes at least one of a delivery method using a short message, a delivery method using paging, and a delivery method using a broadcast channel. The access server receiving a trigger request from an external server;
Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information;
Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And
And a short message service entity receiving the trigger request from the access server, transmitting a short message including the trigger request to the terminal. The access server receiving a trigger request from an external server;
Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information;
Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And
And a paging entity receiving the trigger request from the access server, transmitting a paging including the trigger request to the terminal. The access server receiving a trigger request from an external server;
Determining, by the access server, a trigger request delivery method based on information included in the trigger request and communication network information;
Forwarding, by the access server, a trigger request to an entity determined based on the trigger request delivery method; And
And a broadcast entity receiving the trigger request from the access server, transmitting a broadcast message including the trigger request to the terminal through a broadcast channel. The method of claim 15,
And the broadcast message including the trigger request is coded differently from the broadcast message not including the trigger request.
KR1020110102614A 2011-10-07 2011-10-07 Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof KR20130038002A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020110102614A KR20130038002A (en) 2011-10-07 2011-10-07 Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof
PCT/KR2012/008099 WO2013051898A2 (en) 2011-10-07 2012-10-05 Trigger request transfer server, method for transferring a trigger request of a server, communication network and terminal trigger method in a communication network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020110102614A KR20130038002A (en) 2011-10-07 2011-10-07 Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof

Publications (1)

Publication Number Publication Date
KR20130038002A true KR20130038002A (en) 2013-04-17

Family

ID=48044318

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020110102614A KR20130038002A (en) 2011-10-07 2011-10-07 Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof

Country Status (2)

Country Link
KR (1) KR20130038002A (en)
WO (1) WO2013051898A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220134808A (en) 2021-03-25 2022-10-06 대봉엘에스 주식회사 Citron fermented extracts and uses thereof

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104540107A (en) * 2014-12-03 2015-04-22 东莞宇龙通信科技有限公司 Management method and management system for machine type communication (MTC) terminal cluster, and network side equipment
US9955453B2 (en) 2015-08-25 2018-04-24 Intel Corporation Evolved Node-B, user equipment, and methods for paging using a bitmap of paging indicators

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2505026A1 (en) * 2009-11-25 2012-10-03 InterDigital Patent Holdings, Inc. Machine type communication preregistration

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220134808A (en) 2021-03-25 2022-10-06 대봉엘에스 주식회사 Citron fermented extracts and uses thereof

Also Published As

Publication number Publication date
WO2013051898A2 (en) 2013-04-11
WO2013051898A3 (en) 2013-07-04

Similar Documents

Publication Publication Date Title
US20240147186A1 (en) Registration management method for terminal accessing 5g network on non-3gpp access
US20180332440A1 (en) Group messaging in a communication network
KR102462400B1 (en) Registration management method for terminal accessing 5g network on non-3gpp
EP2448297B1 (en) Information processing method and system, and mobility management network element
KR101540499B1 (en) Short Message Server, User Equipment Triggering Method Thereof, Trigger Request Delivering Server, and Trigger Request Delivering Method Thereof
EP2753106B1 (en) Method and system for sending a trigger message to a mtc ue, and mtc ue
EP2866477B1 (en) Communication method and system for machine-type communication user equipment
WO2011134394A1 (en) Method for triggering communication between group of machine type communication devices and machine type communication server, and machine type communication device thereof
KR20140004775A (en) Method and apparatus for mtc in a wireless communication system
CN102413453B (en) A kind of shared method and system of MTC device Subscriber Number
KR20140022712A (en) Interworking server, group based messaging method thereof, device, and warning message handling method thereof
US9204273B2 (en) Method and system for trigger information transmission and protocol conversion
EP2884779B1 (en) Message processing method in coexistence of multiple external identifiers of terminal and network side device
KR20130038002A (en) Trigger request delivering server, triggering request delivering method thereof, communication network, and user equipment triggering method thereof
WO2012152221A1 (en) Service communication method, device, and system
US9854382B2 (en) Method and unit for processing triggering information of MTC devices
WO2016050034A1 (en) Group addressing processing method, device, mtc intercommunicating gateway and api gw
KR20130049130A (en) Server and method for triggering of machine type communication device
KR20130142895A (en) An overload control method and apparatus for device triggering in mobile communication networks
CN116438816A (en) Method for initiating data transmission from user equipment
KR20180062728A (en) Method and apparatus for transmitting group messages based on nb-iot
KR20130139160A (en) An apparatus and method for delivering messages to a plurality of devices in mobile communication networks

Legal Events

Date Code Title Description
WITN Withdrawal due to no request for examination