KR101873068B1 - User Equipment Monitoring Method and Apparatus in Mobile Network - Google Patents

Abstract

The present invention relates to a method and apparatus for monitoring a UE in a 3GPP mobile communication network in order to monitor a device, an association of the device and a UICC, a change in the point of attachment, a loss of connectivity, (Eg, reporting) a network object, activating monitoring of a specific event on the network entity, and performing an action (eg, reporting) when detecting an event .

Description

TECHNICAL FIELD [0001] The present invention relates to a method and apparatus for monitoring a terminal in a mobile communication network,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for monitoring a user equipment (UE) type used for machine type communication via a mobile communication network, a general UE, and a user or a subscription related event.

Machine Type Communication (MTC) or Machine to Machine Communication (M2M) refers to the form of data communication associated with one or more entities where human intervention is not necessarily required. A service optimized for object communication can have characteristics different from services optimized for human-to-human communication.

The UE (UEs used for MTC or MTC device or M2M device) used for the MTC can be installed in a position where the communication module may be stolen or damaged. It is also possible to periodically or by user's need to monitor the association of the device with the Universal Integrated Circuit Card (UICC), the change in the point of attachment, and the loss of connectivity May be required.

Accordingly, it may be necessary to detect an event occurring in the MTC device, which may be caused by the theft or damage of the communication module in the mobile communication network, and to report the event when the event is detected.

However, in order to monitor a UE accommodated through a mobile communication network (for example, a mobile communication network according to 3GPP (3 ^rd Generation Partnership Project)), a specific monitoring event can be detected through a monitoring application in the UE, It was only possible to report specific monitoring events to the application server upon event detection. Only reports of monitoring events through the application layer were possible.

As described above, the conventional method does not support monitoring to detect and report a specific event generated in the UE through a network entity. Therefore, monitoring information on events such as association of the device and UICC, change in the point of attachment, and loss of connectivity that a user can identify through a network object There was a problem that could not be utilized.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and it is an object of the present invention to provide a method and apparatus for managing a device, a UICC association, a change in the point of attachment, and a loss of connectivity in a 3GPP mobile communication network. For monitoring, in activating or deactivating monitoring of one or more devices at an external server, the serving node provides only the function of providing information for detection of a specific monitoring event, It is intended to provide specific procedures for monitoring detection, reporting, authentication, billing and other control functions through IWF and / or HSS.

An embodiment of the present invention includes: receiving a monitoring request message from a service capability server (SCS); Authenticating whether the SCS is authorized to send the monitoring request message; Determining whether the SCS exceeds an allowed monitoring submission amount or rate; Inquiring the HSS (Home Subscriber Server) to confirm whether the SCS has the right to perform monitoring for a specific terminal; And determining a monitoring event to the serving node and transmitting a monitoring request message to the serving node.

Another embodiment of the present invention provides a method comprising: receiving information related to a monitoring event from a serving node; And transmitting a monitoring result report to the Service Capability Server (SCS) requesting the monitoring event.

According to another embodiment of the present invention, there is provided an information processing apparatus including an SCS communication unit for receiving a monitoring request message from a service capability server (SCS); A control unit for authorizing whether the SCS is authorized to send the monitoring request message and for determining whether the SCS exceeds the allowed monitoring submission amount or rate; An HSS communication unit for inquiring an HSS (Home Subscriber Server) to authenticate whether the SCS is authorized to perform monitoring for a specific terminal; And a serving node communication unit for determining a monitoring event to the serving node and transmitting a monitoring request message.

Another embodiment of the present invention includes a serving node communication unit for receiving information related to a monitoring event from a serving node; And an SCS communication unit for transmitting a monitoring result report to a Service Capability Server (SCS) requesting the monitoring event.

Another embodiment of the present invention includes: receiving a monitoring request message from a Service Capability Server (SCS); Authenticating whether the SCS is authorized to send the monitoring request message; Determining whether the SCS exceeds an allowed monitoring submission amount or rate; And transmitting a monitoring request message to an HSS (Home Subscriber Server).

Another embodiment of the present invention provides a method comprising: configuring a monitoring event to a serving node; Receiving information related to the monitoring event from a serving node; And transmitting a monitoring result report to the Service Capability Server (SCS) requesting the monitoring event.

According to another embodiment of the present invention, there is provided a method for controlling a mobile terminal, the method comprising: receiving a monitoring request message from a Service Capability Server (SCS) for reachable; Transmitting a message instructing the HSS (Home Subscriber Server) to inform the terminal reachable; Receiving notification that the terminal is reachable from the HSS when the terminal becomes reachable; And forwarding the terminal reachability to the SCS.

According to the present invention, there is provided a method for monitoring a device, an association of the device and a UICC, a change in the point of attachment, and loss of connectivity in a mobile communication network .

Figure 1 shows a 3GPP architecture for MTC.
2 illustrates a network structure including a monitoring sensing functional entity and a monitoring reporting functional entity according to an embodiment of the present invention.
3 shows a network structure for reporting by the MTC IWF according to an embodiment of the present invention.
4 illustrates a network structure including a monitoring function entity according to an embodiment of the present invention.
FIG. 5 shows a network structure for providing a monitoring service by the MTC-IWF according to an embodiment of the present invention.
6 shows a network structure for providing a monitoring service by the MTC-IWF and the monitoring function entity according to an embodiment of the present invention.
7 shows an example of a UE Reachability Notification Request Procedure.
8 shows an example of a UE activity procedure.
FIG. 9 shows a monitoring activation procedure or a monitoring procedure through the MTC-IWF or the monitoring function entity in the SCS according to an embodiment of the present invention.
FIG. 10 illustrates a monitoring activation procedure or monitoring procedure of an MTC-IWF or a monitoring function entity through an HSS interface according to an embodiment of the present invention.
11 shows a monitoring activation procedure or monitoring procedure via a MTC-IWF or a monitoring functional entity via a serving node direct interface (T5 interface) according to an embodiment of the present invention.
12 shows a monitoring procedure via the HSS in a specific monitoring event activation state in the serving node according to an embodiment of the present invention.
FIG. 13 shows a monitoring procedure through a direct interface with the MTC-IWF in a specific monitoring event activation state in a serving node according to an exemplary embodiment of the present invention.
FIG. 14 is a block diagram showing a configuration of an MTC-IWF 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 that represents machine to machine communication where one or more entities do not necessarily require human interaction.

The 3GPP architecture for MTC is shown in FIG.

In Fig. 1, each entity is as follows.

