JP4255899B2 - Server device - Google Patents

Description

  The present invention relates to a server device in a mobile communication system that can be connected to the Internet from a mobile terminal such as a mobile phone.

  In recent years, so-called third-generation mobile phone services are being introduced. In this third-generation mobile communication system, standardization is being promoted so that the same mobile terminal can be used in common all over the world. The WAP (Wireless Application Protocol) and MMS (Multimedia Messaging Service) standards are adopted as common specifications (Non-patent Document 1). Hereinafter, a mobile terminal compatible with WAP and MMS is simply referred to as a “WAP compatible terminal”.

  In such a WAP-compatible terminal, copyright management conforming to OMA DRM (OMA Digital Rights Management) version 1.0 is performed. OMA DRM is a digital rights management (DRM) specification established by the Open Mobile Alliance, which is a mobile phone application standardization organization (Non-Patent Document 2).

In OMA DRM ver1.0, there are 3 content delivery methods: (1) Forward Lock, (2) Combined Delivery, and (3) Separate Delivery. There are two specifications.
(1) Forward lock is a method that does not allow transfer of acquired content.
(2) Combined delivery is a delivery method that adds rights (usage rights settings) to forward-locked content and distributes it, limiting the number of times it can be used and the expiration date (for example, only once) Can be used, can be used for 5 days). As usage rights, the number of times the content is used (Count: how many times it can be used), the content availability period (Datetime: year / month / day / hour / minute / second, from when to when) and the content availability time (Interval: For example, it is possible to designate three types of rights (5 minutes after starting use).
(3) Separate Delivery consists of encrypted content (Media Object: media object, MO) and right + key (key for decryption) part (Rights Object: rights object, RO). ) Are distributed separately. Here, the media object is distributed by downloading from the web or the like, and the rights object is distributed by WAP push. On a mobile terminal, the contents can be used only when the media object and the rights object are arranged.
The content body portion of the media object (MO) is encrypted, and a content ID (CID: Contents ID) assigned for each content is assigned. The rights object (RO) is a “rights description file” handled by separate delivery, and is used to decrypt usage rights and key information (CEK: Content Encription Key, encrypted media object) for the corresponding content. Key information used in the A plurality of rights objects can be set for one media object.

  The usage right for the content in the rights object is defined by permission (permission) information that defines the content usage right and constraint (restriction) information that defines the scope of the content usage right. In OMA DRM ver1.0, content playback (Play), content display (Display), content execution (Execute) and content printing (Print) are defined as the permission information, and content information is defined as content information. The usage count (Count), content availability period (Datetime), and content availability time (Interval) are defined.

In addition to downloading from the web as described above, there are methods for acquiring content (media objects), such as a method for acquiring a memory card that stores the content, distribution by e-mail, etc. Since it cannot be used, Super Distribution can be realized.
The WAP Forum Ltd., "WAP 2.0 Technical White Paper", [on line], (2002.01.18), [Search April 28, 2004], Internet <URL: http://www.wapforum.org/ what / WAPWhite_Paper1.pdf> Open Mobile Alliance, "OMA Digital Rights Management version 1.0", [on line], [Search April 28, 2004], Internet <URL: http://www.openmobilealliance.org/tech/release.html>

As described above, in the separate delivery method, since the media object and the rights object are distributed by different distribution methods, it is difficult to manage content distribution as a whole.
In addition, when content is distributed to mobile terminals, there are wireless transmission paths in the path, and transmission errors are likely to occur, so media objects and rights objects can be transferred to mobile terminals using a separate delivery method. It is required to deliver without error.

  Accordingly, an object of the present invention is to provide a server device that can appropriately execute content delivery by separate delivery.

To achieve the above object, the server device of the present invention is a connected server apparatus to the gateway server which is provided between the IP network such as a mobile communication network and the Internet, and the media object from the mobile terminal upon receiving a request for the rights object, a first means for transmitting to said mobile terminal by creating a download descriptor for downloading media that object, from the mobile terminal downloaded the media object after receiving the download completion notice of the media object, receiving a rights object corresponding to the media object from a server that manages the rights object, wherein the second means for distributing to a mobile terminal, request for only the rights object from the mobile terminal When you receive Of the rights object received from a server that manages the rights object, a third means for delivering to the mobile terminal, the distribution processing to the mobile terminal of the media object and the rights object, (1) the start state, ( 2) download descriptor request reception status, (3) download completion notification reception status, (4) rights object distribution status, (5) rights object request reception status, and (6) charging notification transmission status . and a fourth means for managing the transition, the fourth means, upon receiving a request for the media object and the rights object from the mobile terminal (1) start state, (2) download descriptor Transition to the request reception state, (2) In the download descriptor request reception state, When the download descriptor is created by the first means and transmitted to the mobile terminal and a media object download completion notification is received from the mobile terminal, (3) a transition to the download completion notification reception state occurs, 3) In the download completion notification reception state, the corresponding right object is distributed to the mobile terminal by the second means, and (4) the state transitions to the right object distribution state. (4) In the right object distribution state, the movement When charging is required when receiving a rights object delivery result notification message from the terminal, (6) when charging is not required after the state transits to the charging notification transmission state and the charging notification is transmitted to the gateway server Directly controls (1) transition to the start state, and (1) transitions to the start state. When receiving a request for acquiring only the rights object from the terminal, (5) transition to the rights object request reception state, and (5) move the corresponding rights object by the third means in the rights object request reception state. (4) When a right object distribution state is received, and (4) when a right object distribution result notification message is received from the mobile terminal in the right object distribution state, charging is required. (6) after sending the billing notification charging transitions to the notification transmission state to the gateway server, if the charging is not required directly that is intended to control to transition to (1) start condition.

  According to the server device of the present invention, it is possible to manage the state transition in the distribution of the media object and the subsequent distribution of the rights object, so that unauthorized access and useless traffic can be prevented.

