JP2002259334A - Network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system capable of transmitting information surely by the program of a browser. SOLUTION: In the case of transmitting information to the user B of a user terminal device U2 from the user A of a user terminal device U1, 1 the information is registered by designating the user B by accessing a control server. 2 The control server 5 records this information with a destination (user B). 3 When the user B of the user terminal U2 logs in the control server 5, the control server judges whether the logging-in user B exists at the recorded destination. 4 When it exists, link display showing the recording place of the information to the user terminal device U2. Based on this, the user B can obtain the information from the control server 5. Consequently, the user B knows that information addressed to him/herself arrives when he/she logs in the control server 5.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information transmission system, and more particularly to an efficient information transmission.

[0002]

2. Description of the Related Art Generally, mail or web is used for information transmission using a computer.

[0003] Information transmission via the web does not work well unless the user has a willingness to browse the web.

[0004] On the other hand, in information transmission by e-mail, every time the other party starts software for receiving e-mail, it is possible to notify that the e-mail has been sent.
Therefore, there is an advantage that information can be transmitted to the other party more reliably than in the case of the web.

However, in the case of mail, software for mail must be set up. For this reason, when browsing the web with the browser software, in order to check the mail, the mail software had to be started. Therefore, in the work using the browser software, there has been a problem that the cooperation is not always good.

An object of the present invention is to solve the above-mentioned problems and to provide a system capable of reliably transmitting information by a program such as a browser.

[0007]

(1) An information transmission system according to the present invention is an information transmission system including a plurality of terminal devices used by a user and a control server device. When transmitting the information to the destination user, the transmission information and the identification information of the transmission destination user are transmitted from the terminal device of the transmission source user to the control server device, and the control server device records the transmission information in a predetermined recording location. In addition, the identification information of the transmission destination user is recorded in association with the recording location of the transmission information, and the control server device checks whether the user is recorded as the transmission destination user every time the user of the terminal device receives the access. Judgment is made, and if recorded, a screen including a link display to the transmission information is transmitted based on the recording location of the transmission information, and the transmission destination user displays the screen on the terminal device. The screen on the basis of the link display, is characterized by obtaining the transmission information from the transmission source user.

[0008] Therefore, information can be transmitted without using a special mail program so as to be surely seen by the other party.

(5) The information transmission system of the present invention is characterized in that the control server device transmits a portal screen for accessing content to the terminal device and adds a link display to the portal screen. .

[0010] Since the link display to the transmission information is added to the portal screen, it is possible to reliably inform the other party that the transmission information has arrived.

(6) The information transmission system according to the present invention is characterized in that a group is set as a transmission destination, and the link display is displayed to users belonging to the group.
Therefore, it is easy to transmit information to all users belonging to the group.

(7) In the information transmission system according to the present invention, when the transmission destination user browses the transmission information, the notification banner relating to the transmission information is not displayed at the next access to the control server device. It is characterized by.

Therefore, it is possible to eliminate the waste that the user has already obtained the information which has already been browsed.

(8) The information transmission system according to the present invention is characterized in that the program on the terminal device side is a browser program.

Therefore, information transmission can be realized by a browser generally used for browsing.

(9) An information transmission method according to the present invention is an information transmission method using a plurality of terminal devices used by a user and a control server device, wherein a transmission source user transmits information to a transmission destination user. In the case of transmission, the transmission information and the identification information of the transmission destination user are transmitted from the terminal device of the transmission source user to the control server device, and the control server device records the transmission information in a predetermined recording place, and The identification information is recorded in association with the recording location of the transmission information, and the control server device determines whether or not the user is recorded as a transmission destination user every time an access is received from a user of the terminal device, If it has been recorded, a screen including a link display to the transmission information is transmitted based on the recording location of the transmission information, and the transmission destination user makes the link table of the screen displayed on the terminal device. Based on, it is characterized by obtaining the transmission information from the transmission source user.

Therefore, it is possible to transmit information without using a special mail program and without fail so that the other party can see the information.

In the present invention, "link display"
This refers to a display in which recording locations of transmission information are associated with each other. In the embodiment, a notification banner corresponds to this.

The "portal screen" is a screen for facilitating access to contents.

