JP4330506B2 - 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. 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, content acquisition methods include downloading from the web, acquiring a memory card that stores the content, delivery by e-mail, etc., but since it cannot be used only with content, it is super-distributed. (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>

When the above-described third generation service is started, there will be both a mobile terminal that has been provided in the past and that is compatible with each mobile carrier's own protocol and the above-described WAP-compatible terminal.
Each mobile carrier provided a unique service based on its own protocol. From now on, not only mobile terminals that support each mobile carrier's own standard but also WAP compatible terminals. However, it is required to provide services similar to those provided for mobile terminals that have been conventionally compatible with the standards unique to each mobile communication carrier.
For example, in the conventional service, the content is downloaded after the download of the content is completed. However, when a content delivery method based on separate delivery is adopted in a WAP compatible terminal that is protected by OMA DRM-compliant copyright. In addition, it is required to perform a reasonable billing process such that the billing process is performed after the distribution of the content is completed and the content can be used.

  Therefore, an object of the present invention is to provide a server device capable of performing a reasonable charging process when content distribution is performed by separate delivery.

In order to achieve the above object, a server device of the present invention is a server device provided between a mobile communication network and an IP network such as the Internet, and connected to a gateway server that performs processing related to billing. A plurality of gateway servers are provided corresponding to each region, and the host header of the HTTP request from the mobile terminal indicates the region to which the mobile terminal belongs by the server device that terminates the WAP protocol from the mobile terminal. A domain name is supplemented, and when there is a request for acquisition of a rights object in separate delivery from the mobile terminal, means for delivering the rights object to the mobile terminal, and the movement of the rights object When the delivery to the terminal is completed, the HTTP request is sent to the host. Using a domain name that is complemented Da, and has a means for transmitting a charging notifications to the gateway server areas belonging of the mobile terminal.

According to the server device of the present invention, after the delivery of the rights object to the mobile terminal is completed, the billing process for the rights object is performed. Therefore, even in the case of DRM separate delivery, a reasonable charge can be made. It can be carried out.
Further, even when a plurality of web gateways are provided for each region, billing notification can be made to the corresponding web gateway.

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.

  Although only one WGW 11 is shown in FIG. 1, in reality, a plurality of WGWs 11 are provided in the system corresponding to each region, and a movement corresponding to a standard unique to a mobile communication carrier is provided. The terminal 1 is connected to the Internet via the WGW 11 in the region to which the terminal 1 belongs. In the case of a WAP compatible terminal, the WAP-GW / JSP6 belongs to the user from the R2M7 based on the MSISDN (Mobile Station ISDN number) or IMSI (International Mobile Subscriber Identity) of the WAP compatible terminal. A domain name indicating a region is acquired, and the acquired domain name is complemented to the host header of the HTTP request from the WAP-compatible terminal. Thereby, the HTTP request from the WAP-compatible terminal is routed to the WGW 11 corresponding to the area to which the user belongs.

  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 method, it is possible to notify what content is 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.

  The operation of the system configured as described above will be described taking as an example a case where the user of the mobile terminal 1 downloads paid content from the origin server 28 of the content provider 27. In the following description, it is assumed that the mobile terminal 1 is a WAP compatible terminal.

FIG. 2 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 billing (pay-as-you-go billing)) in a series of flows. FIG. 3 is a diagram showing an example of the screen display of the mobile terminal 1 at that time.
In FIG. 2, 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 select the content to be purchased from the content provider 27, “(2) Content selection screen” is sent from the content provider 27 to the mobile terminal 1, and the content selection screen is displayed on the screen of the mobile terminal 1 ((A) in FIG. 3).
As shown in the description example of FIG. 3, 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 views the content selection screen and performs an operation to instruct purchase of paid content, a “(3) CONFON request” is sent to the WGW 11. When the WGW 11 receives the CONFON request, the WGW 11 interprets the type and transmits the “(4) billing authentication screen” of the corresponding pay content to the mobile terminal 1 via the WAP-GW / JSP 6. At this time, WAP-GW / JSP6 encrypts and transmits the parameter including the time information at that time.

