Machine type communication monitoring framework for 3GPP systems
A 3GPP monitoring architecture framework provides monitoring event configuration, detection, and reporting for machine-type and other mobile data applications by configuring monitoring on a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node through existing interfaces, such as Tsp, T4, and T5 interfaces.
1. A method comprising:
receiving from a node in a cellular network a monitoring request for monitoring event configuration of a monitoring event associated with a user equipment (UE) configured to provide machine type communications (MTC) in the cellular network;
determining whether the monitoring request is used for configuring the monitoring event on one or more of a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node;
sending to the node a monitoring response message to acknowledge acceptance or failure of the monitoring request;
determining whether the monitoring request would exceed a quota or rate of submitting monitoring requests; and
providing to the node a cause value indicating an error in response to determining the monitoring request has failed.
2. The method of claim 1 , wherein the node is a services capability server (SCS), an application server (AS), or an MTC interworking function (MTC-IWF).
3. The method of claim 1 , wherein the monitoring request comprises a first monitoring request message, and the method further comprises:
preparing a second monitoring request message based on the first monitoring request message; and
sending the second monitoring request message to the HSS.
4. The method of claim 1 , wherein the monitoring request includes a parameter to associate a monitoring event report to a specific monitoring request or includes an identification to associate a corresponding monitoring report with the node.
5. The method of claim 1 , wherein the monitoring request includes a parameter that indicates a time at which a related monitoring request is considered to expire.
6. The method of claim 1 , wherein the monitoring request includes a parameter that indicates a maximum number of event reports to be generated by the node until an associated monitoring event is considered to expire.
7. The method of claim 1 , wherein the monitoring request includes a parameter that makes a monitoring request a continuous monitoring request or that indicates that a monitoring request should generate a single monitoring report.
8. The method of claim 1 , wherein the monitoring request includes a monitoring type, and wherein the method further comprises providing a message including the monitoring type to the MME/SGSN.
9. The method of claim 1 , further comprising receiving the monitoring request from an MTC interworking function (MTC-IWF) through an S6m interface.
10. A method comprising:
receiving from a node in a cellular network a monitoring request for monitoring event configuration of a monitoring event associated with a user equipment (UE) configured to provide machine type communications (MTC) in the cellular network;
determining whether the monitoring request is used for configuring the monitoring event on one or more of a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node;
sending to the node a monitoring response message to acknowledge acceptance or failure of the monitoring request;
determining whether a services capability server (SCS) or application server (AS) are authorized to make the monitoring request; and
providing to the node a cause value indicating an error in response to determining the monitoring request has failed.
11. The method of claim 10 , wherein the node is a services capability server (SCS), an application server (AS), or an MTC interworking function (MTC-IWF).
12. The method of claim 10 , wherein the monitoring request comprises a first monitoring request message, and the method further comprises:
preparing a second monitoring request message based on the first monitoring request message; and
sending the second monitoring request message to the HSS.
13. The method of claim 10 , wherein the monitoring request includes a parameter to associate a monitoring event report to a specific monitoring request or includes an identification to associate a corresponding monitoring report with the node.
14. The method of claim 10 , wherein the monitoring request includes a parameter that indicates a time at which a related monitoring request is considered to expire.
15. The method of claim 10 , wherein the monitoring request includes a parameter that indicates a maximum number of event reports to be generated by the node until an associated monitoring event is considered to expire.
16. The method of claim 10 , wherein the monitoring request includes a parameter that makes a monitoring request a continuous monitoring request or that indicates that a monitoring request should generate a single monitoring report.
17. The method of claim 10 , wherein the monitoring request includes a monitoring type, and wherein the method further comprises providing a message including the monitoring type to the MME/SGSN.
18. The method of claim 10 , further comprising receiving the monitoring request from an MTC interworking function (MTC-IWF) through an S6m interface.