IP Library Granted Patent US 10,924,895
Granted Patent B2
US 10,924,895 · App. 13/747,207 · Granted Feb 16, 2021

Enhancing short message service addressing and routing

Inventors: Adrian Buckley (Tracy, CA); Nicholas James Russell (Newbury, GB)
Assignee: BlackBerry Limited
H04W4/14H04L61/106H04L69/24H04L61/305H04L61/6054H04L69/18H04W80/085
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,924,895
App. No.
13/747,207
Granted
Feb 16, 2021
Kind
B2
Abstract

A method for sending a short message service (SMS) message is provided. The method comprises receiving, by a destination home network database entity from a sending network entity, a first message containing an indication of support for a plurality of SMS message delivery protocols, wherein the SMS message is transmitted to a target entity address contained in the first message.

Claims (46)

1. A method for sending a short message service (SMS) message, the method comprising:

receiving, by a destination home network database entity from a sending network entity, a Diameter protocol request message identifying a target device, the Diameter protocol request message comprising a Diameter Send-Routing-Info-for-SM-Request command requesting a delivery protocol to deliver the SMS message to the target device identified in the Diameter protocol request message;

using the Diameter Send-Routing-Info-for-SM-Request command to identify, by the destination home network database entity responsive to receiving the Diameter protocol request message, a plurality of distinct addresses for communicating the SMS message from the sending network entity to the target device, the plurality of distinct addresses conveying a plurality of respective distinct delivery protocols for transmitting the SMS message to the target device; and

providing, by the destination home network database entity, to the sending network entity, in response to identifying the plurality of distinct addresses, a list comprising the plurality of distinct addresses and the plurality of distinct delivery protocols conveyed by the plurality of distinct addresses, respectively, each of the plurality of distinct addresses being directed to the target device, wherein the destination home network database entity is a Home Location Register (HLR) or a Home Subscriber Server (HSS).

2. The method of claim 1 , wherein the plurality of distinct addresses comprises at least one of a uniform resource identifier (URI), a uniform resource locator (URL), a Network Access Identifier (NAI), an IPv4 address, or an IPv6 address.

3. The method of claim 1 , wherein the respective distinct delivery protocols include at least one of:

mobile application part (MAP) protocol;

short message point-to-point protocol (SMPP);

remote authentication dial-in user service (RADIUS) protocol;

Diameter protocol; or

session initiation protocol (SIP).

4. The method of claim 1 , wherein at least one of the distinct delivery addresses is identified based on at least two of:

a source address of the Diameter protocol request message;

a status of a memory in the target device for receiving or storing SMS messages; or

a current location of the target device.

5. The method of claim 4 , wherein the current location is based on at least one of: a cell identity, a mobile country code (MCC), a mobile network code (MNC), or a way point associated with the target device.

6. The method of claim 1 , wherein the list lists the plurality of distinct delivery addresses in a prioritized order.

7. The method of claim 6 , wherein the sending network entity is configured to transmit the SMS message using an SMS message delivery protocol having a highest priority among the distinct delivery protocols, wherein the SMS message delivery protocol having the highest priority is based on the prioritized order.

8. The method of claim 6 , wherein the sending network entity is configured to attempt transmitting the SMS message to the target entity using a first delivery protocol conveyed by a first destination address before attempting to transmit the SMS message to the target entity using a second delivery protocol conveyed by a second destination address having a lower priority than the first destination address, wherein the first destination address and the second destination address are selected from the plurality of distinct addresses in the list.

9. The method of claim 1 , further comprising transmitting, from the from sending network entity to the target entity, the SMS message using a first delivery protocol conveyed by a first destination address selected from the plurality of distinct addresses, wherein the sending network entity is configured such that if the target entity fails to receive the SMS message transmitted using the first delivery protocol, the sending entity transmits the SMS message to the target entity using a second delivery protocol conveyed by a second destination address selected from the plurality of distinct addresses.

