RU2754606C1 - Method for identifying the service in the enum structure - Google Patents

Abstract

FIELD: service identification.SUBSTANCE: invention relates to a method for identifying a service. In the method, a request for information about the service is formed, a registry of services is pre-created, in which, using the first network tool, at least one record describing information about the service is pre-entered, where information about the service includes at least network addresses and metadata of the service, and the registry of services is made with the possibility of changing, supplementing and removing the record characterizing the properties of the service, then using the second network tool, at least one resource record is entered into the DNS zone of the ENUM domain associated with the phone number, containing the type of service, a link to the registry of services, the service identifier in the registry, the service parameters for further formation of an appeal to the registry of services, the number defined for the ENUM is converted in a certain way to the ENUM domain name, after that, using a third network tool, a DNS query to obtain resource records for this ENUM domain name using DNS tools is formed, at least one resource record associated with the specified ENUM domain name of the phone number is sent from the DNS server to the third network tool in response to a DNS request, information about the service identifier, service type, links to the service registry, service parameters for further formation of an appeal to the service registry is determined from at least one resource record, using a third network tool, a request to the service registry that at least contains the service identifier is formed and executed, in response to an appeal to the service registry, data about the network address and metadata of the service are sent to the third network tool from the service registry.EFFECT: simplification of the procedure of identifying the service.1 cl, 4 dwg

Description

The technical solution relates to the field of electronic communications, in particular to methods of identification and obtaining information about a service based on completed requests via telecommunication networks.

From the prior art, a system is known for mapping the E.164 ENUM telephone numbers (E.164 NUmber Mapping), according to the protocols of which it becomes possible to combine the EUL 64 telephone numbering system with the Internet addressing system. ENUM is guided by the priority and algorithms for using the domain name system (DNS ) for storing and receiving information about resources in accordance with the telephone number, which is reproduced in a domain name with a set of resource records (NAPTR) about predefined and known types of services in the form of addresses on the Internet, rules and parameters for their processing, for example

- VoIP,

- IP fax servers,

- voicemail servers,

- PSTN services (redirection),

- and others, which are defined in the respective static depository, informatively posted on the IANA Enumservice Registrations page.

The initial and most commonly used ENUM scenario is setting up redirection rules between the telephone network and VoIP Internet telephony systems. For example, if the phone number has different profiles, ENUM can automatically change the receiving method and location by redirecting the call depending on what type of network the receiving party is on (Called Party according to ITU Recommendation Q.731) (automatic switching between mobile phone and VoIP for the most convenient or less costly method of communication to complete the call) or depending on the time of day, for example, if call forwarding is done during lunchtime. ENUM may also match a phone number with an email address, web address, or other service defined in the custodian above.

From the prior art, patent RF No. 2483352 is known, which discloses a method for identifying a service, including the steps at which a service request is received, including the address of a unified resource locator and a field for indicating the type of service content.

The method, device and system for identifying a service described in RF patent No. 2483352 assumes the presence in the system architecture of an element in the form of a device, a wireless application protocol gateway (WAP GW). The WAP GW functions as a pre-configured device for receiving a multimedia messaging service request (MMS), including a field for indicating a service content type from a service request transmitted by the terminal and the service request resolving device. When the service gateway address (APN) is configured incorrectly, as a result of which this request cannot be processed on the device, the identification of the service type from the service request occurs according to the field included in the service request. The address to the address of the MMS service specified in the request is carried out by contacting the ENUM server, which contains the address of the sender's home MMSC, retrieves it and returns it to the WAP GW. WAP GW forwards the response to the request of the user's terminal, which now gets the opportunity to apply for the received address directly to the service.

The disadvantage of the known solution is the use of a gateway (WAP GW), the task of which is to initiate an appeal to the ENUM server with an incorrectly formed address of the service gateway as part of a service request. This assumes that in order to identify a service, it is imperative that a service address must be available to fulfill the request. This imposes additional conditions on the service identification process. Another disadvantage is that the existing solutions deal exclusively with communication services.

The objective of the claimed technical solution is to create a more universal method for identifying services, which can be used for any type of service, including non-communication, and which does not require a gateway (WAP GW), and in which there is no need to know the address of the service in advance. An additional task for the claimed technical solution is to identify the address of the service, if the type of service and the subscriber's phone number are known in advance.

