KR20140022712A - Interworking server, group based messaging method thereof, device, and warning message handling method thereof - Google Patents

Abstract

The present invention relates to a method for transmitting a message to a group of MTC devices, a plurality of MTC devices, a group of terminals, or a plurality of terminals by using a warning message delivery procedure in an evolved packet system that is a long term evolution plain land mobile network.

Description

Interworking Server, Group Based Messaging Method Thereof, Device, and Warning Message Handling Method Thereof}

The present invention utilizes a warning message delivery procedure in a Long Term Evolution (LTE) mobile communication network to a group of or a group of MTC devices or a group of MTC devices or A method for transmitting a message to a plurality of terminals.

Machine type communication (MTC) or machine to machine communication (M2M) refers to a form of data communication associated with one or more entities for which human intervention is not necessary. Services optimized for IoT communication may have different characteristics from those optimized for human-to-human communication.

The service operator can manage a plurality of devices of the same type in one group for convenience in the nature of the MTC device. Grouping and managing MTC devices in an MTC group has several advantages in device control, management, and billing, and can reduce signal overload compared to individual terminal control. In particular, when there are many MTC devices, network resources can be saved.

An object of the present invention is to provide a method for efficiently delivering group-based messaging to a large group of devices in a mobile network in providing a group-based messaging service using an alert message delivery in a mobile communication network. .

Another object of the present invention is to provide a method for effectively identifying and processing a group message in a terminal.

It is another object of the present invention to provide a method for controlling an overload that may occur in providing group-based messaging service for a large group of devices by using alert message delivery in EPS.

An embodiment of the present invention includes the steps of receiving a device trigger request message for a group of devices from a service capability server (SCS); And transmitting a broadcast request message based on the device trigger request message to a CBC (Cell Broadcasting Center) for distributing a warning message to a core network entity in a public warning system (PWS) structure. Group-based messaging of a relay server comprising at least one of a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a number of broadcast requests, a time range during which a specific action should be performed on the device, and a priority Provide a method.

Another embodiment of the present invention includes the steps of receiving a device trigger request message for a group of devices from a service capability server (SCS); And generating an alert message based on the device trigger request message and transmitting the generated alert message to a core network entity, wherein the device trigger request message includes a group identifier, a geographic area, a radio access technology (RAT), a repetition period, and the number of broadcast requests. It provides a group-based messaging method of a relay server, characterized in that it comprises at least one of a time range, priority to be performed a specific action in the device.

Another embodiment of the present invention provides a method for processing an alert message of a device, the method comprising: receiving an alert message from a communication network; Determining whether the warning message is a group message to be received by the device based on a message identifier or a group identifier included in the warning message; And when the warning message is a group message to be received by the device, performing a specific action.

Another embodiment of the present invention, an SCS communication unit for receiving a device trigger request message for a group of devices from a service capability server (SCS); And a PWS communication unit configured to transmit a broadcast request message based on the device trigger request message to a CBC (Cell Broadcasting Center) for distributing a warning message to a core network entity in a public warning system (PWS) structure. Provides a relay server comprising at least one of a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a broadcast request number, a time range in which a specific action should be performed in a device, and a priority. .

Another embodiment of the present invention, an SCS communication unit for receiving a device trigger request message for a group of devices from a service capability server (SCS); And a core network entity communication unit configured to generate an alert message based on the device trigger request message and transmit the generated alert message to a core network entity, wherein the device trigger request message includes a group identifier, a geographic area, a radio access technology (RAT), a repetition period, and a broadcast. And at least one of a cast request number, a time range in which a specific action should be performed in the device, and a priority.

Another embodiment of the invention, the receiving unit for receiving a warning message from the communication network; And determining whether the warning message is a group message to be received by the device based on a message identifier or a group identifier included in the warning message, and performing a specific action when the warning message is a group message to be received by the device. It provides a device comprising a control unit.

As described above, in providing a group-based messaging service using an alert message delivery in an EPS, a group-based message is used by using an external group identifier and a message identifier to enable group-based messaging for a large group of devices in a mobile communication network. There is an effect that can be processed, and effectively identify the message belonging to the group in the terminal to send to the target application. In addition, the present invention has the effect of controlling the overload that may occur in providing group-based messaging service for a large group of devices by using the alert message delivery in EPS.

1 shows a structure of a 3GPP communication network for MTC communication.
2 shows the CBS structure of UMTS.
3 shows the PWS structure of EPS.
4 shows an alert message delivery procedure in an E-UTRAN.
5 illustrates a group based triggering procedure using a warning message in EPS according to an embodiment of the present invention.
6 and 7 show the configuration of a network for one embodiment of the present invention.
8 illustrates a group based triggering procedure through a direct interface between the MTC-IWF and the MME according to an embodiment of the present invention.
9 is a block diagram showing the configuration of an MTC-IWF according to an embodiment of the present invention.
10 is a block diagram showing the configuration of an MTC-IWF according to another embodiment of the present invention.
11 is a block diagram showing the configuration of a device 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.

Machine type communication (MTC) is a form of data communication, in which one or more entities do not necessarily require human interaction.

The 3GPP structure for the MTC is shown in FIG.

End-to-end communication between MTC applications in a mobile communication terminal (UE) and MTC applications in an application server (AS) in an external network of a mobile communication network is performed by a 3GPP system. Service is provided by SCS: Service Capability 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.

Indirect Model refers to a model in which the AS connects indirectly with an operator's network through a service of an SCS in order to use an additional service such as device triggering.

The Hybrid Model shows the use of direct and indirect models between AS and UE simultaneously.

The configuration list of FIG. 1 is as follows.

UE (User Equipment): A mobile communication terminal, a device, and a 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 that provides interworking between a General Packet Radio Service (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)

Serving Gateway (S-GW): Gateway that terminates the interface with E-UTRAN (Evolved Universal Terrestrial Radio Access Network)

-P-GW (PDN Gateway): Gateway that terminates the interface with PDN (Packet Data Network)

- SCS (Service Capability Server): a mobile communication terminal used for MTC (UEs used for MTC) and 3GPP (3 ^rd Generation Partnership Project) as an object to be connected to the network, the home mobile communication network to the device triggering (HPLMN to communicate : Connected with MTC-IWF or SMS-SC of Home Public land mobile network. SCS can be used by one or more MTC applications.

Short Message Service-Service Center (SMS-SC): An entity that performs a function of relaying, storing, and forwarding a short message between an entity that transmits and receives a short message (for example, a UE).

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

MTC-IWF (InterWorking Function): An entity that relays or translates a signaling protocol used to operate a specific function in a mobile communication network through a Tsp with an SCS server.

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: reference point between MTC-IWF and 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

An MTC device (UEs used for MTC or M2M device or MTC terminal) periodically transmits and receives data with an MTC application server or an SCS server through a mobile communication network. The MTC user may allow the MTC device to periodically initiate data communication via the mobile communication network to transmit data to the MTC application server or the SCS server. However, for controlling and managing the MTC device, collecting data on demand, the MTC application server or the SCS server may allow the MTC device to communicate with the MTC application server or the SCS server through a mobile communication network. . 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 may include an MTC device initiating communication with an SCS server, such as an indirect model, or an MTC device initiating communication with an application server, such as a mixed model.

Device triggering standardized in 3GPP currently only specifies how to trigger devices for individual MTC devices. Although triggering for a group of devices (or a plurality of devices) is not standardized, a method of using a cell broadcast service (CBS) is known. By allowing an unknowledged generic CBS message to be broadcast to all recipients in a particular region, the CBS can deliver a specific message for a group of devices located in a particular geographical area. CBS is standardized in 2G (GSM, Global System for Mobile) and 3G (UMTS, Universal Mobile Telecommunication System) networks. In 2G / 3G network, core network cell broadcast message management entity is directly linked with entity of access network.

2 shows a CBS structure of a 3G (UMTS) network.

In FIG. 2, a CBC (Cell Broadcast Center) is an node in a core network that manages CBS messages, such as a cell set to which CBS messages are broadcast, and a CBE (Cell Broadcast Entity) is an entity involved in CBS message formatting. Indicates.

On the other hand, the 4G LTE network (EPS, Evolved Packet System) has been standardized for PWS (Public Warning System) using a message structure related to CBS. PWS allows the network to distribute warning messages such as earthquakes and tsunamis on behalf of public authorities. As shown in FIG. 3, the PWS structure is linked to an access network entity through an MME in which a cell broadcast management entity (CBC) is a core network entity. In addition, the alert message delivery in the EPS system is different from cell broadcast in 2G / 3G networks, such as broadcasting an alert message through system information (SIB) in the access network.

In the E-UTRAN, an Earthquake and Tsunami Warning System (ETWS) capable UE and a Commercial Mobile Alert System (CMAS) capable UE may use an alert message delivery procedure. 4 is a diagram illustrating the warning message delivery procedure, which will be briefly described with reference to FIG. 4.

0) Network registration and security procedures are performed. The UE stores a flag indicating whether it has an authenticated network.

