[go: up one dir, main page]

WO2013165168A1 - Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile - Google Patents

Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile Download PDF

Info

Publication number
WO2013165168A1
WO2013165168A1 PCT/KR2013/003758 KR2013003758W WO2013165168A1 WO 2013165168 A1 WO2013165168 A1 WO 2013165168A1 KR 2013003758 W KR2013003758 W KR 2013003758W WO 2013165168 A1 WO2013165168 A1 WO 2013165168A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
information
scs
event
hss
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2013/003758
Other languages
English (en)
Korean (ko)
Inventor
홍성표
김현표
정성한
최우진
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KT Corp
Original Assignee
KT Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020120143964A external-priority patent/KR101873068B1/ko
Application filed by KT Corp filed Critical KT Corp
Publication of WO2013165168A1 publication Critical patent/WO2013165168A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present invention relates to a user equipment used for machine type communication (UE), a general UE, and a method and apparatus for monitoring a user or subscription related event through a mobile communication network.
  • UE machine type communication
  • general UE a user equipment used for machine type communication
  • mobile communication network a mobile communication network
  • Machine type communication 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.
  • UEs used for MTC may be installed in a location that is concerned about the theft or damage of the communication module. It also monitors the Universal Integrated Circuit Card (UICC) association of the Device and UICC, change in the point of attachment, and loss of connectivity, periodically or at the user's needs. This may be necessary.
  • UICC Universal Integrated Circuit Card
  • a technology for detecting an event occurring in an MTC device that may be caused by the theft or damage of a communication module in a mobile communication network and reporting the event when an event is detected may be required.
  • the mobile communication network to the current through the (e. G., A mobile communication network according to the 3GPP (3 rd Generation Partnership Project) ) to the monitoring of received UE, and to detect the particular monitoring event by the monitoring application in the UE, a specific monitoring It was only possible to report a specific monitoring event to the application server when an event was detected. In other words, only the reporting of monitoring events through the application layer was possible.
  • the network entity does not support monitoring for detecting and reporting a specific event occurring in the UE. Therefore, monitoring information about events such as association of the Device and UICC, change in the point of attachment, and loss of connectivity that users can view through network objects There was a problem that could not be utilized.
  • the serving node For monitoring, in activating or deactivating monitoring of one or more devices in an external server, the serving node provides only the function of providing information for detection of a specific monitoring event and the monitoring function object or MTC. It aims to provide specific procedures for handling monitoring detection, reporting, authentication, billing and other control functions through IWF and / or HSS.
  • a terminal monitoring method executed in an entity relaying a signaling protocol in a mobile communication network, the method comprising: receiving a monitoring request message from an SCS (Service Capability Server); Authorizing whether the SCS is authorized to send the monitoring request message; Determining whether a monitoring request message from the SCS has exceeded an allowable monitoring submission rate or rate; Querying a home subscriber server (HSS) to authorize whether the SCS is authorized to perform monitoring on a specific terminal; Determining a monitoring event to the serving node and transmitting a monitoring request message; Receiving information related to a monitoring event from the serving node; And transmitting a monitoring result report to the SCS requesting the monitoring event.
  • SCS Service Capability Server
  • HSS home subscriber server
  • an apparatus for relaying a signaling protocol in a mobile communication network may include: an SCS communication unit configured to receive a monitoring request message from an SCS (Service Capability Server); A control unit for authorizing whether the SCS is authorized to send the monitoring request message and determining whether the monitoring request message from the SCS exceeds an allowable monitoring submission rate or rate; An HSS communication unit for inquiring a Home Subscriber Server (HSS) to authorize whether the SCS is authorized to perform monitoring on a specific terminal; And a serving node communication unit configured to determine a monitoring event to a serving node and transmit a monitoring request message, wherein the serving node communication unit receives information related to the monitoring event from the serving node, and the SCS communication unit requests the monitoring event. It provides a relay server, characterized in that for transmitting a monitoring result report.
  • SCS Service Capability Server
  • a control unit for authorizing whether the SCS is authorized to send the monitoring request message and determining whether the monitoring request message from the SCS exceeds an allowable monitoring submission rate or rate
  • Another embodiment of the present invention is a terminal monitoring method executed in an entity relaying a signaling protocol in a mobile communication network, the method comprising: receiving a monitoring request message from a service capability server (SCS); Authorizing whether the SCS is authorized to send the monitoring request message; Determining whether a monitoring request message from the SCS has exceeded an allowable monitoring submission rate or rate; Transmitting a monitoring request message to a home subscriber server (HSS); Receiving information on the monitoring event received from a serving node via the HSS; And transmitting a monitoring result report to the SCS requesting the monitoring event.
  • SCS service capability server
  • HSS home subscriber server
  • a specific method for monitoring the association of the Device and UICC, change in the point of attachment, loss of connectivity, etc. in a mobile communication network Can provide.
  • 1 shows a 3GPP structure for MTC.
  • FIG. 2 illustrates a network structure including a monitoring sensing function entity and a monitoring reporting function entity according to an embodiment of the present invention.
  • FIG. 3 shows a network structure for reporting by MTC IWF according to an embodiment of the present invention.
  • FIG. 4 illustrates a network structure including a monitoring function entity according to an embodiment of the present invention.
  • FIG. 5 shows a monitoring service providing network structure by MTC-IWF according to an embodiment of the present invention.
  • FIG. 6 shows a monitoring service providing network structure by an MTC-IWF and a monitoring function object according to an embodiment of the present invention.
  • FIG. 7 shows an example of a UE Reachability Notification Request Procedure.
  • FIG. 8 shows an example of a UE activity procedure.
  • FIG 9 illustrates a monitoring activation procedure or monitoring procedure via the MTC-IWF or monitoring functional entity in the SCS according to an embodiment of the present invention.
  • FIG. 10 illustrates a monitoring activation procedure or a monitoring procedure of an MTC-IWF or a monitoring functional entity through an HSS interface according to an embodiment of the present invention.
  • FIG. 11 illustrates a monitoring activation procedure or monitoring procedure via an MTC-IWF or a monitoring functional entity via a serving node direct interface (T5 interface) according to an embodiment of the present invention.
  • FIG. 12 illustrates a monitoring procedure via the HSS in a specific monitoring event activation state at a serving node according to an embodiment of the present invention.
  • FIG. 13 illustrates a monitoring procedure via a direct interface to the MTC-IWF in a specific monitoring event activation state in a serving node according to an 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.
  • Machine type communication 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.
  • UE User Equipment: a mobile communication terminal, the UE can host one or more MTC applications or monitoring applications,
  • RAN Radio Access Network
  • Wireless Access Network Wireless Access Network
  • MSC Mobile Switching Center
  • SGSN Packet Switching based Mobile Switch that performs Mobility Management
  • Gateway GPRS Support Node An entity that provides interworking between a GPRS network and an external packet switched network.
  • Mobility Management Entity An entity on a control plane to support mobility management function in an Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • -S-GW Serving Gateway: Gateway that terminates the interface with E-UTRAN
  • PDN Gateway Gateway that terminates the interface with PDN
  • SCS Service Capability Server
  • HPLMN Home Public Land Mobile Network
  • SMS-SC Short Message Service-Service Center
  • HSS Home Subscriber Server
  • MTC-IWF InterWorking Function
  • Tsp reference point for control plane signaling between SCS and MTC IWF
  • 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
  • End-to-end communication between the MTC application in a mobile communication terminal (UE) and the MTC application in an application server (AS) in an external network of a mobile communication network is performed by a 3GPP system and a service capability server (SCS). Service is provided by the server.
  • the direct model represents the model in which the AS connects directly to the operator network without using SCS to perform user plane communication with the UE.
  • Indirect Model refers to a model in which an AS connects indirectly with an operator's network through a service of an SCS in order to perform indirect user plane communication with a UE or to use an additional service such as device triggering.
  • Hybrid model represents the simultaneous use of direct and indirect models between AS and UE.
  • Monitoring may be provided on a subscription basis.
  • the monitoring subscription or monitoring subscription profile may be configured in the HSS and / or MTC-IWF as part of the UE subscription.
  • Information that can be configured in the HSS and / or MTC-IWF includes monitoring events for the UE, criteria related to monitoring (eg, allowed IMEI list, allowed location list), actions according to monitoring event detection, specific to the UE.
  • the HSS may include information about whether monitoring is allowed by a request of a specific monitoring server at the UE.
  • monitoring server information allowed for the UE eg, server identifiers allowed for identifiers of individual devices
  • monitoring server information allowed for one or more UEs eg, server identifiers allowed for identifiers of group devices.
  • mapping information of the group identifier and the individual identifier may be an MTC application server or an SCS server, or may be any entity that interacts with a 3GPP network entity (eg, a UE with a monitoring application) to obtain monitoring information.
  • monitoring events and related criteria such as Table 1 may be configured in the HSS.
  • Table 1 Examples of monitoring events, related criteria, and monitoring event actions
  • Monitoring events standard action UE / device and UICC connection Mapping between International Mobile Subscriber Identity (IMSI) and International Mobile Equipment Identity (IMEI) allowed Reporting, restrict access of the UE Alignment of UE features
  • the subscription information includes NAS signaling low priority indication when the network is actually connected when the UE is set to NAS signaling low priority.
  • NAS signaling low priority indication when the network is actually connected when the UE is set to NAS signaling low priority.
  • Allowed geolocation Reporting Loss of connectivity Network Detach when the time that the network connection (e.g. attach, TAU) does not occur from the last UE activity time exceeds a certain time Reporting, restrict access of the UE
  • monitoring subscription or monitoring subscription profile may be subscription information related to a monitoring server or monitoring user who wants 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 (eg, a UE with a monitoring application) to obtain monitoring information.
  • the monitoring user may be a user who wants to obtain monitoring information about one or more UEs through the monitoring server.
  • Subscription information related to the monitoring server or monitoring user may include a monitoring server identifier, an allowed monitoring request type, an allowed monitoring event, a criterion related to monitoring, an action on a monitoring event, an amount or rate of allowed monitoring requests.
  • 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 eg IMSI, MSISDN, Local Identifier @ Domain. It may include one or more information from the list of external identifiers in the form of identifiers.
  • Subscription information related to the monitoring server or monitoring user may be configured in the HSS as part of the UE subscription information.
  • the monitoring server or monitoring user subscription information may be configured in the HSS as group subscription information.
  • the monitoring server or the monitoring user subscription information may be configured or stored in the monitoring function entity or MTC-IWF according to the present invention.
  • detection and reporting of the monitoring event may be provided through a network element of the mobile communication network.
  • the detection of monitoring events may be provided via MME / SGSN or via HSS.
  • monitoring event reporting can be provided via MME / SGSN or via HSS.
  • Detection and reporting of the monitoring events in a Public Land Mobile Network is a new functional entity that is responsible for detecting monitoring events in a mobile network. It can be provided through a monitoring detection function, which is an entity, and a monitoring reporting function, which is a new function entity responsible for reporting on monitoring events in a mobile communication network.
  • the monitoring detection function and the monitoring reporting function may exist as one or more instances in a mobile communication network (PLMN).
  • the monitoring detection function and the monitoring function may be standalone entities or may be functional entities of another network element.
  • FIG. 2 illustrates a network structure including a monitoring sensing function entity and a monitoring reporting function entity according to an embodiment of the present invention.
  • the monitoring reporting function may be provided through an MTC-IWF (InterWorking Function).
  • the monitoring reporting function may be provided as a function object of the MTC-IWF.
  • the monitoring reporting function may be provided as part of the MTC-IWF.
  • the monitoring detection function may be a standalone entity and may be provided as a functional entity of the MME / SGSN or the HSS.
  • FIG. 3 shows a network structure for reporting by MTC IWF according to an embodiment of the present invention.
  • Detection and reporting of the monitoring event in the Public Land Mobile Network is provided through a new functional entity that is responsible for detecting and reporting the monitoring event in the mobile network.
  • a function for monitoring a UE in a mobile communication network such as a sensing function for a monitoring event and a reporting function, may be provided through a single monitoring function entity.
  • the monitoring function may activate monitoring for a particular event.
  • the monitoring function may exist as one or more instances in a PLMN. This monitoring function may be a standalone entity or may be a functional entity of another network element.
  • FIG. 4 illustrates a network structure including a monitoring function entity according to an embodiment of the present invention.
  • the monitoring function may be provided through an MTC-IWF (InterWorking Function).
  • MTC-IWF InterWorking Function
  • the monitoring function may be provided included as a function object of the MTC-IWF.
  • the monitoring function may be provided as part of the MTC-IWF.
  • FIG. 5 shows a monitoring service providing network structure by MTC-IWF according to an embodiment of the present invention.
  • the monitoring user may configure an action to be executed by the network, such as sensing or reporting on a monitoring event, for monitoring for a specific UE.
  • the monitoring user may also activate monitoring for specific events.
  • the monitoring user may configure an action to be executed by the network through the MTC-IWF in the network structure of FIG. 5 or activate monitoring for a specific event.
  • the monitoring user may request monitoring that requires an immediate monitoring information response to the UE.
  • the monitoring user may also request monitoring that requires monitoring information response to a particular event after it occurs in the UE.
  • the monitoring function may be performed through the monitoring function entity for monitoring the UE by the monitoring user.
  • the TSP interface between the MTC-IWF and the SCS server is used to process the monitoring request message, and the monitoring function (activating) for specific monitoring events, the detection of monitoring events, and the reporting of monitoring events are reported.
  • the functions required for monitoring can also be provided through monitoring function entities.
  • FIG. 6 shows a monitoring service providing network structure by an MTC-IWF and a monitoring function object according to an embodiment of the present invention.
  • a new function may be implemented or a new procedure may be provided to support monitoring event detection and reporting in the MME / SGSN.
  • the HSS is subject to specific events to the HSS and / or to the MME / SGSN according to the monitoring subscription information or monitoring subscription profile change and / or by the monitoring request of the external server or by the monitoring request of the MTC-IWF that receives the monitoring request of the external server. It is possible to activate or deactivate monitoring for a specific event by setting indicator information for monitoring for.
  • HSS's monitoring subscriptions or monitoring subscription profiles allow the HSS to configure monitoring-related information in the MME / SGSN or to activate monitoring for specific events.
  • subscriber information in the HSS eg, a change of subscription profile, attach, TAU
  • the HSS is stored in the MME / SGSN using an Insert Subscriber Data Procedure or an Update location procedure.
  • Monitoring-related information can be configured in the MME / SGSN by allowing subscription data to be modified.
  • the HSS may configure monitoring related information in the MME / SGSN by using an Insert Subscriber Data Procedure or an Update Location Procedure.
  • the HSS may activate monitoring for an event specific to the MME / SGSN by using an Insert Subscriber Data Procedure or an Update Location Procedure.
  • the HSS may send IMSI and monitoring subscription data to the MME / SGSN by including the IMSI and monitoring subscription data in the Insert Subscriber Data Request or Update Location Request message.
  • the monitoring subscription data may include a monitoring event for a UE, a criterion related to monitoring, an action for a monitoring event, and the like.
  • the subscription data may include identification information of a monitoring function entity to report detected monitoring event information when an event is detected.
  • the SGSN / MME may transmit the detected monitoring event information to the monitoring function entity.
  • the monitoring event information may be provided through a T5 interface between the MTC-IWF and the MME / SGSN.
  • the application protocol e.g. T5 application protocol
  • the 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.
  • the MME / SGSN can check the association with the configured IMEI and IMSI and, if not, include this information to indicate that it is not associated. Can be delivered to.
  • the MME / SGSN may compare this information with the location information configured from the location registration information and, if the location is changed, include this information and deliver it to the monitoring function entity.
  • a mobility management procedure such as a network registration procedure, occurs, it may be transmitted to the monitoring function entity including information related to the change of location.
  • the UE will include this connectivity-related information if a predetermined time has elapsed since the connection was disconnected, such as a network detachment procedure, or a change was made to the connectivity. This can be delivered to the monitoring entity.
  • the monitoring function entity may perform UE Reachability procedure through the HSS to receive notification of reachability information of the UE.
  • the monitoring function entity may perform the UE Reachability procedure through the HSS when the UE is not reachable to perform the monitoring procedure.
  • the monitoring function entity may perform the UE Reachability procedure through the HSS when requesting reachability information of the terminal through the SCS.
  • the MTC-IWF may be informed of the UE reachability information through the HSS.
  • FIG. 7 shows an example of a UE Reachability Notification Request Procedure.
  • the HSS is a UE-REACHABILITY-NOTIFICATION-REQUEST message (or UE Reachability Request Parameter indicating that UE activity notification from the MME has been requested by the HSS).
  • UE-REACHABILITY-NOTIFICATION-REQUEST message or UE Reachability Request Parameter indicating that UE activity notification from the MME has been requested by the HSS.
  • URRP-MME UE Reachability Request Parameter indicating that UE activity notification from the MME has been requested by the HSS.
  • the monitoring function entity has received connectivity loss information, and / or the UE is unreachable upon monitoring request from the SCS server, and / or the monitoring function entity provides an indication to the HSS about mobile network reachability information for the UE.
  • the HSS stores information (or SCS information) of the monitoring function object and indicates that this request has been received.
  • URRP-MME UE Reachability Request Parameter for MME
  • the MME sets the URRP-MME to indicate that the information on the change in UE reachability (e.g. next NAS activity) needs to report to the HSS.
  • 8 shows an example of a UE activity procedure.
  • an MME when an MME receives an indication regarding UE reachability (or UE Activity) (eg attach request MME receive an indication from S GW that UE has handed over to non-3GPP coverage), 2 If the MME includes the MM context of the UE and the URRP-MME is configured to the UE to 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.
  • the HSS may trigger an appropriate notification to the monitoring function entity (or SCS through the monitoring function entity).
  • URRP-MME can be removed.
  • 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 for specific events for UE monitoring in the mobile communication network may be provided by the monitoring function entity.
  • information about the monitoring subscription information of the HSS or the monitoring event included in the monitoring subscription profile, the criteria related to the monitoring, the action on the monitoring event, etc. may not be configured in the MME / SGSN through the subscriber data insertion procedure or the location update procedure. have.
  • the MME / SGSN may enable monitoring for a specific event to provide monitoring for the UE.
  • the MME / SGSN only a part of the monitoring subscription information of the HSS or the information related to the monitoring event included in the monitoring subscription profile, the monitoring-related criteria, the action on the monitoring event, etc. is transmitted to the MME / SGSN through the subscriber data insertion procedure or the location update procedure. It may be configured. Alternatively, information about a monitoring event included in the HSS or a monitoring event included in the monitoring subscription profile, criteria related to monitoring, an action on the monitoring event, and the like may be configured in the MTC-IWF. At this time, the interface between the MTC-IWF and the HSS can use the S6m interface.
  • the monitoring subscription information of the HSS or the information about the monitoring event included in the monitoring subscription profile, the criteria related to the monitoring, the action on the monitoring event, etc. may not be configured in other network objects, but may be requested by the monitoring function entity to receive an HSS response. have.
  • the procedure for configuring monitoring event detection and reporting by the monitoring function entity to the MME / SGSN, activating monitoring for a specific event, or requesting monitoring event detection and reporting may be provided as follows.
  • the UE performs a network attach procedure.
  • the monitoring function entity is a serving core node (CN: Core) serving the UE.
  • Node Sends a Subscriber Information Request message to the HSS to retrieve the identifier.
  • the subscriber information request message includes identifier information of the UE to be monitored (external identifier or IMSI in the form of MSISDN or local identifier @ domain identifier).
  • the HSS sends a subscriber information response (IMSI, serving node identifier, cause) message to the monitoring entity.
  • IMSI subscriber information response
  • Monitoring Function The entity configures monitoring event detection and reporting with the delivered serving MME / SGSN, activates monitoring for a specific event, or requests monitoring event detection and reporting.
  • 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.
  • the resulting report for configuring the monitoring event detection and reporting, activating monitoring for a specific event, or requesting monitoring event detection and reporting is the MTC-IWF and MME. Can be provided via the T5 interface between / SGSN.
  • the monitoring function entity may 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 through HSS, activating monitoring for specific events, or requesting monitoring event detection and reporting may be provided as follows.
  • the monitoring function entity may identify identifier information (MSISDN or local identifier) of the UE to be monitored.
  • MSISDN mobile subscriber identity
  • the monitoring event detection activation information is included in the Subscriber Information Request message including an external identifier or IMSI in the form of @domain identifier, and sent to the HSS.
  • the HSS configures the monitoring event detection and reporting, activates monitoring for a specific event, or responds to a monitoring event detection and reporting request, in order to provide the above described Subscriber Subscriber Data Procedure or UE.
  • HSS reports the results of configuring monitoring event detection and reporting, activating monitoring for specific events, or requesting monitoring event detection and reporting through subscriber information response messages.
  • the monitoring event detection activation request and the result report thereof may be provided through the S6m interface between the MTC IWF and the HSS.
  • the monitoring function entity may deliver the monitoring result report received through another network entity to the monitoring server configured in the subscription information or requesting monitoring.
  • the monitoring server may be an MTC application server or a 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.
  • the monitoring result report may be provided to the service capability server through the Tsp interface.
  • the monitoring function entity may deliver it to the SMS-SC.
  • the monitoring function entity may attempt to retransmit after storing the report.
  • the monitoring function entity may have an indicator for checking retransmission of the monitoring result report.
  • the retransmission is performed by receiving a request message such as a monitoring request or a device trigger request from the monitoring server, the indication may be removed.
  • the HSS may be connected between the HSS and the MME and / or in accordance with the monitoring subscription information or the monitoring subscription profile change and / or by the monitoring request of the external server or by the monitoring request of the MTC-IWF which receives the monitoring request of the external server.
  • the monitoring result for a specific event can be inquired / checked / obtained.
  • SCS service capability server
  • the monitoring user may wish to configure a monitoring action to be executed by the network, such as detecting or reporting on a monitoring event, for monitoring for a specific UE.
  • the monitoring user may wish to activate monitoring for specific events for the UE.
  • the monitoring user may request monitoring that requires an immediate monitoring information response to the UE.
  • the monitoring user may also request monitoring that requires monitoring information reporting on a particular event after it occurs in the UE.
  • the monitoring function may be performed through the monitoring function entity for monitoring the UE by the monitoring user.
  • the monitoring server is a service capability server.
  • the present invention is not limited thereto, and the monitoring server may be another application server or an entity (eg, a UE) including a monitoring application.
  • the monitoring functional entity may be included in the MTC-IWF, an independent entity, or a functional entity of another network element.
  • the service capability server determines the UE to monitor. If the SCS does not have access information for the MTC-IWF, the IP address / port of the MTC-IWF may be determined using an external identifier of the UE to be monitored.
  • the external identifier is an identifier other than MSISDN and is composed of a domain identifier for identifying a domain under the control of a mobile network operator and a local identifier managed by the mobile network operator.
  • the service capability server sends a monitoring request message to the MTC-IWF.
  • the monitoring request message may include an external identifier or an MSISDN, a service capability server identifier, a monitoring reference number, a validity time, a monitoring timer / period, a priority, an immediate monitoring request / single monitoring attempt request, and monitoring event information (or monitoring). Payload), and monitoring event activation / deactivation discrimination information.
  • the monitoring event information may include at least one of example information of Table 1 (eg, a monitoring event for a UE, a criterion related to monitoring, an action for a monitoring event, etc.).
  • the monitoring event for the attachment point change may include allowable registration location / area information or target area information.
  • the monitoring reference number information identifies the specific monitoring request in the monitoring function entity or MTC-IWF and / or MME / SGSN, reports the monitoring event by the specific monitoring request, and / or indicates the monitoring event activated by the specific monitoring request. Can be used to disable it.
  • the monitoring reference number information includes the monitoring request message, including when the monitoring function object configures monitoring event detection and reporting, activates monitoring for a specific event, or requests monitoring event detection and reporting on a network element of the cellular network. You can send it and receive it through the result report.
  • the monitoring reference number information may uniquely identify the monitoring request together with the UE identifier.
  • the validity time represents a time at which monitoring is performed or stored in the serving node or network by the monitoring request. That is, the valid time represents a time for storing a monitoring request or a monitoring response / report at the serving node or at the network when the monitoring request by the monitoring request by the service capability server is not processed.
  • the monitoring timer / period represents the period during which monitoring is performed at the serving node or at the network.
  • the HSS and / or serving node reports the result of the monitoring timer / period at the end or every monitoring timer / period. You can do that.
  • Immediate monitoring indicates that a monitoring response is sent by sending an immediate response to the monitoring request by the SCS server.
  • the response to the request for the monitoring event may be inquired and responded without setting indication information indicating that the specific monitoring event is activated in the HSS and / or serving core node.
  • the display information for the specific monitoring event is activated for the HSS and / or serving core node, and the display information for the request for the specific monitoring event is inquired. Can be cleared and responded.
  • the immediate monitoring can be sent without assigning a valid time to 0 or assigning a specific value to the priority without sending it to a separate information field.
  • the monitoring event activation / deactivation classification information indicates information for distinguishing whether the monitoring request is a request for activating monitoring or a request for deactivating activated monitoring.
  • the SCS server may request deactivation or release of a previous monitoring request including the UE reference and / or the SCS identifier.
  • the MTC-IWF may authorize the Service Capability Server to allow monitoring.
  • the MTC-IWF may apply other control functions such as overload control and position information control.
  • the MTC-IWF may check whether the SCS has exceeded the allowable amount or rate of monitoring submissions through the interface between the SCS and the MTC-IWF.
  • MTC-IWF or HSS is allowed position information (e.g., latitude / longitude, cell identifier, tracking) delivered by SCS or determined by mutual agreement between MTC user and mobile operator and stored in MTC-IWF or HSS.
  • Area identifiers may be used to determine the area information (e.g., Cell Global Identity (CGI), or E-UTRAN Cell Global Identity (ECGI), Tracking Area Identity (TAI), Routing Area Identity in the mobile communication network. ), LAI (Location Area Identity, etc.) can be provided.
  • CGI Cell Global Identity
  • ECGI E-UTRAN Cell Global Identity
  • TAI Tracking Area Identity
  • LAI Routing Area Identity in the mobile communication network.
  • LAI Location Area Identity, etc.
  • the MTC-IWF sends a subscriber information request message to the HSS to determine whether the SCS server is authorized to perform monitoring for one or more UEs. And / or maps the UE's external identifier or MSISDN to IMSI (resolve) or when using an external group identifier to the IMSI list of individual devices belonging to the external group identifier. And / or extract the identifier of the serving core network node of the UE. And / or in addition to the above, the MTC-IWF determines the specific monitoring event to activate according to the monitoring request from the SCS to send information to indicate the monitoring activation for the specific event to the HSS, and the HSS indicates the monitoring activation for the specific event. You can set the indicator information.
  • the HSS includes the MTC-IWF identifier (or monitoring functional object identifier), external identifier or external group identifier or MSISIDN or IMSI, SCS identifier monitoring reference number, validity time, monitoring timer / period, priority Stores one or more pieces of information together. If the external group identifier is used, the above information may be set for each individual device included in the external group identifier.
  • the HSS sends a subscriber information response message (IMSI, Serving Node Identifier, Cause) to the MTC-IWF.
  • IMSI subscriber information response message
  • MTC-IWF determines the monitoring procedure.
  • the monitoring procedure configures monitoring event detection and reporting by the MTC-IWF to the MME / SGSN via the T5 interface, activates monitoring for a particular event, or requests monitoring event detection and reporting. It may be a procedure.
  • the monitoring procedure configures monitoring event detection and reporting by MTC-IWF to MME-SGSN via HSS via S6m interface, activates monitoring for specific events, or detects and reports monitoring event. It may be a procedure for requesting.
  • the monitoring procedure may not be determined by the MTC-IWF, but the monitoring procedure may be a predetermined procedure. In this case, 6 steps can be omitted.
  • step A And a monitoring procedure as determined in MTC-IWF is performed.
  • the monitoring procedure in step A will be described later.
  • MTC-IWF sends the monitoring report to the service capability server.
  • the 4C of FIG. Step 5 may be omitted, or may be performed when configuring monitoring event detection and reporting via HSS, activating monitoring for a particular event, or requesting monitoring event detection and reporting.
  • the monitoring method may be used for a UE used for MTC, that is, a monitoring method for an MTC device, and may also be used for a normal UE.
  • FIG. 10 illustrates a monitoring activation procedure or monitoring procedure via the MTC-IWF or monitoring functional entity in accordance with an embodiment of the present invention. That is, FIG. 10 details one embodiment of the monitoring procedure (step A) in FIG.
  • FIG. 10 is a procedure in which the MTC-IWF configures monitoring event detection and reporting to the MME-SGSN via HSS through the S6m interface, activates monitoring for a specific event, or requests monitoring event detection and reporting.
  • steps 4 and 5 of requesting and responding to subscriber information in FIG. 9 may be omitted.
  • the MTC-IWF may send a monitoring request message to the HSS by determining a 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 an MSISIDN, an SCS identifier, a monitoring reference number, a validity time, a monitoring timer / period, a priority, an immediate monitoring presence / single monitoring attempt, a monitoring event information, a monitoring event activation /
  • One or more pieces of information such as deactivation identification information and MTC-IWF identifier (or monitoring function entity identifier), may be sent.
  • the message may include indicator information (or flag) for setting activation or deactivation per specific monitoring event.
  • activating the monitoring event for the attachment point change may separately provide the indication information and the indication information for activating the monitoring event for connectivity loss.
  • 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.
  • the monitoring reference number may be mapped to a reference number received by the SCS server and may be a monitoring reference number generated by the MTC-IWF.
  • the monitoring reference number may not be included when the indicator information (or flag) for setting the activation or deactivation for each specific monitoring event is included.
  • the HSS receiving the request message sets monitoring activation indicator information (or flag) for the specific event in the HSS to indicate that monitoring is activated for the specific event.
  • the HSS then sends a monitoring request message to the MME.
  • the HSS is an MTC-IWF identifier (or monitoring functional entity identifier), external identifier or external group identifier or MSISIDN or IMSI, SCS identifier, monitoring reference number, validity time, monitoring timer / period, priority
  • MTC-IWF identifier or monitoring functional entity identifier
  • external identifier or external group identifier or MSISIDN or IMSI SCS identifier
  • monitoring reference number e.g., a single monitoring attempt information
  • the HSS can monitor the specific event monitoring.
  • Insert-Subscriber-Data-Request IDR
  • Insert Subscriber Data Request MME
  • UE Reachability Request UE last radio access timestamp information request
  • T-ADS Terminating Access Domain Selection
  • EPS User State Request EPS User State Request
  • EPS Location Information Request EPS Location Information Request
  • One or more flags of the Current Location Request can be set and sent to the MME.
  • the MME has a mobility management (MM) context for the UE, the MME sets indication information for activating the monitoring and / or the flag to change the UE reachability (eg, next NAS activity). If you receive a message related to or detect a monitoring event, indicate that you need to report it to the HSS.
  • MM mobility management
  • the MME sends the UE.
  • Paging can be used to collect the most up-to-date user information. If the latest location information request bit is set and the UE is in connected mode, the MME 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 (ECGI) information can be retrieved using. 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 most recent radio contact timestamp of the UE. If the EPS user status request bit and / or the EPS location information bit are set, the MME returns the corresponding user information to the HSS.
  • ECGI E-UTRAN Cell Global Identification
  • an operation for detecting a monitoring event without setting indication information for activating the monitoring (e.g., an S1AP location reporting control procedure and / or a ME identity check procedure) ) Can be triggered.
  • the indication information for activating the monitoring may be set and a procedure or message (e.g., the next NAS activity, UE reachability change) related to a specific monitoring event may be set.
  • a tracking area update (TAU), a location area update (LAU), a handover, etc. display information for activating the monitoring can be removed.
  • the charging data record (CDR) is charged.
  • Information can be generated.
  • the billing information includes IMSI and / or MSISDN or external identifier, SCS identifier, monitoring reference number, validity time, monitoring timer / cycle, priority, immediate monitoring / single monitoring attempt request, monitoring event information, monitoring event. It may include one or more pieces of information of activation / deactivation information, start time of monitoring request, start time of processing of monitoring event, and time of delivering information related to monitoring event.
  • the MME may send a request message to the UE. For example, when the MME receives an indication for activating a monitoring event for UICC association with a device through the HSS, the MME may receive an IMEI of the UE using the ME identity check procedure. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME may check whether the IMEI received from the UE is connected to the IMEI stored in the EIR and report the result thereof.
  • EIR Equipment Identity Register
  • FIG. 11 illustrates a monitoring activation procedure or a monitoring procedure through an MTC-IWF or a monitoring functional entity through a 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.
  • the MTC-IWF configures monitoring event detection and reporting to a serving node (eg, MME / SGSN) via a T5 interface, activates monitoring for a particular event, or monitors and detects and reports a monitoring event.
  • a serving node eg, MME / SGSN
  • MTC-IWF sends a monitoring request message to the serving node.
  • the message contains information to indicate that monitoring is activated for a particular event, MTC-IWF identifier (or monitoring function identifier), IMSI, monitoring reference number, validity time, monitoring timer / period, priority, immediate Sends one or more information of monitoring status / single monitoring attempt information together.
  • MTC-IWF may request the UE Reachability Request, the UE's last radio access timestamp information request, EPS User State Request, EPS Location Information Request ), At least one of a current location information request (Current Location Request), a terminal location change information request (eg UE Info Change Reporting Action) flag information is set and sent to the MME.
  • the MME sets indication information for activating the specific monitoring and / or the flag to change the UE reachability (for example, next NAS activity).
  • Receiving a message related to an event or detecting a monitoring event indicates that it needs to report to MTC-IWF (or to SCS via HSS or MTC-IWF).
  • the MME may page the UE to collect the latest user information. If the latest location information request bit is set and the UE is in connected mode, the MME 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 (ECGI) information can be retrieved using. 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 most recent radio contact timestamp of the UE.
  • ECGI E-UTRAN Cell Global Identification
  • the MME If the EPS user status request bit and / or the EPS location information bit are set, the MME returns the corresponding user information to MTC-IWF (or to SCS via HSS or MTC-IWF). If the UE location change information request flag bit is set, the information ECGI is returned whenever UE location information change occurs.
  • an operation for detecting a monitoring event without setting indication information for activating the monitoring (e.g., an S1AP location reporting control procedure and / or a ME identity check procedure) ) Can be triggered.
  • the indication information for activating the monitoring may be set and a procedure or message (e.g., the next NAS activity, UE reachability change) related to a specific monitoring event may be set. Receiving related messages, TAU, LAU, Handover, etc.) can remove the display information for activating the monitoring.
  • the charging data record (CDR) is charged.
  • Information can be generated.
  • the billing information includes IMSI and / or MSISDN or external identifier, SCS identifier, monitoring reference number, validity time, monitoring timer / cycle, priority, immediate monitoring / single monitoring attempt request, monitoring event information, monitoring event. It may include one or more pieces of information of activation / deactivation information, start time of monitoring request, start time of processing of monitoring event, and time of delivering information related to monitoring event.
  • the MME may send a request message to the UE. For example, when the MME receives an indication for activating a monitoring event for UICC association with a device through the HSS, the MME may receive an IMEI of the UE using the ME identity check procedure. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME may check whether the IMEI received from the UE is connected to the IMEI stored in the EIR and report the result thereof.
  • EIR Equipment Identity Register
  • FIG. 12 illustrates a monitoring procedure via the HSS in a specific monitoring event activation state in a serving node according to the present invention.
  • the MME receives a message according to a procedure (eg, attach, TAU) by the UE and / or a procedure (eg, downlink notification, UE has handed over to non-3GPP coverage) by the SGW. Or the UE is reachable by the procedure.
  • a procedure eg, attach, TAU
  • a procedure eg, downlink notification, UE has handed over to non-3GPP coverage
  • the MME informs the information related to the specific monitoring event. May inform 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 another network entity (eg, EIR) to check the information related to the particular monitoring event, if necessary.
  • NAS procedures e.g. Attach
  • TAU detach
  • the update location update message, Notify Request message, and / or Insert Subscriber Data Answer message may include a flag (eg, ULR-flag, IDA-flag, NOR-flag) to indicate that the notification is for a specific monitoring event. Can be.
  • the MME queries the E-UTRAN Cell Global Identification (ECGI) information using the S1AP Location Reporting Control procedure to the eNodeB before reporting to return the cell information of the most recent UE.
  • the eNodeB can always include the eECGI information to perform the NAS procedure.
  • the MME may receive an IMEI of the UE using the ME identity check procedure. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME may check whether the IMEI received from the UE is connected to the IMEI stored in the EIR and report the result thereof.
  • EIR Equipment Identity Register
  • the information set to indicate that monitoring is activated for the specific event may not be removed.
  • the information set to indicate that monitoring is activated for the particular event is removed. can do.
  • the HSS may report it to the MTC-IWF.
  • the HSS may include a flag (eg, Update-Location-Request (ULR) -flag, IDA, etc.) indicating that the Update location update message and / or Notify Request message and / or Insert Subscriber Data Answer message are a notification for a specific monitoring event.
  • ULR Update-Location-Request
  • IDA IDA
  • NOR Notification-Request
  • MTC-IWF can be used to determine whether to report.
  • the information set to indicate that monitoring is activated for the specific event may not be removed.
  • the information set to indicate that monitoring is activated for that particular event can be removed. have.
  • the MTC-IWF performs step 7 of FIG. 9. That is, MTC-IWF provides the SCS with the received monitoring result. At this time, the MTC-IWF may perform mapping for monitoring events and details to be reported to the SCS from the received monitoring result. 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 time from the time of receiving the information related to the event, it may provide the SCS server that a connectivity loss has occurred.
  • information eg, attach, TAU, detach
  • the MTC-IWF and / or MME may generate Charging Data Record (CDR) information before or after reporting the monitoring result.
  • the billing information includes IMSI and / or MSISDN or external identifier, SCS identifier, monitoring reference number, validity time, monitoring timer / cycle, priority, immediate monitoring / single monitoring attempt request, monitoring event information, monitoring event. It may include one or more information of the activation / deactivation identification information, the start time of the monitoring request, the time of starting the processing of the monitoring event, the time of delivering the information related to the monitoring event.
  • FIG. 13 illustrates a monitoring procedure via a direct interface to the MTC-IWF in a particular monitoring event activation state in a serving node according to the present invention.
  • the MME determines the information related to the specific monitoring event. May notify the MTC-IWF.
  • the message may be provided through a T5 interface between the MME and the MTC-IWF.
  • the MME may execute a specific procedure with the UE or another network entity (eg, EIR) to check the information related to the particular monitoring event, if necessary.
  • NAS procedures e.g. Attach
  • TAU detach
  • MTC-IWF E-UTRAN Cell Global Identification
  • the MME queries the E-UTRAN Cell Global Identification (ECGI) information using the S1AP Location Reporting Control procedure to the eNodeB before reporting to return the cell information of the most recent UE. Or you can always include the ECGI information to perform the NAS procedure.
  • ECGI E-UTRAN Cell Global Identification
  • the MME may receive an IMEI of the UE using the ME identity check procedure. If the allowed IMEI information is stored in the Equipment Identity Register (EIR), the MME may check whether the IMEI received from the UE is connected to the IMEI stored in the EIR and report the result thereof. Even when reporting the monitoring result, the information set to indicate that monitoring is activated for the specific event may not be removed. Alternatively, when reporting a monitoring result in a particular case (eg, a single monitoring attempt request and / or a monitoring timer / cycle end, deactivation request), the information set to indicate that monitoring is activated for the particular event is removed. can do.
  • EIR Equipment Identity Register
  • the MTC-IWF performs step 7 of FIG. 9. That is, MTC-IWF provides the SCS with the received monitoring result. At this time, the MTC-IWF may perform mapping for monitoring events and details to be reported to the SCS from the received monitoring result. 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 MME. If the information related to the monitoring event is not received for a certain time from the time of receiving the information related to the event, it may provide the SCS server that a connectivity loss has occurred.
  • information eg, attach, TAU, detach
  • the MTC-IWF and / or MME may generate Charging Data Record (CDR) information before or after reporting the monitoring result.
  • the billing information includes IMSI and / or MSISDN or external identifier, SCS identifier, monitoring reference number, validity time, monitoring timer / cycle, priority, immediate monitoring / single monitoring attempt request, monitoring event information, monitoring event. It may include one or more information of the activation / deactivation identification information, the start time of the monitoring request, the time of starting the processing of the monitoring event, the time of delivering the information related to the monitoring event.
  • the UE and the MME may exchange information about the MME's monitoring support capabilities. And / or the MME may obtain information indicating that a particular monitoring event is activated from the HSS. As a result, the MME may perform an MME redirection procedure such as a multiple operator core network (MOCN) to allow the UE to register with the MME supporting monitoring.
  • MME redirection procedure such as a multiple operator core network (MOCN) to allow the UE to register with the MME supporting monitoring.
  • MOCN multiple operator core network
  • the MME performs an MME redirection procedure such as a Multiple Operator Core Network (MOCN) if the MME has information set to indicate that a particular monitoring event has been activated. You can register.
  • MME redirection procedure such as a Multiple Operator Core Network (MOCN)
  • the MME When active / enforced, if you want to activate or configure specific monitoring events via HSS or MTC-IWF, the MME, if configured to do so, from HSS or MTC-IWF It can reduce the signaling load caused by rejecting the monitoring request and / or causing the MME.
  • the reject may include a cause value for indicating that the trigger has failed due to network congestion, and / or a backoff timer.
  • the monitoring event processing method may be used for a UE used for MTC, that is, a monitoring method for an MTC device, and may also be used 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.
  • the MTC-IWF 1400 may include an SCS communication unit 1410 communicating with an SCS, an HSS communication unit 1420 communicating with an HSS, and a serving node communication unit communicating with a serving node (eg, MME / SGSN). 1430, and a controller 1440.
  • SCS communication unit 1410 communicating with an SCS
  • HSS communication unit 1420 communicating with an HSS
  • serving node communication unit communicating with a serving node (eg, MME / SGSN).
  • MME / SGSN serving node
  • the SCS communication unit 1410 may receive a monitoring request message from the SCS.
  • the monitoring request message may include at least one of an external identifier or an MSISDN, an SCS identifier, a monitoring reference number, an effective time, a monitoring timer / period, priority, immediate monitoring / single monitoring attempt request, monitoring event information, and monitoring event activation / deactivation information. It can contain one piece of information.
  • the controller 1440 may authorize the authorization of whether monitoring by the SCS is allowed.
  • the controller 1420 may perform other control functions such as overload control and location information control.
  • the controller 1440 may determine whether the SCS is authorized to perform monitoring for the UE. To this end, the HSS communication unit 1420 may query the subscriber information to the HSS. On the other hand, as will be described later, when configuring or requesting the monitoring event detection and reporting to the serving node through the HSS through the S6m interface or to activate the monitoring, querying the subscriber information to the HSS can be omitted.
  • controller 1440 may determine a monitoring procedure.
  • the monitoring procedure may be a procedure for configuring or requesting monitoring event detection and reporting or activating monitoring directly from the MTC-IWF to the serving node via the T5 interface.
  • the serving node communication unit 1230 may transmit a monitoring request message to the serving node.
  • the monitoring procedure may be a procedure for configuring or requesting monitoring event detection and reporting or activating monitoring from the MTC-IWF to the serving node via the HSS via the S6m interface.
  • the HSS communication unit 1420 may transmit a monitoring request message to the HSS.
  • the monitoring request message sent from the MTC-IWF 1400 to the HSS or serving node may be an external identifier or an external group identifier or an MSISDN, an SCS identifier, a monitoring reference number, an effective time, a monitoring timer / period, a priority, an immediate monitoring status / single. At least one of monitoring attempts, monitoring event information, monitoring event activation / deactivation classification information, and MTC-IWF identifier may be included.
  • the monitoring request message may set a user's UE reachability request, the UE's last radio access timestamp information request, EPS user status information request, EPS location information request, and recent location information request flag.
  • the present invention monitors the association of the Device and UICC, change in the point of attachment, loss of connectivity, and the like through a monitoring function entity in a 3GPP mobile communication network.
  • the serving node For the purpose of activating or deactivating monitoring of one or more devices in an external server according to a user's request, the serving node provides only a function of providing information for detecting a specific monitoring event. Information related to the monitoring event for the terminal in the mobile communication network can be obtained while reducing the complexity of the serving node by processing monitoring detection, reporting, authentication, billing, and other control functions through the monitoring function object or MTC-IWF and / or HSS. It can be effectively processed and reported.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/KR2013/003758 2012-05-02 2013-04-30 Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile Ceased WO2013165168A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