The task is solved due to the fact that the service identification method includes the stages at which:

- form a request to obtain information about the service,

according to the technical solution,

pre-create a register of services, to which, using the first network tool, preliminarily make at least one record characterizing the properties of the service, and the register of services is made with the possibility of changing, supplementing and removing the record characterizing the properties of the service,

then, using the second network tool, at least one resource record is entered into the ENUM DNS zone of the domain associated with the phone number, containing the type of service, links to the service register, service identifier in the register, service parameters for further formation of an appeal to the service register ,

convert the number in the manner defined for ENUM to the domain name ENUM,

after that, using a third network tool, form a DNS request to obtain resource records for a given ENUM domain name using DNS tools,

sending from the DNS server to the third network facility in response to the DNS request at least one resource record associated with the specified domain name ENUM of the telephone number,

determine from at least one resource record information about the service identifier, type of service, links to the service register, service parameters for further generating an appeal to the service register,

with the help of the third network tool, a request is generated and carried out to the service register, which at least contains a service identifier,

in response to an appeal to the service register, data on the network address and service metadata are sent to the third network facility from the service register.

The technical result, which is achieved when implementing the claimed method, is to ensure the receipt of the network address and metadata of at least one service associated with the subscriber's telephone number. This information is fetched from the service registry, which stores metadata about services. The service registry is capable of storing information about any type of service, not limited to the list of IANA Enumservice Registrations. In this case, a link to the register of services, and the service identifier is saved in the resource records of the ENUM of the subscriber's domain. The metadata that is returned by the service registry is machine-readable. This technical result was obtained for the first time.

Another new technical property is the expansion of the functional properties of the method by its application for non-communication services, which significantly expands the possibilities of its use.

The claimed method is illustrated using the accompanying drawings, which in no way limit the embodiments and applications of the claimed method, but are given to explain the essence of the technical solution.

FIG. 1 shows the system architecture for a typical process of identifying a service in the ENUM structure by the subscriber's telephone number and using the identified service.

FIG. 2 shows a diagram of the organization of requests and data streams of the method.

FIG. 3 provides a diagram of an example of using ENUM to obtain medical data of a subscriber of a telephone number within the framework of the functioning of rescue services in case of emergency.

FIG. 4 provides a diagram of an example of using ENUM to obtain technical information about a vehicle during vehicle maintenance.

Next, a detailed description of the claimed method will be given with reference to the accompanying drawings and its main embodiments. This description is intended to explain the essence of the claimed method and is not intended to be any limitation of implementation.

For a clearer and more unambiguous understanding of the essence of the claimed method, below are the thesaurus of the concepts used.

The first network tool is a network technical solution for predominantly remote work on a server.

The second network tool is a network technical solution that can be used to edit the DNS zone.

The third network facility is a terminal that receives information from DNS and the service registry.

Subscriber number (subscriber number) - telephone number according to E.164 standard.

Metadata is structured information that characterizes existing or expected objects in the information environment, such as service profiles, protocols and rules for accessing information provided by services, service provision regulations, resources, information data, etc.

Service - a software and hardware system (a set of telecommunication and non-telecommunication services associated with software and hardware systems), which provides interactive data exchange to the user, has a unique network address (or several network addresses), which interacts with other third-party applications by exchanging data on request user. The understanding of the concept of "service" according to this definition is broader in relation to the given analogous concept in the patent of the Russian Federation No. 2483352, but does not contradict it.

The service register is an information and telecommunications software and hardware system that stores and issues, upon an appropriate request, information about services, such as, for example (non-exclusively) network addresses responsible for processing service requests, protocols and rules for processing requests (parameters of requests, receiving responses , their processing) of this service, requirements for authentication and authorization, other metadata. Services in the service registry must always have a unique identifier that can be used to request information about that service.

A subscriber of a telephone number is a person or device to which this number is assigned in the E.164 format.

Resource record is a record of the correspondence between the name and service information in the domain name system (DNS).

DNS server is a software and hardware solution for ensuring the functioning of the hierarchical domain name system in accordance with Internet standards.

In the prior art, service types must be pre-known and pre-defined in the IANA Enumservice Registrations repository. The data in the specified repository is not intended for automatic reading, but only statically recalculates the set of available service types.

