A structure and a method for handling software modules

Abstract

The present disclosure relates to a structure (1) for handling software modules comprising a plurality of systems (2a, 2b, 2c, 2d), each system (2a, 2b, 2c, 2d) comprising software modules (3a, 3b, 3c, 3d), at least some of the modules (3a, 3b, 3c, 3d) being associated with at least one characteristic of a thing of interest (4a, 4b, 4c). Further, a first system (2a) contains a first software module (3a), the first system (2a) is configured to seek access to a second software module (3b) associated with a first characteristic of a first thing of interest (4a), the second software module (3b) being contained in a second system (2b) and further configured to access said second software module (3b) associated with said first characteristic.

Description

[0001] A STRUCTURE AND A METHOD FOR HANDLING SOFTWARE MODULES

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to a structure and a method for handling software modules of a structure.

[0004] BACKGROUND

[0005] Today software is divided into modules, these modules might be components, services, microservices, apps, websites etc. The software in these modules is often object oriented with representation of meaningful entities as instances of classes. In other cases, the meaningful entities are only represented as grouped data. The meaningful entities are handled by computing resources in purpose built devices, local generic computers, local internet connected edge devices or in cloud based computers.

[0006] Integration requires that the meaningful entities, in different systems, can collaborate to provide functionality that is greater that the functions of each meaningful entity.

[0007] Today when a meaningful entity (A) needs to collaborate with another meaningful entity (B) it is required that the A entity knows how to reach entity B and if entity B needs to collaborate with entity A it needs to know how to reach A. If we add more collaborating entities to this scenario the amount of integration information pieces required is increasing exponentially based on the number of collaboration entities(n), according to the formula:

[0008] Number of Integration information pieces = n2- n

[0009] This results in a situation where the integration effort increases exponentially with the number of collaborating meaningful entities. A drawback of this is that with increased integration effort, increased system complexity follows. Moreover, increased integration effort also leads to performance issues and scalability challenges.

[0010] Based on the above, there is in the present art room for improvements in order to have a structure with systems in which the systems can integrate in a more efficient manner.

[0011] Even though some currently known solutions work well in some instances it would be desirable to provide a structure that alleviates the abovementioned deficiencies.

[0012] SUMMARY

[0013] It is therefore an object of the present disclosure to alleviate at least some of the mentioned drawbacks to provide an improved structure and a method for handling software module of a structure.

[0014] This and other objects, which will become apparent in the following, are achieved by a structure and a method as defined in the appended claims.

[0015] The present disclosure relates to a (software) structure for handling / integrating software modules, the structure comprising a plurality of systems. Each system comprising software modules, at least some of the modules being associated with at least one characteristic of a thing of interest, wherein a first system of said plurality of systems contains a first software module, the first system is configured to: seek access to a second software module associated with a first characteristic of a first thing of interest, the second software module being contained in a second system access said second software module associated with said first characteristic.

[0016] An advantage of the structure is that it allows for integration of any number of collaborating software modules without exponentially increased integration cost. The first system may seek access in order to integrate with the second software module. For example, the first system may seek access to data related to a first characteristic of a first thing of interest which is contained in the second software module. Therefore, in order to access the data, the first system is required to gain access to the software module which handles / stores the data related to the first characteristic of the first thing of interest.

[0017] The structure may comprise an intermediate system, wherein the intermediate system enable access / integration between / among different software modules of different systems (i.e. between a plurality of software modules being contained in a plurality of systems). Thus, when seeking access the first software module may be configured to: query the intermediate system for at least one interface enabling access to said first thing of interest; wherein the intermediate system is configured to: provide a first interface and a first implementation to enable said first software module access to said first thing of interest.

[0018] The intermediate system may comprise a software catalogue comprising information related to things of interest (e.g. having information related to a first, second, third etc thing of interest). Accordingly, the intermediate system, may when receiving a query for at least one interface enabling access to said first thing of interest, search for an interface and an implementation related to said first thing of interest and upon finding / identifying an interface and an implementation related to said first thing of interest the intermediate system may transmit / expose this to the first software module.