KR10-2012-0046584 2012-05-02
KR20120046584 2012-05-02
KR20120097052 2012-09-03
KR10-2012-0097052 2012-09-03
KR10-2012-0097126 2012-09-03
KR20120097126 2012-09-03
KR1020120143964A KR101873068B1 (ko) 2012-05-02 2012-12-11 이동통신망에서 단말 모니터링 방법 및 장치
KR10-2012-0143964 2012-12-11

Publications (1)

Publication Number Publication Date
WO2013165168A1 true WO2013165168A1 (fr) 2013-11-07

Family

ID=49514522

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2013/003758 Ceased WO2013165168A1 (fr) 2012-05-02 2013-04-30 Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile

Country Status (1)

Country Link
WO (1) WO2013165168A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016153316A1 (fr) * 2015-03-25 2016-09-29 엘지전자(주) Procédé de contrôle de l'accessibilité d'un ue dans un système de communication sans fil, et appareil associé
WO2016186397A1 (fr) * 2015-05-15 2016-11-24 Samsung Electronics Co., Ltd. Procédé et appareil de configuration de surveillance d'équipement d'utilisateur
KR20200011497A (ko) * 2017-07-20 2020-02-03 후아웨이 테크놀러지 컴퍼니 리미티드 핸드오버 방법, 디바이스 및 시스템
US11910287B2 (en) 2018-11-19 2024-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring
WO2025167101A1 (fr) * 2024-02-08 2025-08-14 中国电信股份有限公司技术创新中心 Procédé et dispositif de traitement de messages courts en liaison descendante, dispositif de communication et support de stockage

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080017660A (ko) * 2006-08-22 2008-02-27 에스케이 텔레콤주식회사 사용자 단말의 모니터링 시스템 및 방법, 이를 위한모니터링 장치와 보안 에이전트
KR20100064514A (ko) * 2008-12-05 2010-06-15 삼성전자주식회사 이동하는 단말의 위치에 따라 단말이 등록된 ｇａｎ 제어기를 변경하기 위한 방법 및 장치
KR20110083535A (ko) * 2010-01-13 2011-07-20 엘지전자 주식회사 무선통신 시스템에서의 이벤트 발생 알림 방법 및 장치
KR20110122643A (ko) * 2010-05-04 2011-11-10 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 서비스 네트워크 오버로드의 제어 방법 및 그 장치
KR20120011012A (ko) * 2010-04-28 2012-02-06 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 데이터의 혼잡 제어 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080017660A (ko) * 2006-08-22 2008-02-27 에스케이 텔레콤주식회사 사용자 단말의 모니터링 시스템 및 방법, 이를 위한모니터링 장치와 보안 에이전트
KR20100064514A (ko) * 2008-12-05 2010-06-15 삼성전자주식회사 이동하는 단말의 위치에 따라 단말이 등록된 ｇａｎ 제어기를 변경하기 위한 방법 및 장치
KR20110083535A (ko) * 2010-01-13 2011-07-20 엘지전자 주식회사 무선통신 시스템에서의 이벤트 발생 알림 방법 및 장치
KR20120011012A (ko) * 2010-04-28 2012-02-06 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 데이터의 혼잡 제어 방법
KR20110122643A (ko) * 2010-05-04 2011-11-10 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 서비스 네트워크 오버로드의 제어 방법 및 그 장치

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10420069B2 (en) 2015-03-25 2019-09-17 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
CN107431918B (zh) * 2015-03-25 2020-09-04 Lg 电子株式会社 在无线通信系统中监测ue可达性的方法及其装置
US9668236B2 (en) 2015-03-25 2017-05-30 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
KR20170129157A (ko) * 2015-03-25 2017-11-24 엘지전자 주식회사 무선 통신 시스템에서 단말 접근성 모니터링 방법 및 이를 위한 장치
CN107431918A (zh) * 2015-03-25 2017-12-01 Lg 电子株式会社 在无线通信系统中监测ue可达性的方法及其装置
WO2016153316A1 (fr) * 2015-03-25 2016-09-29 엘지전자(주) Procédé de contrôle de l'accessibilité d'un ue dans un système de communication sans fil, et appareil associé
US10721713B2 (en) 2015-03-25 2020-07-21 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
US10051602B2 (en) 2015-03-25 2018-08-14 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
KR101974948B1 (ko) 2015-03-25 2019-05-03 엘지전자 주식회사 무선 통신 시스템에서 단말 접근성 모니터링 방법 및 이를 위한 장치
KR20170142174A (ko) * 2015-05-15 2017-12-27 삼성전자주식회사 단말 모니터링 설정 방법 및 장치
US10306458B2 (en) 2015-05-15 2019-05-28 Samsung Electronics Co., Ltd. UE monitoring configuration method and apparatus
US9930516B2 (en) 2015-05-15 2018-03-27 Samsung Electronics Co., Ltd. UE monitoring configuration method and apparatus
US10728737B2 (en) 2015-05-15 2020-07-28 Samsung Electronics Co., Ltd. UE monitoring configuration method and apparatus
WO2016186397A1 (fr) * 2015-05-15 2016-11-24 Samsung Electronics Co., Ltd. Procédé et appareil de configuration de surveillance d'équipement d'utilisateur
KR102394118B1 (ko) 2015-05-15 2022-05-04 삼성전자 주식회사 단말 모니터링 설정 방법 및 장치
KR20200011497A (ko) * 2017-07-20 2020-02-03 후아웨이 테크놀러지 컴퍼니 리미티드 핸드오버 방법, 디바이스 및 시스템
KR102268412B1 (ko) * 2017-07-20 2021-06-22 후아웨이 테크놀러지 컴퍼니 리미티드 핸드오버 방법, 디바이스 및 시스템
US11160004B2 (en) 2017-07-20 2021-10-26 Huawei Technologies Co., Ltd. Handover method, device, and system
US11716667B2 (en) 2017-07-20 2023-08-01 Huawei Technologies Co., Ltd. Handover method, device, and system
US11910287B2 (en) 2018-11-19 2024-02-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring
US12425823B2 (en) 2018-11-19 2025-09-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring
WO2025167101A1 (fr) * 2024-02-08 2025-08-14 中国电信股份有限公司技术创新中心 Procédé et dispositif de traitement de messages courts en liaison descendante, dispositif de communication et support de stockage

