KR20130139160A

KR20130139160A - An apparatus and method for delivering messages to a plurality of devices in mobile communication networks

Info

Publication number: KR20130139160A
Application number: KR1020130042067A
Authority: KR
Inventors: 홍성표; 정성한; 최우진
Original assignee: 주식회사 케이티
Priority date: 2012-06-12
Filing date: 2013-04-17
Publication date: 2013-12-20

Abstract

The present invention relates to a method for transmitting trigger messages for a plurality of MTC devices in a Plain Land Mobile Network (PLMN) and at an interface to a Service Capability Server (SCS).

Description

An Apparatus and Method for Delivering Messages to a Plurality of Devices in Mobile Communication Networks}

Machine type communication (MTC) is a form of data communication in which one or more entities do not necessarily require human interaction. MTC communication may need to communicate with multiple MTC terminals at the same time.

SUMMARY OF THE INVENTION The present invention devised to solve the above-mentioned problems efficiently provides device triggering for multiple MTC devices in a PLMN (Plann Mobile Network) and at an interface to a Service Capability Server (SCS). It is an object of the present invention to provide a triggering mechanism for processing.

An embodiment of the present invention provides a device for relaying a message from an external server in a mobile communication network, comprising: an external server communication unit for receiving a message transfer request including an identifier of a group consisting of the plurality of terminals from the external server; A subscriber management server communication unit for querying a subscriber management server with an identifier of each of the plurality of terminals by using the identifier of the group; And a message transmitter for performing a message transfer procedure to the plurality of terminals.

Another embodiment of the present invention provides a device for managing subscriber information in a mobile communication network, comprising: an information storage unit for storing identifiers of each of a plurality of terminals mapped to identifiers of a group consisting of a plurality of terminals; And a communication unit for transmitting an identifier of each of the plurality of terminals mapped to the identifier of the group to the other device when receiving the identifier of the group from another device of the mobile communication network. do.

Another embodiment of the present invention provides a method for delivering a message in an apparatus for relaying a message of a mobile communication network, the method comprising: receiving a message transfer request including an identifier of a group consisting of the plurality of terminals from an external server; Querying a subscriber management server with an identifier of each of the plurality of terminals by using the identifier of the group; And it provides a message delivery method comprising the step of performing a message delivery procedure to the plurality of terminals.

Another embodiment of the present invention is an information inquiry method executed in a device for managing subscriber information of a mobile communication network, wherein the device stores an identifier of each of a plurality of terminals mapped to an identifier of a group consisting of a plurality of terminals, The information inquiry method includes: receiving an identifier of the group from another device of the mobile communication network; And transmitting an identifier of each of the plurality of terminals mapped to the identifier of the group to the other device.

As described above, the present invention relates to a group of MTC devices belonging to the same MTC subscriber and sharing one or more MTC features, in order to enforce the maximum data rate that can be transmitted / received to the MTC group. Enforcing the maximum data rate for aggregated traffic to bearers has the effect of updating QoS parameters when they change. In addition, in the present invention, there is an effect that a group-based policy can be enforced for aggregate traffic for a GBR bearer or a non-GBR bearer per UE. In addition, by providing a group identifier format for identifying an MTC group, there is an effect of facilitating use of the MTC group identifier through an external interface.

1 is a structural diagram showing a 3GPP communication network for MTC communication.
2 is a flow chart illustrating a device triggering procedure via Tsp.
3 is a flowchart illustrating a device triggering procedure according to an embodiment of the present invention.
4 is a flowchart illustrating a T5 trigger delivery procedure according to an embodiment of the present invention.
5 is a flowchart illustrating a T4 trigger delivery procedure according to an embodiment of the present invention.
6 shows a configuration of the MTC-IWF according to an embodiment of the present invention.
7 illustrates a configuration of an HSS according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if 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.

The 3GPP architecture for MTC is shown in FIG.

End-to-end communication between an MTC application in a mobile communication terminal (UE) and an MTC application in an application server (AS) of an external network of a mobile communication network is performed by a 3GPP system and a service capability server (SCS) Server). In FIG. 1, a direct model represents a model in which an AS directly connects to an operator network without using an SCS to perform user plane communication with a UE.

The Indirect Model represents a model in which the AS indirectly connects to the operator's network through the services of the SCS to perform indirect user-plane communications with the UE or to use additional services such as device triggering.

Hybrid model represents the simultaneous use of direct and indirect models between AS and UE.

Configuration List

UE (User Equipment): a mobile communication terminal, the UE can host one or more MTC applications

- RAN (Radio Access Network): A radio access network

- MSC (Mobile Switching Center): Circuit switching based mobile switching center

- Serving GPRS Support Node (SGSN): A packet-based mobile switching center performing mobility management

- Gateway GPRS Support Node (GGSN): An entity providing interworking between the GPRS network and an external packet-switched network

- MME (Mobility Management Entity): An object on the control plane for supporting the mobility management function within the Evolved Packet System (EPS)

- S-GW (Serving Gateway): Gateway that terminates the interface to E-UTRAN

- P-GW (PDN Gateway): Gateway that terminates the interface to PDN

