A browsing support system and program that simplifies the university's official website into an app to encourage repeat visits.

Abstract

To provide a Web site navigation deeply related to the interest and concern of a receiver side of information by timely and smoothly exchanging information without being limited by the kind of an information terminal apparatus of the receiver side and the various kinds of Web sites of sender sides.SOLUTION: A browsing support system assigns a tag code for each Web site of a sender, is capable of registering and storing selection conditions, URL, etc., according to a selection registration of the side of the sender regarding various kinds of information or image notifications corresponding to the code, and transmits information based on the registration and storage. When a condition of an attribute registration or an action history of a receiver is matched with the condition of information of the sender or when an external site is updated, information can be automatically transmitted to the side of the receiver without work of the sender. The side of the receiver performs self-registration and permission of push notification on a site of the side of the sender, thereby referring to individual various kinds of information or notifications corresponding to Web sites stored and added successively in the system through display that is made into Progressive Web Apps.SELECTED DRAWING: Figure 1

Description

Technical Field

[0002] ,

[0001] The present invention can place an icon on the home screen of an information terminal device of an information recipient and send a push notification as if the website has been pseudo-applied in the same way without taking the means of native appifying the website itself or pseudo-appifying it using Progressive Web Apps (hereinafter referred to as PWA), just by adding one tag to the website, regardless of the website specifications on the information provider side. When receiving information on the information terminal device, it can be smoothly referred to without being affected by differences in the OS of the recipient device or differences in versions, and enables website reference applications, etc. at appropriate timings and with appropriate contents, thereby providing a navigation function adapted to the needs of the recipient for the website and changing the website into an active tool. The present invention relates to a browsing support system.

Background Art

[0002] For example, assuming the information is related to university entrance exams, generally, when high school students are notified of detailed information or event schedules related to the exams, the organizers decide on the details and schedule and publicly announce them through media such as the university's official website, flyers, and brochures. Among these, the website is the most detailed way to convey information in real time, but for high school students, it is unclear when the information will be published, and they will not find all the necessary information at once; the information is usually added to the website gradually. Therefore, the target audience needs to access the website repeatedly to check for updates, as the timing of updates is unknown. For example, when University A decides on the dates for open campus events and entrance exam information sessions, it will post the dates on the university's official website, but often the announcement will only state that application methods and details will be posted on the site later. If it says "around which month," students can check the site again at that time, but even if they are interested when they first access the university's official website, they have to manage their own schedule for returning to the university's official website, and they may forget. Furthermore, without any indication of the approximate month, high school students wouldn't know when they should check it.

[0003] For information providers, one way to notify target audiences when new information is added to a website or to share useful information pages is to have them subscribe to an email newsletter. However, with email newsletters, recipients need to register their email address, and some may be hesitant to provide such personal information at an early stage of interest. Another means of communication is push notifications, which can send notifications to PCs and smartphones via a web browser. However, relying solely on web browser functionality for push notifications has a problem: depending on the OS and version of the recipient's device, images may not be displayed in the push notification, or the notification history may not be displayed, resulting in differences in display depending on the recipient's device.

[0004] Another method involves developing the sender's website as a native app and placing an icon on the recipient's home screen to send push notifications. However, this method incurs development costs, and requires submission to application stores such as Google Play (for Android) or the App Store (for iOS), which is a time-consuming and complicated process. Recipients also need to download and install the app from Apple's or Google's store. Furthermore, this method is only usable on smartphones and not on computers. Another method involves directly using Progressive Web Apps (PWA) technology to create a pseudo-app on the sender's website within the given environment. While this method eliminates the need for the sender to submit to an application store, and allows recipients to use the app without downloading it from Apple or Google's store, and also allows use on PCs, the PWA configuration varies depending on how the website is built, making a uniform approach impossible and increasing the workload and effort required from the sender's developers. Furthermore, whether it's a native app or a website directly converted into a PWA, both will be affected by changes in the specifications of the recipient's device's OS or changes in specifications due to new versions. This means that the sender's developers will constantly need to work on it, and maintaining the continuity of the service will become a burden.

[0005] Furthermore, while the website contains various useful information pages for high school students, the sheer volume of information and the scattered nature of the useful information across various menus make it difficult and burdensome for students to find pages that match their interests. Although the website has menus that categorize content, these menus can indicate directly relevant information, but they cannot indicate that a page contains indirectly useful information tailored to the individual student's needs.

[0006] Furthermore, when attempting to provide high school students with useful new information on an individual basis, the sender needs to continuously work on the task, and the effort involved for the sender becomes a major challenge.

[0007] Furthermore, cache control becomes a major challenge. If the sender's official website is directly converted into a pseudo-app using PWA while cache issues remain, there is a possibility that the recipient's information terminal screen may not be updated to the latest version of the sender's official website.

