WO2016127612A1 - 监控处理方法及装置 - Google Patents

监控处理方法及装置 Download PDF

Info

Publication number
WO2016127612A1
WO2016127612A1 PCT/CN2015/086903 CN2015086903W WO2016127612A1 WO 2016127612 A1 WO2016127612 A1 WO 2016127612A1 CN 2015086903 W CN2015086903 W CN 2015086903W WO 2016127612 A1 WO2016127612 A1 WO 2016127612A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
task
request message
identifier
update
Prior art date
Application number
PCT/CN2015/086903
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 中兴通讯股份有限公司
Priority to US15/550,938 priority Critical patent/US10419950B2/en
Priority to EP15881769.2A priority patent/EP3258644B1/en
Publication of WO2016127612A1 publication Critical patent/WO2016127612A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of 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
    • 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 the field of communications, and in particular to a monitoring and processing method and apparatus.
  • M2M Machine to Machine
  • M2M applications run on the M2M terminals through the underlying bearer network, for example, Global System for Mobile communications (referred to as Global System for Mobile communications, referred to as GSM), Wideband Code Division Multiple Access (WCDMA), Wifi, etc., connected to the network side service platform. Therefore, the administrator of an M2M application can perform monitoring of the running status of the M2M terminal by accessing the service platform on the network side.
  • GSM Global System for Mobile communications
  • WCDMA Wideband Code Division Multiple Access
  • the administrator of the intelligent traffic monitoring system can connect to the network service platform by accessing the internet, and the service platform can monitor the connection status of the surveillance camera on one or several roads, and after detecting that the surveillance camera is disconnected. Can receive alert information from the business platform.
  • the monitoring task similar to the above scenario is completed by comparing the traditional methods. For example, if you want to know whether one or several M2M terminals are online, you need the application or service platform to send polling instructions to the M2M terminal. The feedback to the M2M terminal indicates that the M2M terminal is still online. If the feedback of the M2M terminal is not received within a specified time, the M2M terminal is disconnected.
  • the embodiment of the invention provides a monitoring processing method and device, so as to at least solve the monitoring scheme in the related art, which not only makes the operation of the service platform and the corresponding application complicated, but also has low monitoring efficiency of the monitoring task.
  • a monitoring processing method including: monitoring a receiver to receive a monitoring request message sent by a monitoring initiator, where the monitoring request message includes a monitoring task; and the monitoring receiver Performing monitoring processing by interacting with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task.
  • the monitoring identifier is allocated by the monitoring initiator and carried in the monitoring request message; Or the monitoring identifier is allocated by the monitoring receiver to the monitoring task in the monitoring request message after receiving the monitoring request message sent by the monitoring initiator by the monitoring receiver.
  • the monitoring receiver performs an interaction monitoring process with the monitoring performer according to the monitoring identifier corresponding to the monitoring task, where the monitoring receiver sends a monitoring execution request message to the monitoring performer, where The monitoring execution request message includes the monitoring identifier, and the monitoring task.
  • the method further includes: sending a subscription data request message to the home subscriber server HSS, where the subscription data request message is carried in the subscription data request message Identifying a terminal identifier of the terminal corresponding to the monitoring task, and/or the monitoring identifier; determining, by the subscription data response message received from the HSS, the monitoring performer for performing the monitoring task.
  • the monitoring receiver performs an interaction monitoring process with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task, where the monitoring receiver receives the monitoring initiator to send a monitoring termination request message for requesting termination of the monitoring task, wherein the monitoring termination request message includes the monitoring identifier indicating the terminated monitoring task; the monitoring receiver according to the monitoring termination request And sending a stop monitoring request message to the monitoring performer, where the monitoring performer terminates the monitoring task according to the monitoring identifier, where the stop monitoring request message includes the monitoring task indicating that the monitoring is terminated Monitoring ID.
  • the monitoring receiver performs an interaction monitoring process with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task, where the monitoring receiver receives the monitoring initiator to send The update monitoring request message for requesting the update of the monitoring task, wherein the update monitoring request message includes the monitoring identifier indicating the updated monitoring task, and monitoring parameters of the monitoring task update; And the monitoring receiver sends a monitoring task update request message to the monitoring performer according to the update monitoring request message, where the monitoring performer updates the monitoring according to the monitoring identifier and the updated monitoring parameter.
  • the task wherein the monitoring task update request message includes the monitoring identifier indicating the updated monitoring task, and the monitoring parameter of the monitoring task update.
  • the monitoring parameter included in the monitoring task includes at least one of the following: a monitored terminal, a monitored event, a number of monitoring reports, a monitoring duration, a monitoring start time, a monitoring end time, and a monitored event. operating.
  • a monitoring processing method including: a monitoring performer receiving a monitoring execution request message sent by a monitoring receiver, wherein the monitoring execution request message includes identifier for identifying the monitoring The monitoring identifier of the task and the monitoring task; the monitoring performer performs monitoring processing on the monitoring task corresponding to the monitoring identifier.
  • the method further includes: the monitoring performer receiving, by the monitoring receiver, requesting to terminate the monitoring task. Stopping the monitoring request message, where the monitoring and stopping request message includes the monitoring identifier indicating the monitoring task that is terminated; and the monitoring execution of the monitoring task corresponding to the monitoring identifier by the monitoring performer includes: The monitoring performer deletes the monitoring task according to the monitoring identifier.
  • the method further includes: the monitoring executor receiving, by the monitoring receiver, requesting to perform the monitoring task An update update monitoring request message, where the monitoring task update request message includes the monitoring identifier indicating the updated monitoring task, and the monitoring parameter of the monitoring task update; the monitoring performer is to the monitoring
  • the monitoring task execution monitoring process corresponding to the identifier includes: the monitoring performer according to the monitoring identifier in the monitoring task update request message, and the monitoring parameter updated by the monitoring task, and monitoring parameters of the monitoring task Updated to the monitoring parameters of the received monitoring task.
  • the monitoring parameter included in the monitoring task includes at least one of the following: a monitored terminal, a monitored event, a number of monitoring reports, a monitoring duration, a monitoring start time, a monitoring end time, and a monitored event. operating.
  • a monitoring processing apparatus which is applied to a monitoring receiver, and includes: a first receiving module, configured to receive a monitoring request message sent by a monitoring initiator, where the monitoring request message is The monitoring task is included; the first processing module is configured to perform monitoring processing by interacting with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task.
  • the monitoring identifier is allocated by the monitoring initiator and carried in the monitoring request message; or the monitoring identifier is received by the monitoring receiver after receiving the monitoring request message sent by the monitoring initiator Thereafter, the monitoring receiver allocates the monitoring task in the monitoring request message.
  • the first processing module includes: a first sending unit, configured to send a monitoring execution request message to the monitoring performer, where the monitoring execution request message includes the monitoring identifier, and the monitoring task.
  • a first sending unit configured to send a monitoring execution request message to the monitoring performer, where the monitoring execution request message includes the monitoring identifier, and the monitoring task.
  • the first processing module further includes: a second sending unit, configured to send a subscription data request message to the home subscriber server HSS, where the subscription data request message carries a terminal for identifying the monitoring task The terminal identifier, and/or the monitoring identifier; the first determining unit is configured to determine, according to the subscription data response message received from the HSS, the monitoring performer for performing the monitoring task.
  • a second sending unit configured to send a subscription data request message to the home subscriber server HSS, where the subscription data request message carries a terminal for identifying the monitoring task The terminal identifier, and/or the monitoring identifier; the first determining unit is configured to determine, according to the subscription data response message received from the HSS, the monitoring performer for performing the monitoring task.
  • the first processing module includes: a first receiving unit, configured to receive a monitoring termination request message sent by the monitoring initiator for requesting termination of the monitoring task, where the monitoring termination request message includes The monitoring identifier of the monitoring task indicating termination; the third sending unit is configured to be according to the Monitoring the termination request message, and sending a stop monitoring request message to the monitoring performer, where the monitoring performer terminates the monitoring task according to the monitoring identifier, where the stop monitoring request message includes the indication that the indication is terminated The monitoring identifier of the monitoring task.
  • the first processing module includes: a second receiving unit, configured to receive an update monitoring request message sent by the monitoring initiator for requesting update of the monitoring task, where the update monitoring request message is And the fourth sending unit is configured to send a monitoring task update request message to the
  • the monitoring performer is configured to update, by the monitoring performer, the monitoring task according to the monitoring identifier, and the updated monitoring parameter, where the monitoring task update request message includes the indication that the monitoring task is updated Monitoring indicators, and monitoring parameters of the monitoring task updates.
  • the monitoring parameter included in the monitoring task includes at least one of the following: a monitored terminal, a monitored event, a number of monitoring reports, a monitoring duration, a monitoring start time, a monitoring end time, and a monitored event. operating.
  • an interface network element which is located in a bearer network, and includes the apparatus described in any one of the above.
  • the interface network element comprises at least one of the following: a service capability deployment function entity SCEF, an Internet work function entity IWF.
  • SCEF service capability deployment function entity
  • IWF Internet work function entity
  • a monitoring processing apparatus which is applied to a monitoring performer, and includes: a second receiving module, configured to receive a monitoring execution request message sent by a monitoring receiver, wherein the monitoring execution request The message includes a monitoring identifier for identifying the monitoring task and the monitoring task.
  • the second processing module is configured to perform monitoring processing on the monitoring task according to the monitoring identifier.
  • the apparatus further includes: a third receiving module, configured to receive a stop monitoring request message sent by the monitoring receiver for requesting termination of the monitoring task, where the stop monitoring request message includes an indication termination The monitoring identifier of the monitoring task; the second processing module is further configured to delete the monitoring task according to the monitoring identifier.
  • a third receiving module configured to receive a stop monitoring request message sent by the monitoring receiver for requesting termination of the monitoring task, where the stop monitoring request message includes an indication termination The monitoring identifier of the monitoring task
  • the second processing module is further configured to delete the monitoring task according to the monitoring identifier.
  • the device further includes: a fourth receiving module, configured to receive an update monitoring request message sent by the monitoring receiver for requesting update of the monitoring task, where the monitoring task update request message includes And the monitoring identifier of the monitoring task that is updated, and the monitoring parameter of the monitoring task update; the second processing module is further configured to: according to the monitoring identifier in the monitoring task update request message, The monitoring parameter of the monitoring task update is updated, and the monitoring parameter of the monitoring task is updated to the monitoring parameter of the received monitoring task.
  • a fourth receiving module configured to receive an update monitoring request message sent by the monitoring receiver for requesting update of the monitoring task, where the monitoring task update request message includes And the monitoring identifier of the monitoring task that is updated, and the monitoring parameter of the monitoring task update
  • the second processing module is further configured to: according to the monitoring identifier in the monitoring task update request message, The monitoring parameter of the monitoring task update is updated, and the monitoring parameter of the monitoring task is updated to the monitoring parameter of the received monitoring task.
  • the monitoring parameter included in the monitoring task includes at least one of the following: a monitored terminal, and monitoring The number of events, the number of monitoring reports, the duration of monitoring, the monitoring start time, the monitoring end time, and the actions performed after the monitored events occur.
  • a monitoring device located in a carrier network, comprising the apparatus of any of the above.
  • the monitoring device comprises at least one of: a home subscriber server HSS, a mobility management entity MME, and a serving general packet radio service GPRS support node SGSN.
  • the monitoring receiver receives the monitoring request message sent by the monitoring initiator, where the monitoring request message includes a monitoring task, and the monitoring receiver according to the monitoring identifier corresponding to the monitoring task
  • the monitoring initiator and/or the monitoring performer perform the interactive monitoring process, and solve the monitoring scheme in the related technology, which not only makes the operation of the service platform and the corresponding application complicated, but also has low monitoring efficiency of the monitoring task, thereby achieving the problem.
  • the interactive monitoring process is performed according to the monitoring identifier corresponding to the monitoring task, which not only effectively reduces the complexity of monitoring, but also monitors the cost, and improves the monitoring efficiency.
  • FIG. 1 is a flowchart of a first method of monitoring processing according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a second method of monitoring processing according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of a monitoring processing apparatus 1 according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 5 is a block diagram 2 of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 6 is a block diagram 3 of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 7 is a block diagram 4 of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of an interface network element according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of a monitoring processing apparatus 2 according to an embodiment of the present invention.
  • FIG. 10 is a block diagram 1 of a preferred structure of a monitoring processing device 2 according to an embodiment of the present invention.
  • FIG. 11 is a block diagram 2 of a preferred structure of a monitoring processing device 2 according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a monitoring apparatus according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a monitoring processing method according to an embodiment of the present invention. As shown in FIG. 1, the flow includes the following steps:
  • Step S102 The monitoring receiver receives the monitoring request message sent by the monitoring initiator, where the monitoring request message includes a monitoring task.
  • Step S104 The monitoring receiver performs monitoring process interaction with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task.
  • the monitoring process is performed according to the monitoring identifier corresponding to the monitoring task, which not only solves the monitoring scheme in the related technology, but also makes the operation of the service platform and the corresponding application complicated, and the monitoring efficiency of the monitoring task is low. In turn, the complexity of monitoring is effectively reduced, and the cost is monitored, and the effect of monitoring efficiency is improved.
  • the source of the foregoing monitoring identifier may be multiple.
  • the monitoring identifier may be allocated by the monitoring initiator and carried in the monitoring request message.
  • the monitoring identifier may also be sent by the monitoring receiver after receiving the monitoring initiator. After monitoring the request message, the monitoring receiver allocates the monitoring task in the monitoring request message.
  • the “monitoring process” herein refers to monitoring a series of monitoring-related operations performed by the receiver, for example, may include sending a monitoring task to the monitoring performer to instruct the monitoring performer to perform monitoring on the monitoring task.
  • the operation may also include: sending a stop monitoring request message to the monitoring performer for monitoring the related operation of the executor to terminate the monitoring task according to the monitoring identifier; or sending a monitoring task update request message to the monitoring executor for monitoring the executor according to the monitoring identifier
  • the related operations of the updated monitoring parameter update monitoring task are described below.
  • the monitoring receiver performs the monitoring process by interacting with the monitoring executor according to the monitoring identifier corresponding to the monitoring task, and the monitoring receiver may send the monitoring execution request message to the monitoring executor, where the monitoring execution request message includes the monitoring identifier. And monitoring tasks. Corresponding to the monitoring identifier according to the monitoring identifier The monitoring tasks are monitored and processed.
  • the server (Home Subscriber Server, referred to as HSS) sends a subscription data request message, where the subscription data request message carries a terminal identifier for identifying a terminal corresponding to the monitoring task, and/or a monitoring identifier; according to the received from the HSS
  • the monitoring executor for performing the monitoring task is determined in the contract data response message.
  • the monitoring receiver performs the monitoring process according to the monitoring identifier corresponding to the monitoring task and the monitoring initiator and/or the monitoring executor.
  • the monitoring receiver may also include: the monitoring receiver receives the monitoring sent by the monitoring initiator to request the termination of the monitoring task.
  • the termination request message wherein the monitoring termination request message includes a monitoring identifier indicating the terminated monitoring task; the monitoring receiver sends a stop monitoring request message to the monitoring performer according to the monitoring termination request message, and the monitoring performer terminates the monitoring according to the monitoring identifier.
  • the task wherein the stop monitoring request message includes a monitoring identifier indicating the terminated monitoring task. That is, according to the monitoring identifier, the deletion task is performed on the monitoring task corresponding to the monitoring identifier.
  • the monitoring receiver performs the monitoring process by interacting with the monitoring initiator and/or the monitoring performer according to the monitoring identifier corresponding to the monitoring task.
  • the monitoring receiver may further include: receiving, by the monitoring receiver, the monitoring initiator to request to update the monitoring task.
  • the update monitoring request message wherein the update monitoring request message includes a monitoring identifier indicating the updated monitoring task, and a monitoring parameter for monitoring the task update; and the monitoring receiver sends the monitoring task update request message to the monitoring execution according to the update monitoring request message.
  • the monitoring performer updates the monitoring task according to the monitoring identifier and the updated monitoring parameter, wherein the monitoring task update request message includes a monitoring identifier indicating the updated monitoring task, and a monitoring parameter for monitoring the task update. That is, according to the monitoring identifier, the monitoring task corresponding to the monitoring identifier is updated.
  • the monitoring task includes multiple monitoring parameters, for example, at least one of the following: the monitored terminal, the monitored event, the number of monitoring reports, the monitoring duration, the monitoring start time, and the monitoring end time. The operation performed after the monitored event occurs.
  • FIG. 2 is a flowchart of a second method for monitoring processing according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • step S202 the monitoring performer receives the monitoring execution request message sent by the monitoring receiver, where the monitoring execution request message includes a monitoring identifier and a monitoring task for identifying the monitoring task.
  • Step S204 The monitoring performer performs monitoring processing on the monitoring task corresponding to the monitoring identifier.
  • the monitoring process is performed interactively according to the monitoring identifier corresponding to the monitoring task, which not only solves the monitoring scheme in the related technology, but also makes the operation of the service platform and the corresponding application complicated, and
  • the problem of low monitoring efficiency of the control task achieves the effect of effectively reducing the complexity of monitoring, monitoring the cost, and improving the monitoring efficiency.
  • the “monitoring process” herein refers to monitoring a series of monitoring-related operations performed by the performer, for example, may include monitoring operations on the monitoring tasks, and may also include updating the monitoring tasks and deleting the processing operations. , respectively, explained below.
  • the monitoring executor performing the monitoring process on the monitoring task corresponding to the monitoring identifier may include: the monitoring executor performing the monitoring operation according to the received monitoring task sent by the monitoring receiver.
  • the monitoring executor may further receive a stop monitoring request message sent by the monitoring receiver for requesting termination of the monitoring task, where the stop monitoring request message is included
  • the monitoring identifier of the monitoring task indicating the termination is performed; after that, the monitoring performer performs the monitoring process on the monitoring task corresponding to the monitoring identifier, including: the monitoring performer deletes the monitoring task according to the monitoring identifier.
  • the monitoring performer may further receive an update monitoring request message sent by the monitoring receiver for requesting update of the monitoring task, where the monitoring task update request is received.
  • the message includes a monitoring identifier indicating the updated monitoring task, and a monitoring parameter for monitoring the task update.
  • the monitoring performer performs monitoring processing on the monitoring task corresponding to the monitoring identifier, including: monitoring the monitoring device according to the monitoring task update request message The identifier, and the monitoring parameter of the monitoring task update, update the monitoring parameter of the monitoring task to the monitoring parameter of the received monitoring task.
  • the monitoring parameter included in the monitoring task may also include at least one of the following: the monitored terminal, the monitored event, the number of monitoring reports, the monitoring duration, the monitoring start time, the monitoring end time, and the monitored event occurs. Operation.
  • a monitoring processing device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a monitoring processing apparatus according to an embodiment of the present invention. As shown in FIG. 3, the apparatus is applied to a monitoring receiver, including a first receiving module 32 and a first processing module 34. Description.
  • the first receiving module 32 is configured to receive the monitoring request message sent by the monitoring initiator, where the monitoring request message includes a monitoring task; the first processing module 34 is connected to the first receiving module 32, and is configured to correspond to the monitoring task.
  • the monitoring identifier interacts with the monitoring initiator and/or the monitoring performer to perform monitoring processing.
  • the monitoring identifier may be allocated by the monitoring initiator and carried in the monitoring request message; or the monitoring identifier may also be received by the monitoring receiver after receiving the monitoring request message sent by the monitoring initiator.
  • the monitoring task assignment in the monitoring request message may be allocated by the monitoring initiator and carried in the monitoring request message; or the monitoring identifier may also be received by the monitoring receiver after receiving the monitoring request message sent by the monitoring initiator. The monitoring task assignment in the monitoring request message.
  • FIG. 4 is a block diagram of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention. As shown in FIG. 4, the first processing module 34 includes: a first sending unit 42 A transmitting unit 42 will be described.
  • the first sending unit 42 is configured to send a monitoring execution request message to the monitoring performer, where the monitoring execution request message includes a monitoring identifier and a monitoring task.
  • the first processing module 34 includes, in addition to the structure shown in FIG.
  • the second transmitting unit 52 and the first determining unit 54 describe the first processing module 34 below.
  • the second sending unit 52 is configured to send a subscription data request message to the home subscriber server HSS, where the subscription data request message carries a terminal identifier for identifying a terminal corresponding to the monitoring task, and/or a monitoring identifier.
  • the first determining unit 54 Connected to the second sending unit 52 and the first sending unit 42 described above, and configured to determine a monitoring performer for performing a monitoring task according to the subscription data response message received from the HSS.
  • FIG. 6 is a block diagram 3 of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to the embodiment of the present invention.
  • the first processing module 34 includes: a first receiving unit 62 and a third transmitting unit 64.
  • the first processing module 34 will be described below.
  • the first receiving unit 62 is configured to receive a monitoring termination request message sent by the monitoring initiator for requesting termination of the monitoring task, where the monitoring termination request message includes a monitoring identifier indicating the terminated monitoring task, and the third sending unit 64, Connected to the first receiving unit 62, configured to send a stop monitoring request message to the monitoring performer according to the monitoring termination request message, for monitoring the executor to terminate the monitoring task according to the monitoring identifier, wherein the stop monitoring request message includes monitoring indicating termination The monitoring ID of the task.
  • FIG. 7 is a block diagram of a preferred structure of the first processing module 34 in the monitoring processing device 1 according to an embodiment of the present invention. As shown in FIG. 7, the first processing module 34 includes: a second receiving unit 72 and a fourth transmitting unit 74. The first processing module 34 will be described below.
  • the second receiving unit 72 is configured to receive, by the monitoring initiator, an update monitoring request message for requesting to update the monitoring task, where the update monitoring request message includes a monitoring identifier indicating the updated monitoring task, and the monitoring task update Monitoring the parameter;
  • the fourth sending unit 74 is connected to the second receiving unit 72, and configured to send the monitoring task update request message to the monitoring performer for monitoring the performer according to the monitoring identifier and the monitoring of the update according to the update monitoring request message.
  • the parameter update monitoring task wherein the monitoring task update request message includes a monitoring identifier indicating the updated monitoring task, and a monitoring parameter for monitoring the task update.
  • the monitoring parameters included in the foregoing monitoring task include at least one of the following: a monitored terminal, The monitored event, the number of monitoring reports, the duration of monitoring, the monitoring start time, the monitoring end time, and the actions performed after the monitored event occurs.
  • FIG. 8 is a structural block diagram of an interface network element according to an embodiment of the present invention. As shown in FIG. 8, the interface network element 80 is located in a bearer network, and includes a monitoring processing device 82 of any one of the foregoing.
  • the interface network element may include at least one of a service capability expansion service entity (Service Capability Server, SCEF for short) and an Internetworking function entity (Interworking Function, IWF for short).
  • SCEF Service Capability Server
  • IWF Internetworking Function
  • FIG. 9 is a structural block diagram of a monitoring processing apparatus 2 according to an embodiment of the present invention. As shown in FIG. 9, the apparatus is applied to a monitoring performer, and includes: a second receiving module 92 and a second processing module 94. Be explained.
  • the second receiving module 92 is configured to receive the monitoring execution request message sent by the monitoring receiver, where the monitoring execution request message includes a monitoring identifier and a monitoring task for identifying the monitoring task, and the second processing module 94 is connected to the second The receiving module 92 is configured to perform monitoring processing on the monitoring task according to the monitoring identifier.
  • FIG. 10 is a block diagram of a preferred structure of a monitoring processing device 2 according to an embodiment of the present invention. As shown in FIG. 9, the device includes a third receiving module 1002 in addition to all the structures shown in FIG. The preferred structure will be described.
  • the third receiving module 1002 is connected to the second receiving module 92, and is configured to receive a stop monitoring request message sent by the monitoring receiver for requesting termination of the monitoring task, where the stop monitoring request message includes a monitoring task indicating termination
  • the second processing module 94 is connected to the third receiving module 1002, and is further configured to delete the monitoring task according to the monitoring identifier.
  • FIG. 11 is a block diagram of a preferred structure of a monitoring processing device 2 according to an embodiment of the present invention. As shown in FIG. 11, the device includes a fourth receiving module 1102 in addition to all the structures shown in FIG. The preferred structure will be described.
  • the fourth receiving module 1102 is connected to the second receiving module 92, and is configured to receive an update monitoring request message sent by the monitoring receiver for requesting update of the monitoring task, where the monitoring task update request message includes monitoring indicating the update.
  • the second processing module 94 is connected to the fourth receiving module 1102, and is further configured to monitor the monitoring identifier in the request message according to the monitoring task, and monitor the monitoring parameter of the task update.
  • the monitoring parameters of the monitoring task are updated to the monitoring parameters of the received monitoring task.
  • the monitoring parameters included in the foregoing monitoring task may include at least one of the following: a monitored terminal, a monitored event, a number of monitoring reports, a monitoring duration, a monitoring start time, a monitoring end time, The action performed after the monitored event occurs.
  • FIG. 12 is a structural block diagram of a monitoring device according to an embodiment of the present invention. As shown in FIG. 12, the monitoring device 1200 is located in a bearer network, and includes the monitoring processing device 2120 of any of the above.
  • the monitoring device may include at least one of the following: a home subscriber server HSS, a Mobility Management Entity (MME), and a General Packet Radio Service (GPRS) support node (Serving) GPRS Supporting Node, referred to as SGSN).
  • HSS Home Subscriber server
  • MME Mobility Management Entity
  • GPRS General Packet Radio Service
  • SGSN General Packet Radio Service Supporting Node
  • the monitoring solution in the related art is effectively solved, which not only makes the operation of the service platform and the corresponding application complicated, but also has low monitoring efficiency of the monitoring task, thereby effectively reducing the monitoring.
  • the method of executing and managing the monitoring task is implemented by the underlying bearer network. Since any M2M terminal must first connect to the underlying bearer network, the underlying bearer network can directly and quickly detect whether the terminal connected to its network is online, and whether it restores the connection, and can provide more monitoring services, such as Whether the M2M terminal moves out of the known range, whether the device number of the M2M terminal and the incoming network card do not match, and the like. Moreover, according to the pre-configured indication of the application or the service platform, the response operation may be performed immediately after the event detection, for example, rejecting the access of the M2M terminal, reducing the scheduling time slot of the M2M terminal, and the like.
  • the operation and complexity of the service platform and the application can be greatly reduced, and the design cycle of the application is shorter, thereby greatly reducing the development cycle and maintenance cost.
  • the M2M application or service platform is called the monitoring initiator;
  • the underlying bearer network usually has a network element for receiving the service platform or the application, and the network element interacts with the service platform or the application through an interface protocol different from the internal network of the bearer network, and the network element performs the received information.
  • the network element that receives the monitoring instruction from the service platform or the application is referred to as a monitoring receiver;
  • the underlying bearer network has a dedicated network element to detect events that need to be monitored, for example, MME, SGSN, HSS, etc., which are referred to as monitoring performers in this embodiment, and may require multiple implementations of monitoring on the bearer network.
  • the network element coordinates operation, and the monitoring performer may include one or more bearer network elements.
  • the monitoring performer may be an MME, or an SGSN, or an HSS, or an MME and an HSS, or an SGSN, an HSS, or the like.
  • the subject of the monitoring identifier allocation is different according to the source of the monitoring identifier (for example, the supervisor can be assigned by the monitoring receiver)
  • the control identifier may also be assigned by the monitoring initiator.
  • the monitoring task may be performed in the following two manners according to the monitoring identifier:
  • Mode 1 (the monitoring identifier is assigned by the monitoring receiver):
  • the monitoring initiator sends a monitoring request message to the monitoring receiver.
  • the request message includes a monitoring task.
  • the monitoring task includes parameters. Different combinations of monitoring parameters constitute corresponding monitoring tasks. For example, the following combinations may be included, but Limited to this:
  • monitored terminals events to be monitored; 2) monitored terminals, events to be monitored, number of monitoring reports; 3) monitored terminals, events to be monitored, duration of monitoring; 4) monitored Terminal, event to be monitored, monitoring start time, monitoring end time; 5) monitored terminal, event to be monitored, monitoring start time, monitoring duration; 6) monitored terminal, event to be monitored, after event The action to be performed.
  • the monitoring receiver After receiving the monitoring request message, the monitoring receiver sends a response message to the monitoring initiator.
  • the monitoring receiver confirms that the monitoring task can be performed, the monitoring task is assigned a monitoring identifier and is included in the response message.
  • the monitoring identifier is used to identify a monitoring task.
  • the refusal to perform the monitoring task is indicated in the response message.
  • the monitoring receiver sends the monitoring task to the monitoring performer, which includes the monitoring identifier.
  • the monitoring performer saves the monitoring task.
  • the monitoring performer After detecting the event to be monitored, the monitoring performer sends a monitoring report to the monitoring receiver, which includes the monitoring identifier.
  • the monitoring receiver After receiving the monitoring report, the monitoring receiver sends the monitoring report to the monitoring initiator.
  • the monitoring initiator may also send a monitoring stop request message to the monitoring receiver, where the request message includes a monitoring identifier
  • the monitoring receiver After receiving the monitoring stop request message, the monitoring receiver sends a monitoring termination message to the monitoring performer, which includes the monitoring identifier.
  • the monitoring performer After receiving the monitoring termination command, the monitoring performer checks whether the local monitoring task associated with the received monitoring identifier is saved.
  • the monitoring initiator may also send an update monitoring request message to the monitoring receiver, where the request message includes a monitoring identifier and a parameter of the monitoring task that needs to be updated, and the monitoring identifier is used to indicate which monitoring task parameter needs to be updated, and the monitoring needs to be updated.
  • the parameters of the task can contain one or more of the following:
  • Monitoring events (renewing the monitoring events corresponding to the monitoring tasks of the monitoring tasks); 2) monitoring the number of reports (renewing the number of monitoring reports corresponding to the monitoring tasks of the monitoring identifiers); 3) monitoring the duration of the monitoring (upgrading the monitoring indicators corresponding to monitoring)
  • the monitoring of the task is continued; 4) the monitoring start time (update the monitoring start time of the monitoring task corresponding to the monitoring task); 5) the monitoring end time (update the monitoring end corresponding to the monitoring end of the monitoring task); 6) after the event occurs The operation performed (update the operation of the monitoring ID corresponding to the event of the monitoring task); 7) The terminal to be monitored.
  • the monitoring receiver After receiving the update monitoring request message, the monitoring receiver sends the monitoring identifier and the parameter of the monitoring task that needs to be updated to the monitoring performer.
  • the monitoring performer After receiving the update monitoring request message, the monitoring performer checks whether the local monitoring task corresponding to the received monitoring identifier is saved.
  • Mode 2 (the monitoring identifier is assigned by the monitoring initiator):
  • the monitoring initiator sends a monitoring request message to the monitoring receiver, where the monitoring request message includes the identifier or address of the monitoring initiator, the monitoring identifier, and the monitoring task.
  • the parameters included in the monitoring task are the same as in the above manner, and the monitoring identifier is used. To identify a monitoring task.
  • the monitoring receiver After receiving the monitoring request message, the monitoring receiver sends a response message to the monitoring initiator.
  • the monitoring receiver confirms that the monitoring task can be performed, the monitoring message is successfully received in the response message.
  • the refusal to perform the monitoring task is indicated in the response message.
  • the monitoring initiator is a common service entity (Common Service Entity, CSE for short) in the M2M system, and is used to provide management functions of the service layer, for example, application registration, device management, etc., belonging to the service.
  • CSE Common Service Entity
  • the Service Capability Exposure Function (SCEF) or Interworking Function (IWF) is an interface network element of the bearer network to the external network unit, and is configured to receive the network entity from the bearer network. (eg, SCS) messages, and messages sent to network entities outside the bearer network.
  • SCEF Service Capability Exposure Function
  • IWF Interworking Function
  • the monitoring performer includes an HSS, which is configured to store information of users in the bearer network, and the MME is configured to perform mobility management of users in the bearer network, such as handover, tracking area update, attachment, etc., SGSN.
  • HSS which is configured to store information of users in the bearer network
  • MME is configured to perform mobility management of users in the bearer network, such as handover, tracking area update, attachment, etc., SGSN.
  • the MME and the SGSN are similar entities and are entities of the same function of different bearer networks, which are represented by the MME/SGSN in the following preferred embodiments.
  • the CSE sends a monitoring request message to the SCEF/IWF.
  • the request message includes a monitoring task.
  • the parameter combination included in the monitoring task includes at least one of the following: 1) the identifier of the monitored terminal, the event to be monitored; 2) the monitored The identification of the terminal, the events to be monitored, the number of monitoring reports; 3) the identity of the monitored terminal, the event to be monitored, the duration of the monitoring; 4) the identity of the monitored terminal, the event to be monitored, the monitoring start time, Monitoring end time; 5) The identity of the monitored terminal, the event to be monitored, the monitoring start time, and the duration of the monitoring; 6) The identity of the monitored terminal, the event to be monitored, and the operation to be performed after the event occurs.
  • event parameters to be monitored can be implemented in multiple ways.
  • Event A Monitoring location
  • the event definition list is sent to the SCEF/IWF or the HSS in advance by the interaction between the CSE and the SCEF/IWF or the CSE and the HSS, and the event parameter to be monitored may be an event identifier, for example:
  • the SCEF/IWF can know that the Event-A is based on the list query, for example, whether the monitoring is offline; if the event definition list is sent to the HSS in advance, then the SCEF/ After receiving the monitoring request, the IWF can query the HSS for Event-A during the process of sending it to the monitoring performer, for example, to monitor whether it is offline.
  • the SCEF/IWF After receiving the monitoring request message, the SCEF/IWF sends a response message to the CSE.
  • the monitoring task is assigned a monitoring identifier and is included in the response message.
  • the monitoring identifier is used to identify a monitoring task.
  • the SCEF/IWF sends the monitoring task to the monitoring performer, which includes the monitoring identifier, and the monitoring performer saves the monitoring task.
  • This step can be implemented in the following manner in the bearer network:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, such as the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends monitoring task information to the MME/SGSN, which includes the monitoring identifier, or the monitoring identifier and the identifier of the SCEF/IWF.
  • the monitoring report needs to be sent to the correct SCEF/IWF through the identifier of the SCEF/IWF.
  • the SCEF/IWF sends the monitoring task information to the HSS, which includes the monitoring identifier, or the monitoring identifier and the identifier of the SCEF/IWF;
  • the HSS sends a monitoring task to other bearer network nodes, for example, sends monitoring task information to the MME or SGSN, which includes the monitoring identifier.
  • the monitoring performer After detecting the event to be monitored, the monitoring performer sends a monitoring report to the monitoring receiver, which includes the monitoring identifier.
  • This step can be implemented in the following manner in the bearer network:
  • MME Mobility Management Entity
  • the MME or SGSN sends a monitoring report to the HSS, and the HSS forwards the monitoring report to the SCEF/IWF;
  • the MME or the SGSN After the MME or the SGSN queries the HSS to identify the SCEF/IWF, it sends a monitoring report to the SCEF/IWF.
  • the SCEF/IWF After receiving the monitoring report, the SCEF/IWF sends the monitoring report to the CSE.
  • the CSE If, at a certain moment, the CSE considers that it is no longer necessary to continue monitoring the specified terminal, the CSE sends a monitoring stop request message to the SCEF/IWF, where the request message includes:
  • Monitoring identifier the monitoring identifier of the monitoring task that the CSE needs to stop; or 2) monitoring identifier: monitoring of the monitoring task that the CSE needs to stop, and terminal identification: the identifier of the monitored terminal.
  • the two options here are different information that may be needed to query the HSS for contract data in the next step.
  • the traditional way of querying the subscription data to the HSS requires the identification of the terminal.
  • the preferred embodiment of the solution also considers the special scenario of monitoring, that is, the monitoring information can also be used to query the required information.
  • the SCEF/IWF receives the monitoring stop request message, and after confirming that the request can be executed, sends a monitoring termination message to the monitoring performer, where the monitoring termination message includes the monitoring identifier in the monitoring stop request message sent by the CSE.
  • the SCEF/IWF sends a monitoring termination message to the monitoring performer in the following manner:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, such as the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends a Monitoring Termination message to the MME/SGSN, which contains the monitoring identity.
  • the SCEF/IWF sends a monitoring termination request to the HSS, which contains the monitoring identifier;
  • the HSS sends a monitoring termination request to other bearer network nodes, for example, sending a monitoring termination request to the MME or SGSN.
  • the HSS, or the MME, or the SGSN checks whether the local monitoring information of the monitoring task associated with the received monitoring identifier is saved.
  • the rejection message can indicate that the monitoring task does not exist.
  • the CSE If the CSE needs to change a parameter of the monitoring task, the CSE sends an update monitoring request message to
  • the SCEF/IWF includes the monitoring identifier and the parameters of the monitoring task that need to be updated.
  • the monitoring identifier is used to indicate which monitoring task needs to be updated.
  • the parameters of the monitoring task that needs to be updated may include one or more of the following parameters:
  • Monitoring events (renewing the monitoring events corresponding to the monitoring tasks of the monitoring tasks); 2) monitoring the number of reports (renewing the number of monitoring reports corresponding to the monitoring tasks of the monitoring identifiers); 3) monitoring the duration of the monitoring (upgrading the monitoring indicators corresponding to monitoring)
  • the monitoring of the task is continued; 4) the monitoring start time (update the monitoring start time of the monitoring task corresponding to the monitoring task); 5) the monitoring end time (update the monitoring end corresponding to the monitoring end of the monitoring task); 6) after the event occurs
  • the operation performed (updates the operation of the monitoring identifier corresponding to the event of the monitoring task); 7) the monitored terminal; (same reason that the terminal identifier is required in step 7, for possible SCEF/IWF query to HSS Required for signing data).
  • the SCEF/IWF After receiving the update monitoring request message, the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that needs to be updated to the monitoring performer after confirming that the request can be executed.
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that needs to be updated to the monitoring performer in the following manner:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, for example, the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that need to be updated to the MME/SGSN.
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that need to be updated to the HSS;
  • the HSS sends the monitoring identifier and the parameters of the monitoring task that need to be updated to other bearer network nodes, for example, to the MME or the SGSN.
  • the HSS, the MME, or the SGSN After receiving the monitoring identifier and the parameters of the monitoring task to be updated, the HSS, the MME, or the SGSN checks whether the monitoring task information corresponding to the received monitoring identifier is saved locally.
  • an update monitoring rejection message is sent to the SCEF/IWF, and the rejection message may indicate that the monitoring task does not exist.
  • the CSE sends a monitoring request message to the SCEF/IWF, where the request message includes a monitoring task, and the monitoring task includes at least one of the following combinations of parameters:
  • the monitoring identifier is used to identify a monitoring task.
  • the event parameters to be monitored can be implemented in multiple ways.
  • Event A Monitoring location
  • the event definition list is sent to the SCEF/IWF or the HSS in advance by the interaction between the CSE and the SCEF/IWF or the CSE and the HSS, and the event parameter to be monitored may be an event identifier, for example:
  • the SCEF/IWF can know that the Event-A is based on the list query, for example, whether the monitoring is offline; if the event definition list is sent to the HSS in advance, then the SCEF/ After receiving the monitoring request, the IWF can query the HSS for Event-A during the process of sending it to the monitoring performer, for example, to monitor whether it is offline.
  • the SCEF/IWF After receiving the monitoring request message, the SCEF/IWF sends a response message to the CSE.
  • the response message indicates that the monitoring task is successfully accepted.
  • the SCEF/IWF sends the monitoring task to the monitoring performer, which includes the monitoring identifier, and the monitoring performer saves the monitoring task.
  • This step can be implemented in the following manner in the bearer network:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, such as the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends monitoring task information to the MME/SGSN, which includes the monitoring identifier, or the monitoring identifier and the identifier of the SCEF/IWF.
  • the monitoring report needs to be sent to the correct SCEF/IWF through the identifier of the SCEF/IWF.
  • the SCEF/IWF sends the monitoring task information to the HSS, which includes the monitoring identifier, or the monitoring identifier and the identifier of the SCEF/IWF;
  • the HSS sends a monitoring task to other bearer network nodes, for example, sends monitoring task information to the MME or SGSN, which includes the monitoring identifier.
  • the monitoring performer After detecting the event to be monitored, the monitoring performer sends a monitoring report to the monitoring receiver, which includes the monitoring identifier.
  • This step can be implemented in the following manner in the bearer network:
  • MME Mobility Management Entity
  • the MME or SGSN sends a monitoring report to the HSS, and the HSS forwards the monitoring report to the SCEF/IWF;
  • the MME or the SGSN After the MME or the SGSN queries the HSS to identify the SCEF/IWF, it sends a monitoring report to the SCEF/IWF.
  • the SCEF/IWF After receiving the monitoring report, the SCEF/IWF sends the monitoring report to the CSE.
  • the CSE If, at a certain moment, the CSE considers that it is no longer necessary to continue monitoring the specified terminal, the CSE sends a monitoring stop request message to the SCEF/IWF, where the request message includes:
  • Monitoring identifier the monitoring identifier of the monitoring task that the CSE needs to stop; or 2) monitoring identifier: monitoring of the monitoring task that the CSE needs to stop, and terminal identification: the identifier of the monitored terminal.
  • the two options here are different information that may be needed to query the HSS for contract data in the next step.
  • the traditional way to query the HSS for the subscription data must be the identifier of the terminal, but the preferred embodiment of the solution also considers the monitoring
  • the special scenario is that you can also use the monitoring ID to find the information you need.
  • the SCEF/IWF receives the monitoring stop request message, and after confirming that the request can be executed, sends a monitoring termination message to the monitoring performer, where the monitoring termination message includes the monitoring identifier in the monitoring stop request message sent by the CSE.
  • the SCEF/IWF sends a monitoring termination message to the monitoring performer in the following manner:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, such as the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends a Monitoring Termination message to the MME/SGSN, which contains the monitoring identity.
  • the SCEF/IWF sends a monitoring termination request to the HSS, which contains the monitoring identifier;
  • the HSS sends a monitoring termination request to other bearer network nodes, for example, sending a monitoring termination request to the MME or SGSN.
  • the HSS, or the MME, or the SGSN checks whether the local monitoring information of the monitoring task associated with the received monitoring identifier is saved.
  • the rejection message can indicate that the monitoring task does not exist.
  • the CSE If the CSE needs to change a certain parameter of the monitoring task, the CSE sends an update monitoring request message to the SCEF/IWF, where the request message includes the monitoring identifier and the parameter of the monitoring task that needs to be updated, and the monitoring identifier is set to indicate which monitoring task needs to be updated.
  • the parameters of the monitoring task that need to be updated may contain one or more of the following parameters:
  • Monitoring events (renewing the monitoring events corresponding to the monitoring tasks of the monitoring tasks); 2) monitoring the number of reports (renewing the number of monitoring reports corresponding to the monitoring tasks of the monitoring identifiers); 3) monitoring the duration of the monitoring (upgrading the monitoring indicators corresponding to monitoring)
  • the monitoring of the task is continued; 4) the monitoring start time (update the monitoring start time of the monitoring task corresponding to the monitoring task); 5) the monitoring end time (update the monitoring end corresponding to the monitoring end of the monitoring task); 6) after the event occurs
  • the operation performed (updates the operation of the monitoring identifier corresponding to the event of the monitoring task); 7) the monitored terminal; (same reason that the terminal identifier is required in step 7, for possible SCEF/IWF query to HSS Required for signing data).
  • the SCEF/IWF After receiving the update monitoring request message, the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that needs to be updated to the monitoring performer after confirming that the request can be executed.
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that needs to be updated to the monitoring performer in the following manner:
  • the SCEF/IWF sends a subscription data request message to the HSS, where the request message includes a terminal identifier, or/and a monitoring identifier;
  • the HSS sends a subscription data response message to the SCEF/IWF, where the identifier or address of the network element performing the monitoring, for example, the identifier or address of the MME, or the identifier or address of the SGSN, is included;
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that need to be updated to the MME/SGSN.
  • the SCEF/IWF sends the monitoring identifier and the parameters of the monitoring task that need to be updated to the HSS;
  • the HSS sends the monitoring identifier and the parameters of the monitoring task that need to be updated to other bearer network nodes, for example, to the MME or the SGSN.
  • the HSS, the MME, or the SGSN After receiving the monitoring identifier and the parameters of the monitoring task to be updated, the HSS, the MME, or the SGSN checks whether the monitoring task information corresponding to the received monitoring identifier is saved locally.
  • an update monitoring rejection message is sent to the SCEF/IWF, and the rejection message may indicate that the monitoring task does not exist.
  • modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the monitoring scheme in the related art is solved by the foregoing embodiments and the preferred embodiments, which not only makes the operation of the service platform and the corresponding application complicated, but also has low monitoring efficiency of the monitoring task, thereby achieving the monitoring according to the monitoring.
  • the monitoring identifier corresponding to the task performs interactive monitoring and processing, which not only effectively reduces the complexity of monitoring, but also monitors the cost, and improves the monitoring efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种监控处理方法及装置，其中，该方法包括：监控接收者接收监控发起者发送的监控请求消息，其中，监控请求消息中包含有监控任务；监控接收者依据监控任务对应的监控标识与监控发起者和/或监控执行者进行交互执行监控处理，通过本发明，解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题，进而达到了依据监控任务对应的监控标识进行交互执行监控处理，不仅有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。