Service Capability Server (SCS): An entity that is connected to a 3GPP network to communicate with UEs used for MTC and is a Home Public Land Mobile Network (HPLMN) for device triggering. Connected with MTC-IWF or SMS-SC on. SCS can be used by one or more MTC applications.

- SMS-SC (Short Message Service-Service Center): An entity that performs a function of relaying, storing, and delivering a short message between objects (UE)

Home Subscriber Server (HSS): A master database of subscribers, an object containing subscription-related information needed to support session processing on network objects.

Machine Type Communication-InterWorking Function (MTC-IWF): Performs a function of relaying or translating a signaling protocol used to operate a specific function in a mobile communication network through a Tsp with an SCS server. Object

- Tsp: Reference point for control plane signaling between SCS and MTC IWF

-T4: reference point between SMS-SC and MTC IWF in home mobile communication network

- T5a: The reference point between the MTC-IWF and the serving SGSN.

- T5b: reference point between MTC-IWF and serving MME

- T5c: reference point between MTC-IWF and serving MSC

S6m: reference point between MTC-IWF and HSS / HLR

MTC devices (UEs used for MTC or M2M device or UE) periodically transmits and receives data with the MTC application server or SCS server through the mobile communication network. The MTC user may allow the MTC device to periodically initiate data communication through the mobile communication network to transmit data to the MTC application server or the SCS server. However, the MTC application server or SCS server communicates with the MTC application server or SCS server through the mobile network for controlling and managing the MTC device and collecting data on demand. You can also do that. As in the latter case, the SCS server transmits trigger information to the MTC device through the mobile communication network so that the MTC device triggers an application specific action. The application specific action described above includes the MTC device initiating communication with the SCS server as indirect model or the MTC device initiating communication with the application server as in mixed model. Device triggering is needed when the IP address for the MTC device is not available or not reachable by the SCS server / application server.

The device trigger message includes information for allowing the network to route the message to the appropriate MTC device and information for allowing the MTC device to route the message to the appropriate application. The information destined to the application, along with the information to route it, is referred to as the Trigger payload. The MTC device can distinguish a mobile terminated (MT) message carrying device triggering information from other types of messages.

In addition to the trigger payload described above, the SCS server may store an external identifier of the MTC device or a Mobile Station International ISDN Number (MSSI), an SCS identifier, a trigger reference number, a validity period, and priority information. Request a trigger by including it in a trigger message. The trigger reference number is used to co-relate the trigger request and the trigger response.

2 illustrates a device triggering procedure via Tsp. Device triggering is handled on a per MTC device basis. Hereinafter, a step in a triggering procedure having a feature processed in units of one MTC device will be described with reference to FIG. 2.

The SCS server queries the MTC-IWF address (for example, DNS) to send a trigger request to the DNS server. (Step 1)

The SCS server forwards the trigger request message to the MTC-IWF including the MTC device identifier for one MTC device to be triggered. (Step 2)

Receiving the trigger request message, the MTC-IWF checks whether the SCS is authorized to send a trigger request and whether the SCS has exceeded the quota or rate of trigger submission via Tsp. If this check fails, the MTC-IWF sends a Device Trigger Confirm message with a cause value indicating the cause of the failure condition (step 3).

Step 3 described above also provides a check function related to one MTC device.

The MTC-IWF uses the SCS to trigger the UE and to map an external identifier or MSISDN to IMSI and to extract relevant HSS stored routing information (including the serving core node identifier of the MTC device). Send a Subscriber Information Request message to the HSS (step 4).

The subscriber information request message of step 4 also includes an identifier of one MTC device.