[0008] Generally, the following inventions addressing these problems have been recognized, and they describe methods for generating applications for mobile communication terminals. Furthermore, they are characterized by their ability to reduce the development burden on application developers. [Prior art documents] [Patent Documents]

[0009] [Patent Document 1] Japanese Patent Publication No. 2014-18244 [Overview of the project] [Problems that the invention aims to solve]

[0010] However, Reference 1 attempts to turn the website itself into a native app, which has the problem that while push notifications can be sent, they cannot be used on PCs. Furthermore, it is affected by changes in the specifications of the recipient's device's OS and changes in specifications due to new versions, which means that the sending developer will need to continuously work on it and will be burdened with management. There was no system that solved these problems and made it possible to transform a website into a proactive one by enabling requests to access the website at the appropriate time.

[0011] The objectives of the present invention are, firstly, to provide a system that integrates with a sender's website to support website browsing, enabling the recipient to easily and efficiently receive timely and constantly changing website information, regardless of the recipient's information terminal device or the specifications of the sender's website. Secondly, to enable the use of the same convenient functions regardless of the type of recipient's terminal by providing a dedicated system with certain convenient functions. Thirdly, to maintain customer attributes and devise ways to transmit information efficiently and effectively according to the recipient's access frequency and access trends.

[0012] Fourth, because the viewing support system is interposed between the receiver and the sender, the storage capacity of the sender's device is not affected when accumulating the receiver's history status, etc. Furthermore, while updates to operating systems such as Windows®, macOS®, and Android and iOS for mobile devices may affect the application's operation, when an update is planned, the specifications of the functions provided by this system will be reconfirmed, the extent to which the OS specification changes will affect the system will be verified, and the system will be adjusted to accommodate these changes. Since the system intervenes after these adjustments have been made, no action is required from the sender's system administrator, and the system will only need to handle changes in device specifications within this system to enable cooperation between the two parties. Fifth, the goal is to create a browsing support system that allows recipients to select information from the sender, register and modify categories of interest, and control the content of the information they receive. [Means for solving the problem]

[0013] The browsing support system of the present invention solves the aforementioned problems by assisting the sender's website through PWA-enabled icons and web pages generated by this system, without converting the sender's website itself into a PWA. The gist of this system is that it enables the sender to use PWA-enabled pseudo-app functions such as adding icons to the home screen and desktop screen and push notification functions.

[0014] Furthermore, in order to solve the aforementioned problems, the browsing support system of the present invention does not convert the sender's website itself into a PWA, but rather incorporates means to support various information terminal devices and OS versions, as well as processing means to support all specifications of the sender's website. Therefore, regardless of the type of information terminal device the recipient uses, and regardless of the type of specifications of the sender's website, the system can easily and efficiently inform the recipient of the sender's website information, which changes as it happens.

[0015] Furthermore, in order to solve the aforementioned problems, the browsing support system of the present invention is characterized in that the system administrator of the sender's website only needs to set an individual tag code issued by this system, and it becomes possible to use a function that adds an icon to the home screen and desktop screen of the recipient's information terminal device from the website in which the tag code has been set.

[0016] Furthermore, since the browsing support system of the present invention can store and manage the recipient's attribute registration and action history within the system, it is possible to provide a function that enables website navigation tailored to the recipient's interests, thereby transforming the websites being used for browsing support into active tools.

[0017] Furthermore, the essence of the present invention is that by simply setting a single tag code on the sender's website, it can enable navigation to websites tailored to the recipient's interests, thereby transforming the website into an active tool.

[0018] Furthermore, the essence of the present invention is that the viewing support system is a system that does not require management by the sender's system administrator, as the sender is not affected by specification changes such as OS version upgrades of the receiver's information terminal equipment.

[0019] Furthermore, the browsing support system of the present invention addresses the problem that, in the case of push notifications provided by a device, images cannot be displayed in push notifications, particularly in the case of iOS Safari, and that differences in the information provided occur depending on the information terminal device used by the recipient. To solve this problem, the system provides a dedicated website page in addition to the push notification provided by the device, thereby enabling the original content of the push notification banner sent by the sender to be uniformly provided to the recipient, regardless of the information terminal device used by the recipient.

[0020] Furthermore, in the case of push notifications provided by devices, some devices may not display the notification history. If a history exists, unread push notifications can be checked later even if they are not checked immediately. However, if there is no history, information cannot be obtained unless the notification is checked immediately. The essence of the present invention is that the viewing support system creates a screen within the system that allows the recipient to refer to the history information of push notifications regardless of the recipient's information terminal device, and transmits it to the terminal. In other words, in the case of push notifications from this system, the notification history is managed on a sender-specific screen generated by this system, so that there is no difference in the services that the recipient can use depending on the device.

[0021] Furthermore, the browsing support system of the present invention displays a mark on the university's icon each time a push notification is delivered, and the mark remains displayed until the notification is read, thus preventing users from forgetting to read push notifications.

