(19)
(11)EP 2 824 552 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
04.11.2020 Bulletin 2020/45

(21)Application number: 12870833.6

(22)Date of filing:  14.05.2012
(51)International Patent Classification (IPC): 
G06F 9/451(2018.01)
G06F 3/048(2013.01)
G06F 3/0481(2013.01)
(86)International application number:
PCT/CN2012/075468
(87)International publication number:
WO 2013/131321 (12.09.2013 Gazette  2013/37)

(54)

MOBILE TERMINAL APPLICATION ICON MANAGEMENT METHOD AND MOBILE TERMINAL

VERFAHREN ZUR SYMBOLVERWALTUNG BEI EINER ANWENDUNG EINES MOBILEN ENDGERÄTS SOWIE MOBILES ENDGERÄT

PROCÉDÉ DE GESTION D'ICÔNES D'APPLICATIONS POUR TERMINAL MOBILE ET TERMINAL MOBILE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 08.03.2012 CN 201210059491

(43)Date of publication of application:
14.01.2015 Bulletin 2015/03

(73)Proprietor: ZTE Corporation
Shenzhen, Guangdong 518057 (CN)

(72)Inventor:
  • LIANG, Xiaohui
    Shenzhen Guangdong 518057 (CN)

(74)Representative: Ligi, Stefano et al
GLP S.r.l. Viale Europa Unita, 171
33100 Udine
33100 Udine (IT)