[0019] In response to gaining access to said first thing of interest by / through the first interface and implementation, the first software module is configured to: query said first thing of interest for an interface enabling access to said second software module associated with said first characteristic. Then, the intermediate system is configured to, based on said query (provided to the first thing of interest) provide a second interface and a second implementation to enable said first software module access to said second software module and enable, by the second interface and the second implementation, the first software module access to said second software module associated with said first characteristic. Thus, as the first software module has access to the second software module, it can access any data or service related to the second characteristic of the first thing of interest.

[0020] Accordingly, the structure may integrate systems in a systematic manner. A software module may seek specific data. Such data may be categorized by the software module as having (i) a characteristic of (ii) a thing of interest. Based on this, the software module may sequentially query the intermediate system for interfaces & implementations that gives the software module access to the thing of interest. Then, after having access to the thing of interest, the software module may query the thing of interest for access to a specific characteristic of said thing of interest.

[0021] Accordingly, the thing of interest may be a digital representation of an item. The first system may seek access to the second software module (or any software module) based on user-input through a user-interface communicating with the structure.

[0022] Even though it is referred to as that a first system of said plurality of systems is configured to seek access to a second software module. Any software module of a system of the structure may seek access to another software module associated with a specific characteristic of a specific thing of interest, the another software module being contained in another system. Accordingly, terms such as "first" and "second" may be interchanged with any other suitable term.

[0023] The intermediate system is configured to install said first and second interfaces and first and second implementations based on said queries such that the second module is accessible in the first system. In other words, such that it is accessible within a local environment of the first system.

[0024] A thing of interest may be a digital representation of an item. Further, characteristic may be a property or function of a thing of interest. Further, each thing of interest may be defined by the intermediate system as a collection of specific characteristics which may be realized by different systems.

[0025] Further, the first system may seek access to said second software module based on a desired data retrieval, particularly, the desired data retrieval may be selected by a user of the structure. Accordingly, the first system (or any system) may initiate the communication with the intermediate system in response to a desired data retrieval initiated by a user of the structure. The user may have access to one system of the structure when initiating the data retrieval (which requires the user access to a software module of another system of the structure).

[0026] The present disclosure further relates to a computer-implemented method for handling software modules of a structure comprising a plurality of systems. Each system comprising software modules, at least some (in some aspects, each) of the modules being associated with at least one characteristic of a thing of interest, wherein a first system of said plurality of systems contains a first software module. The method comprises the steps of obtaining, from said first software module a query for seeking access to a second software module of said software modules the second software module being associated with a first characteristic of a first thing of interest. Further, the second software module is contained in a second system. Further, the method comprises accessing said second software module associated with said first characteristic.

[0027] Moreover, in some aspects, the structure comprises an intermediate system, wherein the intermediate system enable access between different software modules of different systems. Accordingly, after the step obtaining, the method comprises the step of querying, by the first software module, the intermediate system for at least one interface enabling access to said first thing of interest. Further, the method comprises the step of providing, by the intermediate system, a first interface and a first implementation to enable said first software module access to said first thing of interest. Moreover, wherein, in response to gaining access to said first thing of interest by the first interface and implementation, the method comprises querying, by said first software module said first thing of interest for an interface enabling access to said second software module associated with said first characteristic. Furthermore, the method comprises the step of providing, based on said query, by the intermediate system, a second interface and a second implementation to enable said first software module access to said second software module. Thereafter, the method comprises the step of enabling, by the second interface and the second implementation, the first software module access to said second software module associated with said first characteristic.

[0028] The present disclosure further relates to a computer-readable storage medium storing one or more programs configured to be executed by at least one of a software module and an intermediate system of the structure of any aspect herein. The one or more programs including instructions for performing the method of any of any aspect herein.

