Charging for mtc small data transmission and trigger at mtc-iwf
Abstract
In order for charging SDT and MTC device trigger over control plane, there is provided a network node (40) that relays messages over a control plane (T5 and Tsp) between an MTC device (10) and an SCS (50). The network node (40) counts the number of messages successfully relayed, and generates a CDR in accordance with the counted number. The messages are SDT messages delivered from the MTC device (10) to the SCS (50), SDT messages delivered from the SCS (50) to the MTC device (10), or MTC device trigger messages delivered from the SCS (50) to the MTC device (10). The network node (40) transfers the CDR to an OCF (31) or a CDF (32).
Claims
exact text as granted — not AI-modified1 . A first network node in a mobile communication system including a User Equipment (UE), a second network node for mobility management, and a server, the first network node comprising:
at least one processor; and at least one memory coupled to the at least one processor, the at least one memory storing instructions that when executed by the at least one processor cause the at least one processor to: receive a message from the server, determine that the message indicates a device trigger based on the received message, deliver, responsive to determining that the message indicates the device trigger based on the received message, the device trigger to the UE via the second network node, and generate a Charging Data Record (CDR) for charging for the device trigger, the CDR including a field for an address of the first network node.
2 . The first network node of claim 1 , wherein the first network node is a Mobility Management Entity (MME).
3 . A method of a first network node in a mobile communication system including a User Equipment (UE), a second network node for mobility management, and a server, the method comprising:
receiving a message from the server; determining that the message indicates a device trigger based on the received message; delivering, responsive to determining that the message indicates the device trigger based on the received message, the device trigger to the UE via the second network node; and generating a Charging Data Record (CDR) for charging for the device trigger, the CDR including a field for an address of the first network node.
4 . The method of claim 3 , wherein the first network node is a Mobility Management Entity (MME).
5 . A User Equipment (UE) in a mobile communication system including a first network node, a second network node for mobility management, and a server, the UE comprising:
at least one processor; and at least one memory coupled to the at least one processor, the at least one memory storing instructions that when executed by the at least one processor cause the at least one processor to: receive data via the second network node from the first network node, wherein the data is a device trigger, the first network node receives a message from the server, and first network node determines that the message indicates the device trigger based on the received message, and send a response to the received data via the second network node to the first network node, causing the first network node to generate a Charging Data Record (CDR) including a field for an address of the first network node.
6 . A method of a User Equipment (UE) in a mobile communication system including a first network node, a second network node for mobility management, and a server, the method comprising:
receiving data via the second network node from the first network node, wherein the data is a device trigger, the first network node receives a message from the server, and the first network node determines that the message indicates the device trigger based on the received message; and sending a response to the received data via the second network node to the first network node, and causing the first network node to generate a Charging Data Record (CDR) including a field for an address of the first network node.Join the waitlist — get patent alerts
Track US2020336320A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.