User Equipment (UE): A mobile communication terminal, a UE may host one or more MTC applications or monitoring applications,

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

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

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

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

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

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

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

SCS (Service Capability Server): An entity connected to a 3GPP network to communicate with a mobile communication terminal (UEs used for MTC) used for MTC or a general mobile communication UE. The home service is a home public land mobile network (HPLMN) ) MTC IWF. SCS can be used by one or more MTC applications

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

- Home Subscriber Server (HSS): A master database for users. An object that contains the subscription-related information needed to support session processing in the network object.

- MTC-IWF (InterWorking Function): An object that performs relaying or translating of a signaling protocol used to activate a specific function in the mobile communication network through the Tsp with the 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 (HPLMN)

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

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

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

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

End-to-end communication between an MTC application in a mobile communication terminal (UE) and an MTC application in an application server (AS) of an external network of a mobile communication network is performed by a 3GPP system and a service capability server (SCS) Server). The Direct Model in the figure shows a model in which the AS directly connects to the operator network without using SCS to perform user plane communication with the UE.

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

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

Monitoring may be provided on a subscription basis. The monitoring subscription information or monitoring subscription profile may be configured in the HSS and / or MTC-IWF as part of the UE subscription information. The information that can be configured in the HSS and / or MTC-IWF includes, for example, monitoring events for the UE, criteria related to monitoring (e.g., list of allowed IMEIs, list of allowed locations) Information indicating that the monitoring event is activated, information on the network entity (for example, MTC-IWF identifier) for notifying when a specific monitoring event is activated and related information is received, have. The HSS may include information about whether monitoring by a specific monitoring server's request is allowed at the UE. I.e. monitoring server information allowed for the UE (e.g., a server identifier allowed for an identifier of an individual device) or monitoring server information allowed for one or more UEs (e.g., a server identifier Or mapping information of the group identifier and the individual identifier). The monitoring server may be an MTC application server or an SCS server, or may be any entity (e.g., a UE with a monitoring application) that interacts with a 3GPP network entity to obtain monitoring information.

For monitoring purposes, monitoring events and related criteria as shown in Table 1 can be configured in the HSS.

Another type of monitoring subscription information or monitoring subscription profile may be subscription information associated with a monitoring server or a monitoring user desiring to obtain monitoring information for one or more UEs. The monitoring server may be an MTC application server or an SCS server and may be any entity that interacts with a network entity to obtain monitoring information (e.g., a UE with a monitoring application). The monitoring user may be a user who wants to obtain monitoring information for one or more UEs through the monitoring server.

The subscription information associated with the monitoring server or the monitoring user includes at least one of a monitoring server identifier, an allowed monitoring request type, an allowed monitoring event, a criterion relating to monitoring, an action for a monitoring event, A group identifier for a group of UEs to be monitored and / or an individual terminal identifier to be monitored or mapped to the group identifier (e.g., IMSI, MSISDN, TS 23.682 Local identifier @ external identifier in the form of a domain identifier) list. The subscription information associated with the monitoring server or the monitoring user may be configured in the HSS as part of the UE subscription information. Alternatively, the monitoring server or monitoring user subscription information may be configured in the HSS as group subscription information. Alternatively, the monitoring server or monitoring user subscription information may be configured or stored in the monitoring functional entity or MTC-IWF according to the present invention.

 Detection and reporting of the monitoring event in a PLMN (Public Land Mobile Network) may be provided through a network element of the mobile communication network. For example, detection of monitoring events may be provided via the MME / SGSN or provided via the HSS. Likewise, monitoring event reporting can be provided via the MME / SGSN or through the HSS.

 Detection and reporting of the monitoring event in a PLMN (Public Land Mobile Network) is a new functional entity that is responsible for detecting monitoring events in the mobile communication network. entity, and monitoring reporting function, which is a new functional entity responsible for reporting the event in the mobile communication network. The monitoring sensing function and the monitoring reporting function may exist as one or more instances in a mobile communication network (PLMN). This monitoring and monitoring function may be a standalone entity or a functional entity of another network element.

 2 illustrates a network structure including a monitoring sensing functional entity and a monitoring reporting functional entity according to an embodiment of the present invention.

 For example, the monitoring reporting function may be provided through the MTC-IWF (InterWorking Function) of 3GPP TS 23.682. Alternatively, the monitoring reporting function may be provided as a functional entity of the MTC-IWF of 3GPP TS 23.682. Or the monitoring reporting function may be provided as part of the MTC-IWF of 3GPP TS 23.682. At this time, the monitoring detection function may be a standalone entity and may be provided as a functional entity of the MME / SGSN or the HSS.

 3 shows a network structure for reporting by the MTC IWF according to an embodiment of the present invention.

 Detection and reporting of the monitoring event in a PLMN (Public Land Mobile Network) is provided through a new functional entity that is responsible for sensing and reporting on a monitoring event in the mobile communication network . That is, the functions necessary for UE monitoring in the mobile communication network, such as the detection function and the reporting function for the monitoring event, can be provided through a single monitoring function entity. The monitoring function may activate monitoring for a specific event. The monitoring function may exist as one or more instances in a mobile communication network (PLMN). This monitoring function may be a standalone entity or a functional entity of another network element.

  4 illustrates a network structure including a monitoring function entity according to an embodiment of the present invention.

 For example, the monitoring function may be provided through the MTC-IWF (InterWorking Function) of 3GPP TS 23.682. Alternatively, the monitoring function may be provided as a functional entity of the MTC-IWF of 3GPP TS 23.682. Or the monitoring function may be provided as part of the MTC-IWF of 3GPP TS 23.682.

FIG. 5 illustrates a network structure for providing a monitoring service by the MTC-IWF according to an embodiment of the present invention.

 The monitoring user can configure actions to be performed by the network, such as detection and reporting of monitoring events, for monitoring a specific UE. The monitoring user may also activate monitoring for a specific event. The monitoring user may configure the action to be executed by the network via the MTC-IWF in the network structure of FIG. 5, or may activate monitoring for a specific event.

  The monitoring user may request monitoring to request an immediate monitoring information response to the UE. The monitoring user may also request monitoring to request a monitoring information response thereon after a specific event has occurred in the UE. In this way, a monitoring function can be performed through the monitoring function entity for UE monitoring by the monitoring user.

In order to monitor the UE, a monitoring request message is processed through the Tsp interface between the MTC-IWF and the SCS server, and a monitoring function for activating monitoring for a specific monitoring event, detecting a monitoring event, The functions required for monitoring can also be provided through the monitoring function object.

