FI117153B - Expanded name service framework - Google Patents

Abstract

The present invention describes a dynamic managing method, system and extended naming service framework for enabling service availability in a computer system comprising at least one or more client applications, one or more server applications for providing one or more services, and wherein the client applications use one or more services. The system further comprises one or more entities or pieces of physical equipment for providing one or more server applications and a management entity for supervising and recovering the entities or physical equipment. The framework provides a solution to the problem of locating and managing services within a system. The framework provides a centralised storage of information about all the services within a system, although it can also be a distributed solution as well. Source of information about the services are the service providers themselves or mapped information from HA notifications concerning physical equipment, e.g. a LAN port etc.

Description

EXTENDED NAME SERVICE FRAMEWORK FIELD OF THE INVENTION

The present invention relates to mobile systems. In particular, the present invention 5 is embodied in a new and improved method, system and extended name service framework to ensure service integrity.

BACKGROUND OF THE INVENTION

10 Telecommunication and Computer Networks Supporting Services Asking for Different Services The service here refers to any instance of a software or hardware component that can provide some useful information to entities, users, or customers.

An important feature of the service is that it is available as much as possible. Some slots are more important than others and therefore the low time or fault time for the most important services <20 should be minimized. An important consideration c is that the status information (for example, bug, down, * ·: should be available to those instances, * may need information, for example other users who may send the service): ***; 25 to the service. ; • 9 «: one service, but there may be a state: •». * ··. Where a single process provides one service or one service.

. It can be said that most computer * * * 30 communication systems have some kind of ha! * m «« '31 __! __ i__1 _1 * + * _- | T! _x __- 1 - ........

2 party networks contain several different network management systems (NMS, Network Management System).

Conventional problem-solving tips are often rule-based solutions. What this means is that there are pre-formed ice, and when a fault occurs, something goes wrong and rules determine the effect of the fault. What's even more problematic is that the rules are often customer-specific. Predefined. The main problem with the rules is that they are framework rules and are based on more or less specific situations. A weakness of rule-based solutions is that they are static in nature. When a fault occurs, rule-based frame 15 goes through predefined rules and tries to determine what effects the problem will cause Imagine a situation where a particular fault has not occurred before, so there is no applicable rule . As a result, there are 1 20 lumbar at hand and there is no specific information about the malfunction, nor what the effects of the malfunction are.

There is a high availability service; * ·: To. Core Hardware Technologies Visit: j ': Open Interface Software Components help \ 25 head to product creation. These web servers i * · * '*; eventually replacing, for example, existing mobi:

«M

, ·,: Mobile devices that enable mobile networks to provide ••• call features that are progressive with existing voice and message-centric services 30+.

* * · * · | · * Today, some systems use «f, 11 '3 (IRP, Integrated Reference Point). The customer refers to an entity such as a software process being able to access various services. Proses includes many services and thus multiple p 5 access points.

A problem arises when the High Get Services (HAS) discovers that some process device, such as a disk, is broken. It is up to the breakfast to determine which services are affected by the disk break; 10 technology applications do not explicitly answer this important question. In your current interconnected world, architecture p for processes and messaging for processes v In these, the client knew of his counter-process and thus the impact of 15 process failures was expected, it was only possible to recover from the situation with HAS-ko.

In the current architecture model, the main points are services and their access points. 20 companies are not interested in the physical parts of processes that provide services. Only interested in accessing the service: • * ·. ·: (IRP) and their runtime references: Provides the freedom to pack services in many ways • ·· *** # i 25 ten provides a variety of physical architectures for highly flexible architectural services.

• · m »» vt »

SUMMARY OF THE INVENTION

* ♦ • ♦

• M

The present invention provides the availability of a dynamic, 30 front-end method, system, and extended n: • · application service: • · 411 an entity or physical device for producing a single or man server application and a management comprising information about said entities or physical devices. .

The name service framework described in the present invention provides a solution to the problem of locating and managing a system. The frame provides, in a preferred embodiment, a central location for storing all the bones of the system 10. However, an extended name service framework can also be a distributed solution. The source of the services is the service providers themselves or the HA announcement information that applies to physical components such as the LAN port, etc.

15 Access to the service must be through to the users of the service. The service providers, or assist in providing the service, do not themselves make the service available. The present k illustrates the availability of a generic solution service for implementation.