The "recording medium on which the program is recorded"
A recording medium such as a ROM, a RAM, a flexible disk, a CD-ROM, a memory card, a hard disk, or the like on which a program is recorded. In addition, the concept includes a communication medium such as a telephone line and a transport path. A CD-R that records a program to be executed after being installed on a hard disk or the like, as well as a recording medium such as a hard disk that is connected to the CPU and directly executes the recorded program.
This is a concept including a recording medium such as OM.

The "program" is a concept that includes not only a program directly executable by the CPU but also a source format program, a compressed program, an encrypted program, and the like.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS (1-1) Overall System Configuration and Overview FIG. 1b shows the overall configuration of an information transmission system according to one aspect of the present invention. User terminals U1, U2,... Are connected to the Internet 2. The control server 5 is also connected.

When transmitting information from the user A of the user terminal device U1 to the user B of the user terminal device U2, the user accesses the control server 5, specifies the user B, and registers the information. The control server 5 records this information together with the destination (user B). When the user B of the user terminal U2 logs in to the control server 5, the control server 5 determines whether the logged-in user B is at the recorded destination. If there is, a link display indicating the recording location of the information is transmitted to the user terminal device U2. Based on this, the user B can acquire information from the control server 5.

Therefore, at the time of login, the user B
You can know that you have received information.

(1-2) Overall System Configuration and Overview In the embodiment described below, the control server device 5 shown in FIG.
Is realized as a function of the application server 4 for generating a portal screen as shown in FIG. 1A. Therefore, a system for portal screen generation will be described with reference to FIG. 1a.

The Internet 2 has a user terminal device U
1, U2,... Un are connected. The Internet 2 is also connected to an application server device 4 that is an access control device and a content server device 8 that records a plurality of contents. Further, the application server device 4 can access a user database 6 that records user information. In this embodiment, the case where the Internet 2 is used as a network has been described, but the network may be configured by another network such as a LAN.

The user database 6 records whether each user has an access right to each content. The user accesses the application server device 4 from the user terminal device U1 and requests a portal screen for accessing the content of the content server device 8. Upon receiving this request, the application server device 4 checks the access right of the user to each content based on the user database 6. Next, the application server device 4 generates a link display for the content having the access right as a portal screen. The application server device 4 transmits the generated portal screen to the user terminal device U1.

The user can access the content of the content server device 8 based on the portal screen on which the link to the content to which the user has access right is displayed. Therefore, the content having no access right is not displayed, and the content can be easily accessed without causing confusion.

Also, the administrator who manages the application server device 4 automatically changes the portal screen only by changing the access right of each user recorded in the user database, so that the management is easy. .

(2) Hardware Configuration of Application Server Device 4 and the Like FIG. 2 shows a hardware configuration of the application server device 4. The application server device 4 includes a display 10, a keyboard / mouse 12, a communication circuit 14,
CPU 16, memory 18, hard disk 20, CD-
A ROM drive 22 is provided.

The communication circuit 14 is for communicating with the user terminal devices U1, U2,... Un and the content server device 8 via the Internet 2. The hard disk 20 stores an operating system (such as Microsoft Windows) 30 and an access control program 32. In addition, the ID of each user
And a user database 34 that records access rights and the like.

The access control program 32 realizes each function thereof in cooperation with the operating system 30. The access control program 32 is a CD-ROM
It is installed from the CD-ROM 24 via the drive 22. Note that the access control program 32 may be installed from another server device via the communication circuit 14.

The hardware configuration of the content server device 8 is the same as that of the application server device 4 described above. However, in the content server device 8, a plurality of contents are recorded on the hard disk 20 instead of the access control program 32 and the user database 34.

The user terminal devices U1, U2,.
The hardware configuration of n is the same as that of the application server device 4 described above. However, the user terminal device U1,
In U2... Un, a browser program for acquiring and browsing information from the application server device 4 and the content server device 8 instead of the access control program 32 and the user database 34 is recorded on the hard disk 20. I have.

(3) Contents of User Database FIG. 3 shows an example of an access right table recorded in the application server device 4. The access right table is
It constitutes a part of the user database. The access right table is provided with items of content ID, company ID, organization ID, post ID, user ID, and authority contents.