FIG. 1 is a block diagram showing an example of the overall configuration of a mobile communication system provided with a server device of the present invention. Here, in order to avoid complexity, the illustration of the configuration of the monitoring / maintenance system is omitted.
In this figure, 1 is a mobile terminal (UE: User Equipment) such as a mobile phone, 2 is a mobile communication network (3G mobile network) in which the mobile terminal 1 is accommodated, 3 is the mobile communication network 2 and the Internet, etc. Reference numeral 4 denotes a gateway message (GGSN: Gateway GPRS Support Node), and reference numeral 4 denotes a short message service center (SMSC) for delivering a short message to the mobile terminal 1.

5 is a WAP platform provided for accommodating WAP compatible terminals, terminating the WAP 2.0 protocol from the mobile terminal (UE) 1 and transferring it to the origin server using HTTP (HyperText Transfer Protocol) WAP gateway (WAP-GW: WAP-GW), and adjustment of WAP standard functions and extended functions by mobile operators by converting received requests into appropriate formats and sending them to the subsequent stage Server (WAP-GW / JSP) 6 having a proxy server (JSP: J-Phone Scheme Proxy), RADIUS accounting protocol from GGSN 3 is terminated, and RADIUS is used for session management and session log generation for each user. In addition to providing a server, WAP / MMS service subscribers use services such as web and email Information management server (R2M: RADIUS & Repository Manager) 7 that centrally manages user information necessary for mobile communication and information on mobile terminal capabilities, user setting information (Selfcare-) required for WAP service subscribers to use the web Profile) and profile database server (PDB: ProfileDB) 8 that manages and holds terminal information (UE-Profile), and push proxy gateway (PPG) that executes push services such as WAP push and mail notification delivery Each node such as Push Proxy Gateway) 9 is included.
Reference numeral 10 denotes a directory replica server (DRS) that holds a copy of the stored contents of a directory server that manages all subscriber information in an integrated manner.
The R2M7 is connected to the PDB8 and the DRS 10, and in response to a request from the WAP-GW / JSP6, user information (User-Profile), mobile terminal information (UE-Profile), and user agent profile information (UA-Profile) etc.

  A user agent in a mobile terminal corresponding to a mobile carrier's own standard sends out various HTTP extension headers uniquely defined by the mobile carrier, but in a WAP-compatible terminal, such an extension is used. It is not possible to send a header. Therefore, the WAP-GW / JSP6 uses the profile information stored in the R2M7 to supplement the mobile terminal information that is lacking in the extension header of the received HTTP request and forwards it to the subsequent node. ing. As a result, a service equivalent to a mobile terminal that complies with a mobile carrier's original standard can be provided to a WAP-compatible terminal.

  A web gateway (WGW) 11 is provided between the WAP-GW / JSP 6 and the Internet 26 and mediates a request from the mobile terminal 1 with the origin server. It also has processing functions related to state management and billing for information charges. As shown in the figure, the WGW 11 includes a proxy server (H-MAWG: H-Mobile Active Web Gateway) 12 that performs processing accompanied by a special value-added service such as charge collection for paid content access, customer information management and billing. A CDR (Charging Data Record) collection server (CDRC: CDR Collector) 13 connected to a system that performs checkout processing, a server (AS: Authentication Server) 14 that performs user authentication processing, and a general web caching proxy function A proxy server (L-MAWG) 15 to be provided is included.

  Reference numeral 16 denotes a DRM platform for providing a DRM usage service, which includes a TMS (Transaction Management Server) server 17 and a DRM server 20 node group. As shown in the figure, a TMS (Transaction Management Server) server 17 that manages DRM content transactions manages a content distribution control server (TMS-C: Transaction Management Server-Control) 18 that controls requests from the mobile terminal 1. And a state transition management server (TMS-S: Transaction Management Server-Status) 19 that performs state management in communication with the mobile terminal 1, and the DRM server 20 includes a rights object based on the registered rights information. A license server (LS) 21 that generates and manages (RO), and a packaging server (PS) that controls registration of content information and registration of accompanying rights information in cooperation with a packaging tool described later. Access from Packaging Server) 22 and Content Provider (CP) 27 Information received from a server (CPAS: CP Authentication Server) 23 that mediates communication with the DRM platform 16 side, and content provider (CP) 27 such as content information and rights information, and mobile communication providers A database server (DB: Database Server) 24 that holds service definition information and the like to be created is included. The packaging server (PS) 22 is connected to a database synchronizer (DBS: DB-Synchronizer) 25 for synchronizing generations in the web service, and manages the distribution of provider information and service information in the DBS 25. A node (SPM: Service and Provider Manager) can be used.