6 shows a network structure for providing a monitoring service by the MTC-IWF and the monitoring function entity according to an embodiment of the present invention.

To provide monitoring event detection and reporting for UEs in the mobile communication network, new functions may be implemented or new procedures may be implemented to support monitoring event detection and reporting at the MME / SGSN.

 The HSS may send a specific event to the HSS and / or to the MME / SGSN either by monitoring subscription information or monitoring subscription profile changes and / or by a monitoring request of an external server, or by a monitoring request of an MTC-IWF receiving a monitoring request of an external server The user may activate or deactivate monitoring for a particular event by setting indicator information for monitoring the particular event.

Through the monitoring subscription information or monitoring subscription profile of the HSS, the HSS can configure monitoring related information to the MME / SGSN or activate monitoring for specific events. When the HSS changes the subscriber information (eg, change the subscription profile, attach, TAU), the HSS is stored in the MME / SGSN using the Insert Subscriber Data Procedure or the Update Location Procedure. The MME / SGSN can configure the monitoring related information by making the subscription data modified.

 The HSS can configure monitoring related information to the MME / SGSN using the Insert Subscriber Data Procedure or the Update Location Procedure for UE monitoring. The HSS can activate monitoring for events specific to the MME / SGSN using the Insert Subscriber Data Procedure or the Update Location Procedure for UE monitoring.

 The HSS may send an IMSI and monitoring subscription data to the MME / SGSN in the Insert Subscriber Data Request or Update Location Request message. The monitoring subscription data may include monitoring events for the UE, criteria related to monitoring, actions for monitoring events, and the like. The subscription data may include identification information of a monitoring function entity to be monitored when the event is detected. When UE monitoring is configured in the SGSN / MME through the subscription data to detect a monitoring event, the SGSN / MME may forward the detected monitoring event information to the monitoring function entity.

If the monitoring function entity is MTC-IWF, the monitoring event information may be provided through the T5 interface between the MTC-IWF and the MME / SGSN. An application protocol (e.g., T5 application protocol) on the T5 interface between the MME / SGSN and the MTC-IWF may be provided based on the SCTP / IP or TCP / IP protocol.

For example, if a monitoring event for a device and a UICC association is established, the MME / SGSN can check whether it is associated with the configured IMEI and IMSI, and if not, .

When a monitoring event for the attachment point change is set, the MME / SGSN compares the location information with the configured location information, and when the location is changed, the MME / SGSN can include this information and transmit it to the monitoring function entity. When a mobility management procedure such as a network registration procedure occurs, information related to a location change can be transmitted to a monitoring function entity.

When a monitoring event related to a loss of connectivity (or a reachable notification request) is set, the UE includes such connectivity-related information when a predetermined period of time has elapsed after disconnecting the network, such as a network deregistration procedure, And forward it to the monitoring function entity. When receiving the connectivity loss information (or the reachable notification request), the monitoring functional entity can perform the UE Reachability procedure of 3GPP TS 23.401 through the HSS to be able to receive the reachability information of the UE. Alternatively, the monitoring functional entity may perform the monitoring procedure and perform the UE Reachability procedure through the HSS if the UE is not reachable. Alternatively, the monitoring function entity may perform the UE Reachability procedure through the HSS when requesting the reachability information of the UE through the SCS.

If the monitoring functional entity is MTC-IWF, the MTC-IWF can be informed of the UE reachability information through the HSS.

7 shows an example of a UE Reachability Notification Request Procedure.

Referring to FIG. 7, 1) the HSS transmits a UE-REACHABILITY-NOTIFICATION-REQUEST message (or a UE Reachability Request Prameter (hereinafter, referred to as " UE Activity Notification Request Request ") indicating that UE activity notification from the MME is requested by the HSS, URRP-MME).

If the monitoring functional entity receives connectivity loss information and / or if the UE is not reachable upon a monitoring request from the SCS server, and / or the monitoring functional entity sends an indication to the HSS about mobile network reachability information for the UE , And / or if the SCS requests an indication of mobile network reachability information for the UE, the HSS stores the information (or SCS information) of the monitoring functional entity and, to indicate that such a request has been received And sets the URRP-MME (UE Reachability Request Parameter for MME) parameter. If the URRP-MME parameter is changed from not set to set, the HSS sends a UE-Reachability-Notification-Request (URRP-MME) to the MME. If the MME has a Mobility Management (MM) context for the terminal, the MME sets the URRP-MME to indicate that it needs to report the change in UE reachability (eg, next NAS activity) to the HSS. 8 shows an example of a UE activity procedure.

Referring to FIG. 8, when an MME receives an indication of UE reachability (or UE activity) (e.g., an MME receive an indication from S GW that UE has handed over to a non-3GPP coverage), 2 ) If the MME has configured the URRP-MME to include the MM context of the UE and report that the UE is reachable, the MME sends a UE-Activity-Notification message to the HSS and removes the URRP-MME for the UE . The UE-Activity-Notification message includes IMSI and UE-Reachability information.

3) If the HSS receives a UE-activity-notification message or an Update Location message for the UE set by the URRP-MME, the HSS may trigger an appropriate notification to the monitoring functional entity (or SCS via the monitoring functional entity) URRP-MME can be removed.

Alternatively, information for monitoring event detection and reporting for UE monitoring in a mobile communication network may be configured or provided by a monitoring function entity. Activating monitoring of a specific event for UE monitoring in the mobile communication network may be provided by a monitoring functional entity. In this case, the information on the monitoring subscription information of the HSS or the monitoring event included in the monitoring subscription profile, the criterion related to monitoring, the action on the monitoring event, and the like may not be configured in the MME / SGSN through the subscriber data insertion procedure or the location update procedure have. The MME / SGSN may then enable monitoring for a particular event to provide monitoring for the UE by periodic or immediate request of the monitoring functional entity. In the above example, only a part of the information related to the monitoring subscription information of the HSS or the monitoring event included in the monitoring subscription profile, the criterion related to the monitoring, the action for the monitoring event, etc. is transmitted to the MME / SGSN through the subscriber data insertion procedure or the location update procedure . Or information about monitoring events included in the monitoring subscription information or monitoring subscription profile of the HSS, criteria related to monitoring, actions for monitoring events, etc., may be configured in the MTC-IWF. At this time, the interface between the MTC-IWF and the HSS can use the S6m interface. Or information related to the monitoring event included in the monitoring subscription information or the monitoring subscription profile of the HSS, the criterion related to the monitoring, the action for the monitoring event, etc., is not configured in the other network object but can be requested by the monitoring function entity have.

 Procedures for configuring monitoring event detection and reporting by MME / SGSN by a monitoring function entity, activating monitoring for a specific event, or requesting monitoring event detection and reporting, may be provided as follows.

