Method and system for integrated control of widget visibility

Abstract

According to an embodiment of the present disclosure, a widget visibility integration control method is executed through a computing system and includes the following steps: identifying user permission information for a first widget; identifying business conditions related to visibility determination for the first widget; identifying whether there is a conflict between the first widget and a second widget different from the first widget based on the user permission information and the business conditions; if a conflict is identified, determining the priority order between the first widget and the second widget; and making the widget with the higher priority order visible and making the widget with the lower priority order invisible.

Description

Technical Field

[0001] This disclosure relates to a widget visibility integrated control method and system. More specifically, it relates to a widget visibility integrated control method and system that identifies conflicts between widgets based on user permission information and business conditions, determines a priority order, displays only widgets with high visibility on the screen, or further considers the caching of priority information and the existence of data, thereby effectively controlling the visibility of the user interface (UI). Prior Technology

[0002] In user interface (UI) environments, widgets are widely used as visual elements to provide various information and functions. This is especially true in web or mobile applications, where situations often arise where multiple widgets need to be displayed simultaneously or where widget visibility needs to be defined. Widget visibility is a crucial element in determining user experience (UX) and is directly related to system resource efficiency.

[0003] In existing UI systems, the logic for determining widget visibility is typically distributed across multiple code areas. This approach fails to effectively resolve conflicts between widgets, easily leading to duplicate code for visibility control and reduced system maintainability. Furthermore, the lack of logic for instantly confirming conflicts between widgets and determining their priority results in issues such as displaying widgets that shouldn't be shown or hiding important widgets.

[0004] Furthermore, unnecessary calculations are repeatedly performed during the process of updating widget visibility or checking for conflicts, excessively consuming system resources. This problem is more pronounced when applying complex user permission information or business conditions, potentially leading to decreased system performance. Additionally, failure to handle widgets with non-existent data can easily result in null reference exceptions (NPEs), thus reducing system stability.

[0005] Therefore, a centralized approach is needed to integrate and control the visibility of widgets, effectively resolving conflicts between widgets and saving system resources. Furthermore, a stable visibility control method is required to quickly determine the priority of widgets and proactively identify the presence of data to prevent system errors.

[0006] Prior technology documents

[0007] Patent documents

[0008] Korean Patent No. 10-2736563 Summary of the Invention

[0009] Problem to be solved:

[0010] The technical problem to be solved by some embodiments of this disclosure is to provide a method and system for integrating control of widget visibility based on user license information of a first widget and business conditions related to visibility determination.

[0011] According to some embodiments of this disclosure, the technical problem to be solved is to provide a method and system for integrating control of micro-device visibility based on identifying whether there is a conflict between a first micro-device and a second micro-device different from the first micro-device.

[0012] According to some embodiments of this disclosure, the technical problem to be solved is to provide a method and system for integrating control of micro-device visibility based on a determined priority order between a first micro-device and a second micro-device.

[0013] According to some embodiments of this disclosure, the technical problem to be solved is to provide a method and system for integrating the control of micropart visibility based on making high-priority microparts visible and low-priority microparts invisible.

[0014] It should be understood that the technical problems disclosed herein are not limited to those described above, and those skilled in the art can clearly understand other unmentioned technical problems through the following explanation.

[0015] The technical solution of the present invention is as follows:

[0016] To address the aforementioned technical problems, a widget visibility integration control method executed through a computing system according to an embodiment of this disclosure may include the following steps: identifying user permission information for a first widget; identifying business conditions related to visibility determination for the first widget; identifying whether there is a conflict between the first widget and a second widget different from the first widget based on the user permission information and the business conditions; if a conflict is identified, determining the priority order between the first widget and the second widget; and making the widget with the higher priority determined to be visible and making the widget with the lower priority determined to be invisible.

[0017] According to one embodiment, the widget visibility integration control method may further include the following steps: storing the determined priority order in a cache memory; and using the data stored in the cache memory to determine the visibility of a third widget.

[0018] According to one embodiment, the widget visibility integrated control method can simultaneously make widgets with a higher priority visible and widgets with a lower priority invisible.

[0019] According to one embodiment, the microdevice visibility integrated control method may further include the following step: identifying whether data exists for the first microdevice.

[0020] According to one embodiment, the step of determining the priority order may include the following steps: identifying the most recent update time of the first micro-device and the second micro-device; and determining the priority order based on the identified most recent update time of the first micro-device and the second micro-device.