1) The CBE (for example, an information source such as a regulator) sends emergency information to the CBC, including warning messages and affected area information. The CBC authenticates this request.

2) Using the affected area information, the CBC identifies which MME needs to be contacted and determines the information to be place into the Warning Area Information Element. CBC sends a Write-Replace alert request message to the MME.

3) The MME sends a Write-Replace Warning Confirm message indicating to the CBC that the MME has begun distributing warning messages to the eNodeB.

4) Upon receiving the Write-Replace Warning Confirm message, the CBC may confirm to the CBE that it has begun distributing the warning message to the CBE.

5) The MME forwards the Write-Replace Warning Message request to the eNodeB.

6) The eNodeB uses the alert region information to determine the cell (s) to which the message will be broadcast and broadcast the message.

7) If the UE has been configured to receive warning messages, and the UE has authenticated the core network of the eNodeB it is camped on), the UE can alert the user to 'earthquake', 'tsunami' or 'earthquake and tsunami'. The UE may activate the reception of the broadcast message including the alert message. The UE may display the content of the alert message to the user.

8) From the Write-Replace Warning Response Message returned by the eNodeB, the MME can determine the success or failure of the delivery and generate a trace record (e.g., number of times a particular message has been broadcasted in a given warning area). have.

In order to provide group-based messaging service using cell broadcast in such EPS system, PWS-based alert message delivery procedure had to be used. PWS-based alert message delivery is designed to alert you to an emergency, such as an earthquake or tsunami, and lacks the scalability to provide group-based triggering for large MTC devices. In addition, a specific method for efficiently identifying and processing a group entity and a network entity performing group messaging in a mobile communication network for group messaging has not been provided. In addition, a method of identifying and dispatching group messaging in a terminal and dispatching to a specific application through a triggering function is not provided, which makes it difficult to efficiently process group messages in a terminal or a network. In addition, MTC device triggering may cause an application-specific action such as initiating communication with an SCS server or an application server, causing an excessive signaling load on the network or worsening congestion.

5 illustrates a group based triggering procedure using a warning message in EPS according to an embodiment of the present invention. Hereinafter, an embodiment of the present invention will be described in detail with reference to FIG. 5.

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

If the external group identifier included in the device identifier information element included in the trigger message transmitted for triggering on a group of MTC devices has the same format as the external identifier of the MTC device (<Local Identifier> @ <Domain If Identifier>) or an identifier including a Domain Identifier as a component included in an external identifier as a component, the SCS uses the device identifier (eg, an external group identifier). By performing a DNS query, the IP address (es) / port (s) of the MTC-IWF can be determined.

1) The SCS server sends a device trigger request message (or group trigger request message) for a trigger request for a group of devices to the MTC-IWF. The device trigger request message may include one or more information elements of an external group identifier information, an SCS identifier information, a trigger reference number, a validity period, priority, and a trigger payload. elements) may be included. The trigger reference number can be used to correlate a trigger request and a trigger response and / or to cancel a trigger request that has already been submitted and / or to update a trigger request that has already been submitted. The trigger payload indicates information for determining a destination to the application together with information for routing to the application in the device UE. (The information destined to the application, along with the information to route it, is referred to as the Trigger payload.). The priority handles the trigger preferentially under network congestion or overload within the mobile communication network, and / or handles the trigger at a higher priority than low priority messages in the CBC or MTC-IWF, MME, and / or eNodeB. Information to be used to enable and / or allow the terminal to do NAS signaling without including a low priority, and / or to allow the terminal to be processed with a high priority. The validity period represents a period of time for maintaining the trigger request in the network, such as repeating message delivery in delivering the trigger request to the device.

The outer group identifier represents an identifier for a group of devices belonging to the same subscriber and sharing one or more features, or for a group of devices sharing one or more features regardless of the subscriber.

 The external group identifier may have the same component as an external identifier of the MTC device. That is, it may have a domain identifier under the control of the mobile network operator and a local identifier managed by the mobile network operator (eg, <Local Identifier> @ <Domain Identifier>). Operators can use different domain identifiers to provide access to other services. In order to identify that a specific trigger is a group trigger, an external group identifier may distinguish a domain identifier for a group triggering service from a domain identifier for an individual device triggering service. The local identifier can be used to obtain an internal group identifier if necessary.

Alternatively, the external group identifier can be used to modify the external identifier of the MTC device to identify that a particular trigger is a group trigger. That is, the domain identifier may have a portion for identifying the group trigger, or the local identifier may have a portion for identifying the group trigger. For example, <Local Identifier> @ <Domain Identifier part for Group + part for MNO> (for example, if the local identifier is 123456789, place the part to identify the group at the domain address that identifies the MNO 123456789@group.mno .com) or in the form <Local Identifier part for Group + part for MNO> @ <Domain Identifier> (for example, if the local identifier is 123456789, place the part to identify the group at the domain address that identifies the MNO .123456789 @ mno.com).

Alternatively, the outer group identifier may use a specific number band of MSISDN to identify that a particular trigger is a group trigger. The MSISDN consists of a country code (CC), a national destination code (NDC), and a subscriber number (SN) where a mobile station is registered. If MSISDN is used as the external group identifier, some of the components of the existing MSISDN (eg CC, NDC, SN, etc.) can be designated to use a specific number band as a group identifier or to use a private number plan. Alternatively, an indication to indicate that a group identifier can be used besides MSISDN can be used.

 The group trigger request message may optionally include specific geographical area or location / area and / or Radio Access Technology (RAT) information where MTC devices belonging to the MTC group are located. The geographic area information may be one cell sector, one cell, a group of cells, or the entire PLMN.

 The specific geographic area information or location / area may be allocated by mutual agreement between the MTC user or the SCS server operator and the mobile operator and stored in the HSS. The HSS identifies a serving node (MME) to which a message is to be delivered using the geographic area or location / area information or an external group identifier and the geographic area or location / area information, and a cell ID (eg, E-UTRAN Cell Global Identity, E-UTRAN Cell Identity) or cell ID list and / or TAI (Tracking Area Identity) list may be determined.

Alternatively, the specific geographic area information or location / area information may be allocated by mutual agreement between the MTC user or the SCS server operator and the mobile operator and stored in the MTC-IWF. The MTC-IWF identifies a serving node (MME) to which a message is to be delivered and transmits the message using the geographical area or location / area information, or an external group identifier and the geographical area or location / area information. The ID list and / or the TAI list may be determined. Alternatively, the specific geographic area information or location is allocated to a mutual agreement between the MTC user or the SCS server operator and the mobile operator and stored in the HSS, and the MTC-IWF is interrogated using an external group identifier. You can come.

Alternatively, the specific geographic area information or location / area may be allocated and stored in the CBC by a mutual agreement between the MTC user or the SCS server operator and the mobile operator. The CBC identifies a serving node (MME) to which a message is to be delivered using the geographical area or location / area information or an external group identifier and the geographical area or location / area information, and a cell ID or cell ID list to which the message is to be delivered; And / or determine the TAI list.

The group trigger request message may include the application layer content of the group message. The application layer content may be included in the trigger payload or separately included in a message.

Alternatively, the group trigger request message may include application port information in addition to the above. The application port information may be included in the trigger payload, included in the application layer content, or separately included in a message. The application port information may be set to address a target application by a triggering function in the UE. Alternatively, the application port information may be set to address a target application in the UE.

Alternatively, the group trigger request message may include one or more information of a message identifier, a repetition period, and a number of broadcasts request in addition to the included information. The message identifier identifies the source / type of the broadcast message to be used for the group trigger, the Repetition Period indicates the repetition period of the message to be broadcast, in seconds, and the Number of Broadcasts Requested message. Indicates the number of times to be broadcast. The message identifier may use the existing message identifier format or may extend the existing message identifier format. The message identifier may be set to address a triggering function in the UE and may be reserved for a group trigger message. Alternatively, the message identifier may be used only by the device to be triggered to identify the message without addressing the triggering function in the UE. The message identifier may be included in a trigger payload or application layer or separately in a message.

Alternatively, the group trigger request message by the SCS does not include one or more pieces of information of the message identifier, repetition period, and the number of broadcast requests. As determined by the IWF, the message may be included in the broadcast request message from the MTC-IWF to the CBC.

In another method, the group trigger request message by the SCS does not include one or more pieces of information of the message identifier, repetition period, and broadcast request number information, and the CBC is configured to transmit one or more pieces of information of the message identifier, repetition period, and broadcast request number. May determine and include the message in a Write-Replace alert request message to the MME.