[0022] Also, in a normal Android PWA app, it is possible to refresh (update) by swiping down the screen, but this function is not available on the iPhone (registered trademark). Therefore, for users who keep the PWA app in the background without closing it, the system of the present invention implements a refresh function. When it is activated from the background, it compares the displayed notifications and data, and if there are differences, it automatically refreshes so as to prevent information differences due to the environment of the recipient's information terminal device.

[0023] In addition, to solve the above problems, the browsing support system of the present development saves the recipient's action status in a database, classifies the access status into categories, and can hold customer attributes that enable efficient and effective information transmission according to the frequency and access tendency for each category, and can transmit information by applying them.

[0024] In addition, to solve the above problems, the browsing support system provides a dedicated page for the recipient to select the sender's information and register or change the categories of interest.

[0025] In addition, to solve the above problems, the browsing support system can automatically transmit information from the sender side to the recipient side without the sender's operation when the conditions of the recipient's attribute registration and action history match the conditions of the sender's information.

[0026] In addition, to solve the above problems, when an external site is linked as content to the sender's website, the browsing support system can automatically transmit information from the sender side to the recipient side without the sender's operation when the conditions of the recipient's attribute registration and action history match the conditions of the external site's information when the external site is updated.

[0027] Furthermore, the sender displays a pop-up on their website inviting recipients to opt in to push notifications. Upon seeing this pop-up, the recipient grants the system permission to add an icon to their personal information terminal device and receive information notifications. This allows the PWA-enabled system icon to appear on the home screen and desktop screen of the recipient's information terminal device, enabling them to receive push notifications from the sender, and indicating the addition of information by marking the icon. [Effects of the Invention]

[0028] The present invention, through the aforementioned solution, allows the sender to determine the sending timing, recipient selection, and content simply by setting a tag code provided by this system on their own website and configuring the content to be sent to the recipient within this system. Furthermore, it enables the recipient to display a dedicated page icon identifying them without making any changes to their own website other than the tag code.

[0029] Regardless of the specifications of their own information terminal device, recipients will be able to view push notifications, including images. Even if their own information terminal does not have a function to view the history of push notifications, they will still be able to see the history of push notifications sent to this dedicated page. Moreover, the icon for the dedicated page, which displays the sender's name, will appear on the user's device's TOP screen without requiring them to download the sender's native app or even if the sender's dedicated application is not available, thus saving them time and effort.

[0030] Furthermore, while notification display and history may differ depending on whether the recipient's device is an iPhone (registered trademark), Android, or a PC, and the version of each OS, these will all be displayed in the most convenient way on the next screen after clicking the dedicated page, allowing users to receive the same convenient notifications regardless of the device they use.

[0031] In this way, the same content is sent and received effortlessly regardless of the sender's or receiver's specifications, which motivates the recipient to acquire information and enables the sender to smoothly and timely disseminate information as intended.

[0032] Similarly, the browsing support system of the present invention collects the recipient's attribute information, and by classifying and storing information on push notifications, access to the sender's website, and application status on the sender's website in a database, it becomes possible to give the website navigation functions tailored to the recipient's needs and transform the website into an active tool.

[0033] The browsing support system of the present invention can be used by anyone who owns a website in any industry as an information sender, and by anyone who owns an information terminal device such as a smartphone, PC, or tablet as a receiver. Furthermore, information senders can easily send their intended information in the form of notifications by checking or entering items according to the items provided by the system, such as the selection of notification content, target, and timing. [Brief explanation of the drawing]

[0034] [Figure 1] This is an explanatory diagram of the entire system according to one embodiment of the present invention. [Figure 2] This is an explanatory diagram illustrating the flow of push notification permission, mainly on the recipient side, according to one embodiment of the present invention. [Figure 3] This is a diagram illustrating the screen used to manage the sender-side application according to one embodiment of the present invention. [Figure 4] This is an explanatory diagram showing a message creation screen for creating and managing messages to be sent to a recipient, according to one embodiment of the present invention. [Figure 4-2] This is an explanatory diagram showing the screen when automatic distribution is selected in the message creation screen for creating and managing messages to be sent to recipients according to one embodiment of the present invention. [Figure 5]This is an explanatory diagram illustrating the creation of attribute information confirmation content as a licensor attribute information confirmation master for confirmation by the recipient according to one embodiment of the present invention. [Figure 6] This is an explanatory diagram showing a screen for managing licensor identification information in a push notification licensor database according to one embodiment of the present invention. [Figure 7] This is an explanatory diagram showing a screen for managing licensor attribute information in a push notification licensor database according to one embodiment of the present invention. [Figure 8] This is an explanatory diagram showing a screen for managing push notification banner click information in the action history of a push notification authorizer database according to one embodiment of the present invention. [Figure 9] This is an explanatory diagram showing a screen that records official website access information among the action information of licensors in a push notification licensor database according to one embodiment of the present invention. [Figure 10] This is an explanatory diagram showing a message creation screen for creating and managing reminder messages to be sent to recipients, according to one embodiment of the present invention. [Figure 11] This is an explanatory diagram showing the screen of the analysis unit according to one embodiment of the present invention. [Figure 12] This is an explanatory diagram showing a screen for managing the types of information category classification masters according to one embodiment of the present invention. [Figure 13] This is an explanatory diagram showing a management screen for classifying university official website URLs by information category according to one embodiment of the present invention. [Figure 14] This is an explanatory diagram showing a management screen for linked external website information from a university's official website, according to one embodiment of the present invention. [Modes for carrying out the invention]