High availability services (HAS) correspond to information such as the physical component (CPU, Central Processing Unit), source (LAN, Local Area Network), processes, etc.). Service users (client applications) do not ^. ···. interested in the processes but in the service end. Service providers may offer "fy *., * Customized (for example, pros pros) services" * "·· 'services for an extended name service framework. Ku 30 rack HAS Notifications for Physical Components:: .i .: Extended Naming Framework Can Attach Service: • • f? * 1 ^ 1-1 -P «4 * 1 ___ 1________i_ j 5 11 it is possible to describe processes or physical components of services produced by main processes or physical components.

5 PHOTO LIST

The accompanying drawings, which are included to provide a better understanding of the invention, which form part of the disclosure, illustrate embodiments of the present invention and, in conjunction with the description, facilitate the explanation of the basic concepts of the invention. In the drawings:

FIG. 2 illustrates an example of a service rasterization and a service subscription, FIG.

Figure 3 shows an example of a board p terminating a producer's service,

Figure 4 shows an example of a service change of <20, and

Figure 5 shows an example of a service boundary address retrieval from an extended name server.

• · · * · *

»M

j '* .. 25 DETAILED DESCRIPTION OF THE INVENTION

The following reference is made to the specific embodiments of the present invention, of which the characters are illustrated in the accompanying drawings.

Figure 1 shows an embodiment of the embodiment:; 3 0 according to the invention. Sequence <«* ·. ··. includes two client applications (CUl. CU2) and 6 11

High Availability Services HAS only processes information such as physical components (eg, CPU, Local Area Network, Processes), v 5 HAS manages Recovery Units (RUs), which contain processes. service, but in practice it can provide multiple service access interfaces or integr: Reference Points (IRPs). The dotted lines represent possible messages. The main idea of the present invention is that the named name service framework ENS stores single information about client applications (CUl, CU2). (SP1, SP2) In the event of a failure, the 15 Extended Name Service Framework ENS contains all the pertinent information to determine which services are malfunctioning.

The intelligence of the present invention may further include alarm services (AS, Alarm 20 0 ces) as shown in Figure 1. Alarm service reports on alarm conditions. The present k <provides a powerful tool for use with: reporting. Typically, AS vi ·· «m i forward alarm reports (or

IM

25), for example, a network management system; . * ··. (NMS, Network Management System). Useissc * * Ϊ *. In some cases, problems with physical entities can be found but it is not possible to know what service problems • * * · * · * affect if any. This would make it easier for 30 operators to take corrective action to: \ i ,: you if it received a better alarm report,> Ί Ί rn j-4 Ί nn U · *>. 1 A J ^^. i_ Ί _ _ _ _ _ _ i_ _ _ 1 1 7 11 from the extended name service framework ENS equivalent. call for services, and control based on your alarm report. Previously, this problem was ra using the alarm correlation rules, but i 5 is static in nature and not really minimally bound, as the present k shows.

HAS to launch processes and process! in the initialization step, the HAS provides the process with physical information and process status (active or silent). When the process is started, the current physics: the location is told to it (like the cluster node helper) as well as the status of the process. When prose is launched from Hi 15 MIS, the process registers all of its service terminals into ENS. in the registration messages (or in one large roaming message), the extended name service frame ENS process adds the physical si and status of the service access point 20 integrated reference point (IRP). The process may additionally provide some keys that can be used in the service state.

* later by the customer. Registration «« «9; the extended name service framework ENS has 25 information such as "IRP, IRP state {^ process state), * t · * .. location, other search keys".

* * l '\ If something goes wrong with a CPU node • i * process, HAS sends this information la.

* ··· * for the name service framework ENS. The extended n 3 0 performance framework ENS is now able to associate this fy component related information with the correct service Φ ··. , * Λ. * »I" 1 + * Λ Λ rt rt rt> n T rt rt ^. -Rt _-- 2 _— rt. 1 ___ Ί _ - Ί _ _1______ rt 8 11 service. Requirement for service availability for multiple services. Extended name frame The use of ENS is also flexible, and service providers and producers may decide to use all or a limited set of features provided by hys, for example, the r configuration may work as a simple: Common Object Request Broker tecture for some service providers and visit 10 le.

In Figure 1, the server application SP1 produces the software entity or the physical device and the server application SP2 the software entity the physical device EQ2. The software whole physical device (EQ1, EQ2) refers to, for example, p or processes.

