WO2019141376A1 - Procédés et appareil - Google Patents

Procédés et appareil Download PDF

Info

Publication number
WO2019141376A1
WO2019141376A1 PCT/EP2018/051352 EP2018051352W WO2019141376A1 WO 2019141376 A1 WO2019141376 A1 WO 2019141376A1 EP 2018051352 W EP2018051352 W EP 2018051352W WO 2019141376 A1 WO2019141376 A1 WO 2019141376A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
service server
name service
records
reduced number
Prior art date
Application number
PCT/EP2018/051352
Other languages
English (en)
Inventor
Anubhav Srivastava
Mahesh SURYAWANSHI
Nalin VILOCHAN
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2018/051352 priority Critical patent/WO2019141376A1/fr
Publication of WO2019141376A1 publication Critical patent/WO2019141376A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers

Definitions

  • Some embodiments relate to methods and apparatus for use in the context of requests to and responses from domain name service servers.
  • a DNS domain name service
  • a method comprising: causing a request to be sent to a domain name service server comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and receiving said reduced number of record responses.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server.
  • the type of records may comprise one or more of: SRV records, A records, and
  • the information indicating that the domain name service server is to return a reduced number of record responses may be configured to control switching from a first site to a second site in dependence on said information.
  • a method comprising: receiving at a domain name service server a request comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and causing said reduced number of record responses to be provided.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses comprises one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server and said method comprises providing the type of records in said responses.
  • the type of records comprises one or more of: SRV records, A records, and AAAA records.
  • the method may comprise using said information indicating that the domain name service server is to return a reduced number of record responses to control switching from a first site to a second site in dependence on said information.
  • the method may comprise selecting records in dependence on a load balancing algorithm, wherein the number of records selected is dependent on said information indicating that the domain name service server is to return a reduced number of record responses.
  • an apparatus comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to: cause a request to be sent to a domain name service server comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and receive said reduced number of record responses.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server.
  • the type of records may comprise one or more of: SRV records, A records, and AAAA records.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be configured to control switching from a first site to a second site in dependence on said information.
  • an apparatus in a domain name service server comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to: receive at a request comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and cause said reduced number of record responses to be provided.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses comprises one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server and said method comprises providing the type of records in said responses.
  • the type of records comprises one or more of: SRV records, A records, and AAAA records.
  • the at least one memory and the computer code may be configured with the at least one processor to use said information indicating that the domain name service server is to return a reduced number of record responses to control switching from a first site to a second site in dependence on said information.
  • the at least one memory and the computer code may be configured with the at least one processor to select records in dependence on a load balancing algorithm, wherein the number of records selected is dependent on said information indicating that the domain name service server is to return a reduced number of record responses.
  • an apparatus comprising: means for causing a request to be sent to a domain name service server comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and means for receiving said reduced number of record responses.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server.
  • the type of records may comprise one or more of: SRV records, A records, and AAAA records.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be configured to control switching from a first site to a second site in dependence on said information.
  • an apparatus in a domain name service server comprising: means for receiving a request comprising name information and information indicating that the domain name service server is to return a reduced number of record responses; and means for causing said reduced number of record responses to be provided.
  • the information indicating that the domain name service server is to return a reduced number of record responses may comprise percentage information.
  • the information indicating that the domain name service server is to return a reduced number of record responses may be provided in a field in said request.
  • the field may be dedicated to controlling a number of record responses provided.
  • the request may comprise a domain name service query.
  • the request may be for a fully qualified domain name resolution.
  • the information indicating that the domain name service server is to return a reduced number of record responses comprises one of a plurality of different options.
  • the request and said plurality of responses may comprise SIP messages.
  • the name information may comprise QNAME.
  • the request may further comprise information as to a type of records to be provided in responses from said domain name service server and said method comprises providing the type of records in said responses.
  • the type of records comprises one or more of: SRV records, A records, and AAAA records.
  • the apparatus may comprise means for using said information indicating that the domain name service server is to return a reduced number of record responses to control switching from a first site to a second site in dependence on said information.
  • the apparatus may comprise means for selecting records in dependence on a load balancing algorithm, wherein the number of records selected is dependent on said information indicating that the domain name service server is to return a reduced number of record responses.
  • a computer program comprising program code means adapted to perform the herein described methods may also be provided.
  • apparatus and/or computer program product that can be embodied on a computer readable medium for providing at least one of the above methods is provided.
  • non-transitory computer program product comprising computer executable instructions which when executed by at least one processor perform any of the previously discussed methods.
  • Figure 1 shows DNS configuration and record mapping for two example sites
  • Figure 2 shows a signal flow in an embodiments
  • FIG. 3 shows modified IP selection for the sites of the arrangement of Figure
  • Figure 4 shows a system in which embodiments may be used
  • Figure 5 shows a system in which embodiments may be used.
  • Figure 6 shows an apparatus
  • DNS domain name service
  • a NAPTR name authority pointer
  • a SRV service record query
  • Each site may have a plurality of nodes. Each node may be mapped to different Internet protocols (IP). If all the nodes from one of the sites, for example the active site, is not available then a request may needs to be tried with all the nodes of another of the sites, for example, the backup site.
  • IP Internet protocols
  • the active site may be configured with a SRV
  • IP A/AAAA records
  • a site (for example the active site) may become unavailable. This may be due to planned/unplanned activity. The may mean that means all nodes of that site go out of service.
  • DNS configuration logic In accordance with DNS configuration logic, a request will be tried on all nodes of the active site before being tried on nodes of the second site. This may add an extra delay in processing the request. As a result of this, there may be a relatively high chance of a transaction being terminated. This may result in call failures and a deterioration in end user experience. In this example only two sites are considered but in practice, a network will generally have many more than two sites.
  • Some embodiments may provide for faster switchover to another site for processing messages successfully in the network.
  • Some embodiments will, based on a determination that a plurality of nodes of one site are not reachable that the respective site is down and the message will be tried on the nodes of another site.
  • Some embodiments may restrict the number of SRV and A/AAAA records from the DNS server itself.
  • flexibility will be provided to a DNS client to request a percentage of records out of overall configured ones from the DNS server.
  • Some embodiments may provide a field QLIMIT in DNS query along with existing fields QNAME, QTYPE & QCLASS.
  • QLIMIT may take an integer value which will mean a percentage of records that needs to be returned from DNS server.
  • the QLIMIT field may be filled by the node (DNS client) which is performing DNS lookup of the SRV or A/AAAA records.
  • DNS client DNS client
  • the QLIMIT field may be used by the DNS server to filter out same priority records based on the percentage.
  • the QLIMIT field may apply to the A/AAAA query alternatively or additionally. For example, if each SRV records is mapped to 4 A/AAAA records and DNS query for fetching A/AAAA records contains QLIMIT as 50 it means, 50% record will be returned as response. So in this case out of 4 mapped A/AAAA record, only 2 records will be returned.
  • FIG. 1 shows an example DNS Configurations SRV and A Records Mapping for two example sites according to current proposals.
  • Site 1 DNS records which are to be looked up are referenced 404a and Site 2 DNS records which are to be looked up are referenced by 404b.
  • a NAPTR record query returns a response 401 in the form sip.tcp.example.com.
  • a SRV query gets performed which returns 8 SRV records 400a to h which maps to Site-1 and Site-2.
  • the SRV records 400a to d belonging to Site-1 have higher priority (10) as compared to the priority (20) given to the SRV records 400e to h belonging to Site-2.
  • the SRV records serverl .example.com to server4.example.com belong to Site-1 and server5.example.com to server8.example.com belong to Site-2
  • Each SRV record is mapped to 4 A- records resulting in 16 IPs (IP1...IP16) for Site-1 referenced 402a to 402d and 16 IPs (IP17...IP32) for Site-2 referenced 402e to h.
  • FIG. 2 shows the communication between a DNS client 406 and a DNS server 408 in accordance with an embodiment.
  • This example uses a DNS Query (SRV and A record) with a QLIMIT value.
  • some embodiments provide the flexibility to the DNS client to request a percentage of records out of overall configured ones from the DNS server
  • step S1 the DNS client sends a DNS query along with fields QNAME, QTYPE, QCLASS and QLIMIT.
  • the QNAME may be in the form of sip.tcp.example.com.
  • the QTYPE is 33 indicating a SRV query.
  • the QCLASS is IN.
  • QLIMIT will take integer value which indicates the percentage of records that needs to be returned from DNS server.
  • the QLIMIT field will be filled by the node (DNS client) which is doing DNS lookup of the SRV or A/AAAA records.
  • the QLIMIT VALUE is 50 indicating that 50 percent of the records need to be returned from the DNS server.
  • the DNS server may respond the QLIMIT parameter so to return the required number of records in combination with its existing load balancing algorithm and the parameter QLIMIT.
  • the DNS server filters out 50% of the SRV records from each priority based on its load balancing algorithms and sends a response to the DNS client.
  • the DNS usually sends the list of IP addresses (any DNS record for SRV/A/AAAA) in a different order each time it responds to a new client. This may be by using a round-robin/random method or algorithm. This algorithm of deriving sequence of records will, based on QLIMIT, cause the appropriate number of records to be selected (using the round- robin/random principles) and returned to the client.
  • step S3 the DNS client makes a request to the DNS server for A records.
  • the QNAME is of the form of serverl .example.com.
  • QTYPE is 1 representing an A query.
  • the QCLASS is IN (Internet) and in this example the QLIMIT is 50.
  • step S4 the DNS filters out 50% of A records based on its load balancing algorithm and sends back a DNS response to the DNS client.
  • step S5 the DNS client makes a request to a second DNS server for A records.
  • the QNAME takes the form server2.example.com
  • the QTYPE is 1 representing an A query
  • the QCLASS is IN
  • the QLIMIT is 50.
  • step S6 the second DNS server filters out 50% of A records based on its load balancing algorithm and send the response back to the DNS client.
  • Figure 3 shows the modified DNS server responses for the first and second sites 404a and 404b.
  • DNS response will contain twO higher priority (10) records belonging the first site. These may be serverl .example.com referenced 400a in Figure 1 and server2.example.com referenced 400b. There may be two lower priority (20) records belonging to the second site. These may be server5.example.com referenced 400e and server6.example.com referenced 400f.
  • the SRV records reference 400c, 400d, 400g and 400h will be skipped and DNS server will not return these records in the response.
  • the QLIMIT field may alternatively or additionally be extended to A/AAAA query. For example, if each SRV records is mapped to 4 A records and a DNS query for fetching A records contains QLIMIT as 50, this means that 50% of the records will be returned as response. So in this case out of 4 mapped record with each SRV record, only 2 A records will be returned.
  • an A query on serverl .example.com will return IP1 and IP2.
  • An A query on Server2.example.com will return IPS and IP6.
  • the value of QLIMIT may indicate the percentage of responses which are returned.
  • the value of QLIMIT may indicate the percentage of responses which are not returned.
  • the QLIMT may have one of a plurality of fixed values which control the number of responses returned/not returned.
  • QLIMIT may be defined by a single bit. One value may indicate that there is not limit and the other value may indicate that the particular number of responses are to be returned/not returned.
  • QLIMIT may have four values representing 0, 25, 50, 75 and 100 percent.
  • the number of values may be more or less than four.
  • the actual percentage represented by the values may be differ at least partially or completely from the example.
  • QLIMIT may have any integer value from 0 to 100 percent.
  • QLIMIT may be dependent on the nature of the network which has been provided.
  • the value of QLIMIT may be dependent on one or more of: a) a number of sites and/or regions which have been configured, for example by a particular operator;
  • One or more of these factors may at least partially control a particular value of QLIMIT in request.
  • One or more of these factors may at least partially control the possible values of QLIMIT which can be used.
  • Some embodiments may provide one or more of the following advantages: since the number of records returned on the DNS interface may be less, this may result in lower DNS traffic; faster switching to emergency sites may occur in the case of a disaster when one or more nodes/sites are down;
  • filtering may be done at a central DNS server and may be consistent across clients;
  • client performance during processing of messages may be improved at the client may receive already filtered IPs.
  • the DNS may return less numbers of records, so that less processing done at client side (which does other call related processes), resulting in less DNS traffic.
  • the client itself may filter out the records before switching over to a new site.
  • FIG. 4 shows an example of a communication system enabled to offer multimedia services.
  • IP Internet Protocol
  • IM IP Multimedia
  • CN IP Multimedia Core Network
  • IMS IP Multimedia subsystem
  • IP Multimedia Network 45 is provided for offering IP multimedia services for IP Multimedia Network subscribers.
  • IP Multimedia (IM) functionalities can be provided by means of a mobile communication system.
  • a mobile communication system is typically arranged to serve a plurality of mobile user equipment usually via a wireless interface between the user equipment and at least one base station of the communication system.
  • the mobile communication system may logically be divided between a radio access network (RAN) and a core network (CN).
  • RAN radio access network
  • CN core network
  • base stations 31 and 40 are arranged to transmit signals to and receive signals from mobile user equipment 30, 41 of mobile users i.e. subscribers via a wireless interface between the user equipment and the radio access network.
  • a mobile user equipment is able to transmit signals to and receive signals from the radio access network via the wireless interface.
  • the user equipment 30, 41 may access the IMS network 45 via the access network associated with base station 31 , 40, respectively.
  • a mobile user equipment may comprise any appropriate mobile user equipment adapted for Internet Protocol (IP) communication to connect the network.
  • IP Internet Protocol
  • the mobile user may access the cellular network by means of a Personal computer (PC), Personal Data Assistant (PDA), mobile station (MS), smart phone and so on.
  • PC Personal computer
  • PDA Personal Data Assistant
  • MS mobile station
  • smart phone smart phone
  • a mobile station may include an antenna for wirelessly receiving and transmitting signals from and to base stations of the mobile communication network.
  • a mobile station may also be provided with a display for displaying images and other graphical information for the user of the mobile user equipment.
  • Camera means may be provided for capturing still or video images.
  • Speaker means are also typically provided.
  • the operation of a mobile station may be controlled by means of an appropriate user interface such as control buttons, voice commands and so on.
  • a mobile station is provided with a processor entity and a memory means.
  • the core network (CN) entities typically include various switching and other control entities and gateways for enabling the communication via a number of radio access networks and also for interfacing a single communication system with one or more communication system such as with other cellular systems and/or fixed line communication systems.
  • the radio access network controller is typically connected to an appropriate core network entity or entities such as, but not limited to, a serving general packet radio service support node (SGSN), see controllers 33 and 39 of Figure 1.
  • the radio access network is in communication with the serving GPRS support node via an appropriate interface, for example on an lu interface.
  • the SGSN typically has access to designated subscriber database configured for storing information associated with the subscription of the respective user equipment.
  • the serving GPRS support node in turn, typically communicates with a gateway GPRS support node via the GPRS backbone network 32. This interface is commonly a switched packet data interface.
  • a packet data session may be established to carry traffic flows over the network.
  • a packet data session is often referred as a packet data protocol (PDP) context.
  • a PDP context may include a radio bearer provided between the user equipment and the radio network controller, a radio access bearer provided between the user equipment, the radio network controller and the SGSN, and switched packet data channels provided between the serving GPRS service node and the gateway GPRS service node.
  • Each PDP context usually provides a communication pathway between a particular user equipment and the gateway GPRS support node and, once established, can typically carry multiple flows.
  • Each flow normally represents, for example, a particular service and/or a media component of a particular service.
  • the PDP context therefore often represents a logical communication pathway for one or more flow across the network.
  • radio access bearers To implement the PDP context between user equipment and the serving GPRS support node, radio access bearers (RAB) need to be established which commonly allow for data transfer for the user equipment.
  • RAB radio access bearers
  • the communication systems may be such that services are provided for the user equipment by means of various functions of the data network that are handled by controller entities, such as servers.
  • controller entities such as servers.
  • CSCFs call state control functions
  • the call state control functions may be divided into various categories such as a proxy call state control function (P-CSCF), interrogating call state control function (l-CSCF), and serving call state control function (S-CSCF).
  • P-CSCF proxy call state control function
  • l-CSCF interrogating call state control function
  • S-CSCF serving call state control function
  • similar functions may be referred to in different systems with different names.
  • the CSCFs may be referenced to as the call session control functions.
  • a user who wishes to use services provided by the IMS system may need first to register with a serving controller, such as the serving call session control function (S-CSCF) 36.
  • a serving controller such as the serving call session control function (S-CSCF) 36.
  • S-CSCF serving call session control function
  • P- CSCF proxy call session control function
  • the proxy CSCF 35 is thus for proxying messages from the GGSN 34 to a serving call session control function 36.
  • the serving controller i.e. CSCF 36 in Figure 4, in turn, provides the control entity the user equipment 30 needs to be registered with. The registration is required to enable the user equipment to request for a service from the communication system.
  • a policy control entity 37 may also be provided.
  • the policy control entity 37 may be configured to store required policy information in a database 38 thereof.
  • the network entities may query the policy control entity for various purposes, such as for obtaining information regarding the media policy of a particular user.
  • the policy control entity may be provided by means of a policy decision function (PDF), which is connected to P-CSCF and GGSN.
  • PDF policy decision function
  • FIG. 4 shows also an application server 50.
  • the user equipment may connect, via the GPRS network, to the application server that is connected to one or more data networks such as, but not limited to, the exemplifying Internet Protocol (IP) network.
  • IP Internet Protocol
  • S-CS Call State Control Function S-CS Call State Control Function
  • CSCF selecting an Application Server (AS) node from the given FQDN which resolves in multiple IPs.
  • AS Application Server
  • FIG. 5 shows a S-CSF 800, an Interconnection Border Control Function
  • the MGCF may provide call control protocol conversion.
  • the BGCF may act as a proxy which processes requests for routing from an S-CSCF.
  • the IBSF may provide a gateway to other networks.
  • the DNS is referenced 808.
  • Some embodiments may be used in the S-CSCF selecting an IBCF node from the given FQDN which resolves in multiple IPs.
  • Some embodiments may be used in the S-CSCF selecting a BGCF node from the given FQDN which resolves in multiple IPs.
  • Some embodiments may be used in the BGCF selecting a MGCF node from the given FQDN which resolves in multiple IPs.
  • Embodiments may be applied broadly. Embodiments are not limited to SIP entities. Rather embodiments, may be used in any network element which uses a DNS server for routing the requests.
  • Figure 6 shows an example of an apparatus 300 provided in or associated with any of the DNS client or server entities discussed.
  • the apparatus comprises at least one memory 301 , at least one data processing unit or at least one data processor 302, 303 and an input/output interface 304.
  • Some embodiments may be provided with any entity which uses DNS to resolve any server’s FQDN.
  • DNS resolve any server’s FQDN.
  • one common use may be where a computer is contacting a web server from a computer using a HTTP message.
  • the client uses a DNS server to resolve a web site FQDN which can be mapped to multiple IPs.
  • the required data processing apparatus and functions may be provided by means of one or more data processors.
  • the described functions may be provided by separate processors or by an integrated processor.
  • the data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi core processor architecture, as non-limiting examples.
  • the data processing may be distributed across several data processing modules.
  • a data processor may be provided by means of, for example, at least one chip. Appropriate memory capacity can be provided in the relevant devices.
  • the memory or memories may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • One or more of the steps discussed in relation to Figure 2 may be performed by one or more processors in conjunction with one or more memories.
  • An appropriately adapted computer program code product or products may be used for implementing the embodiments, when loaded or otherwise provided on an appropriate data processing apparatus.
  • the program code product for providing the operation may be stored on, provided and embodied by means of an appropriate carrier medium.
  • An appropriate computer program can be embodied on a computer readable record medium.
  • a possibility is to download the program code product via a data network.
  • the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Embodiments of the inventions may thus be practiced in various components such as integrated circuit modules.
  • the design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur un procédé consistant à amener une requête à être envoyée à un serveur de service de nom de domaine. Cette requête peut être envoyée par un client. La requête comprend des informations de nom et des informations indiquant que le serveur de service de nom de domaine doit renvoyer un nombre réduit de réponses d'enregistrement. En réponse à la requête, un nombre réduit de réponses d'enregistrement est fourni.