[0035] The embodiments of the present invention will be described below with reference to Figures 1 to 14. The sender will be, for example, University A, and the receiver will be a high school student's mobile device. An overview of the entire system is shown in Figure 1. Figure 1 illustrates the flow in three blocks: the center shows the system side, the far right shows the relationship of which management database the input actions from the university side are registered in, and the left side shows the usage flow of a high school student as a user. At the very top right is item 134, which displays tag code 125 issued by the system side on the university site. In Figure 2, 201 shows the initial response from the university side, and then 202-217 show the relationship between the response of the receiving terminal and the system. Figure 3 shows the management details in application management 124 within the system of Figure 1. Even within a single university that disseminates information, it is possible to create multiple dedicated pages and manage them differently, and the basis for this is the application. At the application level, a push notification notification pop-up (112 in Figure 1) displayed on the university's official website, an explanatory screen for push notification recipients (113 in Figure 1), an icon to be set on the user's information terminal device (114 in Figure 1), and university-specific pages (115, 116 in Figure 1) are generated. Here, the link button area (301) corresponds to the three buttons 214 at the top of the university-specific page 212 screen in Figure 2.

[0036] Figure 4 shows the message creation screen for creating and managing messages sent to recipients. It also allows for the configuration of push notification messages that operate in conjunction with the push notification recipient database, particularly as shown in Figure 1, item 119. Checking the corresponding table 401 will target recipients possessing that attribute to receiving the message. Figure 4-2 is an explanatory diagram showing the screen when automatic distribution is selected on the message creation screen for creating and managing messages sent to recipients. Figure 5 shows the management of attribute information questionnaire items for push notification recipients at the university. Figure 6 shows the contents of the database that records user terminal identification information to identify push notification recipients. The user terminal identification information (601) is saved in the system when the user performs the permission action on their information terminal device as shown in Figure 2, item 206. Figure 7 shows the contents of the database that records information answered by users to the attribute information questionnaire set by the university in Figure 5, and this information is saved in the system. Figure 8 shows the contents of the database that records whether the recipient has taken action in response to the push notification, and this information is saved in the system.

[0037] Figure 9 also saves the access history of the recipient within the university's website. 901 saves the URL of the page on the university's official website that the push notification authorizer was accessing when they authorized push notifications, 902 saves the URL of the page on the university's official website that the push notification authorizer accessed, 903 saves a conversion tag indicating that the push notification authorizer requested materials from the university's official website, and 904 saves a conversion tag indicating that they applied for an open campus event. Access terminal information is saved along with the date and time of each set action. Figure 10 is the screen for creating and managing reminder messages to send to recipients. After push notification authorization, it is possible to uniformly send push notifications to authorizers after a certain period of time has elapsed since authorization, such as 3 days after authorization (1001 in Figure 10). This screen is used to guide users on how to use this service after push notification authorization and to promote its use. Figure 11 is the screen for analyzing information obtained through this browsing support system. Figure 12 shows the screen for registering categories as master data for classifying information from the university. Figure 13 shows the registration screen for indicating the relevant information content for each URL under the university's official website. Figure 14 shows the screen for managing information from external websites linked from the university's official website.

[0038] <Procedures for the university> The procedure for university operations is explained based on the university-side flowchart in Figure 1 and Figure 2 of the overview flowchart of the browsing support system. Universities using this system will be provided with a management screen specific to their university (Figure 1, 123). Universities can use this system simply by registering the application management (Figure 1, 124) and setting the application-specific tag code (Figure 1, 125) issued from the management screen on the university's official website (Figure 1, 134). This eliminates the need for continuous management by system administrators, thus reducing the workload.