The HSS sends a Subscriber Information Response message. If the SCS receives a cause value indicating that it is not allowed to send a trigger message to the UE, or that no valid subscription information was returned from the HSS, the MTC-IWF will display the cause value indicating the cause for the failure condition ( A device trigger confirm message is transmitted along with a cause value. (Step 5)

The subscriber information response message of step 5 also includes an identifier of one MTC device.

MTC-IWF selects a trigger delivery procedure based on information received from the HSS and local policy. If the T5 delivery procedure is selected, the MTC-IWF attempts the T5 trigger delivery procedure. (6a step)

If the T5 delivery procedure fails or is not supported by the serving node or UE, or if T4 delivery is selected in step 6a, the MTC-IWF attempts a T4 delivery procedure. (6b step)

Steps 6a and 6b above also process a request for one MTC device.

The MTC-IWF sends a Device Trigger Report message to the SCS server with a cause value indicating whether the trigger delivery succeeded or failed and the cause of the failure. The MTC-IWF generates the necessary charging information including the external identifier or the MSISDN and the SCS identifier. (Step 7)

Step 7 described above also processes a request for one MTC device.

As described above, device triggering through an SCS server in an existing mobile communication network handles a trigger request and a trigger response for each MTC device in an SCS server, an MTC-IWF, and network nodes in a mobile communication network, thereby allowing multiple devices belonging to the same subscriber. For MTC devices of MTC devices or a plurality of MTC devices having the same property, there is a problem that can cause a high network load due to device-by-device processing when attempting device triggering in the SCS. In addition, in device triggering for a large number of MTC devices in the SCS, there is a problem that can cause network congestion when the device triggering is concentrated at a certain time.

3 illustrates a device triggering procedure according to an embodiment of the present invention. A description with reference to FIG. 3 is as follows.

In order for the SCS to send a device trigger request message to the MTC-IWF as in step 1, the SCS may locally set the IP address (es) / port (s) of the MTC-IWF in advance.

Alternatively, the SCS may determine the IP address (es) / port (s) of the MTC-IWF by performing a DNS query using an external identifier of the MTC device to be triggered.

If the MTC group identifier is used in a trigger message sent for triggering on a plurality of MTC devices and the MTC group identifier uses an external identifier of the same format as the external identifier of the MTC device, the SCS may be triggered. The IP address (es) / port (s) of the MTC-IWF may be determined by performing a DNS query using an MTC group identifier for identifying devices.

If an external identifier list of MTC devices (eg external_id1, external_id2, ...) is used in a trigger message sent for triggering on multiple MTC devices, the SCS is external to one of the MTC devices to be triggered. The IP address (es) / port (s) of the MTC-IWF can be determined by performing a DNS query using the identifier.

Alternatively, the SCS may initiate an application layer connection with the MTC-IWF. That is, an application layer protocol session for message transmission between the SCS and the MTC-IWF may be initiated. The connection of the application layer between the SCS and the MTC-IWF may be provided through an SCTP (Stream Control Transmission Protocol) / IP or a transport layer protocol (TCP) / IP protocol (over SCTP / IP or TCP / IP). The SCS may perform authentication for the SCS to initiate the connection of the MTC-IWF and the application layer, during or during the initial connection initiation.

1) The SCS server sends a device trigger request message to the MTC-IWF. The device trigger request message includes MTC device identifier information (eg external identifier or MSISDN), SCS identifier (SCS Identifier) information, trigger reference number, validity period, and trigger payload.

And / or, in order to transmit a trigger request message for a plurality of MTC devices separately from a trigger request message for one MTC device, the trigger request message in the device trigger request message is a trigger request message for a plurality of MTC devices. It may include a message type information field for displaying. For example, a trigger request message for one MTC device and a trigger request message for a plurality of MTC devices may be distinguished by dividing the message type field value.

And / or a separate information field for indicating a trigger request for a plurality of MTC devices.

And / or for the trigger request for the plurality of MTC devices, the device trigger request message may include an information field for the number of MTC devices to trigger.

And / or, for a trigger request for a plurality of MTC devices, the device trigger request message may include an identifier (external identifier) of MTC devices in an information element field of an MTC device (or in an identifier information field of a plurality of MTC devices). Or it may include an identifier list (eg MSISDN1, MSISDN2, MSISDN3, ...) of the MTC devices that list the MSISDN.

And / or, the device trigger request message may include a list name (eg subscriber1_ID_listname) for the identifier (external identifier or MSISDN) of the MTC devices in the information element field of the MTC device for the trigger request for the plurality of MTC devices. It may include an identification number for identifying the list.

Identifier list (eg MSISDN1, MSISDN2, MSISDN3, ...) or identification number for identifying a list of a plurality of individual MTC devices mapped to the list name for the identifier of the MTC devices and the list name for the identifier of the MTC devices And identifier lists (eg MSISDN1, MSISDN2, MSISDN3, ...) of a plurality of individual MTC devices mapped to the identification numbers of the MTC devices are mutually agreed between the SCS server (or MTC user) and the MTC-IWF (or operator). a plurality of individual MTC devices, defined by a mutual agreement, stored in the MTC-IWF, or stored in the HSS, in which the MTC-IWF is mapped to a list name for the identifier of the MTC devices or an identification number for identifying the MTC devices. Can be interrogated to HSS. The inquired mapping information may be cached. Alternatively, when there is a list name of the identifier of the MTC devices or an identification number for identifying the list in the identifier information field of the MTC device, the MTC device lists the identifiers (external identifiers or MSISDN) of the MTC devices in the identifier information field of the plurality of MTC devices. May include a list of identifiers (eg MSISDN1, MSISDN2, MSISDN3, ...).

And / or the device trigger request message may include an MTC group identifier in the information element field of the MTC device for the trigger request for the plurality of MTC devices. The MTC Group Identifier is an identifier for a group of MTC devices belonging to the same Machine Type Communication subscriber and sharing one or more MTC features, and is an external identifier of one MTC device. It may have the same component as the identifier. That is, it may have a domain domain identifier under the control of the mobile network operator and a local identifier element managed by the mobile network operator. Alternatively, the MTC group identifier may use the existing IMSI format or change it. Alternatively, the MTC group identifier may have an MTC Group External Identifier having the same components as the External Identifier and an MTC Group IMSI having the same format as the IMSI.

The identifier list of the plurality of individual MTC devices mapped to the MTC group identifier and the MTC group identifier is stored in the MTC-IWF, or stored in the HSS, and the plurality of individual MTCs in which the MTC-IWF is mapped including the MTC group identifier information. The identifier list of devices can be interrogated to the HSS.