(56)References cited: : 
EP-A2- 2 426 898
CN-A- 102 306 080
US-A1- 2004 155 907
CN-A- 102 236 525
CN-A- 102 360 266
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    TECHNICAL FIELD



    [0001] The disclosure relates to the field of mobile terminal techniques, and in particular to a method for application icon management in a mobile terminal, and a mobile terminal.

    BACKGROUD



    [0002] With the upgrading of communication products, a mobile terminal such as a mobile phone or a Personal Digital Assistant (PDA) has become an indispensable communication tool, and various convenient and recreational applications appear on a mobile terminal.

    [0003] On an existing mobile terminal, icons of various applications are either displayed all in one screen or displayed in multiple screens. Although icon display by multiple screens can facilitate a user in finding an application to some extent, but an existing method for application icon management in a mobile terminal has the following disadvantages:
    1. (1) display of icons of various applications is not managed by class;
    2. (2) one application icon management operation can handle only one icon at a time, instead of batch management of multiple icons;
    3. (3) the icon of an application can be moved only after the application is installed;
    4. (4) a user can complete a move of an icon of an application only after dragging the icon to a target screen.


    [0004] EP 2 426 898 A2 provides a mobile terminal including: a display for displaying a folder icon corresponding to at least one application; a communication unit for receiving update information corresponding at least partially to the at least one application; and a controller for controlling the display to display the folder icon and, upon receipt of the update information by the communication unit, for controlling the display to display a graphical object indicating the receipt of the update information and corresponding to the folder icon.

    [0005] US 2004/0155907 A1 provides an icon display system in which a train of icons (icon train) selectable on an icon menu screen are managed by a display icon management table (28) and non-display icon management table (29) to visualize a part of the entire icon train by disposing it on an orbit (50) while holding the other part of the icon train as invisible icons on the screen and displaying the invisible icons by moving the icon train on the orbit. Also, some icons are made to visually disappear at a discontinuity (52) of the orbit (50) by moving the icon train on the orbit (50) and the new icons can be made to appear at the discontinuity (52) to the screen.

    [0006] CN 102 360 266 A discloses a method for displaying on a screen in an area-dividing mode, where predetermined area-dividing setting information is acquired, which includes area setting information, for dividing the screen into areas, and area association information, which represents an application associated with an area; applications associated respectively with areas on the screen are displayed respectively in the areas according to the predetermined area-dividing setting information. An interface of an application is displayed in a separate display area on the screen corresponding to the application. A user can drag an icon on the desktop into a corresponding area to run the application directly.

    SUMMARY



    [0007] In view of this, it is desired that embodiments of the disclosure provide a method for application icon management in a mobile terminal, and a mobile terminal, capable of implementing batch management and multi-mode management of icons of applications of a mobile terminal.

    [0008] To this end, the disclosure provides a method for application icon management in a mobile terminal, including steps of:

    presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;

    receiving an icon object moving instruction, acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph; and

    updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move.



    [0009] In an embodiment, the step of establishing a table of mapping relation among a class of applications, a screen, and an application may include a step of:
    respectively establishing a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.

    [0010] In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of:

    when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens, and displaying the information on the rule graph, wherein

    after the class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, it is determined whether there is enough space remaining in the target screen for storing the class of applications to be moved; and

    when there is enough space remaining in the target screen for storing the class of applications to be moved, the class of applications to be moved is moved to the area containing the sequence number of the target screen successfully.



    [0011] In an embodiment, the steps of acquiring information on a rule graph corresponding to an icon object to be moved according to the icon object moving instruction, and displaying the information on the rule graph may include steps of:

    when it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, acquiring information on a double-layer annular graph marked with sequence numbers of screens and classes of applications, and displaying the information on the rule graph, wherein

    after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, it may be determined whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and

    when there is enough space remaining in the target screen or the screen containing the target class of applications for storing the to-be-moved icon of the application, the to-be-moved icon of the application is moved to the area containing the sequence number of the target screen or the target class of applications successfully.



    [0012] In an embodiment, the step of updating, after successfully moving the icon object to be moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application according to the move may include steps of:

    after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, updating the table mapping a class of applications to a screen; and refreshing application class layout displayed on the current screen and application class layout displayed on the target screen; or

    after the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, updating the table mapping an application to a class of applications, or the table mapping an application to a screen; and refreshing application icon layout displayed on a current screen and application icon layout displayed on the target screen.



    [0013] In an embodiment, the method may further include a step of: after the steps of presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application,
    updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.

    [0014] The disclosure further provides a mobile terminal, including
    a presetting module configured for: presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;
    a managing module configured for: receiving an icon object moving instruction; acquiring information on a single-layer annular graph or a double-layer annular graph according to the icon object moving instruction; and updating, after successfully moving the icon object to be moved to an area on the single-layer annular graph or the double-layer annular graph, a table of mapping relation among a class of applications, a screen, and an application according to the move; and
    a displaying module configured for: displaying the information on the rule graph.

    [0015] In an embodiment, the managing module may be further configured for:

    after a class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the class of applications to be moved;

    after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, determining whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and

    updating the table mapping an application to a class of applications according to information on a class to which a new application belongs preset in installing the new application.



    [0016] In an embodiment, the displaying module may be further configured for:
    refreshing application class layout and application icon layout displayed on a current screen and on a target screen according to the table of mapping relation among a class of applications, a screen, and an application updated by the managing module.

    [0017] In an embodiment, the mobile terminal may further include an installing module configured for: installing a new application; and after the new application is installed successfully, sending the managing module an icon management message corresponding to the installation, wherein
    the managing module may be further configured for: updating a table mapping an application to a class of applications according to the icon management message; and
    the displaying module may be further configured for: displaying icons of applications by class according to the table mapping an application to a class of applications updated by the managing module.

    [0018] With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. Moreover, with the disclosure, it is possible to set in an installation phase of a new application a class to which the new application belongs, and directly manage display of the icon of the new application by class, thereby saving any icon display management after the new application is installed.

    BRIEF DESCRIPTION OF THE DRAWINGS



    [0019] 

    Fig.1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.4 is a schematic diagram of a structure of a single-layer annular graph displayed on a current screen in case an icon object to be moved is a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.5 is a schematic diagram of a structure of a double-layer annular graph displayed on a current screen in case an icon object to be moved is an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.6 is a flowchart, in installing a new application, of setting a class to which the new application belongs and directly managing display of the icon of the new application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure;

    Fig.7 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure; and

    Fig.8 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure.



    [0020] Implementation, features,and advantages of the disclosure will be further described with reference to accompanying drawings in combination with embodiments.

    DETAILED DESCRIPTION



    [0021] According to embodiments of the disclosure, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established; an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed; and after the icon object to be moved is successfully moved to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move.

    [0022] A technical solution of the disclosure will be further elaborated with reference to the accompanying drawings in combination with specific embodiments. It should be understood that the specific embodiments described herein are only used to interpret the disclosure instead of limiting the disclosure.

    [0023] Fig.1 is a flowchart of a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in Fig.1, the method includes steps as follows.

    [0024] In Step S101, information on a class to which an application belongs is preset, and a table of mapping relation among a class of applications, a screen, and an application is established.

    [0025] In an embodiment, in addition to a default class of applications in a mobile terminal, a new class of applications may be added, and an existing class of applications may be modified or deleted through an application class customizing interface. Then, a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen are established respectively in advance according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.

    [0026] The table mapping a class of applications to a screen (Class_Screen) indicates mapping relation between a class of applications and a screen of the mobile terminal (i.e., table Class_Screen hereafter).

    [0027] The table mapping an application to a class of applications (App_Class) indicates mapping relation between an application and a class of applications (i.e., table App_Class hereafter).

    [0028] The table mapping an application to a screen (App_Screen) indicates mapping relation between an application and a screen of the mobile terminal ((i.e., table App_Screen hereafter), where an application with its icon stored in the screen is not classified. Main fields of the table Class_Screen are as shown in Table 1, main fields of the table App_Class are as shown in Table 2, and main fields of the table App_Screen are as shown in Table 3.
    Table 1
    Fielddescription
    a class the class contained in the screen with the sequence number
    a sequence number of a screen the sequence number of a screen in the mobile terminal
    Table 2
    Fielddescription
    an application an application belonging to the class of applications
    a class a class of applications contained in a screen of the mobile terminal
    Table 3
    Fielddescription
    an application an unclassified application
    a sequence number of a screen the sequence number of a screen in the mobile terminal


    [0029] In Step S102, an icon object moving instruction is received, information on a rule graph corresponding to an icon object to be moved is acquired according to the icon object moving instruction, and the information on the rule graph is displayed.

    [0030] In an embodiment, when it is determined according to the icon object moving instruction that the icon object to be moved is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and the single-layer annular graph is displayed on a current screen. When it is determined according to the icon object moving instruction that the icon object to be moved is an icon of an application, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and the double-layer annular graph is displayed on a current screen.

    [0031] In Step S103, after the icon object to be moved is moved successfully to an area on the rule graph, a table of mapping relation among a class of applications, a screen, and an application is updated according to the move.

    [0032] In an embodiment, after the icon object to be moved is moved successfully to the area on the rule graph, the table mapping a class of applications to a screen, the table mapping an application to a class of applications, or the table mapping an application to a screen may be updated.

    [0033] With the method for application icon management in a mobile terminal according to the disclosure, icons of installed applications are managed rapidly by screen or by class on a respective rule graph, such that with the disclosure, compared with an existing method for application icon management in a mobile terminal, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user.

    [0034] Fig.2 is a flowchart of managing icon-display-by-screen by moving a class of applications in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in Fig.2, the flow of managing icon-display-by-screen by moving a class of applications according to the disclosure includes steps as follows.

    [0035] In Step S201, an icon object is moved.

    [0036] In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications.

    [0037] In Step S202, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application.

    [0038] In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is a class of applications, the flow goes to step S203.

    [0039] In Step S203, information on a single-layer annular graph marked with sequence numbers of screens is acquired; and space remaining in each screen is calculated and compared with space to be occupied by the class of applications.

    [0040] In an embodiment, when it is determined that the icon object is a class of applications, information on a single-layer annular graph marked with sequence numbers of screens is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the class of applications. Here, the information on the single-layer annular graph may include a total size of the graph, a total number of screens in the mobile terminal, size of an area containing a sequence number of a screen, an identifier of a color of an area, an identifier of a color of storage space occupied by each class of applications and icons of applications belonging to the each class in a screen, and the like.

    [0041] In Step S204, the single-layer annular graph marked with sequence numbers of screens is displayed on a current screen.

    [0042] In an embodiment, the single-layer annular graph displayed here, as shown in Fig.4, includes 4 screens with sequence numbers 1, 2, 3, 4, respectively; and areas containing the sequence numbers of screens may be distinguished from each other by color. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing icons of all applications belonging to the class of applications, the sequence number of the screen is shown in bright yellow. When a screen is found not to have sufficient free space, as calculated by the mobile terminal, for storing icons of applications belonging to the class of applications, the sequence number of the screen is shown in black. Here, sequence numbers of screens 1, 3, 4 are shown in bright yellow, indicating that each of screen 1, screen 3, and screen 4 has sufficient free space for storing icons of all applications belonging to the class of applications. The sequence number of screen 2 is shown in black, indicating that the screen 2 has insufficient free space for storing icons of all applications belonging to the class of applications.

    [0043] In Step S205, the class of applications is moved into an area containing a sequence number of a target screen in the single-layer annular graph, and is then released.

    [0044] In Step S206, it is determined whether there is enough space remaining in the target screen for storing the class of applications; if there is, the flow goes to step S207; otherwise if there is insufficient space, the flow goes to Step S211.

    [0045] In an embodiment, it is detected whether the sequence number of the target screen is shown in a bright yellow font. If the sequence number of the target screen is shown in a bright yellow font, it means that there is enough space remaining in the target screen for storing the class of applications. Otherwise if the sequence number of the target screen is not shown in a bright yellow font, it means that space remaining in the target screen is insufficient for storing the class of applications, and a user may be notified that space remaining in the target screen is insufficient for storing the class of applications.

    [0046] As shown in Fig.4, sequence numbers of screens 1, 3, 4 are shown in a bright yellow font, and the sequence number of screen 2 is shown in a black font. A class of applications in the screen 1 can be moved to the area containing the sequence number 4 or the area containing the sequence number 3, but can not be moved to the area containing the sequence number 2.

    [0047] In Step S207, the area containing the sequence number of the target screen in the single-layer annular graph is highlighted.

    [0048] In an embodiment, for example, as shown in Fig.4, if a class of applications in the screen with sequence number 1 is moved to the area containing the sequence number 4, then the area containing the sequence number 4 will be highlighted, indicating that the class of applications is moved successfully.

    [0049] In Step S208, information on the area containing the sequence number of the target screen is recorded, an icon management message corresponding to the move of the class of applications is sent, and a table Class_Screen is updated.

    [0050] In an embodiment, after the class of applications is moved successfully, information on the area containing the sequence number of the target screen is recorded, and an icon management message is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 2, indicating that the current moving operation involves move of a class of applications. After receiving the icon management message, the managing module updates the table Class_Screen, that is, updates the mapping relation between a class of applications and a screen.

    [0051] In Step S209, application class layout displayed on the current screen and application class layout displayed on the target screen are refreshed.

    [0052] In an embodiment, displayed layout of any class of applications on the current screen and on the target screen, and of icons of applications belonging to the any class of applications, are refreshed according to the table Class_Screen updated in step S208.

    [0053] In Step S210, display of the single-layer annular graph is cancelled.

    [0054] In an embodiment, when no class of applications is moved within a preset period of time, display of the single layer annular graph is cancelled.

    [0055] In Step S211, a user is notified that space remaining in the target screen is insufficient for storing the class of applications.

    [0056] If it is determined in Step S206 that space remaining in the target screen is insufficient for storing the class of applications, a notification that space remaining in the target screen is insufficient for storing the class of applications is provided on the current screen.

    [0057] Fig.3 is a flowchart of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in Fig.3, the flow of managing icon-display-by-screen or icon-display-by-class by moving an icon of an application according to the disclosure includes steps as follows.

    [0058] In Step S301, an icon object is moved.

    [0059] In an embodiment, after information on a class to which an application belongs is preset in the mobile terminal, and a table of mapping relation among a class of applications, a screen, and an application is established, an icon object of a class of applications or an icon of an application is dragged into a target screen or a target class of applications.

    [0060] In Step S302, it is determined according to an icon object moving instruction whether the icon object is a class of applications or an icon of an application.

    [0061] In an embodiment, when the icon object is moved, the type of the icon object (a class of applications or an icon of an application) needs to be determined in the first place according to the icon object moving instruction, and when the icon object is an icon of an application, the flow goes to step S303.

    [0062] In Step S303, information on a double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the icon of the application.

    [0063] In an embodiment, when it is determined that the icon object is an icon of an application, information on the double-layer annular graph marked with sequence numbers of screens and classes of applications is acquired, and space remaining in each screen is calculated and compared with space to be occupied by the class of applications.

    [0064] Here, the information on the double-layer annular graph may include: a total size of the graph; a total number of screens in the mobile terminal; any class of applications already in each screen, and a number of classes of applications already in each screen; size of an area containing a class of applications; size of an area containing a sequence number of a screen; an identifier of a color of an area, an identifier of a color of storage space occupied by any class of applications and icons of applications belonging to the class in a screen, and the like.

    [0065] In Step S304, the double-layer annular graph marked with sequence numbers of screens and classes of applications is displayed on a current screen.

    [0066] In an embodiment, the double-layer annular graph displayed here, as shown in Fig.5, includes four classes of applications, namely, everyday, office, game and system. Classes of applications displayed in a same screen occupy continuous areas in the double-layer annular graph and the continuous areas are in the same color. In an embodiment, the two classes of everyday and office are located in screen 1, the game is located in screen 2, the system is located in screen 3, and currently no icon of an application belonging to a class of applications is stored in screen 4. When there is enough space remaining in a screen, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in bright yellow. When a screen is found not to have sufficient free space, as calculated by the mobile terminal, for storing the icon of the application, the sequence number of the screen and any class of applications in the screen are shown in black. Here, the classes "everyday" and "office" and the sequence number "1" of the screen containing the classes "everyday" and "office" are in a bright yellow font; the class "system" and the sequence number "3" of the screen containing the class system are in a bright yellow font too; but class "game" and the sequence number "2" of the screen containing class game are in a black font. This indicates that the icon of the application may be stored in either screen 1 or screen 3, but may not be stored in screen 2, as space remaining in screen 2 is insufficient.

    [0067] In Step S305, the icon of the application is moved into an area containing a sequence number of a target screen or into an area containing a target class of applications in the double-layer annular graph, and is then released.

    [0068] In Step S306, it is determined whether the area contains the sequence number of a target screen or contains a target class of applications; If the area contains a target class of applications, the flow goes to Step S307; otherwise if the area contains the sequence number of a target screen, the flow goes to Step S313.

    [0069] In an embodiment, after the icon of the application is moved into an area containing a sequence number of a screen or containing a class of applications in the double-layer annular graph, and is then released, it is detected whether the area is occupied by a class of applications or a sequence number of a screen. If the area is occupied by a class of applications, the flow goes to Step S307. If the area is occupied by a sequence number of a screen, the flow goes to Step S313.

    [0070] As shown in Fig.5, the icon of an application belonging to the class "system" in screen 3 may be moved to an area containing the sequence number "1" or "4", or to an area containing the class "everyday" or "office" in screen 1 (namely, to an area with a bright yellow font); but cannot be moved to an area containing the sequence number "2" or to an area containing the class "game" (namely, cannot be moved to an area with a black font).

    [0071] In Step S307, it is determined whether there is enough space remaining in a screen containing the target class of applications for storing the icon of the application; if space remaining in the target screen is sufficient for storing the icon of the application, the flow goes to step S308; otherwise if space remaining in the target screen is insufficient for storing the icon of the application, the flow goes to Step S312.

    [0072] In an embodiment, it is detected whether the target class of applications is shown in a bright yellow font, if the target class of applications is shown in a bright yellow font, it means that there is enough space remaining for storing the icon of the application. Otherwise if the target class of applications is not shown in a bright yellow font, it means that space remaining is insufficient for storing the icon of the application.

    [0073] In Step S308, the area containing the target class of applications in the double-layer annular graph is highlighted.

    [0074] In Step S309, information on the area containing the target class of applications is recorded, and an icon management message corresponding to the move of the icon of the application is sent, and a table of mapping relation corresponding to the move of the icon of the application is updated.

    [0075] In an embodiment, after the icon of the application is moved successfully, the information on the area containing the target class of applications is recorded, and the icon management message corresponding to the move of the icon of the application is sent to a managing module of the mobile terminal. The icon management message includes an icon management type MsgType 3, indicating that the current moving operation involves move of an icon of an application into a target class of applications. After receiving the icon management message, the managing module of the mobile terminal checks the table App_Class to determine whether a mapping relation between the application and a class of applications exist, i.e., checks whether the application has been classified. If the application has not been classified, then the table App_Screen is called, and a mapping relation between the application and a screen in the table App_Screen is deleted; in addition, the table App_Class is called, and a mapping relation between the application and the target class of applications is added in the table App_Class; when the application is previously classified, the table App_Class is called, and the mapping relation between the application and a class of applications is updated.

    [0076] In Step S310, application icon layout displayed on a current screen and application icon layout displayed on a target screen are refreshed.

    [0077] In an embodiment, application icon layout displayed on the current screen and application icon layout displayed on the target screen are refreshed according to a table updated in step S309.

    [0078] In Step S311, display of the double-layer annular graph is cancelled.

    [0079] In an embodiment, when no application icon is moved within a preset period of time, display of the double-layer annular graph is cancelled.

    [0080] In Step S312, a user is notified that space remaining in the screen containing the target class of applications is insufficient for storing the icon of the application.

    [0081] In an embodiment, if it is determined in Step S307 that space remaining in the screen containing the target class of applications is insufficient for storing the icon of the application, then a notification that space remaining in the screen containing the target class of applications is insufficient for storing the icon of the application is provided on the current screen.

    [0082] In Step S313, it is determined whether there is enough space remaining in the target screen for storing the icon of the application; if there is enough space, the flow goes to step S314; otherwise if space remaining in the target screen is insufficient for storing the icon of the application, the flow goes to Step S316.

    [0083] In an embodiment, when the mobile terminal detects that the area where the icon of the application is released contains a sequence number of a screen, it is determined whether there is enough space remaining in the target screen for storing the icon of the application. That is, it is detected whether the sequence number of the target screen is shown in a bright yellow font. If the sequence number of the target screen is shown in a bright yellow font, it means that there is enough space remaining in the target screen for storing the icon of the application. Otherwise if the sequence number of the target screen is not shown in a bright yellow font, it means that space remaining in the target screen is insufficient for storing the icon of the application.

    [0084] In Step S314, the area containing the sequence number of the target screen in the double-layer annular graph is highlighted.

    [0085] In Step S315, information on the area containing the sequence number of the target screen is recorded, and an icon mana gement message corresponding to the move of the icon of the application is sent, and a table of mapping relation corresponding to the move of the icon of the application is updated.

    [0086] In an embodiment, after the icon of the application is moved successfully, the information on the area containing the sequence number of the target screen is recorded, and the icon management message corresponding to the move of the icon of the application is sent to the managing module of the mobile terminal. The icon management message includes an icon management type MsgType 4, indicating that the current moving operation involves move of an icon of an application into a target screen. After receiving the icon management message, the managing module of the mobile terminal checks the table App_Class to determine whether a mapping relation between the application and a class of applications exist, i.e., checks whether the application has been classified. If the application has not been classified, then the table App_Screen is called, and a mapping relation between the application and a screen is updated; when the application is previously classified, the table App_Class is called, and the mapping relation between the application and any class of applications in the table App_Class is deleted, and the table App_Screen is called to add a mapping relation between the application and the target screen in the table App_Screen. Then application class layout and application icon layout displayed on a screen is refreshed according to an updated table. When no application icon is moved within a preset period of time, display of the double-layer annular graph is ancelled.

    [0087] In Step S316, a user is notified that space remaining in the target screen is insufficient for storing the icon of the application.

    [0088] If it is determined in Step S313 that space remaining in the target screen is insufficient for storing the icon of the application, a notification that space remaining in the target screen is insufficient for storing the icon of the application is provided on the current screen.

    [0089] Fig.6 is a flowchart, in installing a new application, of setting a class to which the new application belongs and directly managing display of the icon of the new application in a method for application icon management in a mobile terminal according to an embodiment of the disclosure. As shown in Fig.6, the flow, in installing a new application, of setting a class to which the new application belongs and directly managing display of the icon of the new application includes steps as follows.

    [0090] In Step S601, a package file for installing a new application is read.

    [0091] In an embodiment herein, in installing a new application, a mobile terminal will read a package file for installing the new application, where the package file may include information such as an icon of the application, a name of the package for installing the application and a hardware environment needed for installing the application.

    [0092] In Step S602, space remaining in each screen is calculated.

    [0093] In Step S603, it is determined whether there is enough space remaining in a screen for storing the icon of the new application; if there is enough space remaining in a screen for storing the icon of the new application, the flow goes to step S604; otherwise if no screen has enough free space for storing the icon of the new application, the flow goes to Step S610.

    [0094] In Step S604, a sequence number of the screen with free space sufficient for storing the icon of the new application, and a class of applications contained in the screen with the sequence number, are read.

    [0095] In an embodiment, when it is detected that there is enough space remaining in a screen for storing the icon of the new application, the mobile terminal will record and read the sequence number of the screen with free space sufficient for storing the icon of the new application and any class of applications contained in the screen with the sequence number.

    [0096] In Step S605, the sequence number of the screen with free space sufficient for storing the icon of the new application, and a class of applications contained in the screen with the sequence number, are displayed.

    [0097] In an embodiment, the mobile terminal displays on a current screen the sequence number of the screen with free space sufficient for storing the icon of the new application and a class of applications contained in the screen with the sequence number, such that a user may select a class for the new application to be installed.

    [0098] In Step S606, a class of applications to which the new application belongs is selected according to a displayed class of applications, and the new application is installed using the package file.

    [0099] In Step S607, an icon management message is sent.

    [0100] In an embodiment, the icon management message includes the file name of the package for installing the application, the class to which the application belongs, the sequence number of the screen for display the application and an icon management type MsgType of the new application. The class to which the application belongs is that selected when the new application is installed, the MsgType is 1, indicating that during installing a new application, the mobile terminal directly manages display of the icon of the application by class.

    [0101] In Step S608, a table App_Class is updated according to the icon management message.

    [0102] In an embodiment, the managing module of the mobile terminal calls the table App_Class to update a mapping relation between an application and a class of applications according to the icon management message.

    [0103] In Step S609, the table App_Class is read, and layout of icons of applications belonging to the selected class of applications in display is refreshed.

    [0104] In an embodiment, after updating the table App_Class, the mobile terminal reads the table App_Class, and refreshes the layout of icons of applications belonging to the selected class of applications in display, implementing direct management of display of the icon of the new application.

    [0105] In Step S610, a user is notified that the new application cannot be installed.

    [0106] When it is detected that no screen has enough free space for storing the icon of the new application, a notification that the new application cannot be installed is provided in the current screen.

    [0107] With the method for application icon management in a mobile terminal according to the disclosure, display of the icon of a new application by class can be managed directly by setting a class to which the new application belongs during installation of the new application, thereby saving any icon display management after the new application is installed.

    [0108] Fig.7 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure. As shown in Fig.7, the mobile terminal according to the embodiment includes:

    a presetting module 701 configured for: presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;

    a managing module 702 configured for: receiving an icon object moving instruction; acquiring information on a single-layer annular graph or a double-layer annular graph according to the icon object moving instruction; and updating, after successfully moving the icon object to be moved to an area on the single-layer annular graph or the double-layer annular graph, a table of mapping relation among a class of applications, a screen, and an application according to the move; and

    a displaying module 703 configured for: sending the icon object moving instruction to the managing module 702 and displaying on a current screen the single-layer annular graph or the double-layer annular graph according to the information on the single-layer annular graph or the double-layer annular graph acquired by the managing module 702.



    [0109] The presetting module 701 may add a new class of applications in addition to a default class of applications in a mobile terminal, and modify or delete an existing class of applications through an application class customizing interface. Then, a table mapping a class of applications to a screen, a table mapping an application to a class of applications, and a table mapping an application to a screen are established respectively in advance according to affiliation in storing an icon of an application in a screen and in storing a class of applications in a screen.

    [0110] Compared with an existing method for application icon management in a mobile terminal, with the mobile terminal according to the embodiment, in moving a class of applications or an icon of an application, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user.

    [0111] The managing module 702 may be further configured for:
    after a class of applications to be moved is moved to an area containing a sequence number of a target screen in the single-layer annular graph, determining whether there is enough space remaining in the target screen for storing the class of applications to be moved; and after the class of applications is successfully moved to the area in the single-layer annular graph, receiving an icon management message sent by the displaying module 703 and updating the table mapping a class of applications to a screen according to the icon management message.

    [0112] The displaying module 703 may be further configured for:
    after the class of applications is moved successfully to the area in the single-layer annular graph, sending the icon management message corresponding to the move of the class of applications to the managing module 702, and refreshing application class layout displayed on the current screen and application class layout displayed on the target screen according to the table mapping a class of applications to a screen updated by the managing module.

    [0113] The managing module 702 may be further configured for:

    after the to-be-moved icon of the application is moved to an area containing a sequence number of a target screen or a target class of applications in the double-layer annular graph, determining whether there is enough space remaining in the target screen or a screen containing the target class of applications for storing the to-be-moved icon of the application; and after the icon of the application is successfully moved to the area containing the target class of applications in the double-layer annular graph, receiving an icon management message sent by the displaying module 703 and updating the table mapping an application to a class of applications according to the icon management message; and

    after the icon of the application is successfully moved to the area containing the sequence number of the target screen in the double-layer annular graph, receiving an icon management message sent by the displaying module 703 and updating the table mapping an application to a screen according to the icon management message.



    [0114] The displaying module 703 may be further configured for:

    after the icon of the application is successfully moved to the area containing the target class of applications in the double-layer annular graph, sending the icon management message corresponding to the move of the icon of the application to the managing module 702, and refreshing application icon layout displayed on the current screen and application icon layout displayed on the target screen according to the table mapping an application to a class of applications updated by the managing module 702, ; and

    after the icon of the application is successfully moved to the area containing the sequence number of the target screen in the double-layer annular graph, sending the icon management message corresponding to the move of the icon of the application to the managing module 702, and refreshing application icon layout displayed on the current screen and application icon layout displayed on the target screen according to the table mapping an application to a screen updated by the managing module 702.



    [0115] The managing module 702 may be further configured for:
    notifying the displaying module 703 to cancel display of the single-layer annular graph or the double-layer annular graph if no icon object moving operation is detected within a preset period of time.

    [0116] Fig.8 is a schematic diagram of a modular structure of a mobile terminal according to an embodiment of the disclosure. As shown in Fig.8, based on the mobile terminal according to the previous embodiment, the mobile terminal according to the current embodiment further includes:
    an installing module 804 configured for installing a new application.

    [0117] Specifically, the installing module 804 may be further configured for:
    during installation of a new application, determining the class to which the new application belongs according to information on a class to which an application belongs preset by a presetting module 801 and a table Class_Screen, a table App_Class and a table App_Screen, sending an icon management message corresponding to application installation to a managing module 802 to notify the managing module 802 to update the table App_Class.

    [0118] The managing module 802 may be further configured for:
    receiving the icon management message sent by the installing module 804 and updating the table App_Class, i.e., according to the class information (selected class to which the new application belongs) preset during installation of the new application.

    [0119] The displaying module 803 may be further configured for:
    after the installation of the new application is completed, displaying the icon of the new application by class according to the class selected during its installation.

    [0120] Compared with an existing method for application icon management in a mobile terminal, with the mobile terminal according to the embodiment, in moving a class of applications or an icon of an application, icon management is simplified, and batch management and multi-mode management of icons of applications are achieved, thereby greatly facilitating application icon management by a user. Moreover, with the mobile terminal according to the current embodiment, it is possible to set in an installation phase of a new application a class to which the new application belongs, and directly manage display of the icon of the new application by class, thereby saving any icon display management after the new application is installed.

    [0121] What described are merely embodiments of the disclosure, and are not intended to limit the scope of protection of the disclosure. All equivalent structures and flow changes made using the specification and accompanying drawings of the disclosure, or direct or indirect applications of the disclosure to another related technical field should be included within the scope of protection of the disclosure.


    Claims

    1. A method for application icon management in a mobile terminal, comprising:

    presetting, by the mobile terminal, information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application (S101);

    receiving, by the mobile terminal, an icon object moving instruction (S102, S201, S301);

    determining, by the mobile terminal, according to the icon object moving instruction, an icon object to be moved to be a class of applications or an icon of an application (S202, S302);

    acquiring, by the mobile terminal, information on a rule graph corresponding to the icon object to be moved according to the icon object moving instruction (S102), by:

    when it is determined according to the icon object moving instruction that the icon object to be moved is the class of the applications, acquiring, by the mobile terminal, information on a single-layer annular graph marked with sequence numbers of screens (S203);

    when it is determined according to the icon object moving instruction that the icon object to be moved is the icon of the application, acquiring, by the mobile terminal, information on a double-layer annular graph marked with the sequence numbers of the screens and classes of

    applications (S303);

    calculating, by the mobile terminal, space remaining in each of the screens (S203, S303);

    comparing, by the mobile terminal, the space remaining in the each of the screens with space to be occupied by the icon object to be moved (S203, S303);

    displaying, by the mobile terminal, the information on the rule graph (S102), by:

    when it is determined according to the icon object moving instruction that the icon object to be moved is the class of the applications, displaying, by the mobile terminal, the single-layer annular graph marked with the sequence numbers of the screens on a current screen (S204), by showing, by the mobile terminal, a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of all applications belonging to the class of the applications, and by the mobile terminal, showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;

    when it is determined according to the icon object moving instruction that the icon object to be moved is the icon of the application, displaying, by the mobile terminal, the double-layer annular graph marked with the sequence numbers of the screens and the classes of the applications on the current screen (S304), by showing, by the mobile terminal, a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and by the mobile terminal, showing the sequence number of the screen and the any class of the applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application;

    after the class of the applications is moved into an area containing a sequence number of a target screen in the single-layer annular graph, and is then released (S205), determining, by the mobile terminal, whether there is enough space remaining in the target screen for storing the class of the applications (S206), by the mobile terminal, detecting whether the sequence number of the target screen is shown in a bright yellow font;

    or, after the icon of the application is moved into an area containing a sequence number of a target screen or into an area containing a target class of applications in the double-layer annular graph, and is then released (S305), determining, by the mobile terminal, whether there is enough space remaining in the target screen for storing the icon of the application if the area contains the sequence number of the target screen (S306, S313), by the mobile terminal, detecting whether the sequence number of the target screen is shown in the bright yellow font; determining, by the mobile terminal, whether there is enough space remaining in a screen containing the target class of the applications for storing the icon of the application if the area contains the target class of the applications (S306, S307), by the mobile terminal, detecting whether the target class of the applications is shown in the bright yellow font;

    if there is enough space remaining in the target screen for storing the class of the applications, highlighting, by the mobile terminal, the area containing the sequence number of the target screen in the single-layer annular graph (S207), indicating that the class of applications is moved successfully;

    if there is enough space remaining in the target screen for storing the icon of the application, highlighting, by the mobile terminal, the area containing the sequence number of the target screen in the double-layer annular graph (S314);

    if there is enough space remaining in the screen containing the target class of applications for storing the icon of the application, highlighting, by the mobile terminal, the area containing the target class of the applications in the double-layer annular graph (S308);

    updating, after successfully moving the icon object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move (S103);

    cancelling, by the mobile terminal, display of the single-layer annular graph or the double-layer annular graph if no icon object moving operation is detected within a preset period of time (S210, S311),

    wherein the preset information on a class to which an application belongs comprises at least one of a default class of applications and a class of applications added or modified through an application class customizing interface,

    wherein the establishing a table of mapping relation among a class of applications, a screen, and an application comprises:
    respectively establishing, by the mobile terminal, a table Class_Screen, a table App_Class, and a table App_Screen, wherein the table Class_Screen indicates mapping relation between a class of applications and a screen; the table App_Class indicates mapping relation between an application and a class of applications; the table App_Screen indicates mapping relation between an application and a screen,

    wherein the updating, by the mobile terminal, after successfully moving the icon object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:

    after the class of applications is moved successfully into the area containing the sequence number of the target screen, recording, by the mobile terminal, information on the area containing the sequence number of the target screen to update the table Class_Screen (S208);

    after the icon of the application is moved successfully into the area containing the target class of the applications, recording information on the area containing the target class of applications (S309); checking, by the mobile terminal, the table App_Class to determine whether a mapping relation between the application and a class of applications exists to check whether the application has been classified; if the application has not been classified, deleting, by the mobile terminal, a mapping relation between the application and a screen in the table App_Screen, and adding, by the mobile terminal, a mapping relation between the application and the target class of applications in the table App_Class;

    when the application is previously classified, calling, by the mobile terminal, the table App_Class to update the mapping relation between the application and a class of applications (S309);
    after the icon of the application is moved successfully into the area containing the sequence number of the target screen, recording, by the mobile terminal, the information on the area containing the sequence number of the target screen; checking, by the mobile terminal, the table App_Class to determine whether the mapping relation between the application and a class of applications exists to check whether the application has been classified; if the application has not been classified, calling, by the mobile terminal, the table App_Screen to update the mapping relation between the application and a screen; when the application is previously classified, deleting, by the mobile terminal, the mapping relation between the application and any class of applications in the table App_Class, and adding, by the mobile terminal, the mapping relation between the application and the target screen in the table App_Screen (S315).


     
    2. The method according to claim 1, wherein the updating, after successfully moving the icon object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move comprises:

    after the class of applications to be moved is successfully moved to the area containing the sequence number of the target screen in the single-layer annular graph, refreshing application class layout displayed on the current screen and application class layout displayed on the target screen (S209); or

    after the to-be-moved icon of the application is successfully moved to the area containing the sequence number of the target screen or the target class of applications in the double-layer annular graph, refreshing application icon layout displayed on the current screen and application icon layout displayed on the target screen (S310).


     
    3. The method according to claim 1, further comprising: after the presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application,
    updating the table App_Class according to information on a class to which a new application belongs preset in installing the new application (S606-S608).
     
    4. A mobile terminal, comprising:

    a presetting module (701, 801) configured for: presetting information on a class to which an application belongs, and establishing a table of mapping relation among a class of applications, a screen, and an application;

    a managing module (702, 802) configured for:

    receiving an icon object moving instruction;

    determining, according to the icon object moving instruction, an icon object to be moved to be a class of applications or an icon of an application;

    acquiring information on a rule graph corresponding to the icon object to be moved according to the icon object moving instruction, by:

    when it is determined according to the icon object moving instruction that the icon object to be moved is the class of the applications, acquiring information on a single-layer annular graph marked with sequence numbers of screens;

    when it is determined according to the icon object moving instruction that the icon object to be moved is the icon of the application, acquiring information on a double-layer annular graph marked with the sequence numbers of the screens and classes of applications;

    calculating space remaining in each of the screens;

    comparing the space remaining in the each of the screens with space to be occupied by the icon object to be moved; and

    a displaying module (703, 803) configured for: displaying the information on the rule graph, by:

    when it is determined according to the icon object moving instruction that the icon object to be moved is the class of the applications, displaying the single-layer annular graph marked with the sequence numbers of the screens on a current screen, by showing a sequence number of a screen in bright yellow when there is enough space remaining in the screen for storing icons of all applications belonging to the class of the applications, and showing the sequence number of the screen in black when the screen does not have sufficient free space for storing the icons of the applications belonging to the class of the applications;

    when it is determined according to the icon object moving instruction that the icon object to be moved is the icon of the application, displaying the double-layer annular graph marked with the sequence numbers of the screens and the classes of the applications on the current screen, by showing a sequence number of a screen and any class of applications in the screen in bright yellow when there is enough space remaining in the screen for storing the icon of the application, and showing the sequence number of the screen and the any class of the applications in the screen in black when the screen does not have sufficient free space for storing the icon of the application,

    wherein the managing module (702, 802) is further configured for:

    after the class of the applications is moved into an area containing a sequence number of a target screen in the single-layer annular graph, and is then released, determining whether there is enough space remaining in the target screen for storing the class of the applications, by detecting whether the sequence number of the target screen is shown in a bright yellow font;

    or, after the icon of the application is moved into an area containing a sequence number of a target screen or into an area containing a target class of applications in the double-layer annular graph, and is then released, determining whether there is enough space remaining in the target screen for storing the icon of the application if the area contains the sequence number of the target screen, by detecting whether the sequence number of the target screen is shown in the bright yellow font; determining whether there is enough space remaining in a screen containing the target class of the applications for storing the icon of the application if the area contains the target class of the applications, by detecting whether the target class of the applications is shown in the bright yellow font;

    wherein the displaying module (703, 803) is further configured for:

    if there is enough space remaining in the target screen for storing the class of the applications, highlighting the area containing the sequence number of the target screen in the single-layer annular graph, indicating that the class of applications is moved successfully;

    if there is enough space remaining in the target screen for storing the icon of the application, highlighting the area containing the sequence number of the target screen in the double-layer annular graph;

    if there is enough space remaining in the screen containing the target class of applications for storing the icon of the application, highlighting the area containing the target class of the applications in the double-layer annular graph;

    wherein the managing module (702, 802) is further configured for: updating, after successfully moving the icon object to be moved to an area on the rule graph, the table of mapping relation among a class of applications, a screen, and an application according to the move,

    wherein the displaying module (703, 803) is further configured for: cancelling display of the single-layer annular graph or the double-layer annular graph if no icon object moving operation is detected within a preset period of time,

    wherein the preset information on a class to which an application belongs comprises at least one of a default class of applications and a class of applications added or modified through an application class customizing interface,

    wherein the presetting module (701, 801) is configured for:
    respectively establishing a table Class_Screen, a table App_Class, and a table App_Screen, wherein the table Class_Screen indicates mapping relation between a class of applications and a screen; the table App_Class indicates mapping relation between an application and a class of applications; the table App_Screen indicates mapping relation between an application and a screen,

    wherein the managing module (702, 802) is configured for:

    after the class of applications is moved successfully into the area containing the sequence number of the target screen, recording information on the area containing the sequence number of the target screen to update the table Class_Screen;

    after the icon of the application is moved successfully into the area containing the target class of the applications, recording information on the area containing the target class of applications; checking the table App_Class to determine whether a mapping relation between the application and a class of applications exists to check whether the application has been classified; if the application has not been classified, deleting a mapping relation between the application and a screen in the table App_Screen, and adding a mapping relation between the application and the target class of applications in the table App_Class; when the application is previously classified, calling the table App_Class to update the mapping relation between the application and a class of applications;

    after the icon of the application is moved successfully into the area containing the sequence number of the target screen, recording the information on the area containing the sequence number of the target screen; checking the table App_Class to determine whether the mapping relation between the application and a class of applications exists to check whether the application has been classified; if the application has not been classified, calling the table App_Screen to update the mapping relation between the application and a screen; when the application is previously classified, deleting the mapping relation between the application and any class of applications in the table App_Class, and adding the mapping relation between the application and the target screen in the table App_Screen.


     
    5. The mobile terminal according to claim 4, wherein the displaying module (703, 803) is further configured for:
    refreshing application class layout and application icon layout displayed on the current screen and on a target screen according to the table of mapping relation among a class of applications, a screen, and an application updated by the managing module (702, 802).
     
    6. The mobile terminal according to claim 4, further comprising an installing module (804)
    configured for: installing a new application; and after the new application is installed successfully, sending the managing module (702, 802) an icon management message corresponding to the installation, wherein
    the managing module (702, 802) is further configured for: updating the table App_Class according to the icon management message; and
    the displaying module (703, 803) is further configured for: displaying icons of applications by class according to the table App_Class updated by the managing module (702, 802).
     


    Ansprüche

    1. Verfahren zur Anwendungssymbolverwaltung in einem mobilen Endgerät, umfassend:

    Vorgeben, durch das mobile Endgerät, von Informationen über eine Klasse, zu der eine Anwendung gehört, und Aufstellen einer Tabelle einer Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung (S101);

    Empfangen, durch das mobile Endgerät, einer Symbolgegenstand-Bewegungsanweisung (S102, S201, S301);

    Bestimmen, durch das mobile Endgerät, gemäß der Symbolgegenstand-Bewegungsanweisung, dass ein Symbolgegenstand, der bewegt werden soll, eine Klasse von Anwendungen oder ein Symbol einer Anwendung ist (S202, S302);

    Erfassen, durch das mobile Endgerät, von Informationen über ein Regeldiagramm, das dem Symbolgegenstand entspricht, der gemäß der Symbolgegenstand-Bewegungsanweisung (S102) bewegt werden soll, durch:

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, die Klasse der Anwendungen ist, Erfassen, durch das mobile Endgerät, von Informationen über ein Einzelschicht-Ringdiagramm, das mit Sequenznummern von Bildschirmen markiert ist (S203);

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, das Symbol der Anwendung ist, Erfassen, durch das mobile Endgerät, von Informationen über ein Doppelschicht-Ringdiagramm, das mit den Sequenznummern der Bildschirme und der Klassen von Anwendungen markiert ist (S303);

    Berechnen, durch das mobile Endgerät, von Raum, der in jedem der Bildschirme übrigbleibt (S203, S303);

    Vergleichen, durch das mobile Endgerät, des Raums, der in jedem der Bildschirme übrigbleibt, mit Raum, der von dem Symbolgegenstand, der bewegt werden soll, belegt werden soll (S203, S303);

    Anzeigen, durch das mobile Endgerät, der Informationen über das Regeldiagramm (S102), durch:

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, die Klasse der Anwendungen ist, Anzeigen, durch das mobile Endgerät, des Einzelschicht-Ringdiagramms, das mit den Sequenznummern der Bildschirme markiert ist, auf einem aktuellen Bildschirm (S204), durch Zeigen, durch das mobile Endgerät, einer Sequenznummer eines Bildschirms in Hellgelb, wenn es genug Raum gibt, der im Bildschirm übrigbleibt, um Symbole aller Anwendungen zu speichern, die zu der Klasse der Anwendungen gehören, und durch das mobile Endgerät, Zeigen der Sequenznummer des Bildschirms in Schwarz, wenn der Bildschirm keinen ausreichenden freien Raum hat, um die Symbole der Anwendungen zu speichern, die zu der Klasse der Anwendungen gehören;

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, das Symbol der Anwendung ist, Anzeigen, durch das mobile Endgerät, des Doppelschicht-Ringdiagramms, das mit den Sequenznummern der Bildschirme und den Klassen der Anwendungen markiert ist, auf dem aktuellen Bildschirm (S304), durch Zeigen, durch das mobile Endgerät, einer Sequenznummer eines Bildschirms und irgendeiner Klasse von Anwendungen im Bildschirm in Hellgelb, wenn es genug Raum gibt, der im Bildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, und durch das mobile Endgerät, Zeigen der Sequenznummer des Bildschirms und irgendeiner Klasse der Anwendungen im Bildschirm in Schwarz, wenn der Bildschirm keinen ausreichenden freien Raum hat, um das Symbol der Anwendung zu speichern;

    nachdem die Klasse der Anwendungen in einen Bereich bewegt wird, der eine Sequenznummer eines Zielbildschirms im Einzelschicht-Ringdiagramm enthält, und dann freigegeben wird (S205), Bestimmen, durch das mobile Endgerät, ob es genug Raum gibt, der im Zielbildschirm übrigbleibt, um die Klasse der Anwendungen zu speichern (S206), durch das mobile Endgerät, Detektieren, ob die Sequenznummer eines Zielbildschirms in einer hellgelben Schrift gezeigt wird;

    oder, nachdem das Symbol der Anwendung in einen Bereich, der eine Sequenznummer eines Zielbildschirms enthält, oder in einen Bereich, der eine Zielklasse von Anwendungen im Doppelschicht-Ringdiagramm enthält, bewegt wird, und dann freigegeben wird (S305), Bestimmen, durch das mobile Endgerät, ob es genug Raum gibt, der im Zielbildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, wenn der Bereich die Sequenznummer des Zielbildschirms enthält (S306, S313), durch das mobile Endgerät, Detektieren, ob die Sequenznummer des Zielbildschirms in der hellgelben Schrift gezeigt wird; Bestimmen, durch das mobile Endgerät, ob es genug Raum gibt, der in einem Bildschirm übrigbleibt, der die Zielklasse der Anwendungen enthält, um das Symbol der Anwendung zu speichern, wenn der Bereich die Zielklasse der Anwendungen enthält (S306, S307), durch das mobile Endgerät, Detektieren, ob die Zielklasse der Anwendungen in der hellgelben Schrift gezeigt wird;

    wenn es genug Raum gibt, der in dem Zielbildschirm übrigbleibt, um die Klasse der Anwendungen zu speichern, Hervorheben, durch das mobile Endgerät, des Bereichs, der die Sequenznummer des Zielbildschirms im Einzelschicht-Ringdiagramm enthält (S207), Angeben, dass die Klasse von Anwendungen erfolgreich bewegt wird;

    wenn es genug Raum gibt, der in dem Zielbildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, Hervorheben, durch das mobile Endgerät, des Bereichs, der die Sequenznummer des Zielbildschirms im Doppelschicht-Ringdiagramm enthält (S314);

    wenn es genug Raum gibt, der in dem Bildschirm übrigbleibt, der die Zielklasse von Anwendungen enthält, um das Symbol der Anwendung zu speichern, Hervorheben, durch das mobile Endgerät, des Bereichs, der die Zielklasse der Anwendungen im Doppelschicht-Ringdiagramm enthält (S308);

    Aktualisieren, nach dem erfolgreichen Bewegen des Symbolgegenstands, der bewegt werden soll, in einen Bereich im Regeldiagramm, der Tabelle der Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung gemäß der Bewegung (S103);

    Aufheben, durch das mobile Endgerät, der Anzeige des Einzelschicht-Ringdiagramms oder des Doppelschicht-Ringdiagramms, wenn kein Symbolgegenstand-Bewegungsvorgang innerhalb eines vorgegebenen Zeitraums detektiert wird (S210, S311),

    worin die vorgegebenen Informationen über eine Klasse, zu der eine Anwendung gehört, zumindest eine von einer Standard-Klasse von Anwendungen und einer Klasse von Anwendungen, die über eine Anwendungsklasse-Customizingschnittstelle hinzugefügt oder geändert werden, umfassen,

    worin das Aufstellen einer Tabelle einer Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung umfasst:

    jeweils Aufstellen, durch das mobile Endgerät, einer Tabelle Class_Screen, einer Tabelle App_Class und einer Tabelle App_Screen, worin die Tabelle Class_Screen die Zuordnungsbeziehung zwischen einer Klasse von Anwendungen und einem Bildschirm angibt; die Tabelle App_Class die Zuordnungsbeziehung zwischen einer Anwendung und einer Klasse von Anwendungen angibt; die Tabelle App_Screen die Zuordnungsbeziehung zwischen einer Anwendung und einem Bildschirm angibt,

    worin das Aktualisieren, durch das mobile Endgerät, nach dem erfolgreichen Bewegen des Symbolgegenstands, der bewegt werden soll, in einen Bereich im Regeldiagramm, der Tabelle der Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung gemäß der Bewegung umfasst:

    nachdem die Klasse von Anwendungen in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms enthält, Aufzeichnen, durch das mobile Endgerät, von Informationen über den Bereich, der die Sequenznummer des Zielbildschirms enthält, um die Tabelle Class_Screen zu aktualisieren (S208);

    nachdem das Symbol der Anwendung in den Bereich erfolgreich bewegt wird, der die Zielklasse der Anwendungen enthält, Aufzeichnen von Informationen über den Bereich, der die Zielklasse der Anwendungen enthält (S309); Prüfen, durch das mobile Endgerät, der Tabelle App_Class, um zu bestimmen, ob eine Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen existiert, um zu prüfen, ob die Anwendung eingestuft worden ist; wenn die Anwendung nicht eingestuft worden ist, Löschen, durch das mobile Endgerät, einer Zuordnungsbeziehung zwischen der Anwendung und dem Bildschirm in der Tabelle App_Screen, und Hinzufügen, durch das mobile Endgerät, einer Zuordnungsbeziehung zwischen der Anwendung und der Zielklasse von Anwendungen in der Tabelle App_Class; wenn die Anwendung vorher eingestuft ist, Abrufen, durch das mobile Endgerät, der Tabelle App_Class, um die Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen zu aktualisieren (S309);

    nachdem das Symbol der Anwendung in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms enthält, Aufzeichnen, durch das mobile Endgerät, der Informationen über den Bereich, der die Sequenznummer des Zielbildschirms enthält; Prüfen, durch das mobile Endgerät, der Tabelle App_Class, um zu bestimmen, ob die Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen existiert, um zu prüfen, ob die Anwendung eingestuft worden ist; wenn die Anwendung nicht eingestuft worden ist, Abrufen, durch das mobile Endgerät, der Tabelle App_Screen, um die Zuordnungsbeziehung zwischen der Anwendung und einem Bildschirm zu aktualisieren; wenn die Anwendung vorher eingestuft ist, Löschen, durch das mobile Endgerät, der Zuordnungsbeziehung zwischen der Anwendung und irgendeiner Klasse von Anwendungen in der Tabelle App_Class, und Hinzufügen, durch das mobile Endgerät, der Zuordnungsbeziehung zwischen der Anwendung und dem Zielbildschirm in der Tabelle App_Screen (S315).


     
    2. Verfahren nach Anspruch 1, worin das Aktualisieren, nach dem erfolgreichen Bewegen des Symbolgegenstands, der bewegt werden soll, in einen Bereich im Regeldiagramm, der Tabelle der Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung gemäß der Bewegung umfasst:

    nachdem die Klasse von Anwendungen, die bewegt werden sollen, in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms im Einzelschicht-Ringdiagramm enthält, Auffrischen des Anwendungsklassenlayouts, das auf dem aktuellen Bildschirm angezeigt wird, und des Anwendungsklassenlayouts, das auf dem Zielbildschirm angezeigt wird (S209); oder

    nachdem das "zu bewegende" Symbol der Anwendung in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms oder die Zielklasse der Anwendungen im Doppelschicht-Ringdiagramm enthält, Auffrischen des Anwendungssymbollayouts, das auf dem aktuellen Bildschirm angezeigt wird, und des Anwendungssymbollayouts, das auf dem Zielbildschirm angezeigt wird (S310).


     
    3. Verfahren nach Anspruch 1, ferner umfassend: nach dem Vorgeben von Informationen über eine Klasse, zu der eine Anwendung gehört, und Aufstellen einer Tabelle einer Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung,
    Aktualisieren der Tabelle App_Class gemäß Informationen über eine Klasse, zu der eine neue Anwendung gehört, die bei der Installation der neuen Anwendung vorgegeben sind (S606-S608).
     
    4. Mobiles Endgerät, umfassend:

    ein Vorgabemodul (701, 801), das dafür eingerichtet ist: Informationen über eine Klasse, zu der eine Anwendung gehört, vorzugeben und eine Tabelle einer Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung aufzustellen;

    ein Verwaltungsmodul (702, 802), das dafür eingerichtet ist:

    eine Symbolgegenstand-Bewegungsanweisung zu empfangen;

    zu bestimmen, gemäß der Symbolgegenstand-Bewegungsanweisung, dass ein Symbolgegenstand, der bewegt werden soll, eine Klasse von Anwendungen oder ein Symbol einer Anwendung ist;

    Informationen über ein Regeldiagramm zu erfassen, das dem Symbolgegenstand entspricht, der gemäß der Symbolgegenstand-Bewegungsanweisung bewegt werden soll, durch:

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, die Klasse der Anwendungen ist, Erfassen von Informationen über ein Einzelschicht-Ringdiagramm, das mit Sequenznummern von Bildschirmen markiert ist;

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, das Symbol der Anwendung ist, Erfassen von Informationen über ein Doppelschicht-Ringdiagramm, das mit den Sequenznummern der Bildschirme und der Klassen von Anwendungen markiert ist;

    den Raum, der in jedem der Bildschirme übrigbleibt, zu berechnen;

    den Raum, der in jedem der Bildschirme übrigbleibt, mit dem Raum, der von dem Symbolgegenstand, der bewegt werden soll, belegt werden soll, zu vergleichen; und

    ein Anzeigemodul (703, 803), das dafür eingerichtet ist, die Informationen über das Regeldiagramm anzuzeigen, durch:

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, die Klasse der Anwendungen ist, Anzeigen des Einzelschicht-Ringdiagramms, das mit den Sequenznummern der Bildschirme markiert ist, auf einem aktuellen Bildschirm, durch Zeigen einer Sequenznummer eines Bildschirms in Hellgelb, wenn es genug Raum gibt, der im Bildschirm übrigbleibt, um Symbole aller Anwendungen zu speichern, die zu der Klasse der Anwendungen gehören, und Zeigen der Sequenznummer des Bildschirms in Schwarz, wenn der Bildschirm keinen ausreichenden freien Raum hat, um die Symbole der Anwendungen zu speichern, die zu der Klasse der Anwendungen gehören;

    wenn es gemäß der Symbolgegenstand-Bewegungsanweisung bestimmt wird, dass der Symbolgegenstand, der bewegt werden soll, das Symbol der Anwendung ist, Anzeigen des Doppelschicht-Ringdiagramms, das mit den Sequenznummern der Bildschirme und den Klassen der Anwendungen markiert ist, auf dem aktuellen Bildschirm, durch Zeigen einer Sequenznummer eines Bildschirms und irgendeiner Klasse von Anwendungen im Bildschirm in Hellgelb, wenn es genug Raum gibt, der im Bildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, und Zeigen der Sequenznummer des Bildschirms und irgendeiner Klasse der Anwendungen im Bildschirm in Schwarz, wenn der Bildschirm keinen

    ausreichenden freien Raum hat, um das Symbol der Anwendung zu speichern;

    worin das Verwaltungsmodul (702, 802) ferner dafür eingerichtet ist:

    nachdem die Klasse der Anwendungen in einen Bereich bewegt wird, der eine Sequenznummer eines Zielbildschirms im Einzelschicht-Ringdiagramm enthält, und dann freigegeben wird, zu bestimmen, ob es genug Raum gibt, der im Zielbildschirm übrigbleibt, um die Klasse der Anwendungen zu speichern, durch Detektieren, ob die Sequenznummer eines Zielbildschirms in einer hellgelben Schrift gezeigt wird;

    oder, nachdem das Symbol der Anwendung in einen Bereich, der eine Sequenznummer eines Zielbildschirms enthält, oder in einen Bereich, der eine Zielklasse von Anwendungen im Doppelschicht-Ringdiagramm enthält, bewegt wird, und dann freigegeben wird, zu bestimmen, ob es genug Raum gibt, der im Zielbildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, wenn der Bereich die Sequenznummer des Zielbildschirms enthält, durch Detektieren, ob die Sequenznummer des Zielbildschirms in der hellgelben Schrift gezeigt wird; zu bestimmen, ob es genug Raum gibt, der in einem Bildschirm übrigbleibt, der die Zielklasse der Anwendungen enthält, um das Symbol der Anwendung zu speichern, wenn der Bereich die Zielklasse der Anwendungen enthält, durch Detektieren, ob die Zielklasse der Anwendungen in der hellgelben Schrift gezeigt wird;

    worin das Anzeigemodul (703, 803) ferner dafür eingerichtet ist:

    wenn es genug Raum gibt, der in dem Zielbildschirm übrigbleibt, um die Klasse der Anwendungen zu speichern, den Bereich hervorzuheben, der die Sequenznummer des Zielbildschirms im Einzelschicht-Ringdiagramm enthält, anzugeben, dass die Klasse von Anwendungen erfolgreich bewegt wird;

    wenn es genug Raum gibt, der in dem Zielbildschirm übrigbleibt, um das Symbol der Anwendung zu speichern, den Bereich hervorzuheben, der die Sequenznummer des Zielbildschirms im Doppelschicht-Ringdiagramm enthält;

    wenn es genug Raum gibt, der in dem Bildschirm übrigbleibt, der die Zielklasse von Anwendungen enthält, um das Symbol der Anwendung zu speichern, den Bereich hervorzuheben, der die Zielklasse der Anwendungen im Doppelschicht-Ringdiagramm enthält;

    worin das Verwaltungsmodul (702, 802) ferner dafür eingerichtet ist: nach dem erfolgreichen Bewegen des Symbolgegenstands, der bewegt werden soll, in einen Bereich im Regeldiagramm, die Tabelle der Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung gemäß der Bewegung zu aktualisieren;

    worin das Anzeigemodul (703, 803) ferner dafür eingerichtet ist: die Anzeige des Einzelschicht-Ringdiagramms oder des Doppelschicht-Ringdiagramms aufzuheben, wenn kein Symbolgegenstand-Bewegungsvorgang innerhalb eines vorgegebenen Zeitraums detektiert wird,

    worin die vorgegebenen Informationen über eine Klasse, zu der eine Anwendung gehört, zumindest eine von einer Standard-Klasse von Anwendungen und einer Klasse von Anwendungen, die über eine Anwendungsklasse-Customizingschnittstelle hinzugefügt oder geändert werden, umfassen,

    worin das Vorgabemodul (701, 801) dafür eingerichtet ist:
    jeweils eine Tabelle Class_Screen, eine Tabelle App_Class und eine Tabelle App_Screen aufzustellen, worin die Tabelle Class_Screen die Zuordnungsbeziehung zwischen einer Klasse von Anwendungen und einem Bildschirm angibt; die Tabelle App_Class die Zuordnungsbeziehung zwischen einer Anwendung und einer Klasse von Anwendungen angibt; die Tabelle App_Screen die Zuordnungsbeziehung zwischen einer Anwendung und einem Bildschirm angibt,

    worin das Verwaltungsmodul (702, 802) dafür eingerichtet ist:

    nachdem die Klasse von Anwendungen in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms enthält, Informationen über den Bereich aufzuzeichnen, der die Sequenznummer des Zielbildschirms enthält, um die Tabelle Class_Screen zu aktualisieren;

    nachdem das Symbol der Anwendung in den Bereich erfolgreich bewegt wird, der die Zielklasse der Anwendungen enthält, Informationen über den Bereich aufzuzeichnen, der die Zielklasse der Anwendungen enthält; die Tabelle App_Class zu prüfen, um zu bestimmen, ob eine Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen existiert, um zu prüfen, ob die Anwendung eingestuft worden ist; wenn die Anwendung nicht eingestuft worden ist, eine Zuordnungsbeziehung zwischen der Anwendung und dem Bildschirm in der Tabelle App_Screen zu löschen, und eine Zuordnungsbeziehung zwischen der Anwendung und der Zielklasse von Anwendungen in der Tabelle App_Class hinzuzufügen; wenn die Anwendung vorher eingestuft ist, die Tabelle App_Class abzurufen, um die Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen zu aktualisieren;

    nachdem das Symbol der Anwendung in den Bereich erfolgreich bewegt wird, der die Sequenznummer des Zielbildschirms enthält, die Informationen über den Bereich aufzuzeichnen, der die Sequenznummer des Zielbildschirms enthält; die Tabelle App_Class zu prüfen, um zu bestimmen, ob die Zuordnungsbeziehung zwischen der Anwendung und einer Klasse von Anwendungen existiert, um zu prüfen, ob die Anwendung eingestuft worden ist; wenn die Anwendung nicht eingestuft worden ist, die Tabelle App_Screen abzurufen, um die Zuordnungsbeziehung zwischen der Anwendung und einem Bildschirm zu aktualisieren; wenn die Anwendung vorher eingestuft ist, die Zuordnungsbeziehung zwischen der Anwendung und irgendeiner Klasse von Anwendungen in der Tabelle App_Class zu löschen, und die Zuordnungsbeziehung zwischen der Anwendung und dem Zielbildschirm in der Tabelle App_Screen hinzuzufügen.


     
    5. Mobiles Endgerät nach Anspruch 4, worin das Anzeigemodul (703, 803) ferner dafür eingerichtet ist:
    das Anwendungsklassenlayout und das Anwendungsklassenlayout, die auf dem aktuellen Bildschirm und auf einem Zielbildschirm angezeigt werden, gemäß der Tabelle der Zuordnungsbeziehung zwischen einer Klasse von Anwendungen, einem Bildschirm und einer Anwendung, die vom Verwaltungsmodul (702, 802) aktualisiert wird, aufzufrischen.
     
    6. Mobiles Endgerät nach Anspruch 4, ferner umfassend ein Installationsmodul (804), das dafür eingerichtet ist: eine neue Anwendung zu installieren; und nachdem die neue Anwendung erfolgreich installiert ist, dem Verwaltungsmodul (702, 802) eine Symbolverwaltungsnachricht zu senden, die der Installation entspricht, worin
    das Verwaltungsmodul (702, 802) ferner dafür eingerichtet ist: die Tabelle App_Class gemäß der Symbolverwaltungsnachricht zu aktualisieren; und
    das Anzeigemodul (703, 803) ferner dafür eingerichtet ist: Symbole von Anwendungen nach Klasse gemäß der Tabelle App_Class anzuzeigen, die vom Verwaltungsmodul (702, 802) aktualisiert ist.
     


    Revendications

    1. Procédé de gestion d'icônes d'application dans un terminal mobile, comprenant :

    le préréglage, par le terminal mobile, d'informations sur une classe à laquelle appartient une application, et l'établissement d'une table de relation de mappage entre une classe d'applications, un écran et une application (S 101) ;

    la réception, par le terminal mobile, d'une instruction de déplacement d'objet d'icône (S102, S201, S301) ;

    la détermination, par le terminal mobile, selon l'instruction de déplacement d'objet d'icône, d'un objet d'icône à déplacer pour être une classe d'applications ou une icône d'une application (S202, S302);

    l'acquisition, par le terminal mobile, des informations sur un graphe de règles correspondant à l'objet d'icône à déplacer selon l'instruction de déplacement d'objet d'icône (S 102), par :

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est la classe des applications, l'acquisition, par le terminal mobile, des informations sur un graphe annulaire monocouche marqué avec des numéros de séquence d'écrans (S203) ;

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est l'icône de l'application, l'acquisition, par le terminal mobile, des informations sur un graphe annulaire à double couche marqué avec les numéros de séquence des écrans et des classes d'applications (S303) ;

    le calcul, par le terminal mobile, de l'espace restant dans chacun des écrans (S203, S303) ;

    la comparaison, par le terminal mobile, de l'espace restant dans chacun des écrans avec l'espace à occuper par l'objet d'icône à déplacer (S203, S303) ;

    l'affichage, par le terminal mobile, des informations sur le graphe de règles (S 102), par :

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est la classe des applications, l'affichage, par le terminal mobile, du graphe annulaire monocouche marqué avec les numéros de séquence des écrans sur un écran courant (S204), en affichant, par le terminal mobile, un numéro de séquence d'un écran en jaune vif lorsqu'il reste suffisamment d'espace dans l'écran pour stocker des icônes de toutes les applications appartenant à la classe des applications, et par le terminal mobile, l'affichage du numéro de séquence de l'écran en noir lorsque l'écran n'a pas suffisamment d'espace libre pour stocker les icônes des applications appartenant à la classe des applications ;

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est l'icône de l'application, l'affichage, par le terminal mobile, du graphe annulaire à double couche marqué avec les numéros de séquence des écrans et les classes des applications sur l'écran actuel (S304), en affichant, par le terminal mobile, un numéro de séquence d'un écran et toute classe d'applications dans l'écran en jaune vif lorsqu'il reste suffisamment d'espace dans l'écran pour stocker l'icône de l'application, et par le terminal mobile, affichant le numéro de séquence de l'écran et toute classe des applications dans l'écran en noir lorsque l'écran n'a pas suffisamment d'espace libre pour stocker l'icône de l'application ;

    une fois que la classe des applications est déplacée dans une zone contenant un numéro de séquence d'un écran cible dans le graphe annulaire monocouche, et est ensuite libérée (S205), la détermination, par le terminal mobile, s'il reste suffisamment d'espace dans l'écran cible pour stocker la classe des applications (S206), par le terminal mobile, détectant si le numéro de séquence de l'écran cible est affiché dans une police jaune vif ;

    ou, après que l'icône de l'application a été déplacée dans une zone contenant un numéro de séquence d'un écran cible ou dans une zone contenant une classe cible d'applications dans le graphe annulaire à double couche, et est ensuite libérée (S305), la détermination, par le terminal mobile, s'il reste suffisamment d'espace dans l'écran cible pour stocker l'icône de l'application si la zone contient le numéro de séquence de l'écran cible (S306, S313), par le terminal mobile, la détection si le numéro de séquence de l'écran cible est affiché dans la police jaune vif ; la détermination, par le terminal mobile, s'il reste suffisamment d'espace dans un écran contenant la classe cible des applications pour stocker l'icône de l'application si la zone contient la classe cible des applications (S306, S307), par le terminal mobile, la détection si la classe cible des applications est affichée dans la police jaune vif ;

    s'il reste suffisamment d'espace dans l'écran cible pour stocker la classe des applications, la mise en évidence, par le terminal mobile, de la zone contenant le numéro de séquence de l'écran cible dans le graphe annulaire monocouche (S207), indiquant que la classe des applications est déplacée avec succès ;

    s'il reste suffisamment d'espace dans l'écran cible pour stocker l'icône de l'application, la mise en évidence, par le terminal mobile, de la zone contenant le numéro de séquence de l'écran cible dans le graphe annulaire à double couche (S314) ;

    s'il reste suffisamment d'espace dans l'écran contenant la classe cible d'applications pour stocker l'icône de l'application, la mise en évidence, par le terminal mobile, de la zone contenant la classe cible des applications dans le graphe annulaire à double couche (S308) ;

    la mise à jour, après avoir déplacé avec succès l'objet d'icône à déplacer vers une zone sur le graphe de règles, de la table de relation de mappage entre une classe d'applications, un écran et une application selon le déplacement (S 103) ;

    l'annulation, par le terminal mobile, de l'affichage du graphe annulaire monocouche ou du graphe annulaire à double couche si aucune opération de déplacement d'objet d'icône n'est détectée dans

    une période de temps prédéfinie (S210, S311),

    où les informations prédéfinies sur une classe à laquelle appartient une application comprennent au moins l'une d'une classe par défaut d'applications et d'une classe d'applications ajoutées ou modifiées par l'intermédiaire d'une interface de personnalisation de classe d'application, où l'établissement d'une table de relation de mappage parmi une classe d'applications, un écran et une application comprend :
    l'établissement respectivement, par le terminal mobile, d'une table Class_Screen, d'une table App_Class et d'une table App_Screen, où la table Class_Screen indique une relation de mappage entre une classe d'applications et un écran ; la table App_Class indique une relation de mappage entre une application et une classe d'applications ; la table App_Screen indique une relation de mappage entre une application et un écran,

    où la mise à jour, par le terminal mobile, après avoir déplacé avec succès l'objet d'icône à déplacer vers une zone sur le graphe de règles, de la table de relation de mappage entre une classe d'applications, un écran et une application selon le déplacement comprend :

    une fois que la classe d'applications a été déplacée avec succès dans la zone contenant le numéro de séquence de l'écran cible, l'enregistrement, par le terminal mobile, des informations sur la zone contenant le numéro de séquence de l'écran cible pour mettre à jour la table Class_Screen (S208) ;

    une fois que l'icône de l'application a été déplacée avec succès dans la zone contenant la classe cible des applications, l'enregistrement des informations sur la zone contenant la classe cible des applications (S309) ; la vérification, par le terminal mobile, de la table App Class pour déterminer si une relation de mappage entre l'application et une classe d'applications existe pour vérifier si l'application a été classée ;

    si l'application n'a pas été classée, la suppression, par le terminal mobile, d'une relation de mappage entre l'application et un écran dans la table App_Screen, et l'ajout, par le terminal mobile, d'une relation de mappage entre l'application et la classe cible d'applications dans la table App_Class ; lorsque l'application est précédemment classée, l'appel, par le terminal mobile, de la table App_Class pour mettre à jour la relation de mappage entre l'application et une classe d'applications (S309) ;

    après que l'icône de l'application a été déplacée avec succès dans la zone contenant le numéro de séquence de l'écran cible, l'enregistrement, par le terminal mobile, des informations sur la zone contenant le numéro de séquence de l'écran cible ; la vérification, par le terminal mobile, de la table App_Class pour déterminer si la relation de mappage entre l'application et une classe d'applications existe pour vérifier si l'application a été classée ; si l'application n'a pas été classée, l'appel, par le terminal mobile, de la table App_Screen pour mettre à jour la relation de mappage entre l'application et un écran ; lorsque l'application est précédemment classée, la suppression, par le terminal mobile, de la relation de mappage entre l'application et une classe quelconque d'applications dans la table App_Class, et l'ajout, par le terminal mobile, de la relation de mappage entre l'application et l'écran cible dans la table App_Screen (S315).


     
    2. Procédé selon la revendication 1, où la mise à jour, après avoir déplacé avec succès l'objet d'icône à déplacer vers une zone sur le graphe de règles, de la table de relation de mappage parmi une classe d'applications, un écran et une application selon le déplacement comprend :

    une fois que la classe d'applications à déplacer a été déplacée avec succès vers la zone contenant le numéro de séquence de l'écran cible dans le graphe annulaire monocouche, l'actualisation de la disposition de classe d'application affichée sur l'écran actuel et de la disposition de classe d'application affichée sur l'écran cible (S209) ; ou

    après que l'icône à déplacer de l'application a été déplacée avec succès vers la zone contenant le numéro de séquence de l'écran cible ou de la classe cible d'applications dans le graphe annulaire à double couche, l'actualisation de la disposition des icônes d'application affichée sur l'écran actuel et de la disposition des icônes d'application affichée sur l'écran cible (S310).


     
    3. Procédé selon la revendication 1, comprenant en outre : après les informations de préréglage sur une classe à laquelle appartient une application, et l'établissement d'une table de relation de mappage parmi une classe d'applications, un écran et une application,
    une mise à jour de la table App_Class selon des informations sur une classe à laquelle appartient une nouvelle application prédéfinie lors de l'installation de la nouvelle application (S606-S608).
     
    4. Terminal mobile, comprenant :
    un module de préréglage (701, 801) configuré pour : prérégler des informations sur une classe à laquelle appartient une application, et établir une table de relation de mappage entre une classe d'applications, un écran et une application ;
    un module de gestion (702, 802) configuré pour :

    recevoir une instruction de déplacement d'objet d'icône ;

    déterminer, selon l'instruction de déplacement d'objet d'icône, un objet d'icône à déplacer pour être une classe d'applications ou une icône d'une application ;

    acquérir des informations sur un graphe de règles correspondant à l'objet d'icône à déplacer selon l'instruction de déplacement d'objet d'icône, par :

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est la classe des applications, acquisition des informations sur un graphe annulaire monocouche marqué avec des numéros de séquence d'écrans ;

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est l'icône de l'application, acquisition des informations sur un graphe annulaire à double couche marqué avec les numéros de séquence des écrans et des classes d'applications ;

    calcul de l'espace restant dans chacun des écrans ;

    comparaison de l'espace restant dans chacun des écrans avec l'espace à occuper par l'objet d'icône à déplacer ; et

    un module d'affichage (703, 803) configuré pour : afficher les informations sur le graphe de règles, par :

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est la classe des applications, affichage du graphe annulaire monocouche marqué avec les numéros de séquence des écrans sur un écran courant, affichant un numéro de séquence d'un écran en jaune vif lorsqu'il reste suffisamment d'espace dans l'écran pour stocker des icônes de toutes les applications appartenant à la classe des applications, et affichage du numéro de séquence de l'écran en noir lorsque l'écran ne dispose pas d'un espace libre suffisant pour stocker les icônes des applications appartenant à la classe des applications ;

    lorsqu'il est déterminé selon l'instruction de déplacement d'objet d'icône que l'objet d'icône à déplacer est l'icône de l'application, affichage du graphe annulaire à double couche marqué avec les numéros de séquence des écrans et les classes des applications sur l'écran actuel, en affichant un numéro de séquence d'un écran et toute classe d'applications dans l'écran en jaune vif lorsqu'il reste suffisamment d'espace dans l'écran pour stocker l'icône de l'application, et affichage du numéro de séquence de l'écran et toute classe des applications dans l'écran en noir lorsque l'écran n'a pas

    suffisamment d'espace libre pour stocker l'icône de l'application,

    où le module de gestion (702, 802) est en outre configuré pour :

    une fois que la classe des applications est déplacée dans une zone contenant un numéro de séquence d'un écran cible dans le graphe annulaire monocouche, et est ensuite libérée, déterminer s'il reste suffisamment d'espace dans l'écran cible pour stocker la classe des applications, en détectant si le numéro de séquence de l'écran cible est affiché dans une police jaune vif ;

    ou, une fois que l'icône de l'application a été déplacée dans une zone contenant un numéro de séquence d'un écran cible ou dans une zone contenant une classe cible d'applications dans le graphe annulaire à double couche, et est ensuite libérée, déterminer s'il reste suffisamment d'espace dans l'écran cible pour stocker l'icône de l'application si la zone contient le numéro de séquence de l'écran cible, en détectant si le numéro de séquence de l'écran cible est affiché dans la police jaune vif ; déterminer s'il reste suffisamment d'espace dans un écran contenant la classe cible des applications pour stocker l'icône de l'application si la zone contient la classe cible des applications, en détectant si la classe cible des applications est affichée dans la police jaune vif ;

    où le module d'affichage (703, 803) est en outre configuré pour :

    s'il reste suffisamment d'espace dans l'écran cible pour stocker la classe des applications, mettre en évidence la zone contenant le numéro de séquence de l'écran cible dans le graphe annulaire monocouche, indiquant que la classe des applications a été déplacée avec succès ;

    s'il reste suffisamment d'espace dans l'écran cible pour stocker l'icône de l'application, mettre en évidence la zone contenant le numéro de séquence de l'écran cible dans le graphe annulaire à double couche ;

    s'il reste suffisamment d'espace dans l'écran contenant la classe cible d'applications pour stocker l'icône de l'application, mettre en évidence la zone contenant la classe cible des applications dans le graphe annulaire à double couche ;

    où le module de gestion (702, 802) est en outre configuré pour : mettre à jour, après avoir déplacé avec succès l'objet d'icône à déplacer vers une zone sur le graphe de règles, la table de relation de mappage entre une classe d'applications, un écran et une application selon le déplacement,

    où le module d'affichage (703, 803) est en outre configuré pour : annuler l'affichage du graphe annulaire monocouche ou du graphe annulaire à double couche si aucune opération de déplacement d'objet d'icône n'est détectée dans une période de temps prédéfinie,
    où les informations prédéfinies sur une classe à laquelle appartient une application comprennent au moins l'une d'une classe par défaut d'applications et d'une classe d'applications ajoutées ou modifiées par l'intermédiaire d'une interface de personnalisation de classe d'application, où le module de préréglage (701, 801) est configuré pour :

    établir respectivement une table Class_Screen, une table App_Class et une table App_Screen, où la table Class_Screen indique une relation de mappage entre une classe d'applications et un écran ; la table App_Class indique une relation de mappage entre une application et une classe d'applications ; la table App_Screen indique une relation de mappage entre une application et un écran,

    où le module de gestion (702, 802) est configuré pour :

    une fois que la classe d'applications a été déplacée avec succès dans la zone contenant le numéro de séquence de l'écran cible, enregistrer des informations sur la zone contenant le numéro de séquence de l'écran cible pour mettre à jour la table Class_Screen ;

    une fois que l'icône de l'application a été déplacée avec succès dans la zone contenant la classe cible des applications, enregistrer des informations sur la zone contenant la classe cible des applications ; vérifier la table App_Class pour déterminer si une relation de mappage entre l'application et une classe d'applications existe pour vérifier si l'application a été classée ; si l'application n'a pas été classée, supprimer une relation de mappage entre l'application et un écran dans la table App_Screen, et ajouter une relation de mappage entre l'application et la classe cible des applications dans la table App_Class ; lorsque l'application est précédemment classée, appeler la table App_Class pour mettre à jour la relation de mappage entre l'application et une classe d'applications ;

    une fois que l'icône de l'application a été déplacée avec succès dans la zone contenant le numéro de séquence de l'écran cible, enregistrer les informations sur la zone contenant le numéro de séquence de l'écran cible ; vérifier la table App_Class pour déterminer si la relation de mappage entre l'application et une classe d'applications existe pour vérifier si l'application a été classée ; si l'application n'a pas été classée, appeler la table App_Screen pour mettre à jour la relation de mappage entre l'application et un écran ; lorsque l'application est précédemment classée, supprimer la relation de mappage entre l'application et toute classe d'applications dans la table App_Class, et ajouter la relation de mappage entre l'application et l'écran cible dans la table App_Screen.


     
    5. Terminal mobile selon la revendication 4, où le module d'affichage (703, 803) est en outre configuré pour :
    actualiser la disposition de classe d'application et la disposition d'icône d'application affichées sur l'écran actuel et sur un écran cible selon la table de relation de mappage entre une classe d'applications, un écran et une application mise à jour par le module de gestion (702, 802).
     
    6. Terminal mobile selon la revendication 4, comprenant en outre un module d'installation (804) configuré pour : installer une nouvelle application ; et après que la nouvelle application a été installée avec succès, envoyer au module de gestion (702, 802) un message de gestion d'icône correspondant à l'installation, où
    le module de gestion (702, 802) est en outre configuré pour : mettre à jour la table App_Class selon le message de gestion d'icônes ; et
    le module d'affichage (703, 803) est en outre configuré pour : afficher des icônes d'applications par classe selon la table App_Class mise à jour par le module de gestion (702, 802).
     




    Drawing























    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description