[0039] When an application is registered in the application management (124), a push notification request pop-up (Figure 1, 112) is generated within this system. When the application-specific tag code (125) is set on the official website of University A (Figure 1, 134), the push notification request pop-up (Figure 1, 112) is displayed on the website (Figure 2, 203). When a visitor accesses the site and presses the push notification request button (Figure 1, 112, Figure 2, 203) (Figure 1, 101), the push notification request explanation screen (Figure 1, 113, Figure 2, 204) generated by this system is displayed, showing how to add the university icon to the home screen. Following the instructions, the PWA-enabled university name icon (Figure 1, 114) is added to the home screen of the information terminal device (Figure 1, 103, Figure 2, 205). When the PWA-enabled university name icon (Figure 1, 114) is opened, a PWA-enabled university-specific page push notification permission confirmation screen (Figure 1, 115; Figure 2, 206) generated by this system is displayed. If the user grants permission, the target application ID, user terminal identification information (Figure 6, 601), permission date and time, etc. are saved in the system's push notification permission database (Figure 1, 119) under permission identification information (Figure 1, 120; Figure 6). Thereafter, when the user operates a button, this user terminal identification information is used by this system to recognize that it is a specific user. In addition, the URL of the official website of University A accessed when permission for push notifications was granted is saved as the site access information official website page URL at the time of push notification permission in the action history (Figure 1, 122) of the push notification permission database (Figure 1, 119) (Figure 9, 901).

[0040] Since the saved user device identification information is recognized as indicating a consenter for push notifications, when accessing the official website of University A on the same user device, the pop-up prompting the user to opt in to push notifications will not be displayed, thus avoiding annoyance for the recipient. If the university has registered items to be confirmed for push notification entrants in the system's entrant attribute information confirmation master (Figure 1, 127, Figure 5), the user's information terminal will automatically display a PWA-enabled attribute information confirmation screen (Figure 1, 117) after push notification permission is granted (Figure 2, 208). When the user registers attribute information, it will be saved in the attribute information (Figure 1, 121, Figure 7) of the push notification entrant database (Figure 1, 119).

[0041] If the university has registered welcome message information in the Welcome Message section (Figure 3, 304-307) of Application Management (Figure 1, 124; Figure 3), a push notification banner (Figure 1, 118) of the push notification welcome message, automatically generated by this system, will be delivered as a push notification (Figure 1, 106; Figure 2, 210) at the same time as permission for push notifications is granted. When a push notification is delivered, an indicator will appear on the PWA-enabled university name icon (Figure 1, 114; Figure 2, 211) on the user's home screen, indicating that there is a new notification. When the university name icon is pressed, the PWA-enabled university-specific page (Figure 1, 116; Figure 2, 212) will open, and the welcome message will be displayed in the push notification history display area (Figure 2, 215) (Figure 2, 216). Even if the user does not check the push notification at the time it is sent, they can check it later (Figure 1, 107).

[0042] When the push notification for the welcome message (Figure 2, 210) or the push notification history for the university-specific page (Figure 2, 216) is clicked, the website page specified in Figure 3, 307, is displayed, and the user is navigated to a page on the university's official website that the push notification authorizer is expected to view (Figure 2, 217). Additionally, when the delivered push notification welcome message (Figure 1, 106, Figure 2, 210) or the welcome message displayed in the push notification display area of ​​the PWA-enabled university-specific page (Figure 1, 107, Figure 2, 216) is opened, it is saved as an action history in the push notification banner click information of the action history (Figure 1, 122) in the push notification authorizer database (Figure 1, 119) (Figure 8).

[0043] In addition to the welcome message sent immediately after a high school student grants permission for push notifications, it is also possible to register reminder messages that will be automatically delivered at a predetermined time interval after permission is granted (Figure 1, 128; Figure 10). For example, if you want to uniformly deliver push notifications to grantors after a certain period of time has elapsed since permission was granted (e.g., 3 days after permission was granted, as shown in Figure 10, 1001), you would register 3 in 1001. This can be used to guide recipients on how to use the service after they have granted permission for push notifications, and to encourage their use.

[0044] When a university updates its official website, it can register recipient attributes in the message management section of this system (Figure 1, 129; Figure 4), thereby sending push notifications to users as intended and informing them that the official university website has been updated. In this system, user terminal identification information, attribute information, and action history are linked (Figure 1, 119). Therefore, in addition to attribute information that users themselves have answered (Figure 1, 121), action history (Figure 1, 122) such as opening push notification messages (Figure 1, 108), viewing push notification history for university-specific pages (Figure 1, 109), accessing pages within the university's official website (Figure 1, 110), completing requests for materials within the university's official website, and completing applications for open campus events within the university's official website (Figure 1, 111) is stored in the database as the action history of a specific user, based on user device identification information (Figure 1, 120, Figure 6, 601). This makes it possible to directly notify users of updates on the university's official website that are likely to be of interest to them, based on data such as the user's action history, action categories, and user attributes. This enables personalized notifications that users need.

[0045] The university can send push notifications by selecting recipients for push notifications from the system's management screen based on the attribute information and action history of the recipients (401 in Figure 4), registering information categories (402) to classify the push notification content, the message title (403) to be displayed in the push notification, the message body (404), the image to be displayed (405), the URL of the linked page (406), the delivery date and time (407), and the display period (408). By selecting information categories (402) from those registered in the information category master in Figures 130 and 12, it is possible to analyze information on push notification banner clicks not only on a message-by-message basis but also by information category.

