WO2013139073A1 - 一种发送终端监控报告的方法及系统 - Google Patents

一种发送终端监控报告的方法及系统 Download PDF

Info

Publication number
WO2013139073A1
WO2013139073A1 PCT/CN2012/075473 CN2012075473W WO2013139073A1 WO 2013139073 A1 WO2013139073 A1 WO 2013139073A1 CN 2012075473 W CN2012075473 W CN 2012075473W WO 2013139073 A1 WO2013139073 A1 WO 2013139073A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
monitoring event
mtc
mme
monitoring
Prior art date
Application number
PCT/CN2012/075473
Other languages
English (en)
French (fr)
Inventor
吴昊
谢芳
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013139073A1 publication Critical patent/WO2013139073A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present invention relates to a machine type communication (MTC) technology, and in particular, to a method and system for transmitting a terminal monitoring report.
  • MTC machine type communication
  • FIG. 1 is a schematic structural diagram of a conventional cellular wireless communication system.
  • a cellular wireless communication system is mainly composed of a core network (CN, Core Network), an access network (RAN, Radio Access Network), and a terminal.
  • the core network is responsible for non-access stratum transactions, such as terminal location update, and the core network is an anchor point of the user plane;
  • the access network is responsible for access layer transactions, such as management of radio resources, and the access network includes a base station, or a base station.
  • the base station controller the base station may have a physical or logical connection according to the actual situation, such as the connection between the base station 1 and the base station 2, the base station 1 and the base station 3 in FIG. 1, and each base station may have more than one
  • the core network node is connected;
  • the terminal is a user equipment (UE, User Equipment), which refers to various devices that can communicate with the cellular wireless communication network, such as a mobile phone or a notebook computer.
  • UE user equipment
  • the MTC service refers to the communication between machines. In the MTC service, no human participation is required, and all communication is performed by the machine.
  • the MTC service obtains data through sensing devices such as sensors, and then reports the data to the mobile communication network through the communication module, and accesses the public data network through the mobile communication network, for example, in logistics monitoring, security monitoring, telemedicine detection, remote meter reading, etc. application.
  • This data is managed by a mobile operator or a specific MTC operator's specific MTC server and can be viewed by MTC users or MTC managers. In this process, the device that obtains the data required by the business is the MTC device.
  • the MTC service is different from the traditional mobile communication service.
  • MTC devices For an MTC user, there may be multiple MTC devices.
  • the remote meters belong to the MTC user of a power company. In order to facilitate the management of these remote meters belonging to the same MTC user, more remote meters are grouped to reduce control signaling and facilitate management and billing.
  • HSS home subscriber Server
  • HLR home subscriber location register
  • the MME acquires the group information of the MTC device from the HSS or the HLR, and manages the MTC device according to the group information.
  • the HSS or the HLR is an entity in the core network for storing identity information, authentication information, authorization information, and the like of a user or a terminal device.
  • the HSS can be used to store the identity information of the user and the binding information of the user and the terminal device, or only the identity information of the user (the binding information of the user and the terminal device can be saved by the gateway), or the identity of the terminal device can be directly saved. information.
  • the HSS or HLR is also responsible for the user's subscription database, as well as the user's authentication and authorization.
  • the service platform can query user or terminal information from the HSS or HLR.
  • the MME Mobility Management Entity
  • SGSN GPRS Service Support Node
  • the non-access stratum signaling controls and registers the terminal to the network.
  • the MTC Inter-Working Function is an entity connected between the mobile communication network and the external public network, which can implement protocol conversion, address query, and information. Save and other functions.
  • the MTC IWF is externally connected to the MTC server, and may be connected to the mobile communication network element such as the HSS/HLR or the MME/SGSN.
  • MTC users need to be able to monitor their MTC devices, that is, terminals, such as whether some fixed terminals are illegally moved, or whether the SIM (Subscriber Identity Module) card is illegally exchanged.
  • Some network elements are needed to monitor the behavior of the terminal.
  • the network element such as the MME has the function of monitoring the terminal, the MTC server cannot know the result of the monitoring of the network element, so that the MTC user cannot monitor the terminal of the subordinate in time. Summary of the invention
  • the main purpose of the present invention is to provide a method and system for transmitting a terminal monitoring report, which enables the MTC server to know the monitoring result of the network element to the terminal in time.
  • the present invention provides a method for a transmitting terminal to monitor a report.
  • the method includes: after the terminal accesses the network, the MME detects the occurrence of the monitoring event according to the monitored event parameter in the saved subscription data of the terminal, and sends the MTC IWF to the MTC IWF. Send a monitoring event report containing the monitoring event, the external identity of the terminal, and the MTC server identity or address;
  • the MTC IWF sends a monitoring event report containing the monitoring event and the external identifier of the terminal to the MTC server according to the MTC server identifier or address in the received monitoring event report.
  • the method before the MME detects the occurrence of the monitoring event according to the monitored event parameter in the subscription data of the terminal, the method further includes: the MME acquiring the subscription data of the terminal from the HSS, and saving the data.
  • the MME obtains the subscription data of the terminal from the HSS, and includes: after receiving the attach request signaling or the tracking area update request signaling sent by the terminal, the MME sends an update location request signaling to the HSS; Returning the update location approval signaling containing the subscription data of the terminal.
  • the method before the MME obtains the subscription data of the terminal from the PDCCH, the method further includes: the HSS uses the monitoring event parameter, the external identifier of the terminal, and the MTC server identifier or address as the subscription data of the terminal, and saves the data. .
  • the monitoring event report sent by the MME to the MTC IWF further includes protocol identification information; the protocol identification information is used by the MTC IWF to identify the type of the received signaling.
  • the monitoring event report sent by the MTC IWF to the MTC server further includes protocol identification information; the protocol identification information is used by the MTC server to identify the type of the received signaling.
  • the present invention also provides a system for transmitting a terminal to monitor a video, the system comprising: an MME, an MTC IWF, and an MTC server;
  • the MME after the terminal accesses the network, sends a monitoring event, an external identifier of the terminal, and an MTC server to the MTC IWF after detecting that the monitoring event occurs according to the monitored monitoring event parameter in the subscription data of the terminal.
  • An MTC IWF configured to send, to the MTC server, a monitoring event report that includes a monitoring event and an external identifier of the terminal according to the MTC server identifier or address in the received event report;
  • the MTC server is configured to receive a monitoring event report sent by the MTC IWF.
  • the system further includes: an HSS, configured to provide the subscription data of the terminal to the MME, where the MME is further configured to acquire the subscription data of the terminal from the HSS, and save the data.
  • the HSS is further configured to use the monitoring event parameter, the external identifier of the terminal, and the MTC server identifier or address as the subscription data of the terminal, and save the data.
  • the method and system for transmitting a monitoring report of a transmitting terminal provided by the present invention, after the terminal accesses the network, the MME detects the occurrence of the monitoring event according to the monitored monitoring event parameter in the subscription data of the terminal, and sends the monitoring event and the terminal to the MTC IWF.
  • the MTC server can be informed of the monitoring result of the network element to the terminal in time.
  • the MTC server generates an event warning message according to the received monitoring event report, so that the MTC user to which the terminal belongs can view the related event alarm on the MTC server.
  • the information is reported, and then the terminals of its own subordinates can be monitored in time to enhance the user experience.
  • FIG. 1 is a schematic structural diagram of a conventional cellular wireless communication system
  • FIG. 2 is a schematic flowchart of a method for monitoring a report of a transmitting terminal according to the present invention
  • FIG. 3 is a schematic flowchart of a method for transmitting a terminal to monitor 4 advertisements in Embodiment 1;
  • FIG. 4 is a schematic flowchart of a method for transmitting a terminal monitoring and reporting in the second embodiment
  • FIG. 5 is a schematic structural diagram of a system for transmitting a monitoring report of a transmitting terminal according to the present invention. detailed description
  • the method for transmitting the monitoring report of the sending terminal of the present invention includes the following steps: Step 201: After the terminal accesses the network, the MME detects, after detecting the event, the monitoring event occurs according to the saved monitoring event parameter in the subscription data of the terminal.
  • the MTC IWF sends a monitoring event report including a monitoring event, an external identifier of the terminal, and an MTC server identifier or address;
  • the method may further include:
  • the MME obtains the subscription data of the terminal from the HSS and saves it.
  • the MME sends an update location request signaling to the HSS;
  • the HSS returns to the MME the update location approval signaling containing the subscription data of the terminal.
  • the subscription data of the terminal includes: a monitoring event parameter, an external identifier of the terminal, and an MTC server identifier or address.
  • the MME detects that the monitoring event occurs according to the saved monitoring event parameter in the subscription data of the terminal, where the MME matches the device number in the monitoring event parameter with the device number of the terminal itself, or , the tracking area location information in the monitoring event parameter After the location information of the terminal is matched, and the matching is determined, the monitoring event is detected, and after the determination fails, the monitoring event is not detected.
  • the method may further include: the HSS uses the monitoring event parameter, the external identifier of the terminal, and the MTC server identifier or address as the subscription data of the terminal, and saves the data.
  • the event report sent to the MTC IWF may further include: protocol identification information; the protocol identification information is used by the MTC IWF to identify the type of the received signaling.
  • Step 202 The MTC IWF sends a monitoring event report including the monitoring event and the external identifier of the terminal to the MTC server according to the MTC server identifier or address in the received monitoring event report.
  • the monitoring event report sent to the MTC server may further include: protocol identification information; the protocol identification information is used by the MTC server to identify the type of the received signaling.
  • the MTC server may specifically be an MTC server to which the terminal belongs, or may be another MTC server that needs to obtain a monitoring event report.
  • the method may further include: the MTC server generating an event warning message according to the received monitoring event report.
  • the event warning message may include the received monitoring event report.
  • the application scenario of this embodiment is: whether the Universal Integrated Circuit Card (UICC) of the monitoring terminal is illegally stolen.
  • the method for transmitting a terminal monitoring report in this embodiment, as shown in FIG. 3, includes the following steps:
  • Step 301 After the terminal is powered on, sending an attach request signaling to the MME.
  • signing with the operator requires monitoring the association change between the terminal and the UICC card, that is, whether the UICC of the monitoring terminal is illegally stolen.
  • the operator can define the event that the monitoring terminal and the UICC card are associated with changes as monitoring events.
  • monitoring event parameter specifically includes the following parameters: monitoring event code: monitoring event A;
  • the external ID of the set terminal is ExID:
  • the set MTC server ID or address is MTC_Server_A;
  • the MTC server identifier or address may be the serial number of the MTC server, or may be the IP address of the MTC server.
  • the MTC IWF can send the monitoring report to the correct MTC server according to the identity or address of the MTC server.
  • the monitoring event parameters set by the operator, the external ID of the terminal, and the MTC server ID or address are stored as contract data of the terminal and stored on the HSS.
  • the attach request signaling includes an internal identifier of the terminal in the mobile communication network, that is, an International Mobile Subscriber Identification Number (IMSI); wherein the UICC card has a corresponding relationship with the IMSI, that is, has a binding relationship.
  • IMSI International Mobile Subscriber Identification Number
  • the network element in the network uses the identified IMSI as the internal identifier of the terminal, and the IMSI of the terminal is also stored as part of the subscription data of the terminal and stored on the HSS.
  • Step 302 After receiving the attach request signaling, the MME reads the IMSI in the attach request signaling, and sends the IMSI in the update location request signaling to the HSS.
  • Step 303 After receiving the update location request signaling, the HSS reads the IMSI in the update location request, queries the local database according to the IMSI, obtains the subscription data of the terminal corresponding to the IMSI, and returns an update location identifier including the subscription data to the MME. Signaling
  • the subscription data includes: a monitoring event parameter, an external identifier of the terminal, and an MTC server identifier or address.
  • Step 304 After receiving the subscription data, the MME saves the subscription data to a local database.
  • the format of the local database can be as shown in Table 1.
  • Step 305 The MME reads the monitoring event code and the device number in the monitoring event parameter in the subscription data.
  • the monitoring event code is monitoring event A, indicating that it is necessary to monitor the event that the terminal associates with the UICC card.
  • Step 306 The MME sends control signaling to the terminal, requesting the terminal to report its own device number.
  • the device number means: IMEI.
  • Step 307 After receiving the control signaling, the terminal returns a feedback signaling including its own device number to the MME.
  • Step 308 After receiving the feedback signaling, the MME matches the device number of the terminal in the feedback signaling with the device number in the subscription data, determines a mismatch, generates a monitoring event report, and sends the monitoring event report to the MTC IWF. Generated monitoring event report;
  • the MME determines that the device number of the terminal in the feedback signaling does not match the device number in the subscription data, it is determined that the monitoring event A is detected, that is, the UICC of the terminal is illegally stolen.
  • An event report is generated; when the MME determines that the device number of the terminal in the feedback signaling matches the device number in the subscription data, it is determined that the monitoring event A is not detected.
  • Raw that is: the UICC of the terminal is not illegally stolen.
  • the content of the monitoring event report may include: protocol identification information, an IMSI of the terminal that detects the occurrence of the monitoring event, a detected monitoring event, an external identifier of the terminal that detects the occurrence of the monitoring event, and an MTC server identifier or address, etc.
  • the protocol identification information is used by the MTC IWF to identify the type of the received signaling, and may specifically be an event report.
  • the detected monitoring event is monitoring event A
  • the external identifier of the terminal detecting the occurrence of the monitoring event is ExID
  • the MTC server identifier or address is MTC_Server_A.
  • Step 309 After receiving the monitoring event report, the MTC IWF sends a monitoring event report to the corresponding MTC server according to the MTC server identifier or address in the monitoring event report.
  • the MTC server may be an MTC server to which the terminal that legally uses the UICC card belongs, or may be another MTC server that needs to obtain a monitoring event report.
  • the content of the event report sent by the MTC IWF to the MTC server may include: protocol identification information, a detected monitoring event, and an external identifier of the terminal that detects the occurrence of the monitoring event, etc., wherein the protocol identification information is used for the MTC server to identify and receive The type of signaling to be specifically reported for the event.
  • the detected monitoring event is monitoring event A
  • the external identifier of the terminal detecting the occurrence of the monitoring event is ExID.
  • Step 310 After receiving the monitoring event report, the MTC server saves the monitoring event report, and generates event warning information, so that the MTC user to which the terminal legally using the UICC card belongs can view related event warning information on the MTC server. In turn, it is possible to monitor the terminals of its own subordinates in a timely manner.
  • the application scenario of this embodiment is: monitoring whether the terminal is illegally stolen.
  • the MME corresponding to the pre-terminal mobility is referred to as the original MME, and the corresponding MME after the terminal is moved to the new cell is referred to as a new MME.
  • a method for sending a terminal to monitor a notification is as shown in FIG. Including the following steps:
  • Step 401 After the terminal moves to the new cell, and reads the tracking area information in the cell broadcast information, the tracking area information of the new cell is matched with the locally saved tracking area information, and after determining the mismatch, the tracking area update is sent to the new MME. Request signaling
  • the operator when signing with the operator, needs to monitor the terminal location change, that is, whether the monitoring terminal is illegally stolen.
  • the operator can define the event that monitors the location change of the terminal as the monitoring event B, and set the corresponding monitoring event parameter, the external identifier of the terminal, and the MTC server identifier on the HSS or An address; wherein, in this embodiment, the monitoring event parameter specifically includes the following parameters:
  • Monitoring event code monitoring event B
  • Terminal location information Location A.
  • the external ID of the set terminal is ExID; the set MTC server ID or address: MTC_Server_A;
  • the MTC server identifier or address may be the serial number of the MTC server, or may be the IP address of the MTC server.
  • the MTC IWF can send the monitoring report to the correct MTC server according to the identity or address of the MTC server.
  • the monitoring event parameters set by the operator, the external ID of the terminal, and the MTC server ID or address are stored as contract data of the terminal and stored on the HSS.
  • the network element in the network uses the identified IMSI as the internal identifier of the terminal.
  • the IMSI of the terminal will also be used as part of the subscription data of the terminal, and the HSS will be saved.
  • the tracking area update request signaling includes: a temporary internal identifier (GUTI, Global Unique Temporary Identity) allocated by the original MME; the GUTI includes: an identifier of the original MME.
  • GUI Global Unique Temporary Identity
  • Step 402 After receiving the tracking area update request signaling, the new MME sends data request signaling to the original MME.
  • the new MME reads the GUTI in the tracking area update request signaling, obtains the identifier of the original MME, and sends data request signaling to the original MME accordingly.
  • Step 403 After receiving the data request signaling, the original MME sends the IMSI of the terminal to the new MME.
  • Step 404 After receiving the IMSI of the terminal, the new MME sends the IMSI to the HSS in the update location request signaling.
  • Step 405 After receiving the update location request signaling, the HSS reads the IMSI in the update location request, queries the local database according to the IMSI, obtains the subscription data of the terminal, and returns an update location identifier including the subscription data to the new MME. Signaling
  • the subscription data includes: a monitoring event parameter, an external identifier of the terminal, and an MTC server identifier or address.
  • Step 406 After receiving the subscription data, the new MME saves the subscription data to a local database.
  • the format of the local database can be as shown in Table 1.
  • Step 407 The new MME reads the monitoring event code and the terminal location information in the monitoring event parameter in the subscription data.
  • the monitoring event code is the monitoring event B, indicating that the event of the terminal position change needs to be monitored, and the terminal location information is: the tracking area A.
  • Step 408 The new MME matches the terminal location information in the monitoring event parameter in the subscription data with the locally saved tracking area location information, determines a mismatch, generates a monitoring event report, and sends the generated monitoring event to the MTC IWF. Report
  • each MME belongs to a fixed tracking area, and the tracking area information to which it belongs is stored in the local database.
  • the tracking area information to which the new MME belongs is the tracking area B.
  • the new MME determines the locally saved tracking area location information and the terminal in the subscription data After the location information is not matched, it is considered that the monitoring event B is detected, that is, the terminal is illegally stolen, and an event report is generated.
  • the MME determines the locally saved tracking area location information and the terminal location information in the subscription data. After the matching, it is considered that the monitoring event B is not detected, that is, the terminal is not illegally stolen.
  • the subsequent processing procedure of the MME is not the content of the present invention.
  • the content of the monitoring event report may include: protocol identification information, an IMSI of the terminal that detects the occurrence of the monitoring event, a detected monitoring event, an external identifier of the terminal that detects the occurrence of the monitoring event, and an MTC server identifier or address, etc.
  • the protocol identification information is used by the MTC IWF to identify the type of the received signaling, and may specifically be an event report.
  • the detected monitoring event is monitoring event B
  • the external identifier of the terminal detecting the occurrence of the monitoring event is ExID
  • the MTC server identifier or address is MTC_Server_A.
  • Step 409 After receiving the monitoring event report, the MTC IWF sends a monitoring event report to the corresponding MTC server according to the MTC server identifier or address in the monitoring event report.
  • the MTC server may specifically be an MTC server to which the terminal belongs, or may be another MTC server that needs to obtain a monitoring event report.
  • the content of the monitoring event report sent by the MTC IWF to the MTC server may include: protocol identification information, a detected monitoring event, and an external identifier of the terminal that detects the occurrence of the monitoring event; wherein the protocol identification information is used for the MTC server to identify and receive The type of signaling to be specifically reported for the event.
  • the detected monitoring event is monitoring event B
  • the external identifier of the terminal detecting the occurrence of the monitoring event is ExID.
  • the content of the event report may further include: event occurrence location information.
  • the event occurrence location information is the tracking area B.
  • Step 410 After receiving the monitoring event report, the MTC server saves the monitoring event report, and generates event warning information, so that the MTC user to which the terminal belongs can view related event warning information on the MTC server, and then timely The ground monitors the terminals of its own subordinates.
  • the present invention also provides a system for transmitting a terminal monitoring report, such as As shown in FIG. 5, the system includes: an MME 51, an MTC IWF 52, and an MTC server 53;
  • the MME 51 is configured to send, after the terminal accesses the network, the monitored event, the monitoring event, the external identifier of the terminal, and the MTC server to the MTC IWF 52 according to the monitored event parameter in the subscription data of the terminal.
  • the MTC IWF 52 is configured to send, to the MTC server 53, a monitoring event report including the monitoring event and the external identifier of the terminal according to the MTC server identifier or address in the received event report.
  • the MTC server 53 is configured to receive a monitoring event report sent by the MTC IWF 52.
  • the system may further include: an HSS, configured to provide the subscription data of the terminal to the MME 51, where the MME 51 is further configured to acquire the subscription data of the terminal from the HSS, and save the data.
  • an HSS configured to provide the subscription data of the terminal to the MME 51
  • the MME 51 is further configured to acquire the subscription data of the terminal from the HSS, and save the data.
  • the HSS is further configured to use the monitoring event parameter, the external identifier of the terminal, and the MTC server identifier or address as the subscription data of the terminal, and save the data.
  • the MTC server 53 is further configured to generate event warning information according to the received monitoring event report.