The access right for the content shown in the content ID column is a company ID, an organization ID, and a post I
D, given to the group or individual indicated in the user ID column. The content of the access right is determined by the content shown in the column of the right content.

In the first line of the access right table of FIG.
Company ID for content with content ID "1"
It is shown that the entire "15" company is given access rights as "readers". Therefore, all the employees of the company are given access rights as “readers” to the content.

The details of the content corresponding to the content ID are recorded in the content table shown in FIG. This content table is also recorded in the application server device 4 and forms a part of the user database.

In the content table shown in FIG. 4, for example, the content having the content ID “1” has the title “portal questionnaire” and the URL in the content server 8 is http: // www. , The icon of the content is recorded at http: // www... (Application server 4).

Company I in the access right table of FIG.
Details of the company corresponding to D are recorded in the company table shown in FIG. This company table is also recorded in the application server device 4 and forms a part of the user database. In the company table of FIG.
For example, it is indicated that the company with the company ID “15” is KCCS.

Organization I in the access right table of FIG.
The details of the organization corresponding to D are recorded in the organization table shown in FIG. This organization table is also recorded in the application server device 4 and forms a part of the user database. In the organization table of FIG.
For example, in a company with a company ID “15”, an organization ID
“2” indicates that it is the SI package section.

Post I in the access right table of FIG.
The details of the position corresponding to D are recorded in the position table shown in FIG. This post table is also recorded in the application server device 4 and forms a part of the user database. In the post table of FIG.
For example, in a company with a company ID “15”,
"1" indicates that the employee is a general employee.

The details of the user corresponding to the user ID in the access right table of FIG. 3 are recorded in the user table shown in FIG. This user table is also recorded in the application server device 4 and forms a part of the user database. In the user table of FIG. 8, for example, the user ID “1512” is “Eio Furuya”, belongs to the KCCS (company ID “15”), and belongs to the SI package section (organization ID “2”). (Post ID “1”).

If there is a portal screen request from the user terminal devices U1, U2,... Un (the first access is determined to be a portal screen request), the application server device 4 Then, the access right of the user is determined, and a portal screen for the user is generated and transmitted each time.

(4) Display Process of Portal Screen FIG. 9 is a flowchart of a process in which the application server device 4 generates and transmits a portal screen in response to a request from the user terminal device U1 (U2... Un). Show. In FIG. 9, the flowchart of the user terminal device U1 shows the processing of the browser program. The flowchart of the application server device 4 shows a part of the processing of the access control program.

First, the user terminal device U1 accesses a predetermined URL (URL of a portal site) of the application server device 4 (step S1). As a result, the application server device 4 returns a login screen as shown in FIG. The user inputs a company code, a user ID, and a password, and clicks the LOGIN button 40 with a mouse.

The application server device 4 receiving this performs user authentication (step S11). That is,
Based on a user authentication file (not shown) recorded in advance, it is determined whether the user ID and the password are correct. If the user is not a valid user such as a different password, the processing is stopped.

If it is determined that the user is a valid user, the application server device 4 acquires portal page information with reference to each of the tables (step S1).
2). Further, notification information is acquired (step S
13). Thereafter, a portal display screen based on the acquired portal page information and notification information is generated and transmitted to the user terminal device U1 (step S14). The user terminal device U1 displays a portal screen based on this (step S2).

(4-1) Acquisition of Portal Page Information FIGS. 11 to 13 show details of the portal page information acquisition processing in step S12. In this embodiment, based on the access right given to the user who has logged in based on the company, organization, and position to which the user belongs,
Each page of company, organization and job title is generated and sent. Therefore, for example, a portal screen as shown in FIG. 14 is displayed on the user terminal device U1. Pages 50 and 52 corresponding to KKCS (Company), SI Package Section (Organization), and General Employee (Position)
54 is displayed.

The details of the process of acquiring portal page information for displaying such a portal screen on the user terminal device will be described below.

First, C of the application server device 4
The PU 16 determines whether there is a user-defined page (my page) for the logged-in user (Step S1201). Here, description will be made on the assumption that a user-defined page has not been set. Therefore, the process advances to step S1203 to determine whether there is a setting related to page display. Here, too, the description will be given on the assumption that the settings relating to page display have not been made.
Therefore, the process proceeds to step S1205.