1) The UE performs a network registration procedure.

2) In order to configure monitoring event detection and reporting, activating monitoring for a specific event, or requesting monitoring event detection and reporting, a monitoring functional entity may include a serving core node (CN) (Subscriber Information Request) message for retrieving the Node identifier. The subscriber information request message includes the identifier information of the UE to be monitored (MSISDN or local identifier @ external identifier in the form of a domain identifier or IMSI)

3) The HSS sends the subscriber information response (IMSI, serving node identifier, cause) message to the monitoring function entity.

4) The monitoring function entity configures monitoring event detection and reporting with the received serving MME / SGSN, activates monitoring for specific events, or requests monitoring event detection and reporting.

5) The MME / SGSN configures monitoring event detection and reporting, activates monitoring for specific events, or reports the results of monitoring event detection and reporting requests.

 If the monitoring function entity is MTC-IWF, the result report for configuring the monitoring event detection and reporting, activating monitoring for a specific event, or requesting monitoring event detection and reporting is provided by MTC-IWF and MME- RTI ID = 0.0 > / SGSN. ≪ / RTI >

 The monitoring function entity can configure monitoring event detection and reporting through HSS, activate monitoring for specific events, or request monitoring event detection and reporting. Procedures for configuring monitoring event detection and reporting via HSS, activating monitoring for specific events, or requesting monitoring event detection and reporting may be provided as follows.

1) The UE has performed a network registration procedure.

2) In order to configure monitoring event detection and reporting, activating monitoring for specific events, or requesting monitoring event detection and reporting, the monitoring function entity stores the identifier information (MSISDN or local identifier (External identifier in the form of a @ domain identifier or IMSI) to the HSS including the monitoring event detection activation information in the Subscriber Information Request message.

3) The HSS activates the monitoring of a specific event, configures the monitoring event detection and reporting, or performs the above-described Insert Subscriber Data Procedure or UE It performs monitoring event detection and reporting using a reachability procedure or location update procedure, activates monitoring for specific events, or performs procedures for monitoring event detection and responding to a reporting request.

4) The HSS reports the results of configuring monitoring event detection and reporting through subscriber information response messages, activating monitoring for specific events, or requesting monitoring event detection and reporting.

 If the monitoring function entity is the MTC IWF, the above-mentioned monitoring event detection activation request and the result report thereof can be provided through the S6m interface between the MTC IWF and the HSS.

The monitoring function entity can forward the monitoring result report received from other network entity to the monitoring server which is configured in the subscription information or requested monitoring. The monitoring server may be an MTC application server or service capability server, or may be any entity (e.g., a UE with a monitoring application) that interacts with a 3GPP network entity to obtain monitoring information.

 If the monitoring function entity is MTC IWF, the monitoring result report may be provided to the service capability server via the Tsp interface.

If the monitoring function entity fails to deliver the monitoring result report to the monitoring server, the monitoring function entity can deliver it to the SMS-SC.

Alternatively, if a monitoring functional entity fails to deliver a monitoring result report to the monitoring server, the monitoring functional entity may attempt to retransmit the stored monitoring functional entity after storing it. At this time, when the monitoring function entity receives a request message such as a monitoring request or a device trigger request from the monitoring server, an indicator for checking the retransmission of the monitoring result report may be placed. The indication may be removed when a retransmission is performed by receiving a request message such as a monitoring request or a device trigger request from the monitoring server.

Alternatively, the HSS may determine whether the HSS and / or the MME and / or the HSS are connected by the monitoring subscription information or the monitoring subscription profile change and / or by a monitoring request of the external server, or by a monitoring request of the MTC- The procedure between the MME and the UE and / or the interface between the MME and the MTC-IWF may be defined to inquire / confirm / acquire the monitoring result of the specific event.

FIG. 9 shows a monitoring procedure by a service capability server (SCS) according to an embodiment of the present invention.

The monitoring user may want to configure the monitoring action to be performed by the network, such as detection and reporting of monitoring events for monitoring a specific UE. The monitoring user may wish to activate monitoring of a specific event for the UE. The monitoring user may request monitoring to request an immediate monitoring information response to the UE. The monitoring user may also request monitoring that requires reporting of monitoring information thereon after a specific event has occurred in the UE. In this way, a monitoring function can be performed through the monitoring function entity for UE monitoring by the monitoring user.

9 illustrates a case where the monitoring server is a service capability server. However, the present invention is not limited to this, and the monitoring server may be an entity (e.g., a UE) including another application server or a monitoring application.

In FIG. 9, the monitoring function entity may be included in the MTC-IWF, may be an independent entity, or may be a functional entity of another network element.

1) The service capability server determines the UE to be monitored. If the SCS does not have access information for the MTC-IWF, the external identifier of the UE to be monitored can be used to determine the IP address / port of the MTC-IWF. The external identifier is an identifier other than the MSISDN, and consists of a domain identifier for identifying a domain under the control of a mobile network operator and a local identifier managed by a mobile network operator.

2) The service capability server sends a monitoring request message to the MTC-IWF.

The monitoring request message includes at least one of an external identifier or MSISDN, a service capability server identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, Payload), and monitoring event enable / disable discrimination information.

The monitoring event information may include at least one of the example information in Table 1 (e.g., a monitoring event for a UE, a reference related to monitoring, an action for a monitoring event, etc.). For example, location / area information or target area information that is allowed in the case of a monitoring event for an attachment point change.

Monitoring reference number information identifies specific monitoring requests in the monitoring functional entity or MTC-IWF and / or MME / SGSN, reports monitoring events by specific monitoring requests, and / or monitors monitoring events activated by a specific monitoring request Can be used to disable. The monitoring reference number information is used when the monitoring function object configures monitoring event detection and reporting on a network element of the mobile communication network, activates monitoring for a specific event, or requests monitoring and event detection and reporting, And can be delivered through the result report including this. The monitoring reference number information may uniquely identify the monitoring request together with the UE identifier.

The validity time indicates the time at which monitoring is performed at the serving node or at the network by the monitoring request or the time at which the monitoring request is stored. That is, the validity time indicates the time at which the monitoring request or monitoring response / report is stored at the serving node or in the network when the monitoring request by the monitoring service request by the service capability server is not processed.

