U.S. patent application number 12/276251 was filed with the patent office on 2009-03-19 for methods, systems, and computer program products for providing media content delivery audit and verification services.
This patent application is currently assigned to Tekelec. Invention is credited to Peter J. Marsico, Travis E. Russell.
Application Number | 20090075635 12/276251 |
Document ID | / |
Family ID | 37968475 |
Filed Date | 2009-03-19 |
United States Patent
Application |
20090075635 |
Kind Code |
A1 |
Russell; Travis E. ; et
al. |
March 19, 2009 |
METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR PROVIDING MEDIA
CONTENT DELIVERY AUDIT AND VERIFICATION SERVICES
Abstract
Methods, systems, and computer program products for providing
media content delivery audit and verification services are
disclosed. In one example, a monitoring system analyzes messages
associated with communications in a wireless communications
network. The monitoring system identifies, from the messages,
messages that are associated with the request for or delivery of
media content to a wireless communications device via the network.
Copies of the messages relating to media content delivery are
generated, correlated, and analyzed in order to provide a network
operator with information that may be used to verify media content
delivery transactions and associated revenues.
Inventors: |
Russell; Travis E.;
(Clayton, NC) ; Marsico; Peter J.; (Chapel Hill,
NC) |
Correspondence
Address: |
JENKINS, WILSON, TAYLOR & HUNT, P. A.
Suite 1200 UNIVERSITY TOWER, 3100 TOWER BLVD.,
DURHAM
NC
27707
US
|
Assignee: |
Tekelec
|
Family ID: |
37968475 |
Appl. No.: |
12/276251 |
Filed: |
November 21, 2008 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11413064 |
Apr 27, 2006 |
|
|
|
12276251 |
|
|
|
|
60729997 |
Oct 25, 2005 |
|
|
|
Current U.S.
Class: |
455/414.2 |
Current CPC
Class: |
G06Q 20/382 20130101;
G06Q 30/06 20130101 |
Class at
Publication: |
455/414.2 |
International
Class: |
H04M 3/42 20060101
H04M003/42 |
Claims
1. A method for generating ratings indicative of media content
delivery to wireless subscribers, the method comprising: from at
least one location in a wireless communications network that is not
associated with a media content provider: (a) identifying messages
as being associated with delivery of media content to a plurality
of wireless subscribers via the wireless communications network;
and (b) generating, based on the messages, at least one measure
indicative of an absolute or relative number of media content
deliveries being made to the wireless subscribers.
2. The method of claim 1 wherein generating at least one measure
includes generating measures identifying an attribute of the media
content deliveries and absolute or relative numbers of deliveries
corresponding to each attribute.
3. The method of claim 2 wherein the media content attribute
comprises a content type associated with the delivered media
content.
4. The method of claim 2 wherein the media content attribute
comprises a content title associated with the delivered media
content.
5. A system for generating ratings based on media content being
delivered to a plurality of different wireless subscribers, the
system comprising: (a) a message monitoring function for analyzing
messages associated with communications in a wireless
communications network and for identifying, from the messages,
messages associated with delivery of media content to a plurality
of wireless communications devices; and (b) a correlation function
for receiving messages from the monitoring function and for
generating, based on the messages, at least one measure indicative
of an absolute or relative number of media content deliveries being
made to the wireless communications devices wherein the correlation
function is adapted to generate the at least one measure from a
location in the wireless communications network that is not
associated with a media content provider.
6. The system of claim 5 wherein the correlation function is
adapted to identify media content titles corresponding to the
deliveries and to generate absolute or relative numbers of
deliveries for each title.
7. A computer program product comprising computer-executable
instructions embodied in a computer-readable medium for performing
steps comprising: from at least one location in a wireless
communications network that is not associated with a media content
provider: (a) identifying messages as being associated with
delivery of media content to a plurality of wireless subscribers
via the wireless communications network; and (b) generating, based
on the messages, at least one measure indicative of an absolute or
relative number of media content deliveries being made to the
wireless subscribers.
Description
RELATED APPLICATIONS
[0001] This application is a divisional of U.S. patent application
Ser. No. 11/413,064, filed Apr. 27, 2006, which claims the benefit
of U.S. Provisional Patent Application Ser. No. 60/729,997, filed
Oct. 25, 2005, the disclosure of each of which is incorporated
herein by reference in its entirety.
TECHNICAL FIELD
[0002] The subject matter described herein relates to monitoring
transactions associated with delivery of media content. More
particularly, the subject matter described herein relates to
methods, systems, and computer program products for providing media
content delivery audit and verification services.
BACKGROUND ART
[0003] Over the past decade, the use of wireless communications
devices, such as mobile telephones and personal digital assistants,
has increased dramatically. This increased use has also led to an
increase in the capabilities of these communications devices. In
particular, wireless subscribers are increasingly using their
wireless communications devices to access and download various
types of media content, such as ringtones, music, video, graphics,
photos, etc. Access to vendors that provide media content is
provided by wireless network operators, who have previously
negotiated service level agreements with each vendor. A third party
clearinghouse entity is often used by media content owners to
control access to and bill for the use of media content.
[0004] FIG. 1 illustrates an exemplary mobile networking
environment 100, which includes a ringtone content provider 102, a
third party clearinghouse entity 104, a first general packet radio
service (GPRS) network 106 which is owned by network operator X, a
second global system for mobile communications (GSM) or Interim
Standard 41 (IS-41) cellular network 108 which is owned by network
operator Y, and a third Internet protocol (IP) multimedia subsystem
(IMS) network 110 which is owned by network operator Z. Mobile
subscribers 112, 114, and 116 are respectively associated with
networks 106, 108 and 110.
[0005] A typical service agreement may allocate 60% of revenue from
a ringtone sale transaction to ringtone content provider 102, 30%
of revenue from the transaction to network operator Y, and 10% of
revenue from the transaction to the clearinghouse 104. In the
example presented in FIG. 1, mobile subscriber 114 requests and
receives downloadable ringtone content 118 from content provider
102. Content provider 102 reports the content download to the
clearinghouse 104. Clearinghouse 104 subsequently bills mobile
subscriber 114 $1.00 for the downloaded ringtone. Clearinghouse 104
in turn pays $0.60 to the ringtone content provider 102, $0.30 to
network operator Y, and retains $0.10 as an administration fee.
[0006] One problem with the current media content delivery in
wireless communications networks involves the fact that while
network operator Y may be entitled to a 30% commission by a
previously negotiated service agreement, there is no mechanism
available to operator Y to independently monitor and verify content
download transactions that involve the operator's network. Within
the context of current content delivery solutions, a network
operator is completely reliant on the good faith dealings of the
content provider and the content delivery clearinghouse regarding
content delivery transactions and the associated revenue.
[0007] Another problem associated with delivery of media content in
wireless communications networks involves an operator's inability
to verify the success or failure of an attempted media content
download transaction. For instance, mobile subscriber 114 may
contact a customer service center associated with network operator
Y and claim that a ringtone download was purchased but never
received. Currently, network operator Y has no way to verify
whether or not the purchased ringtone content was successfully
delivered to mobile subscriber 114. This inability leaves a network
operator vulnerable to fraud and may result in a less than ideal
quality of service within the network.
[0008] Accordingly, there exists a need for improved methods,
systems, and computer program products for monitoring and auditing
the delivery of media content in a wireless communications
network.
SUMMARY
[0009] The subject matter described herein is generally directed to
methods, systems, and computer program products for providing media
content delivery audit and verification services. According to one
aspect of the subject matter described herein, a monitoring system
is adapted to analyze messages relating to communications in a
wireless communications network and to identify, from the messages,
messages that are associated with the request for or delivery of
media content via the network. Copies of the messages relating to
delivery of media content are generated, correlated, and analyzed
in order to provide a network operator with information that may be
used to verify media content delivery transactions and associated
revenues.
[0010] The term "media content," as used herein, refers to any type
of graphics, text, video, audio, audio/video, or other content that
a user may wish to obtain from a media content provider obtain via
a wireless communications network, and access via a wireless
communications device. Examples of media content include ringtones,
music files, video files, graphics files, audio files, such as
audiobooks, text files, etc.
[0011] The term "wireless communications network," as used herein,
refers to a network that is usable for communications between
wireless devices. Examples of such networks include IS-41, GSM,
Wi-Fi, or other types of networks where the link from the end user
device to the network occurs over a wireless communications
segment. It is understood that such networks may include wired
components for carrying signaling related to media communications
and also for carrying the media communications between network
nodes.
[0012] The term "wireless communications device," as used herein,
includes any device that a user can use for communications via a
wireless wireless network. Examples of such devices include mobile
telephones, personal digital assistants (PDAs), mobile phones with
PDA capabilities, and PDAs with mobile phone capabilities.
[0013] The subject matter described herein for providing media
content delivery audit and verification functionality may be
implemented using a computer program product comprising computer
executable instructions embodied in a computer readable medium.
Exemplary computer readable media suitable for implementing the
subject matter described herein include disk memory devices, chip
memory devices, programmable logic devices, application specific
integrated circuits, and downloadable electrical signals. In
addition, a computer readable medium that implements the subject
matter described herein may be located on a single device or
computing platform or may be distributed across multiple physical
devices and/or computing platforms.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Preferred embodiments of the subject matter described herein
will now be explained with reference to the accompanying drawings
of which:
[0015] FIG. 1 is a network diagram illustrating an exemplary media
content delivery service arrangement that includes a media content
provider and a media content delivery clearinghouse entity;
[0016] FIG. 2 is a network diagram illustrating a probe-based
revenue assurance and content delivery audit (RACDA) system and
exemplary messaging associated with a request for media content by
a wireless subscriber according to an embodiment of the subject
matter described herein;
[0017] FIG. 3 is a block diagram illustrates functional components
of a RACDA system according to an embodiment of the subject matter
described herein;
[0018] FIG. 4 is a network diagram illustrated a probe-based RACDA
system and exemplary messaging associated with the delivery of
media content from a media content provider according to an
embodiment of the subject matter described herein; and
[0019] FIG. 5 is a network diagram illustrating an integrated
message feed RACDA system and exemplary messaging associated with
the delivery of media content from a media content provider
according to an embodiment of the subject matter described
herein.
DETAILED DESCRIPTION OF THE INVENTION
[0020] FIG. 2 is a network diagram illustrating a network
environment 119 that includes a short message service center (SMSC)
128, a mobile subscriber 114, and a probe-based embodiment of
revenue assurance and content delivery audit (RACDA) system. For
purposes of illustration, network environment 119 is considered to
include components that operate in accordance with the global
system for mobile communications (GSM) standard. Accordingly,
mobile subscriber 114 and SMSC 128 are assumed to utilize equipment
that operates in a GSM network environment. It is understood that
the subject matter described herein is not limited to use in GSM
network environments. Embodiments of the subject matter described
herein may be operable in other communications network environments
including IS-41, general packet radio service (GPRS), IP multimedia
subsystem (IMS), session initiation protocol (SIP), radio access
network (RAN), and wireless-fidelity (WiFi) (such as 802.11x)
environments.
[0021] In the embodiment illustrated in FIG. 2, SMSC 128 is adapted
to communicate with signaling system 7 (SS7) network entities as
well as with short message point to point (SMPP) entities. SMSC 128
is further adapted to translate or convert SS7 short message
service (SMS)-formatted messages to SMPP-formatted messages and
vice-versa.
[0022] Network 119 also includes an exemplary revenue assurance and
content delivery auditing (RACDA) system 120. According to one
embodiment of the subject matter described herein, external
communications link monitoring probes 122 and 124 may be adapted to
generate copies of some or all messages observed on their
respective communications links and forward the message copies to
RACDA module 126. Link monitoring probes 122 and 124 may be any
suitable devices for passively copying signaling messages that
traverse network 119. In one example, probes 122 and 124 may be
implemented using any suitable stand-alone network data collection
system, including those available from Catapult Communications of
Mountainview Calif. RACDA module 126 receives and analyzes messages
copied by probes 122 and 124 and may use information obtained from
the message copies to generate media content delivery diagnostic
reports, revenue assurance reports, quality of service (QoS)
reports, media content delivery rating reports that are based on
one or more deliverable content attributes (e.g., attribute
type=ringtone, attribute title="James Bond Ringtone #9", etc.) and
other reports. RACDA module 126 may be implemented using any
suitable general-purpose computing platform with network
communication capabilities. In one exemplary implementation, RACDA
module 126 may be implemented using a SUN Netra.RTM. server.
[0023] The reports generated by RACDA module 126 may be usable by a
network operator to verify or audit service agreements with
affiliated content providers. For example, RACDA module 126 may
generate a media content delivery audit report that includes
information associated with media content deliveries via a wireless
network operator's network. The report may contain information
usable by the operator to obtain and/or audit payments from a media
content provider or clearinghouse for using the operator's network
to deliver media content via the operator's network. If the content
is downloadable content where the subscriber pays the media content
provider or the clearinghouse directly, the report generated by
RACDA module 126 may provide a useful way for the wireless network
operator to audit transactions to which the operator is not a
party.
[0024] The information collected by RACDA system 120 may also be
used to provide the network operator with real time or near-real
time content delivery diagnostic/QoS information. RACDA system 120
may copy, collect and analyze any type of message used to request
or deliver content through a network. Exemplary message
types/protocols that may be copied include SS7 mobile application
part (MAP) short message service (SMS), IETF Sigtran, SIP, IP,
hypertext transport protocol (HTTP), file transfer protocol (FTP),
simple mail transfer protocol (SMTP), and SMPP.
[0025] FIG. 3 is a block diagram of an exemplary RACDA system 120
according to an embodiment of the subject matter described herein.
Exemplary system 120 may include an external communications link
probe or message switch 122 or 124, which is adapted to observe
messages as they are carried on the communications link and
generate copies of some or all of these messages. For example,
probes 122 and 124 may include associated message monitoring
functions for identifying and copying messages associated with
media content delivery transactions.
[0026] System 120 may also include a message feed function 142 that
is adapted to be integrated with a communications network element.
Exemplary network elements may include a signal transfer points
(STPs), Internet protocol (IP) capable STPs, IP routers, short
message service center (SMSCs), short message gateways (SMGs),
mobile switching centers (MSCs), 3G message servers, SIP servers,
an IMS nodes, media gateway controllers (MGCs), and softswitches.
Integrated message feed (IMF) function 142 is adapted to observe
messages that are received by or transmitted from the host network
element and generate copies of some or all of the messages. IMF
function 142 may include an associated message monitoring functions
for identifying and copying messages associated with media content
delivery transactions.
[0027] One exemplary location for the integrated message feed
function to reside is on a network node that provides a network
routing function, such as an STP. System 120 may include multiple
external link probes, multiple IMF functions, and to operate using
both external link probes and IMF functions simultaneously.
[0028] System 120 further includes a message correlation function
144 that is adapted to receive copies of observed messages from
external link probe 122 or 124 or IMF function 142 and organize or
correlate these message copies, such that messages associated with
the same content delivery transaction are identified and grouped or
linked together.
[0029] In one embodiment, correlation function 144 is adapted to
generate a media content delivery transaction detail record (TDR)
for each observed media content delivery transaction. A media
content delivery TDR may include some or all parameters contained
in the message or messages associated with a media content delivery
transaction. A media content delivery TDR may, for example, include
information associated with a request from a mobile subscriber for
a media content download, as well as information associated with
the delivery of the requested content to the requesting subscriber.
In one embodiment, correlation function 144 may associate
date/timestamp information with a received message copy (and/or
TDR) that is indicative of when the message copy was received.
[0030] In another embodiment, correlation function 144 may organize
observed media content delivery transaction information according
to any number of different correlation profiles. Observed messages
that are correlated in accordance with a correlation profile may be
tagged with a correlation identifier or otherwise indexed so as to
facilitate fast and efficient access. Exemplary correlation
profiles include content provider, delivery date/time, requesting
subscriber, content type, delivery status, delivery mode, etc. For
example, a content provider correlation profile may be used to sort
or index observed content delivery transactions information by
content provider. A media content provider identifier, such as a
source network address that is uniquely associated with a media
content provider, may be used to sort or index the observed media
content delivery transaction information. In a similar manner, a
delivery date/time correlation profile may be used to sort or index
observed content delivery transaction information by the date/time
of the content delivery transaction. A requesting subscriber
correlation profile may be used to sort or index observed content
delivery transaction information by the requesting subscriber. A
subscriber identifier, such as a destination address (e.g., IP
address, mobile identification number, mobile subscriber ISDN
number, international mobile station identifier, electronic mail
address, etc.) that is uniquely associated with each requesting
mobile subscriber, may be used to sort or index the observed media
content delivery transaction information
[0031] A media content type correlation profile may be used to sort
or index observed content delivery transaction information by the
type of content associated with the delivery transaction. For
example, correlation function 144 may perform the correlation based
on payload type identification information contained in a message
associated with a media content delivery transaction. Payload type
identification information may include an explicit payload type
identification parameter contained in an observed content delivery
message, or such payload type information may be inferred based on
message characteristics, such as payload size. Exemplary media
content types may include ringtone, sports scores, stock ticker
information, photograph/graphic image, and music. The media content
type may also identify the format of the content, such as MPEG,
JPEG, MP3, etc. Alternatively, correlation function 144 may perform
such a content type correlation by exploiting knowledge that
certain types of content are sourced from specific source addresses
(e.g., IP host.sub.x/port.sub.n=ringtone content, IP
host.sub.y/port.sub.z=sport scores, etc.).
[0032] A delivery status correlation profile may be used to sort or
index observed content delivery transaction information by the
status or disposition of the delivery transaction. For example,
media content delivery status values may include an indicator of
the success or failure of a delivery transaction. Content delivery
status information may also include information related to a
delivery receipt or delivery confirmation message associated with a
media content delivery transaction. A delivery mode correlation
profile may be used to sort or index observed media content
delivery transaction information by the mode or transport
characteristics of the delivery transaction. For example,
correlation function 144 may perform the correlation based on a
transport mode attribute, where transport mode attributes may
include open system interconnection (OSI) layer attributes and SS7
protocol attributes. Delivery or transport mode attributes may
include those protocols (at any layer of the OSI or SS7 stacks)
used in a media content delivery transaction. Exemplary OSI
attributes that may be used by correlation function to correlate
messages associated with media control delivery transactions
include a layer 3 attribute=IP, a layer 4 attribute=transmission
control protocol (TCP), user datagram protocol (UDP) or stream
control transmission protocol (SCTP), and a layer 7 attribute=HTTP,
FTP, SMTP, SIP, or SMPP. Exemplary SS7 protocol attributes include
transaction capabilities application part (TCAP), mobile
application part (MAP), and SMS. Exemplary media content delivery
TDR records are presented below in Table 1.
TABLE-US-00001 TABLE 1 Exemplary Media Content Delivery TDR Records
Media Source Requesting Content Transaction Delivery Date/Timestamp
Address Subscriber ID Type Disposition Mode 1/4/06, 01:34:12
Provider 1 9193451212 Ringtone Successful IP/SIP 1/1/06, 11:45.09
Provider 2 Joe@AOL.com Ringtone Failed SMS
[0033] Correlation profiles may be logically combined to provide
more complex data correlations. For example, a media content
provider correlation profile and a delivery date/time correlation
profile may be logically combined to provide a view of media
content delivery transactions that occurred during a particular
date/time period, where the resulting information is sorted by
content provider. As described above, observed media content
delivery information (e.g., messages, message parameters, TDRs,
etc.) may be simultaneously correlated according to multiple
correlation profiles. Indices associated with each correlation or
logical combination of multiple correlations may be constructed and
stored to facilitate rapid, efficient access of the observed
content delivery transaction information. The correlation profiles
described above are merely illustrative of the types of
correlations that may be performed by RACDA system 120 and are not
intended to be an exhaustive list of possible correlations that
could be provided by correlation function 144.
[0034] System 120 includes a data server 146, which is adapted to
receive correlated media content delivery transaction information
from correlation function 144 and store the information. As
described above, media content delivery transaction information may
include a copy of an observed media content delivery message,
parameters associated with an observed media content delivery
message, a media content delivery TDR, an index to information
contained in an observed media content delivery message, or other
information associated with an observed content delivery
transaction.
[0035] A media content delivery audit application 148 is adapted to
access media content delivery transaction information that is
stored in data server 146. In one embodiment, application 148 may
include a reporting function that is adapted to generate a media
content delivery revenue assurance report, which details the number
of successful content delivery transactions that were observed
during a given period involving a particular media content
provider. The information included in this report may be used to
manually verify content delivery statistics provided by a media
content provider or clearinghouse entity.
[0036] In an alternate embodiment, application 148 may include a
reporting function that is adapted to receive media content
delivery transaction information provided by a media content
provider or clearinghouse entity and automatically analyze and
compare this information against media content delivery transaction
information stored on data server 146. A revenue assurance
discrepancy report may be generated based on the
analysis/comparison. The revenue assurance discrepancy report may
identify and highlight discrepancies between the media content
delivery transactions observed by system 120 and those transactions
reported or claimed by the content provider or clearinghouse
entity. An exemplary revenue assurance discrepancy report is
illustrated below in Table 2.
TABLE-US-00002 TABLE 2 Exemplary Revenue Assurance Discrepancy
Report Media Media Observed Observed Content Start End Content
Reported Successful Failed Provider Date Date Type Transactions
Transactions Transactions Provider 1 Jan. 1, 2006 Jan. 31, 2006
Ringtone 1,322,443 1,102,211 121,227 Provider 2 Jan. 1, 2006 Jan.
31, 2006 Ringtone 324,245 315,654 8,591
[0037] According to another aspect of the subject matter described
herein, application 148 is adapted to provide real time/near-real
time and historical media content delivery transaction information
to a network operations center or customer support center 150. This
information may be used by network operations staff to analyze and
diagnose problems associated with media content delivery
transactions, in response to inquiries or complaints received from
a network subscriber or from a media content provider.
[0038] For example, customer support center 150 may receive a call
from a mobile subscriber in which the subscriber claims that he or
she was billed for a requested media content download which was
never received. Network support personnel may provide application
148 with an identifier associated with the requesting mobile
subscriber (e.g., MSISDN, IMSI, TMSI, SIP URI, email address, IP
address, routing number (RN), directory number (DN), etc.), as well
as the approximate date/time of the content delivery request in
question. In response, application 148 is adapted to search media
content delivery information stored on data server 146 and generate
a viewable report 127 that presents all observed content delivery
transactions and their dispositions (e.g., successful, failed,
unknown, etc.) associated with the requesting mobile subscriber on
or about the specified date/time. The entire signaling/messaging
sequence associated with each observed content delivery transaction
may be displayed such that those content delivery transactions that
are identified as having a failed or unknown disposition may be
analyzed by the network operator.
[0039] According to yet another aspect of the subject matter
described herein, application 148 is adapted to log disputed media
content delivery transactions and provide a report of disputed
media content delivery transactions to a content provider and/or
clearinghouse entity. If it is determined that the mobile
subscriber customer is entitled to a refund and that the media
content delivery problem was associated with the service provided
by a media content provider, then application 148 may record and
log the refund transaction and also include refund related
information (e.g., refund amount) in the disputed media content
delivery transaction report. As such, the subject matter described
herein is adapted to assist a network operator in identifying and
recovering revenue that is lost as a result of fraudulent activity
or legitimate service problems associated with a media content
provider.
Exemplary Revenue Assurance and Media Content Delivery Auditing
System Implementations
[0040] FIG. 2 illustrates an exemplary media content delivery
transaction monitoring scenario that involves a request by mobile
subscriber 114 for a ringtone content download from content
provider 102. In this example, mobile subscriber 114 generates a
short message that serves as the request for downloading the
ringtone and transfers the message to the serving MSC (not shown).
The serving MSC receives the transferred message and generates a
related MAP MAP-MO-FORWARD-SHORT-MESSAGE message 130, which in this
example is transmitted to SMSC 128. The particular content
requested may be conveyed through information carried in the
payload portion of the short message, or the desired content may be
identified/associated with a short code or other destination
address specified in the short message. A detailed description of
MAP short message service messages is presented in 3GPP TS 09.02
V7.15.0 (2004-03); 3rd Generation Partnership Project; Technical
Specification Group Core Network; Mobile Application Part (MAP)
specification (Release 1998), the disclosure of which is
incorporated by reference herein in its entirety.
[0041] The MAP-MO-FORWARD-SHORT-MESSAGE message 130 is
detected/observed by probe 124 and a copy of the message is
generated. The message copy 132 is directed to RACDA module 126.
Exemplary parameters contained in the MAP-MO-FORWARD-SHORT-MESSAGE
message copy include an InvokeID parameter, an SM_RP_DA parameter,
an SM_RP OA parameter, an SM_RP_UI parameter, an IMSI User_Error
parameter, and a Provider_Error parameter. Detailed descriptions
and definitions of these parameters are located in the above
referenced MAP specification. Message copy 132 is provided to
correlation function 144. In this case, correlation function 144
determines that message 132 is associated with a new media content
delivery transaction and accordingly generates a new TDR that is
associated with the content delivery transaction. Some or all of
the information associated with message copy 132 is incorporated
within the TDR, and the TDR is then stored in data server 146.
[0042] SMSC 128 receives MAP message 130 and generates a related
SMPP DELIVER_SM message 134, which is transmitted to media content
provider 102. A detailed description of the SMPP protocol is
provided in SMS Forum standard, Short Message Point To Point
Protocol Specification V5.0, (Feb. 19, 2003), the disclosure of
which is incorporated by reference herein in its entirety. The SMPP
DELIVER_SM message 134 is detected/observed by probe 122 and a copy
of the message is generated. Message copy 136 is directed to RACDA
module 126.
[0043] Exemplary parameters contained in the SMPP DELIVER_SM
message copy include a service_type parameter, a source_addr_ton
parameter, a source_addr_npi parameter, a source_addr parameter, a
dest_addr_ton parameter, a dest_addr_npi parameter, a dest_addr
parameter, an esm_class parameter, a priority_flag parameter, a
schedule_delivery_time parameter, a validity_period parameter, a
registered_delivery parameter, an sm_length parameter, a
short_message parameter. Detailed descriptions and definitions of
these parameters are located in the above referenced SMPP
specification.
[0044] Message copy 136 is provided to correlation function 144. In
this case, correlation function 144 determines that message 136 is
associated with the previously opened media content delivery
transaction TDR, and some or all of the information contained in
message 136 is appended to the TDR associated with that
transaction. It will be appreciated that correlation function 144
may determine that messages 132 and 136 are associated with the
same media content delivery transaction based on a similarity or
other correlation that is identified between functionally similar
parameters in the messages or other message attributes (e.g.,
timestamp information). For example, the SM_RP_OA parameter value
in the MAP-MO-FORWARD-SHORT-MESSAGE message may be compared to the
source_addr parameter in the SMPP DELIVER_SM message.
[0045] Continuing with this media content delivery transaction
example, FIG. 4 illustrates an exemplary message flow associated
with the response of media content provider 102 to the content
download request of mobile subscriber 114. In response to receiving
media content download request message 134, media content provider
102 generates a SMPP SUBMIT_SM message 160 that includes the
requested download content. Exemplary parameters contained in the
SMPP SUBMIT_SM message copy include a service_type parameter, a
source_addr_ton parameter, a source_addr_npi parameter, a
source_addr parameter, a dest_addr_ton parameter, a dest_addr_npi
parameter, a dest_addr parameter, an esm_class parameter, a
priority_flag parameter, a schedule_delivery_time parameter, a
validity_period parameter, a registered_delivery parameter, an
sm_length parameter, a short_message parameter. Detailed
descriptions and definitions of these parameters are located in the
above referenced SMPP specification.
[0046] Message 160 is transmitted to SMSC 128. The SMPP SUBMIT_SM
message 134 is detected/observed by probe 122 and a copy of the
message is generated. Message copy 162 is directed to RACDA module
126 and provided to correlation function 144. Correlation function
144 determines that message 162 is associated with the previously
opened media content delivery transaction TDR, and some or all of
the information contained in message 162 is appended to the TDR
associated with that transaction. Once again, correlation function
144 may determine that messages 132, 136, and 162 are associated
with the same media content delivery transaction based on a
similarity or other correlation that is identified between
functionally similar parameters in the messages or other message
attributes (e.g., timestamp information).
[0047] SMSC 128 receives SMPP message 160 and generates a related
MAP-MT-FORWARD-SHORT-MESSAGE message 164, the media content payload
of which is ultimately delivered to requesting mobile subscriber
114. The MAP-MT-FORWARD-SHORT-MESSAGE message 164 is
detected/observed by probe 124 and a copy of the message is
generated. Message copy 166 is directed to RACDA module 126.
Exemplary parameters contained in the MAP-MT-FORWARD-SHORT-MESSAGE
message copy may include an InvokeID parameter, an SM_RP_DA
parameter, an SM_RP_OA parameter, an SM_RP_UI parameter, a
User_Error parameter, and a Provider_Error parameter. Detailed
descriptions and definitions of these parameters can be found in
the above-referenced MAP specification. Message copy 166 is
provided to correlation function 144. In this case, correlation
function 144 determines that message 166 is associated with the
previously opened media content delivery transaction TDR and some
or all of the information contained in message 166 is incorporated
into the TDR associated with that transaction. Examples of
parameters that may be included in the TDR include a media content
provider identifier, a media content recipient identifier, a media
content type identifier, a media content title, a time of media
content delivery, and a status indicator indicating whether or not
delivery of the media content was successful.
[0048] Correlation function 144 may determine that messages 132,
136, 162, and 166 are associated with the same media content
delivery transaction based on a similarity or other correlation
that is identified between functionally similar parameters in the
messages or other message attributes (e.g., timestamp
information).
[0049] The completed TDR is stored in data server 146 and may
subsequently be accessed by one or more media content delivery
audit/diagnostic applications, such as content delivery audit
application 148. Application 148 may access, analyze and otherwise
use information contained in the TDR to generate various audit and
diagnostic reports associated with media content delivery
transactions that occur in network 200.
[0050] The media content TDR or any information in the media
content TDR may be used to confirm revenue that should be paid to
the wireless network operator (e.g., from the media content
provider or from a clearinghouse) associated with the delivery of
media content to a wireless network subscriber. In another example,
information contained in the TDR may be used by the wireless
network operator to verify delivery of the media content to a
mobile communications device. For example, if media content
transactions appear on the wireless network subscriber's invoice
from the wireless network operator for use of the wireless
communications network, the media content TDR may be used by the
wireless network operator to generate entries on the invoice for
media content downloads and/or to handle disputes from wireless
network subscriber regarding the delivery of the media content.
[0051] Alternate embodiments of a RACDA system may be adapted to
monitor and analyze media content delivery transactions that employ
any number of other suitable communications protocols including IP,
HTTP, FTP, hypertext markup language (HTML), extensible markup
language (XML), and SIP. For example, a mobile subscriber may use a
SIP INFO or a SIP MESSAGE message to request a content download,
and a content provider may provide the requested content download
to the mobile subscriber using SIP INFO or SIP MESSAGE messages.
Regardless of the communications protocol or protocols involved in
a media content delivery transaction, a RACDA system is adapted to
provide message correlation and reporting functionality similar to
that previously described with respect to the SS7-based SMS
embodiments.
[0052] FIG. 5 illustrates the media content delivery portion of an
exemplary content delivery transaction monitoring scenario that
involves a RACDA system embodiment which includes both an external
communications link probe 124 and an IMF function 172 that is
co-located with signal transfer point/SS7-IP gateway (SG) 170. In
this example, an SMPP-based media content delivery message 160 is
received by STP/SG 170 from content provider 102. IMF function 172
generates a copy of some or all of SMPP message 160 and
communicates the message copy 162 to RACDA system 120. STP/SG 170
routes the original SMPP message 160 to SMSC 128. The SMSC
generates a related MAP-MT-FORWARD-SHORT-MESSAGE message 164, the
media content payload of which is ultimately delivered to the
requesting mobile subscriber 114. The MAP-MT-FORWARD-SHORT-MESSAGE
message 164 is detected/observed by probe 124 and a copy of the
message is generated. SMS message copy 166 is directed to RACDA
module 126. Once the SMPP and SMS messages are received by RACDA
module 126 correlation, analysis, and reporting of the information
contained in these messages proceeds in a manner similar to that
previously described herein with respect to the external
probe-based RACDA system embodiment.
[0053] According to another aspect of the subject matter described
herein, RACDA system 120 may be used to generate ratings associated
with the delivery of media content to wireless communications
subscribers. For example, correlation function 144 of RACDA system
120 may identify messages associated with the delivery of media
content to a plurality of wireless communications network
subscribers via a wireless communications network. RACDA system 120
may generate, based on the messages, at least one measure
indicative of an absolute or relative number of media content
delivery being made to the wireless subscribers. The measure may be
based on an attribute associated with the media content deliveries,
such as a content type or a content title associated with the
delivered content. For example, correlation function 144 of RACDA
system 120 may generate ratings that indicate the most popular
media content download during a time period. In another example,
correlation function 144 of RACDA system 120 may generate ratings
indicative of the total number of or most popular MP3 files that
are being downloaded during a time period.
[0054] It will be understood that various details of the invention
may be changed without departing from the scope of the invention.
Furthermore, the foregoing description is for the purpose of
illustration only, and not for the purpose of limitation, as the
invention is defined by the claims as set forth hereinafter.
* * * * *