# US 10,375,530 B2 · Providing data file updates using multimedia broadcast multicast services > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,375,530 B2 - Document ID: US10375530B2 - Status: Granted - Kind: B2 - Application number: 15/619,208 - Filed: 2017-06-09 - Published: 2018-12-13 - Granted: 2019-08-06 - Earliest claimed: 2017-06-09 - Assignees: BlackBerry Limited - Applicants: BlackBerry Limited - Inventors: Adrian Buckley; Stephen John Barrett; Nicholas James Russell - Web page: https://patentgrep.com/patent/US10375530B2 ## CPC - H04W 4/06: Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 65/1016: IP multimedia subsystem [IMS] - H04L 65/4061: Push-to services, e.g. push-to-talk or push-to-video - H04L 65/611: for multicast or broadcast (systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06) - H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences - H04W 12/0431: Key distribution or pre-distribution; Key agreement - H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method is provided for providing application data. The method includes a network node receiving at least one application identifier (App-ID) associated with at least a first user equipment (UE) and a second UE; the network node requesting to receive notifications of updates to application data associated with the at least one App-ID; the network node configuring a broadcast entity to transmit application data associated with the at least one App-ID; and the network node sending configuration data to the first and second UEs for receiving application data from the broadcast entity. ## Claims ### Claim 1 A method for providing application data, the method comprising: receiving, at a network node, a first Session Initiation Protocol (SIP) message comprising at least one application identifier (App-ID) and at least one user ID associated with the at least one App-ID, wherein the at least one App-ID identifies at least one application in which at least a first user equipment (UE) and a second UE are both interested, wherein the at least one user ID identifies at least one of the first UE or the second UE, and wherein the network node receives the first SIP message from the first UE or the second UE; sending, by the network node, a second SIP message requesting to receive notifications of updates to application data associated with the at least one App-ID; configuring, by the network node, a broadcast entity to transmit updated application data associated with the at least one App-ID; and sending, by the network node, configuration data to the first and second UEs for receiving the updated application data from the broadcast entity. ### Claim 2 (depends on 1) The method of claim 1, further comprising the network node determining locations of the first UE and the second UE upon receiving a third SIP message comprising a notification of the updated application data associated with the at least one App-ID, wherein the notification is received from a data store to which the network node sent the second SIP message. ### Claim 3 (depends on 2) The method of claim 2, further comprising the network node configuring the data store to stream the updated application data to the broadcast entity and configuring the broadcast entity to transmit the updated application data to the first and second UEs upon determining that the first and second UEs are within a predefined geographical area, wherein the broadcast entity comprises a Broadcast-Multicast Service Center (BM-SC). ### Claim 4 (depends on 3) The method of claim 3, wherein the configuration data comprise Multimedia Broadcast Multicast Service (MBMS) information comprising an Internet Protocol (IP) address of the BM-SC and a port number associated with the IP address. ### Claim 5 (depends on 4) The method of claim 4, wherein the configuration data are configured such that the first and second UEs use the IP address and the port number to receive the updated application data over an MBMS channel at substantially the same time. ### Claim 6 (depends on 4) The method of claim 4, wherein the MBMS information further comprises encryption data to be used by the first and second UEs to decipher the updated application data transmitted by the BM-SC, wherein the network node receives the encryption data from the data store after determining that the first and second UEs are within the predefined geographical area. ### Claim 7 (depends on 2) The method of claim 2, further comprising: receiving, by the network node, location information associated with the first and second UEs in response to the network node sending a request to a Location Services (LCS) entity for the location information, wherein the request includes at least a first user ID and a second user ID associated with the first UE and the second UE, respectively; and determining, by the network node, the locations of the first and second UEs based on the location information received from the LCS entity, wherein the network node comprises a content manager, a mission critical (MC) push-to-talk (MCPTT) server, a group communication service (GCS) server, an MCData Server, an MCVideo server, a location management server or any combination thereof. ### Claim 8 (depends on 2) The method of claim 2, wherein the first SIP message comprises a SIP Publish message, wherein the second SIP message comprises a SIP Subscribe message, and wherein the third SIP message comprises a SIP Notify message. ### Claim 9 (depends on 1) The method of claim 1, wherein the first SIP message specifies one or more times and/or locations at which the first UE or the second UE prefers receiving updates to the at least one application identified by the at least one App-ID. ### Claim 10 (depends on 1) The method of claim 1, wherein the first SIP message is a modified version of a SIP Publish message specified by Third Generation Partnership Project (3GPP) technical specification (TS) 24.379, wherein the modified version is such that the SIP Publish message at least includes the at least one App-ID. ### Claim 11 A network node comprising: a memory comprising instructions; and a processor coupled to the memory and configured to execute the instructions such that the network node: receives a first Session Initiation Protocol (SIP) message comprising at least one application identifier (App-ID) and at least one user ID associated with the at least one App-ID, wherein the at least one App-ID identifies at least one application in which at least a first user equipment (UE) and a second UE are both interested, wherein the at least one user ID identifies at least one of the first UE or the second UE, and wherein the network node receives the first SIP message from the first UE or the second UE; sends a second SIP message requesting to receive notifications of updates to application data associated with the at least one App-ID; configures a broadcast entity to transmit updated application data associated with the at least one App-ID; and sends configuration data to the first and second UEs for receiving the updated application data from the broadcast entity. ### Claim 12 (depends on 11) The network node of claim 11, wherein the network node is configured to determine locations of the first UE and the second UE upon receiving a third SIP message comprising a notification of the updated application data associated with the at least one App-ID, wherein the notification is received from a data store to which the network node sent the second SIP message. ### Claim 13 (depends on 12) The network node of claim 12, wherein the network node configures the data store to stream the updated application data to the broadcast entity and configures the broadcast entity to transmit the updated application data to the first and second UEs upon determining that the first and second UEs are within a predefined geographical area, wherein the broadcast entity comprises a Broadcast-Multicast Service Center (BM-SC), and wherein the network node comprises a content manager, a Mission critical push-to-talk (MCPTT) server, a Group Communication Service (GCS) server, an MCData server, an MCVideo server, a location management server, or any combination thereof. ### Claim 14 (depends on 13) The network node of claim 13, wherein the configuration data comprise Multimedia Broadcast Multicast Service (MBMS) information comprising an Internet Protocol (IP) address of the BM-SC and a port number associated with the IP address. ### Claim 15 (depends on 14) The network node of claim 14, wherein the configuration data are configured such that the first and second UEs use the IP address and the port number to receive the updated application data over an MBMS channel at substantially the same time. ### Claim 16 (depends on 14) The network node of claim 14, wherein the MBMS information further comprise encryption data to be used by the first and second UEs to decipher the updated application data transmitted by the BM-SC, wherein the network node receives the encryption data from the data store after determining that the first and second UEs are within the predefined geographical area. ### Claim 17 A non-transitory computer-readable medium comprising instructions executable by a processor such that when executed, cause the processor to implement a method on a network node, the method comprising: receiving, at the network node, a first Session Initiation Protocol (SIP) message comprising at least one application identifier (App-ID) and at least one user ID associated with the at least one App-ID, wherein the at least one App-ID identifies at least one application in which at least a first user equipment (UE) and a second UE are both interested, wherein the at least one user ID identifies at least one of the first UE or the second UE, and wherein the network node receives the first SIP message from the first UE or the second UE; sending, by the network node, a second SIP message requesting to receive notifications of updates to application data associated with the at least one App-ID; configuring, by the network node, a broadcast entity to transmit updated application data associated with the at least one App-ID; and sending, by the network node, configuration data to the first and second UEs for receiving the updated application data from the broadcast entity. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, the method further comprising the network node determining locations of the first UE and the second UE upon receiving a third SIP message comprising a notification of the updated application data associated with the at least one App-ID, wherein the notification is received from a data store to which the network node sent the second SIP message. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, the method further comprising the network node configuring the data store to stream the updated application data to the broadcast entity and configuring the broadcast entity to transmit the updated application data to the first and second UEs upon determining that the first and second UEs are within a predefined geographical area, wherein the broadcast entity comprises a Broadcast-Multicast Service Center (BM-SC). ### Claim 20 (depends on 19) The non-transitory computer-readable medium of claim 19, wherein the configuration data comprise Multimedia Broadcast Multicast Service (MBMS) information comprising an Internet Protocol (IP) address of the BM-SC and a port number associated with the IP address. ### Claim 21 (depends on 20) The non-transitory computer-readable medium of claim 20, wherein the configuration data are configured such that the first and second UEs use the IP address and the port number to receive the updated application data over an MBMS channel at substantially the same time. ### Claim 22 (depends on 20) The non-transitory computer-readable medium of claim 20, wherein the MBMS information further comprise encryption data to be used by the first and second UEs to decipher the updated application data transmitted by the BM-SC, wherein the network node receives the encryption data from the data store after determining that the first and second UEs are within the predefined geographical area. ### Claim 23 (depends on 18) The non-transitory computer-readable medium of claim 18, the method further comprising: receiving, by the network node, location information associated with the first and second UEs in response to the network node sending a request to a Location Services (LCS) entity for the location information, wherein the request includes at least a first user ID and a second user ID associated with the first UE and the second UE, respectively; and determining, by the network node, the locations of the first and second UEs based on the location information received from the LCS entity, wherein the network node comprises a content manager, a mission critical push-to-talk (MCPTT) server, a group communication service (GCS) server, an MCData Server, an MCVideo server, a location management server, or any combination thereof.