The monitoring timer / period indicates the time period during which monitoring is performed at the serving node or in the network. When making settings related to the monitoring event to the HSS and / or the serving node, including the monitoring timer / period, the HSS and / or the serving node reports the results thereof at the end of the monitoring timer / period or every monitoring timer / .

Immediate monitoring indicates that a monitoring response is sent by performing an immediate detection of a monitoring request by the SCS server. If immediate monitoring / single monitoring attempt information is included, the HSS and / or the serving core node can inquire and respond to the result of the request for the monitoring event without setting the indication information that the specific monitoring event is activated. Alternatively, if the immediate monitoring / single monitoring attempt information is included, display information is set for the HSS and / or the serving core node to indicate that the specific monitoring event has been activated. If the result of the request for the specific monitoring event is inquired, Can be cleared and responded to. Alternatively, the immediate monitoring status may be sent to a specific information field, and the effective time may be set to 0 or a specific value may be assigned to the priority.

The monitoring event activation / deactivation classification information indicates information for discriminating whether the monitoring request is a request for activating monitoring or a request for deactivating active monitoring. When a specific monitoring event is activated or configured according to a monitoring request by the SCS server, the SCS server may request deactivation or release of the monitoring reference request including the UE identifier and / or the SCS identifier.

3) The MTC-IWF may authorize the service capability server to determine whether monitoring is allowed. In addition, the MTC-IWF may apply other control functions such as overload control and position information control. The MTC-IWF can check whether the SCS has exceeded the allowed monitoring submission or quota rate via the interface between the SCS and the MTC-IWF. The MTC-IWF or the HSS may be configured to determine the allowed location information (e.g., latitude / longitude, cell identifier, tracking) stored in the MTC-IWF or HSS, as determined by a mutual agreement between the MTC user and the mobile operator, (E.g., CGI, E-UTRAN Cell Global Identity), TAI, RAI, LAI, etc.) in the mobile communication network.

4) The MTC-IWF sends a subscriber information request message to the HSS to determine if the SCS server is authorized to perform monitoring for one or more UEs. And / or maps the UE's external identifier or MSISDN to the IMSI, or maps it to the IMSI list of individual devices belonging to the outer group identifier when using the outer group identifier. And / or extract the identifier of the serving core network node of the UE. In addition to the above, the MTC-IWF determines the specific monitoring event to be activated according to the monitoring request of the SCS and sends information to indicate monitoring activation for the event specific to the HSS, and the HSS displays the monitoring activation indication it is possible to set indicator information. The HSS may include an MTC-IWF identifier (or a monitoring functional entity identifier), an external identifier or an external group identifier or an MSISIDN or IMSI, an SCS identifier monitoring reference number, a validity time, a monitoring timer / ≪ / RTI > If an external group identifier is used, the above-described information can be set for each individual device included in the external group identifier.

5) The HSS sends the subscriber information response message (IMSI, serving node identifier, cause) to the MTC-IWF.

6) The MTC-IWF determines the monitoring procedure. In one example, the monitoring procedure may include configuring monitoring event detection and reporting to the MME / SGSN by the MTC-IWF via the T5 interface, activating monitoring for a specific event, or requesting monitoring event detection and reporting Procedure. In another example, the monitoring procedure may include configuring monitoring event detection and reporting to the MME-SGSN via the HSS by the MTC-IWF via the S6m interface, activating monitoring for specific events, or monitoring event detection and reporting For example.

Alternatively, the monitoring procedure is not determined by the MTC-IWF, but the monitoring procedure may be a predetermined procedure. In this case, six steps may be omitted.

A) and a monitoring procedure as determined in the MTC-IWF is performed. The monitoring procedure in step A will be described later.

7) The MTC-IWF sends the monitoring report to the service capability server.

If the MTC-IWF configures monitoring event detection and reporting to the MME / SGSN via the HSS, activates monitoring for specific events, or requests monitoring and event detection and reporting, 5 steps can be omitted or configured together with monitoring event detection and reporting via HSS, activating monitoring for specific events, or requesting monitoring event detection and reporting.

The monitoring method may be used in a monitoring method for a UE, i.e., an MTC device used for the MTC, and may also be used for a normal UE.

FIG. 10 shows a monitoring activation procedure or a monitoring procedure through the MTC-IWF or the monitoring function entity according to an embodiment of the present invention. 10 illustrates an exemplary embodiment of the monitoring procedure (step A) in FIG. 9 in detail. FIG. 10 illustrates an example in which the MTC-IWF transmits monitoring event detection and reporting to the MME- SGSN via the HSS via the S6m interface Activating monitoring for a specific event, or requesting monitoring event detection and reporting. If the procedure of FIG. 10 is performed, steps 4 and 5 for requesting and responding to subscriber information in FIG. 9 may be omitted.

The MTC-IWF can send a monitoring request message to the HSS by determining the specific monitoring event to be activated according to the monitoring request of the SCS. The message may include an external identifier or an external group identifier or MSISIDN, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, instant monitoring / single monitoring attempt, monitoring event information, Disable discrimination information, an MTC-IWF identifier (or a monitoring function entity identifier), and the like. The message may include indicator information (or a flag) for setting activation or deactivation for each specific monitoring event. For example, activating a monitoring event for an attachment point change can provide separate indication information for activating the monitoring event for connectivity loss and activating the monitoring event. Alternatively, the message may include indicator information for setting activation or deactivation for a plurality of specific monitoring events. The message may utilize a subscriber information request message on the S6m interface between the MTC-IWF and the HSS or define a new request message. The monitoring reference number may be a reference received by the SCS server. Alternatively, the monitoring reference number is mapped to a reference number received by the SCS server and may be a monitoring reference number generated by the MTC-IWF. Alternatively, it does not include the monitoring reference number if it includes indicator information (or a flag) for setting activation or deactivation on a specific monitoring event basis.

1) Upon receiving the request message, the HSS sets monitoring activation indicator information (or flag) for an event specific to the HSS to indicate that monitoring is activated for a specific event. Then, the HSS sends a monitoring request message to the MME.

The HSS may include an MTC-IWF identifier (or a monitoring functional entity identifier), an external identifier or an external group identifier or an MSISIDN or IMSI, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / , Immediate monitoring / single monitoring attempt information. If an external group identifier is used, the information can be set for each individual device included in the external group identifier. If the monitoring activation indication for the specific event is changed from not set to set, or if it is received including the immediate monitoring / single monitoring attempt information, the HSS notifies the specific event monitoring to the serving node (UE Reachability Request) information on the IDR-flag of 3GPP TS 29.272, the indication information for activating the monitoring through the Insert Subscriber Data Request for forwarding or setting to the MME, An EPS user state request, an EPS location information request, a recent location information request, a location information request, It can be sent to the MME by setting one or more of the Requests (Current Location Request) flags.