When the user looks at the billing authentication screen ((B) of FIG. 3), inputs the password and operates the “OK” button, the 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 WAP-GW / JSP6 and WGW11 (H-MAWG12) and transferred to TMS-C18 of DRM platform 16. 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. 3D is displayed on the mobile terminal 1 to prompt the user to send the request again.

  The WAP-GW / JSP 6 that has received “(5) DD Request” from the mobile terminal 1 uses the MSISDN or IMSI of the mobile terminal 1 as a key, and information indicating the model information and performance of the mobile terminal from the R2M7. The mobile terminal information (UE-Profile) and the profile information (UA-Profile) of a user agent such as a web browser are acquired. At this time, the WAP-GW / JSP 6 uses, as extended information for DRM, the type of secure clock (time information held inside the mobile terminal 1), the MIME type and permission linking information to be changed, and Also obtain the domain name of the region to which it belongs. Then, the WAP-GW / JSP6 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 WGW11 ( 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. 2, in the download descriptor, the object link (ol) described above is described as a parameter (ObjectURI) indicating the actual location of the content, and as a notification destination (InstallNotifyURI) of the content delivery completion notification , The URI of the TMS server 17 (URI for TMS notification) and the parameter “CPNotify” described above are described.
The “(6) 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 “(6) DD Response”, a content confirmation screen as shown in FIG. 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 “(6) DD Response”. The acquisition request “(7) MO Request” is sent, and the screen shown in FIG. 3E is displayed. When the user operates the “NG” button, the screen shown in FIG. 3F is displayed, and the process is stopped.

The “(7) 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 “(8) MO Response” including the requested content (media object) via the WGW 11, the DRM platform 16, and the WAP-GW / JSP 6. Forward to 1.
In this process, when an error is detected in each server, the error is displayed as shown in FIG. 3G, and the download is stopped. When the MO download fails, an error display shown in FIG.
When the mobile terminal 1 has received all the media objects without detecting an error, the mobile terminal 1 sends a download completion notification “(9) Install Notify” via the WAP-GW / JSP6. 16 TMS servers 17 (notification destination specified by the parameter “InstallNotifyURI”).

Upon receiving the “(9) Install Notify”, the TMS server 17 returns a response “(10) Install Notify Ack” and notifies the license server (LS) 21 to receive the corresponding rights object (RO). . Then, the TMS server 17 delivers the rights object to the PPG 9, and the PPG 9 delivers the rights object to the mobile terminal 1 by WAP push ((11) RO Delivery).
At this time, the DRM platform 16 rewrites the permission information of the rights object or does not distribute the rights information according to the capability of the mobile terminal 1 that has sent the HTTP request. For example, the DRM platform 16 does not distribute a rights object including a content availability time and a content availability period to a mobile terminal in which the user can easily change the time information held therein. ing.

The mobile terminal 1 displays a download completion screen ((I) in FIG. 3) when the push distribution of the rights object (RO) performed following the download of the media object (MO) is completed. When the execution of the content is instructed by the user, the content is executed ((J) in FIG. 3).
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” according to the content and transmits it to the DRM platform 16.
When the DRM platform 16 receives the delivery result notification message “Delivery Report”, it creates a log (Reporting) and determines whether or not the rights object has been successfully delivered. Only when the delivery is successful, the DRM platform 16 The billing notification “(13) Charging Notify” including “” is created and transmitted to the corresponding WGW 11. The WGW 11 that has received the billing notification performs billing processing based on the billing parameter included in the notification (CDR Create).

When a plurality of WGWs 11 are provided as described above, the billing notification is sent to the WGW 11 in the area to which the mobile terminal belongs using the domain name supplemented to the host header of the HTTP request as described above. It is supposed to be sent.
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 (if distribution is successful). ). In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. As a result, a content provider or the like can acquire information indicating that the content has been distributed in real time.

