Method and electronic permission management unit for objects

Cross-reference

[01] Missing.

TECHNICAL FIELD OF THE INVENTION

[02] This technical solution refers to application programming interfaces (APIs) in general, and more particularly to a system and method for managing objects in various implementations of the API.

Prior Art

[03] Various global or local communication networks (the Internet, the World Wide Web, local networks and the like) offer the user a large amount of information. The information includes contextual sections such as, among others, news and current events, maps, company information, financial information and resources, traffic information, games and entertainment information. Users use a variety of electronic devices (desktop computer, laptop computer, laptop, smartphone, tablets and the like) to gain access to rich information content (for example, images, audio and video files, animated images and other multimedia content of such networks). Such electronic devices are becoming more popular in everyday life due to their increasing functionality. Thus, the software becomes more and more extensive in size and quantity, and, consequently, the need for joint work of various programs increases.

[04] The Application Programming Interface (API) is a set of procedures, protocols and tools for creating software applications. The API specifies how exactly the various software components should interact. APIs are used, for example, to develop components of the graphical user interface (GUI). The API helps to develop software by providing all the building blocks that the programmer further composes together. There are various types of APIs for operating systems, applications and Web sites.

[05] Many APIs use object-oriented programming in which programmers define not only the data type in the data structure, but also the types of operations (functions) that will be applied to the data structure. Therefore, the data structure becomes an object that includes data and functions. In general, an "object" is an element that can be individually selected and managed. It can include forms and images that appear on the screen of the monitor, as well as less tangible objects. In object-oriented programming, for example, an object is a stand-alone element that consists of data and procedures for managing data. Object-oriented programming methods allow programmers to create modules that do not need to be changed at a time when a new object is added, since a programmer can easily create a new object that inherits many of the characteristics of existing objects, which makes object-oriented objects more convenient for modification. Additionally, programmers can create relationships between objects. For example, objects can inherit characteristics from other objects.

[06] Since the number of computer programs (for example, browsers, applications, applets, and so on) that are used by electronic devices is growing, so is the need for joint management of objects. In general, objects are managed by the central permissions manager, which facilitates the definition and / or issuance of permits that are necessary for the work. However, there is a need for improved methods and systems for managing objects within the software environment, for example, the API.

[07] US Patent No. US 6,993,665, publ. January 31, 2006 describes the methods and device for providing a permission manager that is able to help an applet, for example, to determine and / or give permissions that are necessary for work. A device for managing permissions is described, the device includes a software application, a permission manager that is associated with a software application and receives a request sent by the software application and a software environment associated with the permission manager. A request can indicate a permission that can be requested by the permission manager. The permissions manager can access the software environment to determine the appropriate permission that is appropriate for the permission, and to determine how exactly the requested permission should be given.

[08] International Application WO 1994023362 publ. 10/13/1994 describes an object-oriented programming environment. The environment includes many classes and objects. Each object is associated with other objects in the environment by passing messages that execute methods in these other objects. The environment contains at least one target object that contains one or more generic methods that are used to communicate with another entity. These universal methods usually includeto all target objects in the environment, simultaneously with the corresponding generic instances of variables that were used by universal methods, thereby forming a universal protocol or interface for the target objects. Behavioral objects, objects that implement the behavior of other objects, receive and modify the properties of the target object by directly applying the universal methods located in the target object. The connection between the behavioral object and the target object is carried out according to the universal protocol (method and instances of variables).

[09] Intermediary templates are known for defining an object, which is a description of how exactly objects interact. Given the mediation template, the relationship between objects is described using an intermediary object. Objects no longer interact with each other, they interact through an intermediary. This reduces the dependency between related objects, which reduces connectivity (see "Mediator (Design Pattern)" on Wikipedia.) Wikipedia Foundation, November 28, 2014. Web .https://ru.wikipedia.org/wiki/Prointer_ (Design Pattern))

Disclosure of Invention

[10] The object of the proposed technical solution is to eliminate at least some of the disadvantages of the prior art. The embodiments of this technical solution were developed based on the inventors' beliefs that there is a need for methods and systems for managing objects in a software environment, for example, an API.

[11] One object of the present technical solution is a method for managing permissions for objects, objects are executed by the server as part of program procedures, the method is performed on an electronic device (eg, client device or server). The method includes obtaining the first request for the first object from the first request item, the first request including the request to perform the first action on the first object, the execution of the first action requires the first permission. In response to the first request, the first permission to perform the first action to the first interrogator is given, and the first interrogator, therefore, controls the first object. A second request is received for the first object from the second interrogator, the second request includes a request to perform a second action on the first object, the second action requires a second permission. In response to said second request, the second request is transmitted to the first interrogator, the first interrogator controls the first entity. One of the following is fulfilled: the first interrogator gives the second permission to the second interrogator, which allows performing the second action by the second interrogator, the second interrogator, therefore, controls the first object, and the first authorization and execution of the first action is completed by the first interrogator; or the first interrogator does not give a second permission to the second interrogator, thereby not allowing the second to perform the second action, the first interrogator continues to monitor the first object. that allows to perform the second action by the second interrogator, the second interrogator, therefore, controls the first object, and the completion of the first permission and execution of the first action by the first interrogator; or the first interrogator does not give a second permission to the second interrogator, thereby not allowing the second to perform the second action, the first interrogator continues to monitor the first object. that allows to perform the second action by the second interrogator, the second interrogator, therefore, controls the first object, and the completion of the first permission and execution of the first action by the first interrogator; or the first interrogator does not give a second permission to the second interrogator, thereby not allowing the second to perform the second action, the first interrogator continues to monitor the first object.

[12] In some embodiments of the present technical solution, in response to the fact that the first interrogator gives the second permission to the second interrogator and allows the second action to be performed by the second interrogator, the first interrogator nevertheless continues to monitor the first entity.