Alternatively, the group trigger request message may include a scheduled time / time range (eg, scheduled time at which the message delivery should be first attempted or the message delivery should be last attempted) in addition to the inclusion information, and And / or to determine the preferred device triggering method, and / or the preferred UE behavior (eg, PDN connection, detach, specific action) and / or the time at which the UE prohibits the execution of the particular action before performing the specific action. Device-specific backoff timer or prohibition / control parameter (eg, barring parameter), and / or a schedule time / time range in which a specific action should be performed in the device. Before performing the specific action, the device-specific backoff timer or the prohibition / control parameter may be performed by the device distributing the specific action within a schedule time / time range in which the specific action should be performed in the device. Indicates information to make it available.

The preferred UE behavior, a device-specific backoff timer or prohibition / control parameter before performing a specific action, or a schedule time / time range in which a specific action should be performed in a device is included in the trigger payload or It may be included in the application layer content or may be included in a message separately.

Alternatively, in addition to the above, the group trigger request message may use message type information to distinguish the group trigger request message from the individual device trigger request message. For example, a trigger request message and a group trigger request message for one MTC device may be distinguished by dividing the message type field value.

2) The MTC-IWF receiving the group trigger request message may check whether the SCS is authorized to send a group trigger request message. To this end, the MTC-IWF shall store the SCS identifier information or the external group identifier and SCS identifier information authorized to send the group trigger request message or the SCS identifier information or the external group identifier authorized to store the group trigger request message to the HSS. Store SCS identifier information and check whether the HSS is authorized to send a group trigger request including SCS identifier information or external group identifier information and SCS identifier information, or query SCS identifier information or external group identifier information and SCS identifier information ( interrogation) to store / cache information retrieved via HSS.

Alternatively, the MTC-IWF receiving the group trigger request message, in addition to the authority check to send the group trigger request message, checks whether there is a right to send the information including one or more of the information included in the group trigger request message. You can check. For example, when the MTC-IWF receives a geographic area, a location / area, a RAT, a schedule time / time range, and the like through a group trigger request message, the MTC-IWF may check whether there is a right to send the received information. For this purpose, the information may be stored in the HSS as subscription information and stored / cached.

Alternatively, the MTC-IWF may check whether the SCS has exceeded the quota or rate of group trigger submission via Tsp. To this end, the MTC-IWF may store quota or rate reference values for external group trigger submissions in accordance with operator policies. Alternatively, the MTC-IWF may store a quota or rate reference value of group trigger submission for each SCS identifier authorized to send a group trigger request message or for each external group identifier for each SCS identifier. Or store the quota or rate reference value of the group trigger submission by the SCS identifier authorized to send the group trigger request message to the HSS or by the external group identifier by the SCS identifier, and the SCS identifier information or the external group identifier information and the SCS identifier information in the HSS. Interrogation of quota or rate reference value of group trigger submission by SCS identifier or external group identifier by SCS identifier authorized to send group trigger request, including Can be cached

Alternatively, in addition to the above, the MTC-IWF checks whether the SCS has exceeded the quota or rate of trigger submission through the Tsp, and the number of individual MTC devices or group trigger request messages to be processed through the group trigger request message. The number of cells to be cast may be considered. To this end, the information included in the group trigger request message in step 1 optionally includes the number of individual devices to be triggered via the external group identifier or the number of cells to be broadcast, or the number of individual devices to be triggered via the group identifier via the HSS, or You can query the number of cells to be broadcast.

Alternatively, in addition to the above, the MTC-IWF checks whether the SCS has exceeded the quota or rate of trigger submission through the Tsp, and includes other information included in the group trigger request message (e.g., priority, expiration date, triggering method). Information) may be considered.

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. Otherwise the flow continues to step 3.

3) The MTC-IWF determines whether the SCS is authorized to trigger a group of devices mapped to an external group identifier, and / or the SCS adds an external group identifier in addition to the above. Routing information (serving core node identifiers of MTC devices) for mapping to and / or for interrogation of message identifiers mapped to external group identifiers in addition to the above, and / or in addition to the above. And / or if the group trigger request message includes one or more of geographic area, location / area, RAT, schedule time / time range SCS in addition to the above, To check whether you have permission (for example, the geographic area or location / area included in a group trigger request message or To determine if the RAT is authorized to trigger), and / or in addition to the above, if the geographic area or location / area information is included in the group trigger request message; A Subscriber Information Request message is sent to the HSS to map to the list. The subscriber information request message may include external group identifier and SCS identifier information.

Or, in addition to the above, if the group trigger request message includes a geographic area or location / area and / or RAT information, the subscriber information request message optionally includes a geographic area or location / area and / or RAT information in addition to the information. can do.

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 group devices or that no valid subscription information was returned from the HSS, the MTC-IWF indicates the cause for the failure condition. A Device Trigger Confirm message is transmitted along with a value.

The HSS may include an internal group identifier, a message identifier, a related "Routing Information" including the serving node identities, a cell ID, or a cell mapped to an external group identifier in a subscriber response message. It may respond with a list of IDs and / or a list of TAIs.

When the external group identifier is used as a group identifier even inside the 3GPP system without distinguishing between the internal group identifier and the external group identifier, or a part of the components of the external group identifier (for example, the local identifier) as the group identifier within the 3GPP system. If used, the mapping process for the external group identifier and the internal group identifier through the HSS may not be performed. Alternatively, the external group identifier may be responded to the mapping request through the external group identifier as the internal group identifier.

The internal identifier used for group message delivery over broadcast is in the same format as an existing IMSI not exceeding 15 digits, or a specific identifier of some component of an IMSI component (eg MCC, MNC, MSIN). It can be assigned and used for the purpose of distinguishing. Alternatively, the internal identifier used for group message delivery through broadcast may use message identifiers for the cell broadcast service and the alert message service. Alternatively, the internal identifier used for group message delivery through broadcast may use the local identifier of the external identifier. Alternatively, the internal identifier used for group message delivery through broadcast can be defined and used.

The routing information including the serving node identifier may be serving node identifier information including one or more cell information in which a group message is to be broadcast. Alternatively, the routing information including the serving node identifier may be identifier information of serving nodes serving all individual devices belonging to an external group identifier. Alternatively, the routing information including the serving node identifier may be transmitted by the subscription information or by the operator's policy among the serving nodes serving all the individual devices belonging to the outer group identifier. It may be identifier information of serving nodes including identifier information or cell information thereof. As another method, the cell information may be information interrogated by the serving nodes in the HSS. To this end, the HSS can inquire cell information by using an internal identifier (IMSI) of an individual device mapped to an external group identifier, an internal group identifier, or an external group identifier as serving nodes. The message between the HSS and the serving node (MME) may be used by using an Insert Subscriber Data Request / Response message or by defining a new message.

Alternatively, in addition to the above, the HSS may respond by including one or more cell information in which the group message is to be broadcast in the subscriber information response message. The cell information is a cell or a group of cells mapped to geographic area information or location / area information known to the MTC user or SCS server operator by a mutual agreement between the MTC user or SCS server operator and the mobile operator. A cell ID (eg, E-UTRAN Cell Global Identity) or a cell ID list or a TAI list of a group of cells. Alternatively, the cell information indicates a cell ID or a cell ID list or a TAI list of one cell or a group of cells allowed for an external group identifier. Alternatively, the cell information may indicate a cell ID or a cell ID list or a tracking area identity (TAI) list of one cell or a group of cells in which all individual devices belonging to an external group identifier are located. The HSS may retrieve cell information using an internal identifier (IMSI) of an individual device mapped to an external group identifier or an internal group identifier or an external group identifier as serving nodes. The message between the HSS and the serving node (MME) may be used by using an Insert Subscriber Data Request / Response message or by defining a new message. The HSS may respond with one or more cell information to broadcast a group message in the subscriber information response message only if it includes geographic area information or location / area information in the subscriber information request message. Alternatively, the HSS may respond by including one or more cell information to broadcast a group message in the subscriber information response message, regardless of including geographic area information or location / area information in the subscriber information request message.

Alternatively, in addition to the above, the HSS may be included in a cell in which the broadcast message is not allowed by the group message in the subscriber response message (eg, when roaming or being directly extracted to the serving node or retrieved through the serving node). Information may be matched to a cell for which broadcast is not allowed), and the like may include the identifier information of the individual device.

Before or after deciding how to trigger the device via the broadcast in step 5, if the HSS responds with only the serving node identifier without cell information in the subscriber response message or if the HSS does not have cell information with the subscriber response message. When responding only to an internal identifier (IMSI) of an individual device mapped to an identifier and an internal group identifier or an external group identifier, or when responding without cell information and a serving node identifier through an HSS subscriber response message, the MTC-IWF is external to the serving nodes. Cell information may be inquired using an internal identifier (IMSI) of an individual device mapped to a group identifier or an internal group identifier or an external group identifier. Alternatively, MTC-IWF provides geographic area or location / area information and / or external group identifier or internal group in a broadcast request message (e.g., Submit Broadcast Request) to CBC without mapping or querying cell information. Identify a serving node (MME) including the identifier and to which the CBC will forward messages using the geographic area or location / area information or using an external group identifier or internal group identifier and the geographic area or location / area information; The cell ID or cell ID list and / or TAI list to which the message is to be delivered may be determined.