[0046] In addition to manually sending push notifications when needed, it is also possible to automatically send them when a pre-registered target page is updated (Figure 4-2). In the university official website URL information category classification in Figure 13, relevant information content is registered for each URL under the university official website, in accordance with the consenter attribute information confirmation master. By setting the attributes of the recipients, action history conditions, and message content to be notified for each URL, it is possible to automatically send push notifications whenever the content under each URL is updated. Furthermore, some university websites include links to external websites operated by third parties as part of their content, in addition to the information reflected on the university website itself. By registering these external websites as linked external sites (Figure 1, 132; Figure 14) and enabling the acquisition of update information from the management screen of the linked external sites, it is possible to automatically distribute updates whenever information on the linked external sites is updated.

[0047] The university can also use the analytics department (Figure 1, 133; Figure 11) to view user attributes, the category of the official website when push notifications are permitted, the number of clicks on category-specific push notification banners, the frequency of access to the official website by category, and the status of requests for materials and open campus applications. This allows the university to determine what information to provide, when to what target audience, and to whom it is most effective to notify users of updates to the university's official website. By specifying user attributes, the category of the official website when push notifications are permitted, the number of clicks on category-specific push notification banners, the frequency of access to the official website by category, and the status of requests for materials and open campus applications (Figure 4, 401), the university can set associated information, enabling more personalized and detailed notifications, motivating users to revisit the university's official website, and guiding them to effectively utilize the university's official website.

[0048] <Flow of information receipt from the high school student side> When the application-specific tag code (Figure 1, 125) is set on the official website of University A, a push notification request pop-up (Figure 1, 112; Figure 2, 203) generated by this system will appear on the website. When a high school student visits the official website of University A and clicks on the push notification request pop-up displayed on the website, a push notification request explanation screen (Figure 1, 113; Figure 2, 204) generated by this system will appear on their smartphone or computer. If the user follows the instructions on the push notification request explanation screen, a PWA-enabled university name icon (Figure 1, 114) generated by this system will be added to the home screen of the information terminal device (Figure 1, 103; Figure 2, 205). When the icon is opened, a PWA-enabled university-specific page push notification permission confirmation screen generated by this system will appear. A screen (Figure 1, 115; Figure 2, 206) is displayed, and once the user grants permission (Figure 1, 104), it is saved as permission identification information (Figure 1, 120) in the push notification permission database (Figure 1, 119), enabling the delivery of push notifications. A push notification banner (Figure 2, 210) generated from the welcome message information (Figure 3, 304-307) registered by University A in application management (Figure 1, 124) is delivered as a push notification, and the user can open the university's official website (Figure 2, 217) linked to the push notification banner. Even if the user does not check the push notification at the time it arrives, they can check the push notification history (Figure 2, 216) on the university-specific page (Figure 2, 212) generated by this system via the university name icon (Figure 2, 211), and open the university's official website (Figure 2, 217) linked to the push notification banner.

[0049] Furthermore, user terminal identification information is stored as the licensor identification information (Figure 1, 120) in the push notification licensor database (Figure 1, 119) of this system, and a PWA-enabled icon of the university name (Figure 1, 114) is set on the information terminal device. Therefore, it is possible to determine from the terminal information that the user of the information terminal device is a push notification licensor, and when accessing the university's official website after licensing for push notifications, the pop-up prompting users to request push notifications will not be displayed, thus avoiding inconvenience for the recipient.

[0050] After obtaining permission, the attribute information screen can be displayed (Figure 1, 117; Figure 2, 208). Attribute information items can be set in the university's management screen (Figure 1, 123) in the permissionee attribute information confirmation master (Figure 1, 127) (Figure 5). These include information categories of interest, preferred faculties and departments, preferred entrance examination methods, preferred academic fields, and questionnaires regarding information the recipient wants to receive (open campus events, entrance examination information, latest information on newly established faculties and departments). The attribute information confirmation screen is linked as a "My Page" on the university-specific page generated by this system (Figure 1, 116; Figure 2, 212) (Figure 2, 213), allowing for later registration and modification.

[0051] The university uses the attribute information (Figure 1, 121) and action history (Figure 1, 122) from the push notification consenter database (Figure 1, 119) to identify recipients (Figure 1, 129, Figure 4, 401) in the message creation and management screen, and to segment the content of push notifications. High school students can edit their responses to surveys related to their interests from the attribute information confirmation screen (Figure 1, 117) to ensure they receive information about the university's official website that is relevant to them. For example, if a high school freshman vaguely registered an interest in science and engineering fields at University A, but then in their second year, their interest shifted to a more specific faculty or department within science and engineering, and they changed their attribute information, University A could now provide push notifications to guide them to information related to the relevant faculty or department. This would include updates to the faculty information survey, news about faculty members in that department, and other information from more specialized sites that aren't specifically targeted at prospective students. This ability for recipients to control the information they receive is a key feature of this system.