10. The method of claim 1 , wherein providing the list further comprises providing an indication to the sending network entity that at least one of the distinct delivery protocols for transmitting the SMS message is only applicable to the target device for a certain time.

11. The method of claim 1 , wherein providing the list further comprises providing routing information to the sending network entity, the routing information identifying one or more components that serve as intermediary hops along a path between the sending network entity and the target device.

12. The method of claim 1 , wherein the destination home network database entity provides the list to the sending network entity via a Diameter protocol response message.

13. The method of claim 1 , wherein the Diameter protocol request message further comprises a destination address of the target device, the destination address containing a Nature of Address Indicator field.

14. A destination home network database entity comprising:

a processor configured such that the destination home network database entity:

receives, from a sending network entity, a Diameter protocol request message identifying a target device, the Diameter protocol request message comprising a Diameter Send-Routing-Info-for-SM-Request command request a delivery protocol to deliver a short message service (SMS) message to the target device identified in the Diameter protocol request message,

identifies, using the Diameter Send-Routing-Info-for-SM-Request command, a plurality of distinct addresses for communicating the SMS message from the sending network entity to the target device, the plurality of distinct addresses conveying a plurality of respective distinct delivery protocols for transmitting the SMS message to the target device, and

provides, to the sending network entity, in response to identifying the plurality of distinct addresses, a list comprising the plurality of distinct addresses and the plurality of distinct delivery protocols conveyed by the plurality of distinct addresses, respectively, each of the plurality of distinct addresses being directed to the target device, wherein the destination home network database entity is a Home Location Register (HLR) or a Home Subscriber Server (HSS).

15. The destination home network database entity of claim 14 , wherein the plurality of distinct delivery addresses comprises a uniform resource identifier (URI).

16. The destination home network database entity of claim 14 , wherein the respective distinct delivery protocols include at least one of:

mobile application part (MAP) protocol;

short message point-to-point protocol (SMPP);

remote authentication dial-in user service (RADIUS) protocol;

Diameter protocol; or

session initiation protocol (SIP).

17. The destination home network database entity of claim 14 , wherein at least one of the distinct delivery addresses is identified based on a status of a memory in the target device for receiving or storing SMS messages and at least one of:

a source address of the Diameter protocol request message; or

a current location of the target device.

18. The destination home network database entity of claim 17 , wherein the current location is based on at least one of: a cell identity, a mobile country code (MCC), a mobile network code (MNC), or a way point associated with the target device.

19. The destination home network database entity of claim 14 , wherein the list lists the plurality of distinct delivery addresses in a prioritized order.

20. The destination home network database entity of claim 19 , wherein the sending network entity is configured to transmit the SMS message using an SMS message delivery protocol having a highest priority among the distinct delivery protocols, wherein the SMS message delivery protocol having the highest priority is based on the prioritized order.

21. A non-transitory computer medium storing computer readable instructions, the computer readable instructions adapted to be executed by a processor to implement a method for sending a short message service (SMS) message, the method comprising:

receiving, by a destination home network database entity from a sending network entity, a Diameter protocol request message identifying a target device, the Diameter protocol request message comprising a Diameter Send-Routing-Info-for-SM-Request command request a delivery protocol to deliver the SMS message to the target device identified in the Diameter protocol request message;

using the Diameter Send-Routing-Info-for-SM-Request command to identify, by the destination home network database entity responsive to receiving the Diameter protocol request message, a plurality of distinct addresses for communicating the SMS message from the sending network entity to the target device, the plurality of distinct addresses conveying a plurality of respective distinct delivery protocols for transmitting the SMS message to the target device; and

providing, by the destination home network database entity, to the sending network entity, in response to identifying the plurality of distinct addresses, a list comprising the plurality of distinct addresses and the plurality of distinct delivery protocols conveyed by the plurality of distinct addresses, respectively, each of the plurality of distinct addresses being directed to the target entity, wherein the destination home network database entity is a Home Location Register (HLR) or a Home Subscriber Server (HSS).

Assignments (7)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
CHANGE OF NAME Recorded Aug 13, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 033541/0704 →