[13] In some embodiments of the present technical solution, the first action and the second action are the same action. In alternative embodiments of the present technical solution, the first action and the second action are different actions. In some embodiments of the present technical solution, the second action includes a first action and an additional action. In such embodiments, the first interrogator can partially give a second permission to the second interrogator, which allows the second requestor to perform part of the second action. For example, the first interrogator can partially give the second permission to the second interrogator, which allows the first action to be performed by the second interrogator and does not allow the second interrogator to perform an additional action. In alternative embodiments of the present technical solution, the first interrogator can allow the second requestor to perform an additional action and not allow the execution of the first action by the second interrogator. In those embodiments of this technical solution where the permission was partially given to the second interrogator, the first interrogator continues to partially control the first entity, the second interrogator controls the portion of the second action for which permission was granted and whose execution was authorized.

[14] In some embodiments of the present technical solution, the first object includes a user interface element, a pointer, an audio object, an image object, a video object, or a text object. Non-limiting examples of user interface elements include text fields, toolbars, menu bars and buttons. In some embodiments of the present technical solution, the first object may be a pop-up object.

[15] In some embodiments of the present technical solution, the first action, the second action and the additional action include, independently, one or more of: demonstrating the first object, allowing the first object to appear, entering text into the first object, inputting data or information in the first object, clicking on the first object, selecting the first object, selecting the part of the first object, deleting the first object.

[16] Another object of the present technical solution is an electronic device associated with a user, the electronic device includes a communication interface for communicating with the server through a communication interface, the server is configured to perform objects as part of program procedures; and a processor operatively coupled to the communication interface. The processor is further configured to receive the first request for the first object from the first request element, the first request includes a request to perform the first action on the first object, the execution of the first action requires the first permission. In response to said first request, the processor is configured to give a first permission to perform the first action to the first interrogator, and the first interrogator, therefore, controls the first entity. The processor is further adapted to receive a second request for the first object from the second interrogator, the second request includes a request to perform a second action on the first entity, the second action requires a second permission. In response to said second request, the processor is configured to transmit the second request to the first interrogator, the first interrogator controlling the first entity, and performing one of the following: 1) in response to the first interrogator providing a second grant to the second interrogator, the processor is executed with the ability to perform the second action by the second interrogator, the second interrogator, therefore, monitors the first object, and the completion of the first permission and the execution of the first action by the first interrogator; or 2) in response to the fact that,

[17] In some embodiments of the electronic device, in response to the fact that the first interrogator gives the second permission to the second interrogator and allows the second action to be performed by the second element, the first interrogator nevertheless continues to monitor the first entity.

[18] In some embodiments of the electronic device, the first action and the second action are the same action. In alternative embodiments of the electronic device, the first action and the second action are different actions. In some embodiments of the electronic device, the second action includes both the first action and the additional action, and the first interrogator partially gives the second permission to the second interrogator, thus the execution of the second action portion is allowed by the second interrogator. For example, in some embodiments of the present technical solution, the first interrogator partially gives a second permission to the second interrogator, which allows the first action to be performed by the second interrogator and does not allow the second interrogator to perform an additional action. In alternative embodiments of the present technical solution, the first interrogator partially gives a second permission to the second interrogator, which allows the second interrogator to perform an additional action and does not allow the first interrogator to perform the first action. In such embodiments of the present technical solution, the first interrogator continues to partially control the first entity, the second interrogator controls the portion of the second action for which permission was granted and whose execution was allowed.

[19] In some embodiments of the electronic device, the first object includes a user interface element, a pointer, an audio object, an image object, a video object, or a text object. Non-limiting examples of user interface elements include text fields, toolbars, menu bars, hyperlinks and buttons. In some embodiments of the electronic device, the first object is a pop-up object.

[20] In some embodiments of the electronic device, the first action, the second action and the additional action include, independently, one or more of: demonstrating the first object, allowing the first object to appear, and entering text into the first object, and inputting data or information to the first object, and clicking on the first object, and selecting the first object, and selecting a part of the first object, and deleting the first object.

[21] As used herein, "server" means a computer program running on appropriate equipment that is capable of receiving requests (eg from electronic devices) over a network (for example, a data network) and to fulfill these requests or initiate the execution of these requests . The equipment may be one physical computer or one physical computer system, but neither is mandatory for this technical solution. In the context of this technical solution, the use of the expression "server" does not mean that each task (for example, received commands or requests) or any specific task will be received, executed or initiated for execution by the same server (i.e., the same software and / or hardware);

[22] In the context of the present description, "electronic device" means a computing device or computer device capable of operating software suitable for the solution of an appropriate task. Thus, some examples of electronic devices (among other things) can be universal personal computers (desktop computers, laptops, netbooks, etc.), mobile computer devices, smartphones, tablets, as well as network equipment such as routers, switches and gateways . It should be borne in mind that an electronic device in the present context can behave as a server to other electronic devices. The use of the expression "electronic device" does not exclude the possibility of using multiple electronic devices to receive / send, execute or initiate the execution of any task or request, or the consequences of any task or request, or the steps of any of the above-described method. As used herein, the term "client device" refers to any of a number of client-related electronic devices associated with a user, for example, personal computers, tablets, smartphones, and the like.

[23] As used herein, a "database" means any structured data set that is independent of a particular structure, database management software, computer hardware on which data is stored, used, or otherwise available for use. The database can reside on the same hardware running a process that stores or uses information stored in the database, or it can reside on separate equipment, such as a dedicated server or multiple servers.

[24] As used herein, the term "data" includes any information that may be stored, for example, in a database, or may be transmitted electronically, for example, by a stream. Thus, the data includes, among other things, audiovisual works (images, video, sound recordings, presentations, etc.), location data, digital data, etc., text (opinions, comments, questions, messages and etc.), documents, tables, etc.