In step S1205, it is confirmed whether or not the content information of the user-defined page has already been acquired. Since there is no user-defined page, step S1
Proceed to 206. In step S1206, by referring to the access right table, it is determined what kind of content link is to be displayed on the default page.

In this embodiment, a company page is generated as a default page. Therefore, based on the user ID of the user who logs in (user ID is “1512”), the CPU 16 acquires the company ID “15” of the user from the user table of FIG. Further, with reference to the access right table of FIG. 3, contents to which the access right is given to the company ID “15” are extracted. In FIG. 3, content IDs “1” and “2” are extracted. Further, the CPU 16 acquires the title, URL, and icon URL of the extracted content with reference to the content table.

As described above, the CPU 16 stores the content information of the company page (default page) in FIG.
5, and is recorded on the hard disk 20.
The content information of the company page includes information of content that can be accessed based on the access right given to the company to which the user belongs.

Upon acquiring the content information of the default page, the CPU 16 determines whether the user Eio Furuya (user ID “1512”) belongs to any organization (step S1208 in FIG. 12). As shown in FIG. 8, the process belongs to the SI package section (organization ID “2”), and thus the process proceeds to step S1209. Step S120
In 9, it is determined whether or not the content information of any page has already been acquired. As described above, since the content information of the company page has already been acquired, the process advances to step S1211 to acquire the tab title of the organization page. That is, the content information included in the organization page is not acquired. Therefore, as the information of the organization page, only the title of the tab is described as shown in FIG.

In the same manner as described above, only the tab information of the post page relating to the post of the user is described and recorded on the hard disk 20 as shown in FIG. 17 (steps S1212, S1213, S1215).

Thereafter, in step S1216, it is determined whether or not the number of page information is zero. When the number of page information is 0, that is, when there is no information of a page to be displayed as a portal screen, content information of a default page (company page) is acquired (step S1217). Here, since the number of page information is not 0, the page information acquisition process ends.

(4-2) Display of Portal Screen The portal page information generated as described above (FIG. 1)
5 to 17), portal screen information is generated and transmitted in step S14 in FIG. When the screen is generated, a predetermined format such as the number of icons displayed in one line on the page screen is used. When the portal screen information is transmitted, a portal screen as shown in FIG. 14 is displayed on the user terminal device U1.

On the portal screen, the company name “KCCS” is displayed in the tab portion of the company page 50 in accordance with the information on the company page in FIG. In addition, icons and titles of contents to which the user has access right by belonging to the company are displayed. Each icon is associated with the URL of the content. Therefore, the user can browse the content of the content server device 8 by clicking the icon with the mouse.

In the portal screen of FIG. 14, only the titles of the tabs, “SI package section” and “general employee” are displayed on the organization page 52 and the post page 54. With this tab, the user can easily grasp the existence of the organization page 52 and the post page 54.

FIG. 18 shows the processing of the access control program when the user clicks the post page 54 with the mouse on the portal screen of FIG. The CPU 16 of the application server device 4 determines which page the clicked tab (that is, the requested page) is. Here, since it is the post page, the process proceeds to step S20 via steps S15, S17, and S19. In step S20, the content information of the post page is acquired based on the access right table (FIG. 3). In other words, page information including the content information as shown in FIG.
The data is recorded on the hard disk 20.

After that, the CPU 16 regenerates the portal screen based on the page information,
1 (step S23). As a result, FIG.
Is displayed on the user terminal device U1.

(5) Access to Contents from Portal Screen FIG. 20 shows a flowchart when the user clicks an icon on the portal screen. First, the user terminal device U1 transmits a request for the content to the content server 8 with the URL of the clicked content (step S3). In response to this, the content server device 8 inquires of the application server device 4 whether or not the user has authority (access right) for the process to be performed on the content (step S101). That is, the content server device 8 transmits to the application server device 4 the accessed user ID, the requested content ID, and the processing content requested by the user (content browsing only, content rewriting, etc.).

The application server device 4 having received this determines whether or not the user has the right to perform the process on the content with reference to the access right table of FIG. If the authority content of the access right table is "Reader", the user has the authority to view the content. In addition, the "editor" has the authority not only to browse but also to rewrite contents.