A proxy server (L-MAWG) 15 in the WGW 11 is connected to the Internet 26, and a content provider (CP: Content Provider) 27 that provides content in response to a request from a user is connected to the Internet 26. Yes.
The content provider 27 is provided with an origin server 28 in which a resource designated by the mobile terminal 1 or the like exists or is generated, and a series of contents to be converted into a DRM compatible format. A packaging tool 29 for performing the above process (packaging) is distributed from a mobile communication carrier or the like.
The packaging tool 29 is connected to the CPAS 23 in the DRM server 20 via the Internet 26 and a firewall (F / W) 30, and the DRM server 20 installed by a mobile communication carrier. The content can be packaged in cooperation with the server group.

That is, the packaging tool 29 receives the raw contents (Raw Contents), the URI (Rights Issuer URI) of the download destination of the rights information, and the rights information as inputs, and the license server LS21 and the packaging server PS22 in the DRM platform 16. In cooperation with the above, a DCF (DRM Contents Format) file, which is a DRM content format including encrypted contents, and a license ID (LID) thereof are created. At this time, information such as key information, content contents, and MIME type is stored in the database server DB 24 in the DRM server 20.
Here, the license ID (LID) is an ID for designating a rights object (RO) linked to the media object (MO). By designating this ID, it is possible to distribute the corresponding rights object (RO).

The media object (MO) is downloaded by a download method (OMA download) defined by OMA. In this system, it is possible to notify what content is to be acquired in advance by acquiring a download descriptor (DD) before downloading the content. In addition, after the download is completed, a download completion notification (Install Notify) can be transmitted to an arbitrary URL. Here, the download descriptor includes metadata (content name, size, type, version, etc.) regarding the content (MO), a URL (ObjectURI) indicating the location of the content, and a URL of a notification destination of a download completion notification. (InstallNotifyURI) is a file that describes.
On the other hand, the rights object (RO) is distributed from the license server LS21 to the mobile terminal 1 via the PPG 9 by a WAP push. In other words, the rights object cannot be acquired from the license server installed by the mobile communication carrier unless it is based on the WAP push.

In the present invention, the TMS-S 19 in the DRM platform 16 manages the state transition of communication with the mobile terminal 1 to cope with unauthorized access and the like.
When content is distributed to mobile terminals by a separate delivery method, both media object (MO) and rights object (RO) are delivered, and only rights object (RO) is delivered. (1) MO + RO (free of charge) distribution, (2) MO + RO (rights charge (pay-as-you-go)) distribution, (3) MO + RO (periodic charge) distribution, (4) RO ( There are six cases of (free) delivery, (5) RO (Rights Billing) delivery, and (6) RO (Period Billing) delivery.
In TMS-S19, the transition of the state of communication with the mobile terminal 1 in each of these six cases is managed.

FIG. 2 is a state transition diagram when content is delivered to the mobile terminal 1 by the separate delivery method.
As shown in this figure, in the present invention, the process of distributing content to the mobile terminal 1 includes: [1] Start (no communication) state, [2] Download descriptor (DD) request: Download Descriptor Request) reception state [3] Download completion notification (Install Notify) reception state, [4] Rights object (RO) delivery (Rights Object Deliver) state, [5] Rights object (RO) request (Rights Object Request) reception state, and [ 6] Management is performed in six states of a charging notification transmission state.
As will be described later, when both the RO and MO of (1) to (3) are distributed, [1] → [2] → [3] → [4] → ([6]) → [1 ], And only the ROs (4) to (6) above are distributed, the transition is [1] → [5] → [4] → ([6]) → [1]. Here, in the case of the rights billing of the above (2) and (5), it goes through the state [6] as [4] → [6] → [1].
Hereinafter, the sequence and state transition in each case of (1) to (6) described above will be described in detail. In any case, the initial state is [1] start (no communication) state.