[0021] To address the aforementioned technical problems, an integrated control system for widget visibility executed by a computing system according to an embodiment of this disclosure includes: one or more processors; and a memory storing a computer program executed by the one or more processors. When the computer program is executed, the one or more processors perform the following operations: identifying user permission information for a first widget; identifying business conditions related to visibility determination for the first widget; identifying whether there is a conflict between the first widget and a second widget different from the first widget based on the user permission information and the business conditions; if a conflict is identified, determining the priority order between the first widget and the second widget; and making the widget with the higher priority determined to be visible and making the widget with the lower priority determined to be invisible.

[0022] According to one embodiment, the processor can also perform the following operation: identifying whether data exists for the first microdevice.

[0023] According to one embodiment, the processor can also perform the following operations: storing the determined priority order in a cache memory; and using the information stored in the cache memory to determine the visibility of the third microdevice.

[0024] According to one embodiment, the process simultaneously makes the micro-parts with higher priority visible and makes the micro-parts with lower priority invisible.

[0025] According to one embodiment, the operation of determining the priority order may include the following operations: identifying the most recent update time of the first micro-device and the second micro-device; and determining the priority order based on the identified most recent update time of the first micro-device and the second micro-device. Simple Explanation of the Diagram

[0026] Figure 1 is a diagram illustrating a micro-parts visibility integrated control system according to one embodiment.

[0027] Figure 2 is a diagram illustrating various micro-devices displayed on a user terminal according to an embodiment of the present disclosure.

[0028] Figure 3 is a diagram related to a conflict with a microdevice according to an embodiment of the present disclosure.

[0029] Figure 4 is a diagram illustrating a widget displayed based on service conditions according to an embodiment of this disclosure.

[0030] Figure 5 is a flowchart illustrating a process for determining the visibility of a specific micro-part in an embodiment of this disclosure.

[0031] Figure 6 is a flowchart illustrating the sequence of a micro-device visibility integration control method according to an embodiment of the present disclosure.

[0032] Figure 7 is a flowchart illustrating the sequence of a widget visibility integration control method according to another embodiment of this disclosure.

[0033] Figure 8 is a flowchart illustrating the sequence of a micro-device visibility integration control method according to yet another embodiment of this disclosure.

[0034] Figure 9 is a flowchart illustrating the detailed sequence of steps S640 according to an embodiment of the present disclosure.

[0035] Figure 10 is a block diagram illustrating the hardware structure of a computing device for integrated control of microdevice visibility according to an embodiment of the present disclosure. Implementation

[0036] The preferred embodiments of this disclosure are described in detail below with reference to the accompanying drawings. The advantages and features of this disclosure, as well as the methods for achieving these advantages and features, will become apparent from the accompanying drawings and the embodiments described below. However, this disclosure is not limited to the embodiments described below, but can be implemented in various forms. These embodiments are intended only to make the disclosure more complete and to fully inform those skilled in the art of the scope of this disclosure, which is defined only within the scope of the claims.

[0037] When assigning element symbols to the technical features in the various figures, it should be noted that for the same technical feature, even if it is indicated in different figures, the same technical feature should have the same element symbol as much as possible. Furthermore, when describing the embodiments of this disclosure, detailed descriptions of related well-known structures or functions will be omitted if they are deemed to obscure the essence of the embodiments of this disclosure.

[0038] Unless otherwise defined, all terms (including technical and scientific terms) used in this specification are to be used in the sense commonly understood by one of ordinary skill in the art to which this disclosure pertains. Furthermore, terms defined in commonly used dictionaries should not be interpreted ideally or excessively unless explicitly defined otherwise. The terminology used in this specification is for describing embodiments and not for limiting the invention. In this specification, unless specifically stated otherwise, singular forms also include plural forms.

[0039] Furthermore, when describing the technical features of the embodiments disclosed herein, terms such as first, second, A, B, (a), and (b) may be used. These terms are used only to distinguish technical features from other technical features, and the nature, order, or sequence of the corresponding technical features are not limited by these terms. When a technical feature is described as "connected," "coupled," or "connected" to another element, that technical feature may be directly connected or connected to that other technical feature, and each technical feature may also be "connected," "coupled," or "connected" to another technical feature.

[0040] The use of "comprises" and / or "comprising" in this specification does not preclude the presence or addition of more than one other technical feature, step, operation, and / or element.

[0041] In this disclosure, a widget, as a single information display unit constituting a user interface (UI), is a concept that includes elements that may or may not be displayed on the screen based on specific conditions. Widgets visually provide various information, and their visibility can be dynamically controlled based on factors such as user permissions, business conditions, data availability, and conflicts between widgets. For example, each widget can display information such as discounts, guaranteed delivery times, and coupon application status, and can optimize the user experience by making only high-priority widgets visible.