Similar Documents

Publication Publication Date Title
WO2013133663A1 (fr) Procédé de commande de service dans un système de radiocommunication
WO2011084010A2 (fr) Procédé pour réaliser une indication hors ligne d'un dispositif de communication de type machine dans un système de communication mobile
WO2018143774A1 (fr) Procédé de gestion d'enregistrement pour un terminal accédant à un réseau 5g au moyen d'un accès non 3 gpp
WO2011021875A2 (fr) Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
WO2013141599A1 (fr) Procédé et appareil de déclenchement de groupe mtc dans un système de communication sans fil
WO2011099769A2 (fr) Système de communication sans fil et procédé de connexion entre un équipement utilisateur et une entité de gestion de mobilité
WO2012074337A2 (fr) Appareil et procédé d'envoi/réception de trafic de diffusion groupée dans un système d'accès sans fil prenant en charge une communication de machine à machine
WO2014027740A1 (fr) Procédé et appareil pour une messagerie basée sur des groupes dans un réseau de communication mobile
WO2018174373A1 (fr) Procédé de gestion de session et nœud smf
WO2013168937A1 (fr) Procédé et appareil prenant en charge la détection de la cause d'une défaillance rlf ou la détection de la cause d'une défaillance de transfert
WO2013051845A2 (fr) Procédé et appareil pour commander l'accès d'un équipement d'utilisateur dans un système de communication mobile
WO2011139098A2 (fr) Procédé destiné à commander une surcharge de réseau mobile mtc dans un système de communication mobile et son dispositif
WO2013165168A1 (fr) Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile
WO2017188787A2 (fr) Procédé de transmission de données mis en œuvre par une station de base dans un système de communication sans fil et appareil utilisant le procédé
EP3566509A1 (fr) Procédé de gestion d'enregistrement pour un terminal accédant à un réseau 5g au moyen d'un accès non 3 gpp
WO2012138107A2 (fr) Messagerie sur un réseau
WO2015174702A1 (fr) Procédé et appareil pour une émission et une réception de signal de hss/mme dans un système de communication sans fil
WO2012138148A2 (fr) Procédé permettant de transmettre et de recevoir des informations de mise à jour de paramètres, et appareil correspondant
EP2425659A2 (fr) Procédé et appareil destinés à assister un accès à un protocole internet (ip) local dans une femtocellule d'un système de communication sans fil
WO2014069928A1 (fr) Procédé de transmission de données d'un dispositif mtc
WO2013055063A1 (fr) Serveur de message court, procédé de déclenchement de terminal de serveur associé, serveur de distribution de requête de déclenchement, procédé de distribution de requête de déclenchement de serveur associé
WO2014051260A1 (fr) Procédé de surveillance mtc
WO2014003455A1 (fr) Procédé de détermination de contrôle d'accès
KR20130112664A (ko) 이중 우선순위 어플리케이션을 갖는 기계 형태 통신 장치에 대한 접속 제어 방법 및 장치
WO2012081882A2 (fr) Procédé et appareil pour la transmission fiable d'une diffusion multiple vers un groupe au moyen d'une technique de radiodiffusion cellulaire dans un système de communication mobile

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13784159

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23.02.2015)

122 Ep: pct application non-entry in european phase

Ref document number: 13784159

Country of ref document: EP

Kind code of ref document: A1