(1) MO + RO (free)
FIG. 3 is a diagram showing a sequence in the case of (1) distribution of MO + RO (free), that is, a case where both media objects (MO) and rights objects (RO) of free content are distributed to the mobile terminal 1. 4 is a diagram showing an example of the screen display of the mobile terminal 1 at that time.
In FIG. 3, in the initial state, [1] is a start (no communication) state.
Here, when the mobile terminal 1, which is a WAP compatible terminal, is connected to the Internet according to the WAP sequence, and the user requests “(1) Contents Select” to download content from the content provider 27, the content provider 27 "(2) Content selection screen" is sent from the mobile terminal 1 to the mobile terminal 1, and the content selection screen is displayed on the screen of the mobile terminal 1 ((A) of FIG. 4).
As shown in the description example of FIG. 4, in the content described on the content selection screen, the service ID (sid), the LID (license ID) designating the rights object, and the location where the media object is actually placed Ol (object link) to indicate (http://www.cp.com/melodyB.dcf in this example), a notification destination (CPNotify) to notify that the rights object was successfully delivered (in this example http A link to the TMS server 17 to which various parameters such as “: //www.cp.com/notify” are added is provided.

When the user selects a desired content on the content selection screen, an HTTP request “(3) DD Request” including a download descriptor (DD) acquisition request for downloading the media object (MO) of the content is transmitted. Is done.
The “(3) DD Request” is relayed by the WAP-GW / JSP 6 and the WGW 11 (H-MAWG 12) and transferred to the TMS-C 18 of the DRM platform 16. As a result, a transition is made from the [1] start (no communication) state to the [2] DD request reception state (FIG. 2).
Here, the WAP-GW / JSP 6 that has received “(3) DD Request” from the mobile terminal 1 uses the MSISDN or IMSI of the mobile terminal 1 as a key, and the model information and performance of the mobile terminal from the R2M7. Mobile terminal information (UE-Profile) consisting of information indicating, and profile information (UA-Profile) of a user agent such as a web browser. At this time, the WAP-GW / JSP 6 also includes the type of secure clock (time information stored in the mobile terminal 1) as extension information for DRM, and the association information of the MIME type and permission to be changed. get. Then, the WAP-GW / JSP 6 adds the acquired mobile terminal information (UE-Profile), user agent profile information (UA-Profile), and the DRM extension information to the HTTP header of the HTTP request, and adds the WGW 11 ( To the TMS server 17 of the DRM platform 16 via the H-MAWG 12).

The TMS server 17 that has received this HTTP request creates a download descriptor for downloading the requested content, and transmits it as an HTTP response to the mobile terminal 1. At this time, the capability of the mobile terminal 1 is checked, and a download descriptor corresponding to the capability is created.
That is, the TMS server 17 of the DRM platform 16 checks the capability of the mobile terminal 1 that has sent the HTTP request based on the DRM extension information included in the HTTP header, and moves the mobile terminal 1 based on the HTTP request. A download descriptor suitable for the terminal is created, and “(6) DD Response” including the download descriptor is returned to the WGW 11.
As shown in FIG. 3, in the download descriptor, the object link (ol) described above is described as a parameter (ObjectURI) indicating the actual location of the content, and the notification destination (InstallNotifyURI) of the content delivery completion notification is described. , The URI of the TMS server 17 (URI for TMS notification) and the parameter “CPNotify” described above are described.
The “(4) DD Response” including the download descriptor created as described above by the TMS server 17 is transferred to the mobile terminal 1 via the WGW 11 and the WAP-GW / JSP6.

  On the display unit of the mobile terminal 1 that has received “(4) DD Response”, a content confirmation screen as shown in FIG. 4B is displayed. Here, when the user operates the “OK” button to download the content, the content (media object) with respect to the object URI in the download descriptor included in the “(4) DD Response”. Acquisition request “(5) MO Request” is sent out, and the screen shown in FIG. 4C is displayed. When the user operates the “NG” button, the screen shown in FIG. 4D is displayed, and the process is stopped.

The “(5) MO Request” is transferred to the content provider 27 that stores the content via the DRM platform 16 and the WGW 11.
The content provider 27 that has received the request relays “(6) MO Response” including the requested content (media object) to the mobile terminal via the WGW 11, the DRM platform 16, and the WAP-GW / JSP 6. Forward to 1. When the number of downloads is limited, etc., “(6) MO Response” is returned after checking the number of downloads (Constraint Check).
In this process, when an error is detected in each server, the error is displayed as shown in FIG. 4E, and the download is stopped. When the MO download fails, an error display shown in FIG. 4F is displayed.
When all media objects are received by the mobile terminal 1 without detecting an error, the mobile terminal 1 sends a download completion notification “(7) Install Notify” to the DRM platform via the WAP-GW / JSP6. 16 TMS servers 17 (notification destination specified by the parameter “InstallNotifyURI”).

When the TMS server 17 receives the “(7) Install Notify”, the state transitions to [3] download completion notification reception state. The TMS server 17 then returns a response “(8) Install Notify Ack” and notifies the license server (LS) 21 to receive the corresponding rights object (RO).
Next, the TMS server 17 transmits the rights object to the PPG 9. Thereby, the state transits to [4] RO distribution state.
Receiving the rights object, the PPG 9 delivers the rights object to the mobile terminal 1 by WAP push ((9) RO Delivery).

The mobile terminal 1 displays a download completion screen ((G) in FIG. 4) when the push distribution of the rights object (RO) performed following the download of the media object (MO) is completed. When the execution of content is instructed by the user, the content is executed ((H) in FIG. 4). When “NG” is selected on the screen shown in FIG. 4G, the screen returns to the content selection screen shown in FIG.
Further, when receiving the rights object, the mobile terminal 1 transmits “(10) Delivery Receipt” for notifying the delivery status to the PPG 9. When the PPG 9 receives the “(10) Delivery Receipt”, the PPG 9 creates a delivery result notification message “Delivery Report” according to the content and transmits it to the DRM platform 16.
Upon receiving the delivery result notification message “Delivery Report”, the DRM platform 16 changes the state to [1] start (no communication) and creates a log (Reporting). Then, whether or not the rights object is successfully delivered is determined from the delivery result notification. If the delivery is successful, the content delivery completion notice “(” is sent to the URI specified by the parameter “CP Notify”. 11) Send “CP Notify”. In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. Thereby, a content provider or the like can acquire information indicating that the content has been distributed in real time.

(2) MO + RO (Rights charge)
FIG. 5 is a diagram showing a sequence when the user of the mobile terminal 1 downloads a media object (MO) and a rights object (RO) of paid content (rights charging) in a series of flows. It is a figure which shows an example of the screen display of the mobile terminal 1 at that time. In this case, the compensation for the content is billed when the corresponding rights object is distributed (rights billing (pay-as-you-go billing)). Detailed description of the same parts as those in FIGS. 3 and 4 will be omitted.
As in the case described above, when the user of the mobile terminal 1 requests “(1) Contents Select” in order to purchase content from the content provider 27, the content provider 27 sends a “(2) content selection screen” to the mobile terminal 1. Is sent to the mobile terminal 1 and a content selection screen ((A) in FIG. 6) is displayed. As shown in the description example of FIG. 6, the service ID (sid), the LID (license ID) designating the rights object, and the media object are actually placed in the content described on the content selection screen. Ol (object link) indicating the location (http://www.cp.com/melodyB.dcf in this example), notification destination (CPNotify) to notify that the rights object was successfully delivered (in this example, A link to a destination (WGW 11) of a CONFON request to which various parameters such as http://www.cp.com/notify are added is provided.
When the user performs an operation to instruct the purchase of the selected paid content, “(3) CONFON request” is sent to the WGW 11 (FIG. 5). When the WGW 11 receives the “(3) CONFON request”, the WGW 11 interprets the type, and transmits the “(4) billing authentication screen” of the corresponding paid content to the mobile terminal 1 via the WAP-GW / JSP 6. To do. At this time, WAP-GW / JSP6 encrypts and transmits the parameter including the time information at that time.

When the user views the billing authentication screen (FIG. 6B), inputs a password and operates the “OK” button, a download descriptor (DD) for downloading the media object (MO) of the content An HTTP request “(5) DD Request” including an acquisition request is sent.
The “(5) DD Request” is relayed by the WAP-GW / JSP6 and WGW11 (H-MAWG12) and transferred to the TMS-C18 of the DRM platform 16 in the same manner as in FIG. From the initial state of “1] Start (no communication)”, the state transits to [2] DD request reception state (FIG. 2).

  At this time, in WAP-GW / JSP6, it is checked whether or not it is within a predetermined time since the transmission of the “(4) Billing authentication screen”. The request is invalidated, and an error screen as shown in FIG. 6D is displayed on the mobile terminal 1 to prompt the user to send the request again.

  [2] In the DD request reception state, the TMS server 17 creates a download descriptor (Download Descriptor) suitable for the mobile terminal in the same manner as described above, and includes “(6) DD including the download descriptor. Response "is transmitted to the mobile terminal 1 via the WGW 11 and the WAP-GW / JSP6.

Similarly to the above, when the user operates the “OK” button to download the content on the content confirmation screen (FIG. 6C), “(7) MO Request” is transmitted, “(8) MO Response” including the requested content (media object) is transmitted from the provider 27 to the mobile terminal 1 through the WGW 11, the DRM platform 16, and the WAP-GW / JSP 6.
When all the media objects are received without detecting an error, the mobile terminal 1 sends a download completion notification “(9) Install Notify” via the WAP-GW / JSP 6 to the TMS server 17 of the DRM platform 16. (Notification destination specified by the parameter “InstallNotifyURI”).

When the “(9) Install Notify” is received by the TMS server 17, the state changes from [2] DD request reception state to [3] download completion notification reception state (FIG. 2), and the response “(10) Install Notify Ack”. return it. Then, as described above, the corresponding rights object (RO) is received from the license server (LS) 21 and the rights object is transmitted to the PPG 9. As a result, the [3] download completion notification reception state transits to the [4] RO distribution state (FIG. 2).
The PPG 9 delivers the rights object to the mobile terminal 1 by WAP push ((11) RO Delivery).

Similarly to the above, when the push distribution of the rights object (RO) performed following the download of the media object (MO) is completed, the mobile terminal 1 displays a download completion screen ((I) in FIG. 6). . When the execution of content is instructed by the user, the content is executed ((J) in FIG. 6).
Further, when receiving the rights object, the mobile terminal 1 transmits “(12) Delivery Receipt” notifying the delivery status to the PPG 9. When the PPG 9 receives the “(12) Delivery Receipt”, the PPG 9 creates a delivery result notification message “Delivery Report” corresponding to the content and transmits it to the DRM platform 16.
Upon receiving the delivery result notification message “Delivery Report”, the DRM platform 16 transitions from [4] RO delivery state to [6] charging notice transmission state (FIG. 2).
In this [6] charging notification transmission state, the DRM platform 16 creates a log (Reporting), determines whether or not the rights object has been successfully distributed from the distribution result notification, and charges only when the distribution is successful. The billing notification “(13) Charging Notify” including the parameters for the server is created and transmitted to the WGW 11. Then, [1] transition to a start (no communication) state.

The WGW 11 that has received the billing notification performs billing processing based on the billing parameter included in the notification (CDR Create). In this way, the billing process is not performed before the distribution of the rights object is completed.
If the parameter CP Notify is set, a content delivery completion notification “(14) CP Notify” is transmitted to the URI specified by the parameter (successful distribution of the rights object). If so). In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. Thereby, a content provider or the like can acquire information indicating that the content has been distributed in real time.