[25] As used herein, the term "computer-readable storage medium" means a carrier of absolutely any type. The computer-readable media can include volatile and nonvolatile, portable and non-portable media that are implemented in any method or technology for storing information, for example, machine-readable instructions, data structures, program modules, or other data. Computer media may include RAM, ROM, electrically erasable programmable ROM, flash memory or any other memory architecture, CDs, DVDs or other optical media, floppy disks, hard disks, magnetic cassettes, tape drives, USB keys , solid state drives, tape drives or any other media,

[26] As used herein, the term "data network" means any data transmission network, for example, a computer network, the Internet, a telephone network, a telex system, a TCP / IP network (eg, a WAN, LAN) and the like. The term "data network" includes a wired network or a directly connected network, as well as wireless communication, for example, acoustic, radio frequency, infrared and other types of wireless communication, as well as combinations of any of the foregoing.

[27] Those skilled in the art will understand that in the present description, the expression "receiving data" from a user or program implies the receipt by an electronic device of data from a user or program in the form of an electronic (or other) signal. In addition, those skilled in the art will understand that displaying the data to a user through a graphical user interface or GUI (eg, computer device screen and the like) may include transmitting a signal to the user's graphical interface, this signal contains data that can be processed, and at least some of this data can be displayed to the user through the graphical user interface. Some of these stages, as well as signal transmission / reception are well known in the art and therefore, for simplicity, have been omitted in specific parts of this specification. It is important to bear in mind that the embodiments of the signals are not particularly specifically limited. For example, signals may be transmitted and received, without limitation, by optical means (e.g., optical connection), electronic means (eg, wired or wireless) and mechanical means (eg, pressure, temperature or other suitable parameter) .

[28] As used herein, the term "cloud storage service" is a computational means in which a plurality of clients, client devices, societies, IT domains, and / or applications are managed or monitored separately in a multi-control environment. A "cloud" environment refers to a framework in which many independent users share a common infrastructure, platforms, services / applications or resources in such a way that each of them is isolated from each other. The user / client can be a company, an organization, an individual person, and the client device can refer to any of the client devices of the user as described herein. Such cloud services provide communication for use, for example, personal computers, tablets, smartphones or other user devices (home entertainment and so on). There are many types of cloud services known. For example, a cloud service may include separate administrative models that apply to blade servers in a data center, or any distribution of connected devices. Common infrastructure, platforms, services / applications or resources are usually managed by an administrator who supports the cloud service. Cloud resources can be private or public. Services / applications or resources are usually managed by an administrator who supports the cloud service. Cloud resources can be private or public. Services / applications or resources are usually managed by an administrator who supports the cloud service. Cloud resources can be private or public.

[29] In the context of the present description, the words "first", "second", "third", etc. are used in the form of adjectives solely to distinguish the nouns to which they refer, from each other, and not for the purpose of describing any particular connection between these nouns. For example, it should be borne in mind that the use of the terms "first user" and "third user" does not imply any order, assignment to a particular type, chronology, hierarchy or ranking (eg) of users / between users, as well as their use (in itself) does not imply that a certain "second user" must necessarily exist in a given situation. In the future, as indicated here in other contexts, the mention of the "first" element and the "second" element does not exclude the possibility that this is the same actual actual element. For example, in some cases, the "first" server and the "second" server may be the same software and / or hardware, and in other cases they may be different software and / or hardware.

[30] Each embodiment of this technical solution pursues at least one of the above objects and / or objects. It should be borne in mind that some of the objects of this technical solution, obtained as a result of attempts to achieve the above-mentioned goal, can satisfy other purposes not specifically indicated here.

[31] Additional and / or alternative characteristics, aspects and advantages of embodiments of this technical solution will become apparent from the following description, the accompanying drawings and the appended claims.

Brief Description of the Drawings

[32] For a better understanding of the present technical solution, as well as other aspects and features thereof, reference is made to the following description, which should be used in conjunction with the accompanying drawings, wherein:

[33] FIG. 1 is a schematic diagram of a system executed in accordance with embodiments of the present technical solution, not limiting its scope.

[34] FIG. Figure 2 shows a screenshot showing a graphical user interface that displays a street map and associated software objects.

[35] FIG. 3 is a flowchart of a method performed within the system depicted in FIG. 1, and executed with the embodiments of the present technical solution, not limiting its scope.

Detailed Description of the Invention

[36] FIG. 1 is a schematic diagram of a system 100 made in accordance with embodiments of the present technical solution, not limiting its scope. It is important to bear in mind that the following description of the system 100 is a description of exemplary embodiments of the present technical solution. Thus, the entire following description is presented only as a description of an illustrative example of this technical solution. This description is not intended to determine the scope or limits of this technical solution. Some useful examples of modifications of the system 100 can also be covered by the following description. The purpose of this is also exclusively assistance in understanding, and not the definition of the scope and boundaries of this technical solution. These modifications are not an exhaustive list, and those skilled in the art will understand that other modifications are possible. Furthermore, this should not be interpreted so that where no examples of modifications have been set forth, no modifications are possible and / or that what is described is the only implementation of this instance of this technical solution. As will be understood by those skilled in the art, this is most likely not the case. In addition, it should be borne in mind that the system 100 is in some specific manifestations a fairly simple embodiment of the present technical solution, and in such cases is presented herein in order to facilitate understanding. As will be appreciated by one skilled in the art,

[37] The system 100 includes a data network 50. The communication network 50 is typically associated with the electronic device 20 and the server 40, the server 40 is associated with a data storage device 30 that stores program code for programs 10, 15.

[38] Embodiments of the server 40 are not particularly limited, and, for example, the server 40 can be implemented as a single server. Alternatively, the server 40 may be a plurality of servers.

