Distribution server, distribution method, and program

Abstract

This enables the delivery of content combining multiple media formats within the same text, without increasing the operational burden. [Solution] A distribution server that distributes content according to an RCS (Rich Communication Services) scenario via a telecommunications carrier server, comprising: a registration unit that generates a scenario information table in which text is specified as an entity and media is specified as a variable in a combination of text and media as content; and a distribution processing unit that generates distribution scenario information specifying text and media as entities by providing a variable corresponding to the media designated as the distribution target as an argument to the scenario information table, and distributes content according to the generated distribution scenario information via the telecommunications carrier server.

Description

Technical Field

[0001] The present invention relates to a distribution server, a distribution method, and a program.

Background Art

[0002] There is an electronic notification service for notifying information online. Patent Document 1 discloses a technique for transmitting information to an address with a high probability that a user can immediately view when notifying the user. Such an electronic notification service includes a content distribution service having a telephone number as a destination, for example, RCS (Rich Communication Services). In content distribution using RCS, an API (Application Programming Interface) is provided by a communication telephone carrier (carrier) corresponding to the destination telephone number, and distribution can be performed using a scenario according to the specification of this API. In the scenario, the content to be distributed is specified together with the destination telephone number and the like. As the content specified here, for example, a combination of media and text can be specified. Media is information such as images, videos, and PDFs (Portable Document Format). Text is text information indicating a text surface such as a guidance text.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there were limitations in the API specifications regarding the combination of media and text specified as content. Specifically, it was not possible to specify the delivery of any of multiple text and media combinations in a single scenario. Therefore, when delivering the same text to multiple users, it was difficult to use a single scenario to deliver different media combinations depending on the recipient user. One possible solution is to prepare multiple scenarios that show content with the same text but different media combinations. However, this approach requires generating multiple scenarios. Furthermore, if the wording of the text is changed, the change must be reflected in all of the multiple scenarios. This resulted in a significant operational burden.

[0005] This invention has been made in view of the above circumstances, and its purpose is to provide a distribution server, distribution method, and program that can deliver content combining any of multiple media in the same text without increasing the operational burden. [Means for solving the problem]

[0006] To solve the above-mentioned problems, one aspect of the present invention is a distribution server that distributes content according to an RCS (Rich Communication Services) scenario via a telecommunications carrier server, comprising: a registration unit that generates a scenario information table in which text is specified as an entity and media is specified as a variable in a combination of text and media as content; and a distribution processing unit that generates distribution scenario information specifying text and media as entities by providing a variable corresponding to the media designated as the distribution target as an argument to the scenario information table, and distributes content according to the generated distribution scenario information via the telecommunications carrier server.

[0007] Furthermore, one aspect of the present invention is a distribution method performed by a computer that is a distribution server that distributes content according to an RCS (Rich Communication Services) scenario via a telecommunications carrier server, wherein a registration unit generates a scenario information table in which text is specified as an entity and media is specified as a variable in a combination of text and media as content, and a distribution processing unit generates distribution scenario information that specifies text and media as entities by providing a variable corresponding to the media designated as the distribution target as an argument to the scenario information table, and distributes the content according to the generated distribution scenario information via the telecommunications carrier server. Note that "specifying text as an entity" means that the text is specified in accordance with the API specifications. For example, if the API specifies that it is possible to specify part or all of the text as a variable, then part or all of the text may be specified as a variable in accordance with those specifications. That is, there may be cases in which part or all of the text is specified as a variable and the media is also specified as a variable.

[0008] Furthermore, one aspect of the present invention is a program that causes a computer, which is a distribution server that distributes content according to an RCS (Rich Communication Services) scenario via a telecommunications carrier server, to generate a scenario information table in which text is specified as an entity and media is specified as a variable in a combination of text and media as content, and to generate distribution scenario information that specifies text and media as entities by providing a variable corresponding to the media specified as the distribution target as an argument to the scenario information table, thereby generating distribution scenario information that specifies text and media as entities, and to distribute content according to the generated distribution scenario information via the telecommunications carrier server. [Effects of the Invention]

[0009] According to the present invention, it is possible to deliver content that combines any of multiple media with the same text without increasing the operational burden. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example configuration of the distribution system 1 according to the embodiment. [Figure 2A] This figure shows an example of the content of the embodiment. [Figure 2B] This figure shows an example of the content of the embodiment. [Figure 3A] This is a diagram illustrating the conventional process. [Figure 3B] This is a diagram illustrating the conventional process. [Figure 4] This figure shows an example configuration of the distribution server 10 according to the embodiment. [Figure 5] This figure shows an example configuration of scenario DB122 according to the embodiment. [Figure 6A] This is a diagram illustrating the processing performed by the distribution server 10 according to the embodiment. [Figure 6B] This is a diagram illustrating the processing performed by the distribution server 10 according to the embodiment. [Figure 7] This is a sequence diagram showing the processing flow performed by the distribution system 1 of the embodiment. [Figure 8] This is a sequence diagram showing the processing flow performed by the distribution system 1 of the embodiment. [Figure 9] This figure shows an example configuration of scenario DB122 based on a modified embodiment. [Figure 10A] This diagram illustrates the processing performed by the distribution server 10 according to a modified embodiment. [Figure 10B] This diagram illustrates the processing performed by the distribution server 10 according to a modified embodiment. [Modes for carrying out the invention]