Description

监控处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种监控处理方法及装置。
背景技术
在机器对机器(Machine to Machine，简称为M2M)网络中，包含有众多的M2M终端，M2M终端上运行有M2M应用，通过底层承载网络，例如，全球移动通信系统(Global System for Mobile communications，简称为GSM)，宽带码分多址接入(Wideband Code Division Multiple Access，简称为WCDMA)，Wifi等，连接到网络侧业务平台。由此，一个M2M应用的管理者可以通过访问网络侧的业务平台执行对M2M终端运行状态的监控。
例如，智能交通监控系统的管理者，可以通过访问internet连接到网络业务平台，像业务平台下发监控某一个或者某几个道路上的监控摄像头的连接状态，并在检测到监控摄像头断线后能接收到来自于业务平台的警报信息。
类似于上述场景的监控任务是通过比较传统的方式来完成的，例如，要想知道某一个或某几个M2M终端是否在线，需要应用或业务平台向M2M终端发送轮询指令，如果能正常接收到M2M终端的反馈，则说明M2M终端仍然在线，如果在一个指定时间内没有能接收到M2M终端的反馈，则说明该M2M终端已断线。
然而通过上述传统的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下。
发明内容
本发明实施例提供了一种监控处理方法及装置，以至少解决相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题。
根据本发明实施例的一个方面，提供了一种监控处理方法，包括：监控接收者接收监控发起者发送的监控请求消息，其中，所述监控请求消息中包含有监控任务；所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或监控执行者进行交互执行监控处理。
优选地，所述监控标识由所述监控发起者分配，并携带在所述监控请求消息中； 或者，所述监控标识由所述监控接收者在接收到所述监控发起者发送的监控请求消息后，由所述监控接收者为所述监控请求消息中的所述监控任务分配。
优选地，所述监控接收者依据所述监控任务对应的监控标识与所述监控执行者进行交互执行监控处理包括：所述监控接收者向所述监控执行者发送监控执行请求消息，其中，所述监控执行请求消息中包含有所述监控标识，以及所述监控任务。
优选地，在所述监控接收者向所述监控执行者发送所述监控执行请求消息之前，还包括：向归属用户服务器HSS发送签约数据请求消息，其中，所述签约数据请求消息中携带有用于标识所述监控任务对应的终端的终端标识，和/或所述监控标识；依据从所述HSS接收到的签约数据响应消息中确定用于执行所述监控任务的所述监控执行者。
优选地，所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或所述监控执行者进行交互执行监控处理包括：所述监控接收者接收所述监控发起者发送的用于请求终止所述监控任务的监控终止请求消息，其中，所述监控终止请求消息中包含有指示终止的所述监控任务的所述监控标识；所述监控接收者依据所述监控终止请求消息，向所述监控执行者发送停止监控请求消息用于所述监控执行者依据所述监控标识终止所述监控任务，其中，所述停止监控请求消息中包含所述指示终止的所述监控任务的监控标识。
优选地，所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或所述监控执行者进行交互执行监控处理包括：所述监控接收者接收所述监控发起者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述更新监控请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；所述监控接收者依据所述更新监控请求消息，将监控任务更新请求消息发送给所述监控执行者用于所述监控执行者依据所述监控标识，以及更新的所述监控参数更新所述监控任务，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数。
优选地，所述监控任务包括的监控参数包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
根据本发明实施例的另一方面，提供了一种监控处理方法，包括：监控执行者接收监控接收者发送的监控执行请求消息，其中，所述监控执行请求消息中包含有用于标识所述监控任务的监控标识和所述监控任务；所述监控执行者对所述监控标识对应的所述监控任务执行监控处理。
优选地，在所述监控执行者接收所述监控接收者发送的所述监控执行请求消息之后，还包括：所述监控执行者接收所述监控接收者发送的用于请求终止所述监控任务的停止监控请求消息，其中，所述停止监控请求消息中包含有指示终止的所述监控任务的所述监控标识；所述监控执行者对所述监控标识对应的所述监控任务执行监控处理包括：所述监控执行者依据所述监控标识删除所述监控任务。
优选地，在所述监控执行者接收所述监控接收者发送的所述监控执行请求消息之后，还包括：所述监控执行者接收所述监控接收者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；所述监控执行者对所述监控标识对应的所述监控任务执行监控处理包括：所述监控执行者依据所述监控任务更新请求消息中的所述监控标识，以及所述监控任务更新的监控参数，将所述监控任务的监控参数更新为接收到的监控任务的监控参数。
优选地，所述监控任务包括的监控参数包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
根据本发明实施例的一方面，提供了一种监控处理装置，应用于监控接收者，包括：第一接收模块，设置为接收监控发起者发送的监控请求消息，其中，所述监控请求消息中包含有监控任务；第一处理模块，设置为依据所述监控任务对应的监控标识与所述监控发起者和/或监控执行者进行交互执行监控处理。
优选地，所述监控标识由所述监控发起者分配，并携带在所述监控请求消息中；或者，所述监控标识由所述监控接收者在接收到所述监控发起者发送的监控请求消息后，由所述监控接收者为所述监控请求消息中的所述监控任务分配。
优选地，所述第一处理模块包括：第一发送单元，设置为向所述监控执行者发送监控执行请求消息，其中，所述监控执行请求消息中包含有所述监控标识，以及所述监控任务。
优选地，所述第一处理模块还包括：第二发送单元，设置为向归属用户服务器HSS发送签约数据请求消息，其中，所述签约数据请求消息中携带有用于标识所述监控任务对应的终端的终端标识，和/或所述监控标识；第一确定单元，设置为依据从所述HSS接收到的签约数据响应消息中确定用于执行所述监控任务的所述监控执行者。
优选地，所述第一处理模块包括：第一接收单元，设置为接收所述监控发起者发送的用于请求终止所述监控任务的监控终止请求消息，其中，所述监控终止请求消息中包含有指示终止的所述监控任务的所述监控标识；第三发送单元，设置为依据所述 监控终止请求消息，向所述监控执行者发送停止监控请求消息用于所述监控执行者依据所述监控标识终止所述监控任务，其中，所述停止监控请求消息中包含所述指示终止的所述监控任务的监控标识。
优选地，所述第一处理模块包括：第二接收单元，设置为接收所述监控发起者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述更新监控请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；第四发送单元，设置为依据所述更新监控请求消息，将监控任务更新请求消息发送给所述监控执行者用于所述监控执行者依据所述监控标识，以及更新的所述监控参数更新所述监控任务，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数。
优选地，所述监控任务包括的监控参数包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
根据本发明实施例的另一方面，提供了一种接口网元，位于承载网中，包括上述任一项所述的装置。
优选地，所述接口网元包括以下至少之一：服务能力展开功能实体SCEF、因特网工作功能实体IWF。
根据本发明实施例的一方面，提供了一种监控处理装置，应用于监控执行者，包括：第二接收模块，设置为接收监控接收者发送的监控执行请求消息，其中，所述监控执行请求消息中包含有用于标识所述监控任务的监控标识和所述监控任务；第二处理模块，设置为依据所述监控标识对所述监控任务执行监控处理。
优选地，该装置还包括：第三接收模块，设置为接收所述监控接收者发送的用于请求终止所述监控任务的停止监控请求消息，其中，所述停止监控请求消息中包含有指示终止的所述监控任务的所述监控标识；所述第二处理模块，还设置为依据所述监控标识删除所述监控任务。
优选地，该装置还包括：第四接收模块，设置为接收所述监控接收者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；所述第二处理模块，还设置为依据所述监控任务更新请求消息中的所述监控标识，以及所述监控任务更新的监控参数，将所述监控任务的监控参数更新为接收到的监控任务的监控参数。
优选地，所述监控任务包括的监控参数包括以下至少之一：被监控的终端、监控 的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
根据本发明实施例的另一方面，提供了一种监控设备，位于承载网中，包括上述任一项所述的装置。
优选地，所述监控设备包括以下至少之一：归属用户服务器HSS、移动管理实体MME、服务通用分组无线业务GPRS支持节点SGSN。
通过本发明实施例，采用监控接收者接收监控发起者发送的监控请求消息，其中，所述监控请求消息中包含有监控任务；所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或监控执行者进行交互执行监控处理，解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题，进而达到了依据监控任务对应的监控标识进行交互执行监控处理，不仅有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的监控处理方法一的流程图；
图2是根据本发明实施例的监控处理方法二的流程图；
图3是根据本发明实施例的监控处理装置一的结构框图；
图4是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图一；
图5是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图二；
图6是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图三；
图7是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图四；
图8是根据本发明实施例的接口网元的结构框图；
图9是根据本发明实施例的监控处理装置二的结构框图；
图10是根据本发明实施例的监控处理装置二的优选结构框图一；
图11是根据本发明实施例的监控处理装置二的优选结构框图二；
图12是根据本发明实施例的监控设备的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种监控处理方法，图1是根据本发明实施例的监控处理方法一的流程图，如图1所示，该流程包括如下步骤：
步骤S102，监控接收者接收监控发起者发送的监控请求消息，其中，该监控请求消息中包含有监控任务；
步骤S104，监控接收者依据监控任务对应的监控标识与监控发起者和/或监控执行者进行交互执行监控处理。
通过上述步骤，依据监控任务对应的监控标识进行交互执行监控处理，不仅解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题，进而达到了有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。
需要说明的是，上述监控标识的来源可以多种，例如，上述监控标识可以由监控发起者分配，并携带在监控请求消息中；该监控标识也可以由监控接收者在接收到监控发起者发送的监控请求消息后，由监控接收者为监控请求消息中的监控任务分配。
需要指出的是，此处的“监控处理”是指监控接收者所执行的一系列与监控有关的操作，例如，可以包括向监控执行者发送监控任务指示监控执行者对监控任务执行监控的相关操作；也可以包括向监控执行者发送停止监控请求消息用于监控执行者依据监控标识终止监控任务的相关操作；还可以是向监控执行者发送监控任务更新请求消息用于监控执行者依据监控标识，以及更新的监控参数更新监控任务的相关操作，下面分别说明。
举例说明，监控接收者依据监控任务对应的监控标识与监控执行者进行交互执行监控处理可以包括：监控接收者向监控执行者发送监控执行请求消息，其中，监控执行请求消息中包含有监控标识，以及监控任务。依据依据监控标识，对监控标识对应 的监控任务进行监控处理。
其中，在监控接收者向监控执行者发送监控执行请求消息之前，需要确定监控任务所对应的监控执行者，确定监控任务执行者的方式可以多种，例如，可以采用以下优选方式：向归属用户服务器(Home Subscriber Server，简称为HSS)发送签约数据请求消息，其中，该签约数据请求消息中携带有用于标识监控任务对应的终端的终端标识，和/或监控标识；依据从该HSS接收到的签约数据响应消息中确定用于执行监控任务的监控执行者。
再举例说明，监控接收者依据监控任务对应的监控标识与监控发起者和/或监控执行者进行交互执行监控处理也可以包括：监控接收者接收监控发起者发送的用于请求终止监控任务的监控终止请求消息，其中，监控终止请求消息中包含有指示终止的监控任务的监控标识；监控接收者依据监控终止请求消息，向监控执行者发送停止监控请求消息用于监控执行者依据监控标识终止监控任务，其中，停止监控请求消息中包含指示终止的监控任务的监控标识。即依据监控标识，对该监控标识对应的监控任务执行删除操作。
还举例说明，监控接收者依据监控任务对应的监控标识与监控发起者和/或监控执行者进行交互执行监控处理还可以包括：监控接收者接收监控发起者发送的用于请求对监控任务进行更新的更新监控请求消息，其中，更新监控请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数；监控接收者依据更新监控请求消息，将监控任务更新请求消息发送给监控执行者用于监控执行者依据监控标识，以及更新的监控参数更新监控任务，其中，监控任务更新请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数。即依据监控标识，对该监控标识对应的监控任务进行更新操作。
需要说明的是，上述监控任务包括的监控参数可以多种，例如，可以包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
图2是根据本发明实施例的监控处理方法二的流程图，如图2所示，该流程包括如下步骤：
步骤S202，监控执行者接收监控接收者发送的监控执行请求消息，其中，监控执行请求消息中包含有用于标识监控任务的监控标识和监控任务；
步骤S204，监控执行者对监控标识对应的监控任务执行监控处理。
通过上述步骤，依据监控任务对应的监控标识进行交互执行监控处理，不仅解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监 控任务的监控效率低下的问题，进而达到了有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。
对应地，此处的“监控处理”是指监控执行者所执行的一系列与监控有关的操作，例如，可以包括对监控任务的监控操作，也可以包括对监控任务的更新，以及删除操作处理，下面分别说明。
例如，监控执行者对监控标识对应的监控任务执行监控处理可以包括：监控执行者依据接收到的该监控接收者发送的监控任务执行监控操作。
又例如，在监控执行者接收监控接收者发送的监控执行请求消息之后，监控执行者还可以接收监控接收者发送的用于请求终止监控任务的停止监控请求消息，其中，停止监控请求消息中包含有指示终止的监控任务的监控标识；之后，该监控执行者对监控标识对应的监控任务执行监控处理包括：监控执行者依据监控标识删除监控任务。
还例如，在监控执行者接收监控接收者发送的监控执行请求消息之后，监控执行者还可以接收监控接收者发送的用于请求对监控任务进行更新的更新监控请求消息，其中，监控任务更新请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数；之后，该监控执行者对监控标识对应的监控任务执行监控处理包括：监控执行者依据监控任务更新请求消息中的监控标识，以及监控任务更新的监控参数，将监控任务的监控参数更新为接收到的监控任务的监控参数。
对应地，该监控任务包括的监控参数也可以包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
在本实施例中还提供了一种监控处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的监控处理装置一的结构框图，如图3所示，该装置应用于监控接收者，包括第一接收模块32和第一处理模块34，下面对该装置进行说明。
第一接收模块32，设置为接收监控发起者发送的监控请求消息，其中，监控请求消息中包含有监控任务；第一处理模块34，连接至上述第一接收模块32，设置为依据监控任务对应的监控标识与监控发起者和/或监控执行者进行交互执行监控处理。
优选地，监控标识可以由监控发起者分配，并携带在监控请求消息中；或者，监控标识也可以由监控接收者在接收到监控发起者发送的监控请求消息后，由监控接收 者为监控请求消息中的监控任务分配。
图4是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图一，如图4所示，该第一处理模块34包括：第一发送单元42，下面对该第一发送单元42进行说明。
第一发送单元42，设置为向监控执行者发送监控执行请求消息，其中，监控执行请求消息中包含有监控标识，以及监控任务。
图5是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图二，如图5所示，该第一处理模块34除包括图4所示的结构外，还包括：第二发送单元52和第一确定单元54，下面对该第一处理模块34进行说明。
第二发送单元52，设置为向归属用户服务器HSS发送签约数据请求消息，其中，签约数据请求消息中携带有用于标识监控任务对应的终端的终端标识，和/或监控标识；第一确定单元54，连接至上述第二发送单元52和上述第一发送单元42，设置为依据从HSS接收到的签约数据响应消息中确定用于执行监控任务的监控执行者。
图6是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图三，如图6所示，该第一处理模块34包括：第一接收单元62、第三发送单元64，下面对该第一处理模块34进行说明。
第一接收单元62，设置为接收监控发起者发送的用于请求终止监控任务的监控终止请求消息，其中，监控终止请求消息中包含有指示终止的监控任务的监控标识；第三发送单元64，连接至上述第一接收单元62，设置为依据监控终止请求消息，向监控执行者发送停止监控请求消息用于监控执行者依据监控标识终止监控任务，其中，停止监控请求消息中包含指示终止的监控任务的监控标识。
图7是根据本发明实施例的监控处理装置一中第一处理模块34的优选结构框图四，如图7所示，该第一处理模块34包括：第二接收单元72和第四发送单元74，下面对该第一处理模块34进行说明。
第二接收单元72，设置为接收监控发起者发送的用于请求对监控任务进行更新的更新监控请求消息，其中，更新监控请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数；第四发送单元74，连接至上述第二接收单元72，设置为依据更新监控请求消息，将监控任务更新请求消息发送给监控执行者用于监控执行者依据监控标识，以及更新的监控参数更新监控任务，其中，监控任务更新请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数。
需要说明的是，上述监控任务包括的监控参数包括以下至少之一：被监控的终端、 监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
图8是根据本发明实施例的接口网元的结构框图，如图8所示，该接口网元80，位于承载网中，包括上述任一项的监控处理装置一82。
优选地，上述接口网元可以包括以下至少之一：服务能力展开功能实体(Service Capability Server，简称为SCEF)、因特网工作功能实体(Interworking Function，简称为IWF)。
图9是根据本发明实施例的监控处理装置二的结构框图，如图9所示，该装置应用于监控执行者，包括：第二接收模块92和第二处理模块94，下面对该装置进行说明。
第二接收模块92，设置为接收监控接收者发送的监控执行请求消息，其中，监控执行请求消息中包含有用于标识监控任务的监控标识和监控任务；第二处理模块94，连接至上述第二接收模块92，设置为依据监控标识对监控任务执行监控处理。
图10是根据本发明实施例的监控处理装置二的优选结构框图一，如图9所示，该装置除包括图9所示的所有结构外，还包括第三接收模块1002，下面对该优选结构进行说明。
第三接收模块1002，连接至上述第二接收模块92，设置为接收监控接收者发送的用于请求终止监控任务的停止监控请求消息，其中，停止监控请求消息中包含有指示终止的监控任务的监控标识；第二处理模块94，连接至上述第三接收模块1002，还设置为依据监控标识删除监控任务。
图11是根据本发明实施例的监控处理装置二的优选结构框图二，如图11所示，该装置除包括图9所示的所有结构外，还包括第四接收模块1102，下面对该优选结构进行说明。
第四接收模块1102，连接至上述第二接收模块92，设置为接收监控接收者发送的用于请求对监控任务进行更新的更新监控请求消息，其中，监控任务更新请求消息中包含指示更新的监控任务的监控标识，以及监控任务更新的监控参数；第二处理模块94，连接至上述第四接收模块1102，还设置为依据监控任务更新请求消息中的监控标识，以及监控任务更新的监控参数，将监控任务的监控参数更新为接收到的监控任务的监控参数。
需要说明的是，上述监控任务包括的监控参数可以包括以下至少之一：被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、 监控的事件发生后执行的操作。
图12是根据本发明实施例的监控设备的结构框图，如图12所示，该监控设备1200位于承载网中，包括上述任一项的监控处理装置二1202。
优选地，该监控设备可以包括以下至少之一：归属用户服务器HSS、移动管理实体(Mobility Management Entity，简称为MME)、服务通用分组无线业务(General Packet Radio Service，简称为GPRS)支持节点(Serving GPRS Supporting Node，简称为SGSN)。
通过上述实施例及优选实施方式，有效解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题，进而达到了有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。
相对于传统的对监控任务的监控处理，完全基于业务层或应用层的操作来实现的，在本实施例中，通过底层承载网来执行和管理监控任务的方式来实现。因为任何一个M2M终端首先必须连接到底层承载网络，底层承载网对连接到其网络的终端能更直接更快的感知其是否在线，以及其是否恢复连接，而且能提供更多的监控服务，比如M2M终端是否移动出已知的范围，M2M终端的设备号和入网卡是否不匹配等等。而且还能根据应用或业务平台预先配置的指示，在事件检测后立即做出响应的操作，例如，拒绝该M2M终端的接入，减少对该M2M终端的调度时隙等等。
并且，在由底层承载网络执行监控任务后，能大大的减少业务平台和应用的操作和复杂度，使得应用的设计周期更短，从而能大大减少开发周期和维护成本。
其中，本实施例中提供的由底层承载网来执行和管理监控任务的方法主要包括以下内容：
首先，将M2M的应用或业务平台称为监控发起者；
底层承载网通常有一个用于接收来自于业务平台或应用的网元，该网元与业务平台或应用之间通过不同于承载网内部的接口协议进行交互，该网元对接收到的信息进行协议转换，以及对需要承载网执行的业务进行管理，在本实施例中将这个从业务平台或应用接收监控指令的网元称为监控接收者；
底层承载网络有专门的网元来对需要监控的事件进行检测，例如，MME，SGSN，HSS等，在本实施例中称为监控执行者，考虑到在承载网对监控的执行可能需要多个网元协调操作，监控执行者可能包含一个或多个承载网网元，例如，监控执行者可以是MME，或SGSN，或HSS，或MME和HSS，或SGSN和HSS等。
因此，结合由底层承载网以及依据监控标识来执行和管理监控任务，依据监控标识的来源不同，即执行监控标识分配的主体不同(例如，可以由监控接收者来分配监 控标识，也可以由监控发起者来分配监控标识)，本实施例依据监控标识来执行监控任务大致可以采用以下两种方式：
方式一(由监控接收者分配监控标识)：
1、监控发起者发送监控请求消息给监控接收者，请求消息中包含监控任务，监控任务中包含有参数，监控参数的不同组合构成对应的监控任务，例如，可以包括以下几种组合，但不限于此：
1)被监控的终端，需监控的事件；2)被监控的终端，需监控的事件，监控报告的次数；3)被监控的终端，需监控的事件，监控持续时长；4)被监控的终端，需监控的事件，监控开始时间，监控结束时间；5)被监控的终端，需监控的事件，监控开始时间，监控持续时长；6)被监控的终端，需监控的事件，事件发生后需执行的操作。
2、监控接收者接收到监控请求消息后，发送响应消息给监控发起者。
2.1、如果监控接收者确认可以执行该监控任务，则为该监控任务分配监控标识，并包含在响应消息中。其中，监控标识用于标识一个监控任务。
2.2、如果监控接收者确认不能执行该监控任务，则在响应消息中指示拒绝执行监控任务。
3、监控接收者将监控任务发送给监控执行者，其中包含监控标识。
4、监控执行者保存监控任务。
5、在检测到需监控的事件后，监控执行者发送监控报告给监控接收者，其中包含监控标识。
6、监控接收者在接收到监控报告后，将监控报告发送给监控发起者。
7、监控发起者还可以发送监控停止请求消息给监控接收者，请求消息中包含监控标识；
8、监控接收者接收到监控停止请求消息后，发送监控终止消息给监控执行者，其中包含监控标识。
9、监控执行者接收到监控终止指令后，检查本地是否保存有跟所收到的监控标识相关联的监控任务，
9.1、如果有，则删除跟监控标识相关的监控任务。
9.2、如果没有，则发送监控终止拒绝消息给监控接收者。
10、监控发起者还可以发送更新监控请求消息给监控接收者，请求消息中包含监控标识和需要更新的监控任务的参数，监控标识用于指示需要更新哪一个监控任务的参数，需要更新的监控任务的参数可以包含如下一个或多个：
1)监控事件(更新该监控标识对应监控任务的监控事件)；2)监控报告的次数(更新该监控标识对应监控任务的监控报告的次数)；3)监控持续时长(更新该监控标识对应监控任务的监控持续)；4)监控开始时间(更新该监控标识对应监控任务的监控开始时间)；5)监控结束时间(更新该监控标识对应监控任务的监控结束时间)；6)事件发生后需执行的操作(更新该监控标识对应监控任务的事件发生后需执行的操作)；7)被监控的终端。
11、监控接收者接收到更新监控请求消息后，将监控标识和需要更新的监控任务的参数发送给监控执行者。
12、监控执行者接收到更新监控请求消息后，检查本地是否保存有跟接收到的监控标识对应的监控任务，
12.1、如果有，则根据需要更新的监控任务的参数更新本地保存的监控任务的参数；
12.2、如果没有，则发送更新监控拒绝消息给监控接收者。
方式二(由监控发起者分配监控标识)：
1、监控发起者发送监控请求消息给监控接收者，该监控请求消息中包含监控发起者的标识或地址，监控标识，和监控任务，监控任务包含的参数跟上述方式一中相同，监控标识用于标识一个监控任务。
2、监控接收者接收到监控请求消息后，发送响应消息给监控发起者。
2.1、如果监控接收者确认可以执行该监控任务，则在响应消息中指示成功接收监控任务。
2.2、如果监控接收者确认不能执行该监控任务，则在响应消息中指示拒绝执行监控任务。
后续步骤同上述方式一。
下面结合本发明优选实施例进行说明。
在下列优选实施例中，监控发起者是一个M2M系统中的公共业务实体(Common Service Entity，简称为CSE)，用于提供业务层的管理功能，例如，应用的注册，设备管理等，属于业务能力服务器SCS(Service Capability Server，简称为SCS)范畴的一个逻辑实体。
监控接收者是(Service Capability Exposure Function，简称为SCEF)或(Interworking Function，简称为IWF)，SCEF/IWF是承载网对外部网络单元的接口网元，设置为接收来自于承载网之外网络实体(例如，SCS)的消息，和发送到承载网之外网络实体的消息。
监控执行者包含HSS，设置为存储承载网中用户的信息，MME，设置为执行承载网中用户的移动性管理，例如切换，跟踪区更新，附着等，SGSN。MME和SGSN是相似的实体，是不同承载网的相同功能的实体，在下列优选实施例中用MME/SGSN表示。
下面举例说明。
优选实施例一：
1、CSE发送监控请求消息给SCEF/IWF，请求消息中包含监控任务，监控任务包含的参数组合包括以下至少之一：1)被监控的终端的标识，需监控的事件；2)被监控的终端的标识，需监控的事件，监控报告的次数；3)被监控的终端的标识，需监控的事件，监控持续时长；4)被监控的终端的标识，需监控的事件，监控开始时间，监控结束时间；5)被监控的终端的标识，需监控的事件，监控开始时间，监控持续时长；6)被监控的终端的标识，需监控的事件，事件发生后需执行的操作。
需要说明的是，这里，需监控的事件参数可以有多种实现方式。
第一：直接给出事件的定义，包含事件的名称，以及相关的参数：
事件A：监控位置
{
合法位置坐标；
}
第二：预先由CSE和SCEF/IWF或CSE和HSS之间通过交互，将事件定义列表事先发送到SCEF/IWF，或HSS，由此需监控的事件参数可以是事件标识，例如：
Event-A；
如果事件定义列表事先发送到SCEF/IWF，那么SCEF/IWF在接收到监控请求后，根据列表查询可以知道Event-A是，例如，监控是否离线；如果事件定义列表事先发送到HSS，那么SCEF/IWF在接收到监控请求后，在发送到监控执行者的过程中可以通过向HSS查询Event-A是，例如，监控是否离线。
2、SCEF/IWF接收到监控请求消息后，发送响应消息给CSE。
2.1、如果SCEF/IWF确认可以执行该监控任务，则为该监控任务分配监控标识，并包含在响应消息中。其中，该监控标识用于标识一个监控任务。
2.2、如果SCEF确认不能执行该监控任务，则在响应消息中指示拒绝执行监控任务。
3、SCEF/IWF将监控任务发送给监控执行者，其中包含监控标识，监控执行者保存监控任务。
该步骤在承载网内部可以采用如下执行方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF发送监控任务信息到MME/SGSN，其中包含监控标识，或监控标识和SCEF/IWF的标识。
当承载网部署不只一个SCEF/IWF时，需要通过SCEF/IWF的标识发送监控报告到正确的SCEF/IWF。
2)SCEF/IWF发送监控任务信息到HSS，其中包含监控标识，或监控标识和SCEF/IWF的标识；
如果监控还需要其他的承载网节点执行，HSS发送监控任务到其他承载网节点，例如发送监控任务信息到MME或SGSN，其中包含监控标识。
5、在检测到需监控的事件后，监控执行者发送监控报告给监控接收者，其中包含监控标识。
该步骤在承载网内部可以采用如下执行方式：
1)MME，或SGSN，或HSS直接发送监控报告给SCEF/IWF；
2)MME或SGSN发送监控报告给HSS，HSS转发监控报告给SCEF/IWF；
3)MME或SGSN向HSS查询到SCEF/IWF的标识后，发送监控报告给SCEF/IWF。
6、SCEF/IWF在接收到监控报告后，将监控报告发送给CSE。
7、如果在某个时刻，CSE认为不再需要继续监控指定的终端，CSE发送监控停止请求消息给SCEF/IWF，请求消息中包含：
1)监控标识：CSE需要停止的监控任务的监控标识；或，2)监控标识：CSE需要停止的监控任务的监控，和终端标识：被监控的终端的标识。
注：这里的两种选项是为下一步向HSS查询签约数据时可能需要的不同信息。传统的向HSS查询签约数据必须要终端的标识，但是本优选实施例方案也考虑监控的特殊场景，那就是使用监控标识也可以查询到所需要的信息。
8、SCEF/IWF接收到监控停止请求消息，在确认可以执行该请求后，发送监控终止消息给监控执行者，监控终止消息中包含CSE发送的监控停止请求消息中的监控标识。
SCEF/IWF发送监控终止消息给监控执行者可以采用以下方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF发送监控终止消息到MME/SGSN，其中包含监控标识。
2)SCEF/IWF发送监控终止请求到HSS，其中包含监控标识；
如果监控还需要其他的承载网节点执行，HSS发送监控终止请求到其他承载网节点，例如，发送监控终止请求到MME或SGSN。
9、HSS，或MME，或SGSN接收到监控终止指令后，检查本地是否保存有跟所收到的监控标识相关联的监控任务的信息。
9.1、如果有，则删除跟监控标识相关的监控任务信息。
9.2、如果没有，则发送监控终止拒绝消息给SCEF/IWF。拒绝消息中可以指示监控任务不存在。
10、如果CSE需要更改监控任务的某个参数，CSE发送更新监控请求消息给 SCEF/IWF，请求消息中包含监控标识和需要更新的监控任务的参数，监控标识用于指示需要更新哪一个监控任务的参数，需要更新的监控任务的参数可以包含一个或多个以下参数：
1)监控事件(更新该监控标识对应监控任务的监控事件)；2)监控报告的次数(更新该监控标识对应监控任务的监控报告的次数)；3)监控持续时长(更新该监控标识对应监控任务的监控持续)；4)监控开始时间(更新该监控标识对应监控任务的监控开始时间)；5)监控结束时间(更新该监控标识对应监控任务的监控结束时间)；6)事件发生后需执行的操作(更新该监控标识对应监控任务的事件发生后需执行的操作)；7)被监控的终端；(同步骤7中的需要终端标识的理由相同，用于可能SCEF/IWF向HSS查询签约数据所需)。
11、SCEF/IWF接收到更新监控请求消息后，在确认可以执行该请求后，将监控标识和需要更新的监控任务的参数发送给监控执行者，
SCEF/IWF将监控标识和需要更新的监控任务的参数发送给监控执行者可以采用以下方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如，MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF将监控标识和需要更新的监控任务的参数发送给MME/SGSN。
2)SCEF/IWF将监控标识和需要更新的监控任务的参数发送给HSS；
如果监控还需要其他的承载网节点执行，HSS将监控标识和需要更新的监控任务的参数发送给其他承载网节点，例如，发送到MME或SGSN。
12、HSS，MME或SGSN接收到监控标识和需要更新的监控任务的参数后，检查本地是否保存有跟接收到的监控标识对应的监控任务信息。
12.1、如果有，则根据需要更新的监控任务的参数更新本地保存的监控任务的参数；
12.2、如果没有，则发送更新监控拒绝消息给SCEF/IWF，拒绝消息中可以指示监控任务不存在。
优选实施例二：
1、CSE发送监控请求消息给SCEF/IWF，请求消息中包含监控任务，监控任务包含参数组合的以下至少之一：
1)监控标识，被监控的终端的标识，需监控的事件；2)监控标识，被监控的终端的标识，需监控的事件，监控报告的次数；3)监控标识，被监控的终端的标识，需监控的事件，监控持续时长；4)监控标识，被监控的终端的标识，需监控的事件，监控开始时间，监控结束时间；5)监控标识，被监控的终端的标识，需监控的事件，监控开始时间，监控持续时长；6)监控标识，被监控的终端的标识，需监控的事件，事件发生后需执行的操作。
这里，监控标识用于标识一个监控任务。
需监控的事件参数可以采用多种实现方式，
第一：直接给出事件的定义，包含事件的名称，以及相关的参数：
事件A：监控位置
{
合法位置坐标；
}
第二：预先由CSE和SCEF/IWF或CSE和HSS之间通过交互，将事件定义列表事先发送到SCEF/IWF，或HSS，由此需监控的事件参数可以是事件标识，例如：
Event-A；
如果事件定义列表事先发送到SCEF/IWF，那么SCEF/IWF在接收到监控请求后，根据列表查询可以知道Event-A是，例如，监控是否离线；如果事件定义列表事先发送到HSS，那么SCEF/IWF在接收到监控请求后，在发送到监控执行者的过程中可以通过向HSS查询Event-A是，例如，监控是否离线。
2、SCEF/IWF接收到监控请求消息后，发送响应消息给CSE。
2.1、如果SCEF/IWF确认可以执行该监控任务，则在响应消息中指示成功接受监控任务。
2.2、如果SCEF确认不能执行该监控任务，则在响应消息中指示拒绝执行监控任务。
3、SCEF/IWF将监控任务发送给监控执行者，其中包含监控标识，监控执行者保存监控任务。
该步骤在承载网内部可以采用如下执行方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF发送监控任务信息到MME/SGSN，其中包含监控标识，或监控标识和SCEF/IWF的标识。
当承载网部署不只一个SCEF/IWF时，需要通过SCEF/IWF的标识发送监控报告到正确的SCEF/IWF。
2)SCEF/IWF发送监控任务信息到HSS，其中包含监控标识，或监控标识和SCEF/IWF的标识；
如果监控还需要其他的承载网节点执行，HSS发送监控任务到其他承载网节点，例如发送监控任务信息到MME或SGSN，其中包含监控标识。
5、在检测到需监控的事件后，监控执行者发送监控报告给监控接收者，其中包含监控标识。
该步骤在承载网内部可以采用如下执行方式：
1)MME，或SGSN，或HSS直接发送监控报告给SCEF/IWF；
2)MME或SGSN发送监控报告给HSS，HSS转发监控报告给SCEF/IWF；
3)MME或SGSN向HSS查询到SCEF/IWF的标识后，发送监控报告给SCEF/IWF。
6、SCEF/IWF在接收到监控报告后，将监控报告发送给CSE。
7、如果在某个时刻，CSE认为不再需要继续监控指定的终端，CSE发送监控停止请求消息给SCEF/IWF，请求消息中包含：
1)监控标识：CSE需要停止的监控任务的监控标识；或，2)监控标识：CSE需要停止的监控任务的监控，和终端标识：被监控的终端的标识。
注：这里的两种选项是为下一步向HSS查询签约数据时可能需要的不同信息。传统的向HSS查询签约数据必须要终端的标识，但是本优选实施例方案也考虑监控的特 殊场景，那就是使用监控标识也可以查询到所需要的信息。
8、SCEF/IWF接收到监控停止请求消息，在确认可以执行该请求后，发送监控终止消息给监控执行者，监控终止消息中包含CSE发送的监控停止请求消息中的监控标识。
SCEF/IWF发送监控终止消息给监控执行者可以采用以下方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF发送监控终止消息到MME/SGSN，其中包含监控标识。
2)SCEF/IWF发送监控终止请求到HSS，其中包含监控标识；
如果监控还需要其他的承载网节点执行，HSS发送监控终止请求到其他承载网节点，例如，发送监控终止请求到MME或SGSN。
9、HSS，或MME，或SGSN接收到监控终止指令后，检查本地是否保存有跟所收到的监控标识相关联的监控任务的信息。
9.1、如果有，则删除跟监控标识相关的监控任务信息。
9.2、如果没有，则发送监控终止拒绝消息给SCEF/IWF。拒绝消息中可以指示监控任务不存在。
10、如果CSE需要更改监控任务的某个参数，CSE发送更新监控请求消息给SCEF/IWF，请求消息中包含监控标识和需要更新的监控任务的参数，监控标识设置为指示需要更新哪一个监控任务的参数，需要更新的监控任务的参数可以包含一个或多个以下参数：
1)监控事件(更新该监控标识对应监控任务的监控事件)；2)监控报告的次数(更新该监控标识对应监控任务的监控报告的次数)；3)监控持续时长(更新该监控标识对应监控任务的监控持续)；4)监控开始时间(更新该监控标识对应监控任务的监控开始时间)；5)监控结束时间(更新该监控标识对应监控任务的监控结束时间)；6)事件发生后需执行的操作(更新该监控标识对应监控任务的事件发生后需执行的操作)；7)被监控的终端；(同步骤7中的需要终端标识的理由相同，用于可能SCEF/IWF向HSS查询签约数据所需)。
11、SCEF/IWF接收到更新监控请求消息后，在确认可以执行该请求后，将监控标识和需要更新的监控任务的参数发送给监控执行者，
SCEF/IWF将监控标识和需要更新的监控任务的参数发送给监控执行者可以采用以下方式：
1)SCEF/IWF向HSS发送签约数据请求消息，请求消息中包含终端标识，或/和监控标识；
HSS发送签约数据响应消息给SCEF/IWF，其中包含执行监控的网元的标识或地址，例如，MME的标识或地址，或SGSN的标识或地址；
SCEF/IWF将监控标识和需要更新的监控任务的参数发送给MME/SGSN。
2)SCEF/IWF将监控标识和需要更新的监控任务的参数发送给HSS；
如果监控还需要其他的承载网节点执行，HSS将监控标识和需要更新的监控任务的参数发送给其他承载网节点，例如，发送到MME或SGSN。
12、HSS，MME或SGSN接收到监控标识和需要更新的监控任务的参数后，检查本地是否保存有跟接收到的监控标识对应的监控任务信息。
12.1、如果有，则根据需要更新的监控任务的参数更新本地保存的监控任务的参数；
12.2、如果没有，则发送更新监控拒绝消息给SCEF/IWF，拒绝消息中可以指示监控任务不存在。
显然，本领域的技术人员应该明白，上述的本发明实施例的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中的监控方案，不仅使得业务平台，以及对应应用的操作复杂，而且对监控任务的监控效率低下的问题，进而达到了依据监控任务对应的监控标识进行交互执行监控处理，不仅有效地降低了监控的复杂度，以及监控成本，而且提高了监控效率的效果。