According to the declared technical solution, it is proposed to create a register of services that must meet the following conditions: each service has at least one original (unique) unique identifier. Using this unique identifier, the service registry searches for and provides network addresses and metadata regarding the corresponding service.

The types of services stored in the service registry can be both telecommunications and non-telecommunications.

The service registry stores blocks of data, in particular regarding:

(1) properties of the service, including data regarding (1.1) the name of the service, (1.2) the network addresses of the service (1.3) the protocol for the service, (1.4) the general description of the service,

(2) functionality and conditions of service execution, including data on (2.1) telecommunication protocols used by the service, (2.2) professional protocols used by the service, (2.3) formalized description of the structure of services included in the service, (2.4) correlated with (2.3) the minimum set of parameters necessary for the execution of the service, (2.5) correlated with (2.3) the full set of parameters necessary for the execution of the service, (2.6) the admissible minimum and maximum limit values of the parameters for the execution of the service,

(3) service access schemes, including data on (3.1) a formalized order of sequence of actions for accessing a service, (3.2) a relevant set of parameters for carrying out authentication, authorization and verification procedures when accessing a service,

(4) security requirements for the use of the service, including data regarding (4.1) a list of CAs that can issue certificates for use with the service, (4.2) validity time intervals for the certificates used,

(5) the formats of the input and output parameters of the service, including data on (5.1) the specification of the initial data required to perform the service, which correlates with (2.4) and (2.5), (5.2) the specification of the initial data for each service, which correlates with ( 2.3),

and issues, upon request, information about services, such as, for example, network addresses at which service resources are located, protocols by which the service operates, service requirements for authentication, authorization and verification procedures, and other service metadata.

This list is not exhaustive and does not contain mandatory data blocks.

Services in the service registry have a unique identifier that can be used to request information about the service.

The claimed solution is explained in FIG. 1 architecture. The DNS standard defines several types of resource records 105 (A, AAAA, TXT, MX, NAPTR, and others). Any number of records 105 of any of these types can be specified for the domain name 102. In general, resource records 105 are created and edited using the second network tool 107. The list of resource records 105 and their structure can be changed using the second network tool 107.

DNS zone 103 of domain 102 is served by at least one DNS server 104, which provides answers to DNS queries 115 of Internet users by selecting appropriate records 105 from DNS zone 103.

In the existing prior art, resource records 105 contain direct links to service 113. In the claimed solution, resource records 105 do not directly store links to service 113, but resource record 105 contains the type of service, links to the service register 111, service identifier and other information , which, for example, identifies object 114 in service 113, and also personalizes the terms of use of service 113.

According to the claimed method, a register of services 111 is preliminarily created, into which, using the first network tool 110, at least one entry [about service 113] is made, characterizing the properties of the service 113. The register of services 111 is configured to change, add or delete records characterizing the properties services 113.

With the help of the second network tool 107, at least one resource record 105 is entered 117 into the ENUM DNS zone 103 of the domain 102 associated with the telephone number 106, which contains the type of service, link 119 to the service register 111, service identifier, service parameters for further formation of an appeal to the register of services 111, for example, the subscriber identifier of the telephone number 106 in the service 113.

Knowing the number 106, the consumer of the service 108 using the third network tool 109, in a standard ENUM way, converts this number into the associated ENUM 102 domain name 101. For the domain name 102 obtained by transforming, from the consumer of the service 108 using the third network tool 109, the standard means direct DNS request 115 for obtaining resource records 105 of DNS zone 103 of domain 102 to DNS server 104, which serves this domain name 102 or is a caching DNS server. In response to query 115, DNS server 104 returns a list of resource records 105 related to this domain name 102. The number of resource records 105 returned by DNS server 104 may be more than one.

Having received a list of resource records 105 with the help of the third network tool 109, the consumer of the service 108 using the third network tool 109 selects from the list those resource records 105 that contain an indication of the desired type of service that the service consumer 108 wishes to use.

Resource records 105 can contain any additional information (for example, about parameters describing the place and time of use of the service), which are an additional filter for selecting the desired resource records 105.

At least one resource record 105 is selected, from the contents of which information about the type of service is taken, links 119 to the service registry 111, service identifier 113 in the service registry 111, and other information are taken, which, for example, identifies object 114 for service 113, and also personalizes the conditions of use of the service 113. On the basis of this data, a request 116 is generated and sent by the third network tool 109 to the service registry 111 to obtain the Internet addresses and metadata of the service 112.