[0042] In this disclosure, "visible" and "invisible" can be concepts used to determine the state of widgets displayed in a user interface (UI). A visible state is when a specific widget is displayed on the screen for the user to view visually, with the purpose of effectively conveying necessary information. Conversely, an invisible state represents the control over a specific widget, preventing it from being displayed on the screen, with the purpose of removing unnecessary information from the user, preventing confusion, and maintaining screen simplicity and efficiency. Visibility and invisibility can be dynamically determined based on various factors such as business conditions, user permissions, data availability, and the priority of widgets, thereby optimizing the user experience (UX) and effectively managing system resources.

[0043] Figure 1 is a diagram illustrating a micro-parts visibility integrated control system according to one embodiment.

[0044] User terminal 110 is a device that displays specific micro-devices identified by the micro-device visibility integrated control system 130 on a screen, and may include various electronic devices such as smartphones, tablets, and computers. User terminal 110 can receive information about visible micro-devices and display it on the display.

[0045] Users of user terminal 110 can view suitable widgets provided by widget visibility integrated control system 130 through the terminal screen. This allows users to access the information or functions they need and use widgets displayed on the screen based on business conditions or user permissions. This helps to eliminate unwanted widgets and effectively provide optimized information.

[0046] Network 120 is a communication network that connects user terminal 110 and widget visibility integrated control system 130 to realize data communication. Network 120 may include various communication technologies such as wired communication network, wireless communication network, mobile communication network, and Wi-Fi, and can transmit widget visibility information determined in widget visibility integrated control system 130 to user terminal 110.

[0047] The widget visibility integrated control system 130 can be a system that comprehensively considers factors such as user permissions, business conditions, whether there are conflicts between widgets, and whether data exists to determine the visibility and invisibility of a specific widget. This system selectively identifies widgets with high visibility and transmits them to the user terminal 110 via the network 120. Furthermore, the priority order between widgets can be stored in cache memory, minimizing resource consumption while effectively and instantly controlling widget visibility.

[0048] The widget visibility integrated control system 130 can maintain a consistent user experience (UX) and enable effective resource management.

[0049] Figure 2 is a diagram illustrating various micro-devices displayed on a user terminal according to an embodiment of the present disclosure.

[0050] 201 is the Discount Rate widget, which represents the percentage of the discount applied. It provides users with intuitive information about discount offers.

[0051] 202 is the Original Price widget, which represents the original price of the product. Users can compare this price with the price before the discount.

[0052] 203 is the Policy Popup widget, which can provide pop-up information about policies. For example, it could be a specific discount policy or offer conditions.

[0053] 204 is the SALE_PRICE widget, which can represent the selling price after applying coupons or discounts. It clearly shows the user the actual purchase amount.

[0054] 205 is the sales unit price (SALE_UNIT_PRICE) widget, which represents the selling price per unit. It helps to evaluate cost-effectiveness based on a single unit price.

[0055] 206 is the SALE_PRICE_TITLE widget, which can provide a title or description of the discounted price. It provides clear pricing information.

[0056] 207 is the Final Price widget, which represents the final price paid. It reflects the result of applying coupons or additional discounts, providing the user with the final purchase price.

[0057] 208 is the Final Price Title widget, which can provide a description or title for the final price. It is a widget used to clearly present the final payment information.

[0058] 209 is the Final Unit Price widget, which represents the final unit price. It allows users to easily view the final unit price.

[0059] 210 is a discount nudge widget that highlights additional discount information or offers to users. For example, it could be a notification such as "Additional coupons are available."

[0060] 211 refers to a specific UI element displayed on the screen based on specific business conditions. 211 could be a widget that displays a guaranteed delivery date and time when specific business conditions are met. For example, 211 could be a widget that displays "Guaranteed delivery before 7 AM tomorrow".

[0061] The widget visibility integrated control system 130 can integrate and control the visibility of widgets 201 to 211. This system can determine the visibility and invisibility of each widget by comprehensively considering user permission information, business conditions, and the existence of data. Furthermore, if it is determined that displaying multiple widgets simultaneously is unsuitable, it can be considered a widget conflict. In this case, the widget visibility integrated control system 130 can control visibility to prevent the display of widgets with lower priority from being displayed on the screen, and to display widgets with higher priority.

[0062] 201 to 211 are merely examples. In addition to the examples above, the widget visibility integrated control system 130 can also integrate and control the visibility of various widgets. The system can also dynamically adjust the visibility of additionally defined widgets or widgets that meet specific business needs.

[0063] Figure 3 is a diagram related to a conflict with a microdevice according to an embodiment of the present disclosure.