Claims (26)

  1. 一种监控处理方法，包括：
    监控接收者接收监控发起者发送的监控请求消息，其中，所述监控请求消息中包含有监控任务；
    所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或监控执行者进行交互执行监控处理。
  2. 根据权利要求1所述的方法，其中，
    所述监控标识由所述监控发起者分配，并携带在所述监控请求消息中；或者，
    所述监控标识由所述监控接收者在接收到所述监控发起者发送的监控请求消息后，由所述监控接收者为所述监控请求消息中的所述监控任务分配。
  3. 根据权利要求1所述的方法，其中，所述监控接收者依据所述监控任务对应的监控标识与所述监控执行者进行交互执行监控处理包括：
    所述监控接收者向所述监控执行者发送监控执行请求消息，其中，所述监控执行请求消息中包含有所述监控标识，以及所述监控任务。
  4. 根据权利要求3所述的方法，其中，在所述监控接收者向所述监控执行者发送所述监控执行请求消息之前，还包括：
    向归属用户服务器HSS发送签约数据请求消息，其中，所述签约数据请求消息中携带有用于标识所述监控任务对应的终端的终端标识，和/或所述监控标识；
    依据从所述HSS接收到的签约数据响应消息中确定用于执行所述监控任务的所述监控执行者。
  5. 根据权利要求1所述的方法，其中，所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或所述监控执行者进行交互执行监控处理包括：
    所述监控接收者接收所述监控发起者发送的用于请求终止所述监控任务的监控终止请求消息，其中，所述监控终止请求消息中包含有指示终止的所述监控任务的所述监控标识；
    所述监控接收者依据所述监控终止请求消息，向所述监控执行者发送停止监控请求消息用于所述监控执行者依据所述监控标识终止所述监控任务，其中，所述停止监控请求消息中包含所述指示终止的所述监控任务的监控标识。
  6. 根据权利要求1所述的方法，其中，所述监控接收者依据所述监控任务对应的监控标识与所述监控发起者和/或所述监控执行者进行交互执行监控处理包括：
    所述监控接收者接收所述监控发起者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述更新监控请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；
    所述监控接收者依据所述更新监控请求消息，将监控任务更新请求消息发送给所述监控执行者用于所述监控执行者依据所述监控标识，以及更新的所述监控参数更新所述监控任务，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数。
  7. 根据权利要求1至6中任一项所述的方法，其中，所述监控任务包括的监控参数包括以下至少之一：
    被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
  8. 一种监控处理方法，包括：
    监控执行者接收监控接收者发送的监控执行请求消息，其中，所述监控执行请求消息中包含有用于标识所述监控任务的监控标识和所述监控任务；
    所述监控执行者对所述监控标识对应的所述监控任务执行监控处理。
  9. 根据权利要求8所述的方法，其中，在所述监控执行者接收所述监控接收者发送的所述监控执行请求消息之后，还包括：
    所述监控执行者接收所述监控接收者发送的用于请求终止所述监控任务的停止监控请求消息，其中，所述停止监控请求消息中包含有指示终止的所述监控任务的所述监控标识；
    所述监控执行者对所述监控标识对应的所述监控任务执行监控处理包括：所述监控执行者依据所述监控标识删除所述监控任务。
  10. 根据权利要求8所述的方法，其中，在所述监控执行者接收所述监控接收者发送的所述监控执行请求消息之后，还包括：
    所述监控执行者接收所述监控接收者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；
    所述监控执行者对所述监控标识对应的所述监控任务执行监控处理包括：所述监控执行者依据所述监控任务更新请求消息中的所述监控标识，以及所述监控任务更新的监控参数，将所述监控任务的监控参数更新为接收到的监控任务的监 控参数。
  11. 根据权利要求8至10中任一项所述的方法，其中，所述监控任务包括的监控参数包括以下至少之一：
    被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
  12. 一种监控处理装置，应用于监控接收者，包括：
    第一接收模块，设置为接收监控发起者发送的监控请求消息，其中，所述监控请求消息中包含有监控任务；
    第一处理模块，设置为依据所述监控任务对应的监控标识与所述监控发起者和/或监控执行者进行交互执行监控处理。
  13. 根据权利要求12所述的装置，其中，
    所述监控标识由所述监控发起者分配，并携带在所述监控请求消息中；或者，
    所述监控标识由所述监控接收者在接收到所述监控发起者发送的监控请求消息后，由所述监控接收者为所述监控请求消息中的所述监控任务分配。
  14. 根据权利要求12所述的装置，其中，所述第一处理模块包括：
    第一发送单元，设置为向所述监控执行者发送监控执行请求消息，其中，所述监控执行请求消息中包含有所述监控标识，以及所述监控任务。
  15. 根据权利要求14所述的装置，其中，所述第一处理模块还包括：
    第二发送单元，设置为向归属用户服务器HSS发送签约数据请求消息，其中，所述签约数据请求消息中携带有用于标识所述监控任务对应的终端的终端标识，和/或所述监控标识；
    第一确定单元，设置为依据从所述HSS接收到的签约数据响应消息中确定用于执行所述监控任务的所述监控执行者。
  16. 根据权利要求12所述的装置，其中，所述第一处理模块包括：
    第一接收单元，设置为接收所述监控发起者发送的用于请求终止所述监控任务的监控终止请求消息，其中，所述监控终止请求消息中包含有指示终止的所述监控任务的所述监控标识；
    第三发送单元，设置为依据所述监控终止请求消息，向所述监控执行者发送 停止监控请求消息用于所述监控执行者依据所述监控标识终止所述监控任务，其中，所述停止监控请求消息中包含所述指示终止的所述监控任务的监控标识。
  17. 根据权利要求12所述的装置，其中，所述第一处理模块包括：
    第二接收单元，设置为接收所述监控发起者发送的用于请求对所述监控任务进行更新的更新监控请求消息，其中，所述更新监控请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；
    第四发送单元，设置为依据所述更新监控请求消息，将监控任务更新请求消息发送给所述监控执行者用于所述监控执行者依据所述监控标识，以及更新的所述监控参数更新所述监控任务，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数。
  18. 根据权利要求12至17中任一项所述的装置，其中，所述监控任务包括的监控参数包括以下至少之一：
    被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
  19. 一种接口网元，位于承载网中，包括权利要求12至18中任一项所述的装置。
  20. 根据权利要求19所述的接口网元，其中，所述接口网元包括以下至少之一：服务能力展开功能实体SCEF、因特网工作功能实体IWF。
  21. 一种监控处理装置，应用于监控执行者，包括：
    第二接收模块，设置为接收监控接收者发送的监控执行请求消息，其中，所述监控执行请求消息中包含有用于标识所述监控任务的监控标识和所述监控任务；
    第二处理模块，设置为依据所述监控标识对所述监控任务执行监控处理。
  22. 根据权利要求21所述的装置，其中，还包括：
    第三接收模块，设置为接收所述监控接收者发送的用于请求终止所述监控任务的停止监控请求消息，其中，所述停止监控请求消息中包含有指示终止的所述监控任务的所述监控标识；
    所述第二处理模块，还设置为依据所述监控标识删除所述监控任务。
  23. 根据权利要求21所述的装置，其中，还包括：
    第四接收模块，设置为接收所述监控接收者发送的用于请求对所述监控任务 进行更新的更新监控请求消息，其中，所述监控任务更新请求消息中包含指示更新的所述监控任务的所述监控标识，以及所述监控任务更新的监控参数；
    所述第二处理模块，还设置为依据所述监控任务更新请求消息中的所述监控标识，以及所述监控任务更新的监控参数，将所述监控任务的监控参数更新为接收到的监控任务的监控参数。
  24. 根据权利要求21至23中任一项所述的装置，其中，所述监控任务包括的监控参数包括以下至少之一：
    被监控的终端、监控的事件、监控报告的次数、监控持续时长、监控开始时间、监控结束时间、监控的事件发生后执行的操作。
  25. 一种监控设备，位于承载网中，包括权利要求21至24中任一项所述的装置。
  26. 根据权利要求25所述的监控设备，其中，所述监控设备包括以下至少之一：归属用户服务器HSS、移动管理实体MME、服务通用分组无线业务GPRS支持节点SGSN。