The service registry 111, having received a request 116 containing a service identifier, returns 121 to the third network facility 109 to the service consumer 108 the metadata and Internet addresses of the service 112.

The consumer of the service 108, using the received Internet addresses and metadata 112, with the help of the third network tool 109 addresses 118 to the service 113 to obtain the desired service or information.

Fig. 2. shows a diagram of the organization of requests and data streams of a method for identifying a service, provided that the architecture shown in Fig. 1 is created.

The service consumer 201 accesses the DNS server or caching DNS server 202 serving the ENUM DNS zone of the domain 103 to obtain resource records 203. It should be noted that the service consumer 201 performs actions using the third network tool 109. The skilled person should be clear that the DNS zone ENUM domain in 103 is served by at least one DNS server 202.

The DNS server 202, based on the information available in the ENUM DNS zone of the domain 103, determines the list of resource records 203 and returns 207 it to the service consumer 201.

From the resource record 203 take 208 information about the type of service, service registry URI, service identifier, service parameters. Based on this received data, a request 209 is made to the service registry 204 in order to obtain data about the Internet address of the service and the metadata of the service. The service registry 204, based on the received request 209, forwards the response 210 to the third network facility 109, which is used by the consumer 201, which contains this service information.

Thereafter, the consumer of the service 201, using the third network tool 109, makes a call to the service 211 using the obtained service metadata. In response, the consumer 201 with the help of the third network tool 109 receives 212 the service result.

Below are examples of the implementation of the declared object. These examples are intended to confirm the applicability of the method. However, the examples given do not limit the application of the claimed subject matter. A specialist in the field of telecommunications or information technology should understand the principles of constructing a protocol of interaction between the user terminal and servers for the implementation of the declared purpose.

Example 1. Using ENUM to obtain medical data for a subscriber of a telephone number, which is a registrant of the corresponding ENUM-domain within the framework of the functioning of emergency services for the population (as an example, a service type "MED" is created).

An example is explained in FIG. 3, which shows a diagram of the use of ENUM for obtaining medical data of a subscriber of a telephone number within the framework of the functioning of rescue services in case of emergency.

Previously, for example, the administrator of the register of services 301 with the help of software, for example, using the administrator panel 302, enters 303 into the register of services 304 records about services 310, 311, which contain information necessary for rescue services and characterizing the properties of services. These services are provided by two relevant medical institutions.

The service registry administrator panel 302 is configured to change, add or delete entries characterizing the properties of services. An example of a service belonging to the rescue services can be medical institutions that, upon an authorized request, issue signaling information about the subscriber's health. An example of signaling information: blood type, drug sensitivity, etc., that is, such information indicating what restrictions should be observed when providing medical care. It should be clear that the databases of the relevant medical institutions providing services 321, 322 store medical signaling information about the subscriber of the telephone number 305. These medical records obtained as a result of examinations, medical examinations and other medical actions in relation to the subscriber of the telephone number in these medical institutions.

Previously, the subscriber of the telephone number 305 using standard means for working with domain names, for example, the registrant panel 306, must register the ENUM domain name 307 corresponding to the subscriber's telephone number.

Resource records NAPTR 308 are created in the ENUM DNS zone of the domain, using tools for working with DNS zones, for example, using the registrant panel 306. Each such record contains the type of service "MED", the service identifier, link 309 to the register of services 304 and subscriber identifier of the telephone number in the service database. Each of these resource records corresponds to one medical institution where the subscriber is served. Thus, each of the medical institutions is a service that, upon an authorized request, provides signaling medical information that is known to this institution.

If it is necessary to provide emergency assistance to a subscriber of a telephone number, for example, upon receipt of a message 312 about the need for an ambulance, knowing the subscriber's number, the ambulance dispatcher 313, using special software 314, addresses 315 to the ENUM DNS zone of the domain of the subscriber telephone number 305, finds there all resource records containing the type of service "MED" 308, takes service identifiers from these records, links 309 to the service register 304, accesses the service register 304 and receives 316 metadata 310, 311 servers of medical institutions 321, 322, however, URI, to which he can apply for signaling medical information about the subscriber using the subscriber identifiers of the telephone number in the service databases, which are also contained in the resource records of the ENUM domain 308.