[0064] The initial price 310 represents the original price of the product, for example, it could display as 20,000 Korean Won. The first-level discount price 320 is the result of applying a first-level discount rate (not shown) to the initial price 310, for example, it could display as 18,000 Korean Won. The final price 330 is the result of applying a second-level discount coupon 340, for example, it could display as 16,460 Korean Won. The second-level discount coupon 340 is an element that provides an additional discount to the final price 330, for example, indicating that 1,540 Korean Won has been applied. The final discount rate 350 is the discount rate of the final price 330 relative to the initial price 310, for example, it could display as 17%.

[0065] In this structure, a conflict may arise between the primary discount rate (not shown) and the final discount rate of 350. For example, the primary discount price of 320 has a primary discount rate of 10% relative to the initial price of 310, but the final discount rate of 350 after applying the secondary discount coupon 340 is 17%. These two discount rates cannot coexist, which may confuse users.

[0066] Additionally, according to one embodiment, widget conflicts may occur in various forms. For example, when a price tag widget is displayed on the screen, a price title widget may not be displayed. This is because the two widgets provide the same or similar functions, and this setting is used to prevent duplicate information and keep the screen clean.

[0067] Additionally, widgets can be prioritized based on specific conditions. For example, if a particular product meets the conditions of Experiment A, the Real Discount Rate widget is displayed, while the conflicting Regular Discount Rate widget is not. This is to prevent information clutter and ensure that only high-priority widgets are visible, thus providing consistent information to the user.

[0068] When controlling widget visibility individually in an existing system, the aforementioned conflict can lead to delays due to additional processing. This not only degrades the user experience but also results in the unnecessary consumption of system resources.

[0069] Conversely, the micro-part visibility integrated control system 130 disclosed herein can instantly confirm whether a conflict exists. The system can instantly detect whether there is a conflict between micro-parts and consider the priority order to resolve the issue. For example, if the priority of the final discount rate 350 is higher than that of the first-level discount rate, then the micro-part can be made visible, while the first-level discount rate with a lower priority can be made invisible.

[0070] Making a widget visible and making it invisible can be performed simultaneously, so that the user terminal 110 can provide consistent information without confusion. Simultaneous execution of visibility and invisibility minimizes system resource consumption and enables efficient widget control.

[0071] Furthermore, the priority order between widgets can be determined in advance and set differently based on update time. For example, if the final discount rate of 350 is recently updated while a secondary discount coupon of 340 is being applied, the final discount rate can be prioritized over the primary discount rate. However, update time is only one factor in determining priority, and this disclosure is not limited to it. That is, in addition to update time, the priority order between widgets can also be determined based on various factors such as business conditions.

[0072] Figure 4 is a diagram illustrating a widget displayed based on service conditions according to an embodiment of this disclosure. Service conditions represent the criteria used to determine whether to display a particular widget. For example, service conditions may include whether a monthly subscription has been signed up, whether a coupon has been issued, and past purchase history, etc.

[0073] The information displayed on the screen of the user terminal 110 shown in Figure 4 can vary depending on the service conditions. Regardless of whether a monthly subscription has been subscribed, delivery information related widgets 410 can be displayed on the user terminal. For example, it may include regular delivery guarantee information.

[0074] Conversely, a widget 420 related to monthly subscription benefits can be displayed on the screen only if the user has not subscribed to a monthly subscription. This widget serves to inform the user about the additional benefits or special conditions available when subscribing to a monthly subscription. For example, it could be a paid membership delivery benefit such as a guarantee of delivery before 7 a.m.

[0075] Furthermore, although not shown in Figure 4, different widgets can be displayed depending on business conditions. For example, when a coupon is issued to a user, a widget indicating whether the coupon is applicable can be displayed on the screen. For products with a past purchase history, a widget guiding users to purchase again can be displayed on the screen.

[0076] Furthermore, there are various examples of making specific widgets visible or invisible based on business conditions. For instance, if the selling price is the same as the original price, the widget displaying the original price can be made invisible. This is to avoid confusion and minimize the waste of system resources by removing information that users don't need. As another example, if the product is fresh food or a product sold by a third party (3P), then specific widgets can be made visible, while some regular widgets can be made invisible. Thus, determining whether to display widgets based on the attributes or selling conditions of a specific product can also be an example of determining widget visibility based on business conditions.

[0077] Figure 5 is a flowchart illustrating a process for determining the visibility of a specific micro-part in an embodiment of this disclosure.