The application server device 4 transmits to the content server device 8 the presence or absence of the authority obtained by referring to the access right table (step S25). When the content server device 4 obtains a response indicating that the process is authorized, the content server device 4 transmits the requested content (or the result of the process) to the user terminal device U1 (steps S102 and S103). If an answer without authority is obtained, a display to that effect is transmitted to the user terminal device U1 (steps S102, S104).

Therefore, if the user has the authority, the content of the content is displayed on the user terminal U1 (step S4).

Thereafter, every time a request for a process (browsing, rewriting, etc.) is made, the content server device 8 inquires of the application server device 4 whether or not the user has authority for the process, and then executes the process. Like that.

As described above, the access right table used at the time of generating the portal screen can also be used for grasping the authority at the time of browsing, etc., which are frequently found in the contents.

(6) Setting and Displaying My Page In the above description, a predetermined display format is used for a page. However, this embodiment allows the user to define the format of the page. In addition, the user can set a page customized for himself / herself, separately from the company, organization, and position.

FIG. 21 is a flowchart showing a process for setting a my page. The user terminal device U1 is a process of a browser program, and the application server device 4 is a process of an access control program.

First, a request for a my page setting screen is transmitted from the user terminal device U1 (step S5). In response to this, the application server device 4 refers to the access right table of FIG. 3 and extracts the content to which the user has access right (step S30). Next, the application server device 4 generates and transmits a setting screen according to the extracted content (Step S31). FIG. 22 shows an example of the setting screen. On this setting screen, only the content to which the user has access right is displayed as the content C to be selected.

The user sets which content icon is to be displayed on the My Page in accordance with the setting screen displayed on the user terminal device U1 (step S).
6). In this embodiment, as shown in FIG. 23, the arrangement order of icons of each content can be set. Further, it is possible to set a plurality of my pages, and as shown in FIG. 24, it is possible to set the display order (which one is the upper page). Also, as shown in the setting unit 150 in FIG.
The number of icons to be displayed in a row, the icon display method, and whether to display the default page (company page) can be set.

These settings are transmitted to the application server device 4 and recorded on the hard disk 20 (step S32). FIG. 25 and FIG. 26 show the page format table and the my page table recorded as described above. These tables constitute a part of the user database.

In the page format table of FIG. 25, the number of icons to be displayed in one line (column size), the icon display method, and the presence / absence of the default page display are recorded in association with the user ID. The display method of the icon is set as “no detailed display” and “with detailed display”.

In the my page table of FIG. 26, the title of the my page, the cell ID,
A content ID to be included in the page is recorded. The cell ID is an ID for distinguishing when a plurality of my pages are set.

The processing when the user with the user ID "1512" logs in when the settings are made as shown in FIGS. 25 and 26 will be described with reference to the flowchart in FIG.

First, C of the application server device 4
The PU 16 refers to the my page table of FIG.
It is determined whether or not the user has a My Page setting (step S1201). Here, since there is a my page setting, the content information of the my page is obtained from the table. In FIG. 26, the user ID
Two my pages are set in “1512”.
In this case, the content information of the page with the cell ID “1” is acquired, and only the title of the page with the cell ID “2” is acquired. The acquired page information is recorded on the hard disk 20.

Next, referring to the page format table of FIG. 25, it is determined whether or not there is a setting relating to page display for the user (step S1203).
Here, a page format is set for the user ID “1512”. Therefore, the page format is obtained, and the process proceeds to step S1204. In step S1204, it is determined whether the default page is set to be displayed. Here, since it is set to “display”, step S120
Go to 5.

Since the content information of the page has already been obtained, only the tab information of the default page is obtained (steps S1205 and S1207). Similarly,
Only tab information about organization page and post page is acquired.

The access control server device 4 generates a portal screen based on the page information and the page format, and transmits the portal screen to the user terminal device U1 (FIG. 9,
Step S14).

In the case where “detailed display” is set in the page format table, FIG.
As shown in FIG. 8, a description 300 of the content is also displayed.

(7) Access Right Setting / Change FIG. 29 is a flowchart showing a process for setting / changing the access right. First, a user who is an administrator requests an access right setting screen from the terminal device U2 to the application server device 4 (step S7). In contrast, the application server device 4
Determines whether the user has the authority to set the access right (step S35).