PCT/EP2018/051352 2018-01-19 2018-01-19 Procédés et appareil WO2019141376A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/051352 WO2019141376A1 (fr) 2018-01-19 2018-01-19 Procédés et appareil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/051352 WO2019141376A1 (fr) 2018-01-19 2018-01-19 Procédés et appareil

Publications (1)

Publication Number Publication Date
WO2019141376A1 true WO2019141376A1 (fr) 2019-07-25

Family

ID=61027716

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/051352 WO2019141376A1 (fr) 2018-01-19 2018-01-19 Procédés et appareil

Country Status (1)

Country Link
WO (1) WO2019141376A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100291943A1 (en) * 2008-01-23 2010-11-18 Attila Mihaly Method and Apparatus for Pooling Network Resources
US20100309784A1 (en) * 2008-01-23 2010-12-09 Attila Mihaly Selection of an Edge Node in a Fixed Access Communication Network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100291943A1 (en) * 2008-01-23 2010-11-18 Attila Mihaly Method and Apparatus for Pooling Network Resources
US20100309784A1 (en) * 2008-01-23 2010-12-09 Attila Mihaly Selection of an Edge Node in a Fixed Access Communication Network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CONTAVALLI W VAN DER GAAST GOOGLE S LEACH NAME COM D RODDEN NEUSTAR C: "Client IP information in DNS requests; draft-vandergaast-edns-client-ip-01.txt", CLIENT IP INFORMATION IN DNS REQUESTS; DRAFT-VANDERGAAST-EDNS-CLIENT-IP-01.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, no. 1, 21 May 2010 (2010-05-21), pages 1 - 23, XP015068632 *