[0078] S510 is a step that determines whether data corresponding to a specific widget exists. In step S510, it checks whether the data or widget to be displayed on the user interface (UI) exists for that specific widget. If the data or widget to be displayed does not exist, the process proceeds to S501 and returns false. Furthermore, step S510 can prevent system errors such as Null Reference Exception (NPE) by identifying the existence of data in advance. Step S510 ensures the stability of the widget-integrated control system and minimizes unexpected errors.

[0079] Information associated with a specific widget may include, for example, guaranteed or estimated delivery dates and times, initial price, first-tier discount price, second-tier discount price, and information related to monthly subscription offers.

[0080] For example, if a secondary discount is not applied, secondary discount data may not exist, and if a secondary discount widget is displayed even though the secondary discount data does not exist, a No Entity Requirement (NPE) system error may occur during this process. A visibility integration control method according to an embodiment of this disclosure may include a step of identifying the presence of data, thereby preventing system errors such as NPEs that may occur in the above-described examples.

[0081] S520 is a step that verifies the user's permission level for a specific widget. This step checks whether the current user has the permission to identify or view information or data related to the specific widget. If no user permission is verified, the process proceeds to S501 and returns false. This prevents inaccessible data or widgets from being displayed in advance.

[0082] S530 is the step that confirms business conditions. In step S530, it can be determined whether a specific widget meets predefined business requirements. For example, if the business conditions determine that a widget is unsuitable for display, the process proceeds to S501 and returns false. This prevents widgets that do not meet the business conditions from being displayed.

[0083] S540 is the step to confirm whether there are conflicts between widgets. In step S540, it checks whether the widget to be displayed conflicts with other widgets. If a conflict occurs, the priority of the widgets is compared. If the priority of the widget to be displayed is lower than that of the conflicting widgets, the process proceeds to S501 and returns false. This effectively resolves widget conflicts, ensuring that only the appropriate widget is displayed on the user's screen without causing confusion.

[0084] S550 is the final step in determining the visibility of the widget. If the checks in steps S510, S520, S530, and S540 all pass, the process returns true and allows the widget to be visible. This allows the corresponding widget to be displayed on the screen of the user terminal 110.

[0085] S501 is the step that occurs when any condition in any of the steps fails. In this step, the process returns false and determines that the visibility of the widget is not allowed. The S501 step serves to prevent the display of unwanted or potentially erroneous widgets.

[0086] Thus, Figure 5 illustrates the process of determining the visibility of a widget by checking various conditions such as the existence of data, user permissions, business conditions, and whether there are conflicts between widgets, and accurately determining whether to display the widget based on the results of each step.

[0087] Meanwhile, although Figure 5 shows the sequential execution of steps S510 to S540, this is for illustrative purposes. The process for determining the visibility of a specific micro-part according to this disclosure can be performed without being restricted by the order of steps S510 to S540.

[0088] Figure 6 is a flowchart illustrating the sequence of a micro-device visibility integration control method according to an embodiment of the present disclosure.

[0089] Step S610 is the step of identifying user permission information. This step confirms whether the current user has permission to access information or functions of a specific widget. User permission information can be set differently based on the user's login status, level (e.g., regular user, paid member), role, etc. For example, if there are information or functions accessible only to users with paid memberships, the relevant widget can be made invisible to regular users who do not have permission. This prevents the display of unwanted information.

[0090] Step S620 is the step of identifying business conditions related to visibility determination. Business conditions can serve as important criteria for determining whether to display a widget. For example, coupons can be issued based on whether a discount is applied, or specific widgets can only be displayed when discount conditions are met. Additionally, promotional widgets can be displayed only to users who have not subscribed to a monthly subscription based on their monthly subscription status, and specific widgets can be made invisible based on the attributes of a particular product, such as fresh produce or products sold by third parties (3Ps). For products with a past purchase history, repeat purchase recommendation widgets can be displayed. The widget visibility integrated control system 130 can instantly confirm such business conditions and determine whether to display a widget accordingly.

[0091] Step S630 is a step to identify whether there is a conflict between the first widget and the second widget. A conflict between widgets can indicate a situation where they are not suitable to be displayed simultaneously on the same screen. For example, if the price tag widget is displayed at the same time as the price title widget, it may cause user confusion and can therefore be judged as a conflict. Additionally, if the actual discount rate widget is displayed according to specific experimental conditions (e.g., Experiment A), the regular discount rate widget may be invisible. The widget visibility integrated control system 130 can identify whether there is a conflict between widgets as described above, creating criteria for determining visibility and invisibility in the next step.