The mapping information between the MTC group external identifier and the MTC group IMSI may be stored in the MTC-IWF or may be stored in the HSS, so that the MTC group IMSI to which the MTC-IWF is mapped including the MTC group external identifier information is interrogated to the HSS. You can come.

And / or, the device trigger request message for the trigger request for the plurality of MTC devices may include specific geographic area information where the MTC devices belonging to the MTC group are located. The geographic area may be one cell sector, one cell, and a group of cells.

And / or said specific geographic area information is defined by a mutual agreement between the SCS server (or MTC user) and the MTC-IWF (or operator), stored in the MTC-IWF, or stored in the HSS The IWF may interrogate the HSS using the MTC group identifier or the list name for the identifier of the MTC devices or the identification number for identifying the MTC devices.

And / or the device trigger request message for a trigger request for one MTC device or for a plurality of MTC devices is scheduled time at which the message delivery should be first attempted May contain information.

Even when the device trigger request message is a trigger request for a plurality of MTC devices, a trigger reference number, validity period, priority information, and trigger page for processing a trigger request message for the plurality of MTC devices. Only one value can be set for each load. That is, in processing the individual MTC device triggering included in the trigger request message for the plurality of MTC devices, the trigger reference number, validity period, priority information, trigger page included in the trigger request message The load value can be used in common. When the schedule time information is used in the trigger request message, the schedule time information value may also be commonly used to process.

Alternatively, when the device trigger request message is a trigger request for a plurality of MTC devices, trigger reference number, validity period priority information for processing a trigger request message for the plurality of MTC devices. The trigger payload can be set differently. That is, the selected MTC device triggering included in the trigger request message for the plurality of MTC devices may have different trigger reference numbers, validity periods, priority information, and trigger payload values. As an optional information element, a trigger reference number, validity period, priority information, and trigger payload for processing a trigger request message may be set for each identifier (external identifier or MSISDN) of the MTC device. If the schedule time information is used in the trigger request message, the schedule time information value can also be set separately.

Alternatively, if the device trigger request message is a trigger request for a plurality of MTC devices, the trigger reference number, validity period, priority for processing the trigger request message for the plurality of MTC devices. One or more of the information and the trigger payload may be set differently. That is, the individual MTC device triggering included in the trigger request message for the plurality of MTC devices may have one or more different trigger reference numbers, validity periods, priority information, and trigger payload values. Trigger reference number and / or validity period and / or priority information and / or trigger page for processing a trigger request message for each MTC device identifier (external identifier or MSISDN) as optional information element. You can set the load. When the schedule time information is used in the trigger request message, the schedule time information value may be set to have a separate schedule time at a predetermined time interval after the initial time information or by using a randomized value within a predetermined range.

2) The MTC-IWF receiving the trigger request message checks whether the SCS is authorized to send a trigger request and whether the SCS has exceeded the quota or rate of trigger submission through the Tsp. If this check fails, the MTC-IWF sends a device trigger confirm message with a cause value indicating the cause for the failure condition and the flow ends at this step.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF may check whether the SCS is authorized to send a trigger request for the plurality of MTC devices.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF checks whether the SCS has exceeded the quota or rate of trigger submission via the Tsp, for the plurality of MTC devices. Consider the number of individual MTC devices included in the trigger request message. In other words, consider the number of individual device triggering processes in the network. For example, the number of identifiers of the MTC devices included in the identifier list of the MTC devices included in the trigger request message or the list name or the identification number for identifying the list of the identifiers of the MTC devices stored or cached in the MTC-IWF. Consider the number of identifiers of MTC devices included.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF checks whether the SCS has exceeded the quota or rate of trigger submission via the Tsp, for the plurality of MTC devices. One or more of other information included in the trigger request message (eg priority, validity period, triggering method / mechanism) may be considered.

If this check fails, the MTC-IWF sends a Device Trigger Confirm with a cause value indicating the cause for the failure condition and the flow ends at this step.

3) MTC-IWF extracts whether the SCS is authorized to trigger the UE, and maps an external identifier or MSISDN to IMSI, and extracts relevant HSS storage routing information (including the serving core node identifier of the MTC device). In order to do so, a subscriber information request message is sent to the HSS.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF determines whether the SCS is authorized to trigger the MTC device on an individual MTC device basis, and / or an external identifier. Or send a Subscriber Information Request message to the HSS to map the MSISDN to IMSI and to extract the associated HSS stored routing information (including the serving core node identifier of the MTC device).