If the MME has a Mobility Management (MME) context for the UE, the MME may set the flag to indicate the indication to activate the monitoring and / or set a specific monitoring event (e.g., next NAS activity) Or when a monitoring event is detected, it is necessary to report it to the HSS.

And / or if the MME receives indication information (or a flag) corresponding to the IDR-flag or IDR-flag, for example, if the recent location information request bit is set and the UE is in idle mode, So that the latest user information can be collected. If the latest location information request bit is set and the UE is in a connected mode, the MME sends an S1AP Location Reporting Control procedure to the eNodeB before reporting to return the cell information of the most recent UE. (E-UTRAN Cell Global Identification) information. As another example, if the last radio access timestamp information request bit is set and the UE is in an attach state. The MME may return the UE's most recent radio contact timestamp. If the EPS user status request bit and / or the EPS position information bit are set, the MME returns the corresponding user information to the HSS.

 (For example, an S1AP position reporting control procedure and / or an ME identity check procedure) for detecting the monitoring event without setting the indication information for activating the monitoring, ). ≪ / RTI > Alternatively, if the current monitoring / single monitoring attempt information is included, the indication information for activating the monitoring may be set and a procedure or message related to the specific monitoring event (e.g., next NAS activity, UE reachability change Related message, TAU, LAU, Handover, etc.), the display information for activating the monitoring can be removed.

After receiving the monitoring request message from the serving node or receiving the confirmation message for the monitoring request from the MTC-IWF or setting the indication information for the monitoring event, the serving node or the MTC-IWF sends a Charging Data Record (CDR) ) ≪ / RTI > information. The billing information may include an IMSI and / or MSISDN or an external identifier, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, The activation / deactivation discrimination information, the start time of the monitoring request, the time at which the processing for the monitoring event is started, and the time at which the information related to the monitoring event is transmitted

1) The MME can send a request message to the UE when it is necessary to forward a request message to the UE to check a specific monitoring event via the UE. For example, if the MME receives an indication through the HSS to activate the monitoring event for the device and the UICC association, the MME may receive the IMEI of the UE using the ME identity check procedure specified in 3GPP TS 23.401. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME can check whether the IMEI received from the UE via the EIR is associated with the IMEI stored in the EIR and report the result thereof.

FIG. 11 shows a monitoring activation procedure or a monitoring procedure through the MTC-IWF or the monitoring function entity through the serving node direct interface according to an embodiment of the present invention. That is, Fig. 11 details one embodiment of the monitoring procedure (step A) in Fig.

FIG. 11 illustrates an example in which the MTC-IWF configures monitoring event detection and reporting to a serving node (e.g., MME / SGSN) via a T5 interface, activates monitoring for a specific event, ≪ / RTI >

1) The MTC-IWF sends a monitoring request message to the serving node. The message may include information for indicating that monitoring has been activated for a particular event, an MTC-IWF identifier (or a monitoring functional entity identifier), an IMSI, a monitoring reference number, a validity time, a monitoring timer / Sends one or more of the monitoring / single monitoring attempt information together. And / or the MTC-IWF may include a UE Reachability Request, a UE's last wireless connection timestamp information request, an EPS User State Request, an EPS Location Information Request ), A current location request, and a UE location change information request flag (e.g., UE Info Change Reporting Action) flag information to the MME.

If the MME has a Mobility Management (MME) context for the UE, the MME may set the flag and / or the indication information to activate the specific monitoring and / or change the UE reachability (e.g., next NAS activity) When receiving a message related to an event or detecting a monitoring event, it indicates that it needs to be reported to the MTC-IWF (or to the SCS via HSS or MTC-IWF).

And / or if the MME has received the flag, e.g., if the recent location information request bit is set and the UE is in idle mode, the MME may page the UE to collect the most up-to-date user information. If the latest location information request bit is set and the UE is in a connected mode, the MME sends an S1AP Location Reporting Control procedure to the eNodeB before reporting to return the cell information of the most recent UE. (E-UTRAN Cell Global Identification) information. As another example, if the last radio access timestamp information request bit is set and the UE is in an attach state. The MME may return the UE's most recent radio contact timestamp. If the EPS user status request bit and / or the EPS position information bit are set, the MME returns the corresponding user information to the MTC-IWF (or to the SCS via the HSS or MTC-IWF). If the terminal location change information request flag bit is set, information (ECGI) is returned whenever the terminal location information change occurs.

(For example, an S1AP position reporting control procedure and / or an ME identity check procedure) for detecting the monitoring event without setting the indication information for activating the monitoring, ). ≪ / RTI > Alternatively, if the current monitoring / single monitoring attempt information is included, the indication information for activating the monitoring may be set and a procedure or message related to the specific monitoring event (e.g., next NAS activity, UE reachability change Related message, TAU, LAU, Handover, etc.), the display information for activating the monitoring can be removed.

After receiving the monitoring request message from the serving node or receiving the confirmation message for the monitoring request from the MTC-IWF or setting the indication information for the monitoring event, the serving node or the MTC-IWF sends a Charging Data Record (CDR) ) ≪ / RTI > information. The billing information may include an IMSI and / or MSISDN or an external identifier, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, The activation / deactivation discrimination information, the start time of the monitoring request, the time at which the processing for the monitoring event is started, and the time at which the information related to the monitoring event is transmitted

2) The MME may send a request message to the UE when it is necessary to forward a request message to the UE to check a specific monitoring event via the UE. For example, if the MME receives an indication through the HSS to activate the monitoring event for the device and the UICC association, the MME may receive the IMEI of the UE using the ME identity check procedure specified in 3GPP TS 23.401. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME can check whether the IMEI received from the UE via the EIR is associated with the IMEI stored in the EIR and report the result thereof.

12 shows a monitoring procedure via the HSS in a specific monitoring event activation state in the serving node according to the present invention.

1) The MME receives a message according to procedures (e.g. attach, TAU) and / or procedures (e.g., downlink notification, UE has handed over to non-3GPP coverage) by the SGW. Or the UE is reachable by the procedure.

2) If the message is received according to the procedure by the UE and / or the procedure by the SGW as in step 1 and the information for indicating that the monitoring is activated for an event specific to the MME is set, the MME transmits information related to the specific monitoring event To the HSS. The message may use a Notify Request message, an Insert Subscriber Data Answer message, and / or an Update Location Update message. The MME may execute a specific procedure with the UE or other network entity (e.g., EIR) to check information related to a particular monitoring event, if desired.