[0092] Step S640 is the step of identifying the priority order between the first and second widgets. In this step, it determines which widget to display first if a conflict is identified. Priority can be set according to various criteria. For example, the most recently updated widget may have a higher priority, or a widget providing more important business information may have a higher priority. Additionally, based on user permissions or specific conditions, widgets providing more meaningful information to the user may be displayed first. The widget visibility integrated control system 130 can comprehensively judge these criteria to determine the widget priority order.

[0093] Step S650 is a step that makes higher-priority widgets visible and lower-priority widgets invisible. In this step, the widget visibility integrated control system 130 can simultaneously perform visibility and invisibility. For example, if the final discount rate widget has a higher priority, only that widget can be made visible, while the first-level discount rate widgets can be made invisible. Such simultaneous execution prevents clutter on the user's screen and minimizes unnecessary resource consumption.

[0094] Thus, Figure 6 illustrates the process of controlling the visibility and invisibility of widgets by comprehensively evaluating user permission information, business conditions, whether there are conflicts between widgets, and priority. The widget visibility integrated control system 130 can improve the user experience (UX), avoid providing unnecessary information, and effectively manage system resources.

[0095] Figure 7 is a flowchart illustrating the sequence of a widget visibility integration control method according to another embodiment of this disclosure.

[0096] Step S710 is a step that stores the determined priority order information in cache memory. Step S710 can record the priority order of the micro-devices determined in previous steps (S610~S650) in cache memory. Therefore, duplicate calculations can be prevented when determining the visibility of the same micro-devices, and visibility can be effectively controlled in subsequent steps.

[0097] Step S720 determines the visibility of a third micro-device using data stored in cache memory. In step S720, the visibility of the third micro-device is determined by referring to cache priority information. At this point, the third micro-device can be a different micro-device from the first or second micro-device. Based on steps S710 or S720, the computational resources required to determine visibility can be reduced, and the visibility of micro-devices can be determined quickly.

[0098] Thus, steps S710 and S720 in Figure 7, as additional steps related to steps S610 to S650 in Figure 6, illustrate the process of more effectively performing widget visibility integration control using cache memory.

[0099] Figure 8 is a flowchart illustrating the sequence of a micro-device visibility integration control method according to yet another embodiment of this disclosure.

[0100] Step S810 is the step of identifying whether data exists. This step allows for advance verification of whether a specific widget contains data intended for display in the user interface (UI). For example, if the data is absent or blank, the visibility of the widget can be restricted.

[0101] S810 may be a pre-step performed before step S610 in Figure 6. However, this disclosure is not limited thereto; step S810 may be performed independently or concurrently with other steps, depending on the system implementation.

[0102] The S810 step, by pre-checking the existence of data, plays a crucial role in preventing system errors such as Null Reference Exception (NPE) and ensuring system stability. Furthermore, it helps reduce unnecessary resource waste and improves the efficiency of the widget visibility determination process.

[0103] By identifying the presence of data through the S810 step, the reliability and efficiency of the microdevice visibility integration control process can be improved.

[0104] Figure 9 is a flowchart illustrating the detailed sequence of steps S640 according to an embodiment of the present disclosure.

[0105] Step S910 is the step of identifying the most recent update time of the first and second micro-parts. In this step, the most recent update time of the data for both micro-parts is determined to ascertain the latest status of each micro-part. The most recent update time can serve as an important criterion for determining the priority of micro-parts.

[0106] Step S920 is a step that determines the priority order by considering the most recent update time identified. In this step, the most recent update time confirmed in step S910 is compared, and the more recently updated widget is assigned a higher priority. Thus, if two widgets conflict, only the widget with the higher priority can be made visible, while the widget with the lower priority remains invisible.

[0107] Thus, Figure 9 illustrates the detailed process of step S640 step by step, demonstrating how to effectively determine the priority order between widgets and control visibility based on the most recent update time. As a result, the system can provide users with only the latest status information, minimizing resource waste.

[0108] Figure 10 is a block diagram illustrating the hardware structure of a computing device for integrated control of microdevice visibility according to an embodiment of the present disclosure.

[0109] As shown in FIG10, the computing device 5000 may include one or more processors 5010, buses 5060, communication interfaces 5020, memory 5040 loading computer programs executed by the processor 5010, and storage 5030 storing computer programs 5050. However, FIG10 only shows technical features relevant to the embodiments disclosed herein.

[0110] Therefore, those skilled in the art to which this disclosure pertains will understand that, in addition to the technical features shown in FIG10, other general technical features may also be included. In other words, the computing device 5000 may also include various technical features other than those shown in FIG10. Furthermore, in some cases, the computing device 5000 may be configured with some technical features shown in FIG10 omitted. Each technical feature of the computing device 5000 will be described below. Additionally, throughout this disclosure, the computing device 5000 and the computing system are interchangeable.