[39] Embodiments of the data storage device 30 are not specifically limited in any way. For example, the data storage device 30 may be a memory device such as a hard disk (not shown) embedded in the electronic device 20, or the data storage device 30 may be connected to the electronic device 20 over the data network 50 or any suitable wired or wireless connection . The data storage device 30 is typically an element capable of storing files and data, for example, program code for programs 10, 15. Similarly to the server 40, the data storage device 30 can be implemented as a single element, or alternatively as a plurality of elements. In the latter embodiment, each of the plurality of storage devices implementing the data storage device 30, can be responsible for saving files for users in a particular region; or a specific type of user; or a particular type or size of files. Alternatively, each of the plurality of storage devices implementing the data storage device 30 may be configured to store files in accordance with the load sharing principle that is performed by the monitoring element (which may be, for example, server 40 or one of multiple servers).

[40] It is important to keep in mind that any suitable hardware for storing data can be used. In some embodiments of the present technical solution, the data storage device 30 may be physically adjacent to the server 40, i. E. it does not have to be a different hardware device, as presented, although this may be so. In some embodiments of this technical solution, the data storage device 30 and / or the server 40 may be implemented in a clouded environment, for example as part of a cloud storage service.

[41] Embodiments of the electronic device 20 are not specifically limited in any way. An electronic device can be any computing device that is capable of working with suitable software for a given task, for example without restriction: general-purpose personal computers (desktop computers, laptops, netbooks, etc.), mobile computing devices, smartphones, tablets, as well as network equipment such as routers, switches and gateways. The electronic device 20 includes a processor or a central processing unit (CPU) 22 and a memory unit 25. Despite the illustrative example in FIG. 1 shows a single electronic device 20, a plurality of electronic devices can be used for receiving / transmitting,

[42] It should be understood that the electronic device 20 can behave as a server 40 with respect to other electronic devices (not shown). In other words, although the embodiment shown in FIG. 1 represents the electronic device 20 and the server 40 as separate hardware components, in some embodiments of the present technical solution, the server 40 may be physically adjacent to the electronic device 20, i. E. they are not necessarily separate hardware elements, as shown, although this may be so.

[43] Instance 11 of program 10 is loaded into memory address space 25 of electronic device 20. Embodiments of memory 25 are not specifically limited in any way. The memory 25 may comprise a virtual memory system with physical memory separate from the address space, but for the sake of simplicity, the memory is shown in FIG. 1 as a simple block 25.

[44] Instance 11 of the program is specifically executed, in turn, for instantiating a number of program objects 121 to 122 (listed together as program objects 12). Software objects can be a combination of executable code and data, and therefore can perform processing independently and / or provide data for processing by other software objects. For example, a program object, such as a function or subroutine, can be created by the parent object or even by the main program to perform some processing on behalf of the calling parent or main program. The object data can be of various types, for example: primitive data types, such as integers, real numbers, Boolean numbers, signs; and structured or abstract data types, such as, arrays or lists,

[45] As described above, program objects can contain examples of functions created during execution of program instance 11 or simple or structured data objects, some of which may contain pointer values ​​that point to other functions or data. Program objects 12 are typically arranged in a hierarchical order, with parent objects causing the instantiation of one or more child objects. For ease of understanding, only one level of child objects is shown in FIG. 1 with objects 121-122, which are instantiated by an instance of program 10. However, it will be understood that even in a medium-complexity program, a hierarchy of objects can contain multiple levels of objects.

[46] Program entities 12 may be implemented by the server 40 as part of program procedures, for example as part of programs 10, 15. It is important to keep in mind that embodiments of program objects are not specifically limited in any way. Non-limiting examples of program objects 12 include user interface elements (eg, text fields, toolbars, menu bars and buttons, and the like), pointers, audio objects, image objects, video objects, and text objects. In some embodiments of the present technical solution, the program entities 12 may be pop-up objects. Non-limiting examples of pop-up objects include objects that appear above or above the browser window with a website. For example, a pop-up object may appear at a time, when the option was selected by pressing or any other indication of the user's choice. In some embodiments of this technical solution, a pop-up object may appear when the user places the cursor (for example, hovers) on a portion of the browser window or web site. Many embodiments of popup objects can be used, as is well known in the art.

[47] The implementation of the data transmission network 50 is not specifically limited in any way, and will depend on how the electronic device 20, the server 40, and the wireless communication device 30 are implemented. In some embodiments of this technical solution, not limiting its scope, the data transmission network 50 may be the Internet. In other embodiments of the present technical solution, the data communication network 50 may be implemented differently, in the form of a global communication network, a local communication network, a private communication network, and the like. By way of example, and not limitation, in these embodiments of this technical solution in cases where the electronic device 20 is a client device, for example, a wireless communication device (eg, a smartphone), the data transmission network 50 is a wireless data link (eg, among other things, a 3G data line, a 4G data line, a Wireless Fidelity wireless network or a short WiFi®, Bluetooth®, etc.). In those examples where the electronic device 20 is a laptop computer, the data network 50 can be either wireless (Wireless Internet Fidelity or short WiFi®, Bluetooth®, etc.) or wired (Ethernet-based connection). Various electronic devices and various data networks can be implemented independently of each other. where the electronic device 20 is a portable computer, the data network 50 can be either wireless (Wireless Internet Fidelity or short WiFi®, Bluetooth®, etc.) or wired (Ethernet-based connection). Various electronic devices and various data networks can be implemented independently of each other. where the electronic device 20 is a portable computer, the data network 50 can be either wireless (Wireless Internet Fidelity or short WiFi®, Bluetooth®, etc.) or wired (Ethernet-based connection). Various electronic devices and various data networks can be implemented independently of each other.

[48] ​​For a further understanding and illustration of system 100, reference will be made to FIG. 2, which is a screenshot 200 of a graphical user interface screen that maps a street map 260 to a user (not shown), a street map 260 indicates the location of the address 250 to the user. It is important to bear in mind that Fig. 2 is presented only for the purpose of illustration and to facilitate understanding of the essence of this technical solution. It is also important to bear in mind that FIG. 2 contains a large amount of information, but only the actual parts will be numbered and described.

[49] Embodiments of the screen shot 200 are not specifically limited in any way. In one non-limiting example, the screenshot 200 may be displayed by a browser application (not shown) or opened via an Internet browser (not shown).