[0029] Generally, all terms used in the description are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a / an / the [element, device, component, means, step, etc.]" are to be interpreted openly as referring to at least one instance of said element, device, component, means, step, etc., unless explicitly stated otherwise.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] These and other features and advantages of the present disclosure will now be further clarified and described in more detail, with reference to the appended drawings;

[0032] Figure 1 schematically illustrates a structure in accordance with aspects of the present disclosure;

[0033] Figure 2 schematically illustrates a flowchart depicting an intermediate system providing access to a first thing of interest and further providing access to a second software module; and

[0034] Figure 3 schematically illustrates in the form of a flowchart a method. DETAILED DESCRIPTION OF EMBODIMENTS

[0035] In the following detailed description, some embodiments of the present disclosure will be described. However, it is to be understood that features of the different embodiments are exchangeable between the embodiments and may be combined in different ways, unless anything else is specifically indicated. Even though in the following description, numerous specific details are set forth to provide a more thorough understanding of the present disclosure, it will be apparent to one skilled in the art that the present disclosure may be practiced without these specific details. In other instances, well known constructions or functions are not described in detail, so as not to obscure the present disclosure.

[0036] It is also to be understood that the terminology used herein is for purpose of describing particular aspects only, and is not intended to be limiting. It should be noted that, as used in the specification and the appended claim, the articles "a", "an", "the", and "said" are intended to mean that there are one or more of the elements unless the context clearly dictates otherwise. Thus, for example, reference to "a unit" or "the unit" may refer to more than one unit in some contexts, and the like. Furthermore, the words "comprising", "including", "containing" do not exclude other elements or steps. It should be emphasized that the term "comprises / comprising" when used in this specification is taken to specify the presence of stated features, integers, steps, or components. It does not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof. The term "and / or" is to be interpreted as meaning "both" as well and each as an alternative. More specifically, the wording "one or more" of a set of elements (as in "one or more of A, B and C" or "at least one of A, B and C") is to be interpreted as either a conjunctive or disjunctive logic. Put differently, it may refer either to all elements, one element or combination of two or more elements of a set of elements. For example, the wording "A, B and C" may be interpreted as A or B or C, A and B and C, A and B, B and C, or A and C.

[0037] It will also be understood that, although the term first, second, etc. may be used herein to describe various elements or features, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the embodiments. The first element and the second element are both elements, but they are not the same element. The term first, second etc. may further be interchanged with "any" or "another" or any other suitable term. Le. the second software module and second system may be referred to as another software module and another system.

[0038] Figure 1 schematically illustrates a structure 1 for handling software modules comprising a plurality of systems 2a, 2b, 2c, 2d. As illustrated in Figure 1, each system 2a, 2b, 2c, 2d comprises software modules 3a, 3b, 3c, 3d. At least some of the modules 3a, 3b, 3c, 3d are associated with at least one characteristic of a thing of interest 4a, 4b, 4c. Further, as illustrated in Figure 1, a first system 2a of said plurality of systems 2a, 2b, 2c, 2d contains a first software module 3a. The first system 2a is configured to seek access to a second software module 3b associated with a first characteristic of a first thing of interest 4a. The second software module 3b being contained in a second system 2b. Further, the first system 2a is configured to access said second software module 3b associated with said first characteristic.

[0039] As illustrated in Figure 1, each system 2a-2d may be an independent system. Each system 2a-2d may comprise a pluraltiy of modules 3a-3d, such as at least thousand or millions modules in each system.

[0040] The term "software module" may refer to a self-contained component of a system. Accordingly, a software module in the context of the present disclosure may refer to an element that handles a specific, well-defined task, or function or stores a specific type of data.

[0041] The term "system" may refer to an element that encompasses a plurality of modules, components and libraries. The term "system " herein may represent a complete software solution designated to fulfill a specific set of requirements.