[0111] Processor 5010 can control the overall operation of various structures of computing device 5000. Processor 5010 may include at least one of a central processing unit (CPU), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), or any form of processor known in the industry. Furthermore, processor 5010 can perform calculations for at least one application or program to perform operations / methods according to embodiments of this disclosure. Computing device 5000 may have one or more processors.

[0112] Furthermore, memory 5040 can store various data commands and / or information. Memory 5040 can load computer program 5050 from storage 5030 to execute the methods and / or operations of the embodiments disclosed herein. Memory 5040 can be implemented using volatile memory such as random access memory (RAM), but this disclosure is not limited thereto.

[0113] Furthermore, bus 5060 can provide communication functions between the technical features of computing device 5000. Bus 5060 can be implemented through various types of buses such as address bus, data bus, and control bus.

[0114] Secondly, the communication interface 5020 can support wired and wireless communication of the computing device 5000. Furthermore, the communication interface 5020 can also support various communication methods other than network communication. Therefore, the communication interface 5020 can include communication modules known in the art to which this disclosure pertains.

[0115] Then, the storage device 5030 can non-temporarily store one or more computer programs 5050. The storage device 5030 may include non-volatile memory such as read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, hard disk, removable hard disk, or any form of computer-readable recording medium known in the art to which this disclosure pertains.

[0116] Then, computer program 5050 may include one or more instructions that, when loaded into memory 5040, cause processor 5010 to perform operations / methods according to various embodiments of the present disclosure. In other words, processor 5010 may perform operations / methods according to various embodiments of the present disclosure by executing one or more loaded instructions.

[0117] For example, computer program 5050 may include instructions to perform the following operations: identifying user permission information for a first widget; identifying business conditions related to visibility determination for the first widget; identifying, based on the user permission information and the business conditions, whether there is a conflict between the first widget and a second widget different from the first widget; if a conflict is identified, determining the priority order between the first widget and the second widget; and making the widget with higher priority visible, while making the widget with lower priority invisible.

[0118] The micro-part visibility integrated control system 130 according to the embodiments of this disclosure can effectively control the visibility and invisibility of micro-parts, thereby achieving various effects. The main effects of this disclosure are as follows.

[0119] First, according to the embodiments disclosed herein, conflicts between widgets can be identified in real time, thereby preventing clutter on the user's screen. For example, even in the case of conflicting information that cannot coexist, clear and consistent information can be provided to the user by selectively making only the widget with higher priority visible and the remaining widgets invisible.

[0120] Second, according to the embodiments disclosed herein, the presence or absence of data can be identified in advance to prevent system errors. By preventing system errors such as Null Reference Exception (NPE) that may occur when displaying a widget without data, the stability of the system can be greatly improved.

[0121] Third, according to the embodiments disclosed herein, cache memory can be used to effectively manage resources. Since priority information between widgets is stored in cache memory, previously stored data can be reused when determining the visibility of a new widget. This reduces unnecessary computation, improves system responsiveness, and minimizes resource consumption.

[0122] Fourth, by simultaneously performing visibility and invisibility, the system's processing speed can be optimized. By simultaneously making higher-priority widgets visible and lower-priority widgets invisible according to their priority, unnecessary delays during screen updates can be prevented, thus improving the user experience (UX).

[0123] Fifth, according to the embodiments disclosed herein, business conditions can be reflected in real time and optimized information can be provided to users. For example, the visibility of widgets can be dynamically controlled based on specific conditions (whether there is a monthly subscription, whether coupons can be used, purchase history, etc.), thereby providing users with a customized screen. Thus, unnecessary information is not displayed, and users can intuitively view only the information they need.

[0124] Sixth, according to the embodiments disclosed herein, the latest information can be provided by determining the priority based on the most recently updated data. Devices with more recent updates are given higher priority and displayed on the user's screen to always provide the user with the latest status information.

[0125] The widget visibility integrated control system 130 according to embodiments of this disclosure can prevent information clutter on the user screen, improve system stability and efficiency, and provide an optimized user experience through these functions. Various embodiments of this disclosure and the effects of these embodiments have now been described with reference to Figures 1 to 10. The effects of this disclosure are not limited to those mentioned herein, and additional effects will be clearly understood by those skilled in the art.

[0126] In the foregoing, although all technical features constituting the embodiments of this disclosure are described as combinations or combinations of operations, this disclosure is not necessarily limited to these embodiments. In other words, within the scope of the technical concept of this disclosure, all technical features can be selectively combined into one or more operations.