5) The MTC-IWF selects a trigger delivery procedure based on information received from the HSS and an operator's policy.

Or, if the MTC-IWF does not receive the cell information to be broadcasted by the group message, prior to selecting the trigger delivery procedure, the MTC-IWF transmits all of the individual devices belonging to the external group identifier through the identifiers of the serving nodes received from the HSS. A cell ID or a cell ID list or a tracking area identity (TAI) list of one cell or a group of cells where individual devices are located may be interrogate from the serving nodes.

Alternatively, if the MTC-IWF does not receive the cell information to be broadcasted by the group message, after selecting the trigger delivery procedure, the MTC-IWF uses the identifiers of the serving nodes received from the HSS to identify individual devices belonging to the external group identifier. A cell ID or a cell ID list or a tracking area identity (TAI) list of one cell or a group of cells in which all individual devices are located may be interrogate from the serving nodes.

Alternatively, if the MTC-IWF does not receive the cell information to be broadcast in the group message, the MTC-IWF does not look up the cell information and is external to the broadcast request message (eg, Submit Broadcast Request) to the CBC. A serving node identifier and related information (eg, an external group identifier or an internal group identifier or an IMSI list or a message identifier of an individual device for each serving node identifier) serving a group identifier may be transmitted.

If possible, the MTC-IWF may select a triggering method through the CBC in consideration of the number of individual devices belonging to a specific cell or a group of cells and / or the trigger frequency. In selecting the triggering method through the CBC, the MTC-IWF may consider information of one or more of information (RAT, priority, preferred device triggering method, geographic area, or location / area) included in the trigger request message. When selecting a triggering method through the CBC, the MTC-IWF may take into account one or more information of RAT, network load, number of cells to trigger, and number of devices per cell to trigger when possible.

Certain congestion situations (eg, NAS level Mobility Management Congestion Control in TS 23.401 4.3.7.4.2) are maintained to prevent network congestion from worsening as a group of devices responds to a trigger contained in a group message. You can prevent the UE from being triggered while it is running. The MME is optional to indicate the suppression parameters, including the suppression factor, the suppression period, and / or the suppression subcategory (eg, priority, etc.) to reflect the trigger load that the MME intends to reduce. Appropriate messages with information elements may be delivered to the MTC-IWF via the T5 interface between the MME and the MTC-IWF. At this time, the MME may include information for requesting to suppress a message to be broadcast in the message.

Alternatively, the MME may contain suppression parameters that include suppression factors, duration of suppression, and / or suppression subcategories (eg, priority, etc.) to reflect the trigger load that the MME is trying to reduce. Appropriate messages with optional information elements may be delivered to the CBC via the Sbc interface between the MME and the CBC. At this time, the MME may include information for requesting to suppress a message to be broadcast in the message. The CBC can forward this to the MTC-IWF.

6) The MTC-IWF sends a broadcast request message (eg, Submit Broadcast Request) to the CBC via the interface with the CBC. The broadcast request message may include one or more information of a warning type, an impacted area, a time period, and a warning message.

The alert type information may be set to address a triggering function in the UE, and a specific value may be reserved for a group trigger message. Alternatively, the warning type information may be assigned to a value different from an existing disaster type (for example, earthquake, tsunami, etc.) for the group trigger message. Alternatively, the warning type information may be set to 'test' so that terminals not using the group trigger message may discard the group message (silently discard). Alternatively, the warning type information may be assigned by using a specific value so that terminals not using the group trigger message may discard the group message (silently discard).

The impacted area may be a geographic area or location / area information transmitted from the SCS. Alternatively, the affected area may be cell information including serving node information mapped by MTC-IWF. Alternatively, the impacted area may be cell information including serving node information retrieved from the HSS by the MTC-IWF.

The time period information may be a value such as a validity period included in a trigger request message between the SCS and the MTC-IWF or a schedule time / time range in which message delivery should be attempted. Alternatively, the time period information may be another value independent of a validity period and / or a schedule time / time range included in a trigger request message between the SCS and the MTC-IWF, or may be another value that is related.

The alert message may include application layer content information included in a trigger request message between the SCS and the MTC-IWF. Alternatively, the warning message may include trigger payload information included in a trigger request message between the SCS and the MTC-IWF. Alternatively, the warning message may include preferred UE behavior (eg, PDN connection, detach, specific action execution) information. Or, in addition to the above, the warning message may include backoff timer information or prohibition / control parameters to prevent overload and / or a schedule time / time range in which a specific action should be performed on the device. Can be.

Alternatively, when the broadcast request message is available from the HSS in addition to the inclusion information, the IMSI list of the individual device for each serving node ID, the external group identifier or the internal group identifier, the message identifier, the SCS identifier, the trigger reference number, the priority, Schedule time / time ranges, repetition periods, and broadcast requests for specific actions to be performed on application ports, backoff timers to prevent overload, or inhibit / control parameters or devices It may include one or more of the number (Number of Broadcasts Requested).

The trigger reference number may be different from the reference number included in the trigger request message between the SCS and the MTC-IWF. In this case, the MTC-IWF may manage mapping information between the reference number included in the trigger request message transmitted by the SCS and the trigger reference number on the broadcast request message transmitted by the MTC-IWF. Alternatively, the trigger reference number may be the same as the reference number included in the trigger request message between the SCS and the MTC-IWF.

When the broadcast request message is received from the MTC-IWF, the CBC may not authenticate the broadcast request message. That is, when the broadcast request message is received from the MTC-IWF, the CBC can process the next step without authenticating the broadcast request message. Alternatively, even if the broadcast request message is received from the MTC-IWF, the CBC may perform authentication on the request.

7) Using “impacted area” information, the CBC can determine one or more MMEs to which alert messages will be broadcast.

CBC sends a Write-Replace alert request message to the MME. The write-replace warning request message may include one or more information of a message identifier, a serial number, a tracking area ID list, a warning area, an OMC ID, and a concurrent warning message indicator.

The message identifier is a value conveyed via SCS, or a value mapped to an external group identifier and / or an SCS identifier in HSS and transmitted through MTC-IWF, or an external group identifier and / or an SCS identifier in MTC-IWF. A value that is mapped and passed, or a value that is mapped and set by an external group identifier and / or an SCS identifier in the CBC without being passed through the MTC-IWF, or set to address a triggering function in the UE. It may be a value.

The serial number is a value for identifying a specific message from a source and a type indicated by a message identifier, and is changed every time a message having a given message identifier changes. The CBC may store / manage message identifiers and / or mapping information between a serial number and the trigger reference number.

The traffic area ID list is information used only in the MME, and the MME can use it to select an eNodeB to forward a Write-Replace alert request message.

The alert area indicates a cell ID list and / or a tracking area identity (TAI) list. The eNodeB consists of a TAI and a cell ID, so as to check the matching of the contents of the alert area to identify the cell to which to distribute the alert message. The warning area is an optional information element. If there is no warning area, it is interpreted as all cells in the eNodeB. If the CBC receives the serving node identifier and the cell information, the traffic area ID list may be included in the serving node identifier and the cell information in the warning area.

If an OMC ID exists, it indicates its destination if the success / failure of message delivery is recorded in a trace record after step 13. By including the MTC-IWF identifier or address information in the OMC ID, the success or failure of the delivery in reporting the delivery of Step 14 and / or Step 15 and / or Step 16 can be communicated to the MTC-IWF. Concurrent Warning Message indicator indicates whether the mobile network supports simultaneous warning message broadcast.

Alternatively, the write-replace warning request message may be added to the include information in addition to the external group identifier or internal group identifier, message identifier, trigger reference number, priority, trigger payload, application layer content, application port, and message delivery. Schedule time / time range (e.g. scheduled time at which the message delivery should be first attempted or the message delivery should be last attempted), preferred device triggering method, preferred UE behavior (e.g. PDN connection, detach , Specific action), backoff timer to prevent overload, or the schedule time / time range, repetition period, and broadcast when specific action is to be performed in the prohibition / control parameter or device. One of the Number of Broadcasts Requested, and the warning type May include information on the award.

The alert type information may be set to address a triggering function in the UE, and a specific value may be reserved for a group trigger message. Alternatively, the warning type information may be assigned to a value different from an existing disaster type (for example, earthquake, tsunami, etc.) for the group trigger message. Alternatively, the warning type information may be set to 'test' so that terminals not using the group trigger message may discard the group message (silently discard). Alternatively, the warning type information may be assigned by using a specific value so that terminals not using the group trigger message may discard the group message (silently discard).