In one embodiment of Figure 1, the wide name service frame ENS includes one or more; Scratching equipment: 20 - Interface for IF notification

from the management entity HAS to the software entity or physical device EQ

• misspelled, # * «·. . ·. - upgrade tools UM service states • »»; ·. 25 to update which services support EQ with malfunctioning software or physical device EQs * /. / - notification tools NM to report changes in client status »30 CU2 that are registered visit said services that produce a status of B 4 9 11, of which said client application CU2 is aware, to query interface IF service lookup request from client application 5 CU2, - output means NM requested service information; for the client application CUl, Cl the service meets the search criteria,

- one or more allocation rules DR

10 is applied when a service registered in an extended nirnip * frame k two or more instances of a server interface IF query received or services associated with one or more software or physical components: checking means CM for service detection, transmitting means NM for transmitting 20 for services that are 1: to one or more mysterious entities or physical: ** to EQ.

»Ta *. The above means are in one so1 m * ·. It is implemented using hardware and / or hardware components.

* · Γ *. In one embodiment of Figure 1, the extension * * * service framework also supports other service access: • · '··· * packages other than CORBA. The message path may be any other protocol and not necessarily CORBA.

In one embodiment of Figure 1, services * * · „. . * _ _ 10 11 instance instance name extension ENS. The search criterion in such a case v is, for example, the exact instance identifier of the particular service in question.

5 In one embodiment of Figure 1, the wide name service framework ENS supports a service provisioning operation. Different instances of the same service can store my service reserve. An Expanded Name Service Framework E nce and manage such a service pool <10 An extended name service framework ENS can apply the sharing principles to various service instances within the beach. The sharing policy includes, for example, a least-loaded server, a recently used (LRD) server, a round-robin procedure, etc.