[0011] Embodiments of the present invention will be described below with reference to the drawings.

[0012] <Configuration of distribution system 1> FIG. 1 is a block diagram showing a configuration example of a distribution system 1 according to an embodiment. As shown in FIG. 1, the distribution system 1 includes, for example, a distribution server 10, a corporate server 20, a communication carrier server 30, a communication terminal 40, and a CDN 50.

[0013] The distribution server 10 is a computer managed by an operator providing a distribution service. The distribution service is a service that transmits content requested from a company corresponding to the corporate server 20 to the communication terminal 40 of the customers of that company. The distribution server 10 distributes content using RCS (Rich Communication Services). RCS is a service that transmits content to a communication terminal to which a telephone number is assigned, using the telephone number as the destination. As the distribution server 10, for example, a computer such as a server device or a personal computer (PC) can be applied. The distribution server 10 performs wireless communication or wired communication with the corporate server 20 and the communication carrier server 30.

[0014] The corporate server 20 is an information processing device managed by a company. As the corporate server 20, for example, a computer such as a server device or a PC can be applied. As the company corresponding to the corporate server 20, any company and organization, for example, a bank, an insurance company, a travel agency, a public body, etc. can be applied. The corporate server 20 performs wireless communication or wired communication with the distribution server 10. The corporate server 20 requests the distribution server 10 to distribute content including information such as notifications and promotions from the company to the communication terminal 40 of the users who are the customers of the company.

[0015] The communication carrier server 30 is a server device managed by a communication carrier. The communication carrier is, for example, an MNO (Mobile Network Operator) that provides a communication service using a telephone number to a communication terminal 40 by using a communication line owned or operated by itself. The communication service includes communication using RCS. In communication using RCS, the communication carrier server 30 transmits content corresponding to RCS to the communication terminal 40 in response to a delivery request from the delivery server 10. The communication carrier server 30 communicates wirelessly or wired between the delivery server 10 and the communication terminal 40.

[0016] The communication terminal 40 is an information processing device used by a user or the like. As the communication terminal 40, for example, a computer having a structure capable of mounting a SIM (Subscriber Identity Module) that stores information such as a contract phone number of a contract customer who has contracted with a communication carrier, such as a smartphone or a mobile phone, and performing communication using a communication network provided by the communication carrier based on the mounted SIM can be applied. Note that, as the communication terminal 40, a computer equipped with an integrated SIM (eSIM) in which the function of the SIM is built in a smartphone may be applied. The communication terminal 40 has a display unit such as a liquid crystal display for displaying information and an operation unit such as a touch panel for receiving operations by the user. The communication terminal 40 receives content from the enterprise server 20 via the delivery server 10 and the communication carrier server 30.

[0017] A contract is made between the communication terminal 40 and a communication carrier corresponding to the communication carrier server 30 by a user or the like for using a communication service using the communication terminal 40. The communication terminal 40 can communicate using a communication service provided by the contracted communication carrier. A telephone number is assigned to the communication terminal 40, and it has a function of performing communication addressed to this telephone number, that is, communication using RCS.

[0018] CDN50 is a Contents Delivery Network (CDN) for delivering media to the destination communication terminal 40. CDN50 is a network designed to ensure smooth content delivery and is composed of multiple cache servers, for example. CDN50 is a network optimized for delivering web content over the internet and can suppress problems such as slow image display speeds or increased processing load on the source server (in this case, the delivery server 10) in situations where there is a high volume of access to the content being delivered.

[0019] <About the content> This embodiment illustrates the distribution of content combining text T and media M. Media refers to information such as images, videos, and PDFs (Portable Document Format). Text refers to text information that represents written content, such as announcements. However, this embodiment is not limited to content combining text T and media M. This embodiment may also be applied to the distribution of content consisting only of text T or content consisting only of media M. Figure 2 (Figures 2A and 2B) shows examples of content in the embodiment. Figure 2A shows an example of content delivered to a user (first user), which is a combination of text T and media MA. Figure 2B shows an example of content delivered to another user (second user), which is a combination of text T and media MB.

[0020] <Regarding conventional processing> Here, we will explain the conventional process using Figure 3 (Figures 3A and 3B). Figure 3 is a diagram for explaining the conventional process.

[0021] Figure 3A shows the conventional process flow for registering content information in a database (DB). As shown in this figure, in conventional systems, a scenario definition file and a media file are prepared as content information D1.

[0022] A scenario definition file contains information that corresponds to the text portion of the content. For example, a scenario file contains the following information: "title": "Notice of Usage Fees" “description”: “This month’s usage fee is…” Here, the scenario definition file indicates that the text corresponding to the "title" tag in the content's text section will be set to "Notice of Usage Fees." It also indicates that the text corresponding to the "description" tag in the content's text section will be set to "This month's usage fees are..."

[0023] A media file is an electronic file corresponding to the media portion of the content (either an image, video, PDF (Portable Document Format), or a combination thereof). For example, a media file might be an electronic file in PNG (Portable Network Graphics) format, which is a raster image file format. In this case, the media file would be indicated by a name such as "mediafile.png".