For example, when the display information for activating the monitoring event for the attachment point change and / or the display information for activating the monitoring event for the connectivity loss is set, the NAS procedure (e.g., Attach, detach, TAU), it is possible to always send information on the location and / or reachability of the UE to the HSS. The update location update message, the notify request message, and / or the insert subscriber data answer message include a flag (for example, ULR-flag, IDA-flag, NOR-flag) . If necessary, the MME may inquire the E-UTRAN Cell Global Identification (ECGI) information using the S1AP Location Reporting Control procedure (S1AP) with the eNodeB before reporting to return the cell information of the most recent UE Or the eNodeB may always perform the NAS procedure including the eECGI information. As another example, if an indication is set to activate the monitoring event for the device and the UICC association in the MME, the MME can receive the IMEI of the UE using the ME identity check procedure specified in 5.3.10.5 of 3GPP TS 23.401. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME can check whether the IMEI received from the UE via the EIR is associated with the IMEI stored in the EIR and report the result thereof. Even when the monitoring result is reported, it may not remove the set information to indicate that monitoring is activated for the specific event. Alternatively, if the monitoring result is reported in a specific case (for example, a single monitoring attempt request and / or a monitoring timer / period end, a deactivation request), the setting information is removed to indicate that monitoring is activated for the specific event can do.

3) When the HSS receives information related to a specific monitoring event from the MME, it can report it to the MTC-IWF. The HSS may include a flag (e.g., ULR-flag, IDA-flag, NOR-flag) indicating that the notification is a specific monitoring event in the Update location update message and / or Notify Request message and / To be reported to the MTC-IWF through the monitoring active indicator for specific events set in the HSS and / or to the MTC-IWF. Even when the monitoring result is reported, it may not remove the set information to indicate that monitoring is activated for the specific event. Alternatively, if the monitoring result is reported in a specific case (for example, a single monitoring attempt request, a monitoring timer / period end, a deactivation request), the setting information may be removed to indicate that monitoring has been activated for the specific event have.

Thereafter, the MTC-IWF performs step 7 of FIG. That is, the MTC-IWF provides the received monitoring results to the SCS. In this case, the MTC-IWF can perform mapping of monitoring events and details to be reported to the SCS from the received monitoring results. For example, if a monitoring event for connectivity loss is requested by the SCS, the MTC-IWF continues to receive information (eg, attach, TAU, detach) related to the monitoring event received from the HSS, If the information related to the monitoring event is not received for a certain period of time after receiving the information related to the event, it can be provided to the SCS server that the connectivity loss has occurred.

The MTC-IWF and / or MME may generate Charging Data Record (CDR) information before or after reporting the monitoring results. The billing information may include an IMSI and / or MSISDN or an external identifier, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, The activation / deactivation discrimination information, the start time of the monitoring request, the time at which the processing for the monitoring event is started, and the time at which the information related to the monitoring event is transmitted

FIG. 13 shows a monitoring procedure through a direct interface with the MTC-IWF in a specific monitoring event activation state in the serving node according to the present invention.

1) is the same as step 1 in FIG.

2) If the procedure for the UE and / or the message for the SGW procedure is received and the information for indicating that the monitoring is activated for an event specific to the MME is set as in step 1, the MME sets the information related to the specific monitoring event To the MTC-IWF. The message may be provided via the T5 interface between the MME and the MTC-IWF. The MME may execute a specific procedure with the UE or other network entity (e.g., EIR) to check information related to a particular monitoring event, if desired.

For example, when the indication information for activating the monitoring event for the attachment point change and / or the indication information for activating the monitoring event for the connectivity loss is set, the NAS procedure (e.g. Attach, detach, TAU), it is possible to always send information on the location and / or reachability of the UE to the MTC-IWF. If necessary, the MME may inquire the E-UTRAN Cell Global Identification (ECGI) information using the S1AP Location Reporting Control procedure (S1AP) with the eNodeB before reporting to return the cell information of the most recent UE It is possible to always carry out the NAS procedure including the ECGI information. As another example, if an indication is set to activate the monitoring event for the device and the UICC association in the MME, the MME can receive the IMEI of the UE using the ME identity check procedure specified in 5.3.10.5 of 3GPP TS 23.401. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME can check whether the IMEI received from the UE via the EIR is associated with the IMEI stored in the EIR and report the result thereof. Even when the monitoring result is reported, it may not remove the set information to indicate that monitoring is activated for the specific event. Alternatively, if the monitoring result is reported in a specific case (for example, a single monitoring attempt request and / or a monitoring timer / period end, a deactivation request), the setting information is removed to indicate that monitoring is activated for the specific event can do.

Thereafter, the MTC-IWF performs step 7 of FIG. That is, the MTC-IWF provides the received monitoring results to the SCS. In this case, the MTC-IWF can perform mapping of monitoring events and details to be reported to the SCS from the received monitoring results. For example, when a monitoring event for connectivity loss is requested by the SCS, the MTC-IWF keeps receiving information (eg, attach, TAU, detach) related to the monitoring event received from the MME, If the information related to the monitoring event is not received for a certain period of time after receiving the information related to the event, it can be provided to the SCS server that the connectivity loss has occurred.

The MTC-IWF and / or MME may generate Charging Data Record (CDR) information before or after reporting the monitoring results. The billing information may include an IMSI and / or MSISDN or an external identifier, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, priority, The activation / deactivation discrimination information, the start time of the monitoring request, the time at which the processing for the monitoring event is started, and the time at which the information related to the monitoring event is transmitted

Next, the control operation of the serving node will be described.

 During the network attach and tracking area updater (TAU) procedure, the UE and the MME may exchange information about the monitoring support capability of the MME. And / or the MME may obtain information from the HSS indicating that a particular monitoring event has been activated. As a result, the MME may perform an MME redirection procedure such as Multiple Operator Core Network (MOCN) to allow the UE to register with the MME supporting monitoring.

Alternatively, during an MME overload situation or when the MME is in a normal NAS level mobility management congestion control or an APN based mobility management congestion control The MME performs an MME redirection procedure such as Multiple Operator Core Network (MOCN) to determine whether the UE is in an MME that has not been overloaded Registration can be made.

Alternatively, during an MME overload situation or when the MME is in a normal NAS level mobility management congestion control or an APN based mobility management congestion control (Active) / when it is desired to activate a specific monitoring event via HSS or MTC-IWF, or to configure monitoring, the MME shall inform the HSS or MTC-IWF if it is configured to do so. Reject the monitoring request, and / or reduce the signaling load that the MME generates. The reject may include a cause value and / or a backoff timer to indicate that the network congestion failed the trigger.