(3) MO + RO (period charge)
Next, FIG. 7 shows a sequence in the case where paid content (media object and rights object) is distributed to a user who subscribes to a period charge (fixed charge) service that can be used any number of times within a certain period. A screen display example will be described with reference to FIG. It is assumed that the user who uses this period billing service has already contracted with the content provider 27 and the like, and the service registration information is stored in the WGW 11. Detailed descriptions of the same parts as those in FIGS. 3 to 6 are omitted.

Similarly to the above-described case, when the user of the mobile terminal 1 requests “(1) Contents Select” to purchase content from the content provider 27 with which the user is contracted, the content provider 27 sends “(2 ) Content selection screen ”is sent, and the content selection screen ((A) of FIG. 8) is displayed on the mobile terminal 1. As shown in the description example of FIG. 8, the content described on the content selection screen is linked to the TMS server 17 to which various parameters similar to those in FIG. 4 are added.
When the user of the mobile terminal 1 selects the content to be purchased on the content selection screen, “(3) DD Request” is transmitted and transferred to the TMS-C 18 of the DRM platform 16 via the WAP-GW / JSP 6 and the WGW 11. . Thereby, [2] the DD request reception state is entered (FIG. 2).
In the [2] DD request reception state, the DRM platform 16 checks the content provision state by the service based on the service ID (sid) included in the header of the “(3) DD Request”. In the case of period billing, “(4) Service registration status inquiry” is sent to the WGW 11 to inquire whether or not the user is registered as a user of the service.
The WGW 11 that has received the inquiry refers to the registration status of the service and returns “(5) Service registration status response” to the DRM platform 16.
As a result, when the user is registered, the corresponding download descriptor is created in the same manner as described above and transmitted to the mobile terminal 1 “(6) DD Response”.
As described above, even in the separate delivery method, the registration state of the user is confirmed by inquiring the registration state from the DRM platform 16 to the WGW 11 that manages the registered user in the mobile communication carrier's original system. I have to.

