# US 12,120,051 B2 · MTC-IWF entity, SCS entity, signaling method, and computer readable medium > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,120,051 B2 - Document ID: US12120051B2 - Status: Granted - Kind: B2 - Application number: 17/897,541 - Filed: 2022-08-29 - Published: 2022-12-29 - Granted: 2024-10-15 - Earliest claimed: 2012-12-21 - Assignees: NEC Corporation - Applicants: NEC Corporation - Inventors: Tetsuo Inoue; Takanori Iwai - Web page: https://patentgrep.com/patent/US12120051B2 ## CPC - H04L 5/0048: {Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091)} - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04W 8/12: between location registers or mobility servers - H04W 48/08: Access restriction or access information delivery, e.g. discovery data delivery (signalling during connection H04W76/00) - H04W 72/20: Control channels or signalling for resource management - H04W 84/04: Large scale networks; Deep hierarchical networks - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A Machine Type Communication Inter Working Function (MTC-IWF) entity (1) includes a trigger controller (11) and a notification service controller (12). The trigger controller (11) controls a device trigger of an MTC device (3) requested from an SCS entity (2). The notification service controller (12) is configured to send, to the SCS entity (2), a subscription request for a notification service including providing a PLMN (5) with management information which is collected outside (4) the PLMN (5) regarding the MTC device (3), and receive, from the SCS entity, a message containing the management information (2) when the subscription request has been accepted. Accordingly, it is possible to contribute to, for example, improvement in collaborative and cooperative operations between the PLMN and an M2M service layer. ## Claims ### Claim 1 A method implemented by a server, the method comprising: hosting an application in an external network outside a Third Generation Partnership Project (3GPP) network; detecting an occurrence of an event corresponding to whether a user equipment (UE) has mobility or not; and in response to detecting the occurrence, sending to an entity in the 3GPP network, a message containing a parameter indicating whether the UE has mobility or not. ### Claim 2 (depends on 1) The method according to claim 1, wherein the parameter is related to a state transition of the UE. ### Claim 3 (depends on 1) The method according to claim 1, wherein the parameter is related to an idle period of the UE. ### Claim 4 (depends on 1) The method according to claim 1, wherein the message further contains a parameter indicating at least one of: a communication duration of the UE; or a communication interval of the UE. ### Claim 5 (depends on 4) The method according to claim 4, wherein the said sending comprises sending the message when the server is aware that at least one of the communication duration or the communication interval of the UE has changed. ### Claim 6 (depends on 1) The method according to claim 1, wherein the entity is in a Public Land Mobile Network (PLMN). ### Claim 7 (depends on 1) The method according to claim 1, further comprising receiving from the entity, before detecting the occurrence of the event, a subscription request for notifying the entity of the message containing the parameter, wherein the subscription request designates a group of a plurality of target UEs whose event related to a location update is to be detected. ### Claim 8 (depends on 1) The method according to claim 1, further comprising receiving from the entity, before detecting the occurrence of the event, a subscription request for notifying the entity of the message containing the parameter, wherein the subscription request designates a target type of the parameter, which indicates whether the UE has mobility or not. ### Claim 9 (depends on 1) The method according to claim 1, further comprising receiving from the entity, before detecting the occurrence of the event, a subscription request for notifying the entity of the message containing the parameter, wherein the subscription request designates a trigger for the notifying of the message. ### Claim 10 (depends on 1) The method according to claim 1, further comprising receiving from the entity, before detecting the occurrence of the event, a subscription request for notifying the entity of the message containing the parameter, wherein the subscription request designates a time for the notifying of the message. ### Claim 11 (depends on 1) The method according to claim 1, further comprising: receiving from the entity, before detecting the occurrence of the event, a first subscription request for notifying the entity of statistical information regarding the UE; sending to the entity, after receiving the first subscription request, a second subscription request for notifying the server of the event; receiving from the entity, information indicating the event; collecting the information indicating the event, sent from the entity; and calculating a statistical value from the collected information indicating the event, wherein the statistical value is the parameter indicating whether the UE has mobility or not. ### Claim 12 A method implemented by an entity, the method comprising: operating in a Third Generation Partnership Project (3GPP) network; and receiving, a message containing a parameter indicating whether a user equipment (UE) has mobility or not, wherein the message is sent, from a server that hosts an application in an external network outside the 3GPP network, in response to the server detecting an occurrence of an event corresponding to whether the UE has mobility or not. ### Claim 13 (depends on 12) The method according to claim 12, wherein the parameter is related to a state transition of the UE. ### Claim 14 (depends on 12) The method according to claim 12, wherein the parameter is related to an idle period of the UE. ### Claim 15 (depends on 12) The method according to claim 12, wherein the message further contains a parameter indicating at least one of: a communication duration of the UE; or a communication interval of the UE. ### Claim 16 (depends on 15) The method according to claim 15, wherein the parameter is sent when the server is aware that at least one of the communication duration or the communication interval of the UE has changed.