To this end, if an identifier list of MTC devices listing the identifiers of the MTC devices is included in the information element field of the MTC device (or in the identifier information field of the plurality of MTC devices), the MTC-IWF is included in the identifier list. A subscription information request (external identifier of the MTC device or MSISDN and SCS identifier) message may be transmitted to the HSS for all identifiers of the MTC devices. And / or, if the MTC device identifier includes an MTC group identifier in the information element field of the MTC device or a list name for the identifier of the MTC devices or an identification number for identifying the list, the MTC-IWF Request subscription information for the MTC group identifier or the list name for the identifier of the MTC devices or the identifiers of all MTC devices mapped to the identification number for identifying the list (external identifier or MSISDN of the MTC device and the SCS identifier) ) May send the message to the HSS.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF determines whether the SCS is authorized to trigger the MTC devices for all of the plurality of MTC devices by the trigger request message; Subscribers to multiple MTC devices in the HSS to map external identifiers or MSISDNs to IMSIs and / or to extract relevant HSS storage routing information (including serving core node identifiers of the MTC device). A Subscriber Information Request message may be sent to the HSS. To this end, the subscriber information request message is added to the subscriber information request message for the plurality of MTC devices so that the subscriber information request message for the plurality of MTC devices can be transmitted separately from the subscriber information request message for one MTC device. It may include a message type information field for indicating that the information is a request message. For example, the subscriber information request message for one MTC device and the subscriber information request message for a plurality of MTC devices may be distinguished by dividing the message type field value.

And / or a separate information field for indicating that the subscriber information is requested for a plurality of MTC devices.

And / or, a subscriber name request for a plurality of MTC devices by including a list name for the identifier of the MTC devices or an identification number for identifying the list or an MTC group identifier (or MTC group external identifier) in the subscriber information request message. I can display it.

And / or for the subscriber information request for a plurality of MTC devices, the subscriber information request message may include an information field for the number of MTC devices having the same reference number.

And / or for the subscriber information request for a plurality of MTC devices, the subscriber information request message is a list of identifiers of MTC devices that list the identifier (external identifier or MSISDN) of the MTC devices in the information element field of the MTC device ( eg MSISDN1, MSISDN2, MSISDN3, ...).

And / or, if the MTC group external identifier is included in the information element field of the MTC device, the MTC-IWF may request a subscription information request to map the MTC group external identifier to the MTC group IMSI. MTC group external identifier and SCS identifier) message can be sent to the HSS.

4) The HSS sends a Subscriber Information Response message. If the SCS receives a cause value indicating that it is not allowed to send a trigger message to the MTC device or that no valid subscription information was returned from the HSS, then the MTC-IWF displays the cause value indicating the cause for the failure condition. Send a Device Trigger Confirm message together with the (cause value).

And / or, when the device trigger request message is a trigger request for a plurality of MTC devices, indicate that the MTC-IWF is a subscriber information request message for a plurality of MTC devices by dividing the subscriber information request message type, and / or If the subscriber information request message indicates a subscriber information request for a plurality of MTC devices by including a list name for the identifier of the MTC devices or an identification number for identifying the list or an MTC group identifier, the HSS indicates a subscriber information response message. Type to indicate that it is a subscriber information response message for a plurality of MTC devices, and / or in the subscriber information response message, a list name for the MTC group identifier or an identifier of the MTC devices or an identification number for identifying the list. All MTC mapped IMSIs of the vice and is able to respond, including the routing information (related "Routing Information" including the serving nodes identities), including / or MSISDNs, and associated serving node identifiers.

And / or, a separate information field for indicating that the subscriber information response to the plurality of MTC devices is included.

Alternatively, without including the IMSIs and / or MSISDNs information of all MTC devices mapped to the MTC group identifier or list name for the identifier of the MTC devices or an identification number for identifying the list in the subscriber response message. Respond only including routing information (related "Routing Information" including the serving nodes identities) of all MTC devices mapped to a list name for an identifier of the MTC devices or an identification number for identifying the list. Can be.

And / or when the MTC group external identifier is included in the information element field of the MTC device of the subscriber information request message, the HSS determines the subscriber information response (MTC group IMSI and associated serving nodes identifiers). Routing information) may be sent to the HSS.

If the MTC device is mapped to an MTC group identifier or a list name for the identifier of the MTC devices or an identification number for identifying the list, the SCS is not allowed to send a trigger message or the valid subscription information is HSS. If not returned, the number of such MTC devices and a list of identifier information of the MTC device is returned in the subscriber response message, and the SCS is not allowed to send a trigger message to the MTC device or valid subscription information is available from the HSS. Can be included with a cause value indicating that it was not returned.

5,6) The MTC-IWF selects a trigger delivery procedure based on information received from the HSS and local policy.

If the T5 delivery procedure is selected, the MTC-IWF attempts the T5 trigger delivery procedure.

If the T5 delivery procedure fails or is not supported by the serving node or UE, or if T4 delivery is selected in step 5, the MTC-IWF attempts the T4 delivery procedure.

And / or Initiating trigger delivery for a plurality of MTC devices, the MTC-IWF may be one of an operator's policy, selected trigger mechanism, information received from the SCS (eg schedule time information), information received from the HSS, and the like. The trigger schedule time of the MTC devices can be set using the above information.

The T5 delivery procedure and the T4 delivery procedure may use the procedure described with reference to FIG. 2. Alternatively, the T5 delivery procedure and the T4 delivery procedure may use a procedure according to the present invention described with reference to FIGS. 4 and 5.