[0052] When a user who has enabled push notifications accesses the university's official website, the URL of the page within the accessed website is obtained, and the high school student's action history is accumulated (Figure 1, 122). University official website URL information category classification (Figure 1, 131, Figure 13) categorizes the URLs within the university's official website into categories based on the type of information, for example, as shown in Figure 4, 409, general, event-related, entrance examination information, faculty research information, and news, according to the category types set in the information category classification master (Figure 1, 130). This makes it possible to manage the frequency of access by category. Since it becomes possible to accumulate the information that high school students need, it is also possible to notify them via push notification when there are updates to information related to that category on the university's official website, based on this category-specific access information.

[0053] Furthermore, the university-specific page generated by this system includes a "My Page" (Figure 2, 213), which is linked to a screen for modifying attribute information. This allows high school students to proactively add and change settings to receive push notifications about new information they are interested in. The attribute information confirmation screen also allows high school students to register questions, enabling universities to individually register answers and send push notifications along with the URL of the relevant university official website. Additionally, by inserting conversion tags into the application completion page for requesting materials or applying for an open campus event, the status of requests for materials and applications for open campus events can be accumulated as action history (Figures 1, 111; 122; 9, 903, 904). This makes it possible to deliver different notifications to those who have already requested materials or applied for an open campus event and those who have not. In this way, by enabling personalized notifications based on attribute information and high school students' action history, this browsing support system motivates high school students to revisit the university's official website, provides navigation functions tailored to the recipient's needs, and transforms the university's official website into an active tool.

[0054] As described above, the present invention is a browsing support system that enables information senders and receivers to easily send and receive required information in a timely manner, regardless of the specifications of their respective devices or websites. Because it can be used in any industry regardless of the type of information, it has industrial applicability. [Explanation of symbols]

[0055] 101 The act of clicking a pop-up prompting users to opt in to push notifications on the university's official website while using a user's device. 102 This shows the state where the explanation screen for users who wish to receive push notifications on their device is displayed, showing how to add the university name icon to the user's device's home screen. 103. Indicates that the university name icon is displayed on the home screen. 104. This indicates that the act of opening the university name icon and granting permission for push notifications was recorded, and that this act was recorded as information in the push notification grantor database's action history site access information, specifically in the URL of the official website page at the time of push notification permission. 105 This indicates that attribute information has been entered into the attribute information confirmation screen, and that this information will be added to the attribute information of the push notification consenter database. 106 This indicates that the user opened the welcome message received as a result of granting permission for push notifications, and that this action is recorded in the push notification banner click information of the action history in the push notification grantor database. 107 This indicates that the welcome message is also displayed in the history of the university-only page, and that even if the welcome message is opened from the history of the university-only page, that action will be recorded in the push notification banner click information of the action history in the push notification consenter database. 108. This indicates that the action of opening a received push notification was recorded, and that this action is recorded in the push notification banner click information of the action history in the push notification authorizer database. 109 This indicates that the received message is also displayed in the history of the university-only page, and that even if the message is opened from the history of the university-only page, that action will be recorded in the push notification banner click information of the action history in the push notification consenter database. 110. This indicates that a push notification authorizer accessed the university's official website, and that this action is recorded as information in the push notification authorizer database's action history, specifically in the URL of the university's official website accessed page. 111. This indicates that a push notification authorizer has requested materials or applied for an open campus event on the university's official website, and that this action is included in the material request / open campus application conversion tag information of the site access information in the action history of the push notification authorizer database. 112 203 Push notification notification prompt pop-up 113 204 Explanation screen for users who wish to receive push notifications 114 205 211 Icons of university names that have been converted to PWAs 115 206 Push notification permission confirmation screen in PWA format 116 212 PWA-enabled university-only page 117 208 213 PWA-enabled attribute information confirmation screen 118 210 Push notification banner 119 207 Push Notification Allowee Database 120 Push notification consenter identification information 121 Push notification consenter attribute information 122 Push Notification Allowee Action History 123. Indicates the scope of the management screen for each university. 124 Application Management 125 Application-specific tag codes 126. Information content at the application level. 127 Licensor Attribute Information Confirmation Master 128. Create and manage reminder messages. 129 Message creation and management 130 Information Category Classification Master 131 University Official Website URL Information Category Classification 132 External Link Site Information 133 Analysis Department 134 Application-Specific Tag Code Settings 201. Initial response by the university 202 Devices of visitors to the university's official website before permission is granted 212 PWA-enabled university-only pages displayed on users' devices 214. Link button to the official university website configured in Application Management 215 Push notification history display area 216 Push notification history 217 Pages on the university's official website that we would like push notification enablers to check out. 301 Link Button Area 302 Text to display in the pop-up for those who wish to receive push notifications. 303 Application-specific tags automatically generated based on input in the application management screen code 304-307 Welcome Message Specify the delivery method for push notifications (400). 401 Screen for specifying attribute information to target recipients of push notifications 402 Push Notification Information Category 403 Push notification banner message title 404 Push notification banner message body Image for displaying the 405 push notification banner 406 URL of the page that links to the push notification banner 407 Push notification delivery date and time 408 Push notification banner display period 409 Examples of information categories registered in the information category classification master 601 User terminal identification information 901 Save the URL of the page on the university's official website that the user who granted permission for push notifications was accessing when they granted permission for push notifications. 902 Save the URL of the page you accessed on the university's official website. 903 Save the conversion tag indicating that the request for materials was made from within the university's official website. 904 Save the conversion tag indicating an open campus application. 1001 Input field for the number of days since permission was granted for automatic delivery of reminder messages.