Further, the received data is transmitted 317 to the software of the ambulance team 318, which in turn, using authorized requests 319, 320 to the corresponding services 321, 322, receives signaling medical information about the subscriber of the telephone number.

Thus, access to signaling medical information (which can be processed automatically), in the event of emergency situations, is greatly facilitated, which reduces the likelihood of medical errors in the provision of emergency care.

Example 2. Using ENUM to obtain technical information about a vehicle during vehicle maintenance (as an example, a service type "VEHICLE" is created).

An example is explained in FIG. 4, which shows a diagram of the use of ENUM for obtaining technical information about a vehicle during vehicle maintenance.

Previously, for example, the administrator of the register of services 401 using software, for example, the administrator panel of the register of services 402, enters 403 into the register of services 404 entries 410 about the service 417, which functionally belongs to the services that carry out maintenance of vehicles and which characterizes the properties service. The service registry administrator panel 402 is configured to modify, add, or delete entries like 410 that characterize the properties of the services. An example of a service belonging to the services performing the maintenance of vehicles is a vehicle maintenance station (STO), which, upon an authorized request, issue the available technical information about the vehicles that were serviced at this service station. An example of technical information: a list and dates of routine maintenance performed, brands of engine oils that were used, identified fault codes with subsequent recommendations for repairing a vehicle, a list of recommended spare parts for replacement, that is, information that may be useful for the following technical work with a vehicle. means.

Previously, the ENUM domain name 407 corresponding to the phone number of the SIM card that is integrated into the vehicle 405 must be registered by standard means for working with domain names, for example, the registrant panel 406. That is, the subscriber of the phone number in this case is the vehicle.

NAPTR 408 resource records are created in the ENUM domain's DNS zone using DNS tools, for example, the 406 registrant panel. Each such record contains the "VEHICLE" service type, the service identifier, and 409 links to the 404 service register and the telephone subscriber identifier. numbers in the service database. Each of these resource records 408 corresponds to one technical establishment, the server of which 417 contains the corresponding data, and serving this vehicle. Thus, each workshop is a service that, upon an authorized request, provides the available technical information about vehicles.

If it is necessary to find out the history of vehicle maintenance, for example, when repairing a car in another city 411, knowing the number of the SIM card that is integrated into the car 405, an employee of the service station 412 using special software 413, addresses 414 to the ENUM DNS zone of the subscriber's domain, finds there, all resource records containing the service type "VEHICLE" 408, takes service identifiers from these records, links 409 to the service register 404, accesses the service register 404 and receives 415 metadata and Internet addresses of the institution's service 417, which can be contacted for technical information about the vehicle using the subscriber identifiers of the telephone number (vehicle) in the service databases, which are also contained in the resource records of the ENUM domain 408.

Further, with the help of specialized software 413, authorized requests 416 are generated and technical information about the vehicle with an integrated SIM card is obtained.

Thus, access to technical information (which can be processed automatically), if necessary, is greatly facilitated, which reduces the likelihood of errors in the maintenance of vehicles.

On the basis of the above, the specialist should understand the solution to the task and the achievement of the claimed technical result.

Claims (11)

A method for identifying a service, which includes the steps at which: - form a request to obtain information about the service, characterized in that pre-create a service register, into which, using the first network tool, preliminarily make at least one record characterizing information about the service, where information about the service includes at least network addresses and service metadata, and the service register is made with the ability to change, supplement and remove the record characterizing the properties of the service, then, using the second network tool, at least one resource record is entered into the ENUM DNS zone of the domain associated with the telephone number, containing the type of service, a link to the service register, a service identifier in the register, service parameters for further formation of an appeal to the service register, convert the number in the manner defined for ENUM to the domain name ENUM, after that, using a third network tool, form a DNS request to obtain resource records for a given ENUM domain name using DNS tools, sending from the DNS server to the third network facility in response to the DNS request at least one resource record associated with the specified domain name ENUM of the telephone number, determine from at least one resource record information about the service identifier, type of service, links to the service register, service parameters for further generating an appeal to the service register, with the help of the third network means form and carry out a request to the service register, which at least contains a service identifier, in response to an appeal to the service register, the network address and service metadata are sent to the third network facility from the service register.

Images