To prevent network congestion from worsening as a group of devices respond to triggers contained within a group message, ensure that the UE is not triggered while certain congestion situations (eg, NAS level Mobility Management Congestion Control) are maintained. There is a need. The MME is optional to indicate the suppression parameters, including the suppression factor, the suppression period, and / or the suppression subcategory (eg, priority, etc.) to reflect the trigger load that the MME intends to reduce. Appropriate messages with information elements can be delivered to the CBC. Upon receiving the suppression parameter from the MME, the CBC can perform overload control in the following manner.

Stop indicated triggers

Return a failure report with the appropriate cause to the SCS to MTC-IWF or via MTC-IWF.

8) The MME sends a Write-Replace Warning Confirm / Write-Replace Warning Response message indicating to the CBC that the MME has begun distributing a warning message to the eNodeB.

If the MME is in a congested state (e.g. NAS level congestion control), or for a group of devices to which the MME is to be broadcast or a group of devices (e.g., an external group identifier or an internal group) When NAS level congestion control is performed (Mobility Management / Session Management backoff timer operation in UE) for a specific target UE belonging to the identifier, the MME warns Write-Replace from CBC to avoid mobility management or session management signaling. You can reject the request. At this time, the MME may reject the warning request by identifying that the Write-Replace warning request message from the CBC is a warning message for group messaging for device triggering or for group messaging requiring a specific action of the device. To this end, the MME uses the external group identifier or internal group identifier and / or message identifier values contained in the Write-Replace alert request message from the CBC to indicate that a specific write-replace alert request message is triggered by group messaging or device specific actions. It can identify that it is a group messaging that requires. Alternatively, the warning type included in the Write-Replace alert request message from the CBC identifies the specific write-replace alert request message as either group messaging for device triggering or group messaging requiring specific device action. can do.

The MME may include a cause value that indicates that the failure by the control according to the overload. And / or the MME may include a backoff timer to prevent the CBC from sending a Write-Replace alert request message for a period of time for the failure cause, in which case the MME is sent to the CBC until the backoff timer expires. You can choose not to send Write-Replace warning request messages. And / or in addition to the above, the MME may include an outer group identifier or an inner group identifier in the MM context of the MME for congestion control for a group device or congestion control for a group based message. To this end, during the attach procedure and / or tracking area update (TAU) procedure, the MME may obtain an outer group identifier or an inner group identifier from the UE or the HSS.

If the CBC does not receive a Write-Replace Warning Confirm / Response message during the appropriate time period, and / or receives a reject response due to an overload by the MME, the CBC is another in the same pool area. Alert messages can be attempted through the MME.

9) Upon receiving the Write-Replace Warning Confirm / Response message, the CBC may send a confirmation message to the MTC-IWF about the distribution of the warning message.

10) 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 group device. Alternatively, the steps 9 and 10 can be omitted. Alternatively, the step 9 and step 10 may proceed immediately after step 6. The MTC-IWF receives an acknowledgment message for alert message / group message distribution from the CBC (step 9), or after receiving a delivery report for alert message / group message distribution from the CBC (step 15). Alternatively, charging information records (CDRs) including internal group identifiers and SCS identifiers may be generated and provided to the charging system. In addition to the included information, the charging information may include a triggering method (for example, CBS / Warning message deliver), a warning type, a message identifier, a geographic area, a location / area, a RAT, a repetition period, and the number of broadcast requests. It may include one or more pieces of information.

11) The MME forwards the Write-Replace Warning Message request to the eNodeB. The MME may use the traffic area ID list or the cell ID or cell ID list to determine the eNodeB in the delivery area. If the tracking area ID list or cell ID or cell ID list information is not included, the message may be forwarded to all eNodeBs connected to the MME. Alternatively, if the warning message for device triggering does not include the tracking area ID list or the cell ID or cell ID list information, the MME does not include the tracking area ID list or the cell ID or cell ID list information to trigger the group. You can send a delivery report to the CBC that contains a cause value indicating that the transfer failed.

12) The eNodeB detects duplicate messages by checking the message identifier and serial number in the alert message. If any duplicate message is detected, only the first received is broadcast in the cell. The eNodeB uses the alert region information to determine the cell where the message will be broadcast. The eNodeB broadcasts the message according to the attributes set by the CBC that generated the alert message distribution (e.g., repetition period, number of broadcast requests). Alternatively, the eNodeB broadcasts the message according to the attributes set by the SCS that generated the alert message distribution (e.g., repetition period, number of broadcast requests). Alternatively, the eNodeB broadcasts the message according to the attributes set by the MTC-IWF that generated the alert message distribution (e.g., repetition period, number of broadcast requests).

If a warning broadcast message is already in progress and a Concurrent Warning Message Indicator is included in the Write-Replace Warning Message Request, the eNodeB does not interrupt the existing broadcast message and simultaneously starts broadcasting a new message. Otherwise, the eNodeB can immediately replace the existing broadcast message with a new one.

In addition to the above, the procedure for self-broadcast delivery (step 12) and action at the UE (step 17) from the eNodeB to the UE is performed by broadcasting a group message using an alert message in the E-UTRAN according to the present invention. The method is further described.

13) The eNodeB sends a Write-Replace Warning Response to the MME (even if the warning message is duplicated).

14) From the Write-Replace Warning Response Message returned by the eNodeB, the MME can determine the success or failure of the delivery. And / or create a trace record (e.g., number of times a particular message has been broadcasted in a given warning area). And / or delivery reports can be made using information from the trace record or from the number of times a particular message has been broadcast. The delivery report may contain one or more of the following: message identifier, serial number, external group identifier or internal group identifier, success or failure of trigger delivery, and the cause of the failure.

15) Receive a delivery report for alert message distribution from the CBC. The delivery report may include information on one or more of an external or internal group identifier, a message identifier, an SCS identifier, a trigger reference number, the success or failure of a trigger delivery, and the cause of the failure.

The CBC and / or MTC-IWF may generate a Charging Data Record (CDR) including an external group identifier or an internal group identifier and an SCS identifier and provide it to the charging system. In addition to the included information, the charging information may include a triggering method (for example, CBS / Warning message deliver), a warning type, a message identifier, a geographic area, a location / area, a RAT, a repetition period, a broadcast request count, It may contain one or more pieces of information of the message size.

16) The MTC-IWF sends a device trigger report message to the SCS. The device trigger report message may include one or more information of an external group identifier, a message identifier, an SCS identifier, a trigger reference number, success or failure of a trigger delivery, and a cause of the failure.

17) If the terminal is configured to receive a warning message and the UE authenticates the core network of the eNodeB camped on or if the terminal is configured to receive a group message, the terminal activates the reception of broadcast messages including the warning message. By activating, the contents of the alert message or the application layer contents of the alert message can be dispatched to an application to perform a specific action. The method of sending the content of the warning message or the application layer content of the warning message to the application to perform a specific action in the terminal will be described in the following group message processing procedure in the network entity and the terminal according to the present invention.

In the embodiment of FIG. 5, the MTC-IWF may be implemented as an independent entity or included in the CBC. Even when the MTC-IWF is implemented including the CBC function, the procedure can be used as it is. If the MTC-IWF is implemented with a CBC function, the procedure to be applied is additionally described in the following method in which the MTC-IWF according to the present invention broadcasts a group message using an alert message in the E-UTRAN through a direct interface with the MME. Explain.

Next, a method of broadcasting a group message using an alert message in the E-UTRAN according to the present invention will be described.

RRC (Radio Resource Control) IDLE and a terminal capable of receiving ETWS in an RRC CONNECTED state (eg, an ETWS capable UE) and / or a terminal capable of receiving CMAS and / or a terminal capable of receiving group messaging (eg, a Group). message capable UE may be informed of the presence of a group message using a paging message.

A new indication (eg, group message Indication) may be used to indicate that an existing etws-Indication and / or cmas-Indication and / or group message exists to inform the presence of a group message in the paging message. Alternatively, an external group identifier or an internal group identifier or a message identifier may be used as paging UE-Identity to indicate the existence of a group message in the paging message.

 If the terminal receives the paging message including the information indicating that the group message exists, the terminal receives the corresponding system information according to the scheduling information list (schedulingInfoList) included in the System Information Block Type 1 (SIB1). (Apply the system information acquisition procedure). That is, if the paging message indicates that the group message exists through etws-Indication, the terminal starts receiving the ETWS primary notification and / or ETWS secondary notification according to the schedulingInfoList included in the system information block type 1, the group message is received. It is included in the ETWS primary notification (system information block type 10, SIB10) and / or ETWS secondary notification (system information block type 11, SIB11). Or, if the paging message informs that the group message exists through cmas-Indication, the terminal starts receiving the CMAS notification according to the schedulingInfoList included in the system information block type 1 and the group message is the CMAS notification (system information block type). 12, SIB12). Segmentation may be applied to ETWS secondary notification and / or CMAS notification delivery.