The case described above is a case where the media object and the rights object are continuously distributed. Next, a case where only the rights object of paid content is distributed will be described. In this case, the media object is distributed in advance to the user's mobile terminal 1 by various means.
FIG. 4 is a diagram showing a sequence when only the rights object is distributed, and FIG. 5 is a diagram showing an example of a screen display on the mobile terminal 1 at that time.
In FIG. 4, when the user selects content for purchasing a rights object on the target content selection screen ((A) of FIG. 5), “(1) Rights Issuer URI Request” is transmitted to the content provider 27. In response to this, “(2) content selection screen” is transmitted from the content provider 27 to the mobile terminal 1. FIG. 5B is a diagram illustrating an example of a content selection screen. As shown in the figure, the content purchase location includes a service ID (sid), an LID that designates a rights object, and a notification destination (CPNotify) that notifies that the rights object has been successfully distributed (in this example, http: / A link to the destination (WGW11) of the CONFON request to which a parameter such as /www.cp.com/notify) is added.
When the user selects purchase on this screen, the “(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. 5C, 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.
The DRM platform 16 (TMS server 17) that has received this “(5) OK (Rights Object Request)” request performs a billing check and transmits the result information “(6) Status Response” to the mobile terminal 1.
The display corresponding to the “(6) Status Response” is displayed on the display unit of the mobile terminal 1. FIG. 5D shows an example of a screen when there is no error, and FIG. 5E shows an example of a screen when an error occurs.
When there is no problem as a result of the charging check, the DRM platform 16 (TMS server 17) receives the rights object requested from the license server (LS) 21 and transmits it to the PPG 9 for distribution to the mobile terminal 1 To do. As a result, the rights object is delivered from the PPG 9 to the mobile terminal 1 “(7) RO Delivery”.

FIG. 5F shows a display screen when an error occurs during distribution of the rights object. When the distribution of the rights object is completed, a screen indicating the completion of the distribution ((G) in FIG. 5) 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 receiving the requested rights object, the mobile terminal 1 transmits “(8) Delivery Receipt” notifying the delivery status to the PPG 9. When the PPG 9 receives the “(8) Delivery Receipt”, the PPG 9 creates a delivery result notification message “Delivery Report” according to the content and transfers it to the DRM platform 16 (TMS server 17).
When the DRM platform 16 receives the delivery result notification message “Delivery Report”, it creates a log (Reporting) and determines whether or not the rights object has been successfully delivered. Only when the delivery is successful, the DRM platform 16 The billing notification “(9) Charging Notify” including “” is created and transmitted to the corresponding WGW 11. 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, the content delivery completion notification “(10) CP Notify” is transmitted to the URI specified by the parameter (if distribution is successful). ). In the illustrated example, a delivery completion notification is transmitted to “http://www.cp.com/notify”. As a result, a content provider or the like can acquire information indicating that the content has been distributed in real time.
In this way, in this case as well, the billing process is not performed before the distribution of the rights object is completed.

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 figure which shows a sequence when purchasing the media object and rights object of paid content in a series of sequences. It is a figure which shows the example of a screen display of a mobile terminal when purchasing a media object and a rights object in a series of sequences. It is a figure which shows the sequence when purchasing only the rights object of paid content. It is a figure which shows the example of a screen display of a mobile terminal when purchasing only a rights object.

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 provided between a mobile communication network and an IP network such as the Internet, and connected to a gateway server for processing related to billing,
A plurality of gateway servers are provided for each region,
In the host header of the HTTP request from the mobile terminal, the server device that terminates the WAP protocol from the mobile terminal is supplemented with a domain name indicating the region to which the mobile terminal belongs,
Means for delivering the rights object to the mobile terminal when the mobile terminal has requested acquisition of the rights object in separate delivery;
When delivery of the rights object to the mobile terminal is completed, a billing notification is sent to the gateway server in the region to which the mobile terminal belongs using the domain name supplemented in the host header of the HTTP request And a server device.

Images