Then, as described above, “(7) MO Request” is transmitted from the mobile terminal 1, and the corresponding media object (MO) “(8) MO Response” is distributed from the content provider 27. When the number of downloads is limited, “(8) MO Response” is returned after checking the number of downloads (Constraint Check).
When the reception of the MO is completed, a download completion notification “(9) Install Notify” is transmitted from the mobile terminal 1 to the TMS server 17.
Upon receiving this download completion notification “(9) Install Notify”, the TMS server 17 changes to [3] download completion notification reception state, returns “(10) Install Notify Ack”, and corresponding rights object (RO ) To the PPG 9. Thereby, it changes to [4] RO distribution state.
Similarly to the above, when receiving the delivery result notification message “Delivery Report” from the PPG 9 that has received “(12) Delivery Receipt” for notifying the delivery status from the mobile terminal 1, the DRM platform 16 [1] Start ( Transition to the (No communication) state. Then, the DRM platform 16 transmits a content delivery completion notification “(13) CP Notify” to the notification destination specified by the parameter “CP NOtify”.

Each case described above is a case where a media object (MO) and a rights object (RO) are distributed in a series of processes. Next, a case where only the content rights object is distributed will be described. In these cases, the media object is distributed in advance to the user's mobile terminal 1 by various means.
(4) RO (free)
FIG. 9 is a diagram illustrating a sequence when only a free rights object is distributed, and FIG. 10 is a diagram illustrating an example of a screen display in the mobile terminal 1 at that time.
When the user selects content for which a rights object is to be acquired on the target content selection screen ((A) of FIG. 10), “(1) Rights Issuer URI Request” is transmitted to the content provider 27. The content provider 27 checks the number of downloads (Constraint Check) as necessary, and transmits “(2) content selection screen” to the mobile terminal 1 as described above.
FIG. 10B is a diagram illustrating an example of a content selection screen. As illustrated, the content includes a service ID (sid), a LID (license ID) designating a rights object, and a rights object normally. A link to the TMS server 17 to which a parameter such as a notification destination (CPNotify) for notification of distribution (in this example, http://www.cp.com/notify) is added.

When the user selects content on this screen, a distribution request “(3) Rights Object Request” of the rights object is transmitted to the TMS server 17 of the DRM platform 16 via the WAP-GW / JSP6 and WGW11.
Upon receiving this “(3) Rights Object Request” request, the TMS server 17 (TMS-S19) transits from the [1] start (no communication) state to the [5] rights object (RO) request reception state, The service ID included in the distribution request is checked and the result information “(4) Status Response” is transmitted to the mobile terminal 1.
When the display corresponding to the “(4) Status Response” is displayed on the display unit of the mobile terminal 1 and an error is detected or the “(4) Status Response” cannot be received even after a predetermined time has elapsed. 10D is displayed as an error, and when no error occurs, a screen as shown in FIG. 10C is displayed.
When there is no problem as a result of the check, the DRM platform 16 (TMS server 17) receives the rights object requested from the license server (LS) 21 and sends it to the PPG 9 for distribution to the mobile terminal 1. And [5] RO request reception state to [4] Rights object (RO) distribution state.
As a result, the rights object is delivered from the PPG 9 to the mobile terminal 1 by the WAP push “(5) RO Delivery”.

When an error occurs during distribution of the rights object, a screen as shown in FIG. 10E is displayed. When there is no error and the distribution of the rights object is completed, a screen indicating the completion of distribution ((F) in FIG. 10) is displayed on the display unit of the mobile terminal 1, and when the user instructs execution of the content, the content is executed. ((G) in FIG. 10). When “NG” is selected on the screen shown in FIG. 10F, the screen returns to the content selection screen shown in FIG.
When the mobile terminal 1 receives the requested rights object, the mobile terminal 1 transmits “(6) Delivery Receipt” for notifying the delivery status to the PPG 9, and the PPG 9 sends a delivery result notification message “Delivery Report” according to the content of the notification. Is generated and transmitted to the DRM platform 16 (TMS server 17).
When the DRM platform 16 receives the delivery result notification message “Delivery Report”, [1] transitions to the start (no communication) state, creates a log (Reporting), and successfully delivers the rights object Transmits a content delivery completion notification “(7) CP Notify” to the URI specified by the parameter “CP Notify”. In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. Thereby, a content provider or the like can acquire information indicating that the content has been distributed in real time.

(5) RO (Rights charge)
Next, a case will be described in which only a rights object of paid content (rights charging) is distributed.
FIG. 11 is a diagram showing a sequence when only the rights object is distributed, and FIG. 12 is a diagram showing an example of a screen display in the mobile terminal 1 at that time.
When the user selects content on the target content selection screen ((A) of FIG. 12), “(1) Rights Issuer URI Request” is transmitted to the content provider 27, and in response to this, the content provider 27 "(2) Content selection screen" ((B) of FIG. 12) is transmitted to the mobile terminal 1. As shown in the description example of FIG. 12, the selection elements in the content selection screen include a service ID (sid), an LID (license ID) designating the rights object, and a rights object as in the case of FIG. A link to the destination (WGW11) of the CONFON request to which various parameters such as a notification destination (CPNotify) (in this example, http://www.cp.com/notify) to notify that the delivery was successful is added It is stretched.
When the user selects purchase on this screen, “(3) CONFON request” is transmitted from the mobile terminal 1 and the corresponding “(4) billing authentication screen” is displayed from the mobile terminal 1 as in the case of FIG. Sent to. At this time, as described above, the parameters are encrypted and transmitted by the WAP-GW / JSP6.

When the user inputs a password and operates the “OK” button on the billing authentication screen shown in FIG. 12C, a rights object distribution request “(5) OK (Rights Object Request)” is displayed in the WAP-GW / It is transmitted to the TMS server 17 of the DRM platform 16 via the JSP 6 and the WGW 11. At this time, the WAP-GW / JSP 6 performs a time limit check in the same manner as described above.
When the TMS server 17 (TMS-S19) of the DRM platform 16 receives this “(5) OK (Rights Object Request)” request, [5] Rights object (RO) request from [1] start (no communication) state. The state transits to the reception state, the charge check is performed, and the result information “(6) Status Response” is transmitted to the mobile terminal 1.
The display corresponding to the “(6) Status Response” is displayed on the display unit of the mobile terminal 1. (D) of FIG. 12 shows an example of a screen when there is no error, and (E) shows an example of a screen when an error occurs.
When there is no problem as a result of the billing check, the TMS server 17 of the DRM platform 16 receives the rights object requested from the license server (LS) 21 and sends it to the PPG 9 for distribution to the mobile terminal 1. Send. Then, a transition is made from the [5] rights object (RO) request reception state to the [4] rights object (RO) delivery state.
The rights object is “(7) RO Delivery” delivered from the PPG 9 to the mobile terminal 1.

FIG. 12F shows a display screen when an error occurs during distribution of a rights object. When the distribution of the rights object is completed, a screen indicating the completion of the distribution ((G) in FIG. 12) is displayed on the display unit of the mobile terminal 1, and when the user instructs the execution of the content, the content is executed ( (H) of FIG.
Similarly to the above, when the mobile terminal 1 receives the requested rights object, the mobile terminal 1 sends “(8) Delivery Receipt” notifying the delivery status to the PPG 9, and the PPG 9 responds to the contents of the delivery status notification. A delivery result notification message “Delivery Report” is created and transmitted to the DRM platform 16 (TMS server 17).
When the DRM platform 16 receives the delivery result notification message “Delivery Report”, it changes to [6] charging notification transmission state, creates a log (Reporting), and only when the rights object has been successfully delivered. A charging notice “(9) Charging Notify” including the charging parameters is created and transmitted to the WGW 11. Then, the DRM platform 16 transitions to a [1] start (no communication) state.
The WGW 11 that has received the billing notification performs billing processing based on the billing parameter included in the notification (CDR Create).
If the parameter CP Notify is set, a content delivery completion notification “(10) CP Notify” is transmitted to the URI specified by the parameter (successful distribution of the rights object). If so). In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. Thereby, a content provider or the like can acquire information indicating that the content has been distributed in real time.

(6) RO (periodic charge)
Next, a case where paid content (right object) is distributed to a user who subscribes to the period billing service will be described with reference to FIG. 13 showing a sequence and FIG. 14 showing a screen display example. As in the case of FIGS. 7 and 8, the service registration information is assumed to be stored in the WGW 11.

Similarly to the case of FIG. 9 or FIG. 11, when the user of the mobile terminal 1 selects content on the target content selection screen ((A) of FIG. 14), the content provider 27 is notified with “(1) Rights”. Issuer URI Request "is sent. The content provider 27 checks the number of downloads (Constraints Check) as necessary, and then returns the “(2) content selection screen” ((B) in FIG. 14) to the mobile terminal 1. As shown in the description example of FIG. 14, the selection elements in this content selection screen include a service ID (sid), a LID (license ID) that designates a rights object, and a notification that notifies that the rights object has been successfully distributed. A link to the TMS server 17 to which a parameter such as “CPNotify” (in this example, http://www.cp.com/notify) is added is provided.
When the user makes a selection on this screen, “(3) Rights Object Request” requesting the rights object is sent to the DRM platform 16.
Upon receiving this “(3) Rights Object Request”, the TMS server 17 (TMS-S19) of the DRM platform 16 changes from [1] start (no communication) state to [5] rights object (RO) request reception state. As in the case of FIG. 7, the state of content provision by the service is checked, and “(4) Service registration status inquiry” is transmitted to the WGW 11. Then, in response to “(5) Service registration status response” from WGW 11, “(6) Status Response” is returned to mobile terminal 1.
When the service may be provided, the rights object is received from the LS 21 and transmitted to the PPG 9, and a transition to the [4] rights object (RO) distribution state is made.
As a result, the rights object is distributed from the PPG 9 to the mobile terminal 1 by the WAP push, and “(8) Delivery Receipt” for notifying the delivery status is sent from the mobile terminal 1 to the PPG 9. The PPG 9 creates a delivery result notification message “Delivery Repot” according to the content of the notification and transmits it to the DRM platform 16.
When receiving the delivery result notification message “Delivery Report”, the TMS server 17 of the DRM platform 16 transitions from the [4] rights object delivery state to the [1] start (no communication) state. Then, in the same manner as described above, a log is created and “(9) CP Notify” is transmitted.

  As described above in detail, in the present invention, the TMS server 17 (TMS-S19) manages the transition of the state of communication with the mobile terminal 1 to prevent an unauthorized transition from occurring. ing. If an error (including a timer expired) occurs in each state, [1] return to the start (no communication) state.

It is a block diagram which shows the whole structure of the system by which the server apparatus of this invention is provided. It is a state transition diagram of the process which distributes a content to a mobile terminal by a separate delivery system. It is a figure which shows a sequence when delivering the media object and rights object of free content in a series of sequences. It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG. It is a figure which shows the sequence at the time of delivering the media object and rights object of paid content (rights charge) in a series of sequences. It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG. It is a figure which shows the sequence at the time of delivering the media object and rights object of paid content (period charge) in a series of sequences. It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG. It is a figure which shows the sequence when delivering the rights object of free content. It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG. It is a figure which shows the sequence when delivering the rights object of paid content (rights charge). It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG. It is a figure which shows the sequence when delivering the rights object of paid content (period charge). It is a figure which shows the example of a screen display of the mobile terminal in the case of FIG.

Explanation of symbols

  1: mobile terminal, 2: mobile communication network, 3: GGSN, 4: SMSC, 5: WAP platform, 6: WAP gateway and proxy server (WAP-GW / JSP), 7: information management server (R2M), 8 : Profile database server (PDB), 9: Push proxy gateway (PPG), 10: Directory replica server (DRS), 11: Web gateway (WGW), 12: Proxy server (H-MAWG) , 13: CDR collection server, 14: server (AS), 15: proxy server (L-MAWG), 16: DRM platform, 17: TMS server, 18: content distribution control server (TMS-C), 19: state transition Management server (TMS-S), 20: DRM server, 21: License server (LS), 22: Packaging server (PS), 23: Server (CPAS), 24: Database server (DB), 25: Database synchronizer (DBS), 26: Internet, 27: Content provider, 28: Origin Server, 29: Packaging tool, 30: Firewall

Claims (1)

A server device connected to a gateway server provided between a mobile communication network and an IP network such as the Internet,
When the mobile terminal has received a request for the media object and the rights object, a first means for transmitting to said mobile terminal by creating a download descriptor for downloading media that object,
Second means for receiving a rights object corresponding to the media object from the server managing the rights object after receiving a media object download completion notification from the mobile terminal that downloaded the media object, and delivering the rights object to the mobile terminal; ,
A third means for receiving a rights object from a server that manages the rights object when receiving a request for obtaining only the rights object from the mobile terminal, and delivering the rights object to the mobile terminal;
Distribution processing of the media object and the rights object to the mobile terminal includes (1) start state, (2) download descriptor request reception state, (3) download completion notification reception state, (4) rights object distribution state, (5) the rights object request reception state, and a fourth means for managing the transition of the six states of (6) charging notification transmission state,
The fourth means includes
(1) When receiving the acquisition request of the media object and rights object from the mobile terminal in the start state, (2) transition to the download descriptor request reception state,
( 2) When the download descriptor request is received, the download descriptor is created by the first means and transmitted to the mobile terminal, and when a media object download completion notification is received from the mobile terminal, (3 ) Transition to download completion notification reception state,
(3) In the download completion notification reception state, the corresponding rights object is distributed to the mobile terminal by the second means, and (4) the rights object distribution state is changed.
(4) When a rights object delivery result notification message is received from the mobile terminal in the rights object delivery state, if charging is required, (6) transition to the billing notification transmission state and notify the gateway server of the billing If you do not need to charge after sending, directly (1) control to transition to the start state,
In addition, (1) when the acquisition request for only the rights object is received from the mobile terminal in the start state, (5) transition to the rights object request reception state,
(5) In the rights object request reception state, the corresponding rights object is delivered to the mobile terminal by the third means, and (4) the rights object delivery state is transitioned.
(4) When a rights object delivery result notification message is received from the mobile terminal in the rights object delivery state, if charging is required, (6) transition to the billing notification transmission state and notify the gateway server of the billing (1) A server device that directly controls to make a transition to a start state when charging is not required after sending the message .

Images