[50] In a non-limiting embodiment of the present technical solution shown in FIG. 2, the screen shot 200 shows a data object 210 in which a user (not shown) has entered the address 250 "address 1" (English "address1") that the user is looking for; a button entity 220 to which the user can click to initiate the display of an address 250 inputted to the data input object 210; a second button entity 230; a pointer object 240 indicating the position of the address 250 on the street map 260.

[51] In the second button entity 230, a user can click on terms ("hotels", "restaurants") to initiate a search for nearby hotels or restaurants (located near address 250). For example, if a user (not shown) clicks on the term "hotels" on the second button entity 230, a new object (not shown) may appear, the new object will point to a hotel located near address 250. In some embodiments of this technical solution , other objects can also be moved in response to the user clicking on the term "hotels" on the second button entity 230. For example, in response to clicking users on the term "hotels" on the second button entity 230, a new object (not shown) appears, the pointer object 240 and the data entry object 210 may be deleted.

[52] The implementation of the 260 street map available to the user is not specifically limited in any way. As one example, a user can access a website associated with a card or other services. For example, the Yandex Maps service can be invoked by entering a URL (for example, https://maps.yandex.com) into a browser, for example, associated with the search engine Yandex www.yandex.ru. The client device can, for example, run the Yandex browser application. It is important to bear in mind that any other commercially available or proprietary browser application and any available mapping system can be used to implement embodiments of the present technical solution that do not limit its scope.

[53] In alternative embodiments of this technical solution, a user can download the Yandex Maps application (also referred to as an "application") to a client device, for example a smartphone, and can access the mapping service using the application. In another non-limiting embodiment of this technical solution, the Yandex Maps API can be installed on a web application or site, and the user can access the mapping service using the API on a Web application or site. Other embodiments are also possible that will be apparent to those skilled in the art.

[54] Referring to Fig. 3 is a schematic diagram of a method 300 executed in accordance with embodiments of the present technical solution, not limiting its scope. Process 300 may be performed by electronic device 20.

[55] Step 302 - obtaining the first request for the first object from the first query element, the first request includes a request for execution of the first action on the first object, the execution of the first action requires the first permission

[56] The method 300 starts in step 302 where the processor 22 of the electronic device 20 receives the first request (not shown) to the first entity 121 from the server 40, the first request includes a request for executing the first action (not shown) on the first entity 121, the execution of the first action requires the first permission (not shown).

[57] In some non-limiting embodiments of this technical solution, the first request is received from the program 10 through the server 40 and the data network 50. In alternative non-limiting embodiments of the present technical solution, the first request is obtained from the instance 11 of the program 10 loaded into the memory 25 of the electronic device 20. In similar embodiments of this technical solution, the first request can be obtained from the processor 22 of the electronic device 20.

[58] The embodiments of the first object 121 are not specifically limited in any way. Referring to an exemplary embodiment of the present technical solution shown in FIG. 2, the first object 121 for illustration purposes can be considered as a pointer object 240. It is important to note that many other embodiments of this technical solution are possible. For example, in alternative embodiments of the present technical solution, the first object 121 may be a data input object 210, a button entity 220, or a second button entity 230. For the sake of simplicity of illustration, it is assumed that in the present embodiment of the present technical solution, the first object 121 is a pointer object 240.

[59] The first request includes a request to perform the first action on the first object 121. The embodiments of the first action are not specifically limited in any way. As is known in the art, various operations or functions can be performed in connection with or through software objects 12. Non-limiting examples of such actions include displaying or demonstrating an object, for example, in a GUI; permission to the appearance of the object; Enter text into the object; input data or information into the object; click on the object; selection of the object; selection of part of the object; and delete the object.

[60] Referring again to the exemplary embodiment shown in FIG. 2, the first request for the first object 121 (the corresponding pointer object 240 in this example) includes a request to display the pointer object 204 on the street map 260, at the address of the address 250. The first interrogator in this example is program 10 (or instance 11 of program 10 ), which for illustration purposes corresponds to a map application (for example, Yandex Maps).

[61] Further, in the first step 302 of the method 300 shown in FIG. 3, the first request for the first object from the first query element is received. The first request requires the first permission (not shown). In other words, the first interrogator requests permission to perform the first action on the first object. In the example shown in FIG. 2, the mapping application (not shown) asks for permission to display the pointer object 240 on the street map 260, at address 250, the user entered the address 250 into the data input object 210 and clicked on the button object 220 to initiate the address display 250.

[62] Step 304 - in response to the first request, the first permission to perform the first action to the interrogator is given, and the first interrogator, therefore, controls the first object

[63] The method 300 then proceeds to step 304. In response to receiving the first request, the first interrogator is given the first permission to perform the first action.

[64] Generally, the operating system (not shown) of the electronic device 20 includes a central permission manager (not shown) that defines the permissions within and within the system of the electronic device 20. At block 304, the first request is received by the central permissions manager, the first the permission to perform the first action is given to the first interrogator by the central permissions manager. With reference to the example shown in FIG. 2, the permission to display the pointer object 240 on the street map 260 at the address of the address 250 is given to the first interrogator by the central permissions manager (not shown) of the electronic device 20. The pointer object 240 is therefore displayed on the street map 260 at address 250, for example, on the GUI (not shown) of the electronic device 20.

[65] Continuing with step 304 of method 300, the first interrogator received the first permission from the central permission manager (not shown) of the electronic device 20, the first interrogator, therefore, monitors the first object 121 (the pointer object 240 in this case). In the context of the present description, the term "monitors" this object implies control over the permissions for a given object. Thus, although the primary central permissions manager (not shown) of the electronic device 20 primarily determines the permissions for the first entity 121, after the first permission has been given to the first interrogator, the first interrogator obtains control over the permissions for the first object 121 from the central permission manager . Further, when the first interrogator continues to monitor the first entity 121,

[66] In embodiments of this technical solution, permits are defined (given / not given) in accordance with predetermined rules. The element responsible for the permissions (for example, the central permission manager of the electronic device 20, the interrogator or the element controlling the first object 121) will determine the permissions for the objects 12 in accordance with pre-established rules. For example, the central permissions manager, API and / or the program in question can follow a set of predefined rules and procedures, as will be understood by those skilled in the art.

[67] The embodiments of the first query element are not particularly specifically limited. In some embodiments of this technical solution, the object-oriented permissions manager, separate from the central permission manager, but associated with it, becomes associated with the first interrogator. Subsequent requests related to the first object 121 will be transmitted from the central permission manager to the object-oriented permission manager associated with the first interrogator that determines the permissions for the first object 121. If another interrogator supervises the first object 121, the object-oriented permissions manager becomes bound with another interrogator and so on. If no query has been made and none of the query elements control the first object 121,

[68] The method 300 then proceeds to step 306.

[69] Step 306 - obtaining the second request for the first object from the second query element, the second request includes a request to perform a second action on the first object, the second action requires a second permission

[70] The method 300 continues in step 306 where a second request (not shown) to the first object 121 is received from the second request item (not shown), the second request includes a request for performing a second action (not shown) on the first entity 121, the second action requires a second permission (not shown).

[71] As described with reference to step 302 and the first request, the central permission manager (not shown) of the electronic device 20 receives a second request for the first entity 121 from the server 40. In some non-limiting embodiments of this technical solution, a second request is received from the second request element through the server 40 and the data transmission network 50. In alternative non-limiting embodiments of the present technical solution, the second interrogator is located in the memory 25 of the electronic device 20, and a second request is received from the processor 22 of the electronic device 20 through the central permissions manager.

[72] The embodiments of the second action are not particularly specifically limited. It is important to bear in mind that the second action may or may not be exactly the same as the first action, i. E. the first action and the second action may be the same or different. With reference to an embodiment of the present technical solution, shown in FIG. 2, the first action and the second action can display the pointer object 240 on the street map 260. For example, the second request from the second request item may be a request to display the pointer object 240 on the street map 260 in a second place (not shown) that is different from the first location corresponding to address 250. Alternatively, the second request from the second request element may be different from the first request to display the pointer object 240,

[73] In some non-limiting embodiments of the present technical solution, the second act may include both the first action and the additional action. For example, the second request from the second request element may be a request to display the pointer object 240 on the street map 260 in the second place (not shown), as well as a request for modifying the appearance of the pointer object 240. Many such embodiments are also possible, as is known to those skilled in the art.

[74] The embodiments of the second query element are not specifically limited in any way. In some non-limiting embodiments of the present technical solution, the first interrogator and the second interrogator are separate elements. For example, in the example described above, the first interrogator is program 10 (or instance 11 of program 10) corresponding to the one shown in FIG. 2 an embodiment of the present technical solution to a mapping application (eg, Yandex Maps). Continuing with this example, the second interrogator is a program 15 (or an instance (not shown) of the program 15 loaded into the address space in the memory 25 of the electronic device 20). Program 15 is separated from program 10. For example, program 10 (the first interrogator) is Yandex. Cards, and program 15 (the second interrogator) can be a Sky Maps, an application that displays maps of stars, constellations and other celestial objects. The second interrogator, Sky Maps program 15, can request permission to display the pointer object 240 on the star map (not shown) in response to the user's request.

[75] Although the first interrogator, the program 10, and the second interrogator, the program 15, are represented in FIG. 1 as separate elements, the first interrogator and the second interrogator need not necessarily be separate elements. In some non-limiting embodiments of the present technical solution, the first interrogator and the second interrogator may be the same, i. E. The first request and the second request were created by the same program. Continuing with the one shown in FIG. 2 example, the first interrogator is program 10 (or instance 11 of program 10), corresponding to Yandex, maps, Yandex. Maps request permission to display the pointer object 240 on the street map 260 at address 250. In response to the user entering the second address (not shown) in the data input 210, a second request is received from Yandex. Kart, the second request includes a request to display the pointer object 240 at the location of the second address. Many similar embodiments are possible.

[76] The method 300 then proceeds to step 308.

[77] Step 308 - in response to the second request, transmission of the second request to the first interrogator, the first interrogator controls the first entity

[78] The method 300 continues at step 308, where, in response to receiving the second request, the second request is transmitted to the first interrogator by the central permission manager, the first interrogator monitors the first entity 121. For example, the central permission manager may transmit the second request to the object-oriented permissions manager. Object-oriented permissions manager becomes associated with the first interrogator.

[79] The embodiments of the first query element are not particularly specifically limited. In some embodiments of this technical solution, the object-oriented permissions manager, separate from the central permission manager, but associated with it, becomes associated with the first interrogator. Subsequent requests related to the first object 121 will be transmitted from the central permission manager to the object-oriented permission manager associated with the first interrogator that determines the permissions for the first object 121. If another interrogator supervises the first object 121, the object-oriented permissions manager becomes bound with another interrogator and so on. If no query has been made and none of the query elements control the first object 121,

[80] As discussed previously, when the first interrogator continues to monitor the first object 121, the first interrogator will already determine permissions to perform actions on the first entity 121. Therefore, the processor 22 of the electronic device 20 issues a second request to the interrogator (program 10 in the above-described example) for Determine the permission for the second query.

[81] The method 300 continues either in step 310 or in step 312, depending on whether the first interrogator gives the second permission to the second interrogator.

[82] Step 310 - in response to the fact that the first interrogator gives the second permission to the second interrogator, the permission for the second action to be executed by the second interrogator, the second interrogator, respectively, controls the first object, and the first authorization and execution of the first action is completed by the first interrogator

[83] Step 312 - in response to the fact that the first interrogator does not give a second permission to the second interrogator and does not allow performing the second action by the second interrogator, the first interrogator continues to monitor the first object

[84] If the first interrogator gives the second permission to the second interrogator, the method proceeds to step 310, so that the second request is allowed to execute the second action. The second interrogator, therefore, controls the first object 121, and the first permission and execution of the first action by the first interrogator is completed.

[85] Continuing with the above and presented in FIG. 2 example, it is assumed that the first interrogator is program 10 (or instance 11 of program 10) corresponding to Yandex.Maps, Yandex. Maps request (and receive) permission to display the pointer object 240 on the street map 260 at address 250. In response to the user entering the second address (not shown) in the data entry object 210, a second request is received from the second request element (in this case, Yandex. Maps), the second request includes a request to display the pointer object 240 at the location of the second address (not shown). At 310, permission is given to display the pointer object 240 on the street map 260 in place of the second address. Accordingly, the first permission and execution of the first action by the first interrogator are completed, i. E. the pointer object 240 is removed from the address 250 (which is instead displayed in place of the second address). The second element controls the first object 121, i.e. captures control of all subsequent permissions for the pointer object.

[86] Alternatively, if the first interrogator does not grant a second permission to the second interrogator, the method proceeds to step 312, thus, the second requestor is not allowed to perform the second action. In this case, the pointer object 240 remains on the street map 260 at address 250, and the first interrogator continues to monitor the first object 121.

[87] In alternative embodiments of the present technical solution of step 310, the first interrogator continues to monitor the first entity 121, although permission has been granted to the second interrogator and the second request has been allowed to perform the second action. For example, in the above-described embodiment, although the second interrogator is allowed in step 310 to display the pointer object 240 on the street map 260 in place of the second address, the first interrogator continues to monitor the first entity 121, i. E. the first interrogator still determines the subsequent permissions for the pointer object 240, and the second interrogator does not capture the subsequent permissions for the pointer object 240.

[88] In some embodiments of the present technical solution, where the second action includes both the first action and the additional action, the first interrogator can partially grant a second permission to the second interrogator, thus allowing the execution of a second action portion by the second interrogator. For example, when the second request from the second request element is a request to display the pointer object 240 on the street map 260 in the second place, and also the request to modify the appearance of the pointer object 240, the first interrogator may permit the second interrogator to display the pointer entity 240 on the street map 260 second place, but do not give permission to modify the appearance of the pointer object. In alternative embodiments of the present technical solution, the first interrogator may permit the second interrogator to modify the appearance of the pointer object 240, but not display the pointer object 240 on the street map 260 in the second place. In such embodiments, the first interrogator can control the first object 121 (in this case, the pointer object 240) completely, partially or not at all (ie, the second interrogator monitors the first object 121).

[89] In embodiments of this technical solution, where the first interrogator continues to monitor the object partially, the second interrogator monitors the first entity 121 in part, permission management in this case will be shared between the first interrogator and the second interrogator. Generally, in such embodiments of the present technical solution, the second interrogator monitors the first object 121 for a portion of the second action for which permission was granted and whose execution was allowed, the first interrogator continues to monitor the first entity 121 for a portion of the second action for which there was not given permission to the second interrogator. For example, in the case where the first interrogator allowed the second interrogator to display the pointer object 240 on the street map 260 in the second place, but did not allow the second interrogator to modify the appearance of the pointer object 240, the second interrogator can control the display permissions of the pointer object 240, and the first interrogator still controls the permissions to modify the appearance of the pointer object 240. As will be appreciated by those skilled in the art, many other variations are possible.

[90] In alternative embodiments of step 310, the first interrogator can give a second permission to the second interrogator, which allows the second action to be performed by the second interrogator, without completing the first permission and performing the first action by the first interrogator. In the above example, the first interrogator may permit the second interrogator to display a second pointer object (not shown) on the street map 260 in the second place (not shown), not ending the display of the pointer object 240 in the first place corresponding to address 250. In this case, two pointer objects are displayed on the 260 street map, one in the first place corresponding to the address 250, and the second in the second place. In such embodiments of the present technical solution, the first interrogator may continue or not continue to monitor the first object 121 (the pointer object 240), i. e. the second second interrogator can control or not control the first object 121.

[91] Thus, from a certain point of view, the embodiments of the present technical solution can be stated as follows, structured, numbered points.

[92] ITEM 1 The method for managing permissions for objects (12), objects (12) is executed by the server (40) as part of the program procedures, the method is performed on the electronic device (20) and includes:

[93] a) receiving the first request for the first object (121) from the first request element, the first request includes a request for executing the first action on the first object (121), the execution of the first action requires the first permission.