Claims

1. A browsing support system that acts as an intermediary between an information sender and a receiver, characterized in that, upon detecting the execution of an individual tag code issued by the system embedded in the sender's website, the system generates the necessary components for PWA (Progressive Web Apps), including a Web App Manifest and a Service Worker, without changing the specifications of the sender's website itself, and transmits them to the receiver's information terminal device as the sender's information device distribution means; and by absorbing operational differences caused by technical constraints for each OS version of the receiver's information terminal device through a compatibility adjustment process performed within the system, the system enables pseudo-app functions, including adding an icon to the home screen and receiving push notifications, to be executed on the receiver's information terminal device.

2. The browsing support system according to claim 1, characterized in that the sender simply sets an individual tag code issued by the system on their own website, the system generates an individual icon according to the OS of the receiver information terminal device, and makes the icon displayable on the home screen of the receiver information terminal device.

3. The system stores and manages the recipient's attribute registration and action history, and then processes the data based on the recipient's interests. The browsing support system according to claim 1, characterized in that it enables navigation of the corresponding website and can transform the support website into an active tool.

4. The browsing support system according to claim 1, characterized in that, when the conditions of the recipient's attribute registration or action history match the conditions of the sender's information, information is automatically transmitted from the sender to the recipient without any action from the sender.

5. The browsing support system according to claim 1, characterized in that, when the sender's website links to an external site as content, and the external site is updated, the sender can automatically transmit information to the recipient without any action from the sender when the recipient's attribute registration or action history conditions match the conditions of the information on the external site.

6. The browsing support system according to claim 1, which generates push notifications having images using the system and enables the content of push notification banners having images to be uniformly provided to recipients, regardless of the type of information terminal device used by the recipient.

7. The browsing support system according to claim 1, characterized in that, with respect to notifications created by the system and sent to the recipient's mobile terminal device, the sender manages the history of such notifications on a dedicated screen and sends a screen to the recipient's terminal device that allows the recipient to refer to the history information of push notifications without being affected by the recipient's information terminal device.

8. The browsing support system according to claim 1, characterized in that when activated from the background within the system, it compares the displayed notification with the data and automatically refreshes if there is a difference, thereby preventing information discrepancies due to the environment of the recipient's information terminal device.

9. The browsing support system according to claim 1, characterized in that when the recipient activates the PWA app from the background while the PWA app is running in the background without being closed, the system compares the notifications displayed in the system with the sent data and, if there is a difference, automatically refreshes and replaces the information with the new information.

10. The browsing support system according to claim 1, characterized in that it stores the recipient's action status in a database within the system, classifies the access status into categories, and enables the maintenance of customer attributes that allow information to be sent according to the frequency and access trends of each category, and enables efficient and effective information dissemination by applying these attributes.

11. The browsing support system according to claim 1, characterized in that it provides a dedicated page for the recipient to select information from the sender and register or change categories of interest.

12. The browsing support system according to claim 1, characterized in that by displaying a guidance pop-up on the sender's website, the recipient grants the system permission to add an icon to their personal information terminal device and receive information notifications, thereby displaying the PWA-enabled icon of the system on the home screen and desktop screen of the recipient's information terminal device, enabling them to receive push notifications from the sender, and indicating the addition of information by marking the icon.

13. A computer-executable program that assists in browsing a sender's website, which acts as an intermediary between an information sender and a receiver, characterized in that, upon detecting the execution of an individual tag code issued by the system embedded in the sender's website, the system generates components necessary for PWA (Progressive Web Apps), including a Web App Manifest and a Service Worker, without changing the specifications of the sender's website itself, and transmits them to the receiver's information terminal device as the sender's information device distribution means, and absorbs operational differences caused by technical constraints for each OS version of the receiver's information terminal device through a compatibility adjustment process executed within the system, thereby enabling pseudo-app functions, including adding an icon to the home screen and receiving push notifications, to be executed on the receiver's information terminal device.

Images