If the user has the right, the access right setting screen is transmitted (step S36). FIG. 30 shows an access right setting screen transmitted. In this figure, access rights for the entire organization (SI package section) are set and changed. In addition, as shown in FIG. 31, access rights can be set and changed for each organization for each content.

In FIG. 31, no authority is given to the management headquarters for the content “phone book” (NO ROL
E). The SI Package Division is authorized as an EDITOR. The "editor" can perform all processes of reading, writing, creating, and deleting. The "creator" can read, create, write and delete what he has created. "reader"
Can only read.

The setting / change contents of the access right are transmitted to the application server device 4, and according to the contents,
The access right table of FIG. 3 is updated (step S3
7).

(8) Notification Banner In this embodiment, a function of a notification banner is provided. As shown in FIG. 36, this is a function of displaying a notice banner 600 for the user to contact the user at the bottom of the portal screen. When you access the portal site, this announcement banner is displayed. The user can know the outline by the characters of the notification banner 600 and click the banner 600 to view the details.

(8-1) Setting of Notice Banner FIG. 32 is a flowchart showing the setting processing of the notice banner. Here, it is assumed that the notification banner is notified from the user terminal device U1 to the user terminal device U2.
The user terminal device U1 indicates processing of a browser program, and the application server 4 indicates processing of an information transmission program.

The user terminal U1, which is the notification source,
A request for setting a notice banner is requested from the application server device 4 (step S501). In response to this, the application server device 4 transmits a notification banner setting screen (step S601).

FIG. 33 shows a notice banner setting screen. As shown in the figure, items such as title, URL, type, notification type, target user, start date and time, end date and time, and image file name are input. Here, the title is the title of the announcement banner. U
The RL is the URL of the content in which the detailed contents of the notice are described. The type indicates whether to display the notification banner as text or an image. The target user is a user who is to be notified. The start date and time is the date and time when the display of the notice banner starts.
The end date and time is the date and time when the display of the notice banner ends. The image file name is an image file name when the notification banner is used as an image.

The user inputs the setting contents based on the setting screen and transmits the contents to the application server device 4 (step S502). The application server device 4 records this on the hard disk 20 as a part of the user database (Step S602). FIG.
The banner table recorded in this way is shown in FIG.

(8-2) Display of notification banner Based on the banner table recorded in this manner, a notification banner is displayed at the time of login in each of the user terminal devices U1, U2,. . That is, as shown in FIG. 9, acquisition of notice banner information (step S13) is performed following acquisition of portal page information (step S12), and a portal screen is generated based on the information (step S1).
4).

FIG. 35 shows a detailed flowchart of the process of acquiring the notice banner information (step S13). First, the CPU 16 of the application server device 4 refers to the banner table of FIG. 34, and determines whether there is notice banner information addressed to the logged-in user (step S611). That is, the ID of the logged-in user
Is included in the item of the destination user ID. If not, the acquisition processing of the notice banner information ends.

If there is notice banner information addressed to the user, the current date and time are obtained, and it is determined whether or not the present date is within the display period (step S612). That is, it is checked whether the current date and time is after the start date and before the end date. If it is not within the display period, the acquisition process of the notice banner information ends.

If it is within the display period, each item (notification banner information) of the banner table of FIG. 34 is obtained (step S613). Based on this information, a notice banner 600 is generated at the bottom of the portal screen (FIG. 9, step S14).

FIG. 36 shows a display example of the notice banner 600 on the portal screen. The contents of the banner table title are displayed as a notice banner. In addition, a link of the URL described in the item of the URL is attached to the notification banner. Therefore, the user clicks the notification banner 600 to
Detailed information can be obtained.

In the example of FIG. 36, the user “1512”
The travel expenses have been settled for the user "1514", and a notification to that effect is given as a notice banner. User "15
14 ", the details of the travel expense settlement can be known by clicking the notification banner 600.

(9) Other Embodiments In the above embodiment, as shown in FIG. 18, every time a tab is clicked, content information is acquired. However, in the processing of FIGS. 11 to 13, content information may be acquired and recorded for all pages. In this case, it is not necessary to refer to the access right table each time the tab is clicked.