[0042] The expression "access a software module" may refer to that an entity is accessing data, functions, tasks stored in the software module. The term "interface" may refer to a contract that defines a set of methods, properties, or functions.

[0043] The term "implementation" may refer to a specific code / instruction that provides the functionality described by the interface and may be a realization of the methods, functions and properties defined by the interface.

[0044] Figure 1 further illustrates that the structure 1 may comprise an intermediate system 6. The term "intermediate system" may refer to a data integration middleware which can be used to connect and enable integration between the modules 3a-3d of the systems 2a-2d.

[0045] The intermediate system 6 enable access between different software modules 3a, 3b, 3c, 3d of different systems 2a, 2b, 2c, 2d. Accordingly, when seeking access the first software module 3a is configured to query the intermediate system 6 in a two- step process.

[0046] Firstly, the first software module 3a may query the intermediate system 6 for at least one interface enabling access to said first thing of interest 4a. Secondly, the first software module 3a may query the first thing of interest 4a for an interface enabling access to said second software module 3b.

[0047] Thus, for example, a user may have access to the first software module 3a and seeks access to a specific type of data / function / task (definable by a first characteristic) contained in the second module 3b. Accordingly, to access said specific type of data, the user needs access to said second module 3b. To obtain access to said second module 3b, an operation may be initiated which:

[0048] Identify, by the first software module, a first thing of interest 4a associated with said first characteristic to gain access to the first thing of interest 4a; and after access thereto; query the first thing of interest 4a for a module 3b which is associated to the first characteristic. Thereby, the first software module 3a may gain access to the second software module 3b. Hence, upon initiating the method, the first software module 3a may have no knowledge of which software module that contains the desired data. Thus, the first software module 2a, may based on the first characteristic query the intermediate system 5 for a thing of interest associated to the characteristic and upon accessing said thing of interest, try to access the first characteristic.

[0049] Accordingly, as illustrated in Figure 1, the intermediate system 6 can search / browse in a library / catalogue thereof for a first interface 7 and a first implementation 8 that is able to enable the first software module 3a access to the first thing of interest 4a. Provided that the intermediate system 6 identifies such a first interface 7 and implementation 8 the intermediate system 6 can provide a first interface 7 and a first implementation 8 to enable said first software module access to said first thing of interest 4a. Accordingly, in response to gaining access to said first thing of interest 4a by the first interface 7 and implementation 8, the first software module 3a is configured to query said first thing of interest 4a for an interface enabling access to said second software module 3b associated with said first characteristic. In other words, the first software module 3a is configured to query said first thing of interest 4a for an interface enabling access to any software module associated with said first characteristic. Accordingly, the intermediate system 6 is configured to, based on said query, browse for a second interface 7' and a second implementation 8' to enable said first software module 3a access to said second software module 3b and enable, by the second interface and the second implementation 7', 8', the first software module 3a access to said second software module 3b associated with said first characteristic.

[0050] Figure 1 illustrates that the intermediate system 6 may be configured to install said first and second interfaces 7, 7' and first and second implementations 8, 8' based on said queries. The intermediate system 6 may, as shown, install the interfaces / implementations in the first system 2a. Le. the intermediate system 6 may transfer the software defining the interfaces and the implementations to the first system 2a and install the same therein. Allowing for local access by the first system 2a.

[0051] It should be noted that the first system 2a may seek access to said second software 3a module based on a desired data retrieval, particularly, the desired data retrieval is selected by a user of the structure 1.

[0052] Any component of the structure 1 such as the intermediate system, each software module etc., herein may comprise control circuitry which comprises at least one memory device. The queries, access etc. may be received / granted by the control circuitry. The memory may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non- transitory device readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used.

[0053] The control circuitry may be arranged to run instruction sets in the memory device for operating in accordance with the configuration of the structure 1. The control circuitry may be any suitable type such as a microprocessor, digital signal processor (DSP), ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), or a combination of these, or other similar processing means arranged to run instruction sets.