7) The MTC-IWF sends a Device Trigger Report message to the SCS server with the cause value indicating the success or failure of the trigger delivery and the cause of the failure. The trigger delivery report message contains the external identifier or MSISDN and the trigger reference number. The MTC-IWF generates the necessary charging information including the external identifier or the MSISDN and the SCS identifier.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, indicate that the SCS is a device trigger request message for a plurality of MTC devices by dividing the device trigger request message type, and / or device If the MTC-IWF indicates a device trigger request for a plurality of MTC devices by including a list name for the identifier of the MTC devices or an identification number for identifying the list or an MTC group identifier in the trigger request message, the MTC-IWF displays a device trigger report message. Type to indicate that it is a device trigger report message for a plurality of MTC devices, and / or a list name or list of MTC group identifiers or identifiers of MTC devices in the device trigger report message. It can respond to include the identification number for the stars. And / or may include a separate information field for indicating that the device trigger report for the plurality of MTC devices.

And / or, if the device trigger request message is a trigger request for a plurality of MTC devices, the MTC-IWF indicates in the device trigger report message the number of MTC devices for which the trigger delivery failed, the identifier information list of the MTC device, and the failure. May contain a cause value for.

8) In response to the received device trigger, the MTC devices take some action taking into account the contents of the trigger payload. This response typically includes immediate communication with the SCS or application server or the initiation of a later communication.

4 illustrates a T5 trigger delivery flow according to an embodiment of the present invention. A description with reference to FIG. 4 is as follows.

1) MTC-IWF is an appropriate serving core node capable of T5 triggering using the capabilities of the MTC device extracted from the HSS and the capabilities of the serving CN node (s). , MME / SGSN). The MTC-IWF sends a Submit Request message to the serving core node. Submission request messages include IMSI, SCS identifier, message priority, MTC-IWF ID, reference number, single delivery attempt flag, validity time, request type / It may include one or more information of a trigger application (request type / trigger application), an application protocol data unit (PDU).

And / or, a message type information field for indicating that the message is a submission request message for a plurality of MTC devices.

And / or may include a separate information field for indicating that the submission request for the plurality of MTC devices.

And / or, the MTC-IWF may include number information of a plurality of MTC devices having the same reference number in the submission request message to the serving core node.

And / or the MTC-IWF may include an IMSI list of a plurality of MTC devices having the same reference number in the submission request message to the serving core node.

And / or the MTC-IWF is a serving cell node for a MTC group identifier and / or a group of cells in which a MTC device may be located in a Submit Request message. May contain information.

And / or the MTC-IWF is a serving cell node for a cell or a group of cells in which MTC group IMSI and / or MTC devices may be located in a Submit Request message. May contain information.

2) The serving core node transmits a Non Access Stratum (NAS) message to the MTC device including information of one or more of a request type / trigger application, an application PDU, an MTC-IWF ID, and a reference number. The serving core node generates the required charging (CDR) information. The UE provides the trigger content and the trigger type to the corresponding application.

The UE may respond with information including one or more of the Delivery Status (Cause), MTC-IWF ID, Reference Number, Response Type / Trigger Application, Application PDU.

And / or, if the MTC-IWF includes the IMSI list of a plurality of MTC devices having the same reference number in the submit request message to the serving core node, the serving CN node is included in the IMSI list for each MTC device. For, send a Non Access Stratum (NAS) message to the MTC device including information of one or more of the request type / trigger application, application PDU, MTC-IWF ID, reference number.

And / or, the MTC-IWF may be a cell or a group of cells in which an MTC group identifier or MTC group IMSI and / or MTC devices may be located in a Submit Request message to a serving core node. In the case of including the cell list information on the MTC group identifier or the MTC group IMSI and / or the cell list information on a cell or a group of cells in which the MTC devices may be located. To MTC devices. The paging message may include one or more information of a request type / trigger application, an application PDU, an MTC-IWF ID, and a reference number. The paging message may include the MTC group identifier or the MTC group IMSI.

MTC devices assigned an MTC group identifier or an MTC group IMSI will be delivered when the MTC group identifier or MTC group IMSI included in the paging message matches the MTC group identifier assigned to the MTC device or the MTC group IMSI (cause), MTC-IWF The response may include one or more of an ID, a reference number, a response type / trigger application, and an application PDU.

3) The serving core node sends a delivery report to the MTC-IWF. The delivery report message may include an IMSI, a cause value indicating the cause of the failure if the trigger message was successfully delivered or failed, a reference number, response type / trigger application, or application PDU. have.

And / or a message type information field for indicating that the delivery report message is for a plurality of MTC devices.

And / or may include a separate information field for indicating that the delivery report for a plurality of MTC devices.

And / or include number information of a plurality of MTC devices having the same reference number in the submit request message to the serving core node and / or a plurality of MTC devices having the same reference number in the submit request message to the serving core node. If including the IMSI list of the serving CN node, the serving CN node includes number information of the plurality of MTC devices having the same reference number in the delivery report message, and / or IMSI of the plurality of MTC devices having the same reference number. Respond with a specific cause.

