Conveyance of application communication patterns from an external application server to a 3rd generation partnership project system
View Patent ↗A machine type communication interworking function (MTC-IWF) is configured to receive from a service capability exposure function (SCEF), services capability server (SCS), or a third-party application server (AS), application communication pattern information defined by an MTC application and representing characteristics of machine-to-machine (M2M) communications expected from a user equipment (UE) machine type communication (MTC) device. The MTC-IWF being configured to communicate the information to a mobility management entity (MME) that thereby provides core network (CN) originated assistance to an evolved universal terrestrial radio access network node B (eNB). Disclosed are embodiments for providing the information in the form of Diameter-based messages communicated through Tsp, T5, and other interfaces, or through an application programming interface (API) exposed by the SCEF, SCS, or MTC-IWF.
1. A machine type communication interworking function (MTC-IWF) apparatus for operation in a core network of a long term evolution (LTE) wireless network, the MTC-IWF apparatus comprising:
a Tsp interface to receive, from a services capability server (SCS), a request message including application communication pattern information and a request that the MTC-IWF apparatus provide the application communication pattern information to a mobility management entity (MME); and
a T5 interface to directly submit the application communication pattern information from the MTC-IWF to the MME, in which the Tsp interface is configured to transmit, from the MTC-IWF apparatus to the SCS, a Diameter-based answer message indicating whether the MME received the application communication pattern information, and in which the Tsp interface is further configured to transmit the Diameter-based answer message by indicating it is an Application-Traffic-Configuration-Information (ATCI) command.
2. The MTC-IWF apparatus of claim 1 , in which the Tsp interfaces is further configured to transmit the Diameter-based answer message having an Internet Assign Number Authority (IANA) Diameter Header code value representing a Device-Action-Answer (DAA) command.
3. The MTC-IWF apparatus of claim 1 , in which the Tsp interface is further configured to transmit the Diameter-based answer message having an Internet Assign Number Authority (IANA) Diameter Header code value representing a Device-Notification-Answer (DNA) command.
4. The MTC-IWF apparatus of claim 1 , in which the request message comprises a Diameter-based request message, and in which the Tsp interface is configured to receive the Diameter-based request message having an Internet Assign Number Authority (IANA) Diameter Header code value representing a Device-Action-Request (DAR) command including the application communication pattern information.
5. The MTC-IWF apparatus of claim 1 , in which the request message comprises a Diameter-based request message, and in which the Tsp interface is configured to receive the Diameter-based request message having an Internet Assign Number Authority (IANA) Diameter Header code value representing a Device-Notification-Request (DNR) command including the application communication pattern information.
6. The MTC-IWF apparatus of claim 1 , in which the request message comprises a Diameter-based request message, and in which the Tsp interface is configured to receive the Diameter-based request message having an Internet Assign Number Authority (IANA) Diameter Header code value representing a Device-Information-Report (DIR) command including the application communication pattern information.
7. The MTC-IWF apparatus of claim 1 , in which the request message comprises a Diameter-based request message, and in which the Tsp interface is configured to receive the Diameter-based request message having an Internet Assign Number Authority (IANA) Diameter Header code value representing an ATCI command type.
8. The MTC-IWF apparatus of claim 1 , further comprising a network communications interface configured to expose a representational state transfer (REST) application programming interface (API) for receiving the request message independent of the Tsp interface.
9. A mobility management entity (MME) for dynamically receiving application communication pattern information associated with a user equipment (UE) device in a long term evolution (LTE) wireless network, the MME comprising:
a communication port to receive, from a machine type communication interworking function (MTC-IWF) node, application communication pattern information provided by a service capability exposure function (SCEF) or a services capability server (SCS) for representing communication patterns of an MTC application in operative association with the UE, in which the communication port is configured for communication over a T5 interface, and in which the communication port is configured to receive the application communication pattern information during a T5 device trigger procedure initiated by the MTC-IWF node;
a transmitter device communicatively couplable with an evolved universal terrestrial radio access network node B (eNB) and configured to provide the application communication pattern information to the eNB; and
circuitry configured to identify from the application communication pattern information an attribute value pair (AVP) including a traffic activity parameter of the application communication pattern information.
10. The MME of claim 9 , in which the AVP includes at least one of traffic type, traffic direction, Inter-Arrival Time (IAT), sub-IAT, packet size/length, time window allowed to transmit, service quality of service, service priority, or an Application-Port-Identifier AVP.
11. The MME of claim 9 , further comprising circuitry configured to provide the application communication pattern information to the eNB in response to S1 establishment.
12. The MME of claim 9 , further comprising circuitry configured to provide the application communication pattern information to the eNB in response to a predetermined timer value for updating the eNB.
13. A method for providing core network (CN) assistance information to a mobility management entity (MME) operating in compliance with one or more 3rd Generation Partnership Project (3GPP) long term evolution (LTE) standards including LTE-Advanced (LTE-A), the method comprising:
receiving at a service capability exposure function (SCEF) or a service capability server (SCS), a first command from an application server (AS) through an application programming interface (API) exposed by the SCEF/SCS, the first command including application communication pattern information;
communicating with a machine type communication interworking function (MTC-IWF) entity to convey the application communication pattern information to the MTC-IWF entity and thereby cause the MTC-IWF entity to submit the application communication pattern information to the MME; and
receiving a second command from the MTC-IWF entity, the second command indicating whether the application communication pattern information was successfully delivered to the MME.
14. The method of claim 13 , further comprising receiving the second command in the form of a Device-Action-Answer (DAA) command.
15. The method of claim 13 , further comprising receiving the second command in the form of a Device-Information-Answer (DIA) command.
16. The method of claim 13 , in which the MTC-IWF entity is co-located with the SCEF/SCS, and the communicating comprising an internal Tsp trigger submission for the co-located MTC-IWF and SCEF/SCS.