Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/30—Creation or generation of source code
  • G06F8/36—Software reuse
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/30—Creation or generation of source code
  • G06F8/31—Programming languages or programming paradigms
  • G06F8/316—Aspect-oriented programming techniques
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/445—Program loading or initiating
  • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Definitions

• the present invention relates to an application server, a repository device, a system, computer program products and methods for managing a service (e.g., communication service) provided to a user.
• a service e.g., communication service
• AOP aspect oriented programming
• AOP is a technique in software design that helps one to implement multiple functions into an application. Often the code of these functions is heavily tangled in the sense that code pieces dedicated to one function needs to be allocated at multiple places within the code of the other functions. This property is referred to as cross-cutting of concerns. However, a clean and modular implementation of these multiple functions by separating them into dedicated and encapsulated units is frequently not possible or extremely difficult.
• point-cuts which is a generic definition of those locations known as join-points within an application, where the aspect code should be added.
• the point-cut might specify to execute the aspect at every call of a certain method.
• the point-cuts are based on conditions that capture points within the source code of the target application or it refers to events with the application execution.
• this technique could allow the automatic application of a certain functionality automatically even without analyzing an application. For example, if a new application is deployed within a service execution environment, the aspects that exist within this environment could be automatically applied to this new target application.
• third party service providers might not support all the functions required by the network operator. For example, activity logging or charging might not be implemented by the third party services.
• these features can be automatically added to the target application.
• the devices and methods which can accomplish this is the subject of the present invention.
• the present invention provides a method implemented by an application server which interfaces with at least one repository for managing a service.
• the method comprises the steps of: (a) interfacing with the at least one repository to load a service description identifying a list of application concerns which are implemented by the service into runtime data; (b) interfacing with the at least one repository to access an aspect description identifying a list of aspect concerns, where the list of aspect concerns has a unique aspect identification and each aspect concern is identified by a unique identifier (e.g., tag or keyword); and (c) dynamically updating the service description of the application concerns in the runtime data throughout execution of the service, wherein during aspect weaving at a join-point an update of the service description of the application concerns in the runtime data is performed by adding, removing or marking as removed the unique identifier defined for the aspect concern that is weaved into the application concerns in the runtime data.
• An advantage this is that the application servicer makes sure that aspects are only weaved into service where they are needed.
• the present invention provides a repository that interfaces with an application server which provides a service.
• the repository comprises a storage device for storing a service description identifying a list of application concerns implemented by the service, wherein each application concern is identified by a unique identifier (e.g., tag or keyword).
• the present invention provides a method implemented by a repository which interfaces with an application server which provides a service, the method comprisees the step of storing a service description identifying a list of application concerns implemented by the service, wherein each application concern is identified by a unique identifier.
• the present invention provides a computer program product comprising computer readable code which, when run in a computer causes the computer to perform the following: storing a service description identifying a list of application concerns implemented by a service, wherein each application concern is identified by a unique identifier (e.g., tag or keyword).
• a unique identifier e.g., tag or keyword
• the present invention provides a computer program product comprising computer readable code which, when run in a computer causes the computer to perform the following: (a) interfacing with the at least one repository to load a service description identifying a list of application concerns which are implemented by the service into runtime data; (b) interfacing with the at least one repository to access an aspect description identifying a list of aspect concerns, where the list of aspect concerns has a unique aspect identification and each aspect concern is identified by a unique identifier (e.g., tag or keyword); and (c) dynamically updating the service description of the application concerns in the runtime data throughout execution of the service, wherein during aspect weaving at a join-point an update of the service description of the application concerns in the runtime data is performed by adding, removing or marking as removed the unique identifier defined for the aspect concern that is weaved into the application concerns in the runtime data.
• a unique identifier e.g., tag or keyword
• FIGURES 2-3 there are two diagrams used to help explain an exemplary weaving scenario performed in accordance with an embodiment of the present invention.
• An application server will be described below that with the help of AOP is capable of automatically adding functionality to an original service without directly modifying the target application code of the original service.
• the application server when automatically adding functionality to a certain application will automatically detect which features are still missing within the certain application code, and which are already supported. For example, if the target application code already supports charging, then the aspects which add charging support would not be applied to avoid duplicate or contradictory charging.
• the application server is configured to dynamically describe the features and capabilities of an application to control which functions are already covered by the application code and the currently applied aspects.
• the application is described with a set of unique identifiers, for example tags or keywords, corresponding to the features and concerns the application is already taking care of. Also, the concerns an aspect would address are described.
• the application server that is configured to manage a service as described above would typically interface with one or more repository devices where both the application server and repository device(s) would have one or more of the following features (which are discussed in greater detail below):
• a description of the concerns a service implements is defined in a service description stored within a service repository (for example) which exposes the service for usage from a particular domain (see FIGURE 1).
• the service description can contain binding information of the service and usually describes the functions and capabilities of the service.
• Web Service Description Language (WSDL) is one scheme that can be used for such service descriptions.
• the list of concerns an instance of the application addresses is dynamically maintained and updated at runtime within an application server (see FIGURE 1). For example, the usage of aspects might lead to changes in the concerns that are addressed by the overall application.
• the run-time service concerns description is evaluated when a decision is needed on whether an aspect is to be weaved into the application.
• the aspect weaving might be rejected, if the application already addresses the same concern as the aspect.
• a policy can be used to support the decision as to which aspects to apply.
• the policy can allow multiple aspects to be weaved although they implement the same concern.
• a policy can be used to decide about the order of the aspect application.
• FIGURE 1 there is shown a block diagram illustrating an exemplary system 100 including an application server 102, a service repository 104, and an aspect repository 106 which together manage a service 108 in accordance with an embodiment of the present invention.
• the application server 102 includes many components which are well known in the art but for clarity are not described herein but the components such as a composition entity 110, analysis function 1 12, runtime data 1 14, and a weaving entity 116 which are relevant to the present invention are described herein.
• the overall functionality of a service 108 comprises of a number of sub-functionalities that provide different parts of the overall application. This is in particular the case for a composite service 118, where each constituent service 121a and 121b (service 1 and service 2) provides a part of the application.
• a functionality that is implemented by the composite service 118 is referred to as a concern 120a and 120b.
• AOP in this respect is a way to modify which concerns 120a and 120b are addressed by the composite service 118.
• the composite service 118 prior to any usage of AOP techniques addresses a number of concerns 120a and 120b.
• the composite service 118 might for example handle charging for the service, but the composite service 1 18 might not contain support for logging.
• a feature of the present invention is to add a list 119 of those concerns 120a and 120b which are already covered by the application's implementation as part of a service description 122 within the service repository 104 (feature 1).
• each concern 120a and 120b that the composite service 118 addresses can correspond to a keyword/tag (e.g., concernl, concern2).
• the overall set of concerns 120a and 120b is then represented by the list 119 of these keywords/tags (feature 1.1).
• the aspect 124 also provides an implementation of concerns 126a and 126b. This is reflected by an aspect description 128 within the aspect repository 106.
• the aspect description 128 contains a unique ID 130 and a list 132 of concerns 126a and 126b associated with the aspect 124 (feature 2).
• the aspect description 128 states which functionality the concern 126a and 126b would add to or remove from an application, if it is applied.
• each concern 126a and 126b that an aspect 124 addresses might be stored within the list 132 with a keyword/tag (e.g., concern3, concern4)(feature 2.1).
• the concerns for which the aspect 124 is able to add an implementation to an application should be distinguished from those concerns (e.g., concern 126b) for which the aspect 124 can remove from an application.
• this can be reached by using separate lists 132a and 132b for the concerns 126a and 126b where one list 132a identifies the concerns 126a that the aspect 124 adds to an application and another list 132b identifies the concerns 126b that the aspect 124 removes from the application (feature 2.2).
• An example for removing and adding concerns to an application is where the original composite service 118 might include functionality that charges the user.
• the operator might not want to have that particular method of charging and thus uses an aspect 124 (concern 126b) to remove this kind of charging. Additionally, the operator might add their preferred way of charging to the composite service 118 through another aspect 124 (concern 126a).
• the concerns 126a and 126b would not be called “charging” for both cases, but they would be called for example “charging methodA” and “charging methodB”.
• Each concern 126a and 126b may be implemented by multiple aspects where each of them implements a part of the concern's overall functionality. These aspects are an aspect group. They are registered in the aspect repository 106 with a common aspect group ID (feature 2.3). There are multiple ways of implementing this Aspect Group ID. For example, by adding the group ID to every aspect 124 that belongs to the particular group. Alternatively, by specifying the group ID separately as a list of all aspects 124 that belong to that particular group. Each of these approaches has its own advantages and disadvantages.
• the service description 122 and the aspect description 128 as introduced in the previous section sets the environment for the execution of the service 108.
• the service descriptions 122 and 128 are used at the run-time of the service 108 (feature 3).
• the application server 102 and in particular the composition engine 110 loads the service description 122 into the runtime data 1 14 of the service instance. In one embodiment, this can be done by copying the service description 122 from the service repository 104 into the runtime data 114 (feature 3.1). In another embodiment, the analysis function 1 12 could determine the service description 122 as result of an analysis of the service 108.
• the run-time service concerns description 122' is updated each time an aspect 124 is weaved into the application (feature 3.2).
• the application server 102 and in particular the weaving entity 1 16 does this by adding the concerns that are specified in the aspect concern description 128 to the run-time service concerns description 122' (feature 3.3).
• the aspect 124 removes functionality, then the respective concern description needs to be removed from the run-time service concern description 122' rather than added (feature 3.4). In one embodiment, the removal of a concern is performed by actually leaving it in the run-time service concern description 122' but marking that concern as removed (feature 3.5).
• the weaving entity 116 selects only one aspect (for example the first aspect processed) for weaving and the other aspects for the same concern are skipped.
• a policy can be defined to control which aspect is used (features 4.3, 4.4). If multiple aspects are used for a single concern this can be reflected in the run-time concerns description 122' by assigning multiple aspect IDs to a concern (features 3.7).
• the ID of the aspect is stored with the concern the aspect has added. This is done to make sure that the same aspect for the same concern is not blocked at different join-points. Otherwise the aspect might block itself. This can happen because the run-time service concern description 122' is updated at the first join-point. Then at the other join-points the weaving of other parts of the aspect is blocked, because the concern is already in the updated run-time service concern description 122'. Such blocking might also happen if the implementation of the concern is spread over a number of aspects intentionally. If multiple aspects are used for a single concern this can be reflected in the run-time service concerns description 122' by assigning multiple aspect IDs to a concern (feature 3.7). This allows all aspects assigned to a concern to be used at other join-points addressing the same concern.
• the policy that leads to the weaving of a particular aspect might change. If this happens, then the run-time service concern description 122' might need to be updated to reflect the new policy. This update might imply the removal of aspect IDs that are assigned to concerns in the run-time service concerns description 122'. It might also lead to the replacement of the original aspect ID by the new ID of aspects that would have been selected according the new policy (feature 3.6). However, this mechanism should be used carefully to make sure not to use aspects for the rest of the execution that are incompatible with those which are used in the beginning. In addition, the replacement algorithm should consider and take into account compatibility problems. In fact, it may be better to keep a policy valid for all running composition sessions and use the new policy only for new sessions. In any case, the described replacement of policies might be required, for example, for long-running composition sessions, where neither a restart of the composition, nor further usage of the old policy is acceptable.
• a concern needs to be distributed over multiple aspects, which in general are weaved into the application at different join-points.
• Such a group of aspects is described in the aspect repository 106 with a single group aspect ID.
• the aspect ID of the group is then also assigned to the concern within the run-time service concerns description 122' once an aspect of the group is applied. If a different aspect from the same group is about to be weaved at another join-point, this is allowed, because the aspect is described with the same aspect group ID as was already assigned to the concern (feature 3.8).
• aspects 124 are weaved into the application and at each join-point the weaving entity 116 needs to take the decision on whether the aspect 124 can be weaved in or not.
• the weaving entity 116 skips the weaving of the aspect 124 if the concerns 126a or 126b that the aspect 124 implements are already present in the target application.
• the aspect concerns description 128 as stored within the aspect repository 106 is compared to the run-time service concerns description 122'. If the aspect concerns 126a or 126b are already in the run-time data 114, then the weaving might be skipped.
• An aspect 124 might be weaved in at multiple join-points throughout the application. This means, further weaving must not always be rejected, just because the run-time service concerns description 122' was updated at first weaving. It should be allowed, if the further weaving can be associated to the same aspect 124. This is reached by not only storing the aspect concerns description tags in a run-time service capability list, but also the aspect ID 130 would be stored with the particular concern 120a and 120b. At further weaving of the same aspect 124, the weaving entity 1 16 finds matching concerns descriptions in the runtime data 114 and the aspect description 128, but the weaving is allowed if the conflicting concern was added by an aspect 124 with the same aspect ID 130.
• a policy provides rules regarding which aspect 124 to choose. For example, the policy might specify to take the first aspect 124 that is considered. For another concern 120a and 120b the last aspect that is applicable for the join-point might be selected. The policy might also allow multiple aspects 124 to be weaved in for a concern 120a and 120b, and then determine the order of aspect weaving/execution.
• the constituent services 121a and 121b that are available for composition and the aspects 124 that are available for weaving, are registered within separate repositories 104 and 106. If desired, only one repository can exist for both the composite service 1 18 (including the constituent services 121a and 121b) and aspects 124.
• the definition of a concrete ontology for the service and aspect concerns descriptions 122 and 128 would be domain specific.
• the list 119 of default concerns 120a and 120b might be pre-defined for a composite service 118 and stored within the service repository 104.
• the list 119 of concerns 120a and 120b that the composite service 118 is already addressing might be generated automatically by the analysis function 112 which analyzes the composition service 118 with respect to the constituent services 121a and 121b which are needed to instantiate this composition service 118 (feature 5).
• online weaving can be used to apply aspects 124 to a composite service 118.
• an aspect 124 is used that adds logging of all used constituent services 121a', 121b', 121 c', 121d', 121e' and 121f to the composite service application 118. This means, that the logging aspect 124 shall be invoked after each service selection within the composite service 118.
• the weaving entity 116 at each join-point takes a decision according to the weaving decision logic which is shown in the flowchart associated with FIGURE 3. Referring to FIGURE 3, there is a flowchart illustrating the weaving decision logic 300 that is performed by the weaving entity 116 to implement the exemplary service shown in FIGURE 2.
• the weaving entity 116 after reaching a join-point (step 302) functions to select an aspect 124 according to weaving instructions (step 304) and obtain the aspect concerns description 128 (step 306). Then, the weaving entity 116 determines if the aspect concern is in a list of run-time service constraints (step 308) where if the result is no then the aspect concern is added to the run-time list of service concerns 122' (step 310) and the aspect 124 is weaved into the application (step 312) before ending (step 314).
• the weaving entity 116 determines the aspect is indeed in the list of run-time service constraints (step 308) then determine if the run-time concern is from same aspect 124 (step 316) if the result is no then end (step 318) and if the result is yes then weave the aspect 124 into the application (step 320) and then end (step 322).
• the service does not support logging. Logging is added by aspects at run-time. The first time, assume when a join-point is reached, where the logging aspect shall be applied, the weaving entity 116 determines that a logging concern is not in the list of those concerns that are already addressed by the application (step 308). The aspect is applied and the list of addressed concerns for this service instance is updated (steps 310 and 312).
• the weaving entity 1 16 finds that a concern of the logging aspect is already within the list of addressed concerns. As this logging concern was added by an aspect of the same ID, the weaving entity 116 decides to allow the usage of this aspect again (step 320). If another aspect is tried, that would also apply logging, then the weaving entity 116 would reject the weaving to avoid two independent aspects from addressing the same concern (step 318).
• the present invention is aimed, at least, to minimize the aforementioned drawbacks associated with the prior art and to provide a central building block of an overall aspect oriented service management environment.
• the weaving language allows to define weaving globally across multiple applications and services.
• the present invention helps to make sure, that aspects are only weaved into applications where they are needed.
• the mechanisms described herein might allow automatic application of aspects without changing the global weaving instructions, because the application server can decide automatically and dynamically, if and which aspects are to be weaved into this application.
• the operator of such a service environment can provide global weaving instructions expressing their requirements regarding the functionality of an application.
• the mechanisms and features described herein also help to add this functionality by means of aspect weaving to applications that do not contain support for them. Applications that are already compliant to these requirements are automatically excluded from weaving.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computing Systems (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (1)

Family

ID=42671846

Family Applications (1)

Country Status (4)

Families Citing this family (3)

Citations (1)

Family Cites Families (17)

• 2010
  • 2010-07-13 JP JP2012540329A patent/JP5613255B2/ja not_active Expired - Fee Related
  • 2010-07-13 EP EP10732956.7A patent/EP2504760B1/en not_active Not-in-force
  • 2010-07-13 WO PCT/EP2010/060060 patent/WO2011064001A1/en not_active Ceased
  • 2010-07-13 US US13/511,250 patent/US8972935B2/en active Active

Patent Citations (1)

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events