And / or, when including a MTC group identifier or an MTC group IMSI in a Submit Request message to a serving core node, the serving CN node may have a number of MTC devices having the same reference number in the delivery report message. It may respond by including information and / or cause-specific cause-specific cause of IMSI of a plurality of MTC devices having the same reference number. Alternatively, only MTC devices having a paging response among the plurality of MTC devices having the same reference number may respond with the cause value for each IMSI.

5 illustrates a T4 trigger delivery flow in accordance with the present invention. A description with reference to FIG. 5 is as follows.

1) MTC-IWF selects the appropriate SMS-SC based on the configured information. The MTC-IWF sends a Submit Trigger message to the SMS-SC. The submission trigger message includes the identifier information (external identifier or MSISDN) of the MTC device, IMSI, SCS identifier, trigger reference number, validity period, priority, serving node ID (s), SMS application port ID, trigger payload. It includes. The SMS-SC avoids additional HSS interrogation (SRI for SM) and receives the necessary parameters in the submission trigger message from the MTC-IWF. The SMS Application port ID is set to address the triggering function in the UE.

And / or indicate in the submission trigger message that the submission trigger message is for a plurality of MTC devices to transmit the submission trigger message for a plurality of MTC devices separately from the submission trigger message for one MTC device. It may include a message type information field. For example, a submission trigger message for one MTC device and a submission trigger message for a plurality of MTC devices may be distinguished by dividing the message type field value.

And / or, may include a separate information field for indicating that it is a submission trigger for a plurality of MTC devices.

And / or, the submission trigger message for the plurality of MTC devices may include an information field for the number of MTC devices having the same reference number.

And / or, the submission trigger message for the plurality of MTC devices may include an identifier list of MTC devices that list identifiers (external identifiers or MSISDNs) of the MTC devices in the identifier information field of the MTC device (or in the identifier information field of the plurality of MTC devices). (eg MSISDN1, MSISDN2, MSISDN3, ...).

2) The SMS-SC sends a Submit Trigger Confirm message to the MTC-IWF to confirm that the SMS submission has been accepted by the SMS-SC.

And / or, if the MTC-IWF indicates the submission trigger message for the plurality of MTC devices by dividing the submission trigger message type, the SMS-SC distinguishes the submission trigger confirmation message type and the submission trigger confirmation message for the plurality of MTC devices. And / or include a separate information field to indicate that it is a submission trigger confirmation message for multiple MTC devices, and / or the number of MTC devices with the same reference number in the submission trigger confirmation message ( responds with an information field for number) and / or a trigger reference number.

3) The MTC-IWF sends a Device Trigger Confirm message to the SCS to confirm that the device trigger request has been accepted for delivery to the UE.

And / or, the MTC-IWF identifies a device trigger confirmation message for a plurality of MTC devices by dividing a device trigger confirmation message type for a plurality of MTC devices, and / or device trigger confirmation for a plurality of MTC devices. Include a separate information field to indicate that it is a message, and / or include an information field for the number of MTC devices with the same reference number in the device trigger confirmation message, and / or a trigger reference number can do.

4,5,6) A short message is delivered from the SMS-SC to the UE via a serving core node (eg, MME.SGSN), and a delivery report is reported to the SMS-SC.

7) The SMS-SC generates necessary CDR information. CDR information includes the SCS identifier. The CDN contains the SMS application port. The CDR information may include MTC group identifier information.

8) The SMS-SC sends a Message Delivery Report to the MTC-IWF. The message delivery report contains the reason code, trigger reference number, and SCS identifier.

And / or, when received and indicating that the submission trigger message is a submission trigger message for a plurality of MTC devices, the message delivery report may include a message type information field for distinguishing a message delivery report message for the plurality of devices. Can be. For example, the message delivery report message for one MTC device and the message delivery report for a plurality of MTC devices may be distinguished by dividing the message type field value.

And / or, a separate information field for indicating that the message is a delivery report for a plurality of MTC devices.

And / or, the device submit trigger message for the plurality of MTC devices may include the number of MTC devices having the same reference number or the number of MTC devices having failed to submit the delivery trigger, the external identifier or the MTC device having the same reference number. It may include an information field for the failure reason code for each MSISDN.

As described above, the present invention provides device triggering for a plurality of MTC devices through an SCS server, and includes a plurality of MTCs in a Plain Land Mobile Network (PLMN) and an interface to a Service Capability Server (SCS). By enabling processing for multiple MTC devices, network resources can be efficiently utilized in providing device triggering via SCS for multiple MTC devices belonging to the same subscriber or multiple MTC devices with the same attributes. It has the effect of making it available.

Although the present invention described above triggers a plurality of MTC terminals, the present invention is not limited thereto and may be used to transmit a message to a plurality of other terminals as well as the MTC terminal.

6 shows a configuration of the MTC-IWF according to an embodiment of the present invention.

Referring to FIG. 6, the MTC-IWF 600 includes an external server communication unit 610 communicating with an SCS, an authority determining unit 620, a subscriber management server communication unit 630 communicating with an HSS, and a message transmitting unit 640. do.