[0024] The conventional distribution server 100 uses information D1 (scenario definition file and media file) to generate information to be registered in the DB. The DB is a database that is referenced when generating distribution scenarios, and it stores various data used in scenario generation.

[0025] When distributing media using CDN50, the distribution server 100 first registers the media files with CDN50. This generates a CDN-compatible URL. For example, if the filename of a media file is "mediafile.png", registering the media file with the CDN will result in the following URL being issued as the URL corresponding to the media file. https: / / … / mediafile.png

[0026] Next, the distribution server 100 generates the conventional scenario information D2 using the URLs issued in accordance with the scenario definition file and media files. Scenario information D2 is information that indicates the combination of text T (text) and media (images, etc.) as content. Scenario information D2 may include information such as the following: "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafile.png”} Here, scenario information D2 shows not only the text of the text T generated in response to the scenario definition file, but also the media to be combined with this text T. Specifically, it indicates that the media to be delivered as content, associated with the "media" tag, will be designated as a "media file". The distribution server 100 stores the generated scenario information D2 in the database.

[0027] Figure 3B shows the conventional processing flow for content distribution. The distribution server 100 acquires the distribution data D3. For example, when the distribution data D3 is sent from the corporate server 20 to the distribution server 100, the corporate server requests distribution according to the distribution data D3.

[0028] The distribution data D3 contains information related to the distribution, including the transmission date and time, "Distributed on 2024 / 8 / 1 at 12:00," and a list of telephone numbers to which the data will be distributed. In this diagram, along with the list of telephone numbers, the distribution data D3 also shows the residential area and gender of each recipient user associated with that telephone number. The distribution server 100 stores the acquired distribution data D3 in the database.

[0029] The distribution server 100 generates a distribution scenario D4 using the information stored in the DB (scenario information D2 and distribution data D3). Scenario D4 is information that formats and links the distribution destination (telephone number) and the distribution content according to the carrier's specifications. For example, scenario D4 includes the following information.

[0030] “userContact”:”090XXXX”, "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafile.png”} Here, in Scenario D4, the recipient's address (phone number) is shown, associated with the “userContact” tag. The text to be included as the “title” in the content text T is shown, associated with the “title” tag. The text to be included as the “body” in the content text T is shown, associated with the “description” tag. Media files such as images to be displayed along with the text T are specified, associated with the “media” tag.

[0031] The distribution server 100 sends a distribution request to the telecommunications carrier server 30 by sending scenario D4. The communication carrier server 30 delivers content to the communication terminal 40 to which the telephone number specified as the destination has been assigned, in response to a delivery request notified by the delivery server 100. Once the content is delivered to the communication terminal 40, the content, which is a combination of text and media, is displayed on the communication terminal 40 in response to an operation to display the delivered content.

[0032] In cases where a company distributes content informing its customers of usage fees, it is common practice to standardize the text portion, such as the title and body text, to the same wording. When distributing identical content to multiple users simultaneously, the distribution process is executed using a single scenario. Specifically, by generating a scenario D4 based on the scenario information D2 and distribution data D3 described above, it is possible to simultaneously distribute content with the same text to multiple users.

[0033] Incidentally, when companies send the same message, such as "Notice of Usage Fees," to multiple users simultaneously, they sometimes request that the media used be tailored to each user's preferences rather than using the same media for everyone.

[0034] In such cases, conventional processing requires generating multiple scenario information D2s, each containing the same text T but with different media paired with it. Specifically, when distributing content combining text T and media MA, as shown in Figure 2A, scenario information D2(T, MA) is generated. Similarly, when distributing content combining text T and media MB, as shown in Figure 2B, scenario information D2(T, MB) is generated. The distribution server 100 receives distribution data D3 specifying whether the media paired with text T should be media MA or MB. Based on the distribution data notified by the company, the distribution server 100 selects the scenario information D2 to use for generating scenario D4 from scenario information D2(T, MA) and D2(T, MB), and generates scenario D4 using the selected scenario information D2. Specifically, when distributing content combining text T and media MA, scenario D4(T, MA) is generated using scenario information D2(T, MA) and distribution data D3. Furthermore, when delivering content that combines text T and media MB, scenario D4(T, MB) is generated using scenario information D2(T, MB) and delivery data D3.

[0035] In other words, when attempting to deliver content that combines the same text T, as shown in Figure 2, with either different media (MA) or (MB) depending on the recipient user, it was necessary to generate two scenarios, D4(T, MA) and D4(T, MB), and then execute a process to deliver content according to each scenario. Thus, when attempting to deliver content combining different media with the same text, multiple scenario information D2 files must be generated, which is time-consuming. Furthermore, if the wording of the text is changed, the change must be reflected in all of the multiple scenarios, resulting in a significant operational burden.

[0036] To address this issue, in this embodiment, a single scenario information D2 (scenario information TBL122B, described later) can be used to generate a scenario D4 that combines different media with the same text. Specifically, when combining text and media as content, we have created information (scenario information TBL122B) that specifies the text as an entity and the media as a variable. Then, by making the variable corresponding to the media specified as the target of distribution an argument to scenario information TBL122B, we have created scenario D4 in which both text and media are specified as entities. As a result, it is possible to generate scenarios that specify content combining the same text with one of multiple media as the target of distribution from a single scenario information TBL122B, thereby suppressing an increase in operational burden.