[94] b) the response to said first request is given the first permission to perform the first action to the first interrogator, and the first interrogator, therefore, controls the first entity (121);

[95] c) obtaining a second request for the first object (121) from the second request element, the second request includes a request to perform a second action on the first object (121), the second action requires a second permission;

[96] d) in response to the second request, transmission of the second request to the first interrogator, the first interrogator monitors the first entity (121); and

[97] Do one of the following:

[98] e) in response to the fact that the first interrogator gives the second permission to the second interrogator, the permission to perform the second action by the second interrogator, the second interrogator, respectively, controls the first object (121), and the first authorization and execution of the first action is completed by the first interrogator; or

[99] f) in response to the fact that the first interrogator does not give the second permission to the second interrogator and does not allow the second action to be performed by the second element, the first interrogator continues to monitor the first object (121).

[100] ITEM 2 The method of claim 1, wherein the first action and the second action are the same action.

[101] ITEM 3 The method of claim 1, wherein the first action and the second action are different actions.

[102] ITEM 4 The method of claim 3, wherein in step e), in response to the fact that the first interrogator gives the second permission to the second interrogator and allows the second action to be performed by the second element, the first interrogator continues to monitor the first entity (121).

[103] ITEM 5 A method according to any of the preceding claims. 3-4, in which the second action includes a first action and an additional action in which the first interrogator gives a second permission to the second interrogator, including that the first interrogator partially gives the second permission to the second interrogator, allowing the execution of the second action portion by the second interrogator.

