# US 2016/0366237 A1 · Multimedia messaging service gateway (mmsgw) system, method of operating a multimedia messaging service gateway (mmsgw) system and a software product > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2016/0366237 A1 - Document ID: US20160366237A1 - Status: Published application - Kind: A1 - Application number: 15/183,261 - Filed: 2016-06-15 - Published: 2016-12-15 - Earliest claimed: 2015-06-15 - Assignees: Webtext Holdings Limited - Applicants: Webtext Holdings Limited - Inventors: Anthony Cahill; Colm Keating - Web page: https://patentgrep.com/patent/US20160366237A1 ## CPC - H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata - H04L 51/10: Multimedia information - H04L 51/58: Message adaptation for wireless communication - H04L 67/53: using third party service providers - H04L 67/5681: Pre-fetching or pre-delivering data based on network characteristics - H04W 4/12: Messaging; Mailboxes; Announcements - H04L 51/066: Format adaptation, e.g. format conversion or compression - H04W 88/16: Gateway arrangements - 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 Multimedia Messaging Service Gateway system for the reception of a content associated with a MMS message, the MMS message originating from a mobile device arranged in co-operation with a carrier comprising a server, where the MMSGW includes an ingress for reception of a notification to the MMSGW of sending of the MMS message and for forwarding of the notification to an initial parser arranged in co-operation with the server and arranged to obtain metadata associated with the content for production of an IP object based on the notification, a content retrieval for download of the content from the server according to the IP object, a store for storage of one or more of the retrieved content or metadata associated with the retrieved content, an egress arranged to transmit a MMSGW process completion indicator, and an API arranged to facilitate retrieval of one or more of the retrieved content or the metadata by at least one remote party. ## Claims ### Claim 1 A Multimedia Messaging Service Gateway (MMSGW) system (10), for the reception of a content associated with a MMS message, the MMS message originating from a mobile device (51) arranged in co-operation with a carrier comprising a server (52), the MMSGW (10) comprising: an ingress (110), for reception of a notification to the MMSGW (10) of sending of the MMS message and for forwarding of the notification to, an initial parser (120), arranged in co-operation with the server and arranged to obtain metadata associated with the content, for production of an IP object based on the notification, a content retrieval (130) for download of the content from the server according to the IP object, a store (90) for storage of one or more of the retrieved content or metadata associated with the retrieved content, an egress (140) arranged to transmit a MMSGW process completion indicator, an API (100), arranged to facilitate retrieval of one or more of the retrieved content or the metadata by at least one remote party. ### Claim 2 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the mobile device comprises one of: a handset (51); a mobile phone; a computer terminal. ### Claim 3 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein: the notification comprises one or more of the following characteristics: the notification originates from one of: the carrier, a third party or network, a third party service provider; or the notification comprises a protocol; or the notification comprises a descriptive file describing the content; or the notification comprises an identifier; or the notification comprises metadata associated with the content. ### Claim 4 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the content comprises at least one file. ### Claim 5 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the initial parser (120) further comprises one or more of a metadata retrieval or a metadata localization. ### Claim 6 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the store (90) comprises one or more of a content store (30) or a meta store (40), arranged internal or external to the MMSGW (10). ### Claim 7 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein at least one of: the ingress (110) comprises a pre-fetch queue; or the egress (140) comprises a post-fetch queue. ### Claim 8 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the server (52) comprises a plurality of servers. ### Claim 9 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the MMSGW further comprises a content processing (150), for post-retrieval processing of the content to produce a CP output, and arranged in co-operation with the content retrieval (130) and the egress (140). ### Claim 10 (depends on 9) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 9, the content processing (150) being further arranged in co-operation with the store (90) for storage of the CP output from the content processing (150). ### Claim 11 (depends on 9) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 9, wherein the CP output from the content processing (150) is arranged to comprise at least one file associated with the content. ### Claim 12 (depends on 1) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 1, wherein the API (100) is arranged to provide the at least one remote party with an API output. ### Claim 13 A method of operating a Multimedia Messaging Service Gateway (MMSGW) system, the MMSGW arranged for the reception of a content associated with a MMS message, the MMS message originating from a mobile device arranged in co-operation with a carrier comprising a server, the MMSGW comprising: providing an ingress (110), for reception of a notification to the MMSGW (10) of sending of the MMS message and for forwarding of the notification to an initial parser (120), providing the initial parser (120), arranged in co-operation with the server and arranged to obtain metadata associated with the content, for production of an IP object based on the notification, providing a content retrieval (130) for download of the content from the server according to the IP object, providing a store (90) for storage of one or more of the retrieved content or metadata associated with the retrieved content, providing an egress (140) arranged to transmit a MMSGW process completion indicator, providing an API (100), arranged to facilitate retrieval of one or more of the retrieved content or the metadata by at least one remote party. ### Claim 14 (depends on 13) A method of operating a MMSGW system, as claimed in claim 13, comprising at least one of the further steps of: arranging the mobile device (51) to comprise one of: a handset; a mobile phone; a computer terminal; arranging the notification to include one or more of the following characteristics: the notification originates from one of: the carrier, a third party or network, a third party service provider; or the notification comprises a protocol; or the notification comprises a descriptive file describing the content; or the notification comprises an identifier; or the notification comprises metadata associated with the content; arranging the content to comprise at least one file; arranging the initial parser (120) to further comprise one or more of a metadata retrieval or a metadata localization; arranging the store (90) to comprise one or more of a content store (30) or a meta store (40), arranged internal or external to the MMSGW (10); arranging one or more of the ingress (110) to comprise a pre-fetch queue or the egress (140) to comprise a post-fetch queue; arranging the server (52) to comprise a plurality of servers. ### Claim 15 (depends on 13) A method of operating a MMSGW system, as claimed in claim 13, comprising at least one of the further steps of: arranging the MMSGW (10) to further comprise a content processing (150), for post-retrieval processing of the content to produce a CP output, and arranged in co-operation with the content retrieval (130) and the egress (140); or arranging the CP output from the content processing (150) to comprise at least one file associated with the content. ### Claim 16 (depends on 13) A method of operating a MMSGW system, as claimed in claim 13, comprising the further step of arranging the API (100) to provide the at least one remote party with an API output. ### Claim 17 (depends on 13) A software product recorded on machine readable data storage media, characterized in that said software product is executable upon computing hardware for implementing a method as claimed in claim 13. ### Claim 18 (depends on 3) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 3, wherein: the notification further comprises one or more of the following characteristics: the notification comprises an HTTP, SMPP, MM4 or MM7 protocol; or the notification comprises a descriptive file describing the content in XML or JSON format; or the notification comprises an identifier arranged to facilitate obtaining a description of the content. ### Claim 19 (depends on 4) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 4, wherein the at least one file comprises an image, a video, or a sound file. ### Claim 20 (depends on 6) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 6, wherein the one or more of a content store or a meta store are implemented as a memory or a database or a plurality of memories or databases. ### Claim 21 (depends on 11) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 11, wherein the at least one file associated with the content is arranged in a desired format. ### Claim 22 (depends on 11) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 11, wherein metadata is associated with the at least one file. ### Claim 23 (depends on 12) A Multimedia Messaging Service Gateway (MMSGW) system, as claimed in claim 12, wherein the API comprises one or more of a JSON format, a number of parts of the message, a MIME type, a size, or a file name of a message component. ### Claim 24 (depends on 14) A method of operating a MMSGW system, as claimed in claim 14, comprising at least one of the further steps of: arranging the notification to include one or more of the following characteristics: the notification comprises an HTTP, SMPP, MM4 or MM7 protocol; or the notification comprises a descriptive file describing the content in XML or JSON format; or the notification comprises an identifier arranged to facilitate obtaining a description of the content; arranging the content to comprise at least one image, video, or sound file; implementing the one or more of a content store or a meta store as a memory or a database or a plurality of memories or databases. ### Claim 25 (depends on 15) A method of operating a MMSGW system, as claimed in claim 15, further comprising arranging the content processing (150) in co-operation with the store (90) for storage of the CP output from the content processing (150). ### Claim 26 (depends on 15) A method of operating a MMSGW system, as claimed in claim 15, wherein the at least one file associated with the content is arranged in a desired format. ### Claim 27 (depends on 15) A method of operating a MMSGW system, as claimed in claim 15, further comprising arranging the CP output from the content processing (150) to comprise metadata associated with the at least one file. ### Claim 28 (depends on 16) A method of operating a MMSGW system, as claimed in claim 16, comprising the further step of arranging the API (100) to comprise at least one of a JSON format, a number of parts of the message, a MIME type, a size, or a file name of a message component.