[0127] Although various operations are shown in a specific order in the accompanying drawings, it should not be construed as meaning that the operations must be performed in the specific order shown or sequentially, or that all shown operations must be performed to obtain the desired result. In some cases, multiplexing and parallel processing may also be advantageous. Moreover, it should be understood that the separation of various technical features in the above embodiments should not be interpreted as a necessity; the described program elements and systems can generally be integrated together as a single software product, or packaged into multiple software products.

[0128] The embodiments of this disclosure have been described above with reference to the accompanying drawings. However, those skilled in the art will understand that the technical concept of this invention can be implemented in other specific forms without changing the invention or essential features of this disclosure. Therefore, it should be understood that the embodiments described above are exemplary and not limiting in all respects. The scope of protection of this disclosure should be interpreted by the appended claims, and all technical concepts within their equivalent scope should be understood to be included within the scope of this disclosure.

[0129] 110: User Terminal 120: Internet 130: Micro-parts visibility integrated control system 201: Discount Rate Micro-parts 202: Original Price Micro-part 203: Policy pop-up widget 204: Sales Price Micro-part 205: Sales unit price micro-parts 206: Sales Price Title Widget 207: Final Price Micropart 208: Final Price Title Widget 209: Final unit price for micro-components 210: Discounted Light Push Micro-devices 211: Guarantee delivery date and time (micro-parts) 310: Initial Price 320: First-level discount price 330: Final Price 340: Secondary discount related coupons 350: Final Discount Rate 410: Delivery Information Related Wi-Fi 420: Widgets related to monthly subscription discounts S501, S510, S520, S530, S540, S550, S610, S620, S630, S640, S650, S710, S720, S810, S910, S920: Steps 5000: Computing device 5100: Processor 5200: Communication Interface 5300: Storage 5400: Memory 5500: Computer Program 5600: Bus

Claims

1. A widget visibility integration control method, executed through a computing system, comprising the following steps: identifying user permission information for a first widget; identifying business conditions related to visibility determination for the first widget; based on the user permission information and the business conditions, identifying whether there is a conflict between the first widget and a second widget different from the first widget; if a conflict is identified, determining the priority order between the first widget and the second widget; and making the widget with the higher priority determined to be visible and making the widget with the lower priority determined to be invisible, wherein the step of identifying whether there is a conflict includes: Determine whether the first piece of information provided by the first widget and the second piece of information provided by the second widget present different values ​​for the same topic.

2. The widget visibility integration control method as described in claim 1, wherein, It also includes the following steps: storing the determined priority in cache memory; and using the information stored in the cache memory to determine the visibility of the third widget.

3. The widget visibility integration control method as described in claim 1, wherein, Simultaneously, make the widget with the higher priority visible and make the widget with the lower priority invisible.

4. The widget visibility integration control method as described in claim 1, wherein, It also includes the following steps: identifying whether data exists for the first micro-device.

5. The widget visibility integrated control method as described in claim 1, wherein, The steps for determining the priority order include: identifying the most recent update times of the first widget and the second widget; and determining the priority order based on the identified most recent update times of the first widget and the second widget.

6. A micro-part visibility integrated control system, comprising: One or more processors; The system also includes memory storing a computer program that executes via one or more processors. When the computer program is executed, the one or more processors perform the following operations: For a first widget, identify user permission information; For the first widget, identify business conditions related to visibility determination; Based on the user permission information and the business conditions, identify whether there is a conflict between the first widget and a second widget different from the first widget; If a conflict is identified, determine the priority between the first widget and the second widget. And in the first micro-device and the second micro-device, make the micro-device with the higher priority visible and make the micro-device with the lower priority invisible, wherein the operation of identifying whether there is a conflict includes: determining whether a first piece of information provided by the first micro-device and a second piece of information provided by the second micro-device present different values ​​for the same topic.

7. The micro-part visibility integrated control system as described in claim 6, wherein, The processor also performs the following operation: identifies whether data exists for the first microdevice.

8. The micro-device visibility integrated control system as described in claim 6, wherein, The processor also performs the following operations: storing the determined priority order in cache memory; and using the information stored in the cache memory to determine the visibility of the third microdevice.

9. The micro-part visibility integrated control system as described in claim 6, wherein, Simultaneously, make the widget with the higher priority visible and make the widget with the lower priority invisible.

10. The micro-part visibility integrated control system as described in claim 6, wherein, The operation of determining the priority order includes the following operations: identifying the most recent update time of the first widget and the second widget; and determining the priority order based on the identified most recent update time of the first widget and the second widget.

Images