The monitoring event processing method may be used for a monitoring method for a UE used for MTC, i.e., an MTC device, or for a normal UE.

FIG. 14 is a block diagram showing a configuration of an MTC-IWF according to an embodiment of the present invention.

14, the MTC-IWF 1400 includes an SCS communication unit 1410 for communicating with the SCS, an HSS communication unit 1420 for communicating with the HSS, a serving node communication unit 1410 for communicating with the serving node (for example, MME / SGSN) (1430), and a control unit (1440).

The SCS communication unit 1410 may receive a monitoring request message from the SCS when it is desired to configure a monitoring action to be performed by the network such as detection and reporting of a monitoring event for monitoring a specific UE. The monitoring request message includes at least one of an external identifier or an MSISDN, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / cycle, a priority, an immediate monitoring / single monitoring attempt request, monitoring event information, And may include one piece of information.

The control unit 1440 can authorize whether monitoring by the SCS is allowed. In addition, the controller 1420 may perform other control functions such as overload control and position information control.

In addition, the control unit 1440 can determine whether the SCS is authorized to perform monitoring for the UE. To this end, the HSS communication unit 1420 can inquire subscriber information to the HSS. Meanwhile, as described later, when the monitoring event detection and reporting is configured or requested to the serving node through the HSS through the S6m interface or the monitoring is activated, the subscriber information inquiry to the HSS can be omitted.

In addition, the control unit 1440 can determine the monitoring procedure.

In one example, the monitoring procedure may be a procedure for configuring or requesting monitoring event detection and reporting directly from the MTC-IWF to the serving node via the T5 interface, or for activating monitoring. In this case, the serving node communication unit 1230 can transmit a monitoring request message to the serving node.

In another example, the monitoring procedure may be a procedure for configuring or requesting monitoring event detection and reporting from the MTC-IWF through the HSS to the serving node via the S6m interface, or for activating monitoring. In this case, the HSS communication unit 1420 can transmit a monitoring request message to the HSS.

The monitoring request message transmitted from the MTC-IWF 1400 to the HSS or the serving node includes an external identifier or an external group identifier or an MSISDN, an SCS identifier, a monitoring reference number, an effective time, a monitoring timer / A monitoring event information, a monitoring event activation / deactivation identification information, and an MTC-IWF identifier. In addition, the monitoring request message may set a user's UE reachability request, a UE's last wireless connection timestamp information request, an EPS user status information request, an EPS position information request, and a recent location information request flag.

As described above, according to the present invention, a monitoring function entity in a 3GPP mobile communication network monitors the association of the device with a UICC, a change in the point of attachment, and loss of connectivity In order to activate or deactivate monitoring of one or more devices at an external server according to a user's request, the serving node only provides a function of providing information for detection of a specific monitoring event Monitoring function, MTC-IWF, and / or HSS to monitor, report, authenticate, charge, and other control functions, thereby reducing the complexity of the serving node and providing information related to the monitoring event of the terminal in the mobile communication network The effect can be effectively processed and reported.

Claims (18)

Receiving a monitoring request message from a service capability server (SCS);
Authenticating whether the SCS is authorized to send the monitoring request message;
Determining whether the SCS exceeds an allowed monitoring submission amount or rate;
Inquiring the HSS (Home Subscriber Server) to confirm whether the SCS has the right to perform monitoring for a specific terminal; And
Determining a monitoring event to the serving node and transmitting a monitoring request message to the serving node. The method according to claim 1,
Wherein the monitoring request message received from the SCS includes at least one of an external identifier, an MSISDN, a monitoring event activation / deactivation classification information, a monitoring reference number, a priority, and monitoring event information. The method according to claim 1,
Wherein the HSS configures a monitoring event as a part of terminal subscription data. The method according to claim 1,
Wherein the serving node sets monitoring indication information in the terminal context. Receiving information related to a monitoring event from a serving node; And
And transmitting a monitoring result report to a Service Capability Server (SCS) requesting the monitoring event. 6. The method of claim 5,
Wherein the serving node includes information of the SCS requesting the monitoring event. 6. The method of claim 5,
Wherein the serving node comprises MTC-IWF information included in the subscription data of the HSS. 6. The method of claim 5,
And generating billing information based on the monitoring result report. An SCS communication unit for receiving a monitoring request message from a Service Capability Server (SCS);
A control unit for authorizing whether the SCS is authorized to send the monitoring request message and for determining whether the SCS exceeds the allowed monitoring submission amount or rate;
An HSS communication unit for inquiring an HSS (Home Subscriber Server) to authenticate whether the SCS is authorized to perform monitoring for a specific terminal; And
And a serving node communication unit for determining a monitoring event to the serving node and transmitting a monitoring request message. 10. The method of claim 9,
Wherein the monitoring request message received from the SCS includes at least one of an external identifier, an MSISDN, a monitoring event activation / deactivation classification information, a monitoring reference number, a priority, and monitoring event information. A serving node communication unit for receiving information related to the monitoring event from the serving node; And
And a SCS communication unit for transmitting a monitoring result report to a Service Capability Server (SCS) requesting the monitoring event. 12. The method of claim 11,
Wherein the serving node includes information of the SCS requesting the monitoring event. Receiving a monitoring request message from a service capability server (SCS);
Authenticating whether the SCS is authorized to send the monitoring request message;
Determining whether the SCS exceeds an allowed monitoring submission amount or rate;
And transmitting a monitoring request message to the home subscriber server (HSS). 14. The method of claim 13,
Wherein the monitoring request message received from the SCS includes at least one of an external identifier, an MSISDN, a monitoring event activation / deactivation classification information, a monitoring reference number, a priority, and monitoring event information. 14. The method of claim 13,
Wherein the HSS stores the SCS identifier received from the MTC-IWF. 14. The method of claim 13,
Wherein the HSS configures a monitoring event in a serving node using a subscriber insertion procedure. Receiving information on a monitoring event received from the serving node via the HSS; And
And transmitting a monitoring result report to a Service Capability Server (SCS) requesting the monitoring event. Receiving a monitoring request message for reachable from a service capability server (SCS);
Transmitting a message instructing the HSS (Home Subscriber Server) to inform the terminal reachable;
Receiving notification that the terminal is reachable from the HSS when the terminal becomes reachable;
And forwarding the terminal reachability to the SCS.

Images