[0054] Further, each component of the structure may comprise interfaces such as input / output interfaces for communicating with a client (user).

[0055] Figure 2 illustrates a schematical flowchart depicting an operation of the structure 1 according to some aspects of the present disclosure. Figure 2 illustrating such a flowchart in four steps, sl-s4. The steps sl-s2 illustrating the intermediate system 6 identifying a thing of interest 4a based on a query. Further, steps s3-s4 illustrates how the thing of interest 4a is queried for a characteristic (colour) in which the thing of interest 4a provides access to the second module 3b.

[0056] Accordingly, Figure 2 illustrates that each thing of interest 4a-4c may be a digital representation of an item. Accordingly, Figure 2 illustrates that the thing of interest 4c is a digital representation of an airplane. Thing of interest 4b is a digital representation of a car. Thing of interest 4a is a digital representation of a drone with Identity (ID) 123456. Accordingly, referring back to e.g. the structure 1 as illustrated in Figure 1. The first software module 2a may seek access to the colour of a drone with ID 123456. Then, the first software module may query the intermediate system 6 for a digital representation 4a of drone with ID 123456. Upon finding such a digital representation 4a. The first software module 3a may query the digital representation 4a for access to a software module associated with the colour (which is the first characteristic) of such a drone. Accordingly, the intermediate system 6 may enable the first software module access to the second software module 3b which contains the data related to the first characteristic. Accordingly, upon gaining access, the first software module can acknowledge that the colour is RED. Thus, characteristic may be a property or function of a thing of interest. As evident by the first thing of interest in Figure 2, each thing of interest 4a, 4b, 4c is defined by the intermediate system 6 as a collection of specific characteristics. For example, the first thing of interest 4a defines a collection of characteristics such as location, colour and speed or functions such as start, stop, move up, move down, etc.

[0057] Figure 3 depicts a method 100 in the form of a flowchart. Specifically, Figure 3 depicts a computer-implemented method 100 for handling software modules 3a, 3b of the structure 1 of Figure 1. The method comprises obtaining 101, from a first software module a query for seeking access to a second software module of said software modules the second software module being associated with a first characteristic of a first thing of interest, the second software module being contained in a second system. Further, the method 100 comprises the step of accessing 110 said second software module associated with said first characteristic.

[0058] As further illustrated in Figure 3, the method 100 may further comprise the steps of querying 102, by the first software module, the intermediate system for at least one interface enabling access to said first thing of interest. Further, the method 100 comprises providing 103, by the intermediate system, a first interface and a first implementation to enable said first software module access to said first thing of interest. Further, in response to gaining access to said first thing of interest by the first interface and implementation, the method comprises the steps of querying, by said first software module said first thing of interest for an interface enabling access to said second software module associated with said first characteristic. Further, the method may comprise the step of providing 105, based on said query, by the intermediate system, a second interface and a second implementation to enable said first software module access to said second software module. Furthermore, the method may comprise the step of enabling 106, by the second interface and the second implementation, the first software module access to said second software module associated with said first characteristic.

[0059] The person skilled in the art realizes that the present disclosure by no means is limited to the embodiments described above. The features of the described embodiments may be combined in different ways, and many modifications and variations are possible within the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting to the claim. The word "comprising" does not exclude the presence of other elements or steps than those listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements.

Claims

CLAIMS1. A structure (1) for handling software modules comprising: a plurality of systems (2a, 2b, 2c, 2d), each system (2a, 2b, 2c, 2d) comprising software modules (3a, 3b, 3c, 3d), at least some of the modules (3a, 3b, 3c, 3d) being associated with at least one characteristic of a thing of interest (4a, 4b, 4c), wherein a first system (2a) of said plurality of systems (2a, 2b, 2c, 2d) contains a first software module (3a), the first system (2a) is configured to: seek access to a second software module (3b) associated with a first characteristic of a first thing of interest (4a), the second software module (3b) being contained in a second system (2b); access said second software module (3b) associated with said first characteristic.