[0037] <Configuration of distribution server 10> Figure 4 shows an example of the configuration of a distribution server 10 according to an embodiment. The distribution server 10 includes, for example, a communication unit 11, a storage unit 12, and a control unit 13. The communications unit 11 communicates with the corporate server 20 and the telecommunications carrier server 30.

[0038] The memory unit 12 includes scenario definition information 120, media information 121, and scenario DB 122. Scenario definition information 120 is text information corresponding to the text portion of the content to be distributed. Scenario definition information 120 corresponds to a conventional scenario definition file, and is information in which the text is set for each tag corresponding to "title," "body," etc.

[0039] Media information 121 is information that indicates images, etc. (either images, videos, PDFs, or a combination thereof) that correspond to the media portion of the content to be distributed. The media information 121 of this embodiment includes media information 121A and media information 121B. Media information 121A is information indicating the classification of the media. The media classification here indicates an arbitrary classification according to the intentions of the company or the content of the services provided by the distribution server 10. For example, if the classification distinguishes media MA and MB as shown in Figure 2, then the categories "Animal (Cat)" and "Animal (Dog)" are provided. In this case, the distribution personal information TBL122A indicates information specifying either "Animal (Cat)" or "Animal (Dog)" as the media classification. Hereafter, it will be assumed that there are two categories for media classification: Value (Valueα) and Value (Valueβ). Media information 121B is information (electronic file) that indicates the physical nature of the media. In this embodiment, media information 121B is stored as multiple media that are candidates to be combined with text. Each piece of media information 121B is classified according to the classification of media, and the classification result is stored in media information 121A. Here, it is assumed that "media file A" corresponding to media information 121A-1 is set as the media belonging to the classification value (Value α). It is assumed that "media file B" corresponding to media information 121A-2 is set as the media belonging to the classification value (Value β).

[0040] Scenario DB122 is a database used to generate scenario D4 for distribution. Figure 5 shows an example of the configuration of Scenario DB122 according to the embodiment. Scenario DB122 comprises Distribution Personal Information TBL122A, Scenario Information TBL122B, and Media Classification TBL122C.

[0041] Distribution Personal Information TBL122A is a table (TBL) that shows the personal information of the users to whom the information is distributed. Distribution Personal Information TBL122A is, for example, the information shown in distribution data D3 notified by a company. Distribution Personal Information TBL122A includes information such as the telephone number, place of residence, and gender of the users to whom the information is distributed. Furthermore, in this embodiment, the distributed personal information TBL122A includes information that specifies the media classification of the content to be distributed, that is, information that indicates either a value (Valueα) or a value (Valueβ) that indicates the classification.

[0042] Scenario information TBL122B corresponds to the conventional scenario information D2, and in the combination of text and media as content, it specifies the text as an entity and the classification of the media as a variable. Scenario information TBL122B includes information such as the following (see Figure 6A). "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:“if image_param1=¥“Valueα¥””, “mediaUrl”:“https: / / … / mediafileA.png”, “media”:“elseif image_param1=¥“Valueβ¥””, “mediaUrl”:“https: / / … / mediafileB.png”

[0043] Scenario information TBL122B differs from conventional scenario information D2 in that the information associated with the “media” tag does not represent an actual media file such as “media file.png”. Scenario information TBL122B indicates that when a classification value (Valueα) is set to the variable (image_param1) associated with the "media" tag, the media to be delivered as content will be "Media File A". It also indicates that when a classification value (Valueβ) is set to the variable (image_param1), the media to be delivered as content will be "Media File B". Thus, in scenario information TBL122B, media are not directly represented as entities such as "media file," "media file A," and "media file B," but rather represented by a variable (image_param1). This allows the value corresponding to the variable to be used as an argument given to scenario information TBL122B, enabling it to function as scenario information D2 corresponding to each of multiple media. Specifically, by providing a value (Valueα) indicating the classification to correspond to the variable (image_param1) as an argument to the scenario information TBL122B, the scenario information TBL122B functions as scenario information D2(T, MA) corresponding to content that combines text and "media file A" belonging to the classification value (Valueα). On the other hand, by providing the classification value (Valueβ) corresponding to the variable (image_param1) as an argument to the scenario information TBL122B, the scenario information TBL122B functions as scenario information D2(T, MB) corresponding to content that combines text T and "media file B" belonging to the classification value (Valueβ).

[0044] Media Classification TBL122C is a table that associates media with a value indicating its classification. For example, Media Classification TBL122C includes two classifications for media: Value α and Value β. In Media Classification TBL122C, "Media File A" is set as media belonging to the classification value (Value α), and "Media File B" is set as media belonging to the classification value (Value β).

[0045] CDN registration information 123 is information that ensures media is delivered via CDN 50. CDN registration information 123 is, for example, a URL generated in response to registration with the CDN. Using this URL, media can be delivered via the CDN.

[0046] The storage unit 12 is composed of a storage medium, such as an HDD (Hard Disk Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access read / write Memory), ROM (Read Only Memory), or any combination of these storage media. The storage unit 12 stores programs for executing various processes of the distribution server 10, and temporary data used when performing these processes.