In one embodiment of Figure 1, the extensive name service framework ENS includes the service provider's management functionality. They are heavily loaded by the service providers for the E2 0 extended name service framework. This decision is based on the collection of system or statistics. In such a case, the quality name service framework ENS may not update new users of * * * * with information about the service 25 in question. It can also notify users of existing o t «# services who are aware of service * · I '\ dancing, service status {heavy load •» *

In one embodiment of Figure 1, the extensive 9 * * ··· * name service framework ENS provides a standard 30 name service functionality for service provider users. However, the frame also offers a CosNaming Boundary • 9 täytyy 11, however, you need to be aware of what is being served from the CORBA name service and what services are using the advanced mechanisms of the extended name service framework ENS. In this way, all of the bone-related functionalities of about 5 are centered in one place.

In another embodiment of Figure 1, the system includes the standard CORBA name service extended name service framework ENS separately; 10 dogs.

Figure 2 shows an example of a service registration of the present invention. The register may occur, for example, during system startup or when the service provider is started / restarted.

The service provider SP registers the pal with the extended name service framework ENS (20) using CORBA messaging. In one application, the registration contains the 20 information:

Name of the service.

Service access point where service k • - Service interface address.

«« T ·. - Physical information about the service (node • · · 25 process information, etc.).

• »· [... t - Service status (active or ready * # ** '. After registration, the service is * · f uniquely registered in the extended name service' ··· * ENS and identified by a unique identifier, 30 Figure 2 also shows the service a subscription order in which a service user SU orders a service; 12 11 using a CORBA call.

Name of the service.

Service access point where the service k 5 - Required physical or other features

Service status.

The number of instances of the service, if one wants to know.

- Reference to the callback interface for p 10 users. This is the boundary frame used to fill the service user.

The Service User SU is now able to successfully upload services from an extended name service framework 15 If the services are available, which services are subscribed to, the service user was updated on a non-regular basis (24). This update details everything about the service including the service identifier, p name, IRP, service interface address, physical engineer 20 service as well as service status. When Palvi registers, the users of the service are updated, the user order matches with the registered p J. In other words, the service user is auto • f · e. ·. receive service information with which <«· 25 to do. To manage the service subscription, the · ·· named service framework ENS can form a dynamic table of customer / service relationship. By using this table, the · · · name service framework ENS can only push p 30 status changes to customers interested in the IRPs in question.

13 11 during service or provider days *

ENS, the extended name service framework, is up and running. The HAS initiates (30) a service provider 5 sequence. Starting a termination sequence means that new requests are no longer accepted. The service provider informs (unregistered) the frame that it is ready for managed management (32). ENS; In addition, it updates all users who are aware of this particular service in the new state of the service. In addition, the extended charge framework ENS informs the service provider SP 15 that all users of the service are aware of Päivi's service (34). Finally, the service provider SP assures HAS that the termination sequence is not to terminate itself (36). Because all service; those who were aware of this particular service 20 dance will be updated, the service users will not enter into any new transactions with the service.

* ·; Figure 4 shows an example of a service failure. In Figure 4, the recovery unit with a specific: * ·. · 25 luminance is running, changes.

*

The initial state of Figure 4 is that the service ··· is aware of both active and ready,

** M

. · * [From the service instance that serves * »as a database fragment. You expand. 30 service frame ENS is up and running and has been r <** j · 'rooted as a client from the CORBA Notification Service coming \ »· * m« 1 - _. '_ ι_ 1 1 1 * 1 η 1 14 117 fetal state is ready (40). S «this exchange information into information about the physical properties of the bone dances produced by the service providers themselves. In other words, the extended name service framework ENS indicates which services are running in this particular revival. As mentioned earlier, the service handbook; it is assumed to be aware of both active and idle service-specific instance 10 host units that hosted the service's active instance changed state and went into standby due to extended name service framework ENS updated the service user's SU service instance to change] lat (active or standby) (42).

15 The extended name service framework ENS is only now announcing that a particular recovery unit has entered an active state, which can be described with the red state that services are running on the complete recovery unit (44). Subsequently, the extended 20 service framework ENS updates all service handlers that have subscribed to information about the relevant toy instances (46). Service users SU · informed about new status of services.

Figure 5 shows an example of retrieving an interface address for a particular Palvi 25 dance. The service provider SU requests interface addresses for a specific service • * ♦ by specifying the name of the service and the service instance * * ·, · *. [The requested service has already been registered for the extended service name frame ENS (50! * *). ENS returns the requested service interface section <«« «* / m *« 1- 4 i, n 'ΟΛτνη 7v τηη \ / rn \ - * - 15

The invention is not limited to the above embodiments only, but many embodiments are possible within the scope of the inventive idea defined by the patents 5 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 99 9 · 9 9 9 9 9 9 9 • 9 9 • «9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9

Claims (38)

1. A dynamic control procedure for establishing service availability in a computer, comprising at least one or more customers, one or more server applications for the provision of one or more services, and which applications use said one or more service or software components. or physical means for producing one or more services and a control unit, comprising formation of said whole or physical ancestors, characterized therein, to be provided. further comprises the steps of: registering to an extended name service tree or multiple services; storing to said extended name information about said one or more services, said information being obtained from said service in the registration process; and on the base of it:. . the information, in the extended name service frame, is associated with a * * * [; · * service for a specific software unit * · physical device, providing said service. 2. Dynamic control procedure according to claim 1, characterized in that: for: the steps include: registering in said extended name service. one or more customer applications; * «*. ···. 30 stores in the aforementioned name are changed to in format • * 29 11 a specific customer application is linked to a received service. Dynamic control procedure according to claim 2, characterized in that nam formation of said customer applications comprises stone one of the following: the customer's narrin; customer interface address; customer status; and 10 physical information about the customer. Dynamic control method according to claim 1, characterized in that no formation about said services comprises the following: - the service name, - the service access point, to the service service: hear; t j interface interface address; status of service; and physical information about the service. A dynamic control method according to claim 1, characterized in that: for: the steps comprise; • * * *; receiving from said control unit of the country that the software unit or the physical system is operating incorrectly; and * «updating the status of the services • * * which services are produced using the • * * ··· 'fully functional software whole or physical 3.. * 6. Dynamic control procedure according to: ***; Tent claim 5, characterized in that for a properly functioning software whole or physics; order. 7. A dynamic control method according to claim 1, characterized in that for 5 further the steps comprise: receiving a service order from your service, said service being counted o: at least one or more of the following: the name of the service in question; The access point of the service to which it belongs: the physical or other property of the service of the service; accessibility; The number of instances of said service; and a hint to the caller interface for customer application. Dynamic control method according to claim 7, characterized in that it comprises the step of: notifying to the customer application, which service <which said customer application is aware, states. • · · » Dynamic control method according to claim 1, characterized in that for «* * the steps comprise: * ♦ V *. receiving the service's search request from the i / application; and «* * · ** giving to said customer application thereof; If the service corresponds; : "V teriet. 10. Dynamic control procedure according to 31 n: Dynamic control method according to claim 1, characterized in that the data registered to the extended name j, but comprising two or more instances of a service, one or more distribution rules * is mentioned. Dynamic control method according to claim 1, characterized in that it comprises the steps of: observing an error in one or more h or physical devices; receiving from said extended name service a request for services which is associated with said damaged one or more entities or devices; control of said service's information and transmission of information about the services, which will be requested. 13. Dynamic control method according to claim 1, characterized in that the system comprises at least one extended name service: 14. Dynamic control method according to claim 1, characterized in that the * * extended name service frame functionality is realized *. • · • « 15. Dynamic control procedure according to • * * exam claim 1, characterized in that said * * * · * · * extended name service frame is a separate name service. 16. Dynamic control method according to claim 1, characterized in that: ***: widened named jänstram is part of a convex 32 11 one or more server applications (SP) for the provision of one or more services, and which Applications (CU1, CU2) use the aforementioned electric services, * one or more whole or physical ancestry (EQ) to offer one or more services; a control unit (HAS), comprising in relation to said whole or physical device * 10, characterized in that the system further comprises: an extended name service frame (ESA) for registering one or more services, said name frame (ESA) storing information on said one or all services, said information being obtained from said service's registration process, and said name service frame associates a specific service with a specific software whole or physical (EQ), providing said service. 18. Dynamic control system according to claim 17, characterized in that said naming service frame registers one or more. ! applications (CU1, CU2) and stores information ♦ said customer applications (CU1, CU2), which formation is obtained in said customer applications: [[[: CU2] said registration process, and associates specific customer application (CU1, CU2) s · ** ·. service. • * 19. Dynamic control system according to. Claim 18, characterized in that said * * cation about said customer applications (CU1, CU2) and * itirn nchnno about axr f ί -ί omHo · 33 20. Dynamic control system according to claim 17, characterized in that said mation on said services comprises at least the following: the service; the access point of the service, to which the service: belongs; service interface address; status of service; and 10 physical information about the service. A dynamic control system according to claim 17, characterized in that the name service framework (ESA) comprises: an interface (IF) for receiving a landing from said control unit (HAS), if the agricolourer or physical device functions incorrectly; and updating means (UM) for updating the status information of the services which are provided by the said malfunctioning program unit or physical device (EQ). 22. Dynamic control system according to * «: claim 21, characterized in that it named the frame of the frame (ESA) comprises:! 25 message means (NM) for notification of it: "* · the status information of the customer applications CU2), which are registered to use • # services produced with said incorrect • software whole or physical device, 23. Dynamic control system according to * * * Claim 17, characterized in that it terminates * in * * (TTTVT G λ of * 34 117 the access point of the service to which service: belongs; the physical or other property status of the service; service availability; number of instances of said service; and hint at the caller interface user interface (CU1, CU2). Dynamic control system according to claim 23, characterized in that the output service frame (ESA) comprises: message means (NM) for message to the application (CU1, CU2), where a service, of which customer application (CU1, CU2) is aware , status t 15. Dynamic control system according to claim 17, characterized in that the output named frame (ESA) comprises: an interface (IF) for receiving a search request from a customer application (CU1, CU2); Providing means (NM) for providing a service information to said customer application CU2), if the service meets the search criteria. : 26. Dynamic control system according to! Claim 25, characterized in that the search application IM 9 comprises at least one or more of the following: the service instance identifier; or • M: a specific database fragment. Dynamic control system according to claim 17, characterized in that the printed name service framework (ESA) comprises at least one * * · several distribution rules (DR), which apply * * 1 P, 1, •. _ * on enm rom o Ί -to t- π 1 1 rlnr * ntTri sh- * · - * A The system comprises receiving means (HAS) producing a message of error or for observing an error in one or more whole or physical arrangements (EQ); Said extended name service frame (ESA) includes interface (IF) for receiving a call service associated with said damaged multiple unit or physical device (EQ controller1 (CM) for checking said 10 t of said information; and transmission means (NM) ) for sending information that matches the request. Dynamic control system according to claim 17, characterized in that the computer 15 comprises at least one extended name service frame (] 30. Dynamic control system according to claim 17, characterized in that said spaced name service frame functionality (ESA) remains with CORBA. 31. Dynamic control system according to claim 17, characterized in that said street name service frame (ESA) is a separate name entity. 32. A dynamic control system according to claim 17, characterized in that said street name service frame (ESA) is part of a converge naming service. • Extended name service frame for possible. ”··] of service availability in a computer system, • * Extended name service frame includes at least:, an interface (IF) for receiving messages •« «from customer applications (CU1, CU2 ), service provider • · • * / nn) Ί __ Λ _ λ__1 1 1 1_ J TT- _ »36 process, and which name service frame associates a service to a specific software unit or device (EQ), which produces said service 34. Extended name service frame according to pat 5 33, characterized in that said named service service frame (ESA) registers one or more; applications (CU1, CU2) and informally stores said customer applications (CU1, CU2), which formation is obtained in said customer applicationsE10 CU2) said registration process, and associates specific customer application (CU1, CU2) with one's service; Extended name service framework according to pat 34, characterized in that said info 15 about said customer applications (CU1, CU2) comprises stone one of the following: the customer's name; customer interface address; customer status; and 20 physical information about the customer. 36. Extended name service frame according to pat 33, characterized in that said info * # * * »h:; if said services comprise at least one of the services. ft tj end's name; ft * • ** 25 access point, to which end: hear; service interface address; * ·. * ··. status of service; and • * physical information about the service. * 30 37. Extended name service frame according to pat # * * 33, characterized in that it extends * »• · 4 ------ k j-. . 37 updating means (UM) for updating the status information of the services, which services pro by means of said incorrectly functioning program unit or physical device (EQ). 38. Extended name service frame according to pat 37, characterized in that the printed name service frame (ESA) comprises: message means (NM) for notification of change information to the customer applications (CU1, which are registered to use said service which are produced with said incorrect function < raw material whole or physical device (EQ). 39. Extended name service frame according to pat 33, characterized in that the output name service frame (ESA) comprises: an interface (IF) for receiving a service position from a customer application (CU1, CU2), said service order comprises at least one of the following : 20 the name of the service in question; the access point of the service, to which the said belongs; • *: physical or other characteristic of said service::: status of service; Service availability; ; *** the number of instances of said service; and * · ·: reference to the caller interface for • ·· t '·· / customer application (CU1, CU2). • * *** 40. Extended name of the frame of the frame according to pat <30 39, characterized in that it includes the * frame of the frame (ENS): * # «• · nnö / ^ / ^ Δΐ f TiTM \ f Xv * 1 -. An interface (IF) for receiving a search request from a customer application (CU1, CU2); donation means (NM) for providing the service information to the said customer (<5 CU2), if the service meets the search criteria. 42. Extended name service framework according to Pat 41, characterized in that search criteria: includes at least one or more of the following: the service's identifier of the service; or a specific database fragment. 43. Extended name service frame according to pat 33, characterized in that the named service name (ESA) comprises at least one multiple distribution rules (DR), which application service registered to the extended service service comprises two or more instances of service. . 44. Extended name service frame according to Pat. 33, characterized in that: the system comprises receiving means (HAS) producing a message about a fault or observing a fault in one or more whole or physical arrangements (EQ); : mention extended name frame (ESA) includes that: • »« · · · 25 interface (IF) for receiving a call service connected to said damaged «♦ several whole or physical devices (EC • M I. · * control means (CM) for checking said «* · * · 's said information; and 3. means of transmission (NM) for sending information * .ϊ · * the services which match the request. ··· * * A S. TTt ".vi rJfTAii riAmnfiän.Qhr ^ m onl i rrh na t-, 39 name service trunk functionality (ESA) real-time CORBA. 47. Extended name service frame according to pat 33, characterized in that said output service frame (ESA) is a separate name service. 48. Extended nainnt jänstam according to pat 33, characterized in that said out nainnt jänen tram (ESA) is part of a conventional naming service. 10 • »• · ·» «· * ·« · * <»» · · »» «· *« • ft »• ft mm ft 1 ft # ··· ft · ft ft ft •« ft • · ftftft • ft ft · ft1 · • • ft ft • «ft • • ft ft1 ft ft Λ