Similar Documents

Publication Publication Date Title
CN105144631B (zh) 用于紧急呼叫路由故障转移的系统和方法
EP2135432B1 (fr) Mécanisme d'exécution d'une découverte de serveur
US7929419B2 (en) Methods, systems, and computer program products for inhibiting message traffic to an unavailable terminating SIP server
US8879442B2 (en) Methods and apparatus to enable call completion in internet protocol communication networks
US8681774B2 (en) System and method of routing voice communications via peering networks
EP1988685A2 (fr) Fourniture de service dans un système de télécommunication
CN101304366A (zh) 一种分组网络中实现负载均衡的方法、装置和系统
US11399005B2 (en) Method and apparatus for expedited domain name system query resolution
US20180132291A1 (en) SIP Call Continuity Upon Failure
EP2380338B1 (fr) Établissement d'un appel d'un réseau non ims à un réseau ims, la passerelle s'interfaçant avec l'hss
US8775610B2 (en) Identifying an application server in a plurality of application servers associated with a shared identifier
CN101325731B (zh) 分配服务呼叫会话控制功能方法、系统及归属用户服务器
WO2002009365A1 (fr) Systeme et procede pour determiner si un cscf doit agir comme i-cscf ou comme s-cscf
WO2019141376A1 (fr) Procédés et appareil
US12010154B2 (en) Support for IMS virtual clients in multi-operator environment
US11251993B2 (en) Gateway apparatus, message transmission method, and program
EP4096183B1 (fr) Procédé de réalisation de sessions de communication à l'aide d'un réseau de télécommunications et impliquant au moins un équipement utilisateur, réseau de télécommunications, entité ou fonctionnalité de traitement, équipement utilisateur, programme et support lisible par ordinateur
WO2023094009A1 (fr) Procédé, appareil et programme informatique
CN115866538A (zh) 短信处理方法、设备、系统及存储介质
CN101137209B (zh) 基于位置路由的系统及位置路由设备和方法
CN109327870A (zh) 与atcf通信的方法、装置、设备及计算机存储介质
EP1718018A2 (fr) Lorsque CSCF doit agir comme I-CSCF ou comme S-CSCF

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18701438

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18701438

Country of ref document: EP

Kind code of ref document: A1