[0047] The control unit 13 comprises a scenario registration unit 130, a distribution data acquisition unit 131, and a distribution processing unit 132. The control unit 13 is implemented, for example, by the CPU (Central Processing Unit) of the distribution server 10 executing a program pre-stored in the storage unit 12. Alternatively, the control unit 13 may be implemented as an integrated circuit such as an ASIC (Application Specific Integrated Circuit).

[0048] The scenario registration unit 130 generates scenario information TBL122B. The scenario registration unit 130 generates scenario information TBL122B using scenario definition information 120 and media information 121. The scenario registration unit 130 stores the generated scenario information TBL122B in the scenario DB 122 of the storage unit 12. The distribution data acquisition unit 131 acquires the distribution data D3 and outputs the acquired distribution data D3 to the distribution processing unit 132. The distribution processing unit 132 performs the processing of distributing content. The distribution processing unit 132 generates a distribution scenario D4 using the distribution data D3 and the scenario information TBL122B.

[0049] <Regarding the processing flow performed by distribution server 10> Here, we will explain the processing performed by the functional units of the control unit 13 (scenario registration unit 130, distribution data acquisition unit 131, and distribution processing unit 132) using Figures 6 (Figures 6A and 6B), 7, and 8. Figure 6 is a diagram illustrating the processing performed by the distribution server 10 according to this embodiment. Figures 7 and 8 are sequence diagrams showing the flow of processing performed by the distribution system 1 according to this embodiment.

[0050] Figure 6A shows the process flow for registering scenario information in the scenario DB 122. As shown in this figure, in the distribution system 1, the following information is provided in advance by, for example, a company, as content information D1: scenario definition information 120, media information 121A (media classification file), and multiple media information 121B (media information 121B-1, 121B-2, ...). Each media corresponding to the multiple media information 121B belongs to one of the media classifications.

[0051] The scenario registration unit 130 uses information D1 (scenario definition information 120, media classification file as media information 121A, and media information 121B) to generate information to be registered in the scenario DB 122 (scenario information TBL 122B and media classification TBL 122C). When distributing media using CDN50, the scenario registration unit 130 first registers the media files with the CDN based on the media files. The scenario registration unit 130 also stores the URL generated in response to the registration of the media files with the CDN in the CDN registration information 123. For example, if the file name corresponding to media information 121B-1 is "mediafileA.png", then a URL like the following will be issued when mediafileA is registered with the CDN. https: / / … / mediafileA.png Furthermore, if the file name corresponding to media information 121B-2 is "mediafileB.png", a URL like the following will be issued in accordance with the registration of this media file B to the CDN. https: / / … / mediafileB.png

[0052] Next, the scenario registration unit 130 generates scenario information TBL122B and media classification TBL122C using the scenario definition information 120, the media classification file, and the URLs issued for each media. Scenario information TBL122B includes information such as the following. "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:“if image_param1=¥“Valueα¥””, “mediaUrl”:“https: / / … / mediafileA.png”, “media”:“elseif image_param1=¥“Valueβ¥””, “mediaUrl”:“https: / / … / mediafileB.png” As mentioned above, here, the scenario information TBL122B includes the text of the text T generated in accordance with the scenario definition information 120, as well as a variable indicating the type of media to be combined with this text. Specifically, it is indicated that when the classification value (Valueα) is set to the variable (image_param1), the media to be delivered as content will be "Media File A". Also, it is indicated that when the classification value (Valueβ) is set to the variable (image_param1), the media to be delivered as content will be "Media File B". The scenario registration unit 130 stores the generated scenario information TBL122B in the scenario DB122. Furthermore, the scenario registration unit 130 generates a table that associates media with their classifications, and stores the generated table as media classification TBL122C in the scenario DB122.

[0053] Figure 6B shows the flow of the content distribution process. The distribution data acquisition unit 131 acquires distribution data D3. Distribution data D3 includes information related to distribution, such as "Distributed on 2024 / 8 / 1 at 12:00" indicating the transmission date and time, and a list of telephone numbers to which the data will be distributed. In addition, information related to distribution includes information specifying the scenario to be used for distribution, and a value (Valueα or Valueβ) indicating the classification of the media to which the data will be distributed, associated with the telephone number. In this diagram, the distribution data D3 shows that media belonging to a classification value (Valueα) is distributed to the user with the telephone number (090XXXX). It also shows that media belonging to a classification value (Valueβ) is distributed to the user with the telephone number (080YYYY). The distribution data acquisition unit 131 stores the acquired distribution data D3 as distribution personal information TBL122A in the scenario DB122.

[0054] The distribution processing unit 132 generates a distribution scenario D4 using the information stored in the scenario DB 122 (scenario information TBL 122B and distribution data D3). The distribution processing unit 132 generates a scenario D4 according to the type of media to be distributed.

[0055] Specifically, the distribution processing unit 132 obtains a value (Valueα) from the distribution data D3 that indicates the classification associated with the telephone number (090XXXX). The distribution processing unit 132 uses the obtained value (Valueα) as an argument to the scenario information TBL122B to generate scenario D4-1, which distributes content to the telephone number (090XXXX) that combines text with media file A belonging to the classification value (Valueα). Scenario D4-1 includes information such as the following. “userContact”:”090XXXX”, "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafileA.png”}