Landscapes

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

Abstract

本发明公开了一种发送终端监控报告的方法，该方法包括：终端入网后，MME根据保存的所述终端的签约数据中的监控事件参数，检测到监控事件发生后，向给MTC IWF发送包含监控事件、终端的外部标识、以及MTC服务器标识或地址的监控事件报告；MTC IWF根据收到的监控事件报告中的MTC服务器标识或地址，向MTC服务器发送包含监控事件及终端的外部标识的监控事件报告。本发明还同时公开了一种发送终端监控报告的及系统，采用本发明的方法及系统，能使MTC服务器及时地获知网元对终端的监控结果。

Description

一种发送终端监控报告的方法及系统 技术领域
本发明涉及机器类型通信（ MTC, Machine Type Communication )技术， 尤其涉及一种发送终端监控报告的方法及系统。 背景技术
图 1为现有蜂窝无线通信系统的架构示意图， 如图 1所示， 蜂窝无线 通信系统主要由核心网（CN, Core Network )、接入网（RAN, Radio Access Network )和终端组成。 其中， 核心网负责非接入层事务， 比如终端位置更 新等， 核心网是用户面的锚点； 接入网负责接入层事务， 比如无线资源的 管理等， 接入网包括基站， 或者基站以及基站控制器， 基站之间可以根据 实际情况存在物理或逻辑上的连接，如图 1中的基站 1和基站 2,基站 1和 基站 3之间的连接， 并且每个基站可以和一个以上的核心网节点连接； 终 端即是用户设备（UE, User Equipment ) , 是指可以和蜂窝无线通信网络通 信的各种设备， 比如移动电话或笔记本电脑等。
MTC业务是指机器之间进行通信的业务， 在 MTC业务中不需要人的 参与， 所有的通信由机器自主完成。 MTC业务通过传感器等感知设备获得 数据， 然后通过通信模块将数据上报给移动通信网络， 并通过移动通信网 络接入到公共数据网， 例如在物流监控、 安全监测、 远程医疗检测、 远程 抄表等应用。 该数据由移动运营商或专门的 MTC运营商的特定 MTC服务 器进行管理， 可供 MTC用户或 MTC管理者查看。 在这个过程中， 获取业 务所需要的数据的设备即为 MTC设备。
MTC业务与传统移动通信业务有所不同， 对于一个 MTC用户， 可能 拥有多个 MTC设备， 比如在远程抄表业务中， 可能数千个作为 MTC设备 的远程电表都属于某电力公司这个 MTC用户，为了方便对这些属于同一个 MTC用户的远程电表进行管理， 对更多的远程电表进行了分组， 以减少控 制信令、 以及方便管理和计费。 目前， 为了方便对组进行管理， 属于同一 个 MTC用户的 MTC设备被划分到同一个组， 并且相关组信息在归属用户 服务器（ HSS , Home Subscriber Server )或归属用户位置寄存器（ HLR, Home Location Register ) 中保存。 在 MTC业务执行过程中， 由 MME从 HSS或 HLR中获取 MTC设备的分组信息，并根据分组信息对 MTC设备进行管理。
这里， HSS或 HLR是核心网中用于保存用户或终端设备的身份信息、 认证信息和授权信息等的实体。 根据不同情况， HSS 可用于保存用户的身 份信息及用户和终端设备的绑定信息， 或只保存用户的身份信息 （可由网 关保存用户和终端设备的绑定信息） ， 或直接保存终端设备的身份信息。 HSS或 HLR还负责用户的签约数据库、以及执行用户的身份验证和授权等。 业务平台可从 HSS或 HLR查询用户或终端信息。 移动性管理实体（MME, Mobility Management Entity )或 GPRS服务支持节点（ SGSN, Servicing GPRS Support Node )是核心网中负责管理终端接入控制、 位置信息更新、 以及切 换的单元， 并负责核心网到终端的非接入层信令控制和将终端注册到网络。
而在实现 MTC业务的无线通信系统中， MTC互操作功能实体（IWF, Inter-Working Function )是一个连接在移动通信网与外部公网之间的实体， 能够实现协议转换、 地址查询、 以及信息保存等功能。 具体地， MTC IWF 对外连接 MTC服务器，对内可以连接到 HSS/HLR、或 MME/SGSN等移动 通信网络网元。
通常， 某些 MTC用户需要能对他们的 MTC设备即终端进行监控， 比 如一些固定放置的终端是否被非法移动， 或者， 是否被非法调换客户识别 模块（SIM, Subscriber Identity Module )卡等， 这就需要一些网元能监控终 端的行为。 目前， 虽然 MME等网元具有对终端进行监控的功能， 但是 MTC服务 器并不能获知这些网元监控的结果，从而使得 MTC用户不能及时地对自身 下属的终端进行监控。 发明内容
有鉴于此， 本发明的主要目的在于提供一种发送终端监控报告的方法 及系统， 能使 MTC服务器及时地获知网元对终端的监控结果。
为达到上述目的， 本发明的技术方案是这样实现的：
本发明提供了一种发送终端监控 4艮告的方法， 所述方法包括： 终端入网后， MME根据保存的所述终端的签约数据中的监控事件参 数， 检测到监控事件发生后， 向 MTC IWF发送包含监控事件、 终端的外部 标识、 以及 MTC服务器标识或地址的监控事件报告；
MTC IWF根据收到的监控事件报告中的 MTC服务器标识或地址， 向 MTC服务器发送包含监控事件及终端的外部标识的监控事件报告。
上述方案中，在 MME根据保存的所述终端的签约数据中的监控事件参 数， 检测到监控事件发生之前， 上述方法还包括： MME向 HSS获取所述 终端的签约数据， 并保存。
上述方案中，所述 MME向 HSS获取所述终端的签约数据，包括： MME 收到终端发送的附着请求信令或跟踪区更新请求信令后， 向 HSS发送更新 位置请求信令； HSS向 MME返回包含所述终端的签约数据的更新位置认 可信令。
上述方案中， 在 MME向 HSS获取所述终端的签约数据之前， 所述方 法还包括： HSS将监控事件参数、 终端的外部标识、 以及 MTC服务器标识 或地址作为所述终端的签约数据， 并保存。
上述方案中，所述 MME向 MTC IWF发送的监控事件报告还包含协议 识别信息； 所述协议识别信息用于 MTC IWF识别接收到的信令的类别。 上述方案中， 所述 MTC IWF向 MTC服务器发送的监控事件报告还包 含协议识别信息；所述协议识别信息用于 MTC服务器识别接收到的信令的 类别。
本发明还提供了一种发送终端监控 4艮告的系统，所述系统包括： MME、 MTC IWF、 以及 MTC服务器； 其中，
MME, 用于终端入网后， 根据保存的所述终端的签约数据中的监控事 件参数， 检测到监控事件发生后， 向所述 MTC IWF发送包含监控事件、 所 述终端的外部标识、 以及 MTC服务器标识或地址的监控事件报告；
MTC IWF, 用于根据收到的事件报告中的 MTC服务器标识或地址， 向所述 MTC服务器发送包含监控事件及所述终端的外部标识的监控事件 报告；
MTC服务器， 用于接收所述 MTC IWF发送的监控事件报告。
上述方案中， 该系统还包括： HSS, 用于向所述 MME提供所述终端的 签约数据； 所述 MME, 还用于向所述 HSS获取所述终端的签约数据， 并 保存。
上述方案中， 所述 HSS, 还用于将监控事件参数、 终端的外部标识、 以及 MTC服务器标识或地址作为所述终端的签约数据， 并保存。
本发明提供的发送终端监控报告的方法及系统， 终端入网后， MME根 据保存的所述终端的签约数据中的监控事件参数， 检测到监控事件发生后， 向 MTC IWF发送包含监控事件、 终端的外部标识、 以及 MTC服务器标识 或地址的监控事件报告； MTC IWF根据收到的监控事件报告中的 MTC服 务器标识或地址，向 MTC服务器发送包含监控事件及终端的外部标识的监 控事件报告， 如此， 能使 MTC服务器及时地获知网元对终端的监控结果。
另外， MTC服务器根据收到的监控事件报告， 生成事件警告信息， 如 此， 终端所归属的 MTC用户能在 MTC服务器上则能查看到相关的事件警 告信息， 进而能及时地对自身下属的终端进行监控， 提升用户体验。 附图说明
图 1为现有蜂窝无线通信系统的架构示意图；
图 2为本发明发送终端监控报告的方法流程示意图；
图 3为实施例一发送终端监控 4艮告的方法流程示意图；
图 4为实施例二发送终端监控 ^艮告的方法流程示意图；
图 5为本发明发送终端监控报告的系统结构示意图。 具体实施方式
下面结合附图及具体实施例对本发明再作进一步详细的说明。
本发明发送终端监控报告的方法， 如图 2所示， 包括以下步驟： 步驟 201 : 终端入网后， MME根据保存的所述终端的签约数据中的监 控事件参数， 检测到监控事件发生后， 向 MTC IWF发送包含监控事件、 终 端的外部标识、 以及 MTC服务器标识或地址的监控事件报告；
这里， 在执行本步驟之前， 该方法还可以进一步包括：
MME向 HSS获取所述终端的签约数据， 并保存。
其中， 所述 MME向 HSS获取所述终端的签约数据， 具体包括： 终端向 MME发送附着请求信令或跟踪区更新请求信令；
MME向 HSS发送更新位置请求信令；
HSS向 MME返回包含所述终端的签约数据的更新位置认可信令。 所述终端的签约数据包含：监控事件参数、终端的外部标识、以及 MTC 服务器标识或地址等。
所述 MME根据保存的所述终端的签约数据中的监控事件参数,检测到 监控事件发生， 具体为： MME将所述监控事件参数中的设备号与所述终端 自身的设备号进行匹配， 或者， 将所述监控事件参数中的跟踪区位置信息 与所述终端的位置信息进行匹配， 确定能匹配后， 则检测到监控事件发生， 确定不能匹配后， 则未检测到监控事件发生。
在 MME向 HSS获取所述终端的签约数据之前， 该方法还可以进一步 包括： HSS将监控事件参数、 终端的外部标识、 以及 MTC服务器标识或地 址作为所述终端的签约数据， 并保存。
向 MTC IWF发送的事件报告还可以包含： 协议识别信息； 所述协议识 别信息用于 MTC IWF识别接收到的信令的类别。
步驟 202: MTC IWF根据收到的监控事件报告中的 MTC服务器标识 或地址，向 MTC服务器发送包含监控事件及终端的外部标识的监控事件报 告。
其中，向 MTC服务器发送的监控事件报告还可以包含：协议识别信息； 所述协议识别信息用于 MTC服务器识别接收到的信令的类别。
这里， 所述 MTC服务器具体可以是所述终端归属的 MTC服务器， 也 可以是需要获得监控事件报告的其它 MTC服务器。
该方法还可以进一步包括： 所述 MTC服务器根据收到的监控事件报 告， 生成事件警告信息。 其中， 事件警告信息可以包含收到的监控事件报 告。
下面结合实施例对本发明再作进一步详细的描述。
实施例一
本实施例的应用场景为：监控终端的通用集成电路卡（UICC, Universal Integrated Circuit Card )是否被非法盗用。 本实施例发送终端监控报告的方 法， 如图 3所示， 包括以下步驟：
步驟 301: 终端开机后， 向 MME发送附着请求信令；
这里，终端在入网时，与运营商签约需要监控终端与 UICC卡关联变更， 即： 监控终端的 UICC是否被非法盗用。 其中， 在实际应用时， 在与运营商 签约时，运营商可以将监控终端与 UICC卡关联变更的事件定义为监控事件
A, 并在 HSS上设置相应的监控事件参数、 终端的外部标识及 MTC服务器 标识或地址； 其中， 在本实施例中， 所述监控事件参数具体包括以下参数： 监控事件代码： 监控事件 A;
设备号： 终端的国际移动电话设备识别码 ( IMEI, International Mobile
Equipment Identity ) 。
设置的终端的外部标识为 ExID: 设置的 MTC服务器标识或地址为 MTC_Server_A;
其中， MTC服务器标识或地址可以是 MTC服务器的串号外， 还可以 是 MTC服务器的 IP地址。 这里， MTC IWF可以根据 MTC服务器的标识 或地址， 将监控报告发送到正确的 MTC服务器。
运营商设置的监控事件参数、终端的外部标识及 MTC服务器标识或地 址会作为终端的签约数据， 保存在 HSS上。
所述附着请求信令包含终端在移动通信网络的内部标识， 即： 国际移 动用户识另 ll码 ( IMSI, International Mobile Subscriber Identification number )； 其中， UICC卡与 IMSI具有对应关系， 即具有绑定关系； 终端入网后， 网 络中的网元通过识别到的 IMSI作为终端的内部标识， 终端的 IMSI也会作 为终端的签约数据的一部分， 保存在 HSS上。
步驟 302: MME收到附着请求信令后， 读取附着请求信令中的 IMSI, 将 IMSI包含在更新位置请求信令中发送给 HSS;
步驟 303： HSS收到更新位置请求信令后，读取更新位置请求中的 IMSI , 根据 IMSI查询本地数据库，获得 IMSI对应的终端的签约数据，并向 MME 返回包含所述签约数据的更新位置认可信令；
这里， 所述签约数据包括： 监控事件参数、 终端的外部标识和 MTC服 务器标识或地址。 步驟 304: MME收到所述签约数据后， 将所述签约数据保存至本地数 据库；
这里， 本地数据库的格式可以如表 1所示。
Figure imgf000010_0001
表 1
步驟 305: MME读取所述签约数据中的监控事件参数中的监控事件代 码及设备号；
这里， 在本实施例中， 监控事件代码为监控事件 A, 表示需要监控终 端与 UICC卡关联变更的事件。
步驟 306: MME向所述终端发送控制信令， 请求所述终端报告自身的 设备号；
这里， 所述设备号就是指： IMEI。
步驟 307: 所述终端收到控制信令后， 向 MME返回包含自身的设备号 的反馈信令；
步驟 308: MME收到反馈信令后， 将反馈信令中的所述终端的设备号 与所述签约数据中的设备号进行匹配， 确定不匹配后， 生成监控事件报告， 并向 MTC IWF发送生成的监控事件报告；
这里，当 MME确定反馈信令中的所述终端的设备号与所述签约数据中 的设备号不匹配后， 则认为检测到监控事件 A发生， 即： 终端的 UICC被 非法盗用， 此时， 会生成事件报告； 当 MME确定反馈信令中的所述终端的 设备号与所述签约数据中的设备号匹配后， 则认为未检测到监控事件 A发 生， 即： 终端的 UICC没有被非法盗用， 此时， MME的后续处理过程不是 本发明关心的内容。
其中， 所述监控事件报告的内容可以包含： 协议识别信息、 检测到监 控事件发生的终端的 IMSI、 检测到的监控事件、 检测到监控事件发生的终 端的外部标识、 以及 MTC服务器标识或地址等； 其中， 所述协议识别信息 用于 MTC IWF识别接收到的信令的类别， 具体可以为事件报告。在本实施 例中， 检测到的监控事件为监控事件 A, 检测到监控事件发生的终端的外 部标识为 ExID, MTC服务器标识或地址为 MTC_Server_A。
步驟 309: MTC IWF收到监控事件报告后，根据监控事件报告中的 MTC 服务器标识或地址， 向对应的 MTC服务器发送监控事件报告。
这里， 所述 MTC服务器可以是合法使用 UICC卡的终端归属的 MTC 服务器， 也可以是需要获得监控事件报告的其它 MTC服务器。
MTC IWF向 MTC服务器发送的事件报告的内容可以包含： 协议识别 信息、 检测到的监控事件、 以及检测到监控事件发生的终端的外部标识等； 其中， 所述协议识别信息用于 MTC服务器识别接收到的信令的类别， 具体 可以为事件报告。 在本实施例中， 检测到的监控事件为监控事件 A, 检测 到监控事件发生的终端的外部标识为 ExID。
步驟 310: MTC服务器收到监控事件报告后， 保存所述监控事件报告， 并生成事件警告信息， 以便合法使用 UICC卡的终端所归属的 MTC用户能 在 MTC服务器上查看到相关的事件警告信息，进而能及时地对自身下属的 终端进行监控。
实施例二
本实施例的应用场景为： 监控终端是否被非法盗用。 在以下的描述中， 将终端移动前对应的 MME称为原 MME, 将终端移动到新小区后对应的 MME称为新 MME。 本实施例发送终端监控 ^艮告的方法， 如图 4所示， 包 括以下步驟：
步驟 401:当终端移动至新小区，读取小区广播信息中的跟踪区信息后， 将新小区的跟踪区信息与本地保存的跟踪区信息进行匹配， 确定不匹配后 向新 MME发送跟踪区更新请求信令；
这里， 终端在入网时， 与运营商签约需要监控终端位置变更， 即： 监 控终端是否被非法盗用。 其中， 在实际应用时， 在与运营商签约时， 运营 商可以将监控终端位置变更的事件定义为监控事件 B, 并在 HSS上设置相 应的监控事件参数、 终端的外部标识及 MTC服务器标识或地址； 其中， 在 本实施例中， 所述监控事件参数， 具体包括以下参数：
监控事件代码： 监控事件 B;
终端位置信息： 位置 A。
设置的终端的外部标识为 ExID; 设置的 MTC服务器标识或地址： MTC_Server_A;
其中， MTC服务器标识或地址可以是 MTC服务器的串号外， 还可以 是 MTC服务器的 IP地址。 这里， MTC IWF可以根据 MTC服务器的标识 或地址， 将监控报告发送到正确的 MTC服务器。
运营商设置的监控事件参数、终端的外部标识及 MTC服务器标识或地 址会作为终端的签约数据， 保存在 HSS上。 另外， 终端入网后， 网络中的 网元通过识别到的 IMSI作为终端的内部标识。 终端的 IMSI也会作为终端 的签约数据的一部分， 保存 HSS在上。
所述跟踪区更新请求信令包含： 原 MME 为终端分配的临时内部标识 ( GUTI, Global Unique Temporary Identity ) ； 所述 GUTI包含： 原 MME 的标识。
步驟 402: 新 MME收到跟踪区更新请求信令后， 向原 MME发送数据 请求信令； 这里 , 新 MME读取跟踪区更新请求信令中的 GUTI , 获得原 MME的 标识， 进而据此向原 MME发送数据请求信令。
步驟 403： 原 MME收到数据请求信令后， 向新 MME发送所述终端的 IMSI;
步驟 404:新 MME收到所述终端的 IMSI后，将 IMSI包含在更新位置 请求信令中发送给 HSS;
步驟 405: HSS收到更新位置请求信令后，读取更新位置请求中的 IMSI, 根据 IMSI查询本地数据库， 获得所述终端的签约数据， 并向新 MME返回 包含所述签约数据的更新位置认可信令；
这里， 所述签约数据包括： 监控事件参数、 终端的外部标识和 MTC服 务器标识或地址。
步驟 406: 新 MME收到所述签约数据后， 将所述签约数据保存至本地 数据库；
这里， 本地数据库的格式可以如表 1所示。
步驟 407:新 MME读取所述签约数据中的监控事件参数中的监控事件 代码及终端位置信息；
这里， 在本实施例中， 监控事件代码为监控事件 B, 表示需要监控终 端位置变更的事件， 终端位置信息为： 跟踪区 A。
步驟 408:新 MME将所述签约数据中的监控事件参数中的终端位置信 息与本地保存的跟踪区位置信息进行匹配， 确定不匹配后， 生成监控事件 报告， 并向 MTC IWF发送生成的监控事件报告；
这里， 通常，每个 MME都属于一个固定的跟踪区， 并将自身所属的跟 踪区信息保存在本地数据库。在本实施例中，假设新 MME所属的跟踪区信 息为 艮踪区 B。
当新 MME确定本地保存的跟踪区位置信息与所述签约数据中的终端 位置信息不匹配后， 则认为检测到监控事件 B发生， 即： 终端被非法盗用， 此时，会生成事件报告； 当 MME确定本地保存的跟踪区位置信息与所述签 约数据中的终端位置信息匹配后， 则认为未检测到监控事件 B发生， 即： 终端没有被非法盗用，此时， MME的后续处理过程不是本发明关心的内容。
其中， 所述监控事件报告的内容可以包含： 协议识别信息、 检测到监 控事件发生的终端的 IMSI、 检测到的监控事件、 检测到监控事件发生的终 端的外部标识、 以及 MTC服务器标识或地址等； 其中， 所述协议识别信息 用于 MTC IWF识别接收到的信令的类别， 具体可以为事件报告。在本实施 例中， 检测到的监控事件为监控事件 B, 检测到监控事件发生的终端的外 部标识为 ExID, MTC服务器标识或地址为 MTC_Server_A。
步驟 409: MTC IWF收到监控事件报告后，根据监控事件报告中的 MTC 服务器标识或地址， 向对应的 MTC服务器发送监控事件报告。
这里， 所述 MTC服务器具体可以是所述终端归属的 MTC服务器， 也 可以是需要获得监控事件报告的其它 MTC服务器。
MTC IWF向 MTC服务器发送的监控事件报告的内容可以包含： 协议 识别信息、 检测到的监控事件、 以及检测到监控事件发生的终端的外部标 识； 其中， 所述协议识别信息用于 MTC服务器识别接收到的信令的类别， 具体可以为事件报告。 在本实施例中， 检测到的监控事件为监控事件 B, 检测到监控事件发生的终端的外部标识为 ExID。 所述事件报告的内容还可 以进一步包含： 事件发生位置信息， 在本实施例中， 事件发生位置信息为 跟踪区 B。
步驟 410: MTC服务器收到监控事件报告后， 保存所述监控事件报告， 并生成事件警告信息， 以便所述终端所归属的 MTC用户能在 MTC服务器 上查看到相关的事件警告信息， 进而能及时地对自身下属的终端进行监控。
为实现上述方法， 本发明还提供了一种发送终端监控报告的系统， 如 图 5所示， 该系统包括： MME 51、 MTC IWF 52、 以及 MTC服务器 53; 其中，
MME 51 , 用于终端入网后， 根据保存的所述终端的签约数据中的监控 事件参数， 检测到监控事件发生后， 向 MTC IWF 52发送包含监控事件、 所述终端的外部标识、 以及 MTC服务器标识或地址的监控事件报告；
MTC IWF 52,用于根据收到的事件报告中的 MTC服务器标识或地址， 向 MTC服务器 53发送包含监控事件及所述终端的外部标识的监控事件报 告.
MTC服务器 53 , 用于接收 MTC IWF 52发送的监控事件报告。
其中， 该系统还可以进一步包括： HSS, 用于向 MME 51提供所述终 端的签约数据； 所述 MME 51 , 还用于向 HSS获取所述终端的签约数据， 并保存。
所述 HSS, 还用于将监控事件参数、 终端的外部标识、 以及 MTC服务 器标识或地址作为所述终端的签约数据， 并保存。
所述 MTC服务器 53, 还用于根据收到的监控事件报告， 生成事件警 告信息。
这里， 本发明的所述系统中的 MME的具体处理过程已在上文中详述， 不再赘述。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种发送终端监控报告的方法， 其特征在于， 该方法包括： 终端入网后，移动性管理实体 MME根据保存的所述终端的签约数据中 的监控事件参数， 检测到监控事件发生后， 向机器类型通信互操作功能实 体 MTC IWF发送包含监控事件、终端的外部标识、以及机器类型通信 MTC 服务器标识或地址的监控事件报告；
MTC IWF根据收到的监控事件报告中的 MTC服务器标识或地址， 向 MTC服务器发送包含监控事件及终端的外部标识的监控事件报告。
2、 根据权利要求 1所述的方法， 其特征在于， 在 MME根据保存的所 述终端的签约数据中的监控事件参数， 检测到监控事件发生之前， 所述方 法还包括： MME向归属用户服务器 HSS获取所述终端的签约数据， 并保 存。
3、 根据权利要求 2所述的方法， 其特征在于， 所述 MME向 HSS获取 所述终端的签约数据， 包括：
MME收到终端发送的附着请求信令或跟踪区更新请求信令后，向 HSS 发送更新位置请求信令； HSS向 MME返回包含所述终端的签约数据的更 新位置认可信令。
4、 根据权利要求 2或 3所述的方法， 其特征在于， 在 MME向 HSS获 取所述终端的签约数据之前， 所述方法还包括： HSS 将监控事件参数、 终 端的外部标识、 以及 MTC服务器标识或地址作为所述终端的签约数据， 并 保存。
5、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 所述 MME向 MTC IWF发送的监控事件报告还包含协议识别信息； 所述协议识别信息用 于 MTC IWF识别接收到的信令的类别。
6、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 所述 MTC IWF 向 MTC服务器发送的监控事件报告还包含协议识别信息；所述协议识别信 息用于 MTC服务器识别接收到的信令的类别。
7、一种发送终端监控报告的系统，其特征在于，所述系统包括： MME、 MTC IWF、 以及 MTC服务器； 其中，
MME, 用于终端入网后， 根据保存的所述终端的签约数据中的监控事 件参数， 检测到监控事件发生后， 向所述 MTC IWF发送包含监控事件、 所 述终端的外部标识、 以及 MTC服务器标识或地址的监控事件报告；
MTC IWF, 用于根据收到的事件报告中的 MTC服务器标识或地址， 向所述 MTC服务器发送包含监控事件及所述终端的外部标识的监控事件 报告；
MTC服务器， 用于接收所述 MTC IWF发送的监控事件报告。
8、 根据权利要求 7所述的系统， 其特征在于，
所述系统还包括： HSS, 用于向所述 MME提供所述终端的签约数据； 所述 MME, 还用于向所述 HSS获取所述终端的签约数据， 并保存。
9、 根据权利要求 8所述的系统， 其特征在于， 所述 HSS, 还用于将监 控事件参数、 终端的外部标识、 以及 MTC服务器标识或地址作为所述终端 的签约数据， 并保存。
10、 根据权利要求 7、 8或 9所述的系统， 其特征在于， 所述 MME向 MTC IWF发送的监控事件报告还包含协议识别信息； 所述协议识别信息用 于 MTC IWF识别接收到的信令的类别。
11、根据权利要求 7、 8或 9所述的系统， 其特征在于， 所述 MTC IWF 向 MTC服务器发送的监控事件报告还包含协议识别信息；所述协议识别信 息用于 MTC服务器识别接收到的信令的类别。
PCT/CN2012/075473 2012-03-22 2012-05-14 一种发送终端监控报告的方法及系统 WO2013139073A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2012100793080A CN103327524A (zh) 2012-03-22 2012-03-22 一种发送终端监控报告的方法及系统
CN201210079308.0 2012-03-22