Alternatively, if the paging message indicates that the group message exists through a new indication (eg, group message indication) to indicate that the group message exists, the terminal schedulingInfoList included in the system information block type 1 According to the new indication for indicating that the group message exists, the system information block type newly defined according to the new message for indicating that the group message exists. It is included in the type.

Alternatively, if the paging message informs the paging UE-Identity to indicate the existence of the group message, the UE indicates that the group message exists through the external group identifier or the internal group identifier or the message identifier. A new paging for indicating that a group message exists according to the schedulingInfoList included in the UE starts receiving a newly defined system information block type according to the UE-Identity. Therefore, it can be included in the newly defined system information block type. To this end, the terminal may configure / store an external group identifier or an internal group identifier or a message identifier used as a paging UE-Identity (eg, USIM storage).

As described above, a terminal capable of receiving ETWS (eg, an ETWS capable UE) and / or a terminal capable of receiving CMAS and / or a terminal capable of receiving group messaging (eg, a group message capable UE) may use a paging message. By checking the presence of the group message can be received through the system information according to the group message.

If the paging message indicates that a group message exists via etws-Indication, the alert type of the group message via system information block type 10 allows the terminal that does not use the group trigger message to discard the group message. ) It can be set as 'test' or assigned a specific value. Among the terminals capable of receiving group messaging, a message identifier may be used to identify a group message to be received by one or more terminals included in a specific group. In this case, the terminal may discard or ignore the message identifier of the group to which the terminal belongs. Alternatively, an external group identifier or an internal group identifier and / or a message identifier may be used to identify a group message to be received by one or more terminals included in a specific group among terminals capable of receiving group messaging. To this end, the terminal may configure / store the external group identifier or the internal group identifier (for example, USIM storage), and include the external group identifier or the internal group identifier in the warning message segment of the system information block type 11/12. have. In this case, the terminal may discard or ignore the external group identifier or internal group identifier and / or message identifier of the group to which the terminal belongs.

If the paging message indicates that the group message exists through a cmas-Indicationr or a new indication (eg, group message Indication) indicating that the group message exists, among the terminals capable of receiving group messaging. One or more terminals included in a specific group may use a message identifier to identify a group message to be received. In this case, the terminal may discard or ignore the message identifier of the group to which the terminal belongs.

Message identifiers with 16 bits can be difficult to use to identify specific groups within a mobile network. That is, since the power of 16 is 2, only 64,000 can be distinguished. Therefore, a group belonging to a specific subscriber or a specific feature may be insufficient to identify the same group in the mobile communication network. To solve this, if a message identifier is used to identify the group message, expand the message identifier field, or combine the message identifier field with some of the application layer content values contained within the alert message segment, or the message identifier and external group identifier or You can also consider combining some of the internal group identifier values to use them as message identifiers.

Alternatively, an external group identifier or an internal group identifier may be used to identify a group message to be received by one or more terminals included in a specific group among terminals capable of receiving group messaging. To this end, the terminal may configure / store the external group identifier or the internal group identifier (for example, USIM storage), and include the external group identifier or the internal group identifier in the warning message segment of the system information block type 11/12. have. In this case, the terminal may discard or ignore the external group identifier or internal group identifier of the group to which the terminal belongs.

If the paging message indicates to the paging UE-Identity that the group message exists through the external group identifier or the internal group identifier to indicate that the group message exists, in this case, the terminal is the external group identifier or internal group of the group to which the terminal belongs; If you do not include a group identifier, you can discard it or ignore it. The terminal may dispatch a message to a triggering function in the UE or an application in the UE using an external group identifier or an internal group identifier and / or a message identifier.

The terminal capable of receiving group messaging in the RRC CONNECTED state may attempt to read the paging at least once per default paging cycle to check whether the group message exists. Alternatively, the terminal capable of receiving group messaging in the RRC CONNECTED state may attempt to read the paging at least once every specific multiple of the default paging cycle to check for the existence of the group message.

6 is a diagram illustrating a network configuration for an embodiment of the present invention. Hereinafter, an embodiment of a group message processing procedure in a network entity and a terminal according to an embodiment of the present invention will be described in detail with reference to FIGS. 5 and 6.

The SCS requests group message transmission to the MTC-IWF through the Tsp interface between the SCS and the MTC-IWF to send a group message for a group of devices.

 The SCS may perform a specific action (eg, for example to initiate immediate or later communication to the SCS / AS) within a terminal that receives a group message. Information related to an application (application 1/2/3 of FIG. 6) to be performed may be included. Application information for enabling the addressing of an application to perform a specific action in the terminal may be included in the application port information or the trigger payload information or the application layer content information. The application information may be dispatched by a trigger function in the terminal. Alternatively, the application information may be dispatched by a warning message function in a terminal that determines and processes a warning message reception (for example, in FIG. 6, a trigger function in the terminal is combined with a warning message function. Occation).

When the terminal receives a group message through a broadcast (for example, through an alert message delivery in EPS), the SCS may include information for identifying a group message to be received by the terminal. The information for identifying the group message to be received by the terminal may be external group identifier or message identifier information. The terminal may identify a group message to be received by the terminal by a warning message function and dispatch the group message to the trigger function.

Alternatively, the MTC-IWF transmits a message including information for identifying a group message to be received by the terminal when the terminal receives the group message through broadcast (for example, through an alert message delivery in EPS). can do. The information for identifying the group message to be received by the terminal may be an external group identifier or an internal group identifier and / or message identifier information. The terminal may identify a group message to be received by the terminal by a warning message function and dispatch the group message to the trigger function.

Alternatively, the CBC may include information for identifying a group message to be received by the terminal when the terminal receives the group message via broadcast (for example, through an alert message delivery in EPS). have. The information for identifying the group message to be received by the terminal may be an external group identifier or an internal group identifier and / or message identifier information. The terminal may identify a group message to be received by the terminal by a warning message function and dispatch the group message to the trigger function.

The eNodeB sends a paging message to broadcast the group message received through the MME. The eNodeB may use a new indication (eg, group message Indication) to indicate that an existing etws-Indication and / or cmas-Indication and / or group message exists to inform the presence of a group message in the paging message. Alternatively, the eNodeB may use an outer group identifier or an inner group identifier or a message identifier as a paging UE-Identity to indicate the presence of a group message in a paging message.

The terminal receiving the paging message checks whether there is information for notifying the existence of the group message in the paging message, checks the information for identifying the group message to be received by the terminal, and receives the broadcasted message. The terminal may discard or ignore the external group identifier or internal group identifier and / or message identifier of the group to which the terminal belongs.

Receiving a group message in the terminal is performed by a warning message function in the terminal. The terminal may dispatch the group message to the triggering function in the terminal by using an external group identifier or an internal group identifier and / or a message identifier in the group message.

The warning message function in the terminal or the trigger function in the terminal or the terminal determines the backoff timer for the specific action according to the backoff timer or the prohibition / control parameter included in the received group message and operates the specific action in the terminal. The backoff timer may not be performed while the backoff timer is in operation, and the specific action may be performed when the backoff timer expires. That is, the back off timer may indicate an offset value at which the terminal performs the specific action. The backoff timer for the specific action may include a backoff timer or prohibition / control on an individual device identifier (eg, IMSI, IMEI) as a parameter and / or included in a group message so as to have a random value for each UE belonging to the group. The parameter may be used to determine the random backoff timer value. Alternatively, a warning message function in the terminal or a trigger function in the terminal or the terminal may select a random backoff timer within a schedule time / time range in which a specific action included in the received group message should be performed. The operation may be performed such that a specific action in the terminal is not performed. The backoff timer for the specific action may be configured to have a warning message function in the terminal or a trigger function in the terminal or a terminal to identify individual device identifiers (eg, IMSI, IMEI) so as to have a random value for each terminal belonging to the group. A backoff timer included in the group message or a prohibition / control parameter may be used to have a random backoff timer value using a hashing algorithm or the like.

In another method, a terminal that has received a message that does not include a high priority in order to control overload by a group message may include signaling with a low access priority in NAS signaling.

Next, when the MTC-IWF is implemented with the CBC function, a method of broadcasting a group message using an alert message in the E-UTRAN through the direct interface between the MTC-IWF and the MME will be described.

7 is a diagram illustrating a network configuration for group messaging through a direct interface between an MTC-IWF and an MME according to an embodiment of the present invention.

8 illustrates a group-based triggering procedure through a direct interface between the MTC-IWF and the MME according to an embodiment of the present invention.

A description with reference to FIGS. 7 and 8 is as follows.

1-5) The same procedure as in Step 1-5 of FIG. 5 is performed.