[104] ITEM 6 The method of claim 5, wherein the first interrogator partially gives the second permission to the second interrogator, including that the first interrogator allows the first action to be performed by the second interrogator and does not allow the second interrogator to perform the additional action.

[105] ITEM 7 The method of claim 5, wherein the first interrogator partially gives a second permission to the second interrogator, including that the first interrogator allows the second interrogator to perform an additional action and does not allow the first interrogator to perform the first action.

[106] ITEM 8 A method according to any of the preceding claims. 5-7, in which the first interrogator continues to partially control the first object (121), the second interrogator monitors part of the second action for which permission was granted and whose execution was allowed.

[107] ITEM 9 A method according to any of the preceding claims. 1-8, wherein the first object (121) includes a user interface element and a pointer and an audio object and an image object and a video object and a text object.

[108] ITEM 10 The method of claim 9, wherein the user interface element includes a text field and a toolbar and a menu line and a hyperlink and a button.

[109] ITEM 11 A method according to any of the preceding claims. 1-10, in which the first object (121) is a pop-up object.

[110] ITEM 12 A method according to any of the preceding claims. 4-7, in which the first action, the second action and the additional action include, independently, one or more of: demonstrating the first object (121), which allows the first object (121) to appear, and inputting the text to the first object (121) , and inputting data or information into the first object 121 and pressing the first object 121 and selecting the first object 121 and selecting a portion of the first object 121 and deleting the first object 121.