[0056] Furthermore, the distribution processing unit 132 obtains a value (Valueβ) from the distribution data D3 that indicates the classification associated with the telephone number (080YYYY). By providing the obtained value (Valueβ) as an argument to the scenario information TBL122B, the distribution processing unit 132 generates a scenario D4-2 that distributes content, which combines text with media file B belonging to the classification value (Valueβ), to the telephone number (080YYYY). Scenario D4-2 includes information such as the following. “userContact”:”080YYYY”, "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafileB.png”}

[0057] The distribution processing unit 132 sends scenario D4 to the telecommunications carrier server 30 to make a distribution request to the telecommunications carrier. The telecommunications carrier server 30 delivers content to the communication terminal 40 to which the telephone number specified as the destination has been assigned, in response to a delivery request notified by the delivery processing unit 132 of the delivery server 100. Specifically, based on scenario D4-1, the telecommunications carrier server 30 sends content combining text T and media file A to the communication terminal 40-1 of user 1, to which the telephone number (090XXXX) has been assigned. In response, the content is delivered to user 1's communication terminal 40-1, and in response to an operation to display the delivered content, the content combining text T and media file A is displayed on the communication terminal 40. Furthermore, based on scenario D4-2, the communication carrier server 30 sends content combining text T and media file B to the communication terminal 40-2 of user 2, which is assigned the telephone number (080YYYY). In response, the content is delivered to user 2's communication terminal 40-2, and in response to an operation to display the delivered content, the content combining text T and media file B is displayed on the communication terminal 40.

[0058] Figure 7 shows a sequence diagram of the distribution system 1 involved in the process of registering scenario-related information in the scenario DB122. The enterprise server 20 sends an electronic file corresponding to the content information D1 to the scenario registration unit 130 of the distribution server 10 (step S10). The electronic file corresponding to information D1 is a scenario definition file corresponding to the scenario definition information 120, a media classification file corresponding to media information 121A, and multiple media files (media file A, media file B, ...) corresponding to media information 121B. The scenario registration unit 130 registers each media file with the CDN 50 (step S11). The scenario registration unit 130 stores the URL issued in response to the registration of the media file with the CDN 50 as CDN registration information 123 in the storage unit 12 (step S12). The scenario registration unit 130 generates a scenario information TBL 122B that shows the contents of the scenario definition file corresponding to the scenario definition information 120 and the URL generated in response to the registration with the CDN, and stores the generated scenario information TBL 122B in the scenario DB 122 (step S13). The scenario registration unit 130 stores a media classification TBL 122C that shows the contents of the media classification file corresponding to the media information 121A in the storage unit 12 (step S14).

[0059] Figure 8 shows a sequence diagram of the distribution system 1 involved in the process of distributing content. The enterprise server 20 sends the distribution data D3 to the distribution data acquisition unit 131 of the distribution server 10 (step S20). The distribution data acquisition unit 131 acquires the media classification table TBL122C from the scenario database DB122 (step S21). The distribution data acquisition unit 131 stores the contents of the distribution data D3 as the distribution personal information table TBL122A in the scenario database DB122 (step S22). The distribution processing unit 132 of the distribution server 10 reads the distribution personal information TBL122A from the scenario DB122 and obtains a value (Valueα or Valueβ) indicating the destination (telephone number) and media classification of the distribution target (step S23). The distribution processing unit 132 reads the scenario information TBL122B from the scenario DB122 and obtains a URL generated corresponding to the text T to be distributed and the media file to be distributed (step S24). From the media classification (Valueα or Valueβ) obtained in step S23, the distribution processing unit 132 identifies the URL of the media to be distributed from the URLs obtained in step S24 (step S25). The distribution processing unit 132 generates a scenario D4 in accordance with the carrier's specifications (step S26). The distribution processing unit 132 sends the generated scenario D4 to the telecommunications carrier server 30 (step S27). The communication carrier server 30 sends (distributes) content to the communication terminal 40 based on scenario D4 received from the distribution server 10 (step S28). When the content is displayed on the communication terminal 40, the CDN 50 sends the media file stored in the URL to the communication terminal 40, causing the communication terminal 40 to display the image, etc., corresponding to the media file (step S29).

[0060] As described above, the distribution server 10 of this embodiment is a distribution server that distributes content according to the RCS scenario via a telecommunications carrier server. The distribution server 10 comprises a scenario registration unit 130 (registration unit) and a distribution processing unit 132. The scenario registration unit 130 generates scenario information TBL122B in which, in combination of text and media as content, the text is specified as an entity and the media is specified as a variable. The distribution processing unit 132 generates distribution scenario information (scenario D4) that specifies both text and media as entities by using a variable (image_param1) corresponding to the media specified as the distribution target as an argument given to the scenario information TBL122B. The distribution processing unit 132 distributes the content according to the generated scenario D4 via the telecommunications carrier server 30. As a result, the distribution server 10 of this embodiment can generate multiple scenarios D4 from a single scenario information TBL122B, corresponding to combinations of the same text and any one of the multiple media. Therefore, it is possible to distribute content combining the same text with any of the multiple media without increasing the operational burden.