6) The MTC-IWF sends a broadcast request message (eg, Submit Broadcast Request) to the MME through the direct interface between the MTC-IWF and the MME using the identifiers of the serving nodes received from the HSS. The broadcast request message may be one or more of a warning type, message identifier, serial number, tracking area ID list, warning area, OMC ID, Concurrent Warning Message Indicator, time period, and warning message. May contain information.

The alert type information may be set to address a triggering function in the UE, and a specific value may be reserved for a group trigger message. And / or the warning type information may be used by assigning a value different from the existing disaster type (for example, earthquake, tsunami, etc.) for the group trigger message. And / or the warning type information may be set to 'test' so that terminals not using the group trigger message may discard the group message (silently discard). And / or the warning type information may be assigned by using a specific value so that the terminal that does not use the group trigger message (silently discard).

The message identifier may be a value passed through SCS or mapped to an external group identifier and / or an SCS identifier in HSS and a value passed through MTC-IWF or mapped to an external group identifier and / or an SCS identifier in MTC-IWF. The delivered value and / or the message identifier may be a value set to address a triggering function in the UE.

The serial number is a value for identifying a specific message from a source and a type indicated by a message identifier, and is changed every time a message having a given message identifier is changed. The MME may store / manage message identifiers and / or mapping information between a serial number and the trigger reference number.

The traffic region ID list is information used only in the MME, and the MME may use it to select an eNodeB to forward a Write-Replace alert request message.

The alert area indicates a cell ID list and / or a tracking area identity (TAI) list. The eNodeB consists of a TAI and a cell ID, so as to check the matching of the contents of the alert area to identify the cell to which to distribute the alert message. The warning area is an optional information element. If there is no warning area, it is interpreted as all cells in the eNodeB. If the CBC receives the serving node identifier and the cell information, the traffic area ID list may be included in the serving node identifier and the cell information in the warning area.

If an OMC ID exists, it indicates its destination if the success / failure of message delivery is recorded in a trace record after step 8. By including the MTC-IWF identifier or address information in the OMC ID, the delivery success or failure in reporting the delivery of step 10 and / or step 11 can be communicated to the MTC-IWF. Concurrent Warning Message indicator indicates whether the mobile network supports simultaneous warning message broadcast.

The time period information may be a value such as a validity period included in a trigger request message between the SCS and the MTC-IWF or a schedule time / time range in which message delivery should be attempted. Or the time period information is another value that is independent of the validity period included in the trigger request message between the SCS and the MTC-IWF and / or the schedule time / time range in which message delivery should be attempted, or is related to another value. Can be a value.

The alert message may include application layer content information included in a trigger request message between the SCS and the MTC-IWF. And / or the alert message may include trigger payload information included in a trigger request message between the SCS and the MTC-IWF. And / or the alert message may include preferred UE behavior (eg, PDN connection, detach, specific action performance) information. And / or in addition to the above, the warning message may contain backoff timer information or prohibition / control parameters to prevent overload and / or a schedule time / time range for which a specific action should be performed on the device. It may include.

Certain congestion situations (eg, NAS level Mobility Management Congestion Control in TS 23.401 4.3.7.4.2) are maintained to prevent network congestion from worsening as a group of devices responds to a trigger contained in a group message. It is necessary to make sure that the UE is not triggered during operation. In order to reflect the trigger load that the MME attempts to reduce, the MME uses a suppression parameter that includes a suppression factor, a suppression period, and / or a suppression subcategory (eg, priority, group trigger type, etc.). Appropriate messages with optional information elements indicating may be delivered to the MTC-IWF. Upon receiving the suppression parameter from the MME, the MTC-IWF may perform overload control in the following manner.

Stop indicated triggers

Return a failure report with the appropriate cause to the SCS to MTC-IWF or via MTC-IWF.

7) The MME forwards the Write-Replace Warning Message request to the eNodeB. The MME may use the traffic area ID list or the cell ID or cell ID list to determine the eNodeB in the delivery area. If the tracking area ID list or cell ID or cell ID list information is not included, the message may be forwarded to all eNodeBs connected to the MME. Alternatively, if the warning message for device triggering does not include the tracking area ID list or the cell ID or cell ID list information, the MME does not include the tracking area ID list or the cell ID or cell ID list information to trigger the group. A delivery report can be sent to the MTC-IWF with a cause value indicating that the transfer failed.

8) eNodeB detects duplicate message by checking message identifier and serial number in warning message. If any duplicate message is detected, only the first received is broadcast in the cell. The eNodeB uses the alert region information to determine the cell where the message will be broadcast. The eNodeB broadcasts the message according to the attributes set by the SCS that generated the alert message distribution (e.g., repetition period, number of broadcast requests). Alternatively, the eNodeB broadcasts the message according to the attributes set by the MTC-IWF that generated the alert message distribution (e.g., repetition period, number of broadcast requests).

If a warning broadcast message is already in progress and a Concurrent Warning Message Indicator is included in the Write-Replace Warning Message Request, the eNodeB does not interrupt the existing broadcast message and simultaneously starts broadcasting a new message. Otherwise, the eNodeB can immediately replace the existing broadcast message with a new one.

In addition to the above, the procedure for self-broadcast delivery (step 9) and action at the UE (step 12) from the eNodeB to the UE is a method of broadcasting a group message using an alert message in the E-UTRAN according to the present invention. Is the same as

9) The eNodeB sends a Write-Replace Warning Response to the MME (even if the warning message is duplicated).

10) From the Write-Replace Warning Response Message returned by the eNodeB, the MME can determine the success or failure of the delivery. And / or create a trace record (e.g., number of times a particular message has been broadcasted in a given warning area). And / or delivery reports can be made using information from the trace record or from the number of times a particular message has been broadcast. The delivery report may include one or more of the message identifier, serial number, external group identifier or internal group identifier, trigger reference number, success or failure of trigger delivery, and the cause of the failure.

The MME and / or MTC-IWF may generate a Charging Data Record (CDR) including an external group identifier or an internal group identifier and an SCS identifier and provide it to the charging system. In addition to the included information, the charging information may include a triggering method (for example, CBS / Warning message deliver), a warning type, a message identifier, a geographic area, a location / area, a RAT, a repetition period, a broadcast request count, It may contain one or more pieces of information of the message size.

11-12) The same procedure as in step 16-17 of FIG. 5 is performed.

Although the present invention has been described using a cell broadcast or alert message delivery procedure, it may be used in a messaging method that uses a broadcast based service (e.g., Multimedia Broadcast Multicast Service (MBMS)) other than the cell broadcast or alert message delivery procedure. Can be.

9 is a block diagram showing the configuration of an MTC-IWF according to an embodiment of the present invention. 9 shows the configuration of the MTC-IWF when the MTC-IWF and the CBC are separate entities.

9, the MTC-IWF 900 includes an SCS communication unit 910 for communicating with an SCS, an HSS communication unit 920 for communicating with an HSS, a CBC communication unit 930 for communicating with a CBC, and The control unit 940 is included.

The SCS communication unit 910 may receive a device triggering request message for a group of devices from the SCS. The device triggering request message may include at least one information element of external group identifier information, SCS identifier information, trigger reference number, validity period, priority, and trigger payload.

In addition, the device triggering request message may include at least one of a specific geographic area where the devices are located, a location / area, and RAT information. Alternatively, the geographic area or location / area information may be stored in the HSS, and the HSS communication unit 920 may inquire the geographic area or the location / area information through the HSS. Alternatively, the geographic region or location / region information may be stored in the MTC-IWF 900. Alternatively, the geographic area or location / area information may be stored in the CBC.

In addition, the device triggering request message may include application layer content or application port information of the group message.

In addition, the device triggering request message may include information of at least one of a message identifier, a repetition period, and the number of broadcast requests. Alternatively, at least one of the message identifier, the repetition period, and the broadcast request number may be determined by the controller 940 of the MTC-IWF 900. Alternatively, at least one of the message identifier, the repetition period, and the broadcast request number may be determined by the CBC.

In addition, the device triggering request message is a backoff timer or prohibition parameter to determine the schedule time at which message delivery is attempted, the preferred device triggering method, the preferred device's behavior, and the time at which the device prohibits the execution of the particular action before performing the particular action. , And at least one of information for allowing the device to distribute and perform a specific action within a schedule time for the device to perform a specific action.

In addition, the device triggering request message for the group may include message type information for distinguishing from the triggering request message for the individual device.

The HSS communication unit 920 may inquire subscriber information to the HSS. The HSS may provide an inner group identifier corresponding to the outer group identifier, a message identifier, routing information including an associated serving node identifier, a cell ID or cell ID list, a TAI list, and the like.