PCT/CN2015/086903 2015-02-12 2015-08-13 监控处理方法及装置 WO2016127612A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/550,938 US10419950B2 (en) 2015-02-12 2015-08-13 Monitoring processing method and device
EP15881769.2A EP3258644B1 (en) 2015-02-12 2015-08-13 Monitoring processing method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510076618.0 2015-02-12
CN201510076618.0A CN105991363B (zh) 2015-02-12 2015-02-12 监控处理方法及装置

Publications (1)

Publication Number Publication Date
WO2016127612A1 true WO2016127612A1 (zh) 2016-08-18

Family

ID=56614193

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/086903 WO2016127612A1 (zh) 2015-02-12 2015-08-13 监控处理方法及装置

Country Status (4)

Country Link
US (1) US10419950B2 (zh)
EP (1) EP3258644B1 (zh)
CN (1) CN105991363B (zh)
WO (1) WO2016127612A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366272A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 传输消息的方法和装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9893939B2 (en) * 2015-03-22 2018-02-13 Lg Electronics Inc. Method for transmitting and receiving signal related to monitoring by SCEF in wireless communication system and apparatus for the same
US10382918B2 (en) * 2015-05-14 2019-08-13 Telefonaktiebolaget Lm Ericsson (Publ) System and methods for monitoring events associated with services of mobile devices
WO2017127102A1 (en) * 2016-01-22 2017-07-27 Nokia Solutions And Networks Oy Application relocation between clouds
CN107770756A (zh) * 2017-10-23 2018-03-06 中兴通讯股份有限公司 一种监控方法、终端、服务器、网关设备以及系统
CN108229183A (zh) * 2017-12-06 2018-06-29 链家网（北京）科技有限公司 一种业务数据监控方法及其监控设备
WO2020124287A1 (zh) * 2018-12-16 2020-06-25 吉安市井冈山开发区金庐陵经济发展有限公司 信息的监控方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101635653A (zh) * 2009-08-31 2010-01-27 杭州华三通信技术有限公司 一种实时性能管理方法和装置
CN102057646A (zh) * 2008-06-06 2011-05-11 艾利森电话股份有限公司 Ims性能监控
CN103442330A (zh) * 2013-06-28 2013-12-11 北京小米科技有限责任公司 一种位置通知的方法及装置
CN103716822A (zh) * 2012-10-09 2014-04-09 中兴通讯股份有限公司 监控方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6930985B1 (en) * 2000-10-26 2005-08-16 Extreme Networks, Inc. Method and apparatus for management of configuration in a network
GB2461716A (en) * 2008-07-09 2010-01-13 Advanced Risc Mach Ltd Monitoring circuitry for monitoring accesses to addressable locations in data processing apparatus that occur between the start and end events.
US20130297791A1 (en) * 2010-12-20 2013-11-07 Telefonaktiebolaget L M Ericsson (Publ) Method of and Device For Service Monitoring and Service Monitoring Management
CN102752877B (zh) * 2011-04-19 2015-01-21 华为技术有限公司 机器对机器服务管理设备、网络设备、业务处理方法及系统
CN103731870B (zh) * 2012-10-12 2019-09-10 中兴通讯股份有限公司 监控任务的管理方法及装置
US8989729B2 (en) * 2012-11-09 2015-03-24 Alcatel Lucent Network monitoring of user equipment events
US10136284B2 (en) * 2014-07-07 2018-11-20 Convida Wireless, Llc Coordinated grouping for machine type communications group based services
US9930516B2 (en) * 2015-05-15 2018-03-27 Samsung Electronics Co., Ltd. UE monitoring configuration method and apparatus

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102057646A (zh) * 2008-06-06 2011-05-11 艾利森电话股份有限公司 Ims性能监控
CN101635653A (zh) * 2009-08-31 2010-01-27 杭州华三通信技术有限公司 一种实时性能管理方法和装置
CN103716822A (zh) * 2012-10-09 2014-04-09 中兴通讯股份有限公司 监控方法及装置
CN103442330A (zh) * 2013-06-28 2013-12-11 北京小米科技有限责任公司 一种位置通知的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3258644A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366272A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 传输消息的方法和装置
CN110366272B (zh) * 2018-04-09 2021-10-15 华为技术有限公司 传输消息的方法和装置
US11324072B2 (en) 2018-04-09 2022-05-03 Huawei Technologies Co., Ltd. Message transmission method and apparatus