Publications (1)

Publication Number Publication Date
WO2013139073A1 true WO2013139073A1 (zh) 2013-09-26

Family

ID=49196000

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075473 WO2013139073A1 (zh) 2012-03-22 2012-05-14 一种发送终端监控报告的方法及系统

Country Status (2)

Country Link
CN (1) CN103327524A (zh)
WO (1) WO2013139073A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106462536B (zh) * 2014-05-23 2019-11-08 富士通互联科技有限公司 机器类通信事件检测方法、系统及非暂态计算机可读介质
CN107295554A (zh) * 2016-03-30 2017-10-24 中兴通讯股份有限公司 一种管理应用状态的方法和装置
CN107770756A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种监控方法、终端、服务器、网关设备以及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011084010A2 (en) * 2010-01-08 2011-07-14 Lg Electronics Inc. Method for performing offline indication of machine type communication device in mobile communication system
CN102202270A (zh) * 2010-03-24 2011-09-28 中兴通讯股份有限公司 基于机器类通信的消息传输方法及互通功能实体
CN102325004A (zh) * 2011-07-15 2012-01-18 电信科学技术研究院 信令发送方法和设备
CN102333294A (zh) * 2011-09-23 2012-01-25 电信科学技术研究院 基于去附着流程更新终端可达状态信息的方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056140B (zh) * 2009-11-06 2013-08-07 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102158835B (zh) * 2010-02-12 2014-11-05 华为技术有限公司 机器类型通信信息传输方法和设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011084010A2 (en) * 2010-01-08 2011-07-14 Lg Electronics Inc. Method for performing offline indication of machine type communication device in mobile communication system
CN102202270A (zh) * 2010-03-24 2011-09-28 中兴通讯股份有限公司 基于机器类通信的消息传输方法及互通功能实体
CN102325004A (zh) * 2011-07-15 2012-01-18 电信科学技术研究院 信令发送方法和设备
CN102333294A (zh) * 2011-09-23 2012-01-25 电信科学技术研究院 基于去附着流程更新终端可达状态信息的方法及装置