The external server communication unit 610 receives a triggering request message from the SCS. The triggering request message received from the SCS may include identifier information of a group consisting of a plurality of terminals. The identifier of the group may be in the form of an external identifier.

The triggering request message may also include schedule time information for which message delivery will be attempted for the first time. The message delivery procedure in the MTC-IWF may be performed at a randomly selected time after the schedule time.

The triggering request message may also include information such as priority, expiration date, message delivery method (eg, T5 procedure or T4 procedure).

The authority determining unit 620 determines whether the SCS that transmitted the triggering request message is authorized to transmit the triggering request message. The authority determining unit 620 may determine whether the authority is based on the information included in the triggering request message.

The management server communication unit 630 inquires an identifier of each terminal included in the group to the HSS by using the identifier of the group. The management server communication unit 630 may transmit an external identifier of the group to the HSS, and receive an identifier (eg, IMSI) of terminals mapped to the external identifier of the group from the HSS.

The message transmitter 640 performs a triggering procedure. In the case of T4 triggering, the message transmitter 640 may transfer the triggering message to the SMS-SC. In the case of T5 triggering, the message transmitter 640 may transfer the triggering message to the MME / SGSN.

7 illustrates a configuration of an HSS according to an embodiment of the present invention.

Referring to FIG. 7, the HSS 700 includes an information storage unit 710 and a communication unit 720.

The information storage unit 710 stores identifiers of terminals mapped to identifiers of groups. The identifier of the group may be an external identifier, and the identifier of the terminals may be an International Mobile Subscriber Identity (IMSI).

The communication unit 720 receives an inquiry request from another server, and transmits an inquiry result to another server. In the case of triggering on a group of MTC devices, the communication unit 720 receives an identifier of the group from the MTC-IWF. When the identifiers of the terminals mapped to the identifiers of the groups are inquired according to the information stored in the information storage unit 710, the communication unit 720 transmits the identifiers of the terminals to the MTC-IWF.

In the above-described example, the MTC-IWF is described as querying a terminal mapped to a group in the HSS. However, another server may query the terminal mapped to the group in the HSS.

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

Claims

A device for relaying messages from an external server in a mobile communication network,
An external server communication unit configured to receive a message transfer request including an identifier of a group consisting of the plurality of terminals from the external server;
A subscriber management server communication unit for querying a subscriber management server with an identifier of each of the plurality of terminals by using the identifier of the group; And
Apparatus comprising a message transmitter for performing a message transfer procedure to the plurality of terminals.

The method according to claim 1,
And the identifier of the group is an external identifier, and the identifier of each of the plurality of terminals is an international mobile subscriber identity (IMSI).

The method according to claim 1,
The message delivery request further includes schedule time information for the first time message delivery, and the message delivery procedure for each of the plurality of terminals is performed at a randomly selected time after the time according to the schedule time information. Device.

The method according to claim 1,
And an authority judging unit for judging whether the external server is authorized to send a message transfer request.

5. The method of claim 4,
The message delivery request includes at least one information of priority, validity period, and message delivery method, and the authority determining unit has the authority to send the message delivery request based on the information included in the message delivery request. And determining whether there is.

A device for managing subscriber information in a mobile communication network,
An information storage unit for storing identifiers of each of a plurality of terminals mapped to identifiers of a group consisting of a plurality of terminals; And
And a communication unit for transmitting an identifier of each of the plurality of terminals mapped to the identifier of the group to the other device when receiving the identifier of the group from another device of the mobile communication network.

The method of claim 6,
And the identifier of the group is an external identifier, and the identifier of each of the plurality of terminals is an international mobile subscriber identity (IMSI).

A method for delivering a message in a device relaying a message in a mobile communication network,
Receiving a message transfer request including an identifier of a group consisting of the plurality of terminals from an external server;
Querying a subscriber management server with an identifier of each of the plurality of terminals by using the identifier of the group; And
Message delivery method comprising the step of performing a message delivery procedure to the plurality of terminals.

The method of claim 8,
The identifier of the group is an external identifier, and the identifier of each of the plurality of terminals is IMSI (International Mobile Subscriber Identity).

The method of claim 8,
The message delivery request further includes schedule time information for the first time message delivery, and the message delivery procedure for each of the plurality of terminals is performed at a randomly selected time after the time according to the schedule time information. Message delivery method.

The method of claim 8,
Determining whether the external server is authorized to send a message delivery request.

12. The method of claim 11,
The message delivery request includes information of at least one of priority, expiration date, and message delivery method, and the authority determination step includes the authority for the external server to transmit a message delivery request based on the information included in the message delivery request. Determining whether there is a message delivery method.

An information inquiry method executed in a device for managing subscriber information of a mobile communication network,
The apparatus stores the identifier of each of the plurality of terminals mapped to the identifier of the group consisting of a plurality of terminals,
The information inquiry method,
Receiving an identifier of the group from another device in the mobile communication network; And
And transmitting an identifier of each of the plurality of terminals mapped to the identifier of the group to the other device.

The method of claim 13,
And the identifier of the group is an external identifier, and the identifier of each of the plurality of terminals is an International Mobile Subscriber Identity (IMSI).