[0061] Furthermore, the distribution server 10 of this embodiment is further equipped with a storage unit 12. The storage unit 12 stores a media classification table TBL 122C. The media classification table TBL 122C is information that associates a value (Value α or Value β) indicating the classification of the media with media that are candidates for distribution. The scenario registration unit 130 generates scenario information table TBL 122B that specifies the media using a variable indicating the classification of the media. The distribution processing unit 132 obtains distribution data D3 (distribution data in which the classification of the media to be distributed is specified). The distribution processing unit 132 identifies a variable corresponding to the classification of the media designated as a distribution target by referring to the media classification table TBL 122C. The distribution processing unit 132 uses the identified variable as an argument to the scenario information table TBL 122B to generate a scenario D4 that specifies both the text and the media corresponding to the classification of the media designated as a distribution target as actual entities. As a result, the distribution server 10 of this embodiment can distribute content that combines media belonging to any of multiple media classifications with the same text, without increasing the operational load.

[0062] <Modification 1 of the embodiment> Here, a modified version of the embodiment will be described. This modified version differs from the embodiment described above in that the media is specified by a variable (rather than a media classification).

[0063] Figure 9 shows an example of the configuration of Scenario DB122 according to a modified embodiment. Scenario DB122 comprises Distribution Personal Information TBL122A, Scenario Information TBL122B, and Media Settings TBL122D.

[0064] The distribution personal information TBL122A is a TBL (table) that shows the personal information of the user to whom the content is distributed, similar to the embodiment described above. In this modified example, the distribution personal information TBL122A includes information that specifies (in terms of actual) the media in the content to be distributed, for example, information that indicates either value (media file A) or value (media file B).

[0065] Scenario information TBL122B is the same as the conventional scenario information D2 in the embodiment described above. In this modified example, scenario information TBL122B is information that specifies text as an entity and media as a variable. Scenario information TBL122B is, for example, the following (see Figure 10A). "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:“if image_param1=￥“Media File A￥””, “mediaUrl”:“https: / / … / mediafileA.png”, “media”:“elseif image_param1=￥“Media File B￥””, “mediaUrl”:“https: / / … / mediafileB.png”

[0066] In this modified example, it is shown that when the variable (image_param1) is associated with the “media” tag in scenario information TBL122B and the value (media file A) is set, the media to be delivered as content will be “media file A”. It is also shown that when the variable (image_param1) is associated with the value (media file B), the media to be delivered as content will be “media file B”.

[0067] Media settings TBL122D is a list of media. For example, media settings TBL122D displays a list of media filenames as the media list.

[0068] Since the CDN registration information 123 is the same as in the embodiment described above, its description is omitted.

[0069] Here, the processing performed by the distribution server 10 in this modified example will be explained using Figure 10 (Figures 10A and 10B). Figure 10 is a diagram illustrating the processing performed by the distribution server 10 according to the modified example of the embodiment.

[0070] Figure 10A shows the process flow for registering scenario-related information in the scenario DB 122. As shown in this figure, in the distribution system 1, scenario definition information 120 and multiple media information 121 (media information 121-1, 121-2, ...) are notified in advance by, for example, a company, as content-related information D1.

[0071] The scenario registration unit 130 uses information D1 (scenario definition information 120 and media information 121B) to generate information to be registered in the scenario DB 122 (scenario information TBL 122B and media setting TBL 122D).

[0072] The scenario registration unit 130 generates scenario information TBL122B and media setting TBL122D using the scenario definition information 120 and the URLs issued for each media. In this modified example, the scenario information TBL122B includes information such as the following. "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:“if image_param1=￥“Media File A￥””, “mediaUrl”:“https: / / … / mediafileA.png”, “media”:“elseif image_param1=￥“Media File B￥””, “mediaUrl”:“https: / / … / mediafileB.png” In this modified example, the scenario information TBL122B includes the text of the text T generated in accordance with the scenario definition information 120, as well as a variable indicating the media to be combined with this text. Specifically, it is indicated that if the variable (image_param1) is set to the value (media file A), the media to be delivered as content will be "media file A". Similarly, if the variable (image_param1) is set to the value (media file B), it is indicated that the media to be delivered as content will be "media file B". The scenario registration unit 130 stores the generated scenario information TBL122B in the scenario DB122. Furthermore, the scenario registration unit 130 generates a list of media that can be set as a variable (image_param1) in the scenario information TBL122B, and stores the generated list in the scenario DB122 as media setting TBL122D.

[0073] Figure 10B shows the flow of the content distribution process. The distribution data acquisition unit 131 acquires distribution data D3. Distribution data D3 contains information related to distribution, such as "Distributed on 2024 / 8 / 1 at 12:00" indicating the transmission date and time, and a list of telephone numbers to be distributed. It also contains information specifying the scenario to be used for distribution, and a name indicating the media to be distributed in association with the telephone number (media file A or media file B). In this diagram, distribution data D3 indicates that media file A is distributed to the user with the telephone number (090XXXX). It also indicates that media file B is distributed to the user with the telephone number (080YYYY). The distribution data acquisition unit 131 stores the acquired distribution data D3 as distribution personal information TBL122A in the scenario DB122.

[0074] The distribution processing unit 132 generates a distribution scenario D4 using the information stored in the scenario DB 122 (scenario information TBL 122B and distribution data D3). The distribution processing unit 132 generates a scenario D4 according to the type of media to be distributed.