Also Published As

Publication number Publication date
CN105991363A (zh) 2016-10-05
EP3258644A1 (en) 2017-12-20
US10419950B2 (en) 2019-09-17
EP3258644B1 (en) 2020-07-22
US20180035313A1 (en) 2018-02-01
EP3258644A4 (en) 2018-04-11
CN105991363B (zh) 2020-11-03

Similar Documents

Publication Publication Date Title
WO2016127612A1 (zh) 监控处理方法及装置
CN112188444B (zh) 一种订阅服务的方法及装置
EP3800934A1 (en) Method for routing internet of things service
WO2018157439A1 (zh) 业务处理的方法和设备
EP3060018B1 (en) Registration method and system for common service entity
EP3145148B1 (en) Resource subscription processing method and device
US9867164B2 (en) Method and device for processing a specific request message in wireless communication system
US10609533B2 (en) Method and device for trigger management of a common service entity (CSE) and a network element of bearer network
EP3291592B1 (en) Monitoring management method and apparatus
EP3148156A1 (en) Sending method and apparatus and computer storage medium of notification message
US20240137269A1 (en) Method for instantiating edge application server and apparatus
WO2017071118A1 (zh) 监控资源管理的方法、装置和cse、存储介质
CN113892279A (zh) 资源订阅方法、设备、服务器以及计算机存储介质
WO2016184178A1 (zh) 资源的控制方法和装置
JP2016511451A (ja) ネットワーク機能を開くためのシステムおよび方法、ならびに関連するネットワーク要素
EP3185598B1 (en) Application registration method and apparatus
US20240098631A1 (en) Filters for bulk subscriptions
CN104507054B (zh) 一种群组成员信息更新的方法及相关设备
US20170085673A1 (en) Attribute Operating Method and Apparatus
US9374710B2 (en) Mediation server, control method therefor, communication device, control method therefor, communication system, and computer program
CN112788518A (zh) 一种位置服务的处理方法及相关设备
WO2017000640A1 (zh) 一种实现成员资源处理的方法及装置
US10805838B2 (en) Method and device for obtaining resources and information of SDN networks of different operators
US20170019872A1 (en) Registering, Deregistering and Standby Processing Methods and Systems for Terminal Peripheral
WO2017166438A1 (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: 15881769

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015881769

Country of ref document: EP