2. The structure (1) according to claim 1, wherein the structure (1) comprises an intermediate system (6), wherein the intermediate system (6) enable access between different software modules (3a, 3b, 3c, 3d) of different systems (2a, 2b, 2c, 2d), wherein when seeking access the first software module (3a) is configured to: query the intermediate system (6) for at least one interface enabling access to said first thing of interest (4a); wherein the intermediate system (6) is configured to: provide a first interface (7) and a first implementation (8) to enable said first software module access to said first thing of interest (4a); wherein, in response to gaining access to said first thing of interest (4a) by the first interface (7) and implementation (8), the first software module (3a) is configured to: query said first thing of interest (4a) for an interface enabling access to said second software module (3b) associated with said first characteristic;wherein the intermediate system (6) is configured to, based on said query: provide a second interface (7') and a second implementation (8') to enable said first software module (3a) access to said second software module (3b); enable, by the second interface and the second implementation (7', 8'), the first software module (3a) access to said second software module (3b) associated with said first characteristic.

3. The structure (1) according to claim 1 or 2, wherein the intermediate system (6) is configured to install said first and second interfaces (7, 7') and first and second implementations (8, 8') based on said queries.

4. The structure (1) according to any one of the claims 1-3, wherein thing of interest is a digital representation of an item.

5. The structure (1) according to any one of the claims 1-4, wherein characteristic is a property or function of a thing of interest.

6. The structure (1) according to any one of the claims 1-5, each thing of interest (4a, 4b, 4c) is defined by the intermediate system (6) as a collection of specific characteristics.

7. The structure (1) according to any one of the claims 1-6, wherein said first system seek access to said second software module based on a desired data retrieval, particularly, the desired data retrieval is selected by a user of the structure (1).

8. A computer-implemented method (100) for handling software modules (3a, 3b) of a structure (1) comprising a plurality of systems (2a, 2b, 2c, 2d), each system (2a, 2b, 2c, 2d) comprising software modules (3a, 3b, 3c, 3d), at leastsome of the modules (3a, 3b) being associated with at least one characteristic of a thing of interest (4a, 4b, 4c), wherein a first system (2a) of said plurality of systems (2a, 2b, 2c, 2d) contains a first software module (3a), the method comprising the steps of: obtaining (101), from a first software module (3a) a query for seeking access to a second software module (3b) of said software modules (3a, 3b, 3c, 3d) the second software module (3b) being associated with a first characteristic of a first thing of interest (4a), the second software module (3b) being contained in a second system (2b); accessing (110) said second software module (3b) associated with said first characteristic.

9. The method (100) according to claim 8, wherein the structure (1) comprises an intermediate system (6), wherein the intermediate system (6) enable access between different software modules (3a, 3b, 3c, 3d) of different systems (2a, 2b, 2c, 2d), wherein after the step obtaining (101), the method (100) comprises: querying (102), by the first software module (3a), the intermediate system (6) for at least one interface enabling access to said first thing of interest (4a); providing (103), by the intermediate system (6), a first interface (7) and a first implementation (8) to enable said first software module access to said first thing of interest (4a); wherein, in response to gaining access to said first thing of interest (4a) by the first interface (7) and implementation (8), the method (100) comprises querying (104), by said first software module (3a) said first thing of interest (4a) for an interface enabling access to said second software module (3b) associated with said first characteristic;providing (105), based on said query, by the intermediate system (6), a second interface (7') and a second implementation (8') to enable said first software module (3a) access to said second software module (3b); enabling (106), by the second interface and the second implementation (7', 8'), the first software module access to said second software module(3b) associated with said first characteristic.

10. A computer-readable storage medium storing one or more programs configured to be executed by at least one of a software module and an intermediate system of the structure (1) of any one of the claims 1-7, the one or more programs including instructions for performing the method (100) of any of claims 8 or 9.

Images