[0075] Specifically, the distribution processing unit 132 obtains the name of the media (media file A) set for the telephone number (090XXXX) from the distribution data D3. The distribution processing unit 132 uses the obtained name (media file A) as an argument to the scenario information TBL122B to generate scenario D4-1, which distributes content combining text and media file A to the telephone number (090XXXX). Scenario D4-1 includes information such as the following: “userContact”:”090XXXX”, "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafileA.png”}

[0076] Furthermore, the distribution processing unit 132 obtains the name of the media (media file B) set to the telephone number (080YYYY) from the distribution data D3. The distribution processing unit 132 provides the obtained name (media file B) as an argument to the scenario information TBL122B, thereby generating scenario D4-2, which distributes content combining text and media file B to the telephone number (080YYYY). Scenario D4-2 includes information such as the following. “userContact”:”080YYYY”, "title": "Notice of Usage Fees", “description”:“This month’s usage fee is…”, “media”:{“mediaUrl”:“https: / / … / mediafileB.png”}

[0077] As described above, the distribution server 10 according to the modified embodiment includes a storage unit 12 that stores a media setting TBL122D. The media setting TBL122D is a list of media to be distributed. The scenario registration unit 130 generates scenario information TBL122B that specifies any of the media shown in the media setting TBL122D using variables. The distribution processing unit 132 obtains distribution data D3 (distribution data in which the media to be distributed is specified). The distribution processing unit 132 identifies variables corresponding to the media specified as the distribution target by referring to the media setting TBL122D. The distribution processing unit 132 generates scenario D4 by using the identified variables as arguments to be given to the scenario information TBL122B. As a result, the distribution server 10 of the embodiment can distribute content that combines any of multiple media in the same text without increasing the operational load.

[0078] The distribution system 1 and distribution server 10 in the above-described embodiment may be implemented in whole or in part by a computer. In that case, the program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into the computer system and executed. The term "computer system" here includes hardware such as the OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into the computer system. Furthermore, the term "computer-readable recording medium" may also include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and those that hold programs for a certain period of time, such as volatile memory inside the computer system that acts as a server or client in such cases. The program may be for implementing a part of the functions described above, or it may be a program that can implement the functions described above in combination with a program already recorded in the computer system, or it may be implemented using a programmable logic device such as an FPGA.

[0079] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and includes designs and the like that do not depart from the spirit of this invention. [Explanation of Symbols]

[0080] 1…Distribution system 10…Distribution Server 20… Enterprise Servers 30… Telecommunications carrier server 40…Communication terminals 50…CDN 11… Communications Department 12...Storage section 13…Control Unit 120... Scenario definition information 121…Media Information 122...Scenario DB 122B...Scenario Information TBL (Scenario Information Table) 122C…Media Classification Table (TBL) 122D...Media Settings TBL (Media Settings Table) 130...Scenario Registration Department 131...Data Acquisition Unit 132…Distribution Processing Unit D4...Scenario (Scenario information for distribution)

Claims

1. A distribution server that delivers content according to the RCS (Rich Communication Services) scenario via a telecommunications carrier server, In combining text and media as content, a registration unit generates a scenario information table in which text is specified as an entity and media is specified as a variable, A distribution processing unit generates distribution scenario information that specifies text and media in concrete terms by providing a variable corresponding to the media designated as the distribution target as an argument to the scenario information table, and distributes the content corresponding to the generated distribution scenario information via the telecommunications carrier server. A distribution server equipped with the following features.

2. The system further includes a memory unit that stores a media classification table, which associates values ​​indicating the media classification with media that are candidates for distribution. The registration unit generates the scenario information table in which the media is specified by a variable indicating the classification of the media, The distribution processing unit obtains distribution data in which the classification of the media to be distributed is specified, identifies a variable corresponding to the classification of the media designated for distribution by referring to the media classification table, and uses the identified variable as an argument to the scenario information table to generate the text and the distribution scenario information that specifies the media corresponding to the classification of the media designated for distribution in physical form. The distribution server according to claim 1.

3. It further includes a storage unit that stores a media settings table showing a list of media to be distributed, The registration unit generates the scenario information table in which any of the media shown in the media setting table is specified by a variable. The distribution processing unit obtains distribution data specifying the media to be distributed, identifies variables corresponding to the media specified for distribution by referring to the media setting table, and generates the distribution scenario information by using the identified variables as arguments to be given to the scenario information table. The distribution server according to claim 1.

4. A distribution method performed by a computer that acts as a distribution server, which distributes content according to the RCS (Rich Communication Services) scenario via a telecommunications carrier server, The registration unit generates a scenario information table in which, when combining text and media as content, text is specified as an entity and media is specified as a variable. The distribution processing unit generates distribution scenario information that specifies text and media in concrete terms by providing a variable corresponding to the media designated as the distribution target as an argument to the scenario information table, and distributes the content corresponding to the generated distribution scenario information via the telecommunications carrier server. Distribution method.

5. A computer that acts as a distribution server, delivering content according to the RCS (Rich Communication Services) scenario via a telecommunications carrier server, In combining text and media as content, a scenario information table is generated in which text is specified as an entity and media is specified as a variable. By providing a variable corresponding to the media designated as the target of distribution as an argument to the scenario information table, distribution scenario information that specifies text and media in concrete terms is generated, and content corresponding to the generated distribution scenario information is distributed via the telecommunications carrier server. program.

Images