The controller 940 may determine whether the SCS is authorized to transmit the group trigger request message. In addition, the controller 940 may determine whether the SCS has authority to send one or more pieces of information included in the group trigger request message. In addition, the controller 940 may determine whether the quota or rate of group trigger submission is exceeded. In addition, the controller 940 may determine whether the SCS is authorized to trigger a device of a specific group. The HSS communication unit 920 may inquire information from the HSS in order to determine the authority or determine whether the quota is exceeded.

In addition, the controller 940 may select the trigger forwarding procedure based on the information and the policy received through the HSS communication unit 920. When the controller 940 selects a trigger delivery procedure using broadcasting, the CBC communication unit 930 transmits a broadcast request message to the CBC. The broadcast request message may include information of at least one of a warning type, a message identifier, a serial number, a tracking area ID list, a warning area, an OMC ID, a Concurrent Warning Message Indicator, a time period, and a warning message.

In addition, the controller 940 may generate charging information. The charging information may include at least one information of a group identifier, an SCS identifier, a triggering method, an alert type, a message identifier, a geographic region, a location / region, a RAT, a repetition period, a broadcast request number, and a message size.

10 is a block diagram illustrating a configuration of the MTC-IWF according to an embodiment of the present invention. 10 shows the configuration of the MTC-IWF when the MTC-IWF and the CBC are integrated.

Referring to FIG. 10, the MTC-IWF 1000 may include an SCS communication unit 1010 for communicating with an SCS, an HSS communication unit 1020 for communicating with an HSS, and a core network entity communication unit for communicating with a core network entity ( 1030, and a control unit 1040.

The SCS communication unit 1010 may receive a device triggering request message for a group of devices from the SCS. The device triggering request message may include at least one information element of external group identifier information, SCS identifier information, trigger reference number, validity period, priority, and trigger payload.

In addition, the device triggering request message may include at least one of a specific geographic area where the devices are located, a location / area, and RAT information. Alternatively, the geographic area or location / area information may be stored in the HSS, and the HSS communication unit 1020 may inquire the geographic area or the location / area information through the HSS. Alternatively, the geographic region or location / region information may be stored in the MTC-IWF 1000. Alternatively, the geographic area or location / area information may be stored in the CBC.

In addition, the device triggering request message may include application layer content or application port information of the group message.

In addition, the device triggering request message may include information of at least one of a message identifier, a repetition period, and the number of broadcast requests. Alternatively, at least one of the message identifier, the repetition period, and the broadcast request number may be determined by the controller 1040 of the MTC-IWF 1000. Alternatively, at least one of the message identifier, the repetition period, and the broadcast request number may be determined by the CBC.

In addition, the device triggering request message is a backoff timer or prohibition parameter to determine the schedule time at which message delivery is attempted, the preferred device triggering method, the preferred device's behavior, and the time at which the device prohibits the execution of the particular action before performing the particular action. , And at least one of information for allowing the device to distribute and perform a specific action within a schedule time for the device to perform a specific action.

In addition, the device triggering request message for the group may include message type information for distinguishing from the triggering request message for the individual device.

The HSS communication unit 1020 may inquire the subscriber information to the HSS. The HSS may provide an inner group identifier corresponding to the outer group identifier, a message identifier, routing information including an associated serving node identifier, a cell ID or cell ID list, a TAI list, and the like.

The controller 1040 may determine whether the SCS is authorized to transmit the group trigger request message. In addition, the controller 1040 may determine whether the SCS has authority to send one or more pieces of information included in the group trigger request message. In addition, the controller 1040 may determine whether the quota or rate of the group trigger submission is exceeded. In addition, the controller 1040 may determine whether the SCS is authorized to trigger a device of a specific group. The HSS communication unit 1020 may inquire information from the HSS in order to determine the authority or determine whether the quota is exceeded.

In addition, the controller 1040 may select a trigger forwarding procedure based on the information and the policy received through the HSS communication unit 1020. When the controller 1040 selects a trigger delivery procedure using broadcasting, the core network entity communication unit 1030 transmits a broadcast request message to the core network entity (eg, MME). The broadcast request message may include information of at least one of a warning type, a message identifier, a serial number, a tracking area ID list, a warning area, an OMC ID, a Concurrent Warning Message Indicator, a time period, and a warning message.

In addition, the controller 940 may generate charging information. The charging information may include at least one information of a group identifier, an SCS identifier, a triggering method, an alert type, a message identifier, a geographic region, a location / region, a RAT, a repetition period, a broadcast request number, and a message size.

11 is a block diagram showing the configuration of a device according to an embodiment of the present invention.

Referring to FIG. 11, the device 1100 includes a receiver 1110, a controller 1120, and at least one application 1130-1-1130-3 that receive a signal from a base station (eg, an eNodeB). The controller 1120 includes a warning message processor 1122 and a trigger processor 1124.

When the receiver 1110 receives an alert message from the base station, the alert message processor 1122 determines whether the alert message is a group message to be received by the device 1100 based on a message identifier included in the alert message. In this case, the warning message processor 1122 may further determine whether the warning message is a group message to be received by the device 1100 by considering the group identifier in addition to the message identifier.

When the warning message processing unit 1122 determines that the warning message is a group message to be received by the device 1100, the trigger processing unit 1124 performs a specific action. The alert message may include information related to the applications 1130-1 to 1130-3 to perform communication initiation with the SCS or AS.

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 scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

Claims (18)

Receiving a device trigger request message for a group of devices from a service capability server (SCS); And
Transmitting a broadcast request message based on the device trigger request message to a CBC (Cell Broadcasting Center) for distributing a warning message to a core network entity in a public warning system (PWS) structure,
The group device trigger request message includes a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a broadcast request number, a time range in which a specific action should be performed in a device, and a specific action in the device is randomly selected on the time range. Group-based messaging method of the relay server, characterized in that it comprises at least one of a control parameter, group message information, priority to be performed. The method of claim 1,
The broadcast request message may include information in at least one of a time range in which a specific action is to be performed in a device and a control parameter for randomly performing a specific action in the device in a group message. Group-based messaging method for servers. The method of claim 1,
And the broadcast request message includes a message identifier corresponding to the group identifier. The method of claim 3, wherein
And the broadcast request message further comprises the group identifier or a local identifier of the group identifier. The method of claim 1,
Generating charging information comprising at least one of a message size, a geographic area, and the number of broadcast requests. The method of claim 1,
And determining whether the SCS is authorized to send a group message. Receiving a device trigger request message for a group of devices from a service capability server (SCS); And
Generating a warning message based on the device trigger request message and transmitting the generated warning message to a core network entity;
The group device trigger request message includes a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a broadcast request number, a time range in which a specific action should be performed in a device, and a specific action in the device is randomly selected on the time range. Group-based messaging method of the relay server, characterized in that it comprises at least one of a control parameter, group message information, priority to be performed. As a warning message handling method of a device,
Receiving an alert message from a communication network;
Determining whether the warning message is a group message to be received by the device based on a message identifier included in the warning message; And
If the warning message is a group message to be received by the device, performing a specific action. The method of claim 8,
And preconfiguring a group message identifier to be received by the device. The method of claim 8,
Determining whether the warning message is a group message to be received by the device further comprises processing the group identifier or the local identifier of the group identifier in the warning message. . The method of claim 8,
If the warning message is a group message to be received by the device, the step of performing a specific action is performed randomly within a time range in which a specific action should be performed in the device included in the received group message. How to handle warning messages. An SCS communication unit configured to receive a device trigger request message for a group of devices from a service capability server (SCS); And
A PWS communication unit for transmitting a broadcast request message based on the device trigger request message to a CBC (Cell Broadcasting Center) for distributing a warning message to a core network entity in a public warning system (PWS) structure;
The device trigger request message may include at least one of a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a broadcast request number, a time range in which a specific action is to be performed in a device, and a priority. Relay server. 13. The method of claim 12,
And a control parameter in the broadcast request message to cause a specific action in the terminal to be performed randomly over the time range. 13. The method of claim 12,
And the broadcast request message includes a message identifier corresponding to the group identifier. 13. The method of claim 12,
The broadcast request message further comprises the group identifier or a local identifier of the group identifier. 13. The method of claim 12,
And a charging information generator for generating charging information including at least one of a message size, a geographic area, and the number of broadcast requests. An SCS communication unit configured to receive a device trigger request message for a group of devices from a service capability server (SCS); And
A core network entity communication unit configured to generate an alert message based on the device trigger request message and transmit the generated alert message to a core network entity;
The device trigger request message may include at least one of a group identifier, a geographic area, a radio access technology (RAT), a repetition period, a broadcast request number, a time range in which a specific action is to be performed in a device, and a priority. Relay server. A receiver for receiving a warning message from a communication network; And
Determining whether the warning message is a group message to be received by the device based on a message identifier or a group identifier included in the warning message, and performing a specific action when the warning message is a group message to be received by the device Device comprising a control unit.

Images