[111] ITEM 13 A method according to any of the preceding claims. 1-12, in which the electronic device (20) is a client device or a server (40).

[112] ITEM 14 The electronic device (20) is connected to the user, the electronic device (20) includes:

a communication interface for communicating with the server (40) via the data transmission network (50), the server (40) is configured to perform the objects (12) as part of the program procedures;

a processor (22) operatively coupled to the communication interface, the processor is further configured to:

a) obtaining the first request for the first object (121) from the first request element, the first request includes a request to perform the first action on the first object (121), the execution of the first action requires the first permission;

b) in response to said first request, issuing the first permission to perform the first action to the first interrogator, and the first interrogator, therefore, controls the first entity (121);

c) obtaining a second request for the first object (121) from the second request element, the second request includes requesting execution of the second action on the first object (121), the second action requires a second permission;

d) in response to the second request, transmission of the second request to the first interrogator, the first interrogator monitors the first entity (121); and

execution of one of:

e) in response to the fact that the first interrogator gives the second permission to the second interrogator, the permission of the second action to be executed by the second interrogator, the second interrogator, respectively, controls the first object (121), and the first authorization and execution of the first action is completed by the first interrogator; and

f) in response to the fact that the first interrogator does not give the second permission to the second interrogator and does not allow the second action to be performed by the second element, the first interrogator continues to monitor the first object (121).

[113] ITEM 15 The electronic device (20) of claim 14, wherein the first action and the second action are the same action.

[114] ITEM 16 The electronic device (20) of claim 14, wherein the first action and the second action are different actions.

[115] ITEM 17 The electronic device (20) of claim 16, in which in step e), in response to the fact that the first interrogator gives the second permission to the second interrogator and performs the second action by the second element, the first interrogator continues to monitor the first object 121).

[116] ITEM 18 The electronic device of claim 16 or 17, wherein the second action includes both the first action and the additional action, in which the first interrogator gives a second permission to the second interrogator, including that the first interrogator partially gives the second permission to the second interrogator, allowing execution of a part of the second action by the second interrogator.

[117] ITEM 19 The electronic device of claim 18, wherein the first interrogator partially gives the second permission to the second interrogator, including that the first interrogator allows the first interrogation to be performed by the second interrogator and does not allow additional action to be performed to the second interrogator.

[118] ITEM 20 The electronic device of claim 18, wherein the first interrogator partially gives a second permission to the second interrogator, including that the first interrogator allows the second interrogator to perform an additional action and does not allow the first interrogator to perform the first action.

[119] ITEM 21 An electronic device according to any of the preceding claims. 18-20, in which the first interrogator continues to partially control the first object (121), the second interrogator monitors part of the second action for which permission was granted and whose execution was allowed.

[120] ITEM 22 A method according to any of the preceding claims. 14-21, wherein the first object (121) includes a user interface element, a pointer, an audio object, an image object, a video object, or a text object.

[121] ITEM 23 The electronic device of claim 22, wherein the user interface element includes a text field, a toolbar, a menu line, a hyperlink, or a button.

[122] ITEM 24 An electronic device according to any one of the preceding claims. 14-23, in which the first object (121) is a pop-up object.

[123] ITEM 25 An electronic device according to any of the preceding claims. 17-20, in which the first action, the second action and the additional action include, independently, one or more of: demonstrating the first object (121), which allows the first object (121) to appear, entering text into the first object (121), entering data or information into the first object 121, clicking on the first object 121, selecting the first object 121, selecting a portion of the first object 121, deleting the first object 121.

[124] ITEM 26 An electronic device according to any of the preceding claims. 14-25, in which the electronic device is a client device or server (40).

[125] Some technical effects of non-limiting embodiments of this technical solution may include the provision of decentralized object management, while the central permissions manager is not responsible for determining permissions for objects in all instances. This provision of object management can be more efficient, faster, less costly from the point of view of computing resources, reduce the CPU load, reduce the use of RAM, and / or reduce the power consumption of the electronic device. In those embodiments of the present technical solution, where the electronic device 20 is configured as a wireless data transmission device, the ability to reduce power consumption can result in the battery saving of the electronic device 20. It is important to keep in mind,

[126] Modifications and improvements to the above-described embodiments of the present technical solution will be apparent to those skilled in the art. The foregoing description is provided by way of example only and does not imply any limitation. Thus, the scope of the present technical solution is limited only by the scope of the appended claims.