Also Published As

Publication number Publication date
CN103327524A (zh) 2013-09-25

Similar Documents

Publication Publication Date Title
US9491594B2 (en) Method and system for managing terminal group
US9294924B2 (en) Monitoring suspicious events in a cellular network
CN103209402A (zh) 终端组可及性确定方法及系统
KR20110081750A (ko) 이동통신 시스템에서의 ｍｔｃ 장치의 모니터링 방법
CN102036222A (zh) 一种m2m设备归属网络运营商变更的方法和系统
US8774864B2 (en) Locking of communication device
EP2824967B1 (en) Device discovery method, device, and system
RU2013141467A (ru) Передача отчетов в системах связи
US8958792B2 (en) Method and system for selecting mobility management entity of terminal group
WO2012113178A1 (zh) 检测终端连接丢失的方法及装置
US9615240B2 (en) Accessibility management method and device for M2M terminal/terminal peripheral
WO2013139073A1 (zh) 一种发送终端监控报告的方法及系统
WO2011116603A1 (zh) 对mtc设备进行分组管理的方法及系统
WO2013123716A1 (zh) 一种监控终端行为异常的方法和系统
CN103096433A (zh) 一种终端组的服务网关选择方法及系统
WO2017020748A1 (zh) 信令跟踪任务的处理方法及装置
US8761767B2 (en) Method, system, terminal and network side for triggering terminal response
CN112637841A (zh) 一种电力无线专网的国际移动设备标识检验方法和系统
WO2012129853A1 (zh) 一种检测机器类型通信终端移动性状态的方法和系统
WO2012152046A1 (zh) 终端接入方法及系统
US10827347B1 (en) Dynamic identities in a mobile device
CN102857899B (zh) 一种mtc设备的接入控制方法和系统
WO2013117056A1 (zh) 终端触发方法及装置
WO2013113183A1 (zh) 触发消息的发送方法、装置及系统

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: 12872178

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12872178

Country of ref document: EP

Kind code of ref document: A1