In the above embodiment, the contents set in the page format table are also used as a display format for pages other than My Page (such as a company page). However, the format of my page and the format of other pages may be set separately. Further, the setting may be made for each page.

In the above embodiment, only the icon of the content to which the user has access right is displayed on the page. Further, the display mode such as the color and size of the icon may be changed according to the contents of the access right (editor, reader, etc.). Thereby, the user can easily recognize not only that he has the access right, but also the contents thereof.

[0100] Also, contents without access right may be displayed together with the page. However, it is preferable to change the display mode of the icons so that the presence or absence of the access right can be distinguished.

In the above embodiment, the page is provided for each group based on the position and organization. However, the page may be provided based on a group such as age, gender, and region.

In the above embodiment, the application server device 4 and the content server device 8 are configured as separate devices. However, both may be configured as the same device.

In the above embodiment, each time a request for processing (browsing, rewriting, etc.) is made, the content server device 8 inquires of the application server device 4 whether or not the user has authority for the processing. I have. However, only at the time of login, the application server 4 may be inquired about whether or not the user has the authority, and may not be inquired in the subsequent processing.

In the above embodiment, a setting is made so that a notice banner is displayed to an individual user. However, a notice banner may be displayed for a group such as an organization or a post.

[0105] The browsing may be recorded in the application server device 4 or the user terminal device, and the notice banner may not be displayed for the notice once viewed from the next login.

In the above embodiment, as shown in FIG.
The user inputs a notification banner setting. However, another application software may automatically set the notification banner. For example, a travel expense settlement program can set an announcement banner upon completion of travel expense settlement.

In the above embodiment, a notice banner is displayed together with the portal screen. However, it may be displayed together with another screen, or may be displayed alone as a notice banner.

[Brief description of the drawings]

FIG. 1a is a diagram showing an overall configuration of a system according to one aspect of the present invention.

FIG. 1b is a diagram showing an overall configuration of a system according to a main aspect of the present invention.

FIG. 2 is a diagram illustrating a hardware configuration of an application server device.

FIG. 3 is a diagram showing an access right table.

FIG. 4 is a diagram showing a content table.

FIG. 5 is a diagram showing a company table.

FIG. 6 is a diagram showing an organization table.

FIG. 7 is a diagram showing a post table.

FIG. 8 is a diagram showing a user table.

FIG. 9 is a diagram showing display processing of a portal screen.

FIG. 10 is a diagram showing a login screen.

FIG. 11 is a diagram showing a process of acquiring portal page information.

FIG. 12 is a diagram illustrating a process of acquiring portal page information.

FIG. 13 is a diagram illustrating a process of acquiring portal page information.

FIG. 14 is a diagram showing a portal screen.

FIG. 15 is a diagram showing content information of a company page.

FIG. 16 is a diagram showing information of an organization page.

FIG. 17 is a diagram showing information on a post page.

FIG. 18 is a diagram illustrating processing when a page tab is pressed.

FIG. 19 is a diagram showing a portal screen.

FIG. 20 is a diagram showing access to content.

FIG. 21 is a diagram showing processing for setting a My page.

FIG. 22 is a diagram showing a setting screen of a my page.

FIG. 23 is a diagram showing a screen for setting a my page.

FIG. 24 is a diagram showing a page format setting screen.

FIG. 25 is a diagram showing a page format table.

FIG. 26 is a diagram showing a my page table.

FIG. 27 is a diagram showing a portal screen.

FIG. 28 is a diagram showing a portal screen.

FIG. 29 illustrates an access right setting process.

FIG. 30 is a diagram showing an access right setting screen.

FIG. 31 is a diagram showing an access right setting screen.

FIG. 32 is a diagram showing a notice banner setting process.

FIG. 33 is a view showing a setting screen of a notice banner.

FIG. 34 is a diagram showing a banner table.

FIG. 35 is a diagram illustrating a process of acquiring notice banner information.

FIG. 36 is a view showing display of a notice banner.

[Explanation of symbols]

 2 ... Internet 4 ... Application server device 6 ... User database 8 ... Content server device U1, U2 ... User terminal device

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Tomoko Toyoda 22 Kyocera Communication System Co., Ltd., 5-22, Higashino Kitanoue-cho, Yamashina-ku, Kyoto-shi, Kyoto (72) Inventor Chikako Inoue Higashino Kitanoinoue, Higashino, Kyoto, Kyoto 5 Kyocera Communication System Co., Ltd. F-term (reference) 5B075 KK07 KK13 KK33 ND03 ND20 ND23 ND36 PP12 PP30 PQ02 PQ40 UU40 5B082 HA05 HA08 5B085 AE02 BC01 BE07 BG07 CA04

Claims (9)

[Claims] 1. An information transmission system comprising a plurality of terminal devices used by a user and a control server device, wherein when a transmission source user transmits information to a transmission destination user, a terminal of the transmission source user is provided. The transmission information and the identification information of the transmission destination user are transmitted from the device to the control server device, and the control server device records the transmission information in a predetermined recording place and records the transmission destination user identification information in the transmission information. The control server device determines whether or not the user is recorded as a transmission destination user every time the terminal device user accesses the terminal device. A screen including a link display to the transmission information is transmitted based on the recording location of the transmission destination user, and the transmission destination user determines the transmission source user based on the link display on the screen displayed on the terminal device. An information transmission system characterized by acquiring transmission information from a user. 2. A control server device capable of communicating with a plurality of terminal devices, comprising receiving transmission information and identification information of a transmission destination user transmitted from a terminal device of a transmission source user, and transmitting the received transmission information. The information is recorded in a predetermined recording location, and the identification information of the transmission destination user is recorded in association with the recording location of the transmission information. Each time the user of the terminal device receives an access, the user is recorded as the transmission destination user. A control server device that determines whether or not the information is recorded and, if recorded, transmits a screen including a link display to the transmitted information based on the recording location of the transmitted information. 3. A recording medium recording a control program for realizing, by using a computer, a control server device capable of communicating with a plurality of terminal devices, the transmission information being transmitted from a terminal device of a transmission source user. And receiving the identification information of the transmission destination user, and recording the received transmission information in a predetermined recording location, and recording the identification information of the transmission destination user in association with the recording location of the transmission information, and Each time access is received, it is determined whether or not the user is recorded as a transmission destination user. If so, a screen including a link display to the transmission information is transmitted based on the recording location of the transmission information. Recording medium for recording a control program for causing a computer to perform processing to be performed. 4. A control program for realizing, using a computer, a control server device capable of communicating with a plurality of terminal devices, the control information being transmitted from a terminal device of a transmission source user and a transmission information of a transmission destination user. Receiving the identification information, recording the received transmission information at a predetermined recording location, recording the identification information of the transmission destination user in association with the recording location of the transmission information, and receiving the access information from the user of the terminal device every time. Determining whether or not the user is recorded as a transmission destination user, and if so, transmitting a screen including a link display to the transmission information to the computer based on the recording location of the transmission information. Control program to make it work. 5. The system, apparatus, recording medium or program according to claim 1, wherein the control server device transmits a portal screen for accessing content to a terminal device, and the link to the portal screen. Features that add a display. 6. A system, apparatus, recording medium or program according to claim 1, wherein a group is set as a transmission destination, and said link display is displayed to a user belonging to said group. . 7. The system, apparatus, recording medium or program according to claim 1, wherein the transmission destination user browses the transmission information, and when the transmission destination user accesses the control server apparatus from the next time on, the transmission information is transmitted. It is characterized by not displaying links related to. 8. The system, apparatus, recording medium or program according to claim 1, wherein the program on the terminal device side is a browser program. 9. An information transmission method using a plurality of terminal devices used by a user and a control server device, wherein when a transmission source user transmits information to a transmission destination user, a terminal of the transmission source user is provided. The transmission information and the identification information of the transmission destination user are transmitted from the device to the control server device, and the control server device records the transmission information in a predetermined recording place and records the transmission destination user identification information in the transmission information. The control server device determines whether or not the user is recorded as a transmission destination user every time an access is received from a user of the terminal device. Transmitting a screen including a link display to the transmission information based on the recording location of the transmission source user, based on the link display on the screen displayed on the terminal